MSP432 Launchpad Error connecting to the target: Error -1170

I can't connect to run the debugger eithre. I got the same message. The new code never made it to the board. I got the message while trying to program it. The code is actually an example code that shuts down everything and goes into LMP3.

Hi Albert,

Can you provide the code so we can try to reproduce it?

You should be able to do a factory reset - it is a different process than just loading new code - you don't simply debug but you connect in a different way, by going in through the target configurations to connect to the debugger without actually needing to connect to the MSP432. You have to follow the steps in www.ti.com/.../slau575 section 7 from pages 22-26 exactly. If you are doing that and getting an error along the way, perhaps providing a screenshot would help us to see what part of the process is giving you the error.

Regards,
Katie

The code I was trying to use was provided by another Ti employee, which is mentioned here 

https://e2e.ti.com/support/microcontrollers/msp430/f/166/t/416484

https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/166/7853.main.c

But the error appeared before a sucessful write.

As you can see below, I didn't have any luck connecting to DAP. I tried to run the factory reset script anyways, but not luck.

e2e.ti.com/.../7853.main.c

Hi Albert,

Thanks for providing more information - I'm sorry to hear of your troubles. I'm going to talk to some people who are looking into a similar issue that is in work (see other thread linked below) and show them your issue as well.

As a note, on some other recent threads, I've seen people run into an issue with a factory reset using the Launchpad on-board emulation, but some of them were able to do the factory reset using one of the other emulation tools for the MSP432 to perform the factory reset: e2e.ti.com/.../1547956

Regards,
Katie

Albert - one more question.

I know that you said the code you were trying to load was the LPM3 example provided in that other thread that you linked - but what was the code that you were debugging when you very first had the issue? It doesn't matter what code you are trying to load now, but rather what matters is what code is already currently in the part from the last time you programmed it before you had the issue. You mentioned some code that you had recently changed a big chunk of. Is this code that you'd be able to share (so that we can reproduce the issue)? If needed you can send it in a private message.

Regards,
Katie

Here is the code I had on the MCU. I ran it many test with energytrace without any problems. I Also used a 8.2 shunt at the return ground to measure the consumption using a super capacitor to compare the results. I switched between shunt, and energytrace many times without any problems. All I wanted to see was the peak current at turn on, and how long it take before it actually goes to sleep. Notice a lot of code are just comments. After the test, I thought I must be doing something wrong if the MCU is drawing 100~120uA during LPM3 even with ISR disabled. So I commented out the entire Main{} function, and replaced it with Ryan 's 7853.main.c. When I tried to program it, the error appeared before an actual write. I took the eval board home and tried it on my home laptop which was never turned off (which was working with the same code), with CCS &code already on the screen, tried to program it, and got the exact same error.. cannot connect.

int main(void)
{
/* Halting the Watchdog */
MAP_WDT_A_holdTimer();

/* Terminating all unused pins to minimize power consumption. This is
done by register accesses for simplicity and to minimize branching API
calls */
DIO->rPADIR.r = 0xFFFF;
DIO->rPBDIR.r = 0xFFFF;
DIO->rPCDIR.r = 0xFFFF;
DIO->rPDDIR.r = 0xFFFF;
DIO->rPEDIR.r = 0xFFFF;
DIO->rPAOUT.r = 0;
DIO->rPBOUT.r = 0;
DIO->rPCOUT.r = 0;
DIO->rPDOUT.r = 0;
DIO->rPEOUT.r = 0;

/* Configuring P1.1 as an input and enabling interrupts */
/*
MAP_GPIO_setAsInputPinWithPullUpResistor(GPIO_PORT_P1, GPIO_PIN1);
MAP_GPIO_clearInterruptFlag(GPIO_PORT_P1, GPIO_PIN1);
MAP_GPIO_enableInterrupt(GPIO_PORT_P1, GPIO_PIN1);
MAP_Interrupt_enableInterrupt(INT_PORT1);
Interrupt_enableSleepOnIsrExit();
*/

/* Starting LFXT and sourcing ACLK and BCLK from it */
MAP_CS_setExternalClockSourceFrequency(32000,48000000);

/*
MAP_GPIO_setAsPeripheralModuleFunctionOutputPin(GPIO_PORT_PJ,
GPIO_PIN0 | GPIO_PIN1, GPIO_PRIMARY_MODULE_FUNCTION);*/
MAP_CS_startLFXT(false);
MAP_CS_initClockSignal(CS_ACLK, CS_LFXTCLK_SELECT, CS_CLOCK_DIVIDER_1);
MAP_CS_initClockSignal(CS_BCLK, CS_LFXTCLK_SELECT, CS_CLOCK_DIVIDER_1);
/* Disabling high side voltage monitor/supervisor*/
MAP_PSS_disableHighSide();


/* Enabling "rude" mode which forces device to go to sleep regardless of outstanding clock requests*/

MAP_PCM_enableRudeMode();

/* Enabling MASTER interrupts */
/* MAP_Interrupt_enableMaster();*/
MAP_PCM_gotoLPM3();

/* Going to LPM3 */
while (1)
{
/*MAP_GPIO_toggleOutputOnPin(GPIO_PORT_P1, GPIO_PIN0);*/
MAP_PCM_gotoLPM3();
}
}

/* GPIO ISR
void gpio_isr(void)
{
uint32_t status;

status = MAP_GPIO_getEnabledInterruptStatus(GPIO_PORT_P1);
MAP_GPIO_clearInterruptFlag(GPIO_PORT_P1, status);

if(status & GPIO_PIN1)
{
MAP_GPIO_toggleOutputOnPin(GPIO_PORT_P1, GPIO_PIN0);
}
} */

I've tried that before. Now that you mentioned again, I'm going to check it with a meter to see if the switch is actually making contact. 

Update: I measured the pins with a meter from the back, it seems its making a good contact. Can I send this to you guys, with prepaid shipping both ways and see if you guys can unbrick it for me?