Support for boot image creation for TI secure devices

Adds doc/README.ti-secure file to explain in generic terms how boot images need to be created for secure devices from Texas Instruments.

Specific details for creating secure boot images for the AM43xx, DRA7xx and AM57xx secure devices from Texas Instruments are also provided in the README file.

Secure devices require a security development package (SECDEV) package that can be downloaded from:

http://www.ti.com/mysecuresoftware

Login is required and access is granted under appropriate NDA and export control restrictions.

Adds doc/README.ti-secure file to explain in generic terms how boot images need to be created for secure devices from Texas Instruments.

Specific details for creating secure boot images for the AM43xx, DRA7xx and AM57xx secure devices from Texas Instruments are also provided in the README file.

Secure devices require a security development package (SECDEV) package that can be downloaded from:

http://www.ti.com/mysecuresoftware

Login is required and access is granted under appropriate NDA and export control restrictions.

Signed-off-by Madan Srinivas <[email protected]>

Signed-off-by Daniel Allred <[email protected]>

---
 doc/README.ti-secure | 92 ++++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 92 insertions(+)
 create mode 100644 doc/README.ti-secure

doc/README.ti-secure new file +71 -0

new file mode 100644
index 0000000..fa818ae
@@ -0,0 +1,92 @@
+README on how boot images are created for secure TI devices
+
+CONFIG_TI_SECURE_DEVICE:
+Secure TI devices require a boot image that is authenticated by ROM
+code to function. Without this, even JTAG remains locked and the
+device is essentially useless. In order to create a valid boot image for
+a secure device from TI, the initial public software image must be signed
+and combined with various headers, certificates, and other binary images.
+
+Information on the details on the complete boot image format can be obtained
+from Texas Instruments. The tools used to generate boot images for secure
+devices are part of a secure development package (SECDEV) that can be
+downloaded from:
+
+	http://www.ti.com/mysecuresoftware (login required)
+
+The secure development package is access controlled due to NDA and export
+control restrictions. Access must be requested and granted by TI before the
+package is viewable and downloadable. Contact TI, either online or by way
+of a local TI representative, to request access.
+
+When CONFIG_TI_SECURE_DEVICE is set, the U-Boot SPL build process requires
+the presence and use of these tools in order to create a viable boot image.
+The build process will look for the environment variable TI_SECURE_DEV_PKG,
+which should be the path of the installed SECDEV package. If the
+TI_SECURE_DEV_PKG variable is not defined or if it is defined but doesn't
+point to a valid SECDEV package, a warning is issued during the build to
+indicate that a final secure bootable image was not created.
+
+Within the SECDEV package exists an image creation script:
+
+${TI_SECURE_DEV_PKG}/scripts/create-boot-image.sh
+
+This is called as part of the SPL/u-boot build process. As the secure boot
+image formats and requirements differ between secure SOC from TI, the
+purpose of this script is to abstract these details as much as possible.
+
+The script is basically the only required interface to the TI SECDEV package
+for secure TI devices.
+
+Invoking the script for AM43xx Secure Devices
+=============================================
+
+create-boot-image.sh <IMAGE_FLAG> <INPUT_FILE> <OUTPUT_FILE> <SPL_LOAD_ADDR>
+
+<IMAGE_FLAG> is a value that specifies the type of the image to generate OR
+the action the image generation tool will take. Valid values are:
+	SPI_X-LOADER - Generates an image for SPI flash (byte swapped)
+	XIP_X-LOADER - Generates a single stage u-boot for NOR/QSPI XiP
+	ISSW - Generates an image for all other boot modes
+
+<INPUT_FILE> is the full path and filename of the public world boot loader
+binary file (depending on the boot media, this is usually either
+u-boot-spl.bin or u-boot.bin).
+
+<OUTPUT_FILE> is the full path and filename of the final secure image. The
+output binary images should be used in place of the standard non-secure
+binary images (see the platform-specific user's guides and releases notes
+for how the non-secure images are typically used)
+	u-boot-spl_HS_SPI_X-LOADER - byte swapped boot image for SPI flash
+	u-boot_HS_XIP_X-LOADER - boot image for NOR or QSPI flash
+	u-boot-spl_HS_ISSW - boot image for all other boot media
+
+<SPL_LOAD_ADDR> is the address at which SOC ROM should load the <INPUT_FILE>
+
+Invoking the script for DRA7xx/AM57xx Secure Devices
+====================================================
+
+create-boot-image.sh <IMAGE_TYPE> <INPUT_FILE> <OUTPUT_FILE>
+
+<IMAGE_TYPE> is a value that specifies the type of the image to generate OR

doc/README.ti-secure new file +6 -0

+		copied to a file named MLO, which is the name that
+		the device ROM bootloader requires for loading from
+		the FAT partition of an SD card (same as on
+		non-secure devices)
+	u-boot-spl_HS_X-LOADER - boot image for all other flash memories
+		including QSPI and NOR flash

Signature · 6 lines

1.9.1

_______________________________________________
U-Boot mailing list
U-Boot at lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Adds doc/README.ti-secure file to explain in generic terms how boot images need to be created for secure devices from Texas Instruments.

Specific details for creating secure boot images for the AM43xx, DRA7xx and AM57xx secure devices from Texas Instruments are also provided in the README file.

Secure devices require a security development package (SECDEV) package that can be downloaded from:

http://www.ti.com/mysecuresoftware

Login is required and access is granted under appropriate NDA and export control restrictions.

Signed-off-by Madan Srinivas <[email protected]>

Signed-off-by Daniel Allred <[email protected]>

From: Madan Srinivas <[email protected]>

Adds a new Kconfig file for AM33xx class devices. We need a common place to define CONFIG parameters for these SOCs, especially for adding support for secure devices.

a) Adds a definition for ISW_ENTRY_ADDR. This is the address to which the ROM branches when the SOC ROM hands off execution to the boot loader. CONFIG_SYS_TEXT_BASE and CONFIG_SPL_TEXT_BASE are set to this value for AM43xx devices.

b) Adds CONFIG_PUB_ROM_DATA_SIZE which is used to calculate CONFIG_SPL_MAX_SIZE. This value indicates the amount of memory needed by the ROM to store data during the boot process.

Currently, these CONFIG options are used only by AM43xx, but in future other AM33xx class SOCs will also use them.

From: Madan Srinivas <[email protected]>

Adds a new Kconfig file for AM33xx class devices. We need a common place to define CONFIG parameters for these SOCs, especially for adding support for secure devices.

a) Adds a definition for ISW_ENTRY_ADDR. This is the address to which the ROM branches when the SOC ROM hands off execution to the boot loader. CONFIG_SYS_TEXT_BASE and CONFIG_SPL_TEXT_BASE are set to this value for AM43xx devices.

b) Adds CONFIG_PUB_ROM_DATA_SIZE which is used to calculate CONFIG_SPL_MAX_SIZE. This value indicates the amount of memory needed by the ROM to store data during the boot process.

Currently, these CONFIG options are used only by AM43xx, but in future other AM33xx class SOCs will also use them.

Signed-off-by Madan Srinivas <[email protected]>

Signed-off-by Daniel Allred <[email protected]>

From: Madan Srinivas <[email protected]>

Adds a new Kconfig file for AM33xx class devices. We need a common place to define CONFIG parameters for these SOCs, especially for adding support for secure devices.

a) Adds a definition for ISW_ENTRY_ADDR. This is the address to which the ROM branches when the SOC ROM hands off execution to the boot loader. CONFIG_SYS_TEXT_BASE and CONFIG_SPL_TEXT_BASE are set to this value for AM43xx devices.

b) Adds CONFIG_PUB_ROM_DATA_SIZE which is used to calculate CONFIG_SPL_MAX_SIZE. This value indicates the amount of memory needed by the ROM to store data during the boot process.

Currently, these CONFIG options are used only by AM43xx, but in future other AM33xx class SOCs will also use them.

Signed-off-by Madan Srinivas <[email protected]>

Signed-off-by Daniel Allred <[email protected]>

From: Madan Srinivas <[email protected]>

Adding support for AM43xx secure devices require the addition of some SOC specific config options like the amount of memory used by public ROM and the address of the entry point of u-boot or SPL, as seen by the ROM code, for the image to be built correctly.

This mandates the addition of am AM43xx CONFIG option and the ARM Kconfig file has been modified to source this SOC Kconfig file. Moving the TARGET_AM43XX_EVM config option to the SOC KConfig and out of the arch/arm/Kconfig.

Updating defconfigs to add the CONFIG_AM43XX=y statement and removing the #define CONFIG_AM43XX from the header file.

From: Madan Srinivas <[email protected]>

Adding support for AM43xx secure devices require the addition of some SOC specific config options like the amount of memory used by public ROM and the address of the entry point of u-boot or SPL, as seen by the ROM code, for the image to be built correctly.

This mandates the addition of am AM43xx CONFIG option and the ARM Kconfig file has been modified to source this SOC Kconfig file. Moving the TARGET_AM43XX_EVM config option to the SOC KConfig and out of the arch/arm/Kconfig.

Updating defconfigs to add the CONFIG_AM43XX=y statement and removing the #define CONFIG_AM43XX from the header file.

Signed-off-by Madan Srinivas <[email protected]>

Signed-off-by Daniel Allred <[email protected]>

---
 arch/arm/Kconfig                          | 19 +++++++++++++------
 arch/arm/cpu/armv7/am33xx/Kconfig         | 13 +++++++++++++
 configs/am43xx_evm_defconfig              |  1 +
 configs/am43xx_evm_ethboot_defconfig      |  1 +
 configs/am43xx_evm_qspiboot_defconfig     |  1 +
 configs/am43xx_evm_usbhost_boot_defconfig |  1 +
 include/configs/am43xx_evm.h              |  2 --
 7 files changed, 30 insertions(+), 8 deletions(-)

arch/arm/Kconfig +13 -6

index f18dbe6..088d6e0 100644
@@ -381,12 +381,6 @@ config TARGET_AM335X_SL50
 	select DM
 	select DM_SERIAL
 
-config TARGET_AM43XX_EVM
-	bool "Support am43xx_evm"
-	select CPU_V7
-	select SUPPORT_SPL
-	select TI_I2C_BOARD_DETECT
-
 config TARGET_BAV335X
 	bool "Support bav335x"
 	select CPU_V7

@@ -507,6 +501,17 @@ config OMAP54XX
 	select CPU_V7
 	select SUPPORT_SPL
 
+config AM43XX
+	bool "AM43XX SoC"
+	select CPU_V7
+	select SUPPORT_SPL
+	help
+	  Support for AM43xx SOC from Texas Instruments.
+	  The AM43xx high performance SOC features a Cortex-A9
+	  ARM core, a quad core PRU-ICSS for industrial Ethernet
+	  protocols, dual camera support, optional 3D graphics
+	  and an optional customer programmable secure boot.
+
 config RMOBILE
 	bool "Renesas ARM SoCs"
 	select CPU_V7

@@ -776,6 +781,8 @@ source "arch/arm/cpu/armv7/omap4/Kconfig"
 
 source "arch/arm/cpu/armv7/omap5/Kconfig"
 
+source "arch/arm/cpu/armv7/am33xx/Kconfig"
+
 source "arch/arm/mach-orion5x/Kconfig"
 
 source "arch/arm/cpu/armv7/rmobile/Kconfig"

arch/arm/cpu/armv7/am33xx/Kconfig +0 -0

index 39759cd..68bcc64 100644

arch/arm/cpu/armv7/am33xx/Kconfig +9 -0

+	help
+	  This option specifies support for the AM43xx
+	  GP and HS EVM development platforms.The AM437x
+	  GP EVM is a standalone test, development, and
+	  evaluation module system that enables developers
+	  to write software and develop hardware around
+	  an AM43xx processor subsystem.
+
 config ISW_ENTRY_ADDR
 	hex "Address in memory or XIP flash of bootloader entry point"
 	help

@@ -25,3 +37,4 @@ config PUB_ROM_DATA_SIZE
 	  image, this area is no longer used, and can be reclaimed
 	  for run time use by the boot image.
 	default 0x8400
+endif

configs/am43xx_evm_defconfig +1 -0

index cc83006..4b0a188 100644
@@ -1,4 +1,5 @@
 CONFIG_ARM=y
+CONFIG_AM43XX=y
 CONFIG_TARGET_AM43XX_EVM=y
 CONFIG_SPL=y
 CONFIG_SYS_EXTRA_OPTIONS="SERIAL1,CONS_INDEX=1,NAND"

configs/am43xx_evm_ethboot_defconfig +1 -0

index a720c14..20001ca 100644
@@ -1,4 +1,5 @@
 CONFIG_ARM=y
+CONFIG_AM43XX=y
 CONFIG_TARGET_AM43XX_EVM=y
 CONFIG_SPL=y
 CONFIG_SYS_EXTRA_OPTIONS="SERIAL1,CONS_INDEX=1,NAND,SPL_ETH_SUPPORT"

configs/am43xx_evm_qspiboot_defconfig +1 -0

index 6db389b..2170a68 100644
@@ -1,4 +1,5 @@
 CONFIG_ARM=y
+CONFIG_AM43XX=y
 CONFIG_TARGET_AM43XX_EVM=y
 CONFIG_SYS_EXTRA_OPTIONS="SERIAL1,CONS_INDEX=1,QSPI,QSPI_BOOT"
 # CONFIG_CMD_IMLS is not set

configs/am43xx_evm_usbhost_boot_defconfig +1 -0

index cbaf5a5..14343a9 100644
@@ -1,4 +1,5 @@
 CONFIG_ARM=y
+CONFIG_AM43XX=y
 CONFIG_TARGET_AM43XX_EVM=y
 CONFIG_SPL=y
 CONFIG_SYS_EXTRA_OPTIONS="SERIAL1,CONS_INDEX=1,NAND,SPL_USB_HOST_SUPPORT"

include/configs/am43xx_evm.h +0 -2

index fd3f6a7..b98f7a1 100644
@@ -9,8 +9,6 @@
 #ifndef __CONFIG_AM43XX_EVM_H
 #define __CONFIG_AM43XX_EVM_H
 
-#define CONFIG_AM43XX
-
 #define CONFIG_CMD_FAT
 
 #define CONFIG_BOARD_LATE_INIT

Quoted 71 lines · Daniel Allred

From: Madan Srinivas <[email protected]>

Adding support for AM43xx secure devices require the addition of some SOC specific config options like the amount of memory used by public ROM and the address of the entry point of u-boot or SPL, as seen by the ROM code, for the image to be built correctly.

This mandates the addition of am AM43xx CONFIG option and the ARM Kconfig file has been modified to source this SOC Kconfig file. Moving the TARGET_AM43XX_EVM config option to the SOC KConfig and out of the arch/arm/Kconfig.

Updating defconfigs to add the CONFIG_AM43XX=y statement and removing the #define CONFIG_AM43XX from the header file.

Signed-off-by Madan Srinivas <[email protected]>

Signed-off-by Daniel Allred <[email protected]>

---
 arch/arm/Kconfig                          | 19 +++++++++++++------
 arch/arm/cpu/armv7/am33xx/Kconfig         | 13 +++++++++++++
 configs/am43xx_evm_defconfig              |  1 +
 configs/am43xx_evm_ethboot_defconfig      |  1 +
 configs/am43xx_evm_qspiboot_defconfig     |  1 +
 configs/am43xx_evm_usbhost_boot_defconfig |  1 +
 include/configs/am43xx_evm.h              |  2 --
 7 files changed, 30 insertions(+), 8 deletions(-)

arch/arm/Kconfig +13 -6

index f18dbe6..088d6e0 100644
@@ -381,12 +381,6 @@ config TARGET_AM335X_SL50
 	select DM
 	select DM_SERIAL
 
-config TARGET_AM43XX_EVM
-	bool "Support am43xx_evm"
-	select CPU_V7
-	select SUPPORT_SPL
-	select TI_I2C_BOARD_DETECT
-
 config TARGET_BAV335X
 	bool "Support bav335x"
 	select CPU_V7

@@ -507,6 +501,17 @@ config OMAP54XX
 	select CPU_V7
 	select SUPPORT_SPL
 
+config AM43XX
+	bool "AM43XX SoC"
+	select CPU_V7
+	select SUPPORT_SPL
+	help
+	  Support for AM43xx SOC from Texas Instruments.
+	  The AM43xx high performance SOC features a Cortex-A9
+	  ARM core, a quad core PRU-ICSS for industrial Ethernet
+	  protocols, dual camera support, optional 3D graphics
+	  and an optional customer programmable secure boot.
+
 config RMOBILE
 	bool "Renesas ARM SoCs"
 	select CPU_V7

@@ -776,6 +781,8 @@ source "arch/arm/cpu/armv7/omap4/Kconfig"
 
 source "arch/arm/cpu/armv7/omap5/Kconfig"
 
+source "arch/arm/cpu/armv7/am33xx/Kconfig"
+
 source "arch/arm/mach-orion5x/Kconfig"
 

arch/arm/cpu/armv7/am33xx/Kconfig line 4

Quoted 10 lines

arch/arm/Kconfig +0 -0

 source "arch/arm/cpu/armv7/rmobile/Kconfig"

arch/arm/cpu/armv7/am33xx/Kconfig +4 -0

index 39759cd..68bcc64 100644
@@ -1,3 +1,15 @@
+if AM43XX
+config TARGET_AM43XX_EVM
+	bool "Support am43xx_evm"
+	select CREATE_BOARD_SYMLINK

This should be TI_I2C_BOARD_DETECT or else you will get a build error.

Thanks and regards,
Lokesh

Quoted 62 lines

arch/arm/cpu/armv7/am33xx/Kconfig +9 -0

+	help
+	  This option specifies support for the AM43xx
+	  GP and HS EVM development platforms.The AM437x
+	  GP EVM is a standalone test, development, and
+	  evaluation module system that enables developers
+	  to write software and develop hardware around
+	  an AM43xx processor subsystem.
+
 config ISW_ENTRY_ADDR
 	hex "Address in memory or XIP flash of bootloader entry point"
 	help

@@ -25,3 +37,4 @@ config PUB_ROM_DATA_SIZE
 	  image, this area is no longer used, and can be reclaimed
 	  for run time use by the boot image.
 	default 0x8400
+endif

configs/am43xx_evm_defconfig +1 -0

index cc83006..4b0a188 100644
@@ -1,4 +1,5 @@
 CONFIG_ARM=y
+CONFIG_AM43XX=y
 CONFIG_TARGET_AM43XX_EVM=y
 CONFIG_SPL=y
 CONFIG_SYS_EXTRA_OPTIONS="SERIAL1,CONS_INDEX=1,NAND"

configs/am43xx_evm_ethboot_defconfig +1 -0

index a720c14..20001ca 100644
@@ -1,4 +1,5 @@
 CONFIG_ARM=y
+CONFIG_AM43XX=y
 CONFIG_TARGET_AM43XX_EVM=y
 CONFIG_SPL=y
 CONFIG_SYS_EXTRA_OPTIONS="SERIAL1,CONS_INDEX=1,NAND,SPL_ETH_SUPPORT"

configs/am43xx_evm_qspiboot_defconfig +1 -0

index 6db389b..2170a68 100644
@@ -1,4 +1,5 @@
 CONFIG_ARM=y
+CONFIG_AM43XX=y
 CONFIG_TARGET_AM43XX_EVM=y
 CONFIG_SYS_EXTRA_OPTIONS="SERIAL1,CONS_INDEX=1,QSPI,QSPI_BOOT"
 # CONFIG_CMD_IMLS is not set

configs/am43xx_evm_usbhost_boot_defconfig +1 -0

index cbaf5a5..14343a9 100644
@@ -1,4 +1,5 @@
 CONFIG_ARM=y
+CONFIG_AM43XX=y
 CONFIG_TARGET_AM43XX_EVM=y
 CONFIG_SPL=y
 CONFIG_SYS_EXTRA_OPTIONS="SERIAL1,CONS_INDEX=1,NAND,SPL_USB_HOST_SUPPORT"

include/configs/am43xx_evm.h +0 -0

index fd3f6a7..b98f7a1 100644

include/configs/am43xx_evm.h line 14

Quoted 8 lines

include/configs/am43xx_evm.h +0 -2

@@ -9,8 +9,6 @@
 #ifndef __CONFIG_AM43XX_EVM_H
 #define __CONFIG_AM43XX_EVM_H
 
-#define CONFIG_AM43XX
-
 #define CONFIG_CMD_FAT
 
 #define CONFIG_BOARD_LATE_INIT

_______________________________________________
U-Boot mailing list
U-Boot at lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Quoted 72 lines · Lokesh Vutla

Quoted 71 lines · Daniel Allred

From: Madan Srinivas <[email protected]>

Adding support for AM43xx secure devices require the addition of some SOC specific config options like the amount of memory used by public ROM and the address of the entry point of u-boot or SPL, as seen by the ROM code, for the image to be built correctly.

This mandates the addition of am AM43xx CONFIG option and the ARM Kconfig file has been modified to source this SOC Kconfig file. Moving the TARGET_AM43XX_EVM config option to the SOC KConfig and out of the arch/arm/Kconfig.

Updating defconfigs to add the CONFIG_AM43XX=y statement and removing the #define CONFIG_AM43XX from the header file.

Signed-off-by Madan Srinivas <[email protected]>

Signed-off-by Daniel Allred <[email protected]>

---
 arch/arm/Kconfig                          | 19 +++++++++++++------
 arch/arm/cpu/armv7/am33xx/Kconfig         | 13 +++++++++++++
 configs/am43xx_evm_defconfig              |  1 +
 configs/am43xx_evm_ethboot_defconfig      |  1 +
 configs/am43xx_evm_qspiboot_defconfig     |  1 +
 configs/am43xx_evm_usbhost_boot_defconfig |  1 +
 include/configs/am43xx_evm.h              |  2 --
 7 files changed, 30 insertions(+), 8 deletions(-)

arch/arm/Kconfig +13 -6

index f18dbe6..088d6e0 100644
@@ -381,12 +381,6 @@ config TARGET_AM335X_SL50
 	select DM
 	select DM_SERIAL
 
-config TARGET_AM43XX_EVM
-	bool "Support am43xx_evm"
-	select CPU_V7
-	select SUPPORT_SPL
-	select TI_I2C_BOARD_DETECT
-
 config TARGET_BAV335X
 	bool "Support bav335x"
 	select CPU_V7

@@ -507,6 +501,17 @@ config OMAP54XX
 	select CPU_V7
 	select SUPPORT_SPL
 
+config AM43XX
+	bool "AM43XX SoC"
+	select CPU_V7
+	select SUPPORT_SPL
+	help
+	  Support for AM43xx SOC from Texas Instruments.
+	  The AM43xx high performance SOC features a Cortex-A9
+	  ARM core, a quad core PRU-ICSS for industrial Ethernet
+	  protocols, dual camera support, optional 3D graphics
+	  and an optional customer programmable secure boot.
+
 config RMOBILE
 	bool "Renesas ARM SoCs"
 	select CPU_V7

@@ -776,6 +781,8 @@ source "arch/arm/cpu/armv7/omap4/Kconfig"
 
 source "arch/arm/cpu/armv7/omap5/Kconfig"
 
+source "arch/arm/cpu/armv7/am33xx/Kconfig"
+
 source "arch/arm/mach-orion5x/Kconfig"
 

Quoted 12 lines

arch/arm/cpu/armv7/am33xx/Kconfig line 4

Quoted 10 lines

arch/arm/Kconfig +0 -0

 source "arch/arm/cpu/armv7/rmobile/Kconfig"

arch/arm/cpu/armv7/am33xx/Kconfig +4 -0

index 39759cd..68bcc64 100644
@@ -1,3 +1,15 @@
+if AM43XX
+config TARGET_AM43XX_EVM
+	bool "Support am43xx_evm"
+	select CREATE_BOARD_SYMLINK

This should be TI_I2C_BOARD_DETECT or else you will get a build error.

Yes this is definitely an issue, I just ran into this when trying to build and test U-Boot for AM43xx HS which is when I saw your response.

However even after fixing this I get additional build errors from SPI, USB Gadget, and UART related routines such as...

cmd/built-in.o: In function `do_spi_xfer':
/home/a0797059/git/u-boot/cmd/spi.c:61: undefined reference to spi_setup_slave' /home/a0797059/git/u-boot/cmd/spi.c:68: undefined reference to spi_claim_bus' /home/a0797059/git/u-boot/cmd/spi.c:71: undefined reference to spi_xfer' /home/a0797059/git/u-boot/cmd/spi.c:88: undefined reference to spi_release_bus' /home/a0797059/git/u-boot/cmd/spi.c:90: undefined reference to `spi_free_slave'

<cut>

I'll be digging into this a bit more to see where that comes from.

From: Madan Srinivas <[email protected]>

Defines CONFIG_TI_SECURE_DEVICE which needs to be turned on when building images for secure devices. This flag is used to invoke the secure image creation tools for creating a boot image that can be used on secure devices. This flag may also be used to conditionally compile code specific to secure devices.

This terminology will be used by all OMAP architecture devices, hence introducing to a common location.

With the creation of Kconfig for omap-common, moved the sourcing of the Kconfig files for the omap3/4/5 and am33xx devices from arch/arm/KConfig to the omap-common one.

Signed-off-by Madan Srinivas <[email protected]>

Signed-off-by Daniel Allred <[email protected]>

---

From: Madan Srinivas <[email protected]>

Defines CONFIG_TI_SECURE_DEVICE which needs to be turned on when building images for secure devices. This flag is used to invoke the secure image creation tools for creating a boot image that can be used on secure devices. This flag may also be used to conditionally compile code specific to secure devices.

This terminology will be used by all OMAP architecture devices, hence introducing to a common location.

With the creation of Kconfig for omap-common, moved the sourcing of the Kconfig files for the omap3/4/5 and am33xx devices from arch/arm/KConfig to the omap-common one.

Signed-off-by Madan Srinivas <[email protected]>

Signed-off-by Daniel Allred <[email protected]>

From: Madan Srinivas <[email protected]>

Defines CONFIG_TI_SECURE_DEVICE which needs to be turned on when building images for secure devices. This flag is used to invoke the secure image creation tools for creating a boot image that can be used on secure devices. This flag may also be used to conditionally compile code specific to secure devices.

This terminology will be used by all OMAP architecture devices, hence introducing to a common location.

With the creation of Kconfig for omap-common, moved the sourcing of the Kconfig files for the omap3/4/5 and am33xx devices from arch/arm/KConfig to the omap-common one.

Signed-off-by Madan Srinivas <[email protected]>

Signed-off-by Daniel Allred <[email protected]>

Adds a centralized config_secure.mk in omap-common for OMAP-style TI secure devices to use for boot image generation

Depending on the boot media, different images are needed for secure devices. These commands generates u-boot*_HS_* files that need to be used to boot secure devices.

Please refer to README.ti-secure for more information.

Adds a centralized config_secure.mk in omap-common for OMAP-style TI secure devices to use for boot image generation

Depending on the boot media, different images are needed for secure devices. These commands generates u-boot*_HS_* files that need to be used to boot secure devices.

Please refer to README.ti-secure for more information.

Signed-off-by Daniel Allred <[email protected]>

Signed-off-by Madan Srinivas <[email protected]>

Adds a centralized config_secure.mk in omap-common for OMAP-style TI secure devices to use for boot image generation

Depending on the boot media, different images are needed for secure devices. These commands generates u-boot*_HS_* files that need to be used to boot secure devices.

Please refer to README.ti-secure for more information.

Signed-off-by Daniel Allred <[email protected]>

Signed-off-by Madan Srinivas <[email protected]>

Modifies the config.mk to build secure images when building the SPL for secure devices.

Depending on the boot media, different images are needed for secure devices. The build generates u-boot*_HS_* files as appropriate for the different boot modes. The same u-boot binary file is processed slightly differently to produce a different boot image, depending on whether the user wants to boot off SPI, QSPI or other boot media.

Refer to README.ti-secure for more information.

Modifies the config.mk to build secure images when building the SPL for secure devices.

Depending on the boot media, different images are needed for secure devices. The build generates u-boot*_HS_* files as appropriate for the different boot modes. The same u-boot binary file is processed slightly differently to produce a different boot image, depending on whether the user wants to boot off SPI, QSPI or other boot media.

Refer to README.ti-secure for more information.

Signed-off-by Madan Srinivas <[email protected]>

Signed-off-by Daniel Allred <[email protected]>

Modifies the config.mk to build secure images when building the SPL for secure devices.

Depending on the boot media, different images are needed for secure devices. The build generates u-boot*_HS_* files as appropriate for the different boot modes. The same u-boot binary file is processed slightly differently to produce a different boot image, depending on whether the user wants to boot off SPI, QSPI or other boot media.

Refer to README.ti-secure for more information.

Signed-off-by Madan Srinivas <[email protected]>

Signed-off-by Daniel Allred <[email protected]>

From: Madan Srinivas <[email protected]>

Updates configs/am43xx_evm.h to use CONFIG options from SOC specific Kconfig file for various calculations.

On AM43x devices, the address of SPL entry point depends on the device type, i.e. whether it is secure or non-secure.

Further, for non-secure devices, the SPL entry point is different between USB HOST boot mode, other "memory" boot modes (MMC, NAND) and "peripheral" boot modes (UART, USB)

To add to the complexity, on secure devices, in addition to the above differences, the SPL entry point can change because of the space occupied by other components (other than u-boot or spl) that go into a secure boot image.

To prevent the user from having to modify source files every time any component of the secure image changes, the value of CONFIG_SPL_TEXT_BASE has been set using a Kconfig option that is supplied in the am43xx_*_defconfig files

Using the CONFIG options also enables us to do away with some compile time flags that were used to specify CONFIG_SPL_TEXT_BASE for different boot modes.

On QSPI devices, the same problem described above occurs w.r.t. the address of the u-boot entry point in flash, when booting secure devices. To handle this, CONFIG_SYS_TEXT_BASE is also setup via a Kconfig option and the defconfig files.

From: Madan Srinivas <[email protected]>

Updates configs/am43xx_evm.h to use CONFIG options from SOC specific Kconfig file for various calculations.

On AM43x devices, the address of SPL entry point depends on the device type, i.e. whether it is secure or non-secure.

Further, for non-secure devices, the SPL entry point is different between USB HOST boot mode, other "memory" boot modes (MMC, NAND) and "peripheral" boot modes (UART, USB)

To add to the complexity, on secure devices, in addition to the above differences, the SPL entry point can change because of the space occupied by other components (other than u-boot or spl) that go into a secure boot image.

To prevent the user from having to modify source files every time any component of the secure image changes, the value of CONFIG_SPL_TEXT_BASE has been set using a Kconfig option that is supplied in the am43xx_*_defconfig files

Using the CONFIG options also enables us to do away with some compile time flags that were used to specify CONFIG_SPL_TEXT_BASE for different boot modes.

On QSPI devices, the same problem described above occurs w.r.t. the address of the u-boot entry point in flash, when booting secure devices. To handle this, CONFIG_SYS_TEXT_BASE is also setup via a Kconfig option and the defconfig files.

Signed-off-by Madan Srinivas <[email protected]>

Signed-off-by Daniel Allred <[email protected]>

From: Madan Srinivas <[email protected]>

Updates configs/am43xx_evm.h to use CONFIG options from SOC specific Kconfig file for various calculations.

On AM43x devices, the address of SPL entry point depends on the device type, i.e. whether it is secure or non-secure.

Further, for non-secure devices, the SPL entry point is different between USB HOST boot mode, other "memory" boot modes (MMC, NAND) and "peripheral" boot modes (UART, USB)

To add to the complexity, on secure devices, in addition to the above differences, the SPL entry point can change because of the space occupied by other components (other than u-boot or spl) that go into a secure boot image.

To prevent the user from having to modify source files every time any component of the secure image changes, the value of CONFIG_SPL_TEXT_BASE has been set using a Kconfig option that is supplied in the am43xx_*_defconfig files

Using the CONFIG options also enables us to do away with some compile time flags that were used to specify CONFIG_SPL_TEXT_BASE for different boot modes.

On QSPI devices, the same problem described above occurs w.r.t. the address of the u-boot entry point in flash, when booting secure devices. To handle this, CONFIG_SYS_TEXT_BASE is also setup via a Kconfig option and the defconfig files.

Signed-off-by Madan Srinivas <[email protected]>

Signed-off-by Daniel Allred <[email protected]>

From: Madan Srinivas <[email protected]>

Adds code to detect AM43xx HS EVMS - the string in the I2C EEPROM for HS EVMs differs from GP EVMs. Adds code to for evm detection, regardless of whether the evm is for GP or HS parts, and updates board init to use that.

Modifies findfdt command to pick up am437x-gp-evm.dtb for the HS EVMs also, as the boards are similar except for some security specific changes around power supply and enclosure protection.

From: Madan Srinivas <[email protected]>

Adds code to detect AM43xx HS EVMS - the string in the I2C EEPROM for HS EVMs differs from GP EVMs. Adds code to for evm detection, regardless of whether the evm is for GP or HS parts, and updates board init to use that.

Modifies findfdt command to pick up am437x-gp-evm.dtb for the HS EVMs also, as the boards are similar except for some security specific changes around power supply and enclosure protection.

Signed-off-by Madan Srinivas <[email protected]>

Signed-off-by Daniel Allred <[email protected]>

Signed-off-by Andreas Dannenberg <[email protected]>

Signed-off-by Lokesh Vutla <[email protected]>

From: Madan Srinivas <[email protected]>

Adds new defconfig files for AM43xx secure devices. These are the same as the non-secure parts, except for
CONFIG_TI_SECURE_DEVICE option set to 'y' CONFIG_ISW_ENTRY_ADDR updated for secure images.

Signed-off-by Daniel Allred <[email protected]>

Signed-off-by Madan Srinivas <[email protected]>

---
 configs/am43xx_hs_evm_defconfig              | 12 ++++++++++++
 configs/am43xx_hs_evm_ethboot_defconfig      | 11 +++++++++++
 configs/am43xx_hs_evm_qspiboot_defconfig     | 10 ++++++++++
 configs/am43xx_hs_evm_rtconly_defconfig      | 12 ++++++++++++

 configs/am43xx_hs_evm_usbhost_boot_defconfig | 11 +++++++++++
 configs/am43xx_hs_evm_usbspl_defconfig       | 12 ++++++++++++
 6 files changed, 68 insertions(+)
 create mode 100644 configs/am43xx_hs_evm_defconfig
 create mode 100644 configs/am43xx_hs_evm_ethboot_defconfig
 create mode 100644 configs/am43xx_hs_evm_qspiboot_defconfig
 create mode 100644 configs/am43xx_hs_evm_rtconly_defconfig
 create mode 100644 configs/am43xx_hs_evm_usbhost_boot_defconfig
 create mode 100644 configs/am43xx_hs_evm_usbspl_defconfig

configs/am43xx_hs_evm_defconfig new file +12 -0

new file mode 100644
index 0000000..a79a82b
@@ -0,0 +1,12 @@
+CONFIG_ARM=y
+CONFIG_AM43XX=y
+CONFIG_TI_SECURE_DEVICE=y
+CONFIG_TARGET_AM43XX_EVM=y
+CONFIG_SPL=y
+CONFIG_ISW_ENTRY_ADDR=0x40302ae0
+CONFIG_SYS_EXTRA_OPTIONS="SERIAL1,CONS_INDEX=1,NAND"
+# CONFIG_CMD_IMLS is not set
+# CONFIG_CMD_FLASH is not set
+# CONFIG_CMD_SETEXPR is not set
+CONFIG_SPI_FLASH_BAR=y
+CONFIG_SPI_FLASH=y

configs/am43xx_hs_evm_ethboot_defconfig new file +11 -0

new file mode 100644
index 0000000..06729fd
@@ -0,0 +1,11 @@
+CONFIG_ARM=y
+CONFIG_AM43XX=y
+CONFIG_TI_SECURE_DEVICE=y
+CONFIG_TARGET_AM43XX_EVM=y
+CONFIG_SPL=y
+CONFIG_ISW_ENTRY_ADDR=0x40302ae0
+CONFIG_SYS_EXTRA_OPTIONS="SERIAL1,CONS_INDEX=1,NAND,SPL_ETH_SUPPORT"
+# CONFIG_CMD_IMLS is not set
+# CONFIG_CMD_FLASH is not set
+# CONFIG_CMD_SETEXPR is not set
+CONFIG_SPI_FLASH=y

configs/am43xx_hs_evm_qspiboot_defconfig new file +10 -0

new file mode 100644
index 0000000..8ae4672
@@ -0,0 +1,10 @@
+CONFIG_ARM=y
+CONFIG_AM43XX=y
+CONFIG_TI_SECURE_DEVICE=y
+CONFIG_TARGET_AM43XX_EVM=y
+CONFIG_ISW_ENTRY_ADDR=0x30002ae0
+CONFIG_SYS_EXTRA_OPTIONS="SERIAL1,CONS_INDEX=1,QSPI,QSPI_BOOT"
+# CONFIG_CMD_IMLS is not set
+# CONFIG_CMD_FLASH is not set
+# CONFIG_CMD_SETEXPR is not set
+CONFIG_SPI_FLASH=y

configs/am43xx_hs_evm_rtconly_defconfig new file +12 -0

new file mode 100644
index 0000000..25c2db2
@@ -0,0 +1,12 @@
+CONFIG_ARM=y
+CONFIG_AM43XX=y
+CONFIG_TI_SECURE_DEVICE=y
+CONFIG_TARGET_AM43XX_EVM=y
+CONFIG_SPL=y
+CONFIG_ISW_ENTRY_ADDR=0x40302ae0
+CONFIG_SYS_EXTRA_OPTIONS="SERIAL1,CONS_INDEX=1,NAND,SPL_RTC_ONLY_SUPPORT"
+# CONFIG_CMD_IMLS is not set
+# CONFIG_CMD_FLASH is not set
+# CONFIG_CMD_SETEXPR is not set
+CONFIG_SPI_FLASH_BAR=y
+CONFIG_SPI_FLASH=y

configs/am43xx_hs_evm_usbhost_boot_defconfig new file +11 -0

new file mode 100644
index 0000000..776f669
@@ -0,0 +1,11 @@
+CONFIG_ARM=y
+CONFIG_AM43XX=y
+CONFIG_TI_SECURE_DEVICE=y
+CONFIG_TARGET_AM43XX_EVM=y
+CONFIG_SPL=y
+CONFIG_ISW_ENTRY_ADDR=0x40302ae0
+CONFIG_SYS_EXTRA_OPTIONS="SERIAL1,CONS_INDEX=1,NAND,SPL_USB_HOST_SUPPORT"
+# CONFIG_CMD_IMLS is not set
+# CONFIG_CMD_FLASH is not set
+# CONFIG_CMD_SETEXPR is not set
+CONFIG_SPI_FLASH=y

configs/am43xx_hs_evm_usbspl_defconfig new file +12 -0

new file mode 100644
index 0000000..5a3f566
@@ -0,0 +1,12 @@
+CONFIG_ARM=y
+CONFIG_AM43XX=y
+CONFIG_TI_SECURE_DEVICE=y
+CONFIG_TARGET_AM43XX_EVM=y
+CONFIG_SPL=y
+CONFIG_ISW_ENTRY_ADDR=0x40302ae0
+CONFIG_SYS_EXTRA_OPTIONS="SERIAL1,CONS_INDEX=1,NAND,SPL_USBETH_SUPPORT"
+# CONFIG_CMD_IMLS is not set
+# CONFIG_CMD_FLASH is not set
+# CONFIG_CMD_SETEXPR is not set
+CONFIG_SPI_FLASH_BAR=y
+CONFIG_SPI_FLASH=y

Quoted 7 lines · Daniel Allred

From: Madan Srinivas <[email protected]>

Adds new defconfig files for AM43xx secure devices. These are the same as the non-secure parts, except for
CONFIG_TI_SECURE_DEVICE option set to 'y' CONFIG_ISW_ENTRY_ADDR updated for secure images.

Quoted 7 lines

Signed-off-by Daniel Allred <[email protected]>

Signed-off-by Madan Srinivas <[email protected]>

---
 configs/am43xx_hs_evm_defconfig              | 12 ++++++++++++
 configs/am43xx_hs_evm_ethboot_defconfig      | 11 +++++++++++
 configs/am43xx_hs_evm_qspiboot_defconfig     | 10 ++++++++++
 configs/am43xx_hs_evm_rtconly_defconfig      | 12 ++++++++++++

You do not need this defconfig. Also now only DT enabled configs are accepted. Ill let Tom to comment here.

Quoted 18 lines · Lokesh Vutla

Quoted 14 lines · Daniel Allred

From: Madan Srinivas <[email protected]>

Adds new defconfig files for AM43xx secure devices. These are the same as the non-secure parts, except for
CONFIG_TI_SECURE_DEVICE option set to 'y' CONFIG_ISW_ENTRY_ADDR updated for secure images.

Signed-off-by Daniel Allred <[email protected]>

Signed-off-by Madan Srinivas <[email protected]>

---
  configs/am43xx_hs_evm_defconfig              | 12 ++++++++++++
  configs/am43xx_hs_evm_ethboot_defconfig      | 11 +++++++++++
  configs/am43xx_hs_evm_qspiboot_defconfig     | 10 ++++++++++
  configs/am43xx_hs_evm_rtconly_defconfig      | 12 ++++++++++++

Quoted 2 lines

You do not need this defconfig. Also now only DT enabled configs are accepted. Ill let Tom to comment here.

Yes, just like was done for the dra7xa/am57xx HS parts, we need to be doing DM+DT here too.

Quoted 19 lines · Tom Rini

Quoted 18 lines · Lokesh Vutla

Quoted 14 lines · Daniel Allred

From: Madan Srinivas <[email protected]>

Adds new defconfig files for AM43xx secure devices. These are the same as the non-secure parts, except for
CONFIG_TI_SECURE_DEVICE option set to 'y' CONFIG_ISW_ENTRY_ADDR updated for secure images.

Signed-off-by Daniel Allred <[email protected]>

Signed-off-by Madan Srinivas <[email protected]>

---
 configs/am43xx_hs_evm_defconfig              | 12 ++++++++++++
 configs/am43xx_hs_evm_ethboot_defconfig      | 11 +++++++++++
 configs/am43xx_hs_evm_qspiboot_defconfig     | 10 ++++++++++
 configs/am43xx_hs_evm_rtconly_defconfig      | 12 ++++++++++++

Quoted 6 lines

Quoted 2 lines

You do not need this defconfig. Also now only DT enabled configs are accepted. Ill let Tom to comment here.

Yes, just like was done for the dra7xa/am57xx HS parts, we need to be doing DM+DT here too.

So I understand to not create any new defconfigs that are not DM+DT, but what happens to these old ones? Are they deprecated? Or does someone need to patch/convert them?

I guess I'll just simplify this to make a single am437x_hs_evm_defconfig that mirrors the am437x_gp_evm_defconfig.

Updated the CONFIG_SPL_TEXT_BASE to support secure parts (moving the start address past secure reserved memory and the size of the security certificate that precedes the boot image on secure devices). Updated the related CONFIG_SPL_MAX_SIZE to properly reflect the internal memory actually available on the various device flavors (Common minimum internal RAM guaranteed for various flavors of DRA7xx/AM57xx is 512KB).

Updated the CONFIG_SPL_TEXT_BASE to support secure parts (moving the start address past secure reserved memory and the size of the security certificate that precedes the boot image on secure devices). Updated the related CONFIG_SPL_MAX_SIZE to properly reflect the internal memory actually available on the various device flavors (Common minimum internal RAM guaranteed for various flavors of DRA7xx/AM57xx is 512KB).

Signed-off-by Daniel Allred <[email protected]>

Signed-off-by Madan Srinivas <[email protected]>

Updated the CONFIG_SPL_TEXT_BASE to support secure parts (moving the start address past secure reserved memory and the size of the security certificate that precedes the boot image on secure devices). Updated the related CONFIG_SPL_MAX_SIZE to properly reflect the internal memory actually available on the various device flavors (Common minimum internal RAM guaranteed for various flavors of DRA7xx/AM57xx is 512KB).

Signed-off-by Daniel Allred <[email protected]>

Signed-off-by Madan Srinivas <[email protected]>

---
 include/configs/ti_omap5_common.h | 32 +++++++++++++++++++++++++++-----
 1 file changed, 27 insertions(+), 5 deletions(-)

include/configs/ti_omap5_common.h +3 -3

index 202b18c..b2d4a0b 100644
@@ -132,13 +132,35 @@
 
 /*
  * SPL related defines.  The Public RAM memory map the ROM defines the
- * area between 0x40300000 and 0x4031E000 as a download area for OMAP5
- * (dra7xx is larger, but we do not need to be larger at this time).  We
- * set CONFIG_SPL_DISPLAY_PRINT to have omap_rev_string() called and
+ * area between 0x40300000 and 0x4031E000 as a download area for OMAP5.
+ * On DRA7xx/AM57XX the download area is between 0x40300000 and 0x4037E000.
+ * We set CONFIG_SPL_DISPLAY_PRINT to have omap_rev_string() called and
  * print some information.
  */

Updates the SPL build so that when CONFIG_TI_SECURE_DEVICE is in use (which it should be when building for secure parts), the TI secure development package is used to create a valid secure boot image. The u-boot SPL build processes is NOT aware of the details of creating the boot image - all of that information is encapsulated in the TI secure development package, which is available from TI. More info can be found in README.ti-secure

Right now, two image types are generated, MLO and X-LOADER. The types are important, as certain boot modes implemented by the device's ROM boot loader require one or the other (they are not equivalent). The output filenames are u-boot-spl_HS_MLO and u-boot-spl_HS_X-LOADER. The u-boot-spl_HS_MLO image is also copied to a file named MLO, which is the name that the device ROM bootloader requires for loading from the FAT partition of an SD card (same as on non-secure devices).

Updates the SPL build so that when CONFIG_TI_SECURE_DEVICE is in use (which it should be when building for secure parts), the TI secure development package is used to create a valid secure boot image. The u-boot SPL build processes is NOT aware of the details of creating the boot image - all of that information is encapsulated in the TI secure development package, which is available from TI. More info can be found in README.ti-secure

Right now, two image types are generated, MLO and X-LOADER. The types are important, as certain boot modes implemented by the device's ROM boot loader require one or the other (they are not equivalent). The output filenames are u-boot-spl_HS_MLO and u-boot-spl_HS_X-LOADER. The u-boot-spl_HS_MLO image is also copied to a file named MLO, which is the name that the device ROM bootloader requires for loading from the FAT partition of an SD card (same as on non-secure devices).

Signed-off-by Daniel Allred <[email protected]>

Signed-off-by Madan Srinivas <[email protected]>

Updates the SPL build so that when CONFIG_TI_SECURE_DEVICE is in use (which it should be when building for secure parts), the TI secure development package is used to create a valid secure boot image. The u-boot SPL build processes is NOT aware of the details of creating the boot image - all of that information is encapsulated in the TI secure development package, which is available from TI. More info can be found in README.ti-secure

Right now, two image types are generated, MLO and X-LOADER. The types are important, as certain boot modes implemented by the device's ROM boot loader require one or the other (they are not equivalent). The output filenames are u-boot-spl_HS_MLO and u-boot-spl_HS_X-LOADER. The u-boot-spl_HS_MLO image is also copied to a file named MLO, which is the name that the device ROM bootloader requires for loading from the FAT partition of an SD card (same as on non-secure devices).

Signed-off-by Daniel Allred <[email protected]>

Signed-off-by Madan Srinivas <[email protected]>

Update the CPU string output so that the device type is now included as part of the CPU string that is printed as the SPL or u-boot comes up. This update adds a suffix of the form "-GP" or "-HS" for production devices, so that general purpose (GP) and high security (HS) can be distiguished. Applies to all OMAP5 variants.

Signed-off-by Daniel Allred <[email protected]>

Signed-off-by Madan Srinivas <[email protected]>

Update the CPU string output so that the device type is now included as part of the CPU string that is printed as the SPL or u-boot comes up. This update adds a suffix of the form "-GP" or "-HS" for production devices, so that general purpose (GP) and high security (HS) can be distiguished. Applies to all OMAP5 variants.

Signed-off-by Daniel Allred <[email protected]>

Signed-off-by Madan Srinivas <[email protected]>

---
 arch/arm/cpu/armv7/omap-common/hwinit-common.c | 22 ++++++++++++++++++++--
 arch/arm/include/asm/arch-omap4/cpu.h          |  7 +++++++
 arch/arm/include/asm/arch-omap5/cpu.h          |  7 +++++++
 3 files changed, 34 insertions(+), 2 deletions(-)

arch/arm/cpu/armv7/omap-common/hwinit-common.c +20 -2

index 01c2d57..078bdd8 100644
@@ -65,12 +65,30 @@ static void omap_rev_string(void)
 	u32 major_rev = (omap_rev & 0x00000F00) >> 8;
 	u32 minor_rev = (omap_rev & 0x000000F0) >> 4;
 
+	const char *sec_s;
+
+	switch (get_device_type()) {
+	case TST_DEVICE:
+		sec_s = "TST";
+		break;
+	case EMU_DEVICE:
+		sec_s = "EMU";
+		break;
+	case HS_DEVICE:
+		sec_s = "HS";
+		break;
+	case GP_DEVICE:
+		sec_s = "GP";
+		break;
+	default:
+		sec_s = "?";
+	}
+
 	if (soc_variant)
 		printf("OMAP");
 	else
 		printf("DRA");
-	printf("%x ES%x.%x\n", omap_variant, major_rev,
-	       minor_rev);
+	printf("%x-%s ES%x.%x\n", omap_variant, sec_s, major_rev, minor_rev);
 }
 
 #ifdef CONFIG_SPL_BUILD

arch/arm/include/asm/arch-omap4/cpu.h +7 -0

index f7595ae..34609b9 100644
@@ -59,6 +59,13 @@ struct watchdog {
 #define TCLR_AR			(0x1 << 1)
 #define TCLR_PRE		(0x1 << 5)
 
+/* device type */
+#define DEVICE_MASK         (BIT(8) | BIT(9) | BIT(10))
+#define TST_DEVICE          0x0
+#define EMU_DEVICE          0x1
+#define HS_DEVICE           0x2
+#define GP_DEVICE           0x3
+
 /* I2C base */
 #define I2C_BASE1		(OMAP44XX_L4_PER_BASE + 0x70000)
 #define I2C_BASE2		(OMAP44XX_L4_PER_BASE + 0x72000)

arch/arm/include/asm/arch-omap5/cpu.h +7 -0

index b1513e9..1d53da6 100644
@@ -63,6 +63,13 @@ struct watchdog {
 #define TCLR_AR			(0x1 << 1)
 #define TCLR_PRE		(0x1 << 5)
 
+/* device type */
+#define DEVICE_MASK         (BIT(8) | BIT(9) | BIT(10))
+#define TST_DEVICE          0x0
+#define EMU_DEVICE          0x1
+#define HS_DEVICE           0x2
+#define GP_DEVICE           0x3
+
 /* I2C base */
 #define I2C_BASE1		(OMAP54XX_L4_PER_BASE + 0x70000)
 #define I2C_BASE2		(OMAP54XX_L4_PER_BASE + 0x72000)

Signature · 6 lines

1.9.1

_______________________________________________
U-Boot mailing list
U-Boot at lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Quoted 6 lines · Daniel Allred

Update the CPU string output so that the device type is now included as part of the CPU string that is printed as the SPL or u-boot comes up. This update adds a suffix of the form "-GP" or "-HS" for production devices, so that general purpose (GP) and high security (HS) can be distiguished. Applies to all OMAP5 variants.

When I'm building for AM437x HS and running on the device I don't see that output. It seems like there is something funny going on with CONFIG_SPL_DISPLAY_PRINT. Even though this definition is activated in ti_omap4_common.h and ti_omap5_common.h it is not seen by preloader_console_init() in spl.c, hence the function that prints the chip-type/rev specifics never gets invoked.

Quoted 8 lines · Andreas Dannenberg

Quoted 6 lines · Daniel Allred

Update the CPU string output so that the device type is now included as part of the CPU string that is printed as the SPL or u-boot comes up. This update adds a suffix of the form "-GP" or "-HS" for production devices, so that general purpose (GP) and high security (HS) can be distiguished. Applies to all OMAP5 variants.

Quoted 6 lines

When I'm building for AM437x HS and running on the device I don't see that output. It seems like there is something funny going on with CONFIG_SPL_DISPLAY_PRINT. Even though this definition is activated in ti_omap4_common.h and ti_omap5_common.h it is not seen by preloader_console_init() in spl.c, hence the function that prints the chip-type/rev specifics never gets invoked.

So when I run the patches on actual DRA72x HS and DRA74x HS hardware I'll get the device name/type output by SPL as expected so that piece works. However this patch's commit message implies the same should also work on AM437x HS which it doesn't. I don't have AM437x non-secure hardware at my desk but I looked at some boot logs from our test farms and I also don't see the device ID output by SPL so that may be just how it currently is implemented generally for AM437* and has nothing to do with the patch discussed here.

Madan, please comment/chime-in as needed.

Tested-by Andreas Dannenberg <[email protected]>

--
Andreas Dannenberg
Texas Instruments Inc

Quoted 16 lines · Andreas Dannenberg

Quoted 8 lines · Andreas Dannenberg

Quoted 6 lines · Daniel Allred

Update the CPU string output so that the device type is now included as part of the CPU string that is printed as the SPL or u-boot comes up. This update adds a suffix of the form "-GP" or "-HS" for production devices, so that general purpose (GP) and high security (HS) can be distiguished. Applies to all OMAP5 variants.

Quoted 6 lines

When I'm building for AM437x HS and running on the device I don't see that output. It seems like there is something funny going on with CONFIG_SPL_DISPLAY_PRINT. Even though this definition is activated in ti_omap4_common.h and ti_omap5_common.h it is not seen by preloader_console_init() in spl.c, hence the function that prints the chip-type/rev specifics never gets invoked.

Quoted 8 lines

So when I run the patches on actual DRA72x HS and DRA74x HS hardware I'll get the device name/type output by SPL as expected so that piece works. However this patch's commit message implies the same should also work on AM437x HS which it doesn't. I don't have AM437x non-secure hardware at my desk but I looked at some boot logs from our test farms and I also don't see the device ID output by SPL so that may be just how it currently is implemented generally for AM437* and has nothing to do with the patch discussed here.

This hwinit-common.c is not used by the AM335x/AM437x parts, hence the statement "Applies to all OMAP5 variants" in the commit message. The omap4/5 use in the commit header is because the omap4 cpu.h header file had to be updated in order to not break omap4 builds (because those builds DO use this hwinit-common.c).

Quoted 25 lines · Daniel

Quoted 24 lines · Andreas Dannenberg

Quoted 8 lines · Andreas Dannenberg

Quoted 6 lines · Daniel Allred

Update the CPU string output so that the device type is now included as part of the CPU string that is printed as the SPL or u-boot comes up. This update adds a suffix of the form "-GP" or "-HS" for production devices, so that general purpose (GP) and high security (HS) can be distiguished. Applies to all OMAP5 variants.

Quoted 6 lines

When I'm building for AM437x HS and running on the device I don't see that output. It seems like there is something funny going on with CONFIG_SPL_DISPLAY_PRINT. Even though this definition is activated in ti_omap4_common.h and ti_omap5_common.h it is not seen by preloader_console_init() in spl.c, hence the function that prints the chip-type/rev specifics never gets invoked.

So when I run the patches on actual DRA72x HS and DRA74x HS hardware I'll get the device name/type output by SPL as expected so that piece works. However this patch's commit message implies the same should also work on AM437x HS which it doesn't. I don't have AM437x non-secure hardware at my desk but I looked at some boot logs from our test farms and I also don't see the device ID output by SPL so that may be just how it currently is implemented generally for AM437* and has nothing to do with the patch discussed here.

Quoted 5 lines

This hwinit-common.c is not used by the AM335x/AM437x parts, hence the statement "Applies to all OMAP5 variants" in the commit message. The omap4/5 use in the commit header is because the omap4 cpu.h header file had to be updated in order to not break omap4 builds (because those builds DO use this hwinit-common.c).

Daniel,
thanks for clarifying/confirming my suspicion. Then I'm okay with this patch.

Quoted 32 lines · Andreas Dannenberg

Quoted 30 lines · Daniel

Quoted 16 lines · Andreas Dannenberg

Quoted 8 lines · Andreas Dannenberg

Quoted 6 lines · Daniel Allred

Update the CPU string output so that the device type is now included as part of the CPU string that is printed as the SPL or u-boot comes up. This update adds a suffix of the form "-GP" or "-HS" for production devices, so that general purpose (GP) and high security (HS) can be distiguished. Applies to all OMAP5 variants.

Quoted 6 lines

When I'm building for AM437x HS and running on the device I don't see that output. It seems like there is something funny going on with CONFIG_SPL_DISPLAY_PRINT. Even though this definition is activated in ti_omap4_common.h and ti_omap5_common.h it is not seen by preloader_console_init() in spl.c, hence the function that prints the chip-type/rev specifics never gets invoked.

Quoted 8 lines

So when I run the patches on actual DRA72x HS and DRA74x HS hardware I'll get the device name/type output by SPL as expected so that piece works. However this patch's commit message implies the same should also work on AM437x HS which it doesn't. I don't have AM437x non-secure hardware at my desk but I looked at some boot logs from our test farms and I also don't see the device ID output by SPL so that may be just how it currently is implemented generally for AM437* and has nothing to do with the patch discussed here.

This hwinit-common.c is not used by the AM335x/AM437x parts, hence the statement "Applies to all OMAP5 variants" in the commit message. The omap4/5 use in the commit header is because the omap4 cpu.h header file had to be updated in order to not break omap4 builds (because those builds DO use this hwinit-common.c).

Quoted 2 lines

Daniel,
thanks for clarifying/confirming my suspicion. Then I'm okay with this patch.

Can we do a follow-up that moves this otherwise common code into the rest of the families?

Quoted 36 lines · Tom Rini

Quoted 34 lines · Andreas Dannenberg

Quoted 25 lines · Daniel

Quoted 16 lines · Andreas Dannenberg

Quoted 8 lines · Andreas Dannenberg

Quoted 6 lines · Daniel Allred

Update the CPU string output so that the device type is now included as part of the CPU string that is printed as the SPL or u-boot comes up. This update adds a suffix of the form "-GP" or "-HS" for production devices, so that general purpose (GP) and high security (HS) can be distiguished. Applies to all OMAP5 variants.

Quoted 6 lines

When I'm building for AM437x HS and running on the device I don't see that output. It seems like there is something funny going on with CONFIG_SPL_DISPLAY_PRINT. Even though this definition is activated in ti_omap4_common.h and ti_omap5_common.h it is not seen by preloader_console_init() in spl.c, hence the function that prints the chip-type/rev specifics never gets invoked.

Quoted 8 lines

So when I run the patches on actual DRA72x HS and DRA74x HS hardware I'll get the device name/type output by SPL as expected so that piece works. However this patch's commit message implies the same should also work on AM437x HS which it doesn't. I don't have AM437x non-secure hardware at my desk but I looked at some boot logs from our test farms and I also don't see the device ID output by SPL so that may be just how it currently is implemented generally for AM437* and has nothing to do with the patch discussed here.

Quoted 5 lines

This hwinit-common.c is not used by the AM335x/AM437x parts, hence the statement "Applies to all OMAP5 variants" in the commit message. The omap4/5 use in the commit header is because the omap4 cpu.h header file had to be updated in order to not break omap4 builds (because those builds DO use this hwinit-common.c).

Daniel,
thanks for clarifying/confirming my suspicion. Then I'm okay with this patch.

Quoted 2 lines

Can we do a follow-up that moves this otherwise common code into the rest of the families?

Hi Tom,
just to make sure I understand your suggestion correctly, this is about a behind the scenes optimization to remove the code duplication we currently have in .../asm/arch-omap(4|5)/cpu.h, rather than making the CPU string output as part of SPL work on all of our (TI) platforms, yes?

Quoted 40 lines · Andreas Dannenberg

Quoted 38 lines · Tom Rini

Quoted 26 lines · Andreas Dannenberg

Quoted 25 lines · Daniel

Quoted 24 lines · Andreas Dannenberg

Quoted 8 lines · Andreas Dannenberg

Quoted 6 lines · Daniel Allred

Update the CPU string output so that the device type is now included as part of the CPU string that is printed as the SPL or u-boot comes up. This update adds a suffix of the form "-GP" or "-HS" for production devices, so that general purpose (GP) and high security (HS) can be distiguished. Applies to all OMAP5 variants.

Quoted 6 lines

When I'm building for AM437x HS and running on the device I don't see that output. It seems like there is something funny going on with CONFIG_SPL_DISPLAY_PRINT. Even though this definition is activated in ti_omap4_common.h and ti_omap5_common.h it is not seen by preloader_console_init() in spl.c, hence the function that prints the chip-type/rev specifics never gets invoked.

So when I run the patches on actual DRA72x HS and DRA74x HS hardware I'll get the device name/type output by SPL as expected so that piece works. However this patch's commit message implies the same should also work on AM437x HS which it doesn't. I don't have AM437x non-secure hardware at my desk but I looked at some boot logs from our test farms and I also don't see the device ID output by SPL so that may be just how it currently is implemented generally for AM437* and has nothing to do with the patch discussed here.

Quoted 8 lines

Quoted 5 lines

This hwinit-common.c is not used by the AM335x/AM437x parts, hence the statement "Applies to all OMAP5 variants" in the commit message. The omap4/5 use in the commit header is because the omap4 cpu.h header file had to be updated in order to not break omap4 builds (because those builds DO use this hwinit-common.c).

Daniel,
thanks for clarifying/confirming my suspicion. Then I'm okay with this patch.

Can we do a follow-up that moves this otherwise common code into the rest of the families?

Quoted 5 lines

Hi Tom,
just to make sure I understand your suggestion correctly, this is about a behind the scenes optimization to remove the code duplication we currently have in .../asm/arch-omap(4|5)/cpu.h, rather than making the CPU string output as part of SPL work on all of our (TI) platforms, yes?

I want as much consolidate and consistency of output as is both feasible and practical.

Update the CPU string output so that the device type is now included as part of the CPU string that is printed as the SPL or u-boot comes up. This update adds a suffix of the form "-GP" or "-HS" for production devices, so that general purpose (GP) and high security (HS) can be distiguished. Applies to all OMAP5 variants.

arch/arm/include/asm/arch-omap4/cpu.h +0 -0

index f7595ae..34609b9 100644

Adds an fdt.c file in that defines the ft_cpu_setup() function, which should be called from a board-specific ft_board_setup()). This ft_cpu_setup() will currently do nothing for non-secure (GP)
devices but contains pertinent updates for booting on secure (HS)
devices.

Update the omap5 Makefile to include the fdt.c in the build.

Signed-off-by Daniel Allred <[email protected]>

Signed-off-by Madan Srinivas <[email protected]>

---
 arch/arm/cpu/armv7/omap5/Makefile |   1 +
 arch/arm/cpu/armv7/omap5/fdt.c    | 183 ++++++++++++++++++++++++++++++++++++++
 2 files changed, 184 insertions(+)
 create mode 100644 arch/arm/cpu/armv7/omap5/fdt.c

arch/arm/cpu/armv7/omap5/Makefile +1 -0

index f2930d5..3caba86 100644
@@ -12,4 +12,5 @@ obj-y	+= sdram.o
 obj-y	+= prcm-regs.o
 obj-y	+= hw_data.o
 obj-y	+= abb.o
+obj-y	+= fdt.o
 obj-$(CONFIG_IODELAY_RECALIBRATION) += dra7xx_iodelay.o

arch/arm/cpu/armv7/omap5/fdt.c new file +183 -0

new file mode 100644
index 0000000..f2f40f0
@@ -0,0 +1,183 @@
+/*
+ * Copyright 2016 Texas Instruments, Inc.
+ *
+ * SPDX-License-Identifier: GPL-2.0+
+ */
+
+#include <common.h>
+#include <libfdt.h>
+#include <fdt_support.h>
+#include <malloc.h>
+
+#include <asm/omap_common.h>
+#include <asm/arch-omap5/sys_proto.h>
+
+#ifdef CONFIG_TI_SECURE_DEVICE
+
+/* Give zero values if not already defined */
+#ifndef CONFIG_SECURE_BOOT_SRAM
+#define CONFIG_SECURE_BOOT_SRAM (0)
+#endif
+#ifndef CONFIG_SECURE_RUN_SRAM
+#define CONFIG_SECURE_RUN_SRAM (0)
+#endif
+
+static u32 hs_irq_skip[] = {
+	8,	/* Secure violation reporting interrupt */
+	15,	/* One interrupt for SDMA by secure world */
+	118	/* One interrupt for Crypto DMA by secure world */
+};
+
+static int ft_hs_fixup_crossbar(void *fdt, bd_t *bd)
+{
+	const char *path;
+	int offs;
+	int ret;
+	int len, i, old_cnt, new_cnt;
+	u32 *temp;
+	const u32 *p_data;
+
+	/*
+	 * Increase the size of the fdt
+	 * so we have some breathing room
+	 */
+	ret = fdt_increase_size(fdt, 512);
+	if (ret < 0) {
+		printf("Could not increase size of device tree: %s\n",
+		       fdt_strerror(ret));
+		return ret;
+	}
+
+	/* Reserve IRQs that are used/needed by secure world */
+	path = "/ocp/crossbar";
+	offs = fdt_path_offset(fdt, path);
+	if (offs < 0) {
+		debug("Node %s not found.\n", path);
+		return 0;
+	}
+
+	/* Get current entries */
+	p_data = fdt_getprop(fdt, offs, "ti,irqs-skip", &len);
+	if (p_data)
+		old_cnt = len / sizeof(u32);
+	else
+		old_cnt = 0;
+
+	new_cnt = sizeof(hs_irq_skip) /
+				sizeof(hs_irq_skip[0]);
+
+	/* Create new/updated skip list for HS parts */
+	temp = malloc(sizeof(u32) * (old_cnt + new_cnt));
+	for (i = 0; i < new_cnt; i++)
+		temp[i] = cpu_to_fdt32(hs_irq_skip[i]);
+	for (i = 0; i < old_cnt; i++)
+		temp[i + new_cnt] = p_data[i];
+
+	/* Blow away old data and set new data */
+	fdt_delprop(fdt, offs, "ti,irqs-skip");
+	ret = fdt_setprop(fdt, offs, "ti,irqs-skip",
+			  temp,
+			  (old_cnt + new_cnt) * sizeof(u32));
+	free(temp);
+
+	/* Check if the update worked */
+	if (ret < 0) {
+		printf("Could not add ti,irqs-skip property to node %s: %s\n",
+		       path, fdt_strerror(ret));
+		return ret;
+	}
+
+	return 0;
+}
+
+static int ft_hs_disable_rng(void *fdt, bd_t *bd)
+{
+	const char *path;
+	int offs;
+	int ret;
+
+	/* Make HW RNG reserved for secure world use */
+	path = "/ocp/rng";
+	offs = fdt_path_offset(fdt, path);
+	if (offs < 0) {
+		debug("Node %s not found.\n", path);
+		return 0;
+	}
+	ret = fdt_setprop_string(fdt, offs,
+				 "status", "disabled");
+	if (ret < 0) {
+		printf("Could not add status property to node %s: %s\n",
+		       path, fdt_strerror(ret));
+		return ret;
+	}
+	return 0;
+}
+
+#if (CONFIG_SECURE_BOOT_SRAM != 0) || (CONFIG_SECURE_RUN_SRAM != 0)
+static int ft_hs_fixup_sram(void *fdt, bd_t *bd)
+{
+	const char *path;
+	int offs;
+	int ret;
+	u32 temp[2];
+
+	/*
+	 * Update SRAM reservations on secure devices. The OCMC RAM
+	 * is always reserved for secure use from the start of that
+	 * memory region
+	 */
+	path = "/ocp/ocmcram at 40300000/sram-hs";
+	offs = fdt_path_offset(fdt, path);
+	if (offs < 0) {
+		debug("Node %s not found.\n", path);
+		return 0;
+	}
+
+	/* relative start offset */
+	temp[0] = cpu_to_fdt32(0);
+	/* reservation size */
+	temp[1] = cpu_to_fdt32(max(CONFIG_SECURE_BOOT_SRAM,
+				   CONFIG_SECURE_RUN_SRAM));
+	fdt_delprop(fdt, offs, "reg");
+	ret = fdt_setprop(fdt, offs, "reg", temp, 2 * sizeof(u32));
+	if (ret < 0) {
+		printf("Could not add reg property to node %s: %s\n",
+		       path, fdt_strerror(ret));
+		return ret;
+	}
+
+	return 0;
+}
+#else
+static int ft_hs_fixup_sram(void *fdt, bd_t *bd) { return 0; }
+#endif
+
+static void ft_hs_fixups(void *fdt, bd_t *bd)
+{
+	/* Check we are running on an HS/EMU device type */
+	if (GP_DEVICE != get_device_type()) {
+		if ((ft_hs_fixup_crossbar(fdt, bd) == 0) &&
+		    (ft_hs_disable_rng(fdt, bd) == 0) &&
+		    (ft_hs_fixup_sram(fdt, bd) == 0))
+			return;
+	} else {
+		printf("ERROR: Incorrect device type (GP) detected!");
+	}
+	/* Fixup failed or wrong device type */
+	hang();
+}
+#else
+static void ft_hs_fixups(void *fdt, bd_t *bd)
+{
+}
+#endif
+
+/*
+ * Place for general cpu/SoC FDT fixups. Board specific
+ * fixups should remain in the board files which is where
+ * this function should be called from.
+ */
+void ft_cpu_setup(void *fdt, bd_t *bd)
+{
+	ft_hs_fixups(fdt, bd);
+}

Adds an fdt.c file in that defines the ft_cpu_setup() function, which should be called from a board-specific ft_board_setup()). This ft_cpu_setup() will currently do nothing for non-secure (GP)
devices but contains pertinent updates for booting on secure (HS)
devices.

Update the omap5 Makefile to include the fdt.c in the build.

Signed-off-by Daniel Allred <[email protected]>

Signed-off-by Madan Srinivas <[email protected]>

Adds an fdt.c file in that defines the ft_cpu_setup() function, which should be called from a board-specific ft_board_setup()). This ft_cpu_setup() will currently do nothing for non-secure (GP)
devices but contains pertinent updates for booting on secure (HS)
devices.

Update the omap5 Makefile to include the fdt.c in the build.

Signed-off-by Daniel Allred <[email protected]>

Signed-off-by Madan Srinivas <[email protected]>

Adds the board specific ft_board_setup() functions that are called when CONFIG_OF_BOARD_SETUP is defined. These functions will currently just call the ft_cpu_setup() function.

Signed-off-by Daniel Allred <[email protected]>

Signed-off-by Madan Srinivas <[email protected]>

Adds the board specific ft_board_setup() functions that are called when CONFIG_OF_BOARD_SETUP is defined. These functions will currently just call the ft_cpu_setup() function.

Signed-off-by Daniel Allred <[email protected]>

Signed-off-by Madan Srinivas <[email protected]>

Adds the board specific ft_board_setup() functions that are called when CONFIG_OF_BOARD_SETUP is defined. These functions will currently just call the ft_cpu_setup() function.

Signed-off-by Daniel Allred <[email protected]>

Signed-off-by Madan Srinivas <[email protected]>

Adds CONFIG_OF_BOARD_SETUP to the config header files for dra7xx_evm and am57xx_evm.

Signed-off-by Daniel Allred <[email protected]>

Signed-off-by Madan Srinivas <[email protected]>

Adds CONFIG_OF_BOARD_SETUP to the config header files for dra7xx_evm and am57xx_evm.

Signed-off-by Daniel Allred <[email protected]>

Signed-off-by Madan Srinivas <[email protected]>

Adds CONFIG_OF_BOARD_SETUP to the config header files for dra7xx_evm and am57xx_evm.

Signed-off-by Daniel Allred <[email protected]>

Signed-off-by Madan Srinivas <[email protected]>

Adds new defconfig files for DRA7xx and AM57xx secure devices. These are the same as the non-secure parts, but with the addition of the CONFIG_TI_SECURE_DEVICE option set to 'y'.

Signed-off-by Daniel Allred <[email protected]>

Signed-off-by Madan Srinivas <[email protected]>

---
 configs/am57xx_hs_evm_defconfig | 20 ++++++++++++++++++++
 configs/dra72_hs_evm_defconfig  | 28 ++++++++++++++++++++++++++++
 configs/dra74_hs_evm_defconfig  | 27 +++++++++++++++++++++++++++
 3 files changed, 75 insertions(+)
 create mode 100644 configs/am57xx_hs_evm_defconfig
 create mode 100644 configs/dra72_hs_evm_defconfig
 create mode 100644 configs/dra74_hs_evm_defconfig

configs/am57xx_hs_evm_defconfig new file +20 -0

new file mode 100644
index 0000000..062471e
@@ -0,0 +1,20 @@
+CONFIG_ARM=y
+CONFIG_OMAP54XX=y
+CONFIG_TI_SECURE_DEVICE=y
+CONFIG_TARGET_BEAGLE_X15=y
+CONFIG_DM_SERIAL=y
+CONFIG_DM_GPIO=y
+CONFIG_SPL_STACK_R_ADDR=0x82000000
+CONFIG_DEFAULT_DEVICE_TREE="am57xx-beagle-x15"
+CONFIG_SPL=y
+CONFIG_SPL_STACK_R=y
+# CONFIG_CMD_IMLS is not set
+# CONFIG_CMD_FLASH is not set
+CONFIG_CMD_GPIO=y
+# CONFIG_CMD_SETEXPR is not set
+CONFIG_OF_CONTROL=y
+CONFIG_DM=y
+CONFIG_DM_MMC=y
+CONFIG_SPI_FLASH=y
+CONFIG_SPI_FLASH_BAR=y
+CONFIG_SYS_NS16550=y

configs/dra72_hs_evm_defconfig new file +28 -0

new file mode 100644
index 0000000..49f2b49
@@ -0,0 +1,28 @@
+CONFIG_ARM=y
+CONFIG_OMAP54XX=y
+CONFIG_TI_SECURE_DEVICE=y
+CONFIG_SYS_MALLOC_F_LEN=0x2000
+CONFIG_TARGET_DRA7XX_EVM=y
+CONFIG_DM_SERIAL=y
+CONFIG_DM_SPI=y
+CONFIG_DM_SPI_FLASH=y
+CONFIG_DM_GPIO=y
+CONFIG_SPL_STACK_R_ADDR=0x82000000
+CONFIG_DEFAULT_DEVICE_TREE="dra72-evm"
+CONFIG_SPL=y
+CONFIG_SPL_STACK_R=y
+# CONFIG_CMD_IMLS is not set
+# CONFIG_CMD_FLASH is not set
+CONFIG_CMD_GPIO=y
+# CONFIG_CMD_SETEXPR is not set
+CONFIG_OF_CONTROL=y
+CONFIG_DM=y
+CONFIG_SPI_FLASH=y
+CONFIG_SPI_FLASH_BAR=y
+CONFIG_SPI_FLASH_SPANSION=y
+CONFIG_SYS_NS16550=y
+CONFIG_TI_QSPI=y
+CONFIG_TIMER=y
+CONFIG_OMAP_TIMER=y
+CONFIG_USB=y
+CONFIG_USB_GADGET=y

configs/dra74_hs_evm_defconfig new file +27 -0

new file mode 100644
index 0000000..0339d7f
@@ -0,0 +1,27 @@
+CONFIG_ARM=y
+CONFIG_OMAP54XX=y
+CONFIG_TI_SECURE_DEVICE=y
+CONFIG_TARGET_DRA7XX_EVM=y
+CONFIG_DM_SERIAL=y
+CONFIG_DM_SPI=y
+CONFIG_DM_SPI_FLASH=y
+CONFIG_DM_GPIO=y
+CONFIG_SPL_STACK_R_ADDR=0x82000000
+CONFIG_DEFAULT_DEVICE_TREE="dra7-evm"
+CONFIG_SPL=y
+CONFIG_SPL_STACK_R=y
+# CONFIG_CMD_IMLS is not set
+# CONFIG_CMD_FLASH is not set
+CONFIG_CMD_GPIO=y
+# CONFIG_CMD_SETEXPR is not set
+CONFIG_OF_CONTROL=y
+CONFIG_DM=y
+CONFIG_SPI_FLASH=y
+CONFIG_SPI_FLASH_BAR=y
+CONFIG_SPI_FLASH_SPANSION=y
+CONFIG_SYS_NS16550=y
+CONFIG_TI_QSPI=y
+CONFIG_TIMER=y
+CONFIG_OMAP_TIMER=y
+CONFIG_USB=y
+CONFIG_USB_GADGET=y

Adds new defconfig files for DRA7xx and AM57xx secure devices. These are the same as the non-secure parts, but with the addition of the CONFIG_TI_SECURE_DEVICE option set to 'y'.

Signed-off-by Daniel Allred <[email protected]>

Signed-off-by Madan Srinivas <[email protected]>

Adds new defconfig files for DRA7xx and AM57xx secure devices. These are the same as the non-secure parts, but with the addition of the CONFIG_TI_SECURE_DEVICE option set to 'y'.

Signed-off-by Daniel Allred <[email protected]>

Signed-off-by Madan Srinivas <[email protected]>