Timestamping allows the local application or
remote EtherCAT master to measure the time
events and plan the subsequent controls.
Timestamping: Device Internal Events
- Enable timestamping and logging of internal device events coming from control logic
- The same outputs of the EPWM crossbar that connect to the 8 EPWMs can be used as 8 input signals (PWMXBAROUT0-PWMXBAROUT7) for time stamping
- Note that there is no independent option for Latch muxing as far as EPWM cross-bar inputs are concerned; unless one of the TRIP outputs are not used in control loop and such a crossbar output is dedicated for LATCH0/1 toggle
Timestamping: External Events
- Enable external board components apart from the MCU to trigger timestamp capture
- For example, timestamp a periodic event or pulse/edge event from a senor when the sensor data is read or accessed
- Connecting the LATCH0/1 controls through the input crossbar allows timestamp capture based on any selected GPIO toggle (such as GPTRIP15 or GPTRIP16)
- Two GPTRIPs are provided for independent GPIO choice for LATCH0 and LATCH1
- GPTRIP1, 2, and 3 allow the same functionality;
however, those can be utilized for EPWM trip zone functions where pins
can or cannot need to match. In the case of a trip zone based on GPTRIP
is to be latched, one of these inputs can be used.
Timestamping: Device Exception Events
- Log and timestamp exception events within the
device (example: NMI exceptions) and periodically collect information to find
out systemic issues in the system
- Can be used by local application and the remote
master device to diagnose or
debug the system
- On CPU1, ERAD can be used to analyze particular
accesses or data patterns/counts on the CPU bus. Refer to the Embedded
Real-time Analysis and Diagnostic (ERAD) chapter for further
information