Issue with MMU-less OMAP4

Vicenç vicencb at
Mon Aug 8 08:10:49 PDT 2016

I've updated the barebox version running on an archosG9 board since a
long time ago and it broke.
After searching for the problem found the commit causing the issue:;a=commitdiff;h=dba6b4919e5b678b3b78b828b54504913577d337
When booting from USB is desired in an OMAP4 system, the MMU needs to
be disabled because the ROM code that deals with the USB
communications does not get on well with it.

The issue is that it "hangs" when calling:
set_vbar((unsigned int)vectors);
I have no idea on how to fix the issue other than reverting the commit.

Does that happen on other OMAP4 boards when the MMU is disabled?
Does that happen on other OMAPs?
Does that happen on other ARMs?

If a fix if found, I would be glad to test.

  Vicente Bergas.

More information about the barebox mailing list