mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Christian Eggers <ceggers@arri.de>
To: barebox@lists.infradead.org
Subject: Updating barebox from Linux
Date: Tue, 4 Feb 2020 15:08:18 +0100	[thread overview]
Message-ID: <3901844.loAZRtzaGB@n95hx1g2> (raw)

Platform: i.MX6 (booting from NAND)

I would like to be able to update Barebox from Linux using a framework like 
RAUC or swupdate. The RAUC documentation states:

https://rauc.readthedocs.io/en/latest/advanced.html#bootloader-update-ideas
> 7.6.3. Bootloader Update Ideas
> 
> The NXP i.MX6 supports up to four bootloader copies when booting from NAND
> flash. The ROM code will try each copy in turn until it finds one which is
> readable without uncorrectable ECC errors and has a correct header. By
> using the trait of NAND flash that interrupted writes cause ECC errors and
> writing the first page (containing the header) last, the bootloader images
> can be replaced one after the other, while ensuring that the system will
> boot even in case of a crash or power failure.
> 
> The slot type could be called “boot-imx6-nand” analogous to eMMC.

In the barebox documentation I only found how to update barebox via the 
barebox_update command within barebox itself.

Updating barebox seems to be SoC specific. Is there already any existing code 
to do this from Linux? Or would it be more wise to write the new barebox image 
to a temporary UBI partition and let barebox do the update itself on next 
reboot?

regards
Christian





_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2020-02-04 14:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-04 14:08 Christian Eggers [this message]
2020-02-04 15:02 ` Sascha Hauer

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=3901844.loAZRtzaGB@n95hx1g2 \
    --to=ceggers@arri.de \
    --cc=barebox@lists.infradead.org \
    /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