|
From: Xiaofan C. <xia...@gm...> - 2012-06-13 13:29:29
|
On Wed, Jun 13, 2012 at 9:17 PM, Markus <li...@ne...> wrote: > On Wed, 13 13:24 , Pete Batard wrote: >> >> When achievable, being able to have a look at the data being sent on the >> bus usually pays off, especially if you're not sure where to look to >> find out where the problem comes from. >> > > Thanks, Pete. As Wireshark doesn't capture USB on Windows, it > looks as I'll have to resort to a proprietary tool. > > Can you (or somebody else reading the list) recommend something > worthwhile in a price range < 500$ ? You may try some free tools or evaluation version of paid software sniffer first. One possibility under Win7 is to use the WinUSB debug trace log. http://blogs.msdn.com/b/usbcoreblog/archive/2010/02/05/how-to-generate-and-view-a-winusb-debug-trace-log.aspx If you are running XP, you can use the following two open source tools. http://sourceforge.net/projects/usbsnoop/ http://www.pcausa.com/Utilities/UsbSnoop/ The following one is supposed to work under Vista/7 as well (for x64 version, you need to sign the driver or disable code signing check) http://code.google.com/p/busdog/ On the other hand, you can buy a hardware analyzer for US$475. http://www.totalphase.com/products/beagle_usb12/ -- Xiaofan |