Unknown device with launchpad G2-G2553

"update firmware" often destroys the firmware instead. The easiest solution is to get another Launchpad and remember to say "no" whenever you are asked to "update firmware".

Luckily I do have a few spare Launchpads. I tried a second one and the result is the same. I normally use IAR and assembler. I could be doing something very silly with CCS ver. 5. I have just taken the Launchpad out of the box and connected to the USB cable. I am using XP and it is recognised in the Contol Panel.

Any futher thoughts?

OCY

I thought there was nothing wrong with the Launchpad modules or I had 4 faulty ones. I decided to have a play and after a while found that if I altered the default port (USB1) to USB2 that the device was recognised. I was able to load and run the "blink led" program. As I said I normally run assembler under IAR. I have also not used the Launchpad before and usually use a FET UIF for programming and debugging. Is there a document aroud that describes the Launchpad with a USB programmer/debugger?

Thanks

Peter

You said earlier that: “I have got a Launchpad G2 with a MSP430G2553 on board. I have downloaded CCSv5 and was try to run the program Blink the LED. As I was doing this I was asked to update the firmware which I did.” I knew that often kills the Launchpad.

I too, normally use IAR Kickstart and write code in Assembly. I know very little about CCS.

Thanks OCY