Datasheet

When the make command is complete, the build-log.txt file contains the execution output. Please check for any errors.
For BUILD_ID & BUILD_NUMBER changing, please update build_id.mk in your ~/myandroid directory, detail step, please
check Android Frequently Asked Questions document.
For both SCM i.MX6DQ QWKS and SCM i.MX6SX EVB platforms, we use the same build configuration. They share the
same system images, except the boot, recovery and uboot image. The following outputs are generated in the directory
myandroid/out/target/product/ qwks_6scm:
• root/ : root file system (including init, init.rc, etc). Mounted at /
• system/: Android system binary/libraries. Mounted at /system
• data/: Android data area. Mounted at /data
• recovery/: root file system when booting in "recovery" mode. Not used directly.
• boot-imx6qdqscm-1gb-qwks-rev3.img: a composite image for SCM i.MX6DQ 1GB QWKS REVC (rev3) which
includes the kernel zImage, ramdisk, board's device tree binary, and boot parameters.
• boot-imx6qdqscm-1gb-qwks-rev2.img: a composite image for SCM i.MX6DQ 1GB QWKS REVB (rev2) which
includes the kernel zImage, ramdisk, board's device tree binary, and boot parameters.
• ramdisk.img: Ramdisk image generated from "root/". Not directly used.
• system.img: EXT4 image generated from "system/". Can be programmed to "SYSTEM" partition on SD/eMMC
card with "dd"
• userdata.img: EXT4 image generated from "data/".
• recovery-imx6dqscm-1gb-qwks-rev3.img: EXT4 image for SCM i.MX6DQ 1GB QWKS REVC (rev3), which is
generated from "recovery/". Can be programmed to "RECOVERY" partition on SD/eMMC card with "dd"
• recovery-imx6dqscm-1gb-qwks-rev2.img: EXT4 image for SCM i.MX6DQ 1GB QWKS REVB (rev2), which is
generated from "recovery/". Can be programmed to "RECOVERY" partition on SD/eMMC card with "dd"
• u-boot-imx6dqscm-1gb-qwks-rev3.imx: uboot image with no padding for SCM i.MX6DQ 1GB QWKS REVC
(rev3).
• u-boot-imx6dqscm-1gb-qwks-rev2.imx: uboot image with no padding for SCM i.MX6DQ 1GB QWKS REVB
(rev2).
● To build the uboot image separately, please refer to the section 3.5 ● To build the kernel uImage
separately, please refer to the section 3.6 ● To build boot.img, please refer to the section 3.7
NOTE
3.3.1 Configuration examples of building NXP devices
The following table shows examples of using the lunch command to set up different NXP devices. After the desired NXP
device is set up, the make command is used to start the build.
Build name Description
SCM i.MX6DQ QWKS Board $ lunch qwks_6scm -user
SCM i.MX6SX EVB Board $ lunch evb_6sxscm-user
3.3.2 User Build mode
A production release Android system image is created by using the user Build Type. For configuration options, see Table
"Build types" in Section Building Android images.
The notable differences between the user and eng build types are as follows:
Build Android for i.MX
SCM i.MX 6 Series Android User's Guide
NXP Semiconductors
7