On Tue, Apr 16 2019 at 15:51 +0200, Ulrich Ölmann <u.oelm...@pengutronix.de> wrote: > Hi Steffen, > > On Tue, Apr 16 2019 at 14:53 +0200, Steffen Kothe > <steffen.kothe.gc1...@googlemail.com> wrote: >> I try to update the U-Boot Loader on two different partitions. >> >> /dev/mmcblk3boot0 >> /dev/mmcblk3boot1 >> >> A restriction on our i.Mx6 platform is location of the u-boot entry on >> the partition. >> >> Offset: 1024 Byte Address: 0x400 >> >> So a raw copy would start at address 0x00, but we have to start 0x400 >> for the entry point. >> >> Does rauc provides any options to customize the startaddress for a raw >> copy/install of a binary file (u-boot binary)? >> >> I have took a look into the source code, but found out, that there is >> no option to customize the default offset address for a write on a >> partition. >> >> >> Could you provide some help in this case? > > take a look at hooks, especially the subsubsection "Install Hook": > https://rauc.readthedocs.io/en/latest/using.html#slot-hooks .
... and use your own logic for updating the bootloader (forgot to mention that): write a script that switches the eMMC's bootloader partition from read-only to read-write and use the mmc-utils (see [1] & [2]) to atomically switch the eMMC's partition once it was written. Best regards Ulrich [1] git://git.kernel.org/pub/scm/linux/kernel/git/cjb/mmc-utils.git [2] https://github.com/torvalds/linux/blob/master/Documentation/mmc/mmc-tools.txt -- Pengutronix e.K. | Ulrich Ölmann | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ RAUC mailing list
