LS1046A UBOOT SGMII TX ERROR

tapyang · ‎04-01-2018

Dear, Experts:

I met a problem when I was debugging my custom LS1046A board. The U-BOOT has started up, but the ethernet has problem:

I read the phy registers by mdio, found that the PHY(AR8031) status is good!

I tried to update the FMAN UCODE to "fsl_fman_ucode_ls1046_r1.0_108_4_9.bin" and it is the same!

I used the SGMII.5, the serdes1 was configed as "0x1133" and the serdes1 pll1 was 100MHz.

The env is as followed:

"
FM1@DTSEC3, FM1@DTSEC4, FM1@DTSEC5 [PRIME], FM1@DTSEC6, FM1@TGEC1
Error: FM1@TGEC1 address not set.
, FM1@TGEC2
Error: FM1@TGEC2 address not set.
Initial value for argc=3
Final value for argc=3

initcall: 0000000040117944 (relocated to 00000000ffd16944)
fdtdec_get_config_int: bootdelay
### main_loop entered: bootdelay=10

fdtdec_get_config_int: kernel-offset
fdtdec_get_config_int: rootdisk-offset
fdtdec_get_config_string: bootcmd
fdtdec_get_config_int: bootsecure
### main_loop: bootcmd="sf probe 0:0;sf read $kernel_load$kernel_start $kernel_size;bootm $kernel_load"
Hit any key to stop autoboot: 0
=>
=> print
EXPORT table = 00000000ffd89780, htab.size = 521, htab.filled = 31, size = 0
Unsorted: n=31
0: 00000000ffc00b98 ==> eth2addr => 00:e0:0c:00:89:02
1: 00000000ffc010c0 ==> initrd_high => 0xffffffffffffffff
2: 00000000ffc013b8 ==> fdtcontroladdr => ffbf87b0
3: 00000000ffc01408 ==> kernel_start => 0x1000000
4: 00000000ffc01458 ==> ethprime => FM1@DTSEC5
5: 00000000ffc016d8 ==> eth1addr => 00:e0:0c:00:89:01
6: 00000000ffc01a48 ==> ethaddr => 00:e0:0c:00:89:00
7: 00000000ffc01a98 ==> ramdisk_size => 0x2000000
8: 00000000ffc01de0 ==> stdin => serial
9: 00000000ffc01f20 ==> baudrate => 115200
10: 00000000ffc022e0 ==> netmask => 255.255.255.0
11: 00000000ffc02358 ==> serverip => 192.168.1.131
12: 00000000ffc025b0 ==> ethact => FM1@DTSEC5
13: 00000000ffc02768 ==> bootcmd => sf probe 0:0;sf read $kernel_load$kernel_start $kernel_size;bootm $kernel_load
14: 00000000ffc02790 ==> kernel_load => 0xa0000000
15: 00000000ffc02da8 ==> stderr => serial
16: 00000000ffc031b8 ==> hwconfig => fsl_ddr:bank_intlv=auto
17: 00000000ffc033e8 ==> fman_ucode => ffc06000
18: 00000000ffc03528 ==> loadaddr => 0x80100000
19: 00000000ffc03820 ==> bootdelay => 10
20: 00000000ffc03bb8 ==> mtdparts => 1550000.quadspi:1m(rcw),15m(u-boot),48m(kernel.itb);7e800000.flash:16m(nand_uboot),48m(nand_kernel),448m(nand_free)
21: 00000000ffc03c80 ==> scsidevs => 0
22: 00000000ffc04040 ==> stdout => serial
23: 00000000ffc04270 ==> ramdisk_addr => 0x800000
24: 00000000ffc04900 ==> kernel_size => 0x2800000
25: 00000000ffc04b80 ==> console => ttyS0,115200
26: 00000000ffc051c0 ==> eth3addr => 00:e0:0c:00:89:03
27: 00000000ffc05328 ==> fdt_high => 0xffffffffffffffff
28: 00000000ffc05490 ==> gatewayip => 192.168.1.1
29: 00000000ffc05648 ==> bootargs => console=ttyS0,115200 root=/dev/ram0 earlycon=uart8250,mmio,0x21c0500 mtdparts=1550000.quadspi:1m(rcw),15m(u-boot),48m(kernel.itb);7e800000.flash:16m(nand_uboot),48m(nand_kernel),448m(nand_free)
30: 00000000ffc05738 ==> ipaddr => 192.168.1.130
baudrate=115200
bootargs=console=ttyS0,115200 root=/dev/ram0 earlycon=uart8250,mmio,0x21c0500 mtdparts=1550000.quadspi:1m(rcw),15m(u-boot),48m(kernel.itb);7e800000.flash:16m(nand_uboot),48m(nand_kernel),448m(nand_free)
bootcmd=sf probe 0:0;sf read $kernel_load$kernel_start $kernel_size;bootm $kernel_load
bootdelay=10
console=ttyS0,115200
eth1addr=00:e0:0c:00:89:01
eth2addr=00:e0:0c:00:89:02
eth3addr=00:e0:0c:00:89:03
ethact=FM1@DTSEC5
ethaddr=00:e0:0c:00:89:00
ethprime=FM1@DTSEC5
fdt_high=0xffffffffffffffff
fdtcontroladdr=ffbf87b0
fman_ucode=ffc06000
gatewayip=192.168.1.1
hwconfig=fsl_ddr:bank_intlv=auto
initrd_high=0xffffffffffffffff
ipaddr=192.168.1.130
kernel_load=0xa0000000
kernel_size=0x2800000
kernel_start=0x1000000
loadaddr=0x80100000
mtdparts=1550000.quadspi:1m(rcw),15m(u-boot),48m(kernel.itb);7e800000.flash:16m(nand_uboot),48m(nand_kernel),448m(nand_free)
netmask=255.255.255.0
ramdisk_addr=0x800000
ramdisk_size=0x2000000
scsidevs=0
serverip=192.168.1.131
stderr=serial
stdin=serial
stdout=serial

Environment size: 1082/8188 bytes
=>"

And I read the memory of the FMAN loaded:

"

Environment size: 1082/8188 bytes
=> md 0xffc06000
ffc06000: b8920000 01464551 7263694d 646f636f ....QEF.Microcod
ffc06010: 65762065 6f697372 3031206e 2e342e38 e version 108.4.
ffc06020: 6f662039 534c2072 36343031 2e317220 9 for LS1046 r1.
ffc06030: 00000030 00000000 00000000 00000000 0...............
ffc06040: 00000000 01000000 00011604 00000000 ................
ffc06050: 00000000 00000000 00000000 00000000 ................
ffc06060: 00000000 00000000 00000000 00000000 ................
ffc06070: 00000000 00000000 00000000 7263694d ............Micr
ffc06080: 646f636f 6f662065 534c2072 36343031 ocode for LS1046
ffc06090: 2e317220 00000030 00000000 00000000 r1.0...........
ffc060a0: 00000000 00000000 00000000 00000000 ................
ffc060b0: 00000000 00000000 00000000 00000000 ................
ffc060c0: 00000000 00000000 00000000 00000000 ................
ffc060d0: 00000000 00000000 00000000 00008020 ............ ...
ffc060e0: 00000000 70240000 f4000000 0009046c ......$p....l...
ffc060f0: 00000000 4202ffb7 09046c00 5602ffb7 .......B.l.....V

"

Expecting your replies, thanks!

santhana_krishn · ‎04-04-2019

Hey tap yang,

How you have solved the problem? Now I am also facing the same problem.

Can you help me to resolve this issue?

tapyang · ‎04-15-2018

I have solved this problem, It is my board's fault.

Thank you all the same!~

yipingwang · ‎04-15-2018

Hello tap yang,

The Ethernet controller has transmission buffers - special blocks in memory, there the customer should place outgoing data. These buffers are described in buffer descriptors (TxBD).

The error "tx error - no empty TxBD" means there is no empty buffer were found to place outgoing data. This is either a software error or controller is not transmitting The controller may be not transmitting due to no transmission clocks present, or stopped due to some errors.

Would you please refer to the section "30.7.8.1 MDIO_SGMII Memory Map" in LS1046 Reference manual to dump all these registers in the list?

Please refer to the following on LS1046ARDB. You could compare these registers values with your custom board, and find whether there is anything abnormal according to the specific register description.

=> mdio read FM1@DTSEC5 0-0x1b
Reading from bus FSL_MDIO0
PHY at address 3:
0 - 0x1040
1 - 0x79a9
2 - 0x1c
3 - 0xc916
4 - 0x1e1
5 - 0xc1e1
6 - 0x6f
7 - 0x2001
8 - 0x5806
9 - 0x200
10 - 0x4800
11 - 0x0
12 - 0x0
13 - 0x0
14 - 0x0
15 - 0x2000
16 - 0x0
17 - 0x0
18 - 0x0
19 - 0x0
20 - 0x0
21 - 0x0
22 - 0x0
23 - 0x0
24 - 0x2198
25 - 0x863
26 - 0x392e
27 - 0x2

In addition, did you configured FM1@DTSEC5 as SGMII @1.25Gbps or 3.125Gbps?

On LS1046ARDB, we configure SD1_CLK1 = 156.25MHZ to configures SGMII at 2.5 G SGMII (3.125
Gbps).

If further assistance is needed, please provided more information which I mentioned as the above.

Have a great day,
TIC

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

tapyang · ‎04-12-2018

Hi, Is there someone help me?

I did some tries on code, such as open the debug and modify the eth.c code.

Then, the situation is different for first time.

=> ping 192.168.1.131
--- net_loop Entry
--- net_loop UDP handler set (0000000000000000)
--- net_loop ARP handler set (0000000000000000)
--- net_loop timeout handler cancelled
Trying FM1@DTSEC5
memac_set_interface_mode, if_mode = 9002
memac_set_interface_mode, if_status = 2000
--- NetState set to 0
--- net_loop Init
Using FM1@DTSEC5 device
--- net_loop timeout handler set (00000000ffd656c4)
sending ARP for 192.168.1.131
ARP broadcast 1
FM1@DTSEC5: Tx buffer ready, txbd->status = 0x800, addr = 0xffbfd7b0
FM1@DTSEC5: Tx error, txbd->status = 0xffff
ARP broadcast 2
FM1@DTSEC5: Tx buffer not ready, txbd->status = 0xffff, addr = 0xffbfd7b0
ARP broadcast 3
FM1@DTSEC5: Tx buffer not ready, txbd->status = 0xffff, addr = 0xffbfd7b0
ARP broadcast 4
FM1@DTSEC5: Tx buffer not ready, txbd->status = 0xffff, addr = 0xffbfd7b0

ARP Retry count exceeded; starting again
--- NetState set to 3
--- NetState set to 3
--- net_loop UDP handler set (0000000000000000)
--- net_loop ARP handler set (0000000000000000)
--- net_loop timeout handler cancelled
--- net_loop Fail!
ping failed; host 192.168.1.131 is not alive
Command failed, result=1
=>

Dear experts, Please help me~!

tapyang · ‎04-02-2018

Hi, Dear NXP Experts:

This project is very very urgent, and I've been stuck in this place for a long time.

Did anyone help me answer this question?

HELP~~~!

I did some tries, as followed:

"

=> ping 192.168.1.130

Trying FM1@DTSEC5

memac_set_interface_mode, if_mode = 9002

memac_set_interface_mode, if_status = 2000

Using FM1@DTSEC5 device

FM1@DTSEC5: Tx error, txbd->status = 0xffff

FM1@DTSEC5: Tx buffer not ready, txbd->status = 0xffff, addr = 0xffbfd990

ARP Retry count exceeded; starting again

ping failed; host 192.168.1.130 is not alive

Command failed, result=1

=> md 0xffbfd990

ffbfd990: ffffffff ffffffff ffffffff ffffffff ................

ffbfd9a0: ffffffff ffffffff ffffffff ffffffff ................

ffbfd9b0: ffffffff ffffffff ffffffff ffffffff ................

ffbfd9c0: 00000008 00000000 00000000 00000000 ................

ffbfd9d0: 00000008 00000000 00000000 00000000 ................

ffbfd9e0: 00000008 00000000 00000000 00000000 ................

ffbfd9f0: 00000008 00000000 00000000 00000000 ................

ffbfda00: 00000008 00000000 00000000 00000000 ................

ffbfda10: 00000000 00000000 00000061 00000000 ........a.......

ffbfda20: ffbfcfb0 00000000 ffd93b88 00000000 .........;......

ffbfda30: 00000000 00000000 ffbfd7b0 00000000 ................

ffbfda40: 000003e8 00000001 00000001 00000000 ................

ffbfda50: 00000002 0000002f 0000002f 00000000 ..../.../.......

ffbfda60: 00000001 00000004 00000000 00000000 ................

ffbfda70: 004dd074 00000000 00000071 00000000 t.M.....q.......

ffbfda80: 40314d46 45535444 00003643 00000000 FM1@DTSEC6......

=> mw

Command failed, result=-1

mw - memory write (fill)

Usage:

mw [.b, .w, .l, .q] address value [count]

=>

Command failed, result=-1

mw - memory write (fill)

Usage:

mw [.b, .w, .l, .q] address value [count]

=> mw 0xffbfd990 0x00000008 4

=>

=> md 0xffbfd990

ffbfd990: 00000008 00000008 00000008 00000008 ................