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

2 Error Handling Architecture Overview

The Figure 2-1 shows at a high level how the error handling is done. Error is detected at source which can be a peripheral, module, memory, interconnect or processing unit and this propagates to EAM for error aggregation and then passed on to ESM for user configurable error response within the device. Critical device error events that need error aggregation and logging go through EAM whereas all other device error events are passed on directly from the error source to ESM and are listed in the Error Events table in the ESM Chapter in F29x Technical Reference Manual.

Device Error Handling Architecture Figure 2-1 Device Error Handling Architecture