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: Can't use more than 9 XDS110 probe

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

Hello Support,

Working on a project where I need to flash more than 10 microcontrollers in the same product, I'm using the following configuration:

  • computer used for this project runs on Windows 7 (64 bits),
  • TI_Debug_Probe USB driver (2.0.0.2) has been installed thanks to a standalone package made with UniFlash 8.0 tool,
  • one XDS110 probe per target,
  • each XDS110 probe has been updated to 3.0.0.20 firmware,
  • two USB HUB (with external power supply) are chained to reach the total required number of USB connectors for the XDS110 probes.

Having a script to make programmation of the whole product faster, I'm facing an issue when the number of connected XDS110 is greater than 9 probes. Windows Device Manager always returns a code 10 error (CM_PROB_FAILED_START) on the 10th connected probe whichever probe is the 10th to be connected on any of the two USB HUB.

Could you please tell me if there is any limitation on how many XDS110 probe could be connected on the same computer?

Is there any more up-to-date driver which could handle such configuration?

If not, do you have any suggestion to handle a USB power up / power down sequence with some Windows / custom TI tool commands?

Thanks in advance,

Best Regards,
Adrien.

  • Adrien,

    I don't know if this will solve the issue, but have you tried issuing a unique serial ID to each of the debug probes? Something similar is done when setting up CCS to support multiple debug probes.

    https://software-dl.ti.com/ccs/esd/documents/sdto_ccs_multi-probe-debug.html

  • Hi Gus,

    Thank you for your tip.
    Yes, I've already done that as one of the first steps to setup my environment. Each probe has its own SN with a format like "0000xxxx" where xxxx allow me to identify each microcontroller.

  • Hello,

    Having a script to make programmation of the whole product faster, I'm facing an issue when the number of connected XDS110 is greater than 9 probes.

    Wow, I've never seen such an environment with that many probes connected to one PC, especially via chained USB hubs. I will need to follow up with engineering

  • two USB HUB (with external power supply) are chained to reach the total required number of USB connectors for the XDS110 probes.

    What type of USB connection does both hubs and the USB port on the PC they connect to? USB 3? USB 2?

    Also, would it be possible to try not chaining the USB hubs but instead have each hub directly connected to a PC USB port and see if it is possible to use the 10th probe?

    Thanks

    ki

  • Hello Ki,

    Thank you for forwarding this support request.

        What type of USB connection does both hubs and the USB port on the PC they connect to? USB 3? USB 2?
    Below is an interconnection diagram of our setup for 9 probes:



         Also, would it be possible to try not chaining the USB hubs but instead have each hub directly connected to a PC USB port and see if it is possible to use the 10th probe?
    I've tried to connect both USB hubs directly to the PC USB ports but this was worst... The OS returns an error message saying too many usb ports connected which haven't happend with the previous setup.

  • Just wondering if this is an old Windows problem! Do you have a Windows 10/11 machine available? It would be interesting to see if they connect any better!

  •    Do you have a Windows 10/11 machine available?
    This partially solved the issue up to 18 debug probes.
    However, I have one setup with almost 30 debug probes which doesn't work even with a Windows 10 (21H2) machine.

  • That does kind of suggest that the restrictions are Windows problems Disappointed
    It might be worth trying to plug your hubs into various combinations of USB ports - even front and back panel ports, so they are on different USB devices.

  • That does kind of suggest that the restrictions are Windows problems

    yes I'm going have to agree with Jim that this seems to be some Windows limitation.

    As for: 

    If not, do you have any suggestion to handle a USB power up / power down sequence with some Windows / custom TI tool commands?

    There are some options for this on Linux but there does not seem to be anything on Windows that we (TI) could find.

    ki