CC3200-LAUNCHXL: CC3200 can neither be debugged nor flashed. Not seen in Device Manager.

Hi Taras,

Are you getting any specific error codes when you try to debug?

1. Try testing with another USB cable. A failing cable can cause unusual behavior.
2. Format the device with Uniflash v3 and then update the service pack to the most recent (1.0.1.11-2.9.0.0).
3. Try the suggestions here: software-dl.ti.com/.../ccsv7_debugging_jtag_connectivity_issues.html
4. And here: software-dl.ti.com/.../ccsv7_debugging_jtag_connectivity_issues.html
5. If all else fails, contact the TI store for a replacement LaunchPad.

Best regards,
Sarah

p { margin-bottom: 0.1in; line-height: 120%; }

Hi Sarah,

Thank you for reply.

I cannot see specific error code – just ”Error connecting target”. Though I’ll look for it.

1. Cable as a reason of the problem should be excluded since I checked with several cables.

2. The problem is that I cannot flash CC3200 just because I cannot establish connection with it.

3, 4. Links are really useful and comprehensive but I they are dedicated to external debugger (XDS) while I’m using built-in CC3200 debugger.

5. I’m trying to do my best to avoid this :). But probably will have to use this option provided other measures fail…

I would like also to narrow the issue and provide info about my last findings.

In my first post I wrote that the problem was gradually growing and eventually I was not able to connect CC3200 at all. After that I continued experiments and surprisingly after a number of attempts I was able to connect a couple of times and then again no connection. So, currently picture looks as follows. Most attempts to connect are unsuccessful. But in these rare cases (appr. 1 to 50) when I do able to connect everything works completely ok (both debugging and flashing). In those cases I can read FTDI module info (including VID and PID) using FT_PROG utility.

When connection is NOT established then:

• In Device Manager I see “Unknown device”

• FT_PROG scan finds no devices

• USB sniffer is silent during around 25 (?!) seconds after usb stick insertion and then says that one packet came from the device with VID and PID equal 0. The following another two messages are “Suprising removal of the device” and “Device disconnected”.

When connection is established then:

• In Device Manager I see “CC3200 UART port B” and “CC3200 JTAG” in USB tree and “CC3200 Dual COM port” in Ports tree.

• FT_PROG scan finds device and shows correct VID and PID.

• USB sniffer shows packets exchange expected for connection establishing. VID and PID are correct.

I cannot figure out what makes up a difference between successful and unsuccessful cases.

So, currently I think this is HW issue. However, FTDI module looks healthy because otherwise I would not be able to connect CC3200 at all but I can, though very rarely. What is left is usb jack itself and usb jack to FTDi circuitry problems…

I would highly appreciate any further advice.

Thank you in advance.

Taras.

Hi all,

Last update.

The third scenario added. CC3200LP Dual Port appears in Device Manager but it cannot be launched due to error code 10. FT_PROG scan in this case

is able to detect FTDI unit but cannot identify its type. Functionally this third scenario is identical to "Unknown device" case - CC3200 is not connected eventually.

I've also carried out a couple of  tests with a scope. I've noticed that just after physical connection the data goes in both direction (D+ and D- pins). But after around 15  

seconds data flow suddenly stops (have not noticed on which pin, unfortunately). As a result, connection is not established.

Though still hoping to make this device working properly, at the same time I'm mentally preparing myself to the need of device replacement. Could anybody please 

suggest me what is procedure to follow in this case?

Thanks in advance.

Taras.

Hi Sarah,

Thank you for reply.

I've bought this LaunchPad in February this year. As far as I understand, according to Returns and Refunds policy, there is 3 years warranty for such devices. So, it looks like I'll try to get replacement.

Best regards,

Taras.