• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 41 subscribers
  • Views 383 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.

CC3200-LAUNCHXL: Launchpad is not recognized by PC

Allan Caniz
Prodigy 10 points
Part Number: CC3200-LAUNCHXL
Other Parts Discussed in Thread: UNIFLASH,

Hello,

I recently purchased a CC3200-LAUNCHXL. As I was connecting it to my computer, the Launchpad was not able to be detected by Code Composer Studio. At first, Device Manager was able to detect the device providing COM 11. The COM port number was used by Uniflash to try to establish a connection and update the service pack. Unfortunately, Uniflash was unable to establish a connection returning an error code (error code 3) even after trying multiple times and resetting the device. I started looking for a solution and found the following link: https://processors.wiki.ti.com/index.php/CC3100_&_CC3200_FTDI_Flashing. After the XML file was updated, Device Manager was unable to detect the device any longer as shown in picture below:

I, then, tried to open FT Prog and scanned for the FTDI FT2232D of the CC3200-LAUNCHXL, but the program could no longer detect the device as shown in the picture below:

The Launchpad has always been powered on and the LEDs D1, D5, and D6 have always been on. I have tried two other USB cables and different USB ports with no success. 

  • 0
    TI__Guru**** 171264 points

    Hi,

    Taking from your description, I suspect the FT_prog utility somehow damaged the device, rendering it unrecognizable by its own device drivers. That or a hardware problem is influencing the ability for the FTDI device to be properly acknowledged - the changes that this is what is happening are smaller, given the board was properly acknowledged before. 

    For the FT_Prog utilty to properly acknowledge the board and attempt to recover the device, its OS drivers must be able to "see" the device. Given that Control Panel is returning 'Unknown device", I would definitely test and verify the connections between the host and the board. At this point anything goes: different USB ports, USB2.0 or 3.0 ports, USB cables, bad or intermittent contact on the micro USB connector on the board, etc. 

    Also, make sure you are not in a Virtual Machine environment (VMware, Virtualbox, Parallels), given these low-level interactions are much less reliable across a VM. 

    Hope this helps,

    Rafael