public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [resent] New chapter in i.MX51 datasheet an issue?
Date: Sun, 06 May 2012 18:15:18 +0200	[thread overview]
Message-ID: <4FA6A396.6010201@denx.de> (raw)
In-Reply-To: <20120504120845.4f0e59ea@archvile>

On 04/05/2012 12:08, David Jander wrote:
> 
> Hi all,
> 

Hi David,

> 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 */
> ...
> 

Agree. The header defines the bit wrongly.

It seems to me that the Reference Manual is correct. It is from
24/2/2010 and it was not updated.

After a reset, value is set to 1, and this means low-voltage for the
most pins.

> 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?

At the moment, we have no problems and I can explain why. The only
boards setting these pins (for SD card) are mx51evk and vision2. Both
are setting PAD_CTL_DRV_VOT_HIGH, and because the define is wrong, they
are really setting the pin to low output voltage mode.

For other boards and other pins, voltage is not explicitely set : this
means they work in low voltage mode after a reset.

To fix arch/arm/include/asm/arch-mx5/iomux.h and synchronize it with the
documentation, we need also to change mx51evk / vision2, setting the
pins to PAD_CTL_DRV_VOT_LOW, and they will work as now.

We can also drop completely PAD_CTL_DRV_VOT_HIGH from these two boards
and use the reset value.

Best regards,
Stefano Babic

-- 
=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
=====================================================================

  reply	other threads:[~2012-05-06 16:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-04 10:08 [U-Boot] [resent] New chapter in i.MX51 datasheet an issue? David Jander
2012-05-06 16:15 ` Stefano Babic [this message]
2012-05-07  7:11   ` David Jander
2012-05-08  8:46     ` Stefano Babic
2012-05-08 10:23       ` Marek Vasut
2012-05-08 12:06       ` David Jander
2012-05-08 12:51         ` Marek Vasut
2012-05-09  9:31           ` David Jander
2012-05-08 13:14         ` Stefano Babic
2012-05-09  9:36           ` David Jander
2012-05-09 10:14             ` Stefano Babic

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=4FA6A396.6010201@denx.de \
    --to=sbabic@denx.de \
    --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