Difference between revisions of "CM-QS600: Android: Getting started"

From Compulab Mediawiki
Jump to: navigation, search
Line 1: Line 1:
 
== Overview ==
 
== Overview ==
The following outlines the procedure necessary to install Android on CM-QS600.
+
The following outlines the procedure necessary to install Android on the CompuLab CM-QS600 System-on-Module / Computer-on-Module.
  
 
== Installation target media ==
 
== Installation target media ==
Line 13: Line 13:
 
* Connect [[CM-QS600: Android: Serial console connection | serial console]] 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 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 ===
 
=== Flashing Android image ===
Line 29: Line 30:
  
 
* Enter ''fastboot mode'' following either of the options:
 
* 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.
+
# 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.
 
#: 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.
+
# There is a valid ''boot'' partition (i.e. CM-QS600 was pre-installed with OS).
 
#: In this case, the device will boot from it.
 
#: 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.
 
#: 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.

Revision as of 13:12, 4 November 2014

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.

Admolition note.png Additional media might be enabled in the coming releases.

Installation onto eMMC

Preconditions

  • CM-QS600 evaluation kit.
  • PC workstation with installed fastboot client software.
  • Connect HDMI display to the CM-QS600 (optional).
  • Connect 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 fastboot protocol.
  • Connect RTC battery to P15.

Flashing Android image

  • Decompress the file, in order to get Android partition images.
  • Enter fastboot mode following either of the options:
  1. 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.
  2. 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.
       # 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
  • Flash each partition image file to the eMMC with the aid of fastboot utility:
$ fastboot flash boot     boot.img
$ fastboot flash system   system.img
$ fastboot flash cache    cache.img
$ fastboot flash userdata userdata.img


  • Proceed to boot, issuing
$ fastboot reboot

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