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
When the DAC trigger is captured by DMA and trigger acknowledgment has been provided, both the DAC and the DMA are in triggered state. In this state, the DAC must not generate any new DMA trigger. When DMA starts to service the DAC, the DMA can perform data transfers to the actual value indicated by the trigger count or to a value less than the trigger count (it can be even no transfer). This is not deterministic and depends on factors like DMA bandwidth and channel priorities.
When the DMA performs a certain number of transfers, it asserts a DMA done signal DONE_REQ to the DAC along with the DMA status side band signal DONE_STATUS. The DAC module provides a DMA done acknowledgment DONE_ACK as a response. The DMA done event and DONE_ACK are routed through the event fabric and follow the standard 4-way request, acknowledge handshake protocol.