How to debug Ethernet connectivity

How to debug Ethernet connectivity

[Atilla Filiz]

Hello

I have been tasked to debug a port of Barebox to our custom board. It
has one Ethernet interface. All network related(dhcp, ping ...) tasks
fail with "Network is down" error, although the link lights on my
switch are on. So I did this on 2013.06:

--- barebox-2013.06.0.orig/net/
eth.c    2013-06-02 12:24:06.000000000 +0200
+++ barebox-2013.06.0/net/eth.c    2013-12-03 16:52:40.428089000 +0100
@@ -142,12 +142,16 @@

     if (force || is_timeout(last_link_check, 5 * SECOND) ||
             !eth_current->phydev->link) {
         ret = phy_update_status(eth_current->phydev);
         if (ret)
             return ret;
         last_link_check = get_time_ns();
     }

+    return 0;
     return eth_current->phydev->link ? 0 : -ENETDOWN;
 }

This bypasses link detection and assumes the link is always up. This
way, I got dhcp, ping and tftp working.

How can I debug this further to hunt down the Ethernet problem?
Something seems wrong with my PHY settings. This is an iMX27 based
board. Which files/functions/structures do I need to check?

--
Atilla Filiz

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

Re: How to debug Ethernet connectivity

[Sascha Hauer]

Hi Atilla,

On Fri, Dec 06, 2013 at 11:21:25AM +0100, Atilla Filiz wrote:
> Hello
> 
> I have been tasked to debug a port of Barebox to our custom board. It
> has one Ethernet interface. All network related(dhcp, ping ...) tasks
> fail with "Network is down" error, although the link lights on my
> switch are on. So I did this on 2013.06:
> 
> --- barebox-2013.06.0.orig/net/
> eth.c    2013-06-02 12:24:06.000000000 +0200
> +++ barebox-2013.06.0/net/eth.c    2013-12-03 16:52:40.428089000 +0100
> @@ -142,12 +142,16 @@
> 
>      if (force || is_timeout(last_link_check, 5 * SECOND) ||
>              !eth_current->phydev->link) {
>          ret = phy_update_status(eth_current->phydev);
>          if (ret)
>              return ret;
>          last_link_check = get_time_ns();
>      }
> 
> +    return 0;
>      return eth_current->phydev->link ? 0 : -ENETDOWN;
>  }
> 
> This bypasses link detection and assumes the link is always up. This
> way, I got dhcp, ping and tftp working.
> 
> How can I debug this further to hunt down the Ethernet problem?
> Something seems wrong with my PHY settings. This is an iMX27 based
> board. Which files/functions/structures do I need to check?

Most likely the phy_addr field in fec_platform_data is wrong.

It could also be that the pinmux for the MDIO lines to the phy
is misconfigured.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

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

Re: How to debug Ethernet connectivity

[Antony Pavlov]

On Fri, 6 Dec 2013 11:21:25 +0100
Atilla Filiz <atilla.filiz@gmail.com> wrote:

> Hello
> 
> I have been tasked to debug a port of Barebox to our custom board. It
> has one Ethernet interface. All network related(dhcp, ping ...) tasks
> fail with "Network is down" error, although the link lights on my
> switch are on. So I did this on 2013.06:
> 
> --- barebox-2013.06.0.orig/net/
> eth.c    2013-06-02 12:24:06.000000000 +0200
> +++ barebox-2013.06.0/net/eth.c    2013-12-03 16:52:40.428089000 +0100
> @@ -142,12 +142,16 @@
> 
>      if (force || is_timeout(last_link_check, 5 * SECOND) ||
>              !eth_current->phydev->link) {
>          ret = phy_update_status(eth_current->phydev);
>          if (ret)
>              return ret;
>          last_link_check = get_time_ns();
>      }
> 
> +    return 0;
>      return eth_current->phydev->link ? 0 : -ENETDOWN;
>  }
> 
> This bypasses link detection and assumes the link is always up. This
> way, I got dhcp, ping and tftp working.
> 
> How can I debug this further to hunt down the Ethernet problem?
> Something seems wrong with my PHY settings. This is an iMX27 based
> board. Which files/functions/structures do I need to check?

There is miitool command to view MII status / registers.

> --
> Atilla Filiz
> 
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox


-- 
-- 
Best regards,
  Antony Pavlov

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

Re: How to debug Ethernet connectivity

[Atilla Filiz]

On Fri, Dec 6, 2013 at 11:52 AM, Antony Pavlov <antonynpavlov@gmail.com> wrote:
> There is miitool command to view MII status / registers.


How do I use it?
barebox@Terminal:/ miitool -v /dev/mc13xxx
10 Mbit, half duplex, no link
  product info: vendor 00:00:00, model 0 rev 0
  basic mode:   10 Mbit, half duplex
  basic status: no link
  capabilities:
  advertising:
barebox@Terminal:/ dhcp
T DHCP client bound to address 10.3.4.161
barebox@Terminal:/ miitool -v /dev/mc13xxx
10 Mbit, half duplex, no link
  product info: vendor 00:00:00, model 0 rev 0
  basic mode:   10 Mbit, half duplex
  basic status: no link
  capabilities:
  advertising:

But there is link, obviously.
-- 
Atilla Filiz

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

Re: How to debug Ethernet connectivity

[Atilla Filiz]

Sorry, figured it out. Just most verbose output is funny as well:
:/ miitool -vvv /dev/mc13xxx
10 Mbit, half duplex, no link
  registers for MII PHY:
    0000 0000 0000 0000 0000 0000 0000 0000
    0000 0000 0000 0000 0000 0000 0000 0000
    0000 0000 0000 0000 0000 0000 0000 0000
    0000 0000 0000 0000 0000 0000 0000 0000
  product info: vendor 00:00:00, model 0 rev 0
  basic mode:   10 Mbit, half duplex
  basic status: no link
  capabilities:
  advertising:

On Fri, Dec 6, 2013 at 1:17 PM, Atilla Filiz <atilla.filiz@gmail.com> wrote:
> On Fri, Dec 6, 2013 at 11:52 AM, Antony Pavlov <antonynpavlov@gmail.com> wrote:
>> There is miitool command to view MII status / registers.
>
>
> How do I use it?
> barebox@Terminal:/ miitool -v /dev/mc13xxx
> 10 Mbit, half duplex, no link
>   product info: vendor 00:00:00, model 0 rev 0
>   basic mode:   10 Mbit, half duplex
>   basic status: no link
>   capabilities:
>   advertising:
> barebox@Terminal:/ dhcp
> T DHCP client bound to address 10.3.4.161
> barebox@Terminal:/ miitool -v /dev/mc13xxx
> 10 Mbit, half duplex, no link
>   product info: vendor 00:00:00, model 0 rev 0
>   basic mode:   10 Mbit, half duplex
>   basic status: no link
>   capabilities:
>   advertising:
>
> But there is link, obviously.
> --
> Atilla Filiz



-- 
Atilla Filiz

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

Re: How to debug Ethernet connectivity

[Alexander Aring]

On Fri, Dec 06, 2013 at 01:18:52PM +0100, Atilla Filiz wrote:
> Sorry, figured it out. Just most verbose output is funny as well:
> :/ miitool -vvv /dev/mc13xxx
> 10 Mbit, half duplex, no link
>   registers for MII PHY:
>     0000 0000 0000 0000 0000 0000 0000 0000
>     0000 0000 0000 0000 0000 0000 0000 0000
>     0000 0000 0000 0000 0000 0000 0000 0000
>     0000 0000 0000 0000 0000 0000 0000 0000
>   product info: vendor 00:00:00, model 0 rev 0
>   basic mode:   10 Mbit, half duplex
>   basic status: no link
>   capabilities:
>   advertising:
> 

In my opinion you reading only zeros from bus. Maybe check your muxing
which Sascha already mentioned.

- Alex

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

Re: How to debug Ethernet connectivity

[Sascha Hauer]

On Fri, Dec 06, 2013 at 01:18:52PM +0100, Atilla Filiz wrote:
> Sorry, figured it out. Just most verbose output is funny as well:
> :/ miitool -vvv /dev/mc13xxx

Don't know what miitool does in this case, but mc13xxx is not your phy,
it's your PMIC.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

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

Re: How to debug Ethernet connectivity

[Alexander Aring]

On Fri, Dec 06, 2013 at 01:39:25PM +0100, Sascha Hauer wrote:
> On Fri, Dec 06, 2013 at 01:18:52PM +0100, Atilla Filiz wrote:
> > Sorry, figured it out. Just most verbose output is funny as well:
> > :/ miitool -vvv /dev/mc13xxx
> 
> Don't know what miitool does in this case, but mc13xxx is not your phy,
> it's your PMIC.
> 

oh, doesn't realize that :D. So reading zeros can make sense in some
offset. :-)

- Alex

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

Re: How to debug Ethernet connectivity

[Atilla Filiz]

Ok, then my problem is slightly more clear, that /dev/phy0 does not exist.
I do define a struct fec_platform_data with
xcv_type=PHY_INTERFACE_MODE_MII and register it via imx27_add_fec().

Now I need to find out why it fails to register the device.

On Fri, Dec 6, 2013 at 1:43 PM, Alexander Aring <alex.aring@gmail.com> wrote:
> On Fri, Dec 06, 2013 at 01:39:25PM +0100, Sascha Hauer wrote:
>> On Fri, Dec 06, 2013 at 01:18:52PM +0100, Atilla Filiz wrote:
>> > Sorry, figured it out. Just most verbose output is funny as well:
>> > :/ miitool -vvv /dev/mc13xxx
>>
>> Don't know what miitool does in this case, but mc13xxx is not your phy,
>> it's your PMIC.
>>
>
> oh, doesn't realize that :D. So reading zeros can make sense in some
> offset. :-)
>
> - Alex



-- 
Atilla Filiz

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

Re: How to debug Ethernet connectivity

[Antony Pavlov]

On Tue, 10 Dec 2013 14:31:23 +0100
Atilla Filiz <atilla.filiz@gmail.com> wrote:

> Ok, then my problem is slightly more clear, that /dev/phy0 does not exist.
> I do define a struct fec_platform_data with
> xcv_type=PHY_INTERFACE_MODE_MII and register it via imx27_add_fec().
> 
> Now I need to find out why it fails to register the device.

There is issue with current barebox.

The /dev/phy0 device is unavailable till you use network.
You can use this (ugly!) way
  So just after boot type 'dhcp', next type 'ctrl-c' to interrupt dhcp and check /dev/phy0 presence.

> On Fri, Dec 6, 2013 at 1:43 PM, Alexander Aring <alex.aring@gmail.com> wrote:
> > On Fri, Dec 06, 2013 at 01:39:25PM +0100, Sascha Hauer wrote:
> >> On Fri, Dec 06, 2013 at 01:18:52PM +0100, Atilla Filiz wrote:
> >> > Sorry, figured it out. Just most verbose output is funny as well:
> >> > :/ miitool -vvv /dev/mc13xxx
> >>
> >> Don't know what miitool does in this case, but mc13xxx is not your phy,
> >> it's your PMIC.
> >>
> >
> > oh, doesn't realize that :D. So reading zeros can make sense in some
> > offset. :-)
> >
> > - Alex
> 
> 
> 
> -- 
> Atilla Filiz
> 
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox


-- 
-- 
Best regards,
  Antony Pavlov

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

Re: How to debug Ethernet connectivity

[Antony Pavlov]

On Tue, 10 Dec 2013 14:31:23 +0100
Atilla Filiz <atilla.filiz@gmail.com> wrote:

> Ok, then my problem is slightly more clear, that /dev/phy0 does not exist.
> I do define a struct fec_platform_data with
> xcv_type=PHY_INTERFACE_MODE_MII and register it via imx27_add_fec().
> 
> Now I need to find out why it fails to register the device.

There is an issue with current barebox.

The /dev/phy0 device not present just after boot. You need somehow to use network
to make it appeared.

Use this [ugly!] method:
  Run barebox on your board. Just after boot /dev/phy0 is absent.
  So run 'dhcp' command. In a few seconds press "ctrl-c" to interrupt it.
  Check /dev/phy0 presence.

 

> On Fri, Dec 6, 2013 at 1:43 PM, Alexander Aring <alex.aring@gmail.com> wrote:
> > On Fri, Dec 06, 2013 at 01:39:25PM +0100, Sascha Hauer wrote:
> >> On Fri, Dec 06, 2013 at 01:18:52PM +0100, Atilla Filiz wrote:
> >> > Sorry, figured it out. Just most verbose output is funny as well:
> >> > :/ miitool -vvv /dev/mc13xxx
> >>
> >> Don't know what miitool does in this case, but mc13xxx is not your phy,
> >> it's your PMIC.
> >>
> >
> > oh, doesn't realize that :D. So reading zeros can make sense in some
> > offset. :-)
> >
> > - Alex
> 
> 
> 
> -- 
> Atilla Filiz
> 
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox


-- 
-- 
Best regards,
  Antony Pavlov

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

Re: How to debug Ethernet connectivity

[Alexander Aring]

On Tue, Dec 10, 2013 at 07:24:40PM +0400, Antony Pavlov wrote:
> On Tue, 10 Dec 2013 14:31:23 +0100
> Atilla Filiz <atilla.filiz@gmail.com> wrote:
> 
> > Ok, then my problem is slightly more clear, that /dev/phy0 does not exist.
> > I do define a struct fec_platform_data with
> > xcv_type=PHY_INTERFACE_MODE_MII and register it via imx27_add_fec().
> > 
> > Now I need to find out why it fails to register the device.
> 
> There is issue with current barebox.
> 
> The /dev/phy0 device is unavailable till you use network.
> You can use this (ugly!) way
>   So just after boot type 'dhcp', next type 'ctrl-c' to interrupt dhcp and check /dev/phy0 presence.
> 
mh, bad... :( Maybe just try a ping instead of dhcp to bring /dev/phy0
alive. But that's a ugly hack, too.

Is there no some global(var/env) to enable it?

- Alex

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

Re: How to debug Ethernet connectivity

[Atilla Filiz]

My problem is, /dev/phy0 never appears when I give the correct phy address.

Unable to find a PHY (unknown ID?)
dhcp failed: I/O error
dhcp: I/O error

Also, fec_probe function for fec_imx driver never gets called.
Ironically, I do not get an I/O error when I give the wrong phy
address. Still nothing gets detected and no device node appears, but
ethernet works(by forcing the line detect functions to return 0).


I will talk to the hardware guys to verify the pin muxing and phy address.

On Tue, Dec 10, 2013 at 6:46 PM, Alexander Aring <alex.aring@gmail.com> wrote:
> On Tue, Dec 10, 2013 at 07:24:40PM +0400, Antony Pavlov wrote:
>> On Tue, 10 Dec 2013 14:31:23 +0100
>> Atilla Filiz <atilla.filiz@gmail.com> wrote:
>>
>> > Ok, then my problem is slightly more clear, that /dev/phy0 does not exist.
>> > I do define a struct fec_platform_data with
>> > xcv_type=PHY_INTERFACE_MODE_MII and register it via imx27_add_fec().
>> >
>> > Now I need to find out why it fails to register the device.
>>
>> There is issue with current barebox.
>>
>> The /dev/phy0 device is unavailable till you use network.
>> You can use this (ugly!) way
>>   So just after boot type 'dhcp', next type 'ctrl-c' to interrupt dhcp and check /dev/phy0 presence.
>>
> mh, bad... :( Maybe just try a ping instead of dhcp to bring /dev/phy0
> alive. But that's a ugly hack, too.
>
> Is there no some global(var/env) to enable it?
>
> - Alex



-- 
Atilla Filiz

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

Re: How to debug Ethernet connectivity

[Sascha Hauer]

On Tue, Dec 10, 2013 at 07:30:29PM +0400, Antony Pavlov wrote:
> On Tue, 10 Dec 2013 14:31:23 +0100
> Atilla Filiz <atilla.filiz@gmail.com> wrote:
> 
> > Ok, then my problem is slightly more clear, that /dev/phy0 does not exist.
> > I do define a struct fec_platform_data with
> > xcv_type=PHY_INTERFACE_MODE_MII and register it via imx27_add_fec().
> > 
> > Now I need to find out why it fails to register the device.
> 
> There is an issue with current barebox.
> 
> The /dev/phy0 device not present just after boot. You need somehow to use network
> to make it appeared.
> 
> Use this [ugly!] method:
>   Run barebox on your board. Just after boot /dev/phy0 is absent.
>   So run 'dhcp' command. In a few seconds press "ctrl-c" to interrupt it.
>   Check /dev/phy0 presence.

This is really annoying and something which I'd like to have fixed for longer.
I'm currently working my way through the phy layer to fix that.

Sascha


-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

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

Re: How to debug Ethernet connectivity

[Sascha Hauer]

On Wed, Dec 11, 2013 at 10:39:17AM +0100, Atilla Filiz wrote:
> My problem is, /dev/phy0 never appears when I give the correct phy address.
> 
> Unable to find a PHY (unknown ID?)
> dhcp failed: I/O error
> dhcp: I/O error
> 
> Also, fec_probe function for fec_imx driver never gets called.

If that's the case...

> Ironically, I do not get an I/O error when I give the wrong phy
> address. Still nothing gets detected and no device node appears, but
> ethernet works(by forcing the line detect functions to return 0).

...your ethernet can't possibly work.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

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