Compulab Mediawiki - User contributions [en]

CM-X300: WinCE: SPI Driver API

2010-04-15T06:46:12Z

Shai: added ssp1 referenece

= Introduction =
This sample application demonstrates the SPI communication between CM-X300 and Maxim Semiconductor DS1722 thermometer. The DS1722 manual is available at: [http://www.maxim-ic.com/quick_view2.cfm/qv_pk/2766/t/al DS1722 manual].

The Windows CE demo image includes the SPI driver, which allows direct access to SSP3 and SSP1 functionality.
= SPI Sample =
== Connecting the device to CM-X300 ==
* The SPI device can be connected to the SSP3 port available on connector P6 on SB-X300. The following table describes the connector pin-out:
{|cellpadding="3" border="1" style="border: 1px solid rgb(85, 85, 85); border-collapse: collapse;"
| '''Signal Name''' || '''Pin Number'''
|-
| SSP3_TXD || 5
|-
| SSP3_RXD || 7
|-
| SSP3_CLK || 3
|-
| SSP3_SFRM || 1
|}
* Connect pin 6 (SERMODE) of DS1722 to VDD.
* Connect all remaining DS1722 pins to VDD and GND according to the device datasheet.
* Refer to [http://compulab.co.il/x300/download/x300-cm-man.pdf CM-X300-Man] for gpio mapping of SSP1.

== SPI Sample ==

The SPI Sample performs the following actions:
* Configure the SPI clock frequency (5KHz) and SFRM signal polarity.
* Read the temperature measurement.
* Write to the DS1722 configuration register.
* Read back from the configuration register.

= SPI Driver =
== Overview ==
The CM-X300 SPI driver is a stream driver that may be accessed using the "SPI" prefix.

== SPI Driver API ==
=== Data Types ===
{{Struct | HeadLevel = ==== | Structname = SPI_SLAVE_CONFIG |
Description = Device configuration structure|
Field1 = DWORD dwDataSize |
Fieldexp1 = Size of each data frame in bits, allowed values: [4,32] |
Field2 = DWORD dwClockRate|
Fieldexp2 = Frequency in KHz. Allowed values: [4,13*1024] |
Field3 = [[#POLARITY|POLARITY]] ClockPol|
Fieldexp3 = Clock polarity |
Field4 = [[#POLARITY|POLARITY]] ChipSelectPol |
Fieldexp4 = SFRM polarity |
Field5 = BOOL bTxTristate |
Fieldexp5 = Tristate TX line when SFRM is de-asserted |
Field6 = BOOL ClkPhaseHalfCycle|
Fieldexp6 = TRUE - CLK remains in its inactive/idle state until one-half clock cycle after the SFRM signal is asserted at the beginning of a frame. 
FALSE - CLK remains in its inactive/idle state until one full clock cycle after the SFRM signal is asserted at the beginning of a frame. 
Meaningless when bCSExternal = TRUE |
Field7 = BOOL bCSExternal|
Fieldexp7 = SFRM is a GPIO |
Field8 = DWORD dwGpioNum|
Fieldexp8 = GPIO number for SFRM |
Remarks = bCSExternal is not supported in CM-X300|
}}
{{Struct | HeadLevel = ==== | Structname = SPITRANS|
Description = Transaction data|
Field1 = DWORD mTransactions |
Fieldexp1 = Number of data frames in the transaction|
Field2 = DWORD *mWriteBuffer |
Fieldexp2 = Data to be written to the port|
Field3 = DWORD *mReadBuffer |
Fieldexp3 = Data that was read from the port|
Field4 = | Field5 = | Field6 = | Field7 = | Field8 = |
Remarks = |
}}
{{Enum| HeadLevel = ==== | Enumname = POLARITY |
Description = Signals polarity enumeration|
Field1 = LOW_INACTIVE |
Field2 = HIGH_INACTIVE |
Field3 = |
Field4 = |
Remarks = |
}}
=== Functions ===
{{APIEx | HeadLevel = ==== | Signature = HANDLE SPIUserOpen() |
Description = Opens an instance of the SPI Bus Driver. |
Return = Returns a handle that should be used to access the driver. Nonzero indicates success. |
Param1 = |
Param2 = |
Param3 = |
Param4 = |
Remarks = }}

{{APIEx | HeadLevel = ==== | Signature = VOID SPIUserClose (HANDLE hDevice) |
Description = Closes the driver handle |
Return = |
Param1 = *hDevice - Handle to an open SPI bus instance|
Param2 = |
Param3 = |
Param4 = |
Remarks = }}

{{APIEx | HeadLevel = ==== | Signature = BOOL SPIUserSetConfiguration(HANDLE hDevice, [[#SPI_SLAVE_CONFIG|SPI_SLAVE_CONFIG]]* Settings) |
Description = Registers the configuration of the device.|
Return = TRUE - indicates success.|
Param1 = *hDevice - Handle to an open SPI bus instance|
Param2 = *Settings - The SPI device configuration|
Param3 = |
Param4 = |
Remarks = The device specific configuration is passed to the SPI controller immediately before the transaction starts. The driver keeps the configuration between calls to this function or until the SPI bus handle is closed}}

{{APIEx | HeadLevel = ==== | Signature = BOOL SPIUserTransact (HANDLE hDevice, [[#SPITRANS|SPITRANS]]* pTrans) |
Description = Submits SPI data transaction to the target device |
Return = TRUE - indicates success.|
Param1 = *hDevice - Handle to an open SPI bus instance|
Param2 = *pTrans - pointer to data structures containing data buffers for the transaction
|
Param3 = |
Param4 = |
Remarks = The SPI transaction data buffers must be allocated and released by the user
}}

[[Category:Windows CE|SPI Sample ]]
[[Category:CM-X300|WinCE: SPI Sample ]]

CM-X300 WinCE

2010-04-14T13:46:43Z

Shai:

{{summary|
This page contains links to information related to the Windows Embedded CE demo package for the CM-X300

The Windows CE package by Compulab supports a ready to run demo image, an SDK that enables application development, and a BSP that allows you to customize the run-time image
|X300-cm-top-m.jpg|thumb}}
{{Resources_Windows
|* [[CM-X300: WinCE: Getting Started|Getting started]]
* [[CM-X300: WinCE: Demo Image|Using the Demo Image]]
* [[CM-X300: WinCE: Configuring Eboot|Configuring Eboot]]
|* [[WinCE: Application Development|Application Development]]
* [[WinCE: Platform Builder Installation | Platform Builder installation]]
* [[CM-X300: WinCE: OSDesign Configuration|OSDesign Configuration]]
* [[WinCE: OSDesign Development|OSDesign Creation]]
|*[[Support]]
* [[CM-X300: WinCE: Known Issues|Known Issues]]
}}
__NOTOC__
{{ChangelogRss| content=
===== 14-Apr-2010 =====
* General notes:
:- Built with QFE up to Jan 2010 R3
:- This release works with Uboot version 5 and above
* Bug fixes:
:- Fixed Suspend/Resume cycle
:- Fixed IP address handling
:- Fixed power levels for the processor
:- Fixed gpio driver crash in Updater
:- Fixed external rtc driver
:- Fixed power handling of bluetooth and wifi
:- Fixed the wakeup service
:- Fixed freeze problems when suspending
:- Fixed interrupt mapping for FFUART
:- Fixed SDK
:- Changed thread priority for the UART
* Added/Changed features:
:- Added Sysconf read of alternate function
:- Enabled L2 cache
:- Changed LED heart bit rate
:- GPIO83 puts the system to suspend
:- Image does not set MAC address. Relies on address set by Uboot
:- Splash screen support
:- Added support for new Nand flashes
:- Enabled ONKEY functionality of the PMIC
:- Added kernel ioctl to sync with external rtc
:- Changed the SDHC indexes to be fixed
:- Added support for SSP1 controller
:- Changed the SPI driver internals. API is still the same
:- Adjusted Camera driver to agree with latest QFE
:- Added RTC/CTS to BTUART
:- Changed the update process to be more stable
:- Added a reboot option in Eboot
:- Frequency is set in Uboot
===== 22-Nov-2009 =====
* Fixed GPIO83 wakeup functionality
* Fixed GPIOExtender interrupt handling bug
* Fixed MAC Address not loaded from UBoot bug
* Fixed MPEG4 playback issue
* Added Eboot configuration through the image updater’s script mode
* Added a Control Panel Applet to choose USB functionality for PXA310
* Added a service that simulates user activity on resume to fix hang on resume bug
* Added automatic detection of revision number (for revision 1.3 and above)
* Added a “Run Once”-like mechanism on first boot
* Added a Silverlight Demo Application
* Generated a new SDK that supports Silverlight for embedded devices
* This release was built using Windows CE 6.0 R3 and has the following items:
:- Silverlight for Embedded devices
:- Adobe Flash Lite ActiveX control for Internet Explorer
:- Gestures support
===== 22-Sep-2009 =====
* Added Bluetooth functionality support for PXA310
* Fixed Green LED functionality in Suspend mode
===== 08-Sep-2009 =====
* In this release only changes relevant to PXA310 were made. No changes were made to the PXA300 image.
* Updated Uboot script to operate properly with PXA310
* Added USB device support for PXA310
* Added Eboot option to clean registry
* Added Eboot option to choose USB functionality
* Added an optional application to activate Wi-Fi power save mode
* Fixed backlight behavior after Suspend
===== 14-Aug-2009 =====
* Corrected static libraries use
* Added support for PXA310 (separate image)
* Added control of Touch sensitivity through the registry
* Added CAB file for Video Acceleration support
* Added a C# demo application
===== 1-Jul-2009 =====
* Fixed minor bugs in LCDAdapt utility
* Fixed device power consumption in Sleep mode
* Fixed COM C and COM D functionality
* Fixed audio recording bug
* Added backlight driver
* Added SPI driver (for HW rev 1.2 and above)
* Added catalog item to the updater to support access to computers on a network
* Added a Battery driver
* Added GPIO as wakeup source from suspend mode
* Added preliminary support for QCI (Video Input)
===== 2-Apr-2009 =====
* Added support for the Hynix 128 MB NAND flash
* Added support for DRAM size detection
* Fixed the functionality of RTC for HW revision 1.2
* Fixed the suspend/resume functionality for Wi-Fi
* Added a FailSafe mechanism to the image updater
* Added script mode support to the image updater
* Fixed the loading of the MAC address from U-BOOT
* Added a CF 3.5 catalog item
* Added a CAB installer catalog item
* Added touch screen support to the updater image
* Changed relocation table handling
* Added a U-BOOT script to set all environment variables
* Added an LCD Adaptation utility
===== 24-Sep-2008 =====
* Added Touch screen functionality
* Ethernet controller retrieves configuration from Eboot
* Added KeyPad support
* Fixed USB 2.0 Slave Suspend/Resume functionality
* Added LED functionality
* Wi-Fi and Bluetooth can be configured through Eboot
* Fixed Wireless Config applet to indicate devices’ true states
* Added Keypad configuration applet
* Fixed audio to play stereo
* Added relocation table creation to Eboot
* Added desktop side driver INF for ActiveSync by Marvell
* Added the following SubProjects:
:- A2dpMgr
:- TCPMP
:- RegEdit
:- AutoLaunch
:- TaskManager
:- LookAndFeel
:- KeypadAppLaunch
===== 28-Aug-2008 =====
* Initial Release of Windows CE package
}}

[[Category:Windows CE]]
[[Category:CM-X300]]

CM-X300: WinCE: OSDesign Configuration

2010-04-14T13:27:13Z

Shai: /* Build Options */

== Installing the Driver Package ==
* Close the Platform Builder Application if it is open.
* Copy the CM_X300_BSP directory to \WINCE600\Platform\
* Copy the CM_X300_CE6 directory to \WINCE600\OSDesigns\
* Launch VS2005 and open \WINCE600\OSDesigns\CM_X300_CE6\CM_X300_CE6.sln

== Building the Platform Project ==
The CM_X300 Platform Project is used to build CompuLab Windows Embedded CE demo image. It includes many components and is highly recommended as a starting point for a new project. The demo image is relatively large, ~35 MB. Typical Windows CE images for a specific application are much smaller, 8-15 MB.

To build the CM_X300 platform:
* select the {{MenuEntry|Open->Project/Solution}} command from the File menu of the VS2005 and select the {{Filename|\WINCE600\OSDesigns\CM_X300_CE6\CM_X300_CE6.sln}} file.
* Check that the project is configured for Release.
* Perform {{Cmd|Rebuild Solution}} from the {{Cmd|Build}} menu (alternatively, perform {{MenuEntry|Build->Advanced Build Commands->Clean Sysgen}}).

The build process takes about 15-20 minutes.

=== CPU Type ===
The CM-X300 may be assembled with two CPU types:
* PXA300 - the C624 option
* PXA310 - the C624M option

The default BSP configuration targets the PXA310 CPU.

==== Choosing CPU Type ====
The CPU type is defined in {{Filename|CM_X300_BSP.BAT}} file in the platform directory. Ensure that the {{parameter|BSP_CPU_TYPE}} setting corresponds with the correct CPU type. Leave the appropriate line without the REM directive:
<pre>
set BSP_CPU_TYPE=310
REM set BSP_CPU_TYPE=300
</pre>

=== Build Options ===
* Use {{MenuEntry|Build->Advanced Build Commands->Sysgen}} when adding Platform Builder components (Catalog items) to the project.
* Use {{MenuEntry|Build->Advanced Build Commands->Clean Sysgen}} when removing Platform Builder components (Catalog items) from the project.
* Use {{MenuEntry|Build->Advanced Build Commands->Build Current BSP and Subprojects}} when modifying Compulab BSP components that are included in the project or performing changes in the BSP files.
* Use {{MenuEntry|Build->Advanced Build Commands-> Rebuild Build Current BSP and Subprojects}} when adding/removing Compulab BSP components to/from the project.
{{Warning|1=Do not use {{MenuEntry|Build->Advanced Build Commands->Build and Sysgen}} or {{MenuEntry|Build->Advanced Build Commands->Rebuild and Clean Sysgen}} that perform compilation and sysgen on the entire Platform Builder tree.
It is recommended to remove the two commands mentioned above from the menu permanently}}

== Windows CE Image Customization ==
There are two ways to customize the Windows CE image:
# Recommended method: Add or remove BSP components from the demo CM_X300_CE6 project.
# Create a new platform project and then manually add all the necessary BSP components as described in the Platform Builder documentation. Refer to [[WinCE: OSDesign Development|Windows CE OSDesign Development]] page.

=== BSP customization using batch files ===
The BSP is fully customizable and allows inclusion/exclusion of each component via BSP_NO environment variables.

To exclude a certain driver, set the BSP_NO environment variables in {{Filename|CM_X300_BSP\CM_X300_BSP_COMMON.bat}} and rebuild the BSP with {{MenuEntry|Build->Advanced Build Commands->Rebuild Current BSP and Subprojects}}.

The following table lists the BSP_NO environment variables that can be defined:

{| border="1"
|-
| '''Variable'''
| '''Meaning'''
| '''Comments'''
|-
| BSP_NOKEYPAD
| No Keypad driver and no support for keyboard
|
|-
| BSP_NODISPLAY
| No Graphics
|
|-
| BSP_NONAND
| No NAND Flash driver
|
|-
| BSP_NOSDHC
| No SDIO card driver
|
|-
| BSP_NOWLAN
| No WiFi driver
|
|-
| BSP_NOI2C
| No I2C driver
|
|-
| BSP_NOUSB20FN
| No Usb 2.0 Function driver
|
|-
| BSP_NOUSBFN
| No Usb 1.1 Function driver
|
|-
| BSP_NOUSBHOST
| No Usb Host driver
|
|-
| BSP_NOAUDIO
| No Audio driver
|
|-
| BSP_NOTOUCH
| No Touch screen driver
|
|-
| BSP_NOCODEC
| No Codec driver
| (no Touch and no Audio)
|-
| BSP_NOBLUETOOTH
| No BlueTooth Driver
| No Bluetooth stack as well
|}

{{Note|Any environment variable defined in CM_X300_BSP\CM_X300_BSP_COMMON.bat will override the variables defined in Platform Builder project}}

=== RAM-Based Registry support ===
The CM-X300 BSP is configured for HIVE-based registry with lazy flushing. The registry hive is located in the system NAND flash.
To support a RAM-Based registry, perform the following actions:
* Add the {{Filename|RAM-based Registry}} component to the project
* Disable the following variables in the {{filename|CM_X300_BSP\CM_X300_PRODUCTION.bat}}:
<pre>
set PRJ_ENABLE_FSREGHIVE=1
set PRJ_ENABLE_REGFLUSH_THREAD=1
</pre>
* Perform "Clean Sysgen" using {{MenuEntry|Build->Advanced Build Commands->Clean Sysgen}}

=== Persistent File System ===
The CM-X300 BSP is configured to store the root directory in RAM, therefore the root filesystem is not persistent. To make the root and its subsequent folders persistent, change the Catalog item "ROM and RAM File System" to "ROM-Only file System".

{{Note|Any data saved to a non-persistent location is erased when the device resets. This includes the root directory ("\").}}

== CM-X300 BSP Subprojects ==
In addition to the drivers supplied with the BSP, there are a few useful utilities distributed as Subprojects. Subprojects allow adding software modules to the build without modifying the BSP source code located in the Platform source tree.
There are two Subproject types available with CM_X300_BSP:
* Subprojects that add optional functionality to the BSP are located in the {{Filename|\WINCE600\PLATFORM\CM_X300_BSP\Subprojects}} directory.
: These Subprojects are provided with the source code.
{| border="1"
|-
| '''Project Name'''
| '''Functionality'''
|-
| ''SetPowerState''
| Command line utility that controls the system power state and is used for software reboot and suspend support
|-
| ''Regedit''
| Command line registry editor. Allows remote changes of the device registry via telnet connection.
|-
| ''CoreCon''
| Executables required for application level debugging over Ethernet in VS2005
|-
| ''AutoLaunch''
| Executable that should be used for automatic launch of CoreCon (ConmanClient2.exe) at system startup. AutoLaunch.exe verifies IP address availability before loading ConmanClient2.exe. This is required because ConmanClient2 waits for incoming TCP/IP connections when communicating with VS 2005
|-
| ''SysConf''
| Command line utility for platform debugging
|-
| ''Tools''
|
* Command line RTC_CMD utility for RTC driven suspend/resume cycles
* CLTerm program for COM ports testing
|-
| ''BuildVer''
| This project adds a text file to the image specifying which revision was used to build the image. It requires a Tortoise Svn client installed on the desktop.
|}

* The Subprojects that add custom applications, control panel applets and registry settings to the demo image are located at {{Filename|\WINCE600\OSDesigns\CM_X300_CE6\Subprojects}} directory.
{| border="1"
|-
| '''Project Name'''
| '''Functionality'''
|-
| ''CPLApplets\WireLessCPL''
| Control panel applet that controls the power state (on/off) of wireless devices
|-
| ''CPLApplets\KeypadConfigCPL''
| Control panel applet that customizes keypad buttons functionality
|-
| ''CPLApplets\BacklightCPL''
| Control panel applet that controls the LCD backlight level
|-
| ''TCPMP''
| Open source Media player
|-
| ''TaskManager''
| Open source Task Manager
|-
| ''KeypadAppLaunch''
| A utility to capture application launching key presses
|-
| ''LookAndFeel''
| Look and feel of the demo image (background, theme, sounds, etc.)
|}

== KITL Connection ==
Platform Builder communicates with a device using KITL protocol. For details about KITL refer to [http://www.microsoft.com/video/en/us/details/0a8d9767-a419-4f5e-9b37-4328b0993d1d Microsoft's KITL Broadcast] article.

The following actions should be performed in order to setup a KITL connection between the CM-X300 and Platform Builder 6.0:
# Ensure that a serial terminal is connected to the CM-X300 as described in [[CM-X300: WinCE: Setting Up a Console|Setting up a console]]
# Ensure that an Ethernet cable is connected to the CM-X300 platform
# In Platform Builder, go to {{MenuEntry| Target->Connectivity Options}}. [[Image:Target Device Connectivity Options X300.jpg]] 
# Click on {{Filename|Add Device}} and provide a device name (such as CM-X300). [[Image:Target Device Connectivity Options Add Device X300.JPG]] 
# In {{Filename|Kernel Service Map}}, select {{Filename|Ethernet}} for Download and Transport options and {{Filename|KdStub}} for the Debugger.
# Press {{Filename|Download settings}} and at the same time, נoot the target device and press {{Filename|SPACE}} in the device console to get Eboot main menu.
# Type "D" to download the image from Platform Builder (results in a broadcast of BOOT ME messages).
# Platform Builder will show the target device unique name (e.g. CM_X30064242) in the {{Filename|Active Devices}} area. [[Image:Ethernet Download SettingsX300.JPG]] 
# Press Transport settings and select {{Filename|Use device name from bootloader}}. [[Image:Ethernet KITL SettingsX300.JPG]] 

Once the connection is configured, download and launch the newly created WinCE image:
# In Platform Builder Target toolbar, select the configured device and then select {{MenuEntry|Target->Attach Device}}.
# Ensure that Eboot is ready for download (i.e. Sends Boot Me messages).

== Image Debugging ==
=== Platform Debugging with RETAILMSG ===
Debug messages output to the serial port may be enabled for both Retail and Debug build types. 
To enable RETAILMSG output to COM-A serial port, set the "STUART Usage" option to "Debug Serial" in the BSP Configuration menu in [[CM-X300: WinCE: Configuring Eboot|Eboot]]

=== Platform Debugging over Ethernet ===
KITL allows platform debugging over Ethernet and enables use of [http://msdn.microsoft.com/en-us/library/ee479862.aspx VS2005 Remote Tools]. During debug session, KITL redirects all the serial output into VS2005 output window.

* Choose the following platform options to enable platform debugging:
** Enable kernel debugger.
** Enable KITL.
* Perform {{MenuEntry|Build->Advanced Build Commands ->Rebuild Current BSP and Subprojects}}.
* Start the debug session as described in [[#KITL_Connection|Setup Target for CM_X300 Image Evaluation]] section.

{{Note|Run-time image built with the Kernel debugger and KITL dedicates CM-X300 Ethernet port to debug communication. This port cannot be used for application Ethernet traffic. The application Ethernet traffic can be routed through virtual VMINI adapter that should be enabled in [[CM-X300: WinCE: Configuring Eboot|Eboot configuration]].}}

== See Also ==
[[WinCE: OSDesign Development | Windows CE OSDesign Development]]

[[CM-X300: WinCE: Hive Based Registry on SD card|Persisting the Registry to the SD Card]]

[[Category:Windows CE|OSDesign Configuration]]
[[Category:CM-X300|OSDesign Configuration]]

CM-X300: WinCE: Known Issues

2010-04-14T11:44:04Z

Shai:

The following list is the known issues for the latest CM-X300 software package:
{{IssueCategory|Graphics|
* After using the overlay, there are visible artifacts when redrawing menu items and icons
* After installing the CAB file with the Codecs it is no longer possible to play MPEG1 movies
* There is no audio filter for MPEG2. This means that MPEG2 playback is done without audio
* There is a memory leak problem when using Marvell's codecs. The memory leaks appear when you destroy and recreate the graphs
}}

{{IssueCategory|Peripherals|
* CM-X300 rev 1.3 in conjunction with SB-X300 rev 1.1 does not have SD card detect and card protect
}}

[[Category:Windows CE|Known Issues]]
[[Category:CM-X300|Known Issues]]

CM-X300: WinCE: Configuring Eboot

2010-04-14T11:43:08Z

Shai: /* System Frequency Menu */

== Introduction ==
CM-X300 firmware for Windows CE consists of two components: U-Boot and Eboot. U-Boot initializes hardware and transfers control to Eboot - Windows CE loader. Eboot waits for 3 seconds (default setting) and then loads the Windows CE image from the NAND Flash. To interrupt the boot sequence, press any key other than ENTER during the first 3 seconds.
<pre>
Press [ENTER] to launch image stored in flash or [SPACE] to cancel.

Initiating image launch in 3 seconds.
</pre>

When the boot sequence is interrupted, Eboot enters menu-driven configuration mode.

== Menu Overview ==

=== Main Menu ===
<pre>
--------------------------------------------------------------------------------
Eboot Main Menu
--------------------------------------------------------------------------------
[0] IP address: 0.0.0.0
[1] Subnet Mask: 0.0.0.0
[2] Boot delay: 3 seconds
[3] DHCP: (Enabled)
[5] Auto Download image at startup(Disable)
[D] Download image now
[L] Launch existing flash resident image now
[S] Set BSP Configuration
[R] Reboot
</pre>
{{Note|Selection is not case sensitive}}

* IP address
:- Configures the IP address of the device in case DHCP is not used
* Subnet Mask
:- Configures the Subnet Mask of the device in case DHCP is not used
* Boot delay
:- Specifies the delay in seconds before Auto Download/Launch of an image
* DHCP
:- Use DHCP to acquire an IP address during Windows CE boot
* Auto Download image at startup
:- Configures whether to launch an image from NAND or download an image using KITL:
:* {{cmd|Disable}} - launch an image from NAND
:* {{cmd|Enable}} - download an image using KITL
* Download image now
:- Download an image using KITL without making this the default option
* Launch existing flash resident image now
:- Load the image stored in the NAND flash without making this the default option
* Set BSP Configuration
:- Advanced configuration of the image. Discussed in the next section.

=== Set BSP Configuration ===
<pre>
----------------------------------------------------------
Set BSP Configuration
----------------------------------------------------------
[B] Bit Blit: (Software optimized)
[T] KITL(Image Download) Transport: (DM9000a)
[K] Enable KITL: (Enabled)
[L] Enable KITL Polling Mode: (Disabled)
[I] Enable IMM driver: (Enabled)
[V] Enable VBridge: (Disabled)
[F] System frequency: IPM enable
[D] Enable/Disable image drivers
[U] USB Functionality: USB Host
[A] STUART usage: (Debug Serial)
[W] BT/WLAN Combo Card usage: (Both Disable)
[C] Clean System Hive Registry: (Disabled)
[E] Clean Users Hive Registry: (Disabled)
[R] Reset to factory default configuration
[S] Save configuration to FLASH
[Q] Quit to Main menu
</pre>
* Bit Blit
:- Open the Bit Blit menu. Only {{Filename|Software Optimized}} setting is supported
* KITL
:- The KITL transport setting. Only DM9000a Ethernet controller is supported
* Enable KITL
:- Enable or disable KITL in images that include it
* Enable KITL Polling Mode
* Enable IMM driver
:- Enable Marvell driver for SRAM handling. Do not change this option.
* Enable VBridge
:- Enable the VMINI virtual network adapter in images that include KITL
* System Frequency
:- Open the [[#System_Frequency_Menu|System frequency sub-menu]]
* Enable/Disable image drivers
:- Open the [[#Drivers_Menu|Drivers sub-menu]]
* STUART Usage
:- Enable/disable debug output via STUART
* BT/WLAN Combo Card usage
:- Open the [[#BT/WLAN_Menu|BT/WLAN submenu]]
* Clean System Hive Registry
:- Reset the System registry to the state stored in the {{filename|NK.bin}} file
* Clean Users Hive Registry
:- Reset the User registry to the state stored in the {{filename|NK.bin}} file
* Reset to factory default configuration
:- Reset Eboot configuration to the state stored in the {{filename|eboot.nb0}} image
* Save configuration to FLASH

=== System Frequency Menu ===
<pre>
--------------------------------------------------------------------------------
System frequency: IPM enable (dynamic frequency)
--------------------------------------------------------------------------------
[1] Disable dynamic frequency changing
[2] IPM enable (dynamic frequency)
[Q] Quit
</pre>
* Disable dynamic frequency changing
:- Disable the IPM driver. The frequency will be the one chosen in Uboot.
* IPM enable (dynamic frequency)
:- The Dynamic Frequency change driver (IPM) is enabled and controls the frequency.

=== Drivers Menu ===
<pre>
-----------------------------------
Enable/Disable image drivers
-----------------------------------
[1] SPI Driver: (Disabled)
[2] Backlight Driver: (Enabled)
[3] Battery Driver: (Disabled)
[4] Codec Driver: (Enabled)
[5] BTUART Driver: (Disabled)
[6] FFUART Driver: (Disabled)
</pre>
Each option Disables/Enables the specified driver.
 The Codec driver is responsible for Audio and Touch functionality.

=== BT/WLAN Menu ===
<pre>
--------------------------------------------
BT/WLAN Combo Card usage: (Both Disable)
--------------------------------------------
[1] Both Disable
[2] Only Enable Bluetooth
[3] Only Enable WiFi
[4] Both Enable
[Q] Quit
</pre>

[[Category:Windows CE|Configuring Eboot]]
[[Category:CM-X300|Configuring Eboot]]

CM-X300: WinCE: Hive Based Registry on SD card

2010-04-08T11:03:32Z

Shai: /* Introduction */

== Introduction ==
Windows Embedded CE supports two types of registries: RAM-based and hive-based.

The registry type is invisible to applications, but affects the persistence, boot sequence, boot time and memory consumption on a target device.

For more information about registry types please refer to [http://msdn.microsoft.com/en-us/library/aa910532.aspx Registry Types] and [http://msdn.microsoft.com/en-us/library/aa911935.aspx Hive-Based Registry] MSDN articles.

This page lists the required steps to set the hive based registry on the SD card.

For a review of changing the registry type to RAM-Based, please refer to [[CM-X300: WinCE: OSDesign_Configuration#RAM-Based_Registry_support|Registry support]].

== Persisting the Registry on SD card ==

The CM-X300 BSP is configured for HIVE-based registry with lazy flushing. The registry hive is located in the system NAND flash.
In order to move registry hive location to SD Card, make the following changes to {{Filename|Platform.reg}}:

* Apply the following values:

<pre>
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\MSFlash]
"Flags"=dword:00010000

[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\MSFlash]
"BootPhase"=dword:1

[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\MSFlash\FATFS]
"MountAsBootable"=dword:0
"MountAsRoot"=dword:0

; HIVE BOOT SECTION

; +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
; PMIC Driver (Power Management IC)
; +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\PI2C]
"Prefix"="PWR"
"Dll"="$(_TGTPLAT_PFX)_PI2C.dll"
"Order"=dword:6 ; Must loading after MFP driver loading
"Flags"=dword:1000

IF BSP_NOPMIC !
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\PowerIC]
"InterfaceType"=dword:0 ; Internal
"Prefix"="PIC"
"Dll"="$(_TGTPLAT_PFX)_PMIC.dll"
"Flags"=dword:11000; DEVFLAGS_TRUSTEDCALLERONLY
"Order"=dword:7
"IClass"="{1B4091E0-9F41-4d4f-8702-8C02368F20B1}"
ENDIF BSP_NOPMIC !

; +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
; IPM - Marvell Power Manager
; +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
IF BSP_NOIPM !
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\IPM]
"Dll"="$(_TGTPLAT_PFX)_ipm_main.dll"
"Prefix"="IPM"
"IClass"="{A32942B7-920C-486b-B0E6-92A702A99B35}"
"Order"=dword:10
"Flags"=dword:11000; DEVFLAGS_TRUSTEDCALLERONLY
"Priority256"=dword:00000010
"EnableD0CSOP"=dword:00000001
"EnableD0CSIDLE"=dword:00000001
"EnableD1IDLE"=dword:00000000
"EnableD2IDLE"=dword:00000001
ENDIF BSP_NOIPM !
; END HIVE BOOT SECTION
</pre>
{{Note|The above keys are already defined in the {{Filename|Platform.reg}} and only their values should be modified}}

* Add the following entries to {{Filename|Platform.reg}}:

<pre>
; @CESYSGEN IF FILESYS_FSREGHIVE
; HIVE BOOT SECTION

[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\SDMemory]
"Name"="SD Memory Card"
"Folder"=""
"MountAsBootable"=dword:1
"MountAsRoot"=dword:1
"MountBootable"=dword:1
"LoadFlags"=dword:1
"BootPhase"=dword:0
"DefaultFileSystem"="BINFS"
"PartitionDriver"="mspart.dll"
"Order"=dword:4
"AutoMount"=dword:1
"AutoPart"=dword:1
"AutoFormat"=dword:1
"MountHidden"=dword:0
"MountAsNetwork"=dword:1
"MountPermanent"=dword:1
"EnableWriteBack"=dword:1
"MountSystem"=dword:1

[HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\ObjectStore]
"MountAsBootable"=dword:0
"MountAsRoot"=dword:0

[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\HDProfile]
"MountAsBootable"=dword:0

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\GIO]
"Prefix"="GIO"
"Dll"="cm_x300_gpio.dll"
"Order"=dword:6 ; Must load after MFP driver loads
"Flags"=dword:00001000

; @CESYSGEN IF CE_MODULES_SDBUS

[HKEY_LOCAL_MACHINE\Drivers\Builtin\SDBusDriver]
"Order"=dword:15
"Dll"="SDBus.dll"
"Prefix"="SDC"
"ThreadPriority"=dword:64 ; default thread priority for dispatch thread
"RequestListDepth"=dword:30 ; pre-allocated requests
"Flags"=dword:10000 ; DEVFLAGS_TRUSTEDCALLERONLY
"IClass"=multi_sz:"{20FA98A8-B298-4b32-8D72-C716AEE2FA84}=%b","{6F40791D-300E-44E4-BC38-E0E63CA8375C}=%b"
"Flags"=dword:00011000

[HKEY_LOCAL_MACHINE\Drivers\SDCARD\ClientDrivers\Class\SDMemory_Class]
"Dll"="SDMemory.dll"
"Prefix"="DSK"
"BlockTransferSize"=dword:40 ; send no more than 64 blocks of data per bus transfer
"Order"=dword:16
"Profile"="SDMemory"
"IClass"=multi_sz:"{A4E7EDDA-E575-4252-9D6B-4195D48BB865}",
"{8DD679CE-8AB4-43c8-A14A-EA4963FAA715}"
"Flags"=dword:00001000

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\SDHC]
"Order"=dword:50
"Flags"=dword:00001000
"Dll"="cm_x300_sdhc.dll"
"Prefix"="SDH"
"SDHCIndex"=dword: 0
"ControllerISTPriority"=dword:64
"SlotNum"=dword:1 ;Number of slots connected to the controller
"ClockAlwaysOn"=dword:0
; Indicate a power manageable interface
"IClass"="{A32942B7-920C-486b-B0E6-92A702A99B35}"
"HotPluginNRemovable"=dword:1 ;Hex that specifies which slot can be HotPlugged
"FastPathEnabled"=dword: 0

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\SDHC_2]
"Order"=dword:50
"Flags"=dword:00001000
"Dll"="cm_x300_sdhc.dll"
"Prefix"="SDH"
"SDHCIndex"=dword: 1
"ControllerISTPriority"=dword:64
"SlotNum"=dword:1
"ClockAlwaysOn"=dword:1
; Indicate a power manageable interface
"IClass"="{A32942B7-920C-486b-B0E6-92A702A99B35}"
"HotPluginNRemovable"=dword:0
"FastPathEnabled"=dword: 0

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\PCI\Template\SDIOStandardHC]
"Dll"="SDHC.dll"
"Prefix"="SHC"
"IsrDll"="giisr.dll"
"IsrHandler"="ISRHandler"
"Class"=dword:08 ; General peripheral
"SubClass"=dword:05 ; SD Host Controller
"ProgIf"=dword:00 ; 00 Std host no DMA, 01 Std host DMA, 02 vendor unique
"DefaultWakeupSources"=dword:06 ; Wake on insertion and removal
"AllowWakeOnSDIOInterrupts"=dword:01
"ObjectCreationProc"="CreateSDHCPciObject"
"Flags"=dword:00001000
"Order"=dword:17

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\PCI\Template\SDIOStandardHCWithDMA]
"Dll"="SDHC.dll"
"Prefix"="SHC"
"IsrDll"="giisr.dll"
"IsrHandler"="ISRHandler"
"Class"=dword:08 ; General peripheral
"SubClass"=dword:05 ; SD Host Controller
"ProgIf"=dword:01 ; 00 Std host no DMA, 01 Std host DMA, 02 vendor unique
"DefaultWakeupSources"=dword:06 ; Wake on insertion and removal
"AllowWakeOnSDIOInterrupts"=dword:01
"ObjectCreationProc"="CreateSDHCPciObject"
"Flags"=dword:00001000
"Order"=dword:18

; @CESYSGEN ENDIF CE_MODULES_SDBUS
; END HIVE BOOT SECTION
; @CESYSGEN ENDIF FILESYS_FSREGHIVE
</pre>
{{Note| The HIVE BOOT SECTION and cesysgen conditionals are not just a comments, do not forget to copy them also.}}

* Rebuild the BSP.

[[Category:Windows CE|Hive Based Registry on SD]]
[[Category:CM-X300|Hive Based Registry on SD]]

CM-X300: WinCE: OSDesign Configuration

2010-04-08T11:00:54Z

Shai: /* Platform Debugging over Ethernet */

== Installing the Driver Package ==
* Close the Platform Builder Application if it is open.
* Copy the CM_X300_BSP directory to \WINCE600\Platform\
* Copy the CM_X300_CE6 directory to \WINCE600\OSDesigns\
* Launch VS2005 and open \WINCE600\OSDesigns\CM_X300_CE6\CM_X300_CE6.sln

== Building the Platform Project ==
The CM_X300 Platform Project is used to build CompuLab Windows Embedded CE demo image. It includes many components and is highly recommended as a starting point for a new project. The demo image is relatively large, ~35 MB. Typical Windows CE images for a specific application are much smaller, 8-15 MB.

To build the CM_X300 platform:
* select the {{MenuEntry|Open->Project/Solution}} command from the File menu of the VS2005 and select the {{Filename|\WINCE600\OSDesigns\CM_X300_CE6\CM_X300_CE6.sln}} file.
* Check that the project is configured for Release.
* Perform {{Cmd|Rebuild Solution}} from the {{Cmd|Build}} menu (alternatively, perform {{MenuEntry|Build->Advanced Build Commands->Clean Sysgen}}).

The build process takes about 15-20 minutes.

=== CPU Type ===
The CM-X300 may be assembled with two CPU types:
* PXA300 - the C624 option
* PXA310 - the C624M option

The default BSP configuration targets the PXA310 CPU.

==== Choosing CPU Type ====
The CPU type is defined in {{Filename|CM_X300_BSP.BAT}} file in the platform directory. Ensure that the {{parameter|BSP_CPU_TYPE}} setting corresponds with the correct CPU type. Leave the appropriate line without the REM directive:
<pre>
set BSP_CPU_TYPE=310
REM set BSP_CPU_TYPE=300
</pre>

=== Build Options ===
* Use {{MenuEntry|Build->Advanced Build Commands->Sysgen}} when adding Platform Builder components (Catalog items) to the project.
* Use {{MenuEntry|Build->Advanced Build Commands->Clean Sysgen}} when removing Platform Builder components (Catalog items) from the project.
* Use {{MenuEntry|Build->Advanced Build Commands->Build Current BSP and Subprojects}} when modifying Compulab BSP components that are included in the project or performing changes in the BSP files.
* Use {{MenuEntry|Build->Advanced Build Commands-> Rebuild Build Current BSP and Subprojects}} when adding/removing Compulab BSP components to/from the project.
{{Warning|Do not use {{MenuEntry|Build->Advanced Build Commands->Build and Sysgen}} or {{MenuEntry|Build->Advanced Build Commands->Rebuild and Clean Sysgen}} that perform compilation and sysgen on the entire Platform Builder tree.
It is recommended to remove the two commands mentioned above from the menu permanently}}

== Windows CE Image Customization ==
There are two ways to customize the Windows CE image:
# Recommended method: Add or remove BSP components from the demo CM_X300_CE6 project.
# Create a new platform project and then manually add all the necessary BSP components as described in the Platform Builder documentation. Refer to [[WinCE: OSDesign Development|Windows CE OSDesign Development]] page.

=== BSP customization using batch files ===
The BSP is fully customizable and allows inclusion/exclusion of each component via BSP_NO environment variables.

To exclude a certain driver, set the BSP_NO environment variables in {{Filename|CM_X300_BSP\CM_X300_BSP_COMMON.bat}} and rebuild the BSP with {{MenuEntry|Build->Advanced Build Commands->Rebuild Current BSP and Subprojects}}.

The following table lists the BSP_NO environment variables that can be defined:

{| border="1"
|-
| '''Variable'''
| '''Meaning'''
| '''Comments'''
|-
| BSP_NOKEYPAD
| No Keypad driver and no support for keyboard
|
|-
| BSP_NODISPLAY
| No Graphics
|
|-
| BSP_NONAND
| No NAND Flash driver
|
|-
| BSP_NOSDHC
| No SDIO card driver
|
|-
| BSP_NOWLAN
| No WiFi driver
|
|-
| BSP_NOI2C
| No I2C driver
|
|-
| BSP_NOUSB20FN
| No Usb 2.0 Function driver
|
|-
| BSP_NOUSBFN
| No Usb 1.1 Function driver
|
|-
| BSP_NOUSBHOST
| No Usb Host driver
|
|-
| BSP_NOAUDIO
| No Audio driver
|
|-
| BSP_NOTOUCH
| No Touch screen driver
|
|-
| BSP_NOCODEC
| No Codec driver
| (no Touch and no Audio)
|-
| BSP_NOBLUETOOTH
| No BlueTooth Driver
| No Bluetooth stack as well
|}

{{Note|Any environment variable defined in CM_X300_BSP\CM_X300_BSP_COMMON.bat will override the variables defined in Platform Builder project}}

=== RAM-Based Registry support ===
The CM-X300 BSP is configured for HIVE-based registry with lazy flushing. The registry hive is located in the system NAND flash.
To support a RAM-Based registry, perform the following actions:
* Add the {{Filename|RAM-based Registry}} component to the project
* Disable the following variables in the {{filename|CM_X300_BSP\CM_X300_PRODUCTION.bat}}:
<pre>
set PRJ_ENABLE_FSREGHIVE=1
set PRJ_ENABLE_REGFLUSH_THREAD=1
</pre>
* Perform "Clean Sysgen" using {{MenuEntry|Build->Advanced Build Commands->Clean Sysgen}}

=== Persistent File System ===
The CM-X300 BSP is configured to store the root directory in RAM, therefore the root filesystem is not persistent. To make the root and its subsequent folders persistent, change the Catalog item "ROM and RAM File System" to "ROM-Only file System".

{{Note|Any data saved to a non-persistent location is erased when the device resets. This includes the root directory ("\").}}

== CM-X300 BSP Subprojects ==
In addition to the drivers supplied with the BSP, there are a few useful utilities distributed as Subprojects. Subprojects allow adding software modules to the build without modifying the BSP source code located in the Platform source tree.
There are two Subproject types available with CM_X300_BSP:
* Subprojects that add optional functionality to the BSP are located in the {{Filename|\WINCE600\PLATFORM\CM_X300_BSP\Subprojects}} directory.
: These Subprojects are provided with the source code.
{| border="1"
|-
| '''Project Name'''
| '''Functionality'''
|-
| ''SetPowerState''
| Command line utility that controls the system power state and is used for software reboot and suspend support
|-
| ''Regedit''
| Command line registry editor. Allows remote changes of the device registry via telnet connection.
|-
| ''CoreCon''
| Executables required for application level debugging over Ethernet in VS2005
|-
| ''AutoLaunch''
| Executable that should be used for automatic launch of CoreCon (ConmanClient2.exe) at system startup. AutoLaunch.exe verifies IP address availability before loading ConmanClient2.exe. This is required because ConmanClient2 waits for incoming TCP/IP connections when communicating with VS 2005
|-
| ''SysConf''
| Command line utility for platform debugging
|-
| ''Tools''
|
* Command line RTC_CMD utility for RTC driven suspend/resume cycles
* CLTerm program for COM ports testing
|-
| ''BuildVer''
| This project adds a text file to the image specifying which revision was used to build the image. It requires a Tortoise Svn client installed on the desktop.
|}

* The Subprojects that add custom applications, control panel applets and registry settings to the demo image are located at {{Filename|\WINCE600\OSDesigns\CM_X300_CE6\Subprojects}} directory.
{| border="1"
|-
| '''Project Name'''
| '''Functionality'''
|-
| ''CPLApplets\WireLessCPL''
| Control panel applet that controls the power state (on/off) of wireless devices
|-
| ''CPLApplets\KeypadConfigCPL''
| Control panel applet that customizes keypad buttons functionality
|-
| ''CPLApplets\BacklightCPL''
| Control panel applet that controls the LCD backlight level
|-
| ''TCPMP''
| Open source Media player
|-
| ''TaskManager''
| Open source Task Manager
|-
| ''KeypadAppLaunch''
| A utility to capture application launching key presses
|-
| ''LookAndFeel''
| Look and feel of the demo image (background, theme, sounds, etc.)
|}

== KITL Connection ==
Platform Builder communicates with a device using KITL protocol. For details about KITL refer to [http://www.microsoft.com/video/en/us/details/0a8d9767-a419-4f5e-9b37-4328b0993d1d Microsoft's KITL Broadcast] article.

The following actions should be performed in order to setup a KITL connection between the CM-X300 and Platform Builder 6.0:
# Ensure that a serial terminal is connected to the CM-X300 as described in [[CM-X300: WinCE: Setting Up a Console|Setting up a console]]
# Ensure that an Ethernet cable is connected to the CM-X300 platform
# In Platform Builder, go to {{MenuEntry| Target->Connectivity Options}}. [[Image:Target Device Connectivity Options X300.jpg]] 
# Click on {{Filename|Add Device}} and provide a device name (such as CM-X300). [[Image:Target Device Connectivity Options Add Device X300.JPG]] 
# In {{Filename|Kernel Service Map}}, select {{Filename|Ethernet}} for Download and Transport options and {{Filename|KdStub}} for the Debugger.
# Press {{Filename|Download settings}} and at the same time, נoot the target device and press {{Filename|SPACE}} in the device console to get Eboot main menu.
# Type "D" to download the image from Platform Builder (results in a broadcast of BOOT ME messages).
# Platform Builder will show the target device unique name (e.g. CM_X30064242) in the {{Filename|Active Devices}} area. [[Image:Ethernet Download SettingsX300.JPG]] 
# Press Transport settings and select {{Filename|Use device name from bootloader}}. [[Image:Ethernet KITL SettingsX300.JPG]] 

Once the connection is configured, download and launch the newly created WinCE image:
# In Platform Builder Target toolbar, select the configured device and then select {{MenuEntry|Target->Attach Device}}.
# Ensure that Eboot is ready for download (i.e. Sends Boot Me messages).

== Image Debugging ==
=== Platform Debugging with RETAILMSG ===
Debug messages output to the serial port may be enabled for both Retail and Debug build types. 
To enable RETAILMSG output to COM-A serial port, set the "STUART Usage" option to "Debug Serial" in the BSP Configuration menu in [[CM-X300: WinCE: Configuring Eboot|Eboot]]

=== Platform Debugging over Ethernet ===
KITL allows platform debugging over Ethernet and enables use of [http://msdn.microsoft.com/en-us/library/ee479862.aspx VS2005 Remote Tools]. During debug session, KITL redirects all the serial output into VS2005 output window.

* Choose the following platform options to enable platform debugging:
** Enable kernel debugger.
** Enable KITL.
* Perform {{MenuEntry|Build->Advanced Build Commands ->Rebuild Current BSP and Subprojects}}.
* Start the debug session as described in [[#KITL_Connection|Setup Target for CM_X300 Image Evaluation]] section.

{{Note|Run-time image built with the Kernel debugger and KITL dedicates CM-X300 Ethernet port to debug communication. This port cannot be used for application Ethernet traffic. The application Ethernet traffic can be routed through virtual VMINI adapter that should be enabled in [[CM-X300: WinCE: Configuring Eboot|Eboot configuration]].}}

== See Also ==
[[WinCE: OSDesign Development | Windows CE OSDesign Development]]

[[CM-X300: WinCE: Hive Based Registry on SD card|Persisting the Registry to the SD Card]]

[[Category:Windows CE|OSDesign Configuration]]
[[Category:CM-X300|OSDesign Configuration]]

CM-X300: WinCE: Demo Image

2010-04-08T10:56:50Z

Shai: /* See Also */

The Windows Embedded CE Demo for CM-X300 is based on the standard {{WindowsCEVer}}.
== CM-X300 Features Supported ==
The CM-X300 Demo image supports the following features:
* NAND Flash Disk
* TFT LCD (pre configured for Toppoly TD035STEE1 TFT 480x640)
* Audio (input/output)
* Wi-Fi 801.11b/g
* Bluetooth
* Suspend / Resume
* USB 1.1 Host / Salve
* USB 2.0 Slave
* Ethernet
* Serial ports
* SD/MMC CARD
* GPIO access
* I2C/SPI bus
* Touch screen
* Keypad
* RTC (H/W rev. 1.2 and up)
* Backlight
* Battery management
* VIP / Quick capture interface (currently with limited functionality)

== Demo Image Contents ==
The following standard Windows Embedded CE components are included in this demo image:
* File system Explorer
* ActiveSync
* AYGShell
* Internet Explorer XAML UI Sample Browser
* Gestures Support
* Flash Lite ActiveX control
* Windows Media Player
* Telnet Server
* TCPMP Player
* ItaskMgr (a PC-like task manager)
* All MS Bluetooth Profiles

{{Note|For a complete list of the components included in the image refer to the [[media:CM-X300-ComponentList-WinCE.zip|Components list]].}}

== Get Connected with ActiveSync ==
ActiveSync enables data synchronization between a desktop computer and the CM-X300. You must install ActiveSync on your PC before connecting it to the CM-X300.

=== On the Host PC ===
==== Hosts running Windows XP ====
* Download and Install [http://www.microsoft.com/windowsmobile/en-us/downloads/microsoft/activesync-download.mspx ActiveSync] from Microsoft website.
* ActiveSync may experience connection problems caused by Windows desktop firewall applications. Read the [http://www.microsoft.com/windowsmobile/en-us/help/synchronize/activesync-usb.mspx ActiveSync Troubleshooting Guide] for host PC configuration instructions.
* Ensure that ActiveSync synchronization via USB is enabled in the Connection Settings dialog box
:[[Image:ActiveSync connection settings window.jpg]]
===== Installing ActiveSync driver for the CM-X300 =====
:* On the first connection the "New hardware found" wizard appears. Please follow the selections depicted below:
: [[image:Active Sync driver step1.jpg]]
: [[image:Active Sync Driver step2.jpg]]
: [[image:Active Sync Driver step3.jpg]]
: [[image:Active Sync Driver step4.jpg]]
: [[image:Active Sync Driver step5.jpg]]
:* If the following confirmation dialog pops up, choose "No":
: [[image:Active Sync Driver step6.jpg]]
: [[image:Active Sync Driver step7.jpg]]
:* Now ActiveSync setup is complete.

==== Hosts running Windows Vista/7 ====
* Download and install the latest version of [http://www.microsoft.com/windowsmobile/en-us/downloads/microsoft/device-center-download.mspx Windows Mobile Device Center (WMDC) for Windows 7] from Microsoft website
* Ensure that the CM-X300 registry has {{parameter|[HKEY_LOCAL_MACHINE\Drivers\USB\FunctionDrivers\Serial_Class]}} key with the following value:
<pre>
[HKEY_LOCAL_MACHINE\Drivers\USB\FunctionDrivers\Serial_Class]
"idVendor"=dword:045E
"idProduct"=dword:00ce
</pre>
:- A dedicated Vendor ID should be purchased and used for mass production.
:- CM-X300 registry may be altered as described in the [[#RegEdit|RegEdit]] section.

=== On the Target (CM-X300) ===
==== PXA300 processor (C624 option) ====
* Connect a USB cable to the USB 2.0 port (connector P8 on SB-X300) or to the USB 1.1 slave port (connector P10 on SB-X300).
* USB 2.0 is the default configuration.

==== PXA310 processor (C624M option) ====
* Configure the USB port to function as Slave as described in [[#USB|USB section]].
* Connect a USB cable to the connector P10 on SB-X300.

== Demo Image Componentes ==
The demo image is packed into the raw NK.bin file that is stored in the CM-X300 NAND flash during installation.

=== RAM ===
The CM-X300 supplied with the evaluation kit is equipped with 128MB of RAM. The demo image requires approximately 40MB and leaves 88MB for application use.

=== NAND Flash ===
The CM-X300 supplied with the evaluation kit is equipped with 512MB NAND flash.
U-Boot and Eboot bootloaders are stored in the NAND flash.

During demo image installation, the NAND flash is automatically partitioned and space is reserved for the runtime image, which is stored in the NAND flash unpartitioned space.

Space for a second runtime image is reserved to facilitate a fail-safe update mechanism.

Approximately 400 MB of free space is available for data storage on the NAND. Data may be stored in the NAND directory ("\nandflash").

=== Persistent Registry ===
The demo image is built with a "Hive-Based Registry" option. This means that the system registry is stored in the NAND flash data partition, making registry entries persistent when the device is powered off.The demo image is configured with a "Lazy Flush" registry policy. The registry settings are stored in RAM and are flushed into the NAND Flash every 30 seconds. After changing registry settings, allow 30 seconds before turning off the power or performing a hardware reset. This will ensure that the changes are saved into the NAND flash.

The flush period may be changed through the following registry value:
<pre>
[HKEY_LOCAL_MACHINE\System\ObjectStore\RegFlush]
"FlushPeriod"=dword:7530
</pre>

=== Networking ===
The following network interfaces are supported in the demo image:
* CM-X300 Ethernet - Full-featured 10/100 Ethernet interface. Implemented with the Davicom DA9000A Ethernet controller on the CM-X300 module.
* Wireless LAN - incorporates full-featured 802.11 b/g capabilities. Implemented with the Wi2Wi W2SW0001 WLAN controller on the CM-X300 module.

The demo image image is configured to use a DHCP server to obtain network settings for the two network adapters. Network settings may be changed in the Windows CE Control Panel.
==== Defining static IP address ====
It is possible to configure a static IP address by modifying the registry.

For example, the following registry settings disable DHCP and define the static IP 10.1.1.144 for the CM-X300 Ethernet controller:
<pre>
[HKEY_LOCAL_MACHINE\Comm\DM9CE1\Parms\TcpIp]
"EnableDHCP"=dword:0
"IpAddress"="10.1.1.44"
"Subnetmask"="255.255.255.0"
"DefaultGateway"="10.1.1.1"
"UseZeroBroadcast"=dword:0
</pre>

A static IP may be assigned to the Ethernet interface using Eboot configuration menu. For further details please refer to [[CM-X300:_WinCE:_Configuring_Eboot|Configuring Eboot]] article.

=== USB ===
==== PXA300 ====
* Connector P10 on SB-X300 provides a USB host port that operates at full/low speed.
:- The port may be configured in Eboot to operate as a device port at full/low speed. See [[CM-X300:_WinCE:_Configuring_Eboot|Configuring Eboot]].
* Connector P8 on SB-X300 provides a USB device port (used mainly for ActiveSync).

==== PXA310 ====
* Connector P10 on SB-X300 provides a USB host port that operates at full/low speed.
: The port may also function as high speed device. The USB port configuration may be changed in the Windows CE Control Panel. Use {{MenuEntry|Start->Settings->Control Panel->USB Functionality Chooser}} to switch between USB host and USB device functionality. The CM-X300 system should be restarted to activate the new settings.

=== SD card ===
* The SB-X300 evaluation board features an SD socket (connector P14).
* When an SD card is inserted it is mounted automatically as “Storage Card” under “My Device”.
* The demo image has been tested successfully with the following types of SD cards: SanDisk Ultra III 2Gb, Kingston 2Gb, SanDisk 1Gb, and Kingston Micro SDHC 4Gb.

=== Touch Screen ===
The demo image is calibrated for the Toppoly TD035STEE1 LCD touch screen.
To fine-tune the calibration, run the touch screen calibrator on the first boot by tapping
{{MenuEntry|Start->Settings->Control Panel->Stylus->Calibration}}.
For further details about touch screen calibrator registry settings refer to the [http://msdn.microsoft.com/en-us/library/ms926952.aspx Touch Screen (Stylus) Registry Settings] MSDN article.

The Touch Screen sensitivity is controlled by the {{RegKey|HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\TOUCH}} registry key:
<pre>
[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\TOUCH]
"Sensitivity"=dword:30
</pre>
The "Sensitivity" value is a hexadecimal number between {{cmd|1}} and {{cmd|3F}}. The lower values correspond to higher panel sensitivity.

Reboot the device after a change.

=== Keypad ===
The demo image is configured to support the 3x3 keypad provided with the CM-X300 evaluation kit.

The default key mappings are listed below:
* "Left", "Right", "Up", "Down" buttons control cursor movement (SW3, SW7, SW4, SW6 respectively)
* "SW5" button acts as "Enter" key
* "SW1" (Func1) button launches Internet Explorer
* "SW2" (Func2) button launches Media Player
* "SW8" (Func3) button launches ItaskMgr
* "SW9" (Func4) button launches Windows Explorer

The application assignment to particular keys is defined in the following registry settings:
<pre>
[HKEY_LOCAL_MACHINE\SOFTWARE\Compulab\KeyPad]
"APP1"= "\\Windows\\iesample.exe"
"APP2"= "\\Windows\\ceplayer.exe"
"APP3"= "\\Windows\\itaskmgr.exe"
"APP4"= "\\Windows\\explorer.exe"
</pre>

=== Display Subsystem ===
The demo image is configured for a Toppoly TD035STEE1 TFT LCD.
The default resolution is 480x640 with 16-bit color depth and portrait display.

==== Using custom display settings ====
The LCDAdapt utility included in the [http://www.compulab.co.il/x300/download/x300-wince6-img.zip Windows CE 6 run-time image package] allows easy configuration of LCD timing parameters.
The LCDAdapt utility runs on the host PC and connects to the CM-X300 device using the ActiveSync.

* The necessary values are extracted from the specification of the display.
* Hovering with the mouse pointer over each field will display a tool tip with an explanation.
* Press the "Connect" button to connect to the device.
* The LCDAdapt will read the current settings on the device and display them.
* Use LCD parameters extracted from the display specification to fill in the settings
* Press the "Send Settings" button. The LCDAdapt utility will configure the LCD controller on the CM-X300 and restart it.
: [[image:LCDAdapt-ScreenShot-X300.jpg]]

The program changes the following registry settings on the device:
<pre>
[HKEY_LOCAL_MACHINE\Drivers\Display\GPE]
"HorizontalSize"=dword:1E0
"VerticalSize"=dword:280
"Bpp"=dword:10 ; Bytes per pixel
"BLW"=dword:7 ; Timing
"ELW"=dword:17 ; Timing
"HSW"=dword:8 ; Timing
"BFW"=dword:2 ; Timing
"EFW"=dword:4 ; Timing
"VSW"=dword:2 ; Timing
"104M"=dword:4 ; PCD
"156M"=dword:6 ; PCD
"208M"=dword:9 ; PCD
"39M"=dword:0 ; PCD
"D0CS"=dword:2 ; PCD
"OEP"=dword:0 ; Polarity
"PCP"=dword:1 ; Polarity
"HSP"=dword:1 ; Polarity
"VSP"=dword:1 ; Polarity
</pre>
{{Note|The LCDAdapt utility requires .Net 3.x framework installed on the host PC}}
For additional details about CompuLab LCD adaptation services, please refer to [http://www.compulab.co.il/x300/html/x300-lcd.htm LCD Panel support].

==== Video Playback ====
The package supports playback of the following video formats:
* MPEG4
* H.264
* MPEG2
* 3GP

Media playback requires installation of codec pack available in the {{filename|Utilities\GraphicAcceleration\Graphics\Cab\HWCodecsCMX300}} CAB archive.

The project that generates the CAB file is located in the same directory.

The rest of the graphics examples are located in {{filename|Utilities\GraphicAcceleration\Graphics}} and there is no documentation available for them.

=== Backlight ===
The CM-X300 supports seven levels of backlight brightness.

The backlight level can be modified in the Windows CE Control Panel. Use {{MenuEntry|Start->Settings->Control Panel-> Backlight Level}} to adjust the brightness.
The backlight level altered directly via the {{RegKey|HKEY_CURRENT_USER\ControlPanel\BackLight}} registry key:
<pre>
[HKEY_CURRENT_USER\ControlPanel\BackLight]
"BacklightLevel"=dword:0
</pre>

=== Battery and Charging ===
The CM-X300 evaluation kit is shipped with a 3000mAh Li battery. For detailed instructions about the battery connection please refer to the SB-X300 manual.

Monitor the battery power by tapping {{MenuEntry|Start->Settings->Control Panel->Power}}.

The CM-X300 / SB-X300 supports battery charging using the power cable supplied with the evaluation kit. For detailed instructions about the battery connection refer to the SB-X300 manual.The charging mechanism utilizes fast charging method with a charge current of 1000mA.

The battery driver must be enabled in the Eboot menu. Refer to [[CM-X300:_WinCE:_Configuring_Eboot|Configuring Eboot]] article.

=== Suspend / Resume ===
The CM-X300 Windows CE demo image enters suspend mode upon one of the following events:
* {{filename|Start->Suspend}} menu entry activation.
* Rising edge detection on GPIO83.
*{{cmd|Rtc_cmd.exe}} invocation. {{cmd|Rtc_cmd.exe}} is a console application with the following syntax:
<pre>
rtc_cmd [time before sleep in seconds] <sleep time in seconds>
</pre>
The system wakes up upon one of the following events:
* Rising edge detection on GPIO83.
* RTC timer (set by {{cmd|Rtc_cmd.exe}}) expiration.

=== Serial Ports ===
The demo image supports three serial ports. The serial ports mapping is summarized below:

{| cellpadding="3" border="1" style="border: 1px solid rgb(85, 85, 85); border-collapse: collapse;"
|-
! UART
! Connector
on SB-X300
! COM-port
! Notes
|-
| STUART
| P16
| COM4
| Used for diagnostic messages. Please refer to [[CM-X300:_WinCE:_Configuring_Eboot|Configuring Eboot]] for configuration
|-
| BTUART
| P6
| COM5
|
|-
| FFUART
| P4
| COM1
| Not available with PXA310 CPU ('''C624M''' option)
|}

The serial ports operate at baud rates up to 3.6M. For more details please refer to the [http://www.marvell.com/products/processors/applications/pxa_3xx/PXA3xx_Developers_Manual.zip PXA3xx developers manual].

=== Wireless Interface Control ===
Bluetooth and WiFi power state is controlled by the Control Panel, {{MenuEntry|Start->Settings->Control Panel->Wireless Config}}.

The initial state of the wireless devices may be configured in Eboot as described at [[CM-X300:_WinCE:_Configuring_Eboot|Configuring Eboot]].

=== Bluetooth ===
The demo image includes the following Microsoft Bluetooth profiles:
* Object Push Profile (OBEX)
* File Transfer Profile
* Human Interface Device Profile
* LAN Access Profile
* Personal Area Network Profile
* Hands-free and headset Profiles

The CM-X300 Bluetooth connectivity was verified with Motorola HT820 Bluetooth Stereo Headphones with A2DP profile.

Bluetooth Manager located at {{MenuEntry|Start->Settings->Control Panel->Bluetooth Device Properties}} allows to scan for remote Bluetooth devices and pair with them.
Bluetooth Audio connection {{cmd|AdpMgr}} sample is available at {{filename|Start->Programs->A2dpMgr}}.

=== Reboot ===
Use the "Software Reboot" shortcut on the desktop to reboot the system. The "Software Reboot" ensures proper system shutdown and registry flush.

=== Run Once Functionality ===
Run Once functionality allows addition of custom files and registry modifications after Windows CE image installation.

During the first boot the Windows CE image searches for {{filename|RunOnceCab.cab}} archive on SD card and USB flash drive. If the archive is found, it is loaded and executed. The Run Once functionality is disabled after the first boot is complete.

=== Running custom applications on startup ===
In order to run a custom application on the system startup, use the AutoLaunch utility integrated into the demo image.

The AutoLaunch utility extends the functionality of the {{RegKey |HKEY_LOCAL_MACHINE\Init}} registry key and allowing configurable launch delay for each application.
AutoLaunch monitors the following registry keys and values:
<pre>
[HKEY_LOCAL_MACHINE\Startup]
“Process0” =”Application.exe param1 param2”
“Process0Delay”=dword:delay ;in milliseconds

[HKEY_LOCAL_MACHINE\Startup\ApplicationName]
“Process0” =”Application.exe param1 param2”
“Process0Delay”=dword:delay ;in milliseconds
</pre>
Usage example:
<pre>
[HKEY_LOCAL_MACHINE\Startup\ceplayer]
"Process0” =”ceplayer.exe \windows\sound2.wav”
“Process0Delay”= dword:1388 ;5000 in decimal
</pre>
The above example launches CEPlayer five seconds after boot completion. The additional "\windows\Sound2.wav" parameter is used by CEPlayer to play the specified file.

== Sample Applications ==
The Windows CE demo image package includes demo applications that demonstrate how to use common interfaces such as SPI, I2C and GPIO.
They applications are located at the {{Filename|Demo Applications}} directory.
==== GPIO Sample ====
This application demonstrates how to use the GPIO driver in order to control the state of GPIO pins.

For further details, please refer to [[CM-X300: WinCE: GPIOs Programming | GPIOs Programming]].
==== I2C Sample ====
The I2C sample demonstrates how to use the I2C driver.

Fur further reading refer to [[CM-X300: WinCE: I2C Programming|I2C Programming]].

==== SPI Sample ====
The SPI_Thermometer sample included in the WinCE demo image package, demonstrates how to use the SPI driver.

For further details, please refer to [[CM-X300: WinCE: SPI Driver API|SPI Programming]].

==== C# ====
The COMPortTester sample demonstrates a simple C# application that interfaces with the COM ports.
==== SilverlightPlayerExample ====
The SilverlightPlayerExample sample demonstrates basic use of Silverlight.

== Miscellaneous Utilities ==
=== SetPowerState ===
A command line utility that performs global system power state transitions.
Syntax:
<pre>
SetPowerState.exe <State> [HexStateFlags [HexOptions]]
</pre>
: {{cmd|State}} - the system power state defined in the registry. Possible values are: {{parameter|Reboot}} and {{parameter|Suspend}}.
: {{cmd|StateFlags}} - specifies hexadecimal state flags, e.g. 200000 (POWER_STATE_SUSPEND).
: {{cmd|Options}} - specifies hexadecimal options, e.g. 1000 (POWER_FORCE).

The most useful transitions are:
: {{filename|SetPowerState reboot}} - performs watchdog reboot of the CM-X300.
: {{filename|SetPowerState suspend}} - puts the CM-X300 into the suspend mode.
{{Note|Before each power state transition, the registry is flushed to the NAND flash}}

=== SysConf ===
A command line utility that allows easier debugging of the platform. For further details please refer to [[WinCE: Sysconf|Sysconf]] article.

=== A2DP Demo Application ===
Th A2DP utility allows the user to pair with a BlueTooth device and activate the A2DP BlueTooth profile.
The program is available with full source code.

=== RegEdit ===
An embedded registry editor able to write/read/delete registry values.
Syntax:
<pre>
reg.exe <(-)Registry Key> (h) <Value>
</pre>
: "-" before a Registry Key deletes the value
: "h" modifier should be used for hexadecimal values

An OnDevice registry editor is available at: [http://geekswithblogs.net/BruceEitman/archive/2009/07/27/window-ce-simple-little-registry-editor.aspx Bruce Eitman's Blog].

=== SetWiFiPowerMode ===
The SetWiFiPowerMode utility activates WiFi power-saving mode. This significantly reduces the WiFi power consumption, however WiFi performance is degraded in this mode.

This program is located at {{filename|\Utilities\SetWiFiPowerMode}}
{{Note|This utility is not included in the NK.bin itself}}

=== LCDAdapt ===
This utility helps to integrate a custom LCD display. Please refer to [[#Using_custom_display_settings| Using custom display settings]].

== See Also ==
* [[CM-X300: WinCE: Getting Started|Getting started with Windows CE on CM-X300]]
* [[WinCE: Application Development|Application Development for CM-X300 modules]]
* [[WinCE: OSDesign Development|Windows CE OSDesign Development for CM-X300 modules]]
* [[CM-X300: WinCE: OSDesign Configuration|OSDesign Configuration]]
* [[CM-X300: WinCE: Configuring Eboot|Configuring Eboot]]

[[Category:Windows CE|Demo Image]]
[[Category:CM-X300|Demo Image]]

CM-X300: WinCE: Configuring Eboot

2010-03-25T11:39:48Z

Shai: /* Main Menu */

== Introduction ==
CM-X300 firmware for Windows CE consists of two components: U-Boot and Eboot. U-Boot initializes hardware and transfers control to Eboot - Windows CE loader. Eboot waits for 3 seconds (default setting) and then loads the Windows CE image from the NAND Flash. To interrupt the boot sequence, press any key other than ENTER during the first 3 seconds.
<pre>
Press [ENTER] to launch image stored in flash or [SPACE] to cancel.

Initiating image launch in 3 seconds.
</pre>

When the boot sequence is interrupted, Eboot enters menu-driven configuration mode.

== Menu Overview ==

=== Main Menu ===
<pre>
--------------------------------------------------------------------------------
Eboot Main Menu
--------------------------------------------------------------------------------
[0] IP address: 0.0.0.0
[1] Subnet Mask: 0.0.0.0
[2] Boot delay: 3 seconds
[3] DHCP: (Enabled)
[5] Auto Download image at startup(Disable)
[D] Download image now
[L] Launch existing flash resident image now
[S] Set BSP Configuration
[R] Reboot
</pre>
{{Note|Selection is not case sensitive}}

* IP address
:- Configures the IP address of the device in case DHCP is not used
* Subnet Mask
:- Configures the Subnet Mask of the device in case DHCP is not used
* Boot delay
:- Specifies the delay in seconds before Auto Download/Launch of an image
* DHCP
:- Use DHCP to acquire an IP address during Windows CE boot
* Auto Download image at startup
:- Configures whether to launch an image from NAND or download an image using KITL:
:* {{cmd|Disable}} - launch an image from NAND
:* {{cmd|Enable}} - download an image using KITL
* Download image now
:- Download an image using KITL without making this the default option
* Launch existing flash resident image now
:- Load the image stored in the NAND flash without making this the default option
* Set BSP Configuration
:- Advanced configuration of the image. Discussed in the next section.

=== Set BSP Configuration ===
<pre>
----------------------------------------------------------
Set BSP Configuration
----------------------------------------------------------
[B] Bit Blit: (Software optimized)
[T] KITL(Image Download) Transport: (DM9000a)
[K] Enable KITL: (Enabled)
[L] Enable KITL Polling Mode: (Disabled)
[I] Enable IMM driver: (Enabled)
[V] Enable VBridge: (Disabled)
[F] System frequency: IPM enable
[D] Enable/Disable image drivers
[U] USB Functionality: USB Host
[A] STUART usage: (Debug Serial)
[W] BT/WLAN Combo Card usage: (Both Disable)
[C] Clean System Hive Registry: (Disabled)
[E] Clean Users Hive Registry: (Disabled)
[R] Reset to factory default configuration
[S] Save configuration to FLASH
[Q] Quit to Main menu
</pre>
* Bit Blit
:- Open the Bit Blit menu. Only {{Filename|Software Optimized}} setting is supported
* KITL
:- The KITL transport setting. Only DM9000a Ethernet controller is supported
* Enable KITL
:- Enable or disable KITL in images that include it
* Enable KITL Polling Mode
* Enable IMM driver
:- Enable Marvell driver for SRAM handling. Do not change this option.
* Enable VBridge
:- Enable the VMINI virtual network adapter in images that include KITL
* System Frequency
:- Open the [[#System_Frequency_Menu|System frequency sub-menu]]
* Enable/Disable image drivers
:- Open the [[#Drivers_Menu|Drivers sub-menu]]
* STUART Usage
:- Enable/disable debug output via STUART
* BT/WLAN Combo Card usage
:- Open the [[#BT/WLAN_Menu|BT/WLAN submenu]]
* Clean System Hive Registry
:- Reset the System registry to the state stored in the {{filename|NK.bin}} file
* Clean Users Hive Registry
:- Reset the User registry to the state stored in the {{filename|NK.bin}} file
* Reset to factory default configuration
:- Reset Eboot configuration to the state stored in the {{filename|eboot.nb0}} image
* Save configuration to FLASH

=== System Frequency Menu ===
<pre>
-------------------------------------------------------
System frequency: IPM enable
-------------------------------------------------------
[1] Ring Oscillator Mode(Some device will not work)
[2] 208 Mhz
[3] 416 Mhz Turbo
[4] 624 Mhz Turbo
[I] IPM enable
[Q] Quit
</pre>
* Ring Oscillator
:- Not supported by Compulab
* 208 - 624
:- Set the CPU frequency to a constant value.
: Constant CPU frequency setting causes output of IPM error messages to the debug console. These messages can be safely disregarded.
* IPM enable
:- The Dynamic Frequency change driver (IPM) is enabled.

=== Drivers Menu ===
<pre>
-----------------------------------
Enable/Disable image drivers
-----------------------------------
[1] SPI Driver: (Disabled)
[2] Backlight Driver: (Enabled)
[3] Battery Driver: (Disabled)
[4] Codec Driver: (Enabled)
[5] BTUART Driver: (Disabled)
[6] FFUART Driver: (Disabled)
</pre>
Each option Disables/Enables the specified driver.
 The Codec driver is responsible for Audio and Touch functionality.

=== BT/WLAN Menu ===
<pre>
--------------------------------------------
BT/WLAN Combo Card usage: (Both Disable)
--------------------------------------------
[1] Both Disable
[2] Only Enable Bluetooth
[3] Only Enable WiFi
[4] Both Enable
[Q] Quit
</pre>

[[Category:Windows CE|Configuring Eboot]]
[[Category:CM-X300|Configuring Eboot]]

CM-X300: WinCE: Demo Image

2010-03-16T16:18:30Z

Shai:

The Windows Embedded CE Demo for CM-X300 is based on the standard {{WindowsCEVer}}.
== CM-X300 Features Supported ==
The CM-X300 Demo image supports the following features:
* NAND Flash Disk
* TFT LCD (pre configured for Toppoly TD035STEE1 TFT 480x640)
* Audio (input/output)
* Wi-Fi 801.11b/g
* Bluetooth
* Suspend / Resume
* USB 1.1 Host / Salve
* USB 2.0 Slave
* Ethernet
* Serial ports
* SD/MMC CARD
* GPIO access
* I2C/SPI bus
* Touch screen
* Keypad
* RTC (H/W rev. 1.2 and up)
* Backlight
* Battery management
* VIP / Quick capture interface (currently with limited functionality)

== Demo Image Contents ==
The following standard Windows Embedded CE components are included in this demo image:
* File system Explorer
* ActiveSync
* AYGShell
* Internet Explorer XAML UI Sample Browser
* Gestures Support
* Flash Lite ActiveX control
* Windows Media Player
* Telnet Server
* TCPMP Player
* ItaskMgr (a PC-like task manager)
* All MS Bluetooth Profiles

{{Note|For a complete list of the components included in the image refer to the [[media:CM-X300-ComponentList-WinCE.zip|Components list]].}}

== Get Connected with ActiveSync ==
ActiveSync enables data synchronization between a desktop computer and the CM-X300. You must install ActiveSync on your PC before connecting it to the CM-X300.

=== On the Host PC ===
==== Hosts running Windows XP ====
* Download and Install [http://www.microsoft.com/windowsmobile/en-us/downloads/microsoft/activesync-download.mspx ActiveSync] from Microsoft website.
* ActiveSync may experience connection problems caused by Windows desktop firewall applications. Read the [http://www.microsoft.com/windowsmobile/en-us/help/synchronize/activesync-usb.mspx ActiveSync Troubleshooting Guide] for host PC configuration instructions.
* Ensure that ActiveSync synchronization via USB is enabled in the Connection Settings dialog box
:[[Image:ActiveSync connection settings window.jpg]]
===== Installing ActiveSync driver for the CM-X300 =====
:* On the first connection the "New hardware found" wizard appears. Please follow the selections depicted below:
: [[image:Active Sync driver step1.jpg]]
: [[image:Active Sync Driver step2.jpg]]
: [[image:Active Sync Driver step3.jpg]]
: [[image:Active Sync Driver step4.jpg]]
: [[image:Active Sync Driver step5.jpg]]
:* If the following confirmation dialog pops up, choose "No":
: [[image:Active Sync Driver step6.jpg]]
: [[image:Active Sync Driver step7.jpg]]
:* Now ActiveSync setup is complete.

==== Hosts running Windows Vista/7 ====
* Download and install the latest version of [http://www.microsoft.com/windowsmobile/en-us/downloads/microsoft/device-center-download.mspx Windows Mobile Device Center (WMDC) for Windows 7] from Microsoft website
* Ensure that the CM-X300 registry has {{parameter|[HKEY_LOCAL_MACHINE\Drivers\USB\FunctionDrivers\Serial_Class]}} key with the following value:
<pre>
[HKEY_LOCAL_MACHINE\Drivers\USB\FunctionDrivers\Serial_Class]
"idVendor"=dword:045E
"idProduct"=dword:00ce
</pre>
:- A dedicated Vendor ID should be purchased and used for mass production.
:- CM-X300 registry may be altered as described in the [[#RegEdit|RegEdit]] section.

=== On the Target (CM-X300) ===
==== PXA300 processor (C624 option) ====
* Connect a USB cable to the USB 2.0 port (connector P8 on SB-X300) or to the USB 1.1 slave port (connector P10 on SB-X300).
* USB 2.0 is the default configuration.

==== PXA310 processor (C624M option) ====
* Configure the USB port to function as Slave as described in [[#USB|USB section]].
* Connect a USB cable to the connector P10 on SB-X300.

== Demo Image Componentes ==
The demo image is packed into the raw NK.bin file that is stored in the CM-X300 NAND flash during installation.

=== RAM ===
The CM-X300 supplied with the evaluation kit is equipped with 128MB of RAM. The demo image requires approximately 40MB and leaves 88MB for application use.

=== NAND Flash ===
The CM-X300 supplied with the evaluation kit is equipped with 512MB NAND flash.
U-Boot and Eboot bootloaders are stored in the NAND flash.

During demo image installation, the NAND flash is automatically partitioned and space is reserved for the runtime image, which is stored in the NAND flash unpartitioned space.

Space for a second runtime image is reserved to facilitate a fail-safe update mechanism.

Approximately 400 MB of free space is available for data storage on the NAND. Data may be stored in the NAND directory ("\nandflash").

=== Persistent Registry ===
The demo image is built with a "Hive-Based Registry" option. This means that the system registry is stored in the NAND flash data partition, making registry entries persistent when the device is powered off.The demo image is configured with a "Lazy Flush" registry policy. The registry settings are stored in RAM and are flushed into the NAND Flash every 30 seconds. After changing registry settings, allow 30 seconds before turning off the power or performing a hardware reset. This will ensure that the changes are saved into the NAND flash.

The flush period may be changed through the following registry value:
<pre>
[HKEY_LOCAL_MACHINE\System\ObjectStore\RegFlush]
"FlushPeriod"=dword:7530
</pre>

=== Networking ===
The following network interfaces are supported in the demo image:
* CM-X300 Ethernet - Full-featured 10/100 Ethernet interface. Implemented with the Davicom DA9000A Ethernet controller on the CM-X300 module.
* Wireless LAN - incorporates full-featured 802.11 b/g capabilities. Implemented with the Wi2Wi W2SW0001 WLAN controller on the CM-X300 module.

The demo image image is configured to use a DHCP server to obtain network settings for the two network adapters. Network settings may be changed in the Windows CE Control Panel.
==== Defining static IP address ====
It is possible to configure a static IP address by modifying the registry.

For example, the following registry settings disable DHCP and define the static IP 10.1.1.144 for the CM-X300 Ethernet controller:
<pre>
[HKEY_LOCAL_MACHINE\Comm\DM9CE1\Parms\TcpIp]
"EnableDHCP"=dword:0
"IpAddress"="10.1.1.44"
"Subnetmask"="255.255.255.0"
"DefaultGateway"="10.1.1.1"
"UseZeroBroadcast"=dword:0
</pre>

A static IP may be assigned to the Ethernet interface using Eboot configuration menu. For further details please refer to [[CM-X300:_WinCE:_Configuring_Eboot|Configuring Eboot]] article.

=== USB ===
==== PXA300 ====
* Connector P10 on SB-X300 provides a USB host port that operates at full/low speed.
:- The port may be configured in Eboot to operate as a device port at full/low speed. See [[CM-X300:_WinCE:_Configuring_Eboot|Configuring Eboot]].
* Connector P8 on SB-X300 provides a USB device port (used mainly for ActiveSync).

==== PXA310 ====
* Connector P10 on SB-X300 provides a USB host port that operates at full/low speed.
: The port may also function as high speed device. The USB port configuration may be changed in the Windows CE Control Panel. Use {{MenuEntry|Start->Settings->Control Panel->USB Functionality Chooser}} to switch between USB host and USB device functionality. The CM-X300 system should be restarted to activate the new settings.

=== SD card ===
* The SB-X300 evaluation board features an SD socket (connector P14).
* When an SD card is inserted it is mounted automatically as “Storage Card” under “My Device”.
* The demo image has been tested successfully with the following types of SD cards: SanDisk Ultra III 2Gb, Kingston 2Gb, SanDisk 1Gb, and Kingston Micro SDHC 4Gb.

=== Touch Screen ===
The demo image is calibrated for the Toppoly TD035STEE1 LCD touch screen.
To fine-tune the calibration, run the touch screen calibrator on the first boot by tapping
{{MenuEntry|Start->Settings->Control Panel->Stylus->Calibration}}.
For further details about touch screen calibrator registry settings refer to the [http://msdn.microsoft.com/en-us/library/ms926952.aspx Touch Screen (Stylus) Registry Settings] MSDN article.

The Touch Screen sensitivity is controlled by the {{RegKey|HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\TOUCH}} registry key:
<pre>
[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\TOUCH]
"Sensitivity"=dword:30
</pre>
The "Sensitivity" value is a hexadecimal number between {{cmd|1}} and {{cmd|3F}}. The lower values correspond to higher panel sensitivity.

Reboot the device after a change.

=== Keypad ===
The demo image is configured to support the 3x3 keypad provided with the CM-X300 evaluation kit.

The default key mappings are listed below:
* "Left", "Right", "Up", "Down" buttons control cursor movement (SW3, SW7, SW4, SW6 respectively)
* "SW5" button acts as "Enter" key
* "SW1" (Func1) button launches Internet Explorer
* "SW2" (Func2) button launches Media Player
* "SW8" (Func3) button launches ItaskMgr
* "SW9" (Func4) button launches Windows Explorer

The application assignment to particular keys is defined in the following registry settings:
<pre>
[HKEY_LOCAL_MACHINE\SOFTWARE\Compulab\KeyPad]
"APP1"= "\\Windows\\iesample.exe"
"APP2"= "\\Windows\\ceplayer.exe"
"APP3"= "\\Windows\\itaskmgr.exe"
"APP4"= "\\Windows\\explorer.exe"
</pre>

=== Display Subsystem ===
The demo image is configured for a Toppoly TD035STEE1 TFT LCD.
The default resolution is 480x640 with 16-bit color depth and portrait display.

==== Using custom display settings ====
The LCDAdapt utility included in the [http://www.compulab.co.il/x300/download/x300-wince6-img.zip Windows CE 6 run-time image package] allows easy configuration of LCD timing parameters.
The LCDAdapt utility runs on the host PC and connects to the CM-X300 device using the ActiveSync.

* The necessary values are extracted from the specification of the display.
* Hovering with the mouse pointer over each field will display a tool tip with an explanation.
* Press the "Connect" button to connect to the device.
* The LCDAdapt will read the current settings on the device and display them.
* Use LCD parameters extracted from the display specification to fill in the settings
* Press the "Send Settings" button. The LCDAdapt utility will configure the LCD controller on the CM-X300 and restart it.
: [[image:LCDAdapt-ScreenShot-X300.jpg]]

The program changes the following registry settings on the device:
<pre>
[HKEY_LOCAL_MACHINE\Drivers\Display\GPE]
"HorizontalSize"=dword:1E0
"VerticalSize"=dword:280
"Bpp"=dword:10 ; Bytes per pixel
"BLW"=dword:7 ; Timing
"ELW"=dword:17 ; Timing
"HSW"=dword:8 ; Timing
"BFW"=dword:2 ; Timing
"EFW"=dword:4 ; Timing
"VSW"=dword:2 ; Timing
"104M"=dword:4 ; PCD
"156M"=dword:6 ; PCD
"208M"=dword:9 ; PCD
"39M"=dword:0 ; PCD
"D0CS"=dword:2 ; PCD
"OEP"=dword:0 ; Polarity
"PCP"=dword:1 ; Polarity
"HSP"=dword:1 ; Polarity
"VSP"=dword:1 ; Polarity
</pre>
{{Note|The LCDAdapt utility requires .Net 3.x framework installed on the host PC}}
For additional details about CompuLab LCD adaptation services, please refer to [http://www.compulab.co.il/x300/html/x300-lcd.htm LCD Panel support].

==== Video Playback ====
The package supports playback of the following video formats:
* MPEG4
* H.264
* MPEG2
* 3GP

Media playback requires installation of codec pack available in the {{filename|Utilities\GraphicAcceleration\Graphics\Cab\HWCodecsCMX300}} CAB archive.

The project that generates the CAB file is located in the same directory.

The rest of the graphics examples are located in {{filename|Utilities\GraphicAcceleration\Graphics}} and there is no documentation available for them.

=== Backlight ===
The CM-X300 supports seven levels of backlight brightness.

The backlight level can be modified in the Windows CE Control Panel. Use {{MenuEntry|Start->Settings->Control Panel-> Backlight Level}} to adjust the brightness.
The backlight level altered directly via the {{RegKey|HKEY_CURRENT_USER\ControlPanel\BackLight}} registry key:
<pre>
[HKEY_CURRENT_USER\ControlPanel\BackLight]
"BacklightLevel"=dword:0
</pre>

=== Battery and Charging ===
The CM-X300 evaluation kit is shipped with a 3000mAh Li battery. For detailed instructions about the battery connection please refer to the SB-X300 manual.

Monitor the battery power by tapping {{MenuEntry|Start->Settings->Control Panel->Power}}.

The CM-X300 / SB-X300 supports battery charging using the power cable supplied with the evaluation kit. For detailed instructions about the battery connection refer to the SB-X300 manual.The charging mechanism utilizes fast charging method with a charge current of 1000mA.

The battery driver must be enabled in the Eboot menu. Refer to [[CM-X300:_WinCE:_Configuring_Eboot|Configuring Eboot]] article.

=== Suspend / Resume ===
The CM-X300 Windows CE demo image enters suspend mode upon one of the following events:
* {{filename|Start->Suspend}} menu entry activation.
* Rising edge detection on GPIO83.
*{{cmd|Rtc_cmd.exe}} invocation. {{cmd|Rtc_cmd.exe}} is a console application with the following syntax:
<pre>
rtc_cmd [time before sleep in seconds] <sleep time in seconds>
</pre>
The system wakes up upon one of the following events:
* Rising edge detection on GPIO83.
* RTC timer (set by {{cmd|Rtc_cmd.exe}}) expiration.

=== Serial Ports ===
The demo image supports three serial ports. The serial ports mapping is summarized below:

{| cellpadding="3" border="1" style="border: 1px solid rgb(85, 85, 85); border-collapse: collapse;"
|-
! UART
! Connector
on SB-X300
! COM-port
! Notes
|-
| STUART
| P16
| COM4
| Used for diagnostic messages. Please refer to [[Configuring_Eboot_(CM-X300)|Configuring Eboot]] for configuration
|-
| BTUART
| P6
| COM5
|
|-
| FFUART
| P4
| COM1
| Not available with PXA310 CPU ('''C624M''' option)
|}

The serial ports operate at baud rates up to 3.6M. For more details please refer to the [http://www.marvell.com/products/processors/applications/pxa_3xx/PXA3xx_Developers_Manual.zip PXA3xx developers manual].

=== Wireless Interface Control ===
Bluetooth and WiFi power state is controlled by the Control Panel, {{MenuEntry|Start->Settings->Control Panel->Wireless Config}}.

The initial state of the wireless devices may be configured in Eboot as described at [[Configuring_Eboot_(CM-X300)|Configuring Eboot]].

=== Bluetooth ===
The demo image includes the following Microsoft Bluetooth profiles:
* Object Push Profile (OBEX)
* File Transfer Profile
* Human Interface Device Profile
* LAN Access Profile
* Personal Area Network Profile
* Hands-free and headset Profiles

The CM-X300 Bluetooth connectivity was verified with Motorola HT820 Bluetooth Stereo Headphones with A2DP profile.

Bluetooth Manager located at {{MenuEntry|Start->Settings->Control Panel->Bluetooth Device Properties}} allows to scan for remote Bluetooth devices and pair with them.
Bluetooth Audio connection {{cmd|AdpMgr}} sample is available at {{filename|Start->Programs->A2dpMgr}}.

=== Reboot ===
Use the "Software Reboot" shortcut on the desktop to reboot the system. The "Software Reboot" ensures proper system shutdown and registry flush.

=== Run Once Functionality ===
Run Once functionality allows addition of custom files and registry modifications after Windows CE image installation.

During the first boot the Windows CE image searches for {{filename|RunOnceCab.cab}} archive on SD card and USB flash drive. If the archive is found, it is loaded and executed. The Run Once functionality is disabled after the first boot is complete.

=== Running custom applications on startup ===
In order to run a custom application on the system startup, use the AutoLaunch utility integrated into the demo image.

The AutoLaunch utility extends the functionality of the {{RegKey |HKEY_LOCAL_MACHINE\Init}} registry key and allowing configurable launch delay for each application.
AutoLaunch monitors the following registry keys and values:
<pre>
[HKEY_LOCAL_MACHINE\Startup]
“Process0” =”Application.exe param1 param2”
“Process0Delay”=dword:delay ;in milliseconds

[HKEY_LOCAL_MACHINE\Startup\ApplicationName]
“Process0” =”Application.exe param1 param2”
“Process0Delay”=dword:delay ;in milliseconds
</pre>
Usage example:
<pre>
[HKEY_LOCAL_MACHINE\Startup\ceplayer]
"Process0” =”ceplayer.exe \windows\sound2.wav”
“Process0Delay”= dword:1388 ;5000 in decimal
</pre>
The above example launches CEPlayer five seconds after boot completion. The additional "\windows\Sound2.wav" parameter is used by CEPlayer to play the specified file.

== Sample Applications ==
The Windows CE demo image package includes demo applications that demonstrate how to use common interfaces such as SPI, I2C and GPIO.
They applications are located at the {{Filename|Demo Applications}} directory.
==== GPIO Sample ====
This application demonstrates how to use the GPIO driver in order to control the state of GPIO pins.

For further details, please refer to [[CM-X300: WinCE: GPIOs Programming | GPIOs Programming]].
==== I2C Sample ====
The I2C sample demonstrates how to use the I2C driver.

Fur further reading refer to [[CM-X300: WinCE: I2C Programming|I2C Programming]].

==== SPI Sample ====
The SPI_Thermometer sample included in the WinCE demo image package, demonstrates how to use the SPI driver.

For further details, please refer to [[CM-X300: WinCE: SPI Driver API|SPI Programming]].

==== C# ====
The COMPortTester sample demonstrates a simple C# application that interfaces with the COM ports.
==== SilverlightPlayerExample ====
The SilverlightPlayerExample sample demonstrates basic use of Silverlight.

== Miscellaneous Utilities ==
=== SetPowerState ===
A command line utility that performs global system power state transitions.
Syntax:
<pre>
SetPowerState.exe <State> [HexStateFlags [HexOptions]]
</pre>
: {{cmd|State}} - the system power state defined in the registry. Possible values are: {{parameter|Reboot}} and {{parameter|Suspend}}.
: {{cmd|StateFlags}} - specifies hexadecimal state flags, e.g. 200000 (POWER_STATE_SUSPEND).
: {{cmd|Options}} - specifies hexadecimal options, e.g. 1000 (POWER_FORCE).

The most useful transitions are:
: {{filename|SetPowerState reboot}} - performs watchdog reboot of the CM-X300.
: {{filename|SetPowerState suspend}} - puts the CM-X300 into the suspend mode.
{{Note|Before each power state transition, the registry is flushed to the NAND flash}}

=== SysConf ===
A command line utility that allows easier debugging of the platform. For further details please refer to [[WinCE: Sysconf|Sysconf]] article.

=== A2DP Demo Application ===
Th A2DP utility allows the user to pair with a BlueTooth device and activate the A2DP BlueTooth profile.
The program is available with full source code.

=== RegEdit ===
An embedded registry editor able to write/read/delete registry values.
Syntax:
<pre>
reg.exe <(-)Registry Key> (h) <Value>
</pre>
: "-" before a Registry Key deletes the value
: "h" modifier should be used for hexadecimal values

An OnDevice registry editor is available at: [http://geekswithblogs.net/BruceEitman/archive/2009/07/27/window-ce-simple-little-registry-editor.aspx Bruce Eitman's Blog].

=== SetWiFiPowerMode ===
The SetWiFiPowerMode utility activates WiFi power-saving mode. This significantly reduces the WiFi power consumption, however WiFi performance is degraded in this mode.

This program is located at {{filename|\Utilities\SetWiFiPowerMode}}
{{Note|This utility is not included in the NK.bin itself}}

=== LCDAdapt ===
This utility helps to integrate a custom LCD display. Please refer to [[#Using_custom_display_settings| Using custom display settings]].

== See Also ==
* [[Getting started with Windows CE on CM-X300]]
* [[WinCE: Application Development|Application Development for CM-X300 modules]]
* [[WinCE: OSDesign Development|Windows CE OSDesign Development for CM-X300 modules]]
* [[CM-X300: WinCE: OSDesign Configuration|OSDesign Configuration]]
* [[CM-X300: WinCE: Configuring Eboot|Configuring Eboot]]

[[Category:Windows CE|Demo Image]]
[[Category:CM-X300|Demo Image]]

CM-X300: WinCE: OSDesign Configuration

2010-03-16T16:16:53Z

Shai: /* Image Debugging */

== Installing the Driver Package ==
* Close the Platform Builder Application if it is open.
* Copy the CM_X300_BSP directory to \WINCE600\Platform\
* Copy the CM_X300_CE6 directory to \WINCE600\OSDesigns\
* Launch VS2005 and open \WINCE600\OSDesigns\CM_X300_CE6\CM_X300_CE6.sln

== Building the Platform Project ==
The CM_X300 Platform Project is used to build CompuLab Windows Embedded CE demo image. It includes many components and is highly recommended as a starting point for a new project. The demo image is relatively large, ~35 MB. Typical Windows CE images for a specific application are much smaller, 8-15 MB.

To build the CM_X300 platform:
* select the {{MenuEntry|Open->Project/Solution}} command from the File menu of the VS2005 and select the {{Filename|\WINCE600\OSDesigns\CM_X300_CE6\CM_X300_CE6.sln}} file.
* Check that the project is configured for Release.
* Perform {{Cmd|Rebuild Solution}} from the {{Cmd|Build}} menu (alternatively, perform {{MenuEntry|Build->Advanced Build Commands->Clean Sysgen}}).

The build process takes about 15-20 minutes.

=== CPU Type ===
The CM-X300 may be assembled with two CPU types:
* PXA300 - the C624 option
* PXA310 - the C624M option

The default BSP configuration targets the PXA310 CPU.

==== Choosing CPU Type ====
The CPU type is defined in {{Filename|CM_X300_BSP.BAT}} file in the platform directory. Ensure that the {{parameter|BSP_CPU_TYPE}} setting corresponds with the correct CPU type. Leave the appropriate line without the REM directive:
<pre>
set BSP_CPU_TYPE=310
REM set BSP_CPU_TYPE=300
</pre>

=== Build Options ===
* Use {{MenuEntry|Build->Advanced Build Commands->Sysgen}} when adding Platform Builder components (Catalog items) to the project.
* Use {{MenuEntry|Build->Advanced Build Commands->Clean Sysgen}} when removing Platform Builder components (Catalog items) from the project.
* Use {{MenuEntry|Build->Advanced Build Commands->Build Current BSP and Subprojects}} when modifying Compulab BSP components that are included in the project or performing changes in the BSP files.
* Use {{MenuEntry|Build->Advanced Build Commands-> Rebuild Build Current BSP and Subprojects}} when adding/removing Compulab BSP components to/from the project.
{{Warning|Do not use {{MenuEntry|Build->Advanced Build Commands->Build and Sysgen}} or {{MenuEntry|Build->Advanced Build Commands->Rebuild and Clean Sysgen}} that perform compilation and sysgen on the entire Platform Builder tree.
It is recommended to remove the two commands mentioned above from the menu permanently}}

== Windows CE Image Customization ==
There are two ways to customize the Windows CE image:
# Recommended method: Add or remove BSP components from the demo CM_X300_CE6 project.
# Create a new platform project and then manually add all the necessary BSP components as described in the Platform Builder documentation. Refer to [[WinCE: OSDesign Development|Windows CE OSDesign Development]] page.

=== BSP customization using batch files ===
The BSP is fully customizable and allows inclusion/exclusion of each component via BSP_NO environment variables.

To exclude a certain driver, set the BSP_NO environment variables in {{Filename|CM_X300_BSP\CM_X300_BSP_COMMON.bat}} and rebuild the BSP with {{MenuEntry|Build->Advanced Build Commands->Rebuild Current BSP and Subprojects}}.

The following table lists the BSP_NO environment variables that can be defined:

{| border="1"
|-
| '''Variable'''
| '''Meaning'''
| '''Comments'''
|-
| BSP_NOKEYPAD
| No Keypad driver and no support for keyboard
|
|-
| BSP_NODISPLAY
| No Graphics
|
|-
| BSP_NONAND
| No NAND Flash driver
|
|-
| BSP_NOSDHC
| No SDIO card driver
|
|-
| BSP_NOWLAN
| No WiFi driver
|
|-
| BSP_NOI2C
| No I2C driver
|
|-
| BSP_NOUSB20FN
| No Usb 2.0 Function driver
|
|-
| BSP_NOUSBFN
| No Usb 1.1 Function driver
|
|-
| BSP_NOUSBHOST
| No Usb Host driver
|
|-
| BSP_NOAUDIO
| No Audio driver
|
|-
| BSP_NOTOUCH
| No Touch screen driver
|
|-
| BSP_NOCODEC
| No Codec driver
| (no Touch and no Audio)
|-
| BSP_NOBLUETOOTH
| No BlueTooth Driver
| No Bluetooth stack as well
|}

{{Note|Any environment variable defined in CM_X300_BSP\CM_X300_BSP_COMMON.bat will override the variables defined in Platform Builder project}}

=== RAM-Based Registry support ===
The CM-X300 BSP is configured for HIVE-based registry with lazy flushing. The registry hive is located in the system NAND flash.
To support a RAM-Based registry, perform the following actions:
* Add the {{Filename|RAM-based Registry}} component to the project
* Disable the following variables in the {{filename|CM_X300_BSP\CM_X300_PRODUCTION.bat}}:
<pre>
set PRJ_ENABLE_FSREGHIVE=1
set PRJ_ENABLE_REGFLUSH_THREAD=1
</pre>
* Perform "Clean Sysgen" using {{MenuEntry|Build->Advanced Build Commands->Clean Sysgen}}

=== Persistent File System ===
The CM-X300 BSP is configured to store the root directory in RAM, therefore the root filesystem is not persistent. To make the root and its subsequent folders persistent, change the Catalog item "ROM and RAM File System" to "ROM-Only file System".

{{Note|Any data saved to a non-persistent location is erased when the device resets. This includes the root directory ("\").}}

== CM-X300 BSP Subprojects ==
In addition to the drivers supplied with the BSP, there are a few useful utilities distributed as Subprojects. Subprojects allow adding software modules to the build without modifying the BSP source code located in the Platform source tree.
There are two Subproject types available with CM_X300_BSP:
* Subprojects that add optional functionality to the BSP are located in the {{Filename|\WINCE600\PLATFORM\CM_X300_BSP\Subprojects}} directory.
: These Subprojects are provided with the source code.
{| border="1"
|-
| '''Project Name'''
| '''Functionality'''
|-
| ''SetPowerState''
| Command line utility that controls the system power state and is used for software reboot and suspend support
|-
| ''Regedit''
| Command line registry editor. Allows remote changes of the device registry via telnet connection.
|-
| ''CoreCon''
| Executables required for application level debugging over Ethernet in VS2005
|-
| ''AutoLaunch''
| Executable that should be used for automatic launch of CoreCon (ConmanClient2.exe) at system startup. AutoLaunch.exe verifies IP address availability before loading ConmanClient2.exe. This is required because ConmanClient2 waits for incoming TCP/IP connections when communicating with VS 2005
|-
| ''SysConf''
| Command line utility for platform debugging
|-
| ''Tools''
|
* Command line RTC_CMD utility for RTC driven suspend/resume cycles
* CLTerm program for COM ports testing
|-
| ''BuildVer''
| This project adds a text file to the image specifying which revision was used to build the image. It requires a Tortoise Svn client installed on the desktop.
|}

* The Subprojects that add custom applications, control panel applets and registry settings to the demo image are located at {{Filename|\WINCE600\OSDesigns\CM_X300_CE6\Subprojects}} directory.
{| border="1"
|-
| '''Project Name'''
| '''Functionality'''
|-
| ''CPLApplets\WireLessCPL''
| Control panel applet that controls the power state (on/off) of wireless devices
|-
| ''CPLApplets\KeypadConfigCPL''
| Control panel applet that customizes keypad buttons functionality
|-
| ''CPLApplets\BacklightCPL''
| Control panel applet that controls the LCD backlight level
|-
| ''TCPMP''
| Open source Media player
|-
| ''TaskManager''
| Open source Task Manager
|-
| ''KeypadAppLaunch''
| A utility to capture application launching key presses
|-
| ''LookAndFeel''
| Look and feel of the demo image (background, theme, sounds, etc.)
|}

== KITL Connection ==
Platform Builder communicates with a device using KITL protocol. For details about KITL refer to [http://www.microsoft.com/video/en/us/details/0a8d9767-a419-4f5e-9b37-4328b0993d1d Microsoft's KITL Broadcast] article.

The following actions should be performed in order to setup a KITL connection between the CM-X300 and Platform Builder 6.0:
# Ensure that a serial terminal is connected to the CM-X300 as described in [[CM-X300: WinCE: Setting Up a Console|Setting up a console]]
# Ensure that an Ethernet cable is connected to the CM-X300 platform
# In Platform Builder, go to {{MenuEntry| Target->Connectivity Options}}. [[Image:Target Device Connectivity Options X300.jpg]] 
# Click on {{Filename|Add Device}} and provide a device name (such as CM-X300). [[Image:Target Device Connectivity Options Add Device X300.JPG]] 
# In {{Filename|Kernel Service Map}}, select {{Filename|Ethernet}} for Download and Transport options and {{Filename|KdStub}} for the Debugger.
# Press {{Filename|Download settings}} and at the same time, נoot the target device and press {{Filename|SPACE}} in the device console to get Eboot main menu.
# Type "D" to download the image from Platform Builder (results in a broadcast of BOOT ME messages).
# Platform Builder will show the target device unique name (e.g. CM_X30064242) in the {{Filename|Active Devices}} area. [[Image:Ethernet Download SettingsX300.JPG]] 
# Press Transport settings and select {{Filename|Use device name from bootloader}}. [[Image:Ethernet KITL SettingsX300.JPG]] 

Once the connection is configured, download and launch the newly created WinCE image:
# In Platform Builder Target toolbar, select the configured device and then select {{MenuEntry|Target->Attach Device}}.
# Ensure that Eboot is ready for download (i.e. Sends Boot Me messages).

== Image Debugging ==
=== Platform Debugging with RETAILMSG ===
Debug messages output to the serial port may be enabled for both Retail and Debug build types. 
To enable RETAILMSG output to COM-A serial port, set the "STUART Usage" option to "Debug Serial" in the BSP Configuration menu in [[CM-X300: WinCE: Configuring Eboot|Eboot]]

=== Platform Debugging over Ethernet ===
KITL allows platform debugging over Ethernet and enables use of [http://msdn.microsoft.com/en-us/library/ee479862.aspx VS2005 Remote Tools]. During debug session, KITL redirects all the serial output into VS2005 output window.

* Choose the following platform options to enable platform debugging:
** Enable kernel debugger.
** Enable KITL.
* Perform {{MenuEntry|Build->Advanced Build Commands ->Rebuild Current BSP and Subprojects}}.
* Start the debug session as described in [[#Connecting to the device using KITL|Setup Target for CM_X300 Image Evaluation]] section.

{{Note|Run-time image built with the Kernel debugger and KITL dedicates CM-X300 Ethernet port to debug communication. This port cannot be used for application Ethernet traffic. The application Ethernet traffic can be routed through virtual VMINI adapter that should be enabled in [[CM-X300: WinCE: Configuring Eboot|Eboot configuration]].}}

== See Also ==
[[WinCE: OSDesign Development | Windows CE OSDesign Development]]

[[CM-X300: WinCE: Hive Based Registry on SD card|Persisting the Registry to the SD Card]]

[[Category:Windows CE|OSDesign Configuration]]
[[Category:CM-X300|OSDesign Configuration]]

Template:MenuEntry

2010-03-16T16:13:12Z

Shai: New page: '''{{{1}}}'''

'''{{{1}}}'''

Template:Struct

2010-03-16T15:19:17Z

Shai:

__NOEDITSECTION__ <noinclude></noinclude>
{{{HeadLevel}}} {{{Structname}}} {{{HeadLevel}}}
{{#if: {{{Description}}} |
{{{Description}}} |
}}
{{#if: {{{Field1}}} |
={{{HeadLevel}}} Fields {{{HeadLevel}}}= |
}}
{|cellpadding="3" border="0" style="border: 0px solid rgb(85, 85, 85); border-collapse: collapse;"
{{#if: {{{Field1|}}}|
! <div style="text-align:left;"> Name </div> !! <div style="text-align:left;"> Description </div>
{{!}}- valign="top"
{{!}} {{{Field1}}} {{!!}} {{{Fieldexp1}}} |}}
{{#if: {{{Field2|}}}|
{{!}}- valign="top"
{{!}} {{{Field2}}} {{!!}} {{{Fieldexp2}}} |}}
{{#if: {{{Field3|}}}|
{{!}}- valign="top"
{{!}} {{{Field3}}} {{!!}} {{{Fieldexp3}}} |}}
{{#if: {{{Field4|}}}|
{{!}}- valign="top"
{{!}} {{{Field4}}} {{!!}} {{{Fieldexp4}}} |}}
{{#if: {{{Field5|}}}|
{{!}}- valign="top"
{{!}} {{{Field5}}} {{!!}} {{{Fieldexp5}}} |}}
{{#if: {{{Field6|}}}|
{{!}}- valign="top"
{{!}} {{{Field6}}} {{!!}} {{{Fieldexp6}}} |}}
{{#if: {{{Field7|}}}|
{{!}}- valign="top"
{{!}} {{{Field7}}} {{!!}} {{{Fieldexp7}}} |}}
{{#if: {{{Field8|}}}|
{{!}}- valign="top"
{{!}} {{{Field8}}} {{!!}} {{{Fieldexp8}}} |}}
{{!}}}
{{#if: {{{Remarks|}}} |
={{{HeadLevel}}} Remarks {{{HeadLevel}}}=
:{{{Remarks}}} |
}}

CM-X300: WinCE: GPIOs Programming

2010-03-15T11:46:28Z

Shai:

== GPIO Sample Application ==
=== Overview ===
This GPIOSample application demonstrates basic functionality of CM-X300 GPIOs under Windows CE:
* How to configure a GPIO pin as output and manipulate it.
* How to configure a GPIO pin as input and respond to changes in signal level.
* How to setup an edge triggered event.

=== Application Behavior ===
The GPIOSample manipulates the following GPIOs:
* GPIO 122 (pin 12 of connector P13 on the SB-X300) - Set as output
* GPIO 124 (pin 14 of connector P13 on the SB-X300) - Set as input
* GPIO 128 (Pin 24 of connector P11 on the SB-X300) - Set as input. (pin 0 on GPIO extender 0)

GPIO122 voltage level may be monitored with a DVM or an oscilloscope. GPIO124 and GPIO128 may be controlled by an external switch or button.

The GPIOSample performs the following actions:
* Edge detection on GPIO124 (cpu GPIO). Event handler is registered with [[#BOOL_GPIOUnRegisterInterrupt.28HANDLE_hDevice.2C_DWORD_num.29|GPIORegisterInterrupt]]. The handler calls [[#VOID_GPIOInterruptDone.28HANDLE_hDevice.2C_DWORD_num.29|GPIOInterruptDone]] to indicate interrupt completion.
* Edge detection on GPIO128 (GPIO extender). Event handler is registered with [[#BOOL_GPIOUnRegisterInterrupt.28HANDLE_hDevice.2C_DWORD_num.29|GPIORegisterInterrupt]]. The handler calls [[#VOID_GPIOInterruptDone.28HANDLE_hDevice.2C_DWORD_num.29|GPIOInterruptDone]] to indicate interrupt completion.
* Clock simulation on GPIO122 with a period of 3 seconds.
* Input voltage level monitoring on GPIO122.

== GPIO Driver API ==
=== Data Types ===
{{Enum| HeadLevel = ==== | Enumname = GPIO_VALUE |
Description = GPIO state enumeration|
Field1 = GPIO_LOW |
Field2 = GPIO_HIGH |
Field3 = |
Field4 = |
Remarks = |
}}

{{Enum| HeadLevel = ==== | Enumname = GPIO_EDGE_SETTINGS |
Description = |
Field1 = GPIO_REACT_ON_FALLING |
Field2 = GPIO_REACT_ON_RISING |
Field3 = GPIO_REACT_ON_BOTH |
Field4 = GPIO_DONT_REACT |
Remarks = |
}}

{{Struct| HeadLevel = ==== | Structname = GPIO_INTERRUPT |
Description = |
Field1 = DWORD dwGpioNum |
Fieldexp1 = |
Field2 = [[#GPIO_EDGE_SETTINGS|GPIO_EDGE_SETTINGS]] Edge|
Fieldexp2 = |
Field3 = HANDLE Event|
Fieldexp3 = |
Field4 = |
Field5 = |
Field6 = |
Field7 = |
Field8 = |
Remarks = |
}}

=== Functions ===
{{APIEx| HeadLevel = ==== | Signature = HANDLE GPIOOpen() |
Description = Opens an instance of the GPIO Driver. |
Return = Returns a handle that should be used to access the driver. Nonzero indicates success. |
Param1 = |
Param2 = |
Param3 = |
Param4 = |
Remarks = }}

{{APIEx| HeadLevel = ==== | Signature = void GPIOClose(HANDLE hDevice) |
Description = Closes the driver handle |
Return = |
Param1 = *hDevice - Handle to an open driver instance|
Param2 = |
Param3 = |
Param4 = |
Remarks = }}

{{APIEx| HeadLevel = ==== | Signature = BOOL GPIOSetValue(HANDLE hDevice,DWORD num, [[#GPIO_VALUE|GPIO_VALUE]] val) |
Description = Sets the state of a GPIO. |
Return = TRUE - indicates success
:FALSE - indicates failure|
Param1 = *hDevice - Handle to an open driver instance|
Param2 = *num - GPIO number.|
Param3 = *val - The desired logical state. |
Param4 = |
Remarks = Make sure the GPIO direction is setup as output.}}

{{APIEx| HeadLevel = ==== | Signature = BOOL GPIOGetValue(HANDLE hDevice,DWORD num,[[#GPIO_VALUE|GPIO_VALUE]] *gpioVal) |
Description = Return the logical state of a GPIO.|
Return = TRUE - indicates success
:FALSE - indicates failure|
Param1 = *hDevice - Handle to an open driver instance|
Param2 = *num - GPIO number.|
Param3 = *gpioVal - pointer to the GPIO state variable|
Param4 = |
Remarks = Make sure the GPIO direction is setup as input. Returned value for an output GPIO is undefined}}

{{APIEx| HeadLevel = ==== | Signature = BOOL GPIOSetAsInput(HANDLE hDevice, DWORD num) |
Description = Configures a GPIO as an input.|
Return = TRUE - indicates success
:FALSE - indicates failure|
Param1 = *hDevice - Handle to an open driver instance.|
Param2 = *num - GPIO number.|
Param3 = |
Param4 = |
Remarks = }}

{{APIEx| HeadLevel = ==== | Signature = BOOL GPIOSetAsOutput(HANDLE hDevice,DWORD num, [[#GPIO_VALUE|GPIO_VALUE]] val) |
Description = Configures a GPIO as an output and sets its logical state. |
Return = TRUE - indicates success
:FALSE - indicates failure|
Param1 = *hDevice - Handle to an open driver instance|
Param2 = *num - GPIO number.|
Param3 = *val - The initial GPIO value|
Param4 = |
Remarks = }}

{{APIEx| HeadLevel = ==== | Signature = BOOL GPIORegisterInterrupt(HANDLE hDevice,[[#GPIO_INTERRUPT|GPIO_INTERRUPT]] interrupt) |
Description = Registers a GPIO as an interrupt source. The interrupt is triggered according to the configuration in [[#GPIO_INTERRUPT|GPIO_INTERRUPT]].Edge member settings. |
Return = TRUE - indicates success.
:FALSE - indicates failure|
Param1 = *hDevice - Handle to an open driver instance|
Param2 = *interrupt- data structure that defines parameters for the interrupt registration |
Param3 = |
Param4 = |
Remarks = * The handle for the interrupt event is stored in [[#GPIO_INTERRUPT|GPIO_INTERRUPT]].Event|
:* This function must be called before using the [[#GPIO_INTERRUPT|GPIO_INTERRUPT]].Event parameter.
:* The [[#GPIO_INTERRUPT|GPIO_INTERRUPT]].Event parameter may only be used in a {{Cmd|WaitForSingleObject}} call. A {{Cmd|WaitForMultipleObjects}} call with [[#GPIO_INTERRUPT|GPIO_INTERRUPT]].Event will fail.
:* If you use GPIO_INTERRUPT.Event in a call to WaitForSingleObject before you call {{Cmd|GPIOInterruptInitialize}}, {{Cmd|GPIOInterruptInitialize}} will fail.
}}

{{APIEx| HeadLevel = ==== | Signature = VOID GPIOInterruptDone(HANDLE hDevice, DWORD num) |
Description = Signals to the kernel that GPIO interrupt processing is complete.|
Return = |
Param1 = *hDevice - Handle to an open driver instance|
Param2 = *num - GPIO number.|
Param3 = |
Param4 = |
Remarks = A program calls {{Cmd|GPIOInterruptDone}} when it has completed the interrupt processing and is ready for another interrupt.}}

{{APIEx| HeadLevel = ==== | Signature = BOOL GPIOUnRegisterInterrupt(HANDLE hDevice, DWORD num) |
Description = Disables the GPIO hardware interrupt.|
Return = TRUE - indicates success.
:FALSE - indicates failure |
Param1 = *hDevice - Handle to an open driver instance|
Param2 = *num - GPIO number.|
Param3 = |
Param4 = |
Remarks = A program calls {{Cmd|GPIOUnRegisterInterrupt}} to disable the hardware interrupt and to unregister the event that was registered by {{Cmd|GPIOInterruptInitialize}}.}}
[[Category:Windows CE|GPIOs Programming]]
[[Category:CM-X300|WinCE6.0: GPIOs Programming]]

CM-X300: WinCE: SPI Driver API

2010-03-15T07:18:04Z

Shai:

= Introduction =
This sample application demonstrates the SPI communication between CM-X300 and Maxim Semiconductor DS1722 thermometer. The DS1722 manual is available at: [http://www.maxim-ic.com/quick_view2.cfm/qv_pk/2766/t/al DS1722 manual].

The Windows CE demo image includes the SPI driver, which allows direct access to SSP3 functionality.
= SPI Sample =
== Connecting the device to CM-X300 ==
* The SPI device can be connected to the SSP3 port available on connector P6 on SB-X300. The following table describes the connector pin-out:
{|cellpadding="3" border="1" style="border: 1px solid rgb(85, 85, 85); border-collapse: collapse;"
| '''Signal Name''' || '''Pin Number'''
|-
| SSP3_TXD || 5
|-
| SSP3_RXD || 7
|-
| SSP3_CLK || 3
|-
| SSP3_SFRM || 1
|}
* Connect pin 6 (SERMODE) of DS1722 to VDD.
* Connect all remaining DS1722 pins to VDD and GND according to the device datasheet.

== SPI Sample ==

The SPI Sample performs the following actions:
* Configure the SPI clock frequency (5KHz) and SFRM signal polarity.
* Read the temperature measurement.
* Write to the DS1722 configuration register.
* Read back from the configuration register.

= SPI Driver =
== Overview ==
The CM-X300 SPI driver is a stream driver that may be accessed using the "SPI" prefix.

== SPI Driver API ==
=== Data Types ===
{{Struct | HeadLevel = ==== | Structname = SPI_SLAVE_CONFIG |
Description = Device configuration structure|
Field1 = DWORD dwDataSize |
Fieldexp1 = Size of each data frame in bits, allowed values: [4,32] |
Field2 = DWORD dwClockRate|
Fieldexp2 = Frequency in KHz. Allowed values: [4,13*1024] |
Field3 = [[#POLARITY|POLARITY]] ClockPol|
Fieldexp3 = Clock polarity |
Field4 = [[#POLARITY|POLARITY]] ChipSelectPol |
Fieldexp4 = SFRM polarity |
Field5 = BOOL bTxTristate |
Fieldexp5 = Tristate TX line when SFRM is de-asserted |
Field6 = BOOL ClkPhaseHalfCycle|
Fieldexp6 = TRUE - CLK remains in its inactive/idle state until one-half clock cycle after the SFRM signal is asserted at the beginning of a frame. 
FALSE - CLK remains in its inactive/idle state until one full clock cycle after the SFRM signal is asserted at the beginning of a frame. 
Meaningless when bCSExternal = TRUE |
Field7 = BOOL bCSExternal|
Fieldexp7 = SFRM is a GPIO |
Field8 = DWORD dwGpioNum|
Fieldexp8 = GPIO number for SFRM |
Remarks = bCSExternal is not supported in CM-X300|
}}
{{Struct | HeadLevel = ==== | Structname = SPITRANS|
Description = Transaction data|
Field1 = DWORD mTransactions |
Fieldexp1 = Number of data frames in the transaction|
Field2 = DWORD *mWriteBuffer |
Fieldexp2 = Data to be written to the port|
Field3 = DWORD *mReadBuffer |
Fieldexp3 = Data that was read from the port|
Field4 = | Field5 = | Field6 = | Field7 = | Field8 = |
Remarks = |
}}
{{Enum| HeadLevel = ==== | Enumname = POLARITY |
Description = Signals polarity enumeration|
Field1 = LOW_INACTIVE |
Field2 = HIGH_INACTIVE |
Field3 = |
Field4 = |
Remarks = |
}}
=== Functions ===
{{APIEx | HeadLevel = ==== | Signature = HANDLE SPIUserOpen() |
Description = Opens an instance of the SPI Bus Driver. |
Return = Returns a handle that should be used to access the driver. Nonzero indicates success. |
Param1 = |
Param2 = |
Param3 = |
Param4 = |
Remarks = }}

{{APIEx | HeadLevel = ==== | Signature = VOID SPIUserClose (HANDLE hDevice) |
Description = Closes the driver handle |
Return = |
Param1 = *hDevice - Handle to an open SPI bus instance|
Param2 = |
Param3 = |
Param4 = |
Remarks = }}

{{APIEx | HeadLevel = ==== | Signature = BOOL SPIUserSetConfiguration(HANDLE hDevice, [[#SPI_SLAVE_CONFIG|SPI_SLAVE_CONFIG]]* Settings) |
Description = Registers the configuration of the device.|
Return = TRUE - indicates success.|
Param1 = *hDevice - Handle to an open SPI bus instance|
Param2 = *Settings - The SPI device configuration|
Param3 = |
Param4 = |
Remarks = The device specific configuration is passed to the SPI controller immediately before the transaction starts. The driver keeps the configuration between calls to this function or until the SPI bus handle is closed}}

{{APIEx | HeadLevel = ==== | Signature = BOOL SPIUserTransact (HANDLE hDevice, [[#SPITRANS|SPITRANS]]* pTrans) |
Description = Submits SPI data transaction to the target device |
Return = TRUE - indicates success.|
Param1 = *hDevice - Handle to an open SPI bus instance|
Param2 = *pTrans - pointer to data structures containing data buffers for the transaction
|
Param3 = |
Param4 = |
Remarks = The SPI transaction data buffers must be allocated and released by the user
}}

[[Category:Windows CE|SPI Sample ]]
[[Category:CM-X300|WinCE: SPI Sample ]]

Template:APIEx

2010-03-11T14:43:54Z

Shai:

__NOEDITSECTION__
{{{HeadLevel}}} {{{Signature}}} {{{HeadLevel}}}
{{{Description}}}
{{#if: {{{Param1}}} |
={{{HeadLevel}}} Parameters {{{HeadLevel}}}=
:{{{Param1}}}
:{{{Param2}}}
:{{{Param3}}}
:{{{Param4}}} |
}}
{{#if: {{{Return}}} |
={{{HeadLevel}}} Return Values {{{HeadLevel}}}=
:{{{Return}}}|
}}
{{#if: {{{Remarks}}} |
={{{HeadLevel}}} Remarks {{{HeadLevel}}}=
:{{{Remarks}}} |
}}

Template:!!

2010-03-11T12:14:27Z

Shai: New page: ||

Template:Enum

2010-03-11T08:33:30Z

Shai:

__NOEDITSECTION__
{{{HeadLevel}}} {{{Enumname}}} {{{HeadLevel}}}
{{#if: {{{Description}}} |
{{{Description}}} |
}}
{{#if: {{{Field1}}} |
={{{HeadLevel}}} Values{{{HeadLevel}}}=
:{{{Field1}}}
:{{{Field2}}}
:{{{Field3}}}
:{{{Field4}}} |
}}
{{#if: {{{Remarks}}} |
={{{HeadLevel}}} Remarks {{{HeadLevel}}}=
:{{{Remarks}}} |
}}

CM-X300: WinCE: Getting Started

2010-03-08T10:00:35Z

Shai:

== Preparation steps ==
{{Note|Windows CE may be installed on CM-X300 using either a USB flash drive or a network connection. USB flash drive installation is the preferred method}}
* Obtain a PC workstation with a serial communication port.
* For networked installation, install a TFTP server on the host PC. For Windows machines we recommend using [http://tftpd32.jounin.net/ TFTPD32].
* Download the [http://compulab.co.il/x300/download/release/x300-wince6-img.zip Windows CE Demo package for CM-X300] from CompuLab website. Unzip the package to a directory on the host PC.
* All image files mentioned below can be found in the {{filename|ImageFiles}} folder.
* Copy the contents of folder corresponding to the CM-X300 hardware configuration to a USB flash drive or to the folder exported by the TFTP server.
** CPU stepping is identified according to the CM-X300 part number:
*:- C624 corresponds to PXA300
*:- C624'''M''' corresponds to PXA310

== Image installation ==
{{Warning|Do not reset or power off the CM-X300 during the installation process! Doing so may result in a disabled module! }}
* Connect the host PC to the CM-X300 via the serial cable supplied with the evaluation kit.
* Start a terminal emulation software on the host PC. Refer to [[CM-X300:_WinCE:_Setting_Up_a_Console|Setting up a console]] for settings.
* Turn on the CM-X300 system. The U-Boot (initial boot-loader) will start with a command prompt.
*: {{Note|If the boot settings of the CM-X300 are different from default, press and hold ^C while turning on the CM-X300 in order to get command prompt.}}

=== Installation with a USB flash drive ===
* Ensure that the files {{filename|wince_updater.nb0}}, {{filename|update.img}}, {{filename|nk.bin}}, {{filename|eboot.nb0}} and, optionally, {{filename|script.xml}} are present in the root directory of the USB flash drive.
* Connect the USB flash drive to USB2 (host/slave) port of the CM-X300 platform.
* Use the following U-Boot command to boot the Windows CE installer:
<pre>
> run ce_setup
</pre>
* Continue to [[CM-X300:_WinCE:_Getting_Started#Burning_the_image_to_NAND|Burning the image to NAND]] section

=== Installation with TFTP ===
* Connect CM-X300 Ethernet port to the local Ethernet network
* Ensure that the files {{filename|wince_updater.nb0}}, {{filename|update.img}}, {{filename|nk.bin}}, {{filename|eboot.nb0}} and, optionally, {{filename|script.xml}} are accessible by the TFTP server.
:- TFTPD32 users: copy the files mentioned above to a folder and point the TFTP server to that folder.
* Use U-Boot {{cmd|dhcp}} command to obtain an IP address or manually set the {{parameter|ipaddr}} environment variable:
<pre>
> setenv ipaddr <CM-X300 ip address>
</pre>
* Set the {{parameter|serverip}} environment variable and save the new environment to NAND flash:
<pre>
> setenv serverip <host ip address>
> saveenv
</pre>

* Use the following U-Boot command to boot the Windows CE installer:
<pre>
> tftp 80400000 update.img && autoscr 80400000
</pre>
* Continue to [[CM-X300:_WinCE:_Getting_Started#Burning_the_image_to_NAND|Burning the image to NAND]] section

=== Burning the image to NAND ===
* {{cmd|CM-X300 Updater}} application will be started automatically after Windows CE installer boot is complete. The following screen will be displayed:
*:- [[Image:X300-Updater-start-screen.jpg]]
* The CM-X300 Updater will point to the {{filename|\Hard Disk\NK.bin}} file, located on a USB flash disk.
* Uncheck the {{cmd|Quick Format}} check box to request a full low-level format of the CM-X300 NAND Flash.
*:- A full low level format of the NAND Flash takes several minutes
* Press the {{cmd|Start}} button
* The update process takes several minutes.
{|
|[[Image:X300-updater-Formatting.jpg]]
|[[Image:CM-X300 Updating.jpg]]
|}
* After the update is completed, the CM-X300 Updater will display the following notification.
*:- [[Image:X300-Updater-finished.jpg]]
* Press {{cmd|OK}}.

== Post Installation ==

* Windows CE boots automatically when the CM-X300 is power cycled or reset.
* The following screen appears when the CM-X300 is up and running:
*:- [[Image:CM-X300-Home-Screen.jpg]]

== See also ==

* [[CM-X300: WinCE: Configuring Eboot|Configuring Eboot]]
* [[WinCE: Application Development|Windows CE Application Development for CM-X300 modules]]
* [[CM-X300: WinCE: Demo Image]]
* [[WinCE: OSDesign Development | Windows CE OSDesign Development]]
* [[U-Boot for CM-X300]]

[[Category:Windows CE|Getting Started]]
[[Category:CM-X300|Getting Started]]

CM-X300 WinCE

2010-03-08T10:00:15Z

Shai:

{{summary|
This page contains links to information related to the Windows Embedded CE demo package for the CM-X300

The Windows CE package by Compulab supports a ready to run demo image, an SDK that enables application development, and a BSP that allows you to customize the run-time image
|X300-cm-top-m.jpg|thumb}}
{{Resources_Windows
|* [[CM-X300: WinCE: Getting Started|Getting started]]
* [[CM-X300: WinCE: Demo Image|Using the Demo Image]]
* [[CM-X300: WinCE: Configuring Eboot|Configuring Eboot]]
|* [[WinCE: Application Development|Application Development]]
* [[WinCE: Platform Builder Installation | Platform Builder installation]]
* [[CM-X300: WinCE: OSDesign Configuration|OSDesign Configuration]]
* [[WinCE: OSDesign Development|OSDesign Creation]]
|*[[Support]]
* [[CM-X300: WinCE: Known Issues|Known Issues]]
}}
__NOTOC__
{{ChangelogRss| content=
===== 22-Nov-2009 =====
* Fixed GPIO83 wakeup functionality
* Fixed GPIOExtender interrupt handling bug
* Fixed MAC Address not loaded from UBoot bug
* Fixed MPEG4 playback issue
* Added Eboot configuration through the image updater’s script mode
* Added a Control Panel Applet to choose USB functionality for PXA310
* Added a service that simulates user activity on resume to fix hang on resume bug
* Added automatic detection of revision number (for revision 1.3 and above)
* Added a “Run Once”-like mechanism on first boot
* Added a Silverlight Demo Application
* Generated a new SDK that supports Silverlight for embedded devices
* This release was built using Windows CE 6.0 R3 and has the following items:
:- Silverlight for Embedded devices
:- Adobe Flash Lite ActiveX control for Internet Explorer
:- Gestures support
===== 22-Sep-2009 =====
* Added Bluetooth functionality support for PXA310
* Fixed Green LED functionality in Suspend mode
===== 08-Sep-2009 =====
* In this release only changes relevant to PXA310 were made. No changes were made to the PXA300 image.
* Updated Uboot script to operate properly with PXA310
* Added USB device support for PXA310
* Added Eboot option to clean registry
* Added Eboot option to choose USB functionality
* Added an optional application to activate Wi-Fi power save mode
* Fixed backlight behavior after Suspend
===== 14-Aug-2009 =====
* Corrected static libraries use
* Added support for PXA310 (separate image)
* Added control of Touch sensitivity through the registry
* Added CAB file for Video Acceleration support
* Added a C# demo application
===== 1-Jul-2009 =====
* Fixed minor bugs in LCDAdapt utility
* Fixed device power consumption in Sleep mode
* Fixed COM C and COM D functionality
* Fixed audio recording bug
* Added backlight driver
* Added SPI driver (for HW rev 1.2 and above)
* Added catalog item to the updater to support access to computers on a network
* Added a Battery driver
* Added GPIO as wakeup source from suspend mode
* Added preliminary support for QCI (Video Input)
===== 2-Apr-2009 =====
* Added support for the Hynix 128 MB NAND flash
* Added support for DRAM size detection
* Fixed the functionality of RTC for HW revision 1.2
* Fixed the suspend/resume functionality for Wi-Fi
* Added a FailSafe mechanism to the image updater
* Added script mode support to the image updater
* Fixed the loading of the MAC address from U-BOOT
* Added a CF 3.5 catalog item
* Added a CAB installer catalog item
* Added touch screen support to the updater image
* Changed relocation table handling
* Added a U-BOOT script to set all environment variables
* Added an LCD Adaptation utility
===== 24-Sep-2008 =====
* Added Touch screen functionality
* Ethernet controller retrieves configuration from Eboot
* Added KeyPad support
* Fixed USB 2.0 Slave Suspend/Resume functionality
* Added LED functionality
* Wi-Fi and Bluetooth can be configured through Eboot
* Fixed Wireless Config applet to indicate devices’ true states
* Added Keypad configuration applet
* Fixed audio to play stereo
* Added relocation table creation to Eboot
* Added desktop side driver INF for ActiveSync by Marvell
* Added the following SubProjects:
:- A2dpMgr
:- TCPMP
:- RegEdit
:- AutoLaunch
:- TaskManager
:- LookAndFeel
:- KeypadAppLaunch
===== 28-Aug-2009 =====
* Initial Release of Windows CE package
}}

[[Category:Windows CE]]
[[Category:CM-X300]]

File:X300-Updater-start-screen.jpg

2010-02-25T15:16:36Z

Shai: uploaded a new version of "Image:X300-Updater-start-screen.jpg"

Importing image file

File:X300-Updater-finished.jpg

2010-02-25T15:14:54Z

Shai: uploaded a new version of "Image:X300-Updater-finished.jpg"

Importing image file

File:CM-X300 Updating.jpg

2010-02-25T15:14:23Z

Shai: uploaded a new version of "Image:CM-X300 Updating.jpg"

Importing image file

File:X300-updater-Formatting.jpg

2010-02-25T15:13:29Z

Shai: uploaded a new version of "Image:X300-updater-Formatting.jpg"

Importing image file

CM-X300: WinCE: Known Issues

2010-02-03T12:08:48Z

Shai:

The following list is the known issues for the latest CM-X300 software package:
{{IssueCategory|Graphics|
* After using the overlay, there are visible artifacts when redrawing menu items and icons
* After installing the CAB file with the Codecs it is no longer possible to play MPEG1 movies
* There is no audio filter for MPEG2. This means that MPEG2 playback is done without audio
* There is a memory leak problem when using Marvell's codecs. The memory leaks appear when you destroy and recreate the graphs
}}

{{IssueCategory|Wireless|
* Wifi and Bluetooth need to be both disabled or both enabled
}}

{{IssueCategory|Peripherals|
* CM-X300 rev 1.3 in conjunction with SB-X300 rev 1.1 does not have SD card detect and card protect
}}

[[Category:Windows CE|Known Issues]]
[[Category:CM-X300|Known Issues]]

Template:WindowsCEVer

2010-01-03T08:59:36Z

Shai: New page: Windows Embedded CE 6.0 R3

Windows Embedded CE 6.0 R3

Template:API

2009-12-23T11:42:25Z

Shai:

__NOEDITSECTION__
=== {{{Signature}}} ===
{{{Description}}}
{{#if: {{{Param1}}} |
==== Parameters ====
:{{{Param1}}}
:{{{Param2}}}
:{{{Param3}}}
:{{{Param4}}} |
}}
{{#if: {{{Return}}} |
==== Return Values ====
:{{{Return}}}|
}}
{{#if: {{{Remarks}}} |
==== Remarks ====
:{{{Remarks}}} |
}}

Template:ModuleSummary

2009-12-23T11:34:35Z

Shai:

{| align="center" style="border: 1px solid #aaaaaa; margin-top: 20px;" width="100%"
| colspan=3 align="center" style="line-height: 120%; border-bottom: 1px solid #aaaaaa; font-size: 115%; background-color: #eeeeee;" {{!}} Place holder so this cell will have volume
|
|-
| valign="top" | {{{ModuleDesc}}}
| rowspan=2 align="center" valign="top" style="border-left: 0px solid #aaaaaa;" | {{{ModulePic}}}
| width="30%" |
|-
| style="border-top: 0px solid #aaaaaa; font-size: 80%; background: #ffffff" | You can use the Rss Feed link to monitor the News. The link is located in the Toolbox on the left
|
|
|}

Category:CM-IGLX

2009-12-15T14:47:46Z

Shai:

CM-iGLX module related pages

CM-iGLX Linux

2009-12-15T14:46:31Z

Shai:

{{summary|
This page contains links to information about Linux kernels, packages and software development for CM-iGLX modules.
* [[Getting started with Linux on CM-iGLX]]
* [[Gentoo Linux for CM-iGLX]]
* [[CM-iGLX Video Input Port]]
|Iglx-cm-top-m.jpg}}

{{changelog|
* '''3-Nov-2008'''
: Linux kernel updated to 2.6.24
: Added support for GeodeLX video input port
: All Gentoo packages updated to recent versions

* '''8-Jan-2008'''
: Added wireless support (Ralink RT73 chipset)
: Added support for custom resolution displays
: All Gentoo packages updated to recent versions

* '''28-May-2007'''
: Added drivers for UCB1400 touchscreen controller
: Changed default audio mixer settings
: Ethernet interface renaming is removed from udev rules
: Fixed library paths

* '''01-Apr-2007'''
: Initial release of Gentoo for CM-iGLX
}}

[[Category:Linux]]
[[Category:CM-IGLX]]

Compulab Technical Support

2009-12-15T14:39:29Z

Shai:

Compulab provides support for its products through the [http://compulab.co.il/supportdb/ online support system].
Please refer to the [http://www.compulab.co.il/supportdb-help/ SupportDB help] page for information about the system and its use.

Please use the following template when you open an issue:
# State the release date you are using
# Does the problem happen on compulab's eval board?
# What is the symptom (upload a log file)
# What are you expecting
# Steps to reproduce
# Additional relevant information

Providing all the above information will enable us to provide faster and more accurate support.

=== Issue report example ===
I am using the Windows CE package for CM-X300 released on 13/4/2014, and downloaded from [http://www.anotherinvalidplace.nul| www.anotherinvalidplace.nul]. 
The following happens on Compulab's eval board (CM+SB): 
RTC fails to save the time. 
I expect the date and time to persist when doing a software reboot.
 ''To reproduce'':
* turn the module on
* Set the time and date
* Reboot the module using Software reboot
* Check the time
''Additional info'':
* Doing the same experiment with a GPIO reset succeeds.
* The device is powered by the battery when doing this.
* Plugging the device to the power supply resolves this.
 
The log file is attached 
Thanks, 
Someone

[[Category:Windows CE]]
[[Category:Linux]]

Category:Windows CE

2009-12-15T14:34:41Z

Shai: New page: Windows CE related pages

Windows CE related pages

Category:U-Boot

2009-12-15T14:34:29Z

Shai: New page: U-Boot related pages

U-Boot related pages

Category:SBC-FITPC2

2009-12-15T14:34:15Z

Shai:

SBC-FITPC2 related pages

Category:EXEDA

2009-12-15T14:33:50Z

Shai: New page: Exeda device related pages

Exeda device related pages

Category:EM-X270

2009-12-15T14:33:27Z

Shai: New page: EM-X270 module related pages

EM-X270 module related pages

Category:CM-X300

2009-12-15T14:33:13Z

Shai: New page: CM-X300 module related pages

CM-X300 module related pages

Category:CM-X270

2009-12-15T14:32:57Z

Shai: New page: CM-X270 module related pages

CM-X270 module related pages

Category:CM-T35

2009-12-15T14:32:46Z

Shai: New page: CM-T35 module related pages

CM-T35 module related pages

Category:CM-IAM

2009-12-15T14:31:18Z

Shai: New page: CM-IAM module related pages

CM-IAM module related pages

CM-iAM Linux

2009-12-15T14:27:46Z

Shai:

{{summary|
This page contains links to information about the Linux kernel, packages and software development for CM-iAM modules.

CompuLab Linux support for the CM-iAM includes modifications of [[Linux Kernel for CM-iAM|Linux kernel]] and [[Ubuntu Linux for CM-iAM|example file system image]] based on Ubuntu Linux. It is possible to use other Linux distributions and environments.

* [[Getting started with Linux on CM-iAM]]
* [[Linux Kernel for CM-iAM]]
* [[Ubuntu Linux for CM-iAM]]
|cm-iam-top.jpg|thumb}}

{{Changelog|
* '''29-Oct-2009'''
: Initial release of Linux for CM-iAM
}}

[[Category:Linux]]
[[Category:CM-IAM]]

SBC-FITPC2 Linux

2009-12-15T14:26:45Z

Shai:

{{summary|
This page contains links to information about Linux kernel, packages and software development for SBC-FITPC2 modules.

CompuLab Linux support for SBC-FITPC2 includes modifications of [[Linux Kernel for SBC-FITPC2|Linux kernel]]. It should be possible to use any Linux distribution with SBC-FITPC2, although certain features may require custom kernel configuration.

* [[Linux Kernel for SBC-FITPC2]]
* [[Ubuntu 8.04 LTS on SBC-FITPC2]]
|Fitpc2-sb-top-ss.jpg|thumb}}

{{Changelog|
* '''30-Aug-2009'''
: Initial release of Linux on SBC-FITPC2 documentation
}}

[[Category:Linux]]
[[Category:SBC-FITPC2]]

Exeda Android

2009-12-15T14:24:24Z

Shai:

== Introduction ==
Android is a set of software for mobile devices, developed by Open Handset Alliance. The [http://www.compulab.co.il/exeda/download/exeda-android.zip CompuLab Android package for Exeda] includes NAND flash image, Linux kernel configuration and source code patches, and patches and configuration files used to build the Android image.

{{Important|The CompuLab Android package for the Exeda is based on Android 1.0 and it is provided "as-is", without maintenance or technical support}}

== Package contents ==
=== images ===
* {{filename|android.jffs2}} - ready to run image for Exeda NAND flash
* {{filename|android.tar.bz2}} - archive of root file system used for JFFS2 image creation

=== kernel ===
* {{filename|kernel-2.6.25-exeda.jffs2}} - JFFS2 image of Linux kernel 2.6.25 with Android and Exeda patches
* {{filename|linux-2.6.25-exeda.patch}} - cumulative patch vs. [http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.25.tar.bz2 Linux kernel 2.6.25] including modifications and additions made by the Android team as well as support for the Exeda peripherals
* {{filename|uImage-2.6.25-exeda}} - kernel image that can be used for network boot

=== patches ===
This directory contains a set of patches required to build Android for the Exeda. The patches were generated vs. "android-1.0" release.
There is a patch per Android subproject, each patch named by subproject path inside the Android tree with '''/''' replaced by '''_'''.
For instance the patch for {{filename|packages/apps/Settings}} is named {{filename|packages_apps_Settings.patch}}

The only exception is
* {{filename|exeda_build.tar.bz2}} - additions to Android build system required to build Android for the Exeda

== Image installation ==
{{Important|The CompuLab Android package for the Exeda can be installed only on the devices with option "Y" assembled}}

* Follow the steps in [[Linux_Development_for_XScale_modules#Networked_Root_Filesystem|Networked Root Filesystem Guide]]. The root filesystem for the Exeda can be extracted from {{filename|images/android.tar.bz2}}.
* Disable automatic Android startup for the networked root filesystem:
<pre>
rm /path/to/exeda/root/etc/rc5.d/S99zzzandroid
</pre>
* Make sure to power off the Exeda
* Connect Exeda Ethernet port to your local Ethernet
* Connect your host PC to the Exeda via a null modem cable supplied with the Eval Kit.
* Start terminal emulation software on your PC using the COM port to which the null modem is connected. Set baud rate to 115200 bps, 8 bit per frame, 1 stop bit, no parity, no flow control.
* Power up the Exeda. U-Boot will start and you will get the command prompt in your terminal program.
{{Note|If the boot settings of your Exeda are set to load the operating system, you may need to press and hold ^C while turning the Exeda on, in order to get command prompt.}}
* You can use U-boot {{cmd|dhcp}} command to obtain IP address or manually set {{parameter|ipaddr}} and {{parameter|serverip}} environment variables:
<pre>
> setenv serverip <host ip address>
> setenv ipaddr <Exeda ip address>
> saveenv
</pre>
* Next environment settings are passed to Linux Kernel and are needed for NFS root:
<pre>
> setenv bootargs "root=/dev/nfs nfsroot=<your host ip>:/path/to/rootfs console=ttyS0,115200 ip=dhcp"
</pre>
* Use the following U-boot command to boot Linux on Eexeda:
<pre>
> tftp a0100000 uImage && bootm
</pre>
* After the image is loaded you will get Linux login prompt. Login as {{parameter|root}} with password {{parameter|111111}} into the system.
* Copy the kernel and Android jffs2 images from the Android package to NFS share, so you can access them from Exeda.
* Now you can install kernel and filesystem images to the NAND flash from NFS share using standard Linux MTD utilities ({{cmd|flash_eraseall, nandwrite}}).
* After the installation procces completed successfully, U-Boot on Exeda needs the following environment variables set prior to booting from NAND flash:
<pre>
> setenv boot_mode "android"
> setenv nand_mode "on"
> setenv bootargs "root=/dev/mtdblock1 rootfstype=jffs2 console=ttyS0,115200"
> setenv bootcmd "fsload && bootm"
> saveenv
</pre>
* Now you can reboot the Exeda and it will boot Android from the internal NAND flash.
{{Note|First boot takes relatively much time because the system performs a lot of one-time initialization tasks}}

== Building Android for Exeda ==
=== Linux kernel ===
* Download Linux kernel source from preferred mirror
* Unpack it to some directory
* Apply the Exeda patchset
* Set environment variables ARCH, and CROSS_COMPILE so that kernel build system cross compile the kernel
* Build the kernel

<pre>
mkdir /home/development/exeda/kernel
cd /home/development/exeda/kernel
wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.25.tar.bz2
tar xjf linux-2.6.25.tar.bz2
cd linux-2.6.25
cat /path/to/exeda-android/kernel/linux-2.6.25-exeda.patch | patch -p1
export ARCH=arm
export CROSS_COMPILE=arm-linux-
make exeda_defconfig
make menuconfig
make uImage
</pre>

In the above example, the Linux kernel image ({{filename|1=uImage}}) will be created in {{filename|1=/home/development/exeda/kernel/linux-2.6.25/arch/arm/boot}}

=== Android ===
* Setup Android working environment as described at [http://source.android.com/download Get Source] page of [http://source.android.com/ Android Open Source Project] website
* Unpack {{filename|exeda_build.tar.bz2}} to the Android working directory
* Apply the Exeda patchset
* Select Exeda platform using {{parameter|choosecombo}} command
* Build Android

<pre>
cd ~/mydroid
tar xjf /path/to/exeda-android/pacthes exeda_build.tar.bz2
for file in /path/to/exeda-android/pacthes/*patch; do
prj=`basename $file .patch | sed -e 's|_|/|g'`
cd $prj
cat $file | patch -p1
cd -
done
choosecombo false release exeda
make
</pre>

== Known problems and limitations ==
* Off-line battery charging is not implemented
* Resume from suspended state may fail
* SD card hotplug sometimes fails
* Wifi connection to secure networks sometimes fails

== See also ==
* [http://www.android.com/about/ What is Android?]
* [http://source.android.com/ Android Open Source Project]
* [http://developer.android.com/ Android Developers]
* [[Linux Development for XScale modules]]

[[Category:Linux]]
[[Category:EXEDA]]

Exeda Linux

2009-12-15T14:24:01Z

Shai:

{{summary|
This page contains links to information about Linux kernels, packages and software development for Exeda device.

* [[Exeda Android|Android for Exeda]]
* [[Linux kernel for Exeda]]
* [[Linux Development for XScale modules]]
|exeda.jpg}}

{{changelog|
* '''23-Jun-2009'''
: Initial release of Linux kernel 2.6.30 for Exeda

* '''8-Jun-2009'''
: Initial release of Android 1.0 for Exeda
}}

[[Category:Linux]]
[[Category:EXEDA]]

EM-X270 Linux

2009-12-15T14:23:10Z

Shai:

{{summary|
This page contains links to information about Linux kernels, packages and software development for EM-X270 device.

* [[Getting started with Linux on EM-X270]]
* [[Angstrom Linux for EM-X270]]
* [[Linux Development for XScale modules]]
|X270-em-bot-m.jpg}}

{{changelog|
* '''29-Dec-2008'''
: Linux kernel updates
: - Added support for PXA Quick Capture interface
: - Added support for PXA frame buffer overlay
: - Fixed battery detection
: Angstrom Linux package updates
: - Added camera example application
: - Added U-Boot environment utility
: - Updated image generation utilities

* '''4-Nov-2008'''
: Linux kernel updated to 2.6.26
: Added support for Wi2Wi W2SW0001 wireless LAN (based on Marvell 8686 chipset)

* '''3-Jan-2008'''
: Added Wireless LAN driver
: Added partitions on EM-X270 NOR flash
: Added support for VGA display
: Added support for GPRS data calls
: Fixed updater application to allow proper setup after Windows CE
: Fixed minor bug in charger driver

* '''14-Nov-2007'''
: Initial release of Angstrom Linux for EM-X270

* '''9-Oct-2007
: Basic support for EM-X270 is merged into mainline Linux kernel 2.6.23
}}

[[Category:Linux]]
[[Category:EM-X270]]

CM-X270 Linux

2009-12-15T14:21:52Z

Shai:

{{summary|
This page contains links to information about Linux kernels, packages and software development for CM-X270 modules.

CompuLab Linux support for CM-X270 includes modifications of [[Linux Kernel for CM-X270|Linux kernel]] and [[Debian Linux for CM-X270|example file system image]] based on Debian Linux. It is possible to use other embedded Linux distributions and environments.
The CM-X270 platform is supported by [http://www.pokylinux.org/ Poky Linux] and [http://www.openembedded.org OpenEmbedded], and
[http://mojo.handhelds.org/frisky-armv5el Ubuntu Frisky] should work on CM-X270 but has not been tested yet.

* [[Getting started with Linux on CM-X270]]
* [[Linux Development for XScale modules]]
* [[Linux Kernel for CM-X270]]
* [[Debian Linux for CM-X270]]
* [[Linux MTD drivers on CM-X270]]
* [[SPI support for CM-X270]]
|X270-cm-l-top-m.jpg|thumb}}

{{Changelog|
* '''23-Nov-2008'''
: Linux kernel 2.6.24 for CM-X270 updates
: - Added Marvell proprietary driver for wireless LAN chip
: - Fixed memory leak in libertas_spi
: - Fixed leds default state

* '''26-Jun-2008'''
: Released Linux kernel 2.6.24 for CM-X270
: Updated Debian filesystem image:
: - Upgrade to Debian Etch
: - Added udev
: - Added Bluetooth utilities
: - Added APM utilities

* '''18-May-2008'''
: Preliminary release of [[Linux Kernel for CM-X270#Linux kernel 2.6.24|Linux kernel 2.6.24 for CM-X270]] is available ([http://www.compulab.co.il/mediawiki/files/Linux/x270cm/linux-2.6.24-cm-x270.tar.gz source code only]).

* '''24-Jan-2008'''
: CM-X270 platform support is merged into mainline Linux kernel 2.6.24

* '''26-Dec-2007'''
: Certain NAND flashes are sensitive to local bus activity. NAND flash driver updated to overcome this limitation.

* '''13-Jun-2007'''
: Fixed RTC access routines.

* '''6-Feb-2007'''
: Added pcibios_set_master for ARM platforms with ITE8152 bridge. This allows proper setting of latency timer for PCI bus masters behind the bridge.

* '''5-Feb-2007'''
: Make default Debian file system image 512 Mbytes

* '''12-Oct-06'''
: Added ability to specify wireless access point MAC address
: Added MMC support
: Serial tty assignment made compatible for CM-X270L and CM-X270W. From now, ttySA0 is default console on both CM-X270L and CM-X270W.
: Fixed wireless LAN driver bug that caused incorrect transmission power setting

* '''15-Aug-06'''
: Added BGW200 Wireless LAN support for CM-X270L

* '''15-May-06'''
: Initial release of Linux 2.6.16:
: - Power management support
: - Added CardBus support
: - Added 2700G frame buffer device driver
: - Audio support upgraded to work with ALSA, added recording support
}}

[[Category:Linux]]
[[Category:CM-X270]]

U-Boot for Exeda

2009-12-15T14:18:47Z

Shai:

== Overview ==
The Exeda uses the U-Boot boot-loader for low-level initialization and operating system loading.
U-Boot is an open source boot-loader available for a wide range of embedded processor architectures.
This page summarizes settings and features unique to the Exeda port of U-Boot. Comprehensive documentation of the U-Boot project may be found at http://www.denx.de/wiki/view/DULG/UBoot.
The CompuLab U-Boot version for the Exeda is checked out from '''U-Boot-1_2_0''' of [http://git.denx.de/?p=u-boot.git;a=summary Das U-Boot repository] and can be obtained from [http://www.compulab.co.il/exeda/html/exeda-developer.py CompuLab website] in binary form.
CompuLab U-Boot source will be provided on request.

== Exeda specific U-Boot commands ==
A brief U-Boot command reference can be found [[U-Boot quick reference|here]].
The following commands are specific to the Exeda port of U-Boot:

* CPU frequency scaling
*: {{cmd|cpufreq}} with no arguments - display the current frequency setting
*: {{cmd|cpufreq <frequency>}} - set CPU frequency; (allowed frequency values : 104/208/312/520)
* Hardware configuration information *
*: {{cmd|hwinfo}} - print device hardware configuration information

== Default Environment ==

U-Boot features an extensive default environment, for boot sequence control and hardware configuration.

{| cellpadding="3" border="1" style="border: 1px solid rgb(85, 85, 85); border-collapse: collapse;"
! Variable
! Default setting
! Description
|-
| bootcmd
|
| This variable defines a command string that is automatically executed when the initial countdown is not interrupted.
|-
| bootdelay
| 3 sec
| Delay before automatic boot starts
|-
| boot_mode
| uboot
| Boot option setting. See [[#section 5]] for details.
|-
| bootargs
|
| The contents of this variable are passed to the Linux kernel as boot arguments
|-
| stdin
| serial
| Standard input stream
|-
| stdout
| serial
| Standard output stream
|-
| stderr
| serial
| Standard error stream
|-
| baudrate
| 115200
| Serial port baud rate
|-
| ethaddr
| set at production time
| Ethernet MAC address for the extender board ethernet interface
|-
| ipaddr
| -
| IP address; needed for tftp command
|-
| serverip
| -
| Server address; needed for tftp command
|-
| autoload
| no
| Determines whether the "dhcp", "bootp" and "rarpb" commands will automatically download an image.
|-
| splashimage
| 0x000B0000
| Address of a bitmap image used as splash-screen.
|-
| usb_mode
| slave
| USB port operation mode. The only values allowed are: "slave" or "host". Must be set before "usb start" command is issued.
|-
| extpwr_mode
| on
| Determines whether the external power enable (GPIO<97>) is asserted.
|-
| cpu_freq
| maximum supported by CPU
| CPU frequency. Used by "cpufreq" command to store the frequency setting.
|-
| mem_zero
| on
| Determines whether memory zeroing is performed. Allowed values: "on", "off".
Set to "off" for shorter boot time.
|}

== Boot Sequence Options ==

=== Boot Options ===
The U-Boot boot-loader supports several basic boot options.
The environment variable "boot_mode" determines which boot sequence is executed.
The variable may be set to the following values:

* {{parameter|uboot}} - the Exeda boots up to the U-boot command prompt.
* {{parameter|linux}} - the default Linux boot from NAND sequence is executed. Please see Linux documentation for details.
* {{parameter|wince}} - the default WinCE boot from NAND sequence is executed. Please see WinCE documentation for details.
* {{parameter|any other value}} - the command stored in the {{parameter|bootcmd}} variable is executed.

=== Bringing to Default State ===
Pressing and holding {{parameter|Ctrl D}} during the boot process will restore the U-Boot settings to the default factory values. Use this if the environment has been corrupted.

=== O/S Update Boot Sequence ===
Pressing the {{parameter|ON/OFF}} button for more than four seconds during the boot process will put the system into the O/S update boot sequence. The boot-loader will attempt to detect an external storage device (USB or MMC) and search for updated image files. If no files are detected, the system will boot up to the U-Boot command prompt. This boot mode allows easy and fast software updates without connecting a PC host.
Please refer to O/S manuals for specific update procedures.

=== NAND Flash System ===
The Exeda port of U-Boot supports the MTD flash driver that is used with the Linux O/S.
U-Boot will load the appropriate driver according to the {{parameter|boot_mode}} environment variable. Additionally, the {{parameter|nand_mode}} environment variable may be used to set the NAND driver mode explicitly. Setting {{parameter|nand_mode}} to {{parameter|on}} will cause U-Boot to load the MTD driver. If {{parameter|nand_mode}} is set to {{parameter|off}} the MTD driver will not be loaded. See WinCE documentation for further details.

== Updating U-Boot ==

{{Warning| Do not interrupt the process or shut down the system during update. Doing so can result in a disabled Exeda device that will need to be shipped to CompuLab for reprogramming}}

=== Update through serial port (preferred method) ===

* Start terminal emulation program on your PC using the serial port to which the supplied serial cable is connected. Set baud rate to 115200 bps, 8 bit per frame, 1 stop bit, no parity, no flow control.
* Turn on the Exeda. U-Boot will start and you will get a command prompt.
* Use the {{cmd|loadb}} command to start image download
<pre>
U-Boot> loadb a0010000
</pre>
* In a terminal emulation program, send the U-Boot image file using kermit mode. For example, in HyperTerminal, use {{cmd|"Transfer >> Send File"}}. A {{parameter|"Send File"}} dialog will appear. In the protocol combo box, choose Kermit. Fill in the U-Boot image filename and press the {{parameter|"Send"}} button.
*: [[Image:Hyperterm_kermit_send.png]]
* Use the following commands to store the downloaded image into the Exeda NOR flash:
<pre>
U-Boot> protect off 0 +50000
U-Boot> erase 0 +50000
U-Boot> cp.b a0010000 0 50000
</pre>
* Reboot the Exeda.

=== Update through USB and Disk-on-Key ===
A USB flash drive is needed for this procedure.
* On the host PC, copy the {{filename|u-boot-x.x.x.bin}} file to the USB flash drive. Rename the file {{filename|u-boot.bin}}.
* Connect the USB flash drive to the Exeda OTG USB port using the supplied "USB-A receptacle to Mini-USB A male" cable.
* Start a terminal emulation program on your PC using the serial port to which the supplied serial cable is connected. Set baud rate to 115200 bps, 8 bit per frame, 1 stop bit, no parity, no flow control.
* Turn on the Exeda. U-Boot will start and you will get a command prompt.
* Enable the U-Boot USB host subsystem:
<pre>
U-Boot> setenv usb_mode host
U-Boot> usb start
</pre>
* After U-Boot has detected the USB storage device copy U-Boot image to the Exeda RAM:
<pre>
U-Boot> fatload usb 0 a0010000 u-boot.bin
</pre>
* Use the following commands to store the U-Boot image into the Exeda NOR flash:
<pre>
U-Boot> protect off 0 +50000
U-Boot> erase 0 +50000
U-Boot> cp.b a0010000 0 50000
</pre>
* Reboot the Exeda.

=== Update through LAN / TFTP ===
The Ethernet extender board ("Y" option) is needed for this procedure.
* Install TFTP service (or server) on the host PC. The TFTP server tested by Compulab is TFTPD32, http://tftpd32.jounin.net, it is also included in the Linux and WinCE distribution packages.
* Rename the {{filename|u-boot-x.x.x.bin}} file to {{filename|u-boot.bin}} and copy it to the TFTP directory.
* Start a terminal emulation program on your PC using the serial port to which the supplied serial cable is connected. Set baud rate to 115200 bps, 8 bit per frame, 1 stop bit, no parity, no flow control.
* Turn on the Exeda. U-Boot will start and you will get a command prompt.
* Type {{cmd|printenv}} in order to check the current IP settings. Modify them if needed using the {{cmd|setenv ipaddr}} and {{cmd|setenv serverip}} commands. Or, use U-Boot's DHCP capability to automatically set the IP address.
* Download U-Boot image to the Exeda RAM:
<pre>
U-Boot> tftp a0010000 u-boot.bin
</pre>
* Use the following commands to store the downloaded image into the Exeda NOR flash:
<pre>
U-Boot> protect off 0 +50000
U-Boot> erase 0 +50000
U-Boot> cp.b a0010000 0 50000
</pre>
* Reboot the Exeda.

== Memory Map ==
=== NOR Flash ===

{{Important|The NOR flash memory is used to store the U-Boot image, the U-Boot environment and Exeda setup data for wireless interfaces. Corruption of this data can result in a disabled Exeda device that will need to be shipped to CompuLab for reprogramming.}}

{| cellpadding="3" border="1" style="border: 1px solid rgb(85, 85, 85); border-collapse: collapse;"
! Memory Address range
! Block Range
! Size
! Usage
|-
| 0x00000000 - 0x0004FFFF
| 1 - 5
| 320KB
| U-Boot bootloader
|-
| 0x00050000 - 0x0005FFFF
| 6
| 64KB
| U-Boot environment
|-
| 0x00060000 - 0x0006FFFF
| 7
| 64KB
| Setup block
|-
| 0x00070000 - 0x000AFFFF
| 8 - 11
| 256KB
| Utilities and applications
|-
| 0x000B0000 - 0x000FFFFF
| 12 - 16
| 320KB
| Splash-screen
|}

=== SDRAM Memory ===

SDRAM map: SDRAM starts at 0xA0000000; maximum is 0xA8000000 (128MB).

U-Boot system: 0xA7800000 ...... SDRAM top

U-Boot operates with a virtual memory subsystem turned on, using one-to-one virtual to physical address mapping.

== See also ==
* [[U-Boot quick reference]]
* [[U-Boot images]]
* [http://www.denx.de/wiki/U-Boot/Documentation U-Boot documentation]
* [[Exeda Linux]]

[[Category:U-Boot]]
[[Category:EXEDA]]

Template:IssueCategory

2009-12-15T13:12:46Z

Shai: New page: {{{!}} style="border: 1px solid #aaaaaa; margin-top: 20px;" width="100% }}" {{!}} style="line-height: 120%; border-bottom: 1px solid #aaaaaa; font-size: 105%; background-color: #eeeeee;" ...

{{{!}} style="border: 1px solid #aaaaaa; margin-top: 20px;" width="100% }}"
{{!}} style="line-height: 120%; border-bottom: 1px solid #aaaaaa; font-size: 105%; background-color: #eeeeee;" {{!}} '''{{{1}}}'''
{{!}}-
{{!}} style="padding-top: 10px" {{!}} {{{2}}}
{{!}}}

Template:Resources Windows

2009-12-14T15:57:35Z

Shai:

{{Resources
|
[[Image:Installation Icon.png|80x80px|left]]
|{{{1}}}
|[[Image:Development Icon.png|80x80px|left]]
|{{{2}}}
|[[Image:Support Icon.png|80x80px|left]]
|{{{3}}}
}}