SPRUJ79 November 2024 F29H850TU , F29H859TU-Q1
Trigger 1 and trigger 2 are used to apply the start condition for the signal analysis. The triggers have flexibility to use either of the two triggers for a specific WADI block. Table 19-2 shows the trigger selections for TRIG1 and TRIG2, respectively. This allows two entirely different sets of trigger inputs providing flexibility for triggering each SIGx. The trigger for SIG1 and SIG2 can be configured in BLKCFG[TRIG1IN] and BLKCFG[TRIG2IN] registers, respectively.
WADI_TRIG_SIG1_I index | WADI1 Signal Name | WADI2 Signal Name |
---|---|---|
0 | PWMXBAR9 | PWMXBAR9 |
1 | PWMXBAR10 | PWMXBAR10 |
2 | PWMXBAR11 | PWMXBAR11 |
3 | PWMXBAR12 | PWMXBAR12 |
4 | PWMXBAR13 | PWMXBAR13 |
5 | PWMXBAR14 | PWMXBAR14 |
6 | PWMXBAR15 | PWMXBAR15 |
7 | PWMXBAR16 | PWMXBAR16 |
8 | INPUTXBAR41 | INPUTXBAR57 |
9 | INPUTXBAR42 | INPUTXBAR58 |
10 | INPUTXBAR43 | INPUTXBAR59 |
11 | INPUTXBAR44 | INPUTXBAR60 |
12 | INPUTXBAR45 | INPUTXBAR61 |
13 | INPUTXBAR46 | INPUTXBAR62 |
14 | INPUTXBAR47 | INPUTXBAR63 |
15 | INPUTXBAR48 | INPUTXBAR64 |
WADI_TRIG_SIG2_I index | WADI1 Signal Name | WADI2 Signal Name |
---|---|---|
0 | PWMXBAR1 | PWMXBAR1 |
1 | PWMXBAR2 | PWMXBAR2 |
2 | PWMXBAR3 | PWMXBAR3 |
3 | PWMXBAR4 | PWMXBAR4 |
4 | PWMXBAR5 | PWMXBAR5 |
5 | PWMXBAR6 | PWMXBAR6 |
6 | PWMXBAR7 | PWMXBAR7 |
7 | PWMXBAR8 | PWMXBAR8 |
8 | INPUTXBAR33 | INPUTXBAR49 |
9 | INPUTXBAR34 | INPUTXBAR50 |
10 | INPUTXBAR35 | INPUTXBAR51 |
11 | INPUTXBAR36 | INPUTXBAR52 |
12 | INPUTXBAR37 | INPUTXBAR53 |
13 | INPUTXBAR38 | INPUTXBAR54 |
14 | INPUTXBAR39 | INPUTXBAR55 |
15 | INPUTXBAR40 | INPUTXBAR56 |
To start the analysis based on trigger, the configurations need to be complete before the WADI block is enabled.
The start of the signal analysis can be enabled for each of the signal measurement using triggers or if no triggers are configured the start of the first event detection right after the clock is enabled begins the signal analysis. SIG1 and SIG2 have individual configuration of the trigger which are no trigger, hardware trigger, software trigger, or synchronized trigger. Once the event triggers the measurements, the comparisons are continuous until the next trigger. If there is subsequent trigger then the measurement count restarts. If there are pending errors from previous counts, those are not reset, the application code must address the errors. Triggers selectable are categorized in Table 19-4.
Selection | Trigger Type | Description |
---|---|---|
0x0 | No Trigger (Default) | In this mode right after configuration for check is done on first event of configured type the measurement starts. |
0x1 | Hardware Trigger | This uses the hardware input from the WADI peripheral to start the measurement of signal. |
0x2 | Software Trigger | Each WADI block signal has an independent software bit control that the application can use to start the measurement. |
0x3 | Either Trigger | Whenever either hardware or software event is present the measurement is reset and started again. |
0x4 | Synchronized Trigger | This is special case when this is configured for signal then the triggers configured for other signal in WADI block is used for starting the measurement, this is useful for the signal to signal comparisons as well as having common trigger for related signals. |
0x5-0x7 | Reserved | All other configurations are reserved and those default to No trigger condition. |
No Trigger condition is used when external trigger is not expected but continuous signal characterization is required. In this case once after WADI clock is enabled the event detection and measurement started. The WADI configurations must be configured before enabling clock. Similarly, if there is need to change the WADI block configuration then the clock must first be disabled followed by configuration change and enable of clock again. In case “No trigger” is set then clock enable acts as trigger, in all other cases detection and measurement waits for trigger.
On revision of settings, if there are stale measurements in WADI block then those are cleared and fresh measurements started for both SIG1 and SIG2. Rewriting the same setting again does not change the status or ongoing waveform measurement.