Compulab Mediawiki - User contributions [en]

CM-QS600: Linux: Getting started

2014-08-06T14:02:40Z

Mike:

= Preparation steps =
* Obtain a Linux PC workstation (host).
* Make sure a {{parameter|fastboot}} utility is installed on the host machine. For more details about the {{parameter|fastboot}} utility refer to [[CM-QS600: Linux: Kernel#Getting_Fastboot|Getting Fastboot]] section of the [[CM-QS600: Linux: Kernel]] article.
* Get a USB Card reader and a micro SD Card. Use either the micro SD card, supplied with the CM-QS600 Evaluation kit, or obtain a new one.
* Plug the USB SD Card reader to a host Linux PC. Insert the micro SD Card into the USB Card reader. From now we assume the device name of the micro SD card on your Linux PC is {{filename|/dev/sdq}}.
* Download the [http://compulab.co.il/products/computer-on-modules/cm-qs600/#devres Linux package for CM-QS600] from Compulab website. Unzip the package to a directory on your host workstation.
* All image files mentioned below can be found in {{filename|images}} subdirectory of the Demo package.

= Preparing micro SD card =
* Create GPT partition table and create one Linux filesystem (ext4) partition on it.
<pre>
Disk /dev/sdq: 3854336 sectors, 1.8 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 28631117-2266-4EE4-AD25-58BF5B06223B
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 3854302
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)

Number Start (sector) End (sector) Size Code Name
1 2048 3854302 1.8 GiB 8300 Linux filesystem
</pre>

The example below shows how to create the GPT table and the ext4 filesystem using {{parameter|gdisk}} and {{parameter|mkfs.ext4}} utilities respectively.
Alternatively, you can use {{parameter|gparted}} to create the GPT table and the ext4 partition.

* Create GPT partition table:
<pre>
echo -e "o\ny\nn\n\n\n8300\nw\ny\neof\n" | sudo gdisk /dev/sdq
</pre>
* Format ext4 partition:
<pre>
sudo mkfs.ext4 -L rootfs /dev/sdq1
</pre>
* Mount the partition under {{filename|/media/boot}} location:
<pre>
sudo mkdir -p /media/rootfs
sudo mount /dev/sdq1 /media/rootfs
</pre>

= Installing Linux root filesystem =
* Extract the Linux root filesystem on to the micro SD card:
<pre>
sudo tar --numeric-owner -xjpf /path/to/cm-qs600-linux/images/debian-image.tar.bz2 -C /media/rootfs && sync
</pre>
* Unmount micro SD card:
<pre>
sudo umount /dev/sdq1
</pre>
* Remove the micro SD card from the SD card reader and insert it into the SB-QS600 micro SD card socket (P5).
* Continue to the [[#Installing Kernel | Installing Kernel]] section.

= Installing Kernel =
* Connect the host PC to the SB-QS600 base-board micro USB port (P7) via the USB to micro USB cable supplied with the evaluation kit.
* Connect the host PC to the SB-QS600 base-board mini USB port (P16) via the USB to mini USB cable supplied with the evaluation kit.
* Make sure the new {{filename|/dev/ttyUSBx}} device file is created by using the {{cmd|ls /dev/ttyUSB*}} command. {{parameter|x}} is the last number of the ttyUSB device.
* Start the terminal emulation software on your PC's {{filename|/dev/ttyUSBx}}. Set baud rate to 115200 bps, 8 bit per frame, 1 stop bit, no parity, no flow control.
* Turn on the CM-QS600 evaluation system. The application boot-loader (LK) will start and you will get a command prompt.
* Run the following fastboot command on the host machine:
<pre>
fastboot flash boot /path/to/cm-qs600-linux/images/boot.img
</pre>
* Continue with the boot process:
<pre>
fastboot continue
</pre>
* Alternatively, power cycle the CM-QS600 evaluation system or run the following fastboot command on the host machine:
<pre>
fastboot reboot
</pre>

= See also =

* [[CM-QS600: Linux: Debian]]
* [[CM-QS600: Linux: Kernel]]
* [[Linux: Development for ARM modules]]
* [[Linux: Debian: Minimal ARM filesystem]]

[[Category:Linux]]
[[Category:CM-QS600]]

CM-X300 WinCE

2011-03-24T07:58:43Z

Mike:

{{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=
===== 24-Mar-2011 =====
* General notes:
:- Built with QFE up to Feb 2011
:- This release works with Uboot version 6.1 and above
* Bug fixes:
:- Fixed PMIC LDOs functionality
:- Fixed battery charger state machine
:- Fixed Updater bug
:- Fixed Microphone default behavior
:- Fixed Memory mapping layout
:- Fixed codec initialization
:- Fixed RTC initialization procedure when running without backup battery
:- Added support for smaller frame buffer in Debug mode
* Added/Changed features:
:- Added support for SB-X300 rev 1.3
:- Enhanced gpio driver functionality in order to support interaction with managed code applications
:- Added EBoot functionality (silent mode support and SB-X300 revision detection)
:- Reduced power consumption while the deivce is on "suspend" mode
:- Added support for battery supervisor and charger (in SB-X300 1.3)
===== 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]]

Linux documentation

2011-03-23T12:05:01Z

Mike:

{| style="border: 1px solid #aaaaaa; margin-top: 20px;" width="100%" align="center"
|- style="line-height: 120%; border-bottom: 1px solid #aaaaaa; font-size: 105%; background-color: #eeeeee;"
| [[CM-iTC Linux | CM-iTC]]
| [[CM-T3517 Linux | CM-T3517]]
| [[CM-A510 Linux | CM-A510]]
| [[CM-T3530 Linux | CM-T3530]]
| [[CM-X300 Linux | CM-X300]]
|-

| <linkedimage>
wikipage=CM-iTC Linux
tooltip=CM-iTC Linux documentation
img_src=Image:itc-cm-top-m.jpg
img_width=200px
img_alt=CM-iTC Linux
</linkedimage>

| <linkedimage>
wikipage=CM-T3517 Linux
tooltip=CM-T3517 Linux documentation
img_src=Image:cm-t3517.jpg
img_width=200px
img_alt=CM-T3517 Linux
</linkedimage>

| <linkedimage>
wikipage=CM-A510 Linux
tooltip=CM-A510 Linux documentation
img_src=Image:A510_CM_top_hq.JPG
img_width=200px
img_alt=CM-A510 Linux
</linkedimage>

| <linkedimage>
wikipage=CM-T3530 Linux
tooltip=CM-T3530 Linux documentation
img_src=Image:T35_CM_top.JPG
img_width=200px
img_alt=CM-T3530 Linux
</linkedimage>

| <linkedimage>
wikipage=CM-X300 Linux
tooltip=CM-X300 Linux documentation
img_src=Image:X300-cm-top-m.jpg
img_width=200px
img_alt=CM-X300 Linux
</linkedimage>

|-

| colspan="5" |
{| width="100%" align="center"
|- style="line-height: 120%; border-bottom: 1px solid #aaaaaa; font-size: 105%; background-color: #eeeeee;"
| [[CM-iGLX Linux | CM-iGLX]]
| [[SBC-FITPC2 Linux | SBC-FITPC2 ]]
| [[CM-iAM Linux | CM-iAM]]
| [[EM-X270 Linux | EM-X270]]
| [[CM-X270 Linux | CM-X270]]
|-

| <linkedimage>
wikipage=CM-iGLX Linux
tooltip=CM-iGLX Linux documentation
img_src=Image:Iglx-cm-top-m.jpg
img_width=200px
img_alt=CM-iGLX Linux
</linkedimage>

| <linkedimage>
wikipage=SBC-FITPC2 Linux
tooltip=SBC-FITPC2 Linux documentation
img_src=Image:Fitpc2-sb-top-ss.jpg
img_width=200px
img_alt=SBC-FITPC2 Linux
</linkedimage>

| <linkedimage>
wikipage=CM-iAM_Linux
tooltip=CM-iAM Linux documentation
img_src=Image:Cm-iam-top.jpg
img_width=200px
img_alt=CM-iAM Linux
</linkedimage>

| <linkedimage>
wikipage=EM-X270 Linux
tooltip=EM-X270 Linux documentation
img_src=Image:X270-em-bot-m.jpg
img_width=200px
img_alt=EM-X270 Linux
</linkedimage>

| <linkedimage>
wikipage=CM-X270 Linux
tooltip=CM-X270 Linux documentation
img_src=Image:X270-cm-l-top-m.jpg
img_width=200px
img_alt=CM-X270 Linux
</linkedimage>

|}

|-
|}

__NOTOC__

{{ChangelogRss| content=
===== 23-Mar-2011, CM-iTC =====
: Updates for Linux kernel and filesystem image for CM-iTC

===== 28-Feb-2011 =====
: Initial release of Linux for CM-iTC

===== 27-Jan-2011, CM-A510 =====
: Updates for Linux kernel and Debian filesystem image for CM-A510

===== 31-Dec-2010, CM-T3517 =====
: Initial release of Linux kernel and Debian filesystem image for CM-T3517

===== 28-Oct-2010, CM-A510 =====
: Initial release of Linux kernel and Debian filesystem image for CM-A510

===== 17-Aug-2010, CM-T3530 =====
: Updates for Linux kernel and Angstrom filesystem image for CM-T3530

===== 1-Jun-2010, CM-X300 =====
: Upgrade of Debian example fileystsem image for CM-X300

===== 6-May-2010, CM-iAM =====
: Updates for Ubuntu Linux image for CM-iAM

===== 26-Nov-2009, CM-X300 =====
: Updates for Linux kernel and Debian filesystem image for CM-X300

===== 29-Oct-2009, CM-iAM =====
: Initial release of [[CM-iAM Linux | Linux documentation for CM-iAM]]

===== 30-Aug-2009, SBC-FitPC2 =====
: Initial release of [[SBC-FITPC2 Linux |Linux documentation for SBC-FITPC2]]

===== 25-Jun-2009, CM-X300 =====
: Updates for Linux kernel and Debian filesystem image for CM-X300

===== 23-Jun-2009, Exeda =====
: Initial release of Linux kernel 2.6.30 for Exeda

===== 8-Jun-2009, Exeda =====
: Initial release of Android 1.0 for Exeda

===== 27-May-2009, CM-X300 =====
: Added [[U-Boot for CM-X300]] documentation

===== 29-Dec-2008, EM-X270 =====
: Updates and fixes for Angstrom Linux for EM-X270

===== 23-Nov-2008, CM-X270 =====
: Updates and fixes for Linux kernel 2.6.24

===== 3-Nov-2008, CM-iGLX =====
: Linux kernel updated to 2.6.24
: Added support for GeodeLX video input port
: All Gentoo packages updated to recent versions

===== 19-Aug-2008, CM-X300 =====
: Initial release of Linux package for CM-X300

===== 26-Jun-2008, CM-X270 =====
: Released Linux kernel 2.6.24 for CM-X270
: Updated Debian filesystem image

===== 18-May-2008, CM-X270 =====
: 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]).

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

===== 3-Jan-2008, EM-X270 =====
: 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

===== 26-Dec-2007, CM-X270 =====
: Certain NAND flashes are sensitive to local bus activity. NAND flash driver updated to overcome this limitation.

===== 14-Nov-2007, EM-X270 =====
: Initial release

===== 13-Jun-2007, CM-X270 =====
: Fixed RTC access routines.

===== 28-May-2007, CM-iGLX =====
: 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, CM-iGLX =====
: Initial release of Gentoo for CM-iGLX

===== 6-Feb-2007, CM-X270 =====
: 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, CM-X270 =====
: Make default Debian file system image 512 Mbytes

===== 12-Oct-06, CM-X270 =====
: 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, CM-X270 =====
: Added BGW200 Wireless LAN support for CM-X270L

===== 15-May-06, CM-X270 =====
: 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]]

CM-iTC: Linux: Kernel

2011-02-28T11:33:11Z

Mike: /* See also */

== Overview ==
The CM-iTC is a fully-compatible x86 PC. Recent Linux kernels support most CM-iTC hardware features. CompuLab provides [http://compulab.co.il/workspace/sw/itc/maverick/source/linux_2.6.38.orig.tar.gz 2.6.38] kernel and customized [http://compulab.co.il/workspace/sw/itc/maverick/source/linux_2.6.38-34.1.diff.gz patch] to it. The configuration file is {{filename|debian/config/i386/config.itc}} in the kernel sources tree.

The most significant features of interest to kernel developers are described below.

== CAN Bus ==
.config - Linux/i386 2.6.38-34-itc Kernel Configuration
────────────────────────────────────────────────────────────────────────────────────────
┌─────────────────────────────── CAN Device Drivers ────────────────────────────────┐
│ Arrow keys navigate the menu. <Enter> selects submenus --->. Highlighted │
│ letters are hotkeys. Pressing <Y> includes, <N> excludes, <M> modularizes │
│ features. Press <Esc><Esc> to exit, <?> for Help, </> for Search. Legend: [*] │
│ built-in [ ] excluded <M> module < > module capable │
│ ┌───────────────────────────────────────────────────────────────────────────────┐ │
│ │ < > Virtual Local CAN Interface (vcan) │ │
│ │ < > Serial / USB serial CAN Adaptors (slcan) │ │
│ │ <M> Platform CAN drivers with Netlink support │ │
│ │ [*] CAN bit-timing calculation │ │
│ │ < > Microchip MCP251x SPI CAN controllers │ │
│ │ <M> PCH CAN │ │
│ │ < > Philips/NXP SJA1000 devices ---> │ │
│ │ CAN USB interfaces ---> │ │
│ │ [ ] CAN devices debugging messages │ │
│ │ │ │
│ └───────────────────────────────────────────────────────────────────────────────┘ │
├───────────────────────────────────────────────────────────────────────────────────┤
│ <Select> < Exit > < Help > │
└───────────────────────────────────────────────────────────────────────────────────┘

== Network device ==
.config - Linux/i386 2.6.38-34-itc Kernel Configuration
────────────────────────────────────────────────────────────────────────────────────────
┌────────────────────────────── Ethernet (1000 Mbit) ───────────────────────────────┐
│ Arrow keys navigate the menu. <Enter> selects submenus --->. Highlighted │
│ letters are hotkeys. Pressing <Y> includes, <N> excludes, <M> modularizes │
│ features. Press <Esc><Esc> to exit, <?> for Help, </> for Search. Legend: [*] │
│ built-in [ ] excluded <M> module < > module capable │
│ ┌────^(-)───────────────────────────────────────────────────────────────────────┐ │
│ │ < > IP1000 Gigabit Ethernet support │ │
│ │ < > Intel(R) 82575/82576 PCI-Express Gigabit Ethernet support │ │
│ │ < > Intel(R) 82576 Virtual Function Ethernet support │ │
│ │ < > National Semiconductor DP83820 support │ │
│ │ < > Packet Engines Hamachi GNIC-II support │ │
│ │ < > Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL) │ │
│ │ <M> Realtek 8169 gigabit ethernet support │ │
│ │ [*] VLAN support │ │
│ │ < > SiS190/SiS191 gigabit ethernet support │ │
│ │ < > New SysKonnect GigaEthernet support │ │
│ └────v(+)───────────────────────────────────────────────────────────────────────┘ │
├───────────────────────────────────────────────────────────────────────────────────┤
│ <Select> < Exit > < Help > │
└───────────────────────────────────────────────────────────────────────────────────┘

.config - Linux/i386 2.6.38-34-itc Kernel Configuration
────────────────────────────────────────────────────────────────────────────────────────
┌────────────────────── PHY Device support and infrastructure ──────────────────────┐
│ Arrow keys navigate the menu. <Enter> selects submenus --->. Highlighted │
│ letters are hotkeys. Pressing <Y> includes, <N> excludes, <M> modularizes │
│ features. Press <Esc><Esc> to exit, <?> for Help, </> for Search. Legend: [*] │
│ built-in [ ] excluded <M> module < > module capable │
│ ┌────^(-)───────────────────────────────────────────────────────────────────────┐ │
│ │ < > Drivers for SMSC PHYs │ │
│ │ < > Drivers for Broadcom PHYs │ │
│ │ < > Drivers for Broadcom 63xx SOCs internal PHY │ │
│ │ < > Drivers for ICPlus PHYs │ │
│ │ <M> Drivers for Realtek PHYs │ │
│ │ < > Drivers for National Semiconductor PHYs │ │
│ │ < > Driver for STMicroelectronics STe10Xp PHYs │ │
│ │ < > Driver for LSI ET1011C PHY │ │
│ │ < > Driver for Micrel PHYs │ │
│ │ < > Support for bitbanged MDIO buses │ │
│ └───────────────────────────────────────────────────────────────────────────────┘ │
├───────────────────────────────────────────────────────────────────────────────────┤
│ <Select> < Exit > < Help > │
└───────────────────────────────────────────────────────────────────────────────────┘

== I2C Hardware Bus ==
.config - Linux/i386 2.6.38-34-itc Kernel Configuration
────────────────────────────────────────────────────────────────────────────────────────
┌──────────────────────────── I2C Hardware Bus support ─────────────────────────────┐
│ Arrow keys navigate the menu. <Enter> selects submenus --->. Highlighted │
│ letters are hotkeys. Pressing <Y> includes, <N> excludes, <M> modularizes │
│ features. Press <Esc><Esc> to exit, <?> for Help, </> for Search. Legend: [*] │
│ built-in [ ] excluded <M> module < > module capable │
│ ┌────^(-)───────────────────────────────────────────────────────────────────────┐ │
│ │ < > VIA VT82C596/82C686/82xx and CX700/VX8xx │ │
│ │ *** ACPI drivers *** │ │
│ │ <M> SMBus Control Method Interface │ │
│ │ *** I2C system bus drivers (mostly embedded / system-on-chip) *** │ │
│ │ < > GPIO-based bitbanging I2C │ │
│ │ < > Intel Moorestown/Medfield Platform I2C controller │ │
│ │ < > OpenCores I2C Controller │ │
│ │ < > PCA9564/PCA9665 as platform device │ │
│ │ < > Simtec Generic I2C interface │ │
│ │ < > Xilinx I2C Controller │ │
│ │ <M> PCH I2C of Intel EG20T │ │
│ └────v(+)───────────────────────────────────────────────────────────────────────┘ │
├───────────────────────────────────────────────────────────────────────────────────┤
│ <Select> < Exit > < Help > │
└───────────────────────────────────────────────────────────────────────────────────┘

== SPI Bus ==
.config - Linux/i386 2.6.38-34-itc Kernel Configuration
────────────────────────────────────────────────────────────────────────────────────────
┌─────────────────────────────────── SPI support ───────────────────────────────────┐
│ Arrow keys navigate the menu. <Enter> selects submenus --->. Highlighted │
│ letters are hotkeys. Pressing <Y> includes, <N> excludes, <M> modularizes │
│ features. Press <Esc><Esc> to exit, <?> for Help, </> for Search. Legend: [*] │
│ built-in [ ] excluded <M> module < > module capable │
│ ┌───────────────────────────────────────────────────────────────────────────────┐ │
│ │ --- SPI support │ │
│ │ [ ] Debug support for SPI drivers │ │
│ │ *** SPI Master Controller Drivers *** │ │
│ │ < > Utilities for Bitbanging SPI masters │ │
│ │ < > Parallel port adapter for AVR Butterfly (DEVELOPMENT) │ │
│ │ < > GPIO-based bitbanging SPI Master │ │
│ │ < > Parallel port adapter for LM70 eval board (DEVELOPMENT) │ │
│ │ < > PXA2xx SSP SPI master │ │
│ │ <*> Topcliff PCH SPI Controller │ │
│ │ < > Xilinx SPI controller common module │ │
│ │ < > DesignWare SPI controller core support │ │
│ └────v(+)───────────────────────────────────────────────────────────────────────┘ │
├───────────────────────────────────────────────────────────────────────────────────┤
│ <Select> < Exit > < Help > │
└───────────────────────────────────────────────────────────────────────────────────┘

== Intel® Embedded Media and Graphics ==
Intel® Embedded Media and Graphics Driver (EMGD) requires a kernel drm module for proper functionality. Sources are available at [http://edc.intel.com/Software/Downloads/emgd/ Intel® Embedded Media and Graphics Driver]. These drivers are not present in official Linux sources.
.config - Linux/i386 2.6.38-34-itc Kernel Configuration
────────────────────────────────────────────────────────────────────────────────────────
┌───────── Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) ─────────┐
│ Arrow keys navigate the menu. <Enter> selects submenus --->. Highlighted │
│ letters are hotkeys. Pressing <Y> includes, <N> excludes, <M> modularizes │
│ features. Press <Esc><Esc> to exit, <?> for Help, </> for Search. Legend: [*] │
│ built-in [ ] excluded <M> module < > module capable │
│ ┌───────────────────────────────────────────────────────────────────────────────┐ │
│ │ --- Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) │ │
│ │ < > 3dfx Banshee/Voodoo3+ │ │
│ │ < > ATI Rage 128 │ │
│ │ < > ATI Radeon │ │
│ │ < > Intel I810 │ │
│ │ < > Intel 830M, 845G, 852GM, 855GM, 865G │ │
│ │ < > Matrox g200/g400 │ │
│ │ < > SiS video cards │ │
│ │ < > Via unichrome video cards │ │
│ │ < > Savage video cards │ │
│ │ <M> Intel IVI EMGD Kernel Module Driver │ │
│ └───────────────────────────────────────────────────────────────────────────────┘ │
├───────────────────────────────────────────────────────────────────────────────────┤
│ <Select> < Exit > < Help > │
└───────────────────────────────────────────────────────────────────────────────────┘

== Intel HD Audio ==
.config - Linux/i386 2.6.38-34-itc Kernel Configuration
────────────────────────────────────────────────────────────────────────────────────────
┌───────────────────────────────── Intel HD Audio ──────────────────────────────────┐
│ Arrow keys navigate the menu. <Enter> selects submenus --->. Highlighted │
│ letters are hotkeys. Pressing <Y> includes, <N> excludes, <M> modularizes │
│ features. Press <Esc><Esc> to exit, <?> for Help, </> for Search. Legend: [*] │
│ built-in [ ] excluded <M> module < > module capable │
│ ┌────^(-)───────────────────────────────────────────────────────────────────────┐ │
│ │ -*- Build hwdep interface for HD-audio driver │ │
│ │ -*- Allow dynamic codec reconfiguration (EXPERIMENTAL) │ │
│ │ [*] Support digital beep via input layer │ │
│ │ (1) Digital beep registration mode (0=off, 1=on, 2=mute sw on/off) │ │
│ │ [*] Support jack plugging notification via input layer │ │
│ │ [*] Support initialization patch loading for HD-audio │ │
│ │ [*] Build Realtek HD-audio codec support │ │
│ │ [ ] Build Analog Device HD-audio codec support │ │
│ │ [*] Build IDT/Sigmatel HD-audio codec support │ │
│ │ [ ] Build VIA HD-audio codec support │ │
│ │ [ ] Build HDMI/DisplayPort HD-audio codec support │ │
│ │ [ ] Build Cirrus Logic codec support │ │
│ │ [ ] Build Conexant HD-audio codec support │ │
│ │ [ ] Build Creative CA0110-IBG codec support │ │
│ │ [ ] Build C-Media HD-audio codec support │ │
│ │ [ ] Build Silicon Labs 3054 HD-modem codec support │ │
│ │ [*] Enable generic HD-audio codec parser │ │
│ │ [*] Aggressive power-saving on HD-audio │ │
│ │ (0) Default time-out for HD-audio power-save mode │ │
│ └───────────────────────────────────────────────────────────────────────────────┘ │
├───────────────────────────────────────────────────────────────────────────────────┤
│ <Select> < Exit > < Help > │
└───────────────────────────────────────────────────────────────────────────────────┘

== MMC/SD/SDIO card support ==
.config - Linux/i386 2.6.38-34-itc Kernel Configuration
────────────────────────────────────────────────────────────────────────────────────────
┌──────────────────────────── MMC/SD/SDIO card support ─────────────────────────────┐
│ Arrow keys navigate the menu. <Enter> selects submenus --->. Highlighted │
│ letters are hotkeys. Pressing <Y> includes, <N> excludes, <M> modularizes │
│ features. Press <Esc><Esc> to exit, <?> for Help, </> for Search. Legend: [*] │
│ built-in [ ] excluded <M> module < > module capable │
│ ┌────^(-)───────────────────────────────────────────────────────────────────────┐ │
│ │ < > MMC host test driver │ │
│ │ *** MMC/SD/SDIO Host Controller Drivers *** │ │
│ │ <*> Secure Digital Host Controller Interface support │ │
│ │ <*> SDHCI support on PCI bus │ │
│ │ [ ] Ricoh MMC Controller Disabler (EXPERIMENTAL) │ │
│ │ < > SDHCI support on the platform specific bus │ │
│ │ < > Winbond W83L51xD SD/MMC Card Interface support │ │
│ │ < > TI Flash Media MMC/SD Interface support (EXPERIMENTAL) │ │
│ │ < > ENE CB710 MMC/SD Interface support │ │
│ │ < > VIA SD/MMC Card Reader Driver │ │
│ │ < > USB SD Host Controller (USHC) support │ │
│ └───────────────────────────────────────────────────────────────────────────────┘ │
├───────────────────────────────────────────────────────────────────────────────────┤
│ <Select> < Exit > < Help > │
└───────────────────────────────────────────────────────────────────────────────────┘

== Serial driver ==
.config - Linux/i386 2.6.38-34-itc Kernel Configuration
────────────────────────────────────────────────────────────────────────────────────────
┌───────────────────────────────── Serial drivers ──────────────────────────────────┐
│ Arrow keys navigate the menu. <Enter> selects submenus --->. Highlighted │
│ letters are hotkeys. Pressing <Y> includes, <N> excludes, <M> modularizes │
│ features. Press <Esc><Esc> to exit, <?> for Help, </> for Search. Legend: [*] │
│ built-in [ ] excluded <M> module < > module capable │
│ ┌────^(-)───────────────────────────────────────────────────────────────────────┐ │
│ │ [*] Support RSA serial ports │ │
│ │ *** Non-8250 serial port support *** │ │
│ │ < > MAX3100 support │ │
│ │ < > MAX3107 support │ │
│ │ < > Medfield High Speed UART support │ │
│ │ < > Digi International NEO PCI Support │ │
│ │ < > Support for timberdale UART │ │
│ │ < > Altera JTAG UART support │ │
│ │ < > Altera UART support │ │
│ │ < > SPI protocol driver for Infineon 6x60 modem (EXPERIMENTAL) │ │
│ │ <M> Intel EG20T PCH UART │ │
│ └───────────────────────────────────────────────────────────────────────────────┘ │
├───────────────────────────────────────────────────────────────────────────────────┤
│ <Select> < Exit > < Help > │
└───────────────────────────────────────────────────────────────────────────────────┘

== See also ==

* [[CM-iTC: Linux: Getting started|Getting started with Linux on CM-iTC]]
* [[CM-iTC: Linux: Mint|Linux Mint for CM-iTC]]

[[Category:Linux]]
[[Category:CM-iTC]]

CM-iTC: Linux: Mint

2011-02-28T11:31:05Z

Mike:

== Overview ==
Linux Mint for the CM-iTC is based on standard Linux Mint 10 "Julia". [http://compulab.co.il/itc/download/itc-linux.zip The Linux package for CM-iTC] contains run-time image with a full-featured desktop filesystem. Network, sound and graphics should work out of the box.

== Bootloader ==
In the provided ready-to-run image {{filename|syslinux}} bootloader is installed instead of commonly used {{filename|grub}}. At the current state neither legacy {{filename|grub}} nor {{filename|grub2}} can boot Linux from SD Card on the CM-iTC.

Take this in account if you are planning to install another Linux distribution to an SD card. By default, most Linux distributions use grub and you will need to replace it with

== Authorization info ==
* username: itc
* password: 111111

== Customized kernel ==
* Based on the 2.6.38 mainline kernel with patches from Ubuntu and Compulab.
* Available in packages [http://compulab.co.il/workspace/sw/itc/maverick/source repository]
* Supports most features present on the SB-iTC development board and CM-iTC module.
* Described in more detail on the [[CM-iTC: Linux: Kernel|Linux kernel for CM-iTC]] page.

== Package management ==
* In order to be consistent with Ubuntu/Debian packaging standards, all custom packages provided by CompuLab reside in the [http://compulab.co.il/workspace/sw/itc/maverick repository].
* This repository contains [http://compulab.co.il/workspace/sw/itc/maverick/binary/ binaries] and [http://compulab.co.il/workspace/sw/itc/maverick/source/ sources] for the kernel, graphic drivers, libraries, etc. You will receive all required updates automatically.
* Please refer to [http://www.debian.org/doc/manuals/repository-howto/repository-howto Debian Repository HOWTO] for information about working with a Ubuntu/Debian repositories.

== Graphic support ==
* Intel Processor E6xx Series using the SGX535 graphic module from PowerVR.
* Graphic drivers are [http://edc.intel.com/Software/Downloads/EMGD/ Intel® Embedded Media and Graphics Drivers].
* Intel® Embedded Graphics Drivers specifically target the needs of embedded platform developers. Please review this [http://edc.intel.com/Download.aspx?id=4722&returnurl=/Software/Downloads/EMGD/default.aspx Users Guide].
*: {{Note|The current state of the EMGD drivers may be called ''alpha version''. They are not included in any official Linux distribution yet. There are still a few technical issues to be fixed. Known issues are listed below.}}
* Known issues
** Display artefacts when visual effects are enabled. Work-around: Set Preferences->Appearance->Visual Effects to "None"

== MPlayer ==
The E6xx graphic module provides support for the hardware decoding of the most popular video formats. The well-known MPlayer media player is patched for this purpose and supports the following codecs:
* MPEG-2
* MPEG-4 ASP (DivX)
* H.263 (MPEG-4 short-video header variant)
* MPEG-4 AVC (H.264)
* Windows Media Video 9 (WMV3)
* Windows Media Video 9 Advanced (VC-1 Advanced profile)
{{Note|Non-accelerated decoding is currently not supported with the vaapi renderer.}}

Please refer to [http://www.splitted-desktop.com/~gbeauchesne/mplayer-vaapi official mplayer-vaapi page] for more information.

== Sound ==
There are two sound cards available in the evaluation kit, one on the CM-iTC core module and another on the SB-iTC baseboard. Current Linux drivers allow only one of the two cards to be active at any given time. The {{filename|/etc/modprobe.d/alsa-base.conf}} file specifies which card will be active.
* To use the CM-iTC sound card, add this line to {{filename|/etc/modprobe.d/alsa-base.conf}}:
<pre>
options snd-hda-intel probe_mask=0x1
</pre>
In this case, the out line is CORE-LINE-OUT (P31) and the in line is CORE-LINE-IN (P29)

* To use the SB-iTC sound card, add this line to {{filename|/etc/modprobe.d/alsa-base.conf}}:
<pre>
options snd-hda-intel probe_mask=0x2
</pre>
In this case, the out lines are BASE-HOUT-A (P23) and BASE-HOUT-B (P22) and the in line is LINE-IN-C (P21)

== See also ==

* [[CM-iTC: Linux: Getting started|Getting started with Linux on CM-iTC]]
* [[CM-iTC: Linux: Kernel|Linux Kernel for CM-iTC]]

[[Category:Linux]]
[[Category:CM-iTC]]

Category:CM-iTC

2011-02-28T11:30:57Z

Mike: New page: CM-iTC module related pages

CM-iTC module related pages

CM-iTC: Linux: Getting started

2011-02-28T11:29:40Z

Mike:

== Overview ==

Linux for the CM-iTC/SB-iTC is based on Linux Mint 10. [http://compulab.co.il/itc/download/itc-linux.zip The Linux package for CM-iTC] includes a ready-to-run image that can be installed on SD Card, SATA or USB storage device.

== Installation ==
* Download and unzip [http://compulab.co.il/itc/download/itc-linux.zip The Linux package for CM-iTC] to the host PC.
* Ensure the integrity of the file:
<pre>
$ md5sum itc-linux.zip
cad78c9ce35effdaad051314c7d5dffd itc-linux.zip
</pre>
* Prepare SD Card, SATA or USB storage device. It must have at least 8GB capacity.
* Create bootable storage device using ''mint10.8GB.img'' file from the package. Please refer to [http://help.ubuntu.com/community/Installation/FromImgFiles Installation From Img Files] for description of installing images.

== Boot ==
* Connect your storage device to CM-iTC.
* Welcome to Linux Mint 10, username: itc, password: 111111.

== See also ==
* [[CM-iTC: Linux: Kernel|Linux Kernel for CM-iTC]]
* [[CM-iTC: Linux: Mint|Linux Mint for CM-iTC]]

[[Category:Linux]]
[[Category:CM-iTC]]

CM-iTC Linux

2011-02-28T11:28:59Z

Mike:

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

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

* [[CM-iTC: Linux: Getting started|Getting started with Linux on CM-iTC]]
* [[CM-iTC: Linux: Kernel|Linux Kernel for CM-iTC]]
* [[CM-iTC: Linux: Mint|Linux Mint for CM-iTC]]
|Itc-cm-top-m.jpg|thumb}}

{{ChangelogRss| content=
===== 28-Feb-2011 =====
: Initial release of Linux for CM-iTC
}}

[[Category:Linux]]
[[Category:CM-iTC]]

Category:CM-iTC

2011-02-28T11:26:22Z

Mike: New page: CM-iTC module related pages

CM-iTC module related pages

CM-iTC Linux

2011-02-28T11:25:43Z

Mike:

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

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

* [[CM-iTC: Linux: Getting started|Getting started with Linux on CM-iTC]]
* [[CM-iTC: Linux: Kernel|Linux Kernel for CM-iTC]]
* [[CM-iTC: Linux: Mint|Linux Mint for CM-iTC]]
|Itc-cm-top-m.jpg|thumb}}

{{ChangelogRss| content=
===== 28-Feb-2011 =====
: Initial release of Linux for CM-iTC
}}

[[Category:Linux]]
[[Category:CM-iTC]]

CM-iTC: Linux: Mint

2011-02-28T11:24:08Z

Mike: Linux Mint for CM-iTC moved to CM-iTC: Linux: Mint

== Overview ==
Linux Mint for the CM-iTC is based on standard Linux Mint 10 "Julia". [http://compulab.co.il/itc/download/itc-linux.zip The Linux package for CM-iTC] contains run-time image with a full-featured desktop filesystem. Network, sound and graphics should work out of the box.

== Bootloader ==
In the provided ready-to-run image {{filename|syslinux}} bootloader is installed instead of commonly used {{filename|grub}}. At the current state neither legacy {{filename|grub}} nor {{filename|grub2}} can boot Linux from SD Card on the CM-iTC.

Take this in account if you are planning to install another Linux distribution to an SD card. By default, most Linux distributions use grub and you will need to replace it with

== Authorization info ==
* username: itc
* password: 111111

== Customized kernel ==
* Based on the 2.6.38 mainline kernel with patches from Ubuntu and Compulab.
* Available in packages [http://compulab.co.il/workspace/sw/itc/maverick/source repository]
* Supports most features present on the SB-iTC development board and CM-iTC module.
* Described in more detail on the [[Linux Kernel for CM-iTC|Linux kernel for CM-iTC]] page.

== Package management ==
* In order to be consistent with Ubuntu/Debian packaging standards, all custom packages provided by CompuLab reside in the [http://compulab.co.il/workspace/sw/itc/maverick repository].
* This repository contains [http://compulab.co.il/workspace/sw/itc/maverick/binary/ binaries] and [http://compulab.co.il/workspace/sw/itc/maverick/source/ sources] for the kernel, graphic drivers, libraries, etc. You will receive all required updates automatically.
* Please refer to [http://www.debian.org/doc/manuals/repository-howto/repository-howto Debian Repository HOWTO] for information about working with a Ubuntu/Debian repositories.

== Graphic support ==
* Intel Processor E6xx Series using the SGX535 graphic module from PowerVR.
* Graphic drivers are [http://edc.intel.com/Software/Downloads/EMGD/ Intel® Embedded Media and Graphics Drivers].
* Intel® Embedded Graphics Drivers specifically target the needs of embedded platform developers. Please review this [http://edc.intel.com/Download.aspx?id=4722&returnurl=/Software/Downloads/EMGD/default.aspx Users Guide].
*: {{Note|The current state of the EMGD drivers may be called ''alpha version''. They are not included in any official Linux distribution yet. There are still a few technical issues to be fixed. Known issues are listed below.}}
* Known issues
** Display artefacts when visual effects are enabled. Work-around: Set Preferences->Appearance->Visual Effects to "None"

== MPlayer ==
The E6xx graphic module provides support for the hardware decoding of the most popular video formats. The well-known MPlayer media player is patched for this purpose and supports the following codecs:
* MPEG-2
* MPEG-4 ASP (DivX)
* H.263 (MPEG-4 short-video header variant)
* MPEG-4 AVC (H.264)
* Windows Media Video 9 (WMV3)
* Windows Media Video 9 Advanced (VC-1 Advanced profile)
{{Note|Non-accelerated decoding is currently not supported with the vaapi renderer.}}

Please refer to [http://www.splitted-desktop.com/~gbeauchesne/mplayer-vaapi official mplayer-vaapi page] for more information.

== Sound ==
There are two sound cards available in the evaluation kit, one on the CM-iTC core module and another on the SB-iTC baseboard. Current Linux drivers allow only one of the two cards to be active at any given time. The {{filename|/etc/modprobe.d/alsa-base.conf}} file specifies which card will be active.
* To use the CM-iTC sound card, add this line to {{filename|/etc/modprobe.d/alsa-base.conf}}:
<pre>
options snd-hda-intel probe_mask=0x1
</pre>
In this case, the out line is CORE-LINE-OUT (P31) and the in line is CORE-LINE-IN (P29)

* To use the SB-iTC sound card, add this line to {{filename|/etc/modprobe.d/alsa-base.conf}}:
<pre>
options snd-hda-intel probe_mask=0x2
</pre>
In this case, the out lines are BASE-HOUT-A (P23) and BASE-HOUT-B (P22) and the in line is LINE-IN-C (P21)

== See also ==

* [[Getting started with Linux on CM-iTC]]
* [[Linux Kernel for CM-iTC]]

[[Category:Linux]]
[[Category:CM-iTC]]

CM-iTC: Linux: Kernel

2011-02-28T11:23:36Z

Mike: Linux Kernel for CM-iTC moved to CM-iTC: Linux: Kernel

== Overview ==
The CM-iTC is a fully-compatible x86 PC. Recent Linux kernels support most CM-iTC hardware features. CompuLab provides [http://compulab.co.il/workspace/sw/itc/maverick/source/linux_2.6.38.orig.tar.gz 2.6.38] kernel and customized [http://compulab.co.il/workspace/sw/itc/maverick/source/linux_2.6.38-34.1.diff.gz patch] to it. The configuration file is {{filename|debian/config/i386/config.itc}} in the kernel sources tree.

The most significant features of interest to kernel developers are described below.

== CAN Bus ==
.config - Linux/i386 2.6.38-34-itc Kernel Configuration
────────────────────────────────────────────────────────────────────────────────────────
┌─────────────────────────────── CAN Device Drivers ────────────────────────────────┐
│ Arrow keys navigate the menu. <Enter> selects submenus --->. Highlighted │
│ letters are hotkeys. Pressing <Y> includes, <N> excludes, <M> modularizes │
│ features. Press <Esc><Esc> to exit, <?> for Help, </> for Search. Legend: [*] │
│ built-in [ ] excluded <M> module < > module capable │
│ ┌───────────────────────────────────────────────────────────────────────────────┐ │
│ │ < > Virtual Local CAN Interface (vcan) │ │
│ │ < > Serial / USB serial CAN Adaptors (slcan) │ │
│ │ <M> Platform CAN drivers with Netlink support │ │
│ │ [*] CAN bit-timing calculation │ │
│ │ < > Microchip MCP251x SPI CAN controllers │ │
│ │ <M> PCH CAN │ │
│ │ < > Philips/NXP SJA1000 devices ---> │ │
│ │ CAN USB interfaces ---> │ │
│ │ [ ] CAN devices debugging messages │ │
│ │ │ │
│ └───────────────────────────────────────────────────────────────────────────────┘ │
├───────────────────────────────────────────────────────────────────────────────────┤
│ <Select> < Exit > < Help > │
└───────────────────────────────────────────────────────────────────────────────────┘

== Network device ==
.config - Linux/i386 2.6.38-34-itc Kernel Configuration
────────────────────────────────────────────────────────────────────────────────────────
┌────────────────────────────── Ethernet (1000 Mbit) ───────────────────────────────┐
│ Arrow keys navigate the menu. <Enter> selects submenus --->. Highlighted │
│ letters are hotkeys. Pressing <Y> includes, <N> excludes, <M> modularizes │
│ features. Press <Esc><Esc> to exit, <?> for Help, </> for Search. Legend: [*] │
│ built-in [ ] excluded <M> module < > module capable │
│ ┌────^(-)───────────────────────────────────────────────────────────────────────┐ │
│ │ < > IP1000 Gigabit Ethernet support │ │
│ │ < > Intel(R) 82575/82576 PCI-Express Gigabit Ethernet support │ │
│ │ < > Intel(R) 82576 Virtual Function Ethernet support │ │
│ │ < > National Semiconductor DP83820 support │ │
│ │ < > Packet Engines Hamachi GNIC-II support │ │
│ │ < > Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL) │ │
│ │ <M> Realtek 8169 gigabit ethernet support │ │
│ │ [*] VLAN support │ │
│ │ < > SiS190/SiS191 gigabit ethernet support │ │
│ │ < > New SysKonnect GigaEthernet support │ │
│ └────v(+)───────────────────────────────────────────────────────────────────────┘ │
├───────────────────────────────────────────────────────────────────────────────────┤
│ <Select> < Exit > < Help > │
└───────────────────────────────────────────────────────────────────────────────────┘

.config - Linux/i386 2.6.38-34-itc Kernel Configuration
────────────────────────────────────────────────────────────────────────────────────────
┌────────────────────── PHY Device support and infrastructure ──────────────────────┐
│ Arrow keys navigate the menu. <Enter> selects submenus --->. Highlighted │
│ letters are hotkeys. Pressing <Y> includes, <N> excludes, <M> modularizes │
│ features. Press <Esc><Esc> to exit, <?> for Help, </> for Search. Legend: [*] │
│ built-in [ ] excluded <M> module < > module capable │
│ ┌────^(-)───────────────────────────────────────────────────────────────────────┐ │
│ │ < > Drivers for SMSC PHYs │ │
│ │ < > Drivers for Broadcom PHYs │ │
│ │ < > Drivers for Broadcom 63xx SOCs internal PHY │ │
│ │ < > Drivers for ICPlus PHYs │ │
│ │ <M> Drivers for Realtek PHYs │ │
│ │ < > Drivers for National Semiconductor PHYs │ │
│ │ < > Driver for STMicroelectronics STe10Xp PHYs │ │
│ │ < > Driver for LSI ET1011C PHY │ │
│ │ < > Driver for Micrel PHYs │ │
│ │ < > Support for bitbanged MDIO buses │ │
│ └───────────────────────────────────────────────────────────────────────────────┘ │
├───────────────────────────────────────────────────────────────────────────────────┤
│ <Select> < Exit > < Help > │
└───────────────────────────────────────────────────────────────────────────────────┘

== I2C Hardware Bus ==
.config - Linux/i386 2.6.38-34-itc Kernel Configuration
────────────────────────────────────────────────────────────────────────────────────────
┌──────────────────────────── I2C Hardware Bus support ─────────────────────────────┐
│ Arrow keys navigate the menu. <Enter> selects submenus --->. Highlighted │
│ letters are hotkeys. Pressing <Y> includes, <N> excludes, <M> modularizes │
│ features. Press <Esc><Esc> to exit, <?> for Help, </> for Search. Legend: [*] │
│ built-in [ ] excluded <M> module < > module capable │
│ ┌────^(-)───────────────────────────────────────────────────────────────────────┐ │
│ │ < > VIA VT82C596/82C686/82xx and CX700/VX8xx │ │
│ │ *** ACPI drivers *** │ │
│ │ <M> SMBus Control Method Interface │ │
│ │ *** I2C system bus drivers (mostly embedded / system-on-chip) *** │ │
│ │ < > GPIO-based bitbanging I2C │ │
│ │ < > Intel Moorestown/Medfield Platform I2C controller │ │
│ │ < > OpenCores I2C Controller │ │
│ │ < > PCA9564/PCA9665 as platform device │ │
│ │ < > Simtec Generic I2C interface │ │
│ │ < > Xilinx I2C Controller │ │
│ │ <M> PCH I2C of Intel EG20T │ │
│ └────v(+)───────────────────────────────────────────────────────────────────────┘ │
├───────────────────────────────────────────────────────────────────────────────────┤
│ <Select> < Exit > < Help > │
└───────────────────────────────────────────────────────────────────────────────────┘

== SPI Bus ==
.config - Linux/i386 2.6.38-34-itc Kernel Configuration
────────────────────────────────────────────────────────────────────────────────────────
┌─────────────────────────────────── SPI support ───────────────────────────────────┐
│ Arrow keys navigate the menu. <Enter> selects submenus --->. Highlighted │
│ letters are hotkeys. Pressing <Y> includes, <N> excludes, <M> modularizes │
│ features. Press <Esc><Esc> to exit, <?> for Help, </> for Search. Legend: [*] │
│ built-in [ ] excluded <M> module < > module capable │
│ ┌───────────────────────────────────────────────────────────────────────────────┐ │
│ │ --- SPI support │ │
│ │ [ ] Debug support for SPI drivers │ │
│ │ *** SPI Master Controller Drivers *** │ │
│ │ < > Utilities for Bitbanging SPI masters │ │
│ │ < > Parallel port adapter for AVR Butterfly (DEVELOPMENT) │ │
│ │ < > GPIO-based bitbanging SPI Master │ │
│ │ < > Parallel port adapter for LM70 eval board (DEVELOPMENT) │ │
│ │ < > PXA2xx SSP SPI master │ │
│ │ <*> Topcliff PCH SPI Controller │ │
│ │ < > Xilinx SPI controller common module │ │
│ │ < > DesignWare SPI controller core support │ │
│ └────v(+)───────────────────────────────────────────────────────────────────────┘ │
├───────────────────────────────────────────────────────────────────────────────────┤
│ <Select> < Exit > < Help > │
└───────────────────────────────────────────────────────────────────────────────────┘

== Intel® Embedded Media and Graphics ==
Intel® Embedded Media and Graphics Driver (EMGD) requires a kernel drm module for proper functionality. Sources are available at [http://edc.intel.com/Software/Downloads/emgd/ Intel® Embedded Media and Graphics Driver]. These drivers are not present in official Linux sources.
.config - Linux/i386 2.6.38-34-itc Kernel Configuration
────────────────────────────────────────────────────────────────────────────────────────
┌───────── Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) ─────────┐
│ Arrow keys navigate the menu. <Enter> selects submenus --->. Highlighted │
│ letters are hotkeys. Pressing <Y> includes, <N> excludes, <M> modularizes │
│ features. Press <Esc><Esc> to exit, <?> for Help, </> for Search. Legend: [*] │
│ built-in [ ] excluded <M> module < > module capable │
│ ┌───────────────────────────────────────────────────────────────────────────────┐ │
│ │ --- Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) │ │
│ │ < > 3dfx Banshee/Voodoo3+ │ │
│ │ < > ATI Rage 128 │ │
│ │ < > ATI Radeon │ │
│ │ < > Intel I810 │ │
│ │ < > Intel 830M, 845G, 852GM, 855GM, 865G │ │
│ │ < > Matrox g200/g400 │ │
│ │ < > SiS video cards │ │
│ │ < > Via unichrome video cards │ │
│ │ < > Savage video cards │ │
│ │ <M> Intel IVI EMGD Kernel Module Driver │ │
│ └───────────────────────────────────────────────────────────────────────────────┘ │
├───────────────────────────────────────────────────────────────────────────────────┤
│ <Select> < Exit > < Help > │
└───────────────────────────────────────────────────────────────────────────────────┘

== Intel HD Audio ==
.config - Linux/i386 2.6.38-34-itc Kernel Configuration
────────────────────────────────────────────────────────────────────────────────────────
┌───────────────────────────────── Intel HD Audio ──────────────────────────────────┐
│ Arrow keys navigate the menu. <Enter> selects submenus --->. Highlighted │
│ letters are hotkeys. Pressing <Y> includes, <N> excludes, <M> modularizes │
│ features. Press <Esc><Esc> to exit, <?> for Help, </> for Search. Legend: [*] │
│ built-in [ ] excluded <M> module < > module capable │
│ ┌────^(-)───────────────────────────────────────────────────────────────────────┐ │
│ │ -*- Build hwdep interface for HD-audio driver │ │
│ │ -*- Allow dynamic codec reconfiguration (EXPERIMENTAL) │ │
│ │ [*] Support digital beep via input layer │ │
│ │ (1) Digital beep registration mode (0=off, 1=on, 2=mute sw on/off) │ │
│ │ [*] Support jack plugging notification via input layer │ │
│ │ [*] Support initialization patch loading for HD-audio │ │
│ │ [*] Build Realtek HD-audio codec support │ │
│ │ [ ] Build Analog Device HD-audio codec support │ │
│ │ [*] Build IDT/Sigmatel HD-audio codec support │ │
│ │ [ ] Build VIA HD-audio codec support │ │
│ │ [ ] Build HDMI/DisplayPort HD-audio codec support │ │
│ │ [ ] Build Cirrus Logic codec support │ │
│ │ [ ] Build Conexant HD-audio codec support │ │
│ │ [ ] Build Creative CA0110-IBG codec support │ │
│ │ [ ] Build C-Media HD-audio codec support │ │
│ │ [ ] Build Silicon Labs 3054 HD-modem codec support │ │
│ │ [*] Enable generic HD-audio codec parser │ │
│ │ [*] Aggressive power-saving on HD-audio │ │
│ │ (0) Default time-out for HD-audio power-save mode │ │
│ └───────────────────────────────────────────────────────────────────────────────┘ │
├───────────────────────────────────────────────────────────────────────────────────┤
│ <Select> < Exit > < Help > │
└───────────────────────────────────────────────────────────────────────────────────┘

== MMC/SD/SDIO card support ==
.config - Linux/i386 2.6.38-34-itc Kernel Configuration
────────────────────────────────────────────────────────────────────────────────────────
┌──────────────────────────── MMC/SD/SDIO card support ─────────────────────────────┐
│ Arrow keys navigate the menu. <Enter> selects submenus --->. Highlighted │
│ letters are hotkeys. Pressing <Y> includes, <N> excludes, <M> modularizes │
│ features. Press <Esc><Esc> to exit, <?> for Help, </> for Search. Legend: [*] │
│ built-in [ ] excluded <M> module < > module capable │
│ ┌────^(-)───────────────────────────────────────────────────────────────────────┐ │
│ │ < > MMC host test driver │ │
│ │ *** MMC/SD/SDIO Host Controller Drivers *** │ │
│ │ <*> Secure Digital Host Controller Interface support │ │
│ │ <*> SDHCI support on PCI bus │ │
│ │ [ ] Ricoh MMC Controller Disabler (EXPERIMENTAL) │ │
│ │ < > SDHCI support on the platform specific bus │ │
│ │ < > Winbond W83L51xD SD/MMC Card Interface support │ │
│ │ < > TI Flash Media MMC/SD Interface support (EXPERIMENTAL) │ │
│ │ < > ENE CB710 MMC/SD Interface support │ │
│ │ < > VIA SD/MMC Card Reader Driver │ │
│ │ < > USB SD Host Controller (USHC) support │ │
│ └───────────────────────────────────────────────────────────────────────────────┘ │
├───────────────────────────────────────────────────────────────────────────────────┤
│ <Select> < Exit > < Help > │
└───────────────────────────────────────────────────────────────────────────────────┘

== Serial driver ==
.config - Linux/i386 2.6.38-34-itc Kernel Configuration
────────────────────────────────────────────────────────────────────────────────────────
┌───────────────────────────────── Serial drivers ──────────────────────────────────┐
│ Arrow keys navigate the menu. <Enter> selects submenus --->. Highlighted │
│ letters are hotkeys. Pressing <Y> includes, <N> excludes, <M> modularizes │
│ features. Press <Esc><Esc> to exit, <?> for Help, </> for Search. Legend: [*] │
│ built-in [ ] excluded <M> module < > module capable │
│ ┌────^(-)───────────────────────────────────────────────────────────────────────┐ │
│ │ [*] Support RSA serial ports │ │
│ │ *** Non-8250 serial port support *** │ │
│ │ < > MAX3100 support │ │
│ │ < > MAX3107 support │ │
│ │ < > Medfield High Speed UART support │ │
│ │ < > Digi International NEO PCI Support │ │
│ │ < > Support for timberdale UART │ │
│ │ < > Altera JTAG UART support │ │
│ │ < > Altera UART support │ │
│ │ < > SPI protocol driver for Infineon 6x60 modem (EXPERIMENTAL) │ │
│ │ <M> Intel EG20T PCH UART │ │
│ └───────────────────────────────────────────────────────────────────────────────┘ │
├───────────────────────────────────────────────────────────────────────────────────┤
│ <Select> < Exit > < Help > │
└───────────────────────────────────────────────────────────────────────────────────┘

== See also ==

* [[Getting started with Linux on CM-iTC]]
* [[Linux Mint for CM-iTC]]

[[Category:Linux]]
[[Category:CM-iTC]]

CM-iTC: Linux: Getting started

2011-02-28T11:21:26Z

Mike: Getting started with Linux on CM-iTC moved to CM-iTC: Linux: Getting started

== Overview ==

Linux for the CM-iTC/SB-iTC is based on Linux Mint 10. [http://compulab.co.il/itc/download/itc-linux.zip The Linux package for CM-iTC] includes a ready-to-run image that can be installed on SD Card, SATA or USB storage device.

== Installation ==
* Download and unzip [http://compulab.co.il/itc/download/itc-linux.zip The Linux package for CM-iTC] to the host PC.
* Ensure the integrity of the file:
<pre>
$ md5sum itc-linux.zip
cad78c9ce35effdaad051314c7d5dffd itc-linux.zip
</pre>
* Prepare SD Card, SATA or USB storage device. It must have at least 8GB capacity.
* Create bootable storage device using ''mint10.8GB.img'' file from the package. Please refer to [http://help.ubuntu.com/community/Installation/FromImgFiles Installation From Img Files] for description of installing images.

== Boot ==
* Connect your storage device to CM-iTC.
* Welcome to Linux Mint 10, username: itc, password: 111111.

== See also ==
* [[Linux Kernel for CM-iTC]]
* [[Linux Mint for CM-iTC]]

[[Category:Linux]]
[[Category:CM-iTC]]

CM-iTC: Linux: Mint

2011-02-28T11:15:50Z

Mike:

== Overview ==
Linux Mint for the CM-iTC is based on standard Linux Mint 10 "Julia". [http://compulab.co.il/itc/download/itc-linux.zip The Linux package for CM-iTC] contains run-time image with a full-featured desktop filesystem. Network, sound and graphics should work out of the box.

== Bootloader ==
In the provided ready-to-run image {{filename|syslinux}} bootloader is installed instead of commonly used {{filename|grub}}. At the current state neither legacy {{filename|grub}} nor {{filename|grub2}} can boot Linux from SD Card on the CM-iTC.

Take this in account if you are planning to install another Linux distribution to an SD card. By default, most Linux distributions use grub and you will need to replace it with

== Authorization info ==
* username: itc
* password: 111111

== Customized kernel ==
* Based on the 2.6.38 mainline kernel with patches from Ubuntu and Compulab.
* Available in packages [http://compulab.co.il/workspace/sw/itc/maverick/source repository]
* Supports most features present on the SB-iTC development board and CM-iTC module.
* Described in more detail on the [[Linux Kernel for CM-iTC|Linux kernel for CM-iTC]] page.

== Package management ==
* In order to be consistent with Ubuntu/Debian packaging standards, all custom packages provided by CompuLab reside in the [http://compulab.co.il/workspace/sw/itc/maverick repository].
* This repository contains [http://compulab.co.il/workspace/sw/itc/maverick/binary/ binaries] and [http://compulab.co.il/workspace/sw/itc/maverick/source/ sources] for the kernel, graphic drivers, libraries, etc. You will receive all required updates automatically.
* Please refer to [http://www.debian.org/doc/manuals/repository-howto/repository-howto Debian Repository HOWTO] for information about working with a Ubuntu/Debian repositories.

== Graphic support ==
* Intel Processor E6xx Series using the SGX535 graphic module from PowerVR.
* Graphic drivers are [http://edc.intel.com/Software/Downloads/EMGD/ Intel® Embedded Media and Graphics Drivers].
* Intel® Embedded Graphics Drivers specifically target the needs of embedded platform developers. Please review this [http://edc.intel.com/Download.aspx?id=4722&returnurl=/Software/Downloads/EMGD/default.aspx Users Guide].
*: {{Note|The current state of the EMGD drivers may be called ''alpha version''. They are not included in any official Linux distribution yet. There are still a few technical issues to be fixed. Known issues are listed below.}}
* Known issues
** Display artefacts when visual effects are enabled. Work-around: Set Preferences->Appearance->Visual Effects to "None"

== MPlayer ==
The E6xx graphic module provides support for the hardware decoding of the most popular video formats. The well-known MPlayer media player is patched for this purpose and supports the following codecs:
* MPEG-2
* MPEG-4 ASP (DivX)
* H.263 (MPEG-4 short-video header variant)
* MPEG-4 AVC (H.264)
* Windows Media Video 9 (WMV3)
* Windows Media Video 9 Advanced (VC-1 Advanced profile)
{{Note|Non-accelerated decoding is currently not supported with the vaapi renderer.}}

Please refer to [http://www.splitted-desktop.com/~gbeauchesne/mplayer-vaapi official mplayer-vaapi page] for more information.

== Sound ==
There are two sound cards available in the evaluation kit, one on the CM-iTC core module and another on the SB-iTC baseboard. Current Linux drivers allow only one of the two cards to be active at any given time. The {{filename|/etc/modprobe.d/alsa-base.conf}} file specifies which card will be active.
* To use the CM-iTC sound card, add this line to {{filename|/etc/modprobe.d/alsa-base.conf}}:
<pre>
options snd-hda-intel probe_mask=0x1
</pre>
In this case, the out line is CORE-LINE-OUT (P31) and the in line is CORE-LINE-IN (P29)

* To use the SB-iTC sound card, add this line to {{filename|/etc/modprobe.d/alsa-base.conf}}:
<pre>
options snd-hda-intel probe_mask=0x2
</pre>
In this case, the out lines are BASE-HOUT-A (P23) and BASE-HOUT-B (P22) and the in line is LINE-IN-C (P21)

== See also ==

* [[Getting started with Linux on CM-iTC]]
* [[Linux Kernel for CM-iTC]]

[[Category:Linux]]
[[Category:CM-iTC]]

CM-iTC: Linux: Getting started

2011-02-28T11:07:34Z

Mike: /* Installation */

== Overview ==

Linux for the CM-iTC/SB-iTC is based on Linux Mint 10. [http://compulab.co.il/itc/download/itc-linux.zip The Linux package for CM-iTC] includes a ready-to-run image that can be installed on SD Card, SATA or USB storage device.

== Installation ==
* Download and unzip [http://compulab.co.il/itc/download/itc-linux.zip The Linux package for CM-iTC] to the host PC.
* Ensure the integrity of the file:
<pre>
$ md5sum itc-linux.zip
cad78c9ce35effdaad051314c7d5dffd itc-linux.zip
</pre>
* Prepare SD Card, SATA or USB storage device. It must have at least 8GB capacity.
* Create bootable storage device using ''mint10.8GB.img'' file from the package. Please refer to [http://help.ubuntu.com/community/Installation/FromImgFiles Installation From Img Files] for description of installing images.

== Boot ==
* Connect your storage device to CM-iTC.
* Welcome to Linux Mint 10, username: itc, password: 111111.

== See also ==
* [[Linux Kernel for CM-iTC]]
* [[Linux Mint for CM-iTC]]

[[Category:Linux]]
[[Category:CM-iTC]]

CM-iTC Linux

2011-02-28T11:06:46Z

Mike:

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

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

* [[Getting started with Linux on CM-iTC]]
* [[Linux Kernel for CM-iTC]]
* [[Linux Mint for CM-iTC]]
|Itc-cm-top-m.jpg|thumb}}

{{ChangelogRss| content=
===== 28-Feb-2011 =====
: Initial release of Linux for CM-iTC
}}

[[Category:Linux]]
[[Category:CM-iTC]]

Linux documentation

2011-02-28T11:06:07Z

Mike:

{| style="border: 1px solid #aaaaaa; margin-top: 20px;" width="100%" align="center"
|- style="line-height: 120%; border-bottom: 1px solid #aaaaaa; font-size: 105%; background-color: #eeeeee;"
| [[CM-iTC Linux | CM-iTC]]
| [[CM-T3517 Linux | CM-T3517]]
| [[CM-A510 Linux | CM-A510]]
| [[CM-T3530 Linux | CM-T3530]]
| [[CM-X300 Linux | CM-X300]]
|-

| <linkedimage>
wikipage=CM-iTC Linux
tooltip=CM-iTC Linux documentation
img_src=Image:itc-cm-top-m.jpg
img_width=200px
img_alt=CM-iTC Linux
</linkedimage>

| <linkedimage>
wikipage=CM-T3517 Linux
tooltip=CM-T3517 Linux documentation
img_src=Image:cm-t3517.jpg
img_width=200px
img_alt=CM-T3517 Linux
</linkedimage>

| <linkedimage>
wikipage=CM-A510 Linux
tooltip=CM-A510 Linux documentation
img_src=Image:A510_CM_top_hq.JPG
img_width=200px
img_alt=CM-A510 Linux
</linkedimage>

| <linkedimage>
wikipage=CM-T3530 Linux
tooltip=CM-T3530 Linux documentation
img_src=Image:T35_CM_top.JPG
img_width=200px
img_alt=CM-T3530 Linux
</linkedimage>

| <linkedimage>
wikipage=CM-X300 Linux
tooltip=CM-X300 Linux documentation
img_src=Image:X300-cm-top-m.jpg
img_width=200px
img_alt=CM-X300 Linux
</linkedimage>

|-

| colspan="5" |
{| width="100%" align="center"
|- style="line-height: 120%; border-bottom: 1px solid #aaaaaa; font-size: 105%; background-color: #eeeeee;"
| [[CM-iGLX Linux | CM-iGLX]]
| [[SBC-FITPC2 Linux | SBC-FITPC2 ]]
| [[CM-iAM Linux | CM-iAM]]
| [[EM-X270 Linux | EM-X270]]
| [[CM-X270 Linux | CM-X270]]
|-

| <linkedimage>
wikipage=CM-iGLX Linux
tooltip=CM-iGLX Linux documentation
img_src=Image:Iglx-cm-top-m.jpg
img_width=200px
img_alt=CM-iGLX Linux
</linkedimage>

| <linkedimage>
wikipage=SBC-FITPC2 Linux
tooltip=SBC-FITPC2 Linux documentation
img_src=Image:Fitpc2-sb-top-ss.jpg
img_width=200px
img_alt=SBC-FITPC2 Linux
</linkedimage>

| <linkedimage>
wikipage=CM-iAM_Linux
tooltip=CM-iAM Linux documentation
img_src=Image:Cm-iam-top.jpg
img_width=200px
img_alt=CM-iAM Linux
</linkedimage>

| <linkedimage>
wikipage=EM-X270 Linux
tooltip=EM-X270 Linux documentation
img_src=Image:X270-em-bot-m.jpg
img_width=200px
img_alt=EM-X270 Linux
</linkedimage>

| <linkedimage>
wikipage=CM-X270 Linux
tooltip=CM-X270 Linux documentation
img_src=Image:X270-cm-l-top-m.jpg
img_width=200px
img_alt=CM-X270 Linux
</linkedimage>

|}

|-
|}

__NOTOC__

{{ChangelogRss| content=

===== 28-Feb-2011 =====
: Initial release of Linux for CM-iTC

===== 27-Jan-2011, CM-A510 =====
: Updates for Linux kernel and Debian filesystem image for CM-A510

===== 31-Dec-2010, CM-T3517 =====
: Initial release of Linux kernel and Debian filesystem image for CM-T3517

===== 28-Oct-2010, CM-A510 =====
: Initial release of Linux kernel and Debian filesystem image for CM-A510

===== 17-Aug-2010, CM-T3530 =====
: Updates for Linux kernel and Angstrom filesystem image for CM-T3530

===== 1-Jun-2010, CM-X300 =====
: Upgrade of Debian example fileystsem image for CM-X300

===== 6-May-2010, CM-iAM =====
: Updates for Ubuntu Linux image for CM-iAM

===== 26-Nov-2009, CM-X300 =====
: Updates for Linux kernel and Debian filesystem image for CM-X300

===== 29-Oct-2009, CM-iAM =====
: Initial release of [[CM-iAM Linux | Linux documentation for CM-iAM]]

===== 30-Aug-2009, SBC-FitPC2 =====
: Initial release of [[SBC-FITPC2 Linux |Linux documentation for SBC-FITPC2]]

===== 25-Jun-2009, CM-X300 =====
: Updates for Linux kernel and Debian filesystem image for CM-X300

===== 23-Jun-2009, Exeda =====
: Initial release of Linux kernel 2.6.30 for Exeda

===== 8-Jun-2009, Exeda =====
: Initial release of Android 1.0 for Exeda

===== 27-May-2009, CM-X300 =====
: Added [[U-Boot for CM-X300]] documentation

===== 29-Dec-2008, EM-X270 =====
: Updates and fixes for Angstrom Linux for EM-X270

===== 23-Nov-2008, CM-X270 =====
: Updates and fixes for Linux kernel 2.6.24

===== 3-Nov-2008, CM-iGLX =====
: Linux kernel updated to 2.6.24
: Added support for GeodeLX video input port
: All Gentoo packages updated to recent versions

===== 19-Aug-2008, CM-X300 =====
: Initial release of Linux package for CM-X300

===== 26-Jun-2008, CM-X270 =====
: Released Linux kernel 2.6.24 for CM-X270
: Updated Debian filesystem image

===== 18-May-2008, CM-X270 =====
: 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]).

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

===== 3-Jan-2008, EM-X270 =====
: 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

===== 26-Dec-2007, CM-X270 =====
: Certain NAND flashes are sensitive to local bus activity. NAND flash driver updated to overcome this limitation.

===== 14-Nov-2007, EM-X270 =====
: Initial release

===== 13-Jun-2007, CM-X270 =====
: Fixed RTC access routines.

===== 28-May-2007, CM-iGLX =====
: 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, CM-iGLX =====
: Initial release of Gentoo for CM-iGLX

===== 6-Feb-2007, CM-X270 =====
: 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, CM-X270 =====
: Make default Debian file system image 512 Mbytes

===== 12-Oct-06, CM-X270 =====
: 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, CM-X270 =====
: Added BGW200 Wireless LAN support for CM-X270L

===== 15-May-06, CM-X270 =====
: 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]]

CM-T3x: Linux: Booting from MMC/SD card

2011-01-31T07:20:23Z

Mike: CM-T3530: Linux: Booting from MMC/SD card moved to CM-T3x: Linux: Booting from MMC/SD card

CM-T3530 can boot either from on-board NAND flash or from MMC/SD card. There are certain requirements for MMC/SD card format imposed by internal boot ROM of the OMAP35x processor. The following describes how to create bootable MMC/SD card for different use cases.

== Creating a bootable MMC/SD card ==
In order to create a bootable MMC/SD card compatible with OMAP35x boot ROM, it is necessary to set a special geometry in the partition table. OMAP35x boot ROM can work only with MMC/SD cards that have 255 heads and 63 sectors/track.

=== Linux ===
Detailed description how use Linux {{cmd|fdisk}} utility to adjust MMC/SD card partition table to suit OMAP35X boot ROM requirements can be found at [http://wiki.omap.com/index.php?title=MMC_Boot_Format TI Embedded Processors Wiki].

=== Windows ===
Windows users can use [http://www.sysanalyser.com/sp27213.exe HP USB Disk Storage Format Tool] and follow the steps below:
* Connect the card reader to the Windows machine where the formatting tool has been installed.
* Insert MMC/SD card into the card reader.
* Launch the HP USB Disk Storage Format Tool.
* Select FAT32 as File System.
* Click on Start.
* After formatting is done click OK.

After a bootable MMC/SD card is created it can be used for recovery system startup, for X-Loader and U-Boot testing and for booting Linux entirely from MMC/SD.

== Booting X-Loader and U-Boot ==
* Copy X-Loader to the MMC/SD card's root directory and rename it as {{filename|MLO}}. It is essential that the MLO will be the first file created on the MMC/SD card.
* Copy U-Boot binary to the MMC/SD card's root directory and rename it as {{filename|u-boot.bin}}.
* Insert the MMC/SD card into SB-T3530 MMC/SD slot.
* Power on the system while holding "SD Boot" (SW1) button on SB-T35.

== Booting Linux ==
CM-T3530 can boot Linux from MMC/SD card. The MMC/SD card should have geometry parameters compatible with OMAP35X boot ROM (255 heads, 63 sectors/track) and two partitions: FAT32 partition for X-Loader, U-Boot and Linux kernel and ext3 partition for root filesystem.

After MMC/SD card geometry and partition table were updated, create FAT32 filesystem on the first partition and ext3 filsystem on the second partition:
sudo mkfs.vfat -F 32 /dev/sdc1
sudo mkfs.ext3 /dev/sdc2
In the above example we assumed that the card was recognized as {{filename|/dev/sdc}}.

Mount the MMC/SD card FAT partition and copy X-Loader ({{filename|MLO}}), U-Boot ({{filename|u-boot.bin}}) and Linux kernel ({{filename|uImage}}) to the MMC/SD card:
mkdir /mnt/card
mount /dev/sdc1 /mnt/card
cp /path/to/t3530-uboot/images/x-load.bin.ift /mnt/card/MLO
sync
cp /path/to/t3530-uboot/images/u-boot.bin /mnt/card
cp /path/to/t3530-linux/images/uImage-cm-t35.bin /mnt/card
umount /mnt/card

Extract Linux filesystem into the ext3 partition of the MMC/SD card:
mount /dev/sdc2 /mnt/card
cd /mnt/card
tar xjvf /path/to/t3530-linux/images/Angstrom-image.tar.bz2
umount /mnt/card

The MMC/SD card is now ready and can be used to boot Linux. The kernel parameters required for MMC/SD boot are
root=/dev/mmcblk0p2 console=ttyS2,115200 rootwait

== See also ==
[http://code.google.com/p/beagleboard/wiki/LinuxBootDiskFormat BeagleBoard MMC/SD boot]

[[Category:Linux|Booting from MMC/SD card]]
[[Category:U-Boot|Booting from MMC/SD card]]
[[Category:CM-T3530|Linux: Booting from MMC/SD card]]

CM-T3530: Linux: Booting from MMC/SD card

2011-01-31T07:20:23Z

Mike: CM-T3530: Linux: Booting from MMC/SD card moved to CM-T3x: Linux: Booting from MMC/SD card

#REDIRECT [[CM-T3x: Linux: Booting from MMC/SD card]]

Linux documentation

2011-01-27T08:23:30Z

Mike:

{| style="border: 1px solid #aaaaaa; margin-top: 20px;" width="100%" align="center"
|- style="line-height: 120%; border-bottom: 1px solid #aaaaaa; font-size: 105%; background-color: #eeeeee;"
| [[CM-T3517 Linux | CM-T3517]]
| [[CM-A510 Linux | CM-A510]]
| [[CM-T3530 Linux | CM-T3530]]
| [[CM-X300 Linux | CM-X300]]
| [[CM-X270 Linux | CM-X270]]
|-

| <linkedimage>
wikipage=CM-T3517 Linux
tooltip=CM-T3517 Linux documentation
img_src=Image:cm-t3517.jpg
img_width=200px
img_alt=CM-T3517 Linux
</linkedimage>

| <linkedimage>
wikipage=CM-A510 Linux
tooltip=CM-A510 Linux documentation
img_src=Image:A510_CM_top_hq.JPG
img_width=200px
img_alt=CM-A510 Linux
</linkedimage>

| <linkedimage>
wikipage=CM-T3530 Linux
tooltip=CM-T3530 Linux documentation
img_src=Image:T35_CM_top.JPG
img_width=200px
img_alt=CM-T3530 Linux
</linkedimage>

| <linkedimage>
wikipage=CM-X300 Linux
tooltip=CM-X300 Linux documentation
img_src=Image:X300-cm-top-m.jpg
img_width=200px
img_alt=CM-X300 Linux
</linkedimage>

| <linkedimage>
wikipage=CM-X270 Linux
tooltip=CM-X270 Linux documentation
img_src=Image:X270-cm-l-top-m.jpg
img_width=200px
img_alt=CM-X270 Linux
</linkedimage>

|-

| colspan="5" |
{| width="100%" align="center"
|- style="line-height: 120%; border-bottom: 1px solid #aaaaaa; font-size: 105%; background-color: #eeeeee;"
| [[CM-iGLX Linux | CM-iGLX]]
| [[SBC-FITPC2 Linux | SBC-FITPC2 ]]
| [[CM-iAM Linux | CM-iAM]]
| [[EM-X270 Linux | EM-X270]]
| [[Exeda Linux | Exeda]]
|-

| <linkedimage>
wikipage=CM-iGLX Linux
tooltip=CM-iGLX Linux documentation
img_src=Image:Iglx-cm-top-m.jpg
img_width=200px
img_alt=CM-iGLX Linux
</linkedimage>

| <linkedimage>
wikipage=SBC-FITPC2 Linux
tooltip=SBC-FITPC2 Linux documentation
img_src=Image:Fitpc2-sb-top-ss.jpg
img_width=200px
img_alt=SBC-FITPC2 Linux
</linkedimage>

| <linkedimage>
wikipage=CM-iAM_Linux
tooltip=CM-iAM Linux documentation
img_src=Image:Cm-iam-top.jpg
img_width=200px
img_alt=CM-iAM Linux
</linkedimage>

| <linkedimage>
wikipage=EM-X270 Linux
tooltip=EM-X270 Linux documentation
img_src=Image:X270-em-bot-m.jpg
img_width=200px
img_alt=EM-X270 Linux
</linkedimage>

| <linkedimage>
wikipage=Exeda Linux
tooltip=Exeda Linux documentation
img_src=Image:exeda.jpg
img_width=200px
img_alt=Exeda Linux
</linkedimage>
|}

|-
|}

__NOTOC__

{{ChangelogRss| content=

===== 27-Jan-2011, CM-A510 =====
: Updates for Linux kernel and Debian filesystem image for CM-A510

===== 31-Dec-2010, CM-T3517 =====
: Initial release of Linux kernel and Debian filesystem image for CM-T3517

===== 28-Oct-2010, CM-A510 =====
: Initial release of Linux kernel and Debian filesystem image for CM-A510

===== 17-Aug-2010, CM-T3530 =====
: Updates for Linux kernel and Angstrom filesystem image for CM-T3530

===== 1-Jun-2010, CM-X300 =====
: Upgrade of Debian example fileystsem image for CM-X300

===== 6-May-2010, CM-iAM =====
: Updates for Ubuntu Linux image for CM-iAM

===== 26-Nov-2009, CM-X300 =====
: Updates for Linux kernel and Debian filesystem image for CM-X300

===== 29-Oct-2009, CM-iAM =====
: Initial release of [[CM-iAM Linux | Linux documentation for CM-iAM]]

===== 30-Aug-2009, SBC-FitPC2 =====
: Initial release of [[SBC-FITPC2 Linux |Linux documentation for SBC-FITPC2]]

===== 25-Jun-2009, CM-X300 =====
: Updates for Linux kernel and Debian filesystem image for CM-X300

===== 23-Jun-2009, Exeda =====
: Initial release of Linux kernel 2.6.30 for Exeda

===== 8-Jun-2009, Exeda =====
: Initial release of Android 1.0 for Exeda

===== 27-May-2009, CM-X300 =====
: Added [[U-Boot for CM-X300]] documentation

===== 29-Dec-2008, EM-X270 =====
: Updates and fixes for Angstrom Linux for EM-X270

===== 23-Nov-2008, CM-X270 =====
: Updates and fixes for Linux kernel 2.6.24

===== 3-Nov-2008, CM-iGLX =====
: Linux kernel updated to 2.6.24
: Added support for GeodeLX video input port
: All Gentoo packages updated to recent versions

===== 19-Aug-2008, CM-X300 =====
: Initial release of Linux package for CM-X300

===== 26-Jun-2008, CM-X270 =====
: Released Linux kernel 2.6.24 for CM-X270
: Updated Debian filesystem image

===== 18-May-2008, CM-X270 =====
: 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]).

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

===== 3-Jan-2008, EM-X270 =====
: 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

===== 26-Dec-2007, CM-X270 =====
: Certain NAND flashes are sensitive to local bus activity. NAND flash driver updated to overcome this limitation.

===== 14-Nov-2007, EM-X270 =====
: Initial release

===== 13-Jun-2007, CM-X270 =====
: Fixed RTC access routines.

===== 28-May-2007, CM-iGLX =====
: 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, CM-iGLX =====
: Initial release of Gentoo for CM-iGLX

===== 6-Feb-2007, CM-X270 =====
: 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, CM-X270 =====
: Make default Debian file system image 512 Mbytes

===== 12-Oct-06, CM-X270 =====
: 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, CM-X270 =====
: Added BGW200 Wireless LAN support for CM-X270L

===== 15-May-06, CM-X270 =====
: 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]]

CM-A510 Linux

2011-01-27T08:16:28Z

Mike:

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

CompuLab Linux support for CM-A510 includes modifications of [[CM-A510: Linux: Kernel|Linux kernel]] and [[CM-A510: Linux: Debian|'''example''' file system image]] based on [http://www.debian.org/ports/arm/ ARM Debian Linux]. It is possible to use other embedded Linux distributions and environments.

|A510_CM_top_hq.JPG|thumb}}
{{Resources Linux
|* [[CM-A510: Linux: Getting started|Getting started with Linux on CM-A510]]
* [[U-Boot for CM-A510]]
|* [[CM-A510: Linux: Kernel|Linux Kernel for CM-A510]]
* [[CM-A510: Linux: Debian|Debian Linux for CM-A510]]
* [[CM-A510: Linux: Ubuntu|Ubuntu Linux for CM-A510]]
* [[Linux Development for ARM modules]]
* [[Linux: Debian: Minimal ARM filesystem | Minimal Debian ARM filesystem]]
|*[[Support]]
* [[CM-A510: Linux: Known Issues|Known Issues]]
}}

{{ChangelogRss| content=

===== 27-Jan-2011: =====
: Updated with Marvell 5.3.6 LSP kernel patch
: Added support for Broadcom bcm4319 wireless LAN
: Added Ubuntu setup guide

===== 28-Oct-2010: =====
: Initial release of Debian Linux for CM-A510
}}

[[Category:Linux]]
[[Category:CM-A510]]

CM-A510: Linux: Ubuntu

2011-01-27T06:31:11Z

Mike: /* Required system changes */

== Prepare installation media ==
* Create bootable LiveUSB using [http://cdimage.ubuntu.com/ports/releases/lucid/release/ubuntu-10.04-server-armel+dove.img Marvell Dove server install image]. Please refer to [http://help.ubuntu.com/community/Installation/FromImgFiles Installation From Img Files] for description of Ubuntu Live USB images.
* Replace {{filename|cdrom/uImage}} file on LiveUSB with [http://compulab.co.il/workspace/sw/ubuntu/lucid/files/uImage uImage] file provided by Compulab.
* Ensure {{filename|uImage}} file integrity, compare its md5sum with [http://compulab.co.il/workspace/sw/ubuntu/lucid/files/uImage.md5 uImage.md5]

== Installation of generic Ubuntu 10.04 Server==
* Connect the host PC to the CM-A510 via the serial cable supplied with the CM-A510 evaluation kit.
* Start terminal emulation software on your PC using the COM port to which the serial cable is connected. Set baud rate to 115200 bps, 8 bit per frame, 1 stop bit, no parity, no flow control.
* Connect LAN0 Ethernet port on CM-A510 (connector P11 on SB-A510) to your local Ethernet.
* Connect LiveUSB to L11 USB port on CM-A510 (connector P11 on SB-A510).
* Connect storage media to the SATA port (connector P18 on SB-A510).
* Turn on the CM-A510. The U-Boot boot-loader will start and you will get a command prompt.
*: {{Note|If the boot settings of your CM-A510 are different than default, you may need to press and hold ^C while turning on the CM-A510, in order to get command prompt.}}
* Start the U-Boot USB subsystem, check that your LiveUSB has valid filesystem and boot.
usb start
fatls usb 0
fatload usb 0:1 0x00200000 /cdrom/uImage
fatload usb 0:1 0x01100000 /cdrom/uInitrd
setenv bootargs pm_disable console=ttyS0,115200 file=/cdrom/preseed/ubuntu-server.seed cdrom-detect/try-usb=true
bootm 0x00200000 0x01100000''

* The resulting output should be similar to the following:
<pre>
CM-A510>> usb start
(Re)start USB...
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 2 USB Device(s) found
Waiting for storage device(s) to settle before scanning...
scanning bus for storage devices... 1 Storage Device(s) found
CM-A510>> fatls usb 0
dists/
pics/
.disk/
install/
preseed/
pool/
cdrom/
1115 cdromupgrade
122326 md5sum.txt
1461 boot.scr
240 readme.diskdefines

4 file(s), 7 dir(s)

CM-A510>> fatload usb 0:1 0x00200000 /cdrom/uImage
reading /cdrom/uImage
............................................................................................................................................................................................................................................................................................

2919244 bytes read
CM-A510>> fatload usb 0:1 0x01100000 /cdrom/uInitrd
reading /cdrom/uInitrd
.......................................................................................................................................................................................................................................................................................................................................................................................

3846585 bytes read
CM-A510>> setenv bootargs pm_disable console=ttyS0,115200 file=/cdrom/preseed/ubuntu-server.seed cdrom-detect/try-usb=true
CM-A510>> bootm 0x00200000 0x01100000
## Booting kernel from Legacy Image at 00200000 ...
Image Name: Linux-2.6.32.21+drm33.7-00068-g2
Created: 2011-01-18 7:57:46 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2919180 Bytes = 2.8 MB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
Image Name: Ubuntu Initrd
Created: 2010-04-28 12:45:39 UTC
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 3846521 Bytes = 3.7 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

[ 0.000000] Linux version 2.6.32.21+drm33.7-00068-g25da183 (kostya@kostya-linux) (gcc version 4.4.1 (Sourcery G++ Lite 2010q1-202) ) #7 Tue Jan 18 09:57:39 IST 2011 ()
[ 0.000000] CPU: Marvell PJ4 v7 Processor-wmmx [560f5815] revision 5 (ARMv7), cr=10c53c7f
[ 0.000000] CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
[ 0.000000] Machine: Compulab CM-A510 Board
...
</pre>
* Continue standard Ubuntu Server installation - choose timezone, partitions, username, password etc.
** Choose language, country, territory or area and keyboard layout
** Say ''"Yes"'' when asked "Continue the install without loading kernel modules?"
** Choose primary network interface, timezone and hostname
** Choose manual partitioning method.
** Make separate partition for {{filename|/boot}} with ext2 or ext3 filesystem. It is essential because U-Boot is able to read {{filename|uImage}} file only from the root directory of a partition.
** Make separate partitions for {{filename|/}} and swap.
** For example use the following scheme:
<pre>
SCSI1 (0,0,0) (sda) - 160.0 GB ATA Hitachi HTS54321
> #1 primary 100.0 MB F ext2 /boot
> #2 primary 158.9 GB F ext4 /
> #3 primary 1.0 GB F swap swap
</pre>
: {{Note|If your partitioning scheme is different, you may need to edit U-Boot boot parameters accordingly.}}
* Write changes to disk and continue installing the system.
** Say ''"Yes"'' when asked "Continue without installing a kernel?"
** Choose username, password and wait until installation will be finished.
** Reboot the CM-A510, leave LiveUSB plugged in the USB port.
** The U-Boot boot-loader will start and you will get a command prompt.
* After the reboot
usb start
fatload usb 0:1 0x00200000 /cdrom/uImage
setenv bootargs 'root=/dev/sda2 pm_disable console=ttyS0,115200'
bootm 0x00200000
* The resulting output should be similar to the following:
<pre>
CM-A510>> usb start
(Re)start USB...
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 2 USB Device(s) found
Waiting for storage device(s) to settle before scanning...
scanning bus for storage devices... 1 Storage Device(s) found
CM-A510>> fatload usb 0:1 0x00200000 /cdrom/uImage
reading /cdrom/uImage
............................................................................................................................................................................................................................................................................................

2919244 bytes read
CM-A510>> setenv bootargs 'root=/dev/sda2 pm_disable console=ttyS0,115200'
CM-A510>> bootm 0x00200000
## Booting kernel from Legacy Image at 00200000 ...
Image Name: Linux-2.6.32.21+drm33.7-00068-g2
Created: 2011-01-18 7:57:46 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2919180 Bytes = 2.8 MB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

[ 0.000000] Linux version 2.6.32.21+drm33.7-00068-g25da183 (kostya@kostya-linux) (gcc version 4.4.1 (Sourcery G++ Lite 2010q1-202) ) #7 Tue Jan 18 09:57:39 IST 2011 ()
[ 0.000000] CPU: Marvell PJ4 v7 Processor-wmmx [560f5815] revision 5 (ARMv7), cr=10c53c7f
[ 0.000000] CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
[ 0.000000] Machine: Compulab CM-A510 Board

...
</pre>
* Boot and login using previously selected username and password.

==Required system changes==
* Add the following lines to {{filename|/etc/apt/sources.list}}
<pre>
## Repository for CM-A510 users provided by Compulab
deb https://compulab.co.il/workspace/sw/ubuntu/lucid binary/
</pre>
* Refresh update manager
<pre>
sudo apt-get update && sudo apt-get upgrade
</pre>
* For convenience we created single metapackage that provides GUI environment, kernel, graphic drivers and media player libraries for HD playback.
<pre>
sudo apt-get install ubuntu-lucid-a510-desktop
</pre>
* Remove custom headers that are not fully compatible with CM-A510.
<pre>
sudo apt-get purge linux-headers-2.6.31-608-imx51 linux-headers-2.6.32-209 linux-headers-2.6.32-209-dove linux-headers-dove linux-headers-imx51 && sudo apt-get autoremove
</pre>
* Ubuntu 10.04 Desktop is now installed, power-off the CM-A510 and unplug LiveUSB.
* Turn on the CM-A510. The U-Boot boot-loader will start and you will get a command prompt.
* Update default boot configuration for the installed system:
setenv bootargs 'root=/dev/sda2 pm_disable console=ttyS0,115200'
setenv bootcmd 'ide reset; ext2load ide 0:1 0x200000 /uImage; bootm 0x200000'
saveenv
* Boot and wait for login screen to appear.
* Welcome to Ubuntu 10.04 Desktop.

== See also ==

* [[CM-A510: Linux: Getting started]]
* [[CM-A510: Linux: Kernel]]

[[Category:Linux|Ubuntu]]
[[Category:CM-A510|Linux: Ubuntu]]

CM-A510: Linux: Kernel

2011-01-25T15:53:31Z

Mike:

== Overview ==
The CM-A510 Linux kernel provides support for on-board peripherals and abstracts the functionality provided by the hardware. Current support coverage is specified at [http://www.compulab.co.il/a510/html/a510-os-support.htm O/S support coverage map] page. CompuLab provides ready-to-run binary kernel images, and source code of the modifications and additions made to the Linux kernel to work properly with CM-A510 modules.

== Kernel command line ==
The CM-A510 Linux kernel is shipped with built-in command line parameters:
ubi.mtd=1,2048 root=ubi0_0 rootfstype=ubifs useNandHal=4bitecc pm_disable console=ttyS0,115200

The default kernel command line defines primary console, default DVI display settings, root device and root filesystem type.

Setting U-Boot {{parameter|bootargs}} environment variable overrides default kernel command line and can be used to set desired kernel parameters.

=== Custom kernel command line options ===

The default command line can be extended with the parameters below to enable additional CM-A510 kernel functionality:

* Enable VGA output:
{{cmd|1=video=dovefb:lcd1:1024x768-16@60-edid clcd.lcd1_enable=1 clcd.lcd0_enable=0}}
* Enable DVI output (default):
{{cmd|1=video=dovefb:lcd0:1024x768-16@60-edid clcd.lcd0_enable=1 clcd.lcd1_enable=0}}
* Enable USB0 device functionality:
{{cmd|1=usb0Mode=device}}
* Enable USB0 host functionality (default):
{{cmd|1=usb0Mode=host}}

{{Note| Current kernel release does not support dual head output. Ensure that only one interface (VGA or DVI) is active.}}

== Building kernel for CM-A510 ==
=== Cross-Compiler ===
There are several options for cross-compilation toolchain setup. You can either compile your cross-compiler or use an already built cross-compiler. The cross-compiler should support the ARM embedded-application binary interface ("[http://en.wikipedia.org/wiki/Application_binary_interface#EABI EABI]")
* Pre-built toolchain:
** [http://www.codesourcery.com/sgpp/lite/arm/portal/release324 CodeSourcery]
* Tools for creating cross-compilers:
** [http://ymorin.is-a-geek.org/dokuwiki/projects/crosstool Crosstool-ng]: Builds a cross-compiler from source. Non-distribution specific.
** [http://www.gentoo.org/proj/en/base/embedded/handbook/index.xml?part=1&chap=4 Crossdev]: Gentoo's cross-compiler builder. Needs Gentoo.

=== U-Boot mkimage tool ===
U-Boot {{cmd|mkimage}} utility is required in order to create kernel images that can be loaded by the CM-A510 boot-loader.
You can download pre-built [[media:mkimage.tar.gz|{{cmd|mkimage}} binary]] or build it yourself:
<pre>
mkdir ~/tmp
cd tmp
wget ftp://ftp.denx.de/pub/u-boot/u-boot-latest.tar.bz2
tar -xjvf u-boot-latest.tar.bz2
cd u-boot-2009.08
touch include/config.{h,mk}
make tools
sudo install tools/mkimage /usr/local/bin
</pre>

=== Getting kernel sources ===
There are two ways to get Linux kernel sources that can be used as a baseline for CM-A510 kernel. You can create a copy of linux-2.6.32.y git tree or download a snapshot and extract it. We assume that you have created {{filename|/home/development/cm-a510/kernel}} directory for CM-A510 kernel development.
==== Snapshot download ====
* Download [http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.32.9.tar.bz2 linux-v2.6.32.9] snapshot with your web browser.
* Extract the downloaded archive {{filename|linux-2.6.32.9.tar.bz2}}
<pre>
cd /home/development/cm-a510/kernel
tar xjvf /path/to/downloaded/linux-2.6.32.9.tar.bz2
</pre>
: This will create {{filename|/home/development/cm-a510/kernel/linux-2.6.32.9}} directory containing linux-2.6.32.9 kernel tree.
* Apply the CM-A510 patch
<pre>
cd /home/development/cm-a510/kernel/linux-2.6.32.9
patch -p1 < /path/to/cm-a510-linux/kernel/linux-2.6.32.9-cm-a510.patch
</pre>

==== Git clone ====
* Install [http://git-scm.com/ git] version control system.
* Create a clone of linux-2.6.32.y kernel tree
<pre>
cd /home/development/cm-a510/kernel
git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.32.y.git linux-2.6.32.9
</pre>
* Create a branch for CM-A510 development. The CM-A510 patches are generated vs. tag v2.6.32.9 in the linux-2.6.32.y tree. It is recommended to use exactly the same baseline to avoid merge conflicts.
<pre>
git checkout -b cm-a510-dev v2.6.32.9
</pre>
* Apply the CM-A510 patch
<pre>
cd /home/development/cm_a510/kernel/linux-2.6.32.9
git apply /path/to/cma510-linux/kernel/linux-2.6.32.9-cm-a510.patch
</pre>

=== Building the kernel ===
<pre>
export ARCH=arm
export CROSS_COMPILE=/path/to/cross-compiler/arm-none-linux-gnueabi-
make cm_a510_defconfig
make uImage && make modules && \
INSTALL_MOD_PATH=/home/development/cm-a510/rootfs make modules_install
</pre>

In the example above, the Linux kernel image ({{filename|uImage}}) will be created in {{filename|/home/development/cm-a510/kernel/linux-2.6.32.9/arch/arm/boot}}, and the loadable kernel modules will be installed into the {{filename|/home/development/cm-a510/rootfs/lib/modules}} directory.

Now, if you boot CM-A510 with newly created kernel image and with networked root filesysem at {{filename|/home/development/cm-a510/rootfs/}} the system will be able to properly load kernel modules and you avoid modules versioning problems.

== See also ==
* [[CM-A510: Linux: Getting started]]

[[Category:Linux]]
[[Category:CM-A510]]

U-Boot documentation

2010-12-16T09:40:09Z

Mike:

{| style="border: 1px solid #aaaaaa; margin-top: 20px;" width="100%" align="center"
|- style="line-height: 120%; border-bottom: 1px solid #aaaaaa; font-size: 105%; background-color: #eeeeee;"
| [[U-Boot for CM-T3517 | CM-T3517]]
| [[U-Boot for CM-A510 | CM-A510]]
| [[U-Boot for CM-T3530 | CM-T3530]]
| [[U-Boot for CM-X300 | CM-X300]]
| [[U-Boot for Exeda | Exeda]]
|-
| <linkedimage>
wikipage=U-Boot for CM-T3517
tooltip=CM-T3517 U-Boot documentation
img_src=Image:cm-t3517.jpg
img_width=200px
img_alt=CM-T3517 U-Boot
</linkedimage>

| <linkedimage>
wikipage=U-Boot for CM-A510
tooltip=CM-A510 U-Boot documentation
img_src=Image:A510_CM_top_hq.JPG
img_width=200px
img_alt=CM-A510 U-Boot
</linkedimage>

| <linkedimage>
wikipage=U-Boot for CM-T3530
tooltip=CM-T3530 U-Boot documentation
img_src=Image:T35_CM_top.JPG
img_width=200px
img_alt=CM-T3530 U-Boot
</linkedimage>

| <linkedimage>
wikipage=U-Boot for CM-X300
tooltip=CM-X300 U-Boot documentation
img_src=Image:X300-cm-top-m.jpg
img_width=200px
img_alt=CM-X300 U-Boot
</linkedimage>

| <linkedimage>
wikipage=U-Boot for Exeda
tooltip=Exeda U-Boot documentation
img_src=Image:exeda.jpg
img_width=200px
img_alt=Exeda U-Boot
</linkedimage>

|-
|}

__NOTOC__

{{ChangelogRss| content=

===== 16-Dec-2010, CM-T3517 =====
: U-Boot 2009.11-cm-t3517-1 initial release

===== 17-Nov-2010, CM-A510 =====
: U-Boot 2009.08-cm-a510-1.0 initial release

===== 21-Oct-2010, CM-X300 =====
: U-Boot 2009.03-cm-x300-6.1 release

===== 10-Oct-2010, CM-X300 =====
: [[CM-X300: U-Boot: Firmware Update]] article updated

===== 05-Oct-2010, CM-X300 =====
: [[CM-X300: U-Boot: LCD and Splash screen]] article renamed to [[CM-X300: U-Boot: Custom Features]] and extended

===== 20-Sep-2010, CM-X300 =====
: U-Boot 2009.03-cm-x300-6 release

===== 14-Apr-2010, CM-X300 =====
: U-Boot 2009.03-cm-x300-5 release

===== 28-Mar-2010, CM-X300 =====
: Added [[CM-X300: U-Boot: Disabled Module Recovery]] article

===== 04-Mar-2010, CM-X300 =====
: Added [[CM-X300: U-Boot: LCD and Splash screen]] article

===== 09-Feb-2010, CM-X300 =====
: U-Boot 2009.03-cm-x300-4 release

===== 10-Dec-2009, CM-X300 =====
: Added [[CM-X300: U-Boot: Firmware Development]] article

===== 15-Nov-2009 =====
: Added [[U-Boot images]] format description

===== 02-Sep-2009, CM-X300 =====
: U-Boot 2009.03-cm-x300-3 release

===== 02-Jul-2009, Exeda =====
: Initial release of [[U-Boot for Exeda]] documentation

===== 27-May-2009, CM-X300 =====
: Initial release of [[U-Boot for CM-X300]] documentation

}}

[[Category:U-Boot]]

U-Boot for CM-T3517

2010-12-16T09:39:54Z

Mike:

{{summary|
The CompuLab CM-T3517 module is using U-Boot boot-loader for low-level initializations and operating system loading.
U-Boot is an open source firmware for wide range of embedded systems (e.g. PowerPC, ARM, MIPS, x86, ColdFire, AVR32, NIOS, etc.).
On this page we will discuss only features and use cases related to CompuLab CM-T3517 module.
For more information on U-Boot, please refer to [http://www.denx.de/wiki/U-Boot/WebHome Official U-Boot Homepage]. 

Links to information about U-Boot package for CM-T3517 modules:
* [[CM-T3517: U-Boot: Firmware Overview|Firmware Overview]]
* [[CM-T3517: U-Boot: Firmware Update|Firmware Update]]
* [[U-Boot quick reference]]
* [[U-Boot images]]
* [http://www.denx.de/wiki/U-Boot/Documentation U-Boot documentation]
|cm-t3517.jpg|thumb}}

{{ChangelogRss| content=
* '''16-Dec-2010'''
: Initial release of U-Boot for CM-T3517
: U-Boot 2009.11-cm-t3517-1 supports:
: - USB Host on mini-USB port
: - MMC/SD Card
: - On SoC EMAC Ethernet
: - SMC911x Ethernet chip on SB-T35
: - Onboard NAND chip
: - Green LED
: - System revision in ATAGS
}}

[[Category:U-Boot]]
[[Category:CM-T3517]]

U-Boot for CM-T3530

2010-12-16T09:39:15Z

Mike:

{{summary|
The CompuLab CM-T3530 module is using U-Boot boot-loader for low-level initializations and operating system loading.
U-Boot is an open source firmware for wide range of embedded systems (e.g. PowerPC, ARM, MIPS, x86, ColdFire, AVR32, NIOS, etc.).
On this page we will discuss only features and use cases related to CompuLab CM-T3530 module.
For more information on U-Boot, please refer to [http://www.denx.de/wiki/U-Boot/WebHome Official U-Boot Homepage]. 

Links to information about U-Boot package for CM-T3530 modules:
* [[CM-T3530: U-Boot: Firmware Overview|Firmware Overview]]
* [[CM-T3530: U-Boot: Firmware Update|Firmware Update]]
* [[U-Boot quick reference]]
* [[U-Boot images]]
* [http://www.denx.de/wiki/U-Boot/Documentation U-Boot documentation]
|T35_CM_top.JPG|thumb}}

{{ChangelogRss| content=
===== 24-Dec-2009 =====
: Initial release of U-Boot for CM-T3530
}}

[[Category:U-Boot]]
[[Category:CM-T3530]]

CM-T3517: U-Boot: Firmware Overview

2010-12-16T09:36:35Z

Mike: Redirecting to CM-T3x: U-Boot: Firmware Update

#REDIRECT [[CM-T3x: U-Boot: Firmware Update]]

CM-T3x: U-Boot: Firmware Overview

2010-12-16T09:34:37Z

Mike:

== Introduction ==
This article describes firmware for CM-T3x system-on-module product line. The CM-T3x product line includes the following modules:
* [http://compulab.co.il/t3517/html/t3517-cm-datasheet.htm CM-T3517]
* [http://compulab.co.il/t3530/html/t3530-cm-datasheet.htm CM-T3530]

CM-T3x firmware consists of two components: X-Loader and U-Boot. X-Loader is the bootstrap utility invoked by the boot ROM code of the CPU. X-Loader performs minimal hardware initialization and loads stage two bootloader, namely U-Boot. U-Boot initializes hardware modules necessary for system boot and loads the operating system.

== X-Loader ==
X-Loader resides in the first erase block of the system NAND flash or in a file on MMC/SD card. It is loaded into the CPU internal SRAM immediately after system reset. The CPU internal boot ROM determines what storage media to use in accordance with BOOT_SOURCE signal value (pin 65 of connector P1 on CM-T3x). SB-T35 allows easy switch between NAND and MMC/SD boot.

X-Loader is responsible for initial clock setup, DDR initialization and boot media controller initialization. After basic hardware setup X-Loader loads U-Boot bootloader into the system RAM and transfers control to the U-Boot bootloader.

== U-Boot ==
U-Boot is the stage two bootloader used on CM-T3x. It allows flexible selection of operating system boot modes, provides scripting facilities and command line interface through serial port.

U-Boot resides in the system NAND flash starting from offset 0x80000. In addition, two blocks at offset 0x260000 are used by the U-Boot environment. In case an MMC/SD card is used as boot media, U-Boot binary should be present in card's root directory and named {{filename|u-boot.bin}}.

U-Boot allows booting operating system from the on-board NAND flash, MMC/SD card or from network.
Please consult [[U-Boot quick reference]] and [http://www.denx.de/wiki/U-Boot/Documentation U-Boot project documentation] for U-Boot features and commands description.

== Boot sources ==
CM-T3x can boot either from on-board NAND flash or from MMC/SD card. The boot source can be selected using jumper E6 or button SW1 on SB-T35.
* To boot the system from the on-board NAND flash make sure that jumper E6 is not present.
* To boot the system from the MMC/SD card install jumper E6 before power-on or hold button SW1 during system startup.
Please refer to [[CM-T3530: Linux: Booting from MMC/SD card]] for further details.

== Default NAND flash mapping ==
{| cellpadding="3" border="1" style="border: 1px solid rgb(85, 85, 85); border-collapse: collapse;"
|+ CM-T3x NAND flash mapping
|-
! Offset
! Description
! Size (kilobytes)
|-
| 0x0
| X-Loader
| 512
|-
| 0x80000
| U-Boot
| 640
|-
| 0x120000
| Reserved
| 1280
|-
| 0x260000
| U-Boot environment
| 256
|-
| 0x2a0000
| Linux kernel
| 4096
|-
| 0x6a0000
| Linux filesystem
| remaining NAND flash space
|}

== Know issues ==
* If U-Boot environment variable {{parameter|bootdelay}} is set to 0 or an invalid value, automatic OS boot cannot be stopped.

[[Category:U-Boot|Firmware Overview]]
[[Category:CM-T3517|U-Boot: Firmware Overview]]
[[Category:CM-T3530|U-Boot: Firmware Overview]]

CM-T3x: U-Boot: Firmware Update

2010-12-16T07:37:53Z

Mike:

{{Warning|Failure in CM-T3x firmware update may prevent proper boot from on-board NAND flash. It is recommended to create a [[CM-T3x: Linux: Booting from MMC/SD card|bootable MMC/SD card]] before updating CM-T3x firmware}}

== Introduction ==
This article describes firmware update process for CM-T3x system-on-module product line. The CM-T3x product line includes the following modules:
* [http://compulab.co.il/t3517/html/t3517-cm-datasheet.htm CM-T3517]
* [http://compulab.co.il/t3530/html/t3530-cm-datasheet.htm CM-T3530]

== Preliminary setup ==
* Make sure to power off the CM-T3x evaluation platform
* Connect the host PC to the SB-T35 base-board (connector P12) via the serial cable supplied with the evaluation kit.
* Start terminal emulation software on your PC. Set baud rate to 115200 bps, 8 bit per frame, 1 stop bit, no parity, no flow control.
* Turn on the CM-T3x evaluation system. The U-Boot boot-loader will start and you will get a command prompt.
{{Note|If the boot settings of your CM-T3x are different than default, you may need to press and hold ^C while turning the CM-T3x on, in order to get command prompt.}}
CM-T3x firmware can be updated from an MMC/SD card or using network TFTP download.
Both methods are performed from the U-Boot command line.

CM-T3x Firmware consists of two components: X-Loader and U-Boot. The U-Boot bootloader can be installed and updated independently without updating the existing X-Loader. Please continue to [[CM-T3x: U-Boot: Firmware Update#CM-T3x_U-Boot_Update|CM-T3x U-Boot Update]] section for U-Boot installation instructions.

== CM-T3x X-Loader Update ==
{{Warning|'''X-Loader can be installed only to completely erased NAND flash! The procedure below erases the entire NAND flash!'''}}
=== MMC/SD card ===
* Copy {{filename|x-load.bin.ift}} from [[CM-T3x:_U-Boot:_Firmware_Update#U-Boot packages|U-Boot package for CM-T3x]] to the root directory of the MMC/SD card.
* Insert the MMC/SD card into the SD socket (P13) on SB-T35.
* Start the U-Boot MMC subsystem and check that your storage device is ready and contains the X-Loader binary
<pre>
# mmc init
# fatls mmc 0
</pre>
* Load the X-Loader into memory
<pre>
# fatload mmc 0 80a00000 x-load.bin.ift
</pre>
* Proceed to [[CM-T3x: U-Boot: Firmware Update#Flashing X-Loader|Flashing X-Loader]] section

=== TFTP download ===
* Setup TFTP server
* Put the X-Loader binary in the root directory of TFTP server
* Setup U-Boot networking:
<pre>
# dhcp
</pre>
: for dynamic IP configuration, or
<pre>
# setenv ipaddr <ip address>
# setenv serverip <server ip>
</pre>
: for static IP configuration
* Download the X-Loader to the CM-T3x RAM
<pre>
# tftp 80a00000 x-load.bin.ift
</pre>
* Proceed to [[CM-T3x:_U-Boot:_Firmware_Update#Flashing X-Loader|Flashing X-Loader]] section

=== Flashing X-Loader ===
{{Warning| Do not reset or power off the CM-T3x during the update process! Doing so may result in nand flash corruption!}}
* Flash the X-Loader onto the on-board NAND flash:
<pre>
# nandecc hw
# nand erase
# nand scrub
# nand write 80a00000 0 20000;
</pre>

{{Important|It is essential to install U-Boot immediately after X-Loader update}}

== CM-T3x U-Boot Update ==
=== MMC/SD card ===
* Copy {{filename|u-boot.bin}} from [[CM-T3x:_U-Boot:_Firmware_Update#U-Boot packages|U-Boot package for CM-T3x]] to the root directory of the MMC/SD card.
* Insert the MMC/SD card into the SD socket (P13) on SB-T35.
* Start the U-Boot MMC subsystem and check that your storage device is ready and contains the U-Boot binary
<pre>
# mmc init
# fatls mmc 0
</pre>
* Load the U-Boot into the CM-T3x RAM
<pre>
# fatload mmc 0 80a00000 u-boot.bin
</pre>
* Proceed to [[CM-T3x:_U-Boot:_Firmware_Update#Flashing U-Boot|Flashing U-Boot]] section

=== TFTP download ===
* Setup TFTP server
* Put the U-Boot binary in the root directory of TFTP server
* Setup U-Boot networking:
<pre>
# dhcp
</pre>
: for dynamic IP configuration, or
<pre>
# setenv ipaddr <ip address>
# setenv serverip <server ip>
</pre>
: for static IP configuration
* Download the U-Boot to the CM-T3x RAM
<pre>
# tftp 80a00000 u-boot.bin
</pre>
* Proceed to [[CM-T3x: U-Boot: Firmware Update#Flashing U-Boot|Flashing U-Boot]] section

=== Flashing U-Boot ===
{{Warning| Do not reset or power off the CM-T3x during the update process! Doing so may result in nand flash corruption!}}
* Flash the U-Boot onto the on-board NAND flash:
<pre>
# nandecc sw
# nand erase 80000 60000
# nand write 80a00000 80000 60000
</pre>
* Reset the CM-T3x evaluation platform

== U-Boot packages ==
* [http://www.compulab.co.il/t3517/download/t3517-uboot.zip U-Boot package for CM-T3517]
* [http://www.compulab.co.il/t3530/download/t3530-uboot.zip U-Boot package for CM-T3530]

== See also ==

* [[CM-T3x: U-Boot: Firmware Overview]]
* [[U-Boot quick reference]]
* [[U-Boot images]]
* [[CM-T3530: Linux: Getting started|Getting started with Linux on CM-T3500]]
* [http://www.denx.de/wiki/U-Boot/Documentation U-Boot documentation]
* [http://processors.wiki.ti.com/index.php?title=MMC_Boot_Format SD/MMC format for OMAP3 boot]

[[Category:U-Boot|Firmware Update]]
[[Category:CM-T3517|U-Boot: Firmware Update]]
[[Category:CM-T3530|U-Boot: Firmware Update]]

CM-T3530: U-Boot: Firmware Overview

2010-12-15T13:55:37Z

Mike: CM-T3530: U-Boot: Firmware Overview moved to CM-T3x: U-Boot: Firmware Overview

#REDIRECT [[CM-T3x: U-Boot: Firmware Overview]]

CM-T3517: U-Boot: Firmware Update

2010-12-15T13:52:32Z

Mike: Redirecting to CM-T3x: U-Boot: Firmware Update

#REDIRECT [[CM-T3x: U-Boot: Firmware Update]]

CM-T3530: U-Boot: Firmware Update

2010-12-15T13:20:35Z

Mike: Redirecting to CM-T3x: U-Boot: Firmware Update

#REDIRECT [[CM-T3x: U-Boot: Firmware Update]]

Linux documentation

2010-11-17T09:23:56Z

Mike:

{| style="border: 1px solid #aaaaaa; margin-top: 20px;" width="100%" align="center"
|- style="line-height: 120%; border-bottom: 1px solid #aaaaaa; font-size: 105%; background-color: #eeeeee;"
| [[CM-A510 Linux | CM-A510]]
| [[CM-T3530 Linux | CM-T3530]]
| [[CM-X300 Linux | CM-X300]]
| [[CM-X270 Linux | CM-X270]]
| [[EM-X270 Linux | EM-X270]]
|-

| <linkedimage>
wikipage=CM-A510 Linux
tooltip=CM-A510 Linux documentation
img_src=Image:A510_CM_top_hq.JPG
img_width=200px
img_alt=CM-A510 Linux
</linkedimage>

| <linkedimage>
wikipage=CM-T3530 Linux
tooltip=CM-T3530 Linux documentation
img_src=Image:T35_CM_top.JPG
img_width=200px
img_alt=CM-T3530 Linux
</linkedimage>

| <linkedimage>
wikipage=CM-X300 Linux
tooltip=CM-X300 Linux documentation
img_src=Image:X300-cm-top-m.jpg
img_width=200px
img_alt=CM-X300 Linux
</linkedimage>

| <linkedimage>
wikipage=CM-X270 Linux
tooltip=CM-X270 Linux documentation
img_src=Image:X270-cm-l-top-m.jpg
img_width=200px
img_alt=CM-X270 Linux
</linkedimage>

| <linkedimage>
wikipage=EM-X270 Linux
tooltip=EM-X270 Linux documentation
img_src=Image:X270-em-bot-m.jpg
img_width=200px
img_alt=EM-X270 Linux
</linkedimage>

|-

| colspan="5" |
{| width="100%" align="center"
|- style="line-height: 120%; border-bottom: 1px solid #aaaaaa; font-size: 105%; background-color: #eeeeee;"
| [[CM-iGLX Linux | CM-iGLX]]
| [[SBC-FITPC2 Linux | SBC-FITPC2 ]]
| [[CM-iAM Linux | CM-iAM]]
| [[Exeda Linux | Exeda]]
|-

| <linkedimage>
wikipage=CM-iGLX Linux
tooltip=CM-iGLX Linux documentation
img_src=Image:Iglx-cm-top-m.jpg
img_width=200px
img_alt=CM-iGLX Linux
</linkedimage>

| <linkedimage>
wikipage=SBC-FITPC2 Linux
tooltip=SBC-FITPC2 Linux documentation
img_src=Image:Fitpc2-sb-top-ss.jpg
img_width=200px
img_alt=SBC-FITPC2 Linux
</linkedimage>

| <linkedimage>
wikipage=CM-iAM_Linux
tooltip=CM-iAM Linux documentation
img_src=Image:Cm-iam-top.jpg
img_width=200px
img_alt=CM-iAM Linux
</linkedimage>

| <linkedimage>
wikipage=Exeda Linux
tooltip=Exeda Linux documentation
img_src=Image:exeda.jpg
img_width=200px
img_alt=Exeda Linux
</linkedimage>
|}

|-
|}

__NOTOC__

{{ChangelogRss| content=
===== 28-Oct-2010, CM-A510 =====
: Initial release of Linux kernel and Debian filesystem image for CM-A510

===== 17-Aug-2010, CM-T3530 =====
: Updates for Linux kernel and Angstrom filesystem image for CM-T3530

===== 1-Jun-2010, CM-X300 =====
: Upgrade of Debian example fileystsem image for CM-X300

===== 6-May-2010, CM-iAM =====
: Updates for Ubuntu Linux image for CM-iAM

===== 26-Nov-2009, CM-X300 =====
: Updates for Linux kernel and Debian filesystem image for CM-X300

===== 29-Oct-2009, CM-iAM =====
: Initial release of [[CM-iAM Linux | Linux documentation for CM-iAM]]

===== 30-Aug-2009, SBC-FitPC2 =====
: Initial release of [[SBC-FITPC2 Linux |Linux documentation for SBC-FITPC2]]

===== 25-Jun-2009, CM-X300 =====
: Updates for Linux kernel and Debian filesystem image for CM-X300

===== 23-Jun-2009, Exeda =====
: Initial release of Linux kernel 2.6.30 for Exeda

===== 8-Jun-2009, Exeda =====
: Initial release of Android 1.0 for Exeda

===== 27-May-2009, CM-X300 =====
: Added [[U-Boot for CM-X300]] documentation

===== 29-Dec-2008, EM-X270 =====
: Updates and fixes for Angstrom Linux for EM-X270

===== 23-Nov-2008, CM-X270 =====
: Updates and fixes for Linux kernel 2.6.24

===== 3-Nov-2008, CM-iGLX =====
: Linux kernel updated to 2.6.24
: Added support for GeodeLX video input port
: All Gentoo packages updated to recent versions

===== 19-Aug-2008, CM-X300 =====
: Initial release of Linux package for CM-X300

===== 26-Jun-2008, CM-X270 =====
: Released Linux kernel 2.6.24 for CM-X270
: Updated Debian filesystem image

===== 18-May-2008, CM-X270 =====
: 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]).

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

===== 3-Jan-2008, EM-X270 =====
: 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

===== 26-Dec-2007, CM-X270 =====
: Certain NAND flashes are sensitive to local bus activity. NAND flash driver updated to overcome this limitation.

===== 14-Nov-2007, EM-X270 =====
: Initial release

===== 13-Jun-2007, CM-X270 =====
: Fixed RTC access routines.

===== 28-May-2007, CM-iGLX =====
: 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, CM-iGLX =====
: Initial release of Gentoo for CM-iGLX

===== 6-Feb-2007, CM-X270 =====
: 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, CM-X270 =====
: Make default Debian file system image 512 Mbytes

===== 12-Oct-06, CM-X270 =====
: 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, CM-X270 =====
: Added BGW200 Wireless LAN support for CM-X270L

===== 15-May-06, CM-X270 =====
: 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]]

U-Boot documentation

2010-11-17T09:20:37Z

Mike:

{| style="border: 1px solid #aaaaaa; margin-top: 20px;" width="100%" align="center"
|- style="line-height: 120%; border-bottom: 1px solid #aaaaaa; font-size: 105%; background-color: #eeeeee;"
| [[U-Boot for CM-A510 | CM-A510]]
| [[U-Boot for CM-T3530 | CM-T3530]]
| [[U-Boot for CM-X300 | CM-X300]]
| [[U-Boot for Exeda | Exeda]]
|-
| <linkedimage>
wikipage=U-Boot for CM-A510
tooltip=CM-A510 U-Boot documentation
img_src=Image:A510_CM_top_hq.JPG
img_width=200px
img_alt=CM-A510 U-Boot
</linkedimage>

| <linkedimage>
wikipage=U-Boot for CM-T3530
tooltip=CM-T3530 U-Boot documentation
img_src=Image:T35_CM_top.JPG
img_width=200px
img_alt=CM-T3530 U-Boot
</linkedimage>

| <linkedimage>
wikipage=U-Boot for CM-X300
tooltip=CM-X300 U-Boot documentation
img_src=Image:X300-cm-top-m.jpg
img_width=200px
img_alt=CM-X300 U-Boot
</linkedimage>

| <linkedimage>
wikipage=U-Boot for Exeda
tooltip=Exeda U-Boot documentation
img_src=Image:exeda.jpg
img_width=200px
img_alt=Exeda U-Boot
</linkedimage>

|-
|}

__NOTOC__

{{ChangelogRss| content=

===== 17-Nov-2010, CM-A510 =====
: U-Boot 2009.03-cm-a510-1.0 initial release

===== 21-Oct-2010, CM-X300 =====
: U-Boot 2009.03-cm-x300-6.1 release

===== 10-Oct-2010, CM-X300 =====
: [[CM-X300: U-Boot: Firmware Update]] article updated

===== 05-Oct-2010, CM-X300 =====
: [[CM-X300: U-Boot: LCD and Splash screen]] article renamed to [[CM-X300: U-Boot: Custom Features]] and extended

===== 20-Sep-2010, CM-X300 =====
: U-Boot 2009.03-cm-x300-6 release

===== 14-Apr-2010, CM-X300 =====
: U-Boot 2009.03-cm-x300-5 release

===== 28-Mar-2010, CM-X300 =====
: Added [[CM-X300: U-Boot: Disabled Module Recovery]] article

===== 04-Mar-2010, CM-X300 =====
: Added [[CM-X300: U-Boot: LCD and Splash screen]] article

===== 09-Feb-2010, CM-X300 =====
: U-Boot 2009.03-cm-x300-4 release

===== 10-Dec-2009, CM-X300 =====
: Added [[CM-X300: U-Boot: Firmware Development]] article

===== 15-Nov-2009 =====
: Added [[U-Boot images]] format description

===== 02-Sep-2009, CM-X300 =====
: U-Boot 2009.03-cm-x300-3 release

===== 02-Jul-2009, Exeda =====
: Initial release of [[U-Boot for Exeda]] documentation

===== 27-May-2009, CM-X300 =====
: Initial release of [[U-Boot for CM-X300]] documentation

}}

[[Category:U-Boot]]

Talk:Main Page

2010-11-16T08:50:10Z

Mike: Removing all content from page

Category:CM-A510

2010-11-03T15:26:47Z

Mike: New page: CM-A510

CM-A510

EM-X270: Linux: Angstrom

2010-10-30T15:15:26Z

Mike: Reverted edits by YanVertongen (Talk); changed back to last version by Mike

== Introduction ==

The run-time Linux image for EM-X270 is based on Angstrom Linux 2007.1. The [http://www.compulab.co.il/x270em/download/x270-em-linux.zip CompuLab Linux package for EM-X270] includes ready to run NAND flash image, Linux kernel configuration and source code patches, and OpenEmbedded
configuration files used to build the Angstrom Linux image. The package also features LiveDisk image for easy installation of the
run-time Angstrom Linux on EM-X270.

The default Angstrom Linux image takes less than 50Mbyte of flash space, and includes above 300 software packages. Among them:
* Core system
* X11 Windowing System
* Matchbox desktop manager
* Minimo web browser
* PIM suite
* Phone dialer

The [[Getting started with Linux on EM-X270]] page gives brief introduction on how to setup and start using the run-time Linux image. Here we describe in
more detail package structure and peripheral devices options specific to EM-X270.

== Package contents ==

=== images ===

* {{filename|LiveDisk.zip}} - archive contains files for USB LiveDisk.
* {{filename|em_x270.img.bz2}} - ready to run image for EM-X270 NAND flash.
* {{filename|angstrom-em-x270.tar.bz2}} - archive of root file system

=== kernel ===

* {{filename|2.6.23/uImage-2.6.23-em-x270}} - ready to run Linux kernel 2.6.23 image for EM-X270
* {{filename|2.6.23/linux-2.6.23-em-x270.config}} - Linux kernel 2.6.23 configuration file
* {{filename|2.6.23/linux-2.6.23-em-x270.pacth}} - patch vs. [http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.23.tar.bz2 Linux kernel 2.6.23] with support for EM-X270 peripherals
* {{filename|2.6.26/uImage-2.6.26-em-x270}} - ready to run Linux kernel 2.6.26 image for EM-X270
* {{filename|2.6.26/linux-2.6.26-em-x270.config}} - Linux kernel 2.6.26 configuration file
* {{filename|2.6.26/linux-2.6.26-em-x270.pacth}} - patch vs. [http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.26.tar.bz2 Linux kernel 2.6.26] with support for EM-X270 peripherals
* {{filename|wifi/gspi.ko}} - Marvell GSPI wifi driver for 2.6.26 Linux kernel
* {{filename|wifi/gspi8xxx.ko}} - Marvell GSPI wifi driver for 2.6.26 Linux kernel

=== oe ===

The {{filename|oe}} directory contains configuration files and EM-X270 specific package definition for OpenEmbedded. These files should reside under the OpenEmbedded root on your host system. Please consult [http://wiki.openembedded.net/index.php/Documentation OpenEmbedded documentation] for further details.

* {{filename|build/conf/local.conf}} - configuration file used to build Angstrom Linux image for EM-X270
* {{filename|org.openembedded.stable/conf/machine/cl-xscale.conf}} - machine definition file
* {{filename|org.openembedded.stable/packages/linux/cl-xscale_2.6.23.bb}} - recipe to build Linux kernel for EM-X270
* {{filename|org.openembedded.stable/packages/linux/cl-xscale-2.6.23/}} - files needed to build Linux kernel for EM-X270

=== utilities ===

{{filename|utilities}} directory contains miscellaneous utilities useful for development

* {{filename|create_image.sh}} - the script creates an image compatible with EM-X270 updater application
* {{filename|fixup-angstrom.sh}} - the script used to update several configuration files in the Angstrom Linux image '''before''' deploying the image to the device
* {{filename|install_modules.sh}} - the script builds and then installs kernel modules (used in create_image.sh)
* {{filename|install_utils.sh}} - the script builds utilities, using OE's devshell, and installs them (also used in create_image.sh)
* {{filename|patches/}} - patches used by the fixup-angstrom.sh (also contains firmware for Marvell wifi adapter)
* {{filename|updater/}} - sources of EM-X270 updater application
* {{filename|examples/}} - some application examples for EM-X270
* {{filename|uboot-env/}} - sources of utility for accessing U-Boot environment ({{filename|fw_printenv}}, {{filename|fw_setenv}})

== Package management on EM-X270 ==
Angstrom Linux on EM-X270 includes {{cmd|ipkg}} package manager. It can be run either from command line, or using GUI. Tap "Settings" -> "Package Manager" to start the application, select packages you'd like to install and press "Apply" button.

== EM-X270 specific device options ==
Certain on-board devices may be of particular interest for EM-X270 application developers. We provide here details of their operation in Angstrom Linux for EM-X270.

=== GSM/GPRS modem ===

GSM/GPRS modem is connected to BTUART of PXA270 processor and can be accessed through {{filename|/dev/ttyS1}} device node. In Angstrom Linux for EM-X270, it can be operated either by GSMD daemon and a Dialer front end for voice calls, or PPPD daemon for data connection. At the system startup GSMD is enabled and it it possible to issue voice phone calls using Dialer application. If you'd like to switch to data communications using GPRS, you shoud tap "Other" -> "GPRS". To switch back to voice calls mode tap "Other" -> "GSM".

GSM/GPRS modem voice lines are connected to EM-X270 Audio Codec and can be accessed via the standard ALSA APIs. The '''Phone''' and '''Mono''' controls in {{filename|alsamixer}} are used to control the incoming and outgoing volume respectively.

The data connection with GPRS modem may require update of provider-specific details in {{filename|/etc/ppp/gprs-connect}}, {{filename|/etc/ppp/gprs-options}} and {{filename|/etc/ppp/pap-secrets}} files.

----
'''/etc/ppp/gprs-connect'''
<pre>
TIMEOUT 60
ABORT 'BUSY'
ABORT 'ERROR'
ABORT 'NO CARRIER'
'' 'AT'
OK AT+CGDCONT=1,"IP","internet","0.0.0.0",0,0
OK ATD*99***1#
CONNECT ''
</pre>
----

The string '''"internet"''' in this example containts the APN (Access Point Name ) address of your GPRS provider. Contact your provider to find out what is the right address and username/password to use. The username and password should reside in {{filename|/etc/ppp/pap-secrets}} (both are '''a''' in the below example):

----
'''/etc/ppp/pap-secrets'''
<pre>
# Secrets for authentication using PAP
# client server secret IP addresses
'a' * 'a' *
</pre>
----

It is important to set the '''user''' field of {{filename|/etc/ppp/gprs-options}} to the same username.

=== GPS reciever ===

GPS reciever is connected to STUART of PXA270 processor and can be accessed through {{filename|/dev/ttyS2}} device node.

=== Wireless LAN ===
Wireless LAN on EM-X270 supports 802.11b. Currently Angstrom Linux for EM-X270 does not enable this interface automaticaly.
The driver for wireless LAN chip present on EM-X270 is provided by the chip manufacturer and therefore redistributed by CompuLab in binary form (see {{filename|kernel/wifi}} directory of the Angstrom Linux package). The driver uses chip/bus specific firmware (also redistributed in binary form), which should reside in {{filename|/lib/firmware/}} and is loaded automatically by the driver. The driver is called gspi and can be enabled using

<pre>
echo 1 > /sys/devices/platform/wlan/pwr_on
modprobe gspi8xxx
iwconfig eth1 essid <your_ESSID>
</pre>

You can use Linux standard {{cmd|iwconfig}}, {{cmd|iwscan}}, {{cmd|iwevent}}, {{cmd|iwgetid}}, {{cmd|iwlist}}, {{cmd|iwpriv}}, {{cmd|iwspy}}, {{cmd|wpa_supplicant}} utilities.

=== Bluetooth ===
EM-X270 has an on board CSR BlueCore4-ROM chipset with an on chip antenna. Currently Linux Kernel default hci_usb driver is used along with BlueZ 3.23 to operate the device. For various setup configurations and instructions please consult [http://wiki.bluez.org/wiki/HOWTO Official Linux Bluetooth HOWTOs page].

=== VGA display ===
EM-X270 with EB-X270 extender board supports connection of standard VGA display. To direct graphics output to VGA append {{parameter|1="display=vga"}} to kernel command line. Tap keyboard icon on the panel, tap "Other" -> "Terminal", and in the terminal window do

<pre>
su
cmd_line=`fw_printenv boot_angstrom | cut -d= -f2- | \
sed 's/setenv bootargs/setenv bootargs display=vga/'`
fw_setenv boot_angstrom $cmd_line
</pre>

If you would like to use mouse rather than touchscreen, you should edit the {{filename|/etc/matchbox/session}} file and change {{parameter|"-use_cursor no"}} to {{parameter|"-use_cursor yes"}}

== Power management ==
Angstrom Linux for EM-X270 allows user to take full advantage of EM-X270 flexible power management capabilities. It supports very low power sleep mode, provides abitity to swtich on and off certain units power and implements charging supervision mechanism for battery powered operation mode.

=== Battery Charger Management ===
When EM-X270 operates as a battery powered device, battery monitoring and charging is supervised by the Linux kernel. It detects insertion and removal of USB OTG connector and performs operations necessary to ensure safe battery charging.

=== On-board Devices Power Control ===
The on-board WiFi interface, GPS reciever and cellular voice and GSM/GPRS modem can be switched on and off on the fly. Linux kernel for EM-X270 defines *`pwr_on`* attribute for these devices. The attributes can be accessed via sysfs:

<pre>
/sys/devices/platform/wlan/pwr_on
/sys/devices/platform/gps/pwr_on
/sys/devices/platform/gprs/pwr_on
</pre>

Writing '''1''' to appropriate attribute file will enable the device power and writng '''0''' will disable it. For instance, to enable the GSM/GPRS unit:

<pre>
echo 1 > /sys/devices/platform/gprs/pwr_on
</pre>

== OpenEmbedded ==

Angstrom Linux images for EM-X270 are built with OpenEmbedded development environment. If you would like to build custom image you need to install the OpenEmbedded environment. [http://www.openembedded.org/index.php/Getting_Started Getting Started] page of OpenEmbedded documentation describes the installation process.

Here we assume that you followed the [http://www.openembedded.org/index.php/Getting_Started Getting Started] instructions and you have the same directory structure.

After you completed the installation of OpenEmbedded, you need to configure it to be able to build images for EM-X270. Recent versions of OpenEmbedded support partially EM-X270. So you may have some of the settings described below already setup.

To configure OpenEmbedded you need to place the current build configuration file {{filename|1=local.conf}} from CompuLab package to {{filename|1=/stuff/build/conf/local.conf}}:

<pre>
cp /path/to/x270-em-linux/oe/build/conf/local.conf /stuff/build/conf
</pre>

and the machine configuration file {{filename|cl-xscale.conf}} from CompuLab package to {{filename|/stuff/your branch/conf/machine/cl-xscale.conf}}

<pre>
cp /path/to/x270-em-linux/oe/org.openembedded.stable/conf/machine/cl-xscale.conf /stuff/your branch/conf/machine
</pre>

or you can use all OpenEmbedded related files from [http://www.compulab.co.il/x270em/download/x270-em-linux.zip CompuLab Linux package for EM-X270]:

<pre>
cp -r /path/to/x270-em-linux/oe/* /stuff/
</pre>

Now you are ready to build Linux images for EM-X270:

<pre>
cd /stuff/build
bitbake x11-image
</pre>

After some time the image will be created and put into {{filename|1=/stuff/build/tmp/deploy/glibc/images/cl-xscale}} directory. Default configuration creates two types of images: '''tar''', and '''jffs2'''. The '''jffs2''' image can be transfered to the EM-X270 on-board NAND flash. The '''tar''' archive can be extracted to some directory on the host workstation, and this directory can be used as networked root filesystem for the device.

== Known problems and limitations ==

== See also ==
* [[Getting started with Linux on EM-X270]]
* [http://www.kernel.org The Linux Kernel Archives]
* [http://www.arm.linux.org.uk/ The ARM Linux Project]
* [http://www.linux-mtd.infradead.org/ Memory Technology Device (MTD) Subsystem for Linux]
* [http://www.angstrom-distribution.org Angstrom Distribution]
* [http://www.openembedded.org OpenEmbedded]
* [http://pokylinux.org Poky Linux]

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

CM-X300: U-Boot: Firmware Development

2010-10-19T16:01:50Z

Mike: Reverted edits by Bettytaylor23 (Talk); changed back to last version by Grinberg

== Overview ==

Compulab CM-X300 is shipped with built-in firmware, which deals with initial module power-up and initialization procedures.
The firmware also provides a command line interface for Operating System or user program installation and loading.

This article describes the CM-X300 firmware structure, firmware assembly process and provides recommendations for testing U-Boot customization.
{{Note|The target audience of this article are developers, who need to alter the CM-X300 U-Boot behavior}}

== CM-X300 firmware structure ==
CM-X300 firmware consists of three main parts:
* [[CM-X300: U-Boot: Firmware Development#Marvell_Non_Trusted_Image_Module_(NTIM)|Marvell Non Trusted Image Module (NTIM)]]
* [[CM-X300: U-Boot: Firmware Development#Marvell_Non_Trusted_OEM_Boot_Module_(OBM)|Marvell Non Trusted OEM Boot Module (OBM)]]
* [[CM-X300: U-Boot: Firmware Development#U-Boot_for_CM-X300_module|U-Boot for CM-X300 module]]
In the default CM-X300 firmware image, all three binaries are built, assembled and tested at CompuLab.
Latest versions of ready to run CM-X300 firmware images are available at [http://www.compulab.co.il/x300/html/x300-developer.py Developer Resources for CM-X300 & SB-X300] web page.

=== Marvell Non Trusted Image Module (NTIM) ===
NTIM is a packed structure (table), which describes the images involved in the PXA3XX boot process.
NTIM must be created each time {{filename|cm-x300-firmware}} is built. 
In order to build the NTIM binary image it is necessary to have the OBM and U-Boot binaries and a Key file with NTIM description.
Building of the NTIM binary image is done by the {{cmd|ntbb}} (non-trusted boot builder) utility. 
The default command line for {{cmd|ntbb}} utility is:
<pre>
$ ./ntbb -v -m 1 -r <Key file name>
</pre>
Both {{cmd|ntbb}} utility and Key file can be obtained from CompuLab.

=== Marvell Non Trusted OEM Boot Module (OBM) ===
OBM is the first boot loader software that runs on the PXA3XX cpu after power on and the internal PXA3XX Boot ROM initializations. It performs low level hardware initialization and copies U-Boot from NAND flash to CM-X300 RAM. 
OBM is a proprietary software and can be distributed in binary form only.

=== U-Boot for CM-X300 module ===

U-Boot for CM-X300 is the last part of the CM-X300 firmware and it is the only part of CM-X300 firmware that could be altered by a user.
Upon its start, U-Boot assumes that it is already in the system's RAM and does not relocate itself. U-Boot initializes CM-X300 peripheral devices, such as PMIC, serial port, network and USB. 
U-Boot source code used for building CM-X300 firmware can be obtained from CompuLab on request.

== CM-X300 firmware assembly ==

All three binary images described above are assembled into one file ({{filename|cm-x300-firmware}}), to avoid errors during firmware update process.
The following command sequence is used:
* Prepare the NTIM table:
<pre>
$ ./ntbb -v -m 1 -r CM-X300L-image.txt
</pre>
* Create empty {{filename|cm-x300-firmware}} file and fill it with ''0xff'':
<pre>
$ cat > ff.pl <<EOF
> open(OUT, ">", "cm-x300-firmware");
> \$data = 0xff;
> binmode(OUT);
> for (\$i = 0; \$i < 0x80000; \$i++) {
> print OUT pack('c', \$data);
> }
> EOF
$ perl ff.pl
</pre>

* Copy all the binary images with offsets defined in {{filename|CM-X300L-image.txt}}:
<pre>
$ dd if=NTIM_X300L.bin of=cm-x300-firmware conv=notrunc
$ dd if=MHL_wince_NTOBM.bin of=cm-x300-firmware conv=notrunc bs=128k seek=1
$ dd if=u-boot.bin of=cm-x300-firmware conv=notrunc bs=128k seek=2
</pre>

After completion of the above process {{filename|cm-x300-firmware}} file contains ready CM-X300 firmware image, that can be flashed into NAND as described in [[CM-X300: U-Boot: Firmware Update|Firmware Update]] article. 
The above sequence is available in a sample [[media:build-firmware-sample.sh|script]].

== Testing U-Boot customizations ==
During normal operation U-Boot is stored in the CM-X300 NAND flash as a part of the CM-X300 firmware. U-Boot development and testing requires frequent updates of the U-Boot bootloader and therefore of the entire CM-X300 firmware. This approach has two significant drawbacks:
* Multiple erases significantly shorten lifetime of vital blocks in the CM-X300 NAND flash.
* Buggy U-Boot build or badly formed firmware can result in disabled CM-X300 module.

=== Recommended testing solution ===

The recommended way to test U-Boot customizations is to load U-Boot into CM-X300 RAM and test it thoroughly before overwriting the working version. 
Use the following steps:
* In the file {{filename|/path/to/u-boot/board/cmx300/config.mk}} change the value of {{parameter|TEXT_BASE}} variable to {{parameter|0x80200000}}. This is the new memory location of your U-Boot under test.
* Compile U-Boot and put the {{filename|u-boot.bin}} file to TFTP root directory or USB thumb drive.
* Power up CM-X300 and wait until the working U-Boot version has started.
* For network {{cmd|tftp}} download:
<pre>
> setenv ipaddr <ip address for CM-X300>
> setenv serverip <TFTP server ip address>
> tftp 0x80200000 u-boot.bin
</pre>
* Or for USB thumb drive:
<pre>
> usb start
> fatload usb 0 0x80200000 u-boot.bin
</pre>
* Start the test U-Boot version:
<pre>
> go 0x80200000
</pre>
* If U-Boot has started normally, continue with the testing, else fix the problem and start over.
{{Warning|After finishing all the tests, and before assembling the CM-X300 firmware, switch back the {{parameter|TEXT_BASE}} value to its default: {{parameter|0x83900000}}, otherwise firmware update will result in disabled CM-X300 module.}}

== Known issues ==
=== Cross-Compiler issues ===
U-Boot compilation process is very sensitive and highly dependent on cross-compiler. It is possible that certain cross-compilers fail to generate bootable code out of U-Boot sources. 
CompuLab recommended cross-compiler and build tool chain is [http://www.codesourcery.com/sgpp/lite/arm/portal/release324 Sourcery G++ Lite 2008q1-126 for ARM GNU/Linux].

== See Also ==

* [[U-Boot quick reference]]
* [[U-Boot images]]
* [[CM-X300: U-Boot: Firmware Update]]
* [[CM-X300: U-Boot: Disabled Module Recovery]]
* [http://www.denx.de/wiki/U-Boot/Documentation U-Boot documentation]

[[Category:U-Boot|Firmware Development]]
[[Category:CM-X300|U-Boot: Firmware Development]]

U-Boot for CM-X300

2010-09-20T15:12:01Z

Mike:

{{summary|
The CompuLab CM-X300 module is using U-Boot boot-loader for low-level initializations and operating system loading.
U-Boot is an open source firmware for wide range of embedded systems (e.g. PowerPC, ARM, MIPS, x86, ColdFire, AVR32, NIOS, etc.).
On this page we will discuss only features and use cases related to CompuLab CM-X300 module.
For more information on U-Boot, please refer to [http://www.denx.de/wiki/U-Boot/WebHome Official U-Boot Homepage]. 
The most recent CompuLab U-Boot version for CM-X300 is checked out from '''v2009.03''' of [http://git.denx.de/?p=u-boot.git Das U-Boot repository] and can be obtained from [http://www.compulab.co.il/x300/html/x300-developer.py CompuLab website] in binary form. CompuLab U-Boot source will be provided on request. 

Links to information about U-Boot package for CM-X300 modules:
* [[CM-X300: U-Boot: Firmware Update|Firmware Update]]
* [[CM-X300: U-Boot: Firmware Development|Firmware Development]]
* [[CM-X300: U-Boot: Disabled Module Recovery|Disabled Module Recovery]]
* [[CM-X300: U-Boot: Custom Features|Custom Features]]
* [[U-Boot quick reference]]
* [[U-Boot images]]
* [http://www.denx.de/wiki/U-Boot/Documentation U-Boot documentation]
|X300-cm-top-m.jpg|thumb}}

__NOTOC__

{{ChangelogRss| content=
===== 20-Sep-2010 =====
: U-Boot 2009.03-cm-x300-6 release
: - Added MMC/SD card support
: - Added Alternative Boot Button handling
: - Added custom GPIO setting
: - Improved PM and PI2C handling

===== 14-Apr-2010 =====
: U-Boot 2009.03-cm-x300-5 release
: - Added CPU frequency change support
: - Added "silent" option support
: - Improved Ethernet performance

===== 28-Mar-2010 =====
: Added [[CM-X300: U-Boot: Disabled Module Recovery]] article

===== 04-Mar-2010 =====
: Added [[CM-X300: U-Boot: LCD and Splash screen]] article

===== 09-Feb-2010 =====
: U-Boot 2009.03-cm-x300-4 release
: - Added DRAM size detection
: - Added LCD and Splash screen support
: - Added support for resume from S3/D4/C4 low power mode
: - Added I2C and PCA953X GPIO chip driver
: - Added support for USB port3 on modules without "W" option
: - Disabled debug output to FFUART
: - Fixed MFPR setup for PXA310
: - Fixed VCC Core voltage configuration

===== 10-Dec-2009 =====
: Added [[CM-X300: U-Boot: Firmware Development]] article

===== 2-Sep-2009 =====
: U-Boot 2009.03-cm-x300-3 release
: - Added PXA310 USB support
: - Green LED (for CM-X300 revision 1.3 and higher)

===== 27-May-2009 =====
: Initial release of [[U-Boot for CM-X300]] documentation
: U-Boot 2009.03-cm-x300-2 release supports:
: - DA9030 power management chip
: - DM9000A Ethernet chip
: - PXA300 USB
: - Onboard NAND chip
: - Green LED (up to CM-X300 revision 1.2)
: - System revision and serial number in ATAGS
}}

[[Category:U-Boot]]
[[Category:CM-X300]]

U-Boot documentation

2010-09-20T15:11:41Z

Mike:

{| style="border: 1px solid #aaaaaa; margin-top: 20px;" width="100%" align="center"
|- style="line-height: 120%; border-bottom: 1px solid #aaaaaa; font-size: 105%; background-color: #eeeeee;"
| [[U-Boot for CM-T3530 | CM-T3530]]
| [[U-Boot for CM-X300 | CM-X300]]
| [[U-Boot for Exeda | Exeda]]
|-
| <linkedimage>
wikipage=U-Boot for CM-T3530
tooltip=CM-T3530 U-Boot documentation
img_src=Image:T35_CM_top.JPG
img_width=200px
img_alt=CM-T3530 U-Boot
</linkedimage>

| <linkedimage>
wikipage=U-Boot for CM-X300
tooltip=CM-X300 U-Boot documentation
img_src=Image:X300-cm-top-m.jpg
img_width=200px
img_alt=CM-X300 U-Boot
</linkedimage>

| <linkedimage>
wikipage=U-Boot for Exeda
tooltip=Exeda U-Boot documentation
img_src=Image:exeda.jpg
img_width=200px
img_alt=Exeda U-Boot
</linkedimage>

|-
|}

__NOTOC__

{{ChangelogRss| content=
===== 20-Sep-2010, CM-X300 =====
: U-Boot 2009.03-cm-x300-6 release

===== 14-Apr-2010, CM-X300 =====
: U-Boot 2009.03-cm-x300-5 release

===== 28-Mar-2010, CM-X300 =====
: Added [[CM-X300: U-Boot: Disabled Module Recovery]] article

===== 04-Mar-2010, CM-X300 =====
: Added [[CM-X300: U-Boot: LCD and Splash screen]] article

===== 09-Feb-2010, CM-X300 =====
: U-Boot 2009.03-cm-x300-4 release

===== 10-Dec-2009, CM-X300 =====
: Added [[CM-X300: U-Boot: Firmware Development]] article

===== 15-Nov-2009 =====
: Added [[U-Boot images]] format description

===== 02-Sep-2009, CM-X300 =====
: U-Boot 2009.03-cm-x300-3 release

===== 02-Jul-2009, Exeda =====
: Initial release of [[U-Boot for Exeda]] documentation

===== 27-May-2009, CM-X300 =====
: Initial release of [[U-Boot for CM-X300]] documentation

}}

[[Category:U-Boot]]

CM-T3530: Linux: Known Issues

2010-08-17T10:15:19Z

Mike:

{{IssueCategory|Graphics|
* LCD display sometimes fails to resume after being blanked
* The "Exquisite" splashscreen utility conflicts with getty on tty1 and dumps a lot of error messages to the console. These errors can be easily ignored.
}}

{{IssueCategory|Peripherals|
* No hotplug on USB ports connected to SB-T35 USB Hub (connector P17) with default kernel binary
:'''Workaround 1:''' append '''usbcore.autosuspend <nowiki>=</nowiki> -1''' to the kernel command line
:'''Workaround 2:''' connect low/full speed USB devices to P17 connector '''before''' booting CM-T3530. Use P21 connector for hotplugable high speed USB devices
}}

[[Category:Linux|Known issues]]
[[Category:CM-T3530|Linux: Known issues]]

Linux documentation

2010-08-17T08:39:28Z

Mike:

{| style="border: 1px solid #aaaaaa; margin-top: 20px;" width="100%" align="center"
|- style="line-height: 120%; border-bottom: 1px solid #aaaaaa; font-size: 105%; background-color: #eeeeee;"
| [[CM-T3530 Linux | CM-T3530]]
| [[CM-X300 Linux | CM-X300]]
| [[CM-X270 Linux | CM-X270]]
| [[EM-X270 Linux | EM-X270]]
|-

| <linkedimage>
wikipage=CM-T3530 Linux
tooltip=CM-T3530 Linux documentation
img_src=Image:T35_CM_top.JPG
img_width=200px
img_alt=CM-T3530 Linux
</linkedimage>

| <linkedimage>
wikipage=CM-X300 Linux
tooltip=CM-X300 Linux documentation
img_src=Image:X300-cm-top-m.jpg
img_width=200px
img_alt=CM-X300 Linux
</linkedimage>

| <linkedimage>
wikipage=CM-X270 Linux
tooltip=CM-X270 Linux documentation
img_src=Image:X270-cm-l-top-m.jpg
img_width=200px
img_alt=CM-X270 Linux
</linkedimage>

| <linkedimage>
wikipage=EM-X270 Linux
tooltip=EM-X270 Linux documentation
img_src=Image:X270-em-bot-m.jpg
img_width=200px
img_alt=EM-X270 Linux
</linkedimage>

|-

| colspan="4" |
{| width="100%" align="center"
|- style="line-height: 120%; border-bottom: 1px solid #aaaaaa; font-size: 105%; background-color: #eeeeee;"
| [[CM-iGLX Linux | CM-iGLX]]
| [[SBC-FITPC2 Linux | SBC-FITPC2 ]]
| [[CM-iAM Linux | CM-iAM]]
| [[Exeda Linux | Exeda]]
|-

| <linkedimage>
wikipage=CM-iGLX Linux
tooltip=CM-iGLX Linux documentation
img_src=Image:Iglx-cm-top-m.jpg
img_width=200px
img_alt=CM-iGLX Linux
</linkedimage>

| <linkedimage>
wikipage=SBC-FITPC2 Linux
tooltip=SBC-FITPC2 Linux documentation
img_src=Image:Fitpc2-sb-top-ss.jpg
img_width=200px
img_alt=SBC-FITPC2 Linux
</linkedimage>

| <linkedimage>
wikipage=CM-iAM_Linux
tooltip=CM-iAM Linux documentation
img_src=Image:Cm-iam-top.jpg
img_width=200px
img_alt=CM-iAM Linux
</linkedimage>

| <linkedimage>
wikipage=Exeda Linux
tooltip=Exeda Linux documentation
img_src=Image:exeda.jpg
img_width=200px
img_alt=Exeda Linux
</linkedimage>
|}

|-
|}

__NOTOC__

{{ChangelogRss| content=
===== 17-Aug-2010, CM-T3530 =====
: Updates for Linux kernel and Angstrom filesystem image for CM-T3530

===== 1-Jun-2010, CM-X300 =====
: Upgrade of Debian example fileystsem image for CM-X300

===== 6-May-2010, CM-iAM =====
: Updates for Ubuntu Linux image for CM-iAM

===== 26-Nov-2009, CM-X300 =====
: Updates for Linux kernel and Debian filesystem image for CM-X300

===== 29-Oct-2009, CM-iAM =====
: Initial release of [[CM-iAM Linux | Linux documentation for CM-iAM]]

===== 30-Aug-2009, SBC-FitPC2 =====
: Initial release of [[SBC-FITPC2 Linux |Linux documentation for SBC-FITPC2]]

===== 25-Jun-2009, CM-X300 =====
: Updates for Linux kernel and Debian filesystem image for CM-X300

===== 23-Jun-2009, Exeda =====
: Initial release of Linux kernel 2.6.30 for Exeda

===== 8-Jun-2009, Exeda =====
: Initial release of Android 1.0 for Exeda

===== 27-May-2009, CM-X300 =====
: Added [[U-Boot for CM-X300]] documentation

===== 29-Dec-2008, EM-X270 =====
: Updates and fixes for Angstrom Linux for EM-X270

===== 23-Nov-2008, CM-X270 =====
: Updates and fixes for Linux kernel 2.6.24

===== 3-Nov-2008, CM-iGLX =====
: Linux kernel updated to 2.6.24
: Added support for GeodeLX video input port
: All Gentoo packages updated to recent versions

===== 19-Aug-2008, CM-X300 =====
: Initial release of Linux package for CM-X300

===== 26-Jun-2008, CM-X270 =====
: Released Linux kernel 2.6.24 for CM-X270
: Updated Debian filesystem image

===== 18-May-2008, CM-X270 =====
: 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]).

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

===== 3-Jan-2008, EM-X270 =====
: 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

===== 26-Dec-2007, CM-X270 =====
: Certain NAND flashes are sensitive to local bus activity. NAND flash driver updated to overcome this limitation.

===== 14-Nov-2007, EM-X270 =====
: Initial release

===== 13-Jun-2007, CM-X270 =====
: Fixed RTC access routines.

===== 28-May-2007, CM-iGLX =====
: 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, CM-iGLX =====
: Initial release of Gentoo for CM-iGLX

===== 6-Feb-2007, CM-X270 =====
: 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, CM-X270 =====
: Make default Debian file system image 512 Mbytes

===== 12-Oct-06, CM-X270 =====
: 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, CM-X270 =====
: Added BGW200 Wireless LAN support for CM-X270L

===== 15-May-06, CM-X270 =====
: 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]]

CM-T3530 Linux

2010-08-17T08:39:15Z

Mike:

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

CompuLab Linux support for CM-T3530 includes modifications of [[CM-T3530: Linux: Kernel|Linux kernel]] and an [[CM-T3530: Linux: Angstrom|example file system image]] based on [http://www.angstrom-distribution.org Angstrom Linux]. It is possible to use other embedded Linux distributions and environments with CM-T3530. The CM-T3530 platform is supported in [http://www.openembedded.org OpenEmbedded]. [http://www.debian.org/ports/arm/ ARM Debian] and [http://www.ubuntu.com/products/whatisubuntu/arm ARM Ubuntu] ports should also work on CM-T3530.
|T35_CM_top.JPG|thumb}}
{{Resources Linux
|* [[CM-T3530: Linux: Getting started|Getting started with Linux on CM-T3530]]
* [[CM-T3530: Linux: Angstrom|Angstrom Linux for CM-T3530]]
* [[U-Boot for CM-T3530]]
|* [[CM-T3530: Linux: Kernel|Linux Kernel for CM-T3530]]
* [[Linux Development for ARM modules]]
* [[CM-T3530:_Linux:_Building_images|Building Linux images for CM-T3530]]
|*[[Support]]
* [[CM-T3530: Linux: Known Issues|Known Issues]]
}}

{{ChangelogRss| content=

===== 17-Aug-2010: =====
: Linux kernel 2.6.32 for CM-T3530 updates
:- Added OTG support
:- Added battery monitoring support
:- Added video capture support
:- Added power management support
: Angstrom Linux image updates
:- Added ALSA mixer default state
:- Added support for video decoding

===== 23-Dec-2009: =====
: Initial release of Angstrom Linux for CM-T3530
}}

[[Category:Linux]]
[[Category:CM-T3530]]

CM-T3530: Linux: Power management

2010-08-17T08:38:51Z

Mike:

== Overview ==
The Linux kernel for CM-T3530 may be built with support for very low power sleep mode and dynamic frequency scaling.
{{Important|Use {{filename|cm_t35_pm_defconfig}} kernel configuration file to build the Linux kernel with enabled power management features.}}

== Frequency scaling ==
The Linux kernel for CM-T3530 utilizes [http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=tree;f=Documentation/cpu-freq;hb=HEAD cpu-freq] framework for dynamic frequency scaling.

The CPU frequency can be changed on the fly using the following commands:
echo userspace > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo <frequency> > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed

The {{parameter|frequency}} should be specified in MHz.

== Suspend to RAM ==
The Linux kernel for CM-T3530 supports very low power sleep mode. Use the following commands to suspend the system:

mount -t debugfs debug /sys/kernel/debug/
echo <wakeup timeout> /sys/kernel/debug/pm_debug/wakeup_timer_seconds
echo 1 > /sys/kernel/debug/pm_debug/enable_off_mode
echo 1 > /sys/kernel/debug/pm_debug/voltage_off_while_idle
echo disabled > /sys/devices/platform/serial8250/power/wakeup
echo disabled > /sys/devices/platform/serial8250.0/power/wakeup
echo disabled > /sys/devices/platform/serial8250.1/power/wakeup
echo disabled > /sys/devices/platform/serial8250.2/power/wakeup
echo mem > /sys/power/state

== Limitations ==
* The only wake-up source is the internal OMAP3 timer
* The USB host driver should be compiled as loadable kernel module. It must be unloaded to allow the system enter the sleep mode.
* The USB OTG driver should be excluded from the kernel
* The video capture drivers should be excluded from the kernel

== See also ==
* [http://elinux.org/OMAP_Power_Management OMAP Power Management]

[[Category:Linux|Power Management]]
[[Category:CM-T3530|Linux: Power Management]]

CM-T3530: Linux: Angstrom

2010-08-17T07:53:36Z

Mike:

== Introduction ==

The example run-time Linux filesystem image for CM-T3530 is based on Angstrom Linux 2009. The [http://www.compulab.co.il/t3530/download/t3530-linux.zip CompuLab Linux package for CM-T3530] includes ready to run NAND flash image, Linux kernel configuration and source code patches, and OpenEmbedded configuration files used to build the Angstrom Linux filesystem image.

The default Angstrom Linux image takes approximately 250 megabytes of flash space, and includes more than 1000 software packages. Among them:
* Core system
* X11 Windowing System
* Enlightment E17 desktop manager
* Firefox and Midory web browsers
* Office applications
* GIMP
* Totem, MPlayer and omapfbplay media players

The [[CM-T3530: Linux: Getting started|Getting started with Linux on CM-T3530]] page provides a brief introduction on how to install the run-time Linux image. This article describes package structure and peripheral device options specific to the CM-T3530.

== Package contents ==

=== version.txt ===
The contents of the {{filename|version.txt}} identifies the package version.

=== images ===
* {{filename|Angstrom-image.ubi}} - ready to run Angstrom Linux image for installation onto CM-T3530 NAND
* {{filename|uImage-cm-t35.bin}} - kernel image binary for installation onto CM-T3530 NAND
* {{filename|Angstrom-image.tar.bz2}} - archive of root file system
* {{filename|bootscr.img}} - U-Boot script used for image installation
* {{filename|kernel.img}} - Kernel image required for NAND image installation
* {{filename|ramdisk.img}} - Ramdisk image required for NAND image installation

=== kernel ===
* {{filename|uImage-2.6.32-omap1-cm-t35.bin}} - ready to run Linux kernel 2.6.32-omap1 for CM-T3530
* {{filename|linux-2.6.32-omap1-cm-t35.defconfig}} - Linux kernel 2.6.32-omap1 configuration file
* {{filename|linux-2.6.32-omap1-cm-t35.pm.defconfig}} - Linux kernel 2.6.32-omap1 configuration file with enabled power management features
* {{filename|linux-2.6.32-omap1-cm-t35.patch}} - patch vs. [http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git Linux-omap kernel 2.6.32] with support for CM-T3530 peripherals

=== oe ===
The {{filename|oe}} directory contains configuration files and CM-T3530 specific package definition for OpenEmbedded.

* {{filename|local.conf}} - configuration file used to build Angstrom Linux image for CM-T3530. This file should be placed in {{filename|${OEBASE}/build/conf}} directory.
* {{filename|cm-t35.patch}} - CM-T3530 specific additions to OpenEmbedded.
* {{filename|base-revision}} - specifies revision of [http://cgit.openembedded.org/cgit.cgi/openembedded/log/ OpenEmbedded git tree] used as a baseline for CM-T3530 patches generation.

=== utilities ===

{{filename|utilities}} directory contains miscellaneous utilities useful for development

* {{filename|first_boot.scr}} - U-Boot script for booting kernel and ramdisk from MMC/SD card or network.
* {{filename|tftpd32.zip}} - TFTP server for Windows users
* {{filename|capture}} - simple video capture example

== Using Angstrom Linux on CM-T3530 ==
=== Display options ===
CM-T3530 evaluation platform has four video output interfaces: LCD, DVI, LVDS and TV-out. Default configuration of Angstrom Linux for CM-T3530 uses Toppoly LCD supplied with the evaluation kit as primary video output. It is possible to switch between LCD and DVI interfaces on the fly. TV-out can be used simultaneously with LCD or DVI interface.

Linux implementation of the OMAP3 display subsystem is described in detail in {{filename|[http://gitorious.org/linux-omap-dss2/linux/blobs/master/Documentation/arm/OMAP/DSS Documentation/arm/OMAP/DSS]}} file in the Linux kernel source tree.

==== Display resolutions ====
* The Toppoly LCD supplied with CM-T3530 evaluation kit supports 480x640 resolution with 18 bits per color
* DVI output can be configured for standard resolutions using kernel command line parameter {{parameter|omapfb.mode}}:
*: 1024x768 - omapfb.mode=dvi:1024x768-24@60
*: 800x600 - omapfb.mode=dvi:800x600-24@60
*: 640x480 - omapfb.mode=dvi:640x480-24@60
* TV-out supports PAL and NTSC standards

==== Examples ====
===== Switch from LCD to DVI =====
<pre>
mgr0=/sys/devices/platform/omapdss/manager0
lcd=/sys/devices/platform/omapdss/display0
dvi=/sys/devices/platform/omapdss/display1
fb0=/sys/class/graphics/fb0

w=`cat $dvi/timings | cut -d "," -f 2 | cut -d "/" -f 1`
h=`cat $dvi/timings | cut -d "," -f 3 | cut -d "/" -f 1`

echo "0" > $lcd/enabled
echo "" > $mgr0/display
fbset -fb /dev/fb0 -xres $w -yres $h -vxres $w -vyres $h
# at this point you have to switch the dvi/lcd dip-switch from the omap board
echo "dvi" > $mgr0/display
echo "1" > $dvi/enabled
</pre>

===== Clone GFX overlay to LCD and TV =====
<pre>
ovl0=/sys/devices/platform/omapdss/overlay0
ovl1=/sys/devices/platform/omapdss/overlay1
tv=/sys/devices/platform/omapdss/display2
fb0=/sys/class/graphics/fb0
fb1=/sys/class/graphics/fb1

w=`cat $tv/timings | cut -d "," -f 2 | cut -d "/" -f 1`
h=`cat $tv/timings | cut -d "," -f 3 | cut -d "/" -f 1`

echo "0" > $ovl0/enabled
echo "0" > $ovl1/enabled

echo "" > $fb1/overlays
echo "0,1" > $fb0/overlays

echo "$w,$h" > $ovl1/output_size
echo "tv" > $ovl1/manager

echo "1" > $ovl0/enabled
echo "1" > $ovl1/enabled

echo "1" > $tv/enabled
</pre>

===== Switch TV-out from PAL to NTSC =====
<pre>
tv=/sys/devices/platform/omapdss/display2
echo "0" $tv/enabled
echo "ntsc" $tv/timings
echo "1" $tv/enabled
</pre>

=== 3D Demos ===
Angstrom Linux for CM-T3530 includes OpenGLES libraries and 3D demos. OMAP3 3D support is limited to 16-bit colors, therefore it is necessary to ensure that display subsystem has proper color mode configuration. For example for 1024x768 resolution the {{parameter|omapfb.mode}} should be set to '''omapfb.mode=dvi:1024x768-16@60'''.

The OpenGLES demos can be found in {{filename|/usr/demos/}} directory in the target filesystem.

=== Video playback ===
Angstrom Linux for CM-T3530 supports playback of MPEG2, MPEG4 and H.264 video formats.
For further information regarding video playback, please refer to [[CM-T3530: Linux: Video playback|Video playback]] article.

=== GPIO access ===
Linux provides simple and convenient GPIO access via {{filename|sysfs}} interface. A GPIO should be requested using {{filename|/sys/class/gpio/export}}. After the GPIO is exported it is possible to change its direction and value using {{filename|/sys/class/gpio/gpioX/direction}} and {{filename|/sys/class/gpio/gpioX/value}} attributes.

==== Example ====
The following example demonstrates how to configure GPIO 140 as output and produce a 1usec pulse:

<pre>
echo 140 > /sys/class/gpio/export
echo 1 > /sys/class/gpio/gpio140/direction
echo 0 > /sys/class/gpio/gpio140/value
echo 1 > /sys/class/gpio/gpio140/value
usleep 1
echo 0 > /sys/class/gpio/gpio140/value
</pre>

=== Angstrom Linux package management ===
Angstrom Linux for CM-T3530 includes {{cmd|opkg}} package manager. It can be run either from command line, or using GUI. Go to "Settings" -> "Package Manager" to start the application, select packages you'd like to install and press "Apply" button.

=== Power management ===
The Angstrom Linux for CM-T3530 supports very low power sleep mode and dynamic frequency scaling. Please refer to [[CM-T3530: Linux: Power management]] article for further details.

== See also ==
* [[CM-T3530: Linux: Getting started|Getting started with Linux on CM-T3530]]
* [[CM-T3530: Linux: Kernel|Linux kernel for CM-T3530]]
* [[CM-T3530: Linux: Booting from MMC/SD card|Booting from MMC/SD card]]
* [[CM-T3530: Linux: Building images|Building Linux images]]
* [[Linux Development for ARM modules]]
* [http://www.angstrom-distribution.org Angstrom Distribution]
* [http://www.openembedded.org OpenEmbedded]
* [http://wiki.omap.com Texas Instruments Embedded Processors Wiki]

[[Category:Linux|Angstrom]]
[[Category:CM-T3530|Linux: Angstrom]]

CM-T3530: Linux: Kernel

2010-08-16T14:10:32Z

Mike:

== Overview ==
Linux kernel for CM-T3530 modules provides support for on-board peripherals and abstracts the functionality provided by the hardware. Current support coverage is specified at [http://www.compulab.co.il/t3530/html/t3530-os-support.htm O/S support coverage map] page. CompuLab provides ready-to-run binary kernel images, and source code of the modifications and additions made to the Linux kernel to work properly with CM-T3530 modules.
Most of the CM-T3530 functionality is merged into the mainline kernel starting from 2.6.33 release.

== Kernel command line ==
The Linux kernel for CM-T3530 is shipped with built-in command line parameters:
ubi.mtd=4,2048 root=ubi0:cm-t35-rootfs rootfstype=ubifs console=ttyS2,115200 \
omapfb.mode=dvi:1024x768-24@60 omapfb.vram=1:4M vram=8M omapdss.def_disp=lcd

The default kernel command line defines primary console, default display settings, root device and root filesystem type.

Setting U-Boot {{parameter|bootargs}} environment variable overrides default kernel command line and can be used to set desired kernel parameters.

== Building kernel for CM-T3530 ==
=== Cross-Compiler ===
There are several options for cross-compilation toolchain setup. You can either compile your cross-compiler or use an already built cross-compiler. The cross-compiler should support the ARM embedded-application binary interface ("[http://en.wikipedia.org/wiki/Application_binary_interface#EABI EABI]")
* Pre-built toolchain:
** [http://www.codesourcery.com/sgpp/lite/arm/portal/release324 CodeSourcery]
* Tools for creating cross-compilers:
** [http://ymorin.is-a-geek.org/dokuwiki/projects/crosstool Crosstool-ng]: Builds a cross-compiler from source. Non-distribution specific.
** [http://www.gentoo.org/proj/en/base/embedded/handbook/index.xml?part=1&chap=4 Crossdev]: Gentoo's cross-compiler builder. Needs Gentoo.

=== U-Boot mkimage tool ===
U-Boot {{cmd|mkimage}} utility is required in order to create kernel images that can be loaded by the CM-T3530 bootloader.
You can download prebuilt [[media:mkimage.tar.gz|{{cmd|mkimage}} binary]] or build it yourself:
<pre>
mkdir ~/tmp
cd tmp
wget ftp://ftp.denx.de/pub/u-boot/u-boot-latest.tar.bz2
tar -xjvf u-boot-latest.tar.bz2
cd u-boot-2009.08
touch include/config.{h,mk}
make tools
sudo install tools/mkimage /usr/local/bin
</pre>

=== Getting kernel sources ===
There are two ways to get Linux kernel sources that can be used as a baseline for CM-T3530 kernel. You can create a copy of linux-omap git tree or download a snapshot and extract it. We assume that you have created {{filename|/home/development/cm-t35/kernel}} directory for CM-T3530 kernel development.
==== Snapshot download ====
* Download [http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=snapshot;h=2a20002a83ce565ed16aaec5e64151cae165cb8f;sf=tgz v2.6.32-omap1] snapshot with your web browser. Note, that tools like {{cmd|wget}} and {{cmd|curl}} will not work here.
* Extract the downloaded archive {{filename|linux-omap-2.6-2a20002a83ce565ed16aaec5e64151cae165cb8f.tar.gz}}
<pre>
cd /home/development/cm-t35/kernel
tar xzvf /path/to/downloaded/linux-omap-2.6-2a20002a83ce565ed16aaec5e64151cae165cb8f.tar.gz
</pre>
: This will create {{filename|/home/development/cm-t35/kernel/linux-omap-2.6}} directory containing linux-omap kernel tree.
* Apply the CM-T3530 patch
<pre>
cd /home/development/cm-t35/kernel/linux-omap-2.6
patch -p1 < /path/to/t3530-linux/kernel/linux-2.6.32-omap1-cm-t35.patch
</pre>

==== Git clone ====
* Install [http://git-scm.com/ git] version control system.
* Create a clone of linux-omap kernel tree
<pre>
cd /home/development/cm-t35/kernel
git clone git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git linux-omap-2.6
</pre>
* Create a branch for CM-T3530 development. The CM-T3530 patches are generated vs. commit 2a20002a83ce565ed16aaec5e64151cae165cb8f in the linux-omap tree. It is recommended to use exactly the same baseline to avoid merge conflicts.
<pre>
git checkout -b cm-t35-dev 2a20002a83ce565ed16aaec5e64151cae165cb8f
</pre>
* Apply the CM-T3530 patch
<pre>
cd /home/development/cm-t35/kernel/linux-omap-2.6
git apply /path/to/t3530-linux/kernel/linux-2.6.32-omap1-cm-t35.patch
</pre>

=== Building the kernel ===
<pre>
export ARCH=arm
export CROSS_COMPILE=arm-none-linux-eabi-
make cm_t35_defconfig
make menuconfig
make && make uImage && \
INSTALL_MOD_PATH=/home/development/cm-t35/rootfs make modules_install
</pre>

In the example above, the Linux kernel image ({{filename|uImage}}) will be created in {{filename|/home/development/cm-t35/kernel/linux-omap-2.6/arch/arm/boot}}, and the loadable kernel modules will be installed into the {{filename|/home/development/cm-t35/rootfs/lib/modules}} directory.

Now, if you boot CM-T3530 with newly created kernel image and with networked root filesysem at {{filename|/home/development/cm-t35/rootfs/}} the system will be able to properly load kernel modules and you avoid modules versioning problems.

== Power management ==
The Linux kernel for CM-T3530 supports very low power sleep mode and dynamic frequency scaling. Please refer to [[CM-T3530: Linux: Power management]] article for further details.

== See also ==
* [[CM-T3530: Linux: Getting started]]
* [[CM-T3530: Linux: Angstrom]]
* [[CM-T3530: Linux: Building images]]
* [[U-Boot for CM-T3530]]

[[Category:Linux]]
[[Category:CM-T3530]]

EM-X270: WinCE: Demo Image Components List

2010-07-27T05:32:55Z

Mike: Reverted edits by Jheena789 (Talk); changed back to last version by Kostyas

<h2>
Predicted WinCE License
</h2><ul><li>
Windows Embedded CE 6.0 Professional Run-Time License
</li></ul><h2>
Included Features
</h2><h3>
Windows Embedded CE 6.0 Professional Run-Time License
</h3>
{|
|
WordPad
|
SYSGEN_PWORD 
|}<h3>
Windows Embedded CE 6.0 Professional Run-Time License. If you are creating a consumer oriented device you may qualify for another SKU, please contact your distributor for more information.
</h3>
{|
|
AYGShell API Set
|
SYSGEN_AYGSHELL 
|-
|
Windows Media Player
|
SYSGEN_CEPLAYER 
|-
|
Windows Media Player OCX
|
SYSGEN_DSHOW_WMP 
|-
|
Help
|
SYSGEN_HELP 
|-
|
Internet Explorer 6.0 for Windows Embedded CE - Standard Components
|
SYSGEN_IE 
|-
|
Adobe Flash Lite ActiveX Control
|
SYSGEN_IE_FLASHLITE 
|-
|
Internet Explorer 6.0 Sample Browser
|
SYSGEN_IESAMPLE 
|-
|
Internet Options Control Panel
|
SYSGEN_INETCPL 
|-
|
Windows Media Player OCX 7
|
SYSGEN_MEDIAAPPS_WMPOCX 
|-
|
Windows Messenger
|
SYSGEN_MESSENGER 
|-
|
Internet Explorer HTML/DHTML API
|
SYSGEN_MSHTML 
|-
|
Internet Explorer Browser Control Host
|
SYSGEN_SHDOCVW 
|-
|
WMA and MP3 Streaming
|
SYSGEN_STREAMAUDIO 
|-
|
Streaming Media Playback
|
SYSGEN_STREAMAV 
|-
|
Silverlight for Windows Embedded
|
SYSGEN_XAML_RUNTIME 
|}<h3>
Windows Embedded CE 6.0 Core Plus Run-Time License
</h3>
{|
|
Bluetooth LAP and Configuration Utility
|
SYSGEN_BTH_GATEWAY 
|-
|
RAS Server/PPTP Server (Incoming)
|
SYSGEN_PPP_SERVER 
|}<h3>
Windows Embedded CE 6.0 Core Run-Time License
</h3>
{|
|
ActiveSync
|
SYSGEN_AS_BASE 
|-
|
File Sync
|
SYSGEN_AS_FILE 
|-
|
Active Template Library (ATL)
|
SYSGEN_ATL 
|-
|
Waveform Audio
|
SYSGEN_AUDIO 
|-
|
Audio Compression Manager
|
SYSGEN_AUDIO_ACM 
|-
|
Authentication Services (SSPI)
|
SYSGEN_AUTH 
|-
|
Kerberos
|
SYSGEN_AUTH_KERBEROS 
|-
|
NTLM
|
SYSGEN_AUTH_NTLM 
|-
|
Schannel (SSL/TLS)
|
SYSGEN_AUTH_SCHANNEL 
|-
|
AutoDial
|
SYSGEN_AUTORAS 
|-
|
Battery Driver
|
SYSGEN_BATTERY 
|-
|
Binary Rom Image File System
|
SYSGEN_BINFS 
|-
|
Bluetooth Stack with Universal Loadable Driver
|
SYSGEN_BTH 
|-
|
Bluetooth HS/HF and Audio Gateway Service
|
SYSGEN_BTH_AG 
|-
|
Bluetooth HID - Keyboard
|
SYSGEN_BTH_HID_KEYBOARD 
|-
|
Bluetooth HID - Mouse
|
SYSGEN_BTH_HID_MOUSE 
|-
|
Bluetooth DUN Gateway
|
SYSGEN_BTH_MODEM 
|-
|
Bluetooth PAN
|
SYSGEN_BTH_PAN 
|-
|
Bluetooth Stack with Integrated USB Driver
|
SYSGEN_BTH_USB_ONLY 
|-
|
Windows Embedded CE Driver Development Kit Support Library
|
SYSGEN_CEDDK 
|-
|
Remote Display Application
|
SYSGEN_CERDISP 
|-
|
Certificates (CryptoAPI 2.0)
|
SYSGEN_CERTS 
|-
|
Command Processor
|
SYSGEN_CMD 
|-
|
Common Control
|
SYSGEN_COMMCTRL 
|-
|
Common Dialog Support
|
SYSGEN_COMMDLG 
|-
|
Network User Interface
|
SYSGEN_CONNMC 
|-
|
Console Window
|
SYSGEN_CONSOLE 
|-
|
National Language Support (NLS)
|
SYSGEN_CORELOC 
|-
|
Standard String Functions - ASCII (corestra)
|
SYSGEN_CORESTRA 
|-
|
C++ Runtime Support for Exception Handling and Runtime Type Information
|
SYSGEN_CPP_EH_AND_RTTI 
|-
|
Credential Manager
|
SYSGEN_CREDMAN 
|-
|
Cryptography Services (CryptoAPI 1.0) with High Encryption Provider
|
SYSGEN_CRYPTO 
|-
|
Control Panel Applets
|
SYSGEN_CTLPNL 
|-
|
Mouse
|
SYSGEN_CURSOR 
|-
|
Direct3D Mobile
|
SYSGEN_D3DM 
|-
|
DCOM
|
SYSGEN_DCOM 
|-
|
DirectDraw
|
SYSGEN_DDRAW 
|-
|
Device Manager
|
SYSGEN_DEVICE 
|-
|
Display Support
|
SYSGEN_DISPLAY 
|-
|
Extended DNS Querying and Update (DNSAPI)
|
SYSGEN_DNSAPI 
|-
|
.NET Compact Framework 2.0
|
SYSGEN_DOTNETV2 
|-
|
OS Dependencies for .NET Compact Framework 2.0
|
SYSGEN_DOTNETV2_SUPPORT 
|-
|
DirectShow Core
|
SYSGEN_DSHOW 
|-
|
ACM Wrapper Filter
|
SYSGEN_DSHOW_ACMWRAP 
|-
|
AVI Filter
|
SYSGEN_DSHOW_AVI 
|-
|
DirectShow Display
|
SYSGEN_DSHOW_DISPLAY 
|-
|
DMO Wrapper Filter
|
SYSGEN_DSHOW_DMO 
|-
|
Video/Image Compression Manager
|
SYSGEN_DSHOW_ICM 
|-
|
MP3 Codec
|
SYSGEN_DSHOW_MP3 
|-
|
MPEG-1 Parser/Splitter
|
SYSGEN_DSHOW_MPEGSPLITTER 
|-
|
G.711 Audio Codec
|
SYSGEN_DSHOW_MSG711 
|-
|
GSM 6.10 Audio Codec
|
SYSGEN_DSHOW_MSGSM610 
|-
|
MS RLE Video Codec
|
SYSGEN_DSHOW_MSRLE 
|-
|
DirectShow Video Renderer
|
SYSGEN_DSHOW_VIDREND 
|-
|
Wave/AIFF/au/snd File Parser
|
SYSGEN_DSHOW_WAV 
|-
|
WMA Codec
|
SYSGEN_DSHOW_WMA 
|-
|
WMA Voice Codec
|
SYSGEN_DSHOW_WMA_VOICE 
|-
|
Windows Media Technologies
|
SYSGEN_DSHOW_WMT 
|-
|
ASX v1 and M3U File Support
|
SYSGEN_DSHOW_WMT_ASXV1 
|-
|
ASX v2 File Support
|
SYSGEN_DSHOW_WMT_ASXV2 
|-
|
ASX v3 File Support
|
SYSGEN_DSHOW_WMT_ASXV3 
|-
|
Windows Media Streaming over HTTP
|
SYSGEN_DSHOW_WMT_HTTP 
|-
|
Windows Media Streaming from Local Storage
|
SYSGEN_DSHOW_WMT_LOCAL 
|-
|
Windows Media Streaming over MMS
|
SYSGEN_DSHOW_WMT_MMS 
|-
|
Windows Media Multicast and Multi-Bit Rate
|
SYSGEN_DSHOW_WMT_MULTI 
|-
|
NSC File Support
|
SYSGEN_DSHOW_WMT_NSC 
|-
|
WMV/MPEG-4 Video Codec
|
SYSGEN_DSHOW_WMV 
|-
|
Extensible Authentication Protocol
|
SYSGEN_EAP 
|-
|
Wireless LAN (802.11) STA - Automatic Configuration and 802.1x
|
SYSGEN_ETH_80211 
|-
|
USB Remote NDIS Class Driver
|
SYSGEN_ETH_USB_HOST 
|-
|
Wired Local Area Network (802.3, 802.5)
|
SYSGEN_ETHERNET 
|-
|
exFAT File System
|
SYSGEN_EXFAT 
|-
|
FAT File System
|
SYSGEN_FATFS 
|-
|
Fiber API
|
SYSGEN_FIBER 
|-
|
Flash MDD
|
SYSGEN_FLASHMDD 
|-
|
FormatMessage API
|
SYSGEN_FMTMSG 
|-
|
Courier New (Subset 1_30)
|
SYSGEN_FONTS_COUR_1_30 
|-
|
Symbol
|
SYSGEN_FONTS_SYMBOL 
|-
|
Tahoma (Subset 1_07)
|
SYSGEN_FONTS_TAHOMA_1_07 
|-
|
Times New Roman (Subset 1_30)
|
SYSGEN_FONTS_TIMES_1_30 
|-
|
Wingding
|
SYSGEN_FONTS_WINGDING 
|-
|
Freecell
|
SYSGEN_FREECELL 
|-
|
CEDB Database Engine
|
SYSGEN_FSDBASE 
|-
|
System Password
|
SYSGEN_FSPASSWORD 
|-
|
Hive-based Registry
|
SYSGEN_FSREGHIVE 
|-
|
Bit-based
|
SYSGEN_FSREPLBIT 
|-
|
ROM-only File System
|
SYSGEN_FSROMONLY 
|-
|
FTP Server
|
SYSGEN_FTPD 
|-
|
Full C Runtime
|
SYSGEN_FULL_CRT 
|-
|
Alphablend API (GDI version)
|
SYSGEN_GDI_ALPHABLEND 
|-
|
GPS Intermediate Driver
|
SYSGEN_GPSID 
|-
|
Gradient Fill Support
|
SYSGEN_GRADFILL 
|-
|
Internet Appliance (IABASE) Support
|
SYSGEN_IABASE 
|-
|
JScript 5.6
|
SYSGEN_IE_JSCRIPT 
|-
|
Still Image Codec Support (Encode and Decode)
|
SYSGEN_IMAGING 
|-
|
BMP Decoder
|
SYSGEN_IMAGING_BMP_DECODE 
|-
|
BMP Encoder
|
SYSGEN_IMAGING_BMP_ENCODE 
|-
|
GIF Decoder
|
SYSGEN_IMAGING_GIF_DECODE 
|-
|
GIF Encoder
|
SYSGEN_IMAGING_GIF_ENCODE 
|-
|
JPG Decoder
|
SYSGEN_IMAGING_JPG_DECODE 
|-
|
JPG Encoder
|
SYSGEN_IMAGING_JPG_ENCODE 
|-
|
PNG Decoder
|
SYSGEN_IMAGING_PNG_DECODE 
|-
|
PNG Encoder
|
SYSGEN_IMAGING_PNG_ENCODE 
|-
|
Input Method Manager (IMM)
|
SYSGEN_IMM 
|-
|
IP Helper API
|
SYSGEN_IPHLPAPI 
|-
|
SIP for Large Screens
|
SYSGEN_LARGEKB 
|-
|
WMA and MP3 Local Playback
|
SYSGEN_LOCALAUDIO 
|-
|
Location Framework Core
|
SYSGEN_LOCATION_FRAMEWORK 
|-
|
Location Framework GPS Plugin
|
SYSGEN_LOCATION_GPS_PROVIDER 
|-
|
Overlapping Menus
|
SYSGEN_MENU_OVERLAP 
|-
|
Minimal GDI Configuration
|
SYSGEN_MINGDI 
|-
|
Minimal GWES Configuration
|
SYSGEN_MINGWES 
|-
|
Minimal Input Configuration
|
SYSGEN_MININPUT 
|-
|
Minimal Window Manager Configuration
|
SYSGEN_MINWMGR 
|-
|
Internet Explorer Multiple-Language Base API
|
SYSGEN_MLANG 
|-
|
Standard Modem Support for Dial Up Networking
|
SYSGEN_MODEM 
|-
|
Message Queue - Point-to-Point
|
SYSGEN_MSGQUEUE 
|-
|
SIP for Small Screens
|
SYSGEN_MSIM 
|-
|
Partition Driver
|
SYSGEN_MSPART 
|-
|
XML Core Services and Document Object Model (DOM)
|
SYSGEN_MSXML_DOM 
|-
|
XML Query Languages (XQL)
|
SYSGEN_MSXML_XQL 
|-
|
Network Driver Architecture (NDIS)
|
SYSGEN_NDIS 
|-
|
NDIS User-mode I/O Protocol Driver
|
SYSGEN_NDISUIO 
|-
|
Domain Discovery
|
SYSGEN_NETAPI32 
|-
|
Network Utilities (IpConfig, Ping, Route)
|
SYSGEN_NETUTILS 
|-
|
Compression
|
SYSGEN_NKCOMPR 
|-
|
Memory Mapped Files
|
SYSGEN_NKMAPFILE 
|-
|
Notification LED Support
|
SYSGEN_NLED 
|-
|
UI based Notification
|
SYSGEN_NOTIFY 
|-
|
OBEX Client
|
SYSGEN_OBEX_CLIENT 
|-
|
OBEX File Browser
|
SYSGEN_OBEX_FILEBROWSER 
|-
|
OBEX Inbox
|
SYSGEN_OBEX_INBOX 
|-
|
OBEX Server
|
SYSGEN_OBEX_SERVER 
|-
|
COM
|
SYSGEN_OLE 
|-
|
Power Management (Full)
|
SYSGEN_PM 
|-
|
Dial Up Networking (RAS/PPP)
|
SYSGEN_PPP 
|-
|
PPTP
|
SYSGEN_PPTP 
|-
|
Windows Networking API/Redirector (SMB/CIFS)
|
SYSGEN_REDIR 
|-
|
Release Directory File System
|
SYSGEN_RELFSD 
|-
|
Serial Port Support
|
SYSGEN_SERDEV 
|-
|
Core Server Support
|
SYSGEN_SERVICES 
|-
|
Target Control Support (Shell.exe)
|
SYSGEN_SHELL 
|-
|
Software-based Input Panel Driver
|
SYSGEN_SOFTKB 
|-
|
Solitaire
|
SYSGEN_SOLITARE 
|-
|
Standard Shell
|
SYSGEN_STANDARDSHELL 
|-
|
Standard I/O (STDIO)
|
SYSGEN_STDIO 
|-
|
Standard I/O ASCII (STDIOA)
|
SYSGEN_STDIOA 
|-
|
Storage Manager
|
SYSGEN_STOREMGR 
|-
|
Storage Manager Control Panel Applet
|
SYSGEN_STOREMGR_CPL 
|-
|
String Safe Utility Functions
|
SYSGEN_STRSAFE 
|-
|
Telephony API (TAPI 2.0)
|
SYSGEN_TAPI 
|-
|
Touch Driver Test Application
|
SYSGEN_TCHTEST 
|-
|
TCP/IP
|
SYSGEN_TCPIP 
|-
|
TCP/IPv6 Support
|
SYSGEN_TCPIP6 
|-
|
Telnet Server
|
SYSGEN_TELNETD 
|-
|
Transaction-Safe FAT File System (TFAT)
|
SYSGEN_TFAT 
|-
|
SNTP Client with DST
|
SYSGEN_TIMESVC_DST 
|-
|
Toolhelp API
|
SYSGEN_TOOLHELP 
|-
|
Touch Screen (Stylus)
|
SYSGEN_TOUCH 
|-
|
UI Proxy for Kernel-Mode Drivers
|
SYSGEN_UIPROXY 
|-
|
Unimodem support
|
SYSGEN_UNIMODEM 
|-
|
URL Moniker Services
|
SYSGEN_URLMON 
|-
|
USB Host Support
|
SYSGEN_USB 
|-
|
USB Human Input Device (HID) Class Driver
|
SYSGEN_USB_HID 
|-
|
USB HID Keyboard and Mouse
|
SYSGEN_USB_HID_CLIENTS 
|-
|
USB HID Keyboard Only
|
SYSGEN_USB_HID_KEYBOARD 
|-
|
USB HID Mouse Only
|
SYSGEN_USB_HID_MOUSE 
|-
|
USB Printer Class Driver
|
SYSGEN_USB_PRINTER 
|-
|
USB Storage Class Driver
|
SYSGEN_USB_STORAGE 
|-
|
USB Function Driver
|
SYSGEN_USBFN 
|-
|
Real-time Communications (RTC) Client API
|
SYSGEN_VOIP 
|-
|
CAB File Installer/Uninstaller
|
SYSGEN_WCELOAD 
|-
|
Windows Internet Services
|
SYSGEN_WININET 
|-
|
Passport SSI 1.4 Authentication
|
SYSGEN_WININET_TWEENER 
|-
|
Winsock Support
|
SYSGEN_WINSOCK 
|-
|
Windows XP-like Sample Skin
|
SYSGEN_XPSKIN 
|}<h3>
Either a Professional or Core license depending on how Cellcore is used. Voice use of Cellcore requires a Professional license.
</h3>
{|
|
RIL Proxy
|
SYSGEN_CELLCORE_RIL 
|}

== See Also ==

[[Category:Windows CE|Demo Image Components ]]
[[Category:EM-X270|WinCE: Demo Image Components ]]

CM-T3530: Linux: Video playback

2010-07-19T13:08:09Z

Mike: /* Videos not playing. */

== Introduction ==
The OMAP3530 includes a built-in TMS320C64X+ DSP Core that provides advanced hardware acceleration support for media encoding / decoding. 
For further details, refer to the [http://focus.ti.com/general/docs/litabsmultiplefilelist.tsp?literatureNumber=spruf98d OMAP35x Technical Reference Manual].

== GStreamer TI Plugin ==

[http://en.wikipedia.org/wiki/GStreamer GStreamer] is a pipeline-based multimedia framework that allows to create a variety of media-handling software components. [https://gstreamer.ti.com/gf/project/gstreamer_ti/ GStreamer TI Plugin] for OMAP3 platform enables DSP hardware utilisation for accelerating streaming audio and video processing and image manipulation by using TI DSP codecs. The plugin contains
[http://processors.wiki.ti.com/index.php?title=GstTIPlugin_Elements GstTIPlugin Elements] for decoding/encoding audio, video and image and for displaying the video using fbdev.

=== Video formats. ===

Gstreamer TI and TI OMAP35x codecs currently support playback of VGA videos of quality up to [http://en.wikipedia.org/wiki/480p 480p] @ 30 fps of the following formats:

* VGA .AVI VGA file with MPEG-2 or MPEG-4 Video and MP1L2 or MP3 Audio. 
* VGA .AVI VGA file with H.264 Video and AAC Audio. 
* VGA .MP4 file with MPEG-2/MPEG-4/H.264 Video and MP1L2/MP3/AAC Audio. 
* VGA .TS file with H.264 Video and MP1L2 or MP3 Audio.

'''Only baseline profile of H.264 and simple profile of MPEG4 formats are supported.''' Please refer to the TI [http://software-dl.ti.com/dsps/dsps_public_sw/codecs/OMAP35xx/index_FDS.html H.264] and [http://software-dl.ti.com/dsps/dsps_public_sw/codecs/C64XPlus_Video/index_FDS.html MPEG-4] codecs Data Sheets.

=== Kernel parameters ===
In order to make the GStreamer-TI package work, please ensure that the framebuffer plains 1 and 2 are enabled in your kernel command line:

<pre>vram=18M omapfb.vram=0:6M,1:6M,2:6M</pre>

Additionally, cmemk kernel module requires a "window" in the kernel memory. It allocates a heap buffer at 0xc9000000 of size 0x53d000. You can leave this memory free by adding for example the following option to the kernel command line:

<pre>mem=99M@0x80000000</pre>

=== Playback pipeline examples ===

Below examples illustrate how to play video samples using GStreamer-TI. For more info please refer to [http://processors.wiki.ti.com/index.php/Example_GStreamer_Pipelines#OMAP35x GStreamer Pipelines Examples for OMAP35x].

* VGA .AVI file with MPEG-2 or MPEG-4 Video and MP1L2 or MP3 Audio. 
gst-launch -v filesrc location=sample.avi ! avidemux name=demux demux.audio_00 ! \
queue max-size-buffers=1200 max-size-time=0 max-size-bytes=0 ! mad ! alsasink demux.video_00 ! \
queue ! TIViddec2 ! queue max-size-buffers=2 max-size-time=0 max-size-bytes=0 ! omapdmaifbsink max-lateness=50000

* VGA .AVI file with H.264 Video and AAC Audio.
gst-launch -v filesrc location=sample.avi ! avidemux name=demux demux.audio_00 ! \
queue max-size-buffers=8000 max-size-time=0 max-size-bytes=0 ! TIAuddec1 ! alsasink demux.video_00 ! \
queue ! TIViddec2 ! omapdmaifbsink max-lateness=50000

* VGA .MP4 file with H.264 Video and MP1L2 or MP3 Audio:
gst-launch -v filesrc location=sample.mp4 ! qtdemux name=demux demux.audio_00 ! \
queue max-size-buffers=8000 max-size-time=0 max-size-bytes=0 ! mad ! alsasink demux.video_00 ! \
queue ! TIViddec2 ! omapdmaifbsink max-lateness=50000

* VGA .MP4 file with H.264 Video and AAC Audio:
gst-launch -v filesrc location=sample.mp4 ! qtdemux name=demux demux.audio_00 ! \
queue max-size-buffers=8000 max-size-time=0 max-size-bytes=0 ! TIAuddec1 ! alsasink demux.video_00 ! \
queue ! TIViddec2 ! omapdmaifbsink max-lateness=50000

* VGA .TS file with H.264 Video and MP1L2 or MP3 Audio:
gst-launch filesrc location=sample.ts ! typefind ! mpegtsdemux name=demux demux. ! \
queue max-size-buffers=1200 max-size-time=0 max-size-bytes=0 ! typefind ! mad ! alsasink demux. ! \
typefind ! TIViddec2 ! queue max-size-buffers=2 max-size-time=0 max-size-bytes=0 ! omapdmaifbsink max-lateness=50000

== Creating Videos ==

Example video clips can be downloaded from [http://www.apple.com/trailers Apple trailers]. Use Quicktime Pro to download and save the trailer videos. Use the [http://www.ffmpeg.org ffmpeg] application to convert the videos to the GStreamer TI compatible formats. Refer to [http://ubuntuforums.org/showthread.php?t=1117283 enabling MP3, MPEG4, AAC, in FFmpeg on Ubuntu].

* Encoding to .AVI file H.264 Video and AAC Audio:
ffmpeg -i test.mov -f avi -r 30 -b 1200kb -s 720x480 -vcodec libx264 -vpre hq -vpre baseline \
-me_range 8 -crf 22 -acodec aac -ar 22050 -ac 2 -threads 0 test.avi
Creates a video file with size 720x480, 30 fps, bitrate 1200 kbps, 2 channels audio with 22050 Hz frequency.
* Encoding to .MP4 file with MPEG-4 Video and MP3 Audio:
ffmpeg -i test.mov -r 30 -f mp4 -b 1200kb -s 720x480 -vcodec mpeg4 -flags +aic+cbp+mv0+mv4 \
-profile 0 -level 2 -trellis 2 -mbd 2 -cmp 2 -subcmp 2 -g 250 -maxrate 2.5M -bufsize 2M \
-acodec libmp3lame -ar 22050 -ac 2 -threads 0 test.mp4

=== Parameters explanation ===

; '''-f''' : container format
; '''-b''' : video bitrate
; '''-s''' : video size
; '''-r''' : frames per second
; '''-ar''' : audio frequency
; '''-ac''' : audio channels
; '''-threads 0''' : indicates that the algorithm should choose the number of threads to be used.

'''H264 specific options''' - please refer for more info to the [http://rob.opendot.cl/index.php/useful-stuff/ffmpeg-x264-encoding-guide/ x264 encoding guide] and [http://rob.opendot.cl/index.php/useful-stuff/x264-to-ffmpeg-option-mapping/ ffmpeg to libx264 options mapping].

<pre>
-vpre libx264 presets
-me_range
-crf
</pre>

'''MPEG-4 specific options''' - please refer for some explanations [http://rob.opendot.cl/index.php/useful-stuff/ipod-video-guide/ here].

<pre>
-profile -level :
- Simple Profile level 0, corresponds to "-profile 0 - level 8"
- Simple Profile level 1, corresponds to "-profile 0 - level 1"
- Simple Profile level 2, corresponds to "-profile 0 - level 2"

-flags

-trellis

-mbd

-cmp

-subcmp

-g

-maxrate

-bufsize
</pre>

== Troubleshooting ==

=== Videos not playing ===

Try to add to your gstreamer command line the debugging option that will display all warnings regarding the TI elements.
<pre>-v --gst-debug=TI*:2</pre>

If there are no errors shown, but the player still doesn't show up, check if the video is of a compatible format and size (should be up to 480p).

[[Category:Linux|Video Playback]]
[[Category:CM-T3530|Linux: Video Playback]]

CM-T3530: WinCE: Updater

2010-07-19T08:54:56Z

Mike: /* Target Media Layout */

== Introduction ==
The CM-T3530 Updater Framework is based on general CompuLab [[WinCE: Updater Framework|Updater framework for Windows CE]].

The CM-T3530 demo image installation flow is described in [[CM-T3530: WinCE: Getting Started#Installing the demo runtime image | Getting Started Guide]]. This article presents an overview of the CM-T3530 target media layout, Updater application installation flow and the demo image [[#Demo Image Installation XML Script|{{filename|installation XML script}}]] located in {{filename|LiveDisk\script.xml}}

== Updater Customization for CM-T3530 ==
=== Target Media Layout ===
The WinCE demo image requires the following logical layout of the CM-T3530 512 MB NAND flash:
* boot section (CMT35-nand.raw) that contains bootstrap, bootloader and bootloader parameters
** 4 copies of XLDR (CM-T3530 bootstrap)
** Eboot (CM-T3530 bootloader)
** Eboot parameters (at offset 0xBF800)
** splashscreen parameters (at offset 0xBF900)
* splashscreen (at offset 0xC0000)
* MBR
* BINFS partition (for NK.bin)
* TFAT partition for user data storage
The above layout settings are defined in the <target_storage> sections of the [[#Demo Image Installation XML Script|installation script]].
{{Note| Please refer to [[WinCE:_Updater_Framework#Target storage XML section| Target storage XML section]] description for the XML syntax details}}

=== Update Flow ===
The Updater application invokes the following actions according to the <actions> section of the installation [[#Demo Image Installation XML Script|{{filename|script.xml}}]]:
* Reserve 10 blocks at the end of NAND (used to compensate bad block variations among different NAND chips)
* Store and reserve bootstrap, bootloader and bootloader parameters (CMT35-nand.raw)
* Store and reserve splashscreen
* Erase non reserved NAND area including existing OS partitions
* Create MBR
* Create BINFS partition for NK.bin storage
* Create user data partition
* Format user data partition with TFAT
* Store NK.bin file into BINFS partition
* Update splashscreen parameters (optional)
{{Note| See [[WinCE:_Updater_Framework#Update flow actions XML section| Update flow actions XML section]] for the XML syntax details}}

=== Demo Image Installation XML Script===
<pre>
<updater version="1.0.0.99">
<source_storage>
<access_information>
<device_type>SD</device_type>
<device_name>DSK1:</device_name>
<mount_path>\Storage Card</mount_path>
</access_information>
<logger_information>
<updater_logger>
<file_name>updater_log.txt</file_name>
<append_log>false</append_log>
<verbosity>debug</verbosity>
</updater_logger>
<system_logger>
<file_name>system_log.txt</file_name>
<append_log>false</append_log>
</system_logger>
</logger_information>
</source_storage>

<target_storage>
<device id="nand1">
<config type="nand" chipid="0" sectorsize="0x800" blocksize="0x20000" length="detected"></config>
<region id="boot_region">
<config type="boot" start="0x0" alignment="blocksize"></config>
<entity id="boot_content">
<config type ="raw" offset="0x0000" length="0xC0000" alignment="blocksize"></config>
<source file="CMT35-nand.raw" format="raw"></source>
</entity>
<entity id="boot_parameters">
<config type ="raw" offset="0xBF800" length="0x800" alignment="sectorsize"></config>
</entity>
<entity id="splashscreen">
<config type ="raw" length="auto" alignment="blocksize"></config>
<source file="splashscreen.bmp" format="raw"></source>
</entity>
</region>
<region id="os_region">
<config type="os" alignment="blocksize"></config>
<source file="os_region.nb0" format="raw"></source>
<entity id="os_partition_table">
<config type="partition_table"></config>
</entity>
<entity id="partition_nk">
<config type="partition" name="nk" length="auto" reserve="10%" alignment="sectorsize"></config>
<source file="nk.bin" format="bin"></source>
</entity>
<entity id="partition_system">
<config type="partition" name="system" alignment="sectorsize"></config>
</entity>
</region>

<region id="reserve_region">
<config type="reserve" length="blocksize" replication="10" alignment="blocksize"></config>
</region>
</device>
</target_storage>

<actions>
<action type="reserve">
<target id="reserve_region" alignment="blocksize"></target>
<params oem_attribute="reserved_readonly"></params>
</action>
<action type="store" subtype="raw">
<target id="boot_content"></target>
<params block_status="reserved" oem_attribute="reserved_readonly"></params>
</action>
<action type="store" subtype="raw">
<target id="splashscreen"></target>
<params block_status="reserved" oem_attribute="reserved_readonly"></params>
</action>
<action type="erase">
<target id="os_region"></target>
</action>
<action type="partition_create">
<target id="partition_nk"></target>
<params part_type="bootsection" active="false"></params>
</action>
<action type="partition_create">
<target id="partition_system"></target>
<params part_type="dos32_fat" active="false"></params>
</action>
<action type="store" subtype="raw">
<target id="partition_nk"></target>
</action>
<action type="update_parameter" subtype="offset">
<target id="boot_parameters"></target>
<params param_offset="0x100" param_length="4" param_value="0x4c434453" param_type="number"></params> 
<params param_offset="0x104" param_length="4" param_value="0x280" param_type="number"></params> 
<params param_offset="0x108" param_length="4" param_value="0x1e0" param_type="number"></params> 
<params param_offset="0x10C" param_length="4" param_value="0x20" param_type="number"></params> 
<params param_offset="0x110" param_length="4" param_value="0x0" param_type="number"></params> 
<params param_offset="0x114" param_length="4" param_value="0x17" param_type="number"></params> 
<params param_offset="0x118" param_length="4" param_value="0x8" param_type="number"></params> 
<params param_offset="0x11C" param_length="4" param_value="0x1" param_type="number"></params> 
<params param_offset="0x120" param_length="4" param_value="0x0" param_type="number"></params> 
<params param_offset="0x124" param_length="4" param_value="0x3" param_type="number"></params> 
<params param_offset="0x128" param_length="4" param_value="0x4" param_type="number"></params> 
<params param_offset="0x12C" param_length="4" param_value="0x17D7840" param_type="number"></params> 
<params param_offset="0x130" param_length="4" param_value="0x1" param_type="number"></params> 
<params param_offset="0x134" param_length="4" param_value="0x0" param_type="number"></params> 
</action>
</actions>
</updater>
</pre>
{{Note| See [[WinCE:_Updater_Framework#Updater Application| Updater Application XML section]] for the XML syntax details}}

== See Also ==
*[[WinCE: Updater Framework]]
[[Category:Windows CE|Updater]]
[[Category:CM-T3530|WinCE: Updater]]

WinCE: Updater Framework

2010-07-19T08:45:35Z

Mike:

= Introduction =
Updater framework is a set of drivers, libraries, applications and configuration files intended for Windows CE installation to systems based on CompuLab products.
This document describes the Updater flow and operating environment.

= Document Conventions =
* Updater OS - the complete bootable operating system image that includes drivers, libraries applications and configuration files necessary to install Windows CE on the target system.
* Updater Application - an application that performs installation of operating system images and (optionally) user data onto the target system.
* Source storage - the storage media that contains images that will be installed on the target system. The source storage may also be used as the boot media for the device and contain the Updater OS.
* Target storage - the storage media that normally holds operating system image and (optionally) user data. In most cases the target storage is the on-board NAND flash.
* Target OS - one or more binary images that will be installed on the device.

= Overview =
The CompuLab Updater framework is designed to support the Windows CE installation on the evaluation kit. The following highlights describe Updater framework features:
* installs the CompuLab generated images to the target storage
* completely erases the flash
* sets bootloader parameters to OS-required defaults
* can use any storage device available in the evaluation kit for image sources
* easy and intuitive

= Operating environment =
The Updater Application is available on all Windows CE platforms supported by CompuLab. Each OS - hardware combination has platform specific customizations for general Updater framework.

== Hardware setup ==
Current Updater framework functionality is designed for CompuLab base board supplied with the evaluation kit. Such policy has the following benefits:
* Well defined module hardware connectivity options
* Provides hardware access to display that allows to perform GUI feedback during update flow
* Allows to use verified Updater OS provided by CompuLab for all custom module configurations independently of custom base board support

== Updater Invocation ==
The Updater Application supports two major invocation modes:
* The system boot is performed from non-default storage into dedicated Updater OS. In this case the Updater Application can have full control over the target storage.
* The system boot is performed from the default storage. In this case the Updater Application is not allowed to overwrite the live system. This in turn poses a requirement for availability of dedicated Updater OS partition on the default storage or external bootable media with Updater OS.
When the Updater Application is invoked on the live system, it will setup configuration files and boot parameters for the Updater OS and issue reboot to the Updater OS.

== Source storage access ==
The source data for the installation/update may reside on
* USB flash
* MMC/SD card
* internal storage(NAND) partition

The Updater OS provides required drivers and configurations for the source storage mount in Updater Application.

== Target storage access ==
Target storage is accessed via target media driver in the Updater OS.
The target media (NAND) driver provides raw access (e.g. NAND FMD) to the media and file based access for data partitions (e.g. NAND FAL/FMD).

== Update Flow ==
General update flow includes:
* prepare source storage content
** source storage content includes configuration (e.g. XML) file that describes installation process
* setup source storage access
** connect external media
* boot module
* boot Updater OS
* get access to source storage
** mount source storage content
* invoke Updater Application
** execute updater flow defined in .xml file

= Updater framework functionality =
== Target storage layout ==
Target storage (default internal storage) is composed of one or more physical devices.
Further it can be logically divided according to the following '''region''' types:
* Unique region
* Boot region
* Target OS region (can be more than one for multi-boot support)
* Reserved region
Each region can be further divided into logical '''entities''', which are defined below according to region type.
=== Unique region ===
Unique region can reside in predefined location in NAND, or NOR flash, or in the different read only physical device, such as EEPROM.
Content of unique region is updated once during production process.

=== Boot region ===
It is important to guarantee hardware write protection to boot region, otherwise in case of accidental content damage the module must be re-manufactured. Typically the boot region contains the following entities:
* bootstrap
* bootstrap parameters
* bootloader
* bootloader parameters
* splash screen
* bootloader reserved
The bootstrap and bootloader implementation is depended on hardware architecture and supported OS.
{{Note| Each entity can appear multiple times for redundancy.}}

=== Target OS region ===
Typical OS region layout suitable for Windows CE from the target OS point of view contains the following entities:
* partition table
* optional Updater OS partition
* kernel partition
* optional OS partition
* user data partition
** read/write access allowed
* optional user read-only data partition for critical user data
To guarantee reliable OS operation the OS region should be hardware write protected except the user data partition

=== Reserved region ===
This region is used for NAND flash bad block compensation, i.e. to unify the logical length of target medium on different NAND flash chips. It is always placed at the end of the medium.
A typical example is relocation table that reserves 127 blocks at the end of NAND storage on CM-X300.

== Updater Application ==
The Updater Application is launched automatically by the Updater OS and executes the update flow in the following manner:
* The update flow is unattended
* The actions specified by the XML configuration file are executed sequentially
* The GUI provides progress notification for each action
* Each action is reported to a log file and to the serial console

The Updater Application uses the XML syntax for its configuration file. There are three major sections in the Updater Application XML file (script.xml):
* Source storage section - provides the source storage access and logging information
* Target storage section - provides the target storage layout information and links it to the source storage content
* Update flow actions section - provides the list of the sequentially executed update flow actions with parameters

==== Source storage XML section ====
The {{Cmd|<source_storage>}} element is used to define the source storage section. The following XML elements are used in this section:

*{{Cmd|<access_information>}} - container element for source storage access information
{| cellpadding="3" border="1" style="border: 1px solid rgb(85, 85, 85); border-collapse: collapse;"
| '''child element''' || '''mandatory''' || '''values''' || '''description'''
|-
| <device_type> || yes || "usb" "sd" "network" || specifies the type of the source storage device
|-
| <mount_path> || yes || string value || specifies the file path for the source storage access. Updater Application will automatically mount this path if needed
|}
*{{Cmd|<logger_information>}} - container element for logging information
*{{Cmd|<logger_information><updater_logger>}} - container element for Updater Application logging information
{| cellpadding="3" border="1" style="border: 1px solid rgb(85, 85, 85); border-collapse: collapse;"
| '''child element''' || '''mandatory''' || '''values''' || '''description'''
|-
| <file_name> || yes || string value || specifies the relative file path of the log file that will be stored on the source media
|-
| <append_log> || no || "true" "false" || specifies the log append policy
|-
| <verbosity> || no || "debug" "info" "error" "none" || specifies the verbosity of the log messages
|}
*{{Cmd|<logger_information><system_logger>}} - container element for Updater OS logging information
{| cellpadding="3" border="1" style="border: 1px solid rgb(85, 85, 85); border-collapse: collapse;"
| '''child element''' || '''mandatory''' || '''values''' || '''description'''
|-
| <file_name> || yes || string value || specifies the relative file path of the log file that will be stored on the source media
|-
| <append_log> || no || "true" "false" || specifies the log append policy
|-
| <verbosity> || no || "debug" "info" "error" "none" || specifies the verbosity of the log messages
|}

=====Source storage XML syntax example=====
Source storage syntax example is taken from the CM-T3530 installation script:
<pre>
<source_storage>
<access_information>
<device_type>USB</device_type>
<mount_path>\Hard Disk</mount_path>
</access_information>
<logger_information>
<updater_logger>
<file_name>updater_log.txt</file_name>
<append_log>false</append_log>
<verbosity>debug</verbosity>
</updater_logger>
<system_logger>
<file_name>system_log.txt</file_name>
<append_log>false</append_log>
</system_logger>
</logger_information>
</source_storage>
</pre>

==== Target storage XML section ====
The {{Cmd|<target_storage>}} element is used to define the target storage section. The following XML elements are used in this section:

*{{Cmd|<device>}} - container element for target storage device information (e.g. NAND or NOR).
{| cellpadding="3" border="1" style="border: 1px solid rgb(85, 85, 85); border-collapse: collapse;"
| '''attribute''' || '''mandatory''' || '''values''' || '''description'''
|-
| id || yes || string value || unique name of the device
|}
*{{Cmd|<device><config>}} - specifies the device specific configuration parameters.
{| cellpadding="3" border="1" style="border: 1px solid rgb(85, 85, 85); border-collapse: collapse;"
| '''attribute''' || '''mandatory''' || '''values''' || '''description'''
|-
| type || yes || "nand" - use NAND flash as target storage "nor" - use NOR flash as target storage || specifies the type of the target storage device
|-
| chipid || yes || numeric value || specifies the chip id of the device
|-
| blocksize || no || numeric value || specifies the block size of the device
|-
| sectorsize || no || numeric value || specifies the sector size of the device
|-
| length || no || numeric value || specifies the device length accessible for Updater Application
|}
*{{Cmd|<region>}} - container element for target storage region information (e.g. Boot, Os, Reserved)
{| cellpadding="3" border="1" style="border: 1px solid rgb(85, 85, 85); border-collapse: collapse;"
| '''attribute''' || '''values''' || '''description'''
|-
| id || yes || string value || unique name of the region
|}
*{{Cmd|<region><config>}} - specifies the device specific configuration parameters.
{| cellpadding="3" border="1" style="border: 1px solid rgb(85, 85, 85); border-collapse: collapse;"
| '''attribute''' || '''mandatory''' || '''values''' || '''description'''
|-
| type || yes || "boot" "os" "reserved"|| specifies the type of the region
|-
| start || no ||numeric value || specifies the absolute start position of the region in bytes from the beginning of the device
|-
| length || no ||numeric value "sectorsize" - use the device sector size "blocksize" - use the device block size "auto" - calculate the length according to the source file info || specifies the region length. The actual region length can be affected with other attributes.
|-
| alignment || no || numeric value "blocksize" - use the device block size "sectorsize" - use the device sector size || specifies the alignment of the region
|-
| reserve || no || percentage value (e.g. "10%")|| specifies the size of the extra space to reserve in percents of the specified length
|-
| replication || no || numeric value || specifies the number of copies of the effective length for the actual region length calculation. calculation is as follows: reserved space = replication * length
|}

*{{Cmd|<entity>}} - container element for logging information
{| cellpadding="3" border="1" style="border: 1px solid rgb(85, 85, 85); border-collapse: collapse;"
| '''attribute''' || '''values''' || '''description'''
|-
| id || yes || string value || unique name of the entity
|}
*{{Cmd|<entity><config>}} - specifies the entity specific configuration parameters
{| cellpadding="3" border="1" style="border: 1px solid rgb(85, 85, 85); border-collapse: collapse;"
| '''attribute''' || '''mandatory''' || '''values''' || '''description'''
|-
| type || yes || "raw" - raw byte access "partition" - partiton level access "partition table" - partition table information || specifies the type of the entity
|-
| offset || no ||numeric value || specifies the relative offset in bytes from the start of the region
|-
| length || no ||numeric value "sectorsize" - use the device sector size "blocksize" - use the device block size "auto" - calculate the length according to the source file info || specifies the entity length. The actual region length can be affected with other attributes.
|-
| alignment || no || numeric value "blocksize" - use the device block size "sectorsize" - use the device sector size|| specifies the alignment of the entity
|-
| reserve || no || percentage value(e.g. "10%")|| specifies the size of the extra space to reserve in percents of the specified length
|-
| replication || no || numeric value || specifies the number of copies of the effective length for the actual region length calculation. calculation is as follows: reserved space = replication * length
|}

Each of the above container elements can include the following elements:
*{{Cmd|<source>}} - specifies the file on the storage media that provides content for the device/region/entity. Used for both store and upload commands.
{| cellpadding="3" border="1" style="border: 1px solid rgb(85, 85, 85); border-collapse: collapse;"
| '''attribute''' || '''values''' || '''description'''
|-
| file || string || name of the file on the source storage
|-
| format || "raw" - indicates raw binary format (e.g. nb0) "bin" - indicates .bin format (e.g. NK.bin)|| file format used by Updater Application to parse the content of the source file
|}

=====General Target storage clarifications=====
* The order of the device/region/entity in the XML file is important
* Each device/region/entity starts where the last device/region/entity has ended
=====Target storage XML syntax example=====
Target storage syntax example is taken from CM-T3530 NAND layout definition:
<pre>
<target_storage>
<device id="nand1">
<config type="nand" chipid="1" sectorsize="0x800" blocksize="0x20000"></config>
<region id="boot_region">
<config type="boot" start="0x0" alignment="blocksize"></config>
<entity id="boot_content">
<config type ="raw" offset="0x0000" length="blocksize" replication="6" alignment="blocksize"></config>
<source file="CMT35-nand.raw" format="raw"></source>
</entity>
<entity id="splashscreen">
<config type ="raw" length="auto" alignment="blocksize"></config>
<source file="splashscreen.bmp" format="raw"></source>
</entity>
</region>
<region id="os_region">
<config type="os" alignment="blocksize"></config>
<source file="os_region.nb0" format="raw"></source>
<entity id="os_partition_table">
<config type="partition_table"></config>
</entity>
<entity id="partition_nk">
<config type="partition" name="nk" length="auto" reserve="10%" alignment="sectorsize"></config>
<source file="nk.bin" format="bin"></source>
</entity>
<entity id="partition_system">
<config type="partition" name="system" alignment="sectorsize"></config>
</entity>
</region>
<region id="reserve_region">
<config type="reserve" length="blocksize" replication="10" alignment="blocksize"></config>
</region>
</device>
</target_storage>
</pre>

==== Update flow actions XML section ====
The {{Cmd|<actions}} element is used to define the update flow actions section. The following XML elements are used in this section:

*{{Cmd|<action>}} - container element for the update flow action information (e.g. store, upload, ..).
{| cellpadding="3" border="1" style="border: 1px solid rgb(85, 85, 85); border-collapse: collapse;"
| '''attribute''' || '''mandatory''' || '''values''' || '''description'''
|-
| type || yes || "erase" "store" "upload" "create_partition" "format_partition" "update_parameter" "reserve" "reset"|| specifies the type of the action to execute by Updater Application. When "reserve" action is used, it must be the first action to be performed on the target.
|-
| subtype || no || for {{Cmd|store/upload}} action type: "raw" - raw byte access "processed" - raw byte access and low level meta inforamtion "filesystem" - file based access for {{Cmd|update_parameter}} action type: "offset" - binary structure parameters (e.g. Eboot parameters) "keyvalue" - key value parameters (e.g. U-boot parameters) || specifies more information about the action. This allows to preoperly parse the action parameters
|}
*{{Cmd|<action><target>}} - container element for the target storage information
{| cellpadding="3" border="1" style="border: 1px solid rgb(85, 85, 85); border-collapse: collapse;"
| '''attribute''' || '''mandatory''' || '''values''' || '''description'''
|-
| id || yes || string value || unique name of the target storage layout part. Must be the same as the '''id''' attribute in the corresponding target storage entity/region/device section.
|}
*{{Cmd|<action><params>}} - container element for the action parameters
{| cellpadding="3" border="1" style="border: 1px solid rgb(85, 85, 85); border-collapse: collapse;"
| '''attribute''' || '''mandatory''' || '''values''' || '''description'''
|-
| oem_attribute|| no || "readonly" "reserved" "reserved_readonly" || specifies the additional OEM attributes for the target storage access (used in FAL/FMD model)
|-
| part_type|| yes, for {{Cmd|create_partition}} action || "binfs" "dos3_fat" "dos4_fat" "binary" "bootsection" "dos32_fat" || specifies the partition type for {{Cmd|create_partition}} action
|-
| part_active|| no || "true" "false" || specifies the active partition request for {{Cmd|create_partition}} action
|-
| part_readonly|| no || "true" "false" || specifies the readonly partition request for {{Cmd|create_partition}} action
|-
| format_tfat|| no || "true" "false" || specifies the TFAT format option for {{Cmd|format_partition}} action
|-
| format_exfat|| no || "true" "false" || specifies the EXFAT format option for {{Cmd|format_partition}} action
|-
| param_name|| yes, for {{Cmd|update_parameter}} action with '''keyvalue''' subtype || string value || specifies the name of the parameter for {{Cmd|update_parameter}} action with '''keyvalue''' subtype
|-
| param_type|| yes, for {{Cmd|update_parameter}} action with '''offset''' subtype || "string" - string value "number" - numeric value "reserved" - parameter value obtained from the source information|| specifies the type of the parameter for {{Cmd|update_parameter}} action
|-
| param_value|| yes, for {{Cmd|update_parameter}} action || string value numeric value "image_start" - image start parsed from NK.bin "image_length" - image length parsed from NK.bin "kernel_start" - kernel section start parsed from NK.bin "kernel_length" - kernel section length parsed from NK.bin|| specifies the value of the parameter for {{Cmd|update_parameter}} action
|-
| image_entity|| no || string value || specifies the target storage entity with NK.bin for extraction of reserved parameters (e.g. kernel_start) for {{Cmd|update_parameter}} action
|-
| param_offset|| yes, for {{Cmd|update_parameter}} action with '''offset''' subtype || numeric value || specifies the offset of the parameter in binary parameters structure for {{Cmd|update_parameter}} action with '''offset''' subtype
|-
| param_length|| yes, for {{Cmd|update_parameter}} action with '''offset''' subtype || numeric value || specifies the length of the parameter in binary parameters structure for {{Cmd|update_parameter}} action with '''offset''' subtype
|-
|}

===== Update flow acitons summary =====
* erase - erase disk/region/entity of the target media
* store - store disk/region/entity content from the source media in to the target disk/region/entity (performs automatic erase if needed)
** store raw - store in .dio/.nb0 format
** store processed - store in .dio.postproc format with FAL meta information (to be developed)
** store filesystem - store files from archive/cab (To be developed)
* upload - upload disk/region/entity to the source storage
** upload raw - upload in .dio/.nb0 format
** upload processed - upload in .dio.postproc format with FAL information (to be developed)
** upload filesystem - upload snapshot files into archive/cab (to be developed)
* create_partition - add new partition to the partition table. If partition table doesn't exist it will be created automatically
* format_partition - format specific partition with certain file system
* update_parameter - apply incremental update to bootloader/bootstrap environment or parameters block
* reserve - reserve some target media blocks from the scope of the block device driver
* reset - perform reset to the system

=====Update flow actions XML syntax example=====
<pre>
<actions>
<action type="reserve">
<target id="reserve_region"></target>
<params oem_attribute="reserved_readonly"></params>
</action>
<action type="store" subtype="raw">
<target id="boot_content"></target>
<params block_status="reserved" oem_attribute="reserved_readonly"></params>
</action>
<action type="store" subtype="raw">
<target id="splashscreen"></target>
<params block_status="reserved" oem_attribute="reserved_readonly"></params>
</action>
<action type="erase">
<target id="os_region"></target>
</action>
<action type="partition_create">
<target id="partition_nk"></target>
<params part_type="bootsection" active="false"></params>
</action>
<action type="partition_create">
<target id="partition_system"></target>
<params part_type="dos32_fat" active="false"></params>
</action>
<action type="store" subtype="raw">
<target id="partition_nk"></target>
</action>
</actions>
</pre>

= See Also =
[[Category:Windows CE|Updater Framework]]