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: Error initializing flash programming: Your XMS432P401R material is no longer supported

Part Number: MSP432P401R

After attempting to upload the code shown below to my MSP432 launchpad, the board entered a constant reset cycle and could no longer be flashed through my board's debugger.

/* DriverLib Includes */
#include <ti/devices/msp432p4xx/driverlib/driverlib.h>

/* Standard Includes */
#include <stdint.h>
#include <stdbool.h>
#include <stdio.h>

//![Simple GPIO Config]
int main(void)
{
    volatile uint32_t ii;

    /* Halting the Watchdog */
    MAP_WDT_A_holdTimer();


    /* Configuring P1.0 as output */
    FPU_enableModule();
    GPIO_setAsOutputPin(GPIO_PORT_P1, GPIO_PIN0);
    CS_setDCOFrequency(CS_DCO_FREQUENCY_48);
    uint32_t volatile freq = CS_getDCOFrequency();

    while (1)
    {
        /* Delay Loop */
//        for(ii=0;ii<50000;ii++)
//        {
//        }
        __delay_cycles(50000);

        MAP_GPIO_toggleOutputOnPin(GPIO_PORT_P1, GPIO_PIN0);
    }
}
//![Simple GPIO Config]

This is the error output:

I don't think the device is bricked, but I would like to be able to use this MSP432 for my project instead of the MSP430.

I tried multiple factory resets and also tried reducing the JTAG CLK frequency

I had previously run some simple GPIO code successfully on this board so I know it was working before I tried the code mentioned about. Apparently, as specified in the DriverLib Manual in section 6.6.2.23, pre-released launchpads can't use the setDCOFrequency() function to anything outside of the preset freqs, which I may have done.

In any case, that's what I know so far, and I would appreciate any help or insight on this issues so that I can save my launchpad

  • Hi Connor,

    One possibility is to re-program the relevant registers with the original values. But those might have already been overwritten when you ran the setDCOFrequency() function. We no longer support the XMS silicon. One possibility is to order a MSP432P401r device and swap it for the XMS device on the Launchpad. 

    Srinivas

  • In the case that I replace the chip, can I still use the launchpad's built-in USB flashing capabilities?

    Also, I am confused if the lack of support for the chip means that there is nothing to be done for saving the one I currently have? Or does it mean that I have to figure it out on my own?

  • That message means you're trying to use a Black Launchpad, but evidently you aren't since you succeeded before. I expect what happened is you set the CPU clock to 48MHz without setting the Flash wait states. The CPU is telling the debugger some kind of nonsense, and that's the best it can guess.

    What happened exactly when you did the Factory Reset? It should have left the MCU erased, i.e. no program in it. Did you re-load that same program afterward?

**Attention** This is a public forum