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.

TMDSEMU110-U: TMDSEMU110-U

Part Number: TMDSEMU110-U
Other Parts Discussed in Thread: TMDSCNCD28335, TM4C1294NCPDT, UNIFLASH

Windows 10 is unable to detect the XDS110 debug probe. However, the green light on D1 turns ON when the device is connected to the USB port. We have installed CCSv7.1.0, control suite v3.4.9, MATLAB 2017b and xdctools_3_50_08_24_core. We have two devices, both are not detected by the OS. We have also tried the solution provided in https://e2e.ti.com/support/tools/ccs/f/81/t/610305?Can-t-find-XDS110-U-device-with-CCS-or-xdsdfu-e and https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz/f/156/p/887212/3281522#3281522  and https://software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/emu_xds110.html#devices-supported  We have also tried to connect the XDS110 to the PC with CCSv8, but the results were the same.

Request your support. Thank you.

  • Hi James,

    Are you using TI EVM or it is your custom board?  If it is TI EVM, then is it Launchpad or controlCARD?

    Is it possible to install latest CCS (CCS10.2)?

  • Hi Santhosh,

    Thank you for the reply.

    We are using OP8665 manufactured by OPAL RT and the control card used on this interface is from TI, TMDSCNCD28335.

    We can install CCS10.2. However, the device (XDS110) is not displayed in device manager.

    Thank you

    Regards

    James

  • Hi,

    I have installed CCS v10.2.0 and have restarted the PC. However, the XDS110 device is not detected by the desktop PC. Also I have tried the commands for checking the XDS device. The screenshot of the same is as below.

    Regards

    James

  • James,

    The picture didn't came through. Can you please post the image again?

    Is OP8665 like dockstation?

  • Hi Santosh,

    The picture was the screenshot that I took after executing the command xdsdfu -e in the command window after installing CCSv10 and then connecting XDS-110.

    The result of this execution was that there were no devices detected.

    Regards

    James

  • James,

    Can you check the Windows Device manager? Do you see XDS110 device?

  • Hi Santhosh,

    Thank you for the reply. 

    XDS 110 is not appearing in the Device manager. 

    Thank you

  • James,

    Please FTDI driver from following link

    https://ftdichip.com/drivers/

    Also, how are you connecting the EVM? 

  • Hi Santosh,

    Thank you for the email.

    I have installed the VCP and D2XX software. After restarting the PC, the XDS-110 is still not detected by the PC.

    The XDS-110 is connected to the OPAL-RT 8665 via JTAG port.

    Regards

    James

  • James,

    When you connect the XDS110 to usb port, there should be some bus activity, and you should see some device. If driver is not correct, then it should show unkbown USB device. Please take a look at troubleshooting section of the link.

    software-dl.ti.com/.../emu_xds110.html

    Also, I am not familiar with OPAL-RT device. Do they need any special driver? 

  • Hi Santosh,

    Thank you for the reply. I have tried connecting the XDS-110 to the USB ports of the PC both front and rear. However, there was no change observed in the device manager. I could only see a green light (D1) turn On when the device was connected to the USB port. I am using the USB cable supplied with the Debug probe.

    The detailed snap shot is attached.

    Regards

    James  

  • James,

    Only one thing I can suggest, disconnect the controlCARD, just connect the emulator, and see if you see any activity on windows device manager. Just thinking if connecting controlCARD is causing any conflict.

  • Hi Santosh, 

    Thank you for the reply.

    I have tried the following connections:

    (1) Connecting XDS-110 to the PC using the USB cable.

    (2) In addition to (1), the XDS-110 is connected to the controller board using JTAG.

    In both the cases, I have found that there is no change in Hardware observed.

    I also tried connecting another TI debug probe, XDS100v2. This debug probe is detected by the PC.

    Regards

    James

  • James,

    Is this new XDS110 or it was working before? 

  • Hi Santhosh,

    Thank you for your reply.

    It's a new probe, we are using it for the first time.

    Regards

    James

  • James,

    Can you disconnects the emulator to USB port, do not connect the board and then check if there is any USB bus activity? 

    Do you have another USB cable around, please try that?

  • Hi Santosh,

    Thank yo for your reply.

    I have disconnected the emulator, the debug probe is not recognized by Windows. 

    I have tried connecting the USB cable used for transferring data from mobile phone. Still the device is not detected by windows.

    We have 2 such units, both have the same problem.

    Regards

    James

  • James,

    Just to make sure you are just trying to xds110 usb cable to PC, do not connect to any EVM or OPALRT.

    Also, try to update the emulator software from here:

    software-dl.ti.com/.../emu_xds_software_package_download.html

  • Hi Santhosh,

    Thank you for the reply.

     I have downloaded the "ti_emupack_setup_9.2.0.00002_win_64.exe" and installed the same as I have installed "Code Composer Studio 10.2.0".

    I have connected the XDS110 probe to the desktop PC and have run the command 'xdsdfu -e'  commnad from the command window and I have also tried creating a CCS project and then verifying the connection to the XDS 110, the results of the two are as attached.

    Request you help in this regard.

    Thank you

    James


  • James,

    As the emulator is not showing in Windows device manager, we cannot run any diagnostic. Do you have any other computer to try, just connect the emulator and check if you see any bus activity?

  • Dear Santhosh,

    Thank you for the reply.

    I have tried connecting XDS110 to 3 different desktops with the following programs loaded:

    Desktop 1: New PC. CCS/ Matlab/RT LAB  is not installed.

    Desktop 2 (With the following software's installed) : Matlab 2016b, Matlab 2017b, CCSv 7.1.0, RT-Lab 2020.4

    Desktop 3 (With the following software's installed) : Matlab 2016b, Matlab 2019b, CCSv 8, RT-Lab 2019


    In all the three desktops, the D1 LED on the XDS 110 glows but there is no bus activity.

    Request your support in this regard.

    Thank you.

  • Can you please XDS100 emulator directly to the computer? Looks like you are connecting other device to PC.

  • Hi James,

    I am really surprised that you do not see any USB activities in device manager on all three computers when you attach XDS100. Can you please go through the troubleshooting section in the following page and let me know if you make any progress:

    software-dl.ti.com/.../emu_xds110.html

  • Hi Santosh,

    Thank you for the reply. The following devices are connected to the 3 PC's

    PC1 has a USB Mouse and a USB keyboard connected to it.

    PC2 has a USB Mouse, USB keyboard and Opal RT OP4510 target connected via ethernet.

    PC3 has a USB mouse, USB keyboard. It had a USB connection to an inverter, but the same was unplugged (placed at the right side of the CPU enclosure).

    I have tried connecting XDS-110 to other laptop as well. But there was no bus activity.

    Regards

    James

     

  • James,

    Please go through the troubleshooting section in the following page and let me know if you make any progress:

    software-dl.ti.com/.../emu_xds110.html

  • Thank you for the reply.

    I have referred to the installation instructions for CCSv9.0.0 at https://software-dl.ti.com/ccs/esd/documents/ccs_downloads.html and installed the same on a new desktop PC with Windows 10 Pro 64bit OS.

    Desktop PC before installing CCSv9.0.0 (PC is connected to 1 USB Mouse+ 1 USB Keyboard+ 1Ethernet LAN)

    Device Manager before installing CCSv9.0.0

     

    XDS-110 Connected to PC after Installating CCSv9.0.0

    Screen shot after executing the command xdsdfu -e in command window.

    The D1 LED on the XDS110 device glows but the device is not detected by the PC. Since the Device manager and the xdsdfu -e command did not show any device connected, I could not go ahead with the troubleshooting.

    Request you support in this regard.

    Thank you

    James

  • James,

    It looks like it is not connected to PC, and PC is not seeing it, so xdsdfu command will not help.

    Did you try another USB cable if it is broken? How many XDS110 behaving like this?

  • Hi Santosh,

    Thank you for the post.

    I have connected the XDS-110 to the USB port in the front of the CPU cabinet.

    I have tried using the USB cable of other device and also the USB data cable used with mobile phone.

    We have 2 units of XDS-110 and both have the same issue.

    Regards

    James

  • James,

    I am checking with my team members. Will get back to you by tomorrow.

  • Hi James,

    Unfortunately it looks like your XDS110 probe is bricked. I'm not sure how that happened but based on the information you have given, it appears to be the case. You can try to fix it but the fix is a pain on the standalone probes. The procedure is described in the below document that comes with CCS:

    <CCS INSTALL DIR>\ccs\ccs_base\common\uscif\xds110\XDS110SupportReadMe.pdf

    See the last section "Recovering a Bricked XDS110 without JTAG"

    When looking at the TM4C1294NCPDT datasheet: https://www.ti.com/lit/ds/symlink/tm4c1294ncpdt.pdf

    Page 1771 shows the pin out for the TM4C1294NCPDT. Based on that, it looks like pin 97 is as shown below on the probe:

    You try the the steps in the readme to unbrick it. I have a probe in a similar state that I need to unbrick also (which I will attempt in next few days).

    ki

  • Ki said:
    Based on that, it looks like pin 97 is as shown below on the probe:

    And looking at the picture, pin 97 on the TM4C1294NCPDT is connected to J1 pin 6. It might be easier to ground J1 pin 6.

    Also, J1 appears to be an ARM 10-Pin JTAG connector. Not sure if that allows the TM4C1294NCPDT in the XDS110 to be unbricked by a different probe.

  • Chester Gillon said:
    And looking at the picture, pin 97 on the TM4C1294NCPDT is connected to J1 pin 6. It might be easier to ground J1 pin 6.

    Yes that is a good point

    Chester Gillon said:
    Also, J1 appears to be an ARM 10-Pin JTAG connector. Not sure if that allows the TM4C1294NCPDT in the XDS110 to be unbricked by a different probe.

    I actually tried attaching a debug probe to that header to see if I can establish a debug session with CCS to erase the flash. But I wasn't able to connect to the TM4C. There likely is a step I am missing to get that going but I'm not sure what it is. I've actually never tried unbricking a standalone probe.

  • Hello Ki,

    If the MCU is possibly bricked then you likely need to use the device unlock process to recover the TM4C MCU. If you have a JTAG connector then you will want to use Uniflash to do this. To do so I recommend using the command line procedure we have documented in our JTAG guide. Refer to Section 5.3.2: https://www.ti.com/lit/an/spma075/spma075.pdf?ts=1595272852526

    Hope this helps :)

  • Thanks Ralph. I'm pretty sure that is a 10-pin JTAG header for the TM4C that Chester pointed out. But I get an error about no target power when trying to connect with the debugger. When I physically connect my other debug probe to the JTAG header, I see the D2 led go off. I am likely missing some step but not sure what it is. Would you by chance know how to set this up for the TM4C on a standalone XDS110?

  • Hi Ki,

    Unfortunately I do not, I've never cracked one open before and only kind of realized in hindsight of this post that of course there is a TM4C inside since we use it for the LaunchPad emulators. Is the no target power showing up for the unlock sequence? I'm not familiar with the setup or schematic but presumably the JTAG is used for first time programming over boot loader so I would think that power shouldn't be an issue if nothing else is connected.

    I would be surprised if this is the case but... check the TDO pin if it is toggling at a constant frequency. If the TDO toggle occurs with a fixed frequency then that indicates that something has gone wrong during the process of boot up of the device, and that would mean the device cannot be recovered and must be replaced. 

  • It's alive! 

    Thanks for sharing that document Ralph. It mentions to use an XDS100v2 or XDS200 to unbrick it. I was originally using another XDS110. I then switched to an XDS200 and was able to connect to the TM4C via UniFlash and flash the boot_loader.bin file at address 0x0 and that did the trick and set my XDS110 in DFU mode so that I was able to then flash the xds110 firmware successfully! My XDS110 probe is now successfully unbricked! Thanks!

    James - I'm not sure if you have an XDS100v2 or XDS200 with the necessary adapters to connect to the 10-pin JTAG header on the XDS110 probe. If so, then you can unbrick it using UniFlash. If not, then you'll have to go through the more arduous way I mentioned earlier.

    ki

  • HI Ki,

    Thank you for your post. I have tried this procedure and it has worked. Now the PC is detecting XDS-110.

    Thank you for your support.

    Regards

    James

  • Hi Ki,

    Thank you for your post.

    I do have an XDS100V2. I will try to load the firmware onto another bricked XDS-110 using XDS100V2.

    Thankyou

    James

  • Good to hear you were unable to brick the debug probe. Thanks for the update.

    ki