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 15:18:50 +0200	[thread overview]
Message-ID: <ba1febb9b457f5876959f093f866b680e266f987.camel@pengutronix.de> (raw)
In-Reply-To: <8f4d5c086afb381b17a2289bdc7e22129a51d9e7.camel@gmail.com>

On Tue, 2024-07-23 at 14:44 +0200, Stefano Manni wrote:
> Hi,
> 
> On Tue, 2024-07-23 at 14:24 +0200, Rouven Czerwinski wrote:
> > 
> > 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.
> > 
> 
> after enabling CAAM I see:
> 
>   rng_self_test: RNG software self-test passed
>   caam 2100000.crypto@2100000.of: Instantiated RNG4 SH1
> 
> but the HAB warning is still there.
> 
> I read from drivers/crypto/caam/rng_self_test.c that the warning is
> a false positive due to an incorrect implementation of the RNG
> self-test procedure in the boot ROM.
> So running the RNG selftest in the bootloader shoul help find
> real RNG failures that may be obfuscated by this false positive.
> 
> Is correct my understanding?

Yes, this is correct. You'll probably want to send a patch to modify
the habv4_known_rng_fail_events[] array in drivers/hab/habv4.c, this
should prevent it from being displayed as an error. 

Best regards,
Rouven Czerwinski



  reply	other threads:[~2024-07-23 13:19 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
2024-07-23 12:44   ` Stefano Manni
2024-07-23 13:18     ` Rouven Czerwinski [this message]
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=ba1febb9b457f5876959f093f866b680e266f987.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