Mstar Usb Debug Tool Driver 31 NEW!

sometimes, the target may not be on the same physical board as the host. this is the case in some embedded systems and in other motherboards that provide usb 3.1 upstream ports. if your host is connected to the target via a ribbon cable, there is no way of knowing whether it is the host controller connected to the target, or the other end of the target is connected to the host. when this happens, a diagnostic cable must be used to connect the host to the target in order to determine whether it is a usb 3.1 controller connected to the host, or a usb 3.0 upstream host connected to the target. in some cases, connecting to a target with a diagnostic cable results in a better debugging experience, as it can detect and compensate for some of the additional issues associated with debug cables.

mstar usb debug tool driver 31

when a diagnostic cable is used to connect a host to a target, the host has to be told where to connect the diagnostic cable. this can be done by using the xtal1 or xtal2 settings on the target. when using the xtal1 setting, the host will connect to any port on the target where an usb 3.1 downstream controller is connected.

debugging with the sigmastar usb com debugger is easy: you just need to power up the uart via the usb b connector. then connect your usb com cable to the sigmastar usb com debugger while the computer system is running and attach the sigmastar usb debugger driver to the port on your target computer. the sigmastar usb debugger will automatically detect the usb com connection when the port is powered on.

you can then set the debug parameters via the com_parameters file in the same folder as the sigmastar usb debugger driver. the com_parameters file can contain any configuration parameters that can be found by searching the internet.