From: Nikolay Dimitrov <picmaster@mail.bg>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] mx6cuboxi: Fix Ethernet PHY detection problem
Date: Mon, 04 May 2015 07:18:51 +0300 [thread overview]
Message-ID: <5546F32B.4020600@mail.bg> (raw)
In-Reply-To: <1430710213-28008-1-git-send-email-festevam@gmail.com>
Hi Fabio,
On 05/04/2015 06:30 AM, Fabio Estevam wrote:
> From: Fabio Estevam <fabio.estevam@freescale.com>
>
> mx6cuboxi sometimes fails to recognize the Ethernet PHY:
>
> Net: Phy 0 not found
>
> The explanation comes from a patch from Rabeeh:
>
> "The LED_ACT pin on the carrier-one boards had a pull down that
> forces the phy address to 0x0; where on CuBox-i and the production
> HummingBoard that pin is connected directly to LED that depending on
> the pull down strength of the LED it might be sampled as '0' or '1'
> thus the phy address might appear as either address 0x0 or 0x4."
There's no such thing as "LED pull-down". The forward voltage drop of a
LED is between 1.65V (red low-power LEDs) to 2.1V (green LEDs) to even
more for blue LEDs. Even the lowest Vf doesn't qualify as logic "0" for
LVCMOS33, which is around 1V max (Vil). The LED just can't pull-down the
voltage level low enough.
So, unless you have some control over the pin (via a programmable
on-chip pull-up or pull-down) which I doubt as it's a PHY pin, the
actual behavior is that the pin is floating, and samples a random value
at boot. Which means, the hardware is just buggy.
Kind regards,
Nikolay
next prev parent reply other threads:[~2015-05-04 4:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-04 3:30 [U-Boot] [PATCH 1/2] mx6cuboxi: Fix Ethernet PHY detection problem Fabio Estevam
2015-05-04 3:30 ` [U-Boot] [PATCH 2/2] mx6cuboxi: Pull down PAD_ENET_RXD0/RXD1 Fabio Estevam
2015-05-04 4:18 ` Nikolay Dimitrov [this message]
2015-05-04 12:22 ` [U-Boot] [PATCH 1/2] mx6cuboxi: Fix Ethernet PHY detection problem Fabio Estevam
2015-05-04 14:06 ` Nikolay Dimitrov
2015-05-04 12:35 ` Rabeeh Khoury
2015-05-04 13:49 ` Nikolay Dimitrov
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=5546F32B.4020600@mail.bg \
--to=picmaster@mail.bg \
--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