From: David Jander <david.jander@protonic.nl>
To: u-boot@lists.denx.de
Subject: [U-Boot] [resent] New chapter in i.MX51 datasheet an issue?
Date: Wed, 9 May 2012 11:31:36 +0200 [thread overview]
Message-ID: <20120509113136.08149af6@archvile> (raw)
In-Reply-To: <201205081451.52689.marex@denx.de>
On Tue, 8 May 2012 14:51:52 +0200
Marek Vasut <marex@denx.de> wrote:
> Dear David Jander,
>
> > On Tue, 08 May 2012 10:46:10 +0200
> >
> > Stefano Babic <sbabic@denx.de> wrote:
> > > On 07/05/2012 09:11, David Jander wrote:
> > > > Dear Stefano,
> > >
> > > Hi David,
> > >
> > > > Yes, but is none of those boards using 3.15 or 3.3V? If they are, those
> > > > bits must be cleared!
> > >
> > > This is a good question - also because SD was tested and it is working
> > > on these cards. I am asking to myself how it can work if voltage is
> > > wrong.
> >
> > That is the whole point: You probably won't notice anything with the wrong
> > settings.... besides slightly lower drive-strength on the pin. Things
> > should just work with either setting. The problem is that now Freescale is
> > telling us that using the incorrect settings can cause "permanent damage"
> > to the chip!!! No idea what sort of damage nor whether it occurs
> > frequently.....
>
> I think it might have something to do with ESD. It's probably unlikely to happen
> anyway.
Why do you think that?
ESD protection is not something that could possibly have something to do with
a running board and wrong PAD configuration bit settings. Or do you mean that
IO-pad ESD protection is the thing that gets destroyed by wrong settings?
AFAICS, this bit probably enables and disables a different set of output
transistors on the pad.
Whether damage is likely to happen or not, is not clear to me yet. I am waiting
on a reply from Freescale about this issue right now. I will post any important
findings here as soon as I know more.
Best regards,
--
David Jander
Protonic Holland.
next prev parent reply other threads:[~2012-05-09 9:31 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
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 [this message]
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=20120509113136.08149af6@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