This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

SDK for Win CE 6.0 and OMAP L138

Other Parts Discussed in Thread: OMAP-L138, OMAPL138

Hi Guys,

I really have problems to develop Windows CE Applications on the OMAP L138, I hope you can help me.

I've the ZOOM OMAP-L138 eXperimeter Kit. The kit included an already build OSDesign of Windwos CE on a SD Card. If I plug in the card and start the board, I can see the Win CE Screen and start menu on the display, so everythings perfect till now. The only thing I want to do now is to write a Hello World program, running on the OMAP board on Win CE.

So how do i do that? My thoughts are to build a SDK for the OSDesign, implement it in Visual Studio and begin writing the Hello World program. But how do i get such a SDK. I tried the AM18x/OMAP-L138 WinCE BSP Quick Start Guide. In this gute you build your own OSDesign in Visual Studio. I believe I don't need this, cause I already have an running WinCE OS on my OMAP, but I thought I need an OSDesign to build the SDK out of it. So I installed all the components on page 2 and tried building the OS described on page 5. Unfortunately I get error: "Cannot include both, Audio and SDMC driver".

Please guys, if you have any hints tell me, I'm sitting here for days trying to write a Hello World application on WinCE, it starts to be frustrating :). It can't be that hard.

Thanks a lot

Regards,

Manuel Rohrauer

  • The build error is because omapl138 does not support both simultaneously due to pin mux conflicts.  

    Please make sure at most one of the following two drivers is enabled in the OSDesign catalog:

      PB > Catalog Item View > Third Party > BSP > OMAPL138_AM18X > Device Drivers > Audio > AIC3106 Audio Codec

      PB > Catalog Item View > Third Party > BSP > OMAPL138_AM18X > Device Drivers > Storage Devices > SD Host Controller

    For more informations about SDK, this and other MSDN articles might help.

    Regards

    WM