SPRUJ28E November 2021 – September 2024 AM68 , AM68A , TDA4AL-Q1 , TDA4VE-Q1 , TDA4VL-Q1
Table 10-50 expands the 32-bit FLAGS field. The numbers above each field here indicate bit numbers within the field.
31 | 24 | 23 | 16 | ||||||||||||
CONFIGURATION SPECIFIC FLAGS | CMD ID | ||||||||||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 0 | ||
TRIGGER1_TYPE | TRIGGER1 | TRIGGER0_TYPE | TRIGGER0 | EVENT_SIZE | WAIT | STATIC | TYPE |
The flags field fills in the remaining details about the stream, as follows:
Bit | Field | Description |
---|---|---|
0-3 | TYPE | The TYPE of TR that is being sent
0: One dimensional data move 1: Two dimensional data move 2: Three dimensional data move 3: Four dimensional data move 4: Four dimensional data move with data formatting 5: Four dimensional Cache Warm 6-7: Reserved 8: Four Dimensional Block Move 9: Four Dimensional Block Move with Repacking 10: Two Dimensional Block Move 11: Two Dimensional Block Move with Repacking 12-14: Reserved 15: Four Dimensional Block Move with Repacking and Indirection |
4 | STATIC | This field is only valid on Type 8 and type 9 TRs The TR is static and will continually reload into the channel upon completion of the TR until a channel tear down. |
5 | WAIT | This field is only valid on Type 15 TRs.
This field indicates whether or not this TR should ensure it completes before allowing the next TR to start on this channel. The encoding is as follows: 0 = Allow next TR to start immediately 1 = Wait for this TR to complete before allowing next TR to start When set, the next TR will not be considered triggered (regardless of any other trigger conditions) until all write status responses for the current TR have landed. |
6-7 | EVENT_SIZE | This is how often the TR will generate an output event.
0: Event is only generated with the TR is complete 1: Event is generated when the second inner most loop (ICNT1) is decremented by 1. 2: Event is generated when the third inner most loop (ICNT2) is decremented by 1. 3: Event is generated when the outer most loop (ICNT3) is decremented by 1. |
8-9 | TRIGGER0 | This is one of two selectable triggers. The receipt of this trigger will enable the TR to be active for enough data transfer as specified by the TRIGGER0_TYPE Field.
0: No Trigger 1: Global Trigger 0 for the channel 2: Global Trigger 1 for the channel 3: Local Event for the channel |
10-11 | TRIGGER0_TYPE | This is the type of data transfer that will be enabled by receiving a trigger.
0: The second inner most loop (ICNT1) will be decremented by 1. 1: The third inner most loop (ICNT2) will be decremented by 1. 2: The outer most loop (ICNT3) will be decremented by 1. 3: The entire TR will be allowed to complete. |
12-13 | TRIGGER1 | This is one of two selectable triggers. The receipt of this trigger will enable the TR to be active for enough data transfer as specified by the TRIGGER1_TYPE Field.
0: No Trigger 1: Global Trigger 0 for the channel 2: Global Trigger 1 for the channel 3: Local Event for the channel This field is reserved for a Direct TR. |
14-15 | TRIGGER1_TYPE | This is the type of data transfer that will be enabled by receiving a trigger.
0: The second inner most loop (ICNT1) will be decremented by 1. 1: The third inner most loop (ICNT2) will be decremented by 1. 2: The outer most loop (ICNT3) will be decremented by 1. 3: The entire TR will be allowed to complete. |
16-23 | CMD ID | The Command ID for the TR. This will be sent back with the response for the Channel controller to identify the specific TR. For a Direct TR this is the event number that will be generated based on the event trigger. |
24-31 | Configuration Specific Flags | These are flag bits that can be specified by the specific UTC configuration. These bits will remain undefined in the global TR format to allow for customization requirements that might be required in the specific UTC implementation. |
The following sections expand on each of these fields.