CCS/MSP430FR2355: Error initializing emulator: MSP-FET430UIF is already in us

Oh, to be able to edit ones own post...

Additional:

Ruining fully updated Windows 10 PRO.   Fully updated CCS.

typo: "I have turned OFF the "feature" in windows were Windows can power down a USB port when it sleeps.

The more I look into this, it is clear that there is a stand along programmer "box" called the MSP-FET.  It is not clear why CCS wants to use this programmer for the Launchpad device. I can not find anywhere in a menu where you can enter your target configuration. Searching the net and TI forums I can't find a list of USB drivers to support launchpad vs. the MSP FET device.  Again, this used to work just fine with the launch pad.

I can not start a new project, because CCS can't connect to the launchpad- it tries to use the MSP-FET device. Again, how do you turn this off / specify you don't have one of these so you can work with Launch Pad devices?

Pete

Hi Pete,

In CCS, you should be able to create a new project regardless of any debugger connected.  If you create a new project(file-->new ccs project-->choose CCS Project), what is selected in "Connection"?  Is it TI MSP430 USB1?

If you use CCS cloud, are you able to connect to the board?   

https://dev.ti.com/

MSP-FET is a standalone debugger that we offer which offers more features than the eZ-FET that is included on launchpads.  FET is flash emulation tool. 

There is no "file-->New CCS Project", there is a "Project-->NewCCS Project..."

No "choose CCS Project" listed there.

If I select a target of MSP430FR2355, I see a connection of TI MSP430 US1 [Default]

If I am in the directory with the project, (i.e. "Active-Debug" displayed and I compile the code OK), and then go to:

Project-->Properties ,  under CCS GEneral I see Family as MSP430, Variant as MSP430FR2355 and the Connection as TI MSP430 USB1 [Default]

Should this not be sufficient? How do I get CCS to stop trying to use the MSP-FET and go back to using the LauchPad USB interface ?

Pete

Pete,

Sorry, meant to say "file-->new project-->select "CCS Project".

Yes, that should be sufficient and is the same configuration I have with my launchpad.  You may want to try doing a clean install of CCS.  Was this after a windows or CCS update that you started seeing the issue?

    I had to upgrade to Windows 10.  I also upgraded CSS.

  I take it the "do a clean install of CSS" means there is no easy way to get rid of CCS wanting to use/thinking it has  the MSP-FET device ?

 If so, add to the "bug reports" for CCS that it does not configure itself according to how the user has set things up.

 I'll nuke CCS, reload, and advise.

Pete

   Uninstall, re-installed CCS, reboot OS, same problem.

 I searched this forum for "CCS USB Drivers". Nothing found. So now we have a situation where the configuration indicates it should use the TI MSP430 USB1 [Default] but it does not. CCS is "stuck" thinking it should use a USB FET.

Is there a place where the various drivers for the USB drivers can be downloaded?

If not, then it would appear CCS is broken with no means to fix it.

Pete

... and FWIW, if I try to   "file-->new project-->select "CCS Project"

 I can't because CCS can not identify the board- same error about "MSP-FET430UIF is already in use".

So CSS is hopelessly stuck and can't even create a new project. So the PCBs with the MSP432P4111, CC1312 and CC2652 are stopped, and the LPSTK-CC1352, the SensorTag Develpment Kit, , the Multi-Standard Remote Control Development kit and the CC2540enmk kit were a wast of resources.  The power supply based on the TPS55288 (using the MSP430FR2355) is also dead in the water. Bad tools are why I dumped NXP, Cypress is starting to look pretty good now...

Please fix CCS so that it uses the connection shown in the "Project-->Properties" CCS General.

Pete

Anyone? Bueller? Bueller?

just knowing this problem has been identified and is being worked on would let me shuffle schedules around.

Pete

Pete,

I have asked the tools team and should have a response shortly.  Sorry for the inconvenience and we will work to get you a solution quickly.

Thank you for the reply, glad to hear you're working on it.

Pete

  Possible piece of out-of-band data, but that's the stuff bugs are made of:

I had to get a USB2ANY so I could use the TPS55288 EVM board. Don't know if using that could have changed some really low level setting common to both the USB2ANY Explorer _and_CCS. ?

Pete

Pete,

I am not immediately sure about the USB2ANY causing an issue, but I will look into this as well.  Please see the feedback below.

First: This is generic error message that is shown, if the USB connection is used by CCS or another program for the connected debug. It is the same for MSP-FET, eZ-FET and UIF.

Just to be more clear, the eZ-FET and MSP-FET are using more or less the same software components. Windows just detects them bye differently due to different PID and VID in their USB firmware.

Second: The eZ-FET and MSP-FET are CDC USB devices. You need no real USB driver. But you have to add the signed .inf files to the certificate storage of windows in order to support windows security. We have all kind of drivers and certificates available  (CDD, VCP,…) as standalone installer

https://www.ti.com/tool/MSPDS?DCMP=msp430&HQS=mspds.

Questions?

• Have you connected multiple debuggers to his PC via USB?

• What is the Launchpad revision you are using?

• What is the CCS version you are using?

• Is this windows a standard installation or is this in an IT controlled environment?

• Do you have a tool installed that scans for new enumerated USB ports and tries to communicate with them?

• Have you tried to identify the eZ-FET in CCS? The Red LED will be switched of if the FET was found. Also an indication dialog is show if you click Identify. This may give us a hint what is going on.

• Have you tried using USB2?

  I plugged in a CC1312 launch pad, it loaded and ran the "timerled" program no problem. I did have to update the firmware on the board, but the "click update" button worked no problem.

  I have ordered 2 more of the MSP-EXP430FE2355 launchpad boards, they will be here Friday. This will let us eliminate the possibility that the board I'm using was damaged.

Answers to your questions:

• Have you connected multiple debuggers to his PC via USB?

  • No. Only 1 debugger at a time.

• What is the Launchpad revision you are using?

  • The MSP-EXP430FR2355 is board revision Rev 1.4, PCB rev. A

• What is the CCS version you are using?

  • Version 10.1.0.00010

• Is this windows a standard installation or is this in an IT controlled environment?

  • Standard Windows 10, up to date, No controlled environment.

• Do you have a tool installed that scans for new enumerated USB ports and tries to communicate with them?

  • No.

• Have you tried to identify the eZ-FET in CCS? The Red LED will be switched of if the FET was found. Also an indication dialog is show if you click Identify. This may give us a hint what is going on.

  • If I try to "Identify..." in the properties under CCS General, I get the same error- "MSP-FET430UIF is already in use". Not sure what you mean by the "red LED", on the launch pad board the only LED that is on is the green LED02 on the USB side of the launch pad.

• Have you tried using USB2?

  • Same problems on both the USB2 and USB3 ports. I tried multiple cables too. With either USB port, the Device Manager sees both the Application and Debug interface COM ports.

  Another piece of info:  When I apply power to the FR2355 launch pad, the program that was there from 4 months ago is still in place and comes up and runs. I can see the debug pins changing on the MSO scope/analizer. So the uP is working correctly.

Pete

  I got the two new launch pads in today.  When I plugged one in, and tried to load it I got a "Must update the firmware" notice, I clicked on the "Update" button. Note that this process is also what happened with the CC1312.

  I gave it a _lot_ of time, far more than the CC1312 took. CCS then tried to load the program, but aborted and this message was in the Debug pannel:

  All further attempts to load give the same error message. The device identifies OK in the device manager:

  Now I have 2 launch pads that won't load. That that the error is different this time, implying that perhaps the firmware update failed, perhaps because it could not see the device just like on the 1st board ?

  The green and red LEDs are on up on the UBS side, and the red LED (LED1) is on on the MSP4320FR2355 side.

  So in addition to the "why can't CSS find this particular launch pad when it found the CC1312 launch pad" there is the question of how to un-brick a launch pad when the update to the USB side failed or was corrupted.

Pete

Part Number: MSP430FR2355

Tool/software: Code Composer Studio

  I connected a new out of the box MSP-EXP430FR2355 launchpad up and tried to load a program with CCS. A notice was printed that the launchpad needed to be updated, and a button to do the update was displayed. I pressed the button. After a bit CCS tried to load the program, failed, and the debug screen showed this message:

   All further attempts to load failed, and no more "Firmware updated" notices are printed. The red (LED101) and the green (LED102) are both on. I can find no description of what these LEDs mean in the launch pad data sheet. The red user led (LED1) is also on at the bottom of the board on the processor side.

  Is there a way to attempt or force the update of the USB side so I can load programs again?

Pete

  I did another un-install / install on CCS. No change. The original board still gets this error when trying to load a program:

The new board, which appears to have been bricked by a failed firmware update shows this when trying to load:

And from earlier posts, the CC1213 did both a successful firmware update and program load. Both boards show up in the device mangers as valid USB serial ports:

I've got one more new in the box MSP-EXP430FR2355, but am reluctant to do anything with it since I've already bricked one.

Pete

Hi Pete,

Thanks for the update.  This does seem like it could be a system dependent issue.  If possible, are you able to try one of the boards on another PC? 

I'm also working with the tools team to get some additional feedback based on your findings. 

Just the one PC. Use Apple for most other things, and FreeBSD for servers.

All this worked a few months ago. Updated to Windows 10 and updated CCS. Is there not a list of "things to remove" to put the machine back before CCS was ever loaded?

I started a separate thread on how to un-brick the launch pad and get the firmware to update.

Pete

I exited CCS and delete all the files in the workspace. Brought it back up again, it was like it was running for the 1st time. Imported the project, compiled it (it compiled all the librarys too). Exact same problem when I went to load:

MSP430: Error initializing emulator: MSP-FET430UIF is already in use

Pete

  this just keeps getting worse...

 I connected the new launch pad board that failed to do the firmware update back. I loaded the "out of the box experience" blinkLED into CCS and compiled it. It loaedd OK on that board, the program ran.

then I tried to go back and load the program I'm working on, and I got the 

error again. So the new board, where I got an error when trying to update the firmware, loads the blinkLED correctly but will not load another program?  My original board, which still has the program from 4 months ago on it which runs on power up, still give me the error

when I try to load it with anything.

I've spent most of the weekend reading the 40+ posts where people have had trouble getting ez-FET working or had other problems. This seems to be a reoccurring problem for the last 10 years. Is there not a list of DLL drivers to look for or remove and then install whatever the current drivers are? Is there not a way to convince either the launch pad or CCS that it should use the specified connection as set in the properties for the project? Is there not some way to force a firmware update on the Launch Pad when it fails ? Where does the information that the MSP-FET430UIF is already in use reside - in CCS or in the LaunchPad board ?

I can't get a screen shot of the Connection options, on loss of focus it closes up. But what I see are:

TI MSP430 USB1   TI MSP430 USB2    TI MSP430 USB3    and UARTConnection

Should there be an eZ-FET option in there?

I'm now 10 days of down time with circuit boards showing up soon. Is there any way to get a faster turn around on questions that one a day? I'm just having a hard time grasping how this exact same issue has been going on for 10 years and there is still no clear way to deal with it.

There is no clear description of what the overall mechanism is. When the PC finds the "MSP Debug Interface" on a com port, does the driver/software in CCS just use the serial port connection to talk to the Launch Pad firmware? This would seem to be a logical way to do things and allow for a high level of platform independence.

I've bet everything on using 4 TI processors, 3 switching power supply chips, the TRF7970 RF ID chip, and I2C sensors for light (OPT3001), temperature/humidity (HDC1080), temperature (TMP116 and TMP117), temperature switch (TMP708), current sense (INA180),audio amplifier (TPA2005) plus level converters, LDO lin regulators, voltage reference (REF3025),voltage converter (LM266x) and a few others. I still have my 1976 TTL Data Book, and have used just about every logic family ever since. I used your FPGAs (Altera 2nd source). If this is going to go on for another 2-3 weeks, I might as well toss out the last 5 months of work and start again. You have created an entire ecosystem of components across a broad spectrum, but can't get the IDE that works will all your processors to work over a serial port. I know these things can take time, I just don't know where the cut and run point is.

Tools breaking mid project is a massive failure. Please focus on this now not only for me, but for all those other users who have had a similar problem over the last decade with your IDE or tools.To quote a variant of the Tennyson poem, "For want of a serial port the company was lost."

Pete

Figured out the problem with why the BlinkLed would load, but not my new code for the power supply I'm working on. The error I got was:

  It turns out that if you copy in an existing project, there is a check box burried in the preferances that specifies if CCS should connect to the target before you debug. Not sure why you would not want to connect.... checking that box got things where I can download my software on the lauch pad. I have no idea why the "update" of the firmeware claimed to fail, but it is working.

This still leaves me with the other launch pad and it's problem:

And there is still the issue of how to force update a launch pad when it's bricked.

At any rate, here is the screen and the box to check, it might somehow get unchecked if you copy in a project,

Pete

Hello TI

Any progress on the "MSP-FET430UIF is already in use" problem when trying to download a program with CCS ?

I'm OK on my development, but, would really like to get the Launch Pad board back, and will need it to program the part on the new PCB when that comes in.

Pete