On 6/12/19 3:22 PM, Igor Opaniuk wrote:
Hi,
Currently a lot of boards started (AFAIK: Colibri/Apalis iMX6/iMX7/iMX8QXP; TI AM56XX [1] etc.) using hardware boot0/1 partitions for storing U-boot blob (which obviously speeds up the booting process).
Taking into account that current implementation of fastboot driver does support only flashing images to "software" partitions in the user data area, does it make sense to add also the same support for boot0/boot1?
It will definitely simplify and unify the way of firmware flashing, as currently people are playing around with `mmc partinfo`/`mmc write` and flashing stuff manually instead of using fastboot (where it's enabled).
My suggestion is to introduce custom handling for `boot0` and `boot1` in the same manner as done for `zimage` [2] [3] for re-packing Android boot image with the new zImage. Example of flashing:
-> fastboot flash boot0 u-boot.img
Question: are there any objections (why it should not be done)/limitations I'm not aware of?
Thanks for your suggestions.
[1] http://git.ti.com/cgit/cgit.cgi/ti-u-boot/ti-u-boot.git/tree/board/ti/am65x/... [2] http://git.denx.de/?p=u-boot.git;a=blob;f=drivers/fastboot/fb_mmc.c;h=90ca81... [3] http://git.denx.de/?p=u-boot.git;a=blob;f=drivers/fastboot/fb_mmc.c;h=90ca81...
+CC Lukasz, Peng.