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.

MSP430F149: Programming the MSP430F149

Part Number: MSP430F149
Other Parts Discussed in Thread: MSP-GANG

Team, 

My customer is having issues programming the MSP430:

We’re having a problem trying to program some of the MSP430F149 revision S microcontrollers using the old PRGS-430 serial programming adapters. In the past when this has happened, we just had to update our ‘device.cfg’ file, and that fixed it. But I looked on the web site, and the latest version of that file is dated from 2012, and that is the version we have on the computers in question. (We have these old programmers embedded in several functional testers, so they aren’t easily upgraded.) I tried using an Elprotronic MSP-GANG programmer to program them manually, and it was able to read and write them just fine. One additional oddity, I have one example of a MSP430F149 revision S chip that I am able to read and write with the old PRGS-430, and a whole bunch that I can’t, so that really confused me. I’m hoping that someone can shed some light on this situation. Thanks for any help you can give me!

Thanks

Viktorija

  • Hello Viktorija,

    Does the customer remember changing anything with their code, design, or setup? I find it strange that everything was working and now isn't if nothing was changed.

    Since the PRGS-430 is so old and not actively supported any more, I would definitely recommend that they use this opportunity to switch over to a newer tool such as MSP-GANG, especially since they've found that it works. In the meantime, I would suggest that they figure out if one, some, or all of the PRGS-430 programmers exhibit this issue, whether or not the issue is observed using a different PC, are the programmers providing the appropriate supply voltage, is the JTAG interface implemented correctly on their board, etc. Are there any error codes getting returned when the issue is observed (discussed in the MSP430 Family Serial Programming Adapter User's Guide)?

    These types of issues are challenging to diagnose. It could be anything from a corrupted file on the PC, blown JTAG fuse, or even a bug that was not detected/addressed when we were supporting the PRGS-430 programmers.

    Regards,

    James

    MSP Customer Applications

**Attention** This is a public forum