From: vj <vicencb@gmail.com>
To: barebox@lists.infradead.org
Subject: Question about OMAP4 boot priorities
Date: Mon, 11 Mar 2013 01:43:38 +0100 [thread overview]
Message-ID: <CAAMcf8DGrgDQrOxJNe+mYoQ8R+3JF8FqW-V4HbA_a8+kFWd0Fg@mail.gmail.com> (raw)
Hello,
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:
1:MMC2(1)
2:USB(1)
3:UART
4:MMC1
scholbert from xda-developers identified some of the sys_boot pins:
http://forum.xda-developers.com/attachment.php?attachmentid=1062421&d=1337087327
And now the tablet is modified with sys_boot = 0x16
1:USB(1)
2:UART
3:MMC1
4:MMC2(1)
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,
Vicente.
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
reply other threads:[~2013-03-11 0:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAAMcf8DGrgDQrOxJNe+mYoQ8R+3JF8FqW-V4HbA_a8+kFWd0Fg@mail.gmail.com \
--to=vicencb@gmail.com \
--cc=barebox@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox