This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

MSP432P401R: SWD error condition

Part Number: MSP432P401R
Other Parts Discussed in Thread: UNIFLASH

I have been unable to flash to the msp432p401r board since adding a careless line of code to main. I'm using this board for a class on Embedded Systems Development in C. For a menu we will need to create for the Final Project I had the thought of adding a case for reset. I used SysCtl_rebootDevice() and it produced the desired effect. After implementing the function to the menu, I had the thought of creating the effect at the begging of main(). This would obviously cause a reboot loop since the code never goes past the reboot function. I corrected the error by deleting the line of code but found I was no longer able to flash to the board with the error (Error -1063 @ 0x0) in platformIO. I used the xdsdfu from the XDS Emulation Software Package v.8.3.0.00003 fount at /ti/ccs_base/common/uscif/xdsdfu to perform a factory reset. The next step was using uniflash to remove the possibility of the issue being the platformIO setup. Uniflash produced the error (Error -614 @ 0x0). Since my computer is setup in dual boot with Arch Linux and Windows, I switched to windows to further reduce potential issues with compatibility. Keil produced a similar error to uniflash. I installed Code Composer and followed the steps provided in the user guide https://www.ti.com/lit/ug/slau575k/slau575k.pdf under section 8.1 to perform a factory reset. The output of the factory resets said they were successful, but I am still unable to flash to the board. After each factory reset the various flashing tools said the firmware needed to be updated and performed the action successfully. Would there be any other suggestions on restoring functionality to the board? 

Flashing attempts

uniflash/Keil
[11/21/2019, 4:11:59 PM] [WARNING] CS_DAP_0: Warning: A firmware update is required for the debug probe. Click the "Update" button to update the firmware and connect to the debug target. DO NOT UNPLUG THE DEBUG PROBE DURING THE UPDATE. (Emulation package 8.0.903.6)
[11/21/2019, 4:12:07 PM] [SUCCESS] CS_DAP_0: Warning: The firmware update completed successfully. (Emulation package 8.0.903.6)
[11/21/2019, 4:12:07 PM] [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 request again. (Emulation package 8.0.903.6)

PlatformIO (personal port of msp432 platform. all functionality appears to be present)
warning: CS_DAP_0: Warning: A firmware update is required for the debug probe. Click the "Update" button to update the firmware and connect to the debug target. DO NOT UNPLUG THE DEBUG PROBE DURING THE UPDATE. (Emulation package 8.0.27.9)
warning: CS_DAP_0: Warning: The firmware update completed successfully. (Emulation package 8.0.27.9)
fatal: CORTEX_M4_0: Error connecting to the target: (Error -1063 @ 0x0) Device ID is not recognized or is not supported by driver. Confirm device and debug probe configuration is correct, or update device driver. (Emulation package 8.0.27.9) Device is not accessible. Reset the device to factory settings?
Failed: Operation was aborted
*** [upload] Error 1


Code Composer
Error connecting to the target:
(Error -1170 @ 0x0)
Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK).
(Emulation package 8.3.0.00003)

No connection possible. This could be caused by the device having gone to low power mode and disabling JTAG PINs.
You have the option to either toggle reset or try to use SWD instead.

**Attention** This is a public forum