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.
仿真器驱动已装好,仿真器,型号选择也正确(TMS320F2809),电源正常,ccs8.3.1版本,连接目标板时提示如下错误
[Start: SEED XDS510PLUS Emulator_0]
Execute the command:
%ccs_base%/common/uscif/dbgjtag.exe -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity
[Result]
-----[Print the board config pathname(s)]------------------------------------
C:\Users\123\AppData\Local\TEXASI~1\CCS\
ti\2\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 'seedjca8990isa.dll'.
The library build date was 'Apr 30 2019'.
The library build time was '14:17:18'.
The library package version is '8.1.0.00012'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.
An error occurred while hard opening the controller.
ffff 5ac3
ffff a53c
ffff 0f0f
ffff 3ca5
ffff c35a
-----[An error has occurred and this utility has aborted]--------------------
This error is generated by TI's USCIF driver or utilities.
The value is '-342' (0xfffffeaa).
The title is 'SC_ERR_HUNG_COMMAND'.
The explanation is:
Failure due to the controller command-finish taking too long.
[End: SEED XDS510PLUS Emulator_0]
这是什么原因,怎么解决?谢谢!
是自制版,PC上xds510,xds100都能正常识别, 我用xds100 v2 也不行,故障提示如下;
[Start: Texas Instruments XDS100v2 USB Debug Probe_0]
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\123\AppData\Local\TEXASI~1\CCS\
ti\2\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 'jioserdesusb.dll'.
The library build date was 'Apr 30 2019'.
The library build time was '14:17:18'.
The library package version is '8.1.0.00012'.
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 '-150' (0xffffff6a).
The title is 'SC_ERR_FTDI_FAIL'.
The explanation is:
One of the FTDI driver functions used during
configuration returned a invalid status or an error.
[End: Texas Instruments XDS100v2 USB Debug Probe_0]