T1040RDB : Repeated ping fails with Tx error in uboot

sareenakp · ‎07-02-2014

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

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

ping failed; host 10.116.65.1 is not alive

=>

yipingwang · ‎07-08-2014

I have verified SDK 1.6 u-boot image, and didn't find this problem. I suggest you update your image to SDK 1.6 which also supports T1040RDB and can be downloaded from SDKLINUX: Linux® SDK for QorIQ Processors.

Have a great day,
Yiping Wang

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

sareenakp · ‎07-08-2014

Thanks for the reply.

Even we are using the SDK V1.6

This is the ISO downloaded and used- QorIQ-SDK-V1.6-SOURCE-20140619-yocto.iso.

Is there any specific configuration/specific that we have missed or may be missing?

Thanks,

Sareena.

yipingwang · ‎07-08-2014

Hello Sareena,

First please download QorIQ-SDK-V1.6-PPCE5500-IMAGE*.iso, this ISO contains pre-built images, you could use directly.

If you want to build or customize images by yourself, please also download QorIQ-SDK-V1.6-SOURCE*.iso and QorIQ-SDK-V1.6-PPCE5500-CACHE*.iso, the SOURCE ISO contains source code and documents, and the Cache ISO contains cache binary to accelerate the build.

Have a great day,
Yiping Wang

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

sareenakp · ‎07-08-2014

Hi Yiping,

Thank you.

I downloaded the image.iso . And I updated the FMAN ucode as well as the uboot.bin in the alternate bank, using the below steps.

But the issue is still seen.

=>tftp 1000000 u-boot.bin

=>erase edf80000 edffffff

=>cp.b 1000000 edf80000 80000

=>tftp 1000000 <ucode_file_name>.bin

=>erase ebf00000 ebf1ffff

=>cp.b 1000000 ebf00000 $filesize

Should I be downloading the entire NOR flash now? If so how?

Thanks and Regards,

Sareena.

yipingwang · ‎07-08-2014

Hello Sareena,

I checked P1040RDB NOR flash memory map, it seems that u-boot(alternate bank) is from 0xEBF40000 to 0xEBFFFFFF.

The entire NOR flash image including all the images in the memory map and reflect the whole 128M flash, if you wan to to you it, you could flash it at the beginning address of NOR FLASH.

I past the NOR flash memory map for you.

Have a great day,
Yiping Wang

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

sareenakp · ‎07-08-2014

Hi Yiping,

Sorry! , I mentioned the wrong address in the above reply for u-boot in the alternate bank

=>erase edf80000 edffffff

=>cp.b 1000000 edf80000 80000

I have been copying u-boot in the range 0xEBF40000 to 0xEBFFFFFF.

And still the issue occurs.

Any reasons/points on what is different in my setup and yours?

Below is the log of the uboot in the alternate bank

=> cpld reset altbank

U-Boot 2014.01QorIQ-SDK-V1.6+gfe1d4f5 (Jun 12 2014 - 18:26:00)

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: 4

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 107.4.1

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

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

Hit any key to stop autoboot: 0

=>

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

=> ping 10.116.65.1

Using FM1@DTSEC4 device

FM1@DTSEC4: Tx buffer not ready

ping failed; host 10.116.65.1 is not alive

=>

Thanks and Regards,

Sareena.

yipingwang · ‎07-09-2014

Hello Sareena,

I didn't find the difference with my environment, please check whether the problem remains with FM1@DTSEC5 and please check whether it would be better to use the Flash image(including u-boot environment).

Have a great day,
Yiping Wang

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

sareenakp · ‎07-09-2014

The flash image QorIQ_SDK_T2080V1.1_T1040V0.3_T1040RDB_20140422_NOR_Flash.bin is 134.2 MB, as compared to the 128 MB flash.

Also this will overwrite both the banks. Is it possible to update both the banks at the same time?

Thanks

Sareena.

yipingwang · ‎07-09-2014

Hi Sareena,

Please use SDK 1.6 flash image.

-r--r--r-- 1 root root 128M Jun 10 17:24 flash-image/QorIQ_SDK_V1.6_T1040RDB_20140619_NOR_Flash.bin

Have a great day,
Yiping Wang

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

sareenakp · ‎07-09-2014

Hi Yiping,

Please confirm if the below steps for updating flash is correct.

I will be booting u-boot in bank 0 and will use the following commands to update the entire 128MB Flash from the SD card.

ext2load mmc 0:1 1000000 flash.bin

erase e8000000 efffffff

cp.b 1000000 e8000000 $filesize

Also FM1@DTSEC5 has the same issue with ping

Thanks and Regards,

Sareena.

sareenakp · ‎07-09-2014

Hi Yiping,

I extracted the QE code + FMAN code + the u boot env from the flash image and flashed it in the alternate bank.

No luck! The issue still exists.

What else could be the reason for this behaviour?

Regards,

Sareena.

yipingwang · ‎07-10-2014

Hello Sareena,

I also confirmed with Linux SDK testing team, they didn't find this problem either.

Are you sure that there is no this problem in Linux Kernel on your target?

I will do more investigation, for any update will let you know.

Have a great day,
Yiping Wang

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

sareenakp · ‎07-10-2014

Hi Yiping,

Yes, on linux kernel no problem seen with network.

We have 4 T1040RDB boxes here and the issue is seen in all of them.

Thanks,

Sareena.

sareenakp · ‎07-10-2014

Hi Yiping,

Below is the version information of the t1040rdb box we are having here.

SCH-28215 REV B

700-28215 REV B

CPLD V1.6

All the four boxes, we have here are from the same shipment and issue in ping/tftp is seen in all of them

Thanks and Regards,

Sareena.

yipingwang · ‎07-11-2014

Hello Sareena,

The attachment is my log, I don't have good idea now, probably you need to contact your local FAE to take a look at your network environment.

Have you tried to connect the target board with your PC directly? I am not sure whether there is IP allocation problem in your network envrionment.

Have a great day,
Yiping Wang

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

sareenakp · ‎07-15-2014

Hello Yiping,

We connected a Linux host system back-to-back with the T1040 board and after configuration of the IP addresses on both sides, we were not able to ping continously. We ran wireshark on the host system to check and have enclosed the two captured screenshots - ping from host to board and vice-versa.

Also in the log you attached , I see an entry for e1000.

e1000: 00:15:17:8e:7b:64

FM1@DTSEC1, FM1@DTSEC2, FM1@DTSEC3 [PRIME], FM1@DTSEC4, FM1@DTSEC5, e1000#0

Warning: e1000#0 MAC addresses don't match:

Address in SROM is 00:15:17:8e:7b:64

Address in environment is 00:e0:0c:00:0c:05

I dont see a e1000 driver getting loaded for the box here. Only the fman driver gets loaded.

Why is this difference?

Regards,
Sareena.

yipingwang · ‎07-15-2014

Hello Sareena,

e1000 is PCIe Ethernet interface, and it seems that there is no the E1000 PCI ethernet card on your target.

Please don't ping the target board from the PC, because u-boot cannot detect and reply ARP packet.

Would you please send your u-boot environment (with pri command) to me?

Thanks,

Yiping

sareenakp · ‎07-15-2014

Hello Yiping,

Below is the u-boot environment

=> pri

baudrate=115200

bdev=sda3

bootargs=root=/dev/mmcblk0p1 rw rootdelay=5 console=ttyS0,115200

bootcmd=run mmcboot

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

filesize=4200ad

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.20

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.10

loadaddr=10000000

mmcboot=setenv bootargs root=/dev/mmcblk0p1 rw rootdelay=5

console=$consoledev,$baudrate;mmcinfo;ext2load mmc 0:1 $loadaddr

$bootfile;ext2load mmc 0:1 $fdtaddr $fdtfile; bootm $loadaddr - $fdtaddr

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

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: 1939/8188 bytes

On Tue, Jul 15, 2014 at 4:16 PM, Yiping Wang <admin@community.freescale.com>

yipingwang · ‎07-15-2014

Hello Sareena,

According to the above two screenshots, it seems that the PC is sending ARP broadcasting packets continuously, please check whether it would be better if stop sending broadcasting packets from PC side.

Have a great day,
Yiping

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

sareenakp · ‎07-17-2014

Hello Yiping,

We have raised a service request of the same . (SR#1-2039245311).

They say , it is a mistake in the board.

Thanks

Sareena.