SWRZ135 December   2023 CC2340R2

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1Advisories Matrix
  5. 2Nomenclature, Package Symbolization, and Revision Identification
    1. 2.1 Device and Development Support-Tool Nomenclature
    2. 2.2 Devices Supported
    3. 2.3 Package Symbolization and Revision Identification
  6. 3Advisories
    1. 3.1 SPI_04
    2. 3.2 ADC_08
    3. 3.3 BATMON_01
    4. 3.4 CLK_01
  7. 4Revision History

3.1 SPI_04

Hang scenario with SPI waiting for CPU intervention forever.

Revisions Affected

A

Details

When the CPU is reading or writing the SPI FIFO using FIFO level triggers to generate interrupts, the system can hang. After the first interrupt is serviced, the FIFO level can permanently be below or above the configured threshold and not generate a subsequent CPU interrupt. This can lead to a hang scenario with SPI waiting for CPU intervention forever.

Workaround

  1. Use polling of FIFO status within SPI and don't rely on FIFO level configured interrupts, or
  2. Use only empty/overflow interrupts and don't use FIFO level configured interrupts, or
  3. Use FIFO level configured interrupts along with empty (for TXFIFO) and overflow (for RXFIFO) as a failsafe to avoid hang scenarios.