RGMII ETHERNET port of P2041 processor is showing alive in uboot but not pinging in kern

[avinashh]

Hello,

We have designed P2041 processor based custom design board.

We are using RGMII ETHERNET ports through PHY VSC8572 which can support two RGMII ports on a single chip.

RGMII 0 port is working fine at all speeds.

But for RGMII 1 port, we are able to see its "alive" in uboot in both loopback and communication path.

But when we try to ping at the kernel level with other PC, we are unable to ping and gives message "Destination Host  Unreachable" at all speeds (10/100/1000 Mbps).

We are using Yocto OS suggested for this processor.

We are unable to fix tis issue since we are trying from last few weeks.

Please support us ASAP to get out of this problem.

Thanks and regards,

Avinash

[avinashh]

Hi, Ufedor,

Awaiting your reply.

[avinashh]

I have attached the current Working DTS file

[avinashh]

Hi,

     The Kernel Ping Log shows only Destination Host Unreachable

[avinashh]

There is no ping log available in uboot. It will just show Host is either alive or not alive.

Regards,

Avinash

[ufedor]

2) There is no Linux ping log - not U-Boot

[avinashh]

In the image, it is shown as mii write 0x05 0x00 0x5040 which is for testing PHY in software loopback. But mii write 0x05 0x00 0x1040 is for communication with other PC.

This meant that it is alive in both loopback and on communication in the uboot.

Regards,

Avinash

[ufedor]

2) There is no Linux ping log

[ufedor]

1) Provided U-Boot log does not match with the previous picture.

2) There is no ping log

[avinashh]

Hi Ufedor,

In service I have not yet got any update.

Pl find textual form of your queries:

1. U-Boot log showing ping through the RGMII 1:

mii write 0x05 0x1f 0x0010

mii write 0x05 0x13 0x800f

mii write 0x05 0x1f 0x0000

mii write 0x05 0x18 0x2041

mii write 0x05 0x12 0x00a8

mii write 0x05 0x1f 0x0002

mii write 0x05 0x12 0x000e

mii write 0x05 0x1f 0x0000

mii write 0x05 0x00 0x1040

setenv ethprime FM1@DTSEC5

setenv ethact FM1@DTSEC5

setenv ipaddr 192.168.20.1

ping 192.168.20.2

----then result is host 192.168.20.2 is alive where 192.168.20.2 is other PC communicating to my device.

2. log of the 'ifconfig -a' and the ping in Linux:

fm1-gb3   Link encap:Ethernet  HWaddr 00:04:9f:02:03:fd 

          inet addr:192.168.3.100  Bcast:192.168.3.255  Mask:255.255.255.0

          inet6 addr: fe80::204:9fff:fe02:3fd/64 Scope:Link

          UP BROADCAST MULTICAST  MTU:1500  Metric:1

          RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:11 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:0 (0.0 B)  TX bytes:1058 (1.0 KiB)

          Memory:fe4e6000-fe4e6fff

fm1-gb4   Link encap:Ethernet  HWaddr 00:04:9f:02:04:fd 

          inet addr:192.168.4.100  Bcast:192.168.4.255  Mask:255.255.255.0

          inet6 addr: fe80::204:9fff:fe02:4fd/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:92 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:0 (0.0 B)  TX bytes:22054 (21.5 KiB)

          Memory:fe4e8000-fe4e8fff

Regards,

Avinash H

[avinashh]

Thanks Ufedor. I have created a Service request. case no. 00079062. Pl refer there.

[ufedor]

Please provide:

1) U-Boot log showing ping through the RGMII 1 port

2) DTS being used

3) log of the 'ifconfig -a' and the ping in Linux

[avinashh]

Hi,

required details:

1> U-Boot log showing ping through the RGMII 1:

             

2>  log of the 'ifconfig -a' and the ping in Linux

             

3>   DTS being used :

       Since we have restriction to upload files, please share your mail id. We will send the file by mail.

Regards,

Avinash

[ufedor]

Please provide textual logs - not pictures.

Please consider creating a Technical Case:

How I could create a Service Request? | NXP Community