- Posts: 959
- Thank you received: 489
Great, yes please send me your bin file from the NVPMG and I can compare to the one from mine that was use to reverse engineer the payload. It will be interesting to see if they have made some changes.I connected stlink to my nvmpg to get a dump of the running firmware, it would be interesting to get a copy from someone that has a working to see if there's major difference? Scott, would you be able to take my .bin from my nvmpg and see if it differed from yours? I dont have the skills to reverse engineer things like you did up front but happy to poke about and learn more!
Please Log in or Create an account to join the conversation.
I will download the remora source plus the build system to add some debug messages and hopefully identify what is happening.tftp> status
Connected to 10.10.10.10.
Mode: netascii Verbose: on Tracing: on
Rexmt-interval: 5 seconds, Max-timeout: 25 seconds
tftp> put /tmp/config.txt
putting config.txt to 10.10.10.10:/tmp/config.txt [netascii]
sent WRQ <file=/tmp/config.txt, mode=netascii>
sent WRQ <file=/tmp/config.txt, mode=netascii>
sent WRQ <file=/tmp/config.txt, mode=netascii>
sent WRQ <file=/tmp/config.txt, mode=netascii>
sent WRQ <file=/tmp/config.txt, mode=netascii>
Transfer timed out.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Hi, thanks but something is not right with the file. It's only 99KB where the hex file I dumped from the MPG with ST-Link Utility is 400KB. On inspection, the file does not look like a valid bin file either.Attaching the nvmpg .bin I was able to extract from my unit. Hope this helps debug what's going on with the TFT/display oddities!
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.