mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Sébastien Merle" <sebastien.merle@stritzinger.com>
To: barebox@lists.infradead.org
Subject: A/B boot on PhyCORE iMX6 with U-Boot env
Date: Fri, 5 Mar 2021 18:30:22 +0100	[thread overview]
Message-ID: <FC8C25F4-6D97-4F8C-83C0-7A1E112FCACC@stritzinger.com> (raw)

Hi,

First, I am a newbie to this and if I should use another channel to ask these questions, please forgive me and redirect me to the proper place.

I am trying to setup A/B boot on a a phyCORE imx6 board with barebox from EMMC. To test the state framework I added Barebox’s imx6ul-phytec-state.dtsi to my device tree. 
 
I am confused about the &eeprom node in imx6ul-phytec-state.dtsi used for the state backend, what is this defining ? Is this really storing the state in the EMMC ?

We would rather use U-Boot env, as our firmware creation tools only support that for now. To setup my firmware update I need to define the offset of barebox, barebox environment and U-Boot environment but I can’t find what offsets I should use so nothing clash. How could I figure out these offsets ?

The idea was to add a U-Boot environment and use a script to boot A or B in function of the U-Boot variables. Is it even possible ?

If it is possible, do I need to add a partition of the EMMC in my device tree as shown in https://www.barebox.org/doc/latest/devicetree/bindings/barebox/barebox,uboot-environment.html ?

I would be grateful for any pointers to documentation or examples to setup A/B boot on similar platform (without yocto).

Thank you very much for your time.

Best regards,
Sebastien Merle,
Peer Stritzinger GmbH.
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2021-03-05 17:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-05 17:30 Sébastien Merle [this message]
2021-03-05 20:23 ` Ahmad Fatoum

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=FC8C25F4-6D97-4F8C-83C0-7A1E112FCACC@stritzinger.com \
    --to=sebastien.merle@stritzinger.com \
    --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