• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Answers 1 answer
  • Subscribers 83 subscribers
  • Views 1137 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TMS320F28377D: XDS110 recognized in dev manager as USB debug probe, TI provided DOS utilities and CCSv7 do not see it (device was not found on the bus). "Bricked" XDS110 recovery instructions don't help.

Susan Beiter78
Intellectual 660 points
Part Number: TMS320F28377D
Other Parts Discussed in Thread: TMDSEMU110-U

My problem is with the XDS110 emulator.  I have been developing using a control card for the TMS320F2837xD using the on-board XDS100 v2, and I'm ready to switch to real hardware and have a new XDS110 emulator.  Right out of the box, it isn't working properly.  Green LED D1 is on, Red LED D2 lights briefly upon plugging in.  I followed the directions in the readme for "bricked" XDS110, but neither grounding TDO nor TCK fixes the problem.  I don't understand how the error is reported as a USB problem when Device manager seems to have no problem recognizing the device over USB, which would seem to exonerate the cable and USB side as being the problems?  I searched the forum for similar postings, but I didn't find any post where someone managed to fix the emulator.  Very frustrating - any advice other than continuing to shell out $99 until I get one that works?  In the olden days of the support model, I would have asked for an FAE to bring a working probe in to check my set-up and prove that the problem is my probe before simply giving up.

  • 0
    Intellectual 660 points
    Also, in a related thread (I searched before posting), someone posted some screen shots from "XDS110 Debugger" schematics. I was wondering if it is possible to get a copy of those - could not find much on the XDS110 product page here in terms of technical docs. Thanks!
  • 0 in reply to Susan Beiter78
    TI__Intellectual 2515 points

    The error message is the result of attempts to find or open a connection to the XDS110 that have failed.  That code doesn't know anything about what the Device Manager sees, only that it cannot find the XDS110 via the host side USB calls.  So from that view it could be a USB issue or device driver issue or something else.

    I am at a loss though to explain how it is possible for the probe to show up correctly in Device Manager yet not be found by either dbgjtag of xdsdfu. Normally, you'd only see that if some process has connected to the XDS110 and is holding it open.  That doesn't sound like what's happening to you because nothing you've said indicates anything you tried ever connected to it.

    This is one of the standalone XDS110 pods?

  • 0 in reply to Edward Fewell
    Intellectual 660 points

    Yes, the pod is TI Product # TMDSEMU110-U, Serial # ETP_1801060, 518155-0001R Rev A.    The other thread where the schematics appear in screenshots is at https://e2e.ti.com/support/wireless_connectivity/proprietary_sub_1_ghz_simpliciti/f/156/t/619437?tisearch=e2e-sitesearch&keymatch=xds110%20brick. 

    I did just notice that my XDS utilities are from August 2017 and there is a new build from December 2017.  I am going to see if upgrading those helps at all.

  • 0 in reply to Susan Beiter78
    Intellectual 660 points

    Nothing changes with the newer XDS110 utilities from December - same inability to enumerate the probe on USB.  And still I can see all the device properties in device manager.

    OK - newest development: I plugged the XDS110 into my personal laptop, which runs Win10 and doesn't have any TI stuff loaded on it, no code composer, etc.  My work laptop runs Win7 and has CCSv7 and now XDS110 emu from December 2017.  I pulled down the package from TI wiki - the "xdsdfu.exe -e" running on my Win10 personal laptop returns Device 0, which means the probe itself is ok.  So what is happening on my work laptop?  Do I need to uninstall something?    Attaching a file with the contents of the DOS window from my personal laptop.

    xds110_windows10_utilities.txt 
    Microsoft Windows [Version 10.0.16299.309]
(c) 2017 Microsoft Corporation. All rights reserved.

C:\Users\beiters>cd \

C:\>cd ti\xds110

C:\ti\xds110>dir
 Volume in drive C is Windows
 Volume Serial Number is 56CD-9026

 Directory of C:\ti\xds110

03/22/2018  03:45 PM    <DIR>          .
03/22/2018  03:45 PM    <DIR>          ..
12/21/2017  01:07 PM            45,659 boot_loader.axf
12/21/2017  01:07 PM             6,194 boot_loader.bin
03/22/2018  03:45 PM    <DIR>          drivers
12/21/2017  01:07 PM           107,159 firmware.bin
03/22/2018  03:45 PM    <DIR>          install_logs
12/21/2017  01:07 PM            95,744 libusb-1.0.dll
03/22/2018  03:45 PM    <DIR>          uninstallers
12/21/2017  01:07 PM           118,272 xds110reset.exe
12/21/2017  01:07 PM           118,438 XDS110SupportReadMe.pdf
12/21/2017  01:07 PM            92,280 XDS110SupportUtilities_manifest.html
12/21/2017  01:07 PM            42,496 xdsdfu.exe
               8 File(s)        626,242 bytes
               5 Dir(s)  900,503,191,552 bytes free

C:\ti\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: 0x0451    PID: 0xbef3
Device Name:   XDS110 Probe with CMSIS-DAP
Version:       2.3.0.5
Manufacturer:  Texas Instruments
Serial Num:    00000000
Mode:          Runtime

Found 1 device.

C:\ti\xds110>xdsdfu.exe -f firmware.bin -r

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

Scanning USB buses for supported XDS110 devices...

Device is in runtime mode. Switch to DFU mode using '-m' before
attempting any other operation

C:\ti\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 Probe with CMSIS-DAP
Version:       2.3.0.5
Manufacturer:  Texas Instruments
Serial Num:    00000000
Mode:          Runtime

Switching device into DFU mode.

C:\ti\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:   Device Firmware Upgrade
Manufacturer:  Texas Instruments
Serial Num:    1.0.0.0
Mode:          DFU

Found 1 device.

C:\ti\xds110>xdsdfu.exe -f firmware.bin -r

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

Scanning USB buses for supported XDS110 devices...

Downloading firmware.bin to device...

C:\ti\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: 0x0451    PID: 0xbef3
Device Name:   XDS110 Probe with CMSIS-DAP
Version:       2.3.0.11
Manufacturer:  Texas Instruments
Serial Num:    00000000
Mode:          Runtime

Found 1 device.

C:\ti\xds110>

  • 0 in reply to Susan Beiter78
    TI__Intellectual 2515 points
    OK, so either the work laptop isn't able to open a handle to the XDS110 for some reason -or- some other process is grabbing it for some reason.

    Some things to try:

    On the work laptop, try to use the "Safely Remove Hardware and Eject Media" to eject the XDS110. If something is holding it open, then it may reject the request, and that can let us find out what's happening.

    If the eject worked OK, then try the utilities again.

    If you haven't already, then try a hard reboot and see if the problem remains.

    It's not a problem I've ever seen before, so I'm not entirely sure yet what may be at fault.
  • 0 in reply to Edward Fewell
    Intellectual 660 points

    I just noticed that there are errors in the xds110 driver install log file.  That seems significant, although I have no idea why and it doesn't tell me what to do about it.  

    ti_xds110_7.0.100.1_install.log 
    Log started 03/22/2018 at 15:21:58
Preferred installation mode : win32
Trying to init installer in mode win32
Mode win32 successfully initialized
Preparing to Install
Preparing to Install
Directory already exists: C:\ti\xds110
Unpacking files
Unpacking C:\ti\xds110\XDS110SupportUtilities_manifest.html
Unpacking C:\ti\xds110\boot_loader.axf
Unpacking C:\ti\xds110\boot_loader.bin
Unpacking C:\ti\xds110\firmware.bin
Unpacking C:\ti\xds110\XDS110SupportReadMe.pdf
Directory already exists: C:\ti\xds110
Creating directory C:\ti\xds110\drivers
Creating directory C:\ti\xds110\drivers\tiva_drivers
Creating directory C:\ti\xds110\drivers\tiva_drivers\amd64
Creating directory C:\ti\xds110\drivers\tiva_drivers\i386
Creating directory C:\ti\xds110\drivers\xds110_drivers
Creating directory C:\ti\xds110\drivers\xds110_drivers\i386
Creating directory C:\ti\xds110\drivers\xds110_drivers\x64
Unpacking files
Unpacking C:\ti\xds110\xdsdfu.exe
Unpacking C:\ti\xds110\xds110reset.exe
Unpacking C:\ti\xds110\libusb-1.0.dll
Unpacking C:\ti\xds110\drivers\DPInst32.exe
Unpacking C:\ti\xds110\drivers\DPInst64.exe
Unpacking C:\ti\xds110\drivers\tiva_drivers\boot_usb.inf
Unpacking C:\ti\xds110\drivers\tiva_drivers\boot_usb_amd64.cat
Unpacking C:\ti\xds110\drivers\tiva_drivers\boot_usb_x86.cat
Unpacking C:\ti\xds110\drivers\tiva_drivers\amd64\lmdfu64.dll
Unpacking C:\ti\xds110\drivers\tiva_drivers\amd64\lmdfu64.lib
Unpacking C:\ti\xds110\drivers\tiva_drivers\amd64\lmusbdll64.dll
Unpacking C:\ti\xds110\drivers\tiva_drivers\amd64\lmusbdll64.lib
Unpacking C:\ti\xds110\drivers\tiva_drivers\amd64\WdfCoInstaller01009.dll
Unpacking C:\ti\xds110\drivers\tiva_drivers\amd64\winusbcoinstaller2.dll
Unpacking C:\ti\xds110\drivers\tiva_drivers\amd64\WUDFUpdate_01009.dll
Unpacking C:\ti\xds110\drivers\tiva_drivers\i386\lmdfu.dll
Unpacking C:\ti\xds110\drivers\tiva_drivers\i386\lmdfu.lib
Unpacking C:\ti\xds110\drivers\tiva_drivers\i386\lmusbdll.dll
Unpacking C:\ti\xds110\drivers\tiva_drivers\i386\lmusbdll.lib
Unpacking C:\ti\xds110\drivers\tiva_drivers\i386\WdfCoInstaller01009.dll
Unpacking C:\ti\xds110\drivers\tiva_drivers\i386\winusbcoinstaller2.dll
Unpacking C:\ti\xds110\drivers\tiva_drivers\i386\WUDFUpdate_01009.dll
Unpacking C:\ti\xds110\drivers\xds110_drivers\xds110_debug.cat
Unpacking C:\ti\xds110\drivers\xds110_drivers\xds110_debug.inf
Unpacking C:\ti\xds110\drivers\xds110_drivers\xds110_ports.cat
Unpacking C:\ti\xds110\drivers\xds110_drivers\xds110_ports.inf
Unpacking C:\ti\xds110\drivers\xds110_drivers\i386\WdfCoInstaller01009.dll
Unpacking C:\ti\xds110\drivers\xds110_drivers\i386\winusbcoinstaller2.dll
Unpacking C:\ti\xds110\drivers\xds110_drivers\x64\WdfCoInstaller01009.dll
Unpacking C:\ti\xds110\drivers\xds110_drivers\x64\winusbcoinstaller2.dll
[15:22:13] Preparing for Post Installation Actions...
Running Post Install Steps
[15:22:18] Running XDS110 Driver Installer
Executing C:\ti\xds110/drivers/DPInst64.exe /SE /SW /SA /PATH "C:\ti\xds110/drivers/xds110_drivers"
Script exit code: 512

Script output:
 

Script stderr:
 Program ended with an error exit code

Error running C:\ti\xds110/drivers/DPInst64.exe /SE /SW /SA /PATH "C:\ti\xds110/drivers/xds110_drivers": Program ended with an error exit code
[15:22:19] Running Tiva Driver Installer
Executing C:\ti\xds110/drivers/DPInst64.exe /SE /SW /SA /PATH "C:\ti\xds110/drivers/tiva_drivers"
Script exit code: 256

Script output:
 

Script stderr:
 Program ended with an error exit code

Error running C:\ti\xds110/drivers/DPInst64.exe /SE /SW /SA /PATH "C:\ti\xds110/drivers/tiva_drivers": Program ended with an error exit code
Creating Uninstaller
Creating uninstaller 25%
Creating uninstaller 50%
Creating uninstaller 75%
Creating uninstaller 100%
Installation completed
Log finished 03/22/2018 at 15:22:22

  • 0 in reply to Susan Beiter78
    TI__Guru 72765 points
    Susan,
    Sorry for the long time between TI responses, just wanted to see if this was resolved with a new install, or other based on the above.

    Thanks,
    Matthew
  • 0 in reply to MatthewPate
    Intellectual 660 points

    Sorry as well - have been up to other things.  I think the issue has to be on my end, so I will need to work with my IT dept. to get what seems like a driver update installation issue sorted out.  Thanks!  If/when I do get a solution, I will try to share in the forum.

  • 0 in reply to Susan Beiter78
    TI__Intellectual 2515 points

    The installation from that log file looks good.  The DPInst64.exe installer returns status codes for the DOS error level instead of a zero on success which is more typical for command line apps.  The installer code isn't aware of that and treats any non-zero error level as an error, but the exit code does look correct for the driver installation.