• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 54 subscribers
  • Views 905 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CCS/MSP430G2553: CCS V7 in SIMPLE mode with Launchpad: debug looks for MSP-FET430UIF

John Linsley
Intellectual 510 points
Part Number: MSP430G2553


Tool/software: Code Composer Studio

I have a project using a Launchpad and CCS V7 in simple mode. Initially I was able to dubug it as expected, several times. Then, after a another small edit, I hit the debug button as ususal but the "Configuring Debugger" pane popped up an error:

"Error initializing emulator:
Could not find MSP-FET430UIF on specified COM port"

I do not have a FET attached and have never used one on this project. I did test another project, once, with the FET shortly after installing V7 to make sure it worked OK but have not used it since.

I have gone through the steps in Troubleshooting CCSv7, deleting launch config etc but no joy. The only thing that seems to work is setting up a new workspace and importing the project into it but, after a few launches, the debug process insists on looking for the FET again. I think that once upon a time I was able to fix this by going to the getting started tab and making sure that simple mode was selected (even though the top rightof CCS shows a red ball with "CCS Simple" next to it) but that's not working now.

How can I get around this "feature" and use the Launchpad without setting up a new workspace every few launches?

  • 0
    Intellectual 510 points
    Hmm! I just installed the latest updates and the need for the FET has disappeared. I wonder if it will last?
  • 0 in reply to John Linsley
    Intellectual 510 points
    Oh well, 6 launches later it's looking for the FET again. All I'm doing in between is minor edits of a function, I'm not changing any project options or anything else.
  • 0 in reply to John Linsley
    TI__Guru**** 162875 points

    John,

    The debug connection type is the same for both the standalone MSPFET-430UIF and the one built onto the LaunchPad.  So here the issue is that CCS is not able to communicate with the LaunchPad.

    I will pull someone else in to help.  For now if creating a new workspace really works around the problem then something else you could try that is less of a pain is to delete the debug launch.

    Click the down arrow beside the bug button and select Debug Configurations...

    Select your project in the list on the left and then click the delete button.

    That will trigger the debug information to get re-generated the next time you launch the debugger.

    I am quite surprised that creating a new workspace fixes the issue as the error.  The debugger built onto the LaunchPad is an older model.   One thing I have found with some of our older ones is that they work better when plugged into a USB2 port vs USB3.

    Regards,

    John

  • 0 in reply to JohnS
    Intellectual 510 points
    Hi John,

    Thank you for replying.

    I already tried deleting the Debug Configuration (apologies for my slack terminology originally) to no effect. Armed with the knowledge that the standalone MSPFET-430UIF and the one built onto the LaunchPad are the same I'll try unplugging the LaunchPad and reconnecting next time, just to see what happens.

    The last time it happened (a couple of hours ago) I closed and reopened CCS and after that it has worked about 10 times or so; previously that has not been successful - even shutting down the computer, having a sleep and restarting has failed in the past. The reason for the frequent edits may end up as another thread;-s

    This laptop only has USB3 so I won't be trying a USB2 port, sorry.

    Best regards, John