AnsweredAssumed Answered

U-boot ping issue: Tx buffer not ready txbd->status =0x8800

Question asked by rjwangpeng@norco.com.cn on Dec 31, 2018
Latest reply on Apr 4, 2019 by Santhana Krishnan T L

The issue is that ping is not alive in U-boot . The platform is ls1046ardb.   The below is the uboot log:

U-Boot SPL 2018.03-dirty (Dec 31 2018 - 15:51:21 +0800)
Initializing DDR....using SPD
WARNING: Calling __hwconfig without a buffer and before environment is ready
WARNING: Calling __hwconfig without a buffer and before environment is ready
WARNING: Calling __hwconfig without a buffer and before environment is ready
WARNING: Calling __hwconfig without a buffer and before environment is ready
Trying to boot from MMC1


U-Boot 2018.03-dirty (Dec 31 2018 - 15:51:21 +0800)

SoC: LS1046AE Rev1.0 (0x87070010)
Clock Configuration:
CPU0(A72):1800 MHz CPU1(A72):1800 MHz CPU2(A72):1800 MHz
CPU3(A72):1800 MHz
Bus: 600 MHz DDR: 2100 MT/s FMAN: 700 MHz
Reset Configuration Word (RCW):
00000000: 0c150012 0e000000 00000000 00000000
00000010: 13335559 40005012 60040000 c1000000
00000020: 00000000 00000000 00000000 00238800
00000030: 20124000 00003101 00000096 00000001
Model: LS1046A RDB Board
Board: LS1046ARDB, boot from Invalid setting of SW5
CPLD: V0.0
PCBA: V0.0
SERDES Reference Clocks:
SD1_CLK1 = 100.00MHZ, SD1_CLK2 = 100.00MHZ
I2C: ready
DRAM: Detected UDIMM 18ASF1G72AZ-2G3B1
7.9 GiB (DDR4, 64-bit, CL=15, ECC on)
SEC0: RNG instantiated
FSL_SDHC: 0
PPA Firmware: Version LSDK-18.06
SEC Firmware: 'loadables' present in config
loadables: 'trustedOS@1'
Using SERDES1 Protocol: 4915 (0x1333)
Using SERDES2 Protocol: 21849 (0x5559)
NAND: 0 MiB
MMC: Loading Environment from MMC... *** Warning - bad CRC, using default environment

...........

...........

 

Command line return "FM1@DTSEC3: Tx buffer not ready, txbd->status = 0x8800" when I ping some ip.

I use command "setenv ethaddr xxxxxxxxxx" to set MAC address.

Command "mmc" cannot read MAC address cause I haven't write MAC in eeprom.

Did anyone who meet this problem before? Hope you can help me 

Thanks. 

 

 

 

-----------------------------

mdio list :

FSL_MDIO0:
1 - AR8031/AR8033 <--> FM1@DTSEC3
2 - AR8031/AR8033 <--> FM1@DTSEC4
3 - AR8031/AR8033 <--> FM1@DTSEC5
4 - AR8031/AR8033 <--> FM1@DTSEC6
5 - AR8031/AR8033 <--> FM1@DTSEC10
FM_TGEC_MDIO:

 

 

 mii dump 0 1 

1. (ffff) -- PHY status register --
(8000:8000) 1.15 = 1 100BASE-T4 able
(4000:4000) 1.14 = 1 100BASE-X full duplex able
(2000:2000) 1.13 = 1 100BASE-X half duplex able
(1000:1000) 1.12 = 1 10 Mbps full duplex able
(0800:0800) 1.11 = 1 10 Mbps half duplex able
(0400:0400) 1.10 = 1 100BASE-T2 full duplex able
(0200:0200) 1. 9 = 1 100BASE-T2 half duplex able
(0100:0100) 1. 8 = 1 extended status
(0080:0080) 1. 7 = 1 (reserved)
(0040:0040) 1. 6 = 1 MF preamble suppression
(0020:0020) 1. 5 = 1 A/N complete
(0010:0010) 1. 4 = 1 remote fault
(0008:0008) 1. 3 = 1 A/N able
(0004:0004) 1. 2 = 1 link status    //link is up
(0002:0002) 1. 1 = 1 jabber detect
(0001:0001) 1. 0 = 1 extended capabilities

Outcomes