[FAQ] PROCESSOR-SDK-AM64X: Error connecting to the target from CCS 10.4.0.00006 on TMDS64GPEVM

Howard Egan

Hi:

I would have tagged onto these other two threads, but I have slightly different error messages.

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1020036/sk-am64-error-connecting-to-the-target-from-ccs-10-3-1

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1028477/processor-sdk-am64x-am64x-eval-board---debugger-failure/3805074#3805074

EVM rev PROC101A (001)

I followed every step in this document to the letter, on Ubuntu 18.04

https://software-dl.ti.com/mcu-plus-sdk/esd/AM64X/08_00_00_21/exports/docs/api_guide_am64x/GETTING_STARTED.html

Two things I noticed that seemed slightly out of the ordinary is that:

for the uart to work on Ubuntu, you have to chmod 666 /dev/ttyUSB0
The version of CCS specified in the Getting Started manual (10.3.1) is not available, it is now 10.4

Anyhow the bootloader progamming all worked and in CCS I got this on the terminal:

Starting NULL Bootloader ...

DMSC Firmware Version 21.5.0--v2021.05 (Terrific Llam
DMSC Firmware revision 0x15
DMSC ABI revision 3.1

INFO: Bootloader_runCpu:147: CPU r5f1-0 is initialized to 800000000 Hz !!!
INFO: Bootloader_runCpu:147: CPU r5f1-1 is initialized to 800000000 Hz !!!
INFO: Bootloader_runCpu:147: CPU m4f0-0 is initialized to 400000000 Hz !!!
INFO: Bootloader_runCpu:147: CPU a530-0 is initialized to 800000000 Hz !!!
INFO: Bootloader_runCpu:147: CPU a530-1 is initialized to 800000000 Hz !!!
INFO: Bootloader_loadSelfCpu:199: CPU r5f0-0 is initialized to 800000000 Hz !!!
INFO: Bootloader_loadSelfCpu:199: CPU r5f0-1 is initialized to 800000000 Hz !!!
INFO: Bootloader_runSelfCpu:216: All done, reseting self ...

When I launch the configuration, I get this error after a long wait:

CS_DAP_0: Error initializing emulator: (Error -260 @ 0x0) An attempt to connect to the XDS110 failed. The cause may be one or more of: no XDS110 is connected, invalid firmware update, invalid XDS110 serial number, or faulty USB cable. The firmware and serial number may be updated using the xdsdfu utility found in the .../ccs_base/common/uscif/xds110 directory of your installation. View the XDS110SupportReadMe.pdf file there for instructions. (Emulation package 9.4.0.00129)

Retrying yields same result, but immediately.

I read and tried the workaround here:

https://www.ti.com/lit/ug/spruix0d/spruix0d.pdf?ts=1629821780669&ref_url=https%253A%252F%252Fe2e.ti.com%252F

However, it never works.

Pretty much stuck at this point.

Thank you

Howard

over 2 years ago

0 Howard Egan over 2 years ago

Intellectual 462 points

Sorry there was one more thing out of the ordinary during the install process of CCS.

This:

Selection was not the same in CCS 10.4. Selected selection was this:

0 Howard Egan over 2 years ago in reply to Howard Egan

Intellectual 462 points

Also I read the XDS110 support notes.

Should I expect this to work:

:~/ti/ccs1040/ccs/ccs_base/common/uscif/xds110$ ./xds110reset
ERROR: Failed to connect to XDS110 (-260).
Check USB connection to the XDS110

I see the XDS110 as a USB device

0 Howard Egan over 2 years ago in reply to Howard Egan

Intellectual 462 points

Ughh, ok so I found the issues. Again its in the documentation ... this time in the CCS installation instructions.

This little tidbit is missing:

https://software-dl.ti.com/ccs/esd/documents/ccsv10_linux_host_support.html#ubuntu-20-04-lts

Specifically:

if CCS was installed as user then run the driver install script

go to <CCS_INSTALL_DIR>/ccs/install_scripts
sudo ./install_drivers.sh

which is very disappointing since its been known for more than a year as this thread indicates:

e2e.ti.com/.../3373284

0 Nick Saulnier over 2 years ago in reply to Howard Egan

TI__Guru* 78855 points

Hello Howard,

Glad you got it working. Sending your thread to the CCS team to see if they have anything to add.

CCS folks: once yall are done, please send back to the business unit so we can submit a bug fix on the SDK documentation.

Regards,

Nick

+1 Ki over 2 years ago in reply to Nick Saulnier

TI__Guru**** 430120 points

The instructions to run the install_drivers script should appear after CCS has been successfully installed:

However, I can see how this can be missed - especially when using the GUI-less silent installation. We can explore making this message more obvious.

Thanks

+1 Howard Egan over 2 years ago in reply to Ki

Intellectual 462 points

Ok, I definitely did not see that. I was blindly following the installation doc, so I could have just missed it. So it would be best if that step was in the doc, especially since everything else is.

Processors

Processors forum

[FAQ] PROCESSOR-SDK-AM64X: Error connecting to the target from CCS 10.4.0.00006 on TMDS64GPEVM