SPRUJF2A March 2026 – March 2026 AM13E23019
The AESADV module provides four interrupt sources which can be configured to source a CPU interrupt event. The CPU interrupt events from the AES are given inTable 33-279 .
| Index (IIDX) | Name | Description |
|---|---|---|
| 0 | NO_INTR | No interrupt pending. |
| 1 | OUTPUTRDY | This indicates that the engine has an output available to be read out. This should not be used if DMA handshake is used (AES_DMA_HS.DMA_DATA_ACK set to 1) |
| 2 | INPUTRDY | This indicates that the engine can take new input. This should not be used if DMA handshake is used (AES_DMA_HS.DMA_DATA_ACK set to 1) |
| 3 | SAVEDCNTXTRDY | This bit indicates that an AES authentication TAG and/or IV block(s) is/are available for the CPU to retrieve. This bit is only asserted if the ‘save_context’ bit is set to ‘1b’. The bit is mutually exclusive with the ‘context_ready’ bit. |
4 | CNTXTRDY | This bit indicates that the context data registers can be overwritten, and the CPU is permitted to write new context. |
The CPU interrupt event configuration is managed with the event management registers. See Using Event Registers for guidance on configuring these registers for CPU interrupts.