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.

DP83869HM: Ethernet communication issue during transmission and reception

Part Number: DP83869HM
Other Parts Discussed in Thread: AM2634, , LP-AM263, DP83869

Tool/software:

While trying to interface DP83869HM with AM2634 we are facing issue with ping transmit and receiving. We have designed our own IoT device with this chipset, considered reference from AM2634 Evaluation board.

We have considered example of "enet_cpsw_rawhttpserver_am263x-lp_r5fss0-0_nortos_ti-arm-clang" and provided static IP as "192.168.8.200" for device and "192.168.8.100" for PC connected directly via Ethernet CAT 6 cable. While trying to check Ping via command prompt, it showing as "Request timed Out". But in Wireshark, both Ping request and reply has been received but the response has been corrupted as below image.

    

We have tried same example with LP-AM263 launch pad, it is working fine without any corrupted data. Can you please check and let us know, how to resolve this issue ?

If you require any additional details or documents let us know

  • Hi,

    I want to make sure I am understanding your setup correctly. Do correct me if my understanding is wrong

    You are using the AM2634 IC in your own design, referencing one of the evaluation boards for your design. Is this referring to the LP-AM263 board or one of the other evaluation boards listed on the AM2634 product page? Additionally, the DP83869HM is a part of this board design, interfacing directly with the AM2634 on the same board. Using this board, you are trying to ping it from the PC side after establishing a successful link between the two. This pinging operation returns as timed out, but wireshark logs show that the response is corrupted. However, the same code example works on the evaluation board LP-AM263. 

    Would it be possible for you to provide a schematic of your DP83869HM design? I want to rule out hardware as a potential cause. You can use the schematic checklist attached below to verify your design as well. 

    3782.DP83869_Schematic_Checklist (public).xlsx

    Another debug step we can take is to enable the reverse loopback function of the DP83869 PHY. This would help us validate if the data corruption is happening in the PHY or the AM2634. This can be done using bits [5:2] of register 0x16. We can then send out packets from the PC, which should then be routed back to the PC through this loopback. Then we can check the wireshark logs to see if the received data is identical to the transmitted or if it is corrupted.

    Best,

    Vivaan