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.

IWR6843ISK-ODS: Debug connection error

Part Number: IWR6843ISK-ODS
Other Parts Discussed in Thread: IWR6843ISK

Hi, I have a MWAVEBOOST. 2x IWR6843ISK-ODS and one  and IWR6843ISK module.
After successfully debugging both IWR6843ISK-ODS modules, I encounter a sudden error this morning while starting a debug session:

Error connecting to the target:
(Error -1170 @ 0x0)
Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK).
(Emulation package

Testing the ccxml file function, it seems that there is an error in the USCIF driver:

-----[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.

Reading through did not solve the problem. Both IWR6843ISK-ODS show the same error. The  IWR6843ISK is working, but the code is not showing any output in the console while running the overhead_3d_people_count_68xx_mss project.

What could be wrong here?

  • Hello.

    I would check and confirm that the EVM is in functional mode.  So I would just check that the ODS switches have been configured for being connected to the ICBoost.  Also check that after being flashed that the jumpers are in the right position as well as the ICBoost board + ODS are reset(press the NRST button).

    With regards to the guide, were you able to go through every possible issue and rule it out and/or isolate it to either a hardware or software issue as demonstrated in the guide?  I've circled(please excuse my penmanship) a couple of points that should definitely help isolate the problem.