R-Car/Boards/CCPF-SK/Yocto-Gen3/v5.9.0

From eLinux.org
Jump to: navigation, search


Introduction

This page contains information abot building and running Yocto on:

If prebuilt binary of Yocto BSP is needed, please refer to the following:

Update info:

  • 2022/08/25: Update some yocto-layers.
  • 2022/03/02: Add support Camera device.

Topic

EOL Notification of the M3SK

Production of M3SK is discontinued.
See M3SK page for detail.

The new version of R-Car Starter Kit Premier is now on sale !!

  • Equipped with R-Car H3e-2G
    (En) https://www.renesas.com/jp/en/about/press-room/renesas-launches-r-car-gen3e-20-percent-higher-cpu-speed-automotive-infotainment-cockpit-and-digital
    (Zh) https://www.renesas.com/jp/zh/about/press-room/renesas-launches-r-car-gen3e-20-percent-higher-cpu-speed-automotive-infotainment-cockpit-and-digital
    (Jp) https://www.renesas.com/jp/ja/about/press-room/renesas-launches-r-car-gen3e-20-percent-higher-cpu-speed-automotive-infotainment-cockpit-and-digital
  • CPU performance is increased 20% by supporting up to 2GHz frequency over past products.
  • You can buy from here.

SW Release Information

Board name SW name Release date Note
R-Car Starter Kit ( Premier / Pro ) Yocto v5.9.0 (stable) [New!!] 2022/02/08
Kingfisher Infotainment Board Yocto v5.9.0 (stable) [New!!] 2022/02/14 To check for latest information, please refer to the meta-rcar/tree/v5.9.0.
Android 10 (stable) 2021/07/26 R-Car Starter Kit Premier(R-Car H3) + Kingfisher is supported.
R-Car Starter Kit Pro(RTP8J77961ASKB0SK0SA05A) + Kingfisher is also supported from 2021/11/25.
Android P (stable) 2020/09/29 R-Car Starter Kit Premier(R-Car H3) + Kingfisher is supported.
R-Car Starter Kit Pro(RTP8J77961ASKB0SK0SA05A) + Kingfisher is also supported from 2021/03/16.
CCPF-SK Board Yocto v5.9.0 (latest) [New!!] 2022/02/08 Prebuilt binary is available in Quick startup guide page. (Updated on 2022/03/18)


Software revisions

Software Revision
Yocto Project 3.1.11
aarch64-poky-linux-gcc (GCC) 9.3
Wayland/Weston 1.18.0/8.0.0
GStreamer 1.16.3
Kernel Ver 5.10.41
Userland 64/32bit 64
U-Boot 2020.10
OP_TEE 3.13.0
OpenGL ES 3.2

Environment

Host PC

Ubuntu 18.04/20.04 LTS (64bit) is recommended as OS. 32bit version is not supported.

Confirmed Board

Board SoC Confirmed
R-Car Starter Kit Premier H3e-2G v3.0 OK
R-Car Starter Kit Premier H3 v3.0 (1rank DDR) NT
R-Car Starter Kit Premier H3 v3.0 (2rank DDR) OK
R-Car Starter Kit Premier H3 v2.0 with 8GB DDR NT
R-Car Starter Kit Premier H3 v2.0 with 4GB DDR NT
R-Car Starter Kit Pro M3 v3.0 OK
R-Car Starter Kit Pro M3 v1.0 NT

18px <translate> Note:</translate> NT='Not Tested'

See also:

Required packages

  1. Download evaluation version of proprietary graphics and multimedia drivers from Renesas.
    To download Multimedia and Graphics library and related Linux drivers, please use the following link:
    Download two files:
    • R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-20220121.zip
    • R-Car_Gen3_Series_Evaluation_Software_Package_of_Linux_Drivers-20220121.zip

    Graphic drivers are required for Wayland. Multimedia drivers are optional.
  2. Install required packages
    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 python3-git python3-jinja2 libegl1-mesa \
    libsdl1.2-dev pylint3 xterm
    
    Refer to Yocto Project Quick Start for more information.

Building the BSP for CCPF-SK

What is different between "MMP" and "MMP-dist".

  • MMP is minimal BSP which contains GFX/MMP evaluation package.
  • MMP-dist is MMP + some additional packages(For debug, development, benchmark, and so on).
  • MMP-dist release package(core-image-weston-release) is distributed on R-Car/Boards/CCPF-SK/GettingStarted
  • BSP is minimal BSP without GFX/MMP evaluation package.

Manual steps for building MMP

Note:

  1. Create a directory and switch to it
    Warning! Yocto builds require a lot of disk space (up to 100 GB). Make sure you have got enough before starting the build.
    mkdir build
    cd build
    export WORK=`pwd`
    
  2. Clone basic Yocto layers:
    cd $WORK
    git clone git://git.yoctoproject.org/poky
    git clone git://git.openembedded.org/meta-openembedded
    git clone https://github.com/renesas-rcar/meta-renesas
    git clone https://github.com/renesas-rcar/meta-renesas-ccpf
    
  3. Switch to proper branches/commits
    cd $WORK/poky
    git checkout -b tmp 74b22db6879b388d700f61e08cb3f239cf940d18
    cd $WORK/meta-openembedded
    git checkout -b tmp 814eec96c2a29172da57a425a3609f8b6fcc6afe
    cd $WORK/meta-renesas
    git checkout -b tmp db07324cef9f09cfccafb36f05b8159421057af5  # <-- 2022/08/24 updated
    cd $WORK/meta-renesas-ccpf
    git checkout -b tmp 09dd815616cce3a2bdcf8906c0d21403df8b93bd
    
    Another versions are not tested for compatibility.
  4. Create $WORK/../proprietary folder, then download proprietary driver modules to it.
    See also Required_packages
    You should see the following files:
    $ ls -1 $WORK/../proprietary/*.zip
    R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-20220121.zip
    R-Car_Gen3_Series_Evaluation_Software_Package_of_Linux_Drivers-20220121.zip
    
  5. Populate meta-renesas with proprietary software packages.
    export PKGS_DIR=$WORK/../proprietary
    cd $PKGS_DIR
    unzip -qo R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-20220121.zip 
    unzip -qo R-Car_Gen3_Series_Evaluation_Software_Package_of_Linux_Drivers-20220121.zip
    cd $WORK/meta-renesas
    sh meta-rcar-gen3/docs/sample/copyscript/copy_proprietary_softwares.sh -f $PKGS_DIR
    unset PKGS_DIR
    
  6. Setup build environment
    cd $WORK
    TEMPLATECONF=$PWD/meta-renesas-ccpf/meta-rcar-gen3/docs/sample/conf/<h3ulcb|m3ulcb>-ccpf-sk/mmp/ \
        source poky/oe-init-build-env ${WORK}/build
    
  7. Start the build
    bitbake core-image-weston
    
  8. Building image can take up to a few hours depending on your host system performance.
    After the build has been completed successfully, you should see the output similar to:
    NOTE: Tasks Summary: Attempted 4704 tasks of which 31 didn't need to be rerun and all succeeded.
    
    and the command prompt should return.
  9. Bitbake has generated all the necessary files in ./tmp/deploy/images directory.
    You can verify its content:
    bash $ ls -1 `find ./tmp/deploy/images/h3ulcb/ -maxdepth 1 -type l -print`
    ./tmp/deploy/images/h3ulcb/Image
    ./tmp/deploy/images/h3ulcb/Image-h3ulcb.bin
    ./tmp/deploy/images/h3ulcb/core-image-weston-h3ulcb.ext4
    ./tmp/deploy/images/h3ulcb/core-image-weston-h3ulcb.manifest
    ./tmp/deploy/images/h3ulcb/core-image-weston-h3ulcb.tar.bz2
    ./tmp/deploy/images/h3ulcb/core-image-weston-h3ulcb.testdata.json
    ./tmp/deploy/images/h3ulcb/core-image-weston-h3ulcb.wic.bmap
    ./tmp/deploy/images/h3ulcb/core-image-weston-h3ulcb.wic.xz
    ./tmp/deploy/images/h3ulcb/core-image-weston-h3ulcb.wic.xz.sha256sum
    ./tmp/deploy/images/h3ulcb/modules-h3ulcb.tgz
    ./tmp/deploy/images/h3ulcb/r8a77951-ulcb-ccpf-sk.dtb
    ./tmp/deploy/images/h3ulcb/r8a77951-ulcb.dtb
    ./tmp/deploy/images/h3ulcb/r8a779m1-ulcb-ccpf-sk.dtb
    ./tmp/deploy/images/h3ulcb/r8a779m1-ulcb.dtb
    ./tmp/deploy/images/h3ulcb/u-boot-elf-h3ulcb.srec
    ./tmp/deploy/images/h3ulcb/u-boot-h3ulcb.bin
    ./tmp/deploy/images/h3ulcb/u-boot-h3ulcb.bin-r8a7795_h3ulcb
    ./tmp/deploy/images/h3ulcb/u-boot-initial-env-h3ulcb-r8a7795_h3ulcb
    ./tmp/deploy/images/h3ulcb/u-boot-initial-env-r8a7795_h3ulcb
    ./tmp/deploy/images/h3ulcb/u-boot.bin
    ./tmp/deploy/images/h3ulcb/u-boot.bin-r8a7795_h3ulcb
    
    Image is a Kernel image, *.dtb is a blob file, core-image-<image_type>-<board_name>.tar.bz2 is the rootfs, modules-<board_name>.tgz are kernel modules.
  10. You can now proceed with Running Yocto images

Using build script

  1. Directory Structure
    |--build.sh
    `--proprietary
       |--R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-20220121.zip
       `--R-Car_Gen3_Series_Evaluation_Software_Package_of_Linux_Drivers-20220121.zip
    
  2. Build script(build.sh)
    #!/bin/bash
    
    BOARD_LIST=("h3ulcb" "m3ulcb")
    PROPRIETARY_DIR=`pwd`/proprietary
    WORK=`pwd`/work_yocto590_ccpfsk
    GFX_MMP_LIB=R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-20220121.zip
    GFX_MMP_DRIVER=R-Car_Gen3_Series_Evaluation_Software_Package_of_Linux_Drivers-20220121.zip
    
    repolist=( \
        "git://git.yoctoproject.org/poky;74b22db6879b388d700f61e08cb3f239cf940d18" \
        "git://git.openembedded.org/meta-openembedded;814eec96c2a29172da57a425a3609f8b6fcc6afe" \
        "https://github.com/renesas-rcar/meta-renesas;db07324cef9f09cfccafb36f05b8159421057af5" \
        "https://github.com/renesas-rcar/meta-renesas-ccpf;09dd815616cce3a2bdcf8906c0d21403df8b93bd" \
        "https://github.com/yhamamachi/meta-rcar-dev-utils;1bc61d16ed0a08797191430b802310ea2ab078e6" \
    )
    repolist_release=( \
        "https://github.com/yhamamachi/meta-rcar-bsp-release;8b38c20918ddcc260ddac1307a60d33c8a358a4b" \
    )
    repolist_dist=( \
        "https://github.com/OSSystems/meta-browser;157c2dcc26304edc2543e5f45e74daf70ef2b7a6" \
        "https://github.com/kraj/meta-clang;76c6751d721a4265e01bb71d8dc4fb46dca6602f" \
        "git://git.openembedded.org/meta-python2;b901080cf57d9a7f5476ab4d96e56c30db8170a8" \
    )
    
    TARGET_BOARD=""
    RELEASE=""
    BUILD_TARGET=core-image-weston
    BUILD_TYPE=mmp
    
    _usage () {
        echo "Usage: $0 \${BOARD_NAME} [build type options] [release package option]"
        echo "BOARD_NAME list: "
        for i in ${BOARD_LIST[@]}; do echo "  - $i"; done
        echo "build type options:"
        echo "  -d: mmp-dist"
        echo "  -m: mmp(default)"
        echo "  -g: gfx-only"
        echo "  -b: bsp"
        echo "release package options:"
        echo "  -r: Create core-image-xxxxx-release"
        echo "Clean build option"
        echo "  -c: Clone repo again(remove repo, then clone repo)"
        exit
    }
    
    repo_clone () {
        mkdir -p ${WORK}
        for repo in ${repolist[@]}; do
            URL=$(echo $repo | cut -d';' -f1)
            COMMIT=$(echo $repo | cut -d';' -f2)
            NAME=${URL##*/}
            # cleanup repo if -c option enabled
            if [[ "${RECLONE_FLAG}" == "True" ]]; then
                rm -rf ${WORK}/${NAME}
            fi
            # Clone repo
            if [[ ! -d "${WORK}/${NAME}" ]]; then
                git clone ${URL} ${WORK}/${NAME}
            fi
            # update and clean up branch
            cd ${WORK}/${NAME};
            git fetch; git checkout -B tmp ${COMMIT};
            git clean -df; git reset --hard;
        done
    }
    
    extract_proprietary_package() {
        WORK_PROP_DIR=${WORK}/proprietary
        mkdir -p ${WORK_PROP_DIR}
        unzip -qo ${PROPRIETARY_DIR}/${GFX_MMP_LIB} -d ${WORK_PROP_DIR}
        unzip -qo ${PROPRIETARY_DIR}/${GFX_MMP_DRIVER} -d ${WORK_PROP_DIR}
        cd ${WORK}/meta-renesas
        sh meta-rcar-gen3/docs/sample/copyscript/copy_proprietary_softwares.sh -f ${WORK_PROP_DIR}
    }
    
    proc_args () {
        TARGET_BOARD=$1; shift 1
        if ! `IFS=$'\n'; echo "${BOARD_LIST[*]}" | grep -qx "${TARGET_BOARD}"`; then
            _usage
        fi
    
        for arg in $@; do
            if [[ "${arg}" == "-m" ]]; then
                BUILD_TYPE=mmp
            elif [[ "${arg}" == "-g" ]]; then
                BUILD_TYPE=gfx-only
            elif [[ "${arg}" == "-b" ]]; then
                BUILD_TYPE=bsp
                BUILD_TARGET=core-image-minimal
            elif [[ "${arg}" == "-d" ]]; then
                BUILD_TYPE=mmp-dist
                repolist=(${repolist[@]} ${repolist_dist[@]})
            elif [[ "${arg}" == "-r" ]]; then
                RELEASE=-release
                repolist=(${repolist[@]} ${repolist_release[@]})
            elif [[ "${arg}" == "-c" ]]; then
                RECLONE_FLAG="True"
            fi
        done
    }
    
    build_yocto () {
        cd ${WORK}
        BUILD_DIR=${WORK}/build_${TARGET_BOARD}_${BUILD_TYPE}${RELEASE}
        rm -rf ${BUILD_DIR}/conf
        TEMPLATECONF=$PWD/meta-renesas-ccpf/meta-rcar-gen3/docs/sample/conf/${TARGET_BOARD}-ccpf-sk/${BUILD_TYPE}/ \
            source poky/oe-init-build-env ${BUILD_DIR}
        cd ${BUILD_DIR}
        echo "DL_DIR = '${DL_DIR:-${WORK}/yocto_dl_dir}'" >> ${BUILD_DIR}/conf/local.conf
        echo "SSTATE_DIR = '${SSTATE_DIR:-${WORK}/yocto_sstate_dir}'" >> ${BUILD_DIR}/conf/local.conf
        echo "${LOCAL_CONF_APPEND}" >> ${BUILD_DIR}/conf/local.conf
        bitbake-layers add-layer ${WORK}/meta-rcar-dev-utils/meta-rcar-gen3
        if [[ "${RELEASE}" != "" ]]; then
            cp -f ${WORK}/meta-rcar-bsp-release/meta-rcar-gen3/docs/sample/site.conf.sample \
                ${BUILD_DIR}/conf/site.conf
            bitbake-layers add-layer ${WORK}/meta-rcar-bsp-release/meta-rcar-gen3
        fi
        bitbake ${BUILD_TARGET}${RELEASE}
    }
    
    ## main process ##
    ulimit -n 8192 # Setting for building Chromium
    proc_args $@
    repo_clone
    if [[ "$BUILD_TYPE" != "bsp" ]]; then
        extract_proprietary_package
    fi
    build_yocto
    
  3. build
    ./build.sh <target_board_name> <build type> <release package option>
    Ex.)
        h3ulcb mmp build:
            ./build.sh h3ulcb -m
        m3ulcb mmp-dist build for release:
            ./build.sh m3ulcb -d -r
    
    18px <translate> Note:</translate> target_board_name is "h3ulcb" or "m3ulcb".
    If the build completes successfully, all the necessary files are generated in a following directory:
    ./work_Yocto590_ccpfsk/build_<target_board_name>_<build type>/tmp/deploy/images/<target_board_name>
    ex.) h3ulcb mmp build:
        ./work_Yocto590_ccpfsk/build_h3ulcb_mmp/tmp/deploy/images/h3ulcb
    ex.) m3ulcb mmp-dist for release build:
        ./work_Yocto590_ccpfsk/build_m3ulcb_mmp-dist-release/tmp/deploy/images/m3ulcb
        or
        ./work_Yocto590_ccpfsk/build_m3ulcb_mmp-dist-release/tmp/deploy/release
    

Build SDK

Refer to Build SDK on the Yocto-Gen3 page.

Running Yocto images

Refer to Running Yocto images on the Yocto-Gen3 page.

Relationship diagram between each SK board and DTB file

Board name SoC version Type Name DTB file
H3SK 2.0
2.0
2.0/3.0
RTP0RC77951SKBX010SA00
RTP0RC77951SKBX010SA01
RTP0RC77951SKBX010SA03
r8a77951-ulcb-ccpf-sk.dtb
H3e-2G SK 3.0 RTP8J779M1ASKB0SK0SA003 r8a779m1-ulcb-ccpf-sk.dtb
M3SK 1.0 RTP0RC7796SKBX0010SA09 r8a77960-ulcb-ccpf-sk.dtb
M3SK 3.0 RTP8J77961ASKB0SK0SA05A r8a77961-ulcb-ccpf-sk.dtb

S/W support status

Support list

Functions Status
CAN ok
USB2.0 ok
USB3.0 ok
HDMI1(only H3SK) ok
Camera 0 ok(After you execute suspend to RAM, you can't use camera.)
Camera 1 ok(After you execute suspend to RAM, you can't use camera.)
NVMe ok
S2RAM(Suspend to RAM) ok(May fail in NVMe connection state.)
fan control ok

Note:

"ok" - Function succeeded in the simple test as below.
"NT" - Function wasn't tested
Please connect USB 3.0 device to USB 3.0 port and USB2.0 device to USB 2.0 port.

How to test some capabilities

CAN

Ex.) loop back

connect pin2 and pin6, pin3 and pin7
CCPF-SK-CAN.png
root@h3ulcb:~# ip link set can0 up type can bitrate 125000
root@h3ulcb:~# ip link set can1 up type can bitrate 125000
root@h3ulcb:~# candump can0&
root@h3ulcb:~# cangen can1 -I i -L i -D i
(Ctrl+C)
root@h3ulcb:~# candump can1&
root@h3ulcb:~# cangen can0 -I i -L i -D i


Camera

loading dtbo files

It requires to use device tree overlay in U-boot. Following is the example of using tftp.

tftp 0x48040000 ulcb-ccpf-sk-cn12-imx219.dtbo
fdt addr 0x48000000
fdt resize 8192
fdt apply 0x48040000
tftp 0x48060000 ulcb-ccpf-sk-cn13-imx219.dtbo
fdt apply 0x48060000

See also:

Setup camera
media-ctl -d /dev/media0 -r
media-ctl -d /dev/media0 -l "'rcar_csi2 feaa0000.csi2':1 -> 'VIN0 output':0 [1]"
media-ctl -d /dev/media0 -V "'rcar_csi2 feaa0000.csi2':1 [fmt:SBGGR8_1X8/3264x2464 field:none]"
media-ctl -d /dev/media0 -l "'rcar_csi2 fea80000.csi2':1 -> 'VIN4 output':0 [1]"
media-ctl -d /dev/media0 -V "'rcar_csi2 fea80000.csi2':1 [fmt:SBGGR8_1X8/3264x2464 field:none]"
Using Camera

Ex.) Show video captured by camera0 in weston.

gst-launch-1.0 v4l2src device=/dev/video0 io-mode=mmap ! \
    video/x-bayer,format=bggr,width=3264,height=2464 ! bayer2rgb ! videobalance ! videoconvert ! waylandsink

Ex.) Show video captured by camera0 in weston.

gst-launch-1.0 v4l2src device=/dev/video1 io-mode=mmap ! \
    video/x-bayer,format=bggr,width=3264,height=2464 ! bayer2rgb ! videobalance ! videoconvert ! waylandsink

Ex.) Save and show an image captured by camera0

gst-launch-1.0 v4l2src device=/dev/video0 io-mode=mmap num-buffers=1 ! \
    video/x-bayer,format=bggr,width=3264, height=2464 ! queue ! bayer2rgb ! queue ! videoconvert ! video/x-raw,format=RGB,framerate=1/1 ! jpegenc ! filesink location=out.jpg
gst-launch-1.0 -v filesrc location=out.jpg ! jpegdec ! imagefreeze ! videoconvert ! video/x-raw, format=BGRA ! waylandsink

How to crop or scale up/down video:

NVMe

root@h3ulcb:~# dmesg | grep nvme
nvme nvme0: pci function 0000:01:00.0
nvme 0000:01:00.0: enabling device (0000 -> 0002)
nvme nvme1: pci function 0001:01:00.0
nvme 0001:01:00.0: enabling device (0000 -> 0002)
nvme nvme0: 8/0/0 default/read/poll queues
nvme nvme1: 8/0/0 default/read/poll queues
root@h3ulcb:~# mount /dev/nvme0n1p1 /mnt
EXT4-fs (nvme0n1p1): mounted filesystem with ordered data mode. Opts: (null)
root@h3ulcb:~# ls /mnt
root@h3ulcb:~# umount /mnt
root@h3ulcb:~# mount /dev/nvme1n1p1 /mnt
EXT4-fs (nvme1n1p1): mounted filesystem with ordered data mode. Opts: (null)
root@h3ulcb:~# ls /mnt
root@h3ulcb:~# umount /mnt

S2RAM

Push SW6 or execute 'systemctl suspend' to enter Suspend to RAM.
it can wake-up by SW4.
18px <translate> Note:</translate>: May fail in NVMe connection state.

fan control

To use the fan control function, RL78 needs to be updated.

Temperature fan speed
less than 35 degrees 0%
above 35 degrees and below 50 degrees 50%
above 50 degrees 100%

This function can be stopped by "systemctl stop ccpfsk-fancontrol".

Known issues and limitations

  1. Refer to R-Car/Boards/CCPF-SK#Known_Issues.
  2. Refer to R-Car/Boards/Yocto-Gen3/v5.9.0#Known_issues_and_limitations.


Q&A site

https://community.renesas.com/automotive/r-car-h3-m3-cockpit/

FAQ site