Search

Technical Discussion Group Forum

This forum is provided for user discussion. While Beacon EmbeddedWorks support staff and engineers participate, Beacon EmbeddedWorks does not guarantee the accuracy of all information within in the Technical Discussion Group (TDG).

The "Articles" forums provide brief Articles written by Beacon EmbeddedWorks engineers that address the most frequently asked technical questions.

To receive email notifications when updates are posted for a Beacon EmbeddedWorks product download, please subscribe to the TDG Forum of interest.

TDG Forum

PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 23 Jun 2008 04:08 PM by  sam.siciliano@gmail.com
Creating Custom OS Image with BSP Source
 0 Replies
Sort:
You are not authorized to post a reply.
Author Messages
sam.siciliano@gmail.com
New Member
New Member
Posts:


--
23 Jun 2008 04:08 PM
    As an FYI (for anyone interested), here are some things that could possibly help when building your own custom OS image using Version 0.4.0 of the WinCE 6.0 BSP source provided on the website:

    The LPD touch calibration app that comes with the BSP depends (I think) on some "headed" catalog components, resulting in build errors for my headless image. To fix I removed the project by doing the following steps (as I couldn't find a BSP environment variable for it):

    ** Removed the DIRS entry (\WINCE600\PLATFORM\LPD_OMAP3430_SOM\SRC\UTILS) for lpd_touchcal
    ** Removed .bib entry (line 403 of C:\WINCE600\PLATFORM\LPD_OMAP3430_SOM\FILES\platform.bib) for touchcal.exe
    ** Set the environment variable "BSP_NOTOUCH" (so the associated touch.dll isn't included)

    Also, I initially ran into some errors in compiling C:\WINCE600\PLATFORM\LPD_OMAP3430_SOM\SRC\OAL\OALLIB\platform.c during the BSP phase of the build. Simply copying the working environment variables set in the example workspace to my custom workspace fixed this problem. To do this, load the sample workspace, right click on the workspace name in the "Solution Explorer" tab and select "properties". Go to "Configuration Properties\Environment" to see all the environment variables you need to add to your own custom workspace (bsp_nomadc=1, bsp_nodvfs=1, etc). These can also be found in the sample workspace .pbxml file. Don't forget to do this for each build configuration.
    You are not authorized to post a reply.