mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Valentina Rusu <skorpyon1992@gmail.com>
To: barebox@lists.infradead.org
Subject: Raspberry Pi Barebox State Integration - SD card
Date: Tue, 4 Jun 2019 09:32:59 +0300	[thread overview]
Message-ID: <CAPYMOwmwmX3G0cHp6DSmw+GxRmENThtABnQdSS-2cL=kgfYYPg@mail.gmail.com> (raw)

    Hello guys,

I want to integrate Barebox state for Raspberry Pi 3 in order to use
it along Barebox bootchooser and RAUC software update.
I have built my image using Yocto Pyro 2.3.2, barebox 2019.04.0 (added
a recipe in my meta layer, based on meta-barebox).
I have integrated Barebox bootchooser and tested it with some
hardcoded values for the target priority and remaining attempts. Works
fine.

The issue to integrate Barebox state are the following:
* we need to specify a backend for the "state" node;
* the backend should point to an of partition on a non-volatile memory;
* other boards have EEPROM, NAND besides SD card and they are
described in the device tree; RPi has no such thing;
* somehow I need to write the state on the SD card in a location where
does not interfere with the partitions created (boot, rootfs, user
partitions, etc);
* the SD card device (mci0) is automatically detected at startup, and
not described in the device tree;

I need to know how should I proceed? How should I describe that
"dynamic" device in my device tree, so I could point it in the
"backend" variable of the state node?

Thank you very much!

      Best regards,
       Vali.

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

             reply	other threads:[~2019-06-04  6:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-04  6:32 Valentina Rusu [this message]
2019-06-04  7:52 ` Tomaž Šolc
2019-06-04  8:59 ` Moritz Augsburger
     [not found] <mailman.44637.1559659159.2376.barebox@lists.infradead.org>
2019-06-05  4:26 ` Valentina Rusu
2019-06-05  6:46   ` Moritz Augsburger

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='CAPYMOwmwmX3G0cHp6DSmw+GxRmENThtABnQdSS-2cL=kgfYYPg@mail.gmail.com' \
    --to=skorpyon1992@gmail.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