AnsweredAssumed Answered

LX2160ARDB - DPMAC17@rgmii-id link not up with 4.14 Early Access kernel

Question asked by Tuan Nguyen on Feb 27, 2019
Latest reply on Mar 4, 2019 by Tuan Nguyen

Hello,

 

I am pretty new to NXP and I need your help.

 

The issue I have is with network interface DPMAC17@rgmii-id on my board LX2160ARDB when booting with NXP's linux kernel 4.14 Early Access branch.

 

The link on the interface 17 is not up after the kernel boots but the link on the interface 18 is up if I plug in a network cable.

 

Here is from the boot log:

 

[ 6.068459] fsl_dpaa2_eth dpni.1: Linked as a consumer to dpio.1
[ 6.071495] fsl_dpaa2_eth dpni.1: Linked as a consumer to dpio.0
[ 6.143159] fsl_dpaa2_eth dpni.1: Probed interface eth0
[ 6.171824] fsl_dpaa2_eth dpni.0: Linked as a consumer to dpio.15
[ 6.174860] fsl_dpaa2_eth dpni.0: Linked as a consumer to dpio.14
[ 6.177896] fsl_dpaa2_eth dpni.0: Linked as a consumer to dpio.13
[ 6.180929] fsl_dpaa2_eth dpni.0: Linked as a consumer to dpio.12
[ 6.183962] fsl_dpaa2_eth dpni.0: Linked as a consumer to dpio.11
[ 6.186997] fsl_dpaa2_eth dpni.0: Linked as a consumer to dpio.10
[ 6.190032] fsl_dpaa2_eth dpni.0: Linked as a consumer to dpio.9
[ 6.193067] fsl_dpaa2_eth dpni.0: Linked as a consumer to dpio.8
[ 6.196100] fsl_dpaa2_eth dpni.0: Linked as a consumer to dpio.7
[ 6.199134] fsl_dpaa2_eth dpni.0: Linked as a consumer to dpio.6
[ 6.202169] fsl_dpaa2_eth dpni.0: Linked as a consumer to dpio.5
[ 6.205204] fsl_dpaa2_eth dpni.0: Linked as a consumer to dpio.4
[ 6.208236] fsl_dpaa2_eth dpni.0: Linked as a consumer to dpio.3
[ 6.211271] fsl_dpaa2_eth dpni.0: Linked as a consumer to dpio.2
[ 6.214306] fsl_dpaa2_eth dpni.0: Linked as a consumer to dpio.1
[ 6.217341] fsl_dpaa2_eth dpni.0: Linked as a consumer to dpio.0
[ 6.288963] fsl_dpaa2_eth dpni.0: Probed interface eth1
[ 6.292910] dpaa2_mac dpmac.18: Connected to rgmii-id PHY.
[ 6.292936] fsl_mc_dprc dprc.1: No more resources of type dpmcp left
[ 6.292954] fsl_mc_dprc dprc.1: No more resources of type dpmcp left

 

I see the network interfaces and able to assign an IP address to it but I got ping failure when trying to ping to the address on a PC connected to the same network.

 

root@client:~# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:04:9F:05:DD:B9
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

eth1 Link encap:Ethernet HWaddr 00:04:9F:05:DD:BE
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1%4879704/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:6 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:392 (392.0 B) TX bytes:392 (392.0 B)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

 

root@client:~# ls-listni
dprc.1/dpni.1 (interface: eth0, end point: dpmac.2)
dprc.1/dpni.0 (interface: eth1, end point: dpmac.17)
root@client:~#

 

Here are the software I use:

- Kernel: 4.14-early-access branch. .config file is based on lsdk.config

- Device tree: from lx2160a-early-access-bsp0.5 flexbuild

- File system: my own file system

- DPL:  From onboard flash

 

U-boot environment variables:

bootcmd=setenv ethact DPMAC17@rgmii-id; dhcp 0xa0000000; fsl_mc apply dpl 0x20d00000; bootm 0xa0000000

 

I don't have this issue with other NXP's kernels (remotes/origin/github.qoriq-os/linux-4.9 and remotes/origin/github.qoriq-os/linux-4.14) The reason I choose 4.14-early-access is for the PCIe Gen4 endpoint.

 

I guess with the 4.14-early-access kernel that includes recent changes, I may need to have a new DPL for it. For the time being, I don't know what I should change to the DPL file (I extracted one from the onboard flash) and how I reflash the compiled DPL to the flash (I was not successful when trying to boot with an SD card or a USB stick unfortunately.)

 

Full /var/log/messages file attached for your reference.

 

Your help would be highly appreciated.

 

Best Regards,
Tuan

Attachments

Outcomes