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.

problem with updating MSP-FET firmware in MSP430Flasher

Other Parts Discussed in Thread: MSP-FET, RF430FRL152HEVM, RF430FRL152H

Win7-64, CCSv6,  MSP430Flasher + MSP-FET

run MSP430Flasherv1.3.3, update FET firmware, do "Y", and unplug/replug,  and check agian:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\ti\MSP430Flasher_1.3.3>msp430flasher
* -----/|-------------------------------------------------------------------- *
*     / |__                                                                   *
*    /_   /   MSP430 Flasher v1.3.3                                           *
*      | /                                                                    *
* -----|/-------------------------------------------------------------------- *
*
* Evaluating triggers...done
* Checking for available FET debuggers:
* Found USB FET @ COM13 <- Selected
* Initializing interface @ COM13...done
* Checking firmware compatibility:
* FET firmware is up to date.
* Reading FW version...done
* Setting VCC to 3000 mV...done
* Accessing device...
# Exit: 16
# ERROR: Unknown device
* Powering down...done
* Disconnecting from device...done
*
* ----------------------------------------------------------------------------
* Driver      : closed (Internal error)
* ----------------------------------------------------------------------------

C:\ti\MSP430Flasher_1.3.3>

...what mean for?  I have checked : MSP430.dll (V 3.4.3.4) HIL.dll  (V 1.2.6.0)

please help me urgently

  • Hi Andy,

    Do you have an MSP430 board connected to the MSP-FET? What device and what board (a TI development board, or one of your own design?) This dialogue above looks like the FET is now up-to-date, but when it tried to access your MSP430 device it did not recognize it and gave an "unknown device" error.

    This could mean no MSP430 device was connected to the MSP-FET, or it was not connected properly, or some other error. If you use your own board, we'd need information on the device used, all of the programming connections used, and how the board is being powered. The programming connections from the MSP430 to the MSP-FET need to match those in Chapter 2 of the Hardware Tools User's Guide www.ti.com/lit/pdf/slau278  

    Regards,
    Katie

  • Hi Katie,

    Thank you for your reply

    Yes, There is a TI RF430FRL152HEVM board was connected to FET, and have checked EVM configuration as Debugging or Progamming according SLAU607_page6 and connection properly. Run MSP430Flasher, the diglogue above not difference on connected or disconneced EVM.
    During FET was updating yesterday(FET drive done and running MSP430Flasher first time, do FET updating automatic), the EVM was not connected. updating done then reset(unplug/replug) and then the digogue above gave whatever EVM was connected or disconnected.
    something wrong I done?

    looking forwad to your solution

    Regards
    Andy
  • Hi Andy,

    Thanks for providing the information about the board that you use - I've been able to get the same board, and I can reproduce the issue. We are looking into this now and I will update you as soon as I learn more. Sorry for your difficulties and thanks so much for reporting the issue.

    Regards,
    Katie
  • Hi Andy,

    Please use the -o switch to specify the operation mode for the RF430 device (-o L = normal mode -o C = ROM emulation mode). Usually, MSP430 Flasher would prompt the user about this parameter being required but that only works if "-n RF430FRL152H" is used. You should be able to access the target device with one of the following commands:

    MSP430Flasher -n RF430FRL152H -o L
    MSP430Flasher -o L

    We will enhance the documentation to highlight this.

    Best regards,
    Robert
  • All fixed.

    Robert and Katie, Thank you so much your help.

    Regards,
    Andy

**Attention** This is a public forum