Skip to content

Building Android SDK

Fetch SDK Source Code

Note

1. Source code MUST NOT be placed in a HOST shared folder for building if you use a virtual machine ENV.
2. DO NOT build source as ROOT.

1. Download SDK .

2. Copy the source code archive to the build host directory.

3. Verify file integrity using MD5.

Example: If the MD5 checksum file for the downloaded SDK code file is named t527-android13.0-20251103.md5, execute the following command to verify file integrity:

md5sum -c t527-android13.0-20251103.md5

Execution Result:

t527-android13.0-20251103.tar.gz: OK

4. Extract the source code archive.

Example: If the source code archive is named t527-android13.0-20251103.tar.gz, execute the following command to extract it:

tar -zxvf t527-android13.0-20251103.tar.gz

Execution Result: You will see output similar to the following: 

./.git/
./.git/objects/
./.git/objects/info/
./.git/objects/pack/
./.git/objects/pack/pack-1c772b481d2d4daa60f5065d9dde9eba68aa09f4.pack
./.git/objects/pack/pack-1c772b481d2d4daa60f5065d9dde9eba68aa09f4.idx
./.git/objects/pack/pack-f3436a64e1037f9724ac55cf89574b61f11e60a5.pack
./.git/objects/pack/pack-f3436a64e1037f9724ac55cf89574b61f11e60a5.idx
./.git/description
./.git/branches/
./.git/FETCH_HEAD
./.git/hooks/
./.git/hooks/applypatch-msg.sample
./.git/hooks/pre-commit.sample
.....
........

5. After extraction is complete, if the source directory only contains a .git folder, enter the following command to restore the source directory:

git reset --hard

Initial Compilation Configuration

The build environment needs to be configured for the first compilation. If the SDK location remains unchanged subsequently, this configuration does not need to be repeated.

1. In the extracted source code directory, execute the following command to enter the longan directory:

cd longan

2. Execute the following command to configure the core information for the development board:

./build.sh config

Execution Steps:

!!! Warning Please configure according to the example below.

Select the following configuration
========ACTION List: mk_config ;========
options :
All available platform:
       0. android
       1. linux
Choice [android]: 0
All available ic:
       0. a523
       1. a527
       2. t527
Choice [t527]: 2
All available board:
       0. demo
       1. demo_battery
       2. demo_car
       3. demo_fastboot
       4. demo_linux_aiot
       5. demo_linux_car
    Choice [demo]: 0
All available flash:
       0. default
       1. nor
 Choice [default]: 0

3. After completing above steps, execute the following command to select the specific board model:

./build.sh lunch

Tip

Here we select the second option, choose the number 2.

will lunch sdk

You're building on Linux
Lunch menu...pick a combo:

1. BoardConfig-t527-default.mk
2. BoardConfig-t527-kickpi-k9.mk
Which would you like? [0]: 2

Building the full Image

1. Before building the full image, return to the extraction directory by executing the following command:

cd -

2. Execute the command to start building the full image:

./build_all.sh

Note

The building speed depends on the computer's hardware performance. Typically, the compilation time ranges between 30 minutes and 90 minutes.
Generated image directory: longan/out/update-t527-kickpi_k9_v1.0-android13-lvds0-7-1024-600-2025110410-v1.0.img

Execution Result:

image-20251105222717996

Build part images individually

Tip

Building U-Boot, Kernel, and configuring the kernel are all executed in the longan directory.

cd longan

Build U-Boot Separately

./build.sh uboot

Build Kernel Separately

./build.sh kernel

Configure Kernel

./build.sh menuconfig
./build.sh saveconfig

Build Android standalone

Tip

Build Android in SDK's root folder.

cd -
make -j16

Device Tree Paths

Tip

U-Boot and Kernel each have their own device tree files.

Kernel device tree path:

longan/device/config/chips/t527/configs/demo/kickpi_k9_v1.0_kernel.dts

U-Boot device tree path:

longan/device/config/chips/t527/configs/demo/uboot-board.dts