SLAU847F October 2022 – March 2026 MSPM0L1105 , MSPM0L1106 , MSPM0L1116 , MSPM0L1117 , MSPM0L1227 , MSPM0L1227-Q1 , MSPM0L1228 , MSPM0L1228-Q1 , MSPM0L1303 , MSPM0L1304 , MSPM0L1304-Q1 , MSPM0L1305 , MSPM0L1305-Q1 , MSPM0L1306 , MSPM0L1306-Q1 , MSPM0L1343 , MSPM0L1344 , MSPM0L1345 , MSPM0L1346 , MSPM0L2116 , MSPM0L2117 , MSPM0L2227 , MSPM0L2227-Q1 , MSPM0L2228 , MSPM0L2228-Q1
The interrupt FIFO level for UNICOMM-I2CC/T is configured in the IFLS register.
When a message gets received, the RX FIFO gets filled immediately. The configurable threshold options for the Receive (RX) FIFO are:
These various conditions are typically used to generate a CPU_INT or DMA_TRIG_RX event where the CPU/RX subsequently reads a specific number of characters into memory from RXDATA. The number of characters read in each Interrupt Service Routine (ISR) equals how many are guaranteed present in the FIFO as indicated by the flag.
Debugger reads of RXDATA have no effect on the contents in the RX FIFO.
On the transmit side, data is written by the CPU/DMA at the top most empty FIFO entry and then transferred to serializer. The configurable threshold options for the Transmit (TX) FIFO are:
These various conditions are typically used to generate a CPU_INT or DMA_TRIG_TX event where the CPU/DMA subsequently writes a specific number of characters into the TXDATA register. The number of characters written in each Interrupt Service Routine (ISR) equals how many spots are guaranteed empty in the FIFO as indicated by the flag.
Debugger writes of TXDATA will add elements to the TX FIFO the same as a CPU write.
Out of reset, both TX and RX FIFOs are configured to trigger an interrupt at half-level mark, and the content of FIFO are also cleared.
FIFO integrity is not guaranteed if the software disables the module in the middle of a transmission with data in the FIFO, and then re-enables it.