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.

Flash Programmer: Battling versions



I have another thread going in which I am trying to establish communications with the MSP430 on a TrxEB board.  I'm branching the discussion here to deal with one set of tools that is causing me some confusion.  I have two questions...

I've run the "Flash Programmer" from within SmartRF Studio. When I did, it challenged the version of my set-up; I'm assuming it wasn't happy with the version in the MSP-FET430 (Question 1 - Is that correct?)

It wanted to (and I let it) update it to 3.4.3.4.

Then, I downloaded the standalone Flash Programmer and when run, it wanted 3.3.0.6.  I let it do so (for giggles) but of course when I ran SmartRF Studio again, it wanted to return the device to 3.4.3.4 (which I let it, again)

Question 2 - Do I need, and is there available, the compatible stand-alone "Flash Programmer", or should I just forget about (and uninstall) the stand-alone?

  • I am thinking a quick conference call can help you here, can I contact you using the email address you provided to our E2E system?

    /TA
  • Yes, that would be great.
  • In reply to MFG-Syr:

    Don't know if you got the answers from the conference call already, but to explain for any others that might need to know. The stand alone flash programmer should have been of the same revision as the one installed together with SmartRF Studio 7. We have to fix this. That means, they should both ask for version 3.4.3.4 (or whatever is the latest) of the MSP-FET430 firmware.

    Another thing that might be of interest, there is another tool that can be used, the "MSP Flasher":
    www.ti.com/.../msp430-flasher
  • A TI rep admitted that the versions were not synchronized. I have *some* sympathy, because, and although it's no excuse, I have run into similar issues in my past (with other vendors). It should still be fixed of course!

    BTW, it was suggested to me to use the Elprotronic FET debugger /interface (free) - I found it to be quite easy to use and it solved my actual problem (whereby the TI tool would NOT allow me read access to the TrxEB's MSP430 so that I could capture the chip's TI-supplied image)

    Øyvind,
    I will keep that "MSP- Flasher" tool in mind, thanks. Unfortunately I am working in an environment that makes it quite difficult for me to download and install new products - so most troubleshooting is done at home and therefore the feedback loop can be painfully slow.

    -Mike
  • OK, I just posted a reply here - where did it go? :-(
  • Trying again...

    A TI rep admitted that the versions were not synchronized. I have *some* sympathy, because, and although it's no excuse, I have run into similar issues in my past (with other vendors). It should still be fixed of course!

    BTW, it was suggested to me to use the Elprotronic FET debugger /interface (free) - I found it to be quite easy to use and it solved my actual problem (whereby the TI tool would NOT allow me read access to the TrxEB's MSP430 so that I could capture the chip's TI-supplied image)

    Øyvind,
    I will keep that "MSP- Flasher" tool in mind, thanks. Unfortunately I am working in an environment that makes it quite difficult for me to download and install new products - so most troubleshooting is done at home and therefore the feedback loop can be painfully slow.

    -Mike

  • Mike,

    Oeyvind is located in Europe, he will answer in the morning.

    Regards,
    /TA