• State
  • Locked Locked
  • Replies 10 replies
  • Subscribers 17 subscribers
  • Views 6027 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.

XDS110 fails after latest XDS Emulation Package update

Thomas Treyer
Prodigy 240 points
Other Parts Discussed in Thread: CC2640, CC2650STK, CC2650

Today I got an update in CCS for the Emulator package, new version is 6.0.83.0.

Today I experienced massive problems with the XDS110 and my custom board. When trying to download my code to the CC2640 I get the following error message:

Error connecting to the target: (Error -1265 @ 0x0) Device ID is not recognized or is not supported by driver. Confirm device and debug probe configuration is correct, or update device driver. (Emulation package 6.0.83.0).

Resetting the target device and disconnecting/reconnecting the USB cable does not help. I checked all puls forms of TDO TDI TCK and TMS, everything seems to be ok. The XDS110 connects shortly via JTAG to the CC2640 at my board and then the error message appears.

Any help?

  • 0
    Guru 735685 points
    Try to use the follow these steps to set serial number to your XDS110.

    1) Plug the XDS110 debug probe into your computer. Make sure that you
    only have one XDS110 class debug probe plugged in. The xdsdfu program
    will attempt to flash the first XDS110 debug probe it finds.

    2) Run the following two commands from this directory:

    xdsdfu -m
    xdsdfu -s xxxxxxxx -r

    where xxxxxxxx is a serial number. Remember to use numbers from 0 to 9.
  • 0 in reply to YiKai Chen
    Prodigy 240 points

    It was not possible to change the serial number. I am able to enumerate the USB devices using .\xdsdfu.exe -e

    PS C:\TI\ccsv6\ccs_base\common\uscif\xds110> .\xdsdfu.exe -e

    USB Device Firmware Upgrade Utility
    Copyright (c) 2008-2015 Texas Instruments Incorporated.  All rights reserved.

    Scanning USB buses for supported XDS110 devices...


    <<<< Device 0 >>>>

    VID: 0x1cbe    PID: 0x00ff
    Device Name:   Tiva Device Firmware Update
    Manufacturer:  Texas Instruments Incorporated
    Serial Num:    00000000
    Mode:          DFU

    Found 1 device.

    I can switch the XDS110 to DFU mode:

    PS C:\TI\ccsv6\ccs_base\common\uscif\xds110> .\xdsdfu.exe -m

    USB Device Firmware Upgrade Utility
    Copyright (c) 2008-2015 Texas Instruments Incorporated.  All rights reserved.

    Scanning USB buses for supported XDS110 devices...


    <<<< Device 0 >>>>

    VID: 0x0451    PID: 0xbef3
    Device Name:   XDS110 with CMSIS-DAP
    Version:       2.2.5.1
    Manufacturer:  Texas Instruments
    Serial Num:    00000000
    Mode:          Runtime

    Switching device into DFU mode.

    But in DFU mode I cannot change the serial number nor can I update the firmware:

    PS C:\TI\ccsv6\ccs_base\common\uscif\xds110> .\xdsdfu.exe -s 1601 -r

    USB Device Firmware Upgrade Utility
    Copyright (c) 2008-2015 Texas Instruments Incorporated.  All rights reserved.

    Scanning USB buses for supported XDS110 devices...

    The requested device was not found on the bus.

    The only way to leave DFU mode ist to disconnect / reconnect the USB cable.

    Any idea / help welcome.

  • 0 in reply to Thomas Treyer
    Guru 735685 points
    The serial number has to be 8 digits. Please try "xdsdfu.exe -s 87654321 -r".
  • 0 in reply to YiKai Chen
    Prodigy 240 points

    Hi Chen,

    your advice helped me to enter a serial number, thank you. I am able to flash the firmware of the XDS110, too. But my problem is still unsolved. I cannot flash my board.

    I tried to downgrade the XDS110 firmware to the old version, but CCS refused to work with it and requested me to upgrade the XDS110 firmware again.

    In my opinion the problem is not the USB communication from the PC to the XDS110. I think the problem is the communication between the XDS110 firmware and the CC2640 located at my board.

    The error number reported by CCS has changed:

    Error connecting to the target:

    (Error -242 @ 0x0)

    A router subpath could not be accessed.

    The board configuration file is probably incorrect.

    (Emulation package 6.0.83.0)

    This error message points to the board configuration file, which file is meant here? is it the board.h file referenced by main.c in my code?

  • 0 in reply to Thomas Treyer
    Guru 735685 points
    Try the following steps:
    1. Disconnect CC2650STK from CC-DEVPACK-DEBUGGER and remove battery on CC2650STK.
    2. Disconnect USB connection between PC and CC-DEVPACK-DEBUGGER.
    3. Connect USB between PC and CC-DEVPACK-DEBUGGER.
    4. Connect CC2650STK to CC-DEVPACK-DEBUGGER.
    5. Use CCS to download and debug CC2650STK.
  • 0 in reply to YiKai Chen
    Prodigy 240 points
    I followed your steps 2 times. In both cases I had no success, but got a new error message:

    Error connecting to the target:
    (Error -1265 @ 0x0)
    Device ID is not recognized or is not supported by driver. Confirm device and debug probe configuration is correct, or update device driver.
    (Emulation package 6.0.83.0)

    My next step is to order an XDS100v3. Do you think this might helpful?
  • 0 in reply to Thomas Treyer
    Guru 735685 points
    Do you use your own customize CC2640 PCB?
  • 0 in reply to YiKai Chen
    Prodigy 240 points
    Yes, it is the target PCB of our product. I was able to use the XDS110 by connecting the JTAG signals TMSC, TCKC, TDI, Reset_N, TDO and GND. The target PCB has a voltage regulator of 3.0 V, which is connected to VDDS, VDDS2 and VDDS_DCDC. For VDDR I measure a value of 1.8 Volt.
    I replaced our prototype board with another one, but no luck. The XDS110 seems to work flawlessly with the SensorTag boards, but the Sensortag has CC2650 instead of 5mm CC2640.

    In board.h I use the following definition:
    /** ============================================================================
    * Symbol by generic Board.c to include the correct kit specific Board.c
    * ==========================================================================*/
    // #define CC2650EM_5XD
    #define CC2650EM_4XS

    I am using 4XS, because a 5XS is not available.

    Everything worked fine until yesterday. I do not understand the error message. Maybe it is a hardware failure of our board, but I tried to check everything.
  • 0 in reply to Thomas Treyer
    Guru 735685 points
    This sounds your HW problem. Check if crystal on your PCB works fine.
  • 0 in reply to Thomas Treyer
    TI__Mastermind 18780 points

    You should have correctly set up in SW with correct packet size and front end config. There are several threads on the e2e on how to do this, for instant 

    and

    The VDDR should be 1.68 V when using the internal DCDC/LDO and the decoupl should be 1.27 V

    Have you tried powering your board with 3.3V? The XDS110 in the DEVPACK_DEBUG does not have any supply voltage sensing/level shifting, so you should power your own board with approx the same supplyvoltage (3.3V) while debugging.