SLAZ758D November   2024  – December 2025 MSPM0G1518 , MSPM0G1519 , MSPM0G3518 , MSPM0G3518-Q1 , MSPM0G3519 , MSPM0G3519-Q1 , MSPM0G3529-Q1

 

  1.   1
  2.   Abstract
  3. 1Functional Advisories
  4. 2Preprogrammed Software Advisories
  5. 3Debug Only Advisories
  6. 4Fixed by Compiler Advisories
  7. 5Device Nomenclature
    1. 5.1 Device Symbolization and Revision Identification
  8. 6Advisory Descriptions
    1. 6.1  ADC_ERR_06
    2. 6.2  ADC_ERR_10
    3. 6.3  AES_ERR_01
    4. 6.4  CPU_ERR_02
    5. 6.5  CPU_ERR_03
    6. 6.6  FLASH_ERR_01
    7. 6.7  FLASH_ERR_03
    8. 6.8  FLASH_ERR_04
    9. 6.9  FLASH_ERR_05
    10. 6.10 FLASH_ERR_08
    11. 6.11 GPIO_ERR_03
    12. 6.12 GPIO_ERR_04
    13. 6.13 I2C_ERR_04
    14. 6.14 I2C_ERR_05
    15. 6.15 I2C_ERR_06
    16. 6.16 I2C_ERR_07
    17. 6.17 I2C_ERR_08
    18. 6.18 I2C_ERR_09
    19. 6.19 I2C_ERR_10
    20. 6.20 I2C_ERR_13
    21. 6.21 KEYSTORE_ERR_01
    22. 6.22 MATHACL_ERR_01
    23. 6.23 MATHACL_ERR_02
    24. 6.24 PMCU_ERR_09
    25. 6.25 PMCU_ERR_10
    26. 6.26 PMCU_ERR_11
    27. 6.27 RST_ERR_01
    28. 6.28 RTC_ERR_01
    29. 6.29 SPI_ERR_02
    30. 6.30 SPI_ERR_04
    31. 6.31 SPI_ERR_05
    32. 6.32 SPI_ERR_06
    33. 6.33 SPI_ERR_07
    34. 6.34 SRAM_ERR_03
    35. 6.35 SYSCTL_ERR_01
    36. 6.36 SYSCTL_ERR_02
    37. 6.37 SYSCTL_ERR_03
    38. 6.38 SYSCTL_ERR_04
    39. 6.39 SYSOSC_ERR_01
    40. 6.40 SYSOSC_ERR_02
    41. 6.41 SYSOSC_ERR_04
    42. 6.42 SYSPLL_ERR_01
    43. 6.43 TIMER_ERR_04
    44. 6.44 TIMER_ERR_06
    45. 6.45 TIMER_ERR_07
    46. 6.46 UART_ERR_01
    47. 6.47 UART_ERR_02
    48. 6.48 UART_ERR_04
    49. 6.49 UART_ERR_05
    50. 6.50 UART_ERR_06
    51. 6.51 UART_ERR_07
    52. 6.52 UART_ERR_08
    53. 6.53 UART_ERR_10
    54. 6.54 UART_ERR_11
  9. 7Trademarks
  10. 8Revision History

6.50 UART_ERR_06

UART Module

Category

Functional

Function

Unexpected behavior RTOUT/Busy/Async in UART 9-bit mode

Description

UART receive timeout (RTOUT) is not working correctly in multi node scenario, where one UART will act as controller and other UART nodes as peripherals , each peripheral is configured with different address in 9-bit UART mode.
First UART controller communicated with UART peripheral1, by sending peripheral1's address as a first byte and then data, peripheral1 has seen the address match and received the data. Once controller is done with peripheral1, peripheral1 is not setting the RTOUT after the configured timeout period, if controller immediately starts the communication with another UART peripheral (peripheral2) which is configured with different address on the bus. The peripheral1 RTOUT counter is resetting while communication ongoing with peripheral2 and peripheral1  setting it's RTOUT only after UART controller is completed the communication with peripheral2 .
Similar behavior observed with BUSY and Async request. Busy and Async request is setting even if address does not match while controller communicating with other peripheral on the bus.

Workaround

Do not use RTOUT/ BUSY /Async clock request behavior in multi node UART communication where single controller is tied to multiple peripherals.