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.

LAUNCHCC3235MOD: Using UART1 on the pin headers

Part Number: LAUNCHCC3235MOD
Other Parts Discussed in Thread: SYSCONFIG

I'm trying to use UART1 on the device in addition to the XDS110-connected UART0, but no matter what pin configuration I use I can't seem to get sysconfig to direct the pins to the header without conflicts.

I'm using the mqtt-client example as the starting point (I'm basically trying to make a serial to MQTT bridge, so would like to use UART1 as the serial port for the IO, and UART0 for debugging.

Alternatively, a second best solution would be to use UART0 for my application, foregoing the use of the debugging UART, but in that case would I still be able to use the XDS110 device for programming over USB?

Any example syscfg files for what I want to achieve?

  • Hi Matthew,

    When debugging, the TMS/TCK/TDO/TDI pins are used, not UART. The default UART0 pins are routed through the XDS110 for convenience (the XDS110 toggles the reset pin required during flashing over the UART). If you debug the mqtt-client example and open a serial terminal (instructions in the example readme or in this SimpleLink Academy lab), you can see printing to the serial terminal. So you do not need to configure UART1.

    To answer your question though, SysConfig is tied to the default LaunchPad configuration, so it will only show you UART0 for the XDS110 header. If you go to the SysConfig settings (top right corner), you can select "Use Custom Board" to see all available pins. The LaunchPad RX and TX UART headers are physically tied to IC pins 55 and 57 (module package pins 46 and 47). You can configure those pins as UART1 and make no hardware changes, and you should be able to print to a serial terminal.


    Best regards,

    Sarah