From: Suniel Mahesh <sunil@amarulasolutions.com>
To: Andre Przywara <andre.przywara@arm.com>
Cc: U-Boot-Denx <u-boot@lists.denx.de>,
Michael Nazzareno Trimarchi <michael@amarulasolutions.com>,
Jagan Teki <jagan@amarulasolutions.com>
Subject: Re: Reset cause register for Allwinner H3/R16 SOC's
Date: Mon, 14 Jun 2021 10:07:47 +0530 [thread overview]
Message-ID: <CAM+7aWs8rA0mrCjqpurMQgNZAZE7CE_HtuPv-XKy4mTQ8110TQ@mail.gmail.com> (raw)
In-Reply-To: <20210613231411.7d4fb5db@slackpad.fritz.box>
Hi Andre,
On Mon, Jun 14, 2021 at 3:44 AM Andre Przywara <andre.przywara@arm.com> wrote:
>
> On Sat, 12 Jun 2021 10:17:08 +0530
> Suniel Mahesh <sunil@amarulasolutions.com> wrote:
>
> > Hi All,
> >
> > I am working on an Allwinner R16 and H3 based targets and I am implementing
> > system update.
> >
> > Is there any way(or a register) on Allwinner R16/H3 which can tell
> > what is the cause
> > of the reset(whether the reset is triggered by a watchdog or thermal
> > or reset or a POR).
>
> I don't think anybody found such an explicit gadget in Allwinner
> chips before.
> Besides, what would be the difference between watchdog, thermal and
> reset? AFAIK those are all the same watchdog triggered reset, in the
> last two cases deliberately triggered.
> If you want to convey information across a reset, you can use the RTC
> data registers: they survive a reset. So you can explicitly write some
> reset cause indicator value into one of the registers, then read that
> back after the reset.
Thanks for the insight.
My basic use case is the update mechanism on the target. The update mechanism
is implemented as follows:
1.
Assigned bootcounter to RTC GPR register. Boot count limit is 3.
If for some reason the device doesn't boot, then the WDOG waits for
specific period of time and triggers a reset.
For every WDOG reset bootcounter increments and if exceeds 3,
altbootcmd is triggered and the device boots recovery mode.
2.
The problem I am facing now is, I need to differentiate WDOG reset and a
normal reset.
If the user does a normal reset the bootcounter value should not be incremented
(as of now bootcounter value is incrementing for both WDOG reset and a
normal reset
which is obvious).
This is where I got stuck.
any more insight would be appreciated.
Suniel
> For power-on-reset there might be some heuristics to tell it apart from
> a mere reset (temperature, PMIC state, DRAM content?), but in
> general the RTC register method should also work here.
> So if you are happy to hack some board specifics into your firmware, it
> should be doable, but there does not seem to be a generic mechanism
> implemented into the SoC.
>
> Cheers,
> Andre
>
>
>
>
next prev parent reply other threads:[~2021-06-14 4:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-12 4:47 Reset cause register for Allwinner H3/R16 SOC's Suniel Mahesh
2021-06-13 22:14 ` Andre Przywara
2021-06-14 4:37 ` Suniel Mahesh [this message]
2021-06-14 5:37 ` Samuel Holland
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=CAM+7aWs8rA0mrCjqpurMQgNZAZE7CE_HtuPv-XKy4mTQ8110TQ@mail.gmail.com \
--to=sunil@amarulasolutions.com \
--cc=andre.przywara@arm.com \
--cc=jagan@amarulasolutions.com \
--cc=michael@amarulasolutions.com \
--cc=u-boot@lists.denx.de \
/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).