USB driver (KDMF) read and write failures

NTDEV
1

I have a driver that is mostly the example fro the DDK. I have a bulk in and out endpoint. It enumerates ok and sets up the various resources - queues, pipes etc. The system has to start with a write - passing a flag to the device. The write code fails WdfUsbTargetPipeFormatRequestForWrite with a STATUS_INVALID_DEVICE_REQUEST code. Can anyone give me a pointer of two of what to look into.

Thanks

Veronica

2

Veronica Merryfield wrote:

The system has to start with a write - passing a flag
to the device. The write code fails
WdfUsbTargetPipeFormatRequestForWrite with a
STATUS_INVALID_DEVICE_REQUEST code. Can anyone
give me a pointer of two of what to look into.

Did you previously set a configuration and pick up all the appropriate WDFUSBPIPE handles? We probably need to see your code.

3

It is not already on, make also sure to enable wdf verifier for your driver.

Egi.

4

Thanks Egi - that proved to be a good lead.

I descovered that the USBPIPES are of the wrong types but match a combination of the pipes that I have had defined during the development of the device code.

I suspect that windows is caching the configuration information. How do I clear it.

Thanks

Vrnc

On 2010-08-30, at 12:25 PM, xxxxx@microsoft.com wrote:

It is not already on, make also sure to enable wdf verifier for your driver.

Egi.

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

5

Veronica Merryfield wrote:

I descovered that the USBPIPES are of the wrong types but match a combination of the pipes that I have had defined during the development of the device code.

I suspect that windows is caching the configuration information. How do I clear it.

What does that mean, exactly? What do you mean by “wrong types”?
Windows doesn’t cache any information about pipes and interfaces.
Everything is read fresh every time you plug in.

What does your configuration descriptor look like? How are you
referring to the pipes you want?

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

6

Well, I was going to just post all the detail butI just did a clean rebuild and reload of all parts to this project, like I had done this morning and this time it is reported correctly, so who knows.

Thanks for the leads.

On 2010-08-30, at 2:34 PM, Tim Roberts wrote:

Veronica Merryfield wrote:
> I descovered that the USBPIPES are of the wrong types but match a combination of the pipes that I have had defined during the development of the device code.
>
> I suspect that windows is caching the configuration information. How do I clear it.

What does that mean, exactly? What do you mean by “wrong types”?
Windows doesn’t cache any information about pipes and interfaces.
Everything is read fresh every time you plug in.

What does your configuration descriptor look like? How are you
referring to the pipes you want?

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

7

you can use windbg and dbgview to print logs,