On Thu, Sep 30, 2010 at 8:00 AM, Shawn Guo <[email protected]> wrote:
>> Could we just use the same partition layout for all images (the imx51
>> one), avoiding the if entirely?
>>
> I'm unsure if OMAP ROM will be unhappy if the FAT partition is not at
> the beginning.
I agree. Also it feels risky to me to change the partition layout of
omap etc. at this point in cycle.
>> If you're using the early data on the image to store stuff, I recommend
>> you protect it with a dumb partition (e.g. "non-FS data" type, 0xda).
>>
> 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.
I think the non-FS data partition is only there so you dont get it
offered as free space if you later run fdisk etc.. Maybe see if
creating that non-fs partition hurts even if the start offset is a bit
odd.
>
>>> + 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.
>
> 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.
yeah. that was a bug i saw in some BSP u-boot for imx51 a few month
back. And yes, the mmc init already needs to be part of of the
built-in default commands in order to find the boot.scr on SD. So I
don't think we need it in boot.scr.
--
- Alexander
_______________________________________________
linaro-dev mailing list
[email protected]
http://lists.linaro.org/mailman/listinfo/linaro-dev
