AnsweredAssumed Answered

T1040RDB : Repeated ping fails with Tx error in uboot

Question asked by Sareena Karapoola on Jul 2, 2014
Latest reply on Jul 17, 2014 by Sareena Karapoola

I am working on the freescale T1040RDB box. In the uboot, I have configured the u-boot variables ipaddr, ethaddr, netmask, gatewayip, ethact.

Ping works and indicates that the 'host is alive' message.However after repeated pings, the ping responds with the error 'Tx error'. Thiis error then exists until a restart.

...

 

=> ping 10.116.65.1

Using FM1@DTSEC4 device

host 10.116.65.1 is alive

=> ping 10.116.65.1

Using FM1@DTSEC4 device

host 10.116.65.1 is alive

=> ping 10.116.65.1

Using FM1@DTSEC4 device

host 10.116.65.1 is alive

=> ping 10.116.65.1

Using FM1@DTSEC4 device

FM1@DTSEC4: Tx error

FM1@DTSEC4: Tx buffer not ready

ping failed; host 10.116.65.1 is not alive

=>

 

What could be  the reason for this? I have connected to eth0 port on the box (fm1-gb3 port in Linux and FM1@DTSEC4 port in uboot)

In Linux, this works fine and no issue is seen in the repeated ping,.

 

 

Below is the uboot console output. uBoot - Log  -->

 

U-Boot 2014.01QorIQ-SDK-T2080V1.1-T1040V0.3 (Apr 22 2014 - 04:04:49)

CPU0:  T1040E, Version: 1.0, (0x85280010)

Core:  e5500, Version: 2.0, (0x80241020)

Clock Configuration:

       CPU0:1400 MHz, CPU1:1400 MHz, CPU2:1400 MHz, CPU3:1400 MHz,

       CCB:600  MHz,

       DDR:800  MHz (1600 MT/s data rate) (Asynchronous), IFC:150  MHz

       QE:300  MHz

       FMAN1: 600 MHz

       QMAN:  300 MHz

       PME:   300 MHz

L1:    D-cache 32 KiB enabled

       I-cache 32 KiB enabled

Reset Configuration Word (RCW):

       00000000: 0c18000e 0e000000 00000000 00000000

       00000010: 66000002 80000002 ec027000 01000000

       00000020: 00000000 00000000 00000000 00032810

       00000030: 00000000 0342500f 00000000 00000000

Board: T1040RDB

Board rev: 0x01 CPLD ver: 0x06, vBank: 0

I2C:   ready

SPI:   ready

DRAM:  Initializing....using SPD

Detected UDIMM 18KSF51272AZ-1G6K1

2 GiB left unmapped

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

       DDR Chip-Select Interleaving Mode: CS0+CS1

Flash: 256 MiB

L2:    256 KiB enabled

Corenet Platform Cache: 256 KiB enabled

Using SERDES1 Protocol: 102 (0x66)

NAND:  1024 MiB

MMC:  FSL_SDHC: 0

Not a microcode

PCIe1: Root Complex, no link, regs @ 0xfe240000

PCIe1: Bus 00 - 00

PCIe2: Root Complex, no link, regs @ 0xfe250000

PCIe2: Bus 01 - 01

PCIe3: Root Complex, no link, regs @ 0xfe260000

PCIe3: Bus 02 - 02

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

PCIe4: Bus 03 - 03

In:    serial

Out:   serial

Err:   serial

Net:   Initializing Fman

Fman1: Uploading microcode version 106.4.14

FSL_MDIO0:0 is connected to FM1@DTSEC1.  Reconnecting to FM1@DTSEC2

FSL_MDIO0:0 is connected to FM1@DTSEC2.  Reconnecting to FM1@DTSEC3

FM1@DTSEC1, FM1@DTSEC2, FM1@DTSEC3, FM1@DTSEC4 [PRIME], FM1@DTSEC5

Hit any key to stop autoboot:  0

=>

=>

=>

=> print

baudrate=115200

bdev=sda3

bootcmd=run flashboot

bootdelay=10

bootfile=uImage

c=ffe

consoledev=ttyS0

eth1addr=00:04:9F:03:3B:47

eth2addr=00:04:9F:03:3B:48

eth3addr=00:04:9F:03:3B:49

eth4addr=00:04:9F:03:3B:4A

ethact=FM1@DTSEC4

ethaddr=00:04:9F:03:3B:46

ethprime=FM1@DTSEC4

fdtaddr=17200000

fdtfile=uImage-t1040rdb.dtb

flashboot=setenv bootargs root=/dev/ram rw console=ttyS0,115200 ramdisk_size=960000; cp.b e9300000 2000000 1b00000;bootm e8020000 2000000 e8800000

fman_ucode=eff00000

gatewayip=10.116.65.1

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

ipaddr=10.116.65.169

loadaddr=10000000

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

othbootargs=ramdisk_size=960000

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=2000000

ramdiskfile="t1040rdb/t1040rdb.dtb"

rootpath=/opt/nfsroot

serverip=172.20.2.180

tftpblocksize=1024

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

video-mode=fslfb:1024x768-32@60,monitor=dvi

 

Environment size: 1657/8188 bytes

=> print ipaddr

ipaddr=10.116.65.169

=> print ethact

ethact=FM1@DTSEC4

=> mdio list

FSL_MDIO0:

0 - RealTek RTL8211E <--> FM1@DTSEC3

1 - RealTek RTL8211E <--> FM1@DTSEC4

2 - RealTek RTL8211E <--> FM1@DTSEC5

=>

=> ping 10.116.65.1

Using FM1@DTSEC4 device

host 10.116.65.1 is alive

=> ping 10.116.65.1

Using FM1@DTSEC4 device

host 10.116.65.1 is alive

=> ping 10.116.65.1

Using FM1@DTSEC4 device

host 10.116.65.1 is alive

=> ping 10.116.65.1

Using FM1@DTSEC4 device

host 10.116.65.1 is alive

=> ping 10.116.65.1

Using FM1@DTSEC4 device

host 10.116.65.1 is alive

=> ping 10.116.65.1

Using FM1@DTSEC4 device

host 10.116.65.1 is alive

=> ping 10.116.65.1

Using FM1@DTSEC4 device

host 10.116.65.1 is alive

=> ping 10.116.65.1

Using FM1@DTSEC4 device

host 10.116.65.1 is alive

=> ping 10.116.65.1

Using FM1@DTSEC4 device

host 10.116.65.1 is alive

=> ping 10.116.65.1

Using FM1@DTSEC4 device

host 10.116.65.1 is alive

=> ping 10.116.65.1

Using FM1@DTSEC4 device

FM1@DTSEC4: Tx error

FM1@DTSEC4: Tx buffer not ready

ping failed; host 10.116.65.1 is not alive

=>

Using FM1@DTSEC4 device

FM1@DTSEC4: Tx buffer not ready

FM1@DTSEC4: Tx buffer not ready

ping failed; host 10.116.65.1 is not alive

=> ping 10.116.65.1

Using FM1@DTSEC4 device

FM1@DTSEC4: Tx buffer not ready

FM1@DTSEC4: Tx buffer not ready

ping failed; host 10.116.65.1 is not alive

=>

Outcomes