That does seem to be what's wrong. The default mx50_usb_work.conf file I have wants to upload an SPL, then u-boot, then it does something I don't understand via the SPL.
Your configuration fails for me because it still doesn't know where to load the binary.
The most working configuration I've found is to adapt the existing script to not try and load the SPL.
u-boot's linked at 0x79800000, so I've tried:
Code:
mx50
hid,64,0xf8006400,0xf8006400,128M,0x70000000,256M
u-boot.bin:load 0x79800000
But this just produces errors which suggest that there's no memory there...
Code:
parse .//mx50_usb_work.conf
Trying to open device vid=0x15a2 pid=0x0052
Interface 0 claimed
HAB security state: development mode (0x56787856)
== work item
filename u-boot.bin
load_size 0 bytes
load_addr 0x79800000
dcd 0
clear_dcd 0
plug 0
jump_mode 2
jump_addr 0x79800000
== end work item
loading binary file(u-boot.bin) to 79800000, skip=0, fsize=10cec type=aa
report 2 out err=-1, last_trans=0 len=0x40 max=0x40 retry=10
report 2 out err=-1, last_trans=0 len=0x40 max=0x20 retry=9
report 2 out err=-1, last_trans=0 len=0x40 max=0x10 retry=8
report 2 out err=-1, last_trans=0 len=0x40 max=0x8 retry=7
report 2 out err=-1, last_trans=0 len=0x40 max=0x10 retry=6
report 2 out err=-1, last_trans=0 len=0x40 max=0x8 retry=5
report 2 out err=-1, last_trans=0 len=0x40 max=0x10 retry=4
report 2 out err=-4, last_trans=0 len=0x40 max=0x8 retry=3
report 2 out err=-4, last_trans=0 len=0x40 max=0x10 retry=2
report 2 out err=-4, last_trans=0 len=0x40 max=0x8 retry=1
Giving up
On startup I get this out of the serial port:
Code:
MC: FSL_ESDHC: 0, FSL_ESDHC: 1
Board: Unknown
Boot Reason: [POR]
Boot Device: MMC
Board Id:
S/N:
Invalid board id! Can't determine system type for RAM init.. bailing!
DRAM: 0 kB
Using default environment
AFAIK this is a classic symptom of eMMC failure, as it can't read the configuration information and cannot configure the DRAM. Therefore, I can't load u-boot into DRAM.
I know that some Kindles have two versions of u-boot: one which is small enough to run from the on-chip RAM, and one which has things like fastboot and bist linked in which are run once the DRAM is set up.
So I'm going to guess that I need to reproduce the cut-down uboot which can run from the on-chip RAM and run that. Is this the one called imx50_yoshi_mfgtool_config? That is also linked at 0x79800000, though...