• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 449 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

SW-EK-TM4C1294XL: UART Connection between SMARTRF06EB and EK-TM4C1294XL

Vikram JHURRY
Prodigy 220 points
Part Number: SW-EK-TM4C1294XL
Other Parts Discussed in Thread: EK-TM4C1294XL

Hello,

I am trying to establish a UART connection between the two above boards. I am making a connection between the RX and TX of the UART pins on the SMARTRF0EB (not the USB port - the pins are located at the bottom -right of the board) and the UART0 and UART1 of the EK-TM4C1294XL. I am using the example codes for UART for both boards but I get no data on the EK-TM4C1294XL.

On the EK-TM4C1294XL I am using TIRTOS.

Can someone please explain the procedure for both the right way to connect these two boards as well as the code required for a UART connection to be done. When debugging I see that the ports are being opened successfully . I will post my codes on a later post.

Thanks,

Vikram

  • 0
    TI__Guru**** 159385 points
    Hi Vikram,

    Do you need both UART0 and UART1 from the TM4C129 LauchPad? Please note that by default the UART0 is used as the virtual COM port so the PA0 (UART0_RX) and PA1 (UART0_TX) are not brought out to the boosterpack header. You will need to change the JP4 and JP5 jumper position from horizontal to vertical position to bring out the UART0. Please refer to the LaunchPad user's guide.
  • 0
    Guru 117850 points

    I'm in complete agreement w/vendor's Charles that your description of your use of (both) UART0 & UART1 proves lacking.  

    UART1 - provided it appears upon a board header - should connect (alone) to your remote device.      There is the potential for danger - you must insure that the remote device's "RX & TX" pins operate at "CMOS" (NOT RS232) signal levels.      Once verified - you may implement the following:

    • connect your UART1 "RX" pin through a 100Ω resistor to the "TX" pin of the remote device
    • connect your UART1 "TX" pin through a 100Ω resistor to the "RX" pin of the remote device  ...  (in each case - the resistor provides a "safety factor" - worth using)
    • connect your MCU's "Board Ground" to the Ground of your remote device
    • insure that the "Baud Rates" of both your MCU Board and Remote Board are set equal.     (Slower rates (9600baud) are preferred when starting - after "success" may be increased.)
    • insure that the number of "Start/Stop" bits are equal
    • best to employ "No Parity and No "Flow Control" (hardware or software) at this early stage
    • insure that power is adequate & proper at the remote board ... AND that a common ground connection is established.    (too often - that's missed)

    As always your providing a "link" to any "remote device" eases & enhances the effort required - in your behalf - by your hapless "helper crüe."

    Code required:  TWare/examples/peripherals/uart/uart_polled.c  will prove easiest & fastest - thus recommended...    You must remember to "Peripheral Enable" (both) UART1 and the GPIO Port upon which those UART1 pins reside...