This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

  • Resolved

CCS/MSP-EXP430G2: Do I need an intermediate connection?

Prodigy 50 points

Replies: 9

Views: 536

Part Number: MSP-EXP430G2

Tool/software: Code Composer Studio


I'm a rookie in this realm of micro-controllers, but have some self taught programming experience and a Systems Engineering background, however; I'm stumped with my dilemma.

I've searched the Ti/E2E forums, found a lot of related topics but nothing that seems to resolve my problem. I'm getting a message of No USB FET was found.  I found a few related items and a couple that lead me to believe that maybe I don't have everything I need to move forward.  In order to debug, do I need another peripheral device to connect between my computer and the Launchpad?  Both of the links below reference debuggers such as the ez-FET.  Do I need to acquire one of these for the MSP-EXP430G2 or are they just a nice to have?

  • Hey Matthew,

    No, you don't need a seperate programmer for any of the launchpads.  These boards have the programmer/debugger built on.  It's the top half of the board labeled Emulation, seen here:

    I have a few more questions on how you're seeing this message:

    1. Which exact Launchpad do you have?  The MSP-EXP430G2 or the MSP-EXP430G2ET?    
    2. Is the board plugged into the PC and have a green Power LED that's on?  
    3. Are you using Code Composer to try and program the Launchpad, or something else?  





  • In reply to JD Crutchfield:

    Thanks for the response.

    I'm using the MSP-EXP430G2
    I'm connecting the board to the PC with the supplied USB cable and the Green light comes on when I connect it.
    I'm using Code Composer V6.1.

    A couple of other things I did was to look in device manager and the USB connection comes and goes as the device is plugged and unplugged, which seems to indicate it is doing something. Then if I keep the device manager open for a few moments a caution indicator (Yellow Triangle with !) pops up next to the device as if its intermittently losing connection.

    Before I tried my new code the device was running through the prepackaged Blinking Led and Temp Sensor programs.

    Thanks again for the help.
  • In reply to Matthew Silhavy:

    Do you have the jumpers (J3 on the PCB) properly connected?

  • In reply to Matthew Silhavy:

    Hey Matthew,

    Is the device not running through the out of the box code now?  

    Maybe the issue is your CCS project settings.  Where did you get this new project?  

    Let's try a TI provided project.  Import some demo code or another example for the G2 Launchpad can be found in resource explorer here:

    I just imported the out-of-the-box software to CCS Cloud and was able to flash from my browser.  Can you try that?  

    Let us know how that goes.  




  • In reply to Mike Tooma:

    That's a good point. I wasn't before, but then I noticed the startup guide has a configuration for HW UART on the J3. I have since arranged the jumpers in that configuration, but that did not seem to help.
  • In reply to JD Crutchfield:

    Okay, I plugged the Launchpad into my USB and the code I was attempting to build the other day was on there, fired up immediately, and seemed to be working fine with the Ultrasonic Sensor. That was odd.

    Then I tried this Out of the Box code and still had the No USB FET message. I took the G2553 chip out of the Launchpad and reinstalled it after about 45 seconds. Then I retried the Build Project and the CCS Cloud seemed like it was moving forward, I don't recall the exact message, but it was something to the extent of being successful and a reading of 88 MB of data used. Then, when I try to build again (without unplugging) I get the No USB message again. I tried this a few times and it seems like when I take the chip out for a few moments something is resetting and the build process works intermittently. Maybe I just need to do some further reading and find some more tutorials. What is the proper procedure to Code, Build, Debug, and Run. I assume I'm missing a critical step / order of events in there since there is an intermittent problem.
  • In reply to Matthew Silhavy:

    The fact that the USB is fading in and out suggests a flaky connection upstream. You might want to try a different USB cable. A bit of a long shot, but a quick experiment.

    To isolate it, you can try removing all the J3 jumpers. You (obviously) won't be able to talk to the MSP, but if your USB flakiness stops that points to something on the MCU side of the "dotted line".

    Do you have anything connected to the pins (J1/J2)?
  • In reply to Matthew Silhavy:

    Hey Matthew,

    Again, I agree with Bruce. There are 2 different main steps here. 1. connecting and recognizing the programmer and 2. Programmer connecting and flashing the target device.

    You don't need to be connected to the device to be able to talk to the programmer. If you are able to talk to just the programmer and try to flash the device, you'll see a "unable to connect to MSPxxxxx Target Device" type error message.

    Take Bruce's suggestion of removing all the jumpers to isolate the programmer side of the board and try a different USB cable and a different USB port on your computer. If you're using a USB hub or extender, also try connecting straight to the PC.

    If that doesn't work, my next guess is either a software/driver issue or something wrong with the launchpad. Both of those issues would be quite rare.

    Run these tests and let us know if that makes the connection to the programmer more stable.



  • In reply to Bruce McKenney47378:

    I took all of the Jumpers off and got the message:
    "Unable to connect to MSP430G2553.
    Please unplug and re-plug the USB connection and try again.
    TI MSP430 USB1/MSP430
    Error connecting to the target: Could not find device (or device not supported)"

    So, then I started adding the Jumpers until it connected. After adding the jumpers to VCC, TEST, and RST it appears the problem was resolved. Now when I run the debugger I get this:

    Flash/FRAM usage is 630 bytes. RAM usage is 88 bytes.

    I've since been able to make some changes and flash the device several times.

    Thanks for the help.

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.