3.6. Setting tracepoints on exception vectors
If you want to trace an exception vector, such as Data Abort,
you must disable the vector catch for that exception before running
the image. This prevents the exception being caught, and the exception
can be recorded in the trace buffer. If the core is tracing and an
exception occurs, the analysis window displays the text in Table 3.1 as appropriate.
Table 3.1. Text recorded in trace buffer for exceptions
| Exception | Text recorded |
|---|
| Reset | RESET |
| Undefined instruction | UNDEF EXCEPTION |
| Supervisor Call (SVC) interrupt | Branch to <SVC> |
| Prefetch Abort (instruction memory read abort) | PREFETCH ABORT |
| Data Abort (data memory read or write abort) | DATA ABORT |
| IRQ (normal interrupt) | INTERRUPTED |
| FIR (fast interrupt) | FAST INTERRUPT |
| Secure Monitor Call (SMC)[1] | SECURE MONITOR CALL |
You can configure vector catching using one of the following
methods:
Configure the connection settings
in the Vectors group of the Advanced_Information block
for the connection. This method persists between debugging sessions.
Select Processor Exceptions... from
the Code window Debug menu to configure the
processor exceptions. The changes are lost when you disconnect.
PDF version