CCSV6 in infinite firmware update loop

Hello Edward,

Can you do me a favor and verify the MSP430.dll and HIL.dll revisions in your installation?

Browse to ./ti/ccsv6/ccs_base/DebugServer/drivers and mouse over HIL.dll and MSP430.dll. There should be revision numbers listed in the file properties under the details tab. This information should also be shown in the file information pop-up when you mouse-over the file.

HLL.DLL: created ‎Monday, ‎July ‎07, ‎2014, ‏‎10:37:55 AM, File Version 1.2.6.0, Product Version 1.2.6.0
MSP430.DLL: created ‎Monday, ‎July ‎07, ‎2014, ‏‎10:37:55 AM, File Version 3.4.3.4, Product Version 3.4.3.4

I hope this helps! And thanks for the amazingly quick response!

Ed Averill

Thank you Ed.  Let's try this;

Download the latest version of the MSP430 Flasher from here and install. Once installed, make sure you only have one FET connected to the host, browse to the installation directory, drop-in the batch file attached to this reply and run it from there.  This will force the firmware update on the FET to v3.4.2.4 and should eliminate the need to update in CCS.

Let me know what happens.

There's no MSP430Flash.exe that I can find. Lots of MSP430Flasher.exe's, though.

Where should I expect to find that EXE?

I'm thinking maybe uninstalling/reinstalling CCS V6 off the original DVD might not be a bad idea...

Ed Averill

Well, de-installed and re-installed from the original DVD and I get the SAME ISSUE:

MSP430: Error initializing emulator: A firmware update is required for the MSP430 Debug Interface (MSP-FET430UIF / MSP-FET / eZ-FET). Click the "Update" button to update the firmware and launch your debug session (this may require several update steps). DO NOT UNPLUG THE INTERFACE DURING THE UPDATE.
MSP430: Error initializing emulator: A firmware update is required for the MSP430 Debug Interface (MSP-FET430UIF / MSP-FET / eZ-FET). Click the "Update" button to update the firmware and launch your debug session (this may require several update steps). DO NOT UNPLUG THE INTERFACE DURING THE UPDATE.
MSP430: Error initializing emulator: A firmware update is required for the MSP430 Debug Interface (MSP-FET430UIF / MSP-FET / eZ-FET). Click the "Update" button to update the firmware and launch your debug session (this may require several update steps). DO NOT UNPLUG THE INTERFACE DURING THE UPDATE.
MSP430: Error initializing emulator: A firmware update is required for the MSP430 Debug Interface (MSP-FET430UIF / MSP-FET / eZ-FET). Click the "Update" button to update the firmware and launch your debug session (this may require several update steps). DO NOT UNPLUG THE INTERFACE DURING THE UPDATE.
MSP430: Error initializing emulator: A firmware update is required for the MSP430 Debug Interface (MSP-FET430UIF / MSP-FET / eZ-FET). Click the "Update" button to update the firmware and launch your debug session (this may require several update steps). DO NOT UNPLUG THE INTERFACE DURING THE UPDATE.
MSP430: Error initializing emulator: A firmware update is required for the MSP430 Debug Interface (MSP-FET430UIF / MSP-FET / eZ-FET). Click the "Update" button to update the firmware and launch your debug session (this may require several update steps). DO NOT UNPLUG THE INTERFACE DURING THE UPDATE.
MSP430: Error initializing emulator: A firmware update is required for the MSP430 Debug Interface (MSP-FET430UIF / MSP-FET / eZ-FET). Click the "Update" button to update the firmware and launch your debug session (this may require several update steps). DO NOT UNPLUG THE INTERFACE DURING THE UPDATE.
MSP430: Error initializing emulator: A firmware update is required for the MSP430 Debug Interface (MSP-FET430UIF / MSP-FET / eZ-FET). Click the "Update" button to update the firmware and launch your debug session (this may require several update steps). DO NOT UNPLUG THE INTERFACE DURING THE UPDATE.
MSP430: Error initializing emulator: A firmware update is required for the MSP430 Debug Interface (MSP-FET430UIF / MSP-FET / eZ-FET). Click the "Update" button to update the firmware and launch your debug session (this may require several update steps). DO NOT UNPLUG THE INTERFACE DURING THE UPDATE.
MSP430: Error initializing emulator: A firmware update is required for the MSP430 Debug Interface (MSP-FET430UIF / MSP-FET / eZ-FET). Click the "Update" button to update the firmware and launch your debug session (this may require several update steps). DO NOT UNPLUG THE INTERFACE DURING THE UPDATE.
MSP430: Error initializing emulator: A firmware update is required for the MSP430 Debug Interface (MSP-FET430UIF / MSP-FET / eZ-FET). Click the "Update" button to update the firmware and launch your debug session (this may require several update steps). DO NOT UNPLUG THE INTERFACE DURING THE UPDATE.
MSP430: Error initializing emulator: A firmware update is required for the MSP430 Debug Interface (MSP-FET430UIF / MSP-FET / eZ-FET). Click the "Update" button to update the firmware and launch your debug session (this may require several update steps). DO NOT UNPLUG THE INTERFACE DURING THE UPDATE.
MSP430: Error initializing emulator: A firmware update is required for the MSP430 Debug Interface (MSP-FET430UIF / MSP-FET / eZ-FET). Click the "Update" button to update the firmware and launch your debug session (this may require several update steps). DO NOT UNPLUG THE INTERFACE DURING THE UPDATE.
MSP430: Error initializing emulator: A firmware update is required for the MSP430 Debug Interface (MSP-FET430UIF / MSP-FET / eZ-FET). Click the "Update" button to update the firmware and launch your debug session (this may require several update steps). DO NOT UNPLUG THE INTERFACE DURING THE UPDATE.
MSP430: Error initializing emulator: A firmware update is required for the MSP430 Debug Interface (MSP-FET430UIF / MSP-FET / eZ-FET). Click the "Update" button to update the firmware and launch your debug session (this may require several update steps). DO NOT UNPLUG THE INTERFACE DURING THE UPDATE.
MSP430: Error initializing emulator: Could not set device Vcc
MSP430: Error initializing emulator: Could not set device Vcc

Is there az decent third-party MSP430 emulator that works with CCS V6? This is holding up my work on the prototype of this new product, I'd rather revisit this issue later if I can find an operational alternative.

Ed Averill

Fixed the script.  Try it now.

Ok, I see what you're trying to do, but there is no MSP430Flasher.exe anywhere in the ZIP package I downloaded.

After running a scan for MSP430Flaser.exe I see over a dozen versions scattered throughout the '
MSP430Ware directories under the c:\ti master directory, none of which  are part of the PATH.. this is why the batch file can't locate the proper executable.

Where should MSP430Flaser.exe live?

Ed Averill

ps. In the meantime, I'm going to de-install CCS V6 again, this time delete the directory, and do a 100% clean re-install and see if that helps.

Ed,

You shouldn't have downloaded a zip package,It should have been an installer package.

MSP430Flasher-1_03_03_00-windows-installer.exe

The package will install to C:\ti\msp430flasher_1.3.3.  MSP430flasher.exe will be in the root of this package.

Ok, this time I see the exe.. no idea how I ended up with a ZIP file. Downloading, will give it a shot next. Thanks for your patience!

Ed Averill

Right.. I ran the updated bath file, and this is what I got:


* Unable to access log file. Creating folder...done
* -----/|-------------------------------------------------------------------- *
* / |__ *
* /_ / MSP430 Flasher v1.3.3 *
* | / *
* -----|/-------------------------------------------------------------------- *
*
* Evaluating triggers...done
* Checking for available FET debuggers:
* Found USB FET @ COM9 <- Selected
* Initializing interface @ COM9...done
* Checking firmware compatibility:
* The firmware of your FET is outdated.
* Skipped firmware update prompt.


*********************************************************
*
* Initializing Update Bootloader.
* Programming new firmware:
* |||||||||||||||||||||||||||||||||||||||||||||||||| 100%
*********************************************************
*
* Initializing Update Bootloader.
* Programming new firmware:
* |||||||||||||||||||||||||||||||||||||||||||||||||| 100%
* Update was successfully finished.
*
*********************************************************

* Exit Update Bootlader and reboot firmware.
# Exit: 49
# ERROR: MSP-FET / eZ-FET legacy module update failed
*
* ----------------------------------------------------------------------------
* Driver : closed (No error)
* ----------------------------------------------------------------------------
*/
Press any key to continue . . .

..manually resetting the FET produces the all-too-familiar messages from CCSV6..

Error initializing emulator:
A firmware update is required for the MSP430 Debug Interface (MSP-FET430UIF / MSP-FET / eZ-FET). Click the "Update" button to update the firmware and launch your debug session (this may require several update steps).

DO NOT UNPLUG THE INTERFACE DURING THE UPDATE.

..I went ahead and did it, and of course no joy..

I switched to the second FET, ran the batch file, and this time I goit this:

* -----/|-------------------------------------------------------------------- *
* / |__ *
* /_ / MSP430 Flasher v1.3.3 *
* | / *
* -----|/-------------------------------------------------------------------- *
*
* Evaluating triggers...done
* Checking for available FET debuggers:
* Found USB FET @ COM5 <- Selected
* Initializing interface @ COM5...done
* Checking firmware compatibility:
* The firmware of your FET is outdated.
* Skipped firmware update prompt.


*********************************************************
*
* Initializing Update Bootloader.
* Programming new firmware:
* |||||||||||||||||||||||||||||||||||||||||||||||||| 100%
* Update was successfully finished.
*
*********************************************************

* Exit Update Bootlader and reboot firmware.
* 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...
* ----------------------------------------------------------------------------
* ERROR on close: Could not set device Vcc
* ----------------------------------------------------------------------------
*/
Press any key to continue . . .

..different, but I have no idea what is meant by "Unknown device".. trying CCS V6 with this FET produces:

Error initializing emulator:
A firmware update is required for the MSP430 Debug Interface (MSP-FET430UIF / MSP-FET / eZ-FET). Click the "Update" button to update the firmware and launch your debug session (this may require several update steps).

DO NOT UNPLUG THE INTERFACE DURING THE UPDATE.

..which, honestly, I didn't expect.

Clueless here and my project manager is getting kind of agitated. Again - are there any third party MSP430 emulators that work with CCS V6?

Ed Averill

Error 16 is expected if you don't have the 14pin end connected to a board. This is normal and shouldn't be a cause for alarm. If the DLL version you told me is correct, the emulator should not have needed an update because you just performed an update to v3.4.3.4.

I want to try a different approach, dependent on the device that you're developing for. What is your development target device?

Edit - The MSP-FET/MSP-FET430UIF HIL/DLL is the only interface supported in CCS.  I'm not aware of any commercial 3P tools that use the same interface.  I'll check around and see if there are any options.

We have an MSP430F5638 on a proto board, hooked to the emulator with the cable that came with the FET. The board is a TI-sourced LQFP ZIF-socketed board (forget the model) that has a USB header and a real nice pin breakout. No mods have been made to the board, and it's powered from the FET.

..here you go, screen caps of the DLL properties.  Looks correct to me...

Ed Averill

This just keeps getting worse.

I installed CCS V5, and it can't even SEE the MSP-FET! Is there some kind of back-rev'ing I need to do on the MSP-FET firmware to get it to operate?

Oh, and when I unplug/replug the MSP-FET, the POWER light comes on, but the it immediately goes off and the MODE light comes on. Does this mean something Bad(tm) has happened?

In the meantime, my project manager insists I find alternatives.. can't blame him for that. Can you recommend a third-party emulator? I've found one already but it'd be nice to hear from the chip vendor!

This has become a showstopper. I'm going to have to re-contact support and get my project manager involved, whatever is going on here is obviously outside of my control.

I tried, in desperation, copying the HLL.dll and MSP430.dll files from the Flasher directory into the C:\ti\ccsv6\ccs_base\DebugServer directory, over-writing the original DLLs, and still the same eternal update. I've tried running CCSV6 as administrator in case something went wrong there. I've pulled every single other USB device off in case CCS was getting confused.

Nothing. Worked.

Hitting IGNORE when CCS tries to reflash produces this, FWIW:

Error initializing emulator:
Could not set device Vcc

Taking this offline.

God! I have same problem with this, how to do " downgrade to v3.4.2.7 DLL and firmware", now it is v3.4.3.4 DLL
Thanks

Regards
Andy

Hi Michael,

how did you downgrade? I am having the same problem, except with the 3.5.0.1 DLL and firmware. I am using a MSP-430FR6989 Launchpad.