MSP432 and XDS110 Debug Probe Error 261

Hi,
I managed to lock up an MSP432E411 by loading an application that programmed the JTAG pins as GPIO. The symptom was fairly similar to yours - the debugger could not detect the micro.
I described the unlock process that I used in another forum question for yet another poor soul who had also locked his chip and it worked for him. Might work for you! See here:-
e2e.ti.com/.../msp432e401y-launchpad-cortex_m4_0-file-loader-memory-write-failed-flash-programmer-verify-error-writing-to-flash-failed

Hi Ted,

Ted Fryberger said:

So something is wrong with my 1st target board (PCB-A). Is the 432 dead or somehow locked up to cause this error?

It appears some issue specific to your first board. I would check the suggestion Jim offered. I will also bring this thread to the attention of the device experts for more suggestions.

Thanks

ki

Thanks Jim, & Ki,

I'll try your suggestion Jim, and as this is vaguely similar to a problem I had with a MSP-EXP432P401R LaunchPad, I've added the link below on resetting the MCU on it. If your suggestion doesn't work I'll try that.

https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/981959/msp-exp432p401r-msp432-launchpad-no-longer-useable

Jim, I tried your method several times and it didn't fix the problem for me. What is the significance of the mode=tiva part of the command? I'm going to try the other method I referenced earlier for a locked up MSP432 LaunchPad.

I can't remember exactly how I got that command - a bit of trial and error I suspect. I think that Tiva was the old name for this processor series.
I got there by starting with:

slaa777a.pdf - 5.3 Executing Unlock Sequence

followed link to table 3 - which suggests that UniFlash should unlock the processor.
Then, deep in the Uniflash quick start quide:

Debug Port Unlock

Users can access the XDS Debug Port Unlock tool (dbgjtag) in the <installDir>/deskdb/content/TICloudAgent/<os>/ccs_base/common/uscif/

Example Usage:

dbgjtag -f @xds100v2 -Y unlock,mode=tiva

dbgjtag -f @xds200 -Y unlock,mode=tiva

Did you manage to hold Reset low while the command was running?

It tells you when to do it, and when it has finished!

 Just noticed - if you run 

dbgjtag.exe -Y help

Some of the info includes:-

-Y unlock,mode=string
Do unlock procedure on target device. The supported modes are
mode=msp432e4. (XDS100, XDS110, and XDS200).
mode=tiva. (XDS100, XDS110, and XDS200).

I am using an msp432e411, but tiva worked for me!

I've now tried the second method and I can't even get to a  CCS v10 menu choice - "Launch Selected Configuration", without this there are no Scripts to run.

CCS v10 UI not even close to CCS v7 used in the MSP432P401R LaunchPad UG. I guess the only option is to replace the MSP432P401R MCU?

I did try using mode=msp432e4 - did not work either. Looks like the only option is replacing the MSP432 MCU.

Ted Fryberger said:

I did try using mode=msp432e4 - did not work either. Looks like the only option is replacing the MSP432 MCU.

The debug unlock (aka factory reset) is different for MSP432P v.s. MSP432E/Tiva devices.

For a MSP432P401R see section 7 Device Security in  SLAU575B. TI seem to have removed all the MSP432P documentation from their web site. Found a copy of SLAU575B at https://manualzz.com/doc/7256083/code-composer-studio-6.1-for-msp432--rev.-b- 

Thanks Chester, I'll take a look at that

Discovered only CCSv6.x and 7.x User Guides even mention 432 - these are both 432 specific variants of the UG. Downloaded and installed CCSv7.4 which runs and has the menu commands listed in Section 8 Device Security. Went through the Factory Reset without a Password process but it cannot Connect Target - I still get the -261 Error.

The targetConfigs shows MSP432P401R.ccxml not XDS110 - tried this, did not connect with CORTEX_M4_O variant, also tried setting to CS_DAP_0 variant but it would not accept it. Still getting -261 Error.

Created a new XDS110.ccxml file which is tied to XDS110 and MSP432P401R, set it as default, same results - can't connect using CORTEX_M4_0 variant, can's set it to CS_DAP_0 variant.

Any other ideas?