Using CC2650Moda Boosterpack module + XDS100V3 + CCSV7

Hi Fredrik,

Thanks for your answer !
Looking closely to my JTAG adapter and the XDS100V3 Embest debugger schematic I noticed one pin identified as GND was the T_DIS.
Communication was then good and just had an issue with the power supply (Error -180).
Power supply issue solved I'm still stuck at the "The value is '-275' (0xfffffeed). The title is 'SC_ERR_SCAN_POLL_BUSY'." level.
Looks like this is a usual issue with this CC2650M, did you get an idea of what could be wrong ? Power supplies are ok.

Cheers,
Ben

Hi,

stepping down the debug clock at 1Mhz, the time out error changes to : The value is '-233' (0xffffff17).

The title is 'SC_ERR_PATH_BROKEN'.

[Start: Texas Instruments XDS100v3 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\BPerrin\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 'Oct  6 2016'.

The library build time was '20:21:35'.

The library package version is '6.0.407.6'.

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]

I checked again my configuration : 1149.7 2 pins, Overclock with user specified value (1Mhz), OSCAN5,...

Using an oscilloscope I get the CLK and TMS sent by the debugger. Power supply is alright.

I add 100k on the reset as external pull-up, but still doesn't work.

Even if running in 2 wire JTAG, TDI and TDO were inverted and disconnected, but still doesn't work.

Does anyone get an idea ?

Regards,

Ben