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.

CCS/IWR6843ISK-ODS: Cannot connect to the C674x core to debug; error -6305

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

Tool/software: Code Composer Studio

I am using the IWR6843 overhead antenna plug-in module (IWR6843ISK-ODS) with the mmWave carrier card platform (MMWAVEICBOOST), with the intention of running the Vital Signs demo of the mmWave Industrial Toolbox: http://dev.ti.com/tirex/explore/node?node=AJ3V.naK7FG5g7n7bxAw5A__VLyFKFf__LATEST

I followed the instructions for using Debug mode. The xwr68xx_ccsdebug.bin file was flashed onto the chip successfully, and the 'Texas Instruments XDS110 USB Debug Probe' target configuration was set up.

However, on clicking Connect Target (for both the Cortex R4 and the C674x cores simultaneously), I get the following log:

CS_DAP_0: GEL Output: --->> DSS is under application controlled reset. Prior to connecting this reset must be released.
CS_DAP_0: GEL Output: --->> The debugger will enable "Halt On Reset" and release the application-extended reset
CS_DAP_0: GEL Output: --->> "Halt On Reset" has been enabled on the C674X_0CS_DAP_0: GEL Output: --->> ERROR : timeout while waiting for DSS to power on
C674X_0: Error connecting to the target: (Error -6305) PRSC module failed to write to a router register. (Emulation package 8.1.0.00012)

The board is connected to a 5V, 3A power supply; the current display on the supply reads 0.3A when the board is connected and the supply activated.

  • Hi TorinCB,

    The only supported labs for IWR6843ISK-ODS are the ODS Point Cloud Lab and the ODS People Counting Lab.

    Are you still seeing this error when working through those labs?

    Cheers,

    Akash

  • Hi Akash,

    This lab works fine without trying to use Debug mode. My error is occurring when trying to connect to the target board through CCS in order to use Debug mode (before flashing the lab binary onto the board); it is not a problem with this lab.

    Additionally, the instructions for using Debug mode are identical on ODS Point Cloud Demo (for example), so yes, I still have a problem if I want to use that lab.

  • I fixed my problems as follows:

    To use Debug, the EVM needs to be physically configured to Development Mode: SOP0 must be open, and SOP1 and SOP2 must be closed. This is not documented in the Vital Signs lab manual, but it is in the reference manual for the MMWAVEICBOOST <http://www.ti.com/lit/ug/swru546b/swru546b.pdf> on page 22.

    This allows the targets to be connected simultaneously and the DSS and MSS binaries to be loaded.

    For the lab to execute successfully, both cores (Cortex R4 and C674X) need to begin execution simultaneously, so auto-run of each core upon program load must be disabled, as follows. Right-click the target configuration, click Edit <filename>, go to the Target tab, go to Auto Run and Launch Options, and uncheck On a program load or reset in the Auto Run Options section.