SPRUI33H November 2015 – June 2024 TMS320F280040-Q1 , TMS320F280040C-Q1 , TMS320F280041 , TMS320F280041-Q1 , TMS320F280041C , TMS320F280041C-Q1 , TMS320F280045 , TMS320F280048-Q1 , TMS320F280048C-Q1 , TMS320F280049 , TMS320F280049-Q1 , TMS320F280049C , TMS320F280049C-Q1
The RX_TRIGx external trigger can be used to initiate FSITX transmission. RX_TRIG0 must be used if TDM mode (multi-slave configuration) is required. RX_TRIG0 must be used as the trigger source for start of transmission while the programmable stretch width RX_TRIG0 signal is used as the SEL_TDM_PATH signal (which decides whether the local FSITX is active or put in bypass mode).
Figure 28-10 RX_TRIGx FSI Trigger
The signal source for the RX_TRIGx signal is selected through the RX_TRIG_CTRL_x.TRIG_SEL bits, as listed in Table 28-10.
| RX_TRIG_CTRLx.TRIG_SEL | Selected Signal |
|---|---|
| 0 | Ping Packet Received |
| 1 | Data Packet Received |
| 2 | Error Packet Received |
| 3 | Ping Frame Tag Match Occurred |
| 4 | Data Frame Tag Match Occurred |
| 5 | Error Frame Tag Match Occurred |
| 6 | Frame Done |
| 7 | Reserved |
| 8 to 15 | Reserved |
The RX_TRIGx signals can optionally be delayed (this can be used in TDM scenarios) through the RX_TRIG_CTRL_x.TRIG_DLY.