Installing USB driver to a Pocket PC device

NTDEV
1

Dear All,

I am into development of USB host development of Pocket PC device.

When I try to install the dll files on the PC, we got Unidentified USB
device POP-up. There I enetered my usb driver dll name, but the pop-up
remains as it’s, the focus remains on dll name.

For testing I entered the wrong dll name, it shows error as “unable to
install”.

Can anybody throw some light on installation of usb driver to a pocket pc
device.

Thanks & Regards,
SeethaRam G.

2

Man, you have already been told before - this is an NT forum.
You seek help for CE.
The link below may help you to get started:
http://msdn.microsoft.com/en-us/embedded/aa731407.aspx

SEETHARAM GOVINDASWAMY wrote:

Dear All,

I am into development of USB host development of Pocket PC device.

When I try to install the dll files on the PC, we got Unidentified USB
device POP-up. There I enetered my usb driver dll name, but the pop-up
remains as it’s, the focus remains on dll name.

For testing I entered the wrong dll name, it shows error as “unable to
install”.

Can anybody throw some light on installation of usb driver to a pocket
pc device.

Thanks & Regards,
SeethaRam G.

— 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

3

Again, it is NT driver development list so don’t expect any more
answers.

You need to debug your driver. What you see can occur if OS tried to
load the DLL and it failed for some reason or looked to OS as a failure
(wrong return code somewhere, incorrect installation etc.). Also, if I
remember correctly, it can occur if your DLL isn’t in the right
directory (\Windows IIRC).

Best regards,

Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com http:</http:>]

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of SEETHARAM
GOVINDASWAMY
Sent: Wednesday, November 19, 2008 2:07 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] Installing USB driver to a Pocket PC device

Dear All,

I am into development of USB host development of Pocket PC
device.

When I try to install the dll files on the PC, we got
Unidentified USB device POP-up. There I enetered my usb driver dll name,
but the pop-up remains as it’s, the focus remains on dll name.

For testing I entered the wrong dll name, it shows error as
“unable to install”.

Can anybody throw some light on installation of usb driver to a
pocket pc device.

Thanks & Regards,
SeethaRam G.

— 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

4

By the way. Pocket PC’s are extremely unfriendly when it gets to debugging.
If you are working with an off-the-shelf Pocket PC, you *may* have no
way to get the debug prints.
When I developed a driver for a Pocket PC, my solution was logging debug
prints to a file.

I would recommend you to build an x86 image in Platform Builder, debug
and polish your driver on x86 target (a regular PC).
You can even build the entire OS in debug mode and selectively turn on
debug prints in in-box drivers (this is impossible with a Pocket PC).
When you are done developing your driver on an x86 target - switch to a
Pocket PC.

Alexey

Michal Vodicka wrote:

Again, it is NT driver development list so don’t expect any more answers.

You need to debug your driver. What you see can occur if OS tried to
load the DLL and it failed for some reason or looked to OS as a
failure (wrong return code somewhere, incorrect
installation etc.). Also, if I remember correctly, it can occur if
your DLL isn’t in the right directory (\Windows IIRC).

*Best regards,

Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, **http://www.upek.com*
http:</http:>*]*

*From:* xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] *On Behalf Of
*SEETHARAM GOVINDASWAMY
*Sent:* Wednesday, November 19, 2008 2:07 AM
*To:* Windows System Software Devs Interest List
*Subject:* [ntdev] Installing USB driver to a Pocket PC device

Dear All,

I am into development of USB host development of Pocket PC device.

When I try to install the dll files on the PC, we got Unidentified
USB device POP-up. There I enetered my usb driver dll name, but
the pop-up remains as it’s, the focus remains on dll name.

For testing I entered the wrong dll name, it shows error as
“unable to install”.

Can anybody throw some light on installation of usb driver to a
pocket pc device.

Thanks & Regards,
SeethaRam G.

— 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

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

> -----Original Message-----

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
Alexey Polonsky
Sent: Thursday, November 20, 2008 9:48 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Installing USB driver to a Pocket PC device

By the way. Pocket PC’s are extremely unfriendly when it gets
to debugging.
If you are working with an off-the-shelf Pocket PC, you *may* have no
way to get the debug prints.
When I developed a driver for a Pocket PC, my solution was
logging debug
prints to a file.

It is one possibility and I use it for power management debugging. For
standard debugging I wrote a tool which is able to capture and display
traces via ActiveSync using RAPI. Debugged code has to be linked with a
library which stores traces to a buffer created by a DLL running by RAPI
process. It is very similar to the way how OutputDebugString() works on
‘real’ Windows. Shared memory, events and monitor running at host.

I would recommend you to build an x86 image in Platform
Builder, debug
and polish your driver on x86 target (a regular PC).
You can even build the entire OS in debug mode and
selectively turn on
debug prints in in-box drivers (this is impossible with a Pocket PC).
When you are done developing your driver on an x86 target -
switch to a
Pocket PC.

Yes. It is exactly what I’d recommend, too. It’d only add KITL and
Ethernet keywords :slight_smile:

Best regards,

Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]