


It supports all processor architectures (32 bit and 64 bit) and all versions of USB (low, high, full and super speed). USBTrace supports all versions of Windows starting from Windows 2000,XP.

This article explains in simple steps how USBTrace can be used to capture USB protocol data. The tool is mainly used by USB device driver, firmware, application developers & test engineers to analyze, debug and test the USB implementation. USBTrace is a software-based USB protocol analyzer (USB sniffer) which can be used to capture/sniff/analyze USB protocol data exchanged between USB devices and the PC. I invite you to test out Wireshark's USB capture with different USB devices, and post a comment with your findings.ī DidierStevensLabs.How to sniff USB traffic using USBTrace ? Introduction Which gives us the serial number in response: With this information, Windows will perform a query to obtain the length of string descriptor 3 in US English:Īnd thus Windows can do a query for a 50 bytes long string descriptor with index 3 in US English: The language used for the string descriptors of the USB stick I inserted is US English (0x0409): In this device descriptor, you can also see the indices for the Manufacturer, Product and SerialNumber string descriptors: 1, 2 and 3.Ī bit later in the capture, you'll see a request for a string descriptor (type 3) with index 0: that actually means an inquiry for the languages used for the string descriptors. Maybe you've already come across VIDs and PIDs, like in this instance ID: USB\VID_0951&PID_16AE\902B341D991AB031991F4C4D The descriptor contains interesting information, like the Vendor ID (VID or idVendor) and Product ID (PID or idProduct). When you start capturing USB traffic and then insert a USB stick, you'll see something like this:įirst we see a request (and response) for the device descriptor. Wireshark can capture USB traffic, provided you fulfil the necessary requirements.
