## Example Summary
The following example configures the UART at 9600bps waiting to echo received
characters.
The device goes to Standby mode while waiting and uses interrupts to wake up.
## Peripherals & Pin Assignments
| Peripheral | Pin | Function |
| --- | --- | --- |
| GPIOA | PA0 | Open-Drain Output |
| GPIOA | PA15 | Standard Output |
| SYSCTL | | |
| UART0 | PA11 | RX Pin |
| UART0 | PA10 | TX Pin |
| EVENT | | |
| DEBUGSS | PA20 | Debug Clock |
| DEBUGSS | PA19 | Debug Data In Out |
## BoosterPacks, Board Resources & Jumper Settings
Visit [LP_MSPM0G3507](https://www.ti.com/tool/LP-MSPM0G3507) for LaunchPad information, including user guide and hardware files.
| Pin | Peripheral | Function | LaunchPad Pin | LaunchPad Settings |
| --- | --- | --- | --- | --- |
| PA0 | GPIOA | PA0 | J27_9 |
- PA0 is 5V tolerant open-drain so it requires pull-up
- `J19 1:2` Use 3.3V pull-up
- `J19 2:3` Use 5V pull-up
- PA0 can be connected to LED1
- `J4 ON` Connect to LED1
- `J4 OFF` Disconnect from LED1
|
| PA15 | GPIOA | PA15 | J3_30 |
- This pin can be used for testing purposes in boosterpack connector
- Pin can be reconfigured for general purpose as necessary
|
| PA11 | UART0 | RX | J4_33/J26_6 |
- PA11 can be used as UART RX connected to XDS-110 backchannel, to boosterpack connector or to CAN/LIN connector:
- To use backchannel UART on J101:
`J22 1:2`: Connects XDS-110 backchannel UART RX to `J101`
`J101 7:8` Connects XDS-110 backchannel to UART RX
- To use UART on boosterpack connector:
`J22 2:3`: Connects UART RX to `J4_33`
- To use on J26 CAN/LIN connector:
`R63` is populated by default and connects pin to `J26_6`
|
| PA10 | UART0 | TX | J4_34/J26_5 |
- PA10 can be used as UART TX connected to XDS-110 backchannel, to boosterpack connector or to CAN/LIN connector:
- To use backchannel UART on J101:
`J21 1:2`: Connects XDS-110 backchannel UART TX to `J101`
`J101 9:10` Connects XDS-110 backchannel to UART TX
- To use UART on boosterpack connector:
`J21 2:3`: Connects UART TX to `J4_34`
- To use on J26 CAN/LIN connector:
`R62` is populated by default and connects pin to `J26_5`
|
| PA20 | DEBUGSS | SWCLK | N/A |
- PA20 is used by SWD during debugging
- `J101 15:16 ON` Connect to XDS-110 SWCLK while debugging
- `J101 15:16 OFF` Disconnect from XDS-110 SWCLK if using pin in application
|
| PA19 | DEBUGSS | SWDIO | N/A |
- PA19 is used by SWD during debugging
- `J101 13:14 ON` Connect to XDS-110 SWDIO while debugging
- `J101 13:14 OFF` Disconnect from XDS-110 SWDIO if using pin in application
|
### Device Migration Recommendations
This project was developed for a superset device included in the LP_MSPM0G3507 LaunchPad. Please
visit the [CCS User's Guide](https://software-dl.ti.com/msp430/esd/MSPM0-SDK/latest/docs/english/tools/ccs_ide_guide/doc_guide/doc_guide-srcs/ccs_ide_guide.html#sysconfig-project-migration)
for information about migrating to other MSPM0 devices.
### Low-Power Recommendations
TI recommends to terminate unused pins by setting the corresponding functions to
GPIO and configure the pins to output low or input with internal
pullup/pulldown resistor.
SysConfig allows developers to easily configure unused pins by selecting **Board**→**Configure Unused Pins**.
For more information about jumper configuration to achieve low-power using the
MSPM0 LaunchPad, please visit the [LP-MSPM0G3507 User's Guide](https://www.ti.com/lit/slau873).
## Example Usage
Compile, load and run the example.
Connect to terminal if using Launchpad's back-channel UART, or connect to
external device using BoosterPack.
The UART will wait to receive data and respond with echo. Every time UART
receives data the LED toggles and the USER_TEST matches the LED pin state.