Hi Ben,
On 30 April 2015 at 00:27, Ben Hewson ben@frazer-nash.com wrote:
Hi Simon,
Thanks for the suggestion. I actually sorted it out late yesterday. A stupid error I suppose, but one that I completely over looked.
I turned on CONFIG_DEBUG_LL in the kernel, tried again and it complained about the machine id not matching.
I just needed to change CONFIG_MACH_TYPE to the correct number in U-Boot.
I didn't realise until after some googling that this was done. I just assumed U-Boot did a jump to the kernel start and that was it. Still live and learn !
The only issue I have now, is that if I enable CONFIG_ENV_IS_IN_FAT U-Boot tries to load the environment before the SATA is initialised and fails. If I do sata init at the U-Boot prompt, I can save the environment, but that is not much use if it isnt loaded at boot.
I can probably live without being able to save the environment, but would be nice to have the option. I did notice after having a quick look through the code that there appears to be a late load option for the environment. Can't remember exactly what it was.
OK, I'm not sure about environment on SATA. It looks like initr_env() is called before initr_pci() and initr_scsi() so you might be out of luck for now.
Regards, Simon
[snip]