+ WARNING
+
+
+ This page is published for Renesas internal purpose only.
+ Do NOT distribute/share this page to external parties.
+ Since this page is still under the review process, the content may change in the official release.
+
+ Due to the necessary software unavailability (i.e., DRP-AI TVM, AI Applications),
+ you can only run following steps with this internal release.
+
+
+ Step 2: Obtain necessary environment
+
+
+ Step 4: Extract RZ/V AI SDK package
+
+
+ Step 7: Deploy AI Application.
+
+
+ 1. Setup RZ/V2H EVK
+
+
+ 3. Boot RZ/V2H EVK
+
+
+
+
+ A4. Shutdown RZ/V2H EVK
+
+
+
+
+
+
+
+
This page explains the additional information of Getting Started.
+
+
A1. Setup for eMMC Bootloader
+
This section explains how to setup the board for eMMC 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 eMMC 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 eMMC 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.
+
+
+
+ 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.
+
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
+
+
+
+
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'
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.
+
+
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'
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.
+
+
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.
+
+
+
+
+
Insert the microSD card to the Board.
+
+ Note
+ Use the microSD card slot CN10 as shown in the figure.
+
+
+
Change SW1 and SW11 setting as shown in the right figure.
+
+
Connect the Board and Windows PC by the USB Serial to Micro USB cable.
+
+
Connect the power cable to the Board.
+
+
Press power button for 1 second to turn on the board.
+
+
Open the terminal emulator, i.e., Tera Term, and connect with COMS port.
+
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 eMMC Bootloader explanation.
+ Please click the button below to update the explanation according to your bootloader interface.
+
+ eSD Bootloader
+ eMMC Bootloader
+
+
+ For eSD
+ eSD explanation will be shown in this style if you click "eSD Bootloader" button above.
+
+
+ For eMMC
+ eMMC explanation will be shown in this style if you click "eMMC Bootloader" button above.
+
+
+
+
Check the SD card connection
+
+
Before inserting the microSD card to your Linux PC, open the terinal 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 eMMC
+
+
+
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 eMMC
+ 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 eMMC
+
+
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 eMMC
+
+
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.
+
+ WARNING
+
+
+ This page is published for Renesas internal purpose only.
+ Do NOT distribute/share this page to external parties.
+ Since this page is still under the review process, the content may change in the official release.
+
+ Due to the necessary software unavailability (i.e., DRP-AI TVM, AI Applications),
+ you can only run following steps with this internal release.
+
+
+ Step 2: Obtain necessary environment
+
+
+ Step 4: Extract RZ/V AI SDK package
+
+
+ Step 7: Deploy AI Application.
+
+
+ 1. Setup RZ/V2H EVK
+
+
+ 3. Boot RZ/V2H EVK
+
+
+
+
+ A4. Shutdown RZ/V2H EVK
+
+
+
+
+
+
+
+
This page explains how to start-up the AI SDK.
+
AI SDK is build for specific board.
+Its version varies depending on the supported board.
+ Note
+ Hereafter, we use following terminology.
+
+
RZ/V AI SDK: Refers both RZ/V2L AI SDK and RZ/V2H AI SDK.
+
EVK: Refers "Evaluation Board Kit".
+
+
+
+
+
+ Tutorial video
+ Tutorial video is available here.
+ Latest tutorial video is based on RZ/V2L AI SDK version 2.10.
+
+
+
Introduction
+
+
+
+
Getting Started Flow
+ Getting Started explains the instruction to run AI Applications.
+ Common instructions are explained in this document.
+ Board dependent instructions are explained in each EVK Getting Started page.
+
+
+
+
+
+
Software
+ Renesas provides following software.
+
+
+
+
Software
+
Provided on
+
Details
+
+
+
AI Applications
+
GitHub
+
+ This software is a set of following files that runs on the evaluation board kit.
+
+
+ Application Source code (C++)
+
+
+ Pre-build application binary
+
+
+ Other necessary files to run the application
+
+
+ Documentation (README.md)
+
+
+ "Getting Started" page (this page) explains how to run the AI Applications.
+
+
+
+
RZ/V AI SDK
+
Renesas Website
+
+ This software is a development environment for AI Applications.
+ Provided as a zip file.
+ "Getting Started" page (this page) explains how to use RZ/V AI SDK to run the AI Applications.
+
+ Following items are included in the RZ/V2L Evaluation Board Kit.
+
+
+
+
Equipment
+
Details
+
+
+
RZ/V2L Evaluation Board
+
Evaluation board itself.
+
+
+
MIPI Camera Module
+
Google Coral Camera.
+
Note that the CMOS sensor (OV5645) in the camera is no longer available, and should not be used for mass production. Any software support provided is for evaluation purposes only.
+
+
+
MicroUSB to Serial Cable
+
For serial communication between PC and the board.
+
+
+
+
+
+
+
+
+
Step 2: Obtain necessary environment
+
1. Necessary Equipments
+
Please prepare the following equipments for your EVK.
+
+
+
For
+
Equipment
+
Details
+
+
+
+ RZ/V2L
+
+
+ RZ/V2L EVK
+
+
+ Evaluation Board Kit for RZ/V2L. Includes followings.
+
+
+ MIPI Camera Module(Google Coral Camera)
+
+
+ Note that the CMOS sensor (OV5645) in the camera is no longer available, and should not be used for mass production.
+ Any software support provided is for evaluation purposes only.
+
+
+
MicroUSB to Serial Cable for serial communication.
+
+
+
+
+
+ AC Adapter
+
+
+ USB Power Delivery adapter for the board power supply.
+
+
+
+
+ MicroHDMI Cable
+
+
+ Used to connect the HDMI Monitor and the board.
+ RZ/V2L EVK has microHDMI port.
+
+
+
+
+ USB Camera
+
+
+ Optional. AI Applications support USB camera input.
+ Supported resolution: 640x480
+ Supported format: 'YUYV' (YUYV 4:2:2)
+
+
+
+
+ Windows PC
+
+
+ Optional. Used as the serial communication console for eMMC Bootloader.
+ Operating Environment : Windows 10
+
+
+
+
+ RZ/V2H
+
+
+ RZ/V2H EVK
+
+
+ Evaluation Board Kit for RZ/V2H.
+
+
+
+
+ AC Adapter
+
+
+ USB Power Delivery adapter for the board power supply.
+ 100W is required.
+
+
+
+
+ HDMI Cable
+
+
+ Used to connect the HDMI Monitor and the board.
+ RZ/V2H EVK has HDMI port.
+
+
+
+
+ USB Camera
+
+
+ Since RZ/V2H EVK does not include camera module, this will be the standard camera input source.
+ Supported resolution: 640x480
+ Supported format: 'YUYV' (YUYV 4:2:2)
+
+ To use MIPI camera, please refer to e-CAM22_CURZH provided by e-con Systems.
+ e-CAM22_CURZH camera supports FHD(1920x1080) resolution.
+
+
+
+
+
+ Common
+
+
+ USB Cable Type-C
+
+
+ Connect AC adapter and the board.
+
+
+
+
+ HDMI Monitor
+
+
+ Used to display the graphics of the board.
+
+
+
+
+ microSD card
+
+
+ Must have over 4GB capacity of blank space.
+ Operating Environment: Transcend UHS-I microSD 300S 16GB
+
+
+
+
+ Linux PC
+
+
+ Used for Setup microSD card and RZ/V AI SDK Setup.
+ Operating Environment: Ubuntu 20.04
+
+
+
+
+ SD card reader
+
+
+ Used for setting up microSD card.
+
+
+
+
+ USB Hub
+
+
+ Used to connect USB Keyboard and USB Mouse to the board.
+
+
+
+
+ USB Keyboard
+
+
+ Used to type strings on the terminal of board.
+
+
+
+
+ USB Mouse
+
+
+ Used to operate the mouse on the screen of board.
+
+
+
+
+ Note
+ USB camera has different supported resolution and format.
+ To check the specification of your USB camera, use v4l2-ctl command.
+
+
+ In addition to the RZ/V2L Evaluation Board Kit, please prepare the following equipments.
+
+ Note
+ Serial to MicroUSB Cable and MIPI Camera Module (Google Coral camera) is included in RZ/V2L Evaluation Board Kit.
+
+
+
+
Equipment
+
Details
+
+
+
HDMI Monitor
+
Used to display the graphics.
+
+
+
Micro HDMI Cable
+
Used to connect the HDMI Monitor and the board.
+
+
+
AC adapter
+
Power supply to the board.
+
+
+
USB Cable Type-C
+
Connect AC adapter and the board.
+
+
+
microSD card
+
Must have over 4GB capacity of blank space. Operating Environment: Transcend UHS-I microSD 300S 16GB
+
+
+
Linux PC
+
Used for Setup microSD card and RZ/V2L AI SDK Setup.
+ Operating Environment: Ubuntu 20.04
+
+
+
SD card reader
+
Used for setting up microSD card.
+
+
+
Windows PC
+
Optional. Used as the serial communication console for eMMC Bootloader.
+ Operating Environment : Windows 10
Create new directory to be mounted on Docker container.
+
+
mkdir${WORK}/ai_sdk_setup/data
+
+
+
Create docker container. Here, <rzv2l/rzv2h>_ai_sdk_container is a name of docker container, which can be changed by user.
+
+
For RZ/V2L
+
+
docker run -it--name rzv2l_ai_sdk_container -v$(pwd)/data:/drp-ai_tvm/data rzv2l_ai_sdk_image
+
+
+
For RZ/V2H
+
+
docker run -it--name rzv2h_ai_sdk_container -v$(pwd)/data:/drp-ai_tvm/data rzv2h_ai_sdk_image
+
+
+
+ The local $(pwd)/data is mounted to /drp-ai_tvm/data on the Docker container by the above command option.
+ For example, you can use this directory to copy files created on the Docker container to your local environment.
+
+
+
In docker container, run the following command to copy libtvm_runtime.so, which is the necessary file for the board, to host machine.
+
+
+ Note
+ Following procedures are for users who would like to build the application from the source code.
+ If you would like to run the application as quickly as possible, you can skip this step and proceed to the next step (Step 7: Deploy AI Application) since pre-build application binary is provided.
+
+ This repository only contains AI Applications for RZ/V2L EVK.
+ It does not provide instructions for RZ/V AI SDK.
+ Please refer to the instruction provided in this page.
+
+ Check the README.md document provided in application directory and follow the instruction in the chapter called "Application: Build Stage" (or similar) to build the application.
+
+ Example:
+ In R01_object_detection application, follow the instruction here to generate the following application binary.
+
+
object_detection
+
+
+
+
+
+
+
+
+ After you generated the application binary, please proceed to Step 7
+
+
+
+
Option 2: For <Application 2>
+
+
Run (or start) docker container.
+
+ Example:
+ Run the following command to start the docker container created in Step 5.
+
+
docker start -i rzv2l_ai_sdk_container
+
+
+
+
Change the environment variable to use the cross compiler.
+
+
You have experienced the AI Application development procedures.
+Next step is to change the application to create your own AI Application.
+You can use the applications listed in AI Applications to expand your ideas!
+
+ WARNING
+
+
+ This page is published for Renesas internal purpose only.
+ Do NOT distribute/share this page to external parties.
+ Since this page is still under the review process, the content may change in the official release.
+
+ Due to the necessary software unavailability (i.e., DRP-AI TVM, AI Applications),
+ you can only run following steps with this internal release.
+
+
+ Step 2: Obtain necessary environment
+
+
+ Step 4: Extract RZ/V AI SDK package
+
+
+ Step 7: Deploy AI Application.
+
+
+ 1. Setup RZ/V2H EVK
+
+
+ 3. Boot RZ/V2H EVK
+
+
+
+
+ A4. Shutdown RZ/V2H EVK
+
+
+
+
+
+
+
+
+
This page explains how to start-up the AI SDK on the RZ/V2H Evaluation Board Kit.
+
+
Supported version: RZ/V2H AI SDK v3.00
+
+
+ Terminology
+
+
+
+
+
Getting Started Flow
+
+
+
+ This page explains RZ/V2H EVK dependent instructions.
+ Common instructions are explained in Getting Started page.
+
+
+
+ The RZ/V2H EVK is the ideal board kit for RZ/V2H evaluation.
+
+ MIPI camera module is not included in EVK.
+
+ As an input device, AI Applications support USB camera with VGA (640x480) resolution.
+
+ To use MIPI camera, please refer to e-CAM22_CURZH camera provided by e-con Systems.
+
+ e-CAM22_CURZH camera supports FHD (1920x1080) resolution.
+
+
+
+
+
+
+
+
+ Following items are included in the RZ/V2H EVK.
+
+
+
+
+
Equipment
+
Details
+
+
+
RZ/V2H Evaluation Board
+
Evaluation board itself.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Step 7: Deploy AI Application
+ This section explains how to deploy the AI Application to the RZ/V2H EVK.
+
+
+
+
+ To boot the board, bootloader and other Linux necessary files are required.
+ Following bootloader is available on RZ/V2H AI SDK.
+
+
+ eSD Bootloader: The board boots up using the bootloader written on microSD card.
+
+
+ Other necessary files, i.e. Linux kernel and root filesystem, are stored on microSD card.
+ You can use Linux PC to format the microSD card and expand the kernel and the root filesystem using SD card reader.
+
+
+
+
1. Setup RZ/V2H EVK
+ microSD card needs to contain bootloaders, the Linux kernel and root filesystem to boot-up the board.
+ RZ/V2H AI SDK supports the WIC format for SD card image.
+ You can use Linux PC to write the SD card image into microSD card with SD card reader.
+
+ 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 with the latest bootloader, Linux kernel, Linux device tree file and root filesystem, skip this step and proceed to the next procedure (2. Deploy Application to the Board).
+
+
+ As explained in Necessary Software of Getting Started Step 2, make sure that bmap-tools is installed on Linux PC.
+ If you have not installed the bmap-tools, install it using following command on Host PC (Not in the docker container).
+
+
sudo apt install bmap-tools
+
+
+
+
Write the Linux files to SD card
+
+ Run the below command to decompress ${WORK}/board_setup/eSD.zip.
+
+
cd${WORK}/board_setup
+unzip eSD.zip
+
+ Following files are necessary.
+ They are in the ${WORK}/board_setup/eSD directory.
+
+
+
+
File
+
Description
+
+
+
core-image-weston-rzv2h-evk-ver1.wic.bmap
+
SD card image
+
+
+
core-image-weston-rzv2h-evk-ver1.wic.gz
+
+
+ Follow the instruction below to prepare the microSD card.
+
+ Warning
+ Here, we use "/dev/sdb" as microSD card device name.
+
+
+
To use bmaptools, microSD card partitions must be unmounted.
+ Run the following command to check the automatically mounted microSD card partitions.
+
+
df-h
+
+
+
+ Check the output and find the mount point, which is "/media/user/9016-4EF8" in the following example.
+
+
Filesystem Size Used Avail Use% Mounted on
+:
+snip
+:
+/dev/sdb1 15G 32K 15G 1% /media/user/9016-4EF8
+
+
+ Warning
+ Here, we use "/dev/sdb" as microSD card device name.
+
+
+
+ Unmount the automatically mounted partitions.
+
+
sudo umount /media/user/9016-4EF8
+
+
+ Note
+ If there are more than one partitions on microSD card, unmount all partitions.
+
+
+
Run the following command to write SD card image.
+
+
+ Run the following command to mount the partition 2, which contains the root filesystem.
+
+
sudo mount /dev/sdb2 /mnt/sd
+
+
+ Warning
+ Change /dev/sdb to your microSD card device name.
+
+
+
+ Create the application directory on root filesystem.
+
+
sudo mkdir /mnt/sd/home/root/tvm
+
+
+ Note
+ Directory name tvm can be determined by user.
+
+
+
+ Copy the necessary files in execution environment.
+ Check the README.md document provided in application directory and follow the instruction in the chapter called "Application: Deploy Stage" (or similar) to deploy the application.
+
+
+ Example:
+ In R01_object_detection application, follow the instruction in here to find files to be copied.
+
+
+ Use the following command to copy the files to root filesystem.
+
+
+
sudo cp$WORK/ai_sdk_setup/data/<Path to target file>/<filename> /mnt/sd/home/root/tvm
+
+
+
+
+ Run the following command to sync the data with memory.
+
+
+
sync
+
+
+
+ Run the following command to unmount the partition 2.
+
+
+
sudo umount /mnt/sd
+
+
+
+ Eject the microSD card by running the following command and remove the microSD card from Linux PC.
+
+
sudo eject /dev/sdb
+
+
+ Warning
+ Change /dev/sdb to your microSD card device name.
+
+
+
+
+
3. Boot RZ/V2H EVK
+ This section explains how to boot the RZ/V2H EVK.
+
+ Follow the instruction below to boot the board.
+
+
+
+
+
+
+ Insert the microSD card to the Board.
+
+ Note
+ Use the microSD card slot SD1 on the Board as shown in the figure.
+
+
+
Change DSW1 and DSW2 setting as shown in the figure.
+
Connect the USB mouse and USB keyboard and USB camera via USB hub.
+
+ Note
+ There are USB 2.0 port and USB 3.0 port on RZ/V2H EVK.
+ Please connect your USB camera to appropriate port according to its requirement.
+ Here, USB camera is connected to USB 2.0 via USB hub.
+
+
+
Connect the HDMI monitor to the Board.
+
Connect the power cable to the Board.
+
Turn the SW3 to ON.
+
Turn the SW2 to ON to power on the Board
+
+
+
+
+
+
+
+
+
+
+
After the boot-up, following screen will be displayed on HDMI monitor.
+
+
+
+
+
+
+
+
+
+
Click the icon at the top-left corner to open the terminal.
+ Follow the instructions explained in the document (README.md) of applications on GitHub.
+
+
+ Example:
+ For R01_object_detection application, follow the instruction here to run the application.
+
+ If you have successfully run the application, you will see following window on HDMI screen.
+
+
+
+
diff --git a/docs/_site/history.html b/docs/_site/history.html
index 43cc9f2..9ca420b 100755
--- a/docs/_site/history.html
+++ b/docs/_site/history.html
@@ -30,10 +30,10 @@
+{"@context":"https://schema.org","@type":"WebPage","dateModified":"2024-01-26T14:34:19+09:00","description":"The best solution for starting your AI applications.","headline":"Renesas RZ/V AI","url":"https://renesas-rz.github.io/rzv_ai_sdk/2.10/history.html"}
-
+
diff --git a/docs/_site/howto_build_aisdk.html b/docs/_site/howto_build_aisdk.html
index 18d9336..a1f0859 100755
--- a/docs/_site/howto_build_aisdk.html
+++ b/docs/_site/howto_build_aisdk.html
@@ -33,7 +33,7 @@
{"@context":"https://schema.org","@type":"WebPage","dateModified":"2023-12-11T19:09:38+09:00","description":"The best solution for starting your AI applications.","headline":"Renesas RZ/V AI","url":"https://renesas-rz.github.io/rzv_ai_sdk/2.10/howto_build_aisdk.html"}
-
+
diff --git a/docs/_site/howto_retrain.html b/docs/_site/howto_retrain.html
index 2842c29..c3620b2 100644
--- a/docs/_site/howto_retrain.html
+++ b/docs/_site/howto_retrain.html
@@ -30,10 +30,10 @@
+{"@context":"https://schema.org","@type":"WebPage","dateModified":"2024-01-26T14:34:19+09:00","description":"The best solution for starting your AI applications.","headline":"Renesas RZ/V AI","url":"https://renesas-rz.github.io/rzv_ai_sdk/2.10/howto_retrain.html"}
-
+
diff --git a/docs/_site/img/V2H_EVK_v1.jpg b/docs/_site/img/V2H_EVK_v1.jpg
new file mode 100755
index 0000000..af298ab
Binary files /dev/null and b/docs/_site/img/V2H_EVK_v1.jpg differ
diff --git a/docs/_site/img/aisdk_sc_v2h.svg b/docs/_site/img/aisdk_sc_v2h.svg
new file mode 100755
index 0000000..247fda1
--- /dev/null
+++ b/docs/_site/img/aisdk_sc_v2h.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/docs/_site/img/block_rzv.svg b/docs/_site/img/block_rzv.svg
new file mode 100755
index 0000000..f077402
--- /dev/null
+++ b/docs/_site/img/block_rzv.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/docs/_site/img/board.svg b/docs/_site/img/board.svg
new file mode 100755
index 0000000..6fe7475
--- /dev/null
+++ b/docs/_site/img/board.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/docs/_site/img/esd.svg b/docs/_site/img/esd.svg
new file mode 100755
index 0000000..493ac3e
--- /dev/null
+++ b/docs/_site/img/esd.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/docs/_site/img/getting_started_flow_base.svg b/docs/_site/img/getting_started_flow_base.svg
new file mode 100755
index 0000000..22d751c
--- /dev/null
+++ b/docs/_site/img/getting_started_flow_base.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/docs/_site/img/getting_started_flow_v2h.svg b/docs/_site/img/getting_started_flow_v2h.svg
new file mode 100755
index 0000000..30e2cf9
--- /dev/null
+++ b/docs/_site/img/getting_started_flow_v2h.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/docs/_site/img/getting_started_flow_v2l.svg b/docs/_site/img/getting_started_flow_v2l.svg
new file mode 100755
index 0000000..ca603ca
--- /dev/null
+++ b/docs/_site/img/getting_started_flow_v2l.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/docs/_site/img/objectdetection_v2h.png b/docs/_site/img/objectdetection_v2h.png
new file mode 100755
index 0000000..0bd9807
Binary files /dev/null and b/docs/_site/img/objectdetection_v2h.png differ
diff --git a/docs/_site/img/rzv2h_evk_diagonal.jpg b/docs/_site/img/rzv2h_evk_diagonal.jpg
new file mode 100755
index 0000000..9979c26
Binary files /dev/null and b/docs/_site/img/rzv2h_evk_diagonal.jpg differ
diff --git a/docs/_site/img/v2h_evk_boot.png b/docs/_site/img/v2h_evk_boot.png
new file mode 100755
index 0000000..28a1323
Binary files /dev/null and b/docs/_site/img/v2h_evk_boot.png differ
diff --git a/docs/_site/img/v2h_evk_shutdown.png b/docs/_site/img/v2h_evk_shutdown.png
new file mode 100755
index 0000000..a02d7ac
Binary files /dev/null and b/docs/_site/img/v2h_evk_shutdown.png differ
diff --git a/docs/_site/img/v2h_evk_wayland.png b/docs/_site/img/v2h_evk_wayland.png
new file mode 100755
index 0000000..bc77433
Binary files /dev/null and b/docs/_site/img/v2h_evk_wayland.png differ
diff --git a/docs/_site/img/v2h_mem.png b/docs/_site/img/v2h_mem.png
new file mode 100755
index 0000000..926ddbe
Binary files /dev/null and b/docs/_site/img/v2h_mem.png differ
diff --git a/docs/_site/img/v2l_mem.png b/docs/_site/img/v2l_mem.png
new file mode 100755
index 0000000..08b5958
Binary files /dev/null and b/docs/_site/img/v2l_mem.png differ
diff --git a/docs/_site/index.html b/docs/_site/index.html
index 25b5100..f3f8169 100755
--- a/docs/_site/index.html
+++ b/docs/_site/index.html
@@ -30,10 +30,10 @@
+{"@context":"https://schema.org","@type":"WebSite","dateModified":"2024-01-26T14:34:19+09:00","description":"The best solution for starting your AI applications.","headline":"Renesas RZ/V AI","name":"Renesas RZ/V AI","url":"https://renesas-rz.github.io/rzv_ai_sdk/2.10/"}
-
+
diff --git a/docs/_site/sitemap.xml b/docs/_site/sitemap.xml
old mode 100644
new mode 100755
index b56c658..784525a
--- a/docs/_site/sitemap.xml
+++ b/docs/_site/sitemap.xml
@@ -2,7 +2,7 @@
https://renesas-rz.github.io/rzv_ai_sdk/latest/ai-sdk.html
-2023-12-11T19:09:38+09:00
+2024-01-26T14:34:19+09:00https://renesas-rz.github.io/rzv_ai_sdk/latest/appendix.html
@@ -18,11 +18,11 @@
https://renesas-rz.github.io/rzv_ai_sdk/latest/getting_started.html
-2023-12-11T19:09:38+09:00
+2024-01-26T14:34:19+09:00https://renesas-rz.github.io/rzv_ai_sdk/latest/history.html
-2023-12-11T19:09:38+09:00
+2024-01-26T14:34:19+09:00https://renesas-rz.github.io/rzv_ai_sdk/latest/howto_build_aisdk.html
@@ -30,11 +30,11 @@
https://renesas-rz.github.io/rzv_ai_sdk/latest/howto_retrain.html
-2024-01-25T20:09:49+09:00
+2024-01-26T14:34:19+09:00https://renesas-rz.github.io/rzv_ai_sdk/latest/
-2023-12-11T19:09:38+09:00
+2024-01-26T14:34:19+09:00https://renesas-rz.github.io/rzv_ai_sdk/latest/version.html
diff --git a/docs/_site/version.html b/docs/_site/version.html
index f9a4de9..2d9abb6 100755
--- a/docs/_site/version.html
+++ b/docs/_site/version.html
@@ -33,7 +33,7 @@
{"@context":"https://schema.org","@type":"WebPage","dateModified":"2023-12-11T19:09:38+09:00","description":"The best solution for starting your AI applications.","headline":"Renesas RZ/V AI","url":"https://renesas-rz.github.io/rzv_ai_sdk/2.10/version.html"}
-
+
diff --git a/docs/appendix_internal.md b/docs/appendix_internal.md
new file mode 100755
index 0000000..f7e7cf7
--- /dev/null
+++ b/docs/appendix_internal.md
@@ -0,0 +1,883 @@
+---
+layout: default
+---
+
+
+
+
+
+
+
+Getting Started Appendix
+
+
+
+
+ WARNING
+
+
+ This page is published for Renesas internal purpose only.
+ Do NOT distribute/share this page to external parties.
+ Since this page is still under the review process, the content may change in the official release.
+
+ Due to the necessary software unavailability (i.e., DRP-AI TVM, AI Applications),
+ you can only run following steps with this internal release.
+
+
+ Step 2: Obtain necessary environment
+
+
+ Step 4: Extract RZ/V AI SDK package
+
+
+ Step 7: Deploy AI Application.
+
+
+ 1. Setup RZ/V2H EVK
+
+
+ 3. Boot RZ/V2H EVK
+
+
+
+
+ A4. Shutdown RZ/V2H EVK
+
+
+
+
+
+
+
+
This page explains the additional information of Getting Started.
+
+
A1. Setup for eMMC Bootloader
+This section explains how to setup the board for eMMC 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 eMMC 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 eMMC 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.
+
+
+
+ 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.
+
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
+
+
+
+
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.
+{% highlight console %}
+ SCIF Download mode
+(C) Renesas Electronics Corp.
+-- Load Program to System RAM ---------------
+please send !
+{% endhighlight %}
+
+
+ Open "File" > "Send file..." and send the Flash Writer file (*.mot) as a text.
+ If following message is displayed, the file transfer suceeded.
+{% highlight console %}
+Flash writer for RZ/V2 Series Vx.xx xxx.xx,20xx
+Product Code : RZ/V2L
+>
+{% endhighlight %}
+
+
Enter "XLS2" on the terminal to get following messages.
+{% highlight console %}
+> 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'
+{% endhighlight %}
+
+
Enter "11E00". The log continues.
+{% highlight console %}
+ Please Input : H'11E00
+===== Please Input Qspi Save Address ===
+ Please Input : H'
+{% endhighlight %}
+
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".
+{% highlight console %}
+SPI Data Clear(H'FF) Check : H'00000000-0000FFFF,Clear OK?(y/n)
+{% endhighlight %}
+
+
Following log will be displayed.
+{% highlight console %}
+SAVE SPI-FLASH.......
+======= Qspi Save Information =================
+SpiFlashMemory Stat Address : H'00000000
+SpiFlashMemory End Address : H'00009A80
+===========================================================
+{% endhighlight %}
+
+
Enter "XLS2" on the terminal to get following messages.
+{% highlight console %}
+> 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'
+{% endhighlight %}
+
+
Enter "00000". The log continues.
+{% highlight console %}
+ Please Input : H'00000
+===== Please Input Qspi Save Address ===
+ Please Input : H'
+{% endhighlight %}
+
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".
+{% highlight console %}
+SPI Data Clear(H'FF) Check : H'00000000-0000FFFF,Clear OK?(y/n)
+{% endhighlight %}
+
+
Following log will be displayed.
+{% highlight console %}
+SAVE SPI-FLASH.......
+======= Qspi Save Information =================
+SpiFlashMemory Stat Address : H'0001D200
+SpiFlashMemory End Address : H'000CC73F
+===========================================================
+{% endhighlight %}
+
+
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.
+
+
+
+
+
Insert the microSD card to the Board.
+
+ Note
+ Use the microSD card slot CN10 as shown in the figure.
+
+
+
Change SW1 and SW11 setting as shown in the right figure.
+
+
Connect the Board and Windows PC by the USB Serial to Micro USB cable.
+
+
Connect the power cable to the Board.
+
+
Press power button for 1 second to turn on the board.
+
+
Open the terminal emulator, i.e., Tera Term, and connect with COMS port.
+
+ 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 eMMC Bootloader explanation.
+ Please click the button below to update the explanation according to your bootloader interface.
+
+ eSD Bootloader
+ eMMC Bootloader
+
+
+ For eSD
+ eSD explanation will be shown in this style if you click "eSD Bootloader" button above.
+
+
+ For eMMC
+ eMMC explanation will be shown in this style if you click "eMMC Bootloader" button above.
+
+
+
+
Check the SD card connection
+
+
Before inserting the microSD card to your Linux PC, open the terinal on Linux PC and run the following command to check the devices without microSD card.
+{% highlight shell %}
+lsblk
+{% endhighlight %}
+ Following is the example output.
+{% highlight shell %}
+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
+{% endhighlight %}
+
+
Insert the microSD card to your Linux PC and run the following command again.
+{% highlight shell %}
+lsblk
+{% endhighlight %}
+
+
Check the output and confirm the name appeared.
+ This would be your microSD card device name.
+
+
Following is the example output.
+{% highlight shell %}
+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
+{% endhighlight %}
+
+
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.
+{% highlight shell %}
+df
+{% endhighlight %}
+
+
Check the output and find the mount point, which is "/media/user/A8D3-393D" in the following example.
+{% highlight shell %}
+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
+{% endhighlight %}
+
+ Warning
+ Use device name. Do NOT use partition name such as /dev/sdb1.
+
+
+
Following log will be shown.
+{% highlight shell %}
+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):
+{% endhighlight %}
+
+
Type "o" to console. The log continues.
+{% highlight shell %}
+Created a new DOS disklabel with disk identifier 0x6b6aac6e.
+
+Command (m for help):
+{% endhighlight %}
+
+
Type "n" to console. The log continues.
+{% highlight shell %}
+Partition type
+p primary (0 primary, 0 extended, 4 free)
+e extended (container for logical partitions)
+Select (default p):
+{% endhighlight %}
+
+
Type "p" to console. The log continues.
+{% highlight shell %}
+Partition number (1-4, default 1):
+{% endhighlight %}
+
+
Press ENTER key. The log continues.
+{% highlight shell %}
+First sector (2048-62333951, default 2048):
+{% endhighlight %}
+
+
Press ENTER key. The log continues.
+{% highlight shell %}
+Last sector, +/-sectors or +/-size{K,M,G,T,P} (2048-62333951,
+default 62333951):
+{% endhighlight %}
+
+
Type "+500M" to console. The log continues.
+{% highlight shell %}
+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:
+{% endhighlight %}
+
+
Type "Y" to console. The log continues.
+{% highlight shell %}
+The signature will be removed by a write command.
+
+Command (m for help):
+{% endhighlight %}
+
+
Type "n" to console. The log continues.
+{% highlight shell %}
+Partition type
+p primary (1 primary, 0 extended, 3 free)
+e extended (container for logical partitions)
+Select (default p):
+{% endhighlight %}
+
+
Type "p" to console. The log continues.
+{% highlight shell %}
+Partition number (2-4, default 2):
+{% endhighlight %}
+
+
Press ENTER key. The log continues.
+{% highlight shell %}
+First sector (1026048-62333951, default 1026048):
+{% endhighlight %}
+
+
Press ENTER key. The log continues.
+{% highlight shell %}
+Last sector, +/-sectors or +/-size{K,M,G,T,P} (1026048-62333951,
+default 62333951):
+{% endhighlight %}
+
+
Press ENTER key. The log continues.
+{% highlight shell %}
+Created a new partition 2 of type 'Linux' and of size 29.2 GiB.
+
+Command (m for help):
+{% endhighlight %}
+
+
Type "p" to console. The log continues.
+{% highlight shell %}
+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):
+{% endhighlight %}
+
+
+ For eMMC
+ Additionally, run the following procedures to set the partition as FAT32.
+
+
Type "t" to console. The log continues.
+{% highlight shell %}
+Partition number (1,2, default 2):
+{% endhighlight %}
+
+
Type "1" to console. The log continues.
+{% highlight shell %}
+Hex code (type L to list all codes):
+{% endhighlight %}
+
+
Type "b" to console. The log continues.
+{% highlight shell %}
+Changed type of partition 'Linux' to 'W95 FAT32'.
+
+Command (m for help):
+{% endhighlight %}
+
+
+
+
+
Type "w" to console. The fdisk interface will end.
+{% highlight shell %}
+The partition table has been altered.
+Syncing disks.
+{% endhighlight %}
+
+
+
+
Check the partition table with the command below.
+{% highlight shell %}
+partprobe
+sudo fdisk -l /dev/sdb
+{% endhighlight %}
+
Output would be as follows. Note that there are two partitions.
+
+ For eSD
+{% highlight shell %}
+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
+{% endhighlight %}
+
+
+ For eMMC
+{% highlight shell %}
+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
+{% endhighlight %}
+
+
+
+
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.
+
+To power-off the RZ/V2L EVK, follow the procedures below.
+
+
+
+
Run the shutdown command on board console.
+
+{% highlight shell %}
+shutdown -h now
+{% endhighlight %}
+
+
On board console, check that shutdown procedure runs and ends with following log.
+
+{% highlight shell %}
+[xxxxx.xxxxxx] reboot: Power down
+{% endhighlight %}
+
+
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.
+
+{% highlight shell %}
+shutdown -h now
+{% endhighlight %}
+
+
On board console, check that shutdown procedure runs and ends with following log.
+
+{% highlight shell %}
+[xxxxx.xxxxxx] reboot: Power down
+{% endhighlight %}
+
+ WARNING
+
+
+ This page is published for Renesas internal purpose only.
+ Do NOT distribute/share this page to external parties.
+ Since this page is still under the review process, the content may change in the official release.
+
+ Due to the necessary software unavailability (i.e., DRP-AI TVM, AI Applications),
+ you can only run following steps with this internal release.
+
+
+ Step 2: Obtain necessary environment
+
+
+ Step 4: Extract RZ/V AI SDK package
+
+
+ Step 7: Deploy AI Application.
+
+
+ 1. Setup RZ/V2H EVK
+
+
+ 3. Boot RZ/V2H EVK
+
+
+
+
+ A4. Shutdown RZ/V2H EVK
+
+
+
+
+
+
+
+
This page explains how to start-up the AI SDK.
+AI SDK is build for specific board.
+Its version varies depending on the supported board.
+
+ Note
+ Hereafter, we use following terminology.
+
+
RZ/V AI SDK: Refers both RZ/V2L AI SDK and RZ/V2H AI SDK.
+
EVK: Refers "Evaluation Board Kit".
+
+
+
+
+
+ Tutorial video
+ Tutorial video is available here.
+ Latest tutorial video is based on RZ/V2L AI SDK version 2.10.
+
+
+
Introduction
+
+
+
+
Getting Started Flow
+ Getting Started explains the instruction to run AI Applications.
+ Common instructions are explained in this document.
+ Board dependent instructions are explained in each EVK Getting Started page.
+
+
+
+
+
+
Software
+ Renesas provides following software.
+
+
+
+
Software
+
Provided on
+
Details
+
+
+
AI Applications
+
GitHub
+
+ This software is a set of following files that runs on the evaluation board kit.
+
+
+ Application Source code (C++)
+
+
+ Pre-build application binary
+
+
+ Other necessary files to run the application
+
+
+ Documentation (README.md)
+
+
+ "Getting Started" page (this page) explains how to run the AI Applications.
+
+
+
+
RZ/V AI SDK
+
Renesas Website
+
+ This software is a development environment for AI Applications.
+ Provided as a zip file.
+ "Getting Started" page (this page) explains how to use RZ/V AI SDK to run the AI Applications.
+
+ Following items are included in the RZ/V2L Evaluation Board Kit.
+
+
+
+
Equipment
+
Details
+
+
+
RZ/V2L Evaluation Board
+
Evaluation board itself.
+
+
+
MIPI Camera Module
+
Google Coral Camera.
+
Note that the CMOS sensor (OV5645) in the camera is no longer available, and should not be used for mass production. Any software support provided is for evaluation purposes only.
+
+
+
MicroUSB to Serial Cable
+
For serial communication between PC and the board.
+
+
+
+
+
+
+
+
+
Step 2: Obtain necessary environment
+
1. Necessary Equipments
+ Please prepare the following equipments for your EVK.
+
+
+
For
+
Equipment
+
Details
+
+
+
+ RZ/V2L
+
+
+ RZ/V2L EVK
+
+
+ Evaluation Board Kit for RZ/V2L. Includes followings.
+
+
+ MIPI Camera Module(Google Coral Camera)
+
+
+ Note that the CMOS sensor (OV5645) in the camera is no longer available, and should not be used for mass production.
+ Any software support provided is for evaluation purposes only.
+
+
+
MicroUSB to Serial Cable for serial communication.
+
+
+
+
+
+ AC Adapter
+
+
+ USB Power Delivery adapter for the board power supply.
+
+
+
+
+ MicroHDMI Cable
+
+
+ Used to connect the HDMI Monitor and the board.
+ RZ/V2L EVK has microHDMI port.
+
+
+
+
+ USB Camera
+
+
+ Optional. AI Applications support USB camera input.
+ Supported resolution: 640x480
+ Supported format: 'YUYV' (YUYV 4:2:2)
+
+
+
+
+ Windows PC
+
+
+ Optional. Used as the serial communication console for eMMC Bootloader.
+ Operating Environment : Windows 10
+
+
+
+
+ RZ/V2H
+
+
+ RZ/V2H EVK
+
+
+ Evaluation Board Kit for RZ/V2H.
+
+
+
+
+ AC Adapter
+
+
+ USB Power Delivery adapter for the board power supply.
+ 100W is required.
+
+
+
+
+ HDMI Cable
+
+
+ Used to connect the HDMI Monitor and the board.
+ RZ/V2H EVK has HDMI port.
+
+
+
+
+ USB Camera
+
+
+ Since RZ/V2H EVK does not include camera module, this will be the standard camera input source.
+ Supported resolution: 640x480
+ Supported format: 'YUYV' (YUYV 4:2:2)
+
+ To use MIPI camera, please refer to e-CAM22_CURZH provided by e-con Systems.
+ e-CAM22_CURZH camera supports FHD(1920x1080) resolution.
+
+
+
+
+
+ Common
+
+
+ USB Cable Type-C
+
+
+ Connect AC adapter and the board.
+
+
+
+
+ HDMI Monitor
+
+
+ Used to display the graphics of the board.
+
+
+
+
+ microSD card
+
+
+ Must have over 4GB capacity of blank space.
+ Operating Environment: Transcend UHS-I microSD 300S 16GB
+
+
+
+
+ Linux PC
+
+
+ Used for Setup microSD card and RZ/V AI SDK Setup.
+ Operating Environment: Ubuntu 20.04
+
+
+
+
+ SD card reader
+
+
+ Used for setting up microSD card.
+
+
+
+
+ USB Hub
+
+
+ Used to connect USB Keyboard and USB Mouse to the board.
+
+
+
+
+ USB Keyboard
+
+
+ Used to type strings on the terminal of board.
+
+
+
+
+ USB Mouse
+
+
+ Used to operate the mouse on the screen of board.
+
+
+
+
+ Note
+ USB camera has different supported resolution and format.
+ To check the specification of your USB camera, use v4l2-ctl command.
+
+
+ In addition to the RZ/V2L Evaluation Board Kit, please prepare the following equipments.
+
+ Note
+ Serial to MicroUSB Cable and MIPI Camera Module (Google Coral camera) is included in RZ/V2L Evaluation Board Kit.
+
+
+
+
Equipment
+
Details
+
+
+
HDMI Monitor
+
Used to display the graphics.
+
+
+
Micro HDMI Cable
+
Used to connect the HDMI Monitor and the board.
+
+
+
AC adapter
+
Power supply to the board.
+
+
+
USB Cable Type-C
+
Connect AC adapter and the board.
+
+
+
microSD card
+
Must have over 4GB capacity of blank space. Operating Environment: Transcend UHS-I microSD 300S 16GB
+
+
+
Linux PC
+
Used for Setup microSD card and RZ/V2L AI SDK Setup.
+ Operating Environment: Ubuntu 20.04
+
+
+
SD card reader
+
Used for setting up microSD card.
+
+
+
Windows PC
+
Optional. Used as the serial communication console for eMMC Bootloader.
+ Operating Environment : Windows 10
+Once downloaded, please check the Release Note included in the package.
+
+
+
Step 4: Extract RZ/V AI SDK package
+This step explains how to extract the RZ/V AI SDK zip file.
+
+
On your Linux PC, make the working directory.
+{% highlight shell %}
+mkdir -p ai_sdk_work
+{% endhighlight %}
+
+
Register the working directory path to an environment variable.
+{% highlight shell%}
+export WORK=/ai_sdk_work
+{% endhighlight %}
+
+
Move to the working directory.
+{% highlight shell%}
+cd ${WORK}
+{% endhighlight %}
+
+
Extract RZ/V AI SDK zip file under the working directory.
+{% highlight shell%}
+unzip /RTK0EF0*.zip -d ${WORK}
+{% endhighlight %}
+
+
Check the working directory to confirm the package contents.
+{% highlight shell%}
+ls ${WORK}/
+{% endhighlight %}
+
+
If the above command prints followings, the package is extracted correctly.
+{% highlight shell%}
+ai_sdk_setup board_setup documents references r11an0*.pdf
+{% endhighlight %}
+
+
+
+
+
+
+
Step 5: Setup RZ/V AI SDK
+This step explains how to setup the RZ/V AI SDK environment.
+
+ Note
+ Make sure that you have installed Docker on your Linux PC.
+
+
+
On your Linux PC, move to the working directory.
+{% highlight shell%}
+cd ${WORK}/ai_sdk_setup
+{% endhighlight %}
+
Create new directory to be mounted on Docker container.
+{% highlight shell%}
+mkdir ${WORK}/ai_sdk_setup/data
+{% endhighlight %}
+
+
Create docker container. Here, _ai_sdk_container is a name of docker container, which can be changed by user.
+
+
For RZ/V2L
+{% highlight shell%}
+docker run -it --name rzv2l_ai_sdk_container -v $(pwd)/data:/drp-ai_tvm/data rzv2l_ai_sdk_image
+{% endhighlight %}
+
+
For RZ/V2H
+{% highlight shell%}
+docker run -it --name rzv2h_ai_sdk_container -v $(pwd)/data:/drp-ai_tvm/data rzv2h_ai_sdk_image
+{% endhighlight %}
+
+
+ The local $(pwd)/data is mounted to /drp-ai_tvm/data on the Docker container by the above command option.
+ For example, you can use this directory to copy files created on the Docker container to your local environment.
+
+
+
In docker container, run the following command to copy libtvm_runtime.so, which is the necessary file for the board, to host machine.
+{% highlight shell%}
+cp /drp-ai_tvm/obj/build_runtime/${PRODUCT}/libtvm_runtime.so /drp-ai_tvm/data
+{% endhighlight %}
+
+
To exit docker, run following commands.
+{% highlight shell%}
+exit
+{% endhighlight %}
+
+
To start the docker container again, run the following command.
+{% highlight shell%}
+docker start -i
+{% endhighlight %}
+
+
+
+You have finished the RZ/V AI SDK environment setup.
+You are ready to build the AI applications!
+
+ Note
+ Following procedures are for users who would like to build the application from the source code.
+ If you would like to run the application as quickly as possible, you can skip this step and proceed to the next step (Step 7: Deploy AI Application) since pre-build application binary is provided.
+
+ This repository only contains AI Applications for RZ/V2L EVK.
+ It does not provide instructions for RZ/V AI SDK.
+ Please refer to the instruction provided in this page.
+
+ Check the README.md document provided in application directory and follow the instruction in the chapter called "Application: Build Stage" (or similar) to build the application.
+
+ Example:
+ In R01_object_detection application, follow the instruction here to generate the following application binary.
+
+
object_detection
+
+
+
+
+
+
+
+
+ After you generated the application binary, please proceed to Step 7
+
+
+
+
Option 2: For <Application 2>
+
+
Run (or start) docker container.
+
+ Example:
+ Run the following command to start the docker container created in Step 5.
+{% highlight shell%}
+docker start -i rzv2l_ai_sdk_container
+{% endhighlight %}
+
+
+
Change the environment variable to use the cross compiler.
+{% highlight shell%}
+source /opt/poky/3.1.21/environment-setup-aarch64-poky-linux
+{% endhighlight %}
+
+ Note
+ This command needs to be called everytime user opened the new terminal.
+
+
+
Move to the mounted point in docker container.
+
+{% highlight shell%}
+cd /drp-ai_tvm/data
+{% endhighlight %}
+
+
Download the application source code.
+ Here, we use RZV2L_AiLibrary repository 01_Head_count application as an example.
+
+{% highlight shell%}
+git clone https://github.com/Ignitarium-Renesas/RZV2L_AiLibrary
+{% endhighlight %}
+
+
+
+
+
Move to the application directory.
+{% highlight shell%}
+cd RZV2L_AiLibrary/01_Head_count/Head_count_cam
+{% endhighlight %}
+
+ Note
+ The file configuration depends on each application. Please check the file configuration in the repository carefully.
+
+
+
Build the application with make command.
+
+{% highlight shell%}
+make
+{% endhighlight %}
+
+
Check that following application is generated in the RZV2L_AiLibrary/01_Head_count/ Head_count_cam/exe.
+
+
head_count_cam_app
+
+
+
If you would like to build the other applications of (Option 1), please exit and restart the docker container.
+
+
+
+ After you generated the application binary, please proceed to Step 7
+
+You have experienced the AI Application development procedures.
+Next step is to change the application to create your own AI Application.
+You can use the applications listed in AI Applications to expand your ideas!
+
+ WARNING
+
+
+ This page is published for Renesas internal purpose only.
+ Do NOT distribute/share this page to external parties.
+ Since this page is still under the review process, the content may change in the official release.
+
+ Due to the necessary software unavailability (i.e., DRP-AI TVM, AI Applications),
+ you can only run following steps with this internal release.
+
+
+ Step 2: Obtain necessary environment
+
+
+ Step 4: Extract RZ/V AI SDK package
+
+
+ Step 7: Deploy AI Application.
+
+
+ 1. Setup RZ/V2H EVK
+
+
+ 3. Boot RZ/V2H EVK
+
+
+
+
+ A4. Shutdown RZ/V2H EVK
+
+
+
+
+
+
+
+
+
This page explains how to start-up the AI SDK on the RZ/V2H Evaluation Board Kit.
+
+
Supported version: RZ/V2H AI SDK v3.00
+
+
+ Terminology
+
+
+
+
+
Getting Started Flow
+
+
+
+ This page explains RZ/V2H EVK dependent instructions.
+ Common instructions are explained in Getting Started page.
+
+
+
+ The RZ/V2H EVK is the ideal board kit for RZ/V2H evaluation.
+
+ MIPI camera module is not included in EVK.
+
+ As an input device, AI Applications support USB camera with VGA (640x480) resolution.
+
+ To use MIPI camera, please refer to e-CAM22_CURZH camera provided by e-con Systems.
+
+ e-CAM22_CURZH camera supports FHD (1920x1080) resolution.
+
+
+
+
+
+
+
+
+ Following items are included in the RZ/V2H EVK.
+
+
+
+
+
Equipment
+
Details
+
+
+
RZ/V2H Evaluation Board
+
Evaluation board itself.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Step 7: Deploy AI Application
+ This section explains how to deploy the AI Application to the RZ/V2H EVK.
+
+
+
+
+ To boot the board, bootloader and other Linux necessary files are required.
+ Following bootloader is available on RZ/V2H AI SDK.
+
+
+ eSD Bootloader: The board boots up using the bootloader written on microSD card.
+
+
+ Other necessary files, i.e. Linux kernel and root filesystem, are stored on microSD card.
+ You can use Linux PC to format the microSD card and expand the kernel and the root filesystem using SD card reader.
+
+
+
+
1. Setup RZ/V2H EVK
+ microSD card needs to contain bootloaders, the Linux kernel and root filesystem to boot-up the board.
+ RZ/V2H AI SDK supports the WIC format for SD card image.
+ You can use Linux PC to write the SD card image into microSD card with SD card reader.
+
+ 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 with the latest bootloader, Linux kernel, Linux device tree file and root filesystem, skip this step and proceed to the next procedure (2. Deploy Application to the Board).
+
+
+ As explained in Necessary Software of Getting Started Step 2, make sure that bmap-tools is installed on Linux PC.
+ If you have not installed the bmap-tools, install it using following command on Host PC (Not in the docker container).
+{% highlight shell %}
+sudo apt install bmap-tools
+{% endhighlight %}
+
+
+
Write the Linux files to SD card
+
+ Run the below command to decompress ${WORK}/board_setup/eSD.zip.
+{% highlight shell %}
+cd ${WORK}/board_setup
+unzip eSD.zip
+{% endhighlight %}
+ Following files are necessary.
+ They are in the ${WORK}/board_setup/eSD directory.
+
+
+
+
File
+
Description
+
+
+
core-image-weston-rzv2h-evk-ver1.wic.bmap
+
SD card image
+
+
+
core-image-weston-rzv2h-evk-ver1.wic.gz
+
+
+ Follow the instruction below to prepare the microSD card.
+
+ Warning
+ Here, we use "/dev/sdb" as microSD card device name.
+
+
+
To use bmaptools, microSD card partitions must be unmounted.
+ Run the following command to check the automatically mounted microSD card partitions.
+{% highlight shell %}
+df -h
+{% endhighlight %}
+
+
+ Check the output and find the mount point, which is "/media/user/9016-4EF8" in the following example.
+{% highlight shell%}
+Filesystem Size Used Avail Use% Mounted on
+:
+snip
+:
+/dev/sdb1 15G 32K 15G 1% /media/user/9016-4EF8
+{% endhighlight %}
+
+ Warning
+ Here, we use "/dev/sdb" as microSD card device name.
+
+ Note
+ If there are more than one partitions on microSD card, unmount all partitions.
+
+
+
Run the following command to write SD card image.
+{% highlight shell %}
+cd ${WORK}/board_setup/eSD
+sudo bmaptool copy --bmap core-image-weston-rzv2h-evk-ver1.wic.bmap core-image-weston-rzv2h-evk-ver1.wic.gz /dev/sdb
+{% endhighlight %}
+
+ Warning
+ Change /dev/sdb to your microSD card device name.
+
+
+
+ Eject microSD card and insert it again to mount the partitions.
+
+
+ Run the following command to check two partitions are created on microSD card.
+{% highlight shell %}
+df -h
+{% endhighlight %}
+
+
+ If the command shows following log, two partitions are created on microSD card successfully.
+{% highlight shell %}
+Filesystem Size Used Avail Use% Mounted on
+:
+snip
+:
+/dev/sdb1 17M 3.0M 14M 18% /media/user/bootloaderf
+/dev/sdb2 3.8G 1.6G 2.0G 45% /media/user/root
+{% endhighlight %}
+
+ Warning
+ Here, we use "/dev/sdb" as microSD card device name.
+
+
+
+
+
Run the following commands to setup the partition 2, which is the root filesystem of the board.
+{% highlight shell %}
+sudo mkdir /mnt/sd -p
+sudo mount /dev/sdb2 /mnt/sd
+sudo cp $WORK/ai_sdk_setup/data/libtvm_runtime.so /mnt/sd/usr/lib64
+sync
+sudo umount /mnt/sd
+{% endhighlight %}
+
+ Warning
+ Change /dev/sdb to your microSD card device name.
+
+
+ Note
+ If you would like to eject the microSD card, please run following command and remove the microSD card from Linux PC.
+
+{% highlight shell %}
+sudo eject /dev/sdb
+{% endhighlight %}
+
+ Warning
+ Change /dev/sdb to your microSD card device name.
+
+ Run the following command to mount the partition 2, which contains the root filesystem.
+{% highlight shell %}
+sudo mount /dev/sdb2 /mnt/sd
+{% endhighlight %}
+
+ Warning
+ Change /dev/sdb to your microSD card device name.
+
+
+
+ Create the application directory on root filesystem.
+{% highlight shell %}
+sudo mkdir /mnt/sd/home/root/tvm
+{% endhighlight %}
+
+ Note
+ Directory name tvm can be determined by user.
+
+
+
+ Copy the necessary files in execution environment.
+ Check the README.md document provided in application directory and follow the instruction in the chapter called "Application: Deploy Stage" (or similar) to deploy the application.
+
+
+ Example:
+ In R01_object_detection application, follow the instruction in here to find files to be copied.
+
+
+ Use the following command to copy the files to root filesystem.
+
+ Run the following command to sync the data with memory.
+
+{% highlight shell %}
+sync
+{% endhighlight %}
+
+
+ Run the following command to unmount the partition 2.
+
+{% highlight shell %}
+sudo umount /mnt/sd
+{% endhighlight %}
+
+
+ Eject the microSD card by running the following command and remove the microSD card from Linux PC.
+{% highlight shell %}
+sudo eject /dev/sdb
+{% endhighlight %}
+
+ Warning
+ Change /dev/sdb to your microSD card device name.
+
+
+
+
+
3. Boot RZ/V2H EVK
+ This section explains how to boot the RZ/V2H EVK.
+
+ Follow the instruction below to boot the board.
+
+
+
+
+
+
+ Insert the microSD card to the Board.
+
+ Note
+ Use the microSD card slot SD1 on the Board as shown in the figure.
+
+
+
Change DSW1 and DSW2 setting as shown in the figure.
+
Connect the USB mouse and USB keyboard and USB camera via USB hub.
+
+ Note
+ There are USB 2.0 port and USB 3.0 port on RZ/V2H EVK.
+ Please connect your USB camera to appropriate port according to its requirement.
+ Here, USB camera is connected to USB 2.0 via USB hub.
+
+
+
Connect the HDMI monitor to the Board.
+
Connect the power cable to the Board.
+
Turn the SW3 to ON.
+
Turn the SW2 to ON to power on the Board
+
+
+
+
+
+
+
+
+
+
+
After the boot-up, following screen will be displayed on HDMI monitor.
+
+
+
+
+
+
+
+
+
+
Click the icon at the top-left corner to open the terminal.
+ Follow the instructions explained in the document (README.md) of applications on GitHub.
+
+
+ Example:
+ For R01_object_detection application, follow the instruction here to run the application.
+
+ If you have successfully run the application, you will see following window on HDMI screen.
+
\ No newline at end of file
diff --git a/docs/img/V2H_EVK_v1.jpg b/docs/img/V2H_EVK_v1.jpg
new file mode 100755
index 0000000..af298ab
Binary files /dev/null and b/docs/img/V2H_EVK_v1.jpg differ
diff --git a/docs/img/aisdk_sc_v2h.svg b/docs/img/aisdk_sc_v2h.svg
new file mode 100755
index 0000000..247fda1
--- /dev/null
+++ b/docs/img/aisdk_sc_v2h.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/docs/img/block_rzv.svg b/docs/img/block_rzv.svg
new file mode 100755
index 0000000..f077402
--- /dev/null
+++ b/docs/img/block_rzv.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/docs/img/board.svg b/docs/img/board.svg
new file mode 100755
index 0000000..6fe7475
--- /dev/null
+++ b/docs/img/board.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/docs/img/esd.svg b/docs/img/esd.svg
new file mode 100755
index 0000000..493ac3e
--- /dev/null
+++ b/docs/img/esd.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/docs/img/getting_started_flow_base.svg b/docs/img/getting_started_flow_base.svg
new file mode 100755
index 0000000..22d751c
--- /dev/null
+++ b/docs/img/getting_started_flow_base.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/docs/img/getting_started_flow_v2h.svg b/docs/img/getting_started_flow_v2h.svg
new file mode 100755
index 0000000..30e2cf9
--- /dev/null
+++ b/docs/img/getting_started_flow_v2h.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/docs/img/getting_started_flow_v2l.svg b/docs/img/getting_started_flow_v2l.svg
new file mode 100755
index 0000000..ca603ca
--- /dev/null
+++ b/docs/img/getting_started_flow_v2l.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/docs/img/objectdetection_v2h.png b/docs/img/objectdetection_v2h.png
new file mode 100755
index 0000000..0bd9807
Binary files /dev/null and b/docs/img/objectdetection_v2h.png differ
diff --git a/docs/img/rzv2h_evk_diagonal.jpg b/docs/img/rzv2h_evk_diagonal.jpg
new file mode 100755
index 0000000..9979c26
Binary files /dev/null and b/docs/img/rzv2h_evk_diagonal.jpg differ
diff --git a/docs/img/v2h_evk_boot.png b/docs/img/v2h_evk_boot.png
new file mode 100755
index 0000000..28a1323
Binary files /dev/null and b/docs/img/v2h_evk_boot.png differ
diff --git a/docs/img/v2h_evk_shutdown.png b/docs/img/v2h_evk_shutdown.png
new file mode 100755
index 0000000..a02d7ac
Binary files /dev/null and b/docs/img/v2h_evk_shutdown.png differ
diff --git a/docs/img/v2h_evk_wayland.png b/docs/img/v2h_evk_wayland.png
new file mode 100755
index 0000000..bc77433
Binary files /dev/null and b/docs/img/v2h_evk_wayland.png differ
diff --git a/docs/img/v2h_mem.png b/docs/img/v2h_mem.png
new file mode 100755
index 0000000..926ddbe
Binary files /dev/null and b/docs/img/v2h_mem.png differ
diff --git a/docs/img/v2l_mem.png b/docs/img/v2l_mem.png
new file mode 100755
index 0000000..08b5958
Binary files /dev/null and b/docs/img/v2l_mem.png differ
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+