I am trying to connect a custom DM642 board to CCS 5.1.1.00031 running on a Win7 x64 machine. It is the first time trying to connect to this board, but I am using a custom GEL file that has worked with this board before (on another host).
I have no idea what a link-delay or a scan-path is in this context or how to fix them. The errors I get are below.
I searched far and wide but found few references to this error and no solutions.
I have used the eclipse "update" feature and I believe I have the latest drivers.
Any idea where I can start to try and fix this?
I get the following error when using "Test Connection":
-----------------------------------------------------------
[Start]
Execute the command:
%ccs_base%/common/uscif/dbgjtag.exe -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity
[Result]
-----[Print the reset-command software log-file]-----------------------------
This utility has selected a 100- or 510-class product.
This utility will load the adapter 'bhemujsc.dll'.
The library build date was 'Dec 19 2011'.
The library build time was '21:32:12'.
The library package version is '5.0.569.0'.
The library component version is '35.34.39.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '1' (0x00000001).
The controller has an insertion length of '16' (0x00000010).
This utility will now attempt to reset the controller.
This utility has successfully reset the controller.
-----[Print the reset-command hardware log-file]-----------------------------
The controller is of an unknown type.
The link from controller to target is direct (without cable).
The controller has a logic ONE on its EMU[0] input pin.
The controller has a logic ONE on its EMU[1] input pin.
The controller will use rising-edge 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 '-230' (0xffffff1a).
The title is 'SC_ERR_PATH_MEASURE'.
The explanation is:
The measured lengths of the JTAG IR and DR scan-paths are invalid.
This indicates that an error exists in the link-delay or scan-path.
[End]
-------------------------------------------------------
And this related error when trying to connect a debug session of CCS:
Error connecting to the target:
(Error -230 @ 0x0)
(Emulation package 5.0.569.0)
-------------------------------------------------
Looks like this is related to this post: http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/165627.aspx. It would have come up in my search if the error number or error message were int he post text instead of a screen cap.