From: Konstantin Kletschke <konstantin.kletschke@inside-m2m.de>
To: Roland Hieber <rhi@pengutronix.de>
Cc: Trent Piepho <trent.piepho@igorinstitute.com>,
barebox@lists.infradead.org
Subject: Re: Howto implement bootchooser <-> rauc interaction
Date: Tue, 14 Dec 2021 22:40:28 +0100 [thread overview]
Message-ID: <c4d432350649f31dbc9b732e96034785@inside-m2m.de> (raw)
In-Reply-To: <20211205225529.5rf5zqpbg7trovst@pengutronix.de>
On 2021-12-05 23:55, Roland Hieber wrote:
> You probably also want to delete your bootchooser variables from the
> env
Are you shure about that? I read some example/documentation at
bootlin.com
doing/presenting a nice phytec device tree for EEPROM state but later on
it points out to
"[...]add bootchooser variables associated to both targets in
arch/arm/<board>/env/nv[...]"
When I utilize "devinfo state" (with all global/nv bootchoser variables
removed) I get
barebox@TI AM335x BeagleBone black:/ devinfo state
Parameters:
bootstate.last_chosen: 0 (type: uint32)
bootstate.system0.ok: 0 (type: uint32)
bootstate.system0.priority: 21 (type: uint32)
bootstate.system0.remaining_attempts: 3 (type: uint32)
bootstate.system1.ok: 0 (type: uint32)
bootstate.system1.priority: 20 (type: uint32)
bootstate.system1.remaining_attempts: 3 (type: uint32)
dirty: 0 (type: bool)
init_from_defaults: 0 (type: bool)
save_on_shutdown: 1 (type: bool)
Is bootchooser smart enough to gather system0 and system1 as bootable
entries/possibilities?
For bootchooser.targets...
My system is not proven to work (I just sent a different mail with my
other issues to this thread)
yet, may be there are other issues hidden, but I do not get this part.
I created two boot entries system0 and system1 in /env/boot/ with
content mmc1.1 (for system0) and
mmc1.2 (for system1.2). Both are bootloader-spec-enabled partitions.
What me bothers is, "boot mmc1.1" works,
"boot system0" not. How do I properly make a bootchoser entry for
mmc1.1?
If no variables are required, where could be the cuplrit for this:
barebox@TI AM335x BeagleBone black:/ bootchooser
ERROR: bootchooser: Target list $global.bootchooser.targets is empty
No bootchooser found
Kind Regards,
Konsti
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2021-12-14 21:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 12:40 Konstantin Kletschke
2021-12-03 17:52 ` Trent Piepho
2021-12-05 22:55 ` Roland Hieber
2021-12-06 8:52 ` Konstantin Kletschke
2021-12-14 21:40 ` Konstantin Kletschke [this message]
2021-12-15 10:56 ` Ahmad Fatoum
2021-12-16 19:35 ` Konstantin Kletschke
2021-12-17 10:00 ` Ahmad Fatoum
2021-12-17 12:50 ` Konstantin Kletschke
2022-01-03 15:24 ` Roland Hieber
2021-12-06 8:30 ` Konstantin Kletschke
2021-12-14 21:28 ` Konstantin Kletschke
2021-12-15 10:50 ` Ahmad Fatoum
[not found] ` <297b3425baa118783dccb6446900fbfa@inside-m2m.de>
2021-12-16 19:42 ` Fwd: " Konstantin Kletschke
2021-12-17 9:46 ` Ahmad Fatoum
2021-12-17 12:43 ` Konstantin Kletschke
2021-12-17 13:08 ` Ahmad Fatoum
2021-12-17 14:21 ` Konstantin Kletschke
2021-12-22 14:05 ` Konstantin Kletschke
2022-01-05 17:50 ` Ahmad Fatoum
2022-01-06 9:59 ` Konstantin Kletschke
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=c4d432350649f31dbc9b732e96034785@inside-m2m.de \
--to=konstantin.kletschke@inside-m2m.de \
--cc=barebox@lists.infradead.org \
--cc=rhi@pengutronix.de \
--cc=trent.piepho@igorinstitute.com \
/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