From: Nitin Garg <nitin.garg@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4] imx: Support i.MX6 High Assurance Boot authentication
Date: Tue, 30 Sep 2014 09:46:19 -0500 [thread overview]
Message-ID: <542AC23B.4040701@freescale.com> (raw)
In-Reply-To: <CAOMZO5ArrXk8w_euwD4Tty23qi23YJiteNUbvJvoXTaoq_BiYA@mail.gmail.com>
Hi Fabio,
On 09/30/2014 08:44 AM, Fabio Estevam wrote:
> Hi Nitin,
>
> On Tue, Sep 16, 2014 at 3:33 PM, Nitin Garg <nitin.garg@freescale.com> wrote:
>> When CONFIG_SECURE_BOOT is enabled, the signed images
>> like kernel and dtb can be authenticated using iMX6 CAAM.
>> The added command hab_auth_img can be used for HAB
>> authentication of images. The command takes the image
>> DDR location, IVT (Image Vector Table) offset inside
>> image as parameters. Detailed info about signing images
>> can be found in Freescale AppNote AN4581.
>>
>> Signed-off-by: Nitin Garg <nitin.garg@freescale.com>
>
> I have just tested the 'hab_status' command and it hangs my mx6sxsabresd board:
>
> U-Boot 2014.10-rc2-16959-g6eb2f0d-dirty (Sep 30 2014 - 10:28:19)
>
> CPU: Freescale i.MX6SX rev1.0 at 792 MHz
> Reset cause: POR
> Board: MX6SX SABRE SDB
> I2C: ready
> DRAM: 1 GiB
> MMC: FSL_SDHC: 0
> In: serial
> Out: serial
> Err: serial
> PMIC: PFUZE100 ID=0x10
> Net: FEC [PRIME]
> Hit any key to stop autoboot: 0
> => hab_status
>
> Secure boot disabled
>
> (hangs the system)
>
> Could you please take a look at this issue?
>
I found the reason for the hang. The HAB api table was not
updated for i.MX6SX. Since i.MX6SX ROM implements unified
sections in ROM, the HAP function pointers needs to be
updated. I have sent a patch for the same.
-Nitin
prev parent reply other threads:[~2014-09-30 14:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 18:33 [U-Boot] [PATCH v4] imx: Support i.MX6 High Assurance Boot authentication Nitin Garg
2014-09-22 14:07 ` Stefano Babic
2014-09-22 14:12 ` Nitin Garg
2014-09-22 14:21 ` Stefano Babic
2014-09-30 13:44 ` Fabio Estevam
2014-09-30 14:46 ` Nitin Garg [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=542AC23B.4040701@freescale.com \
--to=nitin.garg@freescale.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