SDAA104 September   2025 F29H850TU , F29H859TU-Q1

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1Introduction
  5. 2Error Handling Architecture Overview
  6. 3Example Overview
  7. 4Error Aggregator Overview
    1. 4.1 Error Aggregation
    2. 4.2 Error Logging
    3. 4.3 Error Debugging Using EAM Module
      1. 4.3.1 EAM Error Debugging
      2. 4.3.2 Interpreting Error Address and Program Counter Values
  8. 5Error Signaling Module Overview
    1. 5.1 ESM Error Event Output Configuration and Status Information
      1. 5.1.1 Sysconfig ESM Configuration
    2. 5.2 ESM Error Events Debugging
    3. 5.3 Miscellaneous Debug Tips for ESM
  9. 6BootROM EAM and ESM Error Status
  10. 7FAQ's:
  11. 8Summary
  12. 9References

4.3 Error Debugging Using EAM Module

To make error debugging easier, error handling functions are integrated in the Code Composer Studio (CCS) as shown in Figure 4-2.

Using CCS Scripts Menu, user can find the error status captured. All the below steps mentioned below for error debug are done with the Error_Agg_Check_Status() hotmenu function in the GEL file executable from the Scripts Menu as shown in the image Figure 4-2.

Error Aggregator GEL File Function Figure 4-2 Error Aggregator GEL File Function
  1. Check the error type register value for each EAM module (CPU PR/DR1/DR2/DW, RTDMA, SSU, CPU INT, Ethercat) if this has value other than 0x0 to identify if any error has occurred or not.
  2. If particular EAM module error type register has a value other than 0x0 then find the corresponding error aggregator low priority error address for low priority error and high priority error address for high priority error.
  3. If particular EAM module error type register has a value other than 0x0 then find the error aggregator program counter address – only in case of CPU EAM modules.