• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 80 subscribers
  • Views 2279 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.

MSP Flasher : Flashing error with MSP430F5437A

Abinash Prusty
Prodigy 70 points

Other Parts Discussed in Thread: MSP430F5437A, MSP-FET, MSP430-FLASHER

I have following setup

  1. MSP430F5437A
  2. MSP-FET430UIF
  3. MSP Flasher v1.3.8

I am trying to use "MSP Flasher - Command Line Programmer" to flash the micro with a MSP430-TI txt file. Following are the command used and the log from the tool.

Command: MSP430Flasher -n MSP430F5437A -w combined.txt -v -e ERASE_MAIN -z [VCC]

Log:

Wed May 11 15:00:28 2016:    * -----/|-------------------------------------------------------------------- *
Wed May 11 15:00:28 2016:    *     / |__                                                                   *
Wed May 11 15:00:28 2016:    *    /_   /   MSP Flasher v1.3.8                                              *
Wed May 11 15:00:28 2016:    *      | /                                                                    *
Wed May 11 15:00:28 2016:    * -----|/-------------------------------------------------------------------- *
Wed May 11 15:00:28 2016:    *
Wed May 11 15:00:28 2016:    * Evaluating triggers...done
Wed May 11 15:00:28 2016:    * Checking for available FET debuggers:
Wed May 11 15:00:29 2016:    * Found USB FET @ COM31 <- Selected
Wed May 11 15:00:29 2016:    * Initializing interface @ COM31...done
Wed May 11 15:00:29 2016:    * Checking firmware compatibility:
Wed May 11 15:00:29 2016:    * The firmware of your FET is outdated.
Wed May 11 15:00:29 2016:    - Would you like to update it? (Y/N): Wed May 11 15:00:31 2016:    n
Wed May 11 15:00:31 2016:    * Warning: FW mismatch! Correct functionality not guaranteed!
Wed May 11 15:00:31 2016:    * Reading FW version...done
Wed May 11 15:00:31 2016:    * Setting VCC to 3000 mV...done
Wed May 11 15:00:32 2016:    * Accessing device...done
Wed May 11 15:00:33 2016:    * Reading device information...done
Wed May 11 15:00:33 2016:    * Loading file into device...done
Wed May 11 15:03:50 2016:    * Verifying memory (combined.txt)...
Wed May 11 15:03:51 2016:    # Exit: 60
Wed May 11 15:03:51 2016:    # ERROR: Verification error
Wed May 11 15:03:51 2016:    * Starting target code execution...done
Wed May 11 15:03:51 2016:    * Disconnecting from device...done
Wed May 11 15:03:51 2016:    *
Wed May 11 15:03:51 2016:    * ----------------------------------------------------------------------------
Wed May 11 15:03:51 2016:    * Driver      : closed (No error)
Wed May 11 15:03:51 2016:    * ----------------------------------------------------------------------------
Wed May 11 15:03:51 2016:    */

I am able to flash the same file using "FET-Pro430 Lite Software" without any issues.

Please let me know mistake I am doing to use this tool. Thanks!

  • 0
    TI__Guru**** 223077 points
    Why are you choosing to not update the FET firmware? A firmware mismatch could explain the verification error your are experiencing, otherwise it appears that loading the file into the device is successful. Can you provide your TI txt file for me to test?

    Regards,
    Ryan
  • 0 in reply to Ryan Brown1
    Prodigy 70 points
    If I update the FET firmware it doesn't work with existing flashing tools software such as "FET-Pro Lite" or IAR.

    Now I found another version of MSP430 Flasher with version "1.1.9.0" (Current version is 1.3.8.0) and it worked fine. I am able to flash the device using the same command as above. I have following two queries now.
    1. What is the difference in operation of MSP430 Flasher programmer so that older version works where as latest version doesn't?
    2. Flashing time for "MSP430 Flasher" is mush higher than the "FET-Pro Lite" (100 sec vs 40 Sec). What might be the reason and how can I reduce this time ?

    I am trying to automate the flashing of the device for which I need these information. I won't be able to share the binary file as its company property. Let me know if you need some other information.

    Regards,
    Abinash
  • 0 in reply to Abinash Prusty
    TI__Guru**** 223077 points
    1. The MSP-FET430UIF firmware was not in sync with the MSP Debug Stack (MSP430.dll or libmsp430.so or libmsp430.dylib depending on your OS) provided with MSP Flasher 1.3.8. In this particular case the firmware version was so outdated (3.5 years difference judging from MSP Flasher 1.1.9 being mentioned) that there is a high likeliness of incompatibilities between the new MSP Debug Stack and the old FET firmware. As the MSP Flasher console output states, there is no guarantee for full functionality in this case.
    2. This significant difference in programming time points towards a different protocol (4-wire JTAG vs 2-wire SBW) used in the two cases. How exactly is the target MSP connected? Regular target socket board or custom HW? Which version of FET-Pro Lite is being used? What are the settings? MSP Flasher erases the memory as part of the programming step. Is this included in the 40 sec measurement for FET-Pro Lite? The MSP-FET (not MSP-FET430UIF) offers the option of increasing the JTAG frequency. MSP Flasher supports this as of version 1.3.4.

    Regards,
    Ryan
  • 0 in reply to Ryan Brown1
    Prodigy 70 points
    I got the new MSP-FET you have suggested and tested the same with MSP Flasher 1.3.8.0. Still the time for flashing is same(>100 sec).
    Regarding your queries, the connection is a 4-wire JTAG to a custome hardware. Yes I have considered the erasing time for Fet-Pro Lite which is of version 3.4.0. The version of MSP-FET 430UIF firmware is 2.04.09.001. Latest version of this is 3.05.01.001. But if I update the firmware it does not work even with the FET-Pro Lite.
    The connection is same whether I am using Fet-Pro Lite or MSP Flasher. Please let me know if there is difference in operation of these two application with respect to JTAG connection.
  • 0 in reply to Abinash Prusty
    TI__Guru**** 223077 points
    You can also change the JTAG communication speed in MSP430-FLASHER using the -j trigger, default is slow but medium and fast are also supported.

    Regards,
    Ryan

**Attention** This is a public forum