msp432p401r launchpad™ development kit (msp …• out-of-box software example • cc3100boost...

User's GuideSLAU597A–March 2015–Revised July 2015

MSP432P401R LaunchPad™ Development Kit(MSP‑‑EXP432P401R)

The MSP‑EXP432P401R LaunchPad™ is an easy-to-use evaluation module (EVM) for theMSP432P401R microcontroller. It contains everything needed to start developing on the MSP432 Low-Power + Performance ARM® 32-bit Cortex®-M4F microcontroller (MCU), including on-board emulation forprogramming, debugging, and energy measurements. The MSP432P401R device supports low-powerapplications requiring increased CPU speed, memory, analog, and 32-bit performance.

Figure 1. MSP‑‑EXP432P401R LaunchPad

LaunchPad, BoosterPack, Code Composer Studio, EnergyTrace, SimpleLink, E2E are trademarks of Texas Instruments.ARM, Cortex are registered trademarks of ARM Ltd.IAR Embedded Workbench is a trademark of IAR Systems.All other trademarks are the property of their respective owners.

1SLAU597A–March 2015–Revised July 2015 MSP432P401R LaunchPad™ Development Kit (MSP‑EXP432P401R)Submit Documentation Feedback

Copyright © 2015, Texas Instruments Incorporated

http://www.ti.com/tool/MSP%E2%80%91EXP432P401R

http://www.ti.com/product/MSP432P401R

http://www.go-dsp.com/forms/techdoc/doc_feedback.htm?litnum=SLAU597A

www.ti.com

Contents1 Getting Started ............................................................................................................... 32 Hardware...................................................................................................................... 53 Software Examples ........................................................................................................ 174 Resources ................................................................................................................... 245 FAQ .......................................................................................................................... 286 Schematics.................................................................................................................. 32

List of Figures

1 MSP‑EXP432P401R LaunchPad .......................................................................................... 12 EVM Overview ............................................................................................................... 53 Block Diagram................................................................................................................ 54 MSP432P401RIPZ Pinout .................................................................................................. 65 XDS110-ET Emulator ....................................................................................................... 76 XDS110-ET Isolation Block................................................................................................. 87 Application Backchannel UART in Device Manager .................................................................... 98 EnergyTrace Technology Preferences .................................................................................. 119 EnergyTrace Windows..................................................................................................... 1210 MSP‑EXP432P401R Power Block Diagram ............................................................................ 1311 LaunchPad to BoosterPack Connector Pinout ......................................................................... 1612 Out-of-Box GUI Running Locally ......................................................................................... 1813 Out-of-Box GUI Running From TI Cloud Tools......................................................................... 1914 Backend Block Diagram of CC3100BOOST MQTT-Twitter LED Control Demo................................... 2115 Importing and Converting an Image With MSP Image Reformer .................................................... 2316 Using TI Resource Explorer to Browse MSP‑EXP432P401R in MSPWare ........................................ 2617 SWD Mode Settings ....................................................................................................... 2818 Target Configurations...................................................................................................... 2819 Launch Selected Configuration........................................................................................... 2920 Show All Cores ............................................................................................................. 2921 Connect Target ............................................................................................................. 3022 MSP432_Factory_Reset Script........................................................................................... 3023 Schematics (1 of 7) ........................................................................................................ 3224 Schematics (2 of 7) ........................................................................................................ 3325 Schematics (3 of 7) ........................................................................................................ 3426 Schematics (4 of 7) ........................................................................................................ 3527 Schematics (5 of 7) ........................................................................................................ 3628 Schematics (6 of 7) ........................................................................................................ 3729 Schematics (7 of 7) ........................................................................................................ 38

List of Tables

1 Isolation Block Connections ................................................................................................ 72 Default Clock Operation ................................................................................................... 143 Hardware Change Log..................................................................................................... 174 Software Examples ........................................................................................................ 175 IDE Minimum Requirements for MSP‑EXP432P401R ................................................................ 176 Source File and Folders ................................................................................................... 207 How MSP Device Documentation is Organized........................................................................ 27

2 MSP432P401R LaunchPad™ Development Kit (MSP‑EXP432P401R) SLAU597A–March 2015–Revised July 2015Submit Documentation Feedback


http://www.ti.com


www.ti.com Getting Started

1 Getting Started

1.1 IntroductionThe MSP‑EXP432P401R LaunchPad is an easy-to-use evaluation module (EVM) for the MSP432P401Rmicrocontroller. It contains everything needed to start developing on the MSP432 Low-Power +Performance ARM 32-bit Cortex-M4F microcontroller (MCU), including on-board emulation forprogramming, debugging, and energy measurements. The MSP432P401R device supports low-powerapplications that require increased CPU speed, memory, analog, and 32-bit performance.

Rapid prototyping is simplified by access to the 40-pin headers and a wide variety of BoosterPack™ plug-in modules that enable technologies such as wireless connectivity, graphical displays, environmentalsensing, and many more. Free software development tools are also available such as TI's Eclipse-basedCode Composer Studio™ (CCS) IDE, IAR Embedded Workbench™ IDE, and Keil µVision IDE. CodeComposer (CCS) supports EnergyTrace™ technology when paired with the MSP432P401R LaunchPad.More information about the LaunchPad, the supported BoosterPacks, and the available resources can befound at TI's LaunchPad portal. To get started quickly, and find available resources in MSPWare, visit theTI Cloud Development Environment.

1.2 Key Features• Low-power ARM Cortex-M4F MSP432P401R• 40-pin LaunchPad standard that leverages the BoosterPack ecosystem• XDS110-ET, an open-source onboard debugger featuring EnergyTrace+ technology and application

UART• Two buttons and two LEDs for user interaction• Backchannel UART through USB to PC

1.3 What's Included

1.3.1 Kit Contents• One MSP‑EXP432P401R LaunchPad Evaluation Kit• One Micro USB cable• One Quick Start Guide

1.3.2 Software Examples (Section 3)• Out-of-Box Software Example• CC3100BOOST MQTT-Twitter LED Control Example• BOOSTXL-K350QVG-S1 Graphics Library Example• 430BOOST-SHARP96 Graphics Library Example

1.4 First Steps: Out-of-Box ExperienceAn easy way to get familiar with the EVM is by using its preprogrammed out-of-box code. It demonstratessome key features of the LaunchPad from a user level, showing how to use the pushbutton switchestogether with onboard LEDs and basic serial communication with a computer.

A more detailed explanation of the out-of-box demo can be found in Section 3.



http://www.ti.com

http://www.ti.com/product/msp432p401r



http://www.ti.com/tool/ccstudio

http://www.ti.com/tool/iar-kickstart

https://www.keil.com/demo/eval/arm.htm

http://www.ti.com/tool/energytrace

http://www.ti.com/launchpad

http://dev.ti.com/


Getting Started www.ti.com

1.5 Next Steps: Looking Into the Provided CodeIt is now time to start exploring more features of the EVM!

www.ti.com/beginMSP432launchpad

To get started, you will need an integrated development environment (IDE) to explore and start editing thecode examples. Refer to Section 4 for more information on IDEs and where to download them.

The out-of-box source code and more code examples can be downloaded from the MSP-EXP432P401Rtool folder. Find what code examples are available and more details about each example in Section 3. Allcode is licensed under BSD, and TI encourages reuse and modifications to fit specific needs.



http://www.ti.com

http://www.ti.com/beginMSP432launchpad

http://www.ti.com/tool/msp-exp432p401r



Target Device

MSP432P401R

Crystal

48 MHz

Micro‐B

USB

EnergyTrace+

Current

Measure HW

LDO

5 V, 3.3 V

ESD

Protection

Power

Switch

Debug

MCU

LED

Red, Green

Power, UART, SWD to Target

User Interface

Buttons and LEDs

40‐pin LaunchPad

standard headers

www.ti.com Hardware

2 HardwareFigure 2 shows an overview of the EVM hardware.

Figure 2. EVM Overview

2.1 Block DiagramFigure 3 shows the block diagram.

Figure 3. Block Diagram



http://www.ti.com


1P10.1/UCB3CLK

2P10.2/UCB3SIMO/UCB3SDA

3P10.3/UCB3SOMI/UCB3SCL

4P1.0/UCA0STE

5P1.1/UCA0CLK

6P1.2/UCA0RXD/UCA0SOMI

7P1.3/UCA0TXD/UCA0SIMO

8P1.4/UCB0STE

9P1.5/UCB0CLK

10P1.6/UCB0SIMO/UCB0SDA

11P1.7/UCB0SOMI/UCB0SCL

12VCORE

13DVCC1

14VSW

15DVSS1

16P2.0/PM_UCA1STE

17P2.1/PM_UCA1CLK

18P2.2/PM_UCA1RXD/PM_UCA1SOMI

19P2.3/PM_UCA1TXD/PM_UCA1SIMO

20P2.4/PM_TA0.1

21P2.5/PM_TA0.2

22P2.6/PM_TA0.3

23P2.7/PM_TA0.4

24P10.4/TA3.0/C0.7

25P10.5/TA3.1/C0.626

P7.4

/PM

_TA

1.4

/C0.5

27

P7.5

/PM

_TA

1.3

/C0.4

28

P7.6

/PM

_TA

1.2

/C0.3

29

P7.7

/PM

_TA

1.1

/C0.2

30

P8.0

/UC

B3S

TE

/TA

1.0

/C0.1

31

P8

.1/U

CB

3C

LK

/TA

2.0

/C0

.0

32

P3.0

/PM

_U

CA

2S

TE

33

P3.1

/PM

_U

CA

2C

LK

34

P3.2

/PM

_U

CA

2R

XD

/PM

_U

CA

2S

OM

I

35

P3.3

/PM

_U

CA

2T

XD

/PM

_U

CA

2S

IMO

36

P3.4

/PM

_U

CB

2S

TE

37

P3.5

/PM

_U

CB

2C

LK

38

P3.6

/PM

_U

CB

2S

IMO

/PM

_U

CB

2S

DA

39

P3.7

/PM

_U

CB

2S

OM

I/P

M_U

CB

2S

CL

40

AV

SS

3

41

PJ.0

/LF

XIN

42

PJ.1

/LF

XO

UT

43

AV

SS

1

44

DC

OR

45

AV

CC

1

46

P8.2

/TA

3.2

/A23

47

P8.3

/TA

3C

LK

/A22

48

P8.4

/A21

49

P8.5

/A20

50

P8.6

/A19

51 P8.7/A18

52 P9.0/A17

53 P9.1/A16

54 P6.0/A15

55 P6.1/A14

56 P4.0/A13

57 P4.1/A12

58 P4.2/ACLK/TA2CLK/A11

59 P4.3/MCLK/RTCCLK/A10

60 P4.4/HSMCLK/SVMHOUT/A9

61 P4.5/A8

62 P4.6/A7

63 P4.7/A6

64 P5.0/A5

65 P5.1/A4

66 P5.2/A3

67 P5.3/A2

68 P5.4/A1

69 P5.5/A0

70 P5.6/TA2.1/VREF+/VeREF+/C1.7

71 P5.7/TA2.2/VREF-/VeREF-/C1.6

72 DVSS2

73 DVCC2

74 P9.2/TA3.3

75 P9.3/TA3.476

P6.2

/UC

B1S

TE

/C1.5

77

P6.3

/UC

B1C

LK

/C1.4

78

P6.4

/UC

B1S

IMO

/UC

B1S

DA

/C1.3

79

P6.5

/UC

B1S

OM

I/U

CB

1S

CL/C

1.2

80

P6.6

/TA

2.3

/UC

B3S

IMO

/UC

B3S

DA

/C1.1

81

P6.7

/TA

2.4

/UC

B3S

OM

I/U

CB

3S

CL/C

1.0

82

DV

SS

3

83

RS

Tn/N

MI

84

AV

SS

2

85P

J.2

/HF

XO

UT

86

PJ.3

/HF

XIN

87

AV

CC

2

88

P7.0

/PM

_S

MC

LK

/PM

_D

MA

E0

89

P7.1

/PM

_C

0O

UT

/PM

_TA

0C

LK

90

P7.2

/PM

_C

1O

UT

/PM

_TA

1C

LK

91

P7.3

/PM

_TA

0.0

92

PJ.4

/TD

I/A

DC

14C

LK

93

PJ.5

/TD

O/S

WO

94

SW

DIO

TM

S

95

SW

CLK

TC

K

96

P9.4

/UC

A3S

TE

97

P9.5

/UC

A3C

LK

98

P9.6

/UC

A3R

XD

/UC

A3S

OM

I

99

P9.7

/UC

A3T

XD

/UC

A3S

IMO

100

P10.0

/UC

B3S

TE

Hardware www.ti.com

2.2 MSP432P401RThe MSP432P401R is the first MSP432 family device featuring low-power performance with an ARMCortex-M4F core. Device features include:• Low-power ARM Cortex-M4F MSP432P401R• Up to 48-MHz system clock• 256KB flash memory, 64KB SRAM, and 32KB ROM with MSPWare libraries• Four 16-bit timers with capture/compare/PWM, two 32-bit timers, and RTC• Up to eight serial communication channels (I2C, SPI, UART, and IrDA)• Analog: 14-bit SAR ADC, capacitive touch, comparator• Digital: AES256, CRC, uDMA

Figure 4. MSP432P401RIPZ Pinout



http://www.ti.com


www.ti.com Hardware

2.3 XDS110-ET Onboard EmulatorTo keep development easy and cost effective, TI's LaunchPad evaluation kits integrate an onboardemulator, which eliminates the need for expensive programmers. The MSP‑EXP432P401R has theXDS110-ET emulator, which is a simple low-cost debugger that supports nearly all TI ARM devicederivatives.

Figure 5. XDS110-ET Emulator

The XDS110-ET hardware can be found in the schematics in Section 6 and in the MSP‑EXP432P401RHardware Design Files.

2.3.1 XDS110-ET Isolation BlockThe isolation block is comprised of switch S101 and the accompanying jumpers next the switch.

The isolation block allows the user to connect or disconnect signals that cross from the XDS110-ETdomain into the MSP432P401R target domain. This crossing is shown by the dotted line across theLaunchPad. No other signals cross this domain, so the XDS110-ET can be decoupled from theMSP432P401R target side. This includes XDS110-ET Serial Wire Debug signals, application UARTsignals, and 3.3-V and 5-V power.

Table 1 lists the signals that are controlled at the isolation block.

Table 1. Isolation Block Connections

Signal Isolation Type (1) (2) Description5V Jumper 5-V power rail, VBUS from USB3V3 Jumper 3.3-V power rail, derived from VBUS by an LDO in the XDS110-ET domain

Backchannel UART: Ready-To-Send, for hardware flow control. The target can useRTS >> Jumper* this to indicate whether it is ready to receive data from the host PC. The arrows

indicate the direction of the signal.Backchannel UART: Clear-To-Send, for hardware flow control. The host PC (through

CTS << Jumper* the emulator) uses this to indicate whether it is ready to receive data. The arrowsindicate the direction of the signal.Backchannel UART: The target MCU receives data through this signal. The arrowsRXD << Jumper indicate the direction of the signal.Backchannel UART: The target MCU sends data through this signal. The arrowsTXD >> Jumper indicate the direction of the signal.

RST Switch S101 MCU RST signal (active low)TCK_SWCLK Switch S101 Serial wire clock input (SWCLK) / JTAG clock input (TCK)

(1) Jumper* corresponds to signals without a jumper placed by default.(2) Switch* corresponds to signals that are controlled by S101, but not through IC111.



http://www.ti.com

http://software-dl.ti.com/msp430/msp430_public_sw/mcu/msp430/MSP-EXP432P401R/latest/index_FDS.html



XDS110-ET

Emulator MCU

Isolation

Block

JTA

G a

nd

SW

D

Ap

pli

cati

on

UA

RT

3.3

V P

ow

er

5V

Po

we

r

MSP432P401R

Target MCU

XD

S1

10

-ET

MS

P4

32

Ta

rge

t

USB Connector

in out

LDO

Bo

ost

erP

ack

He

ad

er

Bo

ost

erP

ack

He

ad

er

USB

EnergyTrace

S101

eU

SC

I_A

0

Hardware www.ti.com

Table 1. Isolation Block Connections (continued)Signal Isolation Type (1) (2) Description

TMS_SWDIO Switch S101 Serial wire data input/output (SWDIO) / JTAG test mode select (TMS)TDO_SWO Switch S101 Serial wire trace output (SWO) / JTAG trace output (TWO) (Also PJ.5)

TDI Switch* S101 JTAG test data input (Also PJ.4)

Reasons to open these connections:• To remove any and all influence from the XDS110-ET emulator for high accuracy target power

measurements• To control 3-V and 5-V power flow between the XDS110-ET and target domains• To expose the target MCU pins for other use than onboard debugging and application UART

communication• To expose the UART interface of the XDS110-ET so that it can be used for devices other than the

onboard MCU.

Figure 6. XDS110-ET Isolation Block

2.3.2 Application (or "Backchannel") UARTThe XDS110-ET provides a "backchannel" UART-over-USB connection with the host, which can be veryuseful during debugging and for easy communication with a PC. The provided UART supports hardwareflow control (RTS and CTS); although by default these signals are not connected to the target.



http://www.ti.com


www.ti.com Hardware

The backchannel UART allows communication with the USB host that is not part of the target application'smain functionality. This is very useful during development, and also provides a communication channel tothe PC host side. This can be used to create GUIs and other programs on the PC that communicate withthe LaunchPad.

The pathway of the backchannel UART is shown in Figure 7. The backchannel UART eUSCI_A0 isindependent of the UART on the 40-pin BoosterPack connector eUSCI_A2.

On the host side, a virtual COM port for the application backchannel UART is generated when theLaunchPad enumerates on the host. You can use any PC application that interfaces with COM ports,including terminal applications like Hyperterminal or Docklight, to open this port and communicate with thetarget application. You need to identify the COM port for the backchannel. On Windows PCs, DeviceManager can assist.

Figure 7. Application Backchannel UART in Device Manager

The backchannel UART is the XDS110 Class Application/User UART port. In this case, Figure 7 showsCOM156, but this port can vary from one host PC to the next. After you identify the correct COM port,configure it in your host application according to its documentation. You can then open the port and begincommunication to it from the host.

The XDS110-ET has a configurable baud rate; therefore, it is important that the PC application configuresthe baud rate to be the same as what is configured on the eUSCI_A0 backchannel UART.



http://www.ti.com


Hardware www.ti.com

The XDS110-ET also supports hardware flow control, if desired. Hardware flow control (CTS and RTShandshaking) allows the target MSP432P401R and the emulator to tell each other to wait before sendingmore data. At low baud rates and with simple target applications, flow control may not be necessary.Applications with higher baud rates and more interrupts to service have a higher likelihood that the will notbe able to read the eUSCI_A0 buffer in time, before the next byte arrives. If this happens, the eUSCI_A0will report an overrun error.

2.3.3 Using an External Debugger Instead of the Onboard XDS110-ETMany users have a specific debugger that they prefer to use, and may want to bypass the XDS110-ET toprogram the target MCU. This is enabled by switch S101 and connector J102. Using an external debuggeris simple, and full JTAG access is provided through J102.1. Switch S101 to the external debug position (to the right)2. Plug any ARM debugger into J102

(a) J102 follows the ARM Cortex Debug Connector standard outlined here(b) Note that J102 is not keyed, ensure proper orientation of the debug cable, pin 1 of J102 is on the

bottom right side3. Plug USB power into the LaunchPad, or power it externally

(a) Ensure that the jumper across 3V3 is connected if using USB power(b) External debuggers do not provide power, the VCC pin is a power sense pin(c) More details on powering the LaunchPad can be found in Section 2.4

2.3.4 Using the XDS110-ET Emulator With a Different TargetThe XDS110-ET emulator on the LaunchPad can interface to most ARM derivative devices, not just theon-board MSP432P401R target device.

This is not a common use case, but for users who want this functionality, there is a way to enable it.Connector J103 was added to expose all the necessary programming and power signals. J103 is a 50 milspaced 7-pin header. By default it is not populated, so the user will have to populate a connector ordirectly solder in wires.

When using the XDS110-ET with a different target, the jumpers in the isolation block should be removed,and switch S101 moved to the external debug position. This will disconnect the XDS110-ET from theMSP432P401R target and enable debug of an external device. Because only the SWD signals areexposed, the user needs to set the debugger settings to SWD (without SWO) in the IDE. See the IDEspecific MSP432 user's guides for more details on this setting.

To debug other external devices, there are many options in the ARM debugging ecosystem including theXDS100v2/3 and XDS200 from Texas Instruments. There are many other options including IAR I-jet, KeilULINK, and Segger J-Link.

2.3.5 EnergyTrace+ TechnologyEnergyTrace™ technology is an energy-based code analysis tool that measures and displays theapplication's energy profile and helps to optimize it for ultra-low power consumption.

MSP432 devices with built-in EnergyTrace+[CPU State] (or in short EnergyTrace+) technology allow real-time monitoring of internal device states while user program code executes.

EnergyTrace+ technology is supported on the LaunchPad MSP432P401R device + XDS110-ET debugger.EnergyTrace technology is available as part of TI's Code Composer Studio IDE. During application debug,additional windows are available for EnergyTrace technology.

To enable EnergyTrace technology, go to:• Window > Preferences > Code Composer Studio > Advanced Tools > EnergyTrace™ Technology• Check the Enable Auto-Launch on target connect box



http://www.ti.com

http://infocenter.arm.com/help/topic/com.arm.doc.faqs/attached/13634/cortex_debug_connectors.pdf


www.ti.com Hardware

Figure 8. EnergyTrace Technology Preferences



http://www.ti.com


Hardware www.ti.com

Starting a debug session will now open EnergyTrace technology windows. These windows show energy,power, profile, and states to give the user a full view of the energy profile of their application.

Figure 9. EnergyTrace Windows

This data allows the user to see exactly where and how energy is consumed in their application.Optimizations for energy can be quickly made for the lowest power application possible.

On the LaunchPad, EnergyTrace technology measures the current that enters the target side of theLaunchPad. This includes all BoosterPacks plugged in, and anything else connected to the 3V3 powerrail. For more information about powering the LaunchPad, see Section 2.4.

For more information about EnergyTrace technology, see http://www.ti.com/tool/energytrace.

For more details and questions about setting up and using EnergyTrace technology with theMSP432P401R, see the Code Composer Studio 6 User's Guide for MSP432.



http://www.ti.com

http://www.ti.com/tool/energytrace

http://www.ti.com/lit/pdf/slau575


www.ti.com Hardware

2.4 PowerThe board was designed to accommodate various powering methods, including through the on-boardXDS110-ET and from an external source or BoosterPack.

Figure 10. MSP‑‑EXP432P401R Power Block Diagram

2.4.1 XDS110-ET USB PowerThe most common power-supply scenario is from USB through the XDS110-ET debugger. This provides5-V power from the USB and also regulates this power rail to 3.3 V for XDS110-ET operation and 3.3 V tothe target side of the LaunchPad. Power from the XDS110-ET is controlled by the isolation block 3V3jumper, ensure this jumper is connected for power to be provided to the target MCU side.

Under normal operation, the LDO on the XDS110-ET can supply up to 500 mA of current to the target sideincluding any BoosterPacks plugged in. However, when debugging and using the EnergyTrace technologytool, this current is limited to 75 mA total. Be aware of this current limitation when using EnergyTracetechnology.

2.4.2 BoosterPack and External Power SupplyHeader J6 is present on the board to supply external power directly. It is important to comply with thedevice voltage operation specifications when supplying external power. The MSP432P401R has anoperating range of 1.62 V to 3.7 V. More information can be found in the MSP432P401xx Mixed-SignalMicrocontroller data sheet .



http://www.ti.com

http://www.ti.com/lit/pdf/slas826

http://www.ti.com/lit/pdf/slas826


Hardware www.ti.com

2.5 Measure MSP432 Current DrawTo measure the current draw of the MSP432P401R, use the 3V3 jumper on the jumper isolation block.The current measured includes the target device and any current drawn through the BoosterPackheaders.

To measure ultra-low power, follow these steps:1. Remove the 3V3 jumper in the isolation block, and attach an ammeter across this jumper.2. Consider the effect that the backchannel UART and any circuitry attached to the MSP432P401R may

have on current draw. Disconnect these at the isolation block if possible, or at least consider theircurrent sinking and sourcing capability in the final measurement.

3. Make sure there are no floating input I/Os. These cause unnecessary extra current draw. Every I/Oshould either be driven out or, if it is an input, should be pulled or driven to a high or low level.

4. Begin target execution.5. Measure the current. Keep in mind that if the current levels are fluctuating, it may be difficult to get a

stable measurement. It is easier to measure quiescent states.

For a better look at the power consumed in the application, use EnergyTrace+ Technology. EnergyTrace+Technology allows the user to see energy consumed as the application progresses. More details aboutEnergyTrace+ Technology can be found in Section 2.3.5.

2.6 ClockingThe MSP‑EXP432P401R provides external clocks in addition to the internal clocks in the device.• Q1: 32-kHz crystal (LFXTCLK)• Q2: 48-MHz crystal (HFXTCLK)

The 32-kHz crystal allows for lower LPM3 sleep currents, and higher precision clock source than thedefault internal 32 kHz REFOCLK. Therefore, the presence of the crystal allows the full range of low-power modes to be used.

The 48-MHz crystal allows the device to run at its maximum operating speed for MCLK and HSMCLK.

The MSP432P401R device has several internal clocks that can be sourced from many clock sources.Most peripherals on the device can select which of the internal clocks to use to operate at the desiredspeed.

The internal clocks in the device default to the configuration listed in Table 2.

Table 2. Default Clock Operation

Clock Default Clock Source Default Clock DescriptionFrequency

Master ClockMCLK DCO 3 MHz Sources CPU and peripheralsSubsystem Master ClockHSMCLK DCO 3 MHz Sources peripheralsLow-speed subsystem master clockSMCLK DCO 3 MHz Sources peripherals

LFXT (or REFO if no Auxiliary clockACLK 32.768 kHzcrystal present) Sources peripheralsLFXT(or REFO if no Low-speed backup domain clockBCLK 32.768 kHzcrystal present) Sources LPM peripherals

For more information about configuring internal clocks and using the external oscillators, see theMSP432P4xx Family Technical Reference Manual (SLAU356).



http://www.ti.com

http://www.ti.com/lit/pdf/SLAU356


www.ti.com Hardware

2.7 BoosterPack PinoutThe MSP‑EXP432P401R LaunchPad adheres to the 40-pin LaunchPad pinout standard. A standard wascreated to aid compatibility between LaunchPad and BoosterPack tools across the TI ecosystem.

The 40-pin standard is compatible with the 20-pin standard that is used by other LaunchPads like theMSP‑EXP430FR4133. This allows some subset of functionality of 40-pin BoosterPacks to be used with20-pin LaunchPads.

While most BoosterPacks are compliant with the standard, some are not. The MSP‑EXP432P401RLaunchPad is compatible with all 20-pin and 40-pin BoosterPacks that are compliant with the standard. Ifthe reseller or owner of the BoosterPack does not explicitly indicate compatibility with theMSP‑EXP432P401R LaunchPad, compare the schematic of the candidate BoosterPack with theLaunchPad to ensure compatibility. Keep in mind that sometimes conflicts can be resolved by changingthe MSP432P401R device pin function configuration in software. More information about compatibility canalso be found at http://www.ti.com/launchpad.

Figure 11 shows the 40-pin pinout of the MSP‑EXP432P401R LaunchPad.

Note that software configuration of the pin functions plays a role in compatibility. The MSP‑EXP432P401RLaunchPad side of the dashed line in Figure 11 shows all of the functions for which the MSP432P401Rdevice's pins can be configured. This can also be seen in the MSP432P401R data sheet. TheBoosterPack side of the dashed line shows the standard. The MSP432P401R function whose colormatches the BoosterPack function shows the specific software-configurable function by which theMSP‑EXP432P401R LaunchPad adheres to the standard.



http://www.ti.com

http://www.ti.com/tool/msp-exp430fr4133



Hardware www.ti.com

Figure 11. LaunchPad to BoosterPack Connector Pinout

2.8 Design Files

2.8.1 Hardware Design FilesSchematics can be found in Section 6. All design files including schematics, layout, bill of materials(BOM), Gerber files, and documentation are available in the MSP‑EXP432P401R Hardware Design Files.

2.8.2 Software ExamplesAll design files including TI-TXT object-code firmware images, software example projects, anddocumentation are available in the MSP‑EXP432P401R Software Examples.



http://www.ti.com




www.ti.com Hardware

2.9 Hardware Change Log

Table 3. Hardware Change Log

PCB Revision Date DescriptionRev 1.0 March 2015 Initial Release

3 Software ExamplesThere are four software examples included with the MSP‑EXP432P401R LaunchPad (see Table 4), whichcan be found in the MSP‑EXP432P401R Software Examples.

Table 4. Software Examples

Demo Name BoosterPack Required Description More DetailsThe out-of-box demo pre-programmed on theOut-of-Box Software Example N/A Section 3.1LaunchPad from the factory.

CC3100BOOST MQTT- An IoT application demonstrating controlling anCC3100BOOST Section 3.2Twitter LED Control Example RGB LED using Twitter through Wi-FiA simple example showing how to use MSP

BOOSTXL-K350QVG-S1 Graphics Library (grlib) to display graphicsBOOSTXL-K350SVG-S1 Section 3.3Graphics Library Example primitives and images and implementtouchscreen functionalityA simple example showing how to use MSP430BOOST-SHARP96 430BOOST-SHARP96 Graphics Library (grlib) to display graphics Section 3.4Graphics Library Example primitives and images

To use any of the software examples with the LaunchPad, you must have an integrated developmentenvironment (IDE) that supports the MSP432P401R device.

Table 5. IDE Minimum Requirements for MSP‑‑EXP432P401R

Code Composer Studio™ IDE IAR Embedded Workbench® IDE Keil™ uVision® IDECCS v6.1 or later IAR Embedded Workbench for ARM 7.10 or later Keil uVision MDK-ARM v5 or later

For more details on how to get started quickly and where to download the latest CCS, IAR, and Keil IDEs,see Section 4.

3.1 Out-of-Box Software ExampleThis section describes the functionality and structure of the out-of-box software that is preloaded on theEVM. The source code can be found in the MSP‑EXP432P401R Software Examples download, or moreeasily accessible through MSPWare (See 4.3).

The out-of-box software extends a basic blink LED example to allow users to control the blink rate andcolor of an RGB LED on the MSP432 LaunchPad.

3.1.1 OperationUpon powering up the out-of-box demo, the RGB LED2 blinks red at 1 Hz. Switch S1 can be tappedrepeatedly at a constant rate to set the blink frequency of LED2. Switch S2 cycles LED2 through fourdifferent color settings: Red, Green, Blue, and random RGB color. Each color setting retains its own blinkfrequency.

A PC GUI accompanies the out-of-box demo to allow user to set the color and blink rate of the RGB LED.If not already, connect the LaunchPad using the included USB cable to a computer. The out-of-box GUIcan be opened from within CCS using the TI Resource Explorer: MSPWare > Development Tools >MSP‑EXP432P401R > Examples > Out of Box Experience GUI. A copy can also be found in theMSP‑EXP432P401R Software Examples.



http://www.ti.com





Software Examples www.ti.com

Figure 12. Out-of-Box GUI Running Locally

The GUI can also run directly from the TI Cloud Tools (see Section 4.1.1).



http://www.ti.com


www.ti.com Software Examples

Figure 13. Out-of-Box GUI Running From TI Cloud Tools

Click on the Connect button to connect to the LaunchPad then open the serial COM port. Once theconnection has been established and the GUI indicates, "Target Status: Running…," you can use the colorwheel or the Red, Green, and Blue color sliders to set the color of the LaunchPad RGB LED. Changingthe LED Beats Per Minute input box sets the RGB LED blink rate.

3.2 CC3100BOOST MQTT-Twitter LED Control ExampleThis section describes the functionality and structure of the CC3100BOOST MQTT-Twitter LED Controldemo that is included in the MSP‑EXP432P401R Software Examples download, or more easily accessiblethrough MSPWare (See 4.3).

Note: This CC3100BOOST MQTT-Twitter LED Control demo requires the CC3100BOOST BoosterPackto function properly.

This demo uses the MQTT connectivity protocol to realize a simple Internet-of-Things application thatallows user to control MSP432 LaunchPad RGB LED wirelessly via Twitter tweets.



http://www.ti.com


http://www.ti.com/tool/CC3100BOOST



3.2.1 Source File StructureThe project is split into multiple files. This makes it easier to navigate and reuse parts of it for otherprojects.

Table 6. Source File and Folders

Name Descriptionmain.c The demo's main function, shared ISRs, and so onsl_common.h Common SimpleLink™ technology definitionsDriver: board Board specific driver including basic initializationsDriver: cli_uart Command line interface for backchannel UART communicationDriver: spi_cc3100 MSP432 SPI driver to interface CC3100Driver: uart_cc3100 MSP432 UART driver to interface CC3100Library: mqtt MQTT protocol libraryLibrary: simplelink Simplelink library containing Wi-Fi APIsLibrary: driverlib Device driver library (MSP432DRIVERLIB)

3.2.2 Running the DemoIn order to connect the CC3100BOOST to a wireless access point, start by modifying SSID_NAME andPASSKEY in the #define section of main.c with your wireless access point's information. You may alsoneed to change SEC_TYPE depending on your access point's setting.

Next, using TI Cloud tools or offline IDEs, build and download the project to the MSP432 LaunchPad. Ifnot already, plug the CC3100BOOST BoosterPack onto the LaunchPad, and connect the LaunchPad toyour computer. The CC3100 should automatically try to connect to the access point with the providedcredentials. The LaunchPad outputs status messages through its Application/User UART COM port, whichcan be viewed by opening it using terminal applications (see Section 2.3.2).

Once the CC3100 has established internet connection and successfully subscribed to the public MQTTbroker server, the LaunchPad RGB LED is ready to be controlled with Twitter. Any public tweets in thefollowing format will change the RGB LED color on all MSP‑EXP432P401R LaunchPad running thisdemo:

RGB(red_value, green_value, blue_value) #MSP432LaunchPad

The color parameters can be integers ranging from 0 to 255.

Pressing the left push button S1 on the LaunchPad publishes a 32-bit unique ID from the LaunchPad tothe MQTT broker, which then gets tweeted by the twitter account, @MSPLaunchPad. You may then usethis 32-bit Unique ID in your tweet message to control the RGB LED on the specificLaunchPad+CC3100BOOST combination tied to that unique ID:

<32-bit unique ID> RGB(red_value, green_value, blue_value) #MSP432LaunchPad



http://www.ti.com

https://dev.ti.com/

https://twitter.com/msplaunchpad



3.2.3 Overview of Backend Servers

Figure 14. Backend Block Diagram of CC3100BOOST MQTT-Twitter LED Control Demo

As shown in the above Figure 14, inputs from either the MSP432 LaunchPad or Twitter travel through acouple of intermediary servers before reaching the output on the opposite end. Instead of interacting withTwitter server directly through the more resource intensive HTTP, the MSP432 LaunchPad communicateswith the cloud solely through MQTT protocol. MQTT is a publish-subscribe messaging protocol designedfor lightweight M2M communications. Multiple clients sends message to one another through a serverknown as a broker, and each client can publish messages to different topics and subscribe to multipletopics. While a dedicated MQTT broker can be setup for an application, this demo uses one of the severalMQTT brokers that are freely available to the public, http://iot.eclipse.org/sandbox.html.

Every LaunchPad running the CC3100BOOST MQTT-Twitter LED Control demo subscribes to the MQTTtopic, "/msp/cc3100/demo". This is why any RGB data published to this topic will change the LED color onall LaunchPads running this demo. However, each LaunchPad also subscribes to an "<uniqueID>" topicthat can be used to control LaunchPads individually.

A cloud server is also setup/maintained by the MSP Team using the IBM Bluemix cloud platform service.This server runs a couple of Node-RED applications that interface with Twitter directly through HTTP.After processing public tweets containing #MSP432LaunchPad, the Node-RED server also act as a MQTTclient, publishing color information to either the "/msp/cc3100/demo" or "<uniqueID>" topic, which thengets received on subscribed LaunchPads. Conversely, unique id data published by the LaunchPads to the"/msp/cc3100/demo/fromLP" topic gets received by the Node-RED server, which then tweets a timestamped message on the Twitter account @MSPLaunchPad.

Check out IBM Bluemix to see how you can also build your own cloud application.

3.2.4 Developing With CC3100BOOST BoosterPackA SimpleLink Wi-Fi CC3100 Software Development Kit (SDK) can be downloaded athttp://www.ti.com/tool/cc3100sdk. It contains drivers, many sample applications for Wi-Fi features andinternet, and documentation needed to use the CC3100 Internet-on-a-chip™ solution.

The CC3100BOOST MQTT-Twitter LED Control Demo was developed on CC3100SDK_1.0.0. Servicepack update may be required on the CC3100BOOST with newer SDK release. Refer to the CC3100SimpleLink Wi-Fi and IoT Solution Getting Started Guide for more information.



http://www.ti.com

http://mqtt.org/

http://iot.eclipse.org/sandbox.html

https://console.ng.bluemix.net/

http://nodered.org/

https://twitter.com/msplaunchpad

https://console.ng.bluemix.net/

http://www.ti.com/tool/cc3100sdk

http://www.ti.com/lit/pdf/swru375

http://www.ti.com/lit/pdf/swru375



3.3 BOOSTXL-K350QVG-S1 Graphics Library ExampleThis software is available in the MSP‑EXP432P401R Software Examples, or more easily accessiblethrough MSPWare (see Section 4.3).

The demo shows how to use the MSP Graphics Library http://www.ti.com/tool/msp-grlib or "grlib," in aproject with the Kentec display. This demo shows the user how to enable the touch screen, createbuttons, and use graphics primitives including colors and images.

The program begins by calibrating the touch screen. There is a routine that detects the four cornercoordinates to determine if an eligible rectangle boundary is formed. If the calibration was incorrect, amessage will display on the screen indicating the calibration failed. When successful, the calibrationprovides a reference for all button presses throughout the rest of the program.

The next step is to select the mode of the program- display primitives or images. Each mode simply cyclesthrough without user interaction to show off features of the display. In the graphics primitives mode, thefollowing primitives are shown:• Pixels• Lines• Circles• Rectangles• Text

The application is heavily commented to ensure it is very clear how to use the grlib APIs. The aboveprimitives are shown as well as the underlying concepts of grlib including background and foregroundcolors, context, fonts, opacity, and more.

The images mode shows the drawing of a few different images both compressed and uncompressed.Image compression can have a big impact to drawing speeds for simple images. To draw images with theMSP Graphics Library, they must first be converted into the right file format. These files can be generatedby the Image Reformer tool that comes packaged with grlib. Launch this tool from the grlib folder or directfrom TI Resource Explorer.• File Path: <grlib root>\utils\image-reformer\imagereformer.exe• TI Resource Explorer > MSPWare > Libraries > Graphics Library > MSP430 Image Reformer

The Image Reformer tool allows you to import images and output into grlib specific files to add to yourgrlib project. Image Reformer does not manipulate any images (such as color modifications, rotation, orcropping), any image manipulation must be done before importing into the Image Reformer tool. Moreinformation about MSP grlib and the Image Reformer tool can be found in the Design Considerationswhen Using MSP430 Graphics Library application note.



http://www.ti.com


http://www.ti.com/tool/msp-grlib

http://www.ti.com/lit/pdf/slaa548

http://www.ti.com/lit/pdf/slaa548



Figure 15. Importing and Converting an Image With MSP Image Reformer

3.4 430BOOST-SHARP96 Graphics Library ExampleThis software example is similar to the BOOSTXL-K350QVG-S1 Graphics library example. It shows howto use the MSP Graphics Library http://www.ti.com/tool/msp-grlib or "grlib," in a project with the Sharp96×96 display. The Sharp 96×96 display BoosterPack does not support touch or color, it is a simplemonochrome LCD. It is a great LCD for ultra-low power display applications and has a unique mirroredpixel display.

This demo cycles screens without user interaction to show simple graphics primitives.• Pixels• Lines• Circles• Rectangles• Text• Images

This demo introduces the functions to configure grlib such as initialization, color inversion, and usingforeground and background colors properly.



http://www.ti.com

http://www.ti.com/tool/msp-grlib


Resources www.ti.com

4 Resources

4.1 Integrated Development EnvironmentsAlthough the source files can be viewed with any text editor, more can be done with the projects if they'reopened with a development environment like Code Composer Studio™ (CCS), Keil™ uVision®, IAREmbedded Workbench®, or Energia.

4.1.1 TI Cloud Development ToolsTI's Cloud-based software development tools provide instant access to MSPWare content and a web-based IDE.

4.1.1.1 TI Resource Explorer CloudTI Resource Explorer Cloud provides a web interface for browsing examples, libraries and documentationfound in MSPWare without having to download files to your local drive.

Go check out TI Resource Explorer Cloud now at dev.ti.com.

4.1.1.2 Code Composer Studio CloudCode Composer Studio Cloud is a web-based IDE that allows code edit, compile and download to devicesright from your web browser. It also integrates seamlessly with TI Resource Explorer Cloud with the abilityto import projects directly on the cloud.

A full comparison between CCS Cloud and CCS Desktop is available here.

See Code Composer Studio Cloud now at dev.ti.com.

4.1.2 Code Composer StudioCode Composer Studio Desktop is a professional integrated development environment that supports TI'sMicrocontroller and Embedded Processors portfolio. Code Composer Studio comprises a suite of toolsused to develop and debug embedded applications. It includes an optimizing C/C++ compiler, source codeeditor, project build environment, debugger, profiler, and many other features.

Note: MSP432 LaunchPad requires CCS Version 6.1.0 or later. Refer to the Code Composer Studio 6.1for MSP432 User’s Guide (SLAU575) for detailed instructions of using the IDE with MSP432.

You can learn more about CCS and download it at http://www.ti.com/tool/ccstudio.

4.1.3 Keil uVisionuVision IDE is an embedded project development environment included in Keil's MicrocontrollerDevelopment Kit Version 5, that provides an source code editor, project manager, and make utility tool.µVision supports all the Keil tools including C/C++ Compiler, Macro Assembler, Linker, Library Manager,and Object-HEX Converter.

Note: MSP432 LaunchPad requires uVision IDE/MDK Version 5 or later. Refer to the ARM Keil MDK 5IDE for MSP432 User's Guide (SLAU590) for detailed instructions of using the IDE with MSP432.

You can learn more about Keil uVision and download it at http://www.keil.com/arm/mdk.asp.



http://www.ti.com

http://www.ti.com/ww/en/launchpad/software.html

http://dev.ti.com/

https://dev.ti.com/about#cloudordesktop

http://dev.ti.com/


http://www.ti.com/tool/ccstudio


http://www.keil.com/arm/mdk.asp


www.ti.com Resources

4.1.4 IAR Embedded Workbench for ARMIAR Embedded Workbench for ARM is another very powerful integrated development environment thatallows you to develop and manage complete embedded application projects. It integrates the IAR C/C++Compiler, IAR Assembler, IAR ILINK Linker, editor, project manager, command line build utility, and IARC-SPY Debugger.

Note: MSP432 LaunchPad requires IAR Embedded Workbench for ARM Version 7.10 or later. Refer tothe IAR Embedded Workbench for ARM 7.40.2 for MSP432 User's Guide (SLAU574) for detailedinstructions of using the IDE with MSP432.

You can learn more about IAR Embedded Workbench and download it at https://www.iar.com/iar-embedded-workbench/arm.

4.1.5 EnergiaEnergia is a simple open-source community-driven code editor that is based on the Wiring and Arduinoframework. Energia provides unmatched ease of use through very high level APIs that can be used acrosshardware platforms. Energia is a light-weight IDE that doesn't have the full feature set of CCS, Keil, orIAR. However, Energia is great for anyone who wants to get started very quickly or who doesn't havesignificant coding experience.

You can learn more about Energia and download it at www.energia.nu.

4.2 LaunchPad WebsitesMore information about the LaunchPad, supported BoosterPacks, and available resources can be foundat:• MSP‑EXP432P401R tool folder: Resources specific to this particular LaunchPad kit• TI's LaunchPad portal: Information about all LaunchPad kits from TI

4.3 MSPWare and TI Resource ExplorerTI Resource Explorer is a tool integrated into CCS that allows you to browse through available designresources. TI Resource Explorer will help you quickly find what you need inside packages includingMSPWare, ControlSuite, TivaWare and more. TI Resource Explorer is well organized to find everythingthat you need quickly, and you can import software projects into your workspace in one click!

TI Resource Explorer Cloud is one of the TI Cloud Development tools, and is tightly integrated with CCSCloud. See Section 4.1.1 for more information.

MSPWare is a collection of code examples, software libraries, data sheets, and other design resources forall MSP devices delivered in a convenient package – essentially everything developers need to becomeMSP experts!

In addition to providing a complete collection of existing MSP design resources, MSPWare also includes ahigh-level API called MSP Driver Library. This library makes it easy to program MSP hardware. Moreinformation can be found at http://www.ti.com/tool/mspware.



http://www.ti.com


https://www.iar.com/iar-embedded-workbench/arm

https://www.iar.com/iar-embedded-workbench/arm

http://wiring.org.co/

http://arduino.cc/

http://www.energia.nu/



http://www.ti.com/tool/mspware


Resources www.ti.com

Figure 16. Using TI Resource Explorer to Browse MSP‑‑EXP432P401R in MSPWare

Inside TI Resource Explorer, these examples and many more can be found and easily imported into CCSwith one click.



http://www.ti.com


www.ti.com Resources

4.4 MSP432P401R

4.4.1 Device DocumentationAt some point, you will probably want more information about the MSP432P401R device. For every MSPdevice, the documentation is organized as shown in Table 7.

Table 7. How MSP Device Documentation is Organized

Document For MSP432P401R DescriptionArchitectural information about the device,Device family MSP432P4xx Family Technical Reference Manual including all modules and peripherals such asuser's guide clocks, timers, ADC, and so on.

Device-specific Device-specific information and all parametricMSP432P401xx Mixed-Signal Microcontroller data sheetdata sheet information for this device

4.4.2 MSP432P401R Code ExamplesThis is a set of very simple MSP432P401xx code examples that demonstrate how to use the entire set ofMSP432 peripherals: serial communication, ADC14, Timer_A, Timer_B, and so on. These examples showboth the direct register access and driver library methods.

Every MSP derivative has a set of these code examples. When starting a new project or adding a newperipheral, these examples serve as a great starting point.

4.4.3 MSP432 Application Notes and TI DesignsThere are many application notes that can be found at www.ti.com/msp432, as well as TI Designs withpractical design examples and topics.

4.5 Community Resources

4.5.1 TI E2E™ CommunitySearch the E2E forums at e2e.ti.com. If you cannot find your answer, post your question to thecommunity!

4.5.2 Community at LargeMany online communities focus on the LaunchPad; for example, http://www.43oh.com. You can findadditional tools, resources, and support from these communities.



http://www.ti.com


http://www.ti.com/lit/pdf/SLAS826

http://www.ti.com/lit/zip/slac698

http://www.ti.com/msp432

http://www.ti.com/general/docs/refdesignsearch.tsp

http://e2e.ti.com/

http://www.43oh.com/


FAQ www.ti.com

5 FAQQ: I can't program my LaunchPad; the IDE can't connect to target. What's wrong?

A: Check the following:• Is the JTAG switch (S101) in the correct orientation?

– Switch to left for XDS110-ET onboard debugger– Switch to the right for external debugger connection

• If using an external debugger, is USB power provided?• Check the debugger settings: change to Serial Wire Debug (SWD) without SWO

– Under targetconfigs, double-click the *.ccxml file– Click the Advanced tab at the bottom– Click on Texas Instruments XDS110 USB Debug Probe– Under Connection Properties, change SWD Mode Settings to Use SWD Mode with SWO Trace

Disabled

Figure 17. SWD Mode Settings

– When the settings of Port J (PJSEL0 and PJSEL1 bits) are changed, full JTAG access is preventedon these pins. Changing to use SWD allows access through the dedicated debug pins only.

• If even this cannot connect, reset the device to factory settings– Click View → Target Configurations. CCS shows the target configuration.

Figure 18. Target Configurations

If using the onboard emulator, XDS110-ET is shown.



http://www.ti.com


www.ti.com FAQ

– Right click Launch Selected Configuration.

Figure 19. Launch Selected Configuration

– The debugger now connects to the device (which is still possible) but does not try to halt the CPU,write to registers, or even download code (which would not be possible). The Debug view that isspawned shows the CPU core but marks it as disconnected.

– Right click Show all cores.

Figure 20. Show All Cores



http://www.ti.com


FAQ www.ti.com

The MSP432 Debug Access Port, or DAP, is shown under Non Debuggable Devices.– Right click Connect Target

Figure 21. Connect Target

Now run a script to return the device back to factory settings:

Scripts > default > MSP432_Factory_Reset

Figure 22. MSP432_Factory_Reset Script

• These instructions are generally the same for all IDEs, but the exact steps may vary slightly by IDE.See the following MSP432 IDE user's guides for additional details:– Code Composer Studio 6 for MSP432 User's Guide– Keil uVision IDE Version 5 for MSP432 User's Guide– IAR Embedded Workbench for ARM 7.10 for MSP432 User's Guide



http://www.ti.com





www.ti.com FAQ

Q: How do I use the LaunchPad and my Segger J-Link to debug the target externally? It won't connect tothe onboard connector.

A: The Segger J-Link is the only major ARM debugger that doesn't come with an adapter for the 10-pinsmall pitch ARM connector. The adapter cable is found here, and can be purchased from Digi-Key here

Q: Why doesn't the back-channel UART on the MSP432 LaunchPad work with my serial terminal programat speeds faster than 56000 baud?

A: Certain serial terminal programs such as HTerm or the CCS built-in terminal might not work with theMSP432 LaunchPad at specific baud rates, resulting in the software not being able to open the virtualCOM port or in the baud rate being configured incorrectly. An issue with the LaunchPad emulator firmwarehas been identified and will be fixed in the next release. Until the update is available, use Tera Term,ClearConnex, or HyperTerminal instead, or reduce the baud rate to speeds of 38400 baud or lower.

Q: Problems plugging the MSP432 LaunchPad into a USB3.0 Port

A: It has been observed that when the MSP432 LaunchPad is connected to USB3.0 ports provided by acertain combination of USB3.0 host controller hardware and associated device drivers that the IDE isunable to establish a debug session with the LaunchPad, resulting in an error message like "CS_DAP_0:Error connecting to the target: (Error -260 @ 0x0) An attempt to connect to the XDS110 failed." in thecase of Code Composer Studio. In this case the CCS-provided low-level command line utility ‘xdsdfu' willalso not be able to establish a connection with the LaunchPad.

Specifically, this issue was observed on PCs running Windows 7 that show the "Renesas Electronics USB3.0 Host Controller" and the associated "Renesas Electronics USB 3.0 Root Hub" in the device manager.After updating the associated Windows USB drivers to more recent versions obtained from the hardwarevendor the issue went away. There might be other USB3.0 hardware and device driver combinations thatwill lead to the same issue. If you think you might be affected try contacting your PC vendor or try locatingand installing more recent versions of the USB3.0 device drivers. Alternatively, connect the LaunchPad toan USB2.0 port on your PC if available.

Q: I can't get the backchannel UART to connect. What's wrong?

A: Check the following:• Do the baud rate in the host's terminal application and the eUSCI settings match?• Are the appropriate jumpers in place, on the isolation jumper block?• Probe on RXD and send data from the host. If you don't see data, it might be a problem on the host

side.• Probe on TXD while sending data from the MSP432. If you don't see data, it might be a configuration

problem with the eUSCI module.• Consider the use of the hardware flow control lines (especially for higher baud rates).



http://www.ti.com

http://shop-us.segger.com/J_Link_9_Pin_Cortex_M_Adapter_p/8.06.02.htm

http://www.digikey.com/product-detail/en/8.06.02%20J-LINK%209-PIN%20CORTEX-M%20ADAPTER/899-1012-ND/2421158


A B C D

12

34

56

A B C D

12

34

56

P10.1

/UC

B3C

LK

1

P10.2

/UC

B3S

IMO

/UC

B3S

DA

2

P1.0

/UC

A0S

TE

4

P1.1

/UC

A0C

LK

5

P1.2

/UC

A0R

XD

/UC

A0S

OM

I6

P1.3

/UC

A0T

XD

/UC

A0S

IMO

7

P1.4

/UC

B0S

TE

8

P1.5

/UC

B0C

LK

9

P1.6

/UC

B0S

IMO

/UC

B0S

DA

10

P1.7

/UC

B0S

OM

I/U

CB

0S

CL

11

P2.0

/PM

_U

CA

1S

TE

16

P2.1

/PM

_U

CA

1C

LK

17

P2.2

/PM

_U

CA

1R

XD

/PM

_U

CA

1S

OM

I18

P2.3

/PM

_U

CA

1T

XD

/PM

_U

CA

1S

IMO

19

P2.4

/PM

_TA

0.1

20

P2.5

/PM

_TA

0.2

21

P2.6

/PM

_TA

0.3

22

P2.7

/PM

_TA

0.4

23

P3.0

/PM

_U

CA

2S

TE

32

P3.1

/PM

_U

CA

2C

LK

33

P3.2

/PM

_U

CA

2R

XD

/PM

_U

CA

2S

OM

I34

P3.3

/PM

_U

CA

2T

XD

/PM

_U

CA

2S

IMO

35

P3.4

/PM

_U

CB

2S

TE

36

P3.5

/PM

_U

CB

2C

LK

37

P3.6

/PM

_U

CB

2S

IMO

/PM

_U

CB

2S

DA

38

P3.7

/PM

_U

CB

2S

OM

I/P

M_U

CB

2S

CL

39

P4.0

/A13

56

P4.1

/A12

57

P4.2

/AC

LK

/TA

2C

LK

/A11

58

P4.3

/MC

LK

/RT

CC

LK

/A10

59

P4.4

/HS

MC

LK

/SV

MH

OU

T/A

960

P4.5

/A8

61

P4.6

/A7

62

P4.7

/A6

63

P5.0

/A5

64

P5.1

/A4

65

P5.2

/A3

66

P5.3

/A2

67

P5.4

/A1

68

P5.5

/A0

69

P5.6

/TA

2.1

/VR

EF

+/V

ER

EF

+/C

1.7

70

P5.7

/TA

2.2

/VR

EF

-/V

ER

EF

-/C

1.6

71

P6.0

/A15

54

P6.1

/A14

55

P6.2

/UC

B1S

TE

/C1.5

76

P6.3

/UC

B1C

LK

/C1.4

77

P6.4

/UC

B1S

IMO

/UC

B1S

DA

/C1.3

78

P6.5

/UC

B1S

OM

I/U

CB

1S

CL/C

1.2

79

P6.6

/TA

2.3

/UC

B3S

IMO

/UC

B3S

DA

/C1.1

80

P6.7

/TA

2.4

/UC

B3S

OM

I/U

CB

3S

CL/C

1.0

81

P10.3

UC

B3S

OM

I/U

CB

3S

CL

3

P9.7

/UC

A3T

XD

/UC

A3S

IMO

99

P9.6

/UC

A3R

XD

/UC

A3S

OM

I98

P9.5

/UC

A3C

LK

97

P9.4

/UC

A3S

TE

96

P9.3

/TA

3.4

75

P9.2

/TA

3.3

74

P9.1

/A16

53

P9.0

/A17

52

P8.7

/A18

51

P8.6

/A19

50

P8.5

/A20

49

P8.4

/A21

48

P8.3

/TA

3C

LK

/A22

47

P8.2

/TA

3.2

/A23

46

P8.1

/UC

B3C

LK

/TA

2.0

/C0.0

31

P8.0

/UC

B3S

TE

/TA

1.0

/C0.1

30

P7.0

/PM

_S

MC

LK

/PM

_D

MA

E0

88

P7.1

/PM

_C

0O

UT

/PM

_TA

0C

LK

89

P7.2

/PM

_C

1O

UT

/PM

_TA

1C

LK

90

P7.3

/PM

_TA

0.0

91

P7.4

/PM

_TA

1.4

/C0.5

26

P7.5

/PM

_TA

1.3

/C0.4

27

P7.6

/PM

_TA

1.2

/C0.3

28

P7.7

/PM

_TA

1.1

/C0.2

29

DV

SS

382

SW

DIO

TM

S94

PJ.5

/TD

O/S

WO

93

PJ.4

/TD

I/A

DC

14C

LK

92

PJ.3

/HF

XIN

86

PJ.2

/HF

XO

UT

85

PJ.1

/LF

XO

UT

42

PJ.0

/LF

XIN

41

SW

CLK

TC

K95

AV

SS

340

RS

TN

/NM

I83

DC

OR

44

DV

SS

272

DV

SS

115

AV

SS

284

AV

SS

143

AV

CC

287

AV

CC

145

DV

CC

273

DV

CC

113

VC

OR

E12

VS

W14

P10.5

/TA

3.1

/C0.6

25

P10.4

/TA

3.0

/C0.7

24

P10.0

/UC

B3S

TE

100

31

Schematics www.ti.com

6 Schematics

Figure 23. Schematics (1 of 7)



http://www.ti.com


A B C D

12

34

56

A B C D

12

34

56

12

12

12

1

2

1

2

1

2

1

2

1 2 3

1 2 3

www.ti.com Schematics




http://www.ti.com


A B C D

12

34

56

A B C D

12

34

56

1

2

1

2

1

2

1

2

1

2

1

2

1 2 3 4 5 6 7 8 9 10

20

19

18

17

16

15

14

13

12

11

21

22

23

24

25

26

27

28

29

30

40

39

38

37

36

35

34

33

32

31

11

33

55

77

99

11

11

13

13

15

15

17

17

19

19

21

21

23

23

25

25

27

27

29

29

31

31

33

33

35

35

37

37

38

38

36

36

34

34

32

32

30

30

28

28

26

26

24

24

22

22

20

20

18

18

16

16

14

14

12

12

10

10

88

66

44

22





http://www.ti.com


A B C D

12

34

56

A B C D

12

34

56

PA

0P

$3

3

PA

1P

$3

4

PA

2P

$3

5

PA

3P

$3

6

PA

4P

$3

7

PA

5P

$3

8

PA

6P

$4

0

PA

7P

$4

1

PB

0P

$9

5

PB

1P

$9

6

PB

2P

$9

1

PB

3P

$9

2

PB

4P

$1

21

PB

5P

$1

20

PC

0P

$1

00

PC

1P

$9

9

PC

2P

$9

8

PC

3P

$9

7

PC

4P

$2

5

PC

5P

$2

4

PC

6P

$2

3

PC

7P

$2

2

PD

0P

$1

PD

1P

$2

PD

2P

$3

PD

3P

$4

PD

4P

$1

25

PD

5P

$1

26

PD

6P

$1

27

PD

7P

$1

28

PE

0P

$1

5

PE

1P

$1

4

PE

2P

$1

3

PE

3P

$1

2

PE

4P

$1

23

PE

5P

$1

24

PF

0P

$4

2

PF

1P

$4

3

PF

2P

$4

4

PF

3P

$4

5

PF

4P

$4

6

PG

0P

$4

9

PG

1P

$5

0P

H0

P$

29

PH

1P

$3

0

PH

2P

$3

1

PH

3P

$3

2P

J0

P$

116

PJ1

P$

117

PK

0P

$1

8

PK

1P

$1

9

PK

2P

$2

0

PK

3P

$2

1

PK

4P

$6

3

PK

5P

$6

2

PK

6P

$6

1

PK

7P

$6

0

PL

0P

$8

1

PL

1P

$8

2

PL

2P

$8

3

PL

3P

$8

4

PL

4P

$8

5

PL

5P

$8

6

PL

6P

$9

4

PL

7P

$9

3

PM

0P

$7

8

PM

1P

$7

7

PM

2P

$7

6

PM

3P

$7

5

PM

4P

$7

4

PM

5P

$7

3

PM

6P

$7

2

PM

7P

$7

1

PN

0P

$1

07

PN

1P

$1

08

PN

2P

$1

09

PN

3P

$11

0

PN

4P

$11

1

PN

5P

$11

2

PP

0P

$11

8

PP

1P

$11

9

PP

2P

$1

03

PP

3P

$1

04

PP

4P

$1

05

PP

5P

$1

06

PQ

0P

$5

PQ

1P

$6

PQ

2P

$11

PQ

3P

$2

7

PQ

4P

$1

02

HIB

P$

65

RE

SE

TP

$7

0

WA

KE

P$

64

EN

0R

XIN

P$

53

EN

0R

XIP

P$

54

EN

0T

XO

NP

$5

6

EN

0T

XO

PP

$5

7

GN

DP

$1

7

GN

DP

$4

8

GN

DP

$5

5

GN

DP

$5

8

GN

DP

$8

0

GN

DP

$11

4

GN

DA

P$

10

OS

C0

P$

88

OS

C1

P$

89

RB

IAS

P$

59

VB

AT

P$

68

VD

DP

$7

VD

DP

$1

6

VD

DP

$2

6

VD

DP

$2

8

VD

DP

$3

9

VD

DP

$4

7

VD

DP

$5

1

VD

DP

$5

2

VD

DP

$6

9

VD

DP

$7

9

VD

DP

$9

0

VD

DP

$1

01

VD

DP

$11

3

VD

DP

$1

22

VD

DA

P$

8

VD

DC

P$

87

VD

DC

P$

115

VR

EFA

+P

$9

XO

SC

0P

$6

6

XO

SC

1P

$6

7

OSC0 1NC2

OSC13 NC2 4

1

A 1

NC_2 2

C3

NC_34NC5





http://www.ti.com


A B C D

12

34

56

A B C D

12

34

56

1 2 3 4 5 6 710

11

12

13

14

15

16

89T

P

EN

1G

ND

2IN

23

OU

T4

IN1

5





http://www.ti.com


A B C D

12

34

56

A B C D

12

34

56

1 1 1 1 1 111

OU

T1

NC

02

NR

3

GND4

EN

5

NC

16

NC

27

IN8

PAD9

RE

FC

LK

1

NX

T2

DA

TA

03

DA

TA

14

DA

TA

25

DA

TA

36

DA

TA

47

NC

_2

8

DA

TA

59

DA

TA

61

0

CS

11

VD

D1

51

2

DA

TA

71

3

CF

G1

4

NC

_3

15

NC

_4

16

CP

EN

17

DP

18

DM

19

VD

D3

32

0V

BA

T2

1V

BU

S2

2ID

23

NC

_5

24

NC

25

CL

OC

K2

6R

ES

ET

B2

7V

DD

18

_2

28

ST

P2

9V

DD

18

30

DIR

31

VD

DIO

32

EP

AD

33

IN1

GN

D2

OU

T3

NC

_2

4N

C5

EN

6

IO1

1

IO2

2

GN

D3

IO3

4IO

45

VC

C6

1

D+

D-

GN

DN

C

VB

US





http://www.ti.com


A B C D

12

34

56

A B C D

12

34

56

*1O

E1

VC

CB

2V

CC

A3

1D

IR4

2D

IR5

1A

16

1A

27

2A

18

2A

29

GN

D_2

10

GN

D11

2B

212

2B

113

1B

214

1B

115

*2O

E16

*1O

E1

VC

CB

2V

CC

A3

1D

IR4

2D

IR5

1A

16

1A

27

2A

18

2A

29

GN

D_2

10

GN

D11

2B

212

2B

113

1B

214

1B

115

*2O

E16

*1O

E1

VC

CB

2V

CC

A3

1D

IR4

2D

IR5

1A

16

1A

27

2A

18

2A

29

GN

D_2

10

GN

D11

2B

212

2B

113

1B

214

1B

115

*2O

E16

1B

116

1B

21

2B

13

2B

24

3B

19

3B

28

4B

112

4B

211

1A

2

2A

5

3A

7

4A

10

SE

L15

OE

13

VC

C14

GN

D6

1 2 3 4 5 6 7

12

34

56

78

910

C1

2L1

1

L2

3

C2

5L3

4

L4

6





http://www.ti.com


www.ti.com Revision History

Revision History

Changes from March 21, 2015 to July 20, 2015 .............................................................................................................. Page

• Throughout the document, changed the link destinations for the MSP‑EXP432P401R Hardware Design Files and theMSP‑EXP432P401R Software Examples.............................................................................................. 1

NOTE: Page numbers for previous revisions may differ from page numbers in the current version.

39SLAU597A–March 2015–Revised July 2015 Revision HistorySubmit Documentation Feedback


http://www.ti.com


IMPORTANT NOTICE

Texas Instruments Incorporated and its subsidiaries (TI) reserve the right to make corrections, enhancements, improvements and otherchanges to its semiconductor products and services per JESD46, latest issue, and to discontinue any product or service per JESD48, latestissue. Buyers should obtain the latest relevant information before placing orders and should verify that such information is current andcomplete. All semiconductor products (also referred to herein as “components”) are sold subject to TI’s terms and conditions of salesupplied at the time of order acknowledgment.TI warrants performance of its components to the specifications applicable at the time of sale, in accordance with the warranty in TI’s termsand conditions of sale of semiconductor products. Testing and other quality control techniques are used to the extent TI deems necessaryto support this warranty. Except where mandated by applicable law, testing of all parameters of each component is not necessarilyperformed.TI assumes no liability for applications assistance or the design of Buyers’ products. Buyers are responsible for their products andapplications using TI components. To minimize the risks associated with Buyers’ products and applications, Buyers should provideadequate design and operating safeguards.TI does not warrant or represent that any license, either express or implied, is granted under any patent right, copyright, mask work right, orother intellectual property right relating to any combination, machine, or process in which TI components or services are used. Informationpublished by TI regarding third-party products or services does not constitute a license to use such products or services or a warranty orendorsement thereof. Use of such information may require a license from a third party under the patents or other intellectual property of thethird party, or a license from TI under the patents or other intellectual property of TI.Reproduction of significant portions of TI information in TI data books or data sheets is permissible only if reproduction is without alterationand is accompanied by all associated warranties, conditions, limitations, and notices. TI is not responsible or liable for such altereddocumentation. Information of third parties may be subject to additional restrictions.Resale of TI components or services with statements different from or beyond the parameters stated by TI for that component or servicevoids all express and any implied warranties for the associated TI component or service and is an unfair and deceptive business practice.TI is not responsible or liable for any such statements.Buyer acknowledges and agrees that it is solely responsible for compliance with all legal, regulatory and safety-related requirementsconcerning its products, and any use of TI components in its applications, notwithstanding any applications-related information or supportthat may be provided by TI. Buyer represents and agrees that it has all the necessary expertise to create and implement safeguards whichanticipate dangerous consequences of failures, monitor failures and their consequences, lessen the likelihood of failures that might causeharm and take appropriate remedial actions. Buyer will fully indemnify TI and its representatives against any damages arising out of the useof any TI components in safety-critical applications.In some cases, TI components may be promoted specifically to facilitate safety-related applications. With such components, TI’s goal is tohelp enable customers to design and create their own end-product solutions that meet applicable functional safety standards andrequirements. Nonetheless, such components are subject to these terms.No TI components are authorized for use in FDA Class III (or similar life-critical medical equipment) unless authorized officers of the partieshave executed a special agreement specifically governing such use.Only those TI components which TI has specifically designated as military grade or “enhanced plastic” are designed and intended for use inmilitary/aerospace applications or environments. Buyer acknowledges and agrees that any military or aerospace use of TI componentswhich have not been so designated is solely at the Buyer's risk, and that Buyer is solely responsible for compliance with all legal andregulatory requirements in connection with such use.TI has specifically designated certain components as meeting ISO/TS16949 requirements, mainly for automotive use. In any case of use ofnon-designated products, TI will not be responsible for any failure to meet ISO/TS16949.

Products ApplicationsAudio www.ti.com/audio Automotive and Transportation www.ti.com/automotiveAmplifiers amplifier.ti.com Communications and Telecom www.ti.com/communicationsData Converters dataconverter.ti.com Computers and Peripherals www.ti.com/computersDLP® Products www.dlp.com Consumer Electronics www.ti.com/consumer-appsDSP dsp.ti.com Energy and Lighting www.ti.com/energyClocks and Timers www.ti.com/clocks Industrial www.ti.com/industrialInterface interface.ti.com Medical www.ti.com/medicalLogic logic.ti.com Security www.ti.com/securityPower Mgmt power.ti.com Space, Avionics and Defense www.ti.com/space-avionics-defenseMicrocontrollers microcontroller.ti.com Video and Imaging www.ti.com/videoRFID www.ti-rfid.comOMAP Applications Processors www.ti.com/omap TI E2E Community e2e.ti.comWireless Connectivity www.ti.com/wirelessconnectivity

Mailing Address: Texas Instruments, Post Office Box 655303, Dallas, Texas 75265Copyright © 2015, Texas Instruments Incorporated

http://www.ti.com/audio

http://www.ti.com/automotive

http://amplifier.ti.com

http://www.ti.com/communications

http://dataconverter.ti.com

http://www.ti.com/computers

http://www.dlp.com

http://www.ti.com/consumer-apps

http://dsp.ti.com

http://www.ti.com/energy

http://www.ti.com/clocks

http://www.ti.com/industrial

http://interface.ti.com

http://www.ti.com/medical

http://logic.ti.com

http://www.ti.com/security

http://power.ti.com

http://www.ti.com/space-avionics-defense

http://microcontroller.ti.com

http://www.ti.com/video

http://www.ti-rfid.com

http://www.ti.com/omap

http://e2e.ti.com

http://www.ti.com/wirelessconnectivity

msp432p401r launchpad™ development kit (msp …• out-of-box software example • cc3100boost...

Documents