RE: [isar-cip-core][PATCH] Add support for Renesas rzt2h-evk platform

Hi Jan,

> -----Original Message-----
> From: Jan Kiszka <[email protected]>
> Sent: Monday, July 6, 2026 4:13 PM
> To: Hung Tran <[email protected]>; [email protected]
> Subject: Re: [isar-cip-core][PATCH] Add support for Renesas rzt2h-evk
> platform
> 
> On 30.06.26 10:57, Hung Tran wrote:
> > rzt2h-evk is the new reference platform for CIP project.
> > It uses Renesas RZ/T2H SoC, based on armv8.2 architecture.
> > This platform is only supported from CIP Linux 6.12.
> >
> > Signed-off-by: Hung Tran <[email protected]>
> > ---
> >  Kconfig                           | 14 ++++++++++----
> >  conf/machine/rzt2h-evk.conf       | 18 ++++++++++++++++++
> >  kas/board/rzt2h-evk.yml           | 15 +++++++++++++++
> >  wic/rzt2h-evk-efibootguard.wks.in | 14 ++++++++++++++
> >  wic/rzt2h-evk.wks                 | 17 +++++++++++++++++
> >  5 files changed, 74 insertions(+), 4 deletions(-)  create mode 100644
> > conf/machine/rzt2h-evk.conf  create mode 100644
> > kas/board/rzt2h-evk.yml  create mode 100644
> > wic/rzt2h-evk-efibootguard.wks.in  create mode 100644
> > wic/rzt2h-evk.wks
> >
> > diff --git a/Kconfig b/Kconfig
> > index 44f2337..879a31d 100644
> > --- a/Kconfig
> > +++ b/Kconfig
> > @@ -119,6 +119,11 @@ config TARGET_BEAGLEV_FIRE
> >  	select ARCH_RISCV64
> >  	select HAS_SWUPDATE
> >
> > +config TARGET_RZT2H
> > +	bool "RZ/T2H EVK"
> > +	select ARCH_ARM64
> > +	select HAS_SWUPDATE
> > +
> >  endchoice
> >
> >  config KAS_INCLUDE_BOARD
> > @@ -134,6 +139,7 @@ config KAS_INCLUDE_BOARD
> >  	default "kas/board/iwg20m.yml" if TARGET_IWG20D
> >  	default "kas/board/qemu-riscv64.yml" if TARGET_QEMU_RISCV64
> >  	default "kas/board/beaglev-fire.yml" if TARGET_BEAGLEV_FIRE
> > +	default "kas/board/rzt2h-evk.yml" if TARGET_RZT2H
> >
> >  comment "Kernel options"
> >
> > @@ -144,21 +150,21 @@ choice
> >  config KERNEL_4_4
> >  	bool "Kernel 4.4.x-cip"
> >  	depends on !ARCH_ARM64 && !ARCH_RISCV64
> > -	depends on !TARGET_TI_AM62PX_SK
> > +	depends on !TARGET_TI_AM62PX_SK && !TARGET_RZT2H
> 
> Hmm, both target exclusions should actually be redundant to !ARCH_ARM64
> - missed that before.

You are right, I did not notice that either.
I will resend the patch with this part removed.

> 
> >  	depends on !DEBIAN_TRIXIE
> >
> >  config KERNEL_4_19
> >  	bool "Kernel 4.19.x-cip"
> >  	depends on !ARCH_RISCV64
> > -	depends on !TARGET_TI_AM62PX_SK
> > +	depends on !TARGET_TI_AM62PX_SK && !TARGET_RZT2H
> >
> >  config KERNEL_5_10
> >  	bool "Kernel 5.10.x-cip"
> > -	depends on !TARGET_TI_AM62PX_SK && !TARGET_BEAGLEV_FIRE
> > +	depends on !TARGET_TI_AM62PX_SK && !TARGET_BEAGLEV_FIRE &&
> > +!TARGET_RZT2H
> >
> >  config KERNEL_6_1
> >  	bool "Kernel 6.1.x-cip"
> > -	depends on !TARGET_TI_AM62PX_SK && !TARGET_BEAGLEV_FIRE
> > +	depends on !TARGET_TI_AM62PX_SK && !TARGET_BEAGLEV_FIRE &&
> > +!TARGET_RZT2H
> >
> >  config KERNEL_6_12
> >  	bool "Kernel 6.12.x-cip"
> > diff --git a/conf/machine/rzt2h-evk.conf b/conf/machine/rzt2h-evk.conf
> > new file mode 100644 index 0000000..5cfbfa5
> > --- /dev/null
> > +++ b/conf/machine/rzt2h-evk.conf
> > @@ -0,0 +1,18 @@
> > +#
> > +# CIP Core, generic profile
> > +#
> > +# Copyright (c) 2026 Renesas Electronics Corporation # # Authors:
> > +#  Hung Tran <[email protected]> # # SPDX-License-Identifier:
> > +MIT #
> > +
> > +DISTRO_ARCH = "arm64"
> > +
> > +IMAGE_FSTYPES ?= "wic"
> > +
> > +USE_CIP_KERNEL_CONFIG = "1"
> > +DTB_FILES = "r9a09g077m44-rzt2h-evk.dtb"
> > +IMAGE_BOOT_FILES = "${KERNEL_IMAGE} ${DTB_FILES}"
> > diff --git a/kas/board/rzt2h-evk.yml b/kas/board/rzt2h-evk.yml new
> > file mode 100644 index 0000000..90261dc
> > --- /dev/null
> > +++ b/kas/board/rzt2h-evk.yml
> > @@ -0,0 +1,15 @@
> > +#
> > +# CIP Core, generic profile
> > +#
> > +# Copyright (c) 2026 Renesas Electronics Corporation # # Authors:
> > +#  Hung Tran <[email protected]> # # SPDX-License-Identifier:
> > +MIT #
> > +
> > +header:
> > +  version: 14
> > +
> > +machine: rzt2h-evk
> > diff --git a/wic/rzt2h-evk-efibootguard.wks.in b/wic/rzt2h-evk-
> efibootguard.wks.in
> > new file mode 100644
> > index 0000000..ca18bec
> > --- /dev/null
> > +++ b/wic/rzt2h-evk-efibootguard.wks.in
> > @@ -0,0 +1,14 @@
> > +# Copyright (c) 2026 Renesas Electronics Corporation
> > +#
> > +# SPDX-License-Identifier: MIT
> > +
> > +include ebg-sysparts.inc
> > +
> > +part --source rawcopy --sourceparams
> "file=${IMAGE_FULLNAME}.${RO_ROOTFS_TYPE}" --align 1024 --fixed-size 1G --
> uuid "${ABROOTFS_PART_UUID_A}" --part-type 0FC63DAF-8483-4772-8E79-
> 3D69D8477DE4 --part-name systema
> > +part --source empty --sourceparams "${ABROOTFS_SOURCEPARAMS_B}" --align
> 1024 --fixed-size 1G --uuid "${ABROOTFS_PART_UUID_B}" --part-type 0FC63DAF-
> 8483-4772-8E79-3D69D8477DE4 --part-name systemb
> > +
> > +# var and optional home are extra partitions
> > +${WIC_HOME_PARTITION}
> > +${WIC_VAR_PARTITION}
> > +
> > +bootloader --ptable gpt
> > diff --git a/wic/rzt2h-evk.wks b/wic/rzt2h-evk.wks
> > new file mode 100644
> > index 0000000..4a4af6c
> > --- /dev/null
> > +++ b/wic/rzt2h-evk.wks
> > @@ -0,0 +1,17 @@
> > +#
> > +# CIP Core, generic profile
> > +#
> > +# Copyright (c) 2026 Renesas Electronics Corporation
> > +#
> > +# Authors:
> > +#  Hung Tran <[email protected]>
> > +#
> > +# SPDX-License-Identifier: MIT
> > +#
> > +
> > +part /boot --source bootimg-partition --ondisk mmcblk0 --fstype vfat --
> label boot --align 1 --size 32M --extra-space 0 --fsuuid 0x4321dcba --use-
> uuid
> > +
> > +# Rootfs partition
> > +part / --source rootfs --ondisk mmcblk0 --fstype ext4 --label root --align
> 1024 --size 2G --active --fsuuid 1f55d66a-40d8-11ee-be56-0242ac120002 --use-
> uuid
> > +
> > +bootloader --ptable gpt
> 
> Thanks for adding this. I think we also want CI coverage for this.

Right, I forgot about CI again.
I will add CI when resend.

> 
> Are there plans to enable secure boot & Co., like we have for the am62px?

Hum, currently there is no plan for those features.
I will check whether supporting them is feasible.
However, currently upstream support for the RZ/T2H in TF-A and U-Boot is not available yet. Therefore, even if support is possible, it will take some time.

> 
> Jan
> 
> --
> Siemens AG, Foundational Technologies
> Linux Expert Center