[U-Boot] U-Boot stuck after relocation attempt on MX51 board

[Albert ARIBAUD <albert.u.boot@aribaud.net>]

Hello Fabio,

On Sat, 28 Feb 2015 12:56:25 -0300, Fabio Estevam <festevam@gmail.com>
wrote:
> Hi Beno?t,
> 
> On Thu, Feb 26, 2015 at 6:10 PM, Beno?t Th?baudeau
> <benoit.thebaudeau.dev@gmail.com> wrote:
> 
> > That's because CONFIG_HAS_VBAR is set for ARMv7. There may be an
> > issue, though: according to Freescale, the TrustZone security
> > extensions are present on i.MX514/515/516/53x, but not on i.MX512/513.
> > According to ARM, the security extensions seem to always be
> > implemented on Cortex-A8, so it's not clear what Freescale means for
> > i.MX512/513, and if the non-secure VBAR is still available on these.
> > If not, 0x00000000 is the boot ROM, and 0xFFFF0000 is reserved, just
> > like on i.MX25/27/31/35, so disabling CONFIG_HAS_VBAR for i.MX512/513
> > would not help, and your vector relocation patch would be required
> > here too. It would be nice if someone could test the latest U-Boot on
> > i.MX512/513.
> 
> That's a good point. I don't have access to the mx512/mx513 variants though.

Another point is that just skipping vectors relocation is akin to
papering over the issue. If there is any change done in U-Boot, I would
like it to actually ensure that exception handlers are actually called,
as I did with commit db544b96.

> Regards,
> 
> Fabio Estevam

Amicalement,
-- 
Albert.