mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Stefano Manni <stefano.manni@gmail.com>
Cc: Rouven Czerwinski <r.czerwinski@pengutronix.de>
Subject: Re: [PATCH] habv4: ignore engine failure due to RNG self-test in boot ROM
Date: Wed, 24 Jul 2024 10:42:51 +0200	[thread overview]
Message-ID: <172181057152.2579936.10127840573389033275.b4-ty@pengutronix.de> (raw)
In-Reply-To: <9bf8686f882714867ac2dc864c8e5539ad06400b.camel@gmail.com>


On Tue, 23 Jul 2024 17:31:51 +0200, Stefano Manni wrote:
> boot ROM
> 
> Few i.MX chips which have HAB 4.2.3 or beyond, have oberserved
> following warning message generated by HAB due to incorrect
> implementation of RNG self-test in boot ROM:
> 
> 	HABv4: Status: Operation completed with warning (0x69)
> 	HABv4: Config: Non-secure IC (0xf0)
> 	HABv4: State: Non-secure state (0x66)
> 	ERROR: HABv4: -------- HAB Event 0 --------
> 	ERROR: HABv4: event data:
> 	ERROR: HABv4:  db 00 24 42  69 30 e1 1d
> 	ERROR: HABv4:  00 08 00 02  40 00 36 06
> 	ERROR: HABv4:  55 55 00 03  00 00 00 00
> 	ERROR: HABv4:  00 00 00 00  00 00 00 00
> 	ERROR: HABv4:  00 00 00 01
> 	ERROR: HABv4: Status: Operation completed with warning (0x69)
> 	ERROR: HABv4: Reason: Engine failure (0x30)
> 	ERROR: HABv4: Context: Event logged in hab_rvt.entry() (0xe1)
> 	ERROR: HABv4: Engine: CAAM (0x1d)
> 
> [...]

Applied, thanks!

[1/1] habv4: ignore engine failure due to RNG self-test in boot ROM
      https://git.pengutronix.de/cgit/barebox/commit/?id=04656c1bde1e (link may not be stable)

Best regards,
-- 
Sascha Hauer <s.hauer@pengutronix.de>




      reply	other threads:[~2024-07-24  8:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-23 15:31 Stefano Manni
2024-07-24  8:42 ` Sascha Hauer [this message]

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=172181057152.2579936.10127840573389033275.b4-ty@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=r.czerwinski@pengutronix.de \
    --cc=stefano.manni@gmail.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