MSP432P401R LaunchPad External Target Mod

Kevin,

Thank you for taking the time to write up your solution and share it with the community. It should be noted that section 2.3.4 of the MSP432P401R LaunchPad Development Kit (MSP‑EXP432P401R) User's Guide covers using the XDS110-ET emulator with a different target without the need to modify hardware traces. I think the confusion mainly stems from the fact that because only the SWD signals are exposed, the user needs to set the debugger settings to SWD (without SWO) in the IDE.

www.ti.com/.../slau597a.pdf

Regards,
Ryan

This modification is still useful if you want to debug a target that doesn't support SWD debugging, such as the CC26xx.

Also, there are instructions on how to select SWD (without SWO) in this post: https://e2e.ti.com/support/microcontrollers/msp430/f/166/p/421055/1513759#1513759

One comment on the PDF: it says to leave S101 in the "XDS-ET" position. I think it should be switched to "Ext. Debug" instead, as that disconnects the MSP432 target from the debugger. All of the connections for your cable are upstream of the switching points, so the debugger should still connect to the external target without any problem.

UPDATE: The XDS110 firmware now supports cJTAG 2-wire debugging. That means that the debug connections exposed at J103 are sufficient to program/debug a CC26xx target.

The extra connections at S101 and tapping into the trace from pin 12 of IC111 are no longer required.

Ryan,

Thank you for clearing some points, but we are not talkin about same launchpad. in the red one that you mentioned, the j102 can be used to debug an external target, but in the black one that Kevin mentioned, j102 is header for an external debugger. So a hardware modification is necessary i think.

Regards

Labidi,

This thread was concluded long before the red MSP-EXP432P401R LaunchPad revision was released.

Regards,
Ryan