T4240RDB not reachable via 10G ports.

clemenseisserer · ‎06-15-2015

Hi, we experience troubles connecting our T4240RDB via the 10GigE ports.

What I did was basically bringing fm2-mac1 online ( iplink set fm2-mac1 up) and assigning an IP (ifconfig fm2-mac1 up 192.168.1.2), yet I can't ping the other host on 192.168.1.1. Ifconfig shows bytes are sent, but rx bytes always stays 0. Did I miss something? By the way, are jumbo-frames (9000 bytes) not supported by the internal 10G NICs? Syslog doesn't show any suspects.

Any ideas what I missed?

Thank you in advance, Clemens

fm2-mac1 Link encap:Ethernet HWaddr 00:10:f3:41:35:78

inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0

UP BROADCAST MULTICAST MTU:1500 Metric:1

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

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

collisions:0 txqueuelen:1000

RX bytes:0 (0.0 B) TX bytes:3243 (3.1 KiB)

Memory:fe5e0000-fe5e0fff

yipingwang · ‎06-16-2015

Hello Clemens,

For your another question, TGEC XFI port supports jumbo frame, please configure Kernel as the following.

CONFIG_FMAN_DISABLE_OH_TO_REUSE_RESOURCES=y
CONFIG_FSL_DPAA_ETH_JUMBO_FRAME=y

In the u-boot environment, add "fsl_fman_phy_max_frm=9600" directly to the "bootargs" variable.

Have a great day,
Yiping

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

yipingwang · ‎06-16-2015

Hello Clemens Eisserer,

It seems that fm2-mac1 is not a 10G port, please refer to the following Port Map.

Which RCW do you use? Would you please provide your u-boot and Kernel boot up log?

Have a great day,
Yiping

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

clemenseisserer · ‎06-16-2015

I noticed later that fm2-mac1 was not the right interface for the physical "ETH8" labeld SFP+ slot, but instead according to "T4240 RDB reference design board quick start" fm2-mac9 is.

However, initializing fm2-mac9 fails:

root@t4240rdb:~# iplink set fm2-mac9 up;

iplink: SIOCGIFFLAGS: No such device

In syslog I can see that some initialization steps also go wrong:

[	2.284595] cpu1/1: > WARNING (FM) [CPU01, drivers/net/ethernet/freescale/fman/Peripherals/FM/fm.c:3514 FM_Init]:
[	2.293480] cpu1/1: Hack: No FM reset!
[	2.296111] cpu1/1:
[	2.301230] Freescale FM module (Jan 28 2015:16:16:15), FMD API version 21.1.0
[	2.316329] Freescale FM Ports module (Jan 28 2015:16:16:15)
[	2.320689] dpaa_debugfs: FSL DPAA Ethernet debugfs entries ()
[	2.325237] dpaa_generic_debugfs: FSL DPAA Ethernet debugfs entries ()
[	2.330477] fsl_mac: fsl_mac: FSL FMan MAC API based driver ()
[	2.335551] fsl_mac ffe4e0000.ethernet: FMan MEMAC
[	2.339058] fsl_mac ffe4e0000.ethernet: FMan MAC address: 00:10:f3:41:35:74
[	2.345019] fsl_mac ffe4e2000.ethernet: FMan MEMAC
[	2.348524] fsl_mac ffe4e2000.ethernet: FMan MAC address: 00:10:f3:41:35:75
[	2.354486] fsl_mac ffe4e4000.ethernet: FMan MEMAC
[	2.357986] fsl_mac ffe4e4000.ethernet: FMan MAC address: 00:10:f3:41:35:76
[	2.363951] fsl_mac ffe4e6000.ethernet: FMan MEMAC
[	2.367451] fsl_mac ffe4e6000.ethernet: FMan MAC address: 00:10:f3:41:35:77
[	2.373369] fsl_mac ffe4f0000.ethernet: FMan MEMAC
[	2.376875] fsl_mac ffe4f0000.ethernet: FMan MAC address: 00:10:f3:41:35:7e
[	2.382791] fsl_mac ffe4f2000.ethernet: FMan MEMAC
[	2.386289] fsl_mac ffe4f2000.ethernet: FMan MAC address: 00:10:f3:41:35:7f
[	2.392356] fsl_mac ffe5e0000.ethernet: FMan MEMAC
[	2.395854] fsl_mac ffe5e0000.ethernet: FMan MAC address: 00:10:f3:41:35:78
[	2.401880] fsl_mac ffe5e2000.ethernet: FMan MEMAC
[	2.405363] fsl_mac ffe5e2000.ethernet: FMan MAC address: 00:10:f3:41:35:79
[	2.411378] fsl_mac ffe5e4000.ethernet: FMan MEMAC
[	2.414875] fsl_mac ffe5e4000.ethernet: FMan MAC address: 00:10:f3:41:35:7a
[	2.420893] fsl_mac ffe5e6000.ethernet: FMan MEMAC
[	2.424389] fsl_mac ffe5e6000.ethernet: FMan MAC address: 00:10:f3:41:35:7b
[	2.430157] fsl_mac ffe5f0000.ethernet: of_get_mac_address(/soc@ffe000000/fman@500000/ethernet@f0000) failed
[	2.438699] fsl_mac: probe of ffe5f0000.ethernet failed with error -22
[	2.444022] fsl_mac ffe5f2000.ethernet: of_get_mac_address(/soc@ffe000000/fman@500000/ethernet@f2000) failed
[	2.452561] fsl_mac: probe of ffe5f2000.ethernet failed with error -22

Our T2080RDB boards are working fine, so the issue seems to be limited to the T4240RDBs.

Any help would be very appriciated.

Thank you in advance & best regards, Clemens

yipingwang · ‎06-16-2015

Hello Clemens Eisserer,

According to your log, you didn't set MAC address for enet14(FM2@TGEC1, fm2-mac9 ) and enet15(FM2@TGEC2), please refer to the following to set MAC addresses for all the Ethernet interfaces under u-boot environment.

=> pri

eth10addr=00:E0:0C:00:30:0a

eth11addr=00:E0:0C:00:30:0b

eth12addr=00:E0:0C:00:30:0c

eth13addr=00:E0:0C:00:30:0d

eth14addr=00:E0:0C:00:30:0e

eth15addr=00:E0:0C:00:30:0f

eth16addr=00:15:17:80:ad:53

eth1addr=00:E0:0C:00:30:01

eth2addr=00:E0:0C:00:30:02

eth3addr=00:E0:0C:00:30:03

eth4addr=00:E0:0C:00:30:04

eth5addr=00:E0:0C:00:30:05

eth6addr=00:E0:0C:00:30:06

eth7addr=00:E0:0C:00:30:07

eth8addr=00:E0:0C:00:30:08

eth9addr=00:E0:0C:00:30:09

ethaddr=00:E0:0C:00:30:00

If your problem remains, please share your u-boot and kernel boot log.

Have a great day,
Yiping

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

naveennvn · ‎06-15-2015

Hi clemens,

Actually eth4 : fm2-mac1 is not supported 10G.

In T4240 only four ports are supported 10G interface.

Try : eth8 : fm2-mac9

eth9 : fm2-mac10

eth10 : fm1-mac10

eth11 : fm-mac9

and use the transceiver according to that 10G specification.

T4240RDB not reachable via 10G ports.

T4240RDB not reachable via 10G ports.

QorIQ T4 Devices