From: Manas on
Thanx again Chris for the reply.
It is really tedious to develop code without using debugging tools. But I
will have to find some solution.
To debug, the only way I could find is putting file write statements. I have
file write statements in DLL main process attach and detach and all the other
functions. From the outputs in the file, I could see that the dll main and
all the other functions are getting called nicely when the driver is working
perfectly. But there is no output statment atall(not even from dllmain) from
anywhere in the cases of "Uidentified Device". So I think the dll is not
getting loaded.
Can you please throw some light on certificate. I am a bit concern on this.
After reset the USB host might try to load the function driver way before the
security system is loaded. Will that cause any problem.
Thanx,
Manas.

"Chris Tacke, eMVP" wrote:

> Without availability of platform tools, which I've always had for doing
> driver work, I don't really know. For some reason the USB host driver is
> unable to eitehr find or load your function driver. If you can't put a
> break or at least debug output into the host driver, I have no idea how
> you'd find out why. This must be why I never do driver work on WinMo.
>
>
> --
>
> Chris Tacke, Embedded MVP
> OpenNETCF Consulting
> Giving back to the embedded community
> http://community.OpenNETCF.com
>
>
>
> "Manas" <Manas(a)discussions.microsoft.com> wrote in message
> news:BD78A99C-7262-4A1F-8004-6A0C9C239B79(a)microsoft.com...
> > Hi,
> > I am still not able to figure out the reason behind the "Unidentified
> > device" message, when I plug in my device. As I explained below, the
> > driver
> > works fine with the device but the system fails to load my driver at
> > certain
> > instances.
> > 1. Connect O2 Flame to PC ActiveSync. Do some sync. Then connect back to
> > the
> > device, driver loading fails.
> > 2. Leave te device connected to the O2Flame, then reset O2 flame. It boots
> > up but witht he "Unidentified device" message.
> > Chris could you get a chance to think about this. As I said, if the
> > device is replaced by a mass storage in both the above situation, it is
> > working fine. Anything to do with code signing, or OS image (OS image have
> > the mass storage driver but my installed driver goes to some flash)?
> > We need to resolve this issue quickly to release the s/w.
> > Please help.
> > Thanx
> > Manas.
> >
> > "Manas" wrote:
> >
> >> Thanks Chris for the reply.
> >> But I have a point here.
> >> Like wise if instead of the device, I connect a Thumb drive(mass
> >> storage) to the Flame OTG, and perform the same 2 operation as I did
> >> below,
> >> it works perfectly fine and their is no problem atall. That may prove
> >> that
> >> the OTG driver is able to switch correctly between the client and host.
> >> I have 2 concern here:
> >> 1. The mass storage driver is included in the OS image(nk.bin) of the
> >> Flame.
> >> Where as the driver that I installed might get stored in some Flash.
> >> 2. Anything to do with code signing, authentication. I have signed my
> >> driver
> >> dll with the certificate that comes with the Windows Mobile 5, and
> >> installed
> >> that sdkcert.cab file into the Flame (But I don't see any certificate
> >> added
> >> to the certifcate list in the control panel). I also tried changing the
> >> Flame
> >> previledge level using the cpf files included in the Windows Mobile 5
> >> SDK.
> >> I am not sure whether any of these causing the problem. Please let me
> >> know
> >> your opinion.
> >> Thanks,
> >> Manas.
> >>
> >> "Chris Tacke, eMVP" wrote:
> >>
> >> > > 1. If I leave the device connected to the O2 Flame and reset O2
> >> > > Flame. I
> >> > > receive the message box "Unidentified device", asking for the driver
> >> > > dll.
> >> > > If
> >> > > I specifiy the driver dll it fails to load.
> >> >
> >> > Likely the USB hoist driver sees the attached device early on in boot -
> >> > before the function driver is loaded. There may be nothing you can do
> >> > about
> >> > that if the device will properly load if you reset and then plug in
> >> > after
> >> > the device comes up and that works.
> >> >
> >> > > 2. If I connect the O2 Flame with the PC through ActiveSync for
> >> > > syncing
> >> > > some
> >> > > other files. Then I connect back the Flame to the device. I see again
> >> > > the
> >> > > same message box "Unidentified devcie". Whereas the device was
> >> > > working
> >> > > fine
> >> > > before I connect to PC over ActiveSync.
> >> >
> >> > AS is using the client side. If one is interfering with the other, it
> >> > makes
> >> > me think that the device is using an OTG chip, and the same controller
> >> > is
> >> > handlign both host and client requests and that the OEM screwed up in
> >> > their
> >> > implementation. Using WM as a host is rare, so they probably never
> >> > tested
> >> > the scenario you're using.
> >> >
> >> >
> >> > --
> >> >
> >> > Chris Tacke, Embedded MVP
> >> > OpenNETCF Consulting
> >> > Giving back to the embedded community
> >> > http://community.OpenNETCF.com
> >> >
> >> >
> >> >
>
>
>
From: Manas on
Thanx again Chris for the reply.
It is really tedious to develop code without using debugging tools. But I
will have to find some solution.
To debug, the only way I could find is putting file write statements. I have
file write statements in DLL main process attach and detach and all the other
functions. From the outputs in the file, I could see that the dll main and
all the other functions are getting called nicely when the driver is working
perfectly. But there is no output statment atall(not even from dllmain) from
anywhere in the cases of "Uidentified Device". So I think the dll is not
getting loaded.
Can you please throw some light on certificate. I am a bit concern on this.
After reset the USB host might try to load the function driver way before the
security system is loaded. Will that cause any problem.
Thanx,
Manas.

"Chris Tacke, eMVP" wrote:

> Without availability of platform tools, which I've always had for doing
> driver work, I don't really know. For some reason the USB host driver is
> unable to eitehr find or load your function driver. If you can't put a
> break or at least debug output into the host driver, I have no idea how
> you'd find out why. This must be why I never do driver work on WinMo.
>
>
> --
>
> Chris Tacke, Embedded MVP
> OpenNETCF Consulting
> Giving back to the embedded community
> http://community.OpenNETCF.com
>
>
>
> "Manas" <Manas(a)discussions.microsoft.com> wrote in message
> news:BD78A99C-7262-4A1F-8004-6A0C9C239B79(a)microsoft.com...
> > Hi,
> > I am still not able to figure out the reason behind the "Unidentified
> > device" message, when I plug in my device. As I explained below, the
> > driver
> > works fine with the device but the system fails to load my driver at
> > certain
> > instances.
> > 1. Connect O2 Flame to PC ActiveSync. Do some sync. Then connect back to
> > the
> > device, driver loading fails.
> > 2. Leave te device connected to the O2Flame, then reset O2 flame. It boots
> > up but witht he "Unidentified device" message.
> > Chris could you get a chance to think about this. As I said, if the
> > device is replaced by a mass storage in both the above situation, it is
> > working fine. Anything to do with code signing, or OS image (OS image have
> > the mass storage driver but my installed driver goes to some flash)?
> > We need to resolve this issue quickly to release the s/w.
> > Please help.
> > Thanx
> > Manas.
> >
> > "Manas" wrote:
> >
> >> Thanks Chris for the reply.
> >> But I have a point here.
> >> Like wise if instead of the device, I connect a Thumb drive(mass
> >> storage) to the Flame OTG, and perform the same 2 operation as I did
> >> below,
> >> it works perfectly fine and their is no problem atall. That may prove
> >> that
> >> the OTG driver is able to switch correctly between the client and host.
> >> I have 2 concern here:
> >> 1. The mass storage driver is included in the OS image(nk.bin) of the
> >> Flame.
> >> Where as the driver that I installed might get stored in some Flash.
> >> 2. Anything to do with code signing, authentication. I have signed my
> >> driver
> >> dll with the certificate that comes with the Windows Mobile 5, and
> >> installed
> >> that sdkcert.cab file into the Flame (But I don't see any certificate
> >> added
> >> to the certifcate list in the control panel). I also tried changing the
> >> Flame
> >> previledge level using the cpf files included in the Windows Mobile 5
> >> SDK.
> >> I am not sure whether any of these causing the problem. Please let me
> >> know
> >> your opinion.
> >> Thanks,
> >> Manas.
> >>
> >> "Chris Tacke, eMVP" wrote:
> >>
> >> > > 1. If I leave the device connected to the O2 Flame and reset O2
> >> > > Flame. I
> >> > > receive the message box "Unidentified device", asking for the driver
> >> > > dll.
> >> > > If
> >> > > I specifiy the driver dll it fails to load.
> >> >
> >> > Likely the USB hoist driver sees the attached device early on in boot -
> >> > before the function driver is loaded. There may be nothing you can do
> >> > about
> >> > that if the device will properly load if you reset and then plug in
> >> > after
> >> > the device comes up and that works.
> >> >
> >> > > 2. If I connect the O2 Flame with the PC through ActiveSync for
> >> > > syncing
> >> > > some
> >> > > other files. Then I connect back the Flame to the device. I see again
> >> > > the
> >> > > same message box "Unidentified devcie". Whereas the device was
> >> > > working
> >> > > fine
> >> > > before I connect to PC over ActiveSync.
> >> >
> >> > AS is using the client side. If one is interfering with the other, it
> >> > makes
> >> > me think that the device is using an OTG chip, and the same controller
> >> > is
> >> > handlign both host and client requests and that the OEM screwed up in
> >> > their
> >> > implementation. Using WM as a host is rare, so they probably never
> >> > tested
> >> > the scenario you're using.
> >> >
> >> >
> >> > --
> >> >
> >> > Chris Tacke, Embedded MVP
> >> > OpenNETCF Consulting
> >> > Giving back to the embedded community
> >> > http://community.OpenNETCF.com
> >> >
> >> >
> >> >
>
>
>