TDA4VM: When using Code Composer Studio (CCS), if the XDS110 emulator fails to successfully connect to the target device, what potential issues might exist in this scenario?

Hi,

?? ? said:

When I don't load the gel file and try to connect directly to M3, it still fails to connect. Below are the files you mentioned.

launch.zip

Can you please share the device type you are using?  Is it GP, HS-SE?
If it is HS-SE by default, debug prot is not enabled, so unlock JTAG before use.

Please refer to FAQs:
To check device type: [FAQ] TDA4VM: How to check device type (GP/HS-FS/HS-SE) ?
To unlock JTAG: [FAQ] J721S2XSOMXEVM: How to unlock the JTAG using TISCI API ?

Best Regards,
Sudheer

Dear Sudheer

The captured serial port information shows the device type as GP. Does this type still require unlocking the JATG?

Hi,

?? ? said:

The captured serial port information shows the device type as GP. Does this type still require unlocking the JATG?

No, for the GP device, you need to unlock JTAG.

Most likely, the issue is with the drivers of the debugger.
Have you installed the drivers? If not, please follow the release notes, as pointed out in the RTOS SDK documentation.


Can you also check by running the test connection from CCS?


Best Regards,
Sudheer

Dear Sudheer

When i  running the test connection from CCS,

this is the error as below.

[Start: Texas Instruments XDS110 USB Debug Probe_0]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

[Result]

-----[Print the board config pathname(s)]------------------------------------

/home/ubuntu/.ti/ccs1240/0/0/BrdDat/testBoard.dat

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 100/110/510 class product.
This utility will load the adapter 'libjioxds110.so'.
The library build date was 'Jun 2 2023'.
The library build time was '12:44:02'.
The library package version is '9.12.0.00150'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '5' (0x00000005).
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 XDS110 with USB interface.
The link from controller to target is direct (without cable).
The software is configured for XDS110 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 has occurred and this utility has aborted]--------------------

This error is generated by TI's USCIF driver or utilities.

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

The explanation is:
The JTAG IR and DR scan-paths cannot circulate bits, they may be broken.
An attempt to scan the JTAG scan-path has failed.
The target's JTAG scan-path appears to be broken
with a stuck-at-ones or stuck-at-zero fault.

[End: Texas Instruments XDS110 USB Debug Probe_0]

Hi,

Can you please check by lowering the JTAG clock?


If the issue persists, could you please check with your hardware team regarding signaling?
Also, refer to the troubleshooting guide: https://software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/emu_xds110.html

Best Regards,
Sudheer

I have verified that DMSC_M3 can successfully connect, but C66xx_ fails to connect. Does connecting to the DSP SoC require additional configuration?

Now I can successfully connect to the core and am currently developing on C66. The vx_app_rtos_linux_c6x_1.out has been loaded, but it fails to run properly and gets stuck in the OS_init() function. I would like to ask: Can the C66 core run independently? Does it need to work in conjunction with other MCUs?