Prev: usbsamp WdfRequestRetrieveOutputWdmMdl failure question
Next: Installation of WinUSB on XP Pro SP2
From: Asaf Shelly on 23 Dec 2009 08:31
> Well, USB is a protocol bus, and devices are expected to obey the
> protocols. There are tests for protocol compliance that must be passed
> before your driver can be WHQL-approved, but the system cannot be expected
> to protect against every protocol violation.
>
> Yes, you are right, and I am just making lame excuses.

:-)

I remember that there used to be a tool called USBCheck but I can't find it
or I don't remember the name correctly. How do you verify a USB device?

Thanks,
Asaf

From: Tim Roberts on 26 Dec 2009 17:37
Asaf Shelly <MSMediaForum(a)Shelly.co.il> wrote:
>
>I remember that there used to be a tool called USBCheck but I can't find it
>or I don't remember the name correctly. How do you verify a USB device?

The canonical source for these tests is the USB Implementor's Forum at
www.usb.org. I don't know whether they charge for these tests or not.
However, the tests don't do very much to test data transfers. That would
be too dangerous, because they don't know what the data actually means.
They mostly test timing and the descriptor setup.
--
Tim Roberts, timr(a)probo.com
Providenza & Boekelheide, Inc.
From: Asaf Shelly on 27 Dec 2009 03:51
Thanks for all the help.
The 64 byte issue saved me a couple of days.

Asaf
First  |  Prev  | 
Pages: 1 2 3
Prev: usbsamp WdfRequestRetrieveOutputWdmMdl failure question
Next: Installation of WinUSB on XP Pro SP2