How to build kernel for Android

This article explains how to build the Android^® kernel binaries (including the kernel image, the modules and the device trees) for a selected STM32 device. It is intended for Distribution Package users.

The Android^TM Linux^® Common kernel is used in the distribution package.

1. Prerequisites

The environment must be installed using the Distribution Package adapted to the selected microprocessor device. See the list of Android^TM Distribution Package.

To be able to execute the following instructions work from the distribution root directory and initialize the environment:

 source build/envsetup.sh
 bspsetup
 lunch aosp_<BoardId>-userdebug

Information

The bspsetup instruction only needs to be run once for the each distribution

The distribution includes prebuilt kernel binaries used to generate the partition images (boot, dt and vendor). These binaries are available in the device/stm/<STM32Series>-kernel/prebuilt directory.

2. Partition layout

The Linux^® kernel binary is part of the boot partition.

The Linux^® kernel drivers built as loadable modules (.ko files) are part of the vendor partition.

The device tree binary file is part of the dt partition.

For information on the complete partition layout for the selected development platform, refer to the corresponding Flash mapping article named Your_development_platform Flash mapping for Android. Example: STM32MP15 Flash mapping for Android for the STM32MP15 boards.

All Flash mapping for Android^TM articles belong to the Category:Flash mapping for Android.

3. Load the kernel sources

By default, the kernel sources are not part of the STM32MPU distribution for Android^TM. To load the sources, execute the following instruction:

 load_kernel

This will load the Android™ common Linux^® kernel sources. These are located in the device/stm/<STM32Series>-kernel/linux-<STM32Series> directory.

Information

The load_kernel script uses the configuration file available in the /device/stm/<STM32Series>-kernel/source/patch/<kernel version>/ directory.

4. Build the kernel

After retrieving the kernel sources, it is built using:

 build_kernel

The output is located in: out-bsp/<STM32Series>/KERNEL_OBJ

This instruction generates the kernel, DT and gpu modules. It is possible to generate them separately from one another:

 build_kernel dtb
 build_kernel gpu
 build_kernel vmlinux

For more details check the instruction helper:

 build_kernel --help
 Usage: build_kernel [Options] [Command]

This script builds the Linux^® kernel source

Options:

  -h/--help: print this message
  -i/--install: update prebuilt images
   -v/--version: get script version
   --verbose: enable verbose output.

Instruction: only one instruction is supported at a time.

  dtb: build only device-tree binaries
  gpu: build only gpu module (the kernel is build if not already performed)
  defaultconfig: build only .config based on default defconfig files and fragments
  menuconfig: display standard Linux® kernel menuconfig interface
  modules: build only kernel modules binaries (kernel is build if not already performed)
  mrproper: execute make mrproper on targeted kernel
  vmlinux: build only kernel vmlinux binary

5. Integrate the kernel

To integrate the new kernel, modules or/and device tree in the distribution, the prebuilt images have to be update first:

 build_kernel -i

or

 build_kernel -i dtb
 build_kernel -i modules
 build_kernel -i vmlinux

And then build the distribution to generate output images.

 make -j

Finally, update the associated device partitions. Refer to How to populate boards for Android

6. Customize the kernel

If the kernel configuration has to be changed, refer to How to customize kernel for Android page.

eval,disco (Generic term used, to complete configuration modules paths depending on used board)

stm32mp1

Flash memory shortened to gain space in titles, tables and block diagrams

Device Tree

eval,disco (Generic term used, to complete configuration modules paths depending on used board)

stm32mp1

Flash memory shortened to gain space in titles, tables and block diagrams

Device Tree

Flash memories combine high density and cost effectiveness of EPROMs with the electrical erasability of EEPROMs. For this reason, the Flash memory market is one of the most exciting areas of the semiconductor industry today and new applications requiring in system reprogramming, such as cellular telephones, automotive engine management systems, hard disk drives, PC BIOS software for Plug & Play, digital TV, set top boxes, fax and other modems, PC cards and multimedia CD-ROMs, offer the prospect of very high volume demand.