• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 53 subscribers
  • Views 3313 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/TM4C123FH6PM: CCS 9.3 debug probe error

Gary Richardson1
Prodigy 40 points
Part Number: TM4C123FH6PM
Other Parts Discussed in Thread: AM1802

Tool/software: Code Composer Studio

I want the XDS200 debug probe work with CCS version 9.3.0.

The issue:

Using CCS 9.3.0.00012 I try to load my project using debug and I get this warning:

Warning:
A firmware update is recommended for the XDS200 debug probe.
Click the "Update" button to update the firmware. Click the "Continue" button to continue without updating.
(Emulation package 8.4.0.00006)

If I click the update button it says this:

Error initializing emulator:
The XDS200 update cannot work if more than one XDS2xx probe is attached. Click "Cancel" then unplug the other XDS2xx probes and restart the debug session to update the firmware.
Click "Retry" to retry without doing the update.
(Emulation package 8.4.0.00006)

I do not have two XDS200 debuggers. If I unplug the one it says:

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.4.0.00006)

On a related note when I try to use the "loadti.bat" file I this error. In this case I do not know how to do a continue button with the scripting language.

SEVERE: CS_DAP_0: Error initializing emulator: The XDS200 update cannot work if more than one XDS2xx probe is attached. Click "Cancel" then unplug the other XDS2xx probes and restart the debug session to update the firmware.
Click "Retry" to retry without doing the update.
(Emulation package 8.4.0.00006)


SEVERE: Could not start server: DebugServer.1: CS_DAP_0: Error initializing emulator: The XDS200 update cannot work if more than one XDS2xx probe is attached. Click "Cancel" then unplug the other XDS2xx probes and restart the debug session to update the firmware.
Click "Retry" to retry without doing the update.
(Emulation package 8.4.0.00006)

  • 0
    TI__Guru**** 171104 points

    Hi, 

    Interesting; I haven't seen this issue before. Can you check if the Control Panel shows the correct entries as illustrated in the section Troubleshooting of the XDS200 page? That should give an idea on what may be going wrong. 

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

    You could also try to update the firmware by following the instructions shown in the sectino Updating the XDS200 firmware of the same page. 

    Hope this helps,

    Rafael

  • 0
    Prodigy 40 points

    I did follow the Updating the XDS200 firmware instructions and was able to update the XDS200. See session at bottom. However, now CCS is unable to connect to the target at all, see error message picture below. At least before I could click Continue and get past the error.

    I opened the .ccxml file and ran the test connection and that passed, see second picture below.

    C:\ti\ccs930\ccs\ccs_base\common\uscif\xds2xx>xds2xx_conf update xds2xxu 0 xds200_firmware_v1009.bin

    C:\ti\ccs930\ccs\ccs_base\common\uscif\xds2xx>xds2xx_conf program xds2xxu 0 xds220_cpld_iso_v1009.xsvf

    C:\ti\ccs930\ccs\ccs_base\common\uscif\xds2xx>xds2xx_conf boot xds2xxu 0

    C:\ti\ccs930\ccs\ccs_base\common\uscif\xds2xx>
    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-000E9903954D
    swRev=1.0.0.9
    hostCPU=AM1802
    emuCtrlType=Bit bang
    extMemType=SDRAM
    portUSB=true
    portENET=false
    portWIFI=false
    portRS232=false
    EnableUSBSerial=false
    CurrentMeasure=false

  • 0 in reply to Gary Richardson1
    Prodigy 40 points

    I rolled back to swRev 1.0.0.8 that came with CCS 9.20, see below. I do get the Continue button like I used to have, but still get the cannot connect error after that. Now I cannot load a program at all.

    C:\ti\ccs920\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-000E9903954D
    swRev=1.0.0.8
    hostCPU=AM1802
    emuCtrlType=Bit bang
    extMemType=SDRAM
    portUSB=true
    portENET=false
    portWIFI=false
    portRS232=false
    EnableUSBSerial=false
    CurrentMeasure=false

    [Start: Texas Instruments XDS2xx 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\BASEME~1\AppData\Local\TEXASI~1\
    CCS\ccs930\0\0\BrdDat\testBoard.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 'Nov 25 2019'.
    The library build time was '14:43:38'.
    The library package version is '8.4.0.00006'.
    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 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 XDS2xx USB Debug Probe_0]

  • 0 in reply to Gary Richardson1
    Prodigy 40 points

    I made the wrong translation from the CCS v8 instructions. I should have used "xds2xx_cpld_v1009.xsvf". In my previous post it shows I used "xds220_cpld_iso_v1009.xsvf". Therefore using the manual method proposed by desouza; "You could also try to update the firmware by following the instructions shown in the section Updating the XDS200 firmware of the same page." made the debugger work with ccs930.

    Not going to go retest it but downgrading to v1008 left me in worse shape on ccs930. Your mileage may vary.