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

Introduction
This page contains information abot building and running Yocto on: If prebuilt binary of Yocto BSP is needed, please refer to the following:
 * R-Car/Boards/CCPF-SK
 * R-Car/Boards/CCPF-SK/GettingStarted

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

Confirmed Board
NT='Not Tested'

See also:
 * R-Car/Boards/H3SK
 * R-Car/Boards/M3SK

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:
 * https://www.renesas.com/us/en/application/automotive/r-car-h3-m3-h2-m2-e2-documents-software
 * Download two files:
 * R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-20210921.zip
 * R-Car_Gen3_Series_Evaluation_Software_Package_of_Linux_Drivers-20210921.zip
 * Graphic drivers are required for Wayland. Multimedia drivers are optional.
 * 1) Install required packages
 * Refer to Yocto Project Quick Start for more information.
 * Refer to Yocto Project Quick Start for more information.
 * 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.

Using build script

 * 1) Directory Structure
 * 2) Build script(build.sh)
 * 3) build
 * target_board_name is "h3ulcb" or "m3ulcb".
 * If the build completes successfully, all the necessary files are generated in a following directory:
 * target_board_name is "h3ulcb" or "m3ulcb".
 * If the build completes successfully, all the necessary files are generated in a following directory:
 * If the build completes successfully, all the necessary files are generated in a following directory:

Manual steps

 * 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.
 * 1) Clone basic Yocto layers:
 * 2) Switch to proper branches/commits
 * Another versions are not tested for compatibility.
 * 1) Switch to proper branches/commits
 * Another versions are not tested for compatibility.
 * Another versions are not tested for compatibility.


 * 1) Create $WORK/../proprietary folder, then download proprietary driver modules to it.
 * See also Required_packages
 * You should see the following files:
 * 1) Populate meta-renesas with proprietary software packages.
 * 2) Setup build environment
 * 3) Start the build
 * 4) 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:
 * and the command prompt should return.
 * 1) Bitbake has generated all the necessary files in ./tmp/deploy/images directory. You can verify its content:
 * Image is a Kernel image, *.dtb is a blob file, core-image--.tar.bz2 is the rootfs, modules-.tgz are kernel modules.
 * 1) You can now proceed with running Yocto images
 * and the command prompt should return.
 * 1) Bitbake has generated all the necessary files in ./tmp/deploy/images directory. You can verify its content:
 * Image is a Kernel image, *.dtb is a blob file, core-image--.tar.bz2 is the rootfs, modules-.tgz are kernel modules.
 * 1) You can now proceed with running Yocto images
 * Image is a Kernel image, *.dtb is a blob file, core-image--.tar.bz2 is the rootfs, modules-.tgz are kernel modules.
 * 1) You can now proceed with running Yocto images

build script

 * 1) Build script(build.sh)

Build script

 * 1) Build script(build.sh)

Build SDK
Refer to Build SDK on the Yocto-Gen3 page.

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

Support list
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.

CAN
Ex.) loop back
 * connect pin2 and pin6, pin3 and pin7
 * CCPF-SK-CAN.png

S2RAM
Push SW6 or execute 'systemctl suspend' to enter Suspend to RAM. it can wake-up by SW4.
 * May fail in NVMe connection state.

fan control
To use the fan control function, RL78 needs to be updated. This function can be stopped by "systemctl stop ccpfsk-fancontrol".

Known issues and limitations

 * 1) Refer to R-Car/Boards/CCPF-SK.
 * 2) Refer to R-Car/Boards/Yocto-Gen3/.