• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 31 subscribers
  • Views 496 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

MCU-PLUS-SDK-AM243X: EtherCAT Support for DP83826E

Andrew Kirby1
Prodigy 230 points
Part Number: MCU-PLUS-SDK-AM243X
Other Parts Discussed in Thread: DP83826E, SYSCONFIG, DP83869

DP83826E was recommended to us by TI for an EtherCat application.

Standard SDK supports DP83869: only this device is selectable in SysConfig.

We hoped that the ethphy_dp83826e.c and ethphy_dp83826e.h that are included in the SDK in .../source/board/ethphy would be selectable. They're not.

Q1: We were led to believe that there would be proper support. When will DP83826E be properly supported in the SDK?

Q2: For now, we can select "CUSTOM" in Sysconfig but it is unclear what the next steps are... can you elaborate?

EtherCAT code in tiescoc.c and .h appears to have hard coded references to the DP38369 (eg: tiesc_ethphyInit(...)) These are part of the EtherCAT SDK code, so would not be changed by changing the PHY setting in Sysconfig.  We don't really want to branch and modify the SDK as that will make a maintenance headache for us going forwards as you release new versions.

Q3: Is there a properly supported EtherCAT/DP83826E solution?

Q4: What is the recommended route to implementing support for DP83826E without having to branch/change/maintain the SDK?

Many Thanks

Andrew Kirby

  • 0
    TI__Mastermind 36293 points

    Hi Andrew,

    we have started looking into the issue. We will get back by Wednesday next week latest. Appreciate your patience.

  • 0 in reply to Nilabh Anand
    Prodigy 230 points

    I think we are largely there with something hacked together - it would be interesting to know how it is intended to be done properly - the dp83826e files need to be manually added to the project...

    The biggest hurdle was that when you pull the config lines high and low during reset to set the address on the dp83826e it also has a side affect of configuring the pins as active high/low. Therefore the output that is used to indicate the link state is a different polarity depending on the Phy address set during reset. There appears to be provision for this in the ESC code because you can set the link status polarity on a per channel basis. 

    Still in the throes of testing, but I remain interested to hear the official solution of the best way to integrate this device.

  • 0 in reply to Andrew Kirby1
    TI__Mastermind 36293 points

    Hi Andrew,

    We have been able to add integrate the phy to our ethercat example. I am facing some issue on link side. I will try to share the project by next week.

  • 0 in reply to Nilabh Anand
    Prodigy 230 points

    Thanks for the update. What hardware platform are you using for testing? Would like to compare circuits and see the similarities and differences.

  • 0 in reply to Andrew Kirby1
    TI__Mastermind 36293 points

    Hi Andrew,

    I am using AM243-evm.And using beckoff based example to test it.