Compulab Mediawiki - User contributions [en]

CM-QS600: Android: Building from source code

2015-11-01T13:23:09Z

Andreyg: /* Flash ''boot.img'' onto eMMC */

= Overview =
The following outlines the procedure necessary to acquire the Android source code and build it for CM-QS600 System-on-Module / Computer-on-Module.<br/>
CompuLab Android package is obtained by applying CompuLab patches on top of Code Aurora Forum's Android package for APQ8064 CDP platform.

= Prerequisites =
The required steps, as described below, were tested on Ubuntu 14.04 (Trusty).<br/>
Install required packages, as outlined on [http://source.android.com/source/initializing.html#installing-required-packages-ubuntu-1404 AOSP web-page].<br/>
Install additional packages (not listed on AOSP web-page):
$ sudo apt-get install xz-utils make flex lib32z1 zip curl
Install {{filename|repo}} tool for work with multiple {{filename|git}} repositories in the context of Android:
$ curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
$ chmod a+x ~/bin/repo

= Getting Android Source Code =
== Deploy Code Aurora Forum base ==
Download the code base from Code Aurora Forum (CAF):

$ mkdir ~/android
$ cd ~/android
$ 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.}}

== Deploy Wireless kernel driver ==
Clone out of tree wireless kernel driver:
<pre>
$ cd ~/android/external
$ git clone git://codeaurora.org/platform/external/compat-wireless.git compat-wireless
$ git checkout -b codeaurora LNX.LF.3.2-27500-8x10.1
</pre>

== Deploy CompuLab Android package ==
=== Download software package ===
Download CM-QS600 [http://www.compulab.co.il/products/computer-on-modules/cm-qs600/#devres Android software package] in order to access the development resources:
* Prebuilt Qualcomm proprietary libraries for bluetooth, audio, camera, etc.
* CompuLab patches on top of Android for APQ8064 including Linux kernel patches, Android device configuration files and firmware binary blobs.

Uncompress the software package to {{filename|~/tmp}} directory.

=== Unpack Qualcomm proprietary prebuilt libraries ===
Extract prebuilt Qualcomm proprietary libraries:
<pre>
$ tar -xJf ~/tmp/cm-qs600-android/development/cm-qs600-qcom-proprietary.tar.xz -C ~/android/vendor/qcom/
</pre>

=== Apply CompuLab patch ===
Apply CompuLab patch with the aid of the provided utility:
<pre>
$ cd ~/android
$ ~/tmp/cm-qs600-android/development/compulab-patch-apply.sh ~/tmp/cm-qs600-android/development/patches
</pre>

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

{{note|In case Java version required by the build system is different from the system default, download and install the required JDK version, and export path to its root directory:<pre>$ export JAVA_HOME=/path/to/JDK</pre>}}

While the {{cmd|make}} instruction above builds the whole Android image, including all its partitions, it is possible to build {{filename|boot}} partition alone, which is useful for most Android hacking use cases as the {{filename|boot}} partition contains the '''kernel''' and the '''ramfs''' with most of configuration files:
* Bring up kernel configuration menu for adjusting the kernel configuration:<pre>$ make kernelconfig</pre>
* Build boot image (kernel + initramfs):<pre>$ make bootimage -j4</pre>

== Build Summary ==
Upon successful build, the output directory ({{filename|~/android/out/target/product/bellatrix}}) contains ready to deploy OS partitions represented both as directories with appropriate files and compressed image files ready to deploy onto the eMMC:
{| class="wikitable" border="1" cellspacing="0"
! partition<br/>name
! directory
! image file
! file system<br/>type
! access
! mount point
! default<br/>partition<br/>size [MB]
! designation
! notes
|-
| boot
| root
| boot.img
| style="text-align:center;" | -
| read only
| style="text-align:center;" | -
| 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;" | -
| 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
| style="text-align:center;" | 512
| the entire OS:<br/>
Android UI, system applications
| style="text-align:center;" | -
|-
| cache
| cache
| cache.img
| style="text-align:center;" | ext4
| read / write
| /cache
| style="text-align:center;" | 64
| frequently accessed data cache
| style="text-align:center;" | -
|-
| userdata
| data
| userdata.img
| style="text-align:center;" | ext4
| read / write
| /data
| style="text-align:center;" | 2048
| user applications and content
| style="text-align:center;" | -
|-
|}
<br/>

= Deploying Android Image on Target Medium =
The root of Android file system is located on a RAM-disk. Physical storage device partitions, such as {{filename|system}}, {{filename|cache}}, {{filename|userdata}}, are mounted under the root.
These partitions mounting rules are specified in {{filename|/fstab}} file.<br/>
Root on a physical device or on NFS are also viable options. Those options are useful throughout development stage.<br/>
On CM-QS600, LK bootloader expects a valid boot partition ({{filename|boot.img}}) to be present on the eMMC.
In case LK cannot identify a valid boot partition, it falls back to [[Android: Fastboot setup|fastboot mode]].

=== 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>

{{note|More detailed description of the file system deployment on the eMMC is available on the [[CM-QS600: Android: Getting started#Installation onto eMMC | Getting started]] page.}}

=== 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 {{filename|system}} partition contents, maintaining proper file permissions:
<pre>
$ export OUT=~/android/out/target/product/bellatrix
$ export SYSTEM=/media/user/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
</pre>

{{note|The {{parameter|SYSTEM}} location above is specified as it appears in Ubuntu 14.04. It may differ in other Ubuntu versions or distributions.}}

==== Re-build ''boot.img'' with patched ''fstab'' ====
* Edit {{filename|device/qcom/bellatrix/fstab.qcom}} file, in order to override default destination storage medium:
<pre>
--- HEAD.fstab.qcom 2015-09-22 11:48:27.958235845 +0300
+++ fstab.qcom 2015-09-22 11:48:36.962236014 +0300
@@ -9,5 +9,5 @@
#boot time mount
-/dev/block/platform/msm_sdcc.1/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.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/system /system ext4 ro,barrier=1 wait
+/dev/block/platform/msm_sdcc.3/by-name/cache /cache ext4 nosuid,nodev,noatime,barrier=1 wait,check
+/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 {{filename|boot.img}}:
<pre>$ make bootimage -j4</pre>

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

{{Note|The same considerations are applicable to file system deployment on mSATA drive.}}

= See Also =
* [[CM-QS600: Android: Software package | Software package contents]]
* [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: Known Issues

2015-10-26T15:51:26Z

Andreyg:

{{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|Cellular modem|
* Occasionally, Telit 3G modem cannot detect the SIM card.
:'''Workaround:'''
:Istruct the modem to assume SIM card is present, i.e. simulate SIM inserted, by adding to the [[CM-QS600: Android: Enabling platform features#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]]

Android: Fastboot setup

2015-09-21T08:55:48Z

Andreyg: /* Forcing fastboot mode */

= Overview =
Fastboot is a protocol and associated utility, used primarily to modify flash file system while the device is running a bootloader. Fastboot operates via USB OTG. In addition to the bootloader implementing the fastboot protocol, fastboot client utility must be installed on user's workstation.

= Getting Fastboot =
In general fastboot utility is provided within the [http://developer.android.com/sdk/index.html Android SDK]. Also some Linux disributions provide fastboot within their package repositories.
For example, on Ubuntu platform, fastboot may be obtained via {{parameter|android-tools-fastboot}} package.

= Useful commands =
* List connected devices <pre>$ fastboot devices</pre>
* Reboot device <pre>$ fastboot reboot</pre>
* Flash image file onto partition identified by its name, e.g. ''boot'' <pre>$ fastboot flash boot boot.img</pre>
* Boot device, loading ''boot.img'' from the PC workstation, instead of boot partition <pre>$ fastboot boot boot.img</pre>

= Forcing fastboot mode =
Normally a bootloader will proceed to booting a valid boot partition. In case there is none, the bootloader will fall back into fastboot mode.<br/>
There are a few options to force fastboot mode despite valid boot partition:
* By rebooting to fastboot mode. Issue on either workstation <pre>$ adb reboot bootloader</pre> or Android device itself <pre># reboot bootloader</pre>
* By powering up while pressing the '''boot select''' button.
* By invalidating boot partition. Destroy boot partition signature, issuing on the device (in either Linux or Android command line): <pre># dd if=/dev/zero of=/path/to/boot/partition bs=1 count=1</pre>
{{Note | path-to-boot-partition may be, e.g, {{filename | /dev/block/platform/msm_sdcc.1/by-name/boot}} }}

= See Also =
* [http://wiki.cyanogenmod.org/w/Doc:_fastboot_intro Fastboot introduction]

[[Category:Android|Fastboot setup]]

CM-QS600: Android: Serial console connection

2015-09-21T08:49:10Z

Andreyg:

== Overview ==
By default, the serial console provides access to
* kernel console
* bootloader command line interface

== Routing ==
The serial console is routed, via serial to USB converter, to (P16) mini-USB jack.<br/>
The line speed is pre-set to 115200 bps.

== Software configuration ==
Below provided directions for configuring PuTTY (or its fork project KiTTY).<br/>
Notice, on Ubuntu Linux, the user running PuTTY might be required to belong to ''dialout'' user group.<br/>
* Launch PuTTY.
* Change the ''Connection type'' to ''Serial''.
* Set the following configuration options:
** Serial line
** Speed
[[Image:PuTTY-1-options.jpg]]
* From the ''Connection'' menu on the left, select ''Serial''
* Select a serial line:<br/>Select a serial line associated with the connected device, which most probably will not be COM1.
* Configure the serial line:
** Speed (baud): 115200
** Data bits: 8
** Stop bits: 1
** Parity: none
** Flow control: none
[[Image:PuTTY-2-config.jpg]]
* Click ''Open''.
<br/>
At this point PuTTY is configured, its terminal should display the serial console.

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

Template:Resources 4col

2015-08-02T11:48:32Z

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

{| style="border: 1px solid #aaaaaa; margin-top: 20px;" width="100% }}"
| style="line-height: 120%; border-bottom: 1px solid #aaaaaa; font-size: 105%; background-color: #eeeeee;" {{!}} '''Resources'''
|-
| style="padding-top: 10px" {{!}}
{| style="border:0; margin: 0;" width="100%" cellspacing="10"
| valign="top" class="mainpage_hubbox" |
<div class="mainpage_hubtitle">'''Evaluation'''</div>
<div class="mainpage_boxcontents">
{| style="border: 0; margin: 0;" cellpadding="3"
| valign="top" | {{{1}}}
| valign="top" |
{{{2}}}
|}
</div>
| valign="top" class="mainpage_hubbox" |
<div class="mainpage_hubtitle">'''Tools'''</div>
<div class="mainpage_boxcontents">
{| style="border: 0; margin: 0;" cellpadding="3"
| valign="top" | {{{3}}}
| valign="top" |
{{{4}}}
|}
</div>
| valign="top" class="mainpage_hubbox" |
<div class="mainpage_hubtitle">'''Development'''</div>
<div class="mainpage_boxcontents">
{| style="border: 0; margin: 0;" cellpadding="3"
| valign="top" | {{{5}}}
| valign="top" |
{{{6}}}
|}
</div>
| valign="top" class="mainpage_hubbox" |
<div class="mainpage_hubtitle">'''Troubleshooting'''</div>
<div class="mainpage_boxcontents">
{| style="border: 0; margin: 0;" cellpadding="3"
| valign="top" | {{{7}}}
| valign="top" |
{{{8}}}
|}</div>
|}
|}

CM-FX6: Android: Supported features

2013-07-04T20:16:53Z

Andreyg:

{| border="1" cellspacing="0" cellpadding="3" width="75%" style="margin: 1em auto 1em auto;"
|+ '''CM-FX6 Android ICS 4.0.4'''
|- style="background: #D3D3D3"
| align="center" | '''Feature'''<br>
| align="center" | '''Description'''
| align="center" | '''Status'''
| align="center" | '''Notes'''
|- style="background: #EEEEEE"
| align="center" colspan="4" | '''Storage'''
|-
| (full size) SD-Card
| Boot device
| align="center" | +
| P6 slot
|-
| SATA
|
| align="center" | +
| Cannot boot from
|-
| NAND Flash
|
| align="center" | +
| Tested with UBIFS
|-
| I2C EEPROM
|
| align="center" | +
|
|-
|- style="background: #EEEEEE"
| align="center" colspan="4" | '''Video output'''
|-
| HDMI
|
| align="center" | +
|
|-
| DVI
|
| align="center" | +
|
|-
| LCD
|
| align="center" | +
|
|-
| Video decoding
| HW accelerated video playback
| align="center" | +
| Builtin Android player
|-
|- style="background: #EEEEEE"
| align="center" colspan="4" | '''Audio output'''
|-
| HDMI
|
| align="center" | +
|
|-
| Analog
|
| align="center" | +
|
|-
| align="center" colspan="4" | '''IO interfaces'''
|-
| Gigabit Ethernet
|
| align="center" | +
|
|-
| Wi-Fi
|
| align="center" | -
|
|-
| Bluetooth
|
| align="center" | -
|
|-
| UART
| Serial console
| align="center" | +
|
|-
| CAN bus
|
| align="center" | +
| still requires application stack
|-
| USB Host
|
| align="center" | +
|
|-
| USB OTG
| ADB over USB, exporting filesystem
| align="center" | +
|
|-
|- style="background: #EEEEEE"
| align="center" colspan="4" | '''Misc'''
|-
| RTC
| Keeping system time over power down
| align="center" | +
|
|-
| ON/OFF button
| sending OS to sleep and waking it up
| align="center" | +
|
|-
|}

[[Category:Android|Supported features]]
[[Category:CM-FX6|Android: Supported features]]

Android: ADB setup

2013-02-14T15:48:36Z

Andreyg: /* ADB over USB */

Android Debug Bridge is an interface and a command line utility that provides low level control of an Android powered device (physical or emulated).<br/>
To name a few of its features -
* command line shell
* installed package management
* IDE interface for application development
Refer to [http://developer.android.com/tools/help/adb.html Android developer network] for more details.<br/>
== Getting ADB ==
ADB is provided in the Android SDK.<br/>
To get a prebuilt version of ADB (for Linux/OSX/Windows) proceed to the [http://compulab.co.il/products/computer-on-modules/cm-fx6/#devres Downloads] section.

== ADB over IP ==
ADB over IP is set up by default on CM-FX6.<br/>
It can be set by executing the following Android command line:
$ setprop service.adb.tcp.port 5555
===Access Android device via ADB===
Type in on host PC:
$ export ADBHOST=<Android-device-IP-address>
$ adb kill-server
$ adb start-server
$ adb <args...>
Among useful ''args'' are<br/>
* devices - list connected devices<br/>
* shell - run command line shell<br/>
* logcat - view Android log<br/>
* install - install Android application (*.apk)
* push - copy file from host to Android device

== ADB over USB ==
* Properly configure a Linux PC workstation, i.e.<br/>
echo SUBSYSTEM==\"usb\", ATTR{idVendor}==\"18d1\", MODE=\"0666\", GROUP=\"plugdev\" >> /etc/udev/rules.d/51-android.rules
* ADB over USB requires ADB over IP be disabled.<br/>Test ADB TCP port by executing in Android command line:
$ getprop service.adb.tcp.port
:If there is a value, and it is not -1 - it should be set to -1:
$ setprop service.adb.tcp.port -1
* In Android graphic user interface enable ''Settings->Developer options->USB debugging''.
* Connect a USB cable from the PC workstation to the CM-FX6 USB device jack - P48.<br/>At this point ''adb devices'', run on the PC workstation should list your device among attached devices.

===Access Android device via ADB===
Type in on host PC:
$ adb devices # optional
$ adb <args...>

[[Category:Android|ADB setup]]

CM-FX6: Android: Supported features

2013-02-14T15:43:21Z

Andreyg:

{| border="1" cellspacing="0" cellpadding="3" width="75%" style="margin: 1em auto 1em auto;"
|+ '''CM-FX6 Android ICS 4.0.4'''
|- style="background: #D3D3D3"
| align="center" | '''Feature'''<br>
| align="center" | '''Description'''
| align="center" | '''Status'''
| align="center" | '''Notes'''
|- style="background: #EEEEEE"
| align="center" colspan="4" | '''Storage'''
|-
| (full size) SD-Card
| Boot device
| align="center" | +
| P6 slot
|-
| SATA
|
| align="center" | +
| Cannot boot from
|-
| NAND Flash
|
| align="center" | +
| Tested with UBIFS
|-
| I2C EEPROM
|
| align="center" | +
|
|-
|- style="background: #EEEEEE"
| align="center" colspan="4" | '''Video output'''
|-
| HDMI
|
| align="center" | +
|
|-
| DVI
|
| align="center" | +
|
|-
| Video decoding
| HW accelerated video playback
| align="center" | +
| Builtin Android player
|-
|- style="background: #EEEEEE"
| align="center" colspan="4" | '''Audio output'''
|-
| HDMI
|
| align="center" | +
|
|-
| Analog
|
| align="center" | -
| in progress
|-
| align="center" colspan="4" | '''IO interfaces'''
|-
| Gigabit Ethernet
|
| align="center" | +
|
|-
| Wi-Fi
|
| align="center" | -
|
|-
| Bluetooth
|
| align="center" | -
|
|-
| UART
| Serial console
| align="center" | +
|
|-
| USB Host
|
| align="center" | +
|
|-
| USB Device
| ADB over USB
| align="center" | +
|
|-
|- style="background: #EEEEEE"
| align="center" colspan="4" | '''Misc'''
|-
| RTC
| Keeping system time over power down
| align="center" | +
|
|-
|}

[[Category:Android|Supported features]]
[[Category:CM-FX6|Android: Supported features]]

CM-FX6: Android: Serial console connection

2013-02-14T14:58:35Z

Andreyg:

By default, the serial console provides access to
* kernel console
* bootloader command line interface
== Kernel console ==
The kernel console with full root access, provides the most powerful access gate to the CM-FX6 module.
== Bootloader command line interface ==
Prior to kernel boot, the serial console provides the '''U-Boot''' bootloader command line interface, which enables modification of kernel boot arguments.<br/>
Upon power on, U-Boot performs a short countdown (default 3 seconds), prior to proceeding to kernel boot.<br/>
Press ENTER to stop the countdown, and access the command line interface. Type in '''boot''' to proceed to kernel boot.

== Connecting to serial console ==
The serial console is routed to the P60 RS232 jack on the SB-FX6 base board.<br/>
The line speed is 115200 bps.<br/>
<br/>
Below provided directions for configuring [http://www.tucows.com/preview/503076 IVT VT220] in Windows:<br/>
* Launch IVT VT220.
* In transport protocol, choose "Serial" with the following settings:
** Portname: Com''X'' (''X'' is the serial port number used. The port number can be found in Windows Device Manager in the ''ports'' section).
** Baud rate: 115200
** Parity: None
** Data bits: 8
** Stop bits: 1 <br>[[Image:CM_T35_IVT_Create_Session_Window.jpg.jpg]]
* Press the "Setup" button.
* The "IVT Setup System" window opens. Press the serial settings button.<br>[[Image:CM_T35_IVT_Setup_System_Window.jpg]]
* In the Serial Setup window, choose the following settings: <br>[[Image:CM_T35_IVT_Serial_Setup_Window.jpg]]
* Save the settings.

[[Category:Android|Serial console connection]]
[[Category:CM-FX6|Android: Serial console connection]]

CM-FX6: Android: Known issues

2013-02-14T14:26:15Z

Andreyg:

This is only a partial list of known issues and possible workarounds.<br/>
Some of them are constant, others only occasional - so don't be disturbed.<br/>

{{IssueCategory|HDMI|
* Occasionally HDMI video would not show up
:'''Workaround:'''
: make sure signal source selector on the display is still set to HDMI
}}

{{IssueCategory|SATA|
* When SATA is configured in U-Boot, it cannot be configured under Linux
:'''Workaround:'''
: Disable SATA in U-Boot, consequently giving up the ability to boot from SATA device
}}

[[Category:Android|Known issues]]
[[Category:CM-FX6|Android: Known issues]]

CM-FX6: Android: Getting started

2013-02-14T13:23:52Z

Andreyg: /* Preconditions */

== Preconditions ==
* PC workstation
* CM-FX6 evaluation kit [[Media:CM-FX6_Properly_Connected2.jpg|properly connected]]
* SD-Card with minimal capacity of 2GB, which will serve as the boot source

== Creating a bootable SD-Card ==
* Download the compressed [http://compulab.co.il/products/computer-on-modules/cm-fx6/#devres SD-Card image].<br/>Ensure the integrity of the downloaded file by testing its MD5 summary.<br/>
* Unzip the file in order to get the ''dd'' image.<br/>
* Copy the bootable image to the SD-Card following the [https://help.ubuntu.com/community/Installation/FromImgFiles instructions provided] for selection of operating systems.<br/>If you are running Linux, you might prefer the instructions below:<br/>
# dd if=cmfx6-android.img of=/dev/sdc

== Boot ==
* Insert the bootable SD-Card into P6 SD-Card slot.
* Power on.<br/>Press '''RESET''' while '''BOOT SELECT''' is pressed.
* Within 3 seconds the device should start booting into Android.<br/>Within 60 seconds the HDMI display should start showing ''signs of life''.
===Advanced boot===
By default CM-FX6 uses HDMI display with 1080p resolution.<br/>
This can be changed 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.
setenv videomode video=mxcfb0:dev=ldb,if=RGB24,1280x720M@60 fbmem=28M # DVI display with 720p resolution
setenv videomode video=mxcfb0:dev=hdmi,if=RGB32,1920x1080M@60 fbmem=48M # default video mode
* Type in '''boot''' to proceed to kernel boot overriding default video mode.

== Upon first boot ==
* Any Android system performs ''first boot ceremony'' where it introduces its main controls - CompuLab's release is no different.
* With no delay, enable ''Settings->Developer options->Stay awake (...) while charging'' - this will prevent the device from entering ''not yet well managed'', ''hard to wake from'' sleep.

[[Category:Android|Getting started]]
[[Category:CM-FX6|Android: Getting started]]