All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] nxp: HABv4 secure boot on iMX7 NAND broken
Date: Tue, 30 Jul 2019 14:32:35 +0100	[thread overview]
Message-ID: <6a373006-65e5-191a-1ae7-d66bfaa66be5@linaro.org> (raw)
In-Reply-To: <CAByghJZn8d91uFr5JXSR=jXcfU4engZP_=buOk7MNNjaVeigLA@mail.gmail.com>



On 30/07/2019 12:00, Igor Opaniuk wrote:
> Hi folks,
> 
> Just curious if you ever faced any issues with HABv4 based
> secure boot on iMX7 SoC-based boards + NAND +
> mainline U-Boot (although it works perfectly when booting from
> eMMC).
> 
> I'm currently playing with it on Colibri iMX7 NAND version,
> following all steps from [1],
> (colibri_imx7_defconfig, where CONFIG_SECURE_BOOT=y
> and CONFIG_FSL_CAAM=y, without these two options enabled
> it's booting ok) and facing the same issue as explained
> in one of NXP forum threads [2]. Taking into account that default
> BootROM doesn't provide any output at all to the serial console it is like
> looking for a needle in a haystack.

When HAB authentication fails in the BootROM it should drop you back 
into serial download mode.

Does that happen ?

  reply	other threads:[~2019-07-30 13:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-30 11:00 [U-Boot] nxp: HABv4 secure boot on iMX7 NAND broken Igor Opaniuk
2019-07-30 13:32 ` Bryan O'Donoghue [this message]
2019-07-30 13:56   ` Igor Opaniuk
2019-07-30 14:02     ` Bryan O'Donoghue
2019-07-30 14:08       ` Bryan O'Donoghue
2019-07-30 14:26         ` Igor Opaniuk
2019-07-30 14:33           ` Bryan O'Donoghue
2019-09-12 13:55             ` Igor Opaniuk
2019-09-16  2:54               ` Breno Matheus Lima
2019-09-16  8:42                 ` Igor Opaniuk

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=6a373006-65e5-191a-1ae7-d66bfaa66be5@linaro.org \
    --to=bryan.odonoghue@linaro.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.