SPRUII0F May 2019 – June 2024 TMS320F28384D , TMS320F28384D-Q1 , TMS320F28384S , TMS320F28384S-Q1 , TMS320F28386D , TMS320F28386D-Q1 , TMS320F28386S , TMS320F28386S-Q1 , TMS320F28388D , TMS320F28388S
This chapter describes the implementation and integration of the Ethernet for Control Automation Technology (EtherCAT®) Slave Controller (ESC). The ESC peripheral can be mapped to either CM or CPU1 subsystems (default access mapped to CPU1 subsystem), and thus either of these subsystems can run the ESC slave stack and application software to implement an ESC slave node.
On this device, the CPU1 is the master subsystem. If the intention is to use the CM subsystem as the owner of ESC, then certain ESC subsystem configurations can only be done by the CPU1 during initialization before allocating the ownership of the ESC to the CM subsystem. These details are explained in this chapter.
Information about the EtherCAT standards and working principles can be in found these documents:
Refer to Section 31.1.11 for details on EtherCAT IP errata provided from Beckhoff ® Automation.