After building is complete, you can find the target files in the following path:
${MY_ANDROID}/out/target/product/evk_8mn/obj/PACKAGING/target_files_intermediates/evk_8mn-
target_files-${date}.zip
7.1.2 Building a full update package
A full update is one where the entire final state of the device (system, boot, and vendor partitions) is contained in the package.
You can use the following commands to build a full update package under the Android environment:
$ cd ${MY_ANDROID}
$ source build/envsetup.sh
$ lunch evk_8mn-userdebug
$ make otapackage -j4
After building is complete, you can find the OTA packages in the following path:
${MY_ANDROID}/out/target/proudct/evk_8mn/evk_8mn-ota-${date}.zip
evk_8mn-ota-${date}.zip
includes
payload.bin
and
payload_properties.txt
. The two files are used for full update.
•
${date}
is the BUILD_NUMBER in
build_id.mk
.
NOTE
7.1.3 Building an incremental update package
An incremental update contains a set of binary patches to be applied to the data that is already on the device. This can result in
considerably smaller update packages:
• Files that have not changed do not need to be included.
• Files that have changed are often very similar to their previous versions, so the package only needs to contain encoding of
the differences between the two files. You can install the incremental update package only on a device that has the old or
source build used when constructing the package.
Before building an incremental update package, see Section 7.1.1 to build two target files:
• PREVIOUS-target_files.zip: one old package that has already been applied on the device.
• NEW-target_files.zip: the latest package that is waiting to be applied on the device.
Then use the following commands to generate the incremental update package under the Android environment:
$ cd ${MY_ANDROID}
$ ./build/tools/releasetools/ota_from_target_files -i PREVIOUS-target_files.zip NEW-target_files.zip
incremental_ota_update.zip
${MY_ANDROID}/incremental_ota_update.zip
includes
payload.bin
and
payload_properties.txt
. The two files are used
for incremental update.
7.2 Implementing OTA update
7.2.1 Using update_engine_client to update the Android platform
update_engine_client is a pre-built tool to support A/B (seamless) system updates. It supports update system from a remote
server or board's storage.
To update system from a remote server, perform the following steps:
NXP Semiconductors
Over-The-Air (OTA) Update
Android
™
User's Guide, Rev. P9.0.0_2.3.2, 6 March 2020
User's Guide
18 / 31
