Hi

I am developing USB-OTG device driver module for Mainstone II board in
WinCE 5.0.

The module is not available with the WinCE 5.0 for Mainstone II rather
the USB OTG driver is availble with WinCE 6.o Mainstone II board.

Now I am doing BSP cloning for Mainstone II and adding the OTG driver
by picking it up from WinCE 6.0/MainstoneIII/ drivers folder. Now I am
facing certain issues in the same.:-

There are certain header files - like pkfuncs.h, defbus.h and many
others have been modified and many new header file have been added

As a result of this - while building my driver - its giving lots of
erros.

Now some of the issues are WinCE 6.0 and some other are hardware
(Mainsone II and Mainstone III specific)

Since I am new ot WinCe - I am not sure - whether this approach is
correct for building the OTG driver or not.

Kindly help me on the same.


Thanks & Regards

Aman

Re: OTG module development for Mainstone II PXA270X - WinCE 5.0 by Henrik

Henrik
Sat Feb 03 08:59:35 CST 2007

What you're about to do may violate at least one of the licenses (CE5
or CE6) so before shipping code ripped from CE6 in a CE5 licensed
image/BSP, make sure you untangle any licensing issues with MS, OK?

Regarding MII/MIII issues, you know there's a MIII BSP for CE5 that
might be a closer match to the CE6 BSP?

Henrik Viklund
http://www.addlogic.se

On Feb 3, 12:34 pm, "aman" <amitjob...@gmail.com> wrote:
> Hi
>
> I am developing USB-OTG device driver module for Mainstone II board in
> WinCE 5.0.
>
> The module is not available with the WinCE 5.0 for Mainstone II rather
> the USB OTG driver is availble with WinCE 6.o Mainstone II board.
>
> Now I am doing BSP cloning for Mainstone II and adding the OTG driver
> by picking it up from WinCE 6.0/MainstoneIII/ drivers folder. Now I am
> facing certain issues in the same.:-
>
> There are certain header files - like pkfuncs.h, defbus.h and many
> others have been modified and many new header file have been added
>
> As a result of this - while building my driver - its giving lots of
> erros.
>
> Now some of the issues are WinCE 6.0 and some other are hardware
> (Mainsone II and Mainstone III specific)
>
> Since I am new ot WinCe - I am not sure - whether this approach is
> correct for building the OTG driver or not.
>
> Kindly help me on the same.
>
> Thanks & Regards
>
> Aman



Re: OTG module development for Mainstone II PXA270X - WinCE 5.0 by aman

aman
Mon Feb 05 05:50:59 CST 2007


Henrik

Thanks 4 d advise.

I am preparing the drver for my internal use only - not for any
release. So need to worry :)

Well WinCe 5.0 does not contain MIII folder so that option of using
OTG code goes away.

Hence I need to look at the things afresh but with lot of
complexities.

Would appreciate if sum can guide me more on developing OTG drivers -
and layers in the same.

->Does OTG share the USB HCD and USB function controller driver.

->And whats the difference b/w USB client driver and OTG client driver

Regards

Aman

On Feb 3, 7:59 pm, "Henrik Viklund" <henrik.vikl...@gmail.com> wrote:
> What you're about to do may violate at least one of the licenses (CE5
> or CE6) so before shipping code ripped from CE6 in a CE5 licensed
> image/BSP, make sure you untangle any licensing issues with MS, OK?
>
> Regarding MII/MIII issues, you know there's a MIII BSP for CE5 that
> might be a closer match to the CE6 BSP?
>
> Henrik Viklundhttp://www.addlogic.se
>
> On Feb 3, 12:34 pm, "aman" <amitjob...@gmail.com> wrote:
>
>
>
> > Hi
>
> > I am developing USB-OTG device driver module for Mainstone II board in
> > WinCE 5.0.
>
> > The module is not available with the WinCE 5.0 for Mainstone II rather
> > the USB OTG driver is availble with WinCE 6.o Mainstone II board.
>
> > Now I am doing BSP cloning for Mainstone II and adding the OTG driver
> > by picking it up from WinCE 6.0/MainstoneIII/ drivers folder. Now I am
> > facing certain issues in the same.:-
>
> > There are certain header files - like pkfuncs.h, defbus.h and many
> > others have been modified and many new header file have been added
>
> > As a result of this - while building my driver - its giving lots of
> > erros.
>
> > Now some of the issues are WinCE 6.0 and some other are hardware
> > (Mainsone II and Mainstone III specific)
>
> > Since I am new ot WinCe - I am not sure - whether this approach is
> > correct for building the OTG driver or not.
>
> > Kindly help me on the same.
>
> > Thanks & Regards
>
> > Aman- Hide quoted text -
>
> - Show quoted text -



Re: OTG module development for Mainstone II PXA270X - WinCE 5.0 by Henrik

Henrik
Mon Feb 05 07:01:52 CST 2007

On Feb 5, 12:50 pm, "aman" <amitjob...@gmail.com> wrote:
> Henrik
>
> Thanks 4 d advise.
>
> I am preparing the drver for my internal use only - not for any
> release. So need to worry :)
>
> Well WinCe 5.0 does not contain MIII folder so that option of using
> OTG code goes away.

MIII is available for CE5. You just need to install it:

http://www.microsoft.com/downloads/details.aspx?FamilyID=BDF43D00-55B6-4E51-82A5-F0A8395D4903&displaylang=en

Henrik Viklund
http://www.addlogic.se

>
> Hence I need to look at the things afresh but with lot of
> complexities.
>
> Would appreciate if sum can guide me more on developing OTG drivers -
> and layers in the same.
>
> ->Does OTG share the USB HCD and USB function controller driver.
>
> ->And whats the difference b/w USB client driver and OTG client driver
>
> Regards
>
> Aman
>
> On Feb 3, 7:59 pm, "Henrik Viklund" <henrik.vikl...@gmail.com> wrote:
>
>
>
> > What you're about to do may violate at least one of the licenses (CE5
> > or CE6) so before shipping code ripped from CE6 in a CE5 licensed
> > image/BSP, make sure you untangle any licensing issues with MS, OK?
>
> > Regarding MII/MIII issues, you know there's a MIII BSP for CE5 that
> > might be a closer match to the CE6 BSP?
>
> > Henrik Viklundhttp://www.addlogic.se
>
> > On Feb 3, 12:34 pm, "aman" <amitjob...@gmail.com> wrote:
>
> > > Hi
>
> > > I am developing USB-OTG device driver module for Mainstone II board in
> > > WinCE 5.0.
>
> > > The module is not available with the WinCE 5.0 for Mainstone II rather
> > > the USB OTG driver is availble with WinCE 6.o Mainstone II board.
>
> > > Now I am doing BSP cloning for Mainstone II and adding the OTG driver
> > > by picking it up from WinCE 6.0/MainstoneIII/ drivers folder. Now I am
> > > facing certain issues in the same.:-
>
> > > There are certain header files - like pkfuncs.h, defbus.h and many
> > > others have been modified and many new header file have been added
>
> > > As a result of this - while building my driver - its giving lots of
> > > erros.
>
> > > Now some of the issues are WinCE 6.0 and some other are hardware
> > > (Mainsone II and Mainstone III specific)
>
> > > Since I am new ot WinCe - I am not sure - whether this approach is
> > > correct for building the OTG driver or not.
>
> > > Kindly help me on the same.
>
> > > Thanks & Regards
>
> > > Aman- Hide quoted text -
>
> > - Show quoted text -- Hide quoted text -
>
> - Show quoted text -



Re: OTG module development for Mainstone II PXA270X - WinCE 5.0 by aman

aman
Mon Feb 05 09:20:34 CST 2007

On Feb 5, 6:01 pm, "Henrik Viklund" <henrik.vikl...@gmail.com> wrote:
> On Feb 5, 12:50 pm, "aman" <amitjob...@gmail.com> wrote:
>
> > Henrik
>
> > Thanks 4 d advise.
>
> > I am preparing the drver for my internal use only - not for any
> > release. So need to worry :)
>
> > Well WinCe 5.0 does not contain MIII folder so that option of using
> > OTG code goes away.
>
> MIII is available for CE5. You just need to install it:
>
> http://www.microsoft.com/downloads/details.aspx?FamilyID=BDF43D00-55B...
>
> Henrik Viklundhttp://www.addlogic.se
>
>
>
>
>
> > Hence I need to look at the things afresh but with lot of
> > complexities.
>
> > Would appreciate if sum can guide me more on developing OTG drivers -
> > and layers in the same.
>
> > ->Does OTG share the USB HCD and USB function controller driver.
>
> > ->And whats the difference b/w USB client driver and OTG client driver
>
> > Regards
>
> > Aman
>
> > On Feb 3, 7:59 pm, "Henrik Viklund" <henrik.vikl...@gmail.com> wrote:
>
> > > What you're about to do may violate at least one of the licenses (CE5
> > > or CE6) so before shipping code ripped from CE6 in a CE5 licensed
> > > image/BSP, make sure you untangle any licensing issues with MS, OK?
>
> > > Regarding MII/MIII issues, you know there's a MIII BSP for CE5 that
> > > might be a closer match to the CE6 BSP?
>
> > > Henrik Viklundhttp://www.addlogic.se
>
> > > On Feb 3, 12:34 pm, "aman" <amitjob...@gmail.com> wrote:
>
> > > > Hi
>
> > > > I am developing USB-OTG device driver module for Mainstone II board in
> > > > WinCE 5.0.
>
> > > > The module is not available with the WinCE 5.0 for Mainstone II rather
> > > > the USB OTG driver is availble with WinCE 6.o Mainstone II board.
>
> > > > Now I am doing BSP cloning for Mainstone II and adding the OTG driver
> > > > by picking it up from WinCE 6.0/MainstoneIII/ drivers folder. Now I am
> > > > facing certain issues in the same.:-
>
> > > > There are certain header files - like pkfuncs.h, defbus.h and many
> > > > others have been modified and many new header file have been added
>
> > > > As a result of this - while building my driver - its giving lots of
> > > > erros.
>
> > > > Now some of the issues are WinCE 6.0 and some other are hardware
> > > > (Mainsone II and Mainstone III specific)
>
> > > > Since I am new ot WinCe - I am not sure - whether this approach is
Henrik

Appreciate that - the link contains Mainstone iii bsp functionality
for WinCE 5.0

But unfortunately it does not contain OTG functionality

Can somebody tell me - dat if I wish to test OTG port on my mainstone
ii board - Wince 5.0/6.0 then what all functionalities or dlls i need
to create apart from application code.

I know one dll - dats ms2_usbotg.dll - but its not enough to test
functionality if i have to test some otg function device availabl with
me.

Thanks & Regards

aman


> > > > correct for building the OTG driver or not.
>
> > > > Kindly help me on the same.
>
> > > > Thanks & Regards
>
> > > > Aman- Hide quoted text -
>
> > > - Show quoted text -- Hide quoted text -
>
> > - Show quoted text -- Hide quoted text -
>
> - Show quoted text -