AnsweredAssumed Answered

Ethernet connection problem with T2080RDB-PC

Question asked by Ron Gauthier on Apr 7, 2020
Latest reply on Apr 20, 2020 by Yiping Wang

I am working with a T2080RDB device and am having trouble trying to get Ethernet working.  I have not been able to make this work in either U-Boot or Linux that shipped with the board.

 

Should I be able to ping using the standard U-Boot shipped with the board?

 

What about pinging using the embedded Linux shipped with the board?

 

Should I be able to use any of the 6 Ethernet ports, eth0 thru eth5?

 

Some configuration must be set improperly.  Any help on resolving this would be much appreciated.

 

My VxWorks BSP says it only supports ETH0 and ETH1, so I eventually need to get those working.  Since I don't have an SFP+ to RJ45 adapter at the moment, I am using ETH2 to try to get Ethernet working.

 

Thank you,

Ron

 

 

I am aware that there is a typo in the QorIQ T2080 Reference Design Board Quick Start, Table 2 for eth2 and eth3.  As I understand it, the correct info is:

 

Table 2. Ethernet port mapping

 

Label on front panel

Port in U-Boot

Port in Linux

FMAN address

Comments

ETH0

FM1@GTEC1

fm1-mac9

0xfe4f0000

10GBase-T SFP+ (Cortina 4315)

ETH1

FM1@GTEC2

fm1-mac10

0xfe4f2000

10GBase-T SFP+ (Cortina 4315)

ETH3

FM1@GTEC3

fm1-mac1

0xfe4e0000

10GBase-T (AQ1202)

ETH2

FM1@GTEC4

fm1-mac2

0xfe4e2000

10GBase-T (AQ1202)

ETH4

FM1@DTSEC3

fm1-mac3

0xfe4e4000

1G RGMII (RTL8211E)

ETH5

FM1@DTSEC4

fm1-mac4

0xfe4e6000

1G RGMII (RTL8211E)

 

Also, is it correct that the U-Boot port names should be "FM1@TGECn" instead of  "FM1@GTECn" ?

What about "FM1@DTSECn" ?  I am correct in assuming that those are right?

 

In U-Boot, I have been trying to use ETH2, which should be FM1@TGEC4.  (I have tried others as well with similar results.)  With a cable plugged in, the ETH2 Tx/Rx lights continuously flash alternately.  I am trying to ping the network router at 192.168.25.1.  This ping works fine from other devices on the same network.  I have tested the Ethernet cable, which tests fine, and tried other cables as well.

 

First ping attempt:

 

=> ping 192.168.25.1

Using FM1@TGEC4 device

 

ARP Retry count exceeded; starting again

ping failed; host 192.168.25.1 is not alive

=>

 

Second ping attempt (interesting that the output is different than the first ping):

 

=> ping 192.168.25.1

Using FM1@TGEC4 device

FM1@TGEC4: Tx error, txbd->status = 0x8800

FM1@TGEC4: Tx buffer not ready, txbd->status = 0x8800

FM1@TGEC4: Tx buffer not ready, txbd->status = 0x8800

FM1@TGEC4: Tx buffer not ready, txbd->status = 0x8800

 

ARP Retry count exceeded; starting again

ping failed; host 192.168.25.1 is not alive

=>

 

Ping with no cable attached to eth2:

 

=> ping 192.168.25.1

FM1@TGEC4 Waiting for PHY auto negotiation to complete................................ TIMEOUT !

FM1@TGEC4: No link.

 

 

Here is the U-Boot log:

 

U-Boot 2016.012.0+ga9b437f (May 15 2016 - 01:38:26 +0800)

 

CPU0:  T2080E, Version: 1.1, (0x85380011)

Core:  e6500, Version: 2.0, (0x80400120)

Clock Configuration:

       CPU0:1799.820 MHz, CPU1:1799.820 MHz, CPU2:1799.820 MHz, CPU3:1799.820 MHz,

       CCB:599.940 MHz,

       DDR:933.310 MHz (1866.620 MT/s data rate) (Asynchronous), IFC:149.985 MHz

       FMAN1: 699.930 MHz

       QMAN:  299.970 MHz

       PME:   599.940 MHz

L1:    D-cache 32 KiB enabled

       I-cache 32 KiB enabled

Reset Configuration Word (RCW):

       00000000: 1207001b 15000000 00000000 00000000

       00000010: 66150002 00000000 ec027000 c1000000

       00000020: 00800000 00000000 00000000 000307fc

       00000030: 00000000 00000000 00000000 00000004

I2C:   ready

Board: T2080RDB, Board rev: 0x01 CPLD ver: 0x06, boot from NOR vBank0

SERDES Reference Clocks:

SD1_CLK1=156.25MHZ, SD1_CLK2=100.00MHZ

SD2_CLK1=100.00MHZ, SD2_CLK2=100.00MHZ

SPI:   ready

DRAM:  Initializing....using SPD

Detected UDIMM D3XP56082XL10AA

2 GiB left unmapped

4 GiB (DDR3, 64-bit, CL=13, ECC on)

       DDR Chip-Select Interleaving Mode: CS0+CS1

VID: Core voltage after adjustment is at 1023 mV

Flash: 128 MiB

L2:    2 MiB enabled

Corenet Platform Cache: 512 KiB enabled

Using SERDES1 Protocol: 102 (0x66)

Using SERDES2 Protocol: 21 (0x15)

SEC0: RNG instantiated

NAND:  512 MiB

MMC:   FSL_SDHC: 0

EEPROM: Invalid ID (ff ff ff ff)

PCIe1: Endpoint, undetermined, regs @ 0xfe240000

PCIe1: Bus 00 - 00

PCIe2: Root Complex, x2 gen2, regs @ 0xfe250000

  02:00.0     - 1957:0808 - Processor

PCIe2: Bus 01 - 02

PCIe3: disabled

PCIe4: Root Complex, no link, regs @ 0xfe270000

PCIe4: Bus 03 - 03

In:    serial

Out:   serial

Err:   serial

Net:   Fman1: Uploading microcode version 106.4.18

FM1@DTSEC3, FM1@DTSEC4, FM1@TGEC1, FM1@TGEC2, FM1@TGEC3, FM1@TGEC4 [PRIME]

Hit any key to stop autoboot:  0

=>

 

And the environment variables:

 

=> printenv

baudrate=115200

bdev=sda3

bootargs=root=/dev/ram rw console=ttyS0,115200

bootcmd=setenv bootargs root=/dev/ram rw console=$consoledev,$baudrate $othbootargs;bootm e8020000 e9300000 e8800000

bootdelay=10

bootfile=uImage

consoledev=ttyS0

eth0addr=00:04:9F:05:DB:13

eth1addr=00:04:9F:05:DB:14

eth2addr=00:04:9F:05:DB:15

eth3addr=00:04:9F:05:DB:16

eth4addr=00:00:00:00:00:04

eth5addr=00:00:00:00:00:05

eth6addr=00:00:00:00:00:06

eth7addr=00:00:00:00:00:07

eth8addr=00:04:9F:05:DB:17

eth9addr=00:04:9F:05:DB:18

ethact=FM1@TGEC4

ethaddr=00:04:9F:05:DB:15

ethprime=FM1@TGEC4

fdtaddr=2000000

fdtfile=t2080rdb.dtb

fileaddr=1000000

filesize=200000

fman_ucode=eff00000

gatewayip=192.168.25.1

hvboot=setenv bootargs console=ttyS0,115200 config-addr=0xfe8900000;bootm 0xfe8700000 - 0xfe8800000

hwconfig=fsl_ddr:bank_intlv=auto;usb1:dr_mode=host,phy_type=utmi

ipaddr=192.168.25.130

loadaddr=1000000

netdev=eth0

netmask=255.255.255.0

nfsboot=setenv bootargs root=/dev/nfs rw nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname:$netdev:off console=$consoledev,$baudrate $othbootargs;tftp $loadaddr $bootfile;tftp $fdtaddr $fdtfile;bootm $loadaddr - $fdtaddr

ramboot=setenv bootargs root=/dev/ram rw console=$consoledev,$baudrate $othbootargs;tftp $ramdiskaddr $ramdiskfile;tftp $loadaddr $bootfile;tftp $fdtaddr $fdtfile;bootm $loadaddr $ramdiskaddr $fdtaddr

ramdiskaddr=5000000

ramdiskfile=ramdisk.uboot

rootpath=/opt/nfsroot

sataboot=setenv bootargs root=/dev/sda1 rootdelay=5 rw console=$consoledev,$baudrate $othbootargs;bootm e8020000 - e8800000

serverip=192.168.25.1

stderr=serial

stdin=serial

stdout=serial

tftpflash=tftpboot $loadaddr $uboot && protect off $ubootaddr +$filesize && erase $ubootaddr +$filesize && cp.b $loadaddr $ubootaddr $filesize && protect on $ubootaddr +$filesize && cmp.b $loadaddr $ubootaddr $filesize

uboot="u-boot.bin"

ubootaddr=0xeff40000

 

Environment size: 1975/8188 bytes

=>

Outcomes