[U-Boot] [PATCH 1/3] spl: set SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR to 0x4000 for rockchip
Jagan Teki
jagannadh.teki at gmail.com
Mon Nov 6 17:42:05 UTC 2017
On 06-Nov-2017 3:37 PM, "Kever Yang" <kever.yang at rock-chips.com> wrote:
Hi Jegan,
On 11/02/2017 03:32 PM, Jagan Teki wrote:
> On Thu, Nov 2, 2017 at 12:46 PM, Kever Yang <kever.yang at rock-chips.com>
> wrote:
>
>> Rockchip use a 'loader2' partition for U-Boot, so u-boot.bin or
>> u-boot.itb load by SPL need to locate at0x4000. Detail here:
>> http://opensource.rock-chips.com/wiki_Boot_option
>>
> Sorry, I'm not clear is this because of arm64 itb? and we should have
> 16320 sectors in between SPL and U-Boot which is huge isn't it?
>
No, this is nothing to do with arm64 itb.
You can over write this in your board if you use a different partition
table from Rockchip one.
We use 0x4000 because we have use this value for many years for U-Boot
image,
no matter it's uboot.img or u-boot.bin or u-boot.itb, I think it's better
to sync this
value for all Rockchip plaltform including Linux and Android OS in all SoCs.
Sorry, this I didn't understand we left 8M between SPL and U-Boot. What
exactly the use case I never observed any issue case like this.
Can you please elaborate, I understand I can override this but what to know
because generally falcon configuration itself start just from 2M
More information about the U-Boot
mailing list