LS1046A 10G SFP+ operation issue

JSKIM — Tue, 15 Dec 2020 11:06:24 GMT

I have a question about 10G SFP+ operation of lsdk 2004.

After 10G bring-up, i can see interface of 10G SFP+.

And tx count is up. but when i tried ping-test, there was no response. so 10G RX operation is not working.

so i check interface with ethtool. i found out that Transceiver is internal mode.

i think Transceiver would be external when fixed-link used.

may i have the reason about rx operation fail ?

i attach some information about status.

* ethtool info.

root@TinyLinux:~# ethtool fm1-mac9
Settings for fm1-mac9:
Supported ports: [ ]
Supported link modes: Not reported
Supported pause frame use: No
Supports auto-negotiation: No
Supported FEC modes: Not reported
Advertised link modes: Not reported
Advertised pause frame use: No
Advertised auto-negotiation: No
Advertised FEC modes: Not reported
Speed: 10000Mb/s
Duplex: Full
Port: MII
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: d
Wake-on: d
Current message level: 0xffffffff (-1)
drv probe link timer ifdown ifup rx_err tx_err tx_queued intr tx_done rx_status pktdata hw wol 0xffff8000
Link detected: yes

* ifconfig info

root@TinyLinux:~# ifconfig
fm1-mac9 Link encap:Ethernet HWaddr 00:04:9f:05:3d:0b
inet addr:192.168.47.131 Bcast:192.168.47.255 Mask:255.255.255.0
inet6 addr: fe80::204:9fff:fe05:3d0b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:726 (726.0 B)
Memory:1af0000-1af0fff

* Device Tree Info.

&fman0 {
ethernet@e4000 {
phy-handle = <&rgmii_phy1>;
phy-connection-type = "rgmii-id";
};

ethernet@f0000 { /* 10GEC1 */
fixed-link = <0 1 10000 0 0>;
phy-connection-type = "xgmii";
};

mdio@fc000 {
rgmii_phy1: ethernet-phy@1 {
reg = <0x0>;
};
};
};

* mac reg info

root@TinyLinux:/sys/class/net/fm1-mac9# cat mac_regs
-------

FM MAC - MEMAC -0 (0x8645D000)
----------------------------------------

0x008645D008: 0x00020843 command_config
0x008645D00C: 0x059f0400 mac_addr0.mac_addr_l
0x008645D010: 0x00000b3d mac_addr0.mac_addr_u
0x008645D014: 0x00002580 maxfrm
0x008645D02C: 0x00000130 hashtable_ctrl
0x008645D040: 0x00000042 ievent
0x008645D044: 0x0000000c tx_ipg_length
0x008645D04C: 0x63000000 imask
0x008645D054: 0x0000f000 pause_quanta[i]
0x008645D058: 0x00000000 pause_quanta[i]
0x008645D05C: 0x00000000 pause_quanta[i]
0x008645D060: 0x00000000 pause_quanta[i]
0x008645D064: 0x00000000 pause_thresh[i]
0x008645D068: 0x00000000 pause_thresh[i]
0x008645D06C: 0x00000000 pause_thresh[i]
0x008645D070: 0x00000000 pause_thresh[i]
0x008645D074: 0x00000000 rx_pause_status
0x008645D080: 0x00000000 mac_addr[i].mac_addr_l
0x008645D084: 0x00000000 mac_addr[i].mac_addr_u
0x008645D088: 0x00000000 mac_addr[i].mac_addr_l
0x008645D08C: 0x00000000 mac_addr[i].mac_addr_u
0x008645D090: 0x00000000 mac_addr[i].mac_addr_l
0x008645D094: 0x00000000 mac_addr[i].mac_addr_u
0x008645D098: 0x00000000 mac_addr[i].mac_addr_l
0x008645D09C: 0x00000000 mac_addr[i].mac_addr_u
0x008645D0A0: 0x00000000 mac_addr[i].mac_addr_l
0x008645D0A4: 0x00000000 mac_addr[i].mac_addr_u
0x008645D0A8: 0x00000000 mac_addr[i].mac_addr_l
0x008645D0AC: 0x00000000 mac_addr[i].mac_addr_u
0x008645D0B0: 0x00000000 mac_addr[i].mac_addr_l
0x008645D0B4: 0x00000000 mac_addr[i].mac_addr_u
0x008645D0B8: 0x00002000 lpwake_timer
0x008645D0BC: 0x00000000 sleep_timer
0x008645D0E0: 0x00000000 statn_config
0x008645D300: 0x00000000 if_mode
0x008645D304: 0x00002000 if_status
0x008645D340: 0x00000000 hg_config
0x008645D350: 0x00000000 hg_pause_quanta
0x008645D360: 0x00000000 hg_pause_thresh
0x008645D370: 0x00000000 hgrx_pause_status
0x008645D374: 0x00000000 hg_fifos_status
0x008645D378: 0x00000000 rhm
0x008645D37C: 0x00000000 thm
root@TinyLinux:/sys/class/net/fm1-mac9#

root@TinyLinux:/sys/class/net/fm1-mac9/statistics# ls
collisions rx_errors rx_over_errors tx_dropped
multicast rx_fifo_errors rx_packets tx_errors
rx_bytes rx_frame_errors tx_aborted_errors tx_fifo_errors
rx_compressed rx_length_errors tx_bytes tx_heartbeat_errors
rx_crc_errors rx_missed_errors tx_carrier_errors tx_packets
rx_dropped rx_nohandler tx_compressed tx_window_errors
root@TinyLinux:/sys/class/net/fm1-mac9/statistics# cat tx_bytes
866
root@TinyLinux:/sys/class/net/fm1-mac9/statistics# cat rx_errors
0
root@TinyLinux:/sys/class/net/fm1-mac9/statistics# cat rx_bytes
0
root@TinyLinux:/sys/class/net/fm1-mac9/statistics#

Re: LS1046A 10G SFP+ operation issue

bpe — Thu, 17 Dec 2020 13:55:25 GMT

If you are interfacing LS1046A XFI port to an SFP+ without a PHY, make sure
you have a retimer in between, like it is done on LS1046A-RDB. The link may
fail in either direction otherwise. As of the transmitter displayed as internal
or external in ethtool output, since you are using a "fixed-link", which is
effectively a zero-PHY driver, this filed is not meaningful.

Best Regards,
Platon

Re: LS1046A 10G SFP+ operation issue

bpe — Tue, 22 Dec 2020 02:56:33 GMT

I have created a new topic for your recent questions. Please avoid asking unrelated questions in a single thread in future,

LayerscapeのトピックRe: LS1046A 10G SFP+ operation issue

LS1046A 10G SFP+ operation issue

Re: LS1046A 10G SFP+ operation issue

Re: LS1046A 10G SFP+ operation issue