- Ask a related questionWhat is a related question?A related question is a question created from another question. When the related question is created, it will be automatically linked to the original question.
Hi,
I am trying to setup my hardware pinout connection and CCS6 software configuration so that I can connect a custom CC2640(5x5) board to a XDS100v3.
I have been trying to get it to work, but no success. Does anyone have such a setup working? Could you please show the CCS6 JTAG configurations used and also all the physical pinout connections (pins, pull-ups/downs, etc) necessary to make JTAG work? Thanks!
Hi YK Chen,
I can see the XDS100v3 listed but not the CC2640 as shown above. Can you or your TI tooling colleagues provide a schematic/hookup diagram of how I can connect correctly the JTAG pins to a bare CC2640 board so that I can JTAG connect to it? My XDS100v3 debugger has the TI_JTAG_20PIN connector. So how should I connect up the pins like T_DIS, T_EMU0-T_EMU4, T_DIS, T_RTCK, T_RST_N, T_SRST_N, TVD which I am unsure how to correctly. For T_TMS, T_TDI, T_TDO and T_TCK I assume then connect directly to the corresponding JTAG pins on the CC2640. Please show all the necessary, pullup/downs, termination, etc which are required for all the JTAG signals above in order for the XDS100v3 to be able to communicate successfully with the CC2640.
On the software settings side, can you please provide all necessary configuration settings(ccxml) that I need to setup in CCS6 for this to work successfully too?
Also, can you please advise if the XDS100v3 can only connect via CJTAG(1149.7) and not the full JTAG(1149.1) , or are both supported for connecting to the CC2640 family?
Thanks!
Hi YK Chen,
Thank you for your reply. I can see the XDS100v3 listed but not the CC2640 as shown above. Can you or your TI tooling colleagues provide a schematic/hookup diagram of how I can connect correctly the JTAG pins to a bare CC2640 board so that I can JTAG connect to it? My XDS100v3 debugger has the TI_JTAG_20PIN connector. So how should I connect up the pins like T_DIS, T_EMU0-T_EMU4, T_DIS, T_RTCK, T_RST_N, T_SRST_N, TVD which I am unsure how to correctly. For T_TMS, T_TDI, T_TDO and T_TCK I assume then connect directly to the corresponding JTAG pins on the CC2640. Please show all the necessary, pullup/downs, termination, etc which are required for all the JTAG signals above in order for the XDS100v3 to be able to communicate successfully with the CC2640.
On the software settings side, can you please provide all necessary configuration settings(ccxml) that I need to setup in CCS6 for this to work successfully too?
Also, can you please advise if the XDS100v3 can only connect via CJTAG(1149.7) and not the full JTAG(1149.1) , or are both supported by XD100v3 for connecting to the CC2640 family?
Thanks!
I have been trying to get my XDS100v3 Debugger to work with my CC2640 custom board. However, no success in connecting. I have used settings below and have been getting the following error message when running "Test Connection" in CC6 to test the JTAG connection.
[Start: Texas Instruments XDS100v3 USB Debug Probe_0]
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\MW\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 'jioserdesusbv3.dll'.
The library build date was 'Nov 19 2015'.
The library build time was '00:41:25'.
The library package version is '6.0.83.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 '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 '-233' (0xffffff17).
The title is 'SC_ERR_PATH_BROKEN'.
The explanation is:
The JTAG IR and DR scan-paths cannot circulate bits, they may be broken.
An attempt to scan the JTAG scan-path has failed.
The target's JTAG scan-path appears to be broken
with a stuck-at-ones or stuck-at-zero fault.
[End: Texas Instruments XDS100v3 USB Debug Probe_0]
Also, I have probe the TMS and TCK line on the JTAG connection, an got the following oscilloscope capture
The yellow trace is TMS, the blue trace is TCK . Looking at the signalling pattern, the TMS doesn't look correct. Can someone please advise what maybe wrong and how can I rectify the problem so I can JTAG connect successfully to my CC2640 board? Please help.
