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.

MMWAVEICBOOST: The value is '-233' (0xffffff17). The title is 'SC_ERR_PATH_BROKEN'.

Part Number: MMWAVEICBOOST
Other Parts Discussed in Thread: IWR6843ISK-ODS, IWR6843

Tool/software:

Hi TI forum,

I am using the mmWaveICBoost together with the IWR6843ISK-ODS device.

When trying to connect to the cores in CCS debug, I am getting this error:

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 12.7.0.00130)

However, even after much power cycling, and resetting, I am still getting the error.

When I test out the connection in Target Configuration, I am getting -233 SC_ERR_PATH_BROKEN error:

The COM ports are still showing up on device manager :

Here is my setup, I have connected the usb to the XDS110 port, and I am using 5V 3A power supply:

  

I have tried different power supplies, tried the same thing on 2 separate MMwaveICBoost device, as well, I have swapped out with another IWR6843 device but I am getting the same error. 

However, if I remove the power supply jack connector, and connect a usb to the IWR6843 itself. I am able to get past this error, connect to the cores and do the normal debugging:

Here is the setup for that:

Please help me with this issue, while I can still do debugging with the mmwaveICBoost and radar, I am unable to connect the DCA1000 altogether with this setup.

Thank you,

Shi Xiang

  • Hello.

    All of your setup looks correct; have you tried with a different ICBOOST EVM?  It may be an issue with the EVM itself.  When you open up device manager when the ICBOOST is plugged in do you see the correct XDS ports?

    Sincerely,

    Santosh

  • Hi,

    The device manager with the ICBoost shows the correct XDS ports. COM2 Class Application/User UART and COM1 Class Auxilary/Data Port in my case, 

    I have tested it out with a different ICBOOST EVM, this ICBOOST has a bit of a loose usb to xds110 connection, where I would need to angle the device in a way so that the XDS connection appears on the device manager. However I think this is a separate issue altogether.

    Here's what happened:

    1. Flashing the device again

    I needed to flash the device again, but I was unable to do so in this configuration: usb to xds110 on the icboost + iwr6843 + dcjack powersupply:

    But I managed to flash the device in this configuration: usb to xds110 on the icboost + usb to iwr6843

    2. Testing on CCS debug

    Following that, I tried using CCS debug target configuration to test connection JTAG with this configuration: usb to xds110 on the icboost + usb to iwr6843. It worked well, the scan path integrity shows pass in the checks.

    I then tried to test the connection with this configuration: usb to xds110 on the icboost + iwr6843 + dcjack powersupply. Surprisingly, it passed the scan path integrity checks as well. However, after a power cycle/NRST reset, the same error of -233 SC_ERR_PATH_BROKEN happens again.

    Now, I am unable to get this configuration: usb to xds110 on the icboost + iwr6843 + dcjack powersupply, working again for ccs debug, regardless of how many times I reconnect/ powercycle.

    Other:

    I have tested with 3 different power supplies so far, 5V 2A, 5V 3A, and a 5V 4A supply, with all of them having the same issue on both boards. I have no idea what could be causing this issue, be it software or hardware wise. 

    Thank you,

    Shi Xiang

  • Hello.

    I have tested it out with a different ICBOOST EVM, this ICBOOST has a bit of a loose usb to xds110 connection, where I would need to angle the device in a way so that the XDS connection appears on the device manager.

    Not having a good connection could result in not being able to connect to the cores; please make sure that there is a good connection.

    I then tried to test the connection with this configuration: usb to xds110 on the icboost + iwr6843 + dcjack powersupply. Surprisingly, it passed the scan path integrity checks as well. However, after a power cycle/NRST reset, the same error of -233 SC_ERR_PATH_BROKEN happens again.

    It could be something you are doing in your software that could be essentially locking the device.  Are you running a prebuilt binary from the toolbox or custom code?

    Sincerely,

    Santosh

  • Hi

    I am running the ccsdebug binary for the radar, located C:\ti\mmwave_sdk_03_06_02_00-LTS\packages\ti\utils\ccsdebug\xwr68xx_ccsdebug.bin.

    I am not running a custom version of this binary, but I have used it to quick load the program files on the mss and dss according to 4.2: Using CCS Debug

    Thanks,

    Shi Xiang

  • Hello.

    Even though you are flashing the ccsdebug binary, whatever code you are loading could be potentially locking the device.  Can you try loading the mss and dss files from a demo in the toolbox such as out of box to see if this issue persists?  If it does, then it may be a hardware issue with your ICBOOST and I would recommend trying with a new board.  Otherwise, it may be an issue with the software you are loading.

    Sincerely,

    Santosh