• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 31 subscribers
  • Views 826 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Error Connecting to the target: (Error -1170 @0x0)

shraddha naik
Intellectual 370 points

Part Number: AM6442

Tool/software:

Hi,

I am facing the issue while loading the program via XDS110 USB debug port on AM64x EVM board (Green board).

Test connection results attached 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)]------------------------------------

C:\Users\z004dtbz\AppData\Local\TEXASI~1\
    CCS\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 'jioxds110.dll'.
The library build date was 'Jun  2 2023'.
The library build time was '12:47:07'.
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).

-----[Perform the Integrity scan-test on the JTAG IR]------------------------

This test will use blocks of 64 32-bit words.
This test will be applied just once.

Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.

The JTAG IR Integrity scan-test has succeeded.

-----[Perform the Integrity scan-test on the JTAG DR]------------------------

This test will use blocks of 64 32-bit words.
This test will be applied just once.

Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.

The JTAG DR Integrity scan-test has succeeded.

[End: Texas Instruments XDS110 USB Debug Probe_0]

Please do support to resolve the issue.

Regards

Shraddha

  • 0
    TI__Mastermind 44306 points

    Hi Shraddha,

    is this the first time you try this debug or did it work in the past?

    The connection test has no errors so your JTAG HW seems to work. Can you share the rest of the configuration (target config) and CCS version numbers. With above data I don't see a way to help.

    Regards, Frank

  • 0 in reply to Frank Walzer
    Intellectual 370 points

    Hello

    The error is resolved after changing the boot mode to OSPI. 

    But once i try to connect to the R5 core, it show DDR not intialised with R5 as shown below

     Next I tried to do DDR initialization, but it gets stuck at "Waiting for first frequency change request"

    Do support on this

    BR

    Shraddha

  • 0 in reply to shraddha naik
    TI__Mastermind 44306 points

    Hi Shradda,

    I just got informed I am still assigned to this topic although I am not the right expert. Is this issue still open? Then I can assign accordingly. But I wanted to check first if that is still required or if there is a new status. Thanks for a short update,.

    Regards, Frank