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.

CC1310: Can't connect using SWD

Part Number: CC1310

Hi,

We developed a new product using CC1310 Launchpad.

Now, our own board is ready and we are trying to connect and download firmware to it using SWD.

We are connecting the pins (GND, 3v3, TMS and TCK) from the XDS110 presented in the Launchpad to our board.

Be we are getting the following message:

Error connecting to the target:
(Error -615 @ 0x0)
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.
(Emulation package 6.0.579.0)

  • The "Test Connection" log:

    [Start: Texas Instruments XDS110 USB Debug Probe]

    Execute the command:

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

    [Result]


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

    C:\Users\lucas.s\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 22 2017'.
    The library build time was '17:13:34'.
    The library package version is '6.0.579.0'.
    The library component version is '35.35.0.0'.
    The controller does not use a programmable FPGA.

    An error occurred while hard opening the controller.

    -----[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.

    [End: Texas Instruments XDS110 USB Debug Probe]
  • Mad River said:
    Now, our own board is ready and we are trying to connect and download firmware to it using SWD.

    As far as I am aware the CC1310 doesn't support SWD mode.

    When I tried setting an XDS110 to use "SWD Mode - Aux COM port is target TDO pin" with a CC1310F128 the test connection fails with the same SC_ERR_SWD_PROTOCOL error as your are getting.

    Does the following work for you?

  • Hi Chester,

    I was able to download my program after trying your suggestion.

    But now I am getting the following error when trying to connect again:

    [Start: Texas Instruments XDS110 USB Debug Probe]

    Execute the command:

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

    [Result]


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

    C:\Users\lucas.s\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 22 2017'.
    The library build time was '17:13:34'.
    The library package version is '6.0.579.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 occurred while hard opening the controller.

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

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

    The value is '-242' (0xffffff0e).
    The title is 'SC_ERR_ROUTER_ACCESS_SUBPATH'.

    The explanation is:
    A router subpath could not be accessed.
    The board configuration file is probably incorrect.

    [End: Texas Instruments XDS110 USB Debug Probe]
  • Mad River said:
    I was able to download my program after trying your suggestion.

    But now I am getting the following error when trying to connect again:

    From a quick search think the downloaded program may have locked the debug interface, leading to the SC_ERR_ROUTER_ACCESS_SUBPATH error.

    The last post in https://e2e.ti.com/support/wireless_connectivity/bluetooth_low_energy/f/538/t/463274 suggests disabling "custom configuration" in the target configuration file and you should be able to launch the target connection file and use Scripts > CC13x0_CC26x0 > MassErase to wipe the chip flash, and unlock the debug interface.