CCS/CC2640R2F: launchxl-cc2640r2

Hi,

Thanks for sending the additional details - the board is fine, as well as the USB cable. 

kodia raoul said:

But I have seen a difference : On linux the XDCTOOL and others ares installed and i have been prompted for that recommandation .

If this sentence means you don't see the directories "ccsv7", "xdctools_3_32_02_25_core" and "xdctools_3_50_02_20_core" on the place where you installed CCS, then I suspect that somehow the Windows 10 install was not successful, which could explain the problems with device drivers. 

Regards,

Rafael

Hi        ----- I NEED URGEND HELP  -----

i also have Problems with XDC110 as descibed above - i have 2 brand new launchxl-cc2640r2 Launchpads here wich exactly behave the same

When i Start the Test Connection in the CC2640R2F.ccxml "Test Connection" it prints out:

[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\CASE18\AppData\Local\TEXASI~1\CCS\
    ti\1\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 'May  2 2017'.
The library build time was '12:59:57'.
The library package version is '6.0.628.1'.
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 '-261' (0xfffffefb).
The title is 'SC_ERR_XDS110_FAIL'.

The explanation is:
Invalid response was received from the XDS110.

[End: Texas Instruments XDS110 USB Debug Probe]

I've still updated the XDS Tools Software Drivers. I am using WINDOWS 10 - and don't have LINUX

the XDC Tools are located as installed : C:\ti\xdctools_3_32_01_22_core

Any ideas ?

Thanks Thomas