SLAU654E November 2015 – February 2019
Table 3 lists the possible error codes and messages.
| Error Code | Error Message |
|---|---|
| 0 | No error |
| 1 | Could not initialize device interface |
| 2 | Could not close device interface |
| 3 | Invalid parameter(s) |
| 4 | Could not find device (or device not supported) |
| 5 | Unknown device |
| 6 | Could not read device memory |
| 7 | Could not write device memory |
| 8 | Could not read device configuration fuses |
| 9 | Incorrectly configured device; device derivative not supported |
| 10 | Could not set device Vcc |
| 11 | Could not reset device |
| 12 | Could not preserve/restore device memory |
| 13 | Could not set device operating frequency |
| 14 | Could not erase device memory |
| 15 | Could not set device breakpoint |
| 16 | Could not single step device |
| 17 | Could not run device (to breakpoint) |
| 18 | Could not determine device state |
| 19 | Could not open Enhanced Emulation Module |
| 20 | Could not read Enhanced Emulation Module register |
| 21 | Could not write Enhanced Emulation Module register |
| 22 | Could not close Enhanced Emulation Module |
| 23 | File open error |
| 24 | File type could not be identified |
| 25 | File end error |
| 26 | File input/output error |
| 27 | File data error |
| 28 | Verification error |
| 29 | Could not secure the device |
| 30 | The Debug Interface to the device has been secured |
| 31 | Error within Intel Hex file |
| 32 | Could not write device Register |
| 33 | Could not read device Register |
| 34 | Not supported by selected Interface or Interface is not initialized |
| 35 | Interface Communication error |
| 36 | No external power supply detected |
| 37 | External power too low |
| 38 | External power detected |
| 39 | External power too high |
| 40 | Hardware Self Test Error |
| 41 | Fast Flash Routine experienced a timeout |
| 42 | Could not create thread for polling |
| 43 | Could not initialize Enhanced Emulation Module |
| 44 | Insufficient resources |
| 45 | No clock control emulation on connected device |
| 46 | No state storage buffer implemented on connected device |
| 47 | Could not read trace buffer |
| 48 | Enable the variable watch function |
| 49 | No trigger sequencer implemented on connected device |
| 50 | Could not read sequencer state - Sequencer is disabled |
| 51 | Could not remove trigger - Used in sequencer |
| 52 | Could not set combination - Trigger is used in sequencer |
| 53 | System Protection Module A is enabled - Device locked |
| 54 | Invalid SPMA key was passed to the target device - Device locked |
| 55 | Device does not accept any further SPMA keys - Device locked |
| 56 | MSP-FET430UIF Firmware erased - Bootloader active |
| 57 | Could not find MSP-FET430UIF on specified COM port |
| 58 | MSP-FET430UIF is already in use |
| 59 | EEM polling thread is already active |
| 60 | Could not terminate EEM polling thread |
| 61 | Could not unlock BSL memory segments |
| 62 | Could not perform access, BSL memory segments are protected |
| 63 | Another device as selected was found |
| 64 | Could not enable JTAG wrong password |
| 65 | Only one UIF must be connected during update to v3 |
| 66 | CDC-USB-FET-Driver was not installed. Please install the driver |
| 67 | Manual reboot of USB-FET needed ! PLEASE unplug and reconnect your USB-FET!! |
| 68 | Internal error |
| 69 | One of the connected MSP-FETs / eZ-FETs debuggers needs recovery |
| 70 | One of the connected MSP-FETs / eZ-FETs debuggers needs recovery |
| 71 | Feature not supported |
| 72 | Only one MSP-FET / eZ-FET must be connected during recovery |
| 73 | MSP-FET / eZ-FET recovery failed |
| 74 | MSP-FET / eZ-FET core(communication layer) update failed |
| 75 | MSP-FET / eZ-FET legacy module update failed |
| 76 | EnergyTrace is not supported by the selected debugger |
| 77 | Hardware State is unknown |
| 78 | Device configuration data inconsistent. Please discontinue using/replace target device. |
| 79 | EEM module not accessible while running in Ultra Low Power Debug Mode - Deactivate Ultra Low Power Debug mode to enable this feature |
| 80 | Failed to remove software breakpoints, please reprogram target device |
| 81 | Trigger configuration conflicts with existing triggers |
| 82 | Operation not possible while device is running |
| 83 | This function can not be used when software breakpoints are enabled |
| 84 | JTAG/SBW speed configuration failed |
| 85 | Software breakpoint can't be set (followed by critical value) |
| 86 | EnergyTrace is not supported by selected MSP430 device |
| 87 | EnergyTrace requires Ultra-Low Power debug / LPMx.5 enabled |
| 88 | Legacy version of silicon used, which is no longer supported. Please contact TI to obtain a newer version. |
| 89 | Secure device via the IDE is not supported. See Device User Guide for further information. |
| 90 | Cycle counter is in basic mode. Set to advanced mode to use this function. |
| 91 | Parallel port FET (MSP-FETP430IF) is no longer supported. |
| 92 | Wrong target architecture was selected - Valid architectures are MSP430 or MSP432_M4. |
| 93 | Mass erase executed. Please power-cycle your device and restart the debug session. |
| 94 | Your connected hardware might drain too much power from the debugger.This results in an overcurrent. |
| 95 | MSP Tool firmware update failed. Please ensure the USB or Backchannel UART connection is not in use. |
| 96 | MSP432 devices are not supported using the MSPFET430-UIF |
| 97 | DAP is locked or wrong debug protocol selected. |
| 98 | Device database not loaded. |
| 99 | Invalid error number |