• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 2171 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC1310 - What is the maximum reliable UART baud rate and throughput possible with TI-RTOS drivers?

Garry Clarkson
Expert 4635 points
Other Parts Discussed in Thread: CC1310

Team,

I am working with an application that needs a UART for comm’s and for tracing data on the CC1310. 

If we want to put in more tracing capability, without slowing things down the faster the data can be sent the less time running the UART and more time in sleep reducing average power. Some empirical tests have shown that 1M baud is achievable but much over this and buffer overrun problems occur once the device gets a little loaded in other tasks. 

Is there a maximum UART driver throughput we can be aiming to run at?

Are there any known driver errata / updates available for this component?

We are trying to find the limits of the hardware and software.


Regards,

Garry

 

  • 0
    TI__Mastermind 36395 points
    Garry,

    When going above 1mbps on the UART, what was the interface hardware? if you are using the XDS110 on the LaunchPAD there is a limitation of the XDS110 to not support higher than approximately 1mbps.

    Regards,
    /TA
  • 0 in reply to TA12012
    TI__Expert 4635 points

    Hi Thomas,

    Thanks for the response and assist. 

    I checked back with the customer and they have actually managed to get this working now at2Mbps with a short length cable to an FT232RL  so your feedback was spot-on.

    There was a secondary software issue were a SWI gate was being used in the wrong way - calling Semaphore_pend with a timeout inside a SWI gate, which caused issues but this only happened at an increased baudrate though.

    Closing the thread.

    Regards,

    Garry