Understanding TRAP Errors
A TRAP occurs due to various events, including Non-Maskable Interrupts (NMIs), instruction exceptions, memory management exceptions, or illegal access. These traps are always active and cannot be disabled by software. The TriCore™ architecture defines eight general classes for traps, each with a dedicated trap handler and distinguished by a Trap Identification Number (TIN).
Traps can be categorized as synchronous or asynchronous, and as hardware or software generated. This training material explores three key combinations: synchronous and hardware generated, asynchronous and hardware generated, and synchronous and software generated.
Hardware Setup and Implementation
The provided code examples are developed for the KIT_AURIX_TC397_TFT board. The document details the implementation of trap provocation and handling, including specific functions and variables used for triggering and analyzing TRAP events.
Key registers such as DEADD, DATR, and DSTR are discussed for their role in providing additional debug information. The guide also explains how to use the debugger to observe trap behavior, including call stacks and disassembly views.
Key Resources
For further details and resources, please refer to:
- AURIX™ Development Studio
- AURIX Code Examples GIT Repository
- Infineon AURIX Expert Training
- AURIX™ Forum
For any questions regarding this document, please contact erratum@infineon.com.