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.

TMS320F28P650DK: Flaky PHY connections for ethercat communication

Part Number: TMS320F28P650DK
Other Parts Discussed in Thread: C2000WARE

Tool/software:

I am running an example ethercat project from the C2000ware SDK f28p65x_cpu1_echoback_solution on F28P65x controlCARD TMDSCNCD28P65X Evaluation board | TI.com. My setup is ~30 controlCARDs running this example code being driven by either an ethercat master (EC-Engineer/TwinCAT/embedded solution). Regardless of the master in this scenario, when I scan the network, I will discover 0 slaves unless I go through a particular sequence of unplugging and re-plugging port1 and/or power cycle the slave board. I have to do this one-by-one, where a network scan results in 1, 2 , 3, ...,  eventually all the slaves on the bus are discovered. 

The way to recreate the problem is to power cycle the slave boards and try again to scan the network. that is to say, all the slave boards are powered by the same usb power bank. If I turn this power bank off then on again, with all the slave boards powering up at once, and they are all connected for communication in a daisy chain or line as is typical for ethercat, I will no longer be able to discover the slaves on the network. The only way to scan successfully is in the sequence described above: un-plug/re-plug network cable on port1, reset, scan again, one board at a time. 

Why? Is the PHY being mismanaged? Is the ESC peripheral being mismanaged? Is there something wrong at the hardware level? Hoping someone else out there has experienced the same issue, understands the root cause, and has a viable solution.  

P.S. - I have the same exact issue on the launchpad version of this same eval board LAUNCHXL-F28P65X Evaluation board | TI.com

  • Hi Zachary,

    You're running standalone from Flash I assume? By power cycling the board are you unplugging and re-plugging the USB power or just pressing the reset button on the board?

    I'm curious if it's an issue with the power sequencing / supply ramp speed not being fast enough. Have you tried with different kinds of USB power supplies? Like some USB-C Power Delivery charger may have a different behavior.

    Best,

    Kevin