From: "Jorge Ramirez-Ortiz, Foundries" <jorge@foundries.io>
To: Michal Simek <michal.simek@xilinx.com>
Cc: "Jorge Ramirez-Ortiz, Foundries" <jorge@foundries.io>,
u-boot@lists.denx.de
Subject: Re: Zynq MPSoC - secure boot
Date: Tue, 22 Jun 2021 12:58:04 +0200 [thread overview]
Message-ID: <20210622105804.GA1542@trex> (raw)
In-Reply-To: <1c26fc5f-3f0a-7445-4435-d263517a9ed8@xilinx.com>
On 22/06/21, Michal Simek wrote:
> Hi,
>
> On 6/21/21 7:27 PM, Jorge Ramirez-Ortiz, Foundries wrote:
> > hi Michal,
> >
> > Is secure boot supported using SPL? or is there a plan for it (maybe a
> > branch somewhere that I can work from and contribute to?).
>
> I have it on my list but haven't had a time to dig into it yet.
>
> >
> > ATM looking into how to write the key sha to the fuses without Vivado.
>
> The first level of secure boot will be using integrated bootrom
> mechanism and only vivado bootgen can generate images for it. It means
> maybe you will be able to avoid Vivado for efuses programming but not
> for image generation as of now.
um, that is a pity - I was hoping it would be as simple as working
with iMX since the basic principles are the same...but ok, the
integration of the tools are on this ocasion somewhat behind.
>
> As I said I have never had a time to look at it that's why I don't know
> enough to guide you how to do it.
sure np, will browse FSBL and some docs. thanks for your quick response.
>
> Thanks,
> Michal
prev parent reply other threads:[~2021-06-22 10:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 17:27 Zynq MPSoC - secure boot Jorge Ramirez-Ortiz, Foundries
2021-06-22 7:02 ` Michal Simek
2021-06-22 10:58 ` Jorge Ramirez-Ortiz, Foundries [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=20210622105804.GA1542@trex \
--to=jorge@foundries.io \
--cc=michal.simek@xilinx.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