This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

MSP430F427A: MSP430Flasher 1.3.15 won't run under Win XP

Part Number: MSP430F427A
Other Parts Discussed in Thread: MSP430-FLASHER, UNIFLASH

Have a s/n 16... MSPFET that works fine w/ 1.3.11 MSPFlasher under win XP.

Got a new MSPFET s/n 17... which would not work.  After investigating, it appeared I needed to upgrade MSPFlasher s/w, but the new version says: "C:\ti\MSPFlasher_1.3.15\MSPFlasher.exe is not a valid WIN32 application"

Thanks,

  • Hello Joseph,

    I am sorry to hear that you are experiencing difficulties downloading the updated version of the MSP430-Flasher. As this E2E post describes, you are correct that you will need to download the most updated version of the MSP430-Flasher in order for it to be compatible with the new MSP-FETs.

    Please delete all files associated to the old MSP430-Flasher and then download the newest version (1.3.16) from the linked website. Once downloaded you should be able to unzip it and then run the executable file as an administrator. If this process does not work then there may be an issue with your Windows XP compatibility. Hopefully this helps and let me know if you are able to download the newest version properly.

    Best regards,

    Matt Calvo

  • Matt,
    Same error. I can download and install the MSP430 Flasher, but it will not execute as a 32 bit Windows program.
  • Joseph,

    I will look further into this! Have you considered using UniFlash as your preferred method of programming devices? It performs the same functionality as MSP430-Flasher but provides a convenient GUI.

    Best regards,

    Matt Calvo
  • Joseph,

    I just heard back from our tools team and they informed me that we no longer support Windows XP for the MSP430-Flasher, this can be seen in section 2 of the users guide (slau654). They mentioned the issue is most likely caused by a setting within Visual Studio. You have a few options to consider:

    1) Try the workarounds mentioned in this forum entry

    2) Switch to UniFlash to program your devices

    3) Upgrade your OS to a compatible operating system as seen in section 2 of the user's guide (slau654)

    Hopefully this helps you move forward!

    Best regards,

    Matt Calvo

**Attention** This is a public forum