Tx error, txbd->status = 0x8800

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Tx error, txbd->status = 0x8800

4,961 Views
qiaofa_luo
Contributor II

full log as follows,  and can't recover,  power off then power on may be ok, we don't known what happend?

how to fix the issue?   uboot version: U-Boot 2016.09-g9827df2-dirty (Aug 28 2019 - 09:40:58 +0800)

U-Boot 2016.09-g9827df2-dirty (Aug 28 2019 - 09:40:58 +0800)

CPU0: B4860E, Version: 2.2, (0x86880022)
Core: e6500, Version: 2.0, (0x80400120)
Clock Configuration:
CPU0:1600 MHz, CPU1:1600 MHz, CPU2:1600 MHz, CPU3:1600 MHz,
DSP CPU0:1200 MHz, DSP CPU1:1200 MHz, DSP CPU2:1200 MHz, DSP CPU3:1200 MHz,
DSP CPU4:1200 MHz, DSP CPU5:1200 MHz,
CCB:666.667 MHz,
DDR:933.333 MHz (1866.667 MT/s data rate) (Asynchronous), IFC:333.333 MHz
CPRI:600 MHz
MAPLE:600 MHz, MAPLE-ULB:800 MHz, MAPLE-eTVPE:1000 MHz
FMAN1: 666.667 MHz
QMAN: 333.333 MHz
L1: D-cache 32 KiB enabled
I-cache 32 KiB enabled
Reset Configuration Word (RCW):
00000000: 140e0018 0f001218 00000000 00000000
00000010: 52170000 a000a000 dc025000 a9000000
00000020: 01000000 00000000 00000000 0001a1f8
00000030: 00000000 14000020 00000000 00006011
I2C: ready
SPI: ready
DRAM: SPL Initializing....using fixed parameters
Configuring DDR for 1866.667 MT/s data rate
setup lasw for ddr...
total dram size:0x100000000, 4 PiB left unmapped
2 GiB (DDR3, 64-bit, CL=13, ECC on)
Flash: 128 MiB
L2: 2 MiB enabled
Corenet Platform Cache: 512 KiB enabled
Using SERDES1 Protocol: 41 (0x29)
Using SERDES2 Protocol: 23 (0x17)
SRIO1: enabled
SRIO2: disabled
SEC0: RNG instantiated
NAND: 512 MiB
EEPROM: Read failed.
PCIe1: disabled
In: serial
Out: serial
Err: serial
Net: [phy_atheros_init]: Enter
Using SERDES1 Protocol: 0x29:
Using SERDES2 Protocol: 0x17:
Initializing Fman
Fman1: Uploading microcode version 108.4.5
[ar8035_config]: name: AR8031/AR8033
[ar8035_config]: name: AR8031/AR8033
[ar8035_config]: name: AR8031/AR8033
FM1@DTSEC1 [PRIME], FM1@DTSEC2, FM1@DTSEC3
confirming...
confirming...
confirming...
confirming...
confirming...
Hit any key to stop autoboot: 0
=> ping 192.168.0.136
Using FM1@DTSEC1 device

ARP Retry count exceeded; starting again
ping failed; host 192.168.0.136 is not alive
=> ping 192.168.0.136
Using FM1@DTSEC1 device
FM1@DTSEC1: Tx error, txbd->status = 0x8800
FM1@DTSEC1: Tx buffer not ready, txbd->status = 0x8800
FM1@DTSEC1: Tx buffer not ready, txbd->status = 0x8800
FM1@DTSEC1: Tx buffer not ready, txbd->status = 0x8800

ARP Retry count exceeded; starting again
ping failed; host 192.168.0.136 is not alive
=>

Labels (1)
0 Kudos
3 Replies

4,366 Views
artsiomstaliaro
Contributor IV

This happens when LS1043A missing a 125MHz clock from PHY.

0 Kudos

4,703 Views
bpe
NXP Employee
NXP Employee

Your FMAN is not updating transmit buffers status. Typically this happens when the interface is not properly configured, disabled or is missing
input clocks. Suggestions:

1. Verify your RCW to make sure the interface you are trying to bring
   up is enabled at reset time and is properly configured for SerDes
   options and cllocks.
   
2. Check DEVDISR.

3. Make sure the interface has valid input clocks.


Have a great day,
Platon

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

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

0 Kudos

4,703 Views
qiaofa_luo
Contributor II

in addition,  after boot up linux os,  the network don't work too

0 Kudos