Quote:
Originally Posted by Bergfux
1) To interrupt the boot sequence only the "enter" key works. Any other key won't interrupt it.
2)The serial to USB converter I use is this one https://www.ebay.de/itm/Mini-FTDI-Ad...0AAOSwnHZYU5l1
I've found something interesting on this website:
http://www.xodustech.com/guides/kind...te-demo-unlock
This tutorial shows how to find out the hexa value (0xE41000) for booting into diagsnostic mode.
instead of the entry "bootcmd=bootm 0xE41000" I have the entry "bootcmd=mmc dev ${mmcdev};if mmc rescan; then run testboot; fi;"
Could there be the problem?  |
this is really great research, they have started changing things on that device considerably.
Can you try running that command 'diags_boot', or running all those command in order, but also run the 'env' command betweejn the steps, to see if anyhting changes.
you see it runs severla commands before it runs 'bootm $loadaddr - $fdt_addr', lt looks like somewhere in those commands it will set the real value that you need to use, and after that 'rum mmcargs_diags' command, "$loadaddr - $fdt_addr" will be the replacement for 0xe41000 on that sprcific device.