From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [REGRESSION] commit e04916a "SECURE_BOOT : enable esbc_validate..." breaks MX6
Date: Thu, 2 Apr 2015 16:18:37 -0400 [thread overview]
Message-ID: <20150402201837.GO9524@bill-the-cat> (raw)
In-Reply-To: <551D6BFF.2040708@freescale.com>
On Thu, Apr 02, 2015 at 10:19:11AM -0600, Ulises Cardenas wrote:
> Hi,
> The aforementioned commit e04916a721a2069fc770412c57974d02e153ad18, causes MX6 boards to break
>
> Configuring CONFIG_SECURE_BOOT makes the u-boot build fail for any MX6 board. This was reproduced in mx6dl, mx6q and mx6sx. The log for the mx6q build is:
>
> ==============
> In file included from /home/ulises/Security/u-boot-imx/include/fsl_validate.h:11:0,
> from /home/ulises/Security/u-boot-imx/board/freescale/common/fsl_validate.c:8:
> /home/ulises/Security/u-boot-imx/include/fsl_sec_mon.h:27:2: error: #error Neither CONFIG_SYS_FSL_SEC_MON_LE nor CONFIG_SYS_FSL_SEC_MON_BE defined
> #error Neither CONFIG_SYS_FSL_SEC_MON_LE nor CONFIG_SYS_FSL_SEC_MON_BE defined
> ^
> In file included from /home/ulises/Security/u-boot-imx/board/freescale/common/fsl_validate.c:10:0:
> /home/ulises/Security/u-boot-imx/include/fsl_sfp.h:29:2: error: #error Neither CONFIG_SYS_FSL_SFP_LE nor CONFIG_SYS_FSL_SFP_BE is defined
> #error Neither CONFIG_SYS_FSL_SFP_LE nor CONFIG_SYS_FSL_SFP_BE is defined
> ^
> /home/ulises/Security/u-boot-imx/board/freescale/common/fsl_validate.c:19:36: fatal error: asm/arch/immap_ls102xa.h: No such file or directory
> #include <asm/arch/immap_ls102xa.h>
> ^
> compilation terminated.
> AS arch/arm/lib/vectors.o
> /home/ulises/Security/u-boot-imx/scripts/Makefile.build:276: recipe for target 'board/freescale/common/fsl_validate.o' failed
> make[2]: *** [board/freescale/common/fsl_validate.o] Error 1
> /home/ulises/Security/u-boot-imx/Makefile:1112: recipe for target 'board/freescale/common' failed
> make[1]: *** [board/freescale/common] Error 2
> make[1]: *** Waiting for unfinished jobs....
> ==========
>
> If I revert the commit, the build successfully builds and the I am able to boot the boards on secure mode.
Well, lets start with seeing which one of those needs to be set as well
for secure boot to continue to work. From there we can find a good spot
to whack that default in.
--
>
> Thanks,
> Ulises
>
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20150402/9f06c38f/attachment.sig>
next prev parent reply other threads:[~2015-04-02 20:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.970.1424900134.22659.u-boot@lists.denx.de>
2015-04-02 16:19 ` [U-Boot] [REGRESSION] commit e04916a "SECURE_BOOT : enable esbc_validate..." breaks MX6 Ulises Cardenas
2015-04-02 20:18 ` Tom Rini [this message]
2015-04-20 19:42 ` Ulises Cardenas
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=20150402201837.GO9524@bill-the-cat \
--to=trini@konsulko.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