MSP432 Error 261 Redux

Hi,

Ted Fryberger said:

I copied the "fatsd_MSP_EXP432P401R_nortos_ccs" example code to a new workspace / folder for modification & development for my custom SBC's. The example project uses SysConfig to define hardware parameters - and I changed both SD and SPI to match my board. The code builds ok, but can't download it to the MSP432 via the XDS110. Getting Error -261 - Error connecting to the target. This occurs with CCS 10.4 and 12.3. PCB-A locked up last year, PCB-B last week!

First of all, MSP432P was an EOL'ed product. I have never worked on this device and have no experience with it. As it is EOL'ed, we no longer provide direct support for this device on e2e. With that said, my understanding of your problem description is that the code was not even loaded successfully. If this is the case, then the device should have still contained the previous code. What was stored in the MCU prior to loading the new code? I feel that it was the previous code from preventing you to connect to the target. In another word, if the programming was unsuccessful, I have no reason to believe that it was the modified fatsd code that bricked the device. Unless the code was programmed but failed to run afterward. There are instances for other MCUs that I'm aware of that may brick the device. Just to give an example, the JTAG pins was repurposed for other functionality. Or the new firmware put the device into a deepsleep or hibernate mode without a mechanism to wakeup. Without the clock, the debugger can no longer connect to the device. These are for other MCUs. I don't know what happened to your MSP432P. 

Prior to loading the modified fatsd code, did you try to load a simple code such as blinky or hello? Did they work?

Ted Fryberger said:

C:\ti\ccs1230\ccs\ccs_base\common\uscif\

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

You specified tiva. MSP432P is not tiva. tiva is normally TM4C123 or TM4C129 MCU. On a LaunchPad, you may find a TM4C129 that acts as a on-board XDS110 debug probe. Don't be confused with TM4C129 as a XDS110 probe. dbgjtag unlock command is meant to unlock a target device, not the debug probe. I don't even know if you can use dbgjtag to unlock MSP432P at all. I find this thread which may help. 

https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1123634/msp432-debuggers-msp432p401r-giving-error---cortex_m4_0-error-connecting-to-the-target-error--614-0x0-the-target-indicates-there-is-an-error-condition-from-a-previous-swd-request-clear-the-error-the-condition-and-try-the-swd-

Ted Fryberger said:

Are the MSP432's dead or hopelessly locked up, and must be replaced?

If you try all means and still can't get the device to connect/program/debug then I will say it is locked up. 

Again, this is as much as I can assist for this device. 

First of all Charles, there is no need to remind us that the MSP432 is EOL. The entire world knows TI Screwed the Pooch with the MSP432P! There was no warning, no explanation, with data sheets and user guides removed. This was an Exorcism! TI never supported this device properly before it went EOL.

I clearly stated in my post that both MSP432's were working fine on both PCB's prior to trying to get the uSD card example working. My nearly 8000 lines of  working code was developed over many months - and worked perfectly immediately before attempting to load the uSD example. Way more complex than Blinky. Trying to load the new program corrupted what was there, without loading the new program. Charles, do you have a problem with reading, or is it comprehension?

The Tiva reference was from another post someone else used to unlock an MSP432 - it worked for them.

Since you have no experience with the MSP432, of dbgjtag, why did you make a post that was all noise and no signal? If you don't have anything constructive to say, don't say anything.

So to sum up: TI MCU's, TI CCS tool chain, TI LaunchPad, TI Boost board, TI example code - that work fine, but the ported example kills or locks up two MSP432's on two custom boards that worked perfectly prior to the port. It's just a mystery!

I will be replacing both MSP432's on these two boards, and using something else for future designs.

Charles, radio silence for you, you've already raised my blood pressure too much.

Does trying the "Factory Reset Without Password" method in SLAU575K help?

The method in SLAU575K is specific to MSP432P devices, whereas the "dbgjtag -f @xds110 -Y unlock,mode=tiva" which is failing in your first post is for MSP432E devices.

Hi Chester, Thanks for the post. I tried that on the previous board with no success - but will look at it again for this second board. I had previously downloaded the CCS v7.1 UG, and CCS v7.4 IDE. Will investigate further. Thanks for the heads-up on MSP432P vs. E.

I used CCS v7.4 and followed the directions in the CCSv7.1 UG, sections 5.1 and 8.1, used a new project that only stops the WDT

Verified XDS110 connection - including with full verification

View | Target Config | shows MSP432P401R.ccxml    not XDX110 - is that a problem? I think all of my projects use this.

Following UG 8.1 instructions, all works until I right click on TI XDS110 USB Debug Probe/CS_DAP_0 (Disconnected)

Connect Target - that's where I get the Error 261

CS_DAP_0: Error connecting to the target: (Error -261 @ 0x0) Invalid response was received from the XDS110. (Emulation package 7.0.100.0)

Also tried the same process with CCSv10 and got the same result