• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 81 subscribers
  • Views 1891 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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 command line

dieter weh
Prodigy 20 points
Other Parts Discussed in Thread: MSP430-FLASHER, MSP-FLASHER

I use the MSP430flasher to flash a controller with fhe following command line

 MSP430Flasher.exe -iCOM48 -mSBW2 -nMSP430FR5737 -w744.320.027AD.hex -v  

MSP430flasher shows the following

* -----/|-------------------------------------------------------------------- *
*     / |__                                                                   *
*    /_   /   MSP Flasher v1.3.15                                             *
*      | /                                                                    *
* -----|/-------------------------------------------------------------------- *
*
* Evaluating triggers...done
* Checking for available FET debuggers:
* Found USB FET @ COM48 <- Selected
* Initializing interface @ COM48...done
* Checking firmware compatibility:
* FET firmware is up to date.
* Reading FW version...done
* Setting VCC to 3000 mV...done
* Accessing device...done
* Reading device information...done
* Loading file into device...done
* Verifying memory (744.320.027AD.hex)...
 Exit: 10
 ERROR: Could not reset device
* Powering down...done
* Disconnecting from device...done
*
* ----------------------------------------------------------------------------
* Driver      : closed (No error)
* ----------------------------------------------------------------------------
*/
as you see from the ouput the code seems to be flash but it can not be brought into reset -

so I tried to check if the device is programmed and just the verify did not succed, first I tried with the oiginal hexfile

and got the same response as below - to check if the response is okay I changed the command line to use a different

hexfile

 MSP430Flasher.exe -iCOM48 -mSBW2 -nMSP430FR5737 -v744.630.052AA.hex  

 -----/|-------------------------------------------------------------------- *
*     / |__                                                                   *
*    /_   /   MSP Flasher v1.3.15                                             *
*      | /                                                                    *
* -----|/-------------------------------------------------------------------- *
*
* Evaluating triggers...done
* Checking for available FET debuggers:
* Found USB FET @ COM48 <- Selected
* Initializing interface @ COM48...done
* Checking firmware compatibility:
* FET firmware is up to date.
* Reading FW version...done
* Setting VCC to 3000 mV...done
* Accessing device...done
* Reading device information...done
* Powering down...done
* Disconnecting from device...done
*
* ----------------------------------------------------------------------------
* Driver      : closed (No error)
* ----------------------------------------------------------------------------
*/

This looks like there should be no error, but I supplied a wrong hexfile to check for so

what is verified ??

with best regards

     dieter

  • 0
    TI__Mastermind 49692 points

    Hello Dieter,

    Can you confirm that your reset circuitry matches our recommendations? I'm concerned that the MSP430 device is on a custom board, and if the reset circuit isn't correct, I could see where the device would not get reset properly by the MSP430-Flasher. Please refer to Figure 2-3 in our MSP430 Hardware Tools User's Guide.

    Regards,

    James

    MSP Customer Applications

  • 0 in reply to James Evans
    Prodigy 20 points

    The reset circuity mets the recommendation from TI. But this is not rhe Question, if I do a verify I would expect a error code given

    by the tool . I have flashed the controller using a hexfile and did then a separate verify, as I did not trust the result I supplied a wrong

    hexfile to compare with and I got the same result, so what does the verify command check if it does not recognize an error like this.

    with best regards

       dieter

  • 0 in reply to dieter weh
    Guru 34743 points

    dieter weh said:

    The reset circuity mets the recommendation from TI. But this is not rhe Question, if I do a verify I would expect a error code given

    by the tool . I have flashed the controller using a hexfile and did then a separate verify, as I did not trust the result I supplied a wrong

    hexfile to compare with and I got the same result, so what does the verify command check if it does not recognize an error like this.

    You are completely right. Any tool should report precise/clear error description. If there is interface/connection problem, it is tool/software job to report this.

  • 0 in reply to dieter weh
    TI__Prodigy 595 points

    Hi Dieter,

    you have detected a corner case in the MSP-Flasher where the application does not detect the parameter of -v if there is no whitespace between the trigger ("-v") and the filename ("744.630.052AA.hex"). This should work for every other parameter though. Temporary workaround for you is to add the missing whitespace. This limitation will be fixed with the next MSP-Flasher release 1.3.16 (ETA is end of November).

    Regarding your reset issue, I'm not quite sure what could cause this. Would it possible that you attach a file here that helps us reproduce the issue on our end?

    Thanks,

    Bob

**Attention** This is a public forum