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.

MSP430FR2355: MSP-FET430UIF is already in use - still crazy after all these years...

Part Number: MSP430FR2355
Other Parts Discussed in Thread: MSP-FET

Ever since I started working with CCS 5 years ago, there has been a problem that keeps repeating. I get this error when trying to connect to and program a uP:.

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

I have several posts on this form about this, as do 30+ other people over the last 10 years.

To save time here, some information:

Every board I've worked on so far is a MSP430 family.

Rebooting the PC does not help. Power cycling the PC does not help.

I can always see the MSPFET module in the device manager.

CCS revision is Version: 12.6.0.00008

Just a few days ago I was working on another board, no problems. The board I'm working on now was for a software change, the board is known working and has had software loaded into it before.

What is particularly disturbing is that in 10 years, this error message has stayed the same. Imagine how useful it would be if in addition to the "already in use" the error message said _what_ device does it think is using the MSPFET. Think of the hours of time wasted by developers because CCS can't provide more detailed error messages on the process of connecting to a PCB such as:

1) Unable to find debugger on a USB com port

2) Found debugger, but can't talk to it

3) CCS thinks that you are still debugging another project, and as such things the MSPFET is already in use (_and_ told you which project)

4) Found debugger, can talk to it, but it can't talk to any processor

5) Found debugger, can talk to it, but the processor is not the one specified in the project profile.

Such clarity in debug statements would be wonderful. The current error is as useless as a poor compiler that just says "syntax error" when there clearly some very specific issue that was encountered, it's just that the compiler writer was lazy and did not provide a more detailed error message. I again state that everything was working fine just a few days ago on another board.

In a further attempt to avoid several rounds of "is it plugged in", let me pre-emptively ask these questions:

1) Does CCS have a concept of which project has the MSPFET / which project "owns" the MSPFET

2) If so, how do you clear this ownership ?

3) The error reads "...is already in use". How can a developer determine _which_ project/software/processor/resources/whatever claims to be using the MSFET ?

4) What procedure should be used when you are done working on a given PCB with a given processor to avoid the "....already in use" error ?

5) (this is somewhat rhetorical) Any explanation as to how this error has not been fixed in over 10 years ?

 - pete

  • Hi Pete,

    I understand your disappointment about this issue. This looks like a CCS issue to me. I am going to put this thread into CCS org for help. 

    Best regards,

    Cash Hao

  • A CCS related question: I was looking around in the ti directory, and saw 3 shortcuts to CCS. I also saw directories for CCS1000 and CCS1010. Each of those is about 9 GB. All I've ever done is update as new versions come up. Is it normal to leave old versions lying around, and can I safely delete these old directories? The entire ti directory is now 23 GB big.

    I've removed the older shortcuts, so now I just have the 12.6.0 one.

    Is there a reason for keeping these old directories around when you have CCS update itself? Will old projects still load up with the latest version? FWIW, all the projects are saved in another drive partition, no designs live in C:\    When you have CCS update itself, is it supposed to remove old versions ?

    thanks for passing the question on. Here's hoping this can get figured out.

     - pete

  • HI,

    The CCS team replied that this error "MSP430: Error initializing emulator: MSP-FET430UIF is already in use" appears to be coming from the MSP430 dll which is owned by the MSP430 team. So, it is back to MSP team now. I would suggest you to open a new thread to ask about your CCS related question. 

    And for the MSP430 error, we need to check with our software team about the MSP430 dll configuration. Thank you for understanding. 

    Best regards,

    Cash Hao

  •   Any attempt to create a new question in the CCS group falls back to MSP Low-Power forum because the for requires a part number, which them kicks me back.  So I have no idea how to "Open a new thread to ask about your CCS related question". From what I can tell, there is no way to post to Tools->CCS.

     - pete

  • Hi Pete,

    You can post it under MSP, and then send your post link here. I can assign it to CCS team for your CCS related question. 

    Best regards,

    Cash Hao

  •    I un-installed CCS (well, as far as it got before the program printed "Critical Error" and aborted).

    remove all files in the ti directory, then installed the latest version of CCS

    I still get the:

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

    error. So for 3 weeks I've been dead in the water unable to program any boards.

    There is nothing more I can say that even the most casual observer would not conclude. So disappointed in TI.

  • I just read a post where someone had this same issue, the resolution was:

    Figured it out, running the ~/ti/ccs/install_scripts/install_drivers worked

    I don't have this path in my fresh install of CCS. In the CCS directory, there is no 'install_scirpts' directory.

    Shouldn't all installs have the same base code and tools ?

  • I have been re-searching post. I found a post I made 4 years ago with the same problem. Earliest post by anyone was about 15 years ago. Most of the post are not helpful because the various menus have changed. Surely someone in TI land understands how the load process works ?

  • Hi,

    I am really sorry for the poor experience using CCS environment. 

    From your post, it inspires me that you can remove all the JTAG debugger device drivers first and then reinstall the CCS should help. 

    Here is the processer: 

    In Windows, if the complete removal of JTAG debugger device drivers is necessary, you must follow a more thorough procedure:

    1. Check this typical procedure to remove device drivers using the Device Manager, but keep in mind you will have to enable the option Show hidden devices under the menu View to display all JTAG debuggers ever connected to your PC.
    2. With this enabled, in the directory tree look for the branches that start with Blackhawk, SD USB Based Debug Tools, Stellaris Device Firmware Upgrade, Stellaris In-Circuit Debug Interface, Texas Instruments Emulators and Texas Instruments Debug Probes.
    3. For every item inside these branches, right-click and select Uninstall. Also, check the box near Delete the driver software for this device.
    4. Also, when expanding the branch Ports, check for any relevant entries that mention one or more TI targets such as CC3200LP Dual Port, MSP Application UART1, XDS, Stellaris, etc. Repeat step 3 above for each entry.
    5. Similar thing with the branch Universal Serial Bus Controllers.

    You can find more related descriptions in chapter  9.1.7. Clearing Out An Existing Installation. https://software-dl.ti.com/ccs/esd/documents/users_guide/ccs_troubleshooting.html

    Best regards,

    Cash Hao

  •    I did as you advised, and found nothing. However your last item number 5 was a win.  I went in and deleted the drivers for the MSPFET, and those USB freed up. I then un-installed and re-installed CCS. I brought up the project I was trying to load, and the Device Manager displayed only the two com ports 1 & 2 (which I had disabled), I compiled the project, and when I went to load the two MSP interfaces popped up in the Device Manger.

      And then everything loaded normally with no errors.

       So this has me thinking that the drivers for the MSP devices are not just simple "special serial ports". They must clearly have a higher level interface into CCS that has state information associated with them. I'm guessing that the sequencing of disconnecting the MSP-FET from the USB bus or shutting down CCS without terminating the debug session end up leaving the drivers in a state where they believe that the MSP-FET is in use, and there is no recourse from either CCS or the end users to "reset" those drivers.

       This would also explain how this bug has been around for 15 years, and how various attempts to fix things such as reinstalling the world, rebooting the PC, turning off ports and the like eventually work. This would be good to point out to the CCS team. A feature such as when you get the MSP-FET430UIF is already in use that lets you "clear" or "detach" or "reset" the MSP_FET would be really handy.

      Thank you for the help. I'll be changing over to another PCB in a few days, and will be careful to note the sequencing for changing projects, disconnecting the MSP-FET and bringing CCS up and down. When that works, I'll mark this as resolved and hope all this helps others.

     - pete

      

  • Hi,

    Good to know this helps! Sorry again for the inconvenience. 

    Best regards,

    Cash Hao

**Attention** This is a public forum