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 SWD 2 wire debug unreliable or non functional and crashing ccs6

Other Parts Discussed in Thread: CC3200

Hi,

I have been trying to use the 2 wire debug method (SWD) and getting very intermittant results. 

Often CCS6 will get stuck attempting to launch the debug session. It will then require task manager to close it otherwise it will never stop.

To get it to work I change back to 4 wire (JTAG) and connect the eval board to a debug session, and then change back to 2 wire (SWD) mode and attempt to connect a debug session on my other board (my own or eval board makes no difference) . This works some times and a lot of the time not as well, requiring a restart of CCS6 again. The eval board has the same intermittent working as my own PCB does. I am obviously changing the target configuration between JTAG and SWD (in the advanced tab of target configuration) as well as changing the sop jumpers on the board used. I tried changing the frequency from 500000 to 250000, but this made no difference sither. I can't seem to work out what method of sticking your tongue out, standing on one foot, and reciting poetry seems to make it work. But it is very very frustrating to work with. I know the obvious question, why aren't you using 4 wire mode. Well nice try but for my application we didn't have room for that and any wires i tack on fall off due to the pads being so small, so going to 4 wire is not possible on my board, and besides this should work , it just seems not to.  Can anyone shed any light on why this feature works so poorly ? Again it is not a board issue, the eval board does the same, try yourself a few times and you will find out. And CCS should not totally lock up and not be able to recover without system intervention. bad , bad code.

Please chime in if you have had this issue too, misery loves company ;).

  • PS, this is for the cc3200
  • Hi,

    Can you test one thing?

    - Close CCS
    - Unzip the attached file into the directory C:/ti/ccsv6/ccs_base/common/targetdb/devices
    - Restart CCS
    - Create a new target configuration using the JTAG pod configured to SWD and the new CC3200_SWD device

    It is possible the CC3200 device support is missing this file to be properly used with SWD modes.

    Regards,

    Rafael

    CC3200SWD.zip

  • Rafael,

    Hi , thanks, I tried that. Copied the file into the specified directory.

    Started CCS and selected cc3200swd for board type, and changed interface type to swd in advanced menu.

    Note I selected cortex m4  instead of stellaris m4 when the pop up dialogue opened.

    It crashed straight away.I then tried selecting stellaris m4 instead from the pop up dialogue.

    And killed ccs and started it again, and tried debugging again. 

    It hung again as before.

    This change doesn't seem to help.

    Thanks

  • Hi,
    I also tried changing the linker command file in the xml config file for the cc3200 to try and solve the issue with the cc3200R1 not debugging but this did not fix that problem either. This is another problem I and others are trying to solve but still have not got any useful suggestions from TI as yet.
  • Hi,

    I haven't had any more suggestions. Is there any other way I can try and get this to work properly?

    Can TI representatives test this on the eval board and verify this is an issue with the environment?

    Thanks.

  • Hi,

    Sorry about the delay; the file I sent you is based on an internal discussion and was created mainly to overcome a limitation when using XDS200 JTAG debuggers connected to CC3200 devices in SWO mode. However, it also works fine with the Stellaris ICDI connection in several setup systems around here (including mine).

    I have my Launchpad jumpers set to the following:

    Therefore I am unsure what may be going wrong with your setup. For starters I would check the sections General IDE and Debugger of the CCSv6 Troubleshooting page.

    Hope this helps,

    Rafael 

  • Hi,

    I have same issue. I am not able to use SWD with CC3200 LP in CCS 6.1.2. JTAG (4-wire) works well but with 2 wires SWD debug is
    unreliable and CCS is freezing. Exactly same symptoms as at first post. Any news at this topic?


    Thanks,

    Jan
  • Hi

    I have just tried the exact same as shown on the pictures above: Using the "Stellaris InCircuit Debug Interface", and the "CC3200SWD" variant. And setting the "Target Connection Option" to SWD, but it doesn't solve the problem.

    When you look at the pictures above, you can also see, that the jumpers J10 and J11 (TDI and TDO) is still in place. This means that the interface is configured for 4W JTAG, while the SOP0 (J17) are configures for SWD. However it seems that the SOP0 pin is only read by the MCU after a total power off. This means that if I try to connect in 4W JTAG (which is succesfull) and afterwards add a jumper in SOP0, I can still connect to the MCU. If I then cycle the power, and try to connect, it is not possible. The conclusion is, that only after power has been switched off and on, the SOP pin is read, and I guess that since it works in the example above, it is because the Launchpad hasn't been disconnected.

    But the problem is more likely to be Code Composer itself...
    If the launchpad is in JTAG mode (no jumpers on any of the SOP pins), it makes no difference if SWD or JTAG is selected in CCS, it can easily connect. But when the Launchpad is in SWD mode, CCS cannot connect neither in SWD nor in JTAG mode. My suspicion is, that SWD/JTAG option does work or simply isn't implementet in CCS, since CCS is in JTAG mode regardless of the setting.

    It could be nice if someone from TI would reproduce to test described above, but this time cycle the power each time the SOP jumpers have been changed.

    /Henrik
  • I had same problems with CCS, but after upgrading to the lastest version released a few days ago (version 6.1.3.00033) it seems that the problem has been solved - it least i works with my CC3200 Launchpad (with the TDI and TDO jumpers removed).


    /Henrik
  • I have CCS 6.1.3.00033 on Ubuntu 16.04LTS, target is CC3200 Launchpad board, and SWD does not work but JTAG works. Any clues? The error message for SWD is as below.

    Cortex_M4_0: GEL Output:
    Memory Map Initialization Complete
    Cortex_M4_0: GEL Output:
    Target Reset
    Cortex_M4_0: Trouble Writing Memory Block at 0x20004000 on Page 0 of Length 0x7ff0
    Cortex_M4_0: File Loader: Verification failed: Target failed to write 0x20004000
    Cortex_M4_0: GEL: File: /path/to/wlan_station/Release/wlan_station.out: Load failed.