Because of the Thanksgiving holiday in the U.S., TI E2E™ design support forum responses may be delayed from November 25 through December 2. Thank you for your patience.

DRA821U: CPSW2G is not functional with the 1G speed (SDK: J7200 10.00.07.03)

Part Number: DRA821U
Other Parts Discussed in Thread: DRA821

Tool/software:

Hi Team,

I want to use the CPSW2G core in MAC Mode to connect directly to another computer.

The test environments:

Board J721EXCP01EVM www.ti.com/.../J721EXCP01EVM
SDK PROCESSOR-SDK-LINUX-J7200 — Linux SDK for DRA821 Jacinto Processors
SDK 
Version: 10.00.07.03 (https://www.ti.com/tool/PROCESSOR-SDK-J7200)
Boot Mode SD Card
Kernel Version 6.6.32-ti

However, in the previous SDK version: 09.02.00.04, the CPSW2G worked fine and could successfully ping the DUT.

In SDK version 10.00.07.03, the CPSW2G is not functional with the 1G speed setting.

  • 100M ((ethtool -s eth0 speed 100)
    root@j7200-evm:~# ethtool -s eth0 speed 100
    root@j7200-evm:~# [ 3380.929929] am65-cpsw-nuss 46000000.ethernet eth0: Link is Down
    [ 3384.005460] am65-cpsw-nuss 46000000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
    
    root@j7200-evm:~# ping 192.168.3.128 -I eth0
    PING 192.168.3.128 (192.168.3.128) from 192.168.3.127 eth0: 56(84) bytes of data.
    64 bytes from 192.168.3.128: icmp_seq=1 ttl=64 time=0.472 ms
    64 bytes from 192.168.3.128: icmp_seq=2 ttl=64 time=0.389 ms
    64 bytes from 192.168.3.128: icmp_seq=3 ttl=64 time=0.394 ms
    ^C
    --- 192.168.3.128 ping statistics ---
    3 packets transmitted, 3 received, 0% packet loss, time 2040ms
  • 1G (ethtool -s eth0 speed 1000)
    root@j7200-evm:~# ethtool -s eth0 speed 1000
    root@j7200-evm:~# [ 3474.738015] am65-cpsw-nuss 46000000.ethernet eth0: Link is Down
    [ 3478.821479] am65-cpsw-nuss 46000000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
    
    root@j7200-evm:~# ethtool eth0
    Settings for eth0:
    	Supported ports: [ TP	 MII ]
    	Supported link modes:   10baseT/Half 10baseT/Full
    	                        100baseT/Half 100baseT/Full
    	                        1000baseT/Full
    	Supported pause frame use: Symmetric
    	Supports auto-negotiation: Yes
    	Supported FEC modes: Not reported
    	Advertised link modes:  1000baseT/Full
    	Advertised pause frame use: Symmetric
    	Advertised auto-negotiation: Yes
    	Advertised FEC modes: Not reported
    	Link partner advertised link modes:  10baseT/Half 10baseT/Full
    	                                     100baseT/Half 100baseT/Full
    	                                     1000baseT/Full
    	Link partner advertised pause frame use: Symmetric Receive-only
    	Link partner advertised auto-negotiation: Yes
    	Link partner advertised FEC modes: Not reported
    	Speed: 1000Mb/s
    	Duplex: Full
    	Auto-negotiation: on
    	master-slave cfg: preferred slave
    	master-slave status: slave
    	Port: Twisted Pair
    	PHYAD: 0
    	Transceiver: external
    	MDI-X: Unknown
    	Supports Wake-on: ubgs
    	Wake-on: d
            SecureOn password: 00:00:00:00:00:00
            Current message level: 0x000020f7 (8439)
                                   drv probe link ifdown ifup rx_err tx_err hw
    	Link detected: yes
    root@j7200-evm:~# ping 192.168.3.128 -I eth0
    PING 192.168.3.128 (192.168.3.128) from 192.168.3.127 eth0: 56(84) bytes of data.
    ^C
    --- 192.168.3.128 ping statistics ---

  • Hi,

    What is the phy-mode selected for the CPSW2G?

    if RGMII delays are taken care? MAC side only tx delay is supported.
    Please refer to FAQ [How to configure the RGMII delay in J7 devices].

    If delays are taken care? can you please check CPSW statistics any errors/drops in packets.
    #ethtool -S eth0

    Best Regards,
    Sudheer

  • Hi Sudheer,

    The phy-mode is rgmii-rxid

    P: /devices/platform/bus@100000/bus@100000:bus@28380000/46000000.ethernet/net/eth0
    M: eth0
    R: 0
    U: net
    I: 2
    E: DEVPATH=/devices/platform/bus@100000/bus@100000:bus@28380000/46000000.ethernet/net/eth0
    E: SUBSYSTEM=net
    E: INTERFACE=eth0
    E: IFINDEX=2
    E: USEC_INITIALIZED=6239798
    E: ID_NET_DRIVER=am65-cpsw-nuss
    E: ID_NET_NAMING_SCHEME=v255
    E: ID_NET_NAME_MAC=enxf4844cf8e7a9
    E: ID_OUI_FROM_DATABASE=Texas Instruments
    E: ID_PATH=platform-46000000.ethernet
    E: ID_PATH_TAG=platform-46000000_ethernet
    E: ID_NET_LINK_FILE=/usr/lib/systemd/network/99-default.link
    E: ID_NET_NAME=eth0
    E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/eth0
    E: TAGS=:systemd:
    E: CURRENT_TAGS=:systemd
    
    cat /proc/device-tree/bus@100000/bus@28380000/ethernet@46000000/ethernet-ports/port@1/phy-mode
    rgmii-rxid


    The statistics: (The occurrence of RX CRC errors is unusual)

    root@j7200-evm:~# ethtool -S eth0
    NIC statistics:
         p0_rx_good_frames: 109
         p0_rx_broadcast_frames: 24
         p0_rx_multicast_frames: 29
         p0_rx_crc_errors: 0
         p0_rx_oversized_frames: 0
         p0_rx_undersized_frames: 0
         p0_ale_drop: 0
         p0_ale_overrun_drop: 0
         p0_rx_octets: 17566
         p0_tx_good_frames: 6
         p0_tx_broadcast_frames: 0
         p0_tx_multicast_frames: 0
         p0_tx_octets: 384
         p0_tx_64B_frames: 14
         p0_tx_65_to_127B_frames: 66
         p0_tx_128_to_255B_frames: 9
         p0_tx_256_to_511B_frames: 26
         p0_tx_512_to_1023B_frames: 0
         p0_tx_1024B_frames: 0
         p0_net_octets: 17950
         p0_rx_bottom_fifo_drop: 0
         p0_rx_port_mask_drop: 0
         p0_rx_top_fifo_drop: 0
         p0_ale_rate_limit_drop: 0
         p0_ale_vid_ingress_drop: 0
         p0_ale_da_eq_sa_drop: 0
         p0_ale_block_drop: 0
         p0_ale_secure_drop: 0
         p0_ale_auth_drop: 0
         p0_ale_unknown_ucast: 0
         p0_ale_unknown_ucast_bytes: 0
         p0_ale_unknown_mcast: 0
         p0_ale_unknown_mcast_bytes: 0
         p0_ale_unknown_bcast: 0
         p0_ale_unknown_bcast_bytes: 0
         p0_ale_pol_match: 0
         p0_ale_pol_match_red: 0
         p0_ale_pol_match_yellow: 0
         p0_ale_mcast_sa_drop: 0
         p0_ale_dual_vlan_drop: 0
         p0_ale_len_err_drop: 0
         p0_ale_ip_next_hdr_drop: 0
         p0_ale_ipv4_frag_drop: 0
         p0_tx_mem_protect_err: 0
         p0_tx_pri0: 0
         p0_tx_pri1: 0
         p0_tx_pri2: 0
         p0_tx_pri3: 0
         p0_tx_pri4: 0
         p0_tx_pri5: 0
         p0_tx_pri6: 0
         p0_tx_pri7: 0
         p0_tx_pri0_bcnt: 0
         p0_tx_pri1_bcnt: 0
         p0_tx_pri2_bcnt: 0
         p0_tx_pri3_bcnt: 0
         p0_tx_pri4_bcnt: 0
         p0_tx_pri5_bcnt: 0
         p0_tx_pri6_bcnt: 0
         p0_tx_pri7_bcnt: 0
         p0_tx_pri0_drop: 0
         p0_tx_pri1_drop: 0
         p0_tx_pri2_drop: 0
         p0_tx_pri3_drop: 0
         p0_tx_pri4_drop: 0
         p0_tx_pri5_drop: 0
         p0_tx_pri6_drop: 0
         p0_tx_pri7_drop: 0
         p0_tx_pri0_drop_bcnt: 0
         p0_tx_pri1_drop_bcnt: 0
         p0_tx_pri2_drop_bcnt: 0
         p0_tx_pri3_drop_bcnt: 0
         p0_tx_pri4_drop_bcnt: 0
         p0_tx_pri5_drop_bcnt: 0
         p0_tx_pri6_drop_bcnt: 0
         p0_tx_pri7_drop_bcnt: 0
         rx_good_frames: 6
         rx_broadcast_frames: 0
         rx_multicast_frames: 0
         rx_pause_frames: 0
         rx_crc_errors: 51
         rx_align_code_errors: 0
         rx_oversized_frames: 0
         rx_jabber_frames: 0
         rx_undersized_frames: 0
         rx_fragments: 0
         ale_drop: 0
         ale_overrun_drop: 0
         rx_octets: 384
         tx_good_frames: 109
         tx_broadcast_frames: 24
         tx_multicast_frames: 29
         tx_pause_frames: 0
         tx_deferred_frames: 0
         tx_collision_frames: 0
         tx_single_coll_frames: 0
         tx_mult_coll_frames: 0
         tx_excessive_collisions: 0
         tx_late_collisions: 0
         rx_ipg_error: 0
         tx_carrier_sense_errors: 0
         tx_octets: 17566
         tx_64B_frames: 14
         tx_65_to_127B_frames: 117
         tx_128_to_255B_frames: 9
         tx_256_to_511B_frames: 26
         tx_512_to_1023B_frames: 0
         tx_1024B_frames: 0
         net_octets: 23152
         rx_bottom_fifo_drop: 0
         rx_port_mask_drop: 51
         rx_top_fifo_drop: 0
         ale_rate_limit_drop: 0
         ale_vid_ingress_drop: 0
         ale_da_eq_sa_drop: 0
         ale_block_drop: 0
         ale_secure_drop: 0
         ale_auth_drop: 0
         ale_unknown_ucast: 6
         ale_unknown_ucast_bytes: 384
         ale_unknown_mcast: 0
         ale_unknown_mcast_bytes: 0
         ale_unknown_bcast: 0
         ale_unknown_bcast_bytes: 0
         ale_pol_match: 0
         ale_pol_match_red: 0
         ale_pol_match_yellow: 0
         ale_mcast_sa_drop: 0
         ale_dual_vlan_drop: 0
         ale_len_err_drop: 0
         ale_ip_next_hdr_drop: 0
         ale_ipv4_frag_drop: 0
         iet_rx_assembly_err: 0
         iet_rx_assembly_ok: 0
         iet_rx_smd_err: 0
         iet_rx_frag: 0
         iet_tx_hold: 0
         iet_tx_frag: 0
         tx_mem_protect_err: 0
         tx_pri0: 109
         tx_pri1: 0
         tx_pri2: 0
         tx_pri3: 0
         tx_pri4: 0
         tx_pri5: 0
         tx_pri6: 0
         tx_pri7: 0
         tx_pri0_bcnt: 17566
         tx_pri1_bcnt: 0
         tx_pri2_bcnt: 0
         tx_pri3_bcnt: 0
         tx_pri4_bcnt: 0
         tx_pri5_bcnt: 0
         tx_pri6_bcnt: 0
         tx_pri7_bcnt: 0
         tx_pri0_drop: 0
         tx_pri1_drop: 0
         tx_pri2_drop: 0
         tx_pri3_drop: 0
         tx_pri4_drop: 0
         tx_pri5_drop: 0
         tx_pri6_drop: 0
         tx_pri7_drop: 0
         tx_pri0_drop_bcnt: 0
         tx_pri1_drop_bcnt: 0
         tx_pri2_drop_bcnt: 0
         tx_pri3_drop_bcnt: 0
         tx_pri4_drop_bcnt: 0
         tx_pri5_drop_bcnt: 0
         tx_pri6_drop_bcnt: 0
         tx_pri7_drop_bcnt: 0

    The tcpdump on the DUT side shows normal requests and replies, but the CPSW2G side does not receive the replies.

  • Hi,

    The tcpdump on the DUT side shows normal requests and replies, but the CPSW2G side does not receive the replies.

    I could see CRC errors at external port Rx side.
    rx_crc_errors: 51

    It could be due to RGMII RX delay issue.

    As mentioned above MAC side of DRA821 supports only Tx delay. As phy-mode is configured as "rgmii-rxid" Tx delay will be enabled at MAC side.
    But, RX delay to enabled from peer side or via PCB traces.

    It is working at 100Mbps as clock rate is lower and delay doesn't impact the data transfer.

    However, in the previous SDK version: 09.02.00.04, the CPSW2G worked fine and could successfully ping the DUT.

    Please check with your H/W engineer about RGMII delay.
    Is there any Difference in DUT H/W or software running, please check how RGMII Rx delay controlled previously.

    Best Regards,
    Sudheer

  • Sudheer, 

    This test is done on TI DRA821 EVM and software package from TI website download SDK image. 

    Per your observation and comment, it seems RX delay could be enabled on PHY side in SDK 9.0 but it is not enabled in SDK 10.0. 

    Could you confirm this on SDK setting please? 

    BR, Rich 

  • Hi,

    I have tested TI SDK 10.0 (ti-processor-sdk-linux-j7200-evm-10_00_07_03). I am able to run 1Gbps link without any issue.

    Please find the Link speed and Ping log.

    root@j7200-evm:~# ethtool eth0
    Settings for eth0:
            Supported ports: [ TP    MII ]
            Supported link modes:   10baseT/Half 10baseT/Full
                                    100baseT/Half 100baseT/Full
                                    1000baseT/Full
            Supported pause frame use: Symmetric
            Supports auto-negotiation: Yes
            Supported FEC modes: Not reported
            Advertised link modes:  10baseT/Half 10baseT/Full
                                    100baseT/Half 100baseT/Full
                                    1000baseT/Full
            Advertised pause frame use: Symmetric
            Advertised auto-negotiation: Yes
            Advertised FEC modes: Not reported
            Link partner advertised link modes:  10baseT/Half 10baseT/Full
                                                 100baseT/Half 100baseT/Full
                                                 1000baseT/Full
            Link partner advertised pause frame use: No
            Link partner advertised auto-negotiation: Yes
            Link partner advertised FEC modes: Not reported
            Speed: 1000Mb/s
            Duplex: Full
            Auto-negotiation: on
            master-slave cfg: preferred slave
            master-slave status: slave
            Port: Twisted Pair
            PHYAD: 0
            Transceiver: external
            MDI-X: Unknown
            Supports Wake-on: ubgs
            Wake-on: d
            SecureOn password: 00:00:00:00:00:00
            Current message level: 0x000020f7 (8439)
                                   drv probe link ifdown ifup rx_err tx_err hw
            Link detected: yes
    root@j7200-evm:~# 
    root@j7200-evm:~# sudo ping 172.24.227.182 -i 0.01                                                                                                                                    
    PING 172.24.227.182 (172.24.227.182) 56(84) bytes of data.
    64 bytes from 172.24.227.182: icmp_seq=1 ttl=61 time=0.277 ms
    64 bytes from 172.24.227.182: icmp_seq=2 ttl=61 time=0.248 ms
    64 bytes from 172.24.227.182: icmp_seq=3 ttl=61 time=0.218 ms
    64 bytes from 172.24.227.182: icmp_seq=4 ttl=61 time=0.223 ms
    64 bytes from 172.24.227.182: icmp_seq=5 ttl=61 time=0.219 ms
    64 bytes from 172.24.227.182: icmp_seq=6 ttl=61 time=0.188 ms
    64 bytes from 172.24.227.182: icmp_seq=7 ttl=61 time=0.222 ms
    64 bytes from 172.24.227.182: icmp_seq=8 ttl=61 time=0.228 ms
    64 bytes from 172.24.227.182: icmp_seq=9 ttl=61 time=0.219 ms
    64 bytes from 172.24.227.182: icmp_seq=10 ttl=61 time=0.238 ms
    64 bytes from 172.24.227.182: icmp_seq=11 ttl=61 time=0.228 ms
    64 bytes from 172.24.227.182: icmp_seq=12 ttl=61 time=0.222 ms
    64 bytes from 172.24.227.182: icmp_seq=13 ttl=61 time=0.226 ms
    64 bytes from 172.24.227.182: icmp_seq=14 ttl=61 time=0.226 ms
    64 bytes from 172.24.227.182: icmp_seq=15 ttl=61 time=0.223 ms
    64 bytes from 172.24.227.182: icmp_seq=16 ttl=61 time=0.218 ms
    64 bytes from 172.24.227.182: icmp_seq=17 ttl=61 time=0.221 ms
    64 bytes from 172.24.227.182: icmp_seq=18 ttl=61 time=0.221 ms
    64 bytes from 172.24.227.182: icmp_seq=19 ttl=61 time=0.226 ms
    64 bytes from 172.24.227.182: icmp_seq=20 ttl=61 time=0.229 ms
    64 bytes from 172.24.227.182: icmp_seq=21 ttl=61 time=0.219 ms
    64 bytes from 172.24.227.182: icmp_seq=22 ttl=61 time=0.227 ms
    64 bytes from 172.24.227.182: icmp_seq=23 ttl=61 time=0.224 ms
    64 bytes from 172.24.227.182: icmp_seq=24 ttl=61 time=0.227 ms
    64 bytes from 172.24.227.182: icmp_seq=25 ttl=61 time=0.191 ms
    64 bytes from 172.24.227.182: icmp_seq=26 ttl=61 time=0.232 ms
    64 bytes from 172.24.227.182: icmp_seq=27 ttl=61 time=0.235 ms
    64 bytes from 172.24.227.182: icmp_seq=28 ttl=61 time=0.230 ms
    64 bytes from 172.24.227.182: icmp_seq=29 ttl=61 time=0.224 ms
    64 bytes from 172.24.227.182: icmp_seq=30 ttl=61 time=0.223 ms
    64 bytes from 172.24.227.182: icmp_seq=31 ttl=61 time=0.190 ms
    64 bytes from 172.24.227.182: icmp_seq=32 ttl=61 time=0.213 ms
    64 bytes from 172.24.227.182: icmp_seq=33 ttl=61 time=0.233 ms
    64 bytes from 172.24.227.182: icmp_seq=34 ttl=61 time=0.225 ms
    64 bytes from 172.24.227.182: icmp_seq=35 ttl=61 time=0.232 ms
    64 bytes from 172.24.227.182: icmp_seq=36 ttl=61 time=0.236 ms
    64 bytes from 172.24.227.182: icmp_seq=37 ttl=61 time=0.220 ms
    64 bytes from 172.24.227.182: icmp_seq=38 ttl=61 time=0.218 ms
    64 bytes from 172.24.227.182: icmp_seq=39 ttl=61 time=0.232 ms
    64 bytes from 172.24.227.182: icmp_seq=40 ttl=61 time=0.232 ms
    64 bytes from 172.24.227.182: icmp_seq=41 ttl=61 time=0.243 ms
    64 bytes from 172.24.227.182: icmp_seq=42 ttl=61 time=0.226 ms
    64 bytes from 172.24.227.182: icmp_seq=43 ttl=61 time=0.217 ms
    64 bytes from 172.24.227.182: icmp_seq=44 ttl=61 time=0.219 ms
    64 bytes from 172.24.227.182: icmp_seq=45 ttl=61 time=0.232 ms
    64 bytes from 172.24.227.182: icmp_seq=46 ttl=61 time=0.226 ms
    64 bytes from 172.24.227.182: icmp_seq=47 ttl=61 time=0.221 ms
    64 bytes from 172.24.227.182: icmp_seq=48 ttl=61 time=0.227 ms
    64 bytes from 172.24.227.182: icmp_seq=49 ttl=61 time=0.220 ms
    64 bytes from 172.24.227.182: icmp_seq=50 ttl=61 time=0.235 ms
    64 bytes from 172.24.227.182: icmp_seq=51 ttl=61 time=0.199 ms
    64 bytes from 172.24.227.182: icmp_seq=52 ttl=61 time=0.222 ms
    64 bytes from 172.24.227.182: icmp_seq=53 ttl=61 time=0.217 ms
    64 bytes from 172.24.227.182: icmp_seq=54 ttl=61 time=0.224 ms
    64 bytes from 172.24.227.182: icmp_seq=55 ttl=61 time=0.217 ms
    64 bytes from 172.24.227.182: icmp_seq=56 ttl=61 time=0.241 ms
    64 bytes from 172.24.227.182: icmp_seq=57 ttl=61 time=0.187 ms
    64 bytes from 172.24.227.182: icmp_seq=58 ttl=61 time=0.207 ms
    64 bytes from 172.24.227.182: icmp_seq=59 ttl=61 time=0.190 ms
    64 bytes from 172.24.227.182: icmp_seq=60 ttl=61 time=0.231 ms
    64 bytes from 172.24.227.182: icmp_seq=61 ttl=61 time=0.226 ms
    64 bytes from 172.24.227.182: icmp_seq=62 ttl=61 time=0.265 ms
    64 bytes from 172.24.227.182: icmp_seq=63 ttl=61 time=0.195 ms
    64 bytes from 172.24.227.182: icmp_seq=64 ttl=61 time=0.219 ms
    64 bytes from 172.24.227.182: icmp_seq=65 ttl=61 time=0.227 ms
    64 bytes from 172.24.227.182: icmp_seq=66 ttl=61 time=0.201 ms
    64 bytes from 172.24.227.182: icmp_seq=67 ttl=61 time=0.342 ms
    64 bytes from 172.24.227.182: icmp_seq=68 ttl=61 time=0.245 ms
    64 bytes from 172.24.227.182: icmp_seq=69 ttl=61 time=0.301 ms
    64 bytes from 172.24.227.182: icmp_seq=70 ttl=61 time=0.230 ms
    64 bytes from 172.24.227.182: icmp_seq=71 ttl=61 time=0.220 ms
    64 bytes from 172.24.227.182: icmp_seq=72 ttl=61 time=0.212 ms
    64 bytes from 172.24.227.182: icmp_seq=73 ttl=61 time=0.224 ms
    64 bytes from 172.24.227.182: icmp_seq=74 ttl=61 time=0.216 ms
    64 bytes from 172.24.227.182: icmp_seq=75 ttl=61 time=0.223 ms
    64 bytes from 172.24.227.182: icmp_seq=76 ttl=61 time=0.226 ms
    64 bytes from 172.24.227.182: icmp_seq=77 ttl=61 time=0.233 ms
    64 bytes from 172.24.227.182: icmp_seq=78 ttl=61 time=0.220 ms
    64 bytes from 172.24.227.182: icmp_seq=79 ttl=61 time=0.228 ms
    64 bytes from 172.24.227.182: icmp_seq=80 ttl=61 time=0.220 ms
    64 bytes from 172.24.227.182: icmp_seq=81 ttl=61 time=0.202 ms
    64 bytes from 172.24.227.182: icmp_seq=82 ttl=61 time=0.223 ms
    64 bytes from 172.24.227.182: icmp_seq=83 ttl=61 time=0.215 ms
    64 bytes from 172.24.227.182: icmp_seq=84 ttl=61 time=0.201 ms
    64 bytes from 172.24.227.182: icmp_seq=85 ttl=61 time=0.242 ms
    64 bytes from 172.24.227.182: icmp_seq=86 ttl=61 time=0.226 ms
    64 bytes from 172.24.227.182: icmp_seq=87 ttl=61 time=0.212 ms
    64 bytes from 172.24.227.182: icmp_seq=88 ttl=61 time=0.302 ms
    64 bytes from 172.24.227.182: icmp_seq=89 ttl=61 time=0.221 ms
    64 bytes from 172.24.227.182: icmp_seq=90 ttl=61 time=0.220 ms
    64 bytes from 172.24.227.182: icmp_seq=91 ttl=61 time=0.205 ms
    64 bytes from 172.24.227.182: icmp_seq=92 ttl=61 time=0.226 ms
    64 bytes from 172.24.227.182: icmp_seq=93 ttl=61 time=0.216 ms
    64 bytes from 172.24.227.182: icmp_seq=94 ttl=61 time=0.231 ms
    64 bytes from 172.24.227.182: icmp_seq=95 ttl=61 time=0.223 ms
    64 bytes from 172.24.227.182: icmp_seq=96 ttl=61 time=0.214 ms
    64 bytes from 172.24.227.182: icmp_seq=97 ttl=61 time=0.227 ms
    64 bytes from 172.24.227.182: icmp_seq=98 ttl=61 time=0.233 ms
    64 bytes from 172.24.227.182: icmp_seq=99 ttl=61 time=0.218 ms
    64 bytes from 172.24.227.182: icmp_seq=100 ttl=61 time=0.227 ms
    64 bytes from 172.24.227.182: icmp_seq=101 ttl=61 time=0.183 ms
    ^C
    --- 172.24.227.182 ping statistics ---
    101 packets transmitted, 101 received, 0% packet loss, time 1598ms
    rtt min/avg/max/mdev = 0.183/0.224/0.342/0.021 ms
    


    Please check your SD card creation steps? have you suing default SDK image while preparing SD card or not?
    Please follow steps mentioned in SDK documentation for creation of SD card.
    https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-j7200/10_00_07_03/exports/docs/linux/Overview/Processor_SDK_Linux_create_SD_card.html#create-sd-card-with-default-images-using-script

    Best Regards,
    Sudheer

  • Hi Sudheer,

    I use bmap to create boot SD Card from the official SDK
    https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-j7200/10_00_07_03/exports/docs/linux/Overview/Processor_SDK_Linux_create_SD_card.html#create-sd-card-using-bmap-tools

     

    The packet loss rate is too high in the ping log, and the rx_crc_error count is also too high.

    Tue Nov 26 11:20:01 UTC 2024
    root@j7200-evm:~# ping 192.168.3.128 -I eth0 -i 0.01
    PING 192.168.3.128 (192.168.3.128) from 192.168.3.127 eth0: 56(84) bytes of data.
    64 bytes from 192.168.3.128: icmp_seq=30 ttl=64 time=0.280 ms
    64 bytes from 192.168.3.128: icmp_seq=785 ttl=64 time=0.297 ms
    64 bytes from 192.168.3.128: icmp_seq=1531 ttl=64 time=0.404 ms
    ^C
    --- 192.168.3.128 ping statistics ---
    1601 packets transmitted, 3 received, 99.8126% packet loss, time 25596ms
    rtt min/avg/max/mdev = 0.280/0.327/0.404/0.054 ms
    root@j7200-evm:~# date
    Tue Nov 26 11:20:30 UTC 2024

    root@j7200-evm:~# ethtool -S eth0 | grep crc
         p0_rx_crc_errors: 0
         rx_crc_errors: 34475

    Using a different cable or DUT does not work; the condition remains the same.

    Only rolling back to SDK 9.0 resolves this issue.

  • Sudheer, 

    Will there be any hardware difference or limitation on EVM or daughter card? 

    If it is a connection un-solid case, it should have same result on SDK 9.0.  

    BR, Rich

  • One another check point, is Native Ethernet MAC mode is chosen?

    BR, Rich 

  • Hi,

    Can you please check by using below flow for SD card creation.
    https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-j7200/10_00_07_03/exports/docs/linux/Overview/Processor_SDK_Linux_create_SD_card.html#create-sd-card-with-default-images-using-script

    Use below image (ti-processor-sdk-linux-j7200-evm-<version>-Linux-x86-Install.bin)
    software-dl.ti.com/.../Download_and_Install_the_SDK.html

    Will there be any hardware difference or limitation on EVM or daughter card? 

    If it is a connection un-solid case, it should have same result on SDK 9.0.  

    There is no difference in EVM. If it an H/W Issue we should get same result from 9.0.

    is Native Ethernet MAC mode is chosen?

    Yes, default CPSW2G Driver is Native Ethernet MAC mode.

    Best Regards,
    Sudheer