Renesas
RZ/V AI

5.00

The best solution for
starting your AI applications.

Provided by Renesas Electronics Corporation

Get the Board
and Software

AI Applications Overview

AI SDK Overview

To keep you updated,
Watch our GitHub repository

Watch

This project is maintained by renesas-rz

Hosted on GitHub Pages — Theme by orderedlist

Getting Started Appendix

This page explains the additional information of Getting Started.

A1. Setup for QSPI Bootloader

This section explains how to setup the board for QSPI Bootloader.

Note This step is required only when starting the AI SDK or when using the new version of AI SDK.
If you have already setup the microSD card and the bootloader written in QSPI on the board, skip this step and proceed to the next step (Step7:2. Deploy Application to the Board in Getting Started).

Follow the instruction below to setup the board.

Note Explanation in this step is for QSPI Bootloader, which requires Windows PC as serial communication console.

1. Install Terminal Emulator

Note If you have already installed terminal emulator, skip this step and proceed to next procedure.
1. Install following software on Windows PC to be used as serial communication console.
  - Terminal emulator
    - Operating Environment: Tera Term
2. Install the serial port driver

Note If you have already installed the serial port driver, skip this step and proceed to next procedure.
The serial communication between Windows PC and RZ/V2L EVK requires following driver.
https://ftdichip.com/drivers/vcp-drivers/
1. Download the software "Virtual COM port (VCP) driver" from the windows version "setup executable" on the download page and extract it.
2. Run the *.exe file extracted to install the serial port driver.

3. Write bootloaders to QSPI on the board

Copy following files in ${WORK}/board_setup/QSPI/bootloader to your Windows PC.
- Flash_Writer_SCIF_RZV2L_SMARC _PMIC_DDR4_2GB_1PCS.mot
- bl2_bp-smarc-rzv2l_pmic.srec
- fip-smarc-rzv2l_pmic.srec

Connect Windows PC and Board via Serial to MicroUSB Cable.

Change SW1 and SW11 setting (see the figure below).

Connect the power cable to CN6 on the Board.

Press and hold the power button (SW9) for 1 second to turn on the power.

On Windows PC, open the terminal emulator. Here, we use Tera Term as an example.

Select "File" > "New Connection" and select "Serial" port as shown below.

Open the configuration window from the "Setup">"Terminal" and change the setting as follows.

Item Value

New-line Receive: Auto

Transmit: CR

Item	Value
New-line	Receive: Auto
	Transmit: CR

Open the configuration window from the "Setup">"Serial port" and change the setting as follows.

Item	Value
Baud rate	115200
Data	8bit
Parity	none
Stop	1bit
Flow control	none
Transmit delay	0msec/char

Press the reset button (SW10) and following message will be displayed on the terminal.

  SCIF Download mode
(C) Renesas Electronics Corp.
-- Load Program to System RAM ---------------
please send !

Open "File" > "Send file..." and send the Flash Writer file (*.mot) as a text.
If following message is displayed, the file transfer suceeded.
```
Flash writer for RZ/V2 Series Vx.xx xxx.xx,20xx
Product Code : RZ/V2L
>
```

Enter "XLS2" on the terminal to get following messages.

> XLS2
===== Qspi writing of RZ/G2 Board Command =============
Load Program to Spiflash
Writes to any of SPI address.
Micron : MT25QU512
Program Top Address & Qspi Save Address
===== Please Input Program Top Address ============
  Please Input : H'

Enter "11E00". The log continues.

  Please Input : H'11E00
===== Please Input Qspi Save Address ===
  Please Input : H'

Enter "00000". The log continues.

  Please Input : H'00000
Work RAM(H'50000000-H'53FFFFFF) Clear....
please send ! ('.' & CR stop load)

After the "please send!" message, open "File" > "Send file..." and send the bl2_bp-smarc-rzv2l_pmic.srec file as a text from the terminal software.

In case a message to prompt to clear data like below, please enter "y".
```
SPI Data Clear(H'FF) Check : H'00000000-0000FFFF,Clear OK?(y/n)
```

Following log will be displayed. The end address is depending on the version of AI SDK.

SAVE SPI-FLASH.......
======= Qspi Save Information =================
SpiFlashMemory Stat Address : H'00000000
SpiFlashMemory End Address : H'00009A80
===========================================================

Enter "XLS2" on the terminal to get following messages.

> XLS2
===== Qspi writing of RZ/G2 Board Command =============
Load Program to Spiflash
Writes to any of SPI address.
Micron : MT25QU512
Program Top Address & Qspi Save Address
===== Please Input Program Top Address ============
  Please Input : H'

Enter "00000". The log continues.

  Please Input : H'00000
===== Please Input Qspi Save Address ===
  Please Input : H'

Enter "1D200". The log continues.

  Please Input : H'1D200
Work RAM(H'50000000-H'53FFFFFF) Clear....
please send ! ('.' & CR stop load)

After the "please send!" message, open "File" > "Send file..." and send the fip-smarc-rzv2l_pmic.srec file as a text from the terminal software.

In case a message to prompt to clear data like below, please enter "y".
```
SPI Data Clear(H'FF) Check : H'00000000-0000FFFF,Clear OK?(y/n)
```

Following log will be displayed. The end address is depending on the version of AI SDK.

SAVE SPI-FLASH.......
======= Qspi Save Information =================
SpiFlashMemory Stat Address : H'0001D200
SpiFlashMemory End Address : H'000CC73F
===========================================================

Power-off the board by pressing the power button (SW9) for 2 seconds to change SW11 for booting the board.

4. Setup U-boot setting
Follow the procedure below to set the booting configuration of the board.
1. Insert the microSD card to the Board.
  Note Use the microSD card slot CN10 as shown in the figure.
2. Change SW1 and SW11 setting as shown in the right figure.
3. Connect the Board and Windows PC by the USB Serial to Micro USB cable.
4. Connect the power cable to the Board.
5. Press power button for 1 second to turn on the board.
6. Open the terminal emulator, i.e., Tera Term, and connect with COMS port.
  Note When using Tera Term, change the configuration as explained in Write bootloaders to QSPI on the board.
7. On the terminal emulator, keep pressing ENTER key and on the board, press reset button.
1. U-boot console will be activated.
2. Run the following commands to set the booting configuration.
  env default -a saveenv boot
3. After the boot-up, the login message will be shown on the console.
  smarc-rzv2l login:
4. Log-in to the system using the information below.
  
  user: root
  
  password: none
5. Shutdown the board to finish the U-boot setting.
  
  Shutdown Procedures

After this procedure, you can copy the AI Application and boot the board.
Refer to the Step 7: 2. Deploy Application to the Board in RZ/V2L EVK Getting Started.

A2. Format SD card

When writing the necessary files for the board, microSD card needs to have appropriate format.
Note that you need to run this procedure only once as long as you use the same microSD card.

Follow the instruction below to format the microSD card partitions.

Preparation

Click the button This section contains both eSD and QSPI Bootloader explanation.
Please click the button below to update the explanation according to your bootloader interface.

eSD Bootloader QSPI Bootloader

For eSD eSD explanation will be shown in this style if you click "eSD Bootloader" button above.

For QSPI QSPI explanation will be shown in this style if you click "QSPI Bootloader" button above.

Check the SD card connection

Before inserting the microSD card to your Linux PC, open the terminal on Linux PC and run the following command to check the devices without microSD card.

lsblk

Following is the example output.

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

Insert the microSD card to your Linux PC and run the following command again.
```
lsblk
```

Check the output and confirm the name appeared.
This would be your microSD card device name.
- Following is the example output.
```
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
```
- In this case, followings are your microSD card configuration.
  - /dev/sdb: The device name for the entire microSD card.
  - /dev/sdb1: The paritition name in microSD card. There may be multiple sdb* depending on the microSD card.
  Warning Be careful not to use the name of other device since it may destruct your computer filesystem.

Run the following command to check the automatically mounted microSD card partitions.
```
df
```

Check the output and find the mount point, which is "/media/user/A8D3-393D" in the following example.

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

Unmount the automatically mounted partitions.
```
sudo umount /media/user/A8D3-393B
```
- If there are more than one partitions on microSD card, unmount all partitions.

Create SD card partition

Run fdisk command as shown below to change the partition table according to the following table.

For eSD

Type/Number	Size	Type of Filesystem	Contents
Primary #1	500MB (minimum 128MB)	Ext4	Linux kernel Device tree
Primary #2	All remaining	Ext4	Root filesystem

Note "Type of Filesystem" of "Primary #1 Linux kernel and Device tree" Contents is Ext4.

For QSPI

Type/Number	Size	Type of Filesystem	Contents
Primary #1	500MB (minimum 128MB)	FAT32	Linux kernel Device tree
Primary #2	All remaining	Ext4	Root filesystem

Note "Type of Filesystem" of "Primary #1 Linux kernel and Device tree" Contents is FAT32.

sudo fdisk /dev/sdb

Warning Use device name. Do NOT use partition name such as /dev/sdb1.

Following log will be shown.

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):

Type "o" to console. The log continues.

Created a new DOS disklabel with disk identifier 0x6b6aac6e.

Command (m for help):

Type "n" to console. The log continues.

Partition type
p primary (0 primary, 0 extended, 4 free)
e extended (container for logical partitions)
Select (default p):

Type "p" to console. The log continues.
```
Partition number (1-4, default 1):
```

Press ENTER key. The log continues.

First sector (2048-62333951, default 2048):

Press ENTER key. The log continues.

Last sector, +/-sectors or +/-size{K,M,G,T,P} (2048-62333951,
default 62333951):

Type "+500M" to console. The log continues.

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:

Type "Y" to console. The log continues.

The signature will be removed by a write command.

Command (m for help):

Type "n" to console. The log continues.

Partition type
p primary (1 primary, 0 extended, 3 free)
e extended (container for logical partitions)
Select (default p):

Type "p" to console. The log continues.
```
Partition number (2-4, default 2):
```

Press ENTER key. The log continues.

First sector (1026048-62333951, default 1026048):

Press ENTER key. The log continues.

Last sector, +/-sectors or +/-size{K,M,G,T,P} (1026048-62333951,
default 62333951):

Press ENTER key. The log continues.

Created a new partition 2 of type 'Linux' and of size 29.2 GiB.

Command (m for help):

Type "p" to console. The log continues.

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
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):

For QSPI Additionally, run the following procedures to set the partition as FAT32.

Type "t" to console. The log continues.
```
Partition number (1,2, default 2):
```

Type "1" to console. The log continues.
```
Hex code (type L to list all codes):
```

Type "b" to console. The log continues.

Changed type of partition 'Linux' to 'W95 FAT32'.

Command (m for help):

Type "w" to console. The fdisk interface will end.

The partition table has been altered.
Syncing disks.

Check the partition table with the command below.

partprobe
sudo fdisk -l /dev/sdb

Output would be as follows. Note that there are two partitions.

For eSD

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 83 Linux 
/dev/sdb2 1026048 62333951 61307904 29.2G 83 Linux

For QSPI

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

Run the command below to format and mount the partitions 1.

Note If the partitions were automatically mounted after the procedure 6 of "Check the SD card connection", please unmount them again.

For eSD

sudo mkfs.ext4 -L boot /dev/sdb1

Following log will be shown.

mke2fs 1.45.5 (07-Jan-2020)
Creating filesystem with 128000 4k blocks and 128000 inodes
Filesystem UUID: 0d2b995c-dd96-4ff6-953c-66a4701fa034
Superblock backups stored on blocks:
  32768, 98304
Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done

For QSPI

sudo mkfs.vfat -v -c -F 32 /dev/sdb1

Following log will be shown.

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... 10209
6... 119376... 136528... 153552... 170576... 187472... 204624... 221648... 238
928... 256208... 273744... 290768... 308048... 325328... 342480... 359504... 3
76656... 393680... 410576... 427216... 444624... 462032... 479184... 495952...

Run the command below to format and mount the partitions 2.

sudo mkfs.ext4 -L rootfs /dev/sdb2

Following log will be shown.

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

Eject the microSD card and insert it again to remount the partitions.

After this procedure, you can write the necessary data for the board into microSD card.
Refer to the Write the Linux files to SD card in RZ/V2L EVK Getting Started.

A3. Shutdown RZ/V2L EVK

To power-off the RZ/V2L EVK, follow the procedures below.

Run the shutdown command on board console.
```
shutdown -h now
```
On board console, check that shutdown procedure runs and ends with following log.
```
[xxxxx.xxxxxx] reboot: Power down
```
Press and hold the power button for 2 seconds.

A4. Shutdown RZ/V2H EVK

To power-off the RZ/V2H EVK, follow the procedures below.

Run the shutdown command on board console.
```
shutdown -h now
```
On board console, check that shutdown procedure runs and ends with following log.
```
[xxxxx.xxxxxx] reboot: Power down
```
Turn SW2 to OFF.
Turn SW3 to OFF.

This page explains the additional information of Getting Started.

A1. Setup for QSPI Bootloader

1. Install Terminal Emulator

2. Install the serial port driver

3. Write bootloaders to QSPI on the board

4. Setup U-boot setting

A2. Format SD card

Preparation

Check the SD card connection

Create SD card partition

A3. Shutdown RZ/V2L EVK

A4. Shutdown RZ/V2H EVK