• State
  • Replies 3 replies
  • Subscribers 30 subscribers
  • Views 120 views
  • Users 0 members are here
Support feedback
Options
Options
Related

MSPM0L2228: UART RX Issue on MSPM0L2228 at 4 MHz Clock, Baudrate 19200

Ankush
Intellectual 520 points
Part Number: MSPM0L2228
Other Parts Discussed in Thread: MSPM0G3507

Tool/software:

Hi Team,

I am currently working with the MSPM0L2228 controller, where the system clock is configured to 4 MHz. I have set up the UART to operate at a baud rate of 19200.

Here are my observations:

  • TX side is working correctly.

  • RX side is not functioning as expected. The RX interrupt is generated, but during debugging I receive miscellaneous/garbled symbols instead of the expected data.

  • The baud rate can be changed at runtime, but the RX issue persists.

  • I have tested the same configuration on the MSPM0G3507 controller, and in that case both TX and RX work correctly without any issues.

Could you please advise if there are any additional settings or configurations required for stable UART RX operation on the MSPM0L2228 at this clock frequency and baud rate?

Thank you for your support.

Best regards,
Bhairav

  • 0
    TI__Intellectual 1540 points

    Hi Bhairav,

    I don't initially see any issues with this configuration for UART.

    Would you mind running the external loopback driverlib example to see if you can read the correct values in the watch window and/or registers?

    Best Regards,
    Brian

  • 0 in reply to Brian Lee
    Intellectual 520 points

    Hi Brian,

    I ran the external loopback driverlib example as you suggested, but I’m still getting miscellaneous characters on the UART receive side. The issue persists even though the configuration appears correct.

    Please let me know if there are any additional checks or settings I should try.

    Best Regards,
    Bhairav

  • 0 in reply to Ankush
    TI__Intellectual 1540 points

    Hi Bhairav,

    Would you be able to share your configuration settings?

    If UART is sourced from MFCLK or BUSCLK and oversampling is set to 3x, there is an erratum where RXINT is set incorrectly and can result in TX data becoming corrupted.

    Best Regards,
    Brian