SPRUJ28E November 2021 – September 2024 AM68 , AM68A , TDA4AL-Q1 , TDA4VE-Q1 , TDA4VL-Q1
The DRU generates the following events:
The EVENT_SIZE field of each TR specifies how often a TR generates an output event. That event is provided on the local output event interface as shown in Figure 10-50 and as global event on the PSI-L interface. There is one event per channel. The global event number used by a PSI-L event transport lane can be configured for each channel through the DRU_CHOES0_j[15-0] EVT_NUM field.
As shown in Table 10-221, if the EVENT_SIZE value is in range from 1 to 3, then the output event is generated when the write command for the given loop level (ICNT1, ICNT2 or ICNT3 decremented) has been sent. If EVENT_SIZE = 0, then the output event is generated when all responses have been received.
EVENT_SIZE Value | Event Encoding | Description |
---|---|---|
0 | TR complete | The TR has completed and all responses have been received |
1 | ICNT1 loop is decremented | The last write command of a row has been sent |
2 | ICNT2 loop is decremented | The last write command of an array has been sent |
3 | ICNT3 loop is decremented | The last write command of an array of an array has been sent |
For more information about PSI-L interface and its event transport lane, see PSI-L.
For more information about the TR EVENT_SIZE field, see Transfer Request Record of DMA Architecture.
The protocol violation event is not channel associated.
The completion events are defined for each channel. The completion event fires whenever a channel completes a TR successfully. It is only generated when all responses are received from the write portion of the block copy. A single write completion event can occur in a given cycle since it is based on the write responses being received to generate the response.
The error completion events are defined for each channel. The error completion event fires whenever a channel completes a TR with an error and it has flushed out all data related to that TR in the response buffer. Upon determining that a TR is not able to complete successfully, the DRU enters a flush mode to remove all read data received after the error is determined as well as make sure all write responses are received. Once all of this criteria has been matched the write engine fires a completion event. If multiple error completions occur at the same time the DRU will still send them out one at a time using an arbitration scheme used for the original arbitration for the queue, either fixed priority or round robin based on the queue that has the error.