Renesas RZ/Five User guide

R01US0618EJ0101 Rev.1.01 Page 1 of 41
Oct. 31, 2023
SMARC EVK of RZ/Five
Linux Start-up Guide
Introduction
This document provides a guide to prepare RZ/Five reference boards to boot up with the Verified Linux Package.
This guide provides the following information:
•Building procedure
•Preparation for use
•Boot loader and U-Boot
•How to run this Linux package on the target board
•How to create a software development kit (SDK)
Target Reference Board
RZ/Five reference board
•RZ/Five Evaluation board Kit (smarc-rzfive) (*1)
oRZ/Five SMARC Module Board (P/N: RTK9743F01C01000BE)
oRZ SMARC Series Carrier Board (P/N: RTK97X4XXXB00000BE)
(*1) “RZ/Five Evaluation board Kit” includes the RZ/Five SMARC Module Board and the RZ SMARC Series
Carrier Board.
The “Evaluation board Kit for RZ/Five MPU” will be called “RZ/Five Evaluation Kit” in the next section.
Target Software
•RZ/Five Verified Linux Package version 3.0.5 or later. (hereinafter referred to as “VLP/F”)
R01US0618EJ0101
Rev.1.01
Oct. 31, 2023

SMARC EVK of RZ/Five Linux Start-up Guide
R01US0618EJ0101 Rev.1.01 Page 2 of 41
Oct. 31, 2023
Contents
1. Environment Requirement.............................................................................................4
2. Build Instructions...........................................................................................................6
2.1 Notes ............................................................................................................................................ 9
3. Preparing the SD Card .................................................................................................12
3.1 Write files to the microSD card (used wic image).................................................................. 12
3.2 Write files to the microSD card (not used wic image) ........................................................... 14
3.2.1 Create a microSD card for boot Linux .............................................................................. 14
3.2.2 Write files to the microSD card.......................................................................................... 18
4. Reference Board Setting..............................................................................................19
4.1 Preparation of Hardware and Software................................................................................... 19
4.1.1 How to set boot mode and input voltage ......................................................................... 20
4.1.2 How to set SW1 ................................................................................................................... 21
4.1.3 How to use debug serial (console ouput) ........................................................................ 21
4.1.4 Power supply....................................................................................................................... 22
4.1.5 Building files to write.......................................................................................................... 23
4.1.6 Settings ................................................................................................................................ 23
4.2 Download Flash Writer to RAM................................................................................................ 26
4.3 Write the Bootloader................................................................................................................. 28
4.4 Change Back to Normal Boot Mode........................................................................................ 30
5. Booting and Running Linux.........................................................................................32
5.1 Power on the board and Startup Linux................................................................................... 32
5.2 Shutdown the Board ................................................................................................................. 33
6. Building the SDK ..........................................................................................................34
7. Application Building and Running ..............................................................................35
7.1 Make an application .................................................................................................................. 35
7.1.1 How to extract SDK............................................................................................................. 35
7.1.2 How to build Linux application.......................................................................................... 35
7.2 Run a sample application......................................................................................................... 37
8. Appendix.......................................................................................................................38
8.1 Preparing Flash Writer.............................................................................................................. 38
8.1.1 Preparing cross compiler................................................................................................... 38
8.1.2 Building Flash Writer.......................................................................................................... 38
8.2 How to replace the SMARC Module Board............................................................................. 39
8.3 Device drivers............................................................................................................................ 40
9. Revision History ...........................................................................................................41

SMARC EVK of RZ/Five Linux Start-up Guide
R01US0618EJ0101 Rev.1.01 Page 3 of 41
Oct. 31, 2023
Website and Support...........................................................................................................42

SMARC EVK of RZ/Five Linux Start-up Guide
R01US0618EJ0101 Rev.1.01 Page 4 of 41
Oct. 31, 2023
1. Environment Requirement
The environment for building the Board Support Package (hereinafter referred to as “BSP”) is listed in the Table 1.
Please refer to the below documents for details about setting up the environment.
A Linux PC is required for building the software.
A Windows PC can be used as the serial terminal interface with software such as TeraTerm.
Figure 1 Recommend environment
Note: The board shown in Figure 1 is RZ/V2L, but RZ/Five has the same structure.

SMARC EVK of RZ/Five Linux Start-up Guide
R01US0618EJ0101 Rev.1.01 Page 5 of 41
Oct. 31, 2023
Table 1. Equipment and Software for Developing Environments of RZ/Five Linux Platform
Equipment
Description
Linux Host PC
Used as build/debug environment
100GB free space on HDD or SSD is necessary
OS
Ubuntu 20.04 LTS
64 bit OS must be used.
20.04 inside a docker container also OK.
Windows Host PC
Used as debug environment, controlling with terminal software
OS
Windows 10 or Windows 11
Terminal software
Used for controling serial console of the target board
Tera Term (latest version) is recommended
Available at https://ttssh2.osdn.jp/index.html.en
VCP Driver
Virtual COM Port driver which enables to communicate Windows Host PC
and the target board via USB which is virtually used as serial port. Available
at: http://www.ftdichip.com/Drivers/VCP.htm
USB serial to micro–USB
Cable
Serial communication (UART) between the Evaluation Board Kit and
Windows PC. The type of USB serial connector on the Evaluation Board Kit
is Micro USB type B.
microSD Card
Use to boot the system, and store applications.
Note that use a micro-SDHC card for the flash writer.
Most bootable images VLP/F supports can be built on an “offline” environment.
The word “offline” means an isolated environment which does not connect to any network. Since VLP/F includes all
necessary source codes of OSS except for the Linux kernel, VLP/F can always build images in this “offline”
environment without affected from changes of repositories of OSS. Also, this “offline” environment reproduces the
same images as the images which were verified by Renesas.
Below images can be built “offline”.
•core-image-minimal
•core-image-bsp

SMARC EVK of RZ/Five Linux Start-up Guide
R01US0618EJ0101 Rev.1.01 Page 6 of 41
Oct. 31, 2023
2. Build Instructions
2.1 Building images
This section describes the instructions to build the Board Support Package.
Before starting the build, run the command below on the Linux Host PC to install packages used for building the
BSP.
$ sudo apt-get update
$ sudo apt-get install gawk wget git-core diffstat unzip texinfo gcc-multilib \
build-essential chrpath socat cpio python python3 python3-pip python3-pexpect \
xz-utils debianutils iputils-ping libsdl1.2-dev xterm p7zip-full libyaml-dev \
libssl-dev bmap-tools
Please refer to the URL below for detailed information:
•https://docs.yoctoproject.org/3.1.26/brief-yoctoprojectqs/brief-yoctoprojectqs.html
(1) Create a working directory at your home directory, and decompress Yocto recipe package
Run the commandsbelow and set the user name and email address before starting the build procedure. Without this
setting, an error occurs when building procedure runs git command to apply patches.
$ git config --global user.email "[e-mail]"
$ git config --global user.name "Your Name"
Copy all files obtained from Renesas into your Linux Host PC prior to the steps below. The directory which you
put the files in is described as <package download directory> in the build instructions.
Create a working directory at your home directory, and decompress Yocto recipe package
Run the commands below. The name and the place of the working directory can be changed as necessary.
$ mkdir ~/rzfive_vlp_<package version>
$ cd ~/rzfive_vlp_<package version>
$ cp ../<package download directory>/*.zip .
$ unzip ./RTK0EF0045Z0025AZJ-<package version>.zip
$ tar zxvf ./RTK0EF0045Z0025AZJ-<package version>/rzfive_vlp_<package version>.tar.\
gz
Note) Please note that your build environment must have 100GB of free hard drive space in order to complete the
minimum build. The Yocto BSP build environment is very large. Especially in case you are using a Virtual
Machine, please check how much disk space you have allocated for your virtual environment.
<package version>: e.g v3.0.5
(2) Build Initialize
Initialize a build using the 'oe-init-build-env' script in Poky and point TEMPLATECONF to platform conf path.
$ TEMPLATECONF=$PWD/meta-renesas/meta-rzfive/docs/template/conf/ source \
poky/oe-init-build-env build

SMARC EVK of RZ/Five Linux Start-up Guide
R01US0618EJ0101 Rev.1.01 Page 7 of 41
Oct. 31, 2023
(3) Add layers (Optional)
•Docker: Please run the below commands if you want to include Docker. This means running Docker on the
RZ board, not as using Docker as part of your build environment.
$ bitbake-layers add-layer ../meta-openembedded/meta-filesystems
$ bitbake-layers add-layer ../meta-openembedded/meta-networking
$ bitbake-layers add-layer ../meta-virtualization
(4) Decompress OSS files to “build” directory (Optional)
Run the commands below. This step is not mandatory and able to go to the step (5) in case the “offline” environment
is not required. All OSS packages will be decompressed with this '7z' command.
$ cp ../../<package download directory>/*.7z .
$ 7z x oss_pkg_rzfive_<package version>.7z
Note) If this step is omitted and BB_NO_NETWORK is set to “0” in next step, all source codes will be downloaded
from the repositories of each OSS via the internet when running bitbake command. Please note that if you do
not use an “offline” environment, a build may fail due to the implicit changes of the repositories of OSS.
After the above procedure is finished, the “offline” environment is ready. If you want to prevent network access,
please change the line in the “~/rzfive_vlp_<package version>/build/conf/local.conf”as below:
BB_NO_NETWORK = "1"
To change BB_NO_NETWORK from “0” to “1”.
Note) Open source software packages contain all source codes of OSSs. These are the same versions of OSSs used
when VLP/F was verified.
If you are just evaluating VLP/F and RZ/Five series, open source software packages are not mandatory to use.
Usually, all the software can be built without using these files if your build machine is connected to the Internet.
Open source software packages are required for an “offline” environment. The word “offline” means an isolated
environment which does not connect to any network. VLP/F can always build images in this “offline”
environment by using these packages without affected from changes of original repositories of OSSs. Also, this
“offline” environment always reproduces the same images as the images which were verified by Renesas. Note
that if you build without using open source software packages, there are possibilities to use different source
codes than Renesas used due to the implicit changes of the repositories of OSSs.

SMARC EVK of RZ/Five Linux Start-up Guide
R01US0618EJ0101 Rev.1.01 Page 8 of 41
Oct. 31, 2023
(5) Start a build
Run the commands below to start a build. Building an image can take up to a few hours depending on the user’s host
system performance.
Build the target file system image using bitbake
$ MACHINE=smarc-rzfive bitbake core-image-<target>
<target> can be selected in below. Please refer to the Table 2 for supported image details.
•core-image-minimal
•core-image-bsp
After the build is successfully completed, a similar output will be seen, and the command prompt will return.
NOTE: Tasks Summary: Attempted 3795 tasks of which 8 didn't need to be rerun and all s
ucceeded.
All necessary files listed in Table 3 will be generated by the bitbake command and will be located in the
build/tmp/deploy/images directory.
VLP/F can build a few types of images listed in the Table 2.
Table 2. Supported images of VLP/F
Image name
Purpose
core-image-minimal
Minimal set of components
core-image-bsp
Minimal set of components plus audio support and some useful tools
Table 3. Image files for RZ/Five
RZ/Five
Linux kernel
Image-smarc-rzfive.bin
Device tree file
Image-r9a07g043f01-smarc.dtb
root filesystem
<image name>-smarc-rzfive.tar.bz2
Boot loader
•fit-smarc-rzfive.srec
•
spl-smarc-rzfive.srec
Flash Writer
Flash_Writer_SCIF_RZFIVE_SMARC.mot
SD image
core-image-<image name> -smarc-rzfive.wic.gz
core-image-<image name> -smarc-rzfive.wic.bmap

SMARC EVK of RZ/Five Linux Start-up Guide
R01US0618EJ0101 Rev.1.01 Page 9 of 41
Oct. 31, 2023
2.2 Notes
(1) GPLv3 packages
In this release, the GPLv3 packages are disabled as default in build/conf/local.conf:
INCOMPATIBLE_LICENSE = "GPLv3 GPLv3+"
If you want to use GPLv3, just hide this line:
#INCOMPATIBLE_LICENSE = "GPLv3 GPLv3+"
(2) CIP Core Packages
VLP/F includes Debian 10 (Buster) based CIP Core Packages and is enabled by the default settings. These packages can
be changed.
Note that network access is required to start the build process when you enable these packages except for Buster which
is set as the default setting.
CIP Core Packages are going to be maintained by the Civil Infrastructure Platform project. For more technical
information, please contact Renesas.
1. Buster (default):
The following lines are added as default in the local.conf:
# Select CIP Core packages
CIP_CORE = "1"
2. Bullseye:
Please change “CIP_MODE” in the local.conf to change from Buster to Bullseye:
# Select CIP Core packages by switching betwwen Buster and Bullseye.
# - Buster (default) : build all supported Debian 10 Buster recipes
# - Bullseye : build all supported Debian 11 Bullseye recipes
# - Not set (or different with above): not use CIP Core, use default packages
version in Yocto
CIP_MODE = "Bullseye"
3. No CIP Core Packages:
If the CIP Core Packages are unnecessary, comment out and add the following lines to disable CIP Core Packages in
the local.conf:
# Select CIP Core packages
#CIP_CORE = "1"
Note) The above 2 settings disable GPLv3 packages as default. In case the GPLv3 packages are required, please
comment out the following line in the local.conf.
#INCOMPATIBLE_LICENSE = "GPLv3 GPLv3+"
By building the VLP/F, the packages will be replaced as below in the Table 4.

SMARC EVK of RZ/Five Linux Start-up Guide
R01US0618EJ0101 Rev.1.01 Page 10 of 41
Oct. 31, 2023
Table 4. Versions of all Buster Debian packages
Package
Buster Debian
Bullseye Debian
Attr
2.4.48
2.4.48
busybox
1.30.1
1.30.1
coreutils
6.9
6.9
GCC
8.3.0
-
glib-2.0
2.58.3
2.62.2
glibc
2.28
2.31
kbd
2.0.4
2.2.0
libgcrypt
1.8.4
1.8.5
openssh
7.9p1
8.2p1
Perl
5.30.1
5.30.1
pkgconfig
0.29
0.29.2
Quilt
0.65
0.66
(3) ECC
If you want to use ECC, see r01us0647ej0100-rz-mpu_ECC_UME.pdf included in the BSP manual set on the Renesas
Web. Please also check the section 8.3.
(4) WIC image
The name “WIC” is derived from OpenEmbedded Image Creator (oeic). It includes image that system can boot it in
hardware device.
From VLP/G v3.0.5, WIC is supported and below guidelines are shown how to use it to boot Renesas RZ/Five devices.
•Enable building WIC image in local.conf (default is enabled) by setting “WKS_SUPPORT” to 1:
WKS_SUPPORT ?= “1”
•Defines additional free disk space created in the image in Kbytes (keep default value if unsure):
IMAGE_ROOTFS_EXTRA_SPACE = "1048576"
•Select wks file to be built by setting “WKS_DEFAULT_FILE” (keep default value if unsure). Currently,
there are 2 types of wks defined in “meta-renesas/meta-rz-common/wic” for uSD/eMMC (channel 0) and uSD
(channel 1).
•Building your desired core-image by running “bitbake core-image-x”. “core-image-x” should be one of
following options:
ocore-image-minimal
ocore-image-bsp
•There are 2 files *wic.bmap and *wic.gz in deploy folder after building successfully. Example:
ocore-image-minimal-smarc-rzfive.wic.bmap
ocore-image-minimal-smarc-rzfive.wic.gz

SMARC EVK of RZ/Five Linux Start-up Guide
R01US0618EJ0101 Rev.1.01 Page 11 of 41
Oct. 31, 2023
(5) Software bill of materials (SBoM)
Software package data exchange (SPDX) is an open standard for SBoM that identifies and catalogs components,
licenses, copyrights, security references, and other metadata relating to software.
From VLP/G v3.0.5, creating SPDX is supported and below guidelines are shown how to use it:
•Enable creating SPDX in local.conf (default is disabled) by uncommenting out below line:
#INHERIT += "create-spdx"
•Select below optional features to be supported for SDPX by enable in local.conf (all is disabled by default):
oSPDX_PRETTY: Make generated files more human readable (newlines, indentation)
SPDX_PRETTY = "1"
oSPDX_ARCHIVE_PACKAGED: Add compressed archives of the files in the generated target
packages in tar.gz files.
SPDX_ARCHIVE_PACKAGED = "1"
•SPDX is created and deployed in “tmp/deploy/spdx/$MACHINE”. All information can be checked here.s
Note: There is an issue when building SDK (example bitbake core-image-weston -c populate_sdk) with SBoM SPDX
support:
| ERROR: core-image-weston-1.0-r0 do_populate_sdk: Error executing a python function
in exec_func_python() autogenerated:
| *** 1078: return self._accessor.open(self, flags, mode)
| 1079:
| 1080: def _raw_open(self, flags, mode=0o777):
| 1081: """
| 1082: Open the file pointed by this path and return a file descriptor,
|Exception: FileNotFoundError:
|[Errno 2] No such file or directory: 'tmp/work/smarc_rzg2l-poky-linux/core-image-
weston/1.0-r0/spdx/sdk-work/poky-glibc-x86_64-core-image-weston-aarch64-smarc-rzg2l-
target.spdx.json'
To fix this, please apply below change in “poky/meta/classes/populate_sdk_base.bbclass”:
-do_populate_sdk[cleandirs] = "${SDKDEPLOYDIR}"
+do_populate_sdk[cleandirs] += "${SDKDEPLOYDIR}"

SMARC EVK of RZ/Five Linux Start-up Guide
R01US0618EJ0101 Rev.1.01 Page 12 of 41
Oct. 31, 2023
3. Preparing the SD Card
You can prepare the microSD card by the following 2 methods.Please select one of them and follow the steps.
- 3.1 Write files to the microSD card (used wic image)
- 3.2 Write files to the microSD card (not used wic image)
3.1 Write files to the microSD card (used wic image)
Set microSD card to Linux PC. And check the mount device name with fdisk command.
$ sudo fdisk -l
Disk /dev/sdb: 3.74 GiB, 3997171712 bytes, 7806976 sectors
Disk model: Storage Device
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xxxxxxxxxx
$ umount /dev/sdb1
$ umount /dev/sdb2
Expand disk image.
$ sudo bmaptool copy <wic image>.wic.gz /dev/sdb
The file names of <wic image> is listed in the Table 3.
When you complete the above commands, the micro SD card is prepared correctly. Please skip the section 3.2.

SMARC EVK of RZ/Five Linux Start-up Guide
R01US0618EJ0101 Rev.1.01 Page 13 of 41
Oct. 31, 2023
Table 5. File and directory in the micro SD card
Type/Number
Filesystem
Contents
Primary #1
FAT32
Flash_Writer_SCIF_RZFIVE_SMARC.mot
fit-smarc-rzfive.srec
spl-smarc-rzfive.srec
Primary #2
Ext4(*1)
./
├── bin
├── boot
├─Image
└─r9a07g043f01-smarc.dtb
├── dev
├── etc
├── home
├── lib
├── media
├── mnt
├── proc
├── run
├── sbin
├── sys
├── tmp
├── usr
└── var
Note *1) Please refer to 2.2(4) WIC image for partition size specifications.

SMARC EVK of RZ/Five Linux Start-up Guide
R01US0618EJ0101 Rev.1.01 Page 14 of 41
Oct. 31, 2023
3.2 Write files to the microSD card (not used wic image)
3.2.1 Create a microSD card for boot Linux
To boot from SD card, over 4GB capacity of blank SD card is needed. You can use Linux Host PC to expand the kernel
and the rootfs using USB card reader or other equipment.
Please format the card according to the following steps before using the card:
(1) Non-connect microSD card to Linux Host PC
$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 30.9G 0 disk
├─sda1 8:1 0 512M 0 part /boot/efi
├─sda2 8:2 0 1K 0 part
└─sda5 8:5 0 30.3G 0 part /
sr0 11:0 1 1024M 0 rom
(2) Connect microSD card to Linux Host PC with USB adapter
(3) Check the device name which is associated to the microSD card.
$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 30.9G 0 disk
├─sda1 8:1 0 512M 0 part /boot/efi
├─sda2 8:2 0 1K 0 part
└─sda5 8:5 0 30.3G 0 part /
sdb 8:16 1 29.7G 0 disk
└─sdb1 8:17 1 29.7G 0 part
sr0 11:0 1 1024M 0 rom
The message above shows the card associated with the /dev/sdb. Be careful not to use the other device names in the
following steps.
(4) Unmount automatically mounted microSD card partitions
If necessary, unmount all mounted microSD card partitions.
$ df
Filesystem 1K-blocks Used Available Use% Mounted on
udev 745652 0 745652 0% /dev
:
snip
:
/dev/sdb1 511720 4904 506816 1% /media/user/A8D3-393B
$ sudo umount /media/user/A8D3-393B
If more than one partition has already been created on microSD card, unmount all partitions.

SMARC EVK of RZ/Five Linux Start-up Guide
R01US0618EJ0101 Rev.1.01 Page 15 of 41
Oct. 31, 2023
(5) Change the partition table
microSD card needs two partitions as listed in Table 6 .
Table 6. Partitions of microSD card
Type/Number
Size
Filesystem
Contents
Primary #1
500MB (minimum 128MB)
FAT32
Linux kernel
Device tree
Primary #2
All remaining
Ext4
root filesystem
Set the partition table using the fdisk command like this.
$ sudo fdisk /dev/sdb
Welcome to fdisk (util-linux 2.34).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Command (m for help): o
Created a new DOS disklabel with disk identifier 0x6b6aac6e.
Command (m for help): n
Partition type
p primary (0 primary, 0 extended, 4 free)
e extended (container for logical partitions)
Select (default p): p
Partition number (1-4, default 1):
First sector (2048-62333951, default 2048):
Last sector, +/-sectors or +/-size{K,M,G,T,P} (2048-62333951, default 62333951): +500M
Created a new partition 1 of type 'Linux' and of size 500 MiB.
Partition #1 contains a vfat signature.
Do you want to remove the signature? [Y]es/[N]o: Y
The signature will be removed by a write command.
Command (m for help): n
Partition type
p primary (1 primary, 0 extended, 3 free)
e extended (container for logical partitions)
Select (default p): p
Partition number (2-4, default 2): (Push the enter key)
First sector (1026048-62333951, default 1026048): (Push the enter key)
Last sector, +/-sectors or +/-size{K,M,G,T,P} (1026048-62333951, default 62333951): (P
ush the enter key)
Created a new partition 2 of type 'Linux' and of size 29.2 GiB.
Command (m for help): p
Disk /dev/sdb: 29.74 GiB, 31914983424 bytes, 62333952 sectors
Disk model: Transcend
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos

SMARC EVK of RZ/Five Linux Start-up Guide
R01US0618EJ0101 Rev.1.01 Page 16 of 41
Oct. 31, 2023
Disk identifier: 0x6b6aac6e
Device Boot Start End Sectors Size Id Type
/dev/sdb1 2048 1026047 1024000 500M 83 Linux
/dev/sdb2 1026048 62333951 61307904 29.2G 83 Linux
Filesystem/RAID signature on partition 1 will be wiped.
Command (m for help): t
Partition number (1,2, default 2): 1
Hex code (type L to list all codes): b
Changed type of partition 'Linux' to 'W95 FAT32'.
Command (m for help): w
The partition table has been altered.
Syncing disks.
Then, check the partition table with the commands below:
$ partprobe
$ sudo fdisk -l /dev/sdb
Disk /dev/sdb: 29.74 GiB, 31914983424 bytes, 62333952 sectors
Disk model: Maker name etc.
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x6b6aac6e
Device Boot Start End Sectors Size Id Type
/dev/sdb1 2048 1026047 1024000 500M b W95 FAT32
/dev/sdb2 1026048 62333951 61307904 29.2G 83 Linux

SMARC EVK of RZ/Five Linux Start-up Guide
R01US0618EJ0101 Rev.1.01 Page 17 of 41
Oct. 31, 2023
(6) Format and mount the partitions
If the partitions were automatically mounted after the step (4), please unmount them according to the step (3).
Then format the partitions using the command below:
$ sudo mkfs.vfat -v -c -F 32 /dev/sdb1
mkfs.fat 4.1 (2017-01-24)
/dev/sdb1 has 64 heads and 32 sectors per track,
hidden sectors 0x0800;
logical sector size is 512,
using 0xf8 media descriptor, with 1024000 sectors;
drive number 0x80;
filesystem has 2 32-bit FATs and 8 sectors per cluster.
FAT size is 1000 sectors, and provides 127746 clusters.
There are 32 reserved sectors.
Volume ID is a299e6a6, no volume label.
Searching for bad blocks 16848... 34256... 51152... 68304... 85072... 102096... 11937
6... 136528... 153552... 170576... 187472... 204624... 221648... 238928... 256208... 2
73744... 290768... 308048... 325328... 342480... 359504... 376656... 393680... 41057
6... 427216... 444624... 462032... 479184... 495952...
$ sudo mkfs.ext4 -L rootfs /dev/sdb2
mke2fs 1.45.5 (07-Jan-2020)
Creating filesystem with 7663488 4k blocks and 1916928 inodes
Filesystem UUID: 63dddb3f-e268-4554-af51-1c6e1928d76c
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
(7) Remount microSD card
$ umount /dev/sdb1
$ umount /dev/sdb2
After format, remove the card reader and connect it again to mount the partitions.

SMARC EVK of RZ/Five Linux Start-up Guide
R01US0618EJ0101 Rev.1.01 Page 18 of 41
Oct. 31, 2023
3.2.2 Write files to the microSD card
Check the mount point name with df command.
$ df
Filesystem 1K-blocks Used Available Use% Mounted on
udev 745652 0 745652 0% /dev
:
snip
:
/dev/sdb1 510984 16 510968 1% /media/user/A299-E6A6
/dev/sdb2 30041556 45080 28447396 1% /media/user/rootfs
When you use RZ/Five Evaluation board Kit, copy kernel and device tree file to the first partition like as below.
$ cp $WORK/build/tmp/deploy/images/smarc-rzfive/<Linux kernel> /media/user/A299-E6A6
$ cp $WORK/build/tmp/deploy/images/smarc-rzfive/<Devise tree> /media/user/A299-E6A6
When you use RZ/Five Evaluation board Kit, expand rootfs to the second partition like as below.
$ cd /media/user/rootfs
$ sudo tar jxvf $WORK/build/tmp/deploy/images/smarc-rzfive/<root filesystem>
The file nemes of <Linux kernel>, <Devise tree>, and <root filesystem> are listed in the Table 3.
Table 7. File and directory in the microSD card
Type/Number
Size
Filesystem
Contents
Primary #1
Size specified
when the partition
was created.
(minimum 128MB)
FAT32
Image-smarc-rzfive.bin
Image-r9a07g043f01-smarc.dtb
Primary #2
Size specified
when the partition
was created.
Ext4
./
├── bin
├── boot
├── dev
├── etc
├── home
├── lib
├── media
├── mnt
├── proc
├── run
├── sbin
├── sys
├── tmp
├── usr
└──
var

SMARC EVK of RZ/Five Linux Start-up Guide
R01US0618EJ0101 Rev.1.01 Page 19 of 41
Oct. 31, 2023
4. Reference Board Setting
4.1 Preparation of Hardware and Software
The following environment of Hardware and Software is used in the evaluation.
Hardware preparation (Users should purchase the following equipment.):
•USB Type-C cable compatible with USB PD. (e.g. AK-A8485011 (manufactured by Anker))
•USB PD Charger 15W (5V 3.0A) or more. (e.g. PowerPort III 65W Pod (manufactured by Anker))
•USB Type-microAB cable (Any cables)
•PC Installed FTDI VCP driver and Terminal software (Tera Term) (*1)
(*1) Please install the FTDI driver that can be following website (https://www.ftdichip.com/Drivers/VCP.htm).
Figure 2. Operating environment

SMARC EVK of RZ/Five Linux Start-up Guide
R01US0618EJ0101 Rev.1.01 Page 20 of 41
Oct. 31, 2023
4.1.1 How to set boot mode and input voltage
Please set the SW11 settings as follows.
•Pin no1 to no3 of the SW11 is used to control boot mode of RZ/Five.
•Pin no4 of the SW11 is used to control the input voltage from power charger to 5V or 9V. Please use a 5V
setting as initial setting.
Please select boot mode as below figures.
󰑯󰑰󰑱󰑲󰑳Currently we support 2 modes in 4 modes: SCIF Download mode and QSPI Boot mode. eSD Boot mode will be
supported by the future update.
Please select input voltage setting as below.
SW11-4
Input voltage selection
OFF
Input 9V
ON
Input 5V
SW11-1
OFF
SW11-2
ON
SW11-3
OFF
SW11-4
ON