MSP430 LaunchPad can't flash firmware

[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.