[U-Boot] after relocation, the original text_base memory section can't be used

[Albert ARIBAUD]

Hi,

Le 26/05/2011 11:04, Yuping Luo a écrit :
> Hi,
>
>       With 2011.03 uboot, I am adding firmware flashing feature to our
> arm cortex a9 soc platform via usb, in which the data firstly be
> uploaded to memory wholly (more than 200MB, thanks our 512MB physical
> memory), then burned.
>       By my understanding, after relocation the successive memory range
> (0~~ relocaddr) can be (re)used. however, if the original text section
> (in my case, 0x01500000) is written, the data abort happens when
> accessing 0x01600000; if the memory section (0x01500000~0x01600000)
> not written, everything is ok. please correct me if I am wrong.

Well, what is sure is that not all of 1500000-1600000 was used before 
relocation either (it ends around 1546000), so 1600000 was not accessed 
before reloc. How can you be sure the issue happens after reloc? For all 
we know, it could be a bug in the code code that writes 1500000 to 
1600000 itself.

Amicalement,
-- 
Albert.