Dear Rogan Dawes,
In message 4C6BAC5A.6060206@dawes.za.net you wrote:
Thanks for the suggestion. It did make a slight difference in the boot logs. bootcmd uses the default (in flash) location for the ramdisk,
Actually it's a pretty significant difference, as for the first time you actually see the kernel trying to access the ramdisk.
RAMDISK: Compressed image found at block 0 invalid compressed format (err=1)
So it seems that the ramdisk is getting corrupted somehow. And yet, it is fine using the vendor u-boot. It must be something that I am doing wrong.
Try copying the raw ramdisk image (i. e. without the U-Boot header) to RAM, and try that one, i. e. something like
=> cp.b ff9a0040 01600000 ...size... ... => bootm ff820000 1600000
Best regards,
Wolfgang Denk