SPRZ574B December   2023  – October 2025 AM62P , AM62P-Q1

 

  1.   1
  2. 1Usage Notes and Advisories Matrices
    1. 1.1 Devices Supported
  3. 2Silicon Usage Notes and Advisories
    1. 2.1 Silicon Usage Notes
      1.      i2351
      2.      i2424
      3.      i2330
      4.      i2496
    2. 2.2 Silicon Advisories
      1.      i2062
      2.      i2097
      3.      i2103
      4.      i2137
      5.      i2160
      6.      i2189
      7.      i2190
      8.      i2196
      9.      i2208
      10.      i2249
      11.      i2253
      12.      i2278
      13.      i2279
      14.      i2310
      15.      i2311
      16.      i2312
      17.      i2383
      18.      i2401
      19.      i2407
      20.      i2409
      21.      i2410
      22.      i2419
      23.      i2423
      24.      i2431
      25.      i2435
      26.      i2436
      27.      i2457
      28.      i2458
      29.      i2464
      30.      i2482
      31.      i2487
  4.   Trademarks
  5.   Revision History

i2310

USART: Erroneous clear/trigger of timeout interrupt

Details:

The USART may erroneously clear or trigger the timeout interrupt when RHR/MSR/LSR registers are read.

Workaround(s):

For CPU use-case.

  • If the timeout interrupt is erroneously cleared:
    • This is Valid since the pending data inside the FIFO retriggers the timeout interrupt
  • If timeout interrupt is erroneously set, and the FIFO is empty, use the following SW workaround to clear the interrupt:
    • Set a high value of timeout counter in TIMEOUTH and TIMEOUTL registers
    • Set EFR2 bit 6 to 1 to change timeout mode to periodic
    • Read the IIR register to clear the interrupt
    • Set EFR2 bit 6 back to 0 to change timeout mode back to the original mode

For DMA use-case.

  • If timeout interrupt is erroneously cleared:
    • This is valid since the next periodic event retriggers the timeout interrupt
    • User must ensure that RX timeout behavior is in periodic mode by setting EFR2 bit6 to 1
  • If timeout interrupt is erroneously set:
    • This causes DMA to be torn down by the SW driver
    • Valid since next incoming data causes SW to setup DMA again