SWRZ136B December   2023  – July 2025 CC2340R5-Q1

 

  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  ADC_09
    4. 3.4  BATMON_01
    5. 3.5  BATMON_02
    6. 3.6  CKM_01
    7. 3.7  CLK_01
    8. 3.8  I2C_01
    9. 3.9  GPIO_01
    10. 3.10 PMU_01
    11. 3.11 UART_01
  7. 4Revision History

UART_01

UART might issue spurious μDMA write burst requests

Revisions Affected

B

Details

UART issues a μDMA burst write request when the number of entries in the FIFO is less than or equal to the configured burst FIFO threshold. A subsequent μDMA write burst request is issued, if the total FIFO entries are still below the configured threshold. UART takes one additional SVT clock cycle to update the internal FIFO level, when compared to μDMA signaling an end to its burst active state. In corner cases, dependent on initial UART FIFO level, configured FIFO threshold for burst request, interconnect latencies, and so on, this additional clock latency within UART can cause a spurious write burst request to be generated towards μDMA, which might cause the last write(s) by μDMA responding to this to get missed. This is not seen on UART read burst requests as μDMA waits for the read to complete before signaling an end of read burst.

Workaround

When used along with UART, μDMA SETBURST must be configured for burst requests.

μDMA arbitration size must be 2.

TX FIFO level trigger must be set to ≤ 1/4 empty for the write burst trigger