Vim3Pro AOSP recovery image is too large for partition

Which Khadas SBC do you use?


Which system do you use? Android, Ubuntu, OOWOW or others?

Android Kernel 5.10

Which version of system do you use? Khadas official images, self built images, or others?

self built images
ref: Using Reference Boards  |  Android Open Source Project

Please describe your issue below:

I clone aosp kernel images follow below command.

git clone -b android-amlogic-bmeson-5.10

Then, I inserted some additional kernel functions and commands like ‘printk’ and rebuilt it.
The size of recovery.img file increased 32 MB → 32.X MB, and I modified BOARD_RECOVERYIMAGE_PARTITION_SIZE 32MB to 64MB in ‘device/amlogic/yukawa/’ file.

However, when using uboot and fastboot, I still get the below message.

FAILED (remote: too large for partition)

Which file should I modify other files or options?

Post a console log of your issue below:

target reported max download size of 117440512 bytes
sending 'recovery' (33412 KB)...
OKAY [  1.832s]
writing 'recovery'...
FAILED (remote: too large for partition)
finished. total time: 1.845s

basically same process.
just a note, in the example config file, the “-” tells the compiler that the named partition of the device partition table takes up the remainder of the storage, as the device vim3 has 2 different models with differing storage sizes, and as such is more appropriate as a universal u-boot for the both of them. normally the recovery image is able to format and setup the userdata partition for first boot, but thats not working for some reason so theres a need to create a userdata image at rom compile to get the device to work as intended.