From: "Enrico Jörns" <ejo@pengutronix.de>
To: Steffen Kothe <steffen.kothe.gc1993@googlemail.com>
Cc: "Ulrich Ölmann" <u.oelmann@pengutronix.de>, rauc@pengutronix.de
Subject: Re: [RAUC] U-Boot Offset for RAW Image on Slot Update
Date: Tue, 16 Apr 2019 21:22:58 +0200 [thread overview]
Message-ID: <19f3f68d-9571-6608-8ab4-5926cd53af80@pengutronix.de> (raw)
In-Reply-To: <6r7ebuca7d.fsf@pengutronix.de>
Hi Steffen,
Am 16.04.19 um 16:10 schrieb Ulrich Ölmann:
> On Tue, Apr 16 2019 at 15:51 +0200, Ulrich Ölmann <u.oelmann@pengutronix.de> wrote:
>> Hi Steffen,
>>
>> On Tue, Apr 16 2019 at 14:53 +0200, Steffen Kothe <steffen.kothe.gc1993@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.
which platform (i.mx6 variant) is that exactly? Where does the
restriction come from? I would have expected that all i.mx6 platforms
can handle eMMC boot partitions the same way.
>>> 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.
This is exactly what RAUC provides out-of-the box. Thus I would like to
understand why it is not working in that case. I assume you are doing
eMMC boot partitions update to gain atomicity, right?
Did you notice the eMMC boot partition atomic update feature of RAUC?
https://rauc.readthedocs.io/en/latest/advanced.html#update-emmc-boot-partitions
It basically performs the steps Ulrich described above.
And please consider subscribing to the mailing list, because posts by
non-members are blocked by default (and you won't receive messages that
are replied to the list only... ;) ).
Thanks and best regards
Enrico
--
Pengutronix e.K. | Enrico Jörns |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-5080 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
RAUC mailing list
next prev parent reply other threads:[~2019-04-16 19:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 12:53 Steffen Kothe
2019-04-16 13:51 ` Ulrich Ölmann
2019-04-16 14:10 ` Ulrich Ölmann
2019-04-16 19:22 ` Enrico Jörns [this message]
2019-04-23 7:38 ` Steffen Kothe
2019-04-23 7:53 ` Jan Lübbe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19f3f68d-9571-6608-8ab4-5926cd53af80@pengutronix.de \
--to=ejo@pengutronix.de \
--cc=rauc@pengutronix.de \
--cc=steffen.kothe.gc1993@googlemail.com \
--cc=u.oelmann@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox