• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 2 answers
  • Subscribers 52 subscribers
  • Views 2230 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CC2630 + XDS100V2

nicolas izquierdo
Prodigy 40 points
Other Parts Discussed in Thread: CC2630

Hello!

Im getting the following error

[Start: Texas Instruments XDS100v2 USB Debug Probe]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity

[Result]


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

C:\Users\uidj6623\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 'jioserdesusb.dll'.
The library build date was 'Sep 4 2015'.
The library build time was '21:59:23'.
The library package version is '6.0.14.5'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '4' (0x00000004).
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 FTDI FT2232 with USB interface.
The link from controller to target is direct (without cable).
The software is configured for FTDI FT2232 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 XDS100v2 USB Debug Probe]

------------------------------------------------------------------------------------

my JTAG connection is the 20 pin in a 4 pins configuration,

I tried several configuration in the JTAG TCLK but nothing happend.

Is a custom hardware following the sensor tag schematic.

can the 24Mhz crystal doing some problem to the cc2630?

  • 0
    TI__Guru** 105180 points
    Hello,

    Can you try using a path that does not have spaces and follows the 8.3 short filename length:

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

    Best wishes
  • 0
    TI__Genius 12900 points
    The XDS debuggers that are supported for the CC26xx device family are XDS100v3, XDS110 and XDS200. You should use one of these debuggers.

    TIABO
  • 0 in reply to TIABO
    Prodigy 40 points

    HI Tiabo

    I'm a little confused, base on TI wiki I can see the XDS100V2 supporting the ARM Cortex-M3 which is the core of the CC26x0 devices..

    screen-shoot from wiki

  • 0 in reply to nicolas izquierdo
    TI__Genius 12900 points

    I understand the confusion. The difference between XDS100v2 and XDS100v3 is mainly that the latter supports 2-pin cJTAG (compact JTAG, IEEE 1149.7). The CC26xx device powers up in 2-pin cJTAG and a special sequence is required to switch into 4-pin JTAG mode.

    I don't have an XDS100v2, but my guess is that it does not support this switching sequence required to get CC26xx to communicate using 4-pin JTAG.

    TIABO

  • 0 in reply to TIABO
    Prodigy 40 points

    Getting Back

    I have now the XDS100v3 and I having the same error,

    -----[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 XDS100v3 USB Debug Probe_0]

    I am seeing activity with my scope in the pin TDI of the jtag, I was not expecting  a signal there, since this a 2 pin configuration.

    is this is normal?

    I only have connected, TMS, TCK, TVD, SRST_N, GND, 

  • 0 in reply to nicolas izquierdo
    TI__Genius 12900 points

    The error "A router subpath could not be accessed" may be caused by the device's debug interface being locked. The default configuration for CCS is to try to access the CPU_DAP for debugging, but this will not work if the debug interface is locked. You can try the following:

    In the Target connection view you attached above, for both subpath_0 and subpath_1, uncheck the "custom configuration" checkbox. 

    With "custom configuration" disabled, you should be able to launch the target connection file and use Script > CC26xx > MassErase to wipe the chip flash, and unlock the debug interface.

    Let me know if this helps.

    TIABO