SPRUJ79 November 2024 F29H850TU , F29H859TU-Q1
Table 19-37 lists the memory-mapped registers for the WADI_OPER_SSS_REGS registers. All register offset addresses not listed in Table 19-37 should be considered as reserved locations and the register contents should not be modified.
| Offset | Acronym | Register Name | Protection |
|---|---|---|---|
| 0h | BASETIMERLOW | Read only value for lower word of the base timer. | PARITY_PROTECTED |
| 4h | BASETIMERHIGH | Upper word of the base timer and trigger to start the timer. | |
| 8h | INTSTS | Gives the block wise aggregated raw error status that shall trigger the interrupt. | |
| Ch | INTSTSMASK | Provides mask for application to suppress or allow a particular block related errors to cause interrupt or not | |
| 10h | BLKSMASKSTS | This is AND combination of active high indication of block-wise status asserting an interrupt. | |
| 14h | INTSTSCLR | Provides way for application to clear the interrupt status. | |
| 18h | INTSTSFRC | Allows emulation of the RIS to raise interrupt in software | |
| 1Ch | SIGSYNCFILTCFG | Each input SIG to be connected through synchroniser or not | PARITY_PROTECTED |
| 20h | TRIGSYNCFILTCFG | Each trigger to be connected through synchroniser or not | |
| 3Ch | REVISION | IP Revision | |
| 40h | DMATRIGSTS | Status of the DMA triggers active | |
| 44h | DMATRIGEN | Mask to enable individual trigger cause | PARITY_PROTECTED |
| 48h | DMASTSUPDATE | Indicates the register set updated post DMA write | |
| 4Ch | DMAFILTWRCFG | DMA writes Filter enable for each of WADI & SSS blocks | PARITY_PROTECTED |
| A4h | CFGREGLOCK | Configuration Register Lock | |
| A8h | CFGREGCOMMIT | Configuration Register Commit | |
| ACh | OPERREGLOCK | Operating Register Lock | |
| B0h | OPERREGCOMMIT | Operating Register Commit | |
| B8h | SSS_EVTTRIG | Event trigger word output by WADI instance for SSS | PARITY_PROTECTED |
| BCh | SSS_OUTEVTSTS | Status of the active event | |
| C0h | SSS_BLK1_2OUTSEL | Mux select word for outputs 0-3 | PARITY_PROTECTED |
| C4h | SSS_BLK3_4OUTSEL | Mux select word for outputs 4-7 | PARITY_PROTECTED |
| E0h | SSS_OUTEVT1LINKCFG | Output event1 Link configuration | PARITY_PROTECTED |
| E4h | SSS_OUTEVT2LINKCFG | Output event2 link configuration | PARITY_PROTECTED |
| E8h | SSS_OUTEVT3LINKCFG | Output event3 link configuration | PARITY_PROTECTED |
| ECh | SSS_OUTEVT4LINKCFG | Output event4 link configuration | PARITY_PROTECTED |
| F0h | SSS_OUTEVT5LINKCFG | Output event5 link configuration | PARITY_PROTECTED |
| F4h | SSS_OUTEVT6LINKCFG | Output event6 link configuration | PARITY_PROTECTED |
| F8h | SSS_OUTEVT7LINKCFG | Output event7 link configuration | PARITY_PROTECTED |
| FCh | SSS_OUTEVT8LINKCFG | Output event8 link configuration | PARITY_PROTECTED |
| 100h | SSS_EVT1CFG | Event1 that compares to trigger word SSS_EVTTRIG | PARITY_PROTECTED |
| 104h | SSS_EVT2CFG | Event2 that compares to trigger word SSS_EVTTRIG | PARITY_PROTECTED |
| 108h | SSS_EVT3CFG | Event3 that compares to trigger word SSS_EVTTRIG | PARITY_PROTECTED |
| 10Ch | SSS_EVT4CFG | Event4 that compares to trigger word SSS_EVTTRIG | PARITY_PROTECTED |
| 110h | SSS_TRIGEVT1_4CFG | Configuration for using trigger word in specific manner | PARITY_PROTECTED |
| 180h | SSS_BLKSOUTEVT1CFG | Output event1 to be applied for output | PARITY_PROTECTED |
| 184h | SSS_BLKSOUTEVT2CFG | Output event2 to be applied for output | PARITY_PROTECTED |
| 188h | SSS_BLKSOUTEVT3CFG | Output event3 to be applied for output | PARITY_PROTECTED |
| 18Ch | SSS_BLKSOUTEVT4CFG | Output event4 to be applied for output | PARITY_PROTECTED |
| 190h | SSS_OUTEVT1TRIGCFG | Output event1 configuration for triggers, link | PARITY_PROTECTED |
| 194h | SSS_OUTEVT2TRIGCFG | Output event2 configuration for triggers, link | PARITY_PROTECTED |
| 198h | SSS_OUTEVT3TRIGCFG | Output event3 configuration for triggers, link | PARITY_PROTECTED |
| 19Ch | SSS_OUTEVT4TRIGCFG | Output event4 configuration for triggers, link | PARITY_PROTECTED |
| 1A0h | SSS_OUTEVT1DUR | Output event1 configuration of delays | PARITY_PROTECTED |
| 1A4h | SSS_OUTEVT2DUR | Output event2 configuration of delays | PARITY_PROTECTED |
| 1A8h | SSS_OUTEVT3DUR | Output event3 configuration of delays | PARITY_PROTECTED |
| 1ACh | SSS_OUTEVT4DUR | Output event4 configuration of delays | PARITY_PROTECTED |
| 200h | SSS_EVT5CFG | Event5 that compares to trigger word SSS_EVTTRIG | PARITY_PROTECTED |
| 204h | SSS_EVT6CFG | Event6 that compares to trigger word SSS_EVTTRIG | PARITY_PROTECTED |
| 208h | SSS_EVT7CFG | Event7 that compares to trigger word SSS_EVTTRIG | PARITY_PROTECTED |
| 20Ch | SSS_EVT8CFG | Event8 that compares to trigger word SSS_EVTTRIG | PARITY_PROTECTED |
| 210h | SSS_TRIGEVT5_8CFG | Configuration for using trigger word in specific manner | PARITY_PROTECTED |
| 280h | SSS_BLKSOUTEVT5CFG | Output event5 to be applied for output | PARITY_PROTECTED |
| 284h | SSS_BLKSOUTEVT6CFG | Output event6 to be applied for output | PARITY_PROTECTED |
| 288h | SSS_BLKSOUTEVT7CFG | Output event7 to be applied for output | PARITY_PROTECTED |
| 28Ch | SSS_BLKSOUTEVT8CFG | Output event8 to be applied for output | PARITY_PROTECTED |
| 290h | SSS_OUTEVT5TRIGCFG | Output event5 configuration for triggers, link | PARITY_PROTECTED |
| 294h | SSS_OUTEVT6TRIGCFG | Output event6 configuration for triggers, link | PARITY_PROTECTED |
| 298h | SSS_OUTEVT7TRIGCFG | Output event7 configuration for triggers, link | PARITY_PROTECTED |
| 29Ch | SSS_OUTEVT8TRIGCFG | Output event8 configuration for triggers, link | PARITY_PROTECTED |
| 2A0h | SSS_OUTEVT5DUR | Output event5 configuration of delays | PARITY_PROTECTED |
| 2A4h | SSS_OUTEVT6DUR | Output event6 configuration of delays | PARITY_PROTECTED |
| 2A8h | SSS_OUTEVT7DUR | Output event7 configuration of delays | PARITY_PROTECTED |
| 2ACh | SSS_OUTEVT8DUR | Output event8 configuration of delays | PARITY_PROTECTED |
| 2C8h | PARTEST | Enables parity test |
Complex bit access types are encoded to fit into small table cells. Table 19-38 shows the codes that are used for access types in this section.
| Access Type | Code | Description |
|---|---|---|
| Read Type | ||
| R | R | Read |
| R-0 | R -0 | Read Returns 0s |
| Write Type | ||
| W | W | Write |
| W0C | W 0C | Write 0 to clear |
| W1C | W 1C | Write 1 to clear |
| W1S | W 1S | Write 1 to set |
| Reset or Default Value | ||
| -n | Value after reset or the default value | |
| Register Array Variables | ||
| i,j,k,l,m,n | When these variables are used in a register name, an offset, or an address, they refer to the value of a register array where the register is part of a group of repeating registers. The register groups form a hierarchical structure and the array is represented with a formula. | |
| y | When this variable is used in a register name, an offset, or an address it refers to the value of a register array. | |
BASETIMERLOW is shown in Figure 19-39 and described in Table 19-39.
Return to the Summary Table.
Reflects the latest read value of common time base lower word.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| LOWWORD | |||||||||||||||||||||||||||||||
| R-0h | |||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-0 | LOWWORD | R | 0h | The lower 32 bits of the base timer for debug Reset type: SYSRSn |
BASETIMERHIGH is shown in Figure 19-40 and described in Table 19-40.
Return to the Summary Table.
Has latest read value of the common time base of the upper word. Also has time-base start control. This is write once after reset, configured by application after clocks and resets are stable.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
| ENBASETIMER | RESERVED | HIGHWORD | |||||
| R/W-0h | R-0h | R-0h | |||||
| 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| HIGHWORD | |||||||
| R-0h | |||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
| HIGHWORD | |||||||
| R-0h | |||||||
| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| HIGHWORD | |||||||
| R-0h | |||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31 | ENBASETIMER | R/W | 0h | When Set this starts the base timer for the WADI block which is commonly used timer for all WADI blocks Reset type: SYSRSn |
| 30-28 | RESERVED | R | 0h | Reserved |
| 27-0 | HIGHWORD | R | 0h | The upper 32 bits of the base timer for debug Reset type: SYSRSn |
INTSTS is shown in Figure 19-41 and described in Table 19-41.
Return to the Summary Table.
This is 32 bit status register aggregating the error status of each WADI block to trigger an interrupt to CPU.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
| SIGTOSIG_BLKSINT | SIGBLKSINT | RESERVED | |||||
| R-0h | R-0h | R-0h | |||||
| 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| RESERVED | |||||||
| R-0h | |||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
| RESERVED | RESERVED | RESERVED | RESERVED | RESERVED | RESERVED | RESERVED | RESERVED |
| R-0h | R-0h | R-0h | R-0h | R-0h | R-0h | R-0h | R-0h |
| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | RESERVED | RESERVED | RESERVED | BLK4INT | BLK3INT | BLK2INT | BLK1INT |
| R-0h | R-0h | R-0h | R-0h | R-0h | R-0h | R-0h | R-0h |
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31 | SIGTOSIG_BLKSINT | R | 0h | This register provides the raw information about the presence of the mismatch error between SIGs or availability of readings across WADI blocks as reported through the BLKERRSTS[SIGTOSIG_ERR] All the WADI block SIGTOSIG mismatch errors are aggregated together by ORing Reset type: SYSRSn |
| 30 | SIGBLKSINT | R | 0h | This register provides the raw information about the presence of the failed waveform measurement due to signal Anomaly as reported through the BLKERRSTS[SIG_ERR] All the WADI block measurement errors are aggregated together by Oring Reset type: SYSRSn |
| 29-16 | RESERVED | R | 0h | Reserved |
| 15 | RESERVED | R | 0h | Reserved |
| 14 | RESERVED | R | 0h | Reserved |
| 13 | RESERVED | R | 0h | Reserved |
| 12 | RESERVED | R | 0h | Reserved |
| 11 | RESERVED | R | 0h | Reserved |
| 10 | RESERVED | R | 0h | Reserved |
| 9 | RESERVED | R | 0h | Reserved |
| 8 | RESERVED | R | 0h | Reserved |
| 7 | RESERVED | R | 0h | Reserved |
| 6 | RESERVED | R | 0h | Reserved |
| 5 | RESERVED | R | 0h | Reserved |
| 4 | RESERVED | R | 0h | Reserved |
| 3 | BLK4INT | R | 0h | This register provides the raw information about the presence of the error per WADI block as reported through the BLKERRSTS The Oared version of each block reflects index-wise in each bit of this register Reset type: SYSRSn |
| 2 | BLK3INT | R | 0h | This register provides the raw information about the presence of the error per WADI block as reported through the BLKERRSTS The Oared version of each block reflects index-wise in each bit of this register Reset type: SYSRSn |
| 1 | BLK2INT | R | 0h | This register provides the raw information about the presence of the error per WADI block as reported through the BLKERRSTS The Oared version of each block reflects index-wise in each bit of this register Reset type: SYSRSn |
| 0 | BLK1INT | R | 0h | This register provides the raw information about the presence of the error per WADI block as reported through the BLKERRSTS The Oared version of each block reflects index-wise in each bit of this register Reset type: SYSRSn |
INTSTSMASK is shown in Figure 19-42 and described in Table 19-42.
Return to the Summary Table.
This is mask register to suppress the errors related to specific WADI block.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
| SIGTOSIG_BLKSMASK | SIGBLKSMASK | RESERVED | |||||
| R/W-0h | R/W-0h | R-0h | |||||
| 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| RESERVED | |||||||
| R-0h | |||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
| BLKSMASK | |||||||
| R/W-0h | |||||||
| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| BLKSMASK | |||||||
| R/W-0h | |||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31 | SIGTOSIG_BLKSMASK | R/W | 0h | This bit is representative of the masking of mismatch error aggregated across WADI blocks. '0': corresponding interrupt is not asserted to the CPU. '1': related interrupt is allowed to cause an interrupt to CPU. Reset type: SYSRSn |
| 30 | SIGBLKSMASK | R/W | 0h | This bit is representative of the masking of measurement error aggregated across WADI blocks. '0': corresponding interrupt is not asserted to the CPU. '1': related interrupt is allowed to cause an interrupt to CPU. Reset type: SYSRSn |
| 29-16 | RESERVED | R | 0h | Reserved |
| 15-0 | BLKSMASK | R/W | 0h | Each register bit is representative of the block and can enable or mask the corresponding error to trigger an interrupt or not to the CPU '0': corresponding interrupt is not asserted to the CPU '1': related interrupt is allowed to cause an interrupt to CPU Reset type: SYSRSn |
BLKSMASKSTS is shown in Figure 19-43 and described in Table 19-43.
Return to the Summary Table.
This is masked interrupt status for the WADI IP that triggered the interrupt to CPU. ISR can directly read this to check which WADI block(s) caused an interrupt.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
| SIGTOSIGBLKS | SIGBLKS | RESERVED | |||||
| R-0h | R-0h | R-0h | |||||
| 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| RESERVED | |||||||
| R-0h | |||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
| BLKSMASK | |||||||
| R-0h | |||||||
| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| BLKSMASK | |||||||
| R-0h | |||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31 | SIGTOSIGBLKS | R | 0h | This register gives the bit wise status of activated and asserted error bits block-wise Hence interrupt service routine can readily reach to the detailed status of respective block Reset type: SYSRSn |
| 30 | SIGBLKS | R | 0h | This register gives the bit wise status of activated and asserted error bits block-wise Hence interrupt service routine can readily reach to the detailed status of respective block Reset type: SYSRSn |
| 29-16 | RESERVED | R | 0h | Reserved |
| 15-0 | BLKSMASK | R | 0h | This register gives the bit wise status of activated and asserted error bits block-wise Hence interrupt service routine can readily reach to the detailed status of respective block Reset type: SYSRSn |
INTSTSCLR is shown in Figure 19-44 and described in Table 19-44.
Return to the Summary Table.
This is for interrupt service routines to clear the aggregated status of the block error as in RAW_INT_STATUS.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
| SIGTOSIG_BLKSINT | SIGBLKSINT | RESERVED | |||||
| R-0/W1C-0h | R-0/W1C-0h | R-0h | |||||
| 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| RESERVED | |||||||
| R-0h | |||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
| RESERVED | RESERVED | RESERVED | RESERVED | RESERVED | RESERVED | RESERVED | RESERVED |
| R-0/W1C-0h | R-0/W1C-0h | R-0/W1C-0h | R-0/W1C-0h | R-0/W1C-0h | R-0/W1C-0h | R-0/W1C-0h | R-0/W1C-0h |
| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | RESERVED | RESERVED | RESERVED | BLK4INT | BLK3INT | BLK2INT | BLK1INT |
| R-0/W1C-0h | R-0/W1C-0h | R-0/W1C-0h | R-0/W1C-0h | R-0/W1C-0h | R-0/W1C-0h | R-0/W1C-0h | R-0/W1C-0h |
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31 | SIGTOSIG_BLKSINT | R-0/W1C | 0h | This write 1 to clear register clears the INTSTS of corresponding bit that is written 1 This is regardless of the INTSTSMASK Write 0 has no effect Register always reads 0x0 Reset type: SYSRSn |
| 30 | SIGBLKSINT | R-0/W1C | 0h | This write 1 to clear register clears the INTSTS of corresponding bit that is written 1 This is regardless of the INTSTSMASK Write 0 has no effect Register always reads 0x0 Reset type: SYSRSn |
| 29-16 | RESERVED | R | 0h | Reserved |
| 15 | RESERVED | R-0/W1C | 0h | Reserved |
| 14 | RESERVED | R-0/W1C | 0h | Reserved |
| 13 | RESERVED | R-0/W1C | 0h | Reserved |
| 12 | RESERVED | R-0/W1C | 0h | Reserved |
| 11 | RESERVED | R-0/W1C | 0h | Reserved |
| 10 | RESERVED | R-0/W1C | 0h | Reserved |
| 9 | RESERVED | R-0/W1C | 0h | Reserved |
| 8 | RESERVED | R-0/W1C | 0h | Reserved |
| 7 | RESERVED | R-0/W1C | 0h | Reserved |
| 6 | RESERVED | R-0/W1C | 0h | Reserved |
| 5 | RESERVED | R-0/W1C | 0h | Reserved |
| 4 | RESERVED | R-0/W1C | 0h | Reserved |
| 3 | BLK4INT | R-0/W1C | 0h | This write 1 to clear register clears the INTSTS of corresponding bit that is written 1 This is regardless of the INTSTSMASK Write 0 has no effect Register always reads 0x0 Reset type: SYSRSn |
| 2 | BLK3INT | R-0/W1C | 0h | This write 1 to clear register clears the INTSTS of corresponding bit that is written 1 This is regardless of the INTSTSMASK Write 0 has no effect Register always reads 0x0 Reset type: SYSRSn |
| 1 | BLK2INT | R-0/W1C | 0h | This write 1 to clear register clears the INTSTS of corresponding bit that is written 1 This is regardless of the INTSTSMASK Write 0 has no effect Register always reads 0x0 Reset type: SYSRSn |
| 0 | BLK1INT | R-0/W1C | 0h | This write 1 to clear register clears the INTSTS of corresponding bit that is written 1 This is regardless of the INTSTSMASK Write 0 has no effect Register always reads 0x0 Reset type: SYSRSn |
INTSTSFRC is shown in Figure 19-45 and described in Table 19-45.
Return to the Summary Table.
This is 32 bit raw interrupt status emulate register can be used for test and diagnostic of WADI interrupt mechanism.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
| SIGTOSIG_BLKSINT | SIGBLKSINT | RESERVED | |||||
| R-0/W1S-0h | R-0/W1S-0h | R-0h | |||||
| 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| RESERVED | |||||||
| R-0h | |||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
| RESERVED | RESERVED | RESERVED | RESERVED | RESERVED | RESERVED | RESERVED | RESERVED |
| R-0/W1S-0h | R-0/W1S-0h | R-0/W1S-0h | R-0/W1S-0h | R-0/W1S-0h | R-0/W1S-0h | R-0/W1S-0h | R-0/W1S-0h |
| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | RESERVED | RESERVED | RESERVED | BLK4INT | BLK3INT | BLK2INT | BLK1INT |
| R-0/W1S-0h | R-0/W1S-0h | R-0/W1S-0h | R-0/W1S-0h | R-0/W1S-0h | R-0/W1S-0h | R-0/W1S-0h | R-0/W1S-0h |
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31 | SIGTOSIG_BLKSINT | R-0/W1S | 0h | This interrupt status emulate field can be used for test and diagnose the WADI interrupt mechanism. Write 1 forces the corresponding Interrupt bit. Write 0 has no effect. Reset type: SYSRSn |
| 30 | SIGBLKSINT | R-0/W1S | 0h | This interrupt status emulate field can be used for test and diagnose the WADI interrupt mechanism. Write 1 forces the corresponding Interrupt bit. Write 0 has no effect. Reset type: SYSRSn |
| 29-16 | RESERVED | R | 0h | Reserved |
| 15 | RESERVED | R-0/W1S | 0h | Reserved |
| 14 | RESERVED | R-0/W1S | 0h | Reserved |
| 13 | RESERVED | R-0/W1S | 0h | Reserved |
| 12 | RESERVED | R-0/W1S | 0h | Reserved |
| 11 | RESERVED | R-0/W1S | 0h | Reserved |
| 10 | RESERVED | R-0/W1S | 0h | Reserved |
| 9 | RESERVED | R-0/W1S | 0h | Reserved |
| 8 | RESERVED | R-0/W1S | 0h | Reserved |
| 7 | RESERVED | R-0/W1S | 0h | Reserved |
| 6 | RESERVED | R-0/W1S | 0h | Reserved |
| 5 | RESERVED | R-0/W1S | 0h | Reserved |
| 4 | RESERVED | R-0/W1S | 0h | Reserved |
| 3 | BLK4INT | R-0/W1S | 0h | This interrupt status emulate field can be used for test and diagnose the WADI interrupt mechanism. Write 1 forces the corresponding Interrupt bit. Write 0 has no effect. Reset type: SYSRSn |
| 2 | BLK3INT | R-0/W1S | 0h | This interrupt status emulate field can be used for test and diagnose the WADI interrupt mechanism. Write 1 forces the corresponding Interrupt bit. Write 0 has no effect. Reset type: SYSRSn |
| 1 | BLK2INT | R-0/W1S | 0h | This interrupt status emulate field can be used for test and diagnose the WADI interrupt mechanism. Write 1 forces the corresponding Interrupt bit. Write 0 has no effect. Reset type: SYSRSn |
| 0 | BLK1INT | R-0/W1S | 0h | This interrupt status emulate field can be used for test and diagnose the WADI interrupt mechanism. Write 1 forces the corresponding Interrupt bit. Write 0 has no effect. Reset type: SYSRSn |
SIGSYNCFILTCFG is shown in Figure 19-46 and described in Table 19-46.
Return to the Summary Table.
This is 32 bit mux select to either route the raw input signal to WADI block or to connect through synchroniser and filter.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| RESERVED | |||||||||||||||
| R/W-0h | |||||||||||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | BLKS_SIGS_SYNCFILT | ||||||||||||||
| R/W-0h | R/W-0h | ||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-8 | RESERVED | R/W | 0h | Reserved |
| 7-0 | BLKS_SIGS_SYNCFILT | R/W | 0h | This word provides bitwise option to select the mused input to WADI block connected from cross-bar either directly (1'b0) or through synchroniser followed by glitch filter for width of 1 clock. The resultant signal when elected through sync & filter is delayed by as many (3-4) clock cycles. [0] : BLK1.SIG1 Connected through synchroniser and glitch filter [1] : BLK1.SIG2 Connected through synchroniser and glitch filter [2] : BLK2.SIG1 Connected through synchroniser and glitch filter [3] : BLK2.SIG2 Connected through synchroniser and glitch filter [4] : BLK3.SIG1 Connected through synchroniser and glitch filter [5] : BLK3.SIG2 Connected through synchroniser and glitch filter [6] : BLK4.SIG1 Connected through synchroniser and glitch filter [7] : BLK4.SIG2 Connected through synchroniser and glitch filter Reset type: SYSRSn |
TRIGSYNCFILTCFG is shown in Figure 19-47 and described in Table 19-47.
Return to the Summary Table.
This is 32 bit mux select to either route the trigger signal directly to WADI block or to connect through synchroniser and filter.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| RESERVED | |||||||||||||||
| R/W-0h | |||||||||||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | BLKS_TRIG_SYNCFILT | ||||||||||||||
| R/W-0h | R/W-0h | ||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-8 | RESERVED | R/W | 0h | Reserved |
| 7-0 | BLKS_TRIG_SYNCFILT | R/W | 0h | This word provides bitwise option to select the muxed trigger input to WADI block connected from cross-bar either directly (1'b0) or through synchroniser followed by glitch filter for width of 1 clock. The resultant signal when elected through sync & filter is delayed by as many (3-4) clock cycles. [0] : TRIG input for BLK1.SIG1 Connected through synchroniser and glitch filter [1] : TRIG input for BLK1.SIG2 Connected through synchroniser and glitch filter [2] : TRIG input for BLK2.SIG1 Connected through synchroniser and glitch filter [3] : TRIG input for BLK2.SIG2 Connected through synchroniser and glitch filter [4] : TRIG input for BLK3.SIG1 Connected through synchroniser and glitch filter [5] : TRIG input for BLK3.SIG2 Connected through synchroniser and glitch filter [6] : TRIG input for BLK4.SIG1 Connected through synchroniser and glitch filter [7] : TRIG input for BLK4.SIG2 Connected through synchroniser and glitch filter Reset type: SYSRSn |
REVISION is shown in Figure 19-48 and described in Table 19-48.
Return to the Summary Table.
IP Revision
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
| SCHEME | RESERVED | FUNC | |||||
| R-1h | R-0-0h | R-FF0h | |||||
| 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| FUNC | |||||||
| R-FF0h | |||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
| RTL | MAJOR | ||||||
| R-0h | R-1h | ||||||
| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| CUSTOM | MINOR | ||||||
| R-0h | R-0h | ||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-30 | SCHEME | R | 1h | This identifies the scheme revision ID register type implemented for this module Reset type: SYSRSn |
| 29-28 | RESERVED | R-0 | 0h | Reserved |
| 27-16 | FUNC | R | FF0h | Functional Release Number Reflects software-compatability. If there is no software compatability, a unique func number is assigned for compatible modules, the same number is maintained Reset type: SYSRSn |
| 15-11 | RTL | R | 0h | Design Release Number Incremented for releases due to spec changes or post-release design changes Reset to 0 when either MAJOR or MINOR is incremented Reset type: SYSRSn |
| 10-8 | MAJOR | R | 1h | Major Revision Number Represents major changes to the module (e.g. entirely new features are added/changed) The major revision number for this module Reset type: SYSRSn |
| 7-6 | CUSTOM | R | 0h | Custom Module Number Indicates a special version of the module May not be supported by standard software Reset type: SYSRSn |
| 5-0 | MINOR | R | 0h | Minor Revision Number Represents minor changes to the module (e.g. enhancements to existing features) The minor revision number for this module Reset type: SYSRSn |
DMATRIGSTS is shown in Figure 19-49 and described in Table 19-49.
Return to the Summary Table.
This 32b DMA status indicate the WADI Block/SIG that triggered DMA request
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
| SSS_OUTEVT8 | SSS_OUTEVT7 | SSS_OUTEVT6 | SSS_OUTEVT5 | SSS_OUTEVT4 | SSS_OUTEVT3 | SSS_OUTEVT2 | SSS_OUTEVT1 |
| R/W0C-0h | R/W0C-0h | R/W0C-0h | R/W0C-0h | R/W0C-0h | R/W0C-0h | R/W0C-0h | R/W0C-0h |
| 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| SSS_EVT8 | SSS_EVT7 | SSS_EVT6 | SSS_EVT5 | SSS_EVT4 | SSS_EVT3 | SSS_EVT2 | SSS_EVT1 |
| R/W0C-0h | R/W0C-0h | R/W0C-0h | R/W0C-0h | R/W0C-0h | R/W0C-0h | R/W0C-0h | R/W0C-0h |
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
| RESERVED | RESERVED | RESERVED | RESERVED | RESERVED | RESERVED | RESERVED | RESERVED |
| R/W0C-0h | R/W0C-0h | R/W0C-0h | R/W0C-0h | R/W0C-0h | R/W0C-0h | R/W0C-0h | R/W0C-0h |
| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | RESERVED | RESERVED | RESERVED | BLK4_DMAEVT | BLK3_DMAEVT | BLK2_DMAEVT | BLK1_DMAEVT |
| R/W0C-0h | R/W0C-0h | R/W0C-0h | R/W0C-0h | R/W0C-0h | R/W0C-0h | R/W0C-0h | R/W0C-0h |
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31 | SSS_OUTEVT8 | R/W0C | 0h | Each bit is indicative of the SSS Event word event that triggered the DMA event. The status is taken after applying the DMA_Event_Enable mask. Following are the assignments for different Sequencer events. Status bit when set indicates occurrence of event. Upon DMA write and DMA ack the bit will get cleared. Alternatively Write of 0x0 by user shall also clear the corresponding bit status. Write of 0x1 has no effect on bit. DMA enabled event of OUTEVT8 triggered DMA Request Reset type: SYSRSn |
| 30 | SSS_OUTEVT7 | R/W0C | 0h | Each bit is indicative of the SSS Event word event that triggered the DMA event. The status is taken after applying the DMA_Event_Enable mask. Following are the assignments for different Sequencer events. Status bit when set indicates occurrence of event. Upon DMA write and DMA ack the bit will get cleared. Alternatively Write of 0x0 by user shall also clear the corresponding bit status. Write of 0x1 has no effect on bit. DMA enabled event of OUTEVT7 triggered DMA Request Reset type: SYSRSn |
| 29 | SSS_OUTEVT6 | R/W0C | 0h | Each bit is indicative of the SSS Event word event that triggered the DMA event. The status is taken after applying the DMA_Event_Enable mask. Following are the assignments for different Sequencer events. Status bit when set indicates occurrence of event. Upon DMA write and DMA ack the bit will get cleared. Alternatively Write of 0x0 by user shall also clear the corresponding bit status. Write of 0x1 has no effect on bit. DMA enabled event of OUTEVT6 triggered DMA Request Reset type: SYSRSn |
| 28 | SSS_OUTEVT5 | R/W0C | 0h | Each bit is indicative of the SSS Event word event that triggered the DMA event. The status is taken after applying the DMA_Event_Enable mask. Following are the assignments for different Sequencer events. Status bit when set indicates occurrence of event. Upon DMA write and DMA ack the bit will get cleared. Alternatively Write of 0x0 by user shall also clear the corresponding bit status. Write of 0x1 has no effect on bit. DMA enabled event of OUTEVT5 triggered DMA Request Reset type: SYSRSn |
| 27 | SSS_OUTEVT4 | R/W0C | 0h | Each bit is indicative of the SSS Event word event that triggered the DMA event. The status is taken after applying the DMA_Event_Enable mask. Following are the assignments for different Sequencer events. Status bit when set indicates occurrence of event. Upon DMA write and DMA ack the bit will get cleared. Alternatively Write of 0x0 by user shall also clear the corresponding bit status. Write of 0x1 has no effect on bit. DMA enabled event of OUTEVT4 triggered DMA Request Reset type: SYSRSn |
| 26 | SSS_OUTEVT3 | R/W0C | 0h | Each bit is indicative of the SSS Event word event that triggered the DMA event. The status is taken after applying the DMA_Event_Enable mask. Following are the assignments for different Sequencer events. Status bit when set indicates occurrence of event. Upon DMA write and DMA ack the bit will get cleared. Alternatively Write of 0x0 by user shall also clear the corresponding bit status. Write of 0x1 has no effect on bit. DMA enabled event of OUTEVT3 triggered DMA Request Reset type: SYSRSn |
| 25 | SSS_OUTEVT2 | R/W0C | 0h | Each bit is indicative of the SSS Event word event that triggered the DMA event. The status is taken after applying the DMA_Event_Enable mask. Following are the assignments for different Sequencer events. Status bit when set indicates occurrence of event. Upon DMA write and DMA ack the bit will get cleared. Alternatively Write of 0x0 by user shall also clear the corresponding bit status. Write of 0x1 has no effect on bit. DMA enabled event of OUTEVT2 triggered DMA Request Reset type: SYSRSn |
| 24 | SSS_OUTEVT1 | R/W0C | 0h | Each bit is indicative of the SSS Event word event that triggered the DMA event. The status is taken after applying the DMA_Event_Enable mask. Following are the assignments for different Sequencer events. Status bit when set indicates occurrence of event. Upon DMA write and DMA ack the bit will get cleared. Alternatively Write of 0x0 by user shall also clear the corresponding bit status. Write of 0x1 has no effect on bit. DMA enabled event of OUTEVT1 triggered DMA Request Reset type: SYSRSn |
| 23 | SSS_EVT8 | R/W0C | 0h | Each bit is indicative of the SSS Event word event that triggered the DMA event. The status is taken after applying the DMA_Event_Enable mask. Following are the assignments for different events. Status bit when set indicates occurrence of event. Upon DMA write and DMA ack the bit will get cleared. Alternatively Write of 0x0 by user shall also clear the corresponding bit status. Write of 0x1 has no effect on bit. DMA enabled event of EVENT_WORD8 triggered DMA Request Reset type: SYSRSn |
| 22 | SSS_EVT7 | R/W0C | 0h | Each bit is indicative of the SSS Event word event that triggered the DMA event. The status is taken after applying the DMA_Event_Enable mask. Following are the assignments for different events. Status bit when set indicates occurrence of event. Upon DMA write and DMA ack the bit will get cleared. Alternatively Write of 0x0 by user shall also clear the corresponding bit status. Write of 0x1 has no effect on bit. DMA enabled event of EVENT_WORD7 triggered DMA Request Reset type: SYSRSn |
| 21 | SSS_EVT6 | R/W0C | 0h | Each bit is indicative of the SSS Event word event that triggered the DMA event. The status is taken after applying the DMA_Event_Enable mask. Following are the assignments for different events. Status bit when set indicates occurrence of event. Upon DMA write and DMA ack the bit will get cleared. Alternatively Write of 0x0 by user shall also clear the corresponding bit status. Write of 0x1 has no effect on bit. DMA enabled event of EVENT_WORD6 triggered DMA Request Reset type: SYSRSn |
| 20 | SSS_EVT5 | R/W0C | 0h | Each bit is indicative of the SSS Event word event that triggered the DMA event. The status is taken after applying the DMA_Event_Enable mask. Following are the assignments for different events. Status bit when set indicates occurrence of event. Upon DMA write and DMA ack the bit will get cleared. Alternatively Write of 0x0 by user shall also clear the corresponding bit status. Write of 0x1 has no effect on bit. DMA enabled event of EVENT_WORD5 triggered DMA Request Reset type: SYSRSn |
| 19 | SSS_EVT4 | R/W0C | 0h | Each bit is indicative of the SSS Event word event that triggered the DMA event. The status is taken after applying the DMA_Event_Enable mask. Following are the assignments for different events. Status bit when set indicates occurrence of event. Upon DMA write and DMA ack the bit will get cleared. Alternatively Write of 0x0 by user shall also clear the corresponding bit status. Write of 0x1 has no effect on bit. DMA enabled event of EVENT_WORD4 triggered DMA Request Reset type: SYSRSn |
| 18 | SSS_EVT3 | R/W0C | 0h | Each bit is indicative of the SSS Event word event that triggered the DMA event. The status is taken after applying the DMA_Event_Enable mask. Following are the assignments for different events. Status bit when set indicates occurrence of event. Upon DMA write and DMA ack the bit will get cleared. Alternatively Write of 0x0 by user shall also clear the corresponding bit status. Write of 0x1 has no effect on bit. DMA enabled event of EVENT_WORD3 triggered DMA Request Reset type: SYSRSn |
| 17 | SSS_EVT2 | R/W0C | 0h | Each bit is indicative of the SSS Event word event that triggered the DMA event. The status is taken after applying the DMA_Event_Enable mask. Following are the assignments for different events. Status bit when set indicates occurrence of event. Upon DMA write and DMA ack the bit will get cleared. Alternatively Write of 0x0 by user shall also clear the corresponding bit status. Write of 0x1 has no effect on bit. DMA enabled event of EVENT_WORD2 triggered DMA Request Reset type: SYSRSn |
| 16 | SSS_EVT1 | R/W0C | 0h | Each bit is indicative of the SSS Event word event that triggered the DMA event. The status is taken after applying the DMA_Event_Enable mask. Following are the assignments for different events. Status bit when set indicates occurrence of event. Upon DMA write and DMA ack the bit will get cleared. Alternatively Write of 0x0 by user shall also clear the corresponding bit status. Write of 0x1 has no effect on bit. DMA enabled event of EVENT_WORD1 triggered DMA Request Reset type: SYSRSn |
| 15 | RESERVED | R/W0C | 0h | Reserved |
| 14 | RESERVED | R/W0C | 0h | Reserved |
| 13 | RESERVED | R/W0C | 0h | Reserved |
| 12 | RESERVED | R/W0C | 0h | Reserved |
| 11 | RESERVED | R/W0C | 0h | Reserved |
| 10 | RESERVED | R/W0C | 0h | Reserved |
| 9 | RESERVED | R/W0C | 0h | Reserved |
| 8 | RESERVED | R/W0C | 0h | Reserved |
| 7 | RESERVED | R/W0C | 0h | Reserved |
| 6 | RESERVED | R/W0C | 0h | Reserved |
| 5 | RESERVED | R/W0C | 0h | Reserved |
| 4 | RESERVED | R/W0C | 0h | Reserved |
| 3 | BLK4_DMAEVT | R/W0C | 0h | Each bit is indicative of the WADI event that triggered the DMA event. The status is taken after applying the mask. Following are the assignments for different events. Status bit when set indicates occurrence of event. Upon DMA write and DMA ack the bit will get cleared. Alternatively Write of 0x0 by user shall also clear the corresponding bit status. Write of 0x1 has no effect on bit. DMA enabled event of block3 that triggered DMA Request Reset type: SYSRSn |
| 2 | BLK3_DMAEVT | R/W0C | 0h | Each bit is indicative of the WADI event that triggered the DMA event. The status is taken after applying the mask. Following are the assignments for different events. Status bit when set indicates occurrence of event. Upon DMA write and DMA ack the bit will get cleared. Alternatively Write of 0x0 by user shall also clear the corresponding bit status. Write of 0x1 has no effect on bit. DMA enabled event of block2 that triggered DMA Request Reset type: SYSRSn |
| 1 | BLK2_DMAEVT | R/W0C | 0h | Each bit is indicative of the WADI event that triggered the DMA event. The status is taken after applying the mask. Following are the assignments for different events. Status bit when set indicates occurrence of event. Upon DMA write and DMA ack the bit will get cleared. Alternatively Write of 0x0 by user shall also clear the corresponding bit status. Write of 0x1 has no effect on bit. DMA enabled event of block1 that triggered DMA Request Reset type: SYSRSn |
| 0 | BLK1_DMAEVT | R/W0C | 0h | Each bit is indicative of the WADI event that triggered the DMA event. The status is taken after applying the mask. Following are the assignments for different events. Status bit when set indicates occurrence of event. Upon DMA write and DMA ack the bit will get cleared. Alternatively Write of 0x0 by user shall also clear the corresponding bit status. Write of 0x1 has no effect on bit. DMA enabled event of block0 that triggered DMA Request Reset type: SYSRSn |
DMATRIGEN is shown in Figure 19-50 and described in Table 19-50.
Return to the Summary Table.
This 32b control to individually enable DMA trigger reasons of different Block SIG errors
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
| SSS_OUTEVT5_8DMA | SSS_OUTEVT1_4DMA | ||||||
| R/W-0h | R/W-0h | ||||||
| 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| SSS_EVT5_8DMA | SSS_EVT1_4DMA | ||||||
| R/W-0h | R/W-0h | ||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
| BLKSDMAEVT | |||||||
| R/W-0h | |||||||
| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| BLKSDMAEVT | |||||||
| R/W-0h | |||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-28 | SSS_OUTEVT5_8DMA | R/W | 0h | Application needs to enable respective bits to ensure the DMA request is raised based on the event. 0x1 configuration enables DMA request assertion, 0x0 is disable for the event and does not cause the DMA request. Each bit is indicative of the SSS output events as below. [28] :DMA Request Enable for event of OUTEVT5 [29] :DMA Request Enable for event of OUTEVT6 [30] :DMA Request Enable for event of OUTEVT7 [31] :DMA Request Enable for event of OUTEVT8 Reset type: SYSRSn |
| 27-24 | SSS_OUTEVT1_4DMA | R/W | 0h | Application needs to enable respective bits to ensure the DMA request is raised based on the event. 0x1 configuration enables DMA request assertion, 0x0 is disable for the event and does not cause the DMA request. Each bit is indicative of the SSS output events as below. [24] :DMA Request Enable for event of OUTEVT1 [25] :DMA Request Enable for event of OUTEVT2 [26] :DMA Request Enable for event of OUTEVT3 [27] :DMA Request Enable for event of OUTEVT4 Reset type: SYSRSn |
| 23-20 | SSS_EVT5_8DMA | R/W | 0h | Application needs to enable respective bits to ensure the DMA request is raised based on the event. 0x1 configuration enables DMA request assertion, 0x0 is disable for the event and does not cause the DMA request. Each bit is indicative of the SSS Event word as below. [20] :DMA Request Enable for event of SSS_EVT5 [21] :DMA Request Enable for event of SSS_EVT6 [22] :DMA Request Enable for event of SSS_EVT7 [23] :DMA Request Enable for event of SSS_EVT8 Reset type: SYSRSn |
| 19-16 | SSS_EVT1_4DMA | R/W | 0h | Application needs to enable respective bits to ensure the DMA request is raised based on the event. 0x1 configuration enables DMA request assertion, 0x0 is disable for the event and does not cause the DMA request. Each bit is indicative of the SSS Event word as below. [16] :DMA Request Enable for event of SSS_EVT1 [17] :DMA Request Enable for event of SSS_EVT2 [18] :DMA Request Enable for event of SSS_EVT3 [19] :DMA Request Enable for event of SSS_EVT4 Reset type: SYSRSn |
| 15-0 | BLKSDMAEVT | R/W | 0h | Application needs to enable respective bits to ensure the DMA request is raised based on the event. 0x1 configuration enables DMA request assertion, 0x0 is disable for the event and does not cause the DMA request. Each bit is indicative of the WADI Block event as below. [0] :DMA Request Enable for event of block1 [1] :DMA Request Enable for event of block2 [2] :DMA Request Enable for event of block3 [3] :DMA Request Enable for event of block4 [4:15] : Reserved Reset type: SYSRSn |
DMASTSUPDATE is shown in Figure 19-51 and described in Table 19-51.
Return to the Summary Table.
Status register indicating which register thresholds got updated after the DMA write
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
| WRSTSOUT8 | WRSTSOUT7 | WRSTSOUT6 | WRSTSOUT5 | WRSTSOUT4 | WRSTSOUT3 | WRSTSOUT2 | WRSTSOUT1 |
| R/W0C-0h | R/W0C-0h | R/W0C-0h | R/W0C-0h | R/W0C-0h | R/W0C-0h | R/W0C-0h | R/W0C-0h |
| 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| WRSTSEVT8 | WRSTSEVT7 | WRSTSEVT6 | WRSTSEVT5 | WRSTSEVT4 | WRSTSEVT3 | WRSTSEVT2 | WRSTSEVT1 |
| R/W0C-0h | R/W0C-0h | R/W0C-0h | R/W0C-0h | R/W0C-0h | R/W0C-0h | R/W0C-0h | R/W0C-0h |
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
| RESERVED | RESERVED | RESERVED | RESERVED | RESERVED | RESERVED | RESERVED | RESERVED |
| R/W0C-0h | R/W0C-0h | R/W0C-0h | R/W0C-0h | R/W0C-0h | R/W0C-0h | R/W0C-0h | R/W0C-0h |
| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | RESERVED | RESERVED | RESERVED | WRSTSBLK4 | WRSTSBLK3 | WRSTSBLK2 | WRSTSBLK1 |
| R/W0C-0h | R/W0C-0h | R/W0C-0h | R/W0C-0h | R/W0C-0h | R/W0C-0h | R/W0C-0h | R/W0C-0h |
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31 | WRSTSOUT8 | R/W0C | 0h | Indicates if MMR configuration of the WADI block is updated by the filtered DMA transfer or not. Writing 1 to this register has no effect, Writing 0 clears the staus. Register sets were updated for OUTEVT8 Reset type: SYSRSn |
| 30 | WRSTSOUT7 | R/W0C | 0h | Indicates if MMR configuration of the WADI block is updated by the filtered DMA transfer or not. Writing 1 to this register has no effect, Writing 0 clears the staus. Register sets were updated for OUTEVT7 Reset type: SYSRSn |
| 29 | WRSTSOUT6 | R/W0C | 0h | Indicates if MMR configuration of the WADI block is updated by the filtered DMA transfer or not. Writing 1 to this register has no effect, Writing 0 clears the staus. Register sets were updated for OUTEVT6 Reset type: SYSRSn |
| 28 | WRSTSOUT5 | R/W0C | 0h | Indicates if MMR configuration of the WADI block is updated by the filtered DMA transfer or not. Writing 1 to this register has no effect, Writing 0 clears the staus. Register sets were updated for OUTEVT5 Reset type: SYSRSn |
| 27 | WRSTSOUT4 | R/W0C | 0h | Indicates if MMR configuration of the WADI block is updated by the filtered DMA transfer or not. Writing 1 to this register has no effect, Writing 0 clears the staus. Register sets were updated for OUTEVT4 Reset type: SYSRSn |
| 26 | WRSTSOUT3 | R/W0C | 0h | Indicates if MMR configuration of the WADI block is updated by the filtered DMA transfer or not. Writing 1 to this register has no effect, Writing 0 clears the staus. Register sets were updated for OUTEVT3 Reset type: SYSRSn |
| 25 | WRSTSOUT2 | R/W0C | 0h | Indicates if MMR configuration of the WADI block is updated by the filtered DMA transfer or not. Writing 1 to this register has no effect, Writing 0 clears the staus. Register sets were updated for OUTEVT2 Reset type: SYSRSn |
| 24 | WRSTSOUT1 | R/W0C | 0h | Indicates if MMR configuration of the WADI block is updated by the filtered DMA transfer or not. Writing 1 to this register has no effect, Writing 0 clears the staus. Register sets were updated for OUTEVT1 Reset type: SYSRSn |
| 23 | WRSTSEVT8 | R/W0C | 0h | Indicates if MMR configuration of the WADI block is updated by the filtered DMA transfer or not. Writing 1 to this register has no effect, Writing 0 clears the staus. Register sets were updated for SSS_EVT8 Reset type: SYSRSn |
| 22 | WRSTSEVT7 | R/W0C | 0h | Indicates if MMR configuration of the WADI block is updated by the filtered DMA transfer or not. Writing 1 to this register has no effect, Writing 0 clears the staus. Register sets were updated for SSS_EVT7 Reset type: SYSRSn |
| 21 | WRSTSEVT6 | R/W0C | 0h | Indicates if MMR configuration of the WADI block is updated by the filtered DMA transfer or not. Writing 1 to this register has no effect, Writing 0 clears the staus. Register sets were updated for SSS_EVT6 Reset type: SYSRSn |
| 20 | WRSTSEVT5 | R/W0C | 0h | Indicates if MMR configuration of the WADI block is updated by the filtered DMA transfer or not. Writing 1 to this register has no effect, Writing 0 clears the staus. Register sets were updated for SSS_EVT5 Reset type: SYSRSn |
| 19 | WRSTSEVT4 | R/W0C | 0h | Indicates if MMR configuration of the WADI block is updated by the filtered DMA transfer or not. Writing 1 to this register has no effect, Writing 0 clears the staus. Register sets were updated for SSS_EVT4 Reset type: SYSRSn |
| 18 | WRSTSEVT3 | R/W0C | 0h | Indicates if MMR configuration of the WADI block is updated by the filtered DMA transfer or not. Writing 1 to this register has no effect, Writing 0 clears the staus. Register sets were updated for SSS_EVT3 Reset type: SYSRSn |
| 17 | WRSTSEVT2 | R/W0C | 0h | Indicates if MMR configuration of the WADI block is updated by the filtered DMA transfer or not. Writing 1 to this register has no effect, Writing 0 clears the staus. Register sets were updated for SSS_EVT2 Reset type: SYSRSn |
| 16 | WRSTSEVT1 | R/W0C | 0h | Indicates if MMR configuration of the WADI block is updated by the filtered DMA transfer or not. Writing 1 to this register has no effect, Writing 0 clears the staus. Register sets were updated for SSS_EVT1 Reset type: SYSRSn |
| 15 | RESERVED | R/W0C | 0h | Reserved |
| 14 | RESERVED | R/W0C | 0h | Reserved |
| 13 | RESERVED | R/W0C | 0h | Reserved |
| 12 | RESERVED | R/W0C | 0h | Reserved |
| 11 | RESERVED | R/W0C | 0h | Reserved |
| 10 | RESERVED | R/W0C | 0h | Reserved |
| 9 | RESERVED | R/W0C | 0h | Reserved |
| 8 | RESERVED | R/W0C | 0h | Reserved |
| 7 | RESERVED | R/W0C | 0h | Reserved |
| 6 | RESERVED | R/W0C | 0h | Reserved |
| 5 | RESERVED | R/W0C | 0h | Reserved |
| 4 | RESERVED | R/W0C | 0h | Reserved |
| 3 | WRSTSBLK4 | R/W0C | 0h | Indicates if MMR configuration of the WADI block is updated by the filtered transfer or not. The field is not updated if the block is not enabled for filtered write. Writing 1 to this register has no effect, Writing 0 clears the staus. Register sets were updated for block3 Reset type: SYSRSn |
| 2 | WRSTSBLK3 | R/W0C | 0h | Indicates if MMR configuration of the WADI block is updated by the filtered transfer or not. The field is not updated if the block is not enabled for filtered write. Writing 1 to this register has no effect, Writing 0 clears the staus. Register sets were updated for block2 Reset type: SYSRSn |
| 1 | WRSTSBLK2 | R/W0C | 0h | Indicates if MMR configuration of the WADI block is updated by the filtered transfer or not. The field is not updated if the block is not enabled for filtered write. Writing 1 to this register has no effect, Writing 0 clears the staus. Register sets were updated for block1 Reset type: SYSRSn |
| 0 | WRSTSBLK1 | R/W0C | 0h | Indicates if MMR configuration of the WADI block is updated by the filtered transfer or not. The field is not updated if the block is not enabled for filtered write. Writing 1 to this register has no effect, Writing 0 clears the staus. Register sets were updated for block0 Reset type: SYSRSn |
DMAFILTWRCFG is shown in Figure 19-52 and described in Table 19-52.
Return to the Summary Table.
Control for filtered DMA writes to WADI and SSS blocks
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
| OUTEVT5_8WREN | OUTEVT1_4WREN | ||||||
| R/W-0h | R/W-0h | ||||||
| 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| EVT5_8WREN | EVT1_4WREN | ||||||
| R/W-0h | R/W-0h | ||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
| BLKSWREN | |||||||
| R/W-0h | |||||||
| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| BLKSWREN | |||||||
| R/W-0h | |||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-28 | OUTEVT5_8WREN | R/W | 0h | Enables triggered event cause based DMA writes to the MMR of the Block. When Set the DMA writes have effect only if the event has triggered (post enable) the DMA request. If in cleared (0x0) state then all writes are passed through to the block without filter. [28] :Filtered DMA write enable for OUTEVT5 [29] :Filtered DMA write enable for OUTEVT6 [30] :Filtered DMA write enable for OUTEVT7 [31] :Filtered DMA write enable for OUTEVT8 Reset type: SYSRSn |
| 27-24 | OUTEVT1_4WREN | R/W | 0h | Enables triggered event cause based DMA writes to the MMR of the Block. When Set the DMA writes have effect only if the event has triggered (post enable) the DMA request. If in cleared (0x0) state then all writes are passed through to the block without filter. [24] :Filtered DMA write enable for OUTEVT1 [25] :Filtered DMA write enable for OUTEVT2 [26] :Filtered DMA write enable for OUTEVT3 [27] :Filtered DMA write enable for OUTEVT4 Reset type: SYSRSn |
| 23-20 | EVT5_8WREN | R/W | 0h | Enables triggered event cause based DMA writes to the MMR of the Block. When Set the DMA writes have effect only if the event has triggered (post enable) the DMA request. If in cleared (0x0) state then all writes are passed through to the block without filter. [20] :Filtered DMA write enable for SSS_EVT5 [21] :Filtered DMA write enable for SSS_EVT6 [22] :Filtered DMA write enable for SSS_EVT7 [23] :Filtered DMA write enable for SSS_EVT8 Reset type: SYSRSn |
| 19-16 | EVT1_4WREN | R/W | 0h | Enables triggered event cause based DMA writes to the MMR of the Block. When Set the DMA writes have effect only if the event has triggered (post enable) the DMA request. If in cleared (0x0) state then all writes are passed through to the block without filter. [16] :Filtered DMA write enable for SSS_EVT1 [17] :Filtered DMA write enable for SSS_EVT2 [18] :Filtered DMA write enable for SSS_EVT3 [19] :Filtered DMA write enable for SSS_EVT4 Reset type: SYSRSn |
| 15-0 | BLKSWREN | R/W | 0h | Enables triggered event cause based DMA writes to the MMR of the Block. When Set the DMA writes have effect only if the event has triggered (post enable) the DMA request. If in cleared (0x0) state then all writes are passed through to the block without filter. [0] :Filtered DMA write enable for block0 [1] :Filtered DMA write enable for block1 [2] :Filtered DMA write enable for block2 [3] :Filtered DMA write enable for block3 [4] :Filtered DMA write enable for block4 [4:15] : Reserved Reset type: SYSRSn |
CFGREGLOCK is shown in Figure 19-53 and described in Table 19-53.
Return to the Summary Table.
Configuration register lock
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
| RESERVED | |||||||
| R-0h | |||||||
| 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| RESERVED | |||||||
| R-0h | |||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
| RESERVED | |||||||
| R-0h | |||||||
| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | LOCK | ||||||
| R-0h | R/W-0h | ||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-16 | RESERVED | R | 0h | Reserved |
| 15-1 | RESERVED | R | 0h | Reserved |
| 0 | LOCK | R/W | 0h | Determines whether WADI Configuration registers can be written. 0 : Register can be written 1 : Register cannot be written This bit can only be modified if CONFIG_REG_COMMIT.COMMIT is zero. Following block MMR are exmpted from lock, due to regular use in opetration. COMMON_CONFIG COMMON_TRIG_CFG ERR_STATUS PARITY_TEST Reset type: SYSRSn |
CFGREGCOMMIT is shown in Figure 19-54 and described in Table 19-54.
Return to the Summary Table.
Configuration Register Commit
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
| RESERVED | |||||||
| R-0h | |||||||
| 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| RESERVED | |||||||
| R-0h | |||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
| RESERVED | |||||||
| R-0h | |||||||
| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | COMMIT | ||||||
| R-0h | R/W1S-0h | ||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-16 | RESERVED | R | 0h | Reserved |
| 15-1 | RESERVED | R | 0h | Reserved |
| 0 | COMMIT | R/W1S | 0h | When set, locks the CONFIG_REG_LOCK register. This bit cannot be cleared, except by reset. 0 : CONFIG_REG_LOCK is modifiable 1 : CONFIG_REG_LOCK is committed permanently Reset type: SYSRSn |
OPERREGLOCK is shown in Figure 19-55 and described in Table 19-55.
Return to the Summary Table.
Operating Register Lock
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
| RESERVED | |||||||
| R-0h | |||||||
| 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| RESERVED | |||||||
| R-0h | |||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
| RESERVED | |||||||
| R-0h | |||||||
| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | LOCK | ||||||
| R-0h | R/W-0h | ||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-16 | RESERVED | R | 0h | Reserved |
| 15-1 | RESERVED | R | 0h | Reserved |
| 0 | LOCK | R/W | 0h | Determines whether WADI Operational registers can be written. 0 : Register can be written 1 : Register cannot be written This bit can only be modified if OPER_REG_COMMIT.COMMIT is zero. Following block MMR are exmpted from lock, due to regular use in opetration. INT_STATUS_MASK RAW_INT_STATUS_CLR RAW_INT_STATUS_FRC CONFIG_REG_LOCK CONFIG_REG_COMMIT OPER_REG_LOCK OPER_REG_COMMIT PARITY_TEST Reset type: SYSRSn |
OPERREGCOMMIT is shown in Figure 19-56 and described in Table 19-56.
Return to the Summary Table.
Operating Register Commit
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
| RESERVED | |||||||
| R-0h | |||||||
| 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| RESERVED | |||||||
| R-0h | |||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
| RESERVED | |||||||
| R-0h | |||||||
| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | COMMIT | ||||||
| R-0h | R/W1S-0h | ||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-16 | RESERVED | R | 0h | Reserved |
| 15-1 | RESERVED | R | 0h | Reserved |
| 0 | COMMIT | R/W1S | 0h | When set, locks the OPER_REG_LOCK register. This bit cannot be cleared, except by reset. 0 : OPER_REG_LOCK is modifiable 1 : OPER_REG_LOCK is committed permanently Reset type: SYSRSn |
SSS_EVTTRIG is shown in Figure 19-57 and described in Table 19-57.
Return to the Summary Table.
Event trigger word output by WADI instance for SSS
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | EVTTRIG | ||||||||||||||||||||||||||||||
| R/W-0h | R/W-0h | ||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-8 | RESERVED | R/W | 0h | Reserved |
| 7-0 | EVTTRIG | R/W | 0h | Each bit is the event recording of a particular signal of the WADI blocks. All odd bits are used for SIG1 and SIGTOSIG events aggregation and odd bits are used for SIG2 event aggregation. The write override to this register is only to enable the emulation/debug for the event word. [0] : SIG1 & SIGTOSIG event aggregation of block1 [1] : SIG2 event aggregation of block1 [2] : SIG1 & SIGTOSIG event aggregation of block2 [3] : SIG2 event aggregation of block2 [4] : SIG1 & SIGTOSIG event aggregation of block3 [5] : SIG2 event aggregation of block3 [6] : SIG1 & SIGTOSIG event aggregation of block4 [7] : SIG2 event aggregation of block4 Reset type: SYSRSn |
SSS_OUTEVTSTS is shown in Figure 19-58 and described in Table 19-58.
Return to the Summary Table.
Indicates the active status of output events. Allows emulation by of active output event by overriding the value.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| RESERVED | |||||||||||||||
| R-0h | |||||||||||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | OUTEVT5_8 | OUTEVT1_4 | |||||||||||||
| R-0h | R/W-0h | R/W-0h | |||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-16 | RESERVED | R | 0h | Reserved |
| 15-8 | RESERVED | R | 0h | Reserved |
| 7-4 | OUTEVT5_8 | R/W | 0h | This is status register indicating the active status of the output events as triggered by underlying trigger configurations. Write is allowed to emulate these words to help with debug and development. Setting bit has same effect as output events getting activated in event triggered fashion. Deactivating same as completion of active period but without effect of activation of linked word. [4] :Active Status of OUTEVT5 [5] :Active Status of OUTEVT6 [6] :Active Status of OUTEVT7 [7] :Active Status of OUTEVT8 Reset type: SYSRSn |
| 3-0 | OUTEVT1_4 | R/W | 0h | This is status register indicating the active status of the output events as triggered by underlying trigger configurations. Write is allowed to emulate these words to help with debug and development. Setting bit has same effect as output events getting activated in event triggered fashion. Deactivating same as completion of active period but without effect of activation of linked word. [0] :Active Status of OUTEVT1 [1] :Active Status of OUTEVT2 [2] :Active Status of OUTEVT3 [3] :Active Status of OUTEVT4 Reset type: SYSRSn |
SSS_BLK1_2OUTSEL is shown in Figure 19-59 and described in Table 19-59.
Return to the Summary Table.
Selects the output events to be muxed for corresponding output, if that output event is active.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| BLK2SIG2 | BLK2SIG1 | BLK1SIG2 | BLK1SIG1 | ||||||||||||||||||||||||||||
| R/W-0h | R/W-0h | R/W-0h | R/W-0h | ||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-24 | BLK2SIG2 | R/W | 0h | This word shows the association of the WADI output related BLK2-SIG2 to the related OUTEVTn. If the association bit is set then upon sequence word being active the corresponding bit of sequence word drives the related O/P. Where each bit is related to respective output event. Multiple bits can be set to seek the sequence as configured. 0x0 : No Safe state sequencer override. 0x1 : OUTEVT1 drives fixed value of corresponding bit 0x2 : OUTEVT2 drives fixed value of corresponding bit 0x4 : OUTEVT3drives fixed value of corresponding bit 0x8 : OUTEVT4drives fixed value of corresponding bit 0x10 : OUTEVT5 drives fixed value of corresponding bit 0x20 : OUTEVT6 drives fixed value of corresponding bit 0x40 : OUTEVT7 drives fixed value of corresponding bit 0x80 : OUTEVT8 drives fixed value of corresponding bit 0x3 : OUTEVT1,OUTEVT2 drive the sequence from respective bit 0x7 : OUTEVT1, OUTEVT2,OUTEVT3 drive the sequence from respective bit 0xF : OUTEVT1, OUTEVT2,OUTEVT3,OUTEVT4 drive the sequence from respective bit 0x6 : OUTEVT2,OUTEVT3 drive the sequence from respective bit 0xE : OUTEVT2,OUTEVT3,OUTEVT4 drive the sequence from respective bit 0xC : OUTEVT3,OUTEVT4 drive the sequence from respective bit Any such combinations of OUTEVTn are allowed depending upon sequence configuration settings. Only few depicted here. Reset type: SYSRSn |
| 23-16 | BLK2SIG1 | R/W | 0h | This word shows the association of the WADI output related BLK2-SIG1 to the related OUTEVTn. If the association bit is set then upon sequence word being active the corresponding bit of sequence word drives the related O/P. Where each bit is related to respective output event. Multiple bits can be set to seek the sequence as configured. 0x0 : No Safe state sequencer override. 0x1 : OUTEVT1 drives fixed value of corresponding bit 0x2 : OUTEVT2 drives fixed value of corresponding bit 0x4 : OUTEVT3drives fixed value of corresponding bit 0x8 : OUTEVT4drives fixed value of corresponding bit 0x10 : OUTEVT5 drives fixed value of corresponding bit 0x20 : OUTEVT6 drives fixed value of corresponding bit 0x40 : OUTEVT7 drives fixed value of corresponding bit 0x80 : OUTEVT8 drives fixed value of corresponding bit 0x3 : OUTEVT1,OUTEVT2 drive the sequence from respective bit 0x7 : OUTEVT1, OUTEVT2,OUTEVT3 drive the sequence from respective bit 0xF : OUTEVT1, OUTEVT2,OUTEVT3,OUTEVT4 drive the sequence from respective bit 0x6 : OUTEVT2,OUTEVT3 drive the sequence from respective bit 0xE : OUTEVT2,OUTEVT3,OUTEVT4 drive the sequence from respective bit 0xC : OUTEVT3,OUTEVT4 drive the sequence from respective bit Any such combinations of OUTEVTn are allowed depending upon sequence configuration settings. Only few depicted here. Reset type: SYSRSn |
| 15-8 | BLK1SIG2 | R/W | 0h | This word shows the association of the WADI output related BLK1-SIG2 to the related OUTEVTn. If the association bit is set then upon sequence word being active the corresponding bit of sequence word drives the related O/P. Where each bit is related to respective output event. Multiple bits can be set to seek the sequence as configured. 0x0 : No Safe state sequencer override. 0x1 : OUTEVT1 drives fixed value of corresponding bit 0x2 : OUTEVT2 drives fixed value of corresponding bit 0x4 : OUTEVT3drives fixed value of corresponding bit 0x8 : OUTEVT4drives fixed value of corresponding bit 0x10 : OUTEVT5 drives fixed value of corresponding bit 0x20 : OUTEVT6 drives fixed value of corresponding bit 0x40 : OUTEVT7 drives fixed value of corresponding bit 0x80 : OUTEVT8 drives fixed value of corresponding bit 0x3 : OUTEVT1,OUTEVT2 drive the sequence from respective bit 0x7 : OUTEVT1, OUTEVT2,OUTEVT3 drive the sequence from respective bit 0xF : OUTEVT1, OUTEVT2,OUTEVT3,OUTEVT4 drive the sequence from respective bit 0x6 : OUTEVT2,OUTEVT3 drive the sequence from respective bit 0xE : OUTEVT2,OUTEVT3,OUTEVT4 drive the sequence from respective bit 0xC : OUTEVT3,OUTEVT4 drive the sequence from respective bit Any such combinations of OUTEVTn are allowed depending upon sequence configuration settings. Only few depicted here. Reset type: SYSRSn |
| 7-0 | BLK1SIG1 | R/W | 0h | This word shows the association of the WADI output related BLK0-SIG1 to the related OUTEVTn. If the association bit is set then upon sequence word being active the corresponding bit of sequence word drives the related O/P. Where each bit is related to respective output event. Multiple bits can be set to seek the sequence as configured. 0x0 : No Safe state sequencer override. 0x1 : OUTEVT1 drives fixed value of corresponding bit 0x2 : OUTEVT2 drives fixed value of corresponding bit 0x4 : OUTEVT3drives fixed value of corresponding bit 0x8 : OUTEVT4drives fixed value of corresponding bit 0x10 : OUTEVT5 drives fixed value of corresponding bit 0x20 : OUTEVT6 drives fixed value of corresponding bit 0x40 : OUTEVT7 drives fixed value of corresponding bit 0x80 : OUTEVT8 drives fixed value of corresponding bit 0x3 : OUTEVT1,OUTEVT2 drive the sequence from respective bit 0x7 : OUTEVT1, OUTEVT2,OUTEVT3 drive the sequence from respective bit 0xF : OUTEVT1, OUTEVT2,OUTEVT3,OUTEVT4 drive the sequence from respective bit 0x6 : OUTEVT2,OUTEVT3 drive the sequence from respective bit 0xE : OUTEVT2,OUTEVT3,OUTEVT4 drive the sequence from respective bit 0xC : OUTEVT3,OUTEVT4 drive the sequence from respective bit Any such combinations of OUTEVTn are allowed depending upon sequence configuration settings. Only few depicted here. Reset type: SYSRSn |
SSS_BLK3_4OUTSEL is shown in Figure 19-60 and described in Table 19-60.
Return to the Summary Table.
Selects the output events to be muxed for corresponding output, if that output event is active.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| BLK4SIG2 | BLK4SIG1 | BLK3SIG2 | BLK3SIG1 | ||||||||||||||||||||||||||||
| R/W-0h | R/W-0h | R/W-0h | R/W-0h | ||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-24 | BLK4SIG2 | R/W | 0h | This word shows the association of the WADI output related BLK4-SIG2 to the related OUTEVTn. If the association bit is set then upon sequence word being active the corresponding bit of sequence word drives the related O/P. Where each bit is related to respective output event. Multiple bits can be set to seek the sequence as configured. 0x0 : No Safe state sequencer override. 0x1 : OUTEVT1 drives fixed value of corresponding bit 0x2 : OUTEVT2 drives fixed value of corresponding bit 0x4 : OUTEVT3drives fixed value of corresponding bit 0x8 : OUTEVT4drives fixed value of corresponding bit 0x10 : OUTEVT5 drives fixed value of corresponding bit 0x20 : OUTEVT6 drives fixed value of corresponding bit 0x40 : OUTEVT7 drives fixed value of corresponding bit 0x80 : OUTEVT8 drives fixed value of corresponding bit 0x3 : OUTEVT1,OUTEVT2 drive the sequence from respective bit 0x7 : OUTEVT1, OUTEVT2,OUTEVT3 drive the sequence from respective bit 0xF : OUTEVT1, OUTEVT2,OUTEVT3,OUTEVT4 drive the sequence from respective bit 0x6 : OUTEVT2,OUTEVT3 drive the sequence from respective bit 0xE : OUTEVT2,OUTEVT3,OUTEVT4 drive the sequence from respective bit 0xC : OUTEVT3,OUTEVT4 drive the sequence from respective bit Any such combinations of OUTEVTn are allowed depending upon sequence configuration settings. Only few depicted here. Reset type: SYSRSn |
| 23-16 | BLK4SIG1 | R/W | 0h | This word shows the association of the WADI output related BLK4-SIG1 to the related OUTEVTn. If the association bit is set then upon sequence word being active the corresponding bit of sequence word drives the related O/P. Where each bit is related to respective output event. Multiple bits can be set to seek the sequence as configured. 0x0 : No Safe state sequencer override. 0x1 : OUTEVT1 drives fixed value of corresponding bit 0x2 : OUTEVT2 drives fixed value of corresponding bit 0x4 : OUTEVT3drives fixed value of corresponding bit 0x8 : OUTEVT4drives fixed value of corresponding bit 0x10 : OUTEVT5 drives fixed value of corresponding bit 0x20 : OUTEVT6 drives fixed value of corresponding bit 0x40 : OUTEVT7 drives fixed value of corresponding bit 0x80 : OUTEVT8 drives fixed value of corresponding bit 0x3 : OUTEVT1,OUTEVT2 drive the sequence from respective bit 0x7 : OUTEVT1, OUTEVT2,OUTEVT3 drive the sequence from respective bit 0xF : OUTEVT1, OUTEVT2,OUTEVT3,OUTEVT4 drive the sequence from respective bit 0x6 : OUTEVT2,OUTEVT3 drive the sequence from respective bit 0xE : OUTEVT2,OUTEVT3,OUTEVT4 drive the sequence from respective bit 0xC : OUTEVT3,OUTEVT4 drive the sequence from respective bit Any such combinations of OUTEVTn are allowed depending upon sequence configuration settings. Only few depicted here. Reset type: SYSRSn |
| 15-8 | BLK3SIG2 | R/W | 0h | This word shows the association of the WADI output related BLK3-SIG2 to the related OUTEVTn. If the association bit is set then upon sequence word being active the corresponding bit of sequence word drives the related O/P. Where each bit is related to respective output event. Multiple bits can be set to seek the sequence as configured. 0x0 : No Safe state sequencer override. 0x1 : OUTEVT1 drives fixed value of corresponding bit 0x2 : OUTEVT2 drives fixed value of corresponding bit 0x4 : OUTEVT3drives fixed value of corresponding bit 0x8 : OUTEVT4drives fixed value of corresponding bit 0x10 : OUTEVT5 drives fixed value of corresponding bit 0x20 : OUTEVT6 drives fixed value of corresponding bit 0x40 : OUTEVT7 drives fixed value of corresponding bit 0x80 : OUTEVT8 drives fixed value of corresponding bit 0x3 : OUTEVT1,OUTEVT2 drive the sequence from respective bit 0x7 : OUTEVT1, OUTEVT2,OUTEVT3 drive the sequence from respective bit 0xF : OUTEVT1, OUTEVT2,OUTEVT3,OUTEVT4 drive the sequence from respective bit 0x6 : OUTEVT2,OUTEVT3 drive the sequence from respective bit 0xE : OUTEVT2,OUTEVT3,OUTEVT4 drive the sequence from respective bit 0xC : OUTEVT3,OUTEVT4 drive the sequence from respective bit Any such combinations of OUTEVTn are allowed depending upon sequence configuration settings. Only few depicted here. Reset type: SYSRSn |
| 7-0 | BLK3SIG1 | R/W | 0h | This word shows the association of the WADI output related BLK3-SIG1 to the related OUTEVTn. If the association bit is set then upon sequence word being active the corresponding bit of sequence word drives the related O/P. Where each bit is related to respective output event. Multiple bits can be set to seek the sequence as configured. 0x0 : No Safe state sequencer override. 0x1 : OUTEVT1 drives fixed value of corresponding bit 0x2 : OUTEVT2 drives fixed value of corresponding bit 0x4 : OUTEVT3drives fixed value of corresponding bit 0x8 : OUTEVT4drives fixed value of corresponding bit 0x10 : OUTEVT5 drives fixed value of corresponding bit 0x20 : OUTEVT6 drives fixed value of corresponding bit 0x40 : OUTEVT7 drives fixed value of corresponding bit 0x80 : OUTEVT8 drives fixed value of corresponding bit 0x3 : OUTEVT1,OUTEVT2 drive the sequence from respective bit 0x7 : OUTEVT1, OUTEVT2,OUTEVT3 drive the sequence from respective bit 0xF : OUTEVT1, OUTEVT2,OUTEVT3,OUTEVT4 drive the sequence from respective bit 0x6 : OUTEVT2,OUTEVT3 drive the sequence from respective bit 0xE : OUTEVT2,OUTEVT3,OUTEVT4 drive the sequence from respective bit 0xC : OUTEVT3,OUTEVT4 drive the sequence from respective bit Any such combinations of OUTEVTn are allowed depending upon sequence configuration settings. Only few depicted here. Reset type: SYSRSn |
SSS_OUTEVT1LINKCFG is shown in Figure 19-61 and described in Table 19-61.
Return to the Summary Table.
Output event1 configuration that Links it to other Output events.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| RESERVED | |||||||||||||||
| R-0h | |||||||||||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | OUTEVT1LINK | ||||||||||||||
| R-0h | R/W-0h | ||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-8 | RESERVED | R | 0h | Reserved |
| 7-0 | OUTEVT1LINK | R/W | 0h | This enables the configuration of linking EVTOUTn to EVTOUT1 0b0000_000X : No OUTEVT linking 0b0000_0010 : OUTEVT1 is linked to OUTEVT2 as its previous step in sequence this is used for 2 step cyclical sequence. 0b0000_0100 : OUTEVT1 is linked to OUTEVT3 as its previous step in sequence this is used for 3 step cyclical sequence. 0b0000_1000 : OUTEVT1 is linked to OUTEVT4 as its previous step in sequence this is used for 4 step cyclical sequence. 0b0001_0000 : OUTEVT1 is linked to OUTEVT5 as its previous step in sequence this is used for 5 step cyclical sequence. 0b0010_0000 : OUTEVT1 is linked to OUTEVT6 as its previous step in sequence this is used for 6 step cyclical sequence. 0b0100_0000 : OUTEVT1 is linked to OUTEVT7 as its previous step in sequence this is used for 7 step cyclical sequence. 0b1000_0000 : OUTEVT1 is linked to OUTEVT8 as its previous step in sequence this is used for 8 step cyclical sequence. Reset type: SYSRSn |
SSS_OUTEVT2LINKCFG is shown in Figure 19-62 and described in Table 19-62.
Return to the Summary Table.
Output event2 configuration that Links it to other Output events.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| RESERVED | |||||||||||||||
| R-0h | |||||||||||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | OUTEVT2LINK | ||||||||||||||
| R-0h | R/W-0h | ||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-8 | RESERVED | R | 0h | Reserved |
| 7-0 | OUTEVT2LINK | R/W | 0h | This enables the configuration of linking EVTOUTn to EVTOUT2 0b0000_0000 : No OUTEVTn linking 0b0000_0001 : OUTEVT2 is linked to OUTEVT1 as its previous step in sequence this is used for multi step sequence. 0b0000_0100 : OUTEVT2 is linked to OUTEVT3 as its previous step in sequence this is used for 2 step cyclical sequence. Other : No OUTEVTn linking Reset type: SYSRSn |
SSS_OUTEVT3LINKCFG is shown in Figure 19-63 and described in Table 19-63.
Return to the Summary Table.
Output event3 configuration that Links it to other Output events.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| RESERVED | |||||||||||||||
| R-0h | |||||||||||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | OUTEVT3LINK | ||||||||||||||
| R-0h | R/W-0h | ||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-8 | RESERVED | R | 0h | Reserved |
| 7-0 | OUTEVT3LINK | R/W | 0h | This enables the configuration of linking EVTOUTn to EVTOUT3 0b0000_0000 : No OUTEVTn linking 0b0000_0010 : OUTEVT3 is linked to OUTEVT2 as its previous step in sequence this is used for multi step sequence. 0b0000_1000 : OUTEVT3 is linked to OUTEVT4 as its previous step in sequence this is used for 2 step cyclical sequence. Other : No OUTEVTn dependency Reset type: SYSRSn |
SSS_OUTEVT4LINKCFG is shown in Figure 19-64 and described in Table 19-64.
Return to the Summary Table.
Output event4 configuration that Links it to other Output events.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| RESERVED | |||||||||||||||
| R-0h | |||||||||||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | OUTEVT4LINK | ||||||||||||||
| R-0h | R/W-0h | ||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-8 | RESERVED | R | 0h | Reserved |
| 7-0 | OUTEVT4LINK | R/W | 0h | This enables the configuration of linking EVTOUTn to EVTOUT4 0b0000_0000 : No OUTEVTn linking 0b0000_0100 : OUTEVT4 is linked to OUTEVT3 as its previous step in sequence this is used for multi step sequence. Other : No OUTEVTn dependency Reset type: SYSRSn |
SSS_OUTEVT5LINKCFG is shown in Figure 19-65 and described in Table 19-65.
Return to the Summary Table.
Output event5 configuration that Links it to other Output events.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| RESERVED | |||||||||||||||
| R-0h | |||||||||||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | OUTEVT5LINK | ||||||||||||||
| R-0h | R/W-0h | ||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-8 | RESERVED | R | 0h | Reserved |
| 7-0 | OUTEVT5LINK | R/W | 0h | This enables the configuration of linking EVTOUTn to EVTOUT5 0b0000_0000 : No OUTEVTn linking 0b0000_1000 : OUTEVT5 is linked to OUTEVT4 as its previous step in sequence this is used for multi step sequence. 0b0010_0000 : OUTEVT5 is linked to OUTEVT6 as its previous step in sequence this is used for 2 step cyclical sequence. 0b0100_0000 : OUTEVT5 is linked to OUTEVT6 as its previous step in sequence this is used for 3 step cyclical sequence. 0b1000_0000 : OUTEVT5 is linked to OUTEVT6 as its previous step in sequence this is used for 4 step cyclical sequence. Other : No OUTEVTn dependency Reset type: SYSRSn |
SSS_OUTEVT6LINKCFG is shown in Figure 19-66 and described in Table 19-66.
Return to the Summary Table.
Output event6 configuration that Links it to other Output events.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| RESERVED | |||||||||||||||
| R-0h | |||||||||||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | OUTEVT6LINK | ||||||||||||||
| R-0h | R/W-0h | ||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-8 | RESERVED | R | 0h | Reserved |
| 7-0 | OUTEVT6LINK | R/W | 0h | This enables the configuration of linking EVTOUTn to EVTOUT6 0b0000_0000 : No OUTEVTn linking 0b0001_0000 : OUTEVT6 is linked to OUTEVT5 as its previous step in sequence this is used for multi step sequence. 0b0100_0000 : OUTEVT6 is linked to OUTEVT7 as its previous step in sequence this is used for 2 step cyclical sequence. Other : No OUTEVTn dependency Reset type: SYSRSn |
SSS_OUTEVT7LINKCFG is shown in Figure 19-67 and described in Table 19-67.
Return to the Summary Table.
Output event7 configuration that Links it to other Output events.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| RESERVED | |||||||||||||||
| R-0h | |||||||||||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | OUTEVT7LINK | ||||||||||||||
| R-0h | R/W-0h | ||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-8 | RESERVED | R | 0h | Reserved |
| 7-0 | OUTEVT7LINK | R/W | 0h | This enables the configuration of linking EVTOUTn to EVTOUT7 0b0000_0000 : No OUTEVTn linking 0b0010_0000 : OUTEVT7 is linked to OUTEVT6 as its previous step in sequence this is used for multi step sequence. 0b1000_0000 : OUTEVT7 is linked to OUTEVT8 as its previous step in sequence this is used for 2 step cyclical sequence. Other : No OUTEVTn dependency Reset type: SYSRSn |
SSS_OUTEVT8LINKCFG is shown in Figure 19-68 and described in Table 19-68.
Return to the Summary Table.
Output event8 configuration that Links it to other Output events.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | OUT8LINK | ||||||||||||||||||||||||||||||
| R-0h | R/W-0h | ||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-8 | RESERVED | R | 0h | Reserved |
| 7-0 | OUT8LINK | R/W | 0h | This enables the configuration of linking EVTOUTn to EVTOUT8 0b0000_0000 : No OUTEVTn linking 0b0100_0000 : OUTEVT8 is linked to Sequence OUTEVT7 as its previous step in sequence this is used for multi step sequence. Other : No OUTEVTn dependency Reset type: SYSRSn |
SSS_EVT1CFG is shown in Figure 19-69 and described in Table 19-69.
Return to the Summary Table.
Event1 used by SSS to trigger safe state sequence as per safe state sequencer configuration
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | EVT1 | ||||||||||||||||||||||||||||||
| R/W-0h | R/W-0h | ||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-8 | RESERVED | R/W | 0h | Reserved |
| 7-0 | EVT1 | R/W | 0h | Event1 is compared with SSS_TRIGEVT is identification of match condition for set of bits configured '1' by user. Assertion of event is active high condition hence bits programmed '0' in this word have no effect of respective bits in SSS_TRIGEVT Once the match for the word is determined it either triggers SSS or advances to next trigger event as configured by SSS_TRIGEVT1_4CFG or SSS_TRIGEVT5_8CFG. [0] : SIG1 & SIGTOSIG event aggregation of block1 [1] : SIG2 event aggregation of block1 [2] : SIG1 & SIGTOSIG event aggregation of block2 [3] : SIG2 event aggregation of block2 [4] : SIG1 & SIGTOSIG event aggregation of block3 [5] : SIG2 event aggregation of block3 [6] : SIG1 & SIGTOSIG event aggregation of block4 [7] : SIG2 event aggregation of block4 Reset type: SYSRSn |
SSS_EVT2CFG is shown in Figure 19-70 and described in Table 19-70.
Return to the Summary Table.
Event2 used by SSS to trigger safe state sequence as per safe state sequencer configuration
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | EVT2 | ||||||||||||||||||||||||||||||
| R/W-0h | R/W-0h | ||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-8 | RESERVED | R/W | 0h | Reserved |
| 7-0 | EVT2 | R/W | 0h | Event2 is compared with SSS_TRIGEVT is identification of match condition for set of bits configured '1' by user. Assertion of event is active high condition hence bits programmed '0' in this word have no effect of respective bits in SSS_TRIGEVT Once the match for the word is determined it either triggers SSS or advances to next trigger event as configured by SSS_TRIGEVT1_4CFG or SSS_TRIGEVT5_8CFG. [0] : SIG1 & SIGTOSIG event aggregation of block1 [1] : SIG2 event aggregation of block1 [2] : SIG1 & SIGTOSIG event aggregation of block2 [3] : SIG2 event aggregation of block2 [4] : SIG1 & SIGTOSIG event aggregation of block3 [5] : SIG2 event aggregation of block3 [6] : SIG1 & SIGTOSIG event aggregation of block4 [7] : SIG2 event aggregation of block4 Reset type: SYSRSn |
SSS_EVT3CFG is shown in Figure 19-71 and described in Table 19-71.
Return to the Summary Table.
Event3 used by SSS to trigger safe state sequence as per safe state sequencer configuration
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| EVT3_BLK5_TO_16 | EVT3 | ||||||||||||||||||||||||||||||
| R/W-0h | R/W-0h | ||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-8 | EVT3_BLK5_TO_16 | R/W | 0h | [8] : SIG1 & SIGTOSIG event aggregation of block5 [9] : SIG2 event aggregation of block5 [10] : SIG1 & SIGTOSIG event aggregation of block6 [11] : SIG2 event aggregation of block6 [12] : SIG1 & SIGTOSIG event aggregation of block7 [13] : SIG2 event aggregation of block7 [14] : SIG1 & SIGTOSIG event aggregation of block8 [15] : SIG2 event aggregation of block8 [16] : SIG1 & SIGTOSIG event aggregation of block9 [17] : SIG2 event aggregation of block9 [18] : SIG1 & SIGTOSIG event aggregation of block10 [19] : SIG2 event aggregation of block10 [20] : SIG1 & SIGTOSIG event aggregation of block11 [21] : SIG2 event aggregation of block11 [22] : SIG1 & SIGTOSIG event aggregation of block12 [23] : SIG2 event aggregation of block12 [24] : SIG1 & SIGTOSIG event aggregation of block13 [25] : SIG2 event aggregation of block13 [26] : SIG1 & SIGTOSIG event aggregation of block14 [27] : SIG2 event aggregation of block14 [28] : SIG1 & SIGTOSIG event aggregation of block15 [29] : SIG2 event aggregation of block15 [30] : SIG1 & SIGTOSIG event aggregation of block16 [31] : SIG2 event aggregation of block16 Reset type: SYSRSn |
| 7-0 | EVT3 | R/W | 0h | Event3 is compared with SSS_TRIGEVT is identification of match condition for set of bits configured '1' by user. Assertion of event is active high condition hence bits programmed '0' in this word have no effect of respective bits in SSS_TRIGEVT Once the match for the word is determined it either triggers SSS or advances to next trigger event as configured by SSS_TRIGEVT1_4CFG or SSS_TRIGEVT5_8CFG. [0] : SIG1 & SIGTOSIG event aggregation of block1 [1] : SIG2 event aggregation of block1 [2] : SIG1 & SIGTOSIG event aggregation of block2 [3] : SIG2 event aggregation of block2 [4] : SIG1 & SIGTOSIG event aggregation of block3 [5] : SIG2 event aggregation of block3 [6] : SIG1 & SIGTOSIG event aggregation of block4 [7] : SIG2 event aggregation of block4 Reset type: SYSRSn |
SSS_EVT4CFG is shown in Figure 19-72 and described in Table 19-72.
Return to the Summary Table.
Event4 used by SSS to trigger safe state sequence as per safe state sequencer configuration
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| EVT4_BLK5_TO_16 | EVT4 | ||||||||||||||||||||||||||||||
| R/W-0h | R/W-0h | ||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-8 | EVT4_BLK5_TO_16 | R/W | 0h | [8] : SIG1 & SIGTOSIG event aggregation of block5 [9] : SIG2 event aggregation of block5 [10] : SIG1 & SIGTOSIG event aggregation of block6 [11] : SIG2 event aggregation of block6 [12] : SIG1 & SIGTOSIG event aggregation of block7 [13] : SIG2 event aggregation of block7 [14] : SIG1 & SIGTOSIG event aggregation of block8 [15] : SIG2 event aggregation of block8 [16] : SIG1 & SIGTOSIG event aggregation of block9 [17] : SIG2 event aggregation of block9 [18] : SIG1 & SIGTOSIG event aggregation of block10 [19] : SIG2 event aggregation of block10 [20] : SIG1 & SIGTOSIG event aggregation of block11 [21] : SIG2 event aggregation of block11 [22] : SIG1 & SIGTOSIG event aggregation of block12 [23] : SIG2 event aggregation of block12 [24] : SIG1 & SIGTOSIG event aggregation of block13 [25] : SIG2 event aggregation of block13 [26] : SIG1 & SIGTOSIG event aggregation of block14 [27] : SIG2 event aggregation of block14 [28] : SIG1 & SIGTOSIG event aggregation of block15 [29] : SIG2 event aggregation of block15 [30] : SIG1 & SIGTOSIG event aggregation of block16 [31] : SIG2 event aggregation of block16 Reset type: SYSRSn |
| 7-0 | EVT4 | R/W | 0h | Event4 is compared with SSS_TRIGEVT is identification of match condition for set of bits configured '1' by user. Assertion of event is active high condition hence bits programmed '0' in this word have no effect of respective bits in SSS_TRIGEVT Once the match for the word is determined it either triggers SSS or advances to next trigger event as configured by SSS_TRIGEVT1_4CFG or SSS_TRIGEVT5_8CFG. [0] : SIG1 & SIGTOSIG event aggregation of block1 [1] : SIG2 event aggregation of block1 [2] : SIG1 & SIGTOSIG event aggregation of block2 [3] : SIG2 event aggregation of block2 [4] : SIG1 & SIGTOSIG event aggregation of block3 [5] : SIG2 event aggregation of block3 [6] : SIG1 & SIGTOSIG event aggregation of block4 [7] : SIG2 event aggregation of block4 Reset type: SYSRSn |
SSS_TRIGEVT1_4CFG is shown in Figure 19-73 and described in Table 19-73.
Return to the Summary Table.
Allows individual, sequenced and tandem use of event words to trigger the safe sequence
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| RESERVED | TRIG_EVT4CFG | RESERVED | TRIG_EVT3CFG | ||||||||||||
| R-0h | R/W-0h | R-0h | R/W-0h | ||||||||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | TRIG_EVT2CFG | RESERVED | TRIG_EVT1CFG | ||||||||||||
| R-0h | R/W-0h | R-0h | R/W-0h | ||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-28 | RESERVED | R | 0h | Reserved |
| 27-24 | TRIG_EVT4CFG | R/W | 0h | Based on configured value the Event 4 is used for trigger as independent trigger or in sequence with other words 0x0 : Event 4 is not used for any trigger 0x1 : Event 4 is independently used for trigger 0x9 : After Event 4 match sequence check moves to Event 5 is matched before next step. For 4 trigger event system this defaults to 0x1 i.e. triggers the sequencer if configured Any other value : Event 4 is not used for any trigger Reset type: SYSRSn |
| 23-20 | RESERVED | R | 0h | Reserved |
| 19-16 | TRIG_EVT3CFG | R/W | 0h | Based on configured value the Event 3 is used for trigger as independent trigger or in sequence with other words 0x0 : Event 3 is not used for any trigger 0x1 : Event 3 is independently used for trigger 0x9 : After Event 3 match sequence check moves to Event 4 is matched before next step Any other value : Event 3 is not used for any trigger Reset type: SYSRSn |
| 15-12 | RESERVED | R | 0h | Reserved |
| 11-8 | TRIG_EVT2CFG | R/W | 0h | Based on configured value the Event 2 is used for trigger as independent trigger or in sequence with other words 0x0 : Event 2 is not used for any trigger 0x1 : Event 2 is independently used for trigger 0x9 : After Event 2 match sequence check moves to Event 3 is matched before next step Any other value : Event 2 is not used for any trigger Reset type: SYSRSn |
| 7-4 | RESERVED | R | 0h | Reserved |
| 3-0 | TRIG_EVT1CFG | R/W | 0h | Based on configured value the Event 1 is used for trigger as independent trigger or in sequence with other words 0x0 : Event 1 is not used for any trigger 0x1 : Event 1 is independently used for trigger 0x9 : After Event 1 match sequence check moves to Event 2 is matched before next step Any other value : Event 1 is not used for any trigger Reset type: SYSRSn |
SSS_BLKSOUTEVT1CFG is shown in Figure 19-74 and described in Table 19-74.
Return to the Summary Table.
Output event1 used by SSS to drive WADI outputs as per Sequence configuration.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | OUTEVT1 | ||||||||||||||||||||||||||||||
| R/W-0h | R/W-0h | ||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-8 | RESERVED | R/W | 0h | Reserved |
| 7-0 | OUTEVT1 | R/W | 0h | Output on event 1 (OUTEVT1) provides value to be applied on respective signal output when selected. Bits selectively drive the corresponding output line. [0] : SIG1 output override of block1 [1] : SIG2 output override of block1 [2] : SIG1 output override of block2 [3] : SIG2 output override of block2 [4] : SIG1 output override of block3 [5] : SIG2 output override of block3 [6] : SIG1 output override of block4 [7] : SIG2 output override of block4 Reset type: SYSRSn |
SSS_BLKSOUTEVT2CFG is shown in Figure 19-75 and described in Table 19-75.
Return to the Summary Table.
Output event2 used by SSS to drive WADI outputs as per Sequence configuration.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | OUTEVT2 | ||||||||||||||||||||||||||||||
| R/W-0h | R/W-0h | ||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-8 | RESERVED | R/W | 0h | Reserved |
| 7-0 | OUTEVT2 | R/W | 0h | Output on event 2(OUTEVT2) provides value to be applied on respective signal output when selected. Bits selectively drive the corresponding output line. [0] : SIG1 output override of block1 [1] : SIG2 output override of block1 [2] : SIG1 output override of block2 [3] : SIG2 output override of block2 [4] : SIG1 output override of block3 [5] : SIG2 output override of block3 [6] : SIG1 output override of block4 [7] : SIG2 output override of block4 Reset type: SYSRSn |
SSS_BLKSOUTEVT3CFG is shown in Figure 19-76 and described in Table 19-76.
Return to the Summary Table.
Output event3 used by SSS to drive WADI outputs as per Sequence configuration.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | OUTEVT3 | ||||||||||||||||||||||||||||||
| R/W-0h | R/W-0h | ||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-8 | RESERVED | R/W | 0h | Reserved |
| 7-0 | OUTEVT3 | R/W | 0h | Output on event 3(OUTEVT3) provides value to be applied on respective signal output when selected. Bits selectively drive the corresponding output line. [0] : SIG1 output override of block1 [1] : SIG2 output override of block1 [2] : SIG1 output override of block2 [3] : SIG2 output override of block2 [4] : SIG1 output override of block3 [5] : SIG2 output override of block3 [6] : SIG1 output override of block4 [7] : SIG2 output override of block4 Reset type: SYSRSn |
SSS_BLKSOUTEVT4CFG is shown in Figure 19-77 and described in Table 19-77.
Return to the Summary Table.
Output event4 used by SSS to drive WADI outputs as per Sequence configuration.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | OUTEVT4 | ||||||||||||||||||||||||||||||
| R/W-0h | R/W-0h | ||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-8 | RESERVED | R/W | 0h | Reserved |
| 7-0 | OUTEVT4 | R/W | 0h | Output on event 4(OUTEVT4) provides value to be applied on respective signal output when selected. Bits selectively drive the corresponding output line. [0] : SIG1 output override of block1 [1] : SIG2 output override of block1 [2] : SIG1 output override of block2 [3] : SIG2 output override of block2 [4] : SIG1 output override of block3 [5] : SIG2 output override of block3 [6] : SIG1 output override of block4 [7] : SIG2 output override of block4 Reset type: SYSRSn |
SSS_OUTEVT1TRIGCFG is shown in Figure 19-78 and described in Table 19-78.
Return to the Summary Table.
Output event1 configuration that drives which trigger or link make output event active
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
| RESERVED | |||||||
| R-0h | |||||||
| 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| RESERVED | |||||||
| R-0h | |||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
| RESERVED | |||||||
| R-0h | |||||||
| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| EVT8TRIG | EVT7TRIG | EVT6TRIG | EVT5TRIG | EVT4TRIG | EVT3TRIG | EVT2TRIG | EVT1TRIG |
| R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h |
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-8 | RESERVED | R | 0h | Reserved |
| 7 | EVT8TRIG | R/W | 0h | When this control is set '1', then upon Event 8 Trigger assertion OUTEVT1 is set and the duration based on time defined at SSS_OUTEVT1DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 8 Trigger has no effect. Reset type: SYSRSn |
| 6 | EVT7TRIG | R/W | 0h | When this control is set '1', then upon Event 7 Trigger assertion OUTEVT1 is set and the duration based on time defined at SSS_OUTEVT1DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 7 Trigger has no effect. Reset type: SYSRSn |
| 5 | EVT6TRIG | R/W | 0h | When this control is set '1', then upon Event 6 Trigger assertion OUTEVT1 is set and the duration based on time defined at SSS_OUTEVT1DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 6 Trigger has no effect. Reset type: SYSRSn |
| 4 | EVT5TRIG | R/W | 0h | When this control is set '1', then upon Event 5 Trigger assertion OUTEVT1 is set and the duration based on time defined at SSS_OUTEVT1DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 5 Trigger has no effect. Reset type: SYSRSn |
| 3 | EVT4TRIG | R/W | 0h | When this control is set '1', then upon Event 4 Trigger assertion OUTEVT1 is set and the duration based on time defined at SSS_OUTEVT1DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 4 Trigger has no effect. Reset type: SYSRSn |
| 2 | EVT3TRIG | R/W | 0h | When this control is set '1', then upon Event 3 Trigger assertion OUTEVT1 is set and the duration based on time defined at SSS_OUTEVT1DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 3 Trigger has no effect. Reset type: SYSRSn |
| 1 | EVT2TRIG | R/W | 0h | When this control is set '1', then upon Event 2 Trigger assertion OUTEVT1 is set and the duration based on time defined at SSS_OUTEVT1DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 2 Trigger has no effect. Reset type: SYSRSn |
| 0 | EVT1TRIG | R/W | 0h | When this control is set '1', then upon Event 1 Trigger assertion OUTEVT1 is set and the duration based on time defined at SSS_OUTEVT1DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 1 Trigger has no effect. Reset type: SYSRSn |
SSS_OUTEVT2TRIGCFG is shown in Figure 19-79 and described in Table 19-79.
Return to the Summary Table.
Output event2 configuration that drives which trigger or link make sequence word active
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
| RESERVED | |||||||
| R-0h | |||||||
| 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| RESERVED | |||||||
| R-0h | |||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
| RESERVED | |||||||
| R-0h | |||||||
| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| EVT8TRIG | EVT7TRIG | EVT6TRIG | EVT5TRIG | EVT4TRIG | EVT3TRIG | EVT2TRIG | EVT1TRIG |
| R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h |
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-8 | RESERVED | R | 0h | Reserved |
| 7 | EVT8TRIG | R/W | 0h | When this control is set '1', then upon Event 8 Trigger assertion OUTEVT2 is set and the duration based on time defined at SSS_OUTEVT1DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 8 Trigger has no effect. Reset type: SYSRSn |
| 6 | EVT7TRIG | R/W | 0h | When this control is set '1', then upon Event 7 Trigger assertion OUTEVT2 is set and the duration based on time defined at SSS_OUTEVT1DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 7 Trigger has no effect. Reset type: SYSRSn |
| 5 | EVT6TRIG | R/W | 0h | When this control is set '1', then upon Event 6 Trigger assertion OUTEVT2 is set and the duration based on time defined at SSS_OUTEVT1DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 6 Trigger has no effect. Reset type: SYSRSn |
| 4 | EVT5TRIG | R/W | 0h | When this control is set '1', then upon Event 5 Trigger assertion OUTEVT2 is set and the duration based on time defined at SSS_OUTEVT1DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 5 Trigger has no effect. Reset type: SYSRSn |
| 3 | EVT4TRIG | R/W | 0h | When this control is set '1', then upon Event 4 Trigger assertion OUTEVT2 is set and the duration based on time defined at SSS_OUTEVT1DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 4 Trigger has no effect. Reset type: SYSRSn |
| 2 | EVT3TRIG | R/W | 0h | When this control is set '1', then upon Event 3 Trigger assertion OUTEVT2 is set and the duration based on time defined at SSS_OUTEVT1DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 3 Trigger has no effect. Reset type: SYSRSn |
| 1 | EVT2TRIG | R/W | 0h | When this control is set '1', then upon Event 2 Trigger assertion OUTEVT2 is set and the duration based on time defined at SSS_OUTEVT1DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 2 Trigger has no effect. Reset type: SYSRSn |
| 0 | EVT1TRIG | R/W | 0h | When this control is set '1', then upon Event 1 Trigger assertion OUTEVT2 is set and the duration based on time defined at SSS_OUTEVT1DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 1 Trigger has no effect. Reset type: SYSRSn |
SSS_OUTEVT3TRIGCFG is shown in Figure 19-80 and described in Table 19-80.
Return to the Summary Table.
Output event3 configuration that drives which trigger or link make output event active
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
| RESERVED | |||||||
| R-0h | |||||||
| 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| RESERVED | |||||||
| R-0h | |||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
| RESERVED | |||||||
| R-0h | |||||||
| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| EVT8TRIG | EVT7TRIG | EVT6TRIG | EVT5TRIG | EVT4TRIG | EVT3TRIG | EVT2TRIG | EVT1TRIG |
| R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h |
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-8 | RESERVED | R | 0h | Reserved |
| 7 | EVT8TRIG | R/W | 0h | When this control is set '1', then upon Event 8 Trigger assertion OUTEVT3 is set and the duration based on time defined at SSS_OUTEVT3DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 8 Trigger has no effect. Reset type: SYSRSn |
| 6 | EVT7TRIG | R/W | 0h | When this control is set '1', then upon Event 7 Trigger assertion OUTEVT3 is set and the duration based on time defined at SSS_OUTEVT3DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 7 Trigger has no effect. Reset type: SYSRSn |
| 5 | EVT6TRIG | R/W | 0h | When this control is set '1', then upon Event 6 Trigger assertion OUTEVT3 is set and the duration based on time defined at SSS_OUTEVT3DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 6 Trigger has no effect. Reset type: SYSRSn |
| 4 | EVT5TRIG | R/W | 0h | When this control is set '1', then upon Event 5 Trigger assertion OUTEVT3 is set and the duration based on time defined at SSS_OUTEVT3DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 5 Trigger has no effect. Reset type: SYSRSn |
| 3 | EVT4TRIG | R/W | 0h | When this control is set '1', then upon Event 4 Trigger assertion OUTEVT3 is set and the duration based on time defined at SSS_OUTEVT3DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 4 Trigger has no effect. Reset type: SYSRSn |
| 2 | EVT3TRIG | R/W | 0h | When this control is set '1', then upon Event 3 Trigger assertion OUTEVT3 is set and the duration based on time defined at SSS_OUTEVT3DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 3 Trigger has no effect. Reset type: SYSRSn |
| 1 | EVT2TRIG | R/W | 0h | When this control is set '1', then upon Event 2 Trigger assertion OUTEVT3 is set and the duration based on time defined at SSS_OUTEVT3DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 2 Trigger has no effect. Reset type: SYSRSn |
| 0 | EVT1TRIG | R/W | 0h | When this control is set '1', then upon Event 1 Trigger assertion OUTEVT3 is set and the duration based on time defined at SSS_OUTEVT3DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 1 Trigger has no effect. Reset type: SYSRSn |
SSS_OUTEVT4TRIGCFG is shown in Figure 19-81 and described in Table 19-81.
Return to the Summary Table.
Output event4 configuration that drives which trigger or link make output event active
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
| RESERVED | |||||||
| R-0h | |||||||
| 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| RESERVED | |||||||
| R-0h | |||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
| RESERVED | |||||||
| R-0h | |||||||
| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| EVT8TRIG | EVT7TRIG | EVT6TRIG | EVT5TRIG | EVT4TRIG | EVT3TRIG | EVT2TRIG | EVT1TRIG |
| R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h |
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-8 | RESERVED | R | 0h | Reserved |
| 7 | EVT8TRIG | R/W | 0h | When this control is set '1', then upon Event 8 Trigger assertion OUTEVT4 is set and the duration based on time defined at SSS_OUTEVT4DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 8 Trigger has no effect. Reset type: SYSRSn |
| 6 | EVT7TRIG | R/W | 0h | When this control is set '1', then upon Event 7 Trigger assertion OUTEVT4 is set and the duration based on time defined at SSS_OUTEVT4DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 7 Trigger has no effect. Reset type: SYSRSn |
| 5 | EVT6TRIG | R/W | 0h | When this control is set '1', then upon Event 6 Trigger assertion OUTEVT4 is set and the duration based on time defined at SSS_OUTEVT4DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 6 Trigger has no effect. Reset type: SYSRSn |
| 4 | EVT5TRIG | R/W | 0h | When this control is set '1', then upon Event 5 Trigger assertion OUTEVT4 is set and the duration based on time defined at SSS_OUTEVT4DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 5 Trigger has no effect. Reset type: SYSRSn |
| 3 | EVT4TRIG | R/W | 0h | When this control is set '1', then upon Event 4 Trigger assertion OUTEVT4 is set and the duration based on time defined at SSS_OUTEVT4DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 4 Trigger has no effect. Reset type: SYSRSn |
| 2 | EVT3TRIG | R/W | 0h | When this control is set '1', then upon Event 3 Trigger assertion OUTEVT4 is set and the duration based on time defined at SSS_OUTEVT4DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 3 Trigger has no effect. Reset type: SYSRSn |
| 1 | EVT2TRIG | R/W | 0h | When this control is set '1', then upon Event 2 Trigger assertion OUTEVT4 is set and the duration based on time defined at SSS_OUTEVT4DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 2 Trigger has no effect. Reset type: SYSRSn |
| 0 | EVT1TRIG | R/W | 0h | When this control is set '1', then upon Event 1 Trigger assertion OUTEVT4 is set and the duration based on time defined at SSS_OUTEVT4DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 1 Trigger has no effect. Reset type: SYSRSn |
SSS_OUTEVT1DUR is shown in Figure 19-82 and described in Table 19-82.
Return to the Summary Table.
Output event1 configuration that drives delay for applying output
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | TIME | ||||||||||||||||||||||||||||||
| R-0h | R/W-0h | ||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-24 | RESERVED | R | 0h | Reserved |
| 23-0 | TIME | R/W | 0h | Delay count configured is count down to '0' for holding the OUTEVTn active. Upon reaching '0' the OUTEVTn is deactivated and count is reloaded with the configured value for next cyclical round or trigger. 0xFF_FFFF is special value when OUTEVTn is kept active continuously and counter does not count down. This allows defining terminal state of the sequence. Reset type: SYSRSn |
SSS_OUTEVT2DUR is shown in Figure 19-83 and described in Table 19-83.
Return to the Summary Table.
Output event2 configuration that drives delay for applying output
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | TIME | ||||||||||||||||||||||||||||||
| R-0h | R/W-0h | ||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-24 | RESERVED | R | 0h | Reserved |
| 23-0 | TIME | R/W | 0h | Delay count configured is count down to '0' for holding the OUTEVTn active. Upon reaching '0' the OUTEVTn is deactivated and count is reloaded with the configured value for next cyclical round or trigger. 0xFF_FFFF is special value when OUTEVTn is kept active continuously and counter does not count down. This allows defining terminal state of the sequence. Reset type: SYSRSn |
SSS_OUTEVT3DUR is shown in Figure 19-84 and described in Table 19-84.
Return to the Summary Table.
Output event3 configuration that drives delay for applying output
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | TIME | ||||||||||||||||||||||||||||||
| R-0h | R/W-0h | ||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-24 | RESERVED | R | 0h | Reserved |
| 23-0 | TIME | R/W | 0h | Delay count configured is count down to '0' for holding the OUTEVTn active. Upon reaching '0' the OUTEVTn is deactivated and count is reloaded with the configured value for next cyclical round or trigger. 0xFF_FFFF is special value when OUTEVTn is kept active continuously and counter does not count down. This allows defining terminal state of the sequence. Reset type: SYSRSn |
SSS_OUTEVT4DUR is shown in Figure 19-85 and described in Table 19-85.
Return to the Summary Table.
Output event4 configuration that drives delay for applying output
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | TIME | ||||||||||||||||||||||||||||||
| R-0h | R/W-0h | ||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-24 | RESERVED | R | 0h | Reserved |
| 23-0 | TIME | R/W | 0h | Delay count configured is count down to '0' for holding the OUTEVTn active. Upon reaching '0' the OUTEVTn is deactivated and count is reloaded with the configured value for next cyclical round or trigger. 0xFF_FFFF is special value when OUTEVTn is kept active continuously and counter does not count down. This allows defining terminal state of the sequence. Reset type: SYSRSn |
SSS_EVT5CFG is shown in Figure 19-86 and described in Table 19-86.
Return to the Summary Table.
Event5 used by SSS to trigger safe sequence as per safe state sequencer configuration
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| EVT5_BLK5_TO_16 | EVT5 | ||||||||||||||||||||||||||||||
| R/W-0h | R/W-0h | ||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-8 | EVT5_BLK5_TO_16 | R/W | 0h | [8] : SIG1 & SIGTOSIG event aggregation of block5 [9] : SIG2 event aggregation of block5 [10] : SIG1 & SIGTOSIG event aggregation of block6 [11] : SIG2 event aggregation of block6 [12] : SIG1 & SIGTOSIG event aggregation of block7 [13] : SIG2 event aggregation of block7 [14] : SIG1 & SIGTOSIG event aggregation of block8 [15] : SIG2 event aggregation of block8 [16] : SIG1 & SIGTOSIG event aggregation of block9 [17] : SIG2 event aggregation of block9 [18] : SIG1 & SIGTOSIG event aggregation of block10 [19] : SIG2 event aggregation of block10 [20] : SIG1 & SIGTOSIG event aggregation of block11 [21] : SIG2 event aggregation of block11 [22] : SIG1 & SIGTOSIG event aggregation of block12 [23] : SIG2 event aggregation of block12 [24] : SIG1 & SIGTOSIG event aggregation of block13 [25] : SIG2 event aggregation of block13 [26] : SIG1 & SIGTOSIG event aggregation of block14 [27] : SIG2 event aggregation of block14 [28] : SIG1 & SIGTOSIG event aggregation of block15 [29] : SIG2 event aggregation of block15 [30] : SIG1 & SIGTOSIG event aggregation of block16 [31] : SIG2 event aggregation of block16 Reset type: SYSRSn |
| 7-0 | EVT5 | R/W | 0h | Event5 is compared with SSS_TRIGEVT is identification of match condition for set of bits configured '1' by user. Assertion of event is active high condition hence bits programmed '0' in this word have no effect of respective bits in SSS_TRIGEVT Once the match for the word is determined it either triggers SSS or advances to next trigger event as configured by SSS_TRIGEVT1_4CFG or SSS_TRIGEVT5_8CFG. [0] : SIG1 & SIGTOSIG event aggregation of block1 [1] : SIG2 event aggregation of block1 [2] : SIG1 & SIGTOSIG event aggregation of block2 [3] : SIG2 event aggregation of block2 [4] : SIG1 & SIGTOSIG event aggregation of block3 [5] : SIG2 event aggregation of block3 [6] : SIG1 & SIGTOSIG event aggregation of block4 [7] : SIG2 event aggregation of block4 Reset type: SYSRSn |
SSS_EVT6CFG is shown in Figure 19-87 and described in Table 19-87.
Return to the Summary Table.
Event6 used by SSS to trigger safe sequence as per safe state sequencer configuration
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| EVT6_BLK5_TO_16 | EVT6 | ||||||||||||||||||||||||||||||
| R/W-0h | R/W-0h | ||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-8 | EVT6_BLK5_TO_16 | R/W | 0h | [8] : SIG1 & SIGTOSIG event aggregation of block5 [9] : SIG2 event aggregation of block5 [10] : SIG1 & SIGTOSIG event aggregation of block6 [11] : SIG2 event aggregation of block6 [12] : SIG1 & SIGTOSIG event aggregation of block7 [13] : SIG2 event aggregation of block7 [14] : SIG1 & SIGTOSIG event aggregation of block8 [15] : SIG2 event aggregation of block8 [16] : SIG1 & SIGTOSIG event aggregation of block9 [17] : SIG2 event aggregation of block9 [18] : SIG1 & SIGTOSIG event aggregation of block10 [19] : SIG2 event aggregation of block10 [20] : SIG1 & SIGTOSIG event aggregation of block11 [21] : SIG2 event aggregation of block11 [22] : SIG1 & SIGTOSIG event aggregation of block12 [23] : SIG2 event aggregation of block12 [24] : SIG1 & SIGTOSIG event aggregation of block13 [25] : SIG2 event aggregation of block13 [26] : SIG1 & SIGTOSIG event aggregation of block14 [27] : SIG2 event aggregation of block14 [28] : SIG1 & SIGTOSIG event aggregation of block15 [29] : SIG2 event aggregation of block15 [30] : SIG1 & SIGTOSIG event aggregation of block16 [31] : SIG2 event aggregation of block16 Reset type: SYSRSn |
| 7-0 | EVT6 | R/W | 0h | Event6 is compared with SSS_TRIGEVT is identification of match condition for set of bits configured '1' by user. Assertion of event is active high condition hence bits programmed '0' in this word have no effect of respective bits in SSS_TRIGEVT Once the match for the word is determined it either triggers SSS or advances to next trigger event as configured by SSS_TRIGEVT1_4CFG or SSS_TRIGEVT5_8CFG. [0] : SIG1 & SIGTOSIG event aggregation of block1 [1] : SIG2 event aggregation of block1 [2] : SIG1 & SIGTOSIG event aggregation of block2 [3] : SIG2 event aggregation of block2 [4] : SIG1 & SIGTOSIG event aggregation of block3 [5] : SIG2 event aggregation of block3 [6] : SIG1 & SIGTOSIG event aggregation of block4 [7] : SIG2 event aggregation of block4 Reset type: SYSRSn |
SSS_EVT7CFG is shown in Figure 19-88 and described in Table 19-88.
Return to the Summary Table.
Event7 used by SSS to trigger safe state sequence as per safe state sequencer configuration
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| EVT7_BLK5_TO_16 | EVT7 | ||||||||||||||||||||||||||||||
| R/W-0h | R/W-0h | ||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-8 | EVT7_BLK5_TO_16 | R/W | 0h | [8] : SIG1 & SIGTOSIG event aggregation of block5 [9] : SIG2 event aggregation of block5 [10] : SIG1 & SIGTOSIG event aggregation of block6 [11] : SIG2 event aggregation of block6 [12] : SIG1 & SIGTOSIG event aggregation of block7 [13] : SIG2 event aggregation of block7 [14] : SIG1 & SIGTOSIG event aggregation of block8 [15] : SIG2 event aggregation of block8 [16] : SIG1 & SIGTOSIG event aggregation of block9 [17] : SIG2 event aggregation of block9 [18] : SIG1 & SIGTOSIG event aggregation of block10 [19] : SIG2 event aggregation of block10 [20] : SIG1 & SIGTOSIG event aggregation of block11 [21] : SIG2 event aggregation of block11 [22] : SIG1 & SIGTOSIG event aggregation of block12 [23] : SIG2 event aggregation of block12 [24] : SIG1 & SIGTOSIG event aggregation of block13 [25] : SIG2 event aggregation of block13 [26] : SIG1 & SIGTOSIG event aggregation of block14 [27] : SIG2 event aggregation of block14 [28] : SIG1 & SIGTOSIG event aggregation of block15 [29] : SIG2 event aggregation of block15 [30] : SIG1 & SIGTOSIG event aggregation of block16 [31] : SIG2 event aggregation of block16 Reset type: SYSRSn |
| 7-0 | EVT7 | R/W | 0h | Event1 is compared with SSS_TRIGEVT is identification of match condition for set of bits configured '1' by user. Assertion of event is active high condition hence bits programmed '0' in this word have no effect of respective bits in SSS_TRIGEVT Once the match for the word is determined it either triggers SSS or advances to next trigger event as configured by SSS_TRIGEVT1_4CFG or SSS_TRIGEVT5_8CFG. [0] : SIG1 & SIGTOSIG event aggregation of block1 [1] : SIG2 event aggregation of block1 [2] : SIG1 & SIGTOSIG event aggregation of block2 [3] : SIG2 event aggregation of block2 [4] : SIG1 & SIGTOSIG event aggregation of block3 [5] : SIG2 event aggregation of block3 [6] : SIG1 & SIGTOSIG event aggregation of block4 [7] : SIG2 event aggregation of block4 Reset type: SYSRSn |
SSS_EVT8CFG is shown in Figure 19-89 and described in Table 19-89.
Return to the Summary Table.
Event8 used by SSS to trigger safe state sequence as per safe state sequencer configuration
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| EVT8_BLK5_TO_16 | EVT8 | ||||||||||||||||||||||||||||||
| R/W-0h | R/W-0h | ||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-8 | EVT8_BLK5_TO_16 | R/W | 0h | [8] : SIG1 & SIGTOSIG event aggregation of block5 [9] : SIG2 event aggregation of block5 [10] : SIG1 & SIGTOSIG event aggregation of block6 [11] : SIG2 event aggregation of block6 [12] : SIG1 & SIGTOSIG event aggregation of block7 [13] : SIG2 event aggregation of block7 [14] : SIG1 & SIGTOSIG event aggregation of block8 [15] : SIG2 event aggregation of block8 [16] : SIG1 & SIGTOSIG event aggregation of block9 [17] : SIG2 event aggregation of block9 [18] : SIG1 & SIGTOSIG event aggregation of block10 [19] : SIG2 event aggregation of block10 [20] : SIG1 & SIGTOSIG event aggregation of block11 [21] : SIG2 event aggregation of block11 [22] : SIG1 & SIGTOSIG event aggregation of block12 [23] : SIG2 event aggregation of block12 [24] : SIG1 & SIGTOSIG event aggregation of block13 [25] : SIG2 event aggregation of block13 [26] : SIG1 & SIGTOSIG event aggregation of block14 [27] : SIG2 event aggregation of block14 [28] : SIG1 & SIGTOSIG event aggregation of block15 [29] : SIG2 event aggregation of block15 [30] : SIG1 & SIGTOSIG event aggregation of block16 [31] : SIG2 event aggregation of block16 Reset type: SYSRSn |
| 7-0 | EVT8 | R/W | 0h | Event1 is compared with SSS_TRIGEVT is identification of match condition for set of bits configured '1' by user. Assertion of event is active high condition hence bits programmed '0' in this word have no effect of respective bits in SSS_TRIGEVT Once the match for the word is determined it either triggers SSS or advances to next trigger event as configured by SSS_TRIGEVT1_4CFG or SSS_TRIGEVT5_8CFG. [0] : SIG1 & SIGTOSIG event aggregation of block1 [1] : SIG2 event aggregation of block1 [2] : SIG1 & SIGTOSIG event aggregation of block2 [3] : SIG2 event aggregation of block2 [4] : SIG1 & SIGTOSIG event aggregation of block3 [5] : SIG2 event aggregation of block3 [6] : SIG1 & SIGTOSIG event aggregation of block4 [7] : SIG2 event aggregation of block4 Reset type: SYSRSn |
SSS_TRIGEVT5_8CFG is shown in Figure 19-90 and described in Table 19-90.
Return to the Summary Table.
Allows individual, sequenced and tandem use of event words to trigger the safe sequence
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| RESERVED | TRIG_EVT8CFG | RESERVED | TRIG_EVT7CFG | ||||||||||||
| R-0h | R/W-0h | R-0h | R/W-0h | ||||||||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | TRIG_EVT6CFG | RESERVED | TRIG_EVT5CFG | ||||||||||||
| R-0h | R/W-0h | R-0h | R/W-0h | ||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-28 | RESERVED | R | 0h | Reserved |
| 27-24 | TRIG_EVT8CFG | R/W | 0h | Based on configured value the Event 8 is used for trigger as independent trigger or in sequence with other words 0x0 : Event 8 is not used for any trigger 0x1 : Event 8 is independently used for trigger or it is followed up after Word-3 match to trigger SSS Any other value : Event 8 is not used for any trigger Reset type: SYSRSn |
| 23-20 | RESERVED | R | 0h | Reserved |
| 19-16 | TRIG_EVT7CFG | R/W | 0h | Based on configured value the Event 7 is used for trigger as independent trigger or in sequence with other words 0x0 : Event 7 is not used for any trigger 0x1 : Event 7 is independently used for trigger or it is followed up after Word-2 match to trigger SSS 0x9 : After Event 7 match sequence check moves to Event 8 is matched before next step Any other value : Event 7 is not used for any trigger Reset type: SYSRSn |
| 15-12 | RESERVED | R | 0h | Reserved |
| 11-8 | TRIG_EVT6CFG | R/W | 0h | Based on configured value the Event 6 is used for trigger as independent trigger or in sequence with other words. 0x0 : Event 6 is not used for any trigger. 0x1 : Event 6 is independently used for trigger or it is followed up after Word-1 match to trigger SSS 0x9 : After Event 6 match sequence check moves to Event 7 is matched before next step Any other value : Event 6 is not used for any trigger Reset type: SYSRSn |
| 7-4 | RESERVED | R | 0h | Reserved |
| 3-0 | TRIG_EVT5CFG | R/W | 0h | Based on configured value the Event 5 is used for trigger as independent trigger or in sequence with other words. 0x0 : Event 5 is not used for any trigger 0x1 : Event 5 is independently used for trigger 0x9 : After Event 5 match sequence check moves to Event 6 is matched before next step Any other value : Event 5 is not used for any trigger Reset type: SYSRSn |
SSS_BLKSOUTEVT5CFG is shown in Figure 19-91 and described in Table 19-91.
Return to the Summary Table.
Output event5 used by SSS to drive WADI outputs as per Sequence configuration.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | OUTEVT5 | ||||||||||||||||||||||||||||||
| R/W-0h | R/W-0h | ||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-8 | RESERVED | R/W | 0h | Reserved |
| 7-0 | OUTEVT5 | R/W | 0h | Output on event 5(OUTEVT5) provides value to be applied on respective signal output when selected. Bits selectively drive the corresponding output line. [0] : SIG1 output override of block1 [1] : SIG2 output override of block1 [2] : SIG1 output override of block2 [3] : SIG2 output override of block2 [4] : SIG1 output override of block3 [5] : SIG2 output override of block3 [6] : SIG1 output override of block4 [7] : SIG2 output override of block4 Reset type: SYSRSn |
SSS_BLKSOUTEVT6CFG is shown in Figure 19-92 and described in Table 19-92.
Return to the Summary Table.
Output event6 used by SSS to drive WADI outputs as per Sequence configuration.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | OUTEVT6 | ||||||||||||||||||||||||||||||
| R/W-0h | R/W-0h | ||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-8 | RESERVED | R/W | 0h | Reserved |
| 7-0 | OUTEVT6 | R/W | 0h | Output on event 6(OUTEVT6) provides value to be applied on respective signal output when selected. Bits selectively drive the corresponding output line. [0] : SIG1 output override of block1 [1] : SIG2 output override of block1 [2] : SIG1 output override of block2 [3] : SIG2 output override of block2 [4] : SIG1 output override of block3 [5] : SIG2 output override of block3 [6] : SIG1 output override of block4 [7] : SIG2 output override of block4 Reset type: SYSRSn |
SSS_BLKSOUTEVT7CFG is shown in Figure 19-93 and described in Table 19-93.
Return to the Summary Table.
Output event7 used by SSS to drive WADI outputs as per Sequence configuration.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | OUTEVT7 | ||||||||||||||||||||||||||||||
| R/W-0h | R/W-0h | ||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-8 | RESERVED | R/W | 0h | Reserved |
| 7-0 | OUTEVT7 | R/W | 0h | Output on event 7(OUTEVT7) provides value to be applied on respective signal output when selected. Bits selectively drive the corresponding output line. [0] : SIG1 output override of block1 [1] : SIG2 output override of block1 [2] : SIG1 output override of block2 [3] : SIG2 output override of block2 [4] : SIG1 output override of block3 [5] : SIG2 output override of block3 [6] : SIG1 output override of block4 [7] : SIG2 output override of block4 Reset type: SYSRSn |
SSS_BLKSOUTEVT8CFG is shown in Figure 19-94 and described in Table 19-94.
Return to the Summary Table.
Output event8 used by SSS to drive WADI outputs as per Sequence configuration.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | OUTEVT8 | ||||||||||||||||||||||||||||||
| R/W-0h | R/W-0h | ||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-8 | RESERVED | R/W | 0h | Reserved |
| 7-0 | OUTEVT8 | R/W | 0h | Output on event 8(OUTEVT8) provides value to be applied on respective signal output when selected. Bits selectively drive the corresponding output line. [0] : SIG1 output override of block1 [1] : SIG2 output override of block1 [2] : SIG1 output override of block2 [3] : SIG2 output override of block2 [4] : SIG1 output override of block3 [5] : SIG2 output override of block3 [6] : SIG1 output override of block4 [7] : SIG2 output override of block4 Reset type: SYSRSn |
SSS_OUTEVT5TRIGCFG is shown in Figure 19-95 and described in Table 19-95.
Return to the Summary Table.
Output event5 configuration that drives which trigger or link make sequence word active
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
| RESERVED | |||||||
| R-0h | |||||||
| 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| RESERVED | |||||||
| R-0h | |||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
| RESERVED | |||||||
| R-0h | |||||||
| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| EVT8TRIG | EVT7TRIG | EVT6TRIG | EVT5TRIG | EVT4TRIG | EVT3TRIG | EVT2TRIG | EVT1TRIG |
| R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h |
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-8 | RESERVED | R | 0h | Reserved |
| 7 | EVT8TRIG | R/W | 0h | When this control is set '1', then upon Event 8 Trigger assertion OUTEVT5 is set and the duration based on time defined at SSS_OUTEVT5DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 8 Trigger has no effect. Reset type: SYSRSn |
| 6 | EVT7TRIG | R/W | 0h | When this control is set '1', then upon Event 7 Trigger assertion OUTEVT5 is set and the duration based on time defined at SSS_OUTEVT5DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 7 Trigger has no effect. Reset type: SYSRSn |
| 5 | EVT6TRIG | R/W | 0h | When this control is set '1', then upon Event 6 Trigger assertion OUTEVT5 is set and the duration based on time defined at SSS_OUTEVT5DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 6 Trigger has no effect. Reset type: SYSRSn |
| 4 | EVT5TRIG | R/W | 0h | When this control is set '1', then upon Event 5 Trigger assertion OUTEVT5 is set and the duration based on time defined at SSS_OUTEVT5DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 5 Trigger has no effect. Reset type: SYSRSn |
| 3 | EVT4TRIG | R/W | 0h | When this control is set '1', then upon Event 4 Trigger assertion OUTEVT5 is set and the duration based on time defined at SSS_OUTEVT5DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 4 Trigger has no effect. Reset type: SYSRSn |
| 2 | EVT3TRIG | R/W | 0h | When this control is set '1', then upon Event 3 Trigger assertion OUTEVT5 is set and the duration based on time defined at SSS_OUTEVT5DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 3 Trigger has no effect. Reset type: SYSRSn |
| 1 | EVT2TRIG | R/W | 0h | When this control is set '1', then upon Event 2 Trigger assertion OUTEVT5 is set and the duration based on time defined at SSS_OUTEVT5DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 2 Trigger has no effect. Reset type: SYSRSn |
| 0 | EVT1TRIG | R/W | 0h | When this control is set '1', then upon Event 1 Trigger assertion OUTEVT5 is set and the duration based on time defined at SSS_OUTEVT5DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 1 Trigger has no effect. Reset type: SYSRSn |
SSS_OUTEVT6TRIGCFG is shown in Figure 19-96 and described in Table 19-96.
Return to the Summary Table.
Output event6 configuration that drives which trigger or link make sequence word active
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
| RESERVED | |||||||
| R-0h | |||||||
| 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| RESERVED | |||||||
| R-0h | |||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
| RESERVED | |||||||
| R-0h | |||||||
| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| EVT8TRIG | EVT7TRIG | EVT6TRIG | EVT5TRIG | EVT4TRIG | EVT3TRIG | EVT2TRIG | EVT1TRIG |
| R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h |
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-8 | RESERVED | R | 0h | Reserved |
| 7 | EVT8TRIG | R/W | 0h | When this control is set '1', then upon Event 8 Trigger assertion OUTEVT6 is set and the duration based on time defined at SSS_OUTEVT6DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 8 Trigger has no effect. Reset type: SYSRSn |
| 6 | EVT7TRIG | R/W | 0h | When this control is set '1', then upon Event 7 Trigger assertion OUTEVT6 is set and the duration based on time defined at SSS_OUTEVT6DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 7 Trigger has no effect. Reset type: SYSRSn |
| 5 | EVT6TRIG | R/W | 0h | When this control is set '1', then upon Event 6 Trigger assertion OUTEVT6 is set and the duration based on time defined at SSS_OUTEVT6DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 6 Trigger has no effect. Reset type: SYSRSn |
| 4 | EVT5TRIG | R/W | 0h | When this control is set '1', then upon Event 5 Trigger assertion OUTEVT6 is set and the duration based on time defined at SSS_OUTEVT6DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 5 Trigger has no effect. Reset type: SYSRSn |
| 3 | EVT4TRIG | R/W | 0h | When this control is set '1', then upon Event 4 Trigger assertion OUTEVT6 is set and the duration based on time defined at SSS_OUTEVT6DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 4 Trigger has no effect. Reset type: SYSRSn |
| 2 | EVT3TRIG | R/W | 0h | When this control is set '1', then upon Event 3 Trigger assertion OUTEVT6 is set and the duration based on time defined at SSS_OUTEVT6DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 3 Trigger has no effect. Reset type: SYSRSn |
| 1 | EVT2TRIG | R/W | 0h | When this control is set '1', then upon Event 2 Trigger assertion OUTEVT6 is set and the duration based on time defined at SSS_OUTEVT6DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 2 Trigger has no effect. Reset type: SYSRSn |
| 0 | EVT1TRIG | R/W | 0h | When this control is set '1', then upon Event 1 Trigger assertion OUTEVT6 is set and the duration based on time defined at SSS_OUTEVT6DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 1 Trigger has no effect. Reset type: SYSRSn |
SSS_OUTEVT7TRIGCFG is shown in Figure 19-97 and described in Table 19-97.
Return to the Summary Table.
Output event7 configuration that drives which trigger or link make sequence word active
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
| RESERVED | |||||||
| R-0h | |||||||
| 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| RESERVED | |||||||
| R-0h | |||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
| RESERVED | |||||||
| R-0h | |||||||
| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| EVT8TRIG | EVT7TRIG | EVT6TRIG | EVT5TRIG | EVT4TRIG | EVT3TRIG | EVT2TRIG | EVT1TRIG |
| R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h |
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-8 | RESERVED | R | 0h | Reserved |
| 7 | EVT8TRIG | R/W | 0h | When this control is set '1', then upon Event 8 Trigger assertion OUTEVT7 is set and the duration based on time defined at SSS_OUTEVT7DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 8 Trigger has no effect. Reset type: SYSRSn |
| 6 | EVT7TRIG | R/W | 0h | When this control is set '1', then upon Event 7 Trigger assertion OUTEVT7 is set and the duration based on time defined at SSS_OUTEVT7DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 7 Trigger has no effect. Reset type: SYSRSn |
| 5 | EVT6TRIG | R/W | 0h | When this control is set '1', then upon Event 6 Trigger assertion OUTEVT7 is set and the duration based on time defined at SSS_OUTEVT7DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 6 Trigger has no effect. Reset type: SYSRSn |
| 4 | EVT5TRIG | R/W | 0h | When this control is set '1', then upon Event 5 Trigger assertion OUTEVT7 is set and the duration based on time defined at SSS_OUTEVT7DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 5 Trigger has no effect. Reset type: SYSRSn |
| 3 | EVT4TRIG | R/W | 0h | When this control is set '1', then upon Event 4 Trigger assertion OUTEVT7 is set and the duration based on time defined at SSS_OUTEVT7DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 4 Trigger has no effect. Reset type: SYSRSn |
| 2 | EVT3TRIG | R/W | 0h | When this control is set '1', then upon Event 3 Trigger assertion OUTEVT7 is set and the duration based on time defined at SSS_OUTEVT7DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 3 Trigger has no effect. Reset type: SYSRSn |
| 1 | EVT2TRIG | R/W | 0h | When this control is set '1', then upon Event 2 Trigger assertion OUTEVT7 is set and the duration based on time defined at SSS_OUTEVT7DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 2 Trigger has no effect. Reset type: SYSRSn |
| 0 | EVT1TRIG | R/W | 0h | When this control is set '1', then upon Event 1 Trigger assertion OUTEVT7 is set and the duration based on time defined at SSS_OUTEVT7DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 1 Trigger has no effect. Reset type: SYSRSn |
SSS_OUTEVT8TRIGCFG is shown in Figure 19-98 and described in Table 19-98.
Return to the Summary Table.
Output event8 configuration that drives which trigger or link make sequence word active
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
| RESERVED | |||||||
| R-0h | |||||||
| 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| RESERVED | |||||||
| R-0h | |||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
| RESERVED | |||||||
| R-0h | |||||||
| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| EVT8TRIG | EVT7TRIG | EVT6TRIG | EVT5TRIG | EVT4TRIG | EVT3TRIG | EVT2TRIG | EVT1TRIG |
| R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h |
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-8 | RESERVED | R | 0h | Reserved |
| 7 | EVT8TRIG | R/W | 0h | When this control is set '1', then upon Event 8 Trigger assertion OUTEVT8 is set and the duration based on time defined at SSS_OUTEVT8DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 8 Trigger has no effect. Reset type: SYSRSn |
| 6 | EVT7TRIG | R/W | 0h | When this control is set '1', then upon Event 7 Trigger assertion OUTEVT8 is set and the duration based on time defined at SSS_OUTEVT8DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 7 Trigger has no effect. Reset type: SYSRSn |
| 5 | EVT6TRIG | R/W | 0h | When this control is set '1', then upon Event 6 Trigger assertion OUTEVT8 is set and the duration based on time defined at SSS_OUTEVT8DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 6 Trigger has no effect. Reset type: SYSRSn |
| 4 | EVT5TRIG | R/W | 0h | When this control is set '1', then upon Event 5 Trigger assertion OUTEVT8 is set and the duration based on time defined at SSS_OUTEVT8DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 5 Trigger has no effect. Reset type: SYSRSn |
| 3 | EVT4TRIG | R/W | 0h | When this control is set '1', then upon Event 4 Trigger assertion OUTEVT8 is set and the duration based on time defined at SSS_OUTEVT8DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 4 Trigger has no effect. Reset type: SYSRSn |
| 2 | EVT3TRIG | R/W | 0h | When this control is set '1', then upon Event 3 Trigger assertion OUTEVT8 is set and the duration based on time defined at SSS_OUTEVT8DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 3 Trigger has no effect. Reset type: SYSRSn |
| 1 | EVT2TRIG | R/W | 0h | When this control is set '1', then upon Event 2 Trigger assertion OUTEVT8 is set and the duration based on time defined at SSS_OUTEVT8DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 2 Trigger has no effect. Reset type: SYSRSn |
| 0 | EVT1TRIG | R/W | 0h | When this control is set '1', then upon Event 1 Trigger assertion OUTEVT8 is set and the duration based on time defined at SSS_OUTEVT8DUR[TIME] If the trigger is asserted (rise edge) while counter is active then counter is restarted. Hence overlapping triggers extends the duration for which OUTEVTn is held. If control set to '0' Event 1 Trigger has no effect. Reset type: SYSRSn |
SSS_OUTEVT5DUR is shown in Figure 19-99 and described in Table 19-99.
Return to the Summary Table.
Output event5 configuration that drives delay for applying output
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | TIME | ||||||||||||||||||||||||||||||
| R-0h | R/W-0h | ||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-24 | RESERVED | R | 0h | Reserved |
| 23-0 | TIME | R/W | 0h | Delay count configured is count down to '0' for holding the OUTEVTn active. Upon reaching '0' the OUTEVTn is deactivated and count is reloaded with the configured value for next cyclical round or trigger. 0xFF_FFFF is special value when OUTEVTn is kept active continuously and counter does not count down. This allows defining terminal state of the sequence. Reset type: SYSRSn |
SSS_OUTEVT6DUR is shown in Figure 19-100 and described in Table 19-100.
Return to the Summary Table.
Output event6 configuration that drives delay for applying output
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | TIME | ||||||||||||||||||||||||||||||
| R-0h | R/W-0h | ||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-24 | RESERVED | R | 0h | Reserved |
| 23-0 | TIME | R/W | 0h | Delay count configured is count down to '0' for holding the OUTEVTn active. Upon reaching '0' the OUTEVTn is deactivated and count is reloaded with the configured value for next cyclical round or trigger. 0xFF_FFFF is special value when OUTEVTn is kept active continuously and counter does not count down. This allows defining terminal state of the sequence. Reset type: SYSRSn |
SSS_OUTEVT7DUR is shown in Figure 19-101 and described in Table 19-101.
Return to the Summary Table.
Output event7 configuration that drives delay for applying output
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | TIME | ||||||||||||||||||||||||||||||
| R-0h | R/W-0h | ||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-24 | RESERVED | R | 0h | Reserved |
| 23-0 | TIME | R/W | 0h | Delay count configured is count down to '0' for holding the OUTEVTn active. Upon reaching '0' the OUTEVTn is deactivated and count is reloaded with the configured value for next cyclical round or trigger. 0xFF_FFFF is special value when OUTEVTn is kept active continuously and counter does not count down. This allows defining terminal state of the sequence. Reset type: SYSRSn |
SSS_OUTEVT8DUR is shown in Figure 19-102 and described in Table 19-102.
Return to the Summary Table.
Output event8 configuration that drives delay for applying output
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | TIME | ||||||||||||||||||||||||||||||
| R-0h | R/W-0h | ||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-24 | RESERVED | R | 0h | Reserved |
| 23-0 | TIME | R/W | 0h | Delay count configured is count down to '0' for holding the OUTEVTn active. Upon reaching '0' the OUTEVTn is deactivated and count is reloaded with the configured value for next cyclical round or trigger. 0xFF_FFFF is special value when OUTEVTn is kept active continuously and counter does not count down. This allows defining terminal state of the sequence. Reset type: SYSRSn |
PARTEST is shown in Figure 19-103 and described in Table 19-103.
Return to the Summary Table.
Enables parity test
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| RESERVED | |||||||||||||||
| R-0h | |||||||||||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | TESTEN | ||||||||||||||
| R-0h | R/W-0h | ||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-4 | RESERVED | R | 0h | Reserved |
| 3-0 | TESTEN | R/W | 0h | 1010: Parity test feature is enabled All other values: Parity test feature is disabled Note: (1) When the parity test feature is enabled, actual registers are not accessible in the memory map. Instead, the parity values (final XOR output indicating the parity error) are accessible Parity is computed for every byte and the corresponding parity error value is available at the bit-0 of every byte. Value of '1' written to the parity bit after enabling the parity test feature can be used to inject the error by inverting the stored parity value (2) It is recommended to leave the field as 0101 or 0000 after completing the parity test Reset type: SYSRSn |