|Boards Supported||Mamba (VL-EBX-37)|
|Expansion Modules Supported||VL-EPMs-E1|
|OS Version||Windows Embedded CE 6.0 R3 (BUILD 3122 Jan 25 2010)|
|IDE/Platform||Platform Builder (Visual Studio 2005)|
|MNTV||Intel Montevina Platform|
VersaLogic is making no claims of usability, efficacy or warranty. Information in this document is provided in connection with VersaLogic products. No license, express or implied, by estoppel or otherwise, to any intellectual property rights is granted by this document. VersaLogic assumes no liability whatsoever, and VersaLogic disclaims any express or implied warranty relating to the sale and/or use of VersaLogic products, including liability or warranties relating to fitness for a particular purpose, merchantability or infringement of any patent, copyright or other intellectual property right. VersaLogic products are not intended for use in life-saving or life-sustaining applications.
VersaLogic disclaims all warranties and liabilities for the use of this document and the information contained herein, and assumes no responsibility for any errors which may appear in this document, nor does VersaLogic make a commitment to update the information contained herein. VersaLogic reserves the right to make changes to this document at any time without notice.
This BSP is based on Intel's Unified BSP (version 2.4). This document is an addendum to Intel's Unified BSP documentation and primarily discusses only details specific to VersaLogic's Wildcat (VL-EPMp-34), Leopard (VL-EPM-35), Komodo (VL-EPICs-36) and Mamba (VL-EBX-37) boards. This BSP has been modified to include DLL drivers for the 82574L/82541ER Ethernet device, GM45/GS45 graphics device, serial ports, etc. This BSP supports EBOOT/KITL for the 82574L/82541ER Ethernet devices in its default state.
SATA device - Hard drive as boot media
-- or --
USB device - Hard drive or jump drive as boot media
We strongly recommend installing all of the updates for CE 6.0 if you haven't recently updated your CE 6.0 installation. Please see  for more information on how to download updates.
We are assuming that you are going to work from your C: drive and that your $(_WINCEROOT) = C:\WINCE600. If that is not the case, you will need to substitute the proper path as per your customized setup. If you installed CE 6.0 with default settings you should be set up already.
Third Party→CoreCon→CoreCon_v200_x86See Section 3.0 (7,8) and Section 9.0 for more details.
C:\WINCE600\OSDesigns\MontevinaOSDesign\MontevinaOSDesign\RelDir\Montevina_x86_ReleaseCopy this NK.bin file on a CE 6.0 bootable media and boot from it. Alternatively, you can use EBOOT.bin to boot your NK.bin file over Ethernet.
Additional software/hardware components can be added to your image by clicking on the "Catalog Items View" from the left project pane. Some recommended components to be included are:
If you are using our supplied sample projet file (MontevinaOSDesign.pbxml), you do not need to perform these steps. However, we recommend that you still read this section for a better understanding of BSP modifications.
copy %_WINCEROOT%\3rdParty\82574\E1Q51CE6.dll %_FLATRELEASEDIR%\E1Q51CE6.dll
CEPB_INTELE1Q_PCIE=1in your platform's batch file (Montevina.bat) located at:
copy %_WINCEROOT%\3rdParty\82541\e1000ce6.dll %_FLATRELEASEDIR%\e1000ce6.dll
set CEPB_INTELGBE_VL-E=1in your platform's batch file (Montevina.bat) located at:
copy %_WINCEROOT%\3rdParty\IEGD_MNTV\Driver\ddi_iegd.dll %_FLATRELEASEDIR%\ddi_iegd.dllIf you require a graphics driver with a specific resolution and/or feature, you will need to generate your own CE 6.0 driver using Intel's IEGD utility . By default, we supply the driver with the registry settings for 1024 x 768 resolution. We have also supplied a drive registry file for 1280 x 1024 resolution called iegd.reg.1280x768 at:
copy %_WINCEROOT%\3rdParty\IEGD_MNTV\Driver\iegd3dg3.dll %_FLATRELEASEDIR%\iegd3dg3.dll
copy %_WINCEROOT%\3rdParty\IEGD_MNTV\Driver\iegd3dg4.dll %_FLATRELEASEDIR%\iegd3dg4.dll
copy %_WINCEROOT%\3rdParty\IEGD_MNTV\Driver\iegd3dga.dll %_FLATRELEASEDIR%\iegd3dga.dll
copy %_WINCEROOT%\3rdParty\IEGD_MNTV\Driver\analog.dll %_FLATRELEASEDIR%\analog.dll
copy %_WINCEROOT%\3rdParty\IEGD_MNTV\Driver\lvds.dll %_FLATRELEASEDIR%\lvds.dll
copy %_WINCEROOT%\3rdParty\IEGD_MNTV\driver\libGLES_CM.dll %_FLATRELEASEDIR%\libGLES_CM.dll
copy %_WINCEROOT%\3rdParty\IEGD_MNTV\driver\libGLESv2.dll %_FLATRELEASEDIR%\libGLESv2.dll
copy %_WINCEROOT%\3rdParty\IEGD_MNTV\driver\libOpenGL.dll %_FLATRELEASEDIR%\libOpenGL.dll
copy %_WINCEROOT%\3rdParty\IEGD_MNTV\driver\isr_iegd.dll %_FLATRELEASEDIR%\isr_iegd.dll
C:\WINCE600\3rdParty\IEGD_MNTVTo get 1280 x 1024 resolution on your CE image, just rename the above registry file to iegd.reg and select Advanced Build Commands→Rebuild Current BSP and Subprojects from Platform Builder.
set BSP_DISPLAY_IEGD=1in your platform's batch file (Montevina.bat) located at:
C:\WINCE600\PLATFORM\MontevinaNote: The Wildcat (VL-EPMp-34) and Leopard (VL-EPM-35) are both based on the same CPU board; the difference is that the Leopard includes an additional I/O board for enhanced functionality.
If you are using the project file MontevinaOSDesign.pbxml supplied by VersaLogic at:
then the following services/servers are enabled by default:
You configure the settings for the above services/servers in the platform.reg file.
You can access the target system using the telnet utility. After booting NK.bin on the target device, just launch a telnet command from any workstation (Windows, Linux, etc.) like this:
C:\Documents and Settings\User>telnet wince
-- or --
C:\Documents and Settings\User>telnet 192.168.0.136
192.168.0.136 = IP address of the GeodeLX based target device
-- and --
wince = machine name of the target device which is defined in platform.reg file at:
Now you should be able to see your familiar CE 6.0 console with the command prompt ready to take commands, like this:
Welcome to the Windows CE Telnet Service on WinCE
Pocket CMD v 6.00
Once your CE image boots on your target device, launch any web browser from any machine and type in:
-- or --
and you will see the complete contents of the root (/) directory of your target device. To further manage the server remotely, give the following command:
and then create a new password. After that, the device will reset and you will be asked to enter the default username (which is admin) and password (which you just created).
From any workstation give the following command:
C:\Documents and Settings\User>ftp wince
-- or --
C:\Documents and Settings\User>ftp 192.168.0.136
and enter the details as follows:
Connected to wince.
220 Service ready for new user.
User (wince:(none)): anonymous
331 Anonymous access allowed, send identity (e-mail name) as password.
230 User logged in, proceed.
To mount a shared windows folder which resides on a machine on your CE target device, give the following command on the target device:
net use winshare \\windowssharemachine\shareddocs
windowssharemachine = is a Windows machine (example: Windows XP)
shareddocs = a shared folder on the above Windows machine
winshare = destination folder name under which the contents of shareddocs will be mounted (you can give any name you want)
After giving the above command, a username/password dialog box will pop-up. After entering the details you will be able to see the share on your CE target device at:
You can access the above from the My Device icon on the CE desktop.
Similarly, to mount a shared folder which resides on the CE target device on a Windows machine (example: Windows XP), give the following command from a Windows XP machine:
C:\Documents and Settings\User>net use q: \\wince\MYSHARE
MYSHARE = name (alias) of the shared folder called Temp on the CE target device.
You can change the alias name and the folder to share in the platform.reg file.
Here we will discuss how to do remote application debug using the Core Connectivity method in VS 2005. The steps are heavily borrowed from . Also we recommend that you use your sample project file to walk through these steps to minimize errors.
Core OS→CEBASE→CAB File Installer/Uninstaller
Each time the target device resets power and reboots, the ConmanClient2.exe executable needs to launch again.
Since the CoreConOverrideSecurity entry in the registry disable security, the CMaccept.exe executable is not needed for this exercise.
With the CoreCon Connectivity established, we are ready to deploy the managed code application to the CE target device. From the VS 2005 IDE, select Debug→Start Debugging and when asked select Montevina x86 Device and click on Deploy button to deploy the application to the target device. As the application is being deployed, a series of activities is shown on the VS 2005 IDE’s output tab. After deploying, the application is launched on the target device’s CE desktop.
The following features have been tested on this BSP:
Following are the BIOS/CMOS settings that you will need to set for the serial ports to function:
|Name||IOBASE||IRQ||Modes Tested||Boards Tested|
By default, Windows CE uses a Serial/COM port (typically COM1) with IOBASE=0x3F8 and IRQ=4 to send out debug messages. Note that this feature does not use the actual serial port CE driver com16550.dll, it just uses the serial port hardware to output debug messages at 38400,8,N,1 baud rate and hence the COM1 port should be available for use by your application. The supplied project file (MontevinaOSDesign.pbxml) is set up to enable all four serial ports. You can tweak the serial port settings (IO Base Address, IRQs, etc.) by modifying the platform.reg file as per your requirements. Please refer to the board manuals [3,4,5,6] for additional configuration information.
Microsoft Windows CE BIOS Bootloader
C:\WINCE600\3rdParty\82574\Copy the EBOOT.bin file if you want to immediately begin building and booting Debug images over Ethernet.
The EBOOT.bin file is exactly the same in both of the directories i.e. the EBOOT.bin will support both 82574L and 82541ER Ethernet.
ProjectName→Device Drivers→Input Devices→Keyboard/Mouse→NOP (Stub) Keyboard/Mouse EnglishOtherwise, the USB mouse and keyboard won't be functional when the CE desktop loads. The sample project file MontevinaOSDesign.pbxml does NOT have the above catalog item selected and therefore the image that you build from this project file will not have USB mouse and keyboard support.
Copyright © 2010 VersaLogic Corp. All rights reserved.