SLAU846B June 2023 – November 2024 MSPM0G1105 , MSPM0G1106 , MSPM0G1107 , MSPM0G1505 , MSPM0G1506 , MSPM0G1507 , MSPM0G1519 , MSPM0G3105 , MSPM0G3105-Q1 , MSPM0G3106 , MSPM0G3106-Q1 , MSPM0G3107 , MSPM0G3107-Q1 , MSPM0G3505 , MSPM0G3505-Q1 , MSPM0G3506 , MSPM0G3506-Q1 , MSPM0G3507 , MSPM0G3507-Q1 , MSPM0G3519
The AES module contains three event publishers and no event subscribers. One event publisher (CPU_INT) manages AES interrupt requests (IRQs) to the CPU subsystem through a static event route. The second, and third event publishers (DMA_TRIG_DATAIN, and DMA_TRIG_DATAOUT) can be used to publish AES events to the DMA through DMA event routes.
The AES events are summarized in Table 28-194.
Event | Type | Source | Destination | Route | Configuration | Functionality |
---|---|---|---|---|---|---|
CPU Interrupt Event | Publisher | AES | CPU Subsystem | Static route | CPU_INT registers | Fixed interrupt route from RTC to CPU |
DMA Trigger Event 0 | Publisher | AES | DMA | DMA route | DMA_TRIG 0 registers | DMA trigger 0: Data Input into engine |
DMA Trigger Event 1 | Publisher | AES | DMA | DMA route | DMA_TRIG 1 registers | DMA trigger 1: Data Output from engine |
In general, the CPU interrupt event is used to communicate completion of an AES operation to the CPU, and the DMA triggers are used together to implement the block cipher modes (ECB, CBC, OFB, CFB, GCM/GMAC, CCM/CMAC) using the DMA together with the AES accelerator.