Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

WindowsCE 6.0 + OTG support

0 views
Skip to first unread message

embedinfo

unread,
Sep 19, 2008, 12:21:30 PM9/19/08
to
Hi All,

We have ported WM6 BSP to Windows CE 6.0. As per as I know both WM6
and Windows CE 6.0 support USB OTG drivers. In WM6 BSP that I have,
OTG driver registry settings are defined under @CESYSGEN
CE_MODULES_USBOTG. I was able to compile the same OTG driver in
Windows CE 6.0. But I don't see OTG registry settings in reginit.ini
file. Is there any SYSGEN variable for OTG that I have not set,
because of which registry settings wrapped around CE_MODULES_USBOTG
are missing in reginit.ini?

Thanks
-Milind

Henrik Viklund

unread,
Sep 21, 2008, 4:50:11 PM9/21/08
to
On 19 Sep, 18:21, embedinfo <embedi...@gmail.com> wrote:

> file. Is there any SYSGEN variable for OTG that I have not set,
> because of which registry settings wrapped around CE_MODULES_USBOTG
> are missing in reginit.ini?

First of all, there's might be licensing/NDA issues with porting WM6
stuff to CE6. If you havn't allready, make sure you're allowed to ship
the ported code.

Now, if the missing registry section is guarded by a "; @CESYSGEN IF
CE_MODULES_USBOTG" you need to have "SYSGEN_USB==1" set for it to be
included.

Henrik Viklund
Prevas AB

embedinfo

unread,
Sep 22, 2008, 11:14:33 AM9/22/08
to

Hi,

Thanks for the input. I am able to get OTG working now on adding
SYSGEN_USB.
I will check with my supervisor about NDA.

Is there any specific reason, why we are not supposed to use WM6
driver?

Thanks

Henrik Viklund

unread,
Sep 23, 2008, 2:22:04 AM9/23/08
to
On 22 Sep, 17:14, embedinfo <embedi...@gmail.com> wrote:
> Is there any specific reason, why we are not supposed to use WM6
> driver?

Basically, building WM6 device images is done with a custom tool
(based on BP) and an extended WINCE500 codebase that has its own
licensing and NDA:s. If you take code from this codebase and port it
back to say PB5 you probalby need to double check with MS if they are
OK with it. However, if you recieved the code (and the right to use it
in you product) from a 3:rd party vendor you're probably OK.

Henrik Viklund
Prevas AB

0 new messages