R-Car/Boards/S4SK/Yocto-Linux

This page is under preparation.

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

Building the BSP for R-Car S4 Starter Kit
Warning! Yocto builds require a lot of disk space (up to 100 GB). Make sure you have got enough before starting the build.

Using build script

 * 1) Build script(build.sh)
 * 2) build
 * 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:
 * 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
 * 2) Clone basic Yocto layers:
 * 3) Switch to proper branches/commits
 * 4) Setup build environment
 * 5) Prepare default configuration files.
 * 6) Start the build
 * 7) 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) Prepare default configuration files.
 * 2) Start the build
 * 3) 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) 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.
 * and the command prompt should return.

Generated images

 * 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, rcar-image-gateway-s4sk.tar.bz2 is the rootfs, modules-s4sk.tgz are kernel modules.
 * Image is a Kernel image, *.dtb is a blob file, rcar-image-gateway-s4sk.tar.bz2 is the rootfs, modules-s4sk.tgz are kernel modules.

uSD boot
WARNING! These steps will erase the uSD card completely. In short, all files will be lost. In order to prepare you uSD card, follow these instructions on host machine:
 * 1) Partion your uSD card to set 1 partition and ID=83 (Linux)
 * Make sure the uSD card doesn't contain any important files.
 * 1) Format this partition to ext4
 * 2) Mount this partition on your host to any directory and upack the rcar-image-gateway-s4sk.tar.bz2 into mounted folder.
 * NOTE: probably you need to be a root user, hence use "sudo"
 * Image and r8a779f0-s4sk.dtb are deployed under /mnt/boot/ directory
 * 1) Insert uSD card to S4 SK uSD card slot(CN5)
 * 2) Set SW3
 * SW3.1 : On
 * SW3.2 : On
 * SW3.3 : Off
 * SW3.4 : On
 * SW3.5 : Off
 * SW3.6 : On
 * SW3.7 : Off
 * SW3.8 : Off
 * 1) Power ON (SW5)
 * SW3.7 : Off
 * SW3.8 : Off
 * 1) Power ON (SW5)

NFS boot

 * 1) Install some packages for NFS boot (See R-Car/Boards/Yocto-Gen3/v5.9.0)
 * 2) Decompress the rootfs on host PC
 * Image and r8a779f0-s4sk.dtb are deployed under /mnt/boot/ directory
 * 1) Connect the host PC to the S4SK IC101(TSN0) connector with a LAN cable
 * 2) Set SW3
 * SW3.1 : On
 * SW3.2 : On
 * SW3.3 : Off
 * SW3.4 : On
 * SW3.5 : Off
 * SW3.6 : On
 * SW3.7 : Off
 * SW3.8 : Off
 * 1) Power ON (SW5)
 * 1) Power ON (SW5)

PCIe Root Complex(CN30) : SSD
See No.3 of Known issues & Restrictions chapter. Environment:
 * 1) MZVPV512HDGL-0000
 * 2) U.2 to M.2 M-Key NVME SSD and PCIe
 * 3) Oculink to U.2 Cable
 * 4) SATA/IDE AC Adoperq(Japanese site)
 * s4sk_pcie_nvme3.jpg

Known issues & Restrictions

 * 1) [Known issue] Bitbake error messages when building SDK first time
 * These error message are Poky 3.1.11 bug, it doesn't affect to build output.
 * Ignore error messages.
 * 1) [Restriction] The "reboot" command is not completed. Therefore, press the power(SW5) or reset(SW4) button.
 * 1) [Restriction] The "reboot" command is not completed. Therefore, press the power(SW5) or reset(SW4) button.


 * 1) [Known issue] PCIe 0ch(Root Complex) of SDK v3.16.0 may not work with some connected devices.
 * If you see logs like the following, please apply this [[File:0001-pci-dwc-renesas-Change-to-mdelay-from-msleep.zip]] patch
 * How to apply patch
 * How to apply patch