msp430FR4133 FET Firmware PostUpdate Failure - brick or salvage?

David Pekin

Other Parts Discussed in Thread: MSP430FR4133, MSP430-FLASHER, MSP-EXP430FR4133

Hello,

I've broken this thread off from a XP VM tools issue thread as that is a separate and independent problem.

I have the MSP430FR4133 Launchpad. I'm running Windows 8 and the drivers (V 1.4.0) are installed.

To test the firmware burning process I ran the "Program OutOfBox_MSP430FR4133" batch file which calls the MSP Flasher program to burn the default out of box hex image file.

When I ran the batch file the MSP Flasher program indeicated that the FET firmware was outdated and asked if I would like to update it. I selected "Yes" and the program burned new FET firmware and then burned the OutOfBox program. I unplugged and replugged the device to the computer and the Out of Box program ran correctly.

Then I tried to burn another sample program onto the device using the MSP Flasher program. Now, the MSP Flasher program always indicates "Exit 16, Unknown Device" and it aborts. (Shown below)

I can only assume that the burning of the updated FET firmware caused this issue since it recognized the device the first time and now it doesn't.

As it sits, I can no longer update the firmware on the LaunchPad. Is there any way to recover from this???

Thanks,

- Dave

Mon Oct 31 12:22:47 2016: * -----/|-------------------------------------------------------------------- *
Mon Oct 31 12:22:47 2016: * / |__ *
Mon Oct 31 12:22:47 2016: * /_ / MSP430 Flasher v1.3.0 *
Mon Oct 31 12:22:47 2016: * | / *
Mon Oct 31 12:22:47 2016: * -----|/-------------------------------------------------------------------- *
Mon Oct 31 12:22:47 2016: * Evaluating triggers...
Mon Oct 31 12:22:47 2016: * Invalid argument for -m trigger. Default used (AUTO).
Mon Oct 31 12:22:47 2016: * Checking for available FET debuggers:
Mon Oct 31 12:22:47 2016: * Found USB FET @ COM5.Mon Oct 31 12:22:47 2016:
Mon Oct 31 12:22:47 2016: * Initializing interface on TIUSB port...done
Mon Oct 31 12:22:47 2016: * Checking firmware compatibility:
Mon Oct 31 12:22:47 2016: * FET firmware is up to date.
Mon Oct 31 12:22:47 2016: * Reading FW version...done
Mon Oct 31 12:22:47 2016: * Reading HW version...done
Mon Oct 31 12:22:47 2016: * Setting VCC to 3000 mV...done
Mon Oct 31 12:22:49 2016: * Accessing device...
Mon Oct 31 12:22:49 2016: # Exit: 16
Mon Oct 31 12:22:49 2016: # ERROR: Unknown device
Mon Oct 31 12:22:49 2016: * Disconnecting from device...done
Mon Oct 31 12:22:49 2016: *
Mon Oct 31 12:22:49 2016: * ----------------------------------------------------------------------------
Mon Oct 31 12:22:49 2016: * Driver : closed (Internal error)
Mon Oct 31 12:22:49 2016: * ----------------------------------------------------------------------------
Mon Oct 31 12:22:49 2016: */

over 9 years ago

0 Katie Pier over 9 years ago

TI__Guru* 79301 points

Hi Dave,

I was able to reproduce your issue. Fortunately, because this is reporting an Unknown device error it means that the PC is still able to communicate with the eZ-FET emulator, and the error is further down the process. That means this is very recoverable.

I was able to resolve the issue on my Launchpad by using a newer version of MSP430-Flasher - it looks like this OutOfBox software is shipping with version 1.3.0 and we are now on 1.3.10. www.ti.com/.../msp430-flasher

If you install 1.3.10 (very small install), then take the files MSP430Flasher.exe and MSP430.dll from the install location and replace these files in the MSP-EXP430FR4133_Software_Examples_windows/Firmware/Binary/OutOfBox_MSP430FR4133. When I do that, if you then run the .bat file like before and allow it to update the firmware, I had no further issues and could repeatedly load code.

It is unfortunate you are running into these problems, but I really appreciate your posting as it will help us to get things updated for everyone. I'll be filing this against the outOfBox code to get updated.

Regards,
Katie