openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Ivan Mikhaylov <i.mikhaylov@yadro.com>
To: Lei Yu <yulei.sh@bytedance.com>
Cc: Alexander Amelkin <a.amelkin@yadro.com>,
	openbmc <openbmc@lists.ozlabs.org>
Subject: Re: Design proposal for dual BMC flash with "golden image"
Date: Wed, 16 Sep 2020 15:06:23 +0300	[thread overview]
Message-ID: <0bf34c28a4640d9155c3143775dfd0f7b0ee8101.camel@yadro.com> (raw)
In-Reply-To: <CAGm54UFFzkTTKCXCCpFunp8i23Eu8n25gXWcjx5RWm9ioWwrdg@mail.gmail.com>

On Wed, 2020-09-16 at 18:18 +0800, Lei Yu wrote:
> On Wed, Sep 16, 2020 at 5:55 PM Ivan Mikhaylov <i.mikhaylov@yadro.com> wrote:
> > > For now, we use "devmem" to manipulate the registers for testing purpose.
> > > It's nice to have that driver, but in productions there will be no
> > > need to use devmem nor the ioctl on watchdog, so it's not a must for
> > > us to use the driver.
> > > 
> > 
> > And how you switch safely into golden side in this case?
> > 
> 
> The plan is:
> 1. When the primary flash is broken and u-boot could not be started,
> aspeed will switch to the golden side automatically.
> 2. When the primary flash's u-boot is OK, but the kernel/rofs fails a
> couple of times, the u-boot could detect this and switch to the golden
> side by setting the related registers. See example in
> https://github.com/openbmc/openbmc/blob/master/meta-phosphor/aspeed-layer/recipes-bsp/u-boot/files/0005-config-ast-common-Fall-back-to-secondary-flash-on-fa.patch

That's the standard procedure, I'm saying that you may need the access to the
golden side at any time for different purposes(support engineers, manufacturing
department, some problems in field) and how you can achieve that? With u-boot
env set or manual watchdog trigger?

Thanks.

  parent reply	other threads:[~2020-09-16 12:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-11  8:49 Design proposal for dual BMC flash with "golden image" Lei Yu
2020-09-11 11:48 ` Alexander Amelkin
2020-09-11 12:01   ` Lei Yu
2020-09-11 14:26     ` Ivan Mikhaylov
2020-09-15  3:38       ` Lei Yu
2020-09-16  9:58         ` Ivan Mikhaylov
2020-09-16 10:18           ` Lei Yu
2020-09-16 10:35             ` Alexander Amelkin
2020-09-16 12:06             ` Ivan Mikhaylov [this message]
2020-09-16 12:13               ` Lei Yu
2020-09-22 14:19                 ` Ivan Mikhaylov

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=0bf34c28a4640d9155c3143775dfd0f7b0ee8101.camel@yadro.com \
    --to=i.mikhaylov@yadro.com \
    --cc=a.amelkin@yadro.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=yulei.sh@bytedance.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;
as well as URLs for NNTP newsgroup(s).