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.

MSP430Flasher for unattended scripts

Unattended scripts (batch files, nUnit, Nant, etc.) are broken by prompt for y/n input if FET firmware update offered. FET firmware version often does not matter, especially for older, stable parts, or minor firmware bugfixes. Unless someone else has a solution, I would like to add a switch to suppress the FET version check. Unless someone else wants some letter reserved, I would find something mnemonic from the unused command-line switch letters "acjksty".

I've edited an option: case 's': // Suppress FET firmware update prompt ... to support unattended scripts better

which will not attempt console or stdin input.

How can I share my work?

Where can I post or submit this edit?

  • Pete Klammer said:

    I've edited an option: case 's': // Suppress FET firmware update prompt ... to support unattended scripts better

    Where can I post or submit this edit?

    How was this resolved?  I was going to suggest that you post to the wiki page MSP430 Flasher - Command Line Programmer but I can see that you did that the same day you posted on the forum.  What kind of repsonse did you get?  I suppose you could also post the source file with your edit to the wiki.

  • Hi Jason,

    The firmware update suppression switch -s is actually included in the MSP430 Flasher since May 10th, 2011 (version 1.1.2). It was added as a reaction to feedback on the FET FW update user prompt (including Pete’s comment on the wiki).  

    In the upcoming version 1.2.0 of the MSP430 Flasher the function of this switch will change, though. Instead of skipping the FET firmware update, the –s switch will force an update without a user prompt. The reason for this change is that we just can’t guarantee full functionality of our tools if there’s a mismatch between the FET firmware and the low level software running on the host machine.

    Unfortunately right now we don’t provide the infrastructure to enable users to really contribute to the MSP430 Flasher project yet. However this might change in 2013. So stay tuned. We’d love to see more people playing with our open source code!

    Best Regards,

    Robert

**Attention** This is a public forum