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.

MSP-FET 430UIF Could not set device Vcc

I have been building in CCS 5.4.0.00091 and running successefuly. Twice now though we have had a MSP-FET430UIF suddenly fail to sense the boards VCC pin. When we try to start debugging we get the error message: "Could not set device Vcc" but if we switch just the FET it runs just fine. I have tried to reinstall the device driver, changing the USB cable, and verified all the pin connections. We can switch to a different FET but it seems something is going wrong to disable them.

  • What are JTAG connector pin 2 and 4 connected to? What powers the target?

  • The board is powered from a 3V battery. JTAG pin 2 is connected to nothing (unstuffed resistor) and pin 4 is connected VCC with a 0.1uF. 

    The boards were working with the FET and suddenly stopped. Replacing nothing  but the FET (even the cable stayed put) it was able to connect again.

  • Joe Baird1 said:
    ...  Replacing nothing  but the FET (even the cable stayed put) it was able to connect again.

    Do you have several MSP-FET430UIF units? Do you mean when you replace one of them with another one then it works? If that is the case, then one of the units is bad or not reliable.

  • We have a couple of FET units in house for each of the developers. The one I had been using for over a week stopped working today mid session and I grabbed a unit from another co-worker which works. 

  • Well, your FET unit needs to be replaced or repaired. This happens and it is not your fault.

  • OK another mystery added to this issue. After my third FET failed this morning, my coworker took it and ran it on his machine and it worked fine. I took it back and it now works again. We are both using CCS 5.4.0.00091 on Windows 7. I've tried doing the following to fix the issue:

    Replace the USB cable, and USB port

    Delete the driver and reinstall it

    Restart the computer

  • I'd like to add a log to your fire. I have 3 FET's with me, 1 is a week old and the other 2 are more than a year. All have been working fine until today and I recently upgraded from CCS 5.2 to 5.4 I am now dead in the water all 3 of my units passed away today cables and all. I don't believe that it just happens. I have been doing this for years and have had all of the annoying bugs but this one I have not been able to get around. By the way all 3 units worked yesterday on the same boards.

  • Hello....

    I have similar problem, I have a couple of MSPFET430UIF, working with IAR 5.52.1 and CCS 5.4.0.00091 which were working fine until yesterday, now when I try to download my project code I get back the message "Error initializing emulator:Could not set device Vcc2 in both debug platforms.....

    Any idea of what is happening?

  • Jose Carmelo Rangel Breña said:
    now when I try to download my project code I get back the message "Error initializing emulator:Could not set device Vcc2 in both debug platforms.....

    Are you using MSP430.dll v3.3.0.6?

    The New Findings section of MSP Debug Stack states that is a known issue with v3.3.0.6 and the work-around is "Unplug/reconnect debug interface and launch debug session again."

    The release notes for v3.3.1.3 suggest that bug fixes have been made for the "Can't set Vcc" error - something to do with the COM port blocked by the OS.

  • Hi Chester, yes I'm working with the MSP430.dll v3.3.0.6, but I tried to do many times the action you say, but it didn't work....

    This morning I downloaded the MSP flas programmer from http://processors.wiki.ti.com/index.php/MSP430_Flasher_-_Command_Line_Programmer then I tried to download my code using this tool and first askme to reflash the MSP430FETUIF with another firmware version and it work correctly afther this action.

    then I open the CCS and the emulation tool work normally.

    I hope this procedure can help to anyother who has similar problems.

    thank you

**Attention** This is a public forum