LP-EM-CC2745R10-Q1: XDS220 cannot connect : SC_ERR_SWD_PROTOCOL

Expert 2055 points
Part Number: LP-EM-CC2745R10-Q1
Other Parts Discussed in Thread: ENERGYTRACE

Tool/software:

I wanted to use the XDS 220 ISO I have, from Spectrum Digital, on this chip, but have no luck connecting to it.

I'm using the 10-pin connector on the board.

Error I get is SC_ERR_SWD_PROTOCOL, with log below

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

This utility has selected a 560/2xx-class product.
This utility will load the program 'xds2xxu.out'.
The library build date was 'Aug 12 2025'.
The library build time was '07:30:43'.
The library package version is '20.3.0.3656'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '13' (0x0000000d).
The controller has an insertion length of '0' (0x00000000).
This utility will attempt to reset the controller to enter SWD mode.

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

This emulator does not create a reset log-file.

-----[Perform the SWD Mode Integrity test]-----------------------------------

This test will read the IDCODE register 1 time.


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

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

The value is '-615' (0xfffffd99).
The title is 'SC_ERR_SWD_PROTOCOL'.

The explanation is:
The target failed to see a correctly formatted SWD header. The
connection to the target may be unreliable. Try lowering the
TCLK setting before trying again.

I tried lowering debugger clock rate to 1Mhz, with no luck.

This is what that config looks like in CCS:

Shouldn't this probe work with this controller?

  • Hello,

    This configuration should work. 

    I was able connect to my LP-EM-CC2745R10-Q1 with a Spectrum Digital XDS220 using the 10-pin header on the board via a 20-to-10 pin adapter.

    The JTAG connectivity test via "Test Connections" button passes:

    Check your adapter/connections, make sure they are all good.

    Thanks

    ki

  • I can do a test connection ok. 

    I have a regular XDS200 vs the 220.  I am connected via a cTI20 to cortex10 adapter.  I am powering the LaunchPad via the 3.3V and GND pins on the spit XDS110.

    -----[Print the board config pathname(s)]------------------------------------
    
    /Users/xxx/.ti/ccs2030/0/0/BrdDat/testBoard.dat
    
    -----[Print the reset-command software log-file]-----------------------------
    
    This utility has selected a 560/2xx-class product.
    This utility will load the program 'xds2xxu.out'.
    The library build date was 'Aug 12 2025'.
    The library build time was '07:30:43'.
    The library package version is '20.3.0.3656'.
    The library component version is '35.35.0.0'.
    The controller does not use a programmable FPGA.
    The controller has a version number of '13' (0x0000000d).
    The controller has an insertion length of '0' (0x00000000).
    This utility will attempt to reset the controller to enter SWD mode.
    
    -----[Print the reset-command hardware log-file]-----------------------------
    
    This emulator does not create a reset log-file.
    
    -----[Perform the SWD Mode Integrity test]-----------------------------------
    
    This test will read the IDCODE register 1 time.
    
    The IDCODE register value is 0x6ba02477.
    
    The SWD Mode Integrity test has succeeded.
    Close

    I left the default connection settings:

    I can then launch a debug session in CCS and connect to the M33.  However when I try to load one of my programs to flash I get an error.  A couple of us are experimenting with this and will provide more info tomorrow. 

    The XDS110 would be the default debug probe used with this device and it also has a secure debug manager which I am not sure if we support that with XDS200.

    Regards,

    John

  • I see, might be futile in the end. 

    I'm trying not to just discard my expensive XDS probe which I have previously purchased specifically to handle all my TI devices. Note, this model suppors also Ethernet, which I valued.

    Would be nice if TI doesn't make them obsolete.

  • If you would look at the config image I have posted originally, You would have seen I have same settings on SWD TDO pin.

  • More example /details:

    Board not powered log, so it senses something is on/off wire...

    But now i have tried 2 different power supply modes - one from same laptop USB, to 3.3v converter to jumper wires, and one external PSU, but even though board is powered , green led is on, all I get is SC_ERR_SWD_PROTOCOL. No luck ...

  •   Can you then show your physical setup, with a pic or two? Including how you powering the board.

    Also, what is your EVM revision number? of the launchpad

  • The XDS110 would be the default debug probe used with this device and it also has a secure debug manager which I am not sure if we support that with XDS200.

    Unfortunately this appears to be the case. It only appears supported with XDS110. 

    Hence we cannot recommend a non-XDS110 debug probe (for this device).

  • Given the lack of XDS200 support for this device the cheapest option ($29) would be to get a https://www.ti.com/tool/LP-XDS110

    It is a stripped down XDS110 that can connect to the LaunchPad you are using.  It also comes with a 10pin cable for connecting to custom boards that have the Cortex 10 header on them and you can power board from it.  I was actually using it to power the board when I was testing my XDS200 connection.

    There is also a slightly more expensive version that supports EnergyTrace for this device.  https://www.ti.com/tool/LP-XDS110ET

    Regards,

    John

  • I guess that's it then for this question.

    I'll probably have to make another thread if I need to bin my XDS220 probe is it wont work for any new TI devices.?

  • Currently it is the CC234x and CC27x5 devices that have the feature that is not supported by anything other than XDS110.  

    Regards,

    John