SPRADJ8 October   2024 AM3351 , AM3352 , AM3354 , AM3356 , AM3357 , AM3358 , AM3359 , AM4372 , AM4376 , AM4377 , AM4378 , AM4379 , AM620-Q1 , AM623 , AM625 , AM625-Q1 , AM62A3 , AM62A3-Q1 , AM62A7 , AM62A7-Q1 , AM62P , AM6411 , AM6412 , AM6421 , AM6422 , AM6441 , AM6442 , DP83822H , DP83822HF , DP83822I , DP83822IF , DP83826E , DP83826I , DP83848-EP , DP83848Q-Q1 , DP83867CR , DP83867CS , DP83867E , DP83867IR , DP83867IS , DP83TC812R-Q1 , DP83TC812S-Q1 , DP83TC813R-Q1 , DP83TC813S-Q1 , DP83TC814R-Q1 , DP83TC814S-Q1 , DP83TG720R-Q1 , DP83TG720S-Q1 , DP83TG721R-Q1 , DP83TG721S-Q1

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. Terminology
  5. Prerequisites
  6. Quick Initial Steps
  7. Debug Overview
  8. Network Driver Initialization Process
  9. Ethernet PHY Analysis
  10. Ethernet MAC Statistics Analysis
  11. How IPv4 Address is Obtained
  12. Follow the Packet
  13. 10Debug Network Topologies and Techniques
    1. 10.1 Direct Connection
    2. 10.2 Static IP Addresses
    3. 10.3 Setting Low Bit Rates
    4. 10.4 Beware When Connecting to a Switch
  14. 11Linux® Utilities Summary
  15. 12Checklist for Requesting Ethernet Support

Beware When Connecting to a Switch

Do not connect both Ethernet interfaces on a dual port board, such as a TI EVM into the same switch or router. This does not provide a redundant link. Each Ethernet interface must have an exclusive subnet.

To explain why this network topology fails, assume two interfaces on the DUT are named eth0 and eth1 and are both connected to the same switch. When a ping command (issuing an ICMP request) is initiated from eth1 (ping <Ipv4 address> -I eth1), the packet that is sent out by the DUT is received by the destination platform. To respond to the ping request, the destination platform must perform an Address Resolution Protocol (ARP) sequence to get the MAC address of the source platform that made the ping request. This ARP sequence is called an ARP request message.

Since the ARP packet is a broadcast message, eth0 of the source platform responds with the MAC address, which is incorrect for eth1.

If the ARP broadcast returned the wrong MAC address for eth1, every ping reply from the destination platform has the incorrect destination MAC address. Therefore, eth0 is receiving all the responses instead of eth1. If Wireshark is used to view the packet traffic, it looks like every ping request has a matching ping reply except that none of the response packets are received by eth1, causing a ping failure.

For example, in Figure 10-2, the highlighted ping reply is to a destination MAC address of d4:f5:13:87:0b:8c, which is the MAC address associated with eth0.

AM62x, AM64x, AM62Ax, AM62P Wireshark Ping
                    Messages Figure 10-2 Wireshark Ping Messages