• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 79 subscribers
  • Views 3379 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.

Recent CCS v6 problem "No USB FET was found"

Craig Hackerd
Prodigy 70 points
Other Parts Discussed in Thread: MSP430G2553

I had been using CCS v6.1.0 without any problems. I am using a MSP430G2553 on Launchpad MSP-EXP430G2. Now when I try to download new code, I get "TI MSP430 USB1_0/MSP430" "No USB FET was found". This started after some automatic updates of CCS. I have seen on other threads where the G2 needs a firmware upgrade. When I run "LaunchPadFirmwareUpdater2.0" it stops with "Error 52" during the erase emulator firmware. I have all the same problems on both G2 launchpads, with multiple chips, including 2 fresh out of the tube, on multiple USB ports, on multiple computers.

I have performed an update to the latest version, with no improvement. I have done a clean install of CCS v6.1.2 in a different directory with no improvement. The clean install had a slightly different error "Could not find MSP-FET430UIF on specified COM port". I can see that the "Texas Instruments MSP-FET430UIF" has been installed in the "Devices and Printers" folder. In the "Device Manager" I can see "USB Composite Device", "MSP430 Application UART (COM4)", "USB Input Device", "HID-compliant vendor-defined device" all loaded with no errors indicated. All with USB\VID_0451&PID_F432&REV_0105. I have also tried deleting the drivers, and reloading them.

Nothing is working. Can anyone help?

Thanks,

Craig

  • 0
    Prodigy 70 points

    Finally made some progress, could not find drivers for Win 10 on TI site, but did find them here
    . These were good for win 7,8, &10.

    Was able to install CCS v6.1.2 then install the drivers. Can now download to G2 launchpad. Need to use either "DPInst.exe" or "DPInst64.exe" and execute them from inside the downloaded driver directory. They can be found in the MSP430Drivers-1_00_00_01-windows-installer.exe file at this location . This solved my problem, and maybe someone else will be helped by this post.

  • 0 in reply to Craig Hackerd
    TI__Guru**** 217467 points
    Thank you for providing the solution to your problem! This will definitely be helpful for other community members with similar issues who are searching the E2E forum for a solution.

    Regards,
    Ryan
  • 0 in reply to Craig Hackerd
    Prodigy 70 points
    It happened again!
    During a debug session with CCS 6.1.2, suddenly the device was no longer recognized and the FET could not be found. I could reload the driver (while CCS still running), and things would work for a short period, then fail again. Restarting CCS, unplugging/re-plugging the launchpad, and rebooting the computer did not change the failing behavior. When unplugging/re-plugging the launchpad, windows would say the device was unknown, until the driver was re-installed. Only when I modified the code in the MSP430G2553 so that timer0 was running from MSCLK again, instead of from ACLK (VSOCLK) did the problem stop. There is some kind of weird interaction going on between CCS and windows 10 that is corrupting/deleting the device driver. Don't know why changing Timer0 clock from MSCLK to VSOCLK started causing the problem, or why changing back to MSCLK caused the problem to go away. Have not had any problems through multiple debugging sessions since changing timer0 back to MSCLK. Very weird.
  • 0 in reply to Craig Hackerd
    TI__Guru**** 217467 points
    Craig,

    Can you generate a demo code file that recreates the issue and send it to me so that I can try to reproduce this on my end?

    Thanks,
    Ryan
  • 0 in reply to Ryan Brown1
    Prodigy 70 points

    Ryan,

    Before reading your reply, I had already completed the code, and torn down the setup I was using. I will be out of town for a couple of days, but will try to regenerate the problem when I get back.

    Craig

  • 0 in reply to Ryan Brown1
    Prodigy 70 points
    Ryan,
    Could not duplicate the failure mode. Had not saved problem code in version control. Went to prior version and tried to duplicate steps from memory but no luck. If it happens again, I will try upload demo code. For now, everything is working fine.
    Craig

**Attention** This is a public forum