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.

  • Resolved

CC2640 with 2-wire cJTAG CC-DEVPACK-DEBUG

We made a custom board (very simple), using CC2640 4x4 and would like to know how to properly connect 2-wire cJTAG from CC-DEVPACK-DEBUG to it. 

We verified that the devpack can program the sensor tag but are having trouble getting it to recognize our board. 

Attached is a drawing of the connections we made. 

I believe the question comes down to is there is something that needs to be changed in the board configuration of the devpack in CCS (or IAR) to use cJTAG. it seems that by default it uses 4-wire JTAG when programing the sensor tag. 

can someone please clarify of A, our 3 wires (TMS, TCK, GND) are correct and suffice. and B, what change (if any) we need to make in the debugger configuration in CCS/IAR?

CCS is giving the following error when trying to connect to our board:

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.

 

--

PS. Thank you for clicking  Verify Answer  below if this answered your question!

  • I have a cc2640 board that can be programmed using XDS110 with 2 pin cjtag. There is trick involved to change default working mode. I still can not using CCS to program/debug cc2640 using XSD110 with 2 pin cjtag. Is there any trick to change default working mode, there is no setting in CCS UI to choose between JTAG with cJtag.

    Thanks.

    Jin Jiang
  • Genius 12775 points

    In reply to Jin Jiang:

    In CCS, you select 2-pin cJTAG for XDS110 by double-clicking your target configuration file (.ccxml).

    - Select the Advanced tab
    - Select the XDS110 debug probe
    - Choose cJTAG (1149.7)... from the dropdown.

    If you do not have these options, make sure you update CCS from Help > Check for Updates, or download the latest version from the web.

    TIABO

  • In reply to TIABO:

    Tiabo,

    Thank you so much for the quick response and deep insight. Problem solved.


    Jin

  • In reply to Jin Jiang:

    Hi,

    I've just seen that the Debugger Devpack can run in 2-wire cJTAG mode now, which would be really useful for me.  I currently have the Debugger (HW Rev 1.2.0, FW rev 2.3.0.2) communicating to my custom hardware happily in 4-wire JTAG mode.  However when I disconnect the TDI and TDO pins from the devpack and configure my .ccxml for 2-wire, as indicated in the post above, I get the following error message:

    IcePick_C: Error connecting to the target: (Error -242 @ 0x0) A router subpath could not be accessed. The board configuration file is probably incorrect. (Emulation package 6.0.407.3)

    Trying a test connection gives errors too, see the log below:

    [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\Ross\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 'Jul 27 2016'.

    The library build time was '18:31:37'.

    The library package version is '6.0.407.3'.

    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]

    Any suggestions for what might be going wrong here?  I note that the XDS110 wiki page doesn't seem to mention 2-wire JTAG.  Does the Debugger Devpack actually support this feature? 

    Thanks,

    Ross

  • Genius 12775 points

    In reply to Ross Arnott:

    Hi,

    I use this XDS110 2-pin cJTAG configuration:

    I have CCS 6.2.0.048.

    Br,
    TIABO

  • In reply to TIABO:

    Hi TIABO,

    I am using exactly that configuration, albeit with CS 6.2.0.050. I get the errors I showed above. It does connect fine using the 4-wire JTAG option, but the TDO and TDI pins are shared with my external flash MOSI and MISO pins so I can't debug the problems I'm having with OAD whilst debugging in that mode.

    Any suggestions for other things to try would be most welcome.

    Thanks,

    Ross
  • Genius 12775 points

    In reply to Ross Arnott:

    Please try the following:

    1. Select View > Target Configurations
    2. Right click your .ccxml file and select "Launch Selected Configuration"
    3. Select Scripts > CC26x0 > MassErase
    4. Observe "Mass Erase complete" in the Console view.
    5. In the Debug view: Right click "Texas Instruments XDS110..." and select "Connect Target"
    6. You should now be connected to the target.

    Let me know how that goes.

    TIABO
  • In reply to TIABO:

    Hi,

    When I click on the scripts menu there are none there. "No scripts available" is displayed.

    Regards,

    Ross
  • Genius 12775 points

    In reply to Ross Arnott:

    If you don't have that option, the GEL scripts for the CC2640 device havn't been loaded properly.

    1. Have you selected the CC2640F128 device in your .ccxml file?
    If you have, then it looks like the CC13xx/CC26xx device support files aren't installed properly.

    2. You can check in Help > Installation details. Also, check if there are updates available.
    The cleanest way to get them installed is to reinstall CCS, and make sure you install Wireless MCU device support (CC13xx/CC26xx sub menu item selected).


    TIABO
  • In reply to TIABO:

    HI,

    Yes, I have got the CC2640F128 device selected in the .ccxml file. I can (and will) try to reinstall/install updates although I'm a bit nervous after having a bunch of problems with this recently that caused me to have to reinstall windows completely.

    Could you please explain what the steps (1-6 above) that include the mass erase are trying to achieve? How will a mass erase work if a 2-wire JTAG connection can't be established?

    Thanks,

    Ross

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.