CC430F5137: MSP430Flasher doesn't work with current firmware release files

Been playing with UniFlash and the command line information is scarce.

Anyways, this command succesfully flashes and starts the device using the EEPROM hex file that doesn't work via MSP430Flasher:

dslite -c CC430F5137.ccxml -s "MSP430DownloadOptions"="Erase main and information memory"  -e -f -v "<hexfile>"

For example, where do I find a list of settings and possible values for a certain MCU? Is it via the UniFlash UI that one usually get those IDs and value?

OK so today I could get into the same problem again with the EEPROM file not starting *and* with UniFlash command line.

dslite.bat -c "CC430F5137.ccxml" -s "MSP430DownloadOptions"="Erase main and information memory"  -e -f -v "<hexfile>"

Executing that would make the device end up in the state that it can't start, regardless of power cycle.

Using UniFlash GUI did however work, it has always worked. So I generated a Standalone Command Line Package and that didn't work either, same problem.

Checked the command being used and although "Run Target After Program Load/Flash Operation" was checked that parameter didn't make it to the Stand Alone Command Line Package.

This command now works (-u added) :

dslite.bat -c "CC430F5137.ccxml" -s "MSP430DownloadOptions"="Erase main and information memory"  -e -f -v -u "<hexfile>"

Original question still stands though, what could be the reason MSP430Flasher doesn't work.

Hello Jerker,

I am looking into this and will have further feedback shortly.

When using MSPFlasher, does it ever produce an error code or just hangs indefinitely? 

Hi Jerker,

We are unaware of this behavior, but considering that you had some luck replicating a similar behavior with UniFlash and solving it with ''-u", it might be good to try different exit combinations for MSPFlasher:

Now, although MSPFlasher will continue to be available online, we are recommending to use UniFlash.

I assume you are trying to use MSPFlasher since you used it before, but would UniFlash be an option for you?

Regards,

Luis R

MSP430Flasher never hangs and we haven't seen any error code.

Yes, I re-wrote our application to use UniFlash since we had this problem. Although it leaves some uneasiness that do we have something wrong in the firmware.

I tried different VCC before without any change in outcome. This is how it looks after a failed flash.

* -----/|-------------------------------------------------------------------- *
*     / |__                                                                   *
*    /_   /   MSP Flasher v1.3.20                                             *
*      | /                                                                    *
* -----|/-------------------------------------------------------------------- *
*
* Evaluating triggers...done
* Checking for available FET debuggers:
* Found USB FET @ COM6 <- Selected
* Initializing interface @ COM6...done
* Checking firmware compatibility:
* FET firmware is up to date.
* Reading FW version...done
* Setting VCC to 3600 mV...done
* Accessing device...done
* Reading device information...done
* Loading file into device...done
* Verifying memory (<hexfile>)...done
*
* ----------------------------------------------------------------------------
* Arguments   : -e ERASE_ALL -n CC430F5137 -w <hexfile> -v -z [VCC=3600, RESET]
* ----------------------------------------------------------------------------
* Driver      : loaded
* Dll Version : 31400000
* FwVersion   : 31200000
* Interface   : TIUSB
* HwVersion   : U 3.0
* JTAG Mode   : AUTO
* Device      : CC430F5137
* EEM         : Level 5, ClockCntrl 2
* Erase Mode  : ERASE_ALL
* Prog.File   : <hexfile>
* Verified    : TRUE
* BSL Unlock  : FALSE
* InfoA Access: FALSE
* VCC ON      : 3600 mV
* ----------------------------------------------------------------------------
* Resetting device (RST/NMI)...done
* Starting target code execution...done
* Disconnecting from device...done
*
* ----------------------------------------------------------------------------
* Driver      : closed (No error)
* ----------------------------------------------------------------------------
*/

Hi Jerker,

That's interesting. MSPFlasher seems to be successful in verifying memory after programming. But then, if you try to read memory, you say that the contents are incorrect? Are there any particular Flash locations not matching your original file?

Can you run some quick code right after reset to check if the device executes? I.e. LED toggle or something,

Another test could be to run a CRC of the memory right after reset. The way you are describing the problem, it also sounds to me like there could be a problem with your application.

Regards,

Luis R

I have verified the memory using UniFlash after MSP430Flasher and that reported it was OK. So it must be something with resetting the device that isn't working properly.

Yeah could very well be a problem with the firmware. As it works now with UniFlash this has lower prio but I will most likely return to this and I will update this thread with more info if I find antyhing new.

Luis RC said:

Hi Jerker,

That's interesting. MSPFlasher seems to be successful in verifying memory after programming. But then, if you try to read memory, you say that the contents are incorrect? Are there any particular Flash locations not matching your original file?

Can you run some quick code right after reset to check if the device executes? I.e. LED toggle or something,

Another test could be to run a CRC of the memory right after reset. The way you are describing the problem, it also sounds to me like there could be a problem with your application.

Regards,

Luis R