Re: Dynamic Switching at Runtime.
- From: Ilamparithi <Ilamparithi@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 17 Feb 2009 01:31:01 -0800
Hi Prabhu,
I have a Hp Ipaq in which after switching the mode using the above code, my
PC is able to find that the connected device mode has changed automatically(
with unplugging and plugging back the Hp ipaq to the PC). However, I have PDA
from a different vendor in which after switching the mode using the above
code I had to unplug and plug back to the PC to get the PC understand that
device mode has changed.
Why is this difference?
I was trying to use a USB port monitor to find the difference in both the
scenarios. Look like device sends RESET command in working case, which does
not happen in the non working case.
Is it possible for a application running in device, to issue a force
reset(after switching mode) to its usb device port so that the host
recognizes the mode switch without unplugging and plugging?
Any help appreciated.
With Thanks & Regards,
A.Ilamparithi.
"Henrik Viklund" wrote:
OK. The x86 emulator do not support USB function emulation so there.
isn't any usb function driver loaded and that's why the code snippet
will return an error code.
Now, an MDD is not a "stand alone" dll -it's a helper lib that
together with a corresponding PDD lib (the part of the driver that
talks to a particular hardware) can be linked together to form a
driver dll. In theory you should be able to implement a dummy PDD lib
to create a dummy usb bus driver that you can use in the x86 emulator
to test the code below but in reality that is probably not a trivial
excersise for someone with limited knowledge in driver development.
If it is important to test the functionality, use a devboard with usb
function capability.
Henrik Viklund
Prevas AB
On 21 Nov, 10:43, sanju <sunw...@xxxxxxxxx> wrote:
thanks henrik,
The FindFirstDevice is returning an invalid handle. The error number
is 18 ( There are no more files. ERROR_NO_MORE_FILES ) and eventually
failing to continue further execution.
I'm using emulator x86 BSP, is the problem because of that? The
pzBusGuid has the value of the IClass of the Net2280 and i'm not able
to include that in my OS Design. So does this net2280 dll switch
between the client drivers referring to the mdd library?
Now the layered devices are of 2 layers 1.MDD and 2.PDD. My doubt is-
are both these layers having different dll files or the pdd dll file
itself will refer to the MDD library when included in the OS Design?
Cant we include the MDD dll if it exists in the OS design? can MDD
exist independently? where can i find the dll for the mdd in
wince500\public\common\oak\drivers\usbfn\controller\mdd\ufnbus.cpp?
I'm new to the device drivers, your guidance needed.
Thank you.
- Follow-Ups:
- Re: Dynamic Switching at Runtime.
- From: Henrik Viklund
- Re: Dynamic Switching at Runtime.
- Prev by Date: Re: Access CPU Registry in Application?
- Next by Date: Re: Dynamic Switching at Runtime.
- Previous by thread: problem in loading windows Ce image in eBox 2300SX
- Next by thread: Re: Dynamic Switching at Runtime.
- Index(es):
Relevant Pages
|
