fet: Error messages from MSP430DLLv3 version 3.2.4.5.

This commit is contained in:
Tamas TEVESZ 2012-08-15 01:21:04 +02:00 committed by Daniel Beer
parent c717eed96d
commit 84866b78cc
1 changed files with 70 additions and 68 deletions

View File

@ -25,80 +25,82 @@
/* These messages come from uif430 and from MSP430.DLL V3. */ /* These messages come from uif430 and from MSP430.DLL V3. */
static const char *error_strings[] = static const char *error_strings[] =
{ {
"No error", // 0 /* 0 */ "No error",
"Could not initialize device interface", // 1 /* 1 */ "Could not initialize device interface",
"Could not close device interface", // 2 /* 2 */ "Could not close device interface",
"Invalid parameter(s)", // 3 /* 3 */ "Invalid parameter(s)",
"Could not find device (or device not supported)", // 4 /* 4 */ "Could not find device or device not supported",
"Unknown device", // 5 /* 5 */ "Unknown device",
"Could not read device memory", // 6 /* 6 */ "Could not read device memory",
"Could not write device memory", // 7 /* 7 */ "Could not write device memory",
"Could not read device configuration fuses", // 8 /* 8 */ "Could not read device configuration fuses",
"Incorrectly configured device; device derivative not supported", // 9 /* 9 */ "Incorrectly configured device; device derivative not supported",
"Could not set device Vcc", // 10 /* 10 */ "Could not set device Vcc",
"Could not reset device", // 11 /* 11 */ "Could not reset device",
"Could not preserve/restore device memory", // 12 /* 12 */ "Could not preserve/restore device memory",
"Could not set device operating frequency", // 13 /* 13 */ "Could not set device operating frequency",
"Could not erase device memory", // 14 /* 14 */ "Could not erase device memory",
"Could not set device breakpoint", // 15 /* 15 */ "Could not set device breakpoint",
"Could not single step device", // 16 /* 16 */ "Could not single step device",
"Could not run device (to breakpoint)", // 17 /* 17 */ "Could not run device (to breakpoint)",
"Could not determine device state", // 18 /* 18 */ "Could not determine device state",
"Could not open Enhanced Emulation Module", // 19 /* 19 */ "Could not open Enhanced Emulation Module",
"Could not read Enhanced Emulation Module register", // 20 /* 20 */ "Could not read Enhanced Emulation Module register",
"Could not write Enhanced Emulation Module register", // 21 /* 21 */ "Could not write Enhanced Emulation Module register",
"Could not close Enhanced Emulation Module", // 22 /* 22 */ "Could not close Enhanced Emulation Module",
"File open error", // 23 /* 23 */ "File open error",
"Could not determine file type", // 24 /* 24 */ "File type could not be identified",
"Unexpected end of file encountered", // 25 /* 25 */ "File end error",
"File input/output error", // 26 /* 26 */ "File input/output error",
"File data error", // 27 /* 27 */ "File data error",
"Verification error", // 28 /* 28 */ "Verification error",
"Could not blow device security fuse", // 29 /* 29 */ "Could not blow device security fuse",
"Could not access device - security fuse is blown", // 30 /* 30 */ "Security fuse has been blown",
"Error within Intel Hex file", // 31 /* 31 */ "Error within Intel hex file",
"Could not write device Register", // 32 /* 32 */ "Could not write device register",
"Could not read device Register", // 33 /* 33 */ "Could not read device register",
"Not supported by selected Interface", // 34 /* 34 */ "Not supported by selected interface or interface is not initialized",
"Could not communicate with FET", // 35 /* 35 */ "Interface communication error",
"No external power supply detected", // 36 /* 36 */ "No external power supply detected",
"External power too low", // 37 /* 37 */ "External power too low",
"External power detected", // 38 /* 38 */ "External power detected",
"External power too high", // 39 /* 39 */ "External power too high",
"Hardware Self Test Error", // 40 /* 40 */ "Hardware self test error",
"Fast Flash Routine experienced a timeout", // 41 /* 41 */ "Fast flash routine experienced a timeout",
"Could not create thread for polling", // 42 /* 42 */ "Could not create thread for polling",
"Could not initialize Enhanced Emulation Module", // 43 /* 43 */ "Could not initialize Enhanced Emulation Module",
"Insufficient resources", // 44 /* 44 */ "Insufficent resources",
"No clock control emulation on connected device", // 45 /* 45 */ "No clock control emulation on connected device",
"No state storage buffer implemented on connected device", // 46 /* 46 */ "No state storage buffer implemented on connected device",
"Could not read trace buffer", // 47 /* 47 */ "Could not read trace buffer",
"Enable the variable watch function", // 48 /* 48 */ "Enable the variable watch function",
"No trigger sequencer implemented on connected device", // 49 /* 49 */ "No trigger sequencer implemented on connected device",
"Could not read sequencer state - Sequencer is disabled", // 50 /* 50 */ "Could not read sequencer state - sequencer is disabled",
"Could not remove trigger - Used in sequencer", // 51 /* 51 */ "Could not remove trigger - used in sequencer",
"Could not set combination - Trigger is used in sequencer", // 52 /* 52 */ "Could not set combination - trigger is used in sequencer",
"System Protection Module A is enabled - Device locked", // 53 /* 53 */ "System Protection Module A is enabled - device locked",
"Invalid SPMA key was passed to the target device - Device locked", // 54 /* 54 */ "Invalid SPMA key was passed to the target device - device locked",
"Device does not accept any further SPMA keys - Device locked", // 55 /* 55 */ "Device does not accept any further SPMA keys - device locked",
"MSP-FET430UIF Firmware erased - Bootloader active", // 56 /* 56 */ "MSP-FET430UIF Firmware erased - bootloader active",
"Could not find MSP-FET430UIF on specified COM port", // 57 /* 57 */ "Could not find MSP-FET430UIF on specified COM port",
"MSP-FET430UIF is already in use", // 58 /* 58 */ "MSP-FET430UIF is already in use",
"Enhanced Emulation Module polling thread is already active", // 59 /* 59 */ "EEM polling thread is already active",
"Could not terminate Enhanced Emulation Module polling thread", // 60 /* 60 */ "Could not terminate EEM polling thread",
"Could not unlock BSL memory segments", // 61 /* 61 */ "Could not unlock BSL memory segments",
"Could not perform access, BSL memory segments are protected", // 62 /* 62 */ "Could not perform access, BSL memory segments are protected",
"FOUND_OTHER_DEVICE (errcode=63)", /* XXX */ // 63 /* 63 */ "Another device as selected was found",
"Wrong password provided to open JTAG", // 64 /* 64 */ "Could not enable JTAG wrong password",
"Internal error", // 65 /* 65 */ "Only one UIF must be connected during update to v3",
"Only one UIF must be connected during update to v3", // 66 /* 66 */ "CDC-USB-FET driver was not installed, please install the driver",
"Invalid error number", // 67 /* 67 */ "Manual reboot of USB-FET needed! PLEASE unplug and reconnect your USB-FET!",
/* 68 */ "Internal error",
/* 69 */ "Invalid error number",
}; };
const char *fet_error(int code) const char *fet_error(int code)