This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM6548: Ethernet port RX not work well

Part Number: AM6548

Tool/software:

Hi Ti,

We are looking into an issue that Ethernet sometimes cannot work well. 

We are using Linux SDK 7 RT version, we know it' quite old version.

We have two ethernet ports on our customized board.

When this issue happened, we found only port 1 cannot work well and port 2 always working good.

We tried to use ethtool to get some info as below, and we got rx_good_frames: 0.

Could you let us know what is rx_good_frames meaning?

./ethtool -S EthernetX1
NIC statistics:
rx_good_frames: 0
rx_broadcast_frames: 1441
rx_multicast_frames: 6033
rx_crc_error_frames: 6077
rx_mii_error_frames: 0
rx_odd_nibble_frames: 0
rx_frame_max_size: 2000
rx_max_size_error_frames: 0
rx_frame_min_size: 64
rx_min_size_error_frames: 8
rx_overrun_frames: 1
rx_class0_hits: 6078
rx_class1_hits: 0
rx_class2_hits: 0
rx_class3_hits: 0
rx_class4_hits: 0
rx_class5_hits: 0
rx_class6_hits: 0
rx_class7_hits: 0
rx_class8_hits: 0
rx_class9_hits: 0
rx_class10_hits: 0
rx_class11_hits: 0
rx_class12_hits: 0
rx_class13_hits: 0
rx_class14_hits: 0
rx_class15_hits: 0
rx_smd_frags: 0
rx_bucket1_size: 64
rx_bucket2_size: 128
rx_bucket3_size: 256
rx_bucket4_size: 512
rx_64B_frames: 431
rx_bucket1_frames: 439
rx_bucket2_frames: 5061
rx_bucket3_frames: 538
rx_bucket4_frames: 40
rx_bucket5_frames: 0
rx_total_bytes: 602983
rx_tx_total_bytes: 628641
tx_good_frames: 204
tx_broadcast_frames: 42
tx_multicast_frames: 204
tx_odd_nibble_frames: 0
tx_underflow_errors: 0
tx_frame_max_size: 2000
tx_max_size_error_frames: 0
tx_frame_min_size: 64
tx_min_size_error_frames: 0
tx_bucket1_size: 64
tx_bucket2_size: 128
tx_bucket3_size: 256
tx_bucket4_size: 512
tx_64B_frames: 0
tx_bucket1_frames: 0
tx_bucket2_frames: 204
tx_bucket3_frames: 0
tx_bucket4_frames: 0
tx_bucket5_frames: 0
tx_total_bytes: 17702

./ethtool -S EthernetX2
NIC statistics:
rx_good_frames: 14118
rx_broadcast_frames: 205
rx_multicast_frames: 565
rx_crc_error_frames: 0
rx_mii_error_frames: 0
rx_odd_nibble_frames: 0
rx_frame_max_size: 2000
rx_max_size_error_frames: 0
rx_frame_min_size: 64
rx_min_size_error_frames: 0
rx_overrun_frames: 0
rx_class0_hits: 14118
rx_class1_hits: 0
rx_class2_hits: 0
rx_class3_hits: 0
rx_class4_hits: 0
rx_class5_hits: 0
rx_class6_hits: 0
rx_class7_hits: 0
rx_class8_hits: 0
rx_class9_hits: 0
rx_class10_hits: 0
rx_class11_hits: 0
rx_class12_hits: 0
rx_class13_hits: 0
rx_class14_hits: 0
rx_class15_hits: 0
rx_smd_frags: 0
rx_bucket1_size: 64
rx_bucket2_size: 128
rx_bucket3_size: 256
rx_bucket4_size: 512
rx_64B_frames: 221
rx_bucket1_frames: 221
rx_bucket2_frames: 3349
rx_bucket3_frames: 121
rx_bucket4_frames: 12
rx_bucket5_frames: 10415
rx_total_bytes: 15949353
rx_tx_total_bytes: 16874226
tx_good_frames: 4854
tx_broadcast_frames: 0
tx_multicast_frames: 45
tx_odd_nibble_frames: 0
tx_underflow_errors: 0
tx_frame_max_size: 2000
tx_max_size_error_frames: 0
tx_frame_min_size: 64
tx_min_size_error_frames: 0
tx_bucket1_size: 64
tx_bucket2_size: 128
tx_bucket3_size: 256
tx_bucket4_size: 512
tx_64B_frames: 0
tx_bucket1_frames: 0
tx_bucket2_frames: 2360
tx_bucket3_frames: 2284
tx_bucket4_frames: 147
tx_bucket5_frames: 63
tx_total_bytes: 735567

Thanks.

Eric

  • Hi Eric,

    rx_crc_error_frames: 6077

    Please take a look at the Basic Ethernet Interface Debug With Linux application note: https://www.ti.com/lit/an/spradj8/spradj8.pdf (snippet below)

    A non-zero rx crc error counter indicates packets are dropped at the Ethernet interface because CRC checksum errors were detected. It could potentially mean corruption of packets occurred at some point from the sender of the packets, the Ethernet cable, or even the board layout for the MAC-PHY interface. Your next step should be to check one-by one along the path of a packet from the source to your device under test, sources that may be causing CRC checksum errors.

    Let us know if you have additional questions.

    -Daolin