Compulab Mediawiki - User contributions [en]

CM-QS600: Android: Operating instructions

2015-03-22T07:09:32Z

Nadav: /* P9 100mil header */

= Overview =
Most CM-QS600 [http://compulab.co.il/products/operating-systems-and-drivers-for-cm-qs600-and-sbc-qs600 supported features] are operated using normal Android controls. 
This page contains information about features and services, which are less straight-forward to operate, or are less widely known.

= Operating instructions =
=== Automatic suspend when inactive ===
By default, CM-QS600 is configured to stay awake while connected to the power. 
In order to change this behavior, proceed to '''Settings'''->'''Developer options''', uncheck '''Stay awake ... while charging''' to enable the device going to suspended state.
{{Note|If '''Developer options''' item is hidden, re-introduce it proceeding to '''Settings'''->'''About tablet''' and clicking on '''Build number''' 7 times consequently.}}

=== Start-up script ===
'''/system/etc/startup-svc.sh''' script is run upon system boot by Android ''init'' process with ''root'' permissions. 
As ''system'' partition is mounted 'read-only', one should remount ''system'' 'rw', prior to attempting to edit the script.

=== Networking ===
Normal Android behavior is to prioritize network interfaces (in descend order):
* Ethernet
* Wi-Fi
* 3G
Whenever higher-priority network interface is available, the lower-priority interfaces will be torn down.

=== (Optional) 3G Modem ===
In case '''Telit HE910-XX''' 3G modem is installed, it will be detected automatically, by start-up service, with no additional action required. 

=== Audio sink selection ===
CM-QS600 may use either '''HDMI''' or '''analog''' audio device.
Audio sink selection should be done with a designated application, e.g. ''SoundAbout'', available via Google Play Store.

{| class="wikitable" border="1" cellspacing="0"
! audio device
! sink name
|-
| HDMI
| Aux Digital (HDMI)
|-
| analog
| Wired Headphones
|}

{{Note|If after making the selection with ''SoundAbout'' nothing happens, restart the application.}}

=== P9 header ===
* SPI.0
: By default, SPI.0 is routed to the P9 header:
: pin 1 : Clk
: pin 3 : nCS
: pin 5 : MOSI
: pin 7 : MISO

* UART (<code> /dev/ttyHSL1 </code>)
: In order to override the default routing, the kernel should be [[CM-QS600: Android: Building from source code#Build_boot_image_.28kernel_.2B_initramfs.29 | rebuilt]] with patched CM-QS600 board file (<code> kernel/arch/arm/mach-msm/board-cm-qs600.c </code>):
<pre>
- #define CM_QS600_GSBI4_AS_SPI
+ // #define CM_QS600_GSBI4_AS_SPI
</pre>
UART routing to the P9 header:
: pin 5 : TX
: pin 7 : RX

[[Category:Android]]
[[Category:CM-QS600]]

CM-QS600: Android: Operating instructions

2015-03-22T07:08:55Z

Nadav:

= Overview =
Most CM-QS600 [http://compulab.co.il/products/operating-systems-and-drivers-for-cm-qs600-and-sbc-qs600 supported features] are operated using normal Android controls. 
This page contains information about features and services, which are less straight-forward to operate, or are less widely known.

= Operating instructions =
=== Automatic suspend when inactive ===
By default, CM-QS600 is configured to stay awake while connected to the power. 
In order to change this behavior, proceed to '''Settings'''->'''Developer options''', uncheck '''Stay awake ... while charging''' to enable the device going to suspended state.
{{Note|If '''Developer options''' item is hidden, re-introduce it proceeding to '''Settings'''->'''About tablet''' and clicking on '''Build number''' 7 times consequently.}}

=== Start-up script ===
'''/system/etc/startup-svc.sh''' script is run upon system boot by Android ''init'' process with ''root'' permissions. 
As ''system'' partition is mounted 'read-only', one should remount ''system'' 'rw', prior to attempting to edit the script.

=== Networking ===
Normal Android behavior is to prioritize network interfaces (in descend order):
* Ethernet
* Wi-Fi
* 3G
Whenever higher-priority network interface is available, the lower-priority interfaces will be torn down.

=== (Optional) 3G Modem ===
In case '''Telit HE910-XX''' 3G modem is installed, it will be detected automatically, by start-up service, with no additional action required. 

=== Audio sink selection ===
CM-QS600 may use either '''HDMI''' or '''analog''' audio device.
Audio sink selection should be done with a designated application, e.g. ''SoundAbout'', available via Google Play Store.

{| class="wikitable" border="1" cellspacing="0"
! audio device
! sink name
|-
| HDMI
| Aux Digital (HDMI)
|-
| analog
| Wired Headphones
|}

{{Note|If after making the selection with ''SoundAbout'' nothing happens, restart the application.}}

=== P9 100mil header ===
* SPI.0
: By default, SPI.0 is routed to the P9 header:
: pin 1 : Clk
: pin 3 : nCS
: pin 5 : MOSI
: pin 7 : MISO

* UART (<code> /dev/ttyHSL1 </code>)
: In order to override the default routing, the kernel should be [[CM-QS600: Android: Building from source code#Build_boot_image_.28kernel_.2B_initramfs.29 | rebuilt]] with patched CM-QS600 board file (<code> kernel/arch/arm/mach-msm/board-cm-qs600.c </code>):
<pre>
- #define CM_QS600_GSBI4_AS_SPI
+ // #define CM_QS600_GSBI4_AS_SPI
</pre>
UART routing to the P9 header:
: pin 5 : TX
: pin 7 : RX

[[Category:Android]]
[[Category:CM-QS600]]

CM-QS600: Android: Building from source code

2015-03-22T07:06:04Z

Nadav:

= Prerequisites =
The required steps, as outlined below, were tested on Ubuntu 14.04 (Trusty). 
Install required packages, as outlined on [http://source.android.com/source/initializing.html#installing-required-packages-ubuntu-1404 AOSP web-page]. 
Install additional packages (not listed on AOSP web-page):
$ sudo apt-get install xz-utils make flex lib32z1 zip

= Getting Android Source Code =
== Overview ==
CompuLab Android package is obtained by applying CompuLab patches on top of Code Aurora Forum's Android package for MSM APQ8064 CDP platform.

== Download software packages ==
Proceed to CM-QS600 [http://www.compulab.co.il/cm-qs600-android-package-registration-required/ Android Package] page and download the Android Source archive in order to acquire the following software packages:
* '''Qualcomm proprietary libraries'''
: Prebuilt Qualcomm proprietary libraries.
* '''CompuLab patches on top of Android for MSM APQ8064'''
: CompuLab patches on top of Android source code tree include, among other, Linux kernel patches, Android device configuration files and firmware binary blobs.

== Deploy Android source code repository ==
=== Code Aurora Forum base ===
Download the code base from Code Aurora Forum (CAF):
$ mkdir myandroid
$ cd myandroid
$ repo init -u git://codeaurora.org/platform/manifest.git -b release -m '''LNX.LA.2.7-06310-8064.0.xml''' --repo-url=git://codeaurora.org/tools/repo.git --repo-branch=caf-stable
$ repo sync -j4
$ repo forall -c "git checkout -b codeaurora"

{{Note | The last instruction maintains git branch naming convention, which is useful for clarity, but is not strictly necessary.}}

=== Qualcomm proprietary prebuilt libraries ===
Extract prebuilt Qualcomm proprietary libraries:
$ mkdir -p myandroid/vendor/qcom/proprietary
$ tar -xJf cm-qs600-qcom-proprietary.tar.xz -C myandroid/vendor/qcom/proprietary

=== CompuLab patch ===
Apply CompuLab patch:
$ mkdir -p /tmp/sandbox
$ tar -xJf cm-qs600-compulab-patch.tar.xz -C /tmp/sandbox
$ cd myandroid
$ /tmp/sandbox/compulab-patch-apply /tmp/sandbox

=== Wireless kernel driver ===
Clone out of tree wireless kernel driver:
$ cd myandroid/external
$ git clone --branch upstream https://github.com/compulab/cm-qs600-compat-wireless.git compat-wireless

== Building Android image ==
$ cd myandroid
$ export USE_CCACHE=1
$ source build/envsetup.sh
$ choosecombo 1 bellatrix 3
$ make -j4 BUILD_ID=CM-QS600 BUILD_NUMBER=20140901

In case Java version different from the system default, is required by the build system, download the required JDK version, and export path to its root directory:
$ export JAVA_HOME=<full path to JDK>

While the '''make''' instruction above builds the whole Android image, including all its partitions, it is possible to build '''boot''' partition only, which is useful for most Android hacking as the '''boot''' partition contains the '''kernel''' and the '''ramfs''' with most configuration files:
==== Bring up kernel configuration menu ====
$ make kernelconfig

==== Build boot image (kernel + initramfs) ====
$ make bootimage -j4

== Summary ==
Upon successful build, the output directory (<code> myandroid/out/target/product/bellatrix </code>) contains ready to deploy OS partitions represented both as directories with appropriate files and compressed image files ready to deploy on eMMC:
{| class="wikitable" border="1" cellspacing="0"
! partition name
! directory
! image file
! file system type
! access
! mount point
! default partition size [MB]
! designation
! notes
|-
| boot
| root
| boot.img
| style="text-align:center;" | -
| read only
| style="text-align:center;" | -
| 20
| kernel, ramdisk
| style="text-align:center;" | -
|-
| recovery
| recovery
| recovery.img
| style="text-align:center;" | -
| read only
| style="text-align:center;" | -
| 20
| alternative to ''boot'' for recovery and upgrade
| currently not in use
|-
| system
| system
| system.img
| style="text-align:center;" | ext4
| read only
| /system
| 512
| the entire OS: 
Android UI, system applications
| style="text-align:center;" | -
|-
| cache
| cache
| cache.img
| style="text-align:center;" | ext4
| read / write
| /cache
| 64
| frequently accessed data cache
| style="text-align:center;" | -
|-
| userdata
| data
| userdata.img
| style="text-align:center;" | ext4
| read / write
| /data
| 2048
| user applications and content
| style="text-align:center;" | -
|-
|}

= Deploying Android Image on Target Medium =
== Overview ==
In normal boot mode, the root of the file system is mounted from RAM-disk, whereas storage device partitions containing system utilities, applications and data are mounted under it. 
Root on a physical device, or file system mounted via NFS are also viable options, but are used mainly throughout development stage. 
LK bootloader expects a valid boot partition ('''boot.img''') on the eMMC. ''System'', ''userdata'' and ''cache'' partitions mounting is ruled by ''fstab'' file - they can reside on any available storage device. 
In case LK does not identify a valid boot partition on the eMMC, it falls back to [[Android: Fastboot setup | ''fastboot mode'']], where it is possible, along with other options, to load ''boot.img'' dynamically from PC workstation.

=== [[CM-QS600: Android: Getting started#Installation onto eMMC | Deploy file system on eMMC]] ===
* Enter ''fastboot mode''.
* Flash each partition image file to the eMMC with the aid of ''fastboot'' utility:
<pre>
$ fastboot flash boot boot.img
$ fastboot flash system system.img
$ fastboot flash cache cache.img
$ fastboot flash userdata userdata.img
</pre>

=== Deploy file system on SD-card ===
==== Prepare SD-card ====
* [http://linux.die.net/man/8/gdisk GPT-partition] SD-card, creating ''system'', ''cache'', ''userdata'' partitions, and setting GPT names of the partitions appropriately.
* Format each partition with ''ext4'' file system.
* Copy ''system'' partition contents, maintaining proper file permissions
: (assuming the designated target medium is mounted on your workstation under ''/media/<username>''):
$ export OUT=myandroid/out/target/product/bellatrix
$ export SYSTEM=/media/<username>/system
$ cp -a ${OUT}/system/* ${SYSTEM}/.
$ for f in `find ${SYSTEM}`; do [ -f ${f} ] && chmod go-w ${f}; [ `echo ${f} | awk /\.so$/` ] && chmod a-x ${f}; done

==== Re-build ''boot.img'' with patched ''fstab'' ====
* Edit ''device/qcom/bellatrix/fstab.qcom'' file, in order to override default destination medium device:
<pre>
#boot time mount
- /dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,barrier=1 wait
+ /dev/block/platform/msm_sdcc.3/by-name/system /system ext4 ro,barrier=1 wait
- /dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 nosuid,nodev,noatime,barrier=1 wait,check
+ /dev/block/platform/msm_sdcc.3/by-name/cache /cache ext4 nosuid,nodev,noatime,barrier=1 wait,check
- /dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 nosuid,nodev,noatime,barrier=1,noauto_da_alloc wait,check,length=1073741824,encryptable=footer
+ /dev/block/platform/msm_sdcc.3/by-name/userdata /data ext4 nosuid,nodev,noatime,barrier=1,noauto_da_alloc wait,check,length=1073741824,encryptable=footer
</pre>

* Rebuild ''boot.img'':
$ make bootimage -j4

==== Flash ''boot.img'' onto eMMC ====
As pointed out above, ''boot.img'' has to reside on the eMMC, flash it via ''fastboot'' utility:
$ fastboot flash boot boot.img

= See Also =
* [https://www.codeaurora.org CodeAurora Forum website]
* [http://source.android.com/source/building.html Android|Downloading and Building]
* [http://source.android.com/source/developing.html Android|Developing with Repo and Git]
* [http://source.android.com/devices/index.html Android|Subsystems explained]
* [http://www.kandroid.org/online-pdk/guide/build_system.html AOSP|Android Build System]
* [http://blogofterje.wordpress.com/2012/01/14/optimizing-fs-on-sd-card Some thoughts about partitioning flash storage devices]

[[Category:Android]]
[[Category:CM-QS600]]

CM-QS600: Android: Building from source code

2015-03-19T13:00:48Z

Nadav:

= Prerequisites =
The required steps, as outlined below, were tested on Ubuntu 14.04 (Trusty). 
Install required packages, as outlined on [http://source.android.com/source/initializing.html#installing-required-packages-ubuntu-1404 AOSP web-page]. 
Install additional packages (not listed on AOSP web-page):
$ sudo apt-get install xz-utils make flex lib32z1 zip

= Getting Android Source Code =
== Overview ==
CompuLab Android package is obtained by applying CompuLab patches on top of Code Aurora Forum's Android package for MSM APQ8064 CDP platform.

== Download software packages ==
Proceed to CM-QS600 [http://www.compulab.co.il/cm-qs600-android-package-registration-required/ Android Package] page and download the Android Source archive in order to acquire the following software packages:
* '''Qualcomm proprietary libraries'''
: Prebuilt Qualcomm proprietary libraries.
* '''CompuLab patches on top of Android for MSM APQ8064'''
: CompuLab patches on top of Android source code tree include, among other, Linux kernel patches, Android device configuration files and firmware binary blobs.

== Deploy Android source code repository ==
=== Code Aurora Forum base ===
Download the code base from Code Aurora Forum (CAF):
$ mkdir myandroid
$ cd myandroid
$ repo init -u git://codeaurora.org/platform/manifest.git -b release -m '''LNX.LA.2.7-06310-8064.0.xml''' --repo-url=git://codeaurora.org/tools/repo.git --repo-branch=caf-stable
$ repo sync -j4
$ repo forall -c "git checkout -b codeaurora"

{{Note | The last instruction maintains git branch naming convention, which is useful for clarity, but is not strictly necessary.}}

=== Qualcomm proprietary prebuilt libraries ===
Extract prebuilt Qualcomm proprietary libraries:
$ mkdir -p myandroid/vendor/qcom/proprietary
$ tar -xJf cm-qs600-qcom-proprietary.tar.xz -C myandroid/vendor/qcom/proprietary

=== CompuLab patch ===
Apply CompuLab patch:
$ mkdir -p /tmp/sandbox
$ tar -xJf cm-qs600-compulab-patch.tar.xz -C /tmp/sandbox
$ cd myandroid
$ /tmp/sandbox/compulab-patch-apply /tmp/sandbox

=== Wireless kernel driver ===
Clone out of tree wireless kernel driver:
$ cd myandroid/external
$ git clone --branch upstream https://github.com/compulab/cm-qs600-compat-wireless.git compat-wireless

== Building Android image ==
$ cd myandroid
$ export USE_CCACHE=1
$ source build/envsetup.sh
$ choosecombo 1 bellatrix 3
$ make -j4 BUILD_ID=CM-QS600 BUILD_NUMBER=20140901

In case Java version different from the system default, is required by the build system, download the required JDK version, and export path to its root directory:
$ export JAVA_HOME=<full path to JDK>

While the '''make''' instruction above builds the whole Android image, including all its partitions, it is possible to build '''boot''' partition only, which is useful for most Android hacking as the '''boot''' partition contains the '''kernel''' and the '''ramfs''' with most configuration files:
==== Bring up kernel configuration menu ====
$ make kernelconfig

==== Build boot image (kernel + initramfs) ====
$ make bootimage -j4

== Summary ==
Upon successful build, the output directory (<code> myandroid/out/target/product/bellatrix </code>) contains ready to deploy OS partitions represented both as directories with appropriate files and compressed image files ready to deploy on eMMC:
{| class="wikitable" border="1" cellspacing="0"
! partition name
! directory
! image file
! file system type
! access
! mount point
! default partition size [MB]
! designation
! notes
|-
| boot
| root
| boot.img
| style="text-align:center;" | -
| read only
| style="text-align:center;" | -
| 20
| kernel, ramdisk
| style="text-align:center;" | -
|-
| recovery
| recovery
| recovery.img
| style="text-align:center;" | -
| read only
| style="text-align:center;" | -
| 20
| alternative to ''boot'' for recovery and upgrade
| currently not in use
|-
| system
| system
| system.img
| style="text-align:center;" | ext4
| read only
| /system
| 512
| the entire OS: 
Android UI, system applications
| style="text-align:center;" | -
|-
| cache
| cache
| cache.img
| style="text-align:center;" | ext4
| read / write
| /cache
| 64
| frequently accessed data cache
| style="text-align:center;" | -
|-
| userdata
| data
| userdata.img
| style="text-align:center;" | ext4
| read / write
| /data
| 2048
| user applications and content
| style="text-align:center;" | -
|-
|}

= Deploying Android Image on Target Medium =
== Overview ==
In normal boot mode, the root of the file system is mounted from RAM-disk, whereas storage device partitions containing system utilities, applications and data are mounted under it. 
Root on a physical device, or file system mounted via NFS are also viable options, but are used mainly throughout development stage. 
LK bootloader expects a valid boot partition ('''boot.img''') on the eMMC. ''System'', ''userdata'' and ''cache'' partitions mounting is ruled by ''fstab'' file - they can reside on any available storage device. 
In case LK does not identify a valid boot partition on the eMMC, it falls back to [[Android: Fastboot setup | ''fastboot mode'']], where it is possible, along with other options, to load ''boot.img'' dynamically from PC workstation.

=== [[CM-QS600: Android: Getting started#Installation onto eMMC | Deploy file system on eMMC]] ===
* Enter ''fastboot mode''.
* Flash each partition image file to the eMMC with the aid of ''fastboot'' utility:
<pre>
$ fastboot flash boot boot.img
$ fastboot flash system system.img
$ fastboot flash cache cache.img
$ fastboot flash userdata userdata.img
</pre>

=== Deploy file system on SD-card ===
==== Prepare SD-card ====
* [http://linux.die.net/man/8/gdisk GPT-partition] SD-card, creating ''system'', ''cache'', ''userdata'' partitions.
* Format each partition with ''ext4'' file system.
* Copy ''system'' partition contents, maintaining proper file permissions:
$ cp -a ${OUT}/system/* ${SYSTEM}/.
$ for f in `find ${SYSTEM}`; do [ -f ${f} ] && chmod go-w ${f}; [ `echo ${f} | awk /\.so$/` ] && chmod a-x ${f}; done

==== Re-build ''boot.img'' with patched ''fstab'' ====
* Edit ''device/qcom/bellatrix/fstab.qcom'' file, in order to override default destination medium device:
<pre>
#boot time mount
- /dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,barrier=1 wait
+ /dev/block/platform/msm_sdcc.3/by-name/system /system ext4 ro,barrier=1 wait
- /dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 nosuid,nodev,noatime,barrier=1 wait,check
+ /dev/block/platform/msm_sdcc.3/by-name/cache /cache ext4 nosuid,nodev,noatime,barrier=1 wait,check
- /dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 nosuid,nodev,noatime,barrier=1,noauto_da_alloc wait,check,length=1073741824,encryptable=footer
+ /dev/block/platform/msm_sdcc.3/by-name/userdata /data ext4 nosuid,nodev,noatime,barrier=1,noauto_da_alloc wait,check,length=1073741824,encryptable=footer
</pre>

* Rebuild ''boot.img'':
$ make bootimage -j4

==== Flash ''boot.img'' onto eMMC ====
As pointed out above, ''boot.img'' has to reside on the eMMC, flash it via ''fastboot'' utility:
$ fastboot flash boot boot.img

= See Also =
* [https://www.codeaurora.org CodeAurora Forum website]
* [http://source.android.com/source/building.html Android|Downloading and Building]
* [http://source.android.com/source/developing.html Android|Developing with Repo and Git]
* [http://source.android.com/devices/index.html Android|Subsystems explained]
* [http://www.kandroid.org/online-pdk/guide/build_system.html AOSP|Android Build System]

[[Category:Android]]
[[Category:CM-QS600]]

CM-QS600: Android: Building from source code

2015-03-19T12:56:45Z

Nadav:

= Prerequisites =
The required steps, as outlined below, were tested on Ubuntu 14.04 (Trusty). 
Install required packages, as outlined on [http://source.android.com/source/initializing.html#installing-required-packages-ubuntu-1404 AOSP web-page]. 
Install additional packages (not listed on AOSP web-page):
$ sudo apt-get install xz-utils make flex lib32z1 zip

= Getting Android Source Code =
== Overview ==
CompuLab Android package is obtained by applying CompuLab patches on top of Code Aurora Forum's Android package for MSM APQ8064 CDP platform.

== Download software packages ==
Proceed to CM-QS600 [http://compulab.co.il/products/computer-on-modules/cm-qs600/#devres Downloads] page in order to acquire the following software packages:
* '''Qualcomm proprietary libraries'''
: Prebuilt Qualcomm proprietary libraries.
* '''CompuLab patches on top of Android for MSM APQ8064'''
: CompuLab patches on top of Android source code tree include, among other, Linux kernel patches, Android device configuration files and firmware binary blobs.

== Deploy Android source code repository ==
=== Code Aurora Forum base ===
Download the code base from Code Aurora Forum (CAF):
$ mkdir myandroid
$ cd myandroid
$ repo init -u git://codeaurora.org/platform/manifest.git -b release -m '''LNX.LA.2.7-06310-8064.0.xml''' --repo-url=git://codeaurora.org/tools/repo.git --repo-branch=caf-stable
$ repo sync -j4
$ repo forall -c "git checkout -b codeaurora"

{{Note | The last instruction maintains git branch naming convention, which is useful for clarity, but is not strictly necessary.}}

=== Qualcomm proprietary prebuilt libraries ===
Extract prebuilt Qualcomm proprietary libraries:
$ mkdir -p myandroid/vendor/qcom/proprietary
$ tar -xJf cm-qs600-qcom-proprietary.tar.xz -C myandroid/vendor/qcom/proprietary

=== CompuLab patch ===
Apply CompuLab patch:
$ mkdir -p /tmp/sandbox
$ tar -xJf cm-qs600-compulab-patch.tar.xz -C /tmp/sandbox
$ cd myandroid
$ /tmp/sandbox/compulab-patch-apply /tmp/sandbox

=== Wireless kernel driver ===
Clone out of tree wireless kernel driver:
$ cd myandroid/external
$ git clone --branch upstream https://github.com/compulab/cm-qs600-compat-wireless.git compat-wireless

== Building Android image ==
$ cd myandroid
$ export USE_CCACHE=1
$ source build/envsetup.sh
$ choosecombo 1 bellatrix 3
$ make -j4 BUILD_ID=CM-QS600 BUILD_NUMBER=20140901

In case Java version different from the system default, is required by the build system, download the required JDK version, and export path to its root directory:
$ export JAVA_HOME=<full path to JDK>

While the '''make''' instruction above builds the whole Android image, including all its partitions, it is possible to build '''boot''' partition only, which is useful for most Android hacking as the '''boot''' partition contains the '''kernel''' and the '''ramfs''' with most configuration files:
==== Bring up kernel configuration menu ====
$ make kernelconfig

==== Build boot image (kernel + initramfs) ====
$ make bootimage -j4

== Summary ==
Upon successful build, the output directory (<code> myandroid/out/target/product/bellatrix </code>) contains ready to deploy OS partitions represented both as directories with appropriate files and compressed image files ready to deploy on eMMC:
{| class="wikitable" border="1" cellspacing="0"
! partition name
! directory
! image file
! file system type
! access
! mount point
! default partition size [MB]
! designation
! notes
|-
| boot
| root
| boot.img
| style="text-align:center;" | -
| read only
| style="text-align:center;" | -
| 20
| kernel, ramdisk
| style="text-align:center;" | -
|-
| recovery
| recovery
| recovery.img
| style="text-align:center;" | -
| read only
| style="text-align:center;" | -
| 20
| alternative to ''boot'' for recovery and upgrade
| currently not in use
|-
| system
| system
| system.img
| style="text-align:center;" | ext4
| read only
| /system
| 512
| the entire OS: 
Android UI, system applications
| style="text-align:center;" | -
|-
| cache
| cache
| cache.img
| style="text-align:center;" | ext4
| read / write
| /cache
| 64
| frequently accessed data cache
| style="text-align:center;" | -
|-
| userdata
| data
| userdata.img
| style="text-align:center;" | ext4
| read / write
| /data
| 2048
| user applications and content
| style="text-align:center;" | -
|-
|}

= Deploying Android Image on Target Medium =
== Overview ==
In normal boot mode, the root of the file system is mounted from RAM-disk, whereas storage device partitions containing system utilities, applications and data are mounted under it. 
Root on a physical device, or file system mounted via NFS are also viable options, but are used mainly throughout development stage. 
LK bootloader expects a valid boot partition ('''boot.img''') on the eMMC. ''System'', ''userdata'' and ''cache'' partitions mounting is ruled by ''fstab'' file - they can reside on any available storage device. 
In case LK does not identify a valid boot partition on the eMMC, it falls back to [[Android: Fastboot setup | ''fastboot mode'']], where it is possible, along with other options, to load ''boot.img'' dynamically from PC workstation.

=== [[CM-QS600: Android: Getting started#Installation onto eMMC | Deploy file system on eMMC]] ===
* Enter ''fastboot mode''.
* Flash each partition image file to the eMMC with the aid of ''fastboot'' utility:
<pre>
$ fastboot flash boot boot.img
$ fastboot flash system system.img
$ fastboot flash cache cache.img
$ fastboot flash userdata userdata.img
</pre>

=== Deploy file system on SD-card ===
==== Prepare SD-card ====
* [http://linux.die.net/man/8/gdisk GPT-partition] SD-card, creating ''system'', ''cache'', ''userdata'' partitions.
* Format each partition with ''ext4'' file system.
* Copy ''system'' partition contents, maintaining proper file permissions:
$ cp -a ${OUT}/system/* ${SYSTEM}/.
$ for f in `find ${SYSTEM}`; do [ -f ${f} ] && chmod go-w ${f}; [ `echo ${f} | awk /\.so$/` ] && chmod a-x ${f}; done

==== Re-build ''boot.img'' with patched ''fstab'' ====
* Edit ''device/qcom/bellatrix/fstab.qcom'' file, in order to override default destination medium device:
<pre>
#boot time mount
- /dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,barrier=1 wait
+ /dev/block/platform/msm_sdcc.3/by-name/system /system ext4 ro,barrier=1 wait
- /dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 nosuid,nodev,noatime,barrier=1 wait,check
+ /dev/block/platform/msm_sdcc.3/by-name/cache /cache ext4 nosuid,nodev,noatime,barrier=1 wait,check
- /dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 nosuid,nodev,noatime,barrier=1,noauto_da_alloc wait,check,length=1073741824,encryptable=footer
+ /dev/block/platform/msm_sdcc.3/by-name/userdata /data ext4 nosuid,nodev,noatime,barrier=1,noauto_da_alloc wait,check,length=1073741824,encryptable=footer
</pre>

* Rebuild ''boot.img'':
$ make bootimage -j4

==== Flash ''boot.img'' onto eMMC ====
As pointed out above, ''boot.img'' has to reside on the eMMC, flash it via ''fastboot'' utility:
$ fastboot flash boot boot.img

= See Also =
* [https://www.codeaurora.org CodeAurora Forum website]
* [http://source.android.com/source/building.html Android|Downloading and Building]
* [http://source.android.com/source/developing.html Android|Developing with Repo and Git]
* [http://source.android.com/devices/index.html Android|Subsystems explained]
* [http://www.kandroid.org/online-pdk/guide/build_system.html AOSP|Android Build System]

[[Category:Android]]
[[Category:CM-QS600]]

CM-QS600 SW Resources

2015-03-09T11:51:15Z

Nadav:

CM-QS600 is a miniature Computer-on-Module (CoM) / System-on-Module (SoM) built around Qualcomm Snapdragon APQ8064 1.7GHz quad-core SoC with high-performance Adreno 320 GPU. CM-QS600 brings performance and power efficiency of embedded ARM to a new level, enabling design of cost-effective compute-intensive multimedia applications at a much smaller form-factor than ever before. Designed into a tiny footprint of 65 x 68 x 5 mm, CM-QS600 comes with up-to 2GB DDR3 RAM and 32GB of on-board eMMC storage and provides extensive connectivity with dual-band WiFi 802.11, Bluetooth 4.0, Gigabit Ethernet, PCIe, USB, SATA, HDMI, LVDS, serial ports and I/O lines. CompuLab supports CM-QS600 with comprehensive documentation and full ready-to-run SW packages for both Linux and Android. 
With best-in-class graphics and superior video capabilities CM-QS600 is a powerful platform for multimedia demanding applications such as digital signage, IPTV and media players. Miniature size, low power consumption and cutting-edge power management make CM-QS600 an excellent solution for portable and battery-powered systems. 

<div style="background: white; border: 1px solid black; padding: 1em;">
{| border="0" cellpadding="2" width="100%" align="center"
|-
! style="font-size: 125%; background-color: #eeeeee;" align="center" width="25%" | [[CM-QS600_Android | Android]]
! style="font-size: 125%; background-color: #eeeeee;" align="center" width="25%" | [[CM-QS600_Linux | Linux]]
|-

| align="center" | <linkedimage>
wikipage=CM-QS600_Android
tooltip=CM-QS600_Android documentation
img_src=Image:Android-mascot.jpg
img_width=200px
img_height=180px
img_alt=CM-QS600_Android
</linkedimage>

| align="center" | <linkedimage>
wikipage=CM-QS600_Linux
tooltip=CM-QS600 Linux documentation
img_src=Image:Linux-Logo.jpg
img_width=200px
img_height=180px
img_alt=CM-QS600_Linux
</linkedimage>

|}
</div>
__NOTOC__
{{ChangelogRss| content=
===== 9-March-2015, Android =====
: cm-qs600-android.15.03.1 released Android KitKat 4.4.3 (engineering build)
:- adapt to hardware revision 1.1
:- SD-card automount: fix a bug
:- enable LVDS display (Chi Mei)
:- enable SPI bus (spi.0) over GSBI-4
:- enable UART (/dev/ttyHSL1) over GSBI-4

===== 29-Dec-2014, Linux =====
: Linux kernel 3.4.0-14.10-cm-qs600-3 for CM-QS600 updates
:- Switched code base to Linaro Ubuntu [http://releases.linaro.org/14.10/ubuntu/boards/ifc6410 14.10 release] for Snapdragon 600
:- Added WLAN support
:- Added Bluetooth support
:- Added audio playback (analog, digital)
: Documentation
: - Updated multiple articles to comply with the new Linux package

===== 26-Oct-2014: cm-qs600-android.14.10.1 released =====
: ''Android KitKat 4.4.3 (engineering build)''
: - enable Wi-Fi networking
: - enable 3G modem
: - apply performance improvement patches provided by Qualcomm
: - automount removable media
: - switch automatic suspend policy to ''stay awake while charging'' by default
: - preinstall Google Play

===== 29-Sep-2014, Linux =====
: Linux kernel for CM-QS600 updates
:- Switched code base to Linaro Ubuntu [http://releases.linaro.org/14.09/ubuntu/ifc6410 14.09 release] for Snapdragon 600
:- Added HDMI video output support
:- Added SATA support
: Documentation
: - Updated multiple articles to comply with the new Linux package

===== 10-Aug-2014: cm-qs600-android.14.08.1 released =====
: Initial Android package release for CM-QS600 based on Android 4.4.3 (KitKat) for APQ8064 reference design by Qualcomm.

===== 05-Aug-2014, Linux =====
: Initial pre-release of Linux kernel and Debian Linux Demo image for CM-QS600
:- Kernel version is 3.4, source code is based [https://www.codeaurora.org/cgit/quic/la/kernel/msm/ Kernel tree for MSM] by Code Aurora
:- Basic support for the CM-QS600 module
:- MMC/SD card support
:- eMMC internal storage support
:- USB 2.0 host ports support
:- Ethernet support
:- Qualcomm PMIC8XXX RTC support

}}

[[Category:CM-QS600]]

CM-QS600 Android

2015-03-09T11:47:08Z

Nadav:

{{summary|
This page contains up to date information about the Android package and software development for the CompuLab CM-QS600 System-on-Module / Computer-on-Module.
|cm-qs600-top.jpg|thumb}}
{{Resources Linux
|* [[CM-QS600: Android: Getting started | Installation and boot]]
* [[CM-QS600: Android: Operating instructions | Operating instructions]]
* [http://compulab.co.il/products/computer-on-modules/cm-qs600/#devres Downloads]
|* [[CM-QS600: Android: Serial console connection | Serial console connection]]
* [[Android: Fastboot setup | Fastboot setup]]
* [[Android:_ADB_setup | ADB Setup]]
* [[CM-QS600: Android: Building from source code | Building from source code]]
|* [[Support]]
* [[CM-QS600: Android: Known Issues | Known Issues]]
}}

{{ChangelogRss| content=
===== 9-Mar-2015: cm-qs600-android.15.03.1 released =====
: ''Android KitKat 4.4.3 (engineering build)''
: - adapt to hardware release 1.1
: - SD-card automount: fix a bug
: - enable LVDS display (Chi Mei)
: - enable SPI bus (spi.0) over GSBI-4
: - enable UART (/dev/ttyHSL1) over GSBI-4
===== 26-Oct-2014: cm-qs600-android.14.10.1 released =====
: ''Android KitKat 4.4.3 (engineering build)''
: - enable Wi-Fi networking
: - enable 3G modem
: - fixed HDMI flickering
: - apply performance improvement patches provided by Qualcomm
: - automount removable media
: - switch automatic suspend policy to ''stay awake while charging'' by default
: - preinstall Google Play

===== 10-Aug-2014: cm-qs600-android.14.08.1 released =====
: Initial Android package release for CM-QS600 based on Android 4.4.3 (KitKat) for APQ8064 reference design by Qualcomm.

}}

[[Category:Android]]
[[Category:CM-QS600]]

CM-FX6 SW Resources

2015-02-11T13:27:56Z

Nadav:

CM-FX6 is a miniature computer-on-module (CoM) / system-on-module (SoM) board designed to serve as a building block in embedded applications. CM-FX6 is based on the Freescale i.MX6 application processor featuring a highly scalable single/dual/quad core Cortex-A9 CPU at up to 1.2GHz coupled with powerful graphics and video processing units. The processor is supplemented with up-to 4GB DDR3 and 32GB of on-board SSD. In addition, the CM-FX6 features extensive connectivity with a wide range of industry standard interfaces – GbE, PCIe, SATA, USB, RS232 and CAN bus.

CM-FX6 is provided with comprehensive documentation and full ready-to-run SW support for Linux, Android and Windows Embedded Compact 7 operating systems. 

<div style="background: white; border: 1px solid black; padding: 1em;">
{| border="0" cellpadding="2" width="100%" align="center"
|-
! style="font-size: 125%; background-color: #eeeeee;" align="center" width="25%" | [[CM-FX6_Android | Android]]
! style="font-size: 125%; background-color: #eeeeee;" align="center" width="25%" | [[CM-FX6_Windows_Embedded_Compact_7 | Windows Embedded Compact 7]]
! style="font-size: 125%; background-color: #eeeeee;" align="center" width="25%" | [[CM-FX6 Linux | Linux]]
! style="font-size: 125%; background-color: #eeeeee;" align="center" width="25%" | [[U-Boot_for_CM-FX6 | U-Boot]]
|-

| align="center" | <linkedimage>
wikipage=CM-FX6_Android
tooltip=CM-FX6_Android documentation
img_src=Image:Android-mascot.jpg
img_width=200px
img_height=180px
img_alt=CM-FX6 Android
</linkedimage>

| align="center" | <linkedimage>
wikipage=CM-FX6_Windows_Embedded_Compact_7
tooltip=CM-FX6 Windows Embedded Compact 7 documentation
img_src=Image:Windows-ce7.jpg
img_width=200px
img_height=180px
img_alt=CM-FX6 Windows Embedded Compact 7
</linkedimage>

| align="center" | <linkedimage>
wikipage=CM-FX6 Linux
tooltip=CM-FX6 Linux documentation
img_src=Image:Linux-Logo.jpg
img_width=200px
img_height=180px
img_alt=CM-FX6 Linux
</linkedimage>

| align="center" | <linkedimage>
wikipage=U-Boot_for_CM-FX6
tooltip=CM-FX6 U-Boot documentation
img_src=Image:U-boot.jpg
img_width=200px
img_height=180px
img_alt=CM-FX6 U-Boot
</linkedimage>
|}
</div>

__NOTOC__

{{ChangelogRss| content=
===== 10-Feb-2015, WEC7 =====
: New WEC7 BSP version released
: - Eboot modified in order to support the latest UBOOT

===== 08-Feb-2015, U-Boot =====
: U-Boot 2014.10-cm-fx6-2.1 release:
: - Add HDMI support
: - Add HDMI splash screen
: - Add framebuffer console
: - Add USB keyboard support

===== 16-Dec-2014, Android =====
: ''Jelly Bean 4.3'' release:
: - upgrade Freescale code base to the latest Jelly Bean release - IMX6_JB43_111
: - enable Phison SATA SSD module (along with SanDisk)
: - enhance SATA power management
: - apply selection of kernel patches fixing bugs and enhancing stability

===== 11-Dec-2014, Linux =====
: Linux kernel 3.0.35-cm-fx6-6.3 for CM-FX6 release:
: - Added SATA suspend resume
: - Added MIPI DSI support
: - Updated WiFi firmware
: - Changed default lcd display bpp to 32
: - Fixed occasional reboot issue
: Debian Linux image updates
: - Replaced both Debian Jessie/Sid and Sid with one Debian Wheezy image
: - Added FreeScale VPU libraries for Debian Wheezy
: Documentation
: - Updated multiple articles to comply with the new Linux package

===== 11-Nov-2014, Linux =====
: Documentation
: - Updated [[CM-FX6: Linux: Debian]] and [[CM-FX6: Linux: Kernel]] articles with CAN bus information

===== 06-Nov-2014, Linux =====
: Linux kernel 3.0.35-cm-fx6-6.2 for CM-FX6 release:
: - Fixed KD050C LCD timings
: - Fixed KD050C LCD touchscreen functionality
: - Fixed SATA device initialization
: - Fixed PCIE controller power/clock/reset sequence
: - Fixed overall stability
: Debian Linux image updates
: - Added Debian Sid Linux image
: Misc updates
: - Updated CompuLab EEPROM utility to version 2.0
: Documentation
: - Updated multiple articles to comply with the new Linux package

===== 02-Nov-2014, Android =====
: Android JB updates:
: - enable routing audio to S/PDIF
: - fix bug in ADS7846 touchscreen kernel driver
: - support m25px16 SPI flash ROM
: - fix rare cpu stalls in boundary temperature conditions
: - switch automatic suspend policy to ''stay awake while charging'' by default

===== 16-Sep-2014, U-Boot =====
: U-Boot 2014.04-cm-fx6-1.3 release:
: - Add USB and NAND to the default OS boot sequence
: - Fix Phison SSD detection
: - Fix 1GB DRAM detection on i.MX solo modules

===== 27-Aug-2014, U-Boot =====
: U-Boot 2014.04-cm-fx6-1.2 release:
: - Fix USB detection issue
: - Fix boot sequence for some first Utilite units

===== 07-Jul-2014, U-Boot =====
: U-Boot 2014.04-cm-fx6-1.1 release:
: - Improve SATA disks coverage
: - Enable 3Gb/s SATA operation

===== 01-Jul-2014, U-Boot =====
: Added [[CM-FX6: U-Boot: Creating a bootable SD card]] article

===== 30-Jun-2014, U-Boot =====
: Initial release of U-Boot for CM-FX6
: U-Boot 2014.04-cm-fx6-1 supports:
: - MMC/SD Card
: - SPI flash
: - Ethernet
: - NAND flash
: - SATA and on-board SSD
: - USB host and USB OTG in host mode
: - Multiple I2C buses
: - Green LED
: - Fix NAND detection issue found in older U-Boot versions

===== 21-May-2014, Android =====
: Android JB updates:
: - Jelly Bean 4.3 update
: - Support Bluetooth
: - Pre-install Google Play and Services
: - Updated '''busybox''' and '''u-boot tools'''
: - Enable root access via ADB

===== 21-May-2014, Android =====
: Android ICS updates:
: - Ice Cream Sandwich 4.0.4 update for SB-FX6 rev. 1.1
: - Support hardware HOME button
: - Support I2C bus multiplexing
: - Bugfix in power management

===== 29-Apr-2014, Linux =====
: Linux kernel for CM-FX6 updates
: - Added second LVDS port support
: - Added Intel I211 support
: - Added DVI EDID support
: - Added CAN bus
: - Added em3027 RTC
: - Added Startek KD050C LCD support
: - Added IPU1 CSI0 support for camera capture
: - Added tvp5150 encoder with analog camera support
: Debian Linux image updates
: - Added Debian Squeeze Linux image
: Documentation
: - [[CM-FX6: Linux: Getting started#Boot_from_SSD_Disk-on-Chip|CM-FX6: Linux: Getting started]] updated to cover boot from SSD Disk-on-Chip
: - Updated multiple articles to comply with the new Linux package

===== 03-Apr-2014, Android =====
: Android upgrade to Jelly Bean 4.3, based on Android for Sabre SD by Freescale.
: Full feature parity with Ice Cream Sandwich is planned for forthcoming releases.

===== 06-Oct-2013, WEC7 =====
: WEC7 BSP updates:
:- Added WiFi support
:- Added Dual Core CPU support
:- Added WM8731 Audio codec support
:- Added LCD display support
:- Added Touchscreen support

===== 06-Jul-2013, Android =====
: Android updates:
: - Added LCD display support
: - Added CAN bus support
: - Added analog audio support
: - Added resistive touch screen support

===== 04-Jul-2013, Linux =====
: Linux kernel for CM-FX6 updates
: - Added LVDS support
: - Added WiFi support
: - Added support for more SCF0403 panel variants
: - Added analog audio support in master and slave mode
: - Fixed GPIO read mode
: - Fixed Installation RAM Disk (u)mount issue
: Debian Linux image updates
: - Updated MTD utils to support large size NAND flash
: Documentation
: - [[CM-FX6: Linux: Getting started]] article updated to cover large size NAND flash installation
: - Updated multiple articles to comply with the new Linux package

===== 30-May-2013, Linux =====
: Linux kernel for CM-FX6 updates
: - Updated kernel to the latest stable Freescale BSP based on the 3.0.35 mainline Kernel
: - Added analog audio support
: - Added USB OTG support
: - Added Bluetooth support
: - Added UART1 and UART5 support
: - Enabled Intel 82575 Gigabit LAN support
: Documentation
: - Updated multiple articles to comply with the new Linux package

===== 09-Mar-2013, Linux =====
: Initial release of Linux package for CM-FX6, contains
: - Basic support for the CM-FX6 module
: - DataImage SCF0403852GGU04 LCD panel support
: - HX8520-C multi-touch touch screen support
: - UART2 and UART4
: - MMC, USB, SATA, PCIE, I2C, SPI
: - Storage: NAND, SATA SSD, SPI flash
: - Freescale Ethernet Controller (FEC)
: - Green LED
: - TSC2046 resistive touch panel controller support
: - Dual head display (HDMI and DVI/LCD) support
: - HDMI Audio support
: Documentation
: - Initial documentation for CM-FX6 support

===== 06-Mar-2013, Android =====
: Android update:
: - Hotfix: EEPROM test disabled (caused the EEPROM to clear).

===== 14-Feb-2013, WEC7 =====
* Initial release of WEC7 package for CM-FX6:
:- Based on Adeneo's I.MX6Q Sabre-Lite 1.6 BSP release.

===== 14-Feb-2013, Android =====
: Initial Android package release for CM-FX6 based on Android 4.0.4 (Ice Cream Sandwich) for Sabre SD by Freescale

}}

[[Category:CM-FX6]]

CM-FX6 Windows Embedded Compact 7

2015-02-11T13:25:32Z

Nadav:

{{summary|
This page contains links to information related to the Windows Embedded Compact 7.0 demo package for the CompuLab CM-FX6 System-on-Module / Computer-on-Module. 

CompuLab Windows CE support includes a ready to run demo image, an SDK that enables application development, and a BSP that allows you to customize the run-time image
|cm-fx6-top.jpg|thumb}}
{{Resources Windows
|
* [[CM-FX6:_WEC7:_Getting_Started|Getting started]]
* [[CM-FX6:_WEC7:_Demo_Image | Using the Demo Image]]
|
* [[WEC7:_Application_Development|Application Development]]
* [[WEC7:_Platform_Builder_Installation | Platform Builder Installation]]
* [[CM-FX6:_WEC7:_OSDesign_Configuration|OSDesign Configuration]]
* [[WEC7:_OSDesign_Development|OSDesign Creation]]
|
* [[CM-FX6:_WEC7:_Known_issues | Known Issues]]
* [[Support | Support]]
}}

{{ChangelogRss| content=
===== 10-Feb-2015 =====
New BSP version released.
:- Eboot modified in order to support the latest UBOOT
===== 06-Oct-2013 =====
New BSP version released.
Added support:
:- WiFi
:- Dual Core CPU
:- WM8731 Audio codec
:- LCD display
:- Touchscreen
===== 14-Feb-2013 =====
* General notes:
:- Based on Adeneo's I.MX6Q Sabre-Lite 1.6 BSP release.
}}

[[Category:WEC7]]
[[Category:CM-FX6]]

CM-QS600: Android: Operating instructions

2015-02-05T12:10:50Z

Nadav:

CM-T335 SW Resources

2015-01-01T07:22:45Z

Nadav:

CM-T335 is a tiny Computer-on-Module (CoM) / System-on-Module (SoM) board designed to serve as a building block in embedded applications. 
CM-T335 is built around the Texas Instruments Sitara AM3352/4 system-on-chip featuring an advanced Cortex-A8 ARM CPU coupled with a PowerVR SGX GPU. The CPU is supplemented with up-to 512MB DDR3 and 1GB of on-board NAND storage. In addition, CM-T335 features a wide range of industry standard interfaces - Gigabit Ethernet, WiFi 802.11, Bluetooth, USB, CAN bus, serial ports, I/O lines and ADC channels. 
Small size and low power consumption of the CM-T335 allow integration into portable and space-constrained designs, while its low price makes it an ideal selection for cost-sensitive applications. 
CM-T335 is provided with comprehensive documentation and full ready-to-run SW packages for Linux, Android and Windows Embedded Compact 7 operating systems. 

<div style="background: white; border: 1px solid black; padding: 1em;">
{| border="0" cellpadding="2" width="100%" align="center"
|-
! style="font-size: 125%; background-color: #eeeeee;" align="center" width="25%" | [[CM-T335_Android | Android]]
! style="font-size: 125%; background-color: #eeeeee;" align="center" width="25%" | [[CM-T335_Windows_Embedded_Compact_7 | Windows Embedded Compact 7]]
! style="font-size: 125%; background-color: #eeeeee;" align="center" width="25%" | [[CM-T335_Linux | Linux]]
! style="font-size: 125%; background-color: #eeeeee;" align="center" width="25%" | [[U-Boot_for_CM-T335 | U-Boot]]
|-

| align="center" | <linkedimage>
wikipage=CM-T335_Android
tooltip=CM-T335_Android documentation
img_src=Image:Android-mascot.jpg
img_width=200px
img_height=180px
img_alt=CM-T335_Android
</linkedimage>

| align="center" | <linkedimage>
wikipage=CM-T335_Windows_Embedded_Compact_7
tooltip=CM-T335 Windows Embedded Compact 7 documentation
img_src=Image:Windows-ce7.jpg
img_width=200px
img_height=180px
img_alt=CM-T335_Windows_Embedded_Compact_7
</linkedimage>

| align="center" | <linkedimage>
wikipage=CM-T335_Linux
tooltip=CM-T335 Linux documentation
img_src=Image:Linux-Logo.jpg
img_width=200px
img_height=180px
img_alt=CM-T335_Linux
</linkedimage>

| align="center" | <linkedimage>
wikipage=U-Boot_for_CM-T335
tooltip=CM-T335 U-Boot documentation
img_src=Image:U-boot.jpg
img_width=200px
img_height=180px
img_alt=U-Boot_for_CM-T335
</linkedimage>
|}
</div>

__NOTOC__

{{ChangelogRss| content=
===== 31-Dec-2014, WEC7 =====
: WEC7 BSP update:
: - Added NAND flashing functionality.
: - Added CEDDK API support.
: - Added support for GPIO interrupts from user-space.
: - Fixed UART stream interface access issue.

===== 14-Sep-2014, U-Boot =====
: U-Boot update to v2014.04-cm-t335-2.2:
: - DRAM configuration fine tuning

===== 30-June-2014, WEC7 =====
: WEC7 BSP update:
: - Added SPI stream interface.
: - Added Touch support.
: - Added initial CalibrationData for Startek KD050C.
: - Added U4 USB hub delay workaround.

===== 25-May-2014, WEC7 =====
: WEC7 BSP update:
: - Added hive support
: - Fixed USB stability issues.
: - NAND now mounted as "\NAND_Flash"

===== 01-May-2014, Linux =====
: Linux kernel for CM-T335 updates
: - Added LVDS support
: - Added SPI support
: - Added WLAN support
: - Added CAN support
: Updates for Android Demo Package for CM-T335
: - Added WLAN support
: - Added support for NAND flash as a main storage
: Documentation
: - Updated multiple articles to comply with the new Linux package

===== 13-Apr-2014, Linux =====
: Linux kernel for CM-T335 updates
: - Added LVDS support
: Documentation
: - Updated multiple articles to comply with the new Linux package

===== 02-Apr-2014, U-Boot =====
: U-Boot update to v2014.01-cm-t335-2:
: - Add ELM support
: - Add USB support
: - Add USB-to-Ethernet support

===== 5-March-2014, WEC7 =====
: WEC7 BSP update:
: -Fixed bug that could cause build problems.
: -Added NAND support

===== 25-Feb-2014, Linux =====
: Linux kernel for CM-T335 updates
: - Added SPI support
: - Added WLAN support
: - Added CAN support
: Documentation
: - Updated multiple articles to comply with the new Linux package

===== 30-Dec-2013, Linux =====
: Linux kernel for CM-T335 updates
: - Added analog audio support
: - Added Startek KD050C LCD panel support
: - Added PWM backlight support
: - Added 4-wire resistive touchscreen support
: - Added Bluetooth support
: - Added SGX support
: - Fixed CPSW MAC address handling
: Documentation
: - Updated multiple articles to comply with the new Linux package

===== 12-Nov-2013, U-Boot =====
: Initial release of U-Boot for CM-T335
: U-Boot 2013.10-cm-t335-1 supports:
: - MMC/SD Card
: - NAND flash
: - Multiple I2C buses
: - CPSW Ethernet switch
: - Green LED
: - PCA953x GPIO extender

===== 22-Sep-2013, WEC7 =====
: Initial release of Windows Embedded Compact 7 for the CM-T335
: -Based on Adeneo's AM335x_WEC7 BSP

===== 10-Sep-2013, Android =====
: Initial release of Android Demo package for CM-T335, contains
: - Basic support for the CM-T335 module
: - UART0
: - MMC, I2C
: - USB OTG and USB Host
: - RTC
: - TI's CPSW Ethernet Switch
: - DVI display
: Documentation
: - Initial documentation for CM-T335 support

===== 15-Aug-2013, Linux =====
: Linux kernel for CM-T335 updates
: - Added support for EM3027 RTC
: - Fixed USB issue
: Documentation
: - Updated multiple articles to comply with the new Linux package

===== 22-Jul-2013, Linux =====
: Initial release of Linux package for CM-T335, contains
: - Basic support for the CM-T335 module
: - UART0
: - MMC, I2C
: - Storage: NAND
: - TI's CPSW Ethernet Switch
: - DVI display
: Documentation
: - Initial documentation for CM-T335 support
}}

[[Category:CM-T335]]

CM-T335 Windows Embedded Compact 7

2015-01-01T07:21:50Z

Nadav:

{{summary|
This page contains links to information related to the Windows Embedded Compact 7 demo package for the CompuLab CM-T335 System-on-Module / Computer-on-Module. 

CompuLab Windows CE support includes a ready to run demo image, an SDK that enables application development, and a BSP that allows the run-time image customization.
|Cm-t335-top.jpg|thumb}}
{{Resources Windows
|
* [[CM-T335:_WEC7:_Getting_Started|Getting started]]
* [[CM-T335:_WEC7:_Demo_Image | Using the Demo Image]]
|
* [[WEC7:_Application_Development|Application Development]]
* [[WEC7:_Platform_Builder_Installation | Platform Builder Installation]]
* [[CM-T335:_WEC7:_OSDesign_Configuration|OSDesign Configuration]]
* [[WEC7:_OSDesign_Development|OSDesign Creation]]
|
* [[CM-T335:_WEC7:_Known_issues | Known Issues]]
* [[Support | Support]]
}}

__NOTOC__

{{ChangelogRss| content=

===== 31-December-2014 =====
: Added NAND flashing functionality.
: Added CEDDK API support.
: Added support for GPIO interrupts from user-space.
: Fixed UART stream interface access issue.

===== 30-June-2014 =====
: Added SPI stream interface.
: Added Touch support.
: Added initial CalibrationData for Startek KD050C.
: Added U4 USB hub delay workaround.

===== 25-May-2014 =====
: Added hive support
: Fixed USB stability issues.
: NAND now mounted as "\NAND_Flash"

===== 5-March-2014 =====
: Fixed bug that could cause build problems.
: Added NAND support
: Added LCD support for Startek KD050C

===== 22-Sep-2013 =====
: Initial release of Windows Embedded Compact 7 for the CM-T335
: Based on Adeneo's AM335x_WEC7 BSP
}}

[[Category:WEC7]]
[[Category:CM-T335]]

File:X300 Eboot.JPG

2014-12-31T07:48:53Z

Nadav:

CM-T335: WEC7: Getting Started

2014-12-31T07:47:58Z

Nadav:

The CompuLab WinCE demo image for the CompuLab CM-T335 System-on-Module / Computer-on-Module is based on standard WEC 7.0.
== Supported Features ==

== Creating a bootable SD card ==
{{Note | The TI SDCard boot utility does not work well on computers running Windows 7, use Windows XP (WinXP mode in Windows 7 works fine too.)}}
* Download the latest [http://compulab.co.il/products/computer-on-modules/cm-t335/#devres WEC 7.0 runtime image for CM-T335] and unzip the file.
* Use the TI_SDCard_boot_utility to create a disk with partition table geometry compatible with the OMAP3 boot ROM.
: Follow the steps below:
# Insert the SD card into an SD-Reader attached to the desktop computer (an SD-card is supplied with the CM-T335 evaluation kit).
# Launch the TI_SDCard_boot utility (located in the {{filename|Utils}} folder).
# Choose the drive letter of the SD reader. [[Image:Format SD card step 1.jpg|350px]] 
# Select the {{filename|MLO}} file from the LiveDisk folder. [[Image:Format SD card step 2.jpg|350px]] 
# Select the rest of the files in the LiveDisk folder. [[Image:Format SD card step 3.jpg|350px]] 
# Select the {{parameter|FAT 32}} filesystem and {{parameter|4096 bytes}} allocation unit size in the {{cmd|Format Removable Disk}} pop-up and start the SD card format process. [[Image:Format SD card step 4.jpg|200px]] 
# After the formatting is complete, the utility automatically starts to copy the files to the SD card.
# Wait for the "Copying files done" message to appear in the debug output box. [[Image:Format SD card step 5.jpg|350px]] 
# Your SD card is now ready to boot the CM-T335.

== Booting the system ==
* Install the bootable SD card on the CM-T335 micro SD slot (P23).
* Power on the device. A synthetic splash-screen (4 colored squares) will appear on LCD display within a few seconds.

== Flashing the image into NAND flash memory via SD card ==
* In order to run the image from NAND flash, XLDRNAND.BIN/EBOOTNAND.BIN/NK.bin must be written into NAND FLASH via SD card.

* Copy EBOOTND.bin/XLDRNAND.bin/NK.bin to SD card from LiveDisk_SD folder to the bootable SD card created.

* Connect the CM-T335 to your desktop serial port with a cable is supplied in the evaluation kit. If your desktop does not have a serial port, it is possible to use a standard USB to serial adapter.

* Start a terminal emulation software on the host PC using following settings:
** Baud rate: 115200
** Parity: None
** Data bits: 8
** Stop bits: 1

* To flash XLDR/Eboot/nk.bin from SD card:
1. Turn on the CM-T335 system and hit space to enter the Eboot's configuration menu:
 [[Image:X300_Eboot.JPG]] 

2. Enable flashing by select following option from Eboot menu:

[Flash Management] -> [8]Enable flashing NK.bin
3. Change the SDcard settings for image name to eboot.bin/xldrnand.bin/nk.bin from following Eboot Menu:

[SDCard Settings] -> [Enter Filename]
4. Select boot from SD card:

[Select Boot Device] -> [NK from SDCard File]
* If NK.bin is loaded, after flashing, the program will continue to boot Kernel. If XLDR/EBoot is loaded, reboot is needed.
{{Note | 2 reboots are needed in order to complete the process.}}
{{Warning|Do not reset or power off the CM-T335 during the installation process! Doing so may result in a disabled module! }}

== See also ==
*[http://wiki.omap.com/index.php/SD/MMC_format_for_OMAP3_boot SD/MMC format for OMAP3 boot]

[[Category:WEC7|Getting Started]]
[[Category:CM-T335|WEC7: Getting Started]]

CM-FX6 SW Resources

2014-12-17T09:28:23Z

Nadav:

CM-FX6 is a miniature computer-on-module (CoM) / system-on-module (SoM) board designed to serve as a building block in embedded applications. CM-FX6 is based on the Freescale i.MX6 application processor featuring a highly scalable single/dual/quad core Cortex-A9 CPU at up to 1.2GHz coupled with powerful graphics and video processing units. The processor is supplemented with up-to 4GB DDR3 and 32GB of on-board SSD. In addition, the CM-FX6 features extensive connectivity with a wide range of industry standard interfaces – GbE, PCIe, SATA, USB, RS232 and CAN bus.

CM-FX6 is provided with comprehensive documentation and full ready-to-run SW support for Linux, Android and Windows Embedded Compact 7 operating systems. 

<div style="background: white; border: 1px solid black; padding: 1em;">
{| border="0" cellpadding="2" width="100%" align="center"
|-
! style="font-size: 125%; background-color: #eeeeee;" align="center" width="25%" | [[CM-FX6_Android | Android]]
! style="font-size: 125%; background-color: #eeeeee;" align="center" width="25%" | [[CM-FX6_Windows_Embedded_Compact_7 | Windows Embedded Compact 7]]
! style="font-size: 125%; background-color: #eeeeee;" align="center" width="25%" | [[CM-FX6 Linux | Linux]]
! style="font-size: 125%; background-color: #eeeeee;" align="center" width="25%" | [[U-Boot_for_CM-FX6 | U-Boot]]
|-

| align="center" | <linkedimage>
wikipage=CM-FX6_Android
tooltip=CM-FX6_Android documentation
img_src=Image:Android-mascot.jpg
img_width=200px
img_height=180px
img_alt=CM-FX6 Android
</linkedimage>

| align="center" | <linkedimage>
wikipage=CM-FX6_Windows_Embedded_Compact_7
tooltip=CM-FX6 Windows Embedded Compact 7 documentation
img_src=Image:Windows-ce7.jpg
img_width=200px
img_height=180px
img_alt=CM-FX6 Windows Embedded Compact 7
</linkedimage>

| align="center" | <linkedimage>
wikipage=CM-FX6 Linux
tooltip=CM-FX6 Linux documentation
img_src=Image:Linux-Logo.jpg
img_width=200px
img_height=180px
img_alt=CM-FX6 Linux
</linkedimage>

| align="center" | <linkedimage>
wikipage=U-Boot_for_CM-FX6
tooltip=CM-FX6 U-Boot documentation
img_src=Image:U-boot.jpg
img_width=200px
img_height=180px
img_alt=CM-FX6 U-Boot
</linkedimage>
|}
</div>

__NOTOC__

{{ChangelogRss| content=

===== 16-Dec-2014, Android =====
: ''Jelly Bean 4.3'' release:
: - upgrade Freescale code base to the latest Jelly Bean release - IMX6_JB43_111
: - enable Phison SATA SSD module (along with SanDisk)
: - enhance SATA power management
: - apply selection of kernel patches fixing bugs and enhancing stability

===== 11-Dec-2014, Linux =====
:
: Linux kernel 3.0.35-cm-fx6-6.3 for CM-FX6 release:
: - Added SATA suspend resume
: - Added MIPI DSI support
: - Updated WiFi firmware
: - Changed default lcd display bpp to 32
: - Fixed occasional reboot issue
: Debian Linux image updates
: - Replaced both Debian Jessie/Sid and Sid with one Debian Wheezy image
: - Added FreeScale VPU libraries for Debian Wheezy
: Documentation
: - Updated multiple articles to comply with the new Linux package

===== 11-Nov-2014, Linux =====
: Documentation
: - Updated [[CM-FX6: Linux: Debian]] and [[CM-FX6: Linux: Kernel]] articles with CAN bus information

===== 06-Nov-2014, Linux =====
: Linux kernel 3.0.35-cm-fx6-6.2 for CM-FX6 release:
: - Fixed KD050C LCD timings
: - Fixed KD050C LCD touchscreen functionality
: - Fixed SATA device initialization
: - Fixed PCIE controller power/clock/reset sequence
: - Fixed overall stability
: Debian Linux image updates
: - Added Debian Sid Linux image
: Misc updates
: - Updated CompuLab EEPROM utility to version 2.0
: Documentation
: - Updated multiple articles to comply with the new Linux package

===== 02-Nov-2014, Android =====
: Android JB updates:
: - enable routing audio to S/PDIF
: - fix bug in ADS7846 touchscreen kernel driver
: - support m25px16 SPI flash ROM
: - fix rare cpu stalls in boundary temperature conditions
: - switch automatic suspend policy to ''stay awake while charging'' by default

===== 16-Sep-2014, U-Boot =====
: U-Boot 2014.04-cm-fx6-1.3 release:
: - Add USB and NAND to the default OS boot sequence
: - Fix Phison SSD detection
: - Fix 1GB DRAM detection on i.MX solo modules

===== 27-Aug-2014, U-Boot =====
: U-Boot 2014.04-cm-fx6-1.2 release:
: - Fix USB detection issue
: - Fix boot sequence for some first Utilite units

===== 07-Jul-2014, U-Boot =====
: U-Boot 2014.04-cm-fx6-1.1 release:
: - Improve SATA disks coverage
: - Enable 3Gb/s SATA operation

===== 01-Jul-2014, U-Boot =====
: Added [[CM-FX6: U-Boot: Creating a bootable SD card]] article

===== 30-Jun-2014, U-Boot =====
: Initial release of U-Boot for CM-FX6
: U-Boot 2014.04-cm-fx6-1 supports:
: - MMC/SD Card
: - SPI flash
: - Ethernet
: - NAND flash
: - SATA and on-board SSD
: - USB host and USB OTG in host mode
: - Multiple I2C buses
: - Green LED
: - Fix NAND detection issue found in older U-Boot versions

===== 21-May-2014, Android =====
: Android JB updates:
: - Jelly Bean 4.3 update
: - Support Bluetooth
: - Pre-install Google Play and Services
: - Updated '''busybox''' and '''u-boot tools'''
: - Enable root access via ADB

===== 21-May-2014, Android =====
: Android ICS updates:
: - Ice Cream Sandwich 4.0.4 update for SB-FX6 rev. 1.1
: - Support hardware HOME button
: - Support I2C bus multiplexing
: - Bugfix in power management

===== 29-Apr-2014, Linux =====
: Linux kernel for CM-FX6 updates
: - Added second LVDS port support
: - Added Intel I211 support
: - Added DVI EDID support
: - Added CAN bus
: - Added em3027 RTC
: - Added Startek KD050C LCD support
: - Added IPU1 CSI0 support for camera capture
: - Added tvp5150 encoder with analog camera support
: Debian Linux image updates
: - Added Debian Squeeze Linux image
: Documentation
: - [[CM-FX6: Linux: Getting started#Boot_from_SSD_Disk-on-Chip|CM-FX6: Linux: Getting started]] updated to cover boot from SSD Disk-on-Chip
: - Updated multiple articles to comply with the new Linux package

===== 03-Apr-2014, Android =====
: Android upgrade to Jelly Bean 4.3, based on Android for Sabre SD by Freescale.
: Full feature parity with Ice Cream Sandwich is planned for forthcoming releases.

===== 06-Oct-2013, WEC7 =====
: WEC7 BSP updates:
:- Added WiFi support
:- Added Dual Core CPU support
:- Added WM8731 Audio codec support
:- Added LCD display support
:- Added Touchscreen support

===== 06-Jul-2013, Android =====
: Android updates:
: - Added LCD display support
: - Added CAN bus support
: - Added analog audio support
: - Added resistive touch screen support

===== 04-Jul-2013, Linux =====
: Linux kernel for CM-FX6 updates
: - Added LVDS support
: - Added WiFi support
: - Added support for more SCF0403 panel variants
: - Added analog audio support in master and slave mode
: - Fixed GPIO read mode
: - Fixed Installation RAM Disk (u)mount issue
: Debian Linux image updates
: - Updated MTD utils to support large size NAND flash
: Documentation
: - [[CM-FX6: Linux: Getting started]] article updated to cover large size NAND flash installation
: - Updated multiple articles to comply with the new Linux package

===== 30-May-2013, Linux =====
: Linux kernel for CM-FX6 updates
: - Updated kernel to the latest stable Freescale BSP based on the 3.0.35 mainline Kernel
: - Added analog audio support
: - Added USB OTG support
: - Added Bluetooth support
: - Added UART1 and UART5 support
: - Enabled Intel 82575 Gigabit LAN support
: Documentation
: - Updated multiple articles to comply with the new Linux package

===== 09-Mar-2013, Linux =====
: Initial release of Linux package for CM-FX6, contains
: - Basic support for the CM-FX6 module
: - DataImage SCF0403852GGU04 LCD panel support
: - HX8520-C multi-touch touch screen support
: - UART2 and UART4
: - MMC, USB, SATA, PCIE, I2C, SPI
: - Storage: NAND, SATA SSD, SPI flash
: - Freescale Ethernet Controller (FEC)
: - Green LED
: - TSC2046 resistive touch panel controller support
: - Dual head display (HDMI and DVI/LCD) support
: - HDMI Audio support
: Documentation
: - Initial documentation for CM-FX6 support

===== 06-Mar-2013, Android =====
: Android update:
: - Hotfix: EEPROM test disabled (caused the EEPROM to clear).

===== 14-Feb-2013, WEC7 =====
* Initial release of WEC7 package for CM-FX6:
:- Based on Adeneo's I.MX6Q Sabre-Lite 1.6 BSP release.

===== 14-Feb-2013, Android =====
: Initial Android package release for CM-FX6 based on Android 4.0.4 (Ice Cream Sandwich) for Sabre SD by Freescale

}}

[[Category:CM-FX6]]

CM-FX6: Android: Getting started

2014-12-17T09:18:02Z

Nadav: /* Advanced installation options */

== Overview ==
The following outlines the procedure necessary to install Android on the CompuLab CM-FX6 System-on-Module / Computer-on-Module.

== Installation target media ==
CM-FX6 may use either SD card (P6) or SATA SSD as root file system.

== Installation onto SD card ==
=== Preconditions ===
* [[Media:CM-FX6_Properly_Connected2.jpg|Properly connected]] CM-FX6 evaluation kit with valid U-Boot.
* SD-Card with minimal capacity of 2GB, which will serve as boot medium and root file system.
* PC workstation for creating bootable SD-Card.

=== Prepare bootable SD-Card ===
* Download prebuilt [http://compulab.co.il/products/computer-on-modules/cm-fx6/#devres Android image].
* Unzip the file in order to get ''dd'' image. 
* Flash the bootable image to the SD-Card following the [https://help.ubuntu.com/community/Installation/FromImgFiles directions].
: On Linux, the instructions below may be used instead:
<pre>
# dd if=cmfx6-android.img of=/dev/sdc bs=4M
</pre>

=== Boot ===
* Insert bootable SD-Card into SD-Card slot (P6).
* Power on.
* Within 3 seconds the device should start booting into Android.
: Within 60 seconds the HDMI display should start showing ''signs of life''.

== Installation onto SSD ==
=== Preconditions ===
* [[Media:CM-FX6_Properly_Connected2.jpg|Properly connected]] CM-FX6 evaluation kit with valid U-Boot.
* SD-Card with minimal capacity of 2GB, which will serve as installer file system.
* PC workstation for creating bootable SD-Card.

=== Prepare installer SD card ===
* Download prebuilt [http://compulab.co.il/products/computer-on-modules/cm-fx6/#devres installer image].
* Uncompress the file in order to get ''dd'' image.
* Flash the bootable image to the SD-Card following the [https://help.ubuntu.com/community/Installation/FromImgFiles directions].
: On Linux, the instructions below may be used instead:
<pre>
# dd if=cm-fx6_android-ssd-installer.img of=/dev/sdc bs=4M
</pre>

=== Launch installer ===
* Insert the bootable SD card into the CM-FX6 SD socket (P6) and turn the device on.
* CM-FX6 will automatically boot into the installer LXDE desktop.
* Double click on the CM-FX6 Image Installer icon to begin installation and follow the installation wizard directions.

=== Boot ===
* After the installation is complete, shut down CM-FX6 and remove the installation SD card.
* Restart CM-FX6.
{{Note | If the installation SD card is not removed, CM-FX6 will boot into the installer once again.}}
* Within 3 seconds the device should start booting into Android.
: Within 60 seconds the HDMI display should start showing ''signs of life''.

=== Advanced installation options ===
As CM-FX6 is developer-oriented device, the installation process and installer script itself can be customized, in order to fit customer's specific requirements. 
The following section provides an insight into interactive installation process and installer implementation.

==== Installation wizard GUI ====
In the process of installation, the user is presented with a few dialogue windows. 
In the top part of each window a brief description is provided. 
The main stations in the installation process are:
* Target device selection - currently, only SATA SSD may be presented.
* Default partition size overriding - resizing the Android file system partitions, keep in mind:
** ''userdata'' - is where user applications are installed, and where user content (such as downloaded files, recorded video or audio, etc.) is stored
** resizing additional partitions can hardly be benefited
* Default video mode setting - select LCD, HDMI or DVI video output and its resolution. It is possible to override this setting later, following the ''display configuration'' [[CM-FX6: Android: Operating instructions#Display configuration | directions]].

==== Installer script structure ====
Below provided particular details about installer script structure:
* The installer is located within installer file system, under 
:<code>/var/opt/utilite-installer/Android/cm-fx6-<release ID></code>
* The interactive installer consists of 2 phases:
** '''fs-inflate-gui:''' interactive GUI, that overrides default values in a configuration file
** '''fs-inflate:''' non-interactive installer script, that follows the configuration file, partitions the destination medium, formats it and copies the OS files
* For additional details on the Android installation process on CM-FX6, it is recommended to refer either to the installer script source code, or to the [[CM-FX6: Android: Building from source code | Building from source code]] page.

== See Also ==
* [[CM-FX6: Android: Serial console connection]]
* [[Android: ADB setup]]
* [https://help.ubuntu.com/community/Installation/FromImgFiles Installing SD Card image]

[[Category:Android]]
[[Category:CM-FX6]]

CM-FX6: Android: Getting started

2014-12-17T09:16:58Z

Nadav:

== Overview ==
The following outlines the procedure necessary to install Android on the CompuLab CM-FX6 System-on-Module / Computer-on-Module.

== Installation target media ==
CM-FX6 may use either SD card (P6) or SATA SSD as root file system.

== Installation onto SD card ==
=== Preconditions ===
* [[Media:CM-FX6_Properly_Connected2.jpg|Properly connected]] CM-FX6 evaluation kit with valid U-Boot.
* SD-Card with minimal capacity of 2GB, which will serve as boot medium and root file system.
* PC workstation for creating bootable SD-Card.

=== Prepare bootable SD-Card ===
* Download prebuilt [http://compulab.co.il/products/computer-on-modules/cm-fx6/#devres Android image].
* Unzip the file in order to get ''dd'' image. 
* Flash the bootable image to the SD-Card following the [https://help.ubuntu.com/community/Installation/FromImgFiles directions].
: On Linux, the instructions below may be used instead:
<pre>
# dd if=cmfx6-android.img of=/dev/sdc bs=4M
</pre>

=== Boot ===
* Insert bootable SD-Card into SD-Card slot (P6).
* Power on.
* Within 3 seconds the device should start booting into Android.
: Within 60 seconds the HDMI display should start showing ''signs of life''.

== Installation onto SSD ==
=== Preconditions ===
* [[Media:CM-FX6_Properly_Connected2.jpg|Properly connected]] CM-FX6 evaluation kit with valid U-Boot.
* SD-Card with minimal capacity of 2GB, which will serve as installer file system.
* PC workstation for creating bootable SD-Card.

=== Prepare installer SD card ===
* Download prebuilt [http://compulab.co.il/products/computer-on-modules/cm-fx6/#devres installer image].
* Uncompress the file in order to get ''dd'' image.
* Flash the bootable image to the SD-Card following the [https://help.ubuntu.com/community/Installation/FromImgFiles directions].
: On Linux, the instructions below may be used instead:
<pre>
# dd if=cm-fx6_android-ssd-installer.img of=/dev/sdc bs=4M
</pre>

=== Launch installer ===
* Insert the bootable SD card into the CM-FX6 SD socket (P6) and turn the device on.
* CM-FX6 will automatically boot into the installer LXDE desktop.
* Double click on the CM-FX6 Image Installer icon to begin installation and follow the installation wizard directions.

=== Boot ===
* After the installation is complete, shut down CM-FX6 and remove the installation SD card.
* Restart CM-FX6.
{{Note | If the installation SD card is not removed, CM-FX6 will boot into the installer once again.}}
* Within 3 seconds the device should start booting into Android.
: Within 60 seconds the HDMI display should start showing ''signs of life''.

=== Advanced installation options ===
As CM-FX6 is developer-oriented device, the installation process and installer script itself can be customized, in order to fit customer's specific requirements. 
The following section provides an insight into interactive installetion process and installer implementation.

==== Installation wizard GUI ====
In the process of installation, the user is presented with a few dialogue windows. 
In the top part of each window a brief description is provided. 
The main stations in the installation process are:
* Target device selection - currently, only SATA SSD may be presented.
* Default partition size overriding - resizing the Android file system partitions, keep in mind:
** ''userdata'' - is where user applications are installed, and where user content (such as downloaded files, recorded video or audio, etc.) is stored
** resizing additional partitions can hardly be benefited
* Default video mode setting - select LCD, HDMI or DVI video output and its resolution. It is possible to override this setting later, following the ''display configuration'' [[CM-FX6: Android: Operating instructions#Display configuration | directions]].

==== Installer script structure ====
Below provided particular details about installer script structure:
* The installer is located within installer file system, under 
:<code>/var/opt/utilite-installer/Android/cm-fx6-<release ID></code>
* The interactive installer consists of 2 phases:
** '''fs-inflate-gui:''' interactive GUI, that overrides default values in a configuration file
** '''fs-inflate:''' non-interactive installer script, that follows the configuration file, partitions the destination medium, formats it and copies the OS files
* For additional details on the Android installation process on CM-FX6, it is recommended to refer either to the installer script source code, or to the [[CM-FX6: Android: Building from source code | Building from source code]] page.

== See Also ==
* [[CM-FX6: Android: Serial console connection]]
* [[Android: ADB setup]]
* [https://help.ubuntu.com/community/Installation/FromImgFiles Installing SD Card image]

[[Category:Android]]
[[Category:CM-FX6]]

CM-FX6 Android

2014-12-17T09:16:21Z

Nadav:

{{summary|
This page contains up to date information about Android packages and software development for the CompuLab CM-FX6 System-on-Module / Computer-on-Module.
|Cm-fx6-top.jpg|thumb}}
{{Resources Linux
|* [[CM-FX6: Android: Getting started | Installation and update]]
* [[CM-FX6: Android: Operating instructions | Operating instructions]]
* [http://compulab.co.il/products/computer-on-modules/cm-fx6/#devres Downloads]
* [[CM-FX6:_Android:_Supported_features | Supported features]]
|* [[CM-FX6: Android: Serial console connection | Serial console connection]]
* [[Android:_ADB_setup | ADB Setup]]
* [[CM-FX6:_Android:_Building_from_source_code | Building from source code]]
|* [[Support]]
* [[CM-FX6:_Android:_Known_Issues | Known Issues]]
}}

__NOTOC__
{{ChangelogRss| content=
===== 16-Dec-2014: cm-fx6-jb-14.12.1 released =====
: ''Jelly Bean 4.3''
: - upgrade Freescale code base to the latest Jelly Bean release - IMX6_JB43_111
: - enable Phison SATA SSD module (along with SanDisk)
: - enhance SATA power management
: - apply selection of kernel patches fixing bugs and enhancing stability

===== 4-Nov-2014: cm-fx6-jb-14.11.1 released =====
: ''Jelly Bean 4.3''
: - enable routing audio to S/PDIF
: - fix bug in ADS7846 touchscreen kernel driver
: - support m25px16 SPI flash ROM
: - fix rare cpu stalls in boundary temperature conditions
: - switch automatic suspend policy to ''stay awake while charging'' by default

===== 21-May-2014: cm-fx6-jb-14.05.1 released =====
: Jelly Bean 4.3 update
: Support Bluetooth
: Pre-install Google Play and Services
: Updated '''busybox''' and '''u-boot tools'''
: Enable root access via ADB

===== 21-May-2014: cm-fx6-ics-14.05.1 released =====
: Ice Cream Sandwich 4.0.4 update for SB-FX6 rev. 1.1
: Support hardware HOME button
: Support I2C bus multiplexing
: Bugfix in power management

===== 03-Apr-2014: cm-fx6-jb.14.04 released =====
: Android upgrade to Jelly Bean 4.3, based on Android for Sabre SD by Freescale.
: Full feature parity with Ice Cream Sandwich is planned for forthcoming releases.

===== 06-Jul-2013: cm-fx6-android.13.07 released =====
: Android/Linux kernel updates:
: - Added LCD display support
: - Added CAN bus support
: - Added analog audio support
: - Added resistive touch screen support

===== 06-Mar-2013: cm-fx6-android.13.02.1 released =====
: - Hotfix: EEPROM test disabled (caused the EEPROM to clear).

===== 14-Feb-2013: cm-fx6-android.13.02 released =====
: Initial Android package release for CM-FX6 based on Android 4.0.4 (Ice Cream Sandwich) for Sabre SD by Freescale

}}

[[Category:Android]]
[[Category:CM-FX6]]

File:SBC-iBT-top.jpg

2014-12-10T09:30:53Z

Nadav:

File:Windows Embedded Standard 8 logo.jpg

2014-12-10T09:30:34Z

Nadav:

Category:SBC-iBT

2014-12-10T09:11:59Z

Nadav: New page: SBC-iBT related pages

SBC-iBT related pages

CM-QS600: Android: Known Issues

2014-12-09T12:30:33Z

Nadav:

{{IssueCategory|Audio|
* Occasionally, audio cannot be played back, and no sound cards appear in ''/proc/asound/cards'' special file
:'''Workaround:'''
:Exercise power cycle (turn power off)
:'''Notice:'''
:In many cases video playback will fail if no audio is available.
}}

{{IssueCategory|3G modem|
* Occasionally, Telit 3G modem cannot detect the SIM card.
:'''Workaround:'''
:Istruct the modem to assume SIM card is present, i.e. similate SIM inserted, by adding to the [[CM-QS600:_Android:_Operating_instructions#Start-up_script | startup script]] the appropriate line in function ''ril_initialize'', prior to starting ''ril-daemon'': 
<pre>
echo -en "AT#SIMDET=1\r" > /dev/ttyACM0
</pre>

}}

[[Category:Android]]
[[Category:CM-QS600]]

CM-X270 WinCE

2014-11-05T11:34:51Z

Nadav: New page: The documentation for the Windows CE Board Support Package and Demo Image is located within the [http://compulab.co.il/wp-content/uploads/2011/09/x270-wince6-img.zip SW package].

The documentation for the Windows CE Board Support Package and Demo Image is located within the [http://compulab.co.il/wp-content/uploads/2011/09/x270-wince6-img.zip SW package].

CM-QS600 Android

2014-11-05T11:30:22Z

Nadav:

{{summary|
This page contains up to date information about the Android package and software development for the CompuLab CM-QS600 System-on-Module / Computer-on-Module.
|cm-qs600-top.jpg|thumb}}
{{Resources Linux
|* [[CM-QS600: Android: Getting started | Installation and boot]]
* [[CM-QS600: Android: Operating instructions | Operating instructions]]
* [http://compulab.co.il/products/computer-on-modules/cm-qs600/#devres Downloads]
|* [[CM-QS600: Android: Serial console connection | Serial console connection]]
* [[Android: Fastboot setup | Fastboot setup]]
* [[Android:_ADB_setup | ADB Setup]]
* [[CM-QS600: Android: Building from source code | Building from source code]]
|* [[Support]]
* [[CM-QS600: Android: Known Issues | Known Issues]]
}}

{{ChangelogRss| content=
===== 26-Oct-2014: cm-qs600-android.14.10.1 released =====
: ''Android KitKat 4.4.3 (engineering build)''
: - enable Wi-Fi networking
: - enable 3G modem
: - fixed HDMI flickering
: - apply performance improvement patches provided by Qualcomm
: - automount removable media
: - switch automatic suspend policy to ''stay awake while charging'' by default
: - preinstall Google Play

===== 10-Aug-2014: cm-qs600-android.14.08.1 released =====
: Initial Android package release for CM-QS600 based on Android 4.4.3 (KitKat) for APQ8064 reference design by Qualcomm.

}}

[[Category:Android]]
[[Category:CM-QS600]]

CM-T335: WEC7: Demo Image

2014-11-05T11:29:12Z

Nadav:

The CompuLab WinCE demo image for the CompuLab CM-T335 System-on-Module / Computer-on-Module is based on standard WEC 7.0.
== Supported Features ==
The CM-T335 demo image supports the following features:
* DVI
* USB device and host ports
* Ethernet
* Serial ports
* SD/MMC card
* GPIO access
* I2C bus
* RTC

== Demo Image Contents ==
The following standard WEC 7.0 components are included in this demo image:
* File System Explorer
* ActiveSync
* Internet Explorer 7.0 Sample Browser
* .NET Compact Framework 3.5
* Windows Music Player
* Windows Video Player
The full list can be found in [[CM-T335: WEC7 Run-Time License Assessment]]

== Get Connected with ActiveSync ==
ActiveSync enables data synchronization between a host PC and the CM-T335 evaluation platform. You must install ActiveSync on your PC before connecting it to the CM-T335.
=== On the Host PC ===
==== Host running Windows XP ====
* Download and Install [http://www.microsoft.com/windowsmobile/en-us/downloads/microsoft/activesync-download.mspx ActiveSync] from Microsoft website.
* Ensure that ActiveSync synchronization via USB is enabled in the Connection Settings dialog box
:[[Image:ActiveSync connection settings window.jpg]]

==== Host running Windows 7 ====
Download and install the latest version of [http://www.microsoft.com/windowsmobile/en-us/downloads/microsoft/device-center-download.mspx Windows Mobile Device Center (WMDC) for Windows 7] from Microsoft website.

=== On the Target (CM-T335) ===
* Connect the USB cable to the USB OTG port (connector P19 on the SB-T335).
* Reset the CM-T335 evaluation platform.

== Demo Image Components ==
The demo image is packed into the raw NK.bin file that is stored in a micro SD card which is installed on the CM-T335 (P40).

=== RAM ===
The CM-T335 supplied with the evaluation kit is equipped with 256MB of RAM. The demo image requires approximately 89MB of RAM (48MB are reserved for the display and drivers) and leaves 78MB for application use.

=== Networking ===
* CM-T335 Ethernet - Full-featured 10/100 Ethernet interface. Implemented with the Atheros AR8033/AR8031 Ethernet controller on the CM-T335 module. The interface is routed to connector P2 of the SB-T335.

==== Defining static IP address ====
It is possible to configure a static IP address by modifying the registry.

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

=== USB ===
* U1 option - Connector P19 provides a USB device port (used mainly for ActiveSync) or USB host port that operate at high/full/low speeds.
* U4 option - Connector P25-P28 provide a high speed USB host port.

=== SD card ===
* The micro SD mounted on the CM-T335 (P5) can be used as an extra storage device.
* The demo image has been tested successfully with the following types of SD cards: SanDisk Ultra III 2Gb, Kingston 2Gb, SanDisk 1Gb, and Kingston Micro SDHC 4Gb.

=== Display Subsystem ===
The CM-T335 evaluation platform can be connected to a standard DVI display. Use connector J1 on SB-T335 and HDMI-to-DVI adapter cable supplied with the evaluation kit.

[[Category:WEC7|Demo Image]]
[[Category:CM-T335 |WEC7: Demo Image]]

CM-T335 Windows Embedded Compact 7

2014-11-05T11:28:17Z

Nadav:

{{summary|
This page contains links to information related to the Windows Embedded Compact 7 demo package for the CompuLab CM-T335 System-on-Module / Computer-on-Module. 

CompuLab Windows CE support includes a ready to run demo image, an SDK that enables application development, and a BSP that allows the run-time image customization.
|Cm-t335-top.jpg|thumb}}
{{Resources Windows
|
* [[CM-T335:_WEC7:_Getting_Started|Getting started]]
* [[CM-T335:_WEC7:_Demo_Image | Using the Demo Image]]
|
* [[WEC7:_Application_Development|Application Development]]
* [[WEC7:_Platform_Builder_Installation | Platform Builder Installation]]
* [[CM-T335:_WEC7:_OSDesign_Configuration|OSDesign Configuration]]
* [[WEC7:_OSDesign_Development|OSDesign Creation]]
|
* [[CM-T335:_WEC7:_Known_issues | Known Issues]]
* [[Support | Support]]
}}

__NOTOC__

{{ChangelogRss| content=
===== 30-June-2014 =====
: Added SPI stream interface.
: Added Touch support.
: Added initial CalibrationData for Startek KD050C.
: Added U4 USB hub delay workaround.

===== 25-May-2014 =====
: Added hive support
: Fixed USB stability issues.
: NAND now mounted as "\NAND_Flash"

===== 5-March-2014 =====
: Fixed bug that could cause build problems.
: Added NAND support
: Added LCD support for Startek KD050C

===== 22-Sep-2013 =====
: Initial release of Windows Embedded Compact 7 for the CM-T335
: Based on Adeneo's AM335x_WEC7 BSP
}}

[[Category:WEC7]]
[[Category:CM-T335]]

Category:CM-iAM

2014-11-05T11:25:35Z

Nadav: New page: CM-iAM module related pages

CM-iAM module related pages

CM-iAM: WES7: Image Creation And Deployment

2014-11-05T11:24:00Z

Nadav: New page: Under construction

Under construction

WES7: Preparing the UFD to boot the WinPE

2014-11-05T11:20:30Z

Nadav: /* Overview */

== Preparing the UFD ==
* Attach a UFD to the development workstation. '''Important Notes:'''
** The UFD’s capacity must be at least 8GB.
** The UFD will be repartitioned and formatted. Backup all necessary data before proceeding to the next step.
* On the development workstation open the command prompt in the administrative mode.
* In the command prompt type:
<pre>diskpart</pre>
* In the Diskpart prompt type:
<pre>list disk</pre>
* From the list displayed, determine the disk number of the USB disk attached. In the example below, disk 3 is the UFD:
<pre>
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\System32>diskpart

Microsoft DiskPart version 6.1.7601
Copyright (C) 1999-2008 Microsoft Corporation.
On computer: WORKSTATION-PC

DISKPART> list disk

Disk ### Status Size Free Dyn Gpt
-------- ------------- ------- ------- --- ---
Disk 0 Online 465 GB 1024 KB
Disk 1 Online 465 GB 0 B
Disk 2 Online 931 GB 0 B
Disk 3 Online 7663 MB 0 B

DISKPART>
</pre>
* In the Diskpart prompt type:
<pre>select disk [disk number] (disk 3 in this case)</pre>
   '''Important Note:''' Make the selection very carefully. All data contained in the selected drive will be '''OVERWRITTEN'''!
    The output should be:
<pre>Disk [disk number] is now the selected disk. (disk 3 in this case)</pre>

* In the Diskpart prompt type:
<pre>clean</pre>
   The output should be:
<pre>DiskPart succeeded in cleaning the disk.</pre>

* In the Diskpart prompt type:
<pre>create partition primary</pre>
   The output should be:
<pre>DiskPart succeeded in creating the specified partition.</pre>

* In the Diskpart prompt type:
<pre>format fs=ntfs quick</pre>
   The output should be:
<pre>100 percent completed
DiskPart successfully formatted the volume.</pre>

* In the Diskpart prompt type:
<pre>active</pre>
   The output should be:
<pre>DiskPart marked the current partition as active.</pre>

* In the Diskpart prompt type:
<pre>assign</pre>
   The output should be:
<pre>DiskPart successfully assigned the drive letter or mount point.</pre>

* In the Diskpart prompt type:
<pre>exit</pre>
   The output should be:
<pre>Leaving DiskPart...</pre>

[[Category:Windows Embedded Standard]]

WES7: Preparing the UFD to boot the WinPE

2014-11-05T11:20:05Z

Nadav: New page: == Overview == == Preparing the UFD == * Attach a UFD to the development workstation. '''Important Notes:''' ** The UFD’s capacity must be at least 8GB. ** The UFD will be repartitio...

== Overview ==

== Preparing the UFD ==
* Attach a UFD to the development workstation. '''Important Notes:'''
** The UFD’s capacity must be at least 8GB.
** The UFD will be repartitioned and formatted. Backup all necessary data before proceeding to the next step.
* On the development workstation open the command prompt in the administrative mode.
* In the command prompt type:
<pre>diskpart</pre>
* In the Diskpart prompt type:
<pre>list disk</pre>
* From the list displayed, determine the disk number of the USB disk attached. In the example below, disk 3 is the UFD:
<pre>
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\System32>diskpart

Microsoft DiskPart version 6.1.7601
Copyright (C) 1999-2008 Microsoft Corporation.
On computer: WORKSTATION-PC

DISKPART> list disk

Disk ### Status Size Free Dyn Gpt
-------- ------------- ------- ------- --- ---
Disk 0 Online 465 GB 1024 KB
Disk 1 Online 465 GB 0 B
Disk 2 Online 931 GB 0 B
Disk 3 Online 7663 MB 0 B

DISKPART>
</pre>
* In the Diskpart prompt type:
<pre>select disk [disk number] (disk 3 in this case)</pre>
   '''Important Note:''' Make the selection very carefully. All data contained in the selected drive will be '''OVERWRITTEN'''!
    The output should be:
<pre>Disk [disk number] is now the selected disk. (disk 3 in this case)</pre>

* In the Diskpart prompt type:
<pre>clean</pre>
   The output should be:
<pre>DiskPart succeeded in cleaning the disk.</pre>

* In the Diskpart prompt type:
<pre>create partition primary</pre>
   The output should be:
<pre>DiskPart succeeded in creating the specified partition.</pre>

* In the Diskpart prompt type:
<pre>format fs=ntfs quick</pre>
   The output should be:
<pre>100 percent completed
DiskPart successfully formatted the volume.</pre>

* In the Diskpart prompt type:
<pre>active</pre>
   The output should be:
<pre>DiskPart marked the current partition as active.</pre>

* In the Diskpart prompt type:
<pre>assign</pre>
   The output should be:
<pre>DiskPart successfully assigned the drive letter or mount point.</pre>

* In the Diskpart prompt type:
<pre>exit</pre>
   The output should be:
<pre>Leaving DiskPart...</pre>

[[Category:Windows Embedded Standard]]

CM-iAM: WES7: Getting Started

2014-11-05T11:18:45Z

Nadav: New page: == Overview == The [http://msdn.microsoft.com/en-US/library/ff795586(v=WinEmbedded.0).aspx Windows Embedded Standard 7] (WES7) image for [http://www.compulab.co.il/iam/html/iam-cm-datashee...

== Overview ==
The [http://msdn.microsoft.com/en-US/library/ff795586(v=WinEmbedded.0).aspx Windows Embedded Standard 7] (WES7) image for [http://www.compulab.co.il/iam/html/iam-cm-datasheet.htm CM-iAM] is provided in the two variations: image for internal NAND Flash storage device and image for exrenal SATA storage device.
* The image for internal NAND Flash storage device provides the basic features of the Windows 7 SP1 Pro and it is based on the [[WES7: Templates | Thin Client template]] with following additions:
** Enhanced Write Filter Boot Environmet
** Custom Logon Desktop Background Image
** Dialog Box Filter
** Enhanced Write Filter with HORM
** File Based Write Filter
** Hide Boot Screens
** Message Box Default Reply
** RAM Disk Controller
** Registry Filter
** Telnet Server
: The [http://www.compulab.co.il/iam/download/iam-wes7-nand-img.zip WES7 NAND Flash run-time image package for CM-iAM] includes a ready-to-run image which can be installed on the internal NAND Flash storage device.
* The image for external SATA storage device provides the most of the features of the Windows 7 SP1 Pro and it is based on the [[WES7: Templates | Application Compatibility template]] with following additions:
** Custom Logon Desktop Background Image
** Dialog Box Filter
** Enhanced Write Filter with HORM
** File Based Write Filter
** Hide Boot Screens
** Message Box Default Reply
** RAM Disk Controller
** Registry Filter
** Telnet Server
: The [http://www.compulab.co.il/iam/download/iam-wes7-sata-img.zip WES7 SATA run-time image package for CM-iAM] includes a ready-to-run image which can be installed on the external SATA storage device.
The image is installed by using a bootable USB Flash Drive (UFD) combined with the [http://technet.microsoft.com/en-us/library/dd744322(WS.10).aspx WinPE] and [http://technet.microsoft.com/en-us/library/dd744377(WS.10).aspx ImageX] tools.
 
== General Notes ==
The provided WES7 image is built as an evaluation copy and therefore it is time limited (expires after 30 days). In order to create a permanent WES7 image, a license should be purchased from Microsoft and the image should be re-built.
 
== Preparing the USB Flash Drive with WinPE and WES7 Image==
# [[WES7: Preparing the UFD to boot the WinPE | Format the UFD with NTFS and make it active by using Diskpart]].
# Unzip the downloaded WES7 run-time image package.
# Copy the content of the ''WinPE'' and ''WES7 Image'' folders to the UFD.
# Disconnect the UFD from your host computer.
 
== WES7 Image Deployment ==
=== NAND Flash Image Deployment ===
# Connect the UFD with WinPE and WES7 image to the iAM board. '''Important Note:''' Ensure that no other USB or SATA Storage Device is connected.
# Boot the CM-iAM and enter the BIOS Setup.
# Set the appropriate Date and Time.
# Go to the “Boot” section and set your UFD as the first bootable device.
# Save the configuration changes and exit BIOS.
# Wait until the WinPE prompt appears.
# Browse to the USB Flash Drive and run ''iAM_WES7_NAND_deploy.bat'' file for deploying the image.
# The automatic script formats the NAND Flash storage device and deploys the WES7 image.
# Ensure that there is no error message during the installation of the image.
 
The script output should appear as follows:
 
<pre>
X:\windows\system32>wpeinit

X:\windows\system32>d:

D:\>iAM_WES7_NAND_deploy.bat

D:\>diskpart /s prepare_iAM_WES7.txt

Microsoft DiskPart version 6.1.7100
Copyright (C) 1999-2008 Microsoft Corporation.
On computer: MININT-VK6BS5V

Disk 1 is now the selected disk.
DiskPart succeeded in cleaning the disk.
DiskPart succeeded in creating the specified partition.

100 percent completed

DiskPart successfully formatted the volume.
DiskPart marked the current partition as active.
DiskPart successfully assigned the drive letter or mount point.

DiskPart succeeded in creating the specified partition.

100 percent completed

DiskPart successfully formatted the volume.
DiskPart successfully assigned the drive letter or mount point.

Leaving DiskPart...

D:\>imagex.exe /apply iAM_WES7_NAND.wim 1 g:\ /verify

ImageX Tool for Windows
Copyright (C) Microsoft Corp. All rights reserved.
Version: 6.1.7100.0

[ 100% ] Applying (with verification) progress
Successfully applied image.
Total elapsed time: 5 min 45 sec

D:\>pause
Press any key to continue . . .
</pre>
 
=== SATA Image Deployment ===
# Connect the SATA Storage Device to the SATA connector on the CM-iAM.
# Connect the UFD with WinPE and WES7 image to the iAM board. '''Important Note:''' Ensure that no other USB or SATA Storage Device is connected.
# Boot the CM-iAM and enter the BIOS Setup.
# Set the appropriate Date and Time.
# Go to the “Boot” section and set your UFD as the first bootable device.
# Save the configuration changes and exit BIOS.
# Wait until the WinPE prompt appears.
# Browse to the USB Flash Drive and run ''iAM_WES7_NAND_deploy.bat'' file for deploying the image.
# The automatic script formats the SATA Storage Device and deploys the WES7 image.
# Ensure that there is no error message during the installation of the image.
 
The script output should appear as follows:
 
<pre>
X:\windows\system32>wpeinit

X:\windows\system32>d:

D:\>deploy.bat

D:\>diskpart /s prepare_iAM_WES7.txt

Microsoft DiskPart version 6.1.7100
Copyright (C) 1999-2008 Microsoft Corporation.
On computer: MININT-VK6BS5V

Disk 1 is now the selected disk.
DiskPart succeeded in cleaning the disk.
DiskPart succeeded in creating the specified partition.

100 percent completed

DiskPart successfully formatted the volume.
DiskPart marked the current partition as active.
DiskPart successfully assigned the drive letter or mount point.

DiskPart succeeded in creating the specified partition.

100 percent completed

DiskPart successfully formatted the volume.
DiskPart successfully assigned the drive letter or mount point.

Leaving DiskPart...

D:\>imagex.exe /apply iAM_WES7.wim 1 g:\ /verify

ImageX Tool for Windows
Copyright (C) Microsoft Corp. All rights reserved.
Version: 6.1.7100.0

[ 100% ] Applying (with verification) progress
Successfully applied image.
Total elapsed time: 9 min 31 sec

D:\>pause
Press any key to continue . . .
</pre>
 
== Boot the Image ==
# After the system shuts down, disconnect the UFD.
# Turn on the CM-iAM.
# After the system boots, the [http://msdn.microsoft.com/en-us/library/ff793540(v=WinEmbedded.1001).aspx Sysprep] process starts automatically and resets the clock for the Windows Product Activation.
# The system is automatically rebooted once Sysprep is complete.
# After the reboot the system will boot into Windows Welcome mode.
 
== External Links ==
* [http://www.microsoft.com/download/en/details.aspx?id=11887 Download WES7 SP1 Evaluation Edition]
* [http://msdn.microsoft.com/en-US/library/ff795586(v=WinEmbedded.0).aspx WES7 MSDN Resources]
* [http://www.seanliming.com/WES7.html WES7 Sean Liming Resources]
 
[[Category:Windows Embedded Standard]]
[[Category:CM-iAM]]

CM-iAM: WES7

2014-11-05T11:18:28Z

Nadav: New page: {{summary| This page contains links to information about the Windows Embedded Standard 7 demo image for CM-iAM modules. * [[CM-iAM:_WES7:_Getting_Started | Getting Started with Windows E...

{{summary|
This page contains links to information about the Windows Embedded Standard 7 demo image for CM-iAM modules.

* [[CM-iAM:_WES7:_Getting_Started | Getting Started with Windows Embedded Standard 7 on CM-iAM]]
* [[CM-iAM:_WES7:_Image_Creation_And_Deployment | Windows Embedded Standard 7 Image Creation and Deployment on CM-iAM]]
|cm-iam-top.jpg|thumb}}

{{ChangelogRss| content=
===== 07-Aug-2011 =====
* Initial release of Windows Embedded Standard 7 for CM-iAM module.
}}

[[Category:Windows Embedded Standard]]
[[Category:CM-iAM]]

CM-QS600: Android: Getting started

2014-11-05T11:15:40Z

Nadav:

== Overview ==
The following outlines the procedure necessary to install Android on the CompuLab CM-QS600 System-on-Module / Computer-on-Module.

== Installation target media ==
CM-QS600 uses on-board eMMC as root file system medium.
{{Note|Additional media might be enabled in the coming releases.}}

== Installation onto eMMC ==
=== Preconditions ===
* CM-QS600 evaluation kit.
* PC workstation with installed [[Android: Fastboot setup | fastboot]] client software.
* Connect HDMI display to the CM-QS600 ''(optional)''.
* Connect [[CM-QS600: Android: Serial console connection | serial console]] to the CM-QS600 ''(optional)''.
* Connect USB cable between the CM-QS600 USB OTG (P7) jack and PC workstation, in order to enable [[Android: Fastboot setup | fastboot]] protocol.
* Connect RTC battery to P15.

=== Flashing Android image ===
* Download prebuilt [http://compulab.co.il/products/computer-on-modules/cm-qs600/#devres Android image].

* Decompress the file, in order to get Android partition images.


* Enter ''fastboot mode'' following either of the options:
# There is no valid ''boot'' partition (which is how CM-QS600 comes out of the box).
#: In this case, the device will enter ''fastboot mode'' upon power on.
# There is a valid ''boot'' partition (i.e. CM-QS600 was pre-installed with OS).
#: In this case, the device will boot from it.
#: Reboot to bootloader by issuing on either workstation <pre>$ adb reboot bootloader</pre>
#: or Android device itself <pre># reboot bootloader</pre>

* Flash each partition image file to the eMMC with the aid of ''fastboot'' utility:
<pre>
$ fastboot flash boot boot.img
$ fastboot flash system system.img
$ fastboot flash cache cache.img
$ fastboot flash userdata userdata.img
</pre>



* Proceed to boot, issuing
<pre>
$ fastboot reboot
</pre>

=== Boot ===
* Power on
* Within 3 seconds the device should start booting into Android.
: Within 60 seconds the HDMI display should start showing ''signs of life''.

== See Also ==
* [[CM-QS600: Android: Serial console connection]]
* [[Android: Fastboot setup]]
* [[Android: ADB setup]]

[[Category:Android]]
[[Category:CM-QS600]]

CM-T3530: WEC7: Known issues

2014-11-05T10:04:00Z

Nadav: New page: The following lists the known issues for the latest CM-T3530 software package: {{IssueCategory|WiFi| * Wifi and Bluetooth are not supported in the initial release. Support for these featur...

The following lists the known issues for the latest CM-T3530 software package:
{{IssueCategory|WiFi|
* Wifi and Bluetooth are not supported in the initial release. Support for these features will be added in future releases.
}}
{{IssueCategory|Errors on start-up|
* ehcihcd.dll will cause two exceptions during start up.
}}
{{IssueCategory|Activesync|
* Cannot browse while activesync is connected.
}}
[[Category:WEC7|Know Issues]]
[[Category:CM-T3530|WEC7: Known issues]]

CM-T3530: WEC7: Demo Image

2014-11-05T10:03:25Z

Nadav: New page: The CompuLab WinCE demo image for CM-T3530 is based on standard WEC 7.0. == Supported Features == The CM-T3530 demo image supports the following features: * NAND flash * TFT LCD (pre-conf...

The CompuLab WinCE demo image for CM-T3530 is based on standard WEC 7.0.

== Supported Features ==
The CM-T3530 demo image supports the following features:
* NAND flash
* TFT LCD (pre-configured for Toppoly TD035STEE1 TFT 480x640)
* DVI
* LVDS
* Audio
* USB device and host ports
* Ethernet
* Serial ports
* SD/MMC card
* GPIO access
* I2C bus
* Touch screen
* Keypad (6x6)
* RTC
* SPI bus

== Demo Image Contents ==
The following standard WEC 7.0 components are included in this demo image:
* File System Explorer
* ActiveSync
* Internet Explorer 7.0 Sample Browser
* .NET Compact Framework 3.5
* Windows Music Player
* Windows Video Player
* Telnet Server
The full list can be found in [[CM-T3530: WEC7 Run-Time License Assessment]]

== Get Connected with ActiveSync ==
ActiveSync enables data synchronization between a host PC and the CM-T3530 evaluation platform. You must install ActiveSync on your PC before connecting it to the CM-T3530.
=== On the Host PC ===
==== Host running Windows XP ====
* Download and Install [http://www.microsoft.com/windowsmobile/en-us/downloads/microsoft/activesync-download.mspx ActiveSync] from Microsoft website.
* ActiveSync may experience connection problems caused by Windows desktop firewall applications. Read the [http://www.microsoft.com/windowsmobile/en-us/help/synchronize/activesync-usb.mspx ActiveSync Troubleshooting Guide] for host PC configuration instructions.
* Ensure that ActiveSync synchronization via USB is enabled in the Connection Settings dialog box
:[[Image:ActiveSync connection settings window.jpg]]

==== Host running Windows 7 ====
Download and install the latest version of [http://www.microsoft.com/windowsmobile/en-us/downloads/microsoft/device-center-download.mspx Windows Mobile Device Center (WMDC) for Windows 7] from Microsoft website.

=== On the Target (CM-T3530) ===
* Connect the USB cable to the USB OTG port (connector P8 on SB-T35).
* Reset the CM-T3530 evaluation platform.

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

=== RAM ===
The CM-T3530 supplied with the evaluation kit is equipped with 256MB of RAM. The demo image requires approximately 127MB of RAM (56MB are reserved for the display and the DSP) and leaves 129MB for application use.

=== NAND Flash ===
The CM-T3530 supplied with the evaluation kit is equipped with 512MB NAND flash.
XLDR and Eboot bootloaders are stored in the NAND flash.
Demo image installation process partitions the NAND flash and reserves unpartitioned space for the runtime image.

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

Approximately 440 MB of free space is available for data storage on the NAND. Data can be stored in the root directory ("\My device").

=== Persistent Registry ===
The demo image is built with a “Hive-Based Registry” option.
This means that the system registry is stored in the NAND flash data partition, making registry entries persistent when the device is powered off.
The demo image is configured according to a “Lazy Flush” registry policy. The registry settings are stored in RAM and are flushed into the NAND flash every 30 seconds. After changing registry settings, allow 30 seconds before turning off the power or performing a hardware reset. This will ensure that the changes are saved into the NAND flash.
=== Networking ===
The following network interfaces are supported in the demo image:
* CM-T3530 Ethernet - Full-featured 10/100 Ethernet interface. Implemented with the SMSC LAN9220 Ethernet controller on the CM-T3530 module. The interface is routed to connector P18 of the SB-T35.
* SB-T35 Ethernet - Full-featured 10/100 Ethernet interface. Implemented with the SMSC LAN9220 Ethernet controller on the SB-T35 base-board. The interface is routed to connector P16 of the SB-T35.

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

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

=== USB ===
* Connector P17 provides 2 USB host ports that operate at high/full/low speeds.
* Connector P8 provides a USB device port (used mainly for ActiveSync).
* Connector P22 provides a high speed USB host port.

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

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

=== Keypad ===
The CM-T3530 image supports a generic 36 (6x6) button keypad.

The demo image is configured for the 3x3 keypad supplied with the CM-T3530 evaluation kit.
The default key mappings are listed below:
* "Left", "Right", "Up", "Down" buttons control cursor movement (SW3, SW7, SW4, SW6 respectively)
* "SW5" button acts as "Enter" key
* "SW1" button acts as "Escape"
* "SW2" button acts as "Tab"
* "SW8" button acts as "Home"
* "SW9" button acts as "End"
==== Customizing the keypad driver ====
Use the following registry settings to modify virtual key assignments:
<pre>
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Keypad]
"Row0"=multi_sz:"18","9","25","0","0","0"
"Row1"=multi_sz:"26","0d","28","0","0","0"
"Row2"=multi_sz:"27","24","23","0","0","0"
"Row3"=multi_sz:"0","0","0","0","0","0"
"Row4"=multi_sz:"0","0","0","0","0","0"
"Row5"=multi_sz:"0","0","0","0","0","0"
</pre>
The keypad above is defined with 3 columns and 3 rows. The values represent each row virtual keys.
For example:
<pre>
"Row1"=multi_sz:"26","0d","28","0","0","0"
</pre>
The line above informs the keypad driver that:
* The button corresponding to Row1 and Col0 is virtual key 0x26 (VK_UP).
* The button corresponding to Row1 and Col1 is virtual key 0xd (VK_RETURN).
* The button corresponding to Row1 and Col2 is virtual key 0x28 (VK_DOWN).
* The other buttons in Row1 are not connected.

A full list of virtual key codes is available at [http://msdn.microsoft.com/en-us/library/ms959632.aspx MSDN Virtual Key Codes]

=== Display Subsystem ===
The demo image is configured for the Toppoly TD035STEE1 TFT LCD shipped with the evaluation kit

The default resolution is 480x640 with 16-bit color depth and portrait display.
==== Changing from LCD to DVI ====
The CM-T3530 evaluation platform can be connected to a standard DVI display. Use connector J2 on SB-T35 and HDMI-to-DVI adapter cable supplied with the evaluation kit.

The {{RegKey|HKEY_LOCAL_MACHINE\System\GDI\Drivers\Config}} registry key defines display mode configuration.
The example below sets the display subsystem to DVI mode with 1024x748 screen resolution.
<pre>
[HKEY_LOCAL_MACHINE\System\GDI\Drivers\Config]
"PredefinedDisplay"="DVI_1024W_768H"
</pre>

The demo image supports the following predefined display modes:
{| border="1"
| '''"PredefinedDisplay" Value''' || '''Display Mode'''
|-
| DVI_640W_480H|| DVI mode 640x480
|-
| DVI_640W_480H_72HZ|| DVI mode 640x480 @ 72 Hz
|-
| DVI_800W_480H|| DVI mode 800x480
|-
| DVI_800W_600H|| DVI mode 800x600
|-
| DVI_800W_600H_56HZ|| DVI mode 800x600 @ 56 Hz
|-
| DVI_1024W_768H|| DVI mode 1024x768
|-
| DVI_1280W_720H|| DVI mode 1280x720
|-
| TOPPOLY_480W_640H|| LCD mode (Toppoly LCD)
|-
|}

==== Using custom display settings ====
The following registry keys allow setting custom display timings:
<pre>
[HKEY_LOCAL_MACHINE\System\GDI\Drivers\Config]
"IsDVIEnabled"=dword:0 ;0 for LCD, 1 for DVI
"IsLVDSEnabled"=dword:0 ;1 for enabled LVDS interface
"HorizontalSyncPolarity"=dword:0 ;1 for active high , 0 for active low
"VerticalSyncPolarity"=dword:0 ;1 for active high , 0 for active low
"Height"=dword:280 ;Vertical resolution
"Width"=dword:1e0 ;Horizontal resolution
"HorizontalSyncPulseWidth"=dword:20
"VerticalSyncPulseWidth"=dword:1
"HorizontalBackPorch"=dword:17
"HorizontalFrontPorch"=dword:0000008
"VerticalFrontPorch"=dword:0000004
"VerticalBackPorch"=dword:0000003
"PixelClockFrequency"=dword:17D7840 ;In Hz
"PixelClockPolarity"=dword:00000001 ;1 for rising edge, 0 for falling edge
</pre>
{{Note|When using custom display timings, make sure the "PredefinedDisplay" key is not defined.}}
For additional details about CompuLab LCD adaptation services, please refer to [http://www.compulab.co.il/t3530/html/t3530-lcd.htm LCD Panel support].

The [[CM-T3530: WinCE: LCDAdapt Manual | LCDAdapt]] utility included in the
[http://www.compulab.co.il/t3530/download/t3530-wince6-img.zip Windows CE 6 run-time image package] allows easy configuration of LCD timing parameters.

==== Using custom splashscreen ====
Please refer to [[CM-T3530: WinCE: Splashscreen Customization|Splashscreen Customization Guide]] for the splashscreen customization options.

== Using the '''''Do.exe''''' utility for quick system configurations ==
The Do.exe utility is provided with the demo image (source code is available in the BSP). It can be used for the following purposes:
* Access to the physical address space.
* Access to the TPS65930 PMIC registers.
* Access to the I2C devices memory space.
* Get current CPU load.
* Calibrate touch screen.
* Manipulate GPIO pins.
* Reboot the device
=== Physical address space access ===
Use the following commands to access OMAP35x registers (physical address space). For complete OMAP35x register documentation, please refer to the [http://focus.ti.com/lit/ug/spruf98d/spruf98d.pdf OMAP35x Technical Reference Manual].

* {{cmd|do in8 address [size]}} - Read 8-bit registers.
* {{cmd|do in16 address [size]}} - Read 16-bit registers.
* {{cmd|do in32 address [size]}} - Read 32-bit registers.
* {{cmd|do out8 address value}} - Write 8-bit register.
* {{cmd|do out16 address value}} - Write 16-bit register.
* {{cmd|do out32 address value}} - Write 32-bit register.

=== PMIC register access ===
Use the following commands to read/write the TPS65930 register. For complete TPS65930 register documentation, please refer to the [http://focus.ti.com/lit/ug/swcu052c/swcu052c.pdf TPS65930 Technical Reference Manual].
*{{Cmd|do intwl address subaddress [size]}} - Read TPS65930 registers.
*{{Cmd|do outtwl address subaddress value}} - Write TPS65930 registers.

=== I2C device register access ===
Use the following commands to access an I2C device connected to the system.

* {{Cmd|do ini2c [1,2,3] device_address reg_address [size]}} - Read I2C device registers.
* {{Cmd|do outi2c [1,2,3] device_address reg_address reg_value}} - Write I2C device registers.

For example:
The following command will read register 0x12 from a device with slave address 0x20 attached to I2C-2 bus:
<pre>
do ini2c 2 20 12
</pre>
=== Measure CPU load ===
The following command measures the current CPU load:

* {{Cmd|do cpuidle}} - Display amount of time spent in OEMIdle.

The following shows {{Cmd|do cpuidle}} command output with the CPU load at ~8%:
<pre>
idle count=0x00073164, tick count=0x0007D22B
The difference from last check is...
idle delta=0x00073164, tick delta=0x0007D22B
cpu load is 8.030165
</pre>

=== Calibrate Touch-Screen ===
The following command invokes the TouchScreen calibration utility:

* {{Cmd|do tscal}} - Calibrate touchscreen.

=== Manipulate GPIO pins ===
The following commands set a GPIO pin direction to output:
* {{Cmd|do gpio X set_dir out low}} - Set GPIO X to output with logical value 0 (low).
* {{Cmd|do gpio X set_dir out high}} - Set GPIO X as output with logical value 1 (high).
Use the following command to set a GPIO pin direction to input:
* {{Cmd|do gpio X set_dir in}} - Set GPIO X as input.
The following command is used to query a GPIO pin current state:
* {{Cmd|do gpio X info}} - Get GPIO X status.

=== Reboot the device ===
The following command invokes a software reboot:

* {{Cmd|do reboot}} - Software reset of the device.

== Sample Applications ==
The WinCE demo image package includes demo applications that demonstrate how to use common interfaces such as SPI, I2C and GPIO.
=== GPIO Sample ===
This application demonstrates how to use the GPIO driver in order to control the state of GPIO pins.

For further details, please refer to [[CM-T3530: WinCE: GPIOs Programming | GPIOs Programming]].

=== SPI Sample ===
The LCDActivate project included in the WinCE demo image package, demonstrates how to use the SPI driver. This project creates the DLL that is used for Toppoly LCD activation.

For further details, please refer to [[SPI Driver API for CM-T3530]].

=== I2C Sample ===
The I2C Sample application demonstrates how to use the I2C driver. It writes and reads data to/from an EEPROM on the SB-T35.

== See Also ==
*[[CM-T3530:_WinCE:_Splashscreen_Customization]]
[[Category:WEC7|Demo Image]]
[[Category:CM-T3530|WEC7: Demo Image]]

CM-T3530: WEC7: Getting Started

2014-11-05T10:02:35Z

Nadav: New page: == Connecting the module == The following picture shows the recommended evaluation kit setup :- Image:CM T35 Properly Connected Image.jpg == Creating a bootable SD card == {{Note | Th...

== Connecting the module ==
The following picture shows the recommended evaluation kit setup
:- [[Image:CM T35 Properly Connected Image.jpg]]

== Creating a bootable SD card ==
{{Note | The TI SDCard boot utility does not work well on computers running Windows 7, use Windows XP (WinXP mode in Windows 7 works fine too.)}}
* Download the latest [http://compulab.co.il/t3530/download/t3530-wince7-img.zip WEC 7.0 runtime image for CM-T3530] and unzip the file.
* Use the TI_SDCard_boot_utility to create a disk with partition table geometry compatible with the OMAP3 boot ROM.
: Follow the steps below:
# Insert the SD card into an SD-Reader attached to the desktop computer (an SD-card is supplied with the CM-T3530 evaluation kit).
# Launch the TI_SDCard_boot utility (located in the {{filename|Utils}} folder).
# Choose the drive letter of the SD reader. [[Image:Format SD card step 1.jpg|350px]] 
# Select the {{filename|MLO}} file from the LiveDisk folder. [[Image:Format SD card step 2.jpg|350px]] 
# Select the rest of the files in the LiveDisk folder. [[Image:Format SD card step 3.jpg|350px]] 
# Select the {{parameter|FAT 32}} filesystem and {{parameter|4096 bytes}} allocation unit size in the {{cmd|Format Removable Disk}} pop-up and start the SD card format process. [[Image:Format SD card step 4.jpg|200px]] 
# After the formatting is complete, the utility automatically starts to copy the files to the SD card.
# Wait for the "Copying files done" message to appear in the debug output box. [[Image:Format SD card step 5.jpg|350px]] 
# Your SD card is now ready to boot the CM-T3530.

== Installing the demo runtime image ==
* Insert the bootable SD card into the SD socket (connector P13 on SB-T35).
* Configure the CM-T3530 for SD-Boot mode. There are two ways to do it:
** Preferred way: Hold the “SD BOOT” button while booting the device. You should hold the button until the synthetic splash-screen (4 colored squares) appears.
** Installing jumper E6.
* Power on the device. The synthetic splash-screen (4 colored squares) will appear on LCD display within a few seconds.
* An Updater image (dedicated WinCE image) is loaded from the SD-Card. Updater image boot time is approximately 50 seconds.
* The Updater utility will start automatically. The utility will install the runtime image onto the CM-T3530 NAND flash.
:[[Image:CM_T35_Updater_Running.jpg|400px]]
* The following message box informs you that the process is complete.
:[[Image:CM_T35_Updater_Complete.jpg|400px]]
* Make sure jumper E6 is removed. Otherwise, the installation process will be repeated next time you boot the device.
* Use the reset button to reboot the device.
* CompuLab WinCE demo image will be loaded from the NAND flash.

{{Note |Please refer to [[CM-T3530: WinCE: Updater| CM-T3530 Updater Guide]] for the technical installation process details}}

== See also ==
*[http://wiki.omap.com/index.php/SD/MMC_format_for_OMAP3_boot SD/MMC format for OMAP3 boot]
*[[CM-T3530: WinCE: Updater]]

[[Category:WEC7|Getting Started]]
[[Category:CM-T3530|WEC7: Getting Started]]

CM-T3530 Windows Embedded Compact 7

2014-11-05T10:02:17Z

Nadav: New page: {{summary| This page contains links to information related to the Windows Embedded Compact 7 demo package for the CM-T3530 CompuLab Windows CE support includes a ready to run demo i...

{{summary|
This page contains links to information related to the Windows Embedded Compact 7 demo package for the CM-T3530 

CompuLab Windows CE support includes a ready to run demo image, an SDK that enables application development, and a BSP that allows you to customize the run-time image
|T35 CM top.JPG|thumb}}
{{Resources Windows
|
* [[CM-T3530:_WEC7:_Getting_Started|Getting started]]
* [[CM-T3530:_WEC7:_Demo_Image | Using the Demo Image]]
|
* [[WEC7:_Application_Development|Application Development]]
* [[WEC7:_Platform_Builder_Installation | Platform Builder Installation]]
* [[CM-T3530:_WEC7:_OSDesign_Configuration|OSDesign Configuration]]
* [[WEC7:_OSDesign_Development|OSDesign Creation]]
|
* [[CM-T3530:_WEC7:_Known_issues | Known Issues]]
* [[Support | Support]]
}}

{{ChangelogRss| content=
===== 15-March-2011 =====
: Initial release of Windows Embedded Compact 7 for the CM-T3530
: Based on BSquare EVM3530 6.15.0 BSP release
}}

[[Category:WEC7]]
[[Category:CM-T3530]]

CM-FX6: Android: Supported features

2014-11-04T14:00:40Z

Nadav:

{| border="1" cellspacing="0" cellpadding="3" width="75%" style="margin: 1em auto 1em auto;"
|- style="background: #D3D3D3"
| align="center" | '''Feature'''
| align="center" | '''Ice Cream Sandwich'''
| align="center" | '''Jelly Bean'''
| align="center" | '''Notes'''
|- style="background: #EEEEEE"
| align="center" colspan="4" | '''System hardware'''
|-
| align="center" colspan="4" | ''Storage''
|-
| SD card
| +
| +
|
|-
| micro-SD card
| +
| +
| mutually exclusive with Wi-Fi / Bluetooth
|-
| NAND flash
| +
| +
|
|-
| I2C EEPROM
| +
| +
|
|-
| internal SATA storage
| +
| +
|
|-
| align="center" colspan="4" | ''Networking''
|-
| Ethernet 1
| +
| +
|
|-
| Ethernet 2
| TBD
| TBD
|
|-
| Wi-Fi
| +
| +
| '''ICS:''' WEXT interface, '''JB:''' NL80211 interface
|-
| Bluetooth
| +
| +
|
|-
| align="center" colspan="4" | ''I/O interfaces''
|-
| USB host
| +
| +
|
|-
| USB OTG
| +
| +
|
|-
| RS-232 (P60)
| +
| +
|
|-
| RS-232 (P32-A)
| +
| +
|
|-
| align="center" colspan="4" | ''Display''
|-
| HDMI
| +
| +
| 1080p
|-
| DVI
| +
| +
| 1080p
|-
| align="center" colspan="4" | ''Audio''
|-
| HDMI audio
| +
| +
| bound to HDMI video
|-
| analog audio
| +
| +
| bound to DVI video
|-
| S/PDIF audio
| +
| +
| '''JB:''' routed to ''Wired Headphones''
|-
| align="center" colspan="4" | ''Miscellaneous''
|-
| power button
| +
| +
| short press: suspend / resume 
long press: power off menu pops up 
very long press: unconditional power off
|-
| HOME button
| +
| +
|
|-
| RTC
| +
| +
|
|-
| SoC power management
| partial
| partial
|
|-
| USB touchscreen
| +
| +
| particular models might require additional work (e.g. interchanging x/y axes)
|-
| UVC camera
| +
| partial
| '''ICS:''' 480p
|-
|- style="background: #EEEEEE"
| align="center" colspan="4" | '''System software'''
|-
| align="center" colspan="4" | ''Miscellaneous''
|-
| root access
| +
| +
| type in Android command line '''su''', or on desktop computer '''adb root'''
|-
|-
| Play Store (a.k.a. Android Market)
| +
| +
|
|-
| video playback
| +
| +
| particular players might use or not use HW acceleration for video decoding
|-
| YouTube and the like
| +
| +
|
|-
| Skype
| +
| +
|
|-
|}

CM-FX6: Android: Operating instructions

2014-11-04T13:59:21Z

Nadav:

= Overview =
Most CM-FX6 [http://www.compulab.co.il/products/operating-systems-and-drivers-for-cm-fx6-and-sbc-fx6 supported features] are operated using normal Android controls. 
This page contains information about features and services, which are less straight-forward to operate, or are less widely known.

= Operating instructions =
=== Display configuration ===
By default CM-FX6 is configured to use HDMI display with 1080p resolution. 
This setting can be overridden by providing alternate boot arguments to the Android/Linux kernel.
* Connect to the serial console as explained in the [[CM-FX6: Android: Serial console connection | Development]] section.
* Press ENTER to stop the countdown.
<pre>
setenv videomode video=mxcfb0:dev=hdmi,if=RGB24,1920x1080M@60 video=mxcfb1:off video=mxcfb2:off video=mxcfb3:off # default video mode (HDMI)
setenv videomode video=mxcfb0:dev=dvi,if=RGB24,1920x1080M@60 video=mxcfb1:off video=mxcfb2:off video=mxcfb3:off # DVI display with 1080p resolution
setenv videomode video=mxcfb0:dev=dvi,if=RGB24,1280x1024M@60 video=mxcfb1:off video=mxcfb2:off video=mxcfb3:off # DVI display with 1280x1024 resolution
setenv videomode video=mxcfb0:dev=lcd,if=RGB666,SCF04-WVGA video=mxcfb1:off video=mxcfb2:off video=mxcfb3:off # DataImage 480x800 LCD
setenv videomode video=mxcfb0:dev=lcd,if=RGB24,KD050C-WVGA video=mxcfb1:off video=mxcfb2:off video=mxcfb3:off # Startek 800x480 LCD
</pre>
* Type in '''boot''' to proceed to kernel boot overriding default video mode.

=== Handling memory shortage ===
Devices with small amount of physical memory (~512MB) might experience memory shortage expressed by system processes being killed and restarted repeatedly, resulting in performance lag. 
In this case, freeing up some memory reserved for graphics sub-system might turn out useful, e.g. by degrading screen resolution to 720p and lowering GPU-reserved memory below default 192MB, by appropriately setting ''videomode'' bootloader variable:
<pre>
setenv videomode video=mxcfb0:dev=hdmi,if=RGB24,1280x720M@60 video=mxcfb1:off video=mxcfb2:off video=mxcfb3:off gpumem=64M
</pre>

=== Accessing Bootloader Variables from Android ===
CM-FX6 Android is packed with '''fw_printenv''' and '''fw_setenv''' u-boot tools, that allow viewing and setting U-Boot environment variables from Android, as opposed to U-Boot console. 
For instance, '''display configuration''' settings could be overridden from Android:
* Connect ADB to CM-FX6
* On PC workstation, issue
$ adb root
{{Note | In case ADB is connected via USB, detach / re-attach USB cable.}}
* Display ''videomode'' setting
$ adb shell fw_printenv videomode
* Set ''videomode'' to DVI
$ adb shell fw_setenv videomode video=mxcfb0:dev=dvi,if=RGB24,1920x1080M@60 video=mxcfb1:off video=mxcfb2:off video=mxcfb3:off
* Reboot CM-FX6

=== Automatic suspend when inactive ===
By default, CM-FX6 is configured to stay awake while connected to the power. 
In order to change this behavior, proceed to '''Settings'''->'''Developer options''', uncheck '''Stay awake ... while charging''' to enable the device going to suspended state.
{{Note|If '''Developer options''' item is hidden, re-introduce it proceeding to '''Settings'''->'''About tablet''' and clicking on '''Build number''' 7 times consequently.}}

=== ON/OFF button ===
'''ON/OFF''' button suspends and resumes CM-FX6 operation (i.e. sends to sleep / wakes up), whenever suspend is not disabled manually, or by Android policy. 
Pressing and holding the '''ON/OFF''' button for more than 5 seconds, will unconditionally power the module down. This operation is pretty much equivalent to unplugging the power supply, so it should really be considered the last resort.

=== Graceful shutdown ===
Due to specifics of i.MX6 SoC hardware, the ON/OFF button cannot be used to bring up the Android '''Power off''' menu. 
CM-FX6 pre-configures GPIO 29 (P18, pin 2 on SB-FX6 base board) as GPIO Power Button. As GPIO 29 has an internal pull-up resistor, it can be momentarily connected to the ground to produce a ''power button press''. Short press will behave identically to short press on ON/OFF button, whereas long press will bring up the '''Power off''' menu allowing graceful shutdown.

=== Physical HOME button ===
GPIO 205 (GPIO7_13) is pre-programmed as hadware HOME key.

=== Security ===
CM-FX6 Android package permits full root access. 
The '''su''' utility will switch a user to '''root''' not requiring any credentials or password. 
In order to harden system security one might replace '''su''' implementation or remove it altogether.

=== Start-up script ===
'''/system/etc/install-recovery.sh''' script is run upon system boot by Android ''init'' process with ''root'' permissions. 
As ''system'' partition is mounted 'read-only', one should remount ''system'' 'rw', prior to attempting to edit the script.

=== Networking ===
Normal Android behavior is to prioritize network interfaces (in descend order):
* Ethernet
* Wi-Fi
* ''3G [not supported]''
Whenever higher-priority network interface is available, the lower-priority interfaces will be torn down.

=== Audio sink selection ===
CM-FX6 may use either one of the following audio devices:
* '''HDMI''' - default when HDMI video is selected, and totally inaccessible otherwise
* '''analog''' - default when DVI video is selected
* '''S/PDIF'''
Audio sink selection should be done with a designated application, e.g. ''SoundAbout'', available via Google Play Store. 

{| class="wikitable" border="1" cellspacing="0"
! audio device
! sink name
|-
| HDMI
| Aux Digital (HDMI)
|-
| analog
| Speaker
|-
| S/PDIF
| Wired Headphones
|}

{{Note|If after making the selection with ''SoundAbout'' nothing happens, restart the application.}}

[[Category:Android]]
[[Category:CM-FX6]]

CM-FX6: Android: Getting started

2014-11-04T13:52:33Z

Nadav:

CM-FX6 Android

2014-11-04T13:51:40Z

Nadav:

{{summary|
This page contains up to date information about Android packages and software development for the CompuLab CM-FX6 System-on-Module / Computer-on-Module.
|Cm-fx6-top.jpg|thumb}}
{{Resources Linux
|* [[CM-FX6: Android: Getting started | Installation and update]]
* [[CM-FX6: Android: Operating instructions | Operating instructions]]
* [http://compulab.co.il/products/computer-on-modules/cm-fx6/#devres Downloads]
* [[CM-FX6:_Android:_Supported_features | Supported features]]
|* [[CM-FX6: Android: Serial console connection | Serial console connection]]
* [[Android:_ADB_setup | ADB Setup]]
* [[CM-FX6:_Android:_Building_from_source_code | Building from source code]]
|* [[Support]]
* [[CM-FX6:_Android:_Known_Issues | Known Issues]]
}}

__NOTOC__
{{ChangelogRss| content=
===== 4-Nov-2014: cm-fx6-jb-14.11.1 released =====
: ''Jelly Bean 4.3''
: - enable routing audio to S/PDIF
: - fix bug in ADS7846 touchscreen kernel driver
: - support m25px16 SPI flash ROM
: - fix rare cpu stalls in boundary temperature conditions
: - switch automatic suspend policy to ''stay awake while charging'' by default

===== 21-May-2014: cm-fx6-jb-14.05.1 released =====
: Jelly Bean 4.3 update
: Support Bluetooth
: Pre-install Google Play and Services
: Updated '''busybox''' and '''u-boot tools'''
: Enable root access via ADB

===== 21-May-2014: cm-fx6-ics-14.05.1 released =====
: Ice Cream Sandwich 4.0.4 update for SB-FX6 rev. 1.1
: Support hardware HOME button
: Support I2C bus multiplexing
: Bugfix in power management

===== 03-Apr-2014: cm-fx6-jb.14.04 released =====
: Android upgrade to Jelly Bean 4.3, based on Android for Sabre SD by Freescale.
: Full feature parity with Ice Cream Sandwich is planned for forthcoming releases.

===== 06-Jul-2013: cm-fx6-android.13.07 released =====
: Android/Linux kernel updates:
: - Added LCD display support
: - Added CAN bus support
: - Added analog audio support
: - Added resistive touch screen support

===== 06-Mar-2013: cm-fx6-android.13.02.1 released =====
: - Hotfix: EEPROM test disabled (caused the EEPROM to clear).

===== 14-Feb-2013: cm-fx6-android.13.02 released =====
: Initial Android package release for CM-FX6 based on Android 4.0.4 (Ice Cream Sandwich) for Sabre SD by Freescale

}}

[[Category:Android]]
[[Category:CM-FX6]]

CM-QS600: Android: Getting started

2014-11-04T13:12:54Z

Nadav:

== Overview ==
The following outlines the procedure necessary to install Android on the CompuLab CM-QS600 System-on-Module / Computer-on-Module.

== Installation target media ==
CM-QS600 uses on-board eMMC as root file system medium.
{{Note|Additional media might be enabled in the coming releases.}}

== Installation onto eMMC ==
=== Preconditions ===
* CM-QS600 evaluation kit.
* PC workstation with installed [[Android: Fastboot setup | fastboot]] client software.
* Connect HDMI display to the CM-QS600 ''(optional)''.
* Connect [[CM-QS600: Android: Serial console connection | serial console]] to the CM-QS600 ''(optional)''.
* Connect USB cable between the CM-QS600 USB OTG (P7) jack and PC workstation, in order to enable [[Android: Fastboot setup | fastboot]] protocol.
* Connect RTC battery to P15.

=== Flashing Android image ===
* Download prebuilt [http://compulab.co.il/products/computer-on-modules/cm-qs600/#devres Android image].

* Decompress the file, in order to get Android partition images.


* Enter ''fastboot mode'' following either of the options:
# There is no valid ''boot'' partition (which is how CM-QS600 comes out of the box).
#: In this case, the device will enter ''fastboot mode'' upon power on.
# There is a valid ''boot'' partition (i.e. CM-QS600 was pre-installed with OS).
#: In this case, the device will boot from it.
#: Accessing Android command line, one can observe and then destroy ''boot'' partition signature ("ANDROID"), effectively making ''boot'' partition invalid, going back to option '''1''' after reboot.
<pre>
# dd if=/dev/block/platform/msm_sdcc.1/by-name/boot bs=1 count=7
# echo -n "X" | dd of=/dev/block/platform/msm_sdcc.1/by-name/boot bs=1 count=1
</pre>

* Flash each partition image file to the eMMC with the aid of ''fastboot'' utility:
<pre>
$ fastboot flash boot boot.img
$ fastboot flash system system.img
$ fastboot flash cache cache.img
$ fastboot flash userdata userdata.img
</pre>



* Proceed to boot, issuing
<pre>
$ fastboot reboot
</pre>

=== Boot ===
* Power on
* Within 3 seconds the device should start booting into Android.
: Within 60 seconds the HDMI display should start showing ''signs of life''.

== See Also ==
* [[CM-QS600: Android: Serial console connection]]
* [[Android: Fastboot setup]]
* [[Android: ADB setup]]

[[Category:Android]]
[[Category:CM-QS600]]

CM-QS600 Android

2014-11-04T07:41:45Z

Nadav:

{{summary|
This page contains up to date information about the CM-QS600 Android package and software development.
|cm-qs600-top.jpg|thumb}}
{{Resources Linux
|* [[CM-QS600: Android: Getting started | Installation and boot]]
* [[CM-QS600: Android: Operating instructions | Operating instructions]]
* [http://compulab.co.il/products/computer-on-modules/cm-qs600/#devres Downloads]
|* [[CM-QS600: Android: Serial console connection | Serial console connection]]
* [[Android: Fastboot setup | Fastboot setup]]
* [[Android:_ADB_setup | ADB Setup]]
* [[CM-QS600: Android: Building from source code | Building from source code]]
|* [[Support]]
* [[CM-QS600: Android: Known Issues | Known Issues]]
}}

{{ChangelogRss| content=
===== 26-Oct-2014: cm-qs600-android.14.10.1 released =====
: ''Android KitKat 4.4.3 (engineering build)''
: - enable Wi-Fi networking
: - enable 3G modem
: - fixed HDMI flickering
: - apply performance improvement patches provided by Qualcomm
: - automount removable media
: - switch automatic suspend policy to ''stay awake while charging'' by default
: - preinstall Google Play

===== 10-Aug-2014: cm-qs600-android.14.08.1 released =====
: Initial Android package release for CM-QS600 based on Android 4.4.3 (KitKat) for APQ8064 reference design by Qualcomm.

}}

[[Category:Android]]
[[Category:CM-QS600]]

CM-QS600: Android: Getting started

2014-11-04T07:35:20Z

Nadav:

== Overview ==
The following outlines the procedure necessary to install Android on CM-QS600.

== Installation target media ==
CM-QS600 uses on-board eMMC as root file system medium.
{{Note|Additional media might be enabled in the coming releases.}}

== Installation onto eMMC ==
=== Preconditions ===
* CM-QS600 evaluation kit.
* PC workstation with installed [[Android: Fastboot setup | fastboot]] client software.
* Connect HDMI display to the CM-QS600 ''(optional)''.
* Connect [[CM-QS600: Android: Serial console connection | serial console]] to the CM-QS600 ''(optional)''.
* Connect USB cable between the CM-QS600 USB OTG (P7) jack and PC workstation, in order to enable [[Android: Fastboot setup | fastboot]] protocol.

=== Flashing Android image ===
* Download prebuilt [http://compulab.co.il/products/computer-on-modules/cm-qs600/#devres Android image].

* Decompress the file, in order to get Android partition images.


* Enter ''fastboot mode'' following either of the options:
# There is no valid ''boot'' partition - this is the factory default in which the CM-QS600 comes out of the box.
#: In this case, the device will enter ''fastboot mode'' upon power on.
# There is a valid ''boot'' partition - usually the case when android was previously installed on the device.
#: In this case, the device will boot from it.
#: Accessing Android command line, one can observe and then destroy ''boot'' partition signature ("ANDROID"), effectively making ''boot'' partition invalid, going back to option '''1''' after reboot.
<pre>
# dd if=/dev/block/platform/msm_sdcc.1/by-name/boot bs=1 count=7
# echo -n "X" | dd of=/dev/block/platform/msm_sdcc.1/by-name/boot bs=1 count=1
</pre>

* Flash each partition image file to the eMMC with the aid of ''fastboot'' utility:
<pre>
$ fastboot flash boot boot.img
$ fastboot flash system system.img
$ fastboot flash cache cache.img
$ fastboot flash userdata userdata.img
</pre>



* Proceed to boot, issuing
<pre>
$ fastboot reboot
</pre>

=== Boot ===
* Power on
* Within 3 seconds the device should start booting into Android.
: Within 60 seconds the HDMI display should start showing ''signs of life''.

== See Also ==
* [[CM-QS600: Android: Serial console connection]]
* [[Android: Fastboot setup]]
* [[Android: ADB setup]]

[[Category:Android]]
[[Category:CM-QS600]]

Android documentation

2014-10-29T11:47:44Z

Nadav:

{| 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-QS600 Android | CM-QS600]]
| [[CM-T335 Android | CM-T335]]
| [[CM-FX6 Android | CM-FX6]]
| [[CM-T3730 Android | CM-T3730]]
|-

| <linkedimage>
wikipage=CM-QS600 Android
tooltip=CM-QS600 Android documentation
img_src=Image:cm-qs600-top.jpg
img_width=200px
img_alt=CM-QS600 Android
</linkedimage>

| <linkedimage>
wikipage=CM-T335 Android
tooltip=CM-T335 Android documentation
img_src=Image:cm-t335-top.jpg
img_width=200px
img_alt=CM-T335 Android
</linkedimage>

| <linkedimage>
wikipage=CM-FX6 Android
tooltip=CM-FX6 Android documentation
img_src=Image:cm-fx6-top.jpg
img_width=200px
img_alt=CM-FX6 Android
</linkedimage>

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

|}

__NOTOC__

{{ChangelogRss| content=
===== 29-Oct-2014, CM-QS600 =====
: Updates for Android Demo Package for [[CM-QS600 Android|CM-QS600]]

===== 07-Aug-2014, CM-QS600 =====
: Initial release of Android for [[CM-QS600 Android|CM-QS600]]

===== 01-May-2014, CM-T335 =====
: Updates for Android Demo Package for [[CM-T335 Android|CM-T335]]

===== 31-Dec-2013, CM-T335 =====
: Updates for Android Demo Package for [[CM-T335 Android|CM-T335]]

===== 13-Oct-2013, CM-T3730 =====
: Updates for Android Demo Package for [[CM-T3730 Android|CM-T3730]]

===== 10-Sep-2013, CM-T335 =====
: Initial release of Android for [[CM-T335 Android|CM-T335]]

===== 06-Jul-2013, CM-FX6 =====
: Updates for Andoid Demo package for [[CM-FX6 Android|CM-FX6]]

===== 14-May-2013, CM-T3730 =====
: Updates for Android Demo Package for [[CM-T3730 Android|CM-T3730]]

===== 14-Mar-2013, CM-T3730 =====
: Updates for Android Demo Package for [[CM-T3730 Android|CM-T3730]]

===== 09-Mar-2013, CM-FX6 =====
: Initial release of Andoid Demo package for [[CM-FX6 Android|CM-FX6]]

===== 22-Jan-2013, CM-T3730 =====
: Initial pre-release of Android for [[CM-T3730 Android|CM-T3730]]
}}

[[Category:Android]]

CM-QS600: Android: Operating instructions

2014-10-29T11:45:22Z

Nadav: New page: = Overview = Most CM-QS600 [http://compulab.co.il/products/operating-systems-and-drivers-for-cm-qs600-and-sbc-qs600 supported features] are operated using normal Android controls. Thi...

CM-QS600 Android

2014-10-29T11:44:35Z

Nadav:

{{summary|
This page contains up to date information about the CM-QS600 Android package and software development.
|cm-qs600-top.jpg|thumb}}
{{Resources Linux
|* [[CM-QS600: Android: Getting started | Installation and boot]]
* [[CM-QS600: Android: Operating instructions | Operating instructions]]
* [http://compulab.co.il/products/computer-on-modules/cm-qs600/#devres Downloads]
|* [[CM-QS600: Android: Serial console connection | Serial console connection]]
* [[Android: Fastboot setup | Fastboot setup]]
* [[Android:_ADB_setup | ADB Setup]]
* [[CM-QS600: Android: Building from source code | Building from source code]]
|* [[Support]]
* [[CM-QS600: Android: Known Issues | Known Issues]]
}}

{{ChangelogRss| content=
===== 29-Oct-2014: cm-qs600-android.14.10.1 released =====
: ''Android KitKat 4.4.3 (engineering build)''
: - enable Wi-Fi networking
: - enable 3G modem
: - apply performance improvement patches provided by Qualcomm
: - automount removable media
: - switch automatic suspend policy to ''stay awake while charging'' by default
: - preinstall Google Play

===== 10-Aug-2014: cm-qs600-android.14.08.1 released =====
: Initial Android package release for CM-QS600 based on Android 4.4.3 (KitKat) for APQ8064 reference design by Qualcomm.

}}

[[Category:Android]]
[[Category:CM-QS600]]

CM-QS600: Android: Known Issues

2014-10-29T11:43:00Z

Nadav: New page: {{IssueCategory|Audio| * Occasionally, audio cannot be played back, and no sound cards appear in ''/proc/asound/cards'' special file :'''Workaround:''' :Exercise power cycle (turn power of...

CM-QS600 Android

2014-10-29T04:57:36Z

Nadav:

{{summary|
This page contains up to date information about the CM-QS600 Android package and software development.
|cm-qs600-top.jpg|thumb}}
{{Resources Linux
|* [[CM-QS600: Android: Getting started | Installation and boot]]
* [http://compulab.co.il/products/computer-on-modules/cm-qs600/#devres Downloads]
|* [[CM-QS600: Android: Serial console connection | Serial console connection]]
* [[Android: Fastboot setup | Fastboot setup]]
* [[Android:_ADB_setup | ADB Setup]]
* [[CM-QS600: Android: Building from source code | Building from source code]]
|* [[Support]]
* [[CM-QS600: Android: Known Issues | Known Issues]]
}}

{{ChangelogRss| content=
===== 29-Oct-2014: cm-qs600-android.14.10.1 released =====
: ''Android KitKat 4.4.3 (engineering build)''
: - enable Wi-Fi networking
: - enable 3G modem
: - apply performance improvement patches provided by Qualcomm
: - automount removable media
: - switch automatic suspend policy to ''stay awake while charging'' by default
: - preinstall Google Play

===== 10-Aug-2014: cm-qs600-android.14.08.1 released =====
: Initial Android package release for CM-QS600 based on Android 4.4.3 (KitKat) for APQ8064 reference design by Qualcomm.

}}

[[Category:Android]]
[[Category:CM-QS600]]

CM-QS600: Android: Getting started

2014-10-29T04:38:39Z

Nadav:

== Overview ==
The following outlines the procedure necessary to install Android on CM-QS600.

== Installation target media ==
CM-QS600 uses on-board eMMC as root file system medium.
{{Note|Additional media might be enabled in the coming releases.}}

== Installation onto eMMC ==
=== Preconditions ===
* CM-QS600 evaluation kit.
* PC workstation with installed [[Android: Fastboot setup | fastboot]] client software.
* Connect HDMI display to the CM-QS600 ''(optional)''.
* Connect [[CM-QS600: Android: Serial console connection | serial console]] to the CM-QS600 ''(optional)''.
* Connect USB cable between the CM-QS600 USB OTG (P7) jack and PC workstation, in order to enable [[Android: Fastboot setup | fastboot]] protocol.

=== Flashing Android image ===
* Download prebuilt [http://compulab.co.il/products/computer-on-modules/cm-qs600/#devres Android image].

* Decompress the file, in order to get Android partition images.


* Flash each partition image file to the eMMC with the aid of ''fastboot'' utility:
<pre>
$ fastboot flash boot boot.img
$ fastboot flash system system.img
$ fastboot flash cache cache.img
$ fastboot flash userdata userdata.img
</pre>



* Proceed to boot, issuing
<pre>
$ fastboot reboot
</pre>

=== Boot ===
* Power on
* Within 3 seconds the device should start booting into Android.
: Within 60 seconds the HDMI display should start showing ''signs of life''.

== See Also ==
* [[CM-QS600: Android: Serial console connection]]
* [[Android: Fastboot setup]]
* [[Android: ADB setup]]

[[Category:Android]]
[[Category:CM-QS600]]