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.

Cant connect to CC3200 via JTAG (CCS 6.0)

Other Parts Discussed in Thread: CC3200, CC3200SDK

Hi,

I just received a CC3200 Launch Pad, after playing around with the OOB demos I tried to connect to the CC3200 via JTAG, but this doesn't work CCS throws always an error:

The FTDI driver seems to be installed correctly, here is a screenshot from the device manager:

All jumpers on the board are in default position.

I got another issue with the board which might be related: After my first steps with the board I added my AP (FRITZ!Box) in the HTML setup page (add Profile), since then I'm unable to connect to the board. It doesn't show up in the AP point list of my PC and it doesn't connect to my AP (FRITZ!Box).

So maybe I messed up the demo app with adding my AP profile? How can I default the board and successfully connect to the CC3200?

Thanks,

Christian

  • Hi Christian,

    Please ensure the jumpers settings are as shown in the Quick Start Guide to get the CC3200 back in AP mode.

    You can reflash the OOB demo back by using OOB demo html files part of the SDK.

    For CCS env setup, please refer to Getting Started Guide CCS section.

    Regards,
    Geet

  • Hi Geet,

    I checked the jumper settings, they are as shown in the Quick Start Guide: http://processors.wiki.ti.com/index.php/CC32xx_Quick_Start_Guide

    However the LaunchPad still seems to be dead, as the red LED doesn't blink at all.

    I will see if one of my colleges has a LP and cross check with that.

    Best Regards,
    Christian

  • I am having the exact same problem.

    Cannot connect to the board via CCS6 / Uniflasher

    Is there a known issue?

    Is there some workaround to connect to the board and bring it back to life?

  • I am having the exact same problem.

    I checked all jumper and upgrade ccs6, i tryed 3 different computer. But neither flaser nor ccs worked.

    how can i programe cc3200?

    Regards

  • Hi Guys,

    Make sure you have a jumper on SOP2 when debugging and when flashing.

    Please see the Getting Started Guide here: http://www.ti.com/cc3200project0guide

    -Aaron

  • Folks

    I am very new to TI ARM having spent the last 20 years on PICs, although I do have a few months working with CCS from about eight years ago on the TMS320C6xxx DSP side, so please be gentle with me. (Before that I was doing TTL back in the '70s, and still have a copy of The Orange Book but I digress).

    I have a brand new new install of CCS 6.0.0.00190 on Windows 8.1 x64, and the CC3200 LaunchXL. It worked initially and then I started getting the errors cited:

    Error connecting to the target

    in a message box and in the debug console I have

    Cortex_M4_0: GEL Output:

    Memory Map Initialization Complete

    Cortex_M4_0: Error connecting to the target

    I tried restarting CCS, this made no difference. Unplugging the USB connection and plugging it back in, no difference. Then I tried swapping between two USB ports on the hub and I could "reset" the problem, but it meant I had to keep reconnecting Putty (my terminal emulator) to the USB virtual COM port of the CC3200 LaunchXL.

    I have since discovered that there seems to be a conflict between having a Putty session open on the USB COM port at the same time as trying to open a debug session. By closing down the Putty session before starting a debug session from CCS, you can avoid the error. Once the debug session is started, you can safely re-open the Putty session.

    Hope this helps.

    Cheers, Howard

  • Hi Aaron,

    I received a new LP, now I'm able to connect to the CC3200 and to load program code.
    So it seems that the first one was broken.

    Best Regards,
    Christian

  • Thanks for your post Howard and welcome to CC3200!

  • Hi 

    I am having the same problem. The target CC3200 LaunchXL board has all the jumpers in the default positions. I added a jumper to SOP2. I still am unable to connect to the target. I have tested with 2 boards. 

    The PC drivers look like they are working.

    The debug device is listed as Stellaris In Circuit debug interface_0/Cortex_M4_0

    Any ideas

    Paul

  • Hi,

    I'm experiencing the same issue with brand new two CC3200 LaunchXL board. Every time I try to start a debug session, the following message appears in console:

    Cortex_M4_0: GEL Output:
    Memory Map Initialization Complete
    Cortex_M4_0: GEL Output:
    Target Reset
    Cortex_M4_0: Can't Run Target CPU: Debug Port error occurred.
    Cortex_M4_0: Error 

     

    Any hints?

  • Once I cold booted my PC the issue went away. I also tried different USB connections

    -Paul

  • Hello guys, I just bought my CC3200 launchpad and I just tried to debug the "wlan_station" example but I had this error:

    Cortex_M4_0: Trouble Reading Memory Block at 0x20004000 on Page 0 of Length 0x4: Debug Port error occurred.
    Cortex_M4_0: File Loader: Data verification failed at address 0x20004001 Please verify target memory and memory map.
    Cortex_M4_0: GEL: File: C:\ti\CC3200SDK\cc3200-sdk\example\getting_started_with_wlan_station\ccs\Release\wlan_station.out: a data verification error occurred, file load failed.

    All pin headers are configured as the "getting started" guide said. Any clues?

    Thanks.

  • Hi Christian:

        I get the same error as yours. Any idea now?

  • Hi,about CC3200 LaunchPad,

    The first time I can  program *.ucf, and test wifi APP link is ok , But now become unable to program , I do not know what happened?

    Please tell me how to solve this problem ?

  • I've tried to debug with this launchpad,it works when i debug the wlan station example ,but failed on blinky eaxmple. CCS always says 

    Stellaris In-Circuit Debug Interface_0/Cortex_M4_0 : Target must be connected before loading program.

    What should I do?

  • I am also facing the same error. It worked for me couple of times and the it started giving same error. Is there any way that I can fix this?

    Thanks.

  • I am getting the same errors, and other similar ones.  Sometimes the CC3200LP works, but most of the time it hangs up with errors when running wlan_station.  I have not been able to run the Out-of-Box project from CCS.  An access point is never shown and there are multiple port errors.


    Are the boards bad or is there some other fix that we need to know about? 

  • We are having exact the same problam !
    Maybe it is time for someone of Ti's engineers to ansewer this threat since there a many of us having this problem ...
    would be great. best , Vinc
  • Thank you Howard,

    great fix for a daft problem 

  • This problem  might be when the serial port is not free, or either some background apps are sniffing,etc.

    Try changing the USB port in which it is plugged in. Make sure no application is monitoring the COM port that's connected..

  • Error connecting to the target

    I tried restarting CCS, this made no difference. Unplugging the USB connection and plugging it back in, no difference. Then I tried swapping between two USB ports on the hub and I could "reset" the problem, but it meant I had to keep reconnecting Putty (my terminal emulator) to the USB virtual COM port of the CC3200 LaunchXL.

    I have since discovered that there seems to be a conflict between having a Putty session open on the USB COM port at the same time as trying to open a debug session. By closing down the Putty session before starting a debug session from CCS, you can avoid the error. Once the debug session is started, you can safely re-open the Putty session.