DistroKit Mailinglist
 help / color / mirror / Atom feed
From: Lars Schmidt <l.schmidt@pengutronix.de>
To: distrokit@pengutronix.de
Cc: l.schmidt@pengutronix.de
Subject: [DistroKit] [PATCH v2 10/10] beagleplay: add initial platform config
Date: Tue, 24 Jun 2025 17:47:00 +0200	[thread overview]
Message-ID: <20250624-am62-beagleplay-v2-10-9fcf3e67a98b@pengutronix.de> (raw)
In-Reply-To: <20250624-am62-beagleplay-v2-0-9fcf3e67a98b@pengutronix.de>

The first stages of BeaglePlay's boot process use a 32bit
Cortex-R5 processor, whilst later stages use a 64bit Cortex-A53.
For this reason, barebox needs two stages to boot.
So we add barebox_r5 which needs selected_toolchain_r5 with
a 32bit toolchain for compilation.
TF-A does also need K3 as target platform and the extra arg
TARGET_BOARD=lite for compilation.

Signed-off-by: Lars Schmidt <l.schmidt@pengutronix.de>
---
 configs/platform-v8a/platformconfig | 14 +++++++++++---
 1 file changed, 11 insertions(+), 3 deletions(-)

diff --git a/configs/platform-v8a/platformconfig b/configs/platform-v8a/platformconfig
index 95ac6c8f1e58fec61d6ac7db40bf73fbc2c4ebee..23db066c688e637e0f3b550e03671e8423465cee 100644
--- a/configs/platform-v8a/platformconfig
+++ b/configs/platform-v8a/platformconfig
@@ -137,7 +137,7 @@ PTXCONF_KERNEL_IMAGE_RAW=y
 PTXCONF_KERNEL_IMAGE="Image"
 PTXCONF_KERNEL_DTB=y
 PTXCONF_KERNEL_DTS_PATH="${PTXDIST_PLATFORMCONFIG_SUBDIR}/dts:${KERNEL_DIR}/arch/${GENERIC_KERNEL_ARCH}/boot/dts"
-PTXCONF_KERNEL_DTS="armada-3720-community.dts freescale/imx8mm-evk.dts freescale/imx8mn-ddr4-evk.dts freescale/imx8mn-ddr4-evk.dts freescale/imx8mp-evk.dts freescale/imx8mq-evk.dts rockchip/rk3568-rock-3a.dts freescale/imx8mp-tqma8mpql-mba8mpxl.dts freescale/imx93-tqma9352-mba93xxca.dts"
+PTXCONF_KERNEL_DTS="armada-3720-community.dts freescale/imx8mm-evk.dts freescale/imx8mn-ddr4-evk.dts freescale/imx8mn-ddr4-evk.dts freescale/imx8mp-evk.dts freescale/imx8mq-evk.dts rockchip/rk3568-rock-3a.dts freescale/imx8mp-tqma8mpql-mba8mpxl.dts freescale/imx93-tqma9352-mba93xxca.dts ti/k3-am625-beagleplay.dts"
 # PTXCONF_KERNEL_DTBO is not set
 # PTXCONF_KERNEL_CODE_SIGNING is not set
 # PTXCONF_KERNEL_ZSTD is not set
@@ -176,6 +176,8 @@ PTXCONF_CONSOLE_SPEED="115200"
 # bootloaders                   
 #
 # PTXCONF_AT91BOOTSTRAP2 is not set
+PTXCONF_BAREBOX_R5=y
+PTXCONF_COMPILERPREFIX_R5="arm-v7a-linux-gnueabihf-"
 PTXCONF_BAREBOX_ARCH_STRING="arm"
 PTXCONF_BAREBOX_DEPENDENCIES=y
 PTXCONF_BAREBOX=y
@@ -213,9 +215,9 @@ PTXCONF_TF_A_MD5="dea016f3707117c7935a8a26433a1e46 5b90a1c21210702e64234a2beb79f
 PTXCONF_TF_A_ARCH_STRING="aarch64"
 PTXCONF_TF_A_ARM_ARCH_MAJOR_8=y
 PTXCONF_TF_A_ARM_ARCH_MAJOR=8
-PTXCONF_TF_A_PLATFORMS="imx8mq imx8mm imx8mn imx8mp imx93"
+PTXCONF_TF_A_PLATFORMS="imx8mq imx8mm imx8mn imx8mp imx93 k3"
 PTXCONF_TF_A_ARM_ARCH_MINOR=0
-PTXCONF_TF_A_EXTRA_ARGS="IMX_BOOT_UART_BASE=auto"
+PTXCONF_TF_A_EXTRA_ARGS="IMX_BOOT_UART_BASE=auto TARGET_BOARD=lite"
 PTXCONF_TF_A_ARTIFACTS="bl31.bin"
 
 #
@@ -238,9 +240,11 @@ PTXCONF_BLSPEC_ENTRY_APPENDROOT=y
 #
 # image creation options        
 #
+PTXCONF_IMAGE_BEAGLEPLAY=y
 # PTXCONF_IMAGE_BOOT_MLO is not set
 # PTXCONF_IMAGE_BOOT_VFAT is not set
 PTXCONF_IMAGE_ESPRESSOBIN=y
+PTXCONF_IMAGE_FIP_K3=y
 # PTXCONF_IMAGE_HD_VDI is not set
 # PTXCONF_IMAGE_HDIMG is not set
 PTXCONF_IMAGE_IMX8MM_EVK=y
@@ -310,6 +314,7 @@ PTXCONF_CODE_SIGNING_PROVIDER="devel"
 PTXCONF_CODE_SIGNING_PROVIDER_DEVEL=y
 PTXCONF_HOST_PTX_CODE_SIGNING_DEV=y
 PTXCONF_HOST_CMAKE=y
+PTXCONF_HOST_DOSFSTOOLS=y
 PTXCONF_HOST_DTC=y
 PTXCONF_HOST_E2FSPROGS=y
 PTXCONF_HOST_EXTRACT_CERT=y
@@ -348,6 +353,8 @@ PTXCONF_HOST_SYSTEM_PYTHON3_SETUPTOOLS=y
 PTXCONF_HOST_SYSTEM_PYTHON3_TOMLI=y
 PTXCONF_HOST_SYSTEM_PYTHON3_WHEEL=y
 PTXCONF_HOST_SYSTEM_PYTHON3=y
+PTXCONF_HOST_SYSTEM_PYTHON3_SYSTEM_PACKAGES=y
+PTXCONF_HOST_SYSTEM_PYTHON3_PYYAML=y
 PTXCONF_HOST_UTIL_LINUX=y
 PTXCONF_HOST_ZLIB=y
 PTXCONF_HOST_ZSTD=y
@@ -369,4 +376,5 @@ PTXCONF_FIRMWARE_ROCKCHIP_RK3568_SDRAM=y
 PTXCONF_FIRMWARE_ROCKCHIP_RK356x_BL31=y
 PTXCONF_FIRMWARE_ROCKCHIP_RK356x_BL32=y
 # PTXCONF_FIRMWARE_SENTINEL is not set
+PTXCONF_FIRMWARE_TI=y
 # end of non-free firmware blobs       

-- 
2.39.5




      parent reply	other threads:[~2025-06-24 16:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-24 15:46 [DistroKit] [PATCH v2 00/10] Add beagleplay support to DistroKit Lars Schmidt
2025-06-24 15:46 ` [DistroKit] [PATCH v2 01/10] v8a: barebox: bump version v2025.03.0 -> v2025.06.0 Lars Schmidt
2025-06-24 15:46 ` [DistroKit] [PATCH v2 02/10] beagleplay: k3: barebox needs part of tf-a firmware Lars Schmidt
2025-06-24 15:46 ` [DistroKit] [PATCH v2 03/10] tf-a: unify handling of firmware parts for barebox Lars Schmidt
2025-06-24 15:46 ` [DistroKit] [PATCH v2 04/10] beagleplay: firmware-ti: initial package Lars Schmidt
2025-06-24 15:46 ` [DistroKit] [PATCH v2 05/10] beagleplay: barebox: first stage bootloader for Cortex-R5 Lars Schmidt
2025-06-24 15:46 ` [DistroKit] [PATCH v2 06/10] beagleplay: fipimage: add fip image for K3 Lars Schmidt
2025-06-24 15:46 ` [DistroKit] [PATCH v2 07/10] beagleplay: add full image including bootloaders and rootfs Lars Schmidt
2025-06-24 15:46 ` [DistroKit] [PATCH v2 08/10] beagleplay: add initial kernel configuration Lars Schmidt
2025-06-24 15:46 ` [DistroKit] [PATCH v2 09/10] beagleplay: barebox: get second boot stage running Lars Schmidt
2025-06-24 15:47 ` Lars Schmidt [this message]

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=20250624-am62-beagleplay-v2-10-9fcf3e67a98b@pengutronix.de \
    --to=l.schmidt@pengutronix.de \
    --cc=distrokit@pengutronix.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