mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: gianluca <gianlucarenzi@eurek.it>
To: Antony Pavlov <antonynpavlov@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: Ethernet PHY KSZ9031 is not working
Date: Thu, 3 Mar 2016 14:47:26 +0100	[thread overview]
Message-ID: <56D8406E.6020208@eurek.it> (raw)
In-Reply-To: <20160303165252.0911b6cb49599a5bc06090ca@gmail.com>

On 03/03/2016 02:52 PM, Antony Pavlov wrote:

>> When Barebox takes control over, those pins are turned off, the device
>> tree information is telling me:
>>
>>> `-- 2188000.ethernet
>>>     `-- miibus0
>>>        `-- phy0
>>>           `-- 0x00000000-0x0000003f ( 64 Bytes): /dev/phy0
>>>     `-- eth0
>>
>> but when I try to bring up the ethernet connection here is the message:
>>
>>> dhcp
>>> warning: No MAC address set. Using random address ae:05:f1:62:bd:d8
>>> ksz9031rn_phy_fixup Called
>>> ksz9031rn_phy_fixup Exit
>>> dhcp: Network is down
>>
>> And all leds in the RJ-45 JackMag are still turned off.
>>
>> I don't know where I can check if something goes wrong. May be a failure
>> on board, but at this time this board is the ONLY BOARD I can use.
>
> Use 'miitool -v -v' command to check your phy registers and the link status.
>

Thank you for this hint.
Before digging on the Datasheet for the explanation of all MII PHY 
registers, here is the output of the command you wrote above:

> barebox@EK360 Eurek i.MX6 Quad:/ miitool -v -v
> phy0: 2188000.ethernet-1: no link
> registers for MII PHY:
> 1140 7949 0022 1622 01e1 0000 0006 2001
> 0000 0300 0000 0000 0000 0000 0000 3000
> 0000 00f4 0000 0000 0000 0000 0000 0200
> 0000 0000 0000 0028 0000 0000 0000 0301
> product info: Micrel KSZ9031 Gigabit PHY (vendor 00:08:85, model 34 rev 2)
> basic mode: autonegotiation enabled
> basic status: no link
> capabilities: 1000baseT-FD 1000baseT-HD 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
> advertising: 1000baseT-FD 1000baseT-HD 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
>

So, the link between the FEC and the PHY it is seems to working good.
If everything seems to be ok (speaking about registers) maybe there is 
some issue on the RJ-45 MagJack connector.

What kind of RJ45 are you using?? I am using a 1000/100/10 from Wuerth 
Elektronic named:
Artikelnummer / part number :
Bezeichnung :
description :
7499111121A
LAN-Übertrager WE-RJ45LAN 10/100/1000 BaseT
LAN-Transformer WE-RJ45LAN 10/100/1000 BaseT

Best Regards,
Gianluca
-- 
Eurek s.r.l.                          |
Electronic Engineering                | http://www.eurek.it
via Celletta 8/B, 40026 Imola, Italy  | Phone: +39-(0)542-609120
p.iva 00690621206 - c.f. 04020030377  | Fax:   +39-(0)542-609212

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2016-03-03 13:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-03 12:44 gianluca
2016-03-03 13:52 ` Antony Pavlov
2016-03-03 13:47   ` gianluca [this message]
2016-03-03 15:21     ` Antony Pavlov
2016-03-04 11:12       ` Ethernet PHY KSZ9031 is not working [SOLVED] gianluca
2016-03-03 14:42 ` Ethernet PHY KSZ9031 is not working Holger Schurig
2016-03-09  8:58   ` Alexander Aring
2016-03-16 12:34     ` Holger Schurig
2016-03-03 14:53 ` Sascha Hauer

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=56D8406E.6020208@eurek.it \
    --to=gianlucarenzi@eurek.it \
    --cc=antonynpavlov@gmail.com \
    --cc=barebox@lists.infradead.org \
    /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