mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Rouven Czerwinski <r.czerwinski@pengutronix.de>
To: Stefano Manni <stefano.manni@gmail.com>, barebox@lists.infradead.org
Subject: Re: HAB warning on imx6sx
Date: Tue, 23 Jul 2024 14:24:22 +0200	[thread overview]
Message-ID: <c91faed04802d13072ac42b233216fc5cb414d4f.camel@pengutronix.de> (raw)
In-Reply-To: <CANn9nbgEYhJEPCZs4oQ-TBLM5OFz-076yiwRCYzewPJVfoiKMw@mail.gmail.com>

Hi,

On Tue, 2024-07-23 at 14:09 +0200, Stefano Manni wrote:
> Hello,
> 
> on a board based on imx6sx I'm facing the following warning when
> HABv4
> is enabled on barebox 2024.02:
> 
> 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)
> 
> Have you ever experienced something like this? On another board based
> on on imx6ul I've never seen it.
> 
> Should I ignore it? Maybe it disappears when I secure the device?

This is a common warning on some i.MX6 devices which indicates a CAAM
RNG self-test failure, see the description in
drivers/crypto/caam/rng_self_test.c which should be run by the
bootloader to ensure that the RNG part of the CAAM is not faulty.
This requires the CAAM driver within barebox to be enabled.

Best regards,
Rouven Czerwinski



  reply	other threads:[~2024-07-23 12:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-23 12:09 Stefano Manni
2024-07-23 12:24 ` Rouven Czerwinski [this message]
2024-07-23 12:44   ` Stefano Manni
2024-07-23 13:18     ` Rouven Czerwinski
2024-07-23 14:54       ` Stefano Manni

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=c91faed04802d13072ac42b233216fc5cb414d4f.camel@pengutronix.de \
    --to=r.czerwinski@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --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