From: David Jander <david.jander@protonic.nl>
To: u-boot@lists.denx.de
Subject: [U-Boot] New chapter in i.MX51 datasheet an issue?
Date: Fri, 4 May 2012 10:28:05 +0200 [thread overview]
Message-ID: <20120504102805.7f8d9e76@archvile> (raw)
Hi all,
I discovered a bug in u-boot, that got evident after Freescale updated the
i.MX51 datasheets to revision 5 in March this year. I don't know if it is a
serious problem or not, but if I believe the wording of the datasheet many of
the boards that use a i.MX51 processor and running u-boot as of latest git,
can potentially suffer "permanent damage", whatever that means.
I am referring to the new paragraphs at the end of chapter 4.3.4 of the
datasheet, and the wrong interpretation of the meaning of the HVE bit in the
iomuxc.h header file of u-boot here:
arch/arm/include/asm/arch-mx5/iomux.h:
...
69 PAD_CTL_DRV_VOT_LOW = 0x0 << 13, /* Low voltage mode */
70 PAD_CTL_DRV_VOT_HIGH = 0x1 << 13,/* High voltage mode */
...
According to the reference manual, the correct meaning of this bit is negated:
"Bit 13:
High / Low Output Voltage Range. This bit selects the output voltage mode for SD2_CMD.
0 High output voltage mode
1 Low output voltage mode"
Added to the new paragraph in the datasheet:
"The UHVIO type of I/O cells have to be configured properly according to their
supply voltage level, in order to prevent permanent damage to them and in
order to not degrade their timing performance."
Seems like we may have a problem here!
I would like to know if anyone is aware of this? Does anyone know of a board
that is actually destroyed this way?
Best regards,
--
David Jander
Protonic Holland.
reply other threads:[~2012-05-04 8:28 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=20120504102805.7f8d9e76@archvile \
--to=david.jander@protonic.nl \
--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