Add a new defconfig file for the K2E High Security EVM.
This defconfig is the same as for the non-secure part, except for:
CONFIG_TI_SECURE_DEVICE option set to 'y'
CONFIG_FIT option set to 'y'
CONFIG_FIT_IMAGE_POST_PROCESS option set to 'y'
Enables the platform-specific
Add a section describing the secure boot image used on
keystone secure devices.
This patch applies on top of the patch
doc: Update info on using AM33xx secure devices from TI
submitted by Andrew Davis
Signed-off-by: Madan Srinivas
Reviewed-by: Tom Rini
---
Changes in v3: None
Changes in v2:
Adds an additional image type needed for supporting secure keystone
devices. The build generates u-boot_HS_MLO which can be used to boot
from all media on secure keystone devices.
Signed-off-by: Madan Srinivas
Cc: Andrew F. Davis
---
Changes in v3:
- Corrects commit message in patch 5/7 in th
Like the OMAP54xx, AM43xx & AM33xx family SoCs, the keystone family
of SoCs also have high security enabled models. Allow K2E devices to
be built with HS Device Type Support.
This patch applies on top of the patch
ti: omap-common: Allow AM33xx devices to be built securely
submitted by Andrew Davi
As K2 can directly boot u-boot, add u-boot_HS_MLO as the
secure image while booting secure K2 devicesr, for all
boot modes other than SPI flash.
Signed-off-by: Madan Srinivas
Reviewed-by: Tom Rini
---
Changes in v3: None
Changes in v2:
- Adds a new name for the signed output image in config_s
This commit implements the board_fit_image_post_process() function for
the keystone architecture. Unlike OMAP class devices, security
functions in keystone are not handled in the ROM.
The interface to the secure functions is TI proprietary and depending
on the keystone platform, the security funct
The function board_fit_image_post_process is defined only when the config
CONFIG_FIT_IMAGE_POST_PROCESS is enabled. For secure systems that do not
use SPL but use FIT kernel images, only CONFIG_FIT_IMAGE_POST_PROCESS will
be defined, which will result in an implicit declaration of function
'board_
This series adds support for secure keystone family of devices, more
specifically for K2E (Edison).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 ROM on keystone2 devices does not
On 9/6/2016 9:34 AM, Tom Rini wrote:
On Thu, Sep 01, 2016 at 01:04:37AM -0400, Madan Srinivas wrote:
From: Vitaly Andrianov
This commit implements the board_fit_image_post_process() function for
the keystone architecture. Unlike OMAP class devices, security
functions in keystone are not handl
On 9/2/2016 12:25 AM, Lokesh Vutla wrote:
On Thursday 01 September 2016 10:34 AM, Madan Srinivas wrote:
This series adds support for secure keystone family of devices, more
specifically for K2E (Edison).This work is similar to what has already
been done for the AM43xx and AM57xx SoCs and lever
From: Madan Srinivas
An issue in the TI secure image generation tool causes the ROM to
load the SPL at a different load address than what is specified by
CONFIG_ISW_ENTRY_ADDR while doing a peripheral boot on HS devices.
This causes the SPL to fail on secure devices during peripheral
boot.
The
Adding FIT support to the SPL and u-boot for AM437x HS devices.
Signed-off-by: Madan Srinivas
---
configs/am437x_hs_evm_defconfig | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/configs/am437x_hs_evm_defconfig b/configs/am437x_hs_evm_defconfig
index 3cd39eb..fac06a7 100644
12 matches
Mail list logo
