• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 31 subscribers
  • Views 2087 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

jonathan vandamme
Prodigy 65 points
Other Parts Discussed in Thread: UNIFLASH

Hi,

I have been programming a RM57Lx launchpad for a few weeks now to evaluate the Hercules microcontrollers for a safety-critical application. Unfortunately, I can't connect to the board anymore. The issue once after I loaded the program and I was stepping through the code using the debugger. Could it be related to AJSM ?

CCS 6.1.1.00022 and UniFlash give me the following error when trying to connect:

Dap: Error connecting to the target: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 6.0.14.5)

The connection log gives me this:

[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\jo\AppData\Local\TEXASI~1\CCS\ti\
0\0\BrdDat\testBoard.dat

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

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'jioxds110.dll'.
The library build date was 'Sep 4 2015'.
The library build time was '21:59:23'.
The library package version is '6.0.14.5'.
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]

I have found this thread but it doesn't work for me:

https://e2e.ti.com/support/microcontrollers/hercules/f/312/t/264498

Thank you for your help.

Jonathan

  • 0
    TI__Guru 68950 points
    Jonathan,

    It could be related to AJSM but it is unusual for this type of problem to be an AJSM problem unless you knowingly tried to program the OTP of the device.

    Normally this is due to code that is put into the device, where the code does something that (unintentionally) disables JTAG like setting the clock frequency out of spec or causing some sort of fault in a tight loop.

    Try this next (of course with the board connected to your PC and powered on.)
    1) In CCS, View->Target Configurations
    2) In the target configurations tab that pops up, find the correct .ccxml for your target board.
    3) Right click on the CCXML and "Launch Selected Configuration".
    4) The "Debug" tab should open. You will see your CCXML file at the top of the tree. The next node down is the CPU/Emulator line with the Cortex R as a target.
    5) Right Click on the cortex R target line (with the X).
    6) From the context menu select "Show all Cores"
    7) You should see now that there are connections available to IcePickC and DAP under 'Non Debuggable Devices"
    8) Right click on IcePickC only and do a 'connect to target'.

    If you are able to connect to IcePickC then it's not AJSM but you've got some code in the device bricking the part. You can try to issue a System Reset (Debug->System Reset) with IcePickC selected and the other two devices still not 'connected' i.e. showing X. Then try connecting to the DAP just like you did with IcePick C. If these things work, you can try to connect to the cortex R. You may have to 'retry' a bunch of times like 10's or more times while pressing the 'reset' (not Power on Reset) button.
  • 0 in reply to Anthony F. Seely
    Prodigy 65 points
    Mr. F. Seely,

    Thank you for your detailed answer. I went through the actions you recommended and I was able to connect with the IcePick and the DAP, thus ruling out any AJSM problem. I then tried to connect to the target while pressing the reset button and I was able after maybe a hundred tries to succesfully connect to the cortex R and erase the flash.

    Best regards,

    Jonathan
  • 0 in reply to jonathan vandamme
    TI__Guru 68950 points
    Hi Jonathan,

    I'm so glad you were able to connect finally. When there is bad code in the flash - the timing window to can be really short and it's hard to 'hit'. Thanks for not giving up after the first 99 trials ;)

    Best Regards,
    Anthony