From: "Çağlar Kilimci" <ckilimci@gmail.com>
To: Martin Hollingsworth <Martin.Hollingsworth@itk-engineering.de>
Cc: barebox <barebox@lists.infradead.org>
Subject: Re: Bootchooser - remaining_attempts
Date: Wed, 12 Jul 2017 10:08:16 +0300 [thread overview]
Message-ID: <CAGUZs0mQMQ_J6BNk4H3me_8t_pNC4aRYErSzmTSbHGVj6MrQ2Q@mail.gmail.com> (raw)
In-Reply-To: <11441e7979d54a34951ab2bd2860a75f@itk-engineering.de>
Hello Martin,
Firstly, thank you for your reply.
2017-07-11 12:45 GMT+03:00 Martin Hollingsworth
<Martin.Hollingsworth@itk-engineering.de>:
> Hello Caglar,
> I am no expert in bootchooser, but I am currently implementing it on an imx6 board using barebox 2017-3.
>
> Regarding the first issue. These are my settings, with them target A is successfully disabled after 5 attempts and never automatically enabled again.
> I set the "default_xxx" values within the config-board script of my barebox default-environment. I do not set the current values (like "A.remaining_attempts") within the environment. They are generated on the first execution of bootchooser and stored within the nv variables. Do you maybe accidentally overwrite the current values on startup with some script from the environment? (happened to me ^^^).
> Have you tried explicitly configuring global.bootchooser.reset_attempts='' as empty, instead of not defining it?
Actually, no. I did not intentionally set reset_attempts as an empty
string. As your recommend, while setting it as an empty string, I saw
that each boot time I am setting bootchooser variable from the state
framework:
nv bootchooser.system1.boot=$state.bootchooser.system1.boot
nv bootchooser.system1.default_attempts=$state.bootchooser.system1.default_attempts
nv bootchooser.system1.remaining_attempts=$state.bootchooser.system1.remaining_attempts
nv bootchooser.system1.default_priority=$state.bootchooser.system1.default_priority
nv bootchooser.system1.priority=$state.bootchooser.system1.priority
nv bootchooser.system2.boot=$state.bootchooser.system2.boot
nv bootchooser.system2.default_attempts=$state.bootchooser.system2.default_attempts
nv bootchooser.system2.remaining_attempts=$state.bootchooser.system2.remaining_attempts
nv bootchooser.system2.default_priority=$state.bootchooser.system2.default_priority
nv bootchooser.system2.priority=$state.bootchooser.system2.priority
I am now decreasing 1 from the state each boot time. After enough
unsuccessful attempts, it is disabled and never enabled again.
Thanks again.
Best Regards,
--
Çağlar Kilimci
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2017-07-12 7:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 12:36 Çağlar Kilimci
2017-07-10 6:48 ` Çağlar Kilimci
2017-07-11 9:45 ` AW: " Martin Hollingsworth
2017-07-12 7:08 ` Çağlar Kilimci [this message]
2017-07-11 10:48 ` B Gol
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=CAGUZs0mQMQ_J6BNk4H3me_8t_pNC4aRYErSzmTSbHGVj6MrQ2Q@mail.gmail.com \
--to=ckilimci@gmail.com \
--cc=Martin.Hollingsworth@itk-engineering.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