On Thu, Sep 30, 2010, Shawn Guo wrote:
I'm unsure if OMAP ROM will be unhappy if the FAT partition is not at the beginning.
According to the docs, OMAP ROM searches for a FAT partition with the bootable flag turned on. It certainly doesn't care (too much) about the location of the partition. I added a non-FS data partition in the bzr version now, and factored your code with the general case.
The u-boot.imx really needs to be at offset 1KB on card to make imx51 ROM happy. Even I create the "non-FS data" partition from 0 cylinder with sfdisk, it actually starts from sector 63 (offset ~ 32KB). We can not really get the u-boot.imx into this partition for now.
Sounds like a bug in sfdisk. I guess we need to move to parted at some point.
- cat > ${TMP_DIR}/boot.cmd << BOOTCMD
+setenv bootcmd 'fatload mmc 0:1 0x90000000 uImage; fatload mmc 0:1 0x90800000 uInitrd; bootm 0x90000000 0x90800000'
no mmc init?
This is something I'm not very clear. This bootcmd is written into boot.scr which has to be loaded out from card first, in order to launch the bootcmd. So we need to get "mmc init" executed before we load fatload boot.scr.
Hmm you're right; I was wondering because the other boards at one, but these boards need to drop it! Fixed
Maybe it's an issue. The u-boot.imx "mmc init" is not working in this case. I have to run "mmcinfo" before the first fatload, or it hangs.
If "mmc init" breaks in mx51evk u-boot, we should probably fix it; you could start by filing a bug against u-boot-linaro to track this, explaining how to trigger the bug.