NetCube-Systems-Austria/kumquat-buildroot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
e03513c773
kumquat-buildroot/configs/avenger96_defconfig

36 lines
1.5 KiB
Plaintext
Raw Normal View History

configs/avenger96_defconfig: add support for Arrow Avenger96 board Very similar to the other stm32mp157-based boards, except that we use the multi_v7 defconfig for ease of maintenance. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2021-02-07 22:52:27 +01:00
BR2_arm=y
BR2_cortex_a7=y
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_5_8=y
configs/avenger96_defconfig: downgrade to TF-A v2.5 Commit 27bf08e4addb78 (configs/avenger96_defconfig: bump ATF version to 2.9 for binutils 2.39+ support) bumped TF-A, but it unfortunately does not boot and instead dies with a panic: NOTICE: CPU: STM32MP157AAC Rev.B NOTICE: Model: Arrow Electronics STM32MP157A Avenger96 board ERROR: nvmem node board_id not found INFO: PMIC version = 0x10 ERROR: Product_below_2v5=1: ERROR: HSLVEN update is destructive, ERROR: no update as VDD > 2.7V PANIC at PC : 0x2fff086f Exception mode=0x00000016 at: 0x2fff086f Instead use v2.5 to match the other stm32mp1 boards and use the same E=0 -Werror workaround. The avenger95 support is unfortunately broken since v2.3 with the introduction of authentication support, so add a patch to the DTS to fix that. Notice that the authentication support was reworked in v2.7 so it is skipped for the mp157a variant used on the avenger96, so the patch is not upstreamable. While we're at it, also drop the debug option for consistency with the other boards. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2023-11-05 19:37:19 +01:00
BR2_GLOBAL_PATCH_DIR="board/arrow/avenger96/patches"
configs/avenger96_defconfig: add support for Arrow Avenger96 board Very similar to the other stm32mp157-based boards, except that we use the multi_v7 defconfig for ease of maintenance. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2021-02-07 22:52:27 +01:00
BR2_ROOTFS_OVERLAY="board/arrow/avenger96/overlay/"
BR2_ROOTFS_POST_IMAGE_SCRIPT="board/stmicroelectronics/common/stm32mp157/post-image.sh"
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_VERSION=y
BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="5.8.13"
BR2_LINUX_KERNEL_DEFCONFIG="multi_v7"
BR2_LINUX_KERNEL_DTS_SUPPORT=y
BR2_LINUX_KERNEL_INTREE_DTS_NAME="stm32mp157a-dhcor-avenger96"
BR2_LINUX_KERNEL_INSTALL_TARGET=y
configs/avenger96_defconfig: linux build needs host-openssl Fixes the gitlab build: https://gitlab.com/buildroot.org/buildroot/-/jobs/1019385566/ HOSTCC scripts/extract-cert scripts/extract-cert.c:21:25: fatal error: openssl/bio.h: No such file or directory Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2021-02-11 14:23:11 +01:00
BR2_LINUX_KERNEL_NEEDS_HOST_OPENSSL=y
configs/avenger96_defconfig: add support for Arrow Avenger96 board Very similar to the other stm32mp157-based boards, except that we use the multi_v7 defconfig for ease of maintenance. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2021-02-07 22:52:27 +01:00
BR2_TARGET_ROOTFS_EXT2=y
BR2_TARGET_ROOTFS_EXT2_4=y
BR2_TARGET_ROOTFS_EXT2_SIZE="120M"
# BR2_TARGET_ROOTFS_TAR is not set
BR2_TARGET_ARM_TRUSTED_FIRMWARE=y
BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_VERSION=y
configs/avenger96_defconfig: downgrade to TF-A v2.5 Commit 27bf08e4addb78 (configs/avenger96_defconfig: bump ATF version to 2.9 for binutils 2.39+ support) bumped TF-A, but it unfortunately does not boot and instead dies with a panic: NOTICE: CPU: STM32MP157AAC Rev.B NOTICE: Model: Arrow Electronics STM32MP157A Avenger96 board ERROR: nvmem node board_id not found INFO: PMIC version = 0x10 ERROR: Product_below_2v5=1: ERROR: HSLVEN update is destructive, ERROR: no update as VDD > 2.7V PANIC at PC : 0x2fff086f Exception mode=0x00000016 at: 0x2fff086f Instead use v2.5 to match the other stm32mp1 boards and use the same E=0 -Werror workaround. The avenger95 support is unfortunately broken since v2.3 with the introduction of authentication support, so add a patch to the DTS to fix that. Notice that the authentication support was reworked in v2.7 so it is skipped for the mp157a variant used on the avenger96, so the patch is not upstreamable. While we're at it, also drop the debug option for consistency with the other boards. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2023-11-05 19:37:19 +01:00
BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_VERSION_VALUE="v2.5"
configs/avenger96_defconfig: add support for Arrow Avenger96 board Very similar to the other stm32mp157-based boards, except that we use the multi_v7 defconfig for ease of maintenance. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2021-02-07 22:52:27 +01:00
BR2_TARGET_ARM_TRUSTED_FIRMWARE_PLATFORM="stm32mp1"
configs/avenger96_defconfig: downgrade to TF-A v2.5 Commit 27bf08e4addb78 (configs/avenger96_defconfig: bump ATF version to 2.9 for binutils 2.39+ support) bumped TF-A, but it unfortunately does not boot and instead dies with a panic: NOTICE: CPU: STM32MP157AAC Rev.B NOTICE: Model: Arrow Electronics STM32MP157A Avenger96 board ERROR: nvmem node board_id not found INFO: PMIC version = 0x10 ERROR: Product_below_2v5=1: ERROR: HSLVEN update is destructive, ERROR: no update as VDD > 2.7V PANIC at PC : 0x2fff086f Exception mode=0x00000016 at: 0x2fff086f Instead use v2.5 to match the other stm32mp1 boards and use the same E=0 -Werror workaround. The avenger95 support is unfortunately broken since v2.3 with the introduction of authentication support, so add a patch to the DTS to fix that. Notice that the authentication support was reworked in v2.7 so it is skipped for the mp157a variant used on the avenger96, so the patch is not upstreamable. While we're at it, also drop the debug option for consistency with the other boards. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2023-11-05 19:37:19 +01:00
BR2_TARGET_ARM_TRUSTED_FIRMWARE_ADDITIONAL_VARIABLES="STM32MP_SDMMC=1 AARCH32_SP=sp_min DTB_FILE_NAME=stm32mp157a-avenger96.dtb E=0"
configs/avenger96_defconfig: add support for Arrow Avenger96 board Very similar to the other stm32mp157-based boards, except that we use the multi_v7 defconfig for ease of maintenance. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2021-02-07 22:52:27 +01:00
BR2_TARGET_ARM_TRUSTED_FIRMWARE_IMAGES="*.stm32"
BR2_TARGET_ARM_TRUSTED_FIRMWARE_NEEDS_DTC=y
BR2_TARGET_UBOOT=y
BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y
BR2_TARGET_UBOOT_CUSTOM_VERSION=y
BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE="2020.07"
BR2_TARGET_UBOOT_BOARD_DEFCONFIG="stm32mp15_trusted"
# BR2_TARGET_UBOOT_FORMAT_BIN is not set
BR2_TARGET_UBOOT_FORMAT_STM32=y
boot/u-boot: fix u-boot.stm32 creation on newer version As reported in commit [1] of the U-Boot project, the config.mk file has been suppressed in order to use binman to manage FIT generation. Therefore, the "u-boot.stm32" make target should no longer be used with recent versions of U-Boot. The configuration option added by this comit allows the creation of the u-boot.stm32 image for both recent versions of U-Boot, which use binman, and older versions. Legacy handling would have suggested that this new option should "default y" to preserve existing behavior, but as moving forward all U-Boot new versions will no longer need this u-boot.stm32 target, it probably makes sense here to not comply with this backward compatibility rule, as an exception. [1] 5564b4cd4d5c69 ("stm32mp: add binman support for STM32MP15x") Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com> Tested-by: David Reaver <me@davidreaver.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2023-07-03 18:01:48 +02:00
BR2_TARGET_UBOOT_BUILD_FORMAT_STM32_LEGACY=y
configs/avenger96_defconfig: add support for Arrow Avenger96 board Very similar to the other stm32mp157-based boards, except that we use the multi_v7 defconfig for ease of maintenance. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2021-02-07 22:52:27 +01:00
BR2_TARGET_UBOOT_CUSTOM_MAKEOPTS="DEVICE_TREE=stm32mp15xx-dhcor-avenger96"
BR2_PACKAGE_HOST_GENIMAGE=y
Reference in New Issue Copy Permalink