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.

problem with msp432 launchpad: CORTEX_M4_0: Error connecting to the target: (Error -1063 @ 0x0) Device ID is not recognized or is not supported by driver.

Launchpad worked fine for first few demos blinking light and out of box experience, however during the last demo, TI cloud agent (CCS cloud) updated the firmware on Launchpad emulator, now i get the error "(Error -1063 @ 0x0) Device ID is not recognized or is not supported by driver. " The error appears in both windows CCS on my laptop as well as running CCS cloud when i try to load the demo software. I have tried an option 7 device security reset in windows CCS but still have same error:

"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 6.0.83.1)  "

any help or suggestions appreciated


Jack Bouska

  • Moving it to the MSP forum.
  • Hi John,

    Please have a look at this wiki topic and try the mass erase procedure.

  • Thank you for the help, I was just now able to revive the board by following all the steps listed in another post (with very similar symptoms)
    MSP432P401R launchpad DOA? e2e.ti.com/.../456120
    to recap: first i ran factory rest, then upload firmware, then ran blinky code in windows ccs, which uploaded firmware again, then was able to revive the launchpad.

    as warning to other novices out there like myself: I do not recommend switching between Cloud CCS and windows CCS, as incompatibility in firmware requirements appears to be toxic to the launchpad.

    thanks again, Jack
  • Hi Jack,

    Glad to hear you were able to recover the board. For your information, I wanted to provide some comments on they types of error you may see and what they mean.

    As you know ... the MSP430 launchpad has an on-board XDS110 debug probe. The debug probe has it's own firmware that may need to be updated depending on the version of CCS or CCS Cloud being used. If there was something wrong with the debug probe firmware, the host PC would not be able to talk to the debug probe and would give an error message complaining about invalid firmware, firmware corruption, needing an update etc. If the firmware is valid, but the debug probe cannot talk to the MSP432 on the launchpad, you will get a different kind of error message similar to the one you were seeing initially.

    If a target program is corrupted or the target flash is corrupted, you may end up with an invalid reset vector. In that case, the CPU may get into a tight loop where it starts executing from the reset vector, immediately faults, and then goes back to the reset vector to repeat the loop. The debug probe will not be able to halt and talk to the CPU. Erasing the entire flash through the DAP is the only option if that happens.

**Attention** This is a public forum