MSP430F4152: Programming issue with new MSP-FET programmer

Hi Jim,

Could you describe the phenomenon of the problem?

Thanks,

Yuhao

The info above was a reply to my original post that is now locked. Be;ow is my issue:

We have a PCB that uses a MSP430F4152 chip that we have been programming with a MSP-FET programmer since 2017. We are trying to setup a second programming station.  We are using the MSP430Flasher_1.3.7 with a batch file. The programmer from 2017 (SN 1512007C7) works fine. The newly purchased programmer (SN 220200B29) fails with an "Could not set device Vcc" and exit code of 44. Other then the programmer, everything else is then same; PC, programming cable, etc.

==== programming command from batch file =====

MSP430Flasher.exe -n MSP430F4152 -w "FRM00005_AD.txt" -v -g -z [VCC]

===== Output from batch file =====

* Evaluating triggers...done
* Checking for available FET debuggers:
* Found USB FET @ COM23 <- Selected
* Initializing interface @ COM23...done
* Checking firmware compatibility:
* FET firmware is up to date.
* Reading FW version...done
* Setting VCC to 3000 mV...
# Exit: 44
# ERROR: Could not set device Vcc
* Starting target code execution...done
* Disconnecting from device...done

Thanks!

FYI, I just found that I can load the .HEX file in the chip using Code Composer Studio with the newer (SN 220200B29) MSP-FET programmer. So, it seems that the issues is with the MP430Flasher.exe. Anyone have any ideas as to why the MP430Flasher.exe does not work with the newer MSP-FET programmer?

Hi Jim,

It seems strange. I'll try to test it.

Thanks

Yuhao

Thanks, using CCS is a bit slower and not the best for production programming.

BTW, I'm using Windows 10. I was thinking of trying it on a old WIN 7 or XP machine.

Jim

Here is some more info on this issue:

-Using WIN XP does not help this issue.

-I have I third (verified functional with another micro/PCB) MSP-FET programmer (SN: 1805006FF) that has the same issue as the newer (SN 220200B29) MSP-FET programmer. Only the programmer from 2017 (SN 1512007C7) will work with the MP430Flasher.exe.

-I just discovered that while CCS is programming my PCB they are not functioning correctly when tested. Maybe some configuration bit not configured correctly?

Jim

 Yuhao Zhao

I found some info about two different generations of MSP-FET programmers. Below is from the MSP debugger’s guide:

5.6.1 General Features
The MSP-FET debug probe includes the following features:
• MSP-FET first generation (v1.2):
– Has no CE sticker or label on the case, and no W at the end of the version number
– Is supported since:
• CCS v6.0.0
• IAR EW430 v5.60.7 and IAR EWARM v6.10.1
• MSP-FET second generation (v2.04, v2.05, and v2.06):
– Has a CE sticker or label on the case, or a W at the end of the version number
– Is supported since:
• CCS v7.0
• IAR EW430 7.1 and IAR EWARM 8.10
• Operating systems: OS X, Linux, Windows
• Software configurable supply voltage between 1.8 V and 3.6 V at 100 mA

The programmer that works seems to be a FIRST GENERATION (v1.2) and the two programmers that do not work seem to be SECOND GENERATION (v2.04, v2.05, and v2.06). There info about compatibility with CCS and other development tools but nothing about MP430Flasher compatibility. Could you look into this issue?

Could you have a try with Uniflash? It also support command line mode.

https://www.ti.com/tool/UNIFLASH?keyMatch=&tisearch=search-everything&usecase=software