From: Andrew F. Davis <afd@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4 00/10] Allow secure boot on AM33xx devices
Date: Tue, 30 Aug 2016 14:06:19 -0500 [thread overview]
Message-ID: <20160830190629.13956-1-afd@ti.com> (raw)
Hello all,
I've recently been tasked with enabling authenticated boot for AM33xx based
devices. This work is similar to what has already been done for the AM43xx
and AM57xx SoCs and leverages much of the infrastructure from them.
The big difference here is the size of SRAM available on AM33xx being much
less than on the other SoCs, when performing a secure boot this limits
the maximum size of the SPL to just ~41k, the SPL currently generated for
AM33xx SoCs is ~70k.
I have added a defconfig for booting from mmc, but it is RFC for now as
the generated SPL is still much too large to fit into SRAM on HS devices.
If you would like to help out you can build this defconfig and it will
report by how much we have overflowed SRAM, any help reducing this would
be greatly appreciated.
Thanks,
Andrew
Changes from v3:
- Drop SPL_*_BOOT patches as these do not get used by almost anyone
so we can just work to remove them completly.
- Fixed defaults for ISW_ENTRY_ADDR.
Changes from v2:
- Dropping the SPL_*_SUPPORT patches as Simon is already way ahead
of me on this front[0].
- Minor re-organization of the patches, dropped a couple that I didn't
feel were important enough to continue working right now.
Changes from v1:
- I've moved the cleanup patches to the end of the series and now
consider them RFCs. I also do not move any Kconfig options over
as this can be performed automatically but will need to be done
by someone who understands the build system better than me.
- Separate additional AM33xx SOC based boards out from the SoC
definition in patch #1.
[0] https://www.mail-archive.com/u-boot at lists.denx.de/msg222736.html
Andrew F. Davis (10):
Kconfig: Separate AM33XX SOC config from target board config
am33xx: config.mk: Add support for additional secure boot image types
doc: Update info on using AM33xx secure devices from TI
am33xx: config.mk: Fix option used to enable SPI SPL image type
board: am33xx-hs: Allow post-processing of FIT image on AM33xx
ti: omap-common: Allow AM33xx devices to be built securely
am335x: configs: Use ISW_ENTRY_ADDR to set SPL_TEXT_BASE
config: Remove usage of CONFIG_STORAGE_EMMC
ti_armv7_common: Disable Falcon Mode on HS devices
defconfig: Add a config for AM335x High Security EVM with SD Boot
support
arch/arm/Kconfig | 98 +++-------------------
arch/arm/cpu/armv7/am33xx/Kconfig | 89 +++++++++++++++++++-
arch/arm/cpu/armv7/am33xx/config.mk | 24 +++++-
arch/arm/cpu/armv7/omap-common/Kconfig | 2 +-
board/ti/am335x/board.c | 8 ++
configs/am335x_baltos_defconfig | 1 +
configs/am335x_boneblack_defconfig | 1 +
configs/am335x_boneblack_vboot_defconfig | 1 +
configs/am335x_evm_defconfig | 1 +
configs/am335x_evm_nor_defconfig | 1 +
configs/am335x_evm_norboot_defconfig | 1 +
configs/am335x_evm_spiboot_defconfig | 1 +
configs/am335x_evm_usbspl_defconfig | 1 +
...x_evm_defconfig => am335x_hs_evm_mmc_defconfig} | 8 +-
configs/am335x_igep0033_defconfig | 1 +
configs/am335x_shc_defconfig | 1 +
configs/am335x_shc_ict_defconfig | 1 +
configs/am335x_shc_netboot_defconfig | 1 +
configs/am335x_shc_prompt_defconfig | 1 +
configs/am335x_shc_sdboot_defconfig | 1 +
configs/am335x_shc_sdboot_prompt_defconfig | 1 +
configs/am335x_sl50_defconfig | 1 +
configs/birdland_bav335a_defconfig | 1 +
configs/birdland_bav335b_defconfig | 1 +
configs/cm_t335_defconfig | 1 +
configs/pcm051_rev1_defconfig | 1 +
configs/pcm051_rev3_defconfig | 1 +
configs/pengwyn_defconfig | 1 +
configs/pepper_defconfig | 1 +
doc/README.ti-secure | 32 +++++++
include/configs/am335x_evm.h | 2 -
include/configs/am335x_shc.h | 2 -
include/configs/am335x_sl50.h | 2 -
include/configs/bav335x.h | 2 -
include/configs/ti_am335x_common.h | 3 +-
include/configs/ti_armv7_common.h | 15 ++--
36 files changed, 201 insertions(+), 109 deletions(-)
copy configs/{am335x_evm_defconfig => am335x_hs_evm_mmc_defconfig} (86%)
--
2.9.3
next reply other threads:[~2016-08-30 19:06 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-30 19:06 Andrew F. Davis [this message]
2016-08-30 19:06 ` [U-Boot] [PATCH v4 01/10] Kconfig: Separate AM33XX SOC config from target board config Andrew F. Davis
2016-08-31 3:26 ` Lokesh Vutla
2016-08-31 16:06 ` Hannes Schmelzer
2016-08-31 16:16 ` Andrew F. Davis
2016-08-31 17:45 ` Hannes Schmelzer
2016-09-02 14:53 ` Tom Rini
2016-10-03 13:38 ` [U-Boot] [U-Boot, v4, " Tom Rini
2016-08-30 19:06 ` [U-Boot] [PATCH v4 02/10] am33xx: config.mk: Add support for additional secure boot image types Andrew F. Davis
2016-08-31 3:26 ` Lokesh Vutla
2016-09-02 14:53 ` Tom Rini
2016-10-03 13:38 ` [U-Boot] [U-Boot, v4, " Tom Rini
2016-08-30 19:06 ` [U-Boot] [PATCH v4 03/10] doc: Update info on using AM33xx secure devices from TI Andrew F. Davis
2016-08-31 3:26 ` Lokesh Vutla
2016-09-02 14:53 ` Tom Rini
2016-10-03 13:38 ` [U-Boot] [U-Boot, v4, " Tom Rini
2016-08-30 19:06 ` [U-Boot] [PATCH v4 04/10] am33xx: config.mk: Fix option used to enable SPI SPL image type Andrew F. Davis
2016-08-31 3:27 ` Lokesh Vutla
2016-09-02 14:53 ` Tom Rini
2016-10-03 13:38 ` [U-Boot] [U-Boot, v4, " Tom Rini
2016-08-30 19:06 ` [U-Boot] [PATCH v4 05/10] board: am33xx-hs: Allow post-processing of FIT image on AM33xx Andrew F. Davis
2016-08-31 3:28 ` Lokesh Vutla
2016-09-02 14:53 ` Tom Rini
2016-10-03 13:38 ` [U-Boot] [U-Boot, v4, " Tom Rini
2016-08-30 19:06 ` [U-Boot] [PATCH v4 06/10] ti: omap-common: Allow AM33xx devices to be built securely Andrew F. Davis
2016-08-31 3:28 ` Lokesh Vutla
2016-09-02 14:53 ` Tom Rini
2016-10-03 13:38 ` [U-Boot] [U-Boot, v4, " Tom Rini
2016-08-30 19:06 ` [U-Boot] [PATCH v4 07/10] am335x: configs: Use ISW_ENTRY_ADDR to set SPL_TEXT_BASE Andrew F. Davis
2016-08-31 3:28 ` Lokesh Vutla
2016-09-02 14:53 ` Tom Rini
2016-08-30 19:06 ` [U-Boot] [PATCH v4 08/10] config: Remove usage of CONFIG_STORAGE_EMMC Andrew F. Davis
2016-08-31 3:28 ` Lokesh Vutla
2016-09-02 14:54 ` Tom Rini
2016-10-03 13:38 ` [U-Boot] [U-Boot, v4, " Tom Rini
2016-08-30 19:06 ` [U-Boot] [PATCH v4 09/10] ti_armv7_common: Disable Falcon Mode on HS devices Andrew F. Davis
2016-08-31 3:29 ` Lokesh Vutla
2016-09-02 14:54 ` Tom Rini
2016-10-03 13:38 ` [U-Boot] [U-Boot, v4, " Tom Rini
2016-08-30 19:06 ` [U-Boot] [PATCH v4 10/10] defconfig: Add a config for AM335x High Security EVM with SD Boot support Andrew F. Davis
2016-08-31 3:30 ` Lokesh Vutla
2016-09-02 14:54 ` Tom Rini
2016-09-02 14:57 ` Andrew F. Davis
2016-09-02 14:58 ` Tom Rini
2016-09-07 18:04 ` Andrew F. Davis
2016-10-03 13:39 ` [U-Boot] [U-Boot, v4, " Tom Rini
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=20160830190629.13956-1-afd@ti.com \
--to=afd@ti.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