There are two aspects of the EtherCAT IP operation that need to be considered from a debug emulation stand point.
- Debugger Writes/Reads of EtherCAT IP registers/memories Condition: The EtherCAT IP does not have any mechanism to identify a debug initiated read/write. Debug accesses to the registers or the ESC RAM can affect the state of the EtherCAT IP. This is addressed by the following:
- CPU1/CPU2/CPU3: The ENABLE_DEBUG_ACCESS
bit must be set in the ESCSS Access Control Register to enable user
access to the ESC RAM and EtherCAT registers for the purpose of debug.
By default, this is disabled.