I've been working on a Chronos altimeter app. But after some code changes suddenly my Chronos is not recognized by the FET. I got another, same story - programmed my code and it is bricked. I did not change the BSL address (so it should not be locked). The hex file of the code that kills the cc430f6137: http://dmitry.gr/ChronosAlt.hex
Here is the session whewre I flash it and the part dies. It should not be a complier issue, since no opcode shoudl disable debugging, but in case it matters: mspgcc to compile&link, mspdebug to program the code.
I verified that the FET is functional byt trying it with another chronos as well as this one before it bricked. I verified the chronos is bricked b y trying it with other FETs. Ideas?
mspdebug rf2500 "prog ChronosAlt.hex" MSPDebug version 0.21 - debugging tool for MSP430 MCUs Copyright (C) 2009-2012 Daniel Beer <dlbeer@gmail.com> This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Trying to open interface 1 on 020 rf2500: warning: can't detach kernel driver: No data available Initializing FET... FET protocol version is 30001000 Set Vcc: 3000 mV Configured for Spy-Bi-Wire Device ID: 0x6137 Code start address: 0x8000 Code size : 32768 byte = 32 kb RAM start address: 0x1c00 RAM end address: 0x2bff RAM size : 4096 byte = 4 kb Device: CC430F6137 Number of breakpoints: 3 fet: FET returned NAK warning: device does not support power profiling Chip ID data: 61 37 12 Erasing... Programming... Writing 4096 bytes at c800... Writing 2576 bytes at d800... Writing 48 bytes at ffd0... Done, 6720 bytes total dmitrygr@vwm64:/mnt/hgfs/D/msp430/Chronos-Altimeter$ mspdebug You need to specify a driver. Try --help for a list. dmitrygr@vwm64:/mnt/hgfs/D/msp430/Chronos-Altimeter$ mspdebug rf2500 MSPDebug version 0.21 - debugging tool for MSP430 MCUs Copyright (C) 2009-2012 Daniel Beer <dlbeer@gmail.com> This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Trying to open interface 1 on 020 rf2500: warning: can't detach kernel driver: No data available Initializing FET... FET protocol version is 30001000 Set Vcc: 3000 mV Configured for Spy-Bi-Wire fet: FET returned error code 11 (Could not reset device) fet: command C_IDENT1 failed fet: identify failed Trying again... Initializing FET... FET protocol version is 30001000 Set Vcc: 3000 mV Configured for Spy-Bi-Wire Sending reset... fet: FET returned error code 11 (Could not reset device) warning: fet: reset failed fet: FET returned error code 11 (Could not reset device) fet: command C_IDENT1 failed fet: identify failed dmitrygr@vwm64:/mnt/hgfs/D/msp430/Chronos-Altimeter$