From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/1] ARM: mxs: get boot mode from OTP
Date: Thu, 26 Mar 2015 15:57:14 +0100 [thread overview]
Message-ID: <1427381834.21230.10.camel@embedded.rocks> (raw)
In-Reply-To: <5513FC3A.8050606@denx.de>
Hi Stefano,
On Do, 2015-03-26 at 13:31 +0100, Stefano Babic wrote:
> Hi J?rg,
>
> On 26/03/2015 10:39, J?rg Krause wrote:
> > Reading the GPIOs for getting the boot mode does not show the correct result
> > for USB boot mode in case the recovery switch, eg. BM2 for switching from NAND
> > to USB boot mode, is hold down while plugging in USB and released before U-Boot
> > is loaded by mxsldr.
> >
> > This state is stored in the HW_OCOTP_ROM0 register. HW_OCOTP_ROM0[27:24] maps to
> > BM3-BM0, HW_OCOTP_ROM0[28] maps to voltage selector.
> >
> > For using mxs_wait_mask_clr() add imx-common/misc.o to the SPL build.
> >
>
> As far as I understand from the manual, bootmode is *always* copied
> fromt the OTP after a reset. Then, I agree that is better to use OCOTP
> as the GPIOs. GPIOs were already sampled by ROM at reset and their value
> could be different when evaluated by SPL.
I fear the patch does not work as I expected. With OCOTP_ROM0 the boot
mode can be blown, but it does not present the state of the BM pads as I
understood from the RM. I thought the patch works because the boot mode
is read as USB (0x0) if I do USB recovery, but it's also 0x0 for NAND
boot.
Sadly, no reliable way to detect boot mode. Sorry for submitting to
early!
Best regards
J?rg Krause
next prev parent reply other threads:[~2015-03-26 14:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 9:39 [U-Boot] [PATCH 1/1] ARM: mxs: get boot mode from OTP Jörg Krause
2015-03-26 12:31 ` Stefano Babic
2015-03-26 14:57 ` Jörg Krause [this message]
2015-03-26 22:57 ` Jörg Krause
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=1427381834.21230.10.camel@embedded.rocks \
--to=joerg.krause@embedded.rocks \
--cc=u-boot@lists.denx.de \
/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