Skip to main content

[TOC]

Notes

SDK Compatibility​

androidboot.mode Compatibility​

For SDK versions earlier than Android 8.1, U-Boot must enable the following configuration to boot Android properly:

CONFIG_RKIMG_ANDROID_BOOTMODE_LEGACY

For the reason, please refer to the commit:

commit a7774f5911624928ed1d9cfed5453aab206c512e
Author: Zhangbin Tong <zebulun.tong@rock-chips.com>
Date:   Thu Sep 6 17:35:16 2018 +0800

    common: boot_rkimg: set "androidboot.mode=" as "normal" or "charger"

    - The legacy setting rule is deprecated(Android SDK < 8.1).
    - Provide CONFIG_RKIMG_ANDROID_BOOTMODE_LEGACY to enable legacy setting.

    Change-Id: I5c8b442b02df068a0ab98ccc81a4f008ebe540c1
    Signed-off-by: Zhangbin Tong <zebulun.tong@rock-chips.com>
    Signed-off-by: Joseph Chen <chenjh@rock-chips.com>

misc Compatibility​

The purpose of misc.img is to serve as a boot interaction mechanism between U-Boot and Android. Its main content is the BCB (Bootloader Control Block).

Due to historical reasons on the RK platform, for SDK versions Android 10.0 and above, the BCB in misc.img must be stored at offset 0 of the misc partition; for versions below Android 10.0, the BCB must be stored at offset 16KB of the misc partition.

Users who obtain the released SDK do not need to handle this additionally — U-Boot will adapt automatically. However, if users mix misc.img from different SDKs, problems may occur. The typical symptom is that Android will keep entering recovery mode.