OnD0Entry not called

Hi,

I'm new to driver development and I have to to implement a UMDF driver for a
custom USB device.
I used the umdfSkeleton code from the help as a starting point. When I call
the CreateDevice method from the WDF Framework the framework requests the
IPnpCallback and IPnpCallbackHardware interface and I return them properly
(stepped through the code with WinDBG). But the framework won't call the
OnD0Entry method at my driver.
My Question is now: Do I have to set-up queues or something so that the
framework will call this method?

Thanks

how did you install the driver? using devcon or via device manager?

"Kai" wrote in message
news:894D2D16-AE18-45CB-8169-...

Hi,

I'm new to driver development and I have to to implement a UMDF driver for a
custom USB device.
I used the umdfSkeleton code from the help as a starting point. When I call
the CreateDevice method from the WDF Framework the framework requests the
IPnpCallback and IPnpCallbackHardware interface and I return them properly
(stepped through the code with WinDBG). But the framework won't call the
OnD0Entry method at my driver.
My Question is now: Do I have to set-up queues or something so that the
framework will call this method?

Thanks

Both ways. Results in the same "error"

"Doron Holan [MSFT]" wrote:

> how did you install the driver? using devcon or via device manager?
>
> "Kai" wrote in message
> news:894D2D16-AE18-45CB-8169-...
>
> Hi,
>
> I'm new to driver development and I have to to implement a UMDF driver for a
> custom USB device.
> I used the umdfSkeleton code from the help as a starting point. When I call
> the CreateDevice method from the WDF Framework the framework requests the
> IPnpCallback and IPnpCallbackHardware interface and I return them properly
> (stepped through the code with WinDBG). But the framework won't call the
> OnD0Entry method at my driver.
> My Question is now: Do I have to set-up queues or something so that the
> framework will call this method?
>
> Thanks
>
> .
>

what command line did you use for devcon? devcon install or devcon update?

"Kai" wrote in message
news:73ED97D4-2C82-42A5-8F99-...

Both ways. Results in the same "error"

"Doron Holan [MSFT]" wrote:

> how did you install the driver? using devcon or via device manager?
>
> "Kai" wrote in message
> news:894D2D16-AE18-45CB-8169-...
>
> Hi,
>
> I'm new to driver development and I have to to implement a UMDF driver for
> a
> custom USB device.
> I used the umdfSkeleton code from the help as a starting point. When I
> call
> the CreateDevice method from the WDF Framework the framework requests the
> IPnpCallback and IPnpCallbackHardware interface and I return them properly
> (stepped through the code with WinDBG). But the framework won't call the
> OnD0Entry method at my driver.
> My Question is now: Do I have to set-up queues or something so that the
> framework will call this method?
>
> Thanks
>
> .
>

I tried both versions: install and update. Anytime the same error.
But I've found out, that when I program my usb device to be for example a
HID Mouse, and install my driver for that device, the driver loads
successfully. But when I revert my usb-device to be the custom-device, then
the driver fails to load.
So I think it might have something to do with the configuration descriptor
of my usb device.
Do you have any idea, where I could obtain information about why windows
does or does not like my descriptor?

Kai <> wrote:
>
>I tried both versions: install and update. Anytime the same error.
>But I've found out, that when I program my usb device to be for example a
>HID Mouse, and install my driver for that device, the driver loads
>successfully. But when I revert my usb-device to be the custom-device, then
>the driver fails to load.

Does the device appear in Device Manager? If you're popping up in Device
Manager (as an unknown device, presumably), then your descriptors are
probably pretty close.

>So I think it might have something to do with the configuration descriptor
>of my usb device.
>Do you have any idea, where I could obtain information about why windows
>does or does not like my descriptor?

Post your descriptors here and we'll take a look.
--
Tim Roberts,
Providenza & Boekelheide, Inc.

devcon install is not what you want, that will create a root enumerated
device. use devcon update exclusively

"Kai" wrote in message
news:9A5CD775-526A-4B04-8698-...

I tried both versions: install and update. Anytime the same error.
But I've found out, that when I program my usb device to be for example a
HID Mouse, and install my driver for that device, the driver loads
successfully. But when I revert my usb-device to be the custom-device, then
the driver fails to load.
So I think it might have something to do with the configuration descriptor
of my usb device.
Do you have any idea, where I could obtain information about why windows
does or does not like my descriptor?