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.

AM2432: Ethercat Link Status

Part Number: AM2432

Tool/software:

Hi TI Experts,

Customer has a strange AM243 board that the Ethercat link status read out from the PHY (DP83822, addr: 0x0019) is different with the actual status.(all other boards are normal) For example, if the Ethercat is working normally, the PHY link status result shows the status is not linked. Customer wants to know if there is a register at AM24 side that could also shows the status of the Ethercat link?

Could you please help check if our AM24 side also has this register that could show the Ethercat link status?

Thanks,

Kevin

  • Hi Kevin,

    Customer has a strange AM243 board that the Ethercat link status read out from the PHY (DP83822, addr: 0x0019) is different with the actual status.(all other boards are normal)
    • So just to clarify myself, all the boards in the network are loaded with the same EtherCAT application and one of the board’s PHY link status register is not getting updated for an active link ?

    Could you please help check if our AM24 side also has this register that could show the Ethercat link status?

    • You can monitor the MDIO_LINK_REG register (0x300B240C) to see if the link status is getting updated. For more details on this, you can refer to section 6.4.14.10.4 of the Technical Reference Manual for AM243x/AM64x.

    Regards,
    Aarob

  • read out from the PHY (DP83822, addr: 0x0019) i

    Can you share the value of 0x0019 and other PHY registers (0 to 0x1F) in working vs non-working scenario

  • Hi Aaron, Pratheesh,

    Thanks for your support. Customer finally solved this problem by directly reading the registers with MDIO and then to judge the link status. This method does not meet the above problem anymore. Previously customer used phy link status detect function provided in the SDK and have this problem. Customer is also okay with this workaround, so closing this issue now.

    Thanks,

    Kevin