2.3.2. Exception types

The exception types are:


Reset is invoked on power up or a warm reset. The exception model treats reset as a special form of exception. It is permanently enabled and has a fixed priority of -3. When reset is asserted, the operation of the processor stops, potentially at any point in an instruction. When reset is deasserted, execution restarts from the address provided by the reset entry in the vector table. Execution restarts as privileged execution in Thread mode.


A non-maskable interrupt is signaled by a peripheral or triggered by software. This is the highest priority exception other than reset. It is permanently enabled and has a fixed priority of -2. NMIs cannot be:

  • Masked or prevented from activation by any other exception.

  • Preempted by any exception other than Reset.


A HardFault is an exception that occurs because of an error during exception processing, or because an exception cannot be managed by any other exception mechanism. HardFaults have a fixed priority of -1, meaning they have higher priority than any exception with configurable priority.


A MemManage fault is an exception that occurs because of a memory protection related fault. The fixed memory protection constraints, or the MPU if implemented, determines this fault, for both instruction and data memory transactions. This fault is always used to abort instruction accesses to Execute Never (XN) memory regions.


A BusFault is an exception that occurs because of a memory related fault for an instruction or data memory transaction. This might be from an error detected on a bus in the memory system.


A UsageFault is an exception that occurs because of a fault related to instruction execution. This includes:

  • An undefined instruction.

  • An illegal unaligned access.

  • Invalid state on instruction execution.

  • An error on exception return.

The following can cause a UsageFault when the core is configured to report them:

  • An unaligned address on word and halfword memory access.

  • Division by zero.


A supervisor call (SVC) is an exception triggered by the SVC instruction. In an OS environment, applications can use SVC instructions to access OS kernel functions and device drivers.


PendSV is an interrupt-driven request for system-level service. In an OS environment, use PendSV for context switching when no other exception is active.


A SysTick exception is an exception the system timer generates when it reaches zero. Software can also generate a SysTick exception. In an OS environment, the processor can use this exception as system tick.

Interrupt (IRQ)

A interrupt, or IRQ, is an exception signaled by a peripheral, or generated by a software request. All interrupts are asynchronous to instruction execution. In the system, peripherals use interrupts to communicate with the processor.

Table 2.14. Properties of the different exception types

Exception number [a]

IRQ number [a]Exception typePriorityVector address or offset [b]Activation

-3, the highest



4 -12


Configurable [c]


Configurable [c]

0x00000014Synchronous when precise, asynchronous when imprecise

Configurable [c]


Configurable [c]


Configurable [c]



Configurable [c]

0x0000003C Asynchronous
16 and above[d]0 and above[e]

Interrupt (IRQ)

Configurable [f]

0x00000040 and above [g]Asynchronous

[a] To simplify the software layer, the CMSIS only uses IRQ numbers and therefore uses negative values for exceptions other than interrupts. The IPSR returns the Exception number, see Interrupt Program Status Register.

[b] See Vector table for more information.

[d] The exception number range is implementation defined.

[e] The IRQ number range is implementation defined.

[g] Increasing in steps of 4. The vector address or offset range is implementation defined.

For an asynchronous exception, other than reset, the processor can execute another instruction between when the exception is triggered and when the processor enters the exception handler.

Privileged software can disable the exceptions that Table 2.14 shows as having configurable priority, see:

For more information about HardFaults, MemManage faults, BusFaults, and UsageFaults, see Fault handling.

Copyright © 2015, 2018 Arm. All rights reserved.ARM DUI 0646C