TMDS64EVM: Error connecting to the target: Error -2081

Owen Murphy

Part Number: TMDS64EVM
Other Parts Discussed in Thread: UNIFLASH, TMDSEMU110-U

Hello,

I am having trouble loading a program on the AM64x eval board (TMDS64EVM). I receive the follow error message when I try to flash the chip:

CortexA53_0: Error connecting to the target: (Error -2081 - (0:0:0)) Device functional clock appears to be off. Power-cycle the board. If error persists, confirm configuration and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.11.0.00128)

I have tried reducing the JTAG clock speed from 5.5MHz to 1MHz and to 100kHz. I have also tried using each of the modes listed in the "JTAG / SWD / cJTAG Mode" drop down.

I am using Code Composer Studio, version 12.3.0.00005. I am trying to load the "gpio_led_blink_am64x-evm_m4fss0-0_nortos_ti-arm-clang" example project. I am able to build the project without any errors, but it fails when I try to load it.

I am using the onboard XDS110 USB debugger. It passes the "Test Connection" JTAG DR Integrity scan-test.

Do you have any recommendations?

over 2 years ago

0 Anshu Choudhary over 2 years ago

TI__Genius 12330 points

owen

can you please confirm that you have followed the EVM Setup instructions specified here https://software-dl.ti.com/mcu-plus-sdk/esd/AM64X/08_05_00_24/exports/docs/api_guide_am64x/EVM_SETUP_PAGE.html

Also can you please specify the Bootmode you are using.

Regards

Anshu

0 Owen Murphy over 2 years ago in reply to Anshu Choudhary

Prodigy 45 points

Hello Anshu,

Thanks for the reply. I followed the setup instruction up until the "Flash SOC Initialization Binary" section. I confirmed the UART communication, and set the boot mode dip switches to "UART Boot Mode" (SW's 0, 1, 3, 4, 5, 8, 10, 11 are up, SW's 2, 6, 7, 9, 13, 14, 15 are down). I am able to receive the "C" character over UART to confirm the boot mode.

However, when I run:

python uart_uniflash.py -p COM<x> --cfg=sbl_prebuilt/am64x-evm/default_sbl_null.cfg

I get the following error:

[ERROR] XMODEM send failed, no response OR incorrect response from EVM OR cancelled by user

0 Nitika Verma over 2 years ago in reply to Owen Murphy

TI__Expert 7385 points

Hi Owen,

You can refer to the below FAQ on steps needed to flash SOC initialization binaries on TMDS64EVM:

[FAQ] AM64X: How can I flash SOC initialization binaries on HS - FS HW versions . - Processors forum - Processors - TI E2E support forums

Please let me know if it helps your query.

Regards,

Nitika

0 Owen Murphy over 2 years ago in reply to Nitika Verma

Prodigy 45 points

Hi Nitika,

I performed the steps listed in the forum post that you sent, and I was able to successfully run the "uart_uniflash.py" script. However, I am unable to run the next steps in the EVM setup guide. I changed the boot mode DIP switches to "OSPI BOOT MODE" (SW's 0, 1, 3, 4, 5, 8, 10, 11 are UP, SW's 2, 6, 7, 9, 12, 13, 14, 15 are DOWN), but when I power on the EVM with the terminal open, I do not receive any message (ie "Starting NULL Bootloader ...").

When I try to test the JTAG connection in CCS using the .ccxml file, I receive the following error:

[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)]------------------------------------

C:\Users\owenf\AppData\Local\TEXASI~1\CCS\
    ccs1230\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 'jioxds110.dll'.
The library build date was 'Mar 10 2023'.
The library build time was '17:27:27'.
The library package version is '9.11.0.00128'.
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]

Also, I am now unable to run the "uart_uniflash.py" script. I receive the following error:

PS C:\ti\mcu_plus_sdk_am64x_08_05_00_24\tools\boot> python uart_uniflash.py -p COM7 --cfg=sbl_prebuilt/am64x-evm/default_sbl_null.cfg

Parsing config file ...
Parsing config file ... SUCCESS. Found 2 command(s) !!!

Executing command 1 of 2 ...
Found flash writer ... sending sbl_prebuilt/am64x-evm/sbl_uart_uniflash.release.hs_fs.tiimage
Sending sbl_prebuilt/am64x-evm/sbl_uart_uniflash.release.hs_fs.tiimage:   0%| | 2/297306 [01:50<9093:47:11, 110.12s/byt
[ERROR] XMODEM send failed, no response OR incorrect response from EVM OR cancelled by user,
Power cycle EVM and run this script again !!!

Finally, before I successfully ran the "uart_uniflash.py" script, there were several LEDs on the EVM that turned on whenever the board was powered on. These LEDs are no longer turned on.

0 Nitika Verma over 2 years ago in reply to Owen Murphy

TI__Expert 7385 points

Hi Owen,

Owen Murphy said:
When I try to test the JTAG connection in CCS using the .ccxml file, I receive the following error

This is a low level JTAG connectivity error, usually caused due to some hardware issue. Please check if your JTAG and power cables are connected properly, see the below link for more details and suggestions on how to resolve it:

https://software-dl.ti.com/ccs/esd/documents/ccs_debugging_jtag_connectivity_issues.html#:~:text=the%20search%20path.-,Invalid%20data%20read%20back

Additionally, can you remove the JTAG cable, power on the board and let me know if the LEDs on the EVM turn on.

Regards,

Nitika

0 Owen Murphy over 2 years ago in reply to Nitika Verma

Prodigy 45 points

When I power up the EVM without the JTAG usb cable connected, the LEDs still do not turn on.

I have an AM243x EVM on order, and I will try to program that board when it arrives, since this board might be damaged in some way, according the errors.

0 Nitika Verma over 2 years ago in reply to Owen Murphy

TI__Expert 7385 points

Hi Owen,

Do let me know if you still face the above errors with the new board.

Regards,

Nitika

0 Owen Murphy over 2 years ago in reply to Nitika Verma

Prodigy 45 points

Hello Nitika,

I purchased AM243x EVM and AM243x LP eval boards and tried to run through the setup guide, but I was unsuccessful with both boards.
https://software-dl.ti.com/mcu-plus-sdk/esd/AM243X/latest/exports/docs/api_guide_am243x/GETTING_STARTED.html

With the AM243x EVM, I received the following error:

PS C:\ti\mcu_plus_sdk_am243x_08_05_00_24\tools\boot> python uart_uniflash.py -p COM14 --cfg=sbl_prebuilt/am243x-evm/default_sbl_null.cfg

Parsing config file ...
Parsing config file ... SUCCESS. Found 2 command(s) !!!

Executing command 1 of 2 ...
Found flash writer ... sending sbl_prebuilt/am243x-evm/sbl_uart_uniflash.release.tiimage
Sent flashwriter sbl_prebuilt/am243x-evm/sbl_uart_uniflash.release.tiimage of size 316052 bytes in 32.29s.

Executing command 2 of 2 ...
Command arguments : --file=sbl_prebuilt/am243x-evm/sbl_null.release.tiimage --operation=flash --flash-offset=0x0
Sending sbl_prebuilt/am243x-evm/sbl_null.release.tiimage:   1%|              | 2058/269684 [00:02<12:21, 361.13bytes/s]send error: expected ACK; got b'\x18' for block 2
Sending sbl_prebuilt/am243x-evm/sbl_null.release.tiimage:   1%|▏            | 3087/269684 [00:03<03:29, 1270.78bytes/s]send error: expected ACK; got b'\x18' for block 2
Sending sbl_prebuilt/am243x-evm/sbl_null.release.tiimage:   2%|▏            | 4116/269684 [00:03<03:28, 1270.78bytes/s]send error: expected ACK; got b'0' for block 2
Sending sbl_prebuilt/am243x-evm/sbl_null.release.tiimage:   2%|▏            | 5145/269684 [00:03<03:28, 1270.78bytes/s]send error: expected ACK; got b'2' for block 2
Sending sbl_prebuilt/am243x-evm/sbl_null.release.tiimage:   2%|▎            | 6174/269684 [00:03<01:27, 3015.52bytes/s]send error: expected ACK; got b'0' for block 2
Sending sbl_prebuilt/am243x-evm/sbl_null.release.tiimage:   3%|▎            | 7203/269684 [00:03<01:27, 3015.52bytes/s]send error: expected ACK; got b'0' for block 2
Sending sbl_prebuilt/am243x-evm/sbl_null.release.tiimage:   3%|▍            | 8232/269684 [00:03<01:03, 4144.04bytes/s]send error: expected ACK; got b'0' for block 2
Sending sbl_prebuilt/am243x-evm/sbl_null.release.tiimage:   3%|▍            | 9261/269684 [00:03<01:02, 4144.04bytes/s]send error: expected ACK; got b'0' for block 2
Sending sbl_prebuilt/am243x-evm/sbl_null.release.tiimage:   4%|▍           | 10290/269684 [00:03<00:48, 5363.24bytes/s]send error: expected ACK; got b'0' for block 2
Sending sbl_prebuilt/am243x-evm/sbl_null.release.tiimage:   4%|▌           | 11319/269684 [00:03<00:48, 5363.24bytes/s]send error: expected ACK; got b'0' for block 2
Sending sbl_prebuilt/am243x-evm/sbl_null.release.tiimage:   5%|▌           | 12348/269684 [00:03<00:39, 6458.67bytes/s]send error: expected ACK; got b'0' for block 2
send error: NAK received 11 times, aborting.
Sending sbl_prebuilt/am243x-evm/sbl_null.release.tiimage:   5%|▌           | 12350/269684 [00:03<00:39, 6458.67bytes/s]
[ERROR] XMODEM send failed, no response OR incorrect response from EVM OR cancelled by user,
Power cycle EVM and run this script again !!!

With the AM243x LP board, I received the following error:

PS C:\ti\mcu_plus_sdk_am243x_08_05_00_24\tools\boot> python uart_uniflash.py -p COM4 --cfg=sbl_prebuilt/am243x-lp/default_sbl_null.cfg

Parsing config file ...
Parsing config file ... SUCCESS. Found 2 command(s) !!!

Executing command 1 of 2 ...
Found flash writer ... sending sbl_prebuilt/am243x-lp/sbl_uart_uniflash.release.tiimage
Sent flashwriter sbl_prebuilt/am243x-lp/sbl_uart_uniflash.release.tiimage of size 294772 bytes in 28.7s.

Executing command 2 of 2 ...
Command arguments : --file=sbl_prebuilt/am243x-lp/sbl_null.release.tiimage --operation=flash --flash-offset=0x0
Sending sbl_prebuilt/am243x-lp/sbl_null.release.tiimage:   0%|                           | 0/258683 [00:00<?, ?bytes/s]send error: expected NAK, CRC, EOT or CAN; got b'0'
send error: expected NAK, CRC, EOT or CAN; got b'2'
send error: expected NAK, CRC, EOT or CAN; got b'0'
send error: expected NAK, CRC, EOT or CAN; got b'0'
send error: expected NAK, CRC, EOT or CAN; got b'0'
send error: expected NAK, CRC, EOT or CAN; got b'0'
send error: expected NAK, CRC, EOT or CAN; got b'0'
send error: expected NAK, CRC, EOT or CAN; got b'0'
send error: expected NAK, CRC, EOT or CAN; got b'0'
send error: expected NAK, CRC, EOT or CAN; got b'1'
send error: expected NAK, CRC, EOT or CAN; got b'1'
Sending sbl_prebuilt/am243x-lp/sbl_null.release.tiimage:   0%|               | 2/258683 [00:01<143:05:31,  1.99s/bytes]
[ERROR] XMODEM send failed, no response OR incorrect response from EVM OR cancelled by user,
Power cycle EVM and run this script again !!!

I also tried to boot the AM243 EVM board using the SD card, following these steps:

https://software-dl.ti.com/mcu-plus-sdk/esd/AM243X/latest/exports/docs/api_guide_am243x/EVM_SETUP_PAGE.html#EVM_SOC_INIT_SD_BOOT_MODE

However, I when I powered on the EVM, I did not receive any message in the terminal. I only received this character "Þ" immediately after booting, then nothing.

Is this an issue on your end or on my end?

0 Owen Murphy over 2 years ago in reply to Owen Murphy

Prodigy 45 points

Also, I have an external XDS110 Debug probe (TMDSEMU110-U). Can I use this to program the IC, without having to go through these "setup" steps? On paper, the AM243x series is exactly what I need, but I don't know if I can use it simply because I can't get any of the eval boards working.

0 Nitika Verma over 2 years ago in reply to Owen Murphy

TI__Expert 7385 points

Hi Owen,

Since you have moved to AM243x and AM243x LP board, I request you to create a separate query for this so it can be tracked accordingly.

Regards,

Nitika