[U-Boot] U-Boot stuck after relocation attempt on MX51 board
Benoît Thébaudeau
benoit.thebaudeau.dev at gmail.com
Thu Feb 26 22:10:08 CET 2015
.Hi Fabio,
On Wed, Feb 25, 2015 at 11:05 PM, Fabio Estevam <festevam at gmail.com> wrote:
> I have just tested top of tree U-boot and my mx53loco board boots fine.
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.
Best regards,
Benoît
More information about the U-Boot
mailing list