Texas Instruments MSP-EXP432P4111, User Manual

Page: 26 / 40

FAQ
www.ti.com
26 SLAU747B – October 2017 – Revised January 2019
Submit Documentation Feedback
Copyright © 2017–2019, Texas Instruments Incorporated
MSP432P4111 SimpleLink™ microcontroller LaunchPad™ development kit
(MSP-EXP432P4111)
Figure 20. MSP432_Factory_Reset Script
• The preceding instructions are generally the same for all IDEs, but the exact steps may vary slightly by
IDE. See the following IDE user’s guides for additional details:
– Code Composer Studio™ IDE 7.1+ for SimpleLink™ MSP432™ Microcontrollers User's Guide
– Arm® Keil® MDK Version 5 for SimpleLink™ MSP432™ Microcontrollers User's Guide
– IAR Embedded Workbench for Arm 7.x for SimpleLink™ MSP432™ Microcontrollers User's Guide
Q: How do I use the LaunchPad development kit and my Segger J-Link to debug the target
externally? It won’t connect to the onboard connector?
A: The Segger J-Link does not come with an adapter for the 10-pin small-pitch Arm connector. The
adapter cable is available from
Segger .
Q: Problems plugging the MSP432 LaunchPad into a USB3.0 Port
A: It has been observed that when the MSP432 LaunchPad development kit is connected to USB3.0 ports
provided by a certain combination of USB3.0 host controller hardware and associated device drivers that
the IDE is unable to establish a debug session with the LaunchPad development kit, 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 the case of Code Composer Studio. In this case the CCS-provided low-level command
line utility ‘xdsdfu’ will also 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 USB
3.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 hardware
vendor the issue went away. There might be other USB3.0 hardware and device driver combinations that
will lead to the same issue. If you think you might be affected try contacting your PC vendor or try locating
and installing more recent versions of the USB3.0 device drivers. Alternatively, connect the LaunchPad
development kit to an USB2.0 port on your PC if available.
Q: I cant 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.