Other Parts Discussed in Thread: TDA4VM
I am trying to use usb560v2 system trace to debug tda4vm through JTAG interface.
The JTAG interface of tda4vm is 14 pins.
1) The error when trying to connect through CCS(Version 9.3.0) is SC_ERR_CTL_CBL_BREAK_FAR
I attach an error message：
[Start: Blackhawk XDS560v2-USB System Trace Emulator_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)]------------------------------------
/home/zhh/.ti/ccs930/0/0/BrdDat/testBoard.dat
-----[Print the reset-command software log-file]-----------------------------
This utility has selected a 560/2xx-class product.
This utility will load the program 'libbh560v2u.out'.
Loaded FPGA Image: /home/zhh/ti/ccs930/ccs/ccs_base/common/uscif/./././././dtc_top.jbc
The library build date was 'Nov 25 2019'.
The library build time was '14:08:22'.
The library package version is '8.4.0.00006'.
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.
-----[An error has occurred and this utility has aborted]--------------------
This error is generated by TI's USCIF driver or utilities.
The value is '-183' (0xffffff49).
The title is 'SC_ERR_CTL_CBL_BREAK_FAR'.
The explanation is:
The controller has detected a cable break far-from itself.
The user must connect the cable/pod to the target.
[End: Blackhawk XDS560v2-USB System Trace Emulator_0]
2) However, under all conditions unchanged, TI's EVM can be successfully connected.
3) When other debugging conditions remain unchanged, replacing xds110 debugger can successfully connect tda4vm.
