CCS/CC3220MOD: Debugging CC3220MOD with XDS110 debug probe

Hi Sarah,

Thanks for replying. 

Actually i'm trying to do that (i.e not using the embedded XDS110 on the launchpad board but the embedded probe i have bought) but also to use that probe to debug a custom board, build around the CC3220MODSF. 

Neither of them are visible for the probe. 

Best regards,

Kateline 

Hi Kateline,

When working with the LaunchPad JTAG, did you remove jumpers as described in the CC3220MODA LP Hardware User's Guide: http://www.ti.com/lit/swru512

You may want to review the Hardware Design Checklist for your custom board. This E2E thread may also help: e2e.ti.com/.../2361386

Best regards,
Sarah

Hello Sarah, 

Thanks for your answer and sorry for the late reply... 

For what concerns the launchpad: 

I checked the user manual and the jumpers are as described: from TMS to BRD open (no jumper on it). 

I've set the SOP bit as such: 010 (UARTLOAD_FUNCTIONNAL_4WJ). 

The Launchpad is powered externally with a 5V alimentation. 

Still CSS doesn't "see" the board via the probe. 

Is there something else left to do?

For what concerns the custom board, i'll check the link that you posted in your previous message, thank you very much.

Thanks in advance for your help!

Best,

Kateline 

EDIT: 

When i check Uniflash, it does detect the XDS110 probe but not the CC3220 (launchpadXL or own board). I then try to select the device from the list proposed by Uniflash but the CC3220 isn't anywhere in that list... Do I have to do an update of the probe to enable it to see the XX3220?

Hi Kateline,

Do I understand correctly that you removed the jumpers you mentioned from the LaunchPad? If you are supplying power via the USB, you need to have the jumpers populated as shown in the figure of the USB Power section of the LaunchPad Hardware User's Guide: http://www.ti.com/lit/swru463

Please be sure you have the latest UniFlash (4.2 or later) installed. If you can't see the CC3220 at all in the Choose Your Device list, then it sounds like you have an old version.

Are you able to see the CC3220 in your PC's device manager?

Best regards,

Sarah

Hello Sarah,

Indeed, i removed the jumpers from TCK to BRD on J3. 

I have uniflash 4.2.0 on my computer.

The launchpad is powered via an external 5V power. 

Previously, I worked with the launchpad's embedded XDS110 (via USB thus) and uniflash could see it directly, so i'm gessing there is something wrong either with the XDS 110 (stand alone) firmware or with the way i set the jumpers on the board. 

I ran the "Connection Test" from CCS (7.2.0 version) and i got the following log (i don't know if it will help you tell me what i do wrong:) 

[Start: Texas Instruments XDS110 USB Debug Probe_0]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

[Result]

-----[Print the board config pathname(s)]------------------------------------

C:\Users\KDRIES~1\AppData\Local\TEXASI~1\
CCS\ti\0\0\BrdDat\testBoard.dat

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'jioxds110.dll'.
The library build date was 'Feb 8 2018'.
The library build time was '18:36:28'.
The library package version is '7.0.188.0'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '5' (0x00000005).
The controller has an insertion length of '0' (0x00000000).
This utility will attempt to reset the controller.
This utility has successfully reset the controller.

-----[Print the reset-command hardware log-file]-----------------------------

The scan-path will be reset by toggling the JTAG TRST signal.
The controller is the XDS110 with USB interface.
The link from controller to target is direct (without cable).
The software is configured for XDS110 features.
The controller cannot monitor the value on the EMU[0] pin.
The controller cannot monitor the value on the EMU[1] pin.
The controller cannot control the timing on output pins.
The controller cannot control the timing on input pins.
The scan-path link-delay has been set to exactly '0' (0x0000).

-----[An error has occurred and this utility has aborted]--------------------

This error is generated by TI's USCIF driver or utilities.

The value is '-231' (0xffffff19).
The title is 'SC_ERR_PATH_IR_MEASURE'.

The explanation is:
The measured length of the JTAG IR instruction path is invalid.
This indicates that an error exists in the link-delay or scan-path.

[End: Texas Instruments XDS110 USB Debug Probe_0]

I've found some threads with the same error as "The controller cannot monitor the value on the EMU[0] pin." and they were talking about a pullup resistor that was to high on TRST? But on the JTAG on the board there is no such signal... So I don't really know if it can apply here.

Thanks again for your help,

Best,

Kateline 

Hello Sarah,

Thanks for your answer,

Populating the J3-RST, J20 and J19 pins on the board worked! I can now see the board from CCS and successfully compile my code.

I would like to test the network_terminal example. For this one I have to use the UART (to send the commands to the board). However it doesn't seem to work. 

Which pins do i have to populate/unpopulate to get the UART to work? (I'm connecting to the COM8 on my computer, corresponding to the "XDS110 Class Application/User UART" of the XDS110 probe). 

EDIT: 

I use the AUXILIARY port of the XDS110 for the UART: on the cable, UARTTX and UARTRX connected to GPIO13 and GPIO12 respectively. In CCS i see indeed lots of things on the terminal but it is not what i am expecting so here is now my question: Which one of the two virtual com ports do i need to connect to (Class Appluication/User UART or Class Auxiliary data port?) and which baud rate do i need to use for the XDS110 to communicate properly with the CC3220? 

Thanks again for your help,

Best,

Kateline