How To Build HMI SDK¶

Introduction¶

HMI SDK is a quick and easy HMI Application development environment.

To modify Linux component, you need to build HMI SDK from source code.
HMI SDK source code will generate same Linux environment as HMI SDK.

This page explains how to build HMI SDK source code.
After you have completed this page, you would be able to change the source code and customize Linux environment (i.e., memory map, additional OSS etc...).

Step 1: Obtain HMI SDK Yocto recipe¶

Download HMI SDK Yocto recipe and pre-built binary image package from below link.

In the build process, source code of modules in the HMI SDK will be downloaded via network connection, but you can use the same source code used for creating the HMI SDK binaries. Download HMI SDK source code from below link.

Get HMI SDK
Source code package

Step 2: Build HMI SDK source code¶

This step explains how to build Linux environment with HMI SDK source code.

1. Install the required packages

   Install some packages into your Linux PC, which are necessary in the following steps.

   sudo apt-get update
   sudo apt-get install gawk wget git-core diffstat unzip texinfo gcc-multilib build-essential chrpath socat cpio python3 python3-pip python3-pexpect xz-utils debianutils iputils-ping libsdl1.2-dev xterm p7zip-full libyaml-dev libssl-dev bmap-tools
   

2. Set up your git environment

   Set up your git environment if you have never done it.

   git config --global user.email "<Your email address>"
   git config --global user.name "<Your user name>"
   

   Note

   For more information, refer to Yocto Project Quick Build.

3. Set environment variables

   Set the following environment variables.

   RZ/G2LRZ/G2LCRZ/G2UL

   export WORK=<A directory path for building>
   export PLATFORM=rzg2l
   export BOARD=smarc-rzg2l
   export SDK_PKG_DIR=<A directory path for HMI SDK source code packages>
   

   export WORK=<A directory path for building>
   export PLATFORM=rzg2l
   export BOARD=smarc-rzg2lc
   export SDK_PKG_DIR=<A directory path for HMI SDK source code packages>
   

   export WORK=<A directory path for building>
   export PLATFORM=rzg2l
   export BOARD=smarc-rzg2ul
   export SDK_PKG_DIR=<A directory path for HMI SDK source code packages>
   

   Note

   The directory set to SDK_PKG_DIR shall include the HMI SDK packages such as RTK0EF0195F*SJ_*_yocto-and-pre-built-image.zip and RTK0EF0195F*SJ_linux-src.zip.

4. Extract Yocto recipe package

   Decompress the Yocto recipe and pre-built binary image package, create a working directory, and extract Yocto recipe package.

   cd ${SDK_PKG_DIR}
   unzip RTK0EF0195F*SJ_*_yocto-and-pre-built-image.zip
   

   mkdir -p ${WORK}
   cd ${WORK}
   tar xf ${SDK_PKG_DIR}/RTK0EF0195F*SJ_*_yocto-and-pre-built-image/yocto_recipe_rzg2_hmi-sdk_v*.tar.gz --strip-components 1
   

5. Initialize build environment

   Run an environment setup script as follows.

   cd ${WORK}
   TEMPLATECONF=${PWD}/meta-renesas/meta-${PLATFORM}/docs/template/conf/ source poky/oe-init-build-env build
   

6. Add layers

   Add necessary Yocto meta-layers layer as follows.

   RZ/G2LRZ/G2LCRZ/G2UL

   cd ${WORK}/build
   bitbake-layers add-layer ../meta-rz-features/meta-rz-graphics
   bitbake-layers add-layer ../meta-rz-features/meta-rz-codecs
   bitbake-layers add-layer ../meta-clang
   bitbake-layers add-layer ../meta-browser/meta-chromium
   bitbake-layers add-layer ../meta-openembedded/meta-networking
   bitbake-layers add-layer ../meta-browser-hwdecode
   bitbake-layers add-layer ../meta-rz-demos
   

   cd ${WORK}/build
   bitbake-layers add-layer ../meta-rz-features/meta-rz-graphics
   bitbake-layers add-layer ../meta-clang
   bitbake-layers add-layer ../meta-browser/meta-chromium
   bitbake-layers add-layer ../meta-openembedded/meta-networking
   bitbake-layers add-layer ../meta-browser-hwdecode
   bitbake-layers add-layer ../meta-rz-demos
   

   cd ${WORK}/build
   bitbake-layers add-layer ../meta-rz-demos
   

7. Set up environment for offline build

   This step is configuration for offline building.

   If you would like to get source code via network when you build the HMI SDK, skip this step.

   Change the environment variable BB_NO_NETWORK in local.conf from 0 to 1 using sed command.

   cd ${WORK}/build
   sed -i "s|\(BB_NO_NETWORK =.*\)\"0\"|\1\"1\"|" "conf/local.conf"
   

   Decompress source code package and set it into the build environment.

   cd ${SDK_PKG_DIR}
   unzip RTK0EF0195F*SJ_linux-src.zip
   cd ${SDK_PKG_DIR}/RTK0EF0195F*SJ_linux-src/
   7z x oss-souce-code-pkg_rzg2_hmi-sdk_v*.7z
   mv downloads/ ${WORK}/build/
   

8. Modify configurations for build environment

   Add IMAGE_INSTALL_append and other settings to local.conf as follows.

   RZ/G2LRZ/G2LCRZ/G2UL

   cd ${WORK}/build
   sed -i '$aIMAGE_INSTALL_append = \" packagegroup-lvgl-demo packagegroup-benchmark-tools packagegroup-chromium-demo packagegroup-rzg-hmi-sdk-demo \"' "conf/local.conf"
   sed -i '$aWHITELIST_GPL-3.0 += \" glmark2 \"' "conf/local.conf"
   sed -i '$aPREFERRED_VERSION_nodejs-native = \"14.%\"' "conf/local.conf"
   

   cd ${WORK}/build
   sed -i '$aIMAGE_INSTALL_append = \" packagegroup-lvgl-demo packagegroup-benchmark-tools packagegroup-chromium-demo packagegroup-rzg-hmi-sdk-demo \"' "conf/local.conf"
   sed -i '$aWHITELIST_GPL-3.0 += \" glmark2 \"' "conf/local.conf"
   sed -i '$aPREFERRED_VERSION_nodejs-native = \"14.%\"' "conf/local.conf"
   

   cd ${WORK}/build
   sed -i '$aIMAGE_INSTALL_append = \" packagegroup-lvgl-demo packagegroup-benchmark-tools packagegroup-rzg-hmi-sdk-demo \"' "conf/local.conf"
   

9. Build images

   Run bitbake command to build images.

   RZ/G2LRZ/G2LCRZ/G2UL

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

   After the above build process, change the setting of EMMC from '1' to '0'.

   cd $WORK/build/tmp/work-shared/${BOARD}/kernel-source
   vi arch/arm64/boot/dts/renesas/rzg2l-smarc-som.dtsi
       (change EMMC setting)
           before) #define EMMC    1
           after)  #define EMMC    0
   

   After the change above, you need to have additional build process as follows:

   cd $WORK/build
   MACHINE=${BOARD} bitbake linux-renesas -C compile
   MACHINE=${BOARD} bitbake core-image-weston
   

   Note

   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
   

   After the above build process, change the setting of SW_SD0_DEV_SEL from '1' to '0'.

   cd $WORK/build/tmp/work-shared/${BOARD}/kernel-source
   vi arch/arm64/boot/dts/renesas/r9a07g044c2-smarc.dts
       (change SW_SD0_DEV_SEL setting)
           before) #define SW_SD0_DEV_SEL 1
           after)  #define SW_SD0_DEV_SEL 0
   

   After the change above, you need to have additional build process as follows:

   cd $WORK/build
   MACHINE=${BOARD} bitbake linux-renesas -C compile
   MACHINE=${BOARD} bitbake core-image-weston
   

   Note

   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
   

   Note

   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
   

   Note

   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/