The (out of the box) UMDF driver successfully installs, the device name is read, then the usb device reports slow speed (onpreparehardware speed -1 ). Then stops as thbe device reports that it can not start. Power managment device status reports D3
The same firmware loaded with the KMDF driver, sucessfully installs, reports full speed then performs all functions in testapp.c and reports a power state of D0.
Can power managment code differences between UMDF and KMDF cause the USB device NOT to start?
Since the speed is read from the device, what could cause the UMDF driver to read it as slow while the KMDF driver to read it as full?
Power management has nothing to do with the problems you are seeing
d
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@mpr.com
Sent: Friday, November 26, 2010 11:44 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] UMDF usb device power management
The (out of the box) UMDF driver successfully installs, the device name is read, then the usb device reports slow speed (onpreparehardware speed -1 ). Then stops as thbe device reports that it can not start. Power managment device status reports D3
The same firmware loaded with the KMDF driver, sucessfully installs, reports full speed then performs all functions in testapp.c and reports a power state of D0.
Can power managment code differences between UMDF and KMDF cause the USB device NOT to start?
Since the speed is read from the device, what could cause the UMDF driver to read it as slow while the KMDF driver to read it as full?
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
To clarify the umdf usb trace:
Retrieve hardware device name successfully
OnPrepareHardware speed - 1 (incorrect should be full)
~CMyReadWriteQueue Entry
~CMyQueue Entry
~CMyQueue Entry
fails to start
Can this have something to do with configuration selection ?
Does this device have two configurations, high speed and low speed?
– pa
wrote in message news:xxxxx@ntdev…
> To clarify the umdf usb trace:
>
> Retrieve hardware device name successfully
> OnPrepareHardware speed - 1 (incorrect should be full)
> ~CMyReadWriteQueue Entry
> ~CMyQueue Entry
> ~CMyQueue Entry
> fails to start
>
You are correct, once I added the slow speed descriptor (8 bytes message length) the device starts… The problem is that RetrieveDeviceInformation only knows about high and low speed devices so my full speed clone was having problems…