Skip to content

How to Update Linux Packages in the HMI SDK

Page Information

The information provided on this page has been verified using the following SDK versions and evaluation kits (EVKs):

  • HMI SDK v2.3.1.0 (Yocto 3.1.31 (dunfell), kernel 5.10) using RZ/G2L, RZ/G2LC, and RZ/G2UL EVK

Last updated: December 23, 2025

The HMI SDK is configured using RZ/G Verified Linux Package (hereinafter referred to as "VLP/G") or Board Support Package (hereinafter referred to as "BSP"). When the VLP/G or the BSP in the HMI SDK is updated to fix issues, you can replace the VLP/G or the BSP with new one.

Updates of VLP/G v3.0.7

HMI SDK v2.3.1.0 uses VLP/G v3.0.7, but some issues were detected in the VLP/G. VLP/G v3.0.7-update3 was released to address vulnerabilities and improve drivers in VLP/G v3.0.7.

Changes

Changes in VLP/G v3.0.7-update3 are listed below.

FeaturesDescription
KernelThe VLP/G v3.0.7-update3 includes several minor kernel fixes.
U-BootUpdate vmmc and vqmmc settings for eSD mode. Configure U-Boot to set a random MAC address.
CVE-2024-53104Fix out-of-bounds write by skipping UVC_VS_UNDEFINED frame parsing in uvc_parse_format (media: uvcvideo).
CVE-2025-4802The VLP/G v3.0.7-update3 includes the patch for the glibc vulnerability.
glib-2.0Updated to glib2.0_2.58.3-2+deb10u8.
multimediaUpdate runtime dependencies, fix MMNGR issues, and add GRAY10_LE64 support to GStreamer.
attr, binutils, busybox, coreutils, gcc-8, gnupg2, gzip, kbd, libassuan, libgcrypt20, libunistring, nss, openssh, openssl, perl, pkg-config, pseudo, quiltSwitch to the ELTS mirror to prevent removal from the Debian Buster mirror:
- attr, coreutils, gcc-8, gnupg2, gzip, kbd, libassuan, libgcrypt20, libunistring, nss, perl, pkg-config, pseudo, quilt
Upgraded packages:
- binutils 2.31.1-16 -> 2.31.1-16+deb10u1
- busybox 1.30.1-4 -> 1.30.1-4+deb10u1
- openssh 7.9p1-10+deb10u2 -> 7.9p1-10+deb10u5
- openssl 1.1.1n-0+deb10u6 -> 1.1.1n-0+deb10u7
SSI DriverFix random recording failures in full-duplex communication mode (RZ/G2L Series and RZ/G3S).
PCIe DriverEnables NVMe PCIe support (RZ/G3S only).

For more detailed information about VLP/G v3.0.7-update3, get RZ/G Verified Linux Package v3.0.7 (RTK0EF0045Z0021AZJ-v3.0.7-update3) and check the release note in the package.

How to Update VLP/G from v3.0.7 to v3.0.7-update3

To update VLP/G v3.0.7 in HMI SDK v2.3.1.0, build the HMI SDK by following the instructions below.

i. First, perform instructions at step 1 and #1 through #4 at step 2 in How To Build HMI SDK.

Note

You do not need to download the HMI SDK source code package at step 1. Due to the update of the VLP/G, source codes of some modules were updated. So, you will get new source codes over a network in this build process.

ii. Next, replace meta-renesas with new one as follows:

cd ${WORK}
rm -rf meta-renesas
git clone https://github.com/renesas-rz/meta-renesas.git
cd meta-renesas/
git checkout -b tmp BSP-3.0.7-update3

iii. Then, proceed with #5 through #8 at step 2 in How To Build HMI SDK, but skip #7 at step 2.

Note

You can skip #7 at step 2 because it shows instructions for offline build using the source code package.

iv. Finally, run bitbake command to build images.

cd ${WORK}/build
MACHINE=${BOARD} bitbake core-image-weston

Note

A change of EMMC setting in #9 at step 2 is no longer necessary for VLP/G v3.0.7-update3.

If you need to create an SDK toolchain, run bitbake command as follows.

cd ${WORK}/build
MACHINE=${BOARD} bitbake core-image-weston -c populate_sdk

cd ${WORK}/build
MACHINE=${BOARD} bitbake core-image-weston

Note

A change of SW_SD0_DEV_SEL setting in #9 at step 2 is no longer necessary for VLP/G v3.0.7-update3.

If you need to create an SDK toolchain, run bitbake command as follows.

cd ${WORK}/build
MACHINE=${BOARD} bitbake core-image-weston -c populate_sdk

cd ${WORK}/build
MACHINE=${BOARD} bitbake core-image-bsp

If you need to create an SDK toolchain, run bitbake command as follows.

cd ${WORK}/build
MACHINE=${BOARD} bitbake core-image-bsp -c populate_sdk

After building images or SDK toolchain, you can find them in the following directories, respectively.

  • Images: ${WORK}/build/tmp/deploy/images/${BOARD}/
  • SDK toolchain: ${WORK}/build/tmp/deploy/sdk/