 Hello, and welcome to this presentation of the STM32 nested vector interrupt controller. We will be presenting the features of this controller. The nested vector interrupt controller embedded inside of the STM32MP1 series microprocessor provides up to 150 interrupt channels served with low latency. One of 16 priorities can be assigned to each interrupt source. Interrupt levels can benefit from dynamic prioritization of the interrupt levels, fast response to the requests thanks to low latency response and tail chaining, and also from vector table relocation. The nested vector interrupt controller provides a fast response to interrupt requests, allowing an application to quickly serve incoming events. Most of the peripherals have a unique interrupt vector, making development of the application easier, with less need to programmatically determine the source of an interrupt during processing. The interrupt vector table can also be relocated, which allows the system designer to adapt the placement of the interrupt service routines to the application's memory layout. The nested vector interrupt controller provides several features for efficient handling of exceptions. When an interrupt is served and a new request with higher priority arrives, the new exception can preempt the current one. This is called nested exception handling. The previous exception handler resumes execution after the higher priority exception is handled. When an interrupt request with lower or equal priority is raised during execution of an interrupt handler, it becomes pending. Once the current interrupt handler is finished, the context saving and restoring process is skipped and control is transferred directly to the new exception handler to decrease interrupt latency. When an interrupt arrives, the processor first saves the program context before executing the interrupt handler. If the processor is performing this context saving operation when an interrupt of higher priority arrives, the processor switches directly to handling the higher priority interrupt when it is finished saving the program context. Then tail chaining is used prior to executing the IRQB interrupt service routine. When all of the exception handlers have been run and no other exception is pending, the processor restores the previous context from the stack and returns to normal application execution. When accessing the nested vector interrupt controller registers, ensure that your code uses a correctly aligned register access. Unaligned access is not supported for nested vector interrupt controller registers as well as all memory mapped registers located in the Cortex-M4. An interrupt becomes pending when the source asks for service. Disabling the interrupt only prevents the processor from taking that interrupt. Make sure the related interrupt flag is cleared before enabling the interrupt vector. Before relocating the vector table using the VTOR register, ensure that fault handlers, NMI and all enabled interrupts are correctly set up on the new location. For detailed information, please refer mainly to Programming Manual PM0214.