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.2 Error Logging

The EAM module provides comprehensive error logging capabilities needed for user to debug the source of all critical errors in the device.

All errors are logged in EAM registers with the following information:
  1. Error Type – Multibit value that maps to specific error type (for example Access acknowledge error, Uncorrectable error etc.). The value is pre-defined for each type, for example – 0x20 for Access ACK error on CPU PR error as shown in the table in Error Aggregation section above.
  2. Error Address – System Address at which the error occurred used to debug the error origin. There are separate high priority and low priority error address registers.
  3. Program Counter (Applicable only for CPU EAM modules) – Program counter address captured helps identify the source of error. The PC address is particularly useful to identify code corresponding to the program counter address that respective CPU was executing which caused the error.