MSP430 LaunchPad can't flash firmware

[Jdkmotorhead]

Our LaunchPad was working fine for a while, but it just stopped connecting to the driver station laptop, so I tried reflashing it. Whenever I try to flash the FRC firmware onto the LaunchPad, it gives me the error:

The program encountered an error: Error: 5000
Gamepad Tool.vi<ERR>
Programmer did not succeed. Check log for details

And in the log:

tilib: MSP430_OpenDevice: Unknown device (error = 5)
tilib: device initialization failed
MSPDebug version 0.20 - debugging tool for MSP430 MCUs
Copyright (C) 2009-2012 Daniel Beer <dlbeer@gmail.com>
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

MSP430_Initialize: COM8
Firmware version is 30301004
MSP430_VCC: 3000 mV
MSP430_OpenDevice

Every few times I try to flash it, it does work, but it still isn't recognized by the driver station; and if I try to immediately reflash it, it gives me the error again.

Also, does anyone know what the four buttons on the LaunchPad do? Is there a chance that I accidentally pushed one of them and disabled it somehow? (the green power led is on, and when I am attempting to flash it, the red led starts blinking) I also tried it on another laptop, and it does the same thing. I also attempted to flash Energia on it, but that gave me the same error.

I also tried flashing it from the command line, but the outcome was no different:

C:\WINDOWS\system32>"C:\Program Files (x86)\FRC Gamepad Tool\Tools\mspdebug\mspdebug.exe" tilib --allow-fw-update
MSPDebug version 0.20 - debugging tool for MSP430 MCUs
Copyright (C) 2009-2012 Daniel Beer <dlbeer@gmail.com>
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

MSP430_GetNumberOfUsbIfs
MSP430_GetNameOfUsbIf
Found FET: COM8
MSP430_Initialize: COM8
Firmware version is 30301004
MSP430_VCC: 3000 mV
MSP430_OpenDevice
tilib: MSP430_OpenDevice: Unknown device (error = 5)
tilib: device initialization failed

[wt200999]

Originally Posted by Jdkmotorhead

Our LaunchPad was working fine for a while, but it just stopped connecting to the driver station laptop

When you say it was working, does that mean it was showing up on the driver station as a joystick?

Did anything happen to the board when it disconnected, or was it truly random? (Where you in the process or testing a button/axis? Did the board fall and maybe short a few pins? etc.).

Based on your description, it sounds like the board may be damaged. If you go to the device manager in Windows, you should see two devices based on the MSP430. One is under 'Ports' and one is either under 'ports' or under 'HID' (or something similar).

[EthanJF123]

Attached are instructions on how to make it first enumerate as what TI originally programmed the launchpad to be, a small flash drive. There are also instructions on how to make it a joystick. Also attached is zipped file of an installer to program the launchpad to make it a flash drive.

------------------------------------------------------------------------------------------
Ethan Fuller
Programmer for MARS 2614

[Jdkmotorhead]

Originally Posted by EthanJF123

Attached are instructions on how to make it first enumerate as what TI originally programmed the launchpad to be, a small flash drive. There are also instructions on how to make it a joystick. Also attached is zipped file of an installer to program the launchpad to make it a flash drive.

------------------------------------------------------------------------------------------
Ethan Fuller
Programmer for MARS 2614

Ok thanks, I'll give this a try when I get the chance.

[Jdkmotorhead]

Originally Posted by wt200999

When you say it was working, does that mean it was showing up on the driver station as a joystick?

Did anything happen to the board when it disconnected, or was it truly random? (Where you in the process or testing a button/axis? Did the board fall and maybe short a few pins? etc.).

Based on your description, it sounds like the board may be damaged. If you go to the device manager in Windows, you should see two devices based on the MSP430. One is under 'Ports' and one is either under 'ports' or under 'HID' (or something similar).

Well, it actually happened when I was testing a switch; first, it started behaving strangely. When I would flip the switch on, the LaunchPad just shut off; the green LED turned off, and it was no longer seen by the driver station. When I flipped the switch back off, the LED came back on, and it was recognized by the driver station again. I was messing with it and trying to get the switch to work when it stopped working.

[wt200999]

Originally Posted by Jdkmotorhead

Well, it actually happened when I was testing a switch; first, it started behaving strangely. When I would flip the switch on, the LaunchPad just shut off; the green LED turned off, and it was no longer seen by the driver station. When I flipped the switch back on, the LED came back on, and it was recognized by the driver station again. I was messing with it and trying to get the switch to work when it stopped working.

Which pins did you have connected to the switch when this started to happen?

One thing to be careful of with the Launchpad is the IO pins are meant to be run on 3.3V and not 5V. Unfortunately the 3.3V and the 5V pins are right next to each other on the header.

Originally Posted by Jdkmotorhead

Ok thanks, I'll give this a try when I get the chance.

If you try this and still cannot get it to work, let me know and we can ship you out a replacement.

[Jdkmotorhead]

Originally Posted by wt200999

Which pins did you have connected to the switch when this started to happen?

One thing to be careful of with the Launchpad is the IO pins are meant to be run on 3.3V and not 5V. Unfortunately the 3.3V and the 5V pins are right next to each other on the header.



If you try this and still cannot get it to work, let me know and we can ship you out a replacement.

I tried it, but I'm stuck on the part where you enumerate it as a flash drive. Whenever I run the command, it says it cannot find the LaunchPad:

Programing MSP-EXP430F5529UserExperience.txt into MSP430F5529 ......
Log directory already exist
Evaluating additional triggers...done
Initializing interface on TIUSB port...


 # Exit: 19
 # ERROR 1014: Could not find MSP-FET430UIF on specified COM port

*******************************************************************************
UseCase for MSP430.dll
Demo application for identifying an MSP430 device and compare the read
parameters of the device properties structure against the parameters given by
the DeviceID number through MSP430_Device().

Usage: MSP430Flasher.exe [OPTIONS]

 -n DEVICE NAME              specifies the name of the targeted device.
                             (required)
 -o L | C                    specifies the desired mode (only for L092 device).
                             (use L for L092 and C for C092-emulator mode)
 -l PASSWORD LENGTH          specifies the length of the JTAG password.
                             (in words, if any, default: 0)
 -p JTAG PASSWORD            specifies the JTAG password (form: 0x...).
                             (if any, default: no password)
 -i (TI)USB | LPTn | COMn    specifies the connection interface.
                             (default: TIUSB (=USB))
 -m JTAG | SBW2 | SBW4 |     specifies the communication mode
    AUTO                     (JTAG or Spy-Bi-Wire. default: AUTO)

 -r [filenname,mem_sect]     specifies a memory section to read from and a file
                             (txt/hex) to write to. mem_sect: RAM, INFO, MAIN,
                             BSL
 -w filenname                specifies a file (txt/hex) for device programming.

 -b                          unlocks BSL memory for writing
                             (use only with -w switch)
 -u                          unlocks InfoA memory for writing
                             (use only with -w switch)
 -e ERASE_ALL | ERASE_MAIN | specifies erase mode before programming.
    ERASE_SEGMENT            (use only with -w switch, default: ERASE_ALL but
                              ERASE_MAIN for the L092 devices)
 -v                          triggers verification after programming
                             (use only with -w switch)
 -z [exit_spec,...]          specifies state of device on exit
                             (view available 'exit_spec's using -x switch)
 -g                          switches log OFF (default: ON)

 -q                          triggers QUIET MODE (no system messages displayed)

 -d [breakpoint addresses]      specifies addresses for hardware breakpoints and
                             triggers RUN_TO_BREAKPOINT mode after initialization
 -t timeout_in_ms                       specifies the breakpoint timeout (in milliseconds)

 -s                          suppresses the FET firmware update prompt

If not all options are initialized the demo will use default options and return
a warning!
*******************************************************************************
Press any key to continue . . .

C:\ti\msp430\MSP-EXP430F5529_UE_1_31_00_00\bin\firmware>

Could it be that it requires USB 2.0 to work? My laptop only has 3.0.

If I had accidentally connected the switch to 5V, would it cause this? and would it be recoverable?

[wt200999]

Originally Posted by Jdkmotorhead

Could it be that it requires USB 2.0 to work? My laptop only has 3.0.

I would be surprised if this was the case, but it may be worth trying on another computer.

Originally Posted by Jdkmotorhead

If I had accidentally connected the switch to 5V, would it cause this? and would it be recoverable?

It would damage that particular IO pin for sure, but I am not sure if it would cause the who device to be damaged.

[Jdkmotorhead]

Originally Posted by wt200999

I would be surprised if this was the case, but it may be worth trying on another computer.

I tried it on my desktop with USB 2.0, but it still gives me the same error.

[Jdkmotorhead]

Is there anything else that you suggest I try?

[wt200999]

It really sounds like something was damaged.

Send an email to our support list with the shipping information for your team and we will send a replacement.