On Sun, 28 Dec 2008 09:24:05 +0100, Michelle Konzack <linux4michelle@xxxxxxxxxxxxxxx> wrote: > Does this mean, we have to sniff on the USB cable direct to get suitable > results? [] This depends on the kind of problem you're dealing with. If it's some kind of signal integrity issue, you have to see the eye with an oscylloscope. For some bus protocol violations, a sniffer printing all packets is required, e.g. if you run outside of frame time or something. If it's something like a toggle mixed up, your firmware may trace packets it receives and sends, with PIDs. Wrong descriptors, control commands timed out, etc. can be uncovered easily with usbmon and other programmatic sniffers. Primarily, usbmon is used when the host stack above HCD (HID, SCSI, etc.) misbehaves, or is not compatible with your firmware. For example, stock firmware for FX2 hates extra SET-CONFIGURATION, and you can see it dying right after that. It all depends on the level where the problem occurs. You never told us what your problem was. -- Pete -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
