Custom boot.img with android_p9.0.0_2.3.0

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Custom boot.img with android_p9.0.0_2.3.0

1,297 Views
dylanjohnson
Contributor I

Hello!


We're attempting to create a custom boot image alongside other pre-made image files for a custom Android build. Currently, we're using the IMX8mm EVK for development and separate hardware that we've written custom kernel drivers for. We've finished the kernel driver and tested everything on Linux (kernel 4.14) and know that it is working as intended, but porting over to Android has been the main hurdle.


We've tested the pre-built images for the android_p9.0.0_2.3.0 and know that the IMX8mm EVK is working as intended, so there shouldn't be any issues with the board. We've repackaged our custom built kernel with the extracted ramdisk binary from the pre-built boot image of android_p9.0.0_2.3.0 to create our own boot image. Finally, we attempted to run the fsl-sdcard-partition.sh script with all of the pre-built images, but we replaced the boot.img file with our own custom boot.img file. Unfortunately, it's unable to boot with the custom image (boot error log attached). Note that the same SD card was used originally for testing the fully pre-built images, so it hopefully shouldn't be an issue with the SD card.


Would anything else need to be modified to get the custom Android build running? Is this process even correct? We're combining documentation from Google (mainly for building custom kernels and boot images) as well as the Android User's Guide from android_P9.0.0_2.3.0_docs. Any help on this process would be greatly appreciated. Let me know if I need to share any additional documents if this is specifically an issue with the build process.

--Dylan Johnson

0 Kudos
2 Replies

1,203 Views
chpub70
Contributor II

Hi,

As the vbmeta.img is not updated, so AVB will fail. Unless you port the kernel to Android_build. Otherwise, you need to modify the uboot to bypass this check.

Best Regards,

Pun

0 Kudos

1,203 Views
IvanRuiz
NXP Employee
NXP Employee

Hello,

A reply was already made via case, please see below:

It is not recommended to replace the boot.img. A correct implementation would require to import the necessary Drivers to the corresponding target version and generate the boot image on the target version.

Hope it helps!

BR,

Ivan.

0 Kudos