[U-Boot] ARM: Incorrect ROM protection range?

[Wolfgang Denk]

Dear Albert ARIBAUD,

In message <4D6611A7.5050802 at free.fr> you wrote:
> 
> >>> In the U-Boot image itself, knowing the image size could be achieved in
> >>> ARM by using a general _end symbol that would be set after the last
> >>> image output section, so _end-_start would equal the image size.
> >>
> >> we have such a "_end" in u-boot.lds files.
> 
> I *knew* this name did not pop up in my mind without a reason. :)
> 
> Apologies for not having checked.
> 
> > I guess we need a __dynsym_end in all u-boot.lds files.
> 
> I'd rather go for "_end", which does not tie the solution to dynsym 
> being the last section in the image -- imagine for some reason we move 
> dynsym inside the image rather than at the end, end the image size will 
> be wrong again. With _end, and a suitable comment in the LD file... this 
> will be averted where-ever dynsym ends up.
> 
> After all, the bug you uncovered was due to using the wrong symbol, a 
> BSS related one rather than an image-related one, in the first place; so 
> let's try and learn from past mistakes.

I think the location of _end in the linker scripts needs to be changed
- so far it covers the maximum of dynsym and bss, but it should refer
to the end of dynsym only.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
If in any problem you find yourself doing an immense amount of  work,
the answer can be obtained by simple inspection.