• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 54 subscribers
  • Views 1004 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.

CCS/AM5728: Error -2085 @ 0x0 when trying to connect with the target with XDS200 emulator

Jam psym
Prodigy 140 points
Part Number: AM5728
Other Parts Discussed in Thread: AM1802, BEAGLEBOARD-X15

Tool/software: Code Composer Studio

Hi experts,

after trying to launch debug session just with .ccxml configuration file (as XDS2xx USB Debug Probe and evmAM572x) I've got either:

Error initializing emulator:
(Error -2085 @ 0x0)
Internal error: Missing or corrupt application file. Restart the application. If error persists, please report the error.
(Emulation package 8.4.0.00006)

or

Error initializing emulator:
(Error -2083 @ 0x0)
Unable to communicate with the debug probe. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation.
(Emulation package 8.1.0.00012)

errors.

The Test Connection button to determine whether your JTAG connection is working at the lowest level gives:

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

This utility has successfully reset the controller.
...
The JTAG IR Integrity scan-test has succeeded.
...
The JTAG DR Integrity scan-test has succeeded.

What I have done already:

- Updating the XDS200 firmware

c:\ti\ccs930\ccs\ccs_base\common\uscif\xds2xx>xds2xx_conf get xds2xxu 0
boardRev=1
ipAddress=0.0.0.0
ipConfig=dhcp
ipGateway=0.0.0.0
ipNetmask=0.0.0.0
productClass=XDS2XX
productName=XDS200
serialNum=S200-000E990464D0
swRev=1.0.0.9
hostCPU=AM1802
emuCtrlType=Bit bang
extMemType=SDRAM
portUSB=true
portENET=false
portWIFI=false
portRS232=false
EnableUSBSerial=false
CurrentMeasure=false

- reinstalled the Windows device drivers

- reductin JTAG clock to 1MHz

- different usb ports, cables etc...

as suggested in troubleshooting guides.

Also it worked once after degrading to CCS 8.3 but 1 hout later when I compiled pdk to this version it stoped working and problem persists.

Do you have any solution for that?

  • 0
    Prodigy 140 points

    I tried with CCS10 CCS9.3 CCS9.1 and CCS8.1(where it connected once)

  • 0
    Prodigy 140 points

    I tried with another xds200 and the problem persists.

  • 0 in reply to Jam psym
    TI__Guru**** 171044 points

    Hi,

    I just tested this scenario but couldn't reproduce it.

    The emulation package software shown in the second error message (8.1.0.00012) has the firmware version 1.0.0.8, which should work with several prior CCS versions (9.1, 8.1). 

    The first message is expected if you try to connect using the newer versions (10, 9.3), since the emulation package software (8.4.0.00006) features the newer firmware version 1.0.0.9.

    Therefore, I am unsure what to try, apart from the manual procedure shown in the XDS200 page at:

    https://software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/emu_xds200.html 

    Can you try that and see if it works with the newest versions?

    Regards,

    Rafael

  • 0 in reply to desouza
    Prodigy 140 points

    Thanks for your reply.

    So I tried again after installing RMUPack 9.1.0.00001 into ccs10 and I've got: (I use ccs10 to do this)

    Error initializing emulator:
    (Error -2085 @ 0x0)
    Internal error: Missing or corrupt application file. Restart the application. If error persists, please report the error.
    (Emulation package 9.1.0.00001)

    and also with this:

    C:\ti\ccs1000\ccs\ccs_base\common\uscif\xds2xx>xds2xx_conf get xds2xxu 0
    boardRev=1
    ipAddress=0.0.0.0
    ipConfig=dhcp
    ipGateway=0.0.0.0
    ipNetmask=0.0.0.0
    productClass=XDS2XX
    productName=XDS200
    serialNum=S200-000E990464D0
    swRev=1.0.0.9
    hostCPU=AM1802
    emuCtrlType=Bit bang
    extMemType=SDRAM
    portUSB=true
    portENET=false
    portWIFI=false
    portRS232=false
    EnableUSBSerial=false
    CurrentMeasure=false


    If this is relevant it is beaglebone X15 board version and it worked just fine one year ago with the same emulator.

  • 0 in reply to Jam psym
    TI__Guru**** 171044 points

    Hi,

    Jam psym said:
    If this is relevant it is beaglebone X15 board version and it worked just fine one year ago with the same emulator.

    I now suspect what it is: the BeagleBone X15 board has a watchdog tied to the PMIC that powers off the board during the debug launch, which can render very random errors during the connection. This is covered at the post below:

    https://e2e.ti.com/support/processors/f/791/p/768826/2844272

    One additional detail: do you have Linux running on the board? If so, sometimes it may either power down the debug subsystem or disallow any JTAG access to the Cortex A15 core. In this case, the tips shown at the thread above can be helpful to try to connect to a board without MLO/U-boot disabling the watchdog. 

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Prodigy 140 points

    Hi,

    there is a default linux image on eMMC which starts after powering up the board. Last time I used the board it was enough to start a debug session and pushing the restart button in the same time. 

    The problem persists if I short J5 (PMIC can't power down the board).

    So as I understand the only option left is to try change Boot strapping not to boot from eMMC? I'm afraid that I won't be able to desolder those tiny resistors :/

    Thank you for your help anyway!

    Maybe the last thing I noticed is that: before uploading the firmware to XDS200 (if emulator was plugged in) the board powered off after few seconds but after changing the firmware it boots with linux (if emulator was plugged in). And the error had appeared even before the board turned off.

    Testing stability of JTAG connection turns out as OK:

    stability of your XDS200 JTAG connection

    C:\ti\ccs1000\ccs\ccs_base\common\uscif>dbgjtag -f ccBoard0.dat -rv -Sgivendata,repeat=0

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

    ccBoard0.dat

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

    This utility has selected a 560/2xx-class product.
    This utility will load the program 'xds2xxu.out'.
    The library build date was 'Feb 13 2020'.
    The library build time was '17:48:35'.
    The library package version is '9.1.0.00001'.
    The library component version is '35.35.0.0'.
    The controller does not use a programmable FPGA.
    The controller has a version number of '13' (0x0000000d).
    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]-----------------------------

    This emulator does not create a reset log-file.

    -----[Perform the Given Data scan-test on the JTAG IR]-----------------------

    This test will use blocks of 64 32-bit words.
    This test will be applied forever.
    It uses all of the 10 different test-cases.

    Do a test using 0x5533CCAA.
    Scan tests: 341, skipped: 0, failed: 0^C

  • 0 in reply to Jam psym
    Guru 92251 points

    Jam psym said:
    there is a default linux image on eMMC which starts after powering up the board. Last time I used the board it was enough to start a debug session and pushing the restart button in the same time. 

    What I have done with the BeagleBoard-X15 in the past was:

    a. Connect to the serial debug connector.

    b. Power on, or reset the board, while watching the serial port output.

    c. Press any key when U-Boot say "press any key to stop autoboot"

    d. With U-Boot stopped at the prompt, i.e. before Linux has been loaded, you can connect with the debugger without the PMIC from powering off the board.

    That was with a rev A2 BeagleBoard-X15 when using a BH-USB-560M debug probe.