Android Customizing the Linux kernel: Difference between revisions
From Variscite Wiki
No edit summary |
|||
Line 127: | Line 127: | ||
== Flashing bootimage to target == | == Flashing bootimage to target == | ||
Make sure device is in the fastboot mode if not , reboot in fastboot mode by using below commands. | Make sure device is in the fastboot mode if not , reboot in fastboot mode by using below commands. <br> | ||
adb reboot bootloader | |||
adb reboot bootloader | |||
$ fastboot flash boot boot-<setup-name>.img | $ fastboot flash boot boot-<setup-name>.img | ||
Replace setup-name as per above table. | Replace setup-name as per above table. |
Revision as of 23:41, 31 December 2018
Manual build Android Linux Kernel
Change to Android top level directory.
$ cd / $ source build/envsetup.sh $ lunch var_mx6-eng or $ lunch var_mx6-user
Note: var_mx6-user creates a production version of Android. var_mx6-eng creates an engineering version of Android. Development mode enable and development tools are available on target.
Switching from eMMC build to SD card build and vice versa
When you switch your target MMC device you need to remove the fstab file. This will guarantee that the make system will copy the right one into target.
$ rm out/target/product/var_mx6/recovery/root/fstab* out/target/product/var_mx6/root/fstab*
Build Android for SD card
$ make -j4 BUILD_TARGET_DEVICE=sd bootimage 2>&1 | tee build1-1.log
- Note: When running Android from an SD card, the eMMC will be detected and presented as an SD card storage.
Build Android for on-SOM eMMC
$ make -j4 BUILD_TARGET_DEVICE=emmc bootimage 2>&1 | tee build1-1.log
This will generate image as per table below
Setup Name |
Images Names |
SOM type |
Carrier Board type |
LCD Type |
Evaluation Kit name |
---|---|---|---|---|---|
som-mx6qp-c | boot-som-mx6qp-c.img, recovery-som-mx6qp-c.img |
VAR-SOM-MX6_V2 (Quad Plus) | VAR-MX6CustomBoard | Capacitive touch | VAR-DVK-MX6_V2-PRO, VAR-STK-MX6_V2 |
som-mx6qp-r | boot-som-mx6qp-r.img, recovery-som-mx6qp-r.img |
VAR-SOM-MX6_V2 (Quad Plus) | VAR-MX6CustomBoard | Resistive touch | VAR-DVK-MX6_V2, VAR-STK-MX6_V2 |
som-mx6qp-vsc | boot-som-mx6qp-vsc.img, recovery-som-mx6qp-vsc.img |
VAR-SOM-MX6_V2 (Quad Plus) | VAR-SOLOCustomBoard | Capacitive LVDS touch | N/A |
som-mx6q-c | boot-som-mx6q-c.img, recovery-som-mx6q-c.img |
VAR-SOM-MX6_V2 (Quad / Dual) | VAR-MX6CustomBoard | Capacitive touch | VAR-DVK-MX6_V2-PRO, VAR-STK-MX6_V2 |
som-mx6q-r | boot-som-mx6q-r.img, recovery-som-mx6q-r.img |
VAR-SOM-MX6_V2 (Quad / Dual) | VAR-MX6CustomBoard | Resistive touch | VAR-DVK-MX6_V2, VAR-STK-MX6_V2 |
som-mx6q-vsc | boot-som-mx6q-vsc.img, recovery-som-mx6q-vsc.img |
VAR-SOM-MX6_V2 (Quad / Dual) | VAR-SOLOCustomBoard | Capacitive LVDS touch | N/A |
som-mx6dl-c | boot-som-mx6dl-c.img, recovery-som-mx6dl-c.img |
VAR-SOM-MX6_V2 (DualLite/ Solo) | VAR-MX6CustomBoard | Capacitive touch | N/A |
som-mx6dl-r | boot-som-mx6dl-r.img, recovery-som-mx6dl-r.img |
VAR-SOM-MX6_V2 (DualLite/ Solo) | VAR-MX6CustomBoard | Resistive touch | N/A |
som-solo-vsc | boot-som-solo-vsc.img, recovery-som-solo-vsc.img |
VAR-SOM-SOLO / VAR-SOM-DUAL | VAR-SOLOCustomBoard | Capacitive LVDS touch | VAR-DVK-SOLO/DUAL, VAR-STK-SOLO/DUAL |
som-solo-c | boot-som-solo-c.img, recovery-som-solo-c.img |
VAR-SOM-SOLO / VAR-SOM-DUAL | VAR-MX6CustomBoard | Capacitive touch | N/A |
imx6q-var-dart | boot-imx6q-var-dart.img, recovery-imx6q-var-dart.img |
DART-MX6 | VAR-DT6CustomBoard | Capacitive touch | VAR-STK-DT6, VAR-DVK-DT6 |
Flashing bootimage to target
Make sure device is in the fastboot mode if not , reboot in fastboot mode by using below commands.
adb reboot bootloader $ fastboot flash boot boot-<setup-name>.img
Replace setup-name as per above table.