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: Unable to connect after flashing firmware, error -261 "Invalid response was received from the XDS110"

Part Number: MSP432P401R

Hi, I am having issues connecting to a custom board design using the MSP432P401R after flashing the firmware my team has written for the board. The initial connection attempt to the surface mounted MSP432 succeeded, and we were able to flash firmware onto the device. The code paused at the standard "main" breakpoint set by CCS, and after running the code in the debugger we lost connection to the device. Now, whenever we attempt to flash the device CCS reports the following error:

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

We have tried to factory reset the device, as well as changing the target configuration settings to use JTAG instead of SWD, and slowing the clock speed down. Our current design does not use an external oscillator, and the reference design used in the launchpad platform does.

I am wondering if the issue with our design is a hardware fault (either due to the lack of an oscillator, or due to damage to the chip), or if the issue is related to the software we flashed. I know that the software is accessing pins that are currently not connected in our design, but I did not expect that to be an issue. If the software is the source of the problem, are there any other methods we could use to reset the firmware on the board and recover it?

I've attached a copy of the firmware flashed onto the board, as well as a copy of the Eagle schematic for our board implementation. We have modified our test board (separately of the attached schematic) to connect all AVCC and AVSS pins to +3v3 and GND, as well as adding a 47k Ohm pullup resistor to RST.

I've attached our Eagle files as well as the relevant software in the zip below, thank you for any help!

e2e-helprequest.zip