• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 31 subscribers
  • Views 377 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.

Simple example of using hardware UART

Todd Wild
Prodigy 10 points


I'm looking for a simple example of using the UART. I can find plenty of examples using the debugger virtual com port but I'm hoping to send the data out of PB0 and PB1. Can anybody link to where I should look? Thank you in advance.

  • 0
    Guru 26105 points

    Hi,

    How do you expect to do that? easy way or hard way?

    For "hard" way, which is not at all hard, look at, learn and test the uart_echo examples, and when ready just apply for PortB. To have communications with PC or other external device, you need also a level translator to be added to your hardware.

    The "easy" way - use PinMux utility to write some code for you - but try to avoid this... hope you need to learn some thing useful - better to read twice the user manual and driverlib source code.

    Petrei

  • 0 in reply to Petrei
    TI__Guru**** 244410 points

    Hello All,

    Or use one of the USB 2 UART dongles, reducing the chances of making a mistake doing a level translator.

    I agree there with Petrei, it is not the "hard" to retrofit one of the TivaWare examples for a new Pin/Peripheral Instance configuration.

    Regards

    Amit

  • 0 in reply to Amit Ashara
    Guru 47900 points

    Amit Ashara said:
    it is not "hard" to retrofit one of the TivaWare examples for a new Pin/Peripheral Instance configuration.

    Or not!

    Suppose one of the Port A instantiations is to be modeled.  Do not these "exploit" the default behavior of many of the Port A pins/peripherals?  And - via that default exploitation - the set-up/config code is somewhat reduced? 

    Then - when the user simply, "copies/pastes" (after tweaking to the new peripheral enumeration) that very available, Port A peripheral example code - as the set-up/config is "incomplete" - the "easy" retrofit fails!

    Imho all Port A code should be rewritten to include the normal/customary set-up/configs - required by any/all other peripheral instantiations!  Those Port A "shortcuts" have derailed many - and may thus conflict with the claim that retrofit is not, "hard."