From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] arm: mxs: Add support for generating signed BootStream
Date: Fri, 4 Apr 2014 13:54:17 +0200 [thread overview]
Message-ID: <201404041354.17241.marex@denx.de> (raw)
In-Reply-To: <533E80C9.4080606@denx.de>
On Friday, April 04, 2014 at 11:52:09 AM, Stefano Babic wrote:
> Hi Marek,
>
> On 03/04/2014 19:12, Marek Vasut wrote:
> > This patch adds the groundwork for generating signed BootStream, which
> > can be used by the HAB library in i.MX28. We are adding a new target,
> > u-boot-signed.sb , since the process for generating regular non-signed
> > BootStream is much easier. Moreover, the signed bootstream depends on
> > external _proprietary_ _binary-only_ tool from Freescale called 'cst',
> > which is available only under NDA.
> >
> > To make things even uglier, the CST or HAB mandates a kind-of circular
> > dependency. The problem is, unlike the regular IVT, which is generated
> > by mxsimage, the IVT for signed boot must be generated by hand here due
> > to special demands of the CST. The U-Boot binary (or SPL binary) and IVT
> > are then signed by the CST as a one block. But here is the problem. The
> > size of the entire image (U-Boot, IVT, CST blocks) must be appended at
> > the end of IVT. But the size of the entire image is not known until the
> > CST has finished signing the U-Boot and IVT. We solve this by expecting
> > the CST block to be always 3904B (which it is in case two files, U-Boot
> > and the hand-made IVT, are signed in the CST block).
> >
> > Signed-off-by: Marek Vasut <marex@denx.de>
> > Cc: Stefano Babic <sbabic@denx.de>
> > ---
> >
> > Makefile | 2 +
> > arch/arm/cpu/arm926ejs/mxs/Makefile | 60
> > ++++++++++++++++++++++++++
> > arch/arm/cpu/arm926ejs/mxs/mxsimage-signed.cfg | 10 +++++
> > 3 files changed, 72 insertions(+)
> > create mode 100644 arch/arm/cpu/arm926ejs/mxs/mxsimage-signed.cfg
> >
> > NOTE: Stefano, I had to tweak this to play well with kbuild.
>
> ok - only to track what we have already discussed via IIRC.
>
> The patch was already accepted, but it conflicts with current
> u-boot-arm. I revert it on u-boot-imx, and Marek rebased it.
>
> Marek, I could not apply it directly after merging u-boot-arm - maybe
> because we set on different commit id. Never mind, I merge it again and
> it looks ok.
>
> I have pushed a -test branch on u-boot-imx after merging u-boot-arm and
> your patches. It looks ok, and if you do not complain, I will send it to
> Albert for inclusion in u-boot-arm.
All good, thank you !
Best regards,
Marek Vasut
next prev parent reply other threads:[~2014-04-04 11:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 17:12 [U-Boot] [PATCH 1/2] arm: mxs: Adjust the load address of U-Boot and SPL for HAB Marek Vasut
2014-04-03 17:12 ` [U-Boot] [PATCH 2/2] arm: mxs: Add support for generating signed BootStream Marek Vasut
2014-04-04 9:52 ` Stefano Babic
2014-04-04 11:54 ` Marek Vasut [this message]
2014-04-04 9:39 ` [U-Boot] [PATCH 1/2] arm: mxs: Adjust the load address of U-Boot and SPL for HAB Stefano Babic
-- strict thread matches above, loose matches on Subject: below --
2014-03-05 19:01 Marek Vasut
2014-03-05 19:01 ` [U-Boot] [PATCH 2/2] arm: mxs: Add support for generating signed BootStream Marek Vasut
2014-04-01 8:16 ` Stefano Babic
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=201404041354.17241.marex@denx.de \
--to=marex@denx.de \
--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.