Re: [isar-cip-core][PATCH] Add support Plat'Home OpenBlocks IoT VX2

Jan Kiszka
2023-08-28T06:43:57Z

On 23.08.23 04:17, Nobuhiro Iwamatsu wrote:
> From: Nobuhiro Iwamatsu <iwamatsu@nigauri.org>
>
> This adds configuration files to support Plat'Home OpenBlocks IoT VX2.
>
> CC: Masato Minda <minmin@plathome.co.jp>
> Signed-off-by: Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp>
> ---
> Kconfig | 4 ++++
> conf/machine/openblocks-iot-vx2.conf | 15 +++++++++++++++
> kas/board/openblocks-iot-vx2.yml | 15 +++++++++++++++
> wic/openblocks-iot-vx2.wks | 15 +++++++++++++++
> 4 files changed, 49 insertions(+)
> create mode 100644 conf/machine/openblocks-iot-vx2.conf
> create mode 100644 kas/board/openblocks-iot-vx2.yml
> create mode 100644 wic/openblocks-iot-vx2.wks
>
> diff --git a/Kconfig b/Kconfig
> index ec49631..778acf6 100644
> --- a/Kconfig
> +++ b/Kconfig
> @@ -67,6 +67,9 @@ config TARGET_QEMU_RISCV64
> bool "QEMU RISC-V 64-bit (riscv64)"
> select ARCH_RISCV64
>
> +config TARGET_OBS_IOT_VX2
> + bool "Plat'Home OpenBlocks IoT VX2"
> + select ARCH_AMD64
> endchoice
>
> config KAS_INCLUDE_BOARD
> @@ -79,6 +82,7 @@ config KAS_INCLUDE_BOARD
> default "kas/board/bbb.yml" if TARGET_BBB
> default "kas/board/iwg20m.yml" if TARGET_IWG20D
> default "kas/board/qemu-riscv64.yml" if TARGET_QEMU_RISCV64
> + default "kas/board/openblocks-iot-vx2.yml" if TARGET_OBS_IOT_VX2
>
> comment "Kernel options"
>
> diff --git a/conf/machine/openblocks-iot-vx2.conf b/conf/machine/openblocks-iot-vx2.conf
> new file mode 100644
> index 0000000..a9bf65d
> --- /dev/null
> +++ b/conf/machine/openblocks-iot-vx2.conf
> @@ -0,0 +1,15 @@
> +#
> +# CIP Core, generic profile
> +#
> +# Copyright (c) Siemens AG, 2019
> +# Copyright (c) TOSHIBA CORPORATION, 2023
> +#
> +# SPDX-License-Identifier: MIT
> +#
> +
> +DISTRO_ARCH = "amd64"
> +
> +IMAGE_FSTYPES ?= "wic"
> +IMAGER_INSTALL += "${GRUB_BOOTLOADER_INSTALL}"
> +USE_CIP_KERNEL_CONFIG = "1"
> +KERNEL_DEFCONFIG = "cip-kernel-config/${KERNEL_DEFCONFIG_VERSION}/x86/plathome_obsvx2_defconfig"
> diff --git a/kas/board/openblocks-iot-vx2.yml b/kas/board/openblocks-iot-vx2.yml
> new file mode 100644
> index 0000000..6951e2e
> --- /dev/null
> +++ b/kas/board/openblocks-iot-vx2.yml
> @@ -0,0 +1,15 @@
> +#
> +# CIP Core, generic profile
> +#
> +# TOSHIBA CORPORATION, 2023
> +#
> +# Authors:
> +# Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp>
> +#
> +# SPDX-License-Identifier: MIT
> +#
> +
> +header:
> + version: 12
> +
> +machine: openblocks-iot-vx2
> diff --git a/wic/openblocks-iot-vx2.wks b/wic/openblocks-iot-vx2.wks
> new file mode 100644
> index 0000000..3050684
> --- /dev/null
> +++ b/wic/openblocks-iot-vx2.wks
> @@ -0,0 +1,15 @@
> +#
> +# CIP Core, generic profile
> +#
> +# Copyright (c) Siemens AG, 2019
> +#
> +# SPDX-License-Identifier: MIT
> +#
> +# Based wic/simatic-ipc227e.wks
> +#
> +
> +part /boot --source bootimg-efi-isar --sourceparams "loader=grub-efi" --label efi --part-type EF00 --align 1024
> +
> +part / --source rootfs --fstype ext4 --mkfs-extraopts "-T default" --label platform --align 1024 --use-uuid
> +
> +bootloader --ptable gpt --timeout 2 --append "console=ttyS0,115200"

I wonder if we should (and could) consolidate the x86 configs. Or does
this target come with any specialties?

Jan

--
Siemens AG, Technology
Linux Expert Center