Question about OMAP4 boot priorities

vj vicencb at
Sun Mar 10 20:43:38 EDT 2013

I'm experimenting with a tablet with an OMAP4460 SoC. It's not a
development board with easy access to the sys_boot pins.
It's factory defaults for sys_boot is 0x36 which defines a boot
priority as follows:
scholbert from xda-developers identified some of the sys_boot pins:
And now the tablet is modified with sys_boot = 0x16
To check the modification:
	printf("sys_boot = 0x%08X\n", readl(0x4A0022C4));
	sys_boot = 0x00000B16
Which confirms the modification is correct.
for more information on this register see Table 18-178. CONTROL_STATUS
on OMAP4460_1.x_TRM_vX

Now the tablet has no cables connected (nor serial, nor usb), so what
I expect is:
 1) The SoC will detect there is no usb cable connected and will skip
the 3 seconds timeout
 2) The SoC will try to boot over serial port and will abort after a
300 ms timeout
 3) A micro SD-card is inserted and is connected to the MMC1
controller so the SoC will detect and boot it.
What really happens:
 1) Don't know...
 2) ...
 n) After less than a second MMC2(1) is booted.

The contents of the SD-card are correct as I could make it boot on
warm reset modifying accordingly the SAR memory.

So the question is: why the SoC does not behave as expected?
Has any body tried this? Does anybody has a development board in which
testing this is easy? in such case, works?

Thank you all,

More information about the barebox mailing list