In addition to what's required of an [Android bootloader (ABL)][6], the SDV Core Bootloader (or the guest "loader" running on the host within the Hypervisor, if there's no ABL on the guest side) needs to perform the following:
- Verify SDV images as per Android Verified Boot 2.0.
- Generate the Android HLOS CDI layer.
Kernel parameters
The SDV Core bootloader must pass the kernel parameters described in the following sections.
androidboot.verifiedbootstate
In SDV, it's not possible to set a custom root of trust for Android
Verified boot. For example, by the owner of the vehicle. Therefore, in SDV Core
there are no yellow androidboot.verifiedbootstate. Possible values are:
- green: bootloader is locked
- orange: bootloader is unlocked
androidboot.sdv.instance_name
The SDV VM instance name.
androidboot.sdv.boot_mode
In addition to being present in the Android HLOS CDI certificate, the SDV Boot
Mode is also passed to SDV Core as a kernel parameter named
androidboot.sdv.boot_mode.
Possible values are locked and unlocked.
androidboot.sdv.vvmfactorytrust
The VVMFactoryTrust, a SHA-256 hash value, encoded as a hexadecimal string
of 64 characters, case-insensitive. If the VVMFactoryTrust hasn't been written
, or if it's not supported, the value of androidboot.sdv.vvmfactorytrust
should be the string 00 (two characters).