SWD and CC3200Mod

My understanding of SWD is that you will not need to involve the FTDI circuitry at all, as this is only used for USB support using the Stellaris ICDI or for Programming the Serial Flash. You should only need to connect direct to the SWD pins (Just like JTAG). You will need a emulator for this purposes.

This will only be used for debugging and not for programming serial flash, as programming will need to be performed using FTDI circuitry.

Glenn.

Glenn - that doesn't answer the question of why I cannot use the LaunchPad's emulator to debug our circuit.

To all,
To clarify the issue.
We would like to use the LaunchPad's emulator to debug the CC3200 on our circuit. The jumpers on J9 have been removed, TCK, TMS from the pins away from the LaunchPad's CC3200 are connected to the corresponding pins of the CC3200 on our circuit. SOP0 is high as well. We are unable to debug using this setup.
Our understanding from answers to prior questions is that this is possible.
e2e.ti.com/.../1264767

Any insights would be greatly appreciated.

Thank you,

same problem, SWD is flaky at best on either eval board or own board. Cannot get it to work reliably and crashes css constantly needed rask manager intervention. Please help this is driving me round the bend!

Hi Jill:

Did you find any solution to this issue? I'm experiencing the same problem now with my custom CC3200 board. Everything seems to be working fine except for SWD. I can flash the board using Uniflash and I can debug the board when I use full JTAG. However, using SWD doesn't seem to work and I get an "Error connecting to the target." message.

My I2C bus is sharing the TDI and TDO lines on the JTAG port, so I need to use SWD to free up those lines. For what it's worth, SWD works fine on my LauchPad, just not on my custom board.

Thanks!
- Will

----- UPDATE -----

This is working now. Can't say exactly why and it's not entirely reliable. I am able to debug using SWD but it's pretty flaky. I get frequent "Debug Port error occurred." messages.

Hi TI,
Do you have any insights on debugging CC3200MOD on a custom board? I still have the problem above!

Thanks!

Can you also connect the nRESET signal from the FTDI to the target board? This should solve the stability problems.

Dear Prajay,

We have TCK, TMS, nReset and GND from LaunchPad connected to our custom circuit.  The settings in CodeComposer are set to use SWD.  Yet, debugging capability does not work.

It sounds like several others are having this issue.  Can TI team resolve this soon?  Is it a bug in the silicon?

FYI - we are using CC3200MOD.

Hi Jill:

I have a similar set-up and it's been up and running for a while and it's been pretty stable. I'm not using the CC3200MOD, but I'm using a custom PCB that we designed. I am also using SWD and using a Launchpad as the debugging interface. It sounds like you've got most of your jumper settings and configuration correct, but I'll lay out our setup to see if it helps you at all.

This is how we have our set-up configured for debugging with SWD:

Launchpad jumpers J6 and J7 OFF
Launchpad jumpers J8, J9, J10, J11 OFF
Launchpad jumper J12 OFF
Launchpad jumper J13 ON
We have a jumper wire connecting TCK on the Launchpad to TCK on our board
We have a jumper wire connecting TMS on the Launchpad to TMS on our board
We're also supplying power to our board from Launchpad VCC_BRD and GND
Jumper SOP0 is ON on our board (SOP jumpers on Launchpad should be irrelevant)
We do NOT have the Reset line from the Launchpad connected to Reset on our board. We tried this with and without and it didn't seem to make a difference.

It should be noted that this setup works fine almost all of the time and we're able to connect to our board and run the debugger. However, it will occasionally get into to a state where the CC3200 on our board appears to be completely locked up, and we get a few different errors like "cannot connect to target" or an error related to the ROM table. Sometimes it stays locked in this state for a while and it takes repeated attempts at debugging to reinstate communication with our board.

Thanks Will! I have rechecked the configuration with what you specified and it matches. However it still doesn't connect. This is the case across multiple PCBs.
I have a question about your circuit - do you have SOP1 pulled down with a 100k resistor as shown in the cc3200 launchpad schematic for SWD? The CC3200Mod datasheet in one instance says "Do Not Connect" and another instance requires it to be pulled down.

Everything else works well including uniflash.

Hi Jill:

Yes, we have SOP1 pulled low through a 100k resistor, which is connected to pin 34 on the CC3200. We left SOP0 and SOP2 configurable through jumpers.

Thanks for confirming.