CC3200 Error connecting to the target (Windows 10 only)

TFont

Other Parts Discussed in Thread: CC3200

My CC3200 launchpad always gives a "Error connecting to the target" whenever I have a terminal connected prior to launching the debug. If I disconnect the terminal, the debug session will properly connect/download and I can then reconnect and use the terminal once downloaded.

This seems to be an issue with Windows 10 only. I have a nearly identical CC6 installation on a Windows 7 machine and the same launchpad will connect for debug with the terminal active.

So I can work around it by disconnecting/reconnecting the terminal each debug session but this is very annoying. Has anybody experienced this or is there something I could try to fix this?

over 9 years ago

0 Hnz over 9 years ago

Guru 39650 points

Hi,

I think reason of your issue is different. Probably you have at Windows 10 latest SDK (1.2.0) and at Windows 7 previous version. Please see this: e2e.ti.com/.../499123

Jan

0 Markel Robregado over 9 years ago

Guru 86755 points

Hi TFont,

I don't have Windows 10, but I experience the same with my Windows 7. Here below is what I do.

1. At your CCS Project press debug button. After it goes to debug mode, open your Terminal like Tera Term and set the correct Tera Term settings. After that you can do CCS Debug Run or Debug Step. However if you open the Tera Term before pressing CCS debug button, you will get an error.

- kel

0 Hnz over 9 years ago in reply to Markel Robregado

Guru 39650 points

HI Markel,

This is weird. I debug my CC3200 project by CSS and haven't issue which you described. Always I use terminal in my projects, and I did not need disconnect terminal before debug. I tried different terminal software, and all worked. I debug my projects on Windows 8.1/32bit and Windows 10/64bit. Maybe issue is related on FTDI driver version. I use driver version 13.11.35.0 (2014.8.15).

Jan

0 Markel Robregado over 9 years ago in reply to Hnz

Guru 86755 points

Hi Hnz,

Yeah its weird. I will try the latest FTDI version and see how it does.

- kel

0 TFont over 9 years ago in reply to Hnz

Intellectual 270 points

In my case, I cannot load a debug session at all unless the terminal/console is disconnected.

0 TFont over 9 years ago in reply to Hnz

Intellectual 270 points

Jan,

It must be something else. I'm using the same FTDI version as you (13.11.35.0). Could it be something in the CC3200.ccxml target configuration? Would you be willing to share yours for testing/comparison?

0 Hnz over 9 years ago in reply to TFont

Guru 39650 points

Hi,

I don't think that CC3200.ccxml is that trick. I use default CC3200.ccxml from SDK. Also I check settings of JTAG and COM port in device manager. I found nothing obvious.

By the way. For debug I use JTAG not SWD. SWD is not reliable on my machines.

Jan

0 Alon Gilboa over 9 years ago in reply to Hnz

Prodigy 100 points

I have the exact same problem. did you find solution already?

0 TFont over 9 years ago in reply to Alon Gilboa

Intellectual 270 points

No, still using the workaround in my original post.

0 Alon Gilboa over 9 years ago in reply to TFont

Prodigy 100 points

i think i have solution by using different com ports on same usb. one for jtag and other for uart, where uart use vcp driver. but im not sure about exact way to do it. i will post if successful

0 Benjamin Moore over 9 years ago in reply to Alon Gilboa

TI__Mastermind 30810 points

You can also consider using the Terminal included as part of CCS (View->Other...->Terminal). I don't believe you run into the issue when constantly connected via that terminal.

Best Regards,
Ben Moore

0 Alon Gilboa over 9 years ago in reply to Benjamin Moore

Prodigy 100 points

Hi Ben

Thank you for your suggestion, but I get the exact same problem

the basic problem is that windows OS, after one program already use the com port (e.g. COM6), does not allow the second program to use the same COM port.

So if the first to use the com port is the terminal program, the debugger fails, and if the debugger is the first to use the com port, then the terminal fails.

it happened to me with many terminals I tried, and it also happened now with the internal terminal of the IDE

I will keep trying other solutions

Alon

0 Hnz over 9 years ago in reply to Alon Gilboa

Guru 39650 points

Hi Alon,

I really not understand this behaviour. Now I have two Win 10 machines (Home x64 and Pro x32) and both works in this case properly and I don't need disconnect external terminal in case of using JTAG from CCS. As terminal I use this software (sites.google.com/.../), but this is not important because it works with all terminals.

Can you share screenshot from device manager, my looks this...

And I use default CC3200.ccxml Target configuration from SDK:

Jan

0 Alon Gilboa over 9 years ago in reply to Hnz

Prodigy 100 points

Hi Jan

I still need to learn how to do these screen shots... I tried but failed.
my device-manager settings are exactly same as yours, even the com port number is 6.
I also use the same default target configuration file of CC3200.ccxml
since its the first time I use code composer and the first time I use this kind of debugger, I use the ready-made example wlan_station project.
I used the getting started guide and followed all the instructions, so there is not even one line of code\configuration which I did myself.
I use windows 10 professional x64
I suspect now that the problem is in the process of "connection to Target" performed by the debugger.
maybe a too-short timeout somewhere, or s specific settings of the parameters debug->Target-> Auto Run and Launch or in Program/Memory Load
could you share your settings with me?
also the example I use include few projects, such as simpleLink, os_lib, ti_rtos_config - maybe one of them has wrong load/start parameter?

alon

0 Hnz over 9 years ago in reply to Alon Gilboa

Guru 39650 points

Hi Alon,

I have no idea what can be wrong...

If you need some other settings, let me know.

Jan

0 Alon Gilboa over 9 years ago in reply to Hnz

Prodigy 100 points

thanx!!!! i will check n let you know

0 Alon Gilboa over 9 years ago in reply to Alon Gilboa

Prodigy 100 points

same as my settings.
i will try reinstall drivers

0 Hnz over 9 years ago in reply to Alon Gilboa

Guru 39650 points

Hi,

I have also one idea what can be different, but it only idea without any confirmation. It can be different settings in FTDI chip. Settings from FTDI can be read/changed by FT_PROG utility (www.ftdichip.com/.../Utilities.htm. But use FT_PROG carefully...

Jan

0 Alon Gilboa over 9 years ago in reply to Hnz

Prodigy 100 points

hi Jan

After re-installation of drivers, and few more tries, I give up

I tried to talk with other users of CCS on windows 10, and they all have this problem!

Thanx to everyone who tried to help, I will have to try live with this bug.

I will be happy to hear solution if someone finds in the future

alon

0 Alon Gilboa over 9 years ago in reply to Alon Gilboa

Prodigy 100 points

Hi Jan

The problem is solved in IAR workbench !
I use there freertos instead of TI RTOS, and simplelink is in OS_debug mode, and I work with terminal always connected, and debug works fine!

still same problem with CCS

I believe now that the problem is in TI RTOS/ configuration settings

Alon G

Wi-Fi

Wi-Fi forum

CC3200 Error connecting to the target (Windows 10 only)