Skip to content

Quick Start Guides

Notice

Please download RTK0EF0188Z76001ZJ_v15.3.0_prebuilt-images.zip package that includes the prebuilt images.

RTK0EF0188Z76001ZJ_v15.3.0_prebuilt-images.zip

To boot Android, it’s required to flash Android bootloader and flash Android images.

Device connection information:

PeripheralRZ/V2H EVK
HDMIHDMI (CN4)
USB cable for HDMI touch panelUSB 2.0 Type A Port (CN3)
USB cable for serial consoleUSB Micro-B Port (CN12) UART
USB cable for adbUSB Micro-B Port (CN2)
Ethernet cableEthernet port (CN6 and CN5)

Start up the device by turning on switch POWER (SW3) and switch RESET(SW2).

CAUTION: It's NOT recommended to hot plug HDMI. It may cause board breaking.

Note:

  • It's required to disable "Auto Select" feature on monitor to disable auto scanning input.

The standard configuration is shown in the following figure.

Figure. Top side view of the RZ/V2H expansion board
Figure. Top side view of the RZ/V2H EVK main board
NumberDescriptionBoard
1HDMI Port (CN4)Expansion
2AUX port (P1)
3HP port (P2)
4Mic port (P3)
5MIPI DSI (CN5)
6Ethernet port (CN5)Main
7Ethernet port (CN6)
8USB 2.0 Type-A (CN3)
9Micro USB 2.0 (CN2)
10USB 3.0 Type-A (CN4)
11SD card slot (SD1)
12SD card slot (SD2)
13UART USB debug serial (CN12)
14DSW1
15Power input (CN13)
16Power Switch (SW3)
17Reset Switch (SW2)
18-21MIPI-CSI (CN7-CN10)
22MIPI DSI (CN11)

Connect the hardware as shown below.

Flashing bootloader

It’s needed to update the firmware (*). Especially, it’s mandatory to use U-Boot which support “fastboot” command.

(*)bootloader binaries:

  • bl2_bp_rzv2h_evk_ver1_esd.bin
  • bl2_bp_rzv2h_evk_ver1_esd.srec
  • bl2_bp_rzv2h_evk_ver1_spi.bin
  • bl2_bp_rzv2h_evk_ver1_spi.srec
  • fip_rzv2h_evk_ver1_sdhi.bin
  • fip_rzv2h_evk_ver1_sdhi.srec
  • fip_rzv2h_evk_ver1_spi.bin
  • fip_rzv2h_evk_ver1_spi.srec.

Use provided *.mot (Flash Writer) firmware below for flashing SPI bootloader:

  • Flash_Writer_SCIF_RZV2H_DEV_INTERNAL_MEMORY_0203.mot

Use provided *.ttl (TeraTerm Language) macros below for flashing SPI bootloader:

  • V2H-EVK-1-IPL Macro-Flash Writer V0.60_921600bps_spi.ttl

Use provided script below for flashing eSD bootloader:

  • flash_eSD_rzv2h_evk_ver1.sh

Note:

  • The command in the box below will be executed on the Ubuntu Host PC.
  • In RZ/V2H EVK, SPI and eSD boot mode are supported.
  • After first flashing new bootloaders of this release, the SPI bootloaders will be updated by default when users flash Android images. Please refer Flashing images using fastboot for more detail.
# For RZ/V2H prebuilt images
$ unzip RTK0EF0188Z76001ZJ_v15.3.0_prebuilt-images.zip

# Confirm the content of `RTK0EF0188Z76001ZJ_v15.3.0_prebuilt-images`
$ tree -L 1 RTK0EF0188Z76001ZJ_v15.3.0_prebuilt-images

# Content of the `RTK0EF0188Z76001ZJ_v15.3.0_prebuilt-images`
RTK0EF0188Z76001ZJ_v15.3.0_prebuilt-images
   |-- notice-files
   |-- prebuilt-images
   |-- sbom
   |-- L-497(Rev1.1)_RZ-MPU-ソフトウェアライセンス契約書.pdf
   |-- L-498(Rev1.1)_RZ-MPU-Software-License-Agreement.pdf
   `-- README.txt

# Confirm the content of prebuilt-images
$ tree RTK0EF0188Z76001ZJ_v15.3.0_prebuilt-images/prebuilt-images

# Content of the `RTK0EF0188Z76001ZJ_v15.3.0_prebuilt-images/prebuilt-images`
   |-- adb
   |-- bl2_bp_rzv2h_evk_ver1_esd.bin
   |-- bl2_bp_rzv2h_evk_ver1_esd.srec
   |-- bl2_bp_rzv2h_evk_ver1_spi.bin
   |-- bl2_bp_rzv2h_evk_ver1_spi.srec
   |-- boot.img
   |-- codec_bin.img
   |-- dtb.img
   |-- dtbo.img
   |-- fastboot
   |-- fastboot.sh
   |-- fastboot_functions.sh
   |-- fip_rzv2h_evk_ver1_sdhi.bin
   |-- fip_rzv2h_evk_ver1_sdhi.srec
   |-- fip_rzv2h_evk_ver1_spi.bin
   |-- fip_rzv2h_evk_ver1_spi.srec
   |-- init_boot.img
   |-- mke2fs
   |-- super.img
   |-- vbmeta.img
   |-- vendor_boot.img
   |-- flash_eSD_rzv2h_evk_ver1.sh
   |-- Flash_Writer_SCIF_RZV2H_DEV_INTERNAL_MEMORY_0203.mot
   `-- V2H-EVK-1-IPL Macro-Flash Writer V0.60_921600bps_spi.ttl

Please follow below steps to flash IPL (these steps are executed on Windows PC and use TeraTerm tool for flashing) on RZ/V2H boards.

Method 1: Flash bootloaders by using SCIF Download Mode

  1. Set DSW1 to SCIF Download Mode:

    Switch NamePin1Pin2Pin3Pin4
    DSW1ONOFFONOFF
    Switch NamePin5Pin6Pin7Pin8
    DSW1ONOFFOFFOFF

  2. Connect CN12 to Windows PC (via micro-USB cable), plug power adapter (At least 100W) into Power Input (CN13). Run TeraTerm on Windows PC, choose correct COM port and change its Baud rate to 115200 (“Setup > Serial port…”).

  3. On TeraTerm, choose “File > Disconnect” (if any), then “File > New connection…”. Turn switch POWER on (SW3), turn switch RESET on (SW2) to start up board and you will receive messages below:

    SCI Download mode (Normal SCI boot)
-- Load Program to SRAM -------------

  4. Copy below files to the same folder on firmware Windows machine

    • All *.mot files
    • All *.ttl files
    • All “*.srec” files

    Note: Make sure to copy them to the same directory.

  5. On TeraTerm, go to “Control > Macro”, choose corrected ttl file:
    “V2H-EVK-1-IPL Macro-Flash Writer V0.60_921600bps_spi.ttl”
    TeraTerm will automatically load firmware, then detect all “*.srec” files and load them to appropriate addresses.

    You will receive messages below after flashing bootloaders finished:

    Please change to 115.2Kbps baud rate setting of the terminal.
Changing to 115.2Kbps baud rate--------------DONE--------------

  6. Turn off switch RESET (SW2), turn off switch POWER (SW3) and plug out Power input (CN13).

  7. Set DSW1 to normal SPI boot mode:

    Switch NamePin1Pin2Pin3Pin4
    DSW1ONOFFONOFF
    Switch NamePin5Pin6Pin7Pin8
    DSW1OFFOFFOFFOFF

  8. Insert SD card (at least 16 GB) into SD1 slot.

    Note: If no SD card is inserted, you will see error messages in the yellow box below:

    Card did not respond to voltage select! : -110
invalid mmc device
Failed to read Android bootloader record

  9. Plug in Power input (CN13) again. Turn on switch POWER (SW3) and switch RESET (SW2) again! On Teraterm choose “File > Disconnect”, “File > New connection…”. After this step, if you see the similar messages as yellow box below, it means that bootloader is loaded successfully.

    Expected SPI boot mode logs:

    NOTICE: BL2: v2.7(release):v2.5/rzg2l-1.00-2305-gc3ed9fc4c
NOTICE: BL2: Built : 20:52:34, Apr 21 2026
NOTICE: BL2: Booting BL31
NOTICE: BL31: v2.7(release):v2.5/rzg2l-1.00-2305-gc3ed9fc4c
NOTICE: BL31: Built : 20:52:36, Apr 21 2026

U-Boot 2021.10-gcc1de54513 (Apr 21 2026 - 20:48:06 +0700)

CPU: Renesas Electronics R8A77970 rev 8.8
Model: Renesas EVK Version 1 based on r9a09g057h4
DRAM: 15.9 GiB
WDT: watchdog@0000000014400000
WDT: Started with servicing (60s timeout)
MMC: mmc@15c00000: 0, mmc@15c10000: 1
Loading Environment from SPIFlash... SF: Detected mt25qu512a with page size 256
Bytes, erase size 64 KiB, total 64 MiB
OK
Saving Environment to SPIFlash... Erasing SPI flash...Writing to SPI flash...done
OK
In: serial@11c01400
Out: serial@11c01400
Err: serial@11c01400
U-boot WDT started!
Net:
Error: ethernet@15c40000 address not set.

Error: ethernet@15c30000 address not set.

Error: ethernet@15c30000 address not set.

Error: ethernet@15c40000 address not set.
No ethernet found.

Setting bootmode 'android'
Hit any key to stop autoboot: 0

Method 2: Flash bootloaders to eSD (eSD boot mode, see Support eSD boot)

  1. Plug SDCard into the host PC.

  2. Copy the files below to the same folder on host PC:

    • bl2_bp_rzv2h_evk_ver1_esd.bin
    • fip_rzv2h_evk_ver1_sdhi.bin
    • flash_eSD_rzv2h_evk_ver1.sh
    # On Ubuntu Host PC, execute command:

$ chmod a+x flash_eSD_rzv2h_evk_ver1.sh
$ ./flash_eSD_rzv2h_evk_ver1.sh <block_dev_path_of_SDCard>

Example: ./flash_eSD_rzv2h_evk_ver1.sh /dev/sdf (sdf is block device. It should not have partition number)
Note: This script will format the SD card, so back up your data before proceeding

  3. Set DSW1 to eSD boot mode:

    Switch NamePin1Pin2Pin3Pin4
    DSW1ONOFFONON
    Switch NamePin5Pin6Pin7Pin8
    DSW1OFFOFFOFFOFF

  4. Plug SDCard to SD1 on RZ/V2H EVK board, Turn on switch POWER (SW3) and switch RESET (SW2) to boot the board.

    Note: Note: If the SD Card is not flashed eSD bootloaders yet or failed to flash eSD bootloaders, you will see error messages in the yellow box below:

    SCI Download mode (Normal SCI boot)
-- Load Program to SRAM -------------

    Expected eSD boot mode logs:

    NOTICE: BL2: v2.7(release):v2.5/rzg2l-1.00-2305-gc3ed9fc4c
NOTICE: BL2: Built : 13:14:36, Apr 23 2026
NOTICE: SD boot from partition 0
NOTICE: Load dst=0x8136680 src=(p:0)0x60000(768) len=0x10(1)
NOTICE: SD boot from partition 0
NOTICE: Load dst=0x8136850 src=(p:0)0x60010(768) len=0x28(1)
NOTICE: SD boot from partition 0
NOTICE: Load dst=0x44000000 src=(p:0)0x60090(768) len=0x6071(49)
NOTICE: SD boot from partition 0
NOTICE: Load dst=0x8136680 src=(p:0)0x60000(768) len=0x10(1)
NOTICE: SD boot from partition 0
NOTICE: Load dst=0x8136850 src=(p:0)0x60010(768) len=0x28(1)
NOTICE: Load dst=0x8136850 src=(p:0)0x60038(768) len=0x28(1)
NOTICE: SD boot from partition 0
NOTICE: Load dst=0x50000000 src=(p:0)0x66110(816) len=0xd2648(1684)
NOTICE: BL2: Booting BL31
NOTICE: BL31: v2.7(release):v2.5/rzg2l-1.00-2305-gc3ed9fc4c
NOTICE: BL31: Built : 13:14:38, Apr 23 2026

U-Boot 2021.10-gcc1de54513 (Apr 23 2026 - 13:14:28 +0700)

CPU: Renesas Electronics CPU rev 1.0
Model: Renesas EVK Version 1 based on r9a09g057h4
DRAM: 15.9 GiB
WDT: watchdog@0000000014400000
WDT: Started with servicing (60s timeout)
MMC: mmc@15c00000: 0, mmc@15c10000: 1
Loading Environment from MMC... OK
Saving Environment to MMC... Writing to MMC(0)... OK
In: serial@11c01400
Out: serial@11c01400
Err: serial@11c01400
U-boot WDT started!
Net:
Error: ethernet@15c40000 address not set.
eth0: ethernet@15c30000
Error: ethernet@15c40000 address not set.

Setting bootmode 'android'
Hit any key to stop autoboot: 0

Note:

  • This step is only for loading bootloaders. Users still need to flash Android images refer to Flashing images using fastboot.
  • After first flashing eSD bootloaders of this release, users do NOT need to use flash_eSD_rzv2h_evk_ver1.sh to update bootloaders. Users can use fastboot to update eSD bootloaders.

$ sudo ./fastboot.sh --serial=<serialno> --noresetenv --blonly --update_bootloaderesd
<serialno> is board serial number which is set in Flashing images using fastboot.

Boot Sequence of bootloader

Note: If you face troubles with booting Android, we recommend flashing bootloaders files by following Flashing bootloader

Boot sequence

Figure. Boot sequence (RZ/V2H)

Flashing images using fastboot

This step should be done after successful IPL and U-Boot flashing. (See Flashing bootloader)

Note: When users load bootloader at the first time, bootloaders will display warning messages as below:

    cannot find partition: 'misc'
    Failed to read Android bootloader record.

This warning is expected. The "misc" partition doesn't exist yet because no Android images have been flashed. It will be created automatically during the Android image flashing steps.

1) There are 2 ways to flash images:

  • In case using “fastboot usb” please connect Micro USB 2.0 (CN2) to Ubuntu Host PC with an USB cable for fastboot.
  • In case using “fastboot udp” please connect Ethernet port (CN5) via Ethernet cable to a router and an Ubuntu Host PC connected to the same router.

2) Power on device and interrupt autoboot.
3) Execute below commands on target board.

Set environment values on U-boot

=> env default -a
=> setenv bootargs ‘video=HDMI-A-1:e $bootargs’
	video=HDMI-A-1:e : Skip hotplug, keep connector always on

For fastboot USB

# For fastboot USB
=> setenv serialno <serial number>
	Example:
	setenv serialno 00001234
=> saveenv
=> fastboot usb
For fastboot UDP (see Fastboot UDP) 
=> setenv ethaddr <board MAC addr>
=> setenv ipaddr <board IP addr>
=> setenv bootargs ‘ip=<client-ip>::<gateway-ip>:<netmask>::<device>:off $bootargs’
	<client-ip>: Board IP address
	<gateway-ip>: Host PC IP address
	<netmask>: Network mask
	<device>: Network interface
	Example:
	setenv ethaddr aa:bb:cc:dd:ee:ff
	setenv ipaddr 192.168.1.2
	setenv bootargs 'ip=192.168.1.2::192.168.1.1:255.255.255.0::eth0:off $bootargs'
=> saveenv
=> fastboot udp

Note:

  • fastboot device is only detected if user runs fastboot usb command on u-boot console.
  • If the “ip” is set in bootargs and the Ethernet cable is not plugged in, the system will wait for 100 seconds during boot

4) Execute below commands on Ubuntu Host PC.

Format SD card partition and write image file to target. Please use “fastboot” command that you built in step Building Android, IPL, U-Boot, and Kernel sources. (Of course, fastboot tool included in latest Android SDK is also worked.)

Method 1: Fastboot USB

$ cd <your working dir>/RTK0EF0188Z76001ZJ_v15.3.0_prebuilt-images/prebuilt-images
$ chmod a+x *

$ sudo ./fastboot -s <serialno> oem format
Expected output: "Finished. Total time: 1.857s"

$ sudo ./fastboot -s <serialno> reboot bootloader
Expected output: "Finished. Total time: 0.266s"

# In case of SPI boot, fastboot.sh updates Android images and SPI bootloaders
$ sudo ./fastboot.sh --serial=<serialno> --noresetenv

# In case of eSD boot, fastboot.sh updates Android images and eSD bootloaders
$ sudo ./fastboot.sh --serial=<serialno> --noresetenv --update_bootloaderesd

# If users do not want to update bootloaders
$ sudo ./fastboot.sh --serial=<serialno> --noresetenv --nobl

Expected output: "SUCCESS. Script finished successfully"

Additional option:
	--blonly: Update bootloaders only

<serialno> is board serial number which is set in the board console.

Method 2: Fastboot UDP (See Fastboot UDP)

For SPI Flash only (not supported eSD boot mode)

$ cd <your working dir>/RTK0EF0188Z76001ZJ_v15.3.0_prebuilt-images/prebuilt-images
$ chmod a+x *

$ sudo ./fastboot -s udp:<ipaddress> oem format
Expected output: "Finished. Total time: 1.652s"

$ sudo ./fastboot -s udp:<ipaddress> reboot bootloader
Expected output: "Finished. Total time: 0.013s"

$ sudo ./fastboot.sh --serial=udp:<ipaddress> --noresetenv --nobl
Expected output: "SUCCESS. Script finished successfully"

<ipaddress> is board IP address which is set in the board console.
# Fastboot UDP only work on Ethernet port (CN5).

Note:

  • Running oem format may be failed at the first time. The information might be like the log below. 
    (bootloader)  eMMC: Man 000003 Snr 290cbd00 SE16G 0.1 15193MiB
(bootloader)  Created new GPT partition table:
(bootloader)      /misc (ERROR unable to get info)
(bootloader)      /pst (ERROR unable to get info)
(bootloader)      /vbmeta (ERROR unable to get info)
(bootloader)      /vbmeta (ERROR unable to get info)
(bootloader)      /dtbo (ERROR unable to get info)
(bootloader)      /dtbo (ERROR unable to get info)
(bootloader)      /boot (ERROR unable to get info)
(bootloader)      /boot (ERROR unable to get info)
(bootloader)      /init_boot (ERROR unable to get info)
(bootloader)      /init_boot (ERROR unable to get info)
(bootloader)      /codec_bin_a (ERROR unable to get info)
(bootloader)      /codec_bin_b (ERROR unable to get info)
(bootloader)      /vendor_boot (ERROR unable to get info)
(bootloader)      /vendor_boot (ERROR unable to get info)
(bootloader)      /metadata (ERROR unable to get info)
(bootloader)      /super (ERROR unable to get info)
(bootloader)      /userdata (ERROR unable to get info)
OKAY [  1.956s]
Finished. Total time: 1.957s

Please try to turn off your board, plug out power. Then plug in power, turn on the board again and try to re-run oem format again

  • HDMI is required to boot successfully.
  • It is required to plug external power if user uses external devices like portable monitor, USB hub, etc.

Once the boot process completes successfully, the GUI should appear on the HDMI monitor.

Boot complete

The console should display logs like the following:

[ 140.089754] init: Command 'setprop persist.device_config.attempted_boot_count 0' action=sys.boot_completed=1 (/system/etc/init/flags_health_check.rc:8) took 60ms and succeeded

Booting RZ/V2H EVK

After flashing Bootloaders and images according to the Quick Start Guides, please follow the steps below to power on the RZ/V2H EVK.

Note: This step expects the user to have completed the "flashing Bootloaders and images" of the Quick Start Guides

  1. Insert the microSD card to the Board.
  2. Change DSW1 setting to SPI boot mode as shown above.
  3. Connect Micro USB 2.0 (CN2) to Ubuntu Host PC with USB cable.
  4. Connect the HDMI touch panel to the Board.

    Note: HDMI monitor can also be used.

  5. Connect the USB cable for HDMI touch panel to the USB 2.0 Type A (CN3).

    Note: USB mouse can also be used.

  6. Connect the USB camera via USB hub.

    Note: Used when running YOLOv8 Application.

  7. Connect the Windows PC and the Board by the Ethernet cable.

    Note: Used when running YOLOv8 Streaming Application.

  8. Connect the power cable to the board and turn SW3 ON.

  9. Turn the SW2 to ON to power on the Board. Verify that the following is displayed on the HDMI screen.

Application Installation and Run

This section explains how to run the Application.

Install APK

This section explains how to install APK file to Android UI.

Requirements:

  • To install the APK, you need to flash the prebuilt images and booting Android Environment successfully, referring to the Flashing bootloader and Flashing images using fastboot.
  • Connect the CN2 (RZ/V2H EVK) and Ubuntu Host PC using a MicroUSB cable.
  • Connect the HDMI touch panel with USB. If you do not have one, you can substitute it with a HDMI display and a USB mouse connected to RZ/V2H EVK.

Step 1: Check the setting to install APK

  1. Boot the RZ/V2H EVK according to the Booting RZ/V2H EVK. Open a terminal for adb (Android Debug Bridge) on your Ubuntu Host PC.

  2. On Ubuntu Host PC, check the connection between RZ/V2H EVK and Ubuntu Host PC. The ID 18d1 should be displayed. If the ID 18d1 is not displayed, check the physical connection:

    $ lsusb

    If the following output is displayed, you have successfully connected to the RZ/V2H EVK.

    Bus 003 Device 008: ID 18d1:4e11 Google Inc. Nexus One

  3. Check whether an Android-specific udev rules file such as 51-android.rules or 99-android.rules exists in /etc/udev/rules.d/.

    $ ls /etc/udev/rules.d/

  4. If the rules file does not exist, create a rules file that grants device access permissions to the plugdev group.
    In this example, create 51-android.rules using a text editor and enter the following content, then save the file:

    SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666", GROUP="plugdev"
    SUBSYSTEM=="usb": Targets only USB devices
    ATTR{idVendor}==“18d1": Set the vendor ID (Geogle: 18d1) of the device
    MODE="0666": Allows access for all user
    GROUP="plugdev": Grants access if the user belongs to the plugdev group

  5. If the rules file such as 51-android.rules or 99-android.rules already exists but does not contain the same entries, append the same entries to the file.

  6. Reload the rules to apply the changes

    $ sudo udevadm control --reload-rules
$ sudo udevadm trigger

  7. Add the current user to the plugdev group.

    $ sudo usermod -aG plugdev $USER

  8. Log out and log back in, then restart the RZ/V2H EVK. (Shutdown RZ/V2H EVK/Booting RZ/V2H EVK)

Step 2: Install APK file using adb

  1. Move to the prebuilt binary directory. 
    $ cd <your working dir>/RTK0EF0188Z76001ZJ_v15.3.0_prebuilt-images/prebuilt-images
$ chmod a+x *

  2. Verify that the connection to the RZ/V2H EVK and Ubuntu Host PC is established using the following command:

    $ ./adb devices -l

    If the following output is displayed, you have successfully connected to the RZ/V2H EVK.

    List of devices attached
    XXXXXXXX device usb:xxx product:rzv2h_evk_ver1 model:RZV2H_EVK_VER1_r9a09g057h4_evk device:rzv2h_evk_ver1 transport_id:x

  3. If you already have installed the ResNet application, uninstall the application.

    $ ./adb uninstall com.tutorial

  4. Install the built application on V2H EVK board using the following command. The message "Performing Streamed Install" will be displayed. Wait until "Success" message is displayed.

    If you are using the APK file provided by Renesas, execute the following command.

    $ wget https://github.com/renesas-rz/rzv_aosp_ai_apps/releases/download/v1.00/resnet_app-release.apk
$ ./adb install resnet_app-release.apk

Note: If the APK file installation fails, please use the adb tool from platform-tools following the below steps and perform the installation again.

  • Download and extract the platform-tools package from Google

    $ cd <your working dir>
$ wget https://dl.google.com/android/repository/platform-tools-latest-linux.zip
$ unzip platform-tools-latest-linux.zip
$ export PATH=<path to your working dir>/platform-tools:$PATH

  • Confirm the new adb tool before using

    $ which adb
    The output should be: 
    <path to your working dir>/platform-tools/adb

  • Please update your adb command when switching to use adb from platform-tools

    Old command (use adb tool from prebuilt-images)

    $ ./adb install <path to your working dir>/RTK0EF0188Z76001ZJ_v15.3.0_prebuilt-images/prebuilt-images/resnet_app-release.apk

    New command (use adb tool from platform-tools)

    $ adb install <path to your working dir>/RTK0EF0188Z76001ZJ_v15.3.0_prebuilt-images/prebuilt-images/resnet_app-release.apk

Note: These commands are executed on Ubuntu Host PC

Run the Application

This section explains how to run the Application.

Requirements:

  • To run the application, you have completed the installation of the APK file by following the instructions in Install APK file using adb.
  • Connect the HDMI touch panel with USB. If you do not have one, you can substitute it with a HDMI display and a USB mouse connected to RZ/V2H EVK.

Step 1: Boot Android Environment

  1. Confirm if Android environment is booted successfully, the following screen is displayed:
    After Booting RZ/V2H EVK, the following screen will appear after a few minutes.

  2. Swipe up to open the home screen, When the home screen appears, tap the square icon at the bottom-right corner of the screen, and then tap the icon at the bottom-center of the next screen.

Step 2: Run the Application

  1. Click to TutorialApp icon to start the application

  2. The application screen will appear. Click Run to start AI inference

  3. To change the AI model, tap the triangle icon at the top-right of the screen, select a model from the drop-down menu, and then tap RUN.

  4. To change the DRP-AI frequency, enter the frequency index n (1 <= n <= 127) in the Optional field, and then tap the RUN. The relationship between the DRP-AI frequency and the frequency index n is as follows: Without an index, or with index 1 or 2: 1 GHz. For index n (3 <= n <= 127): 1260/(n-1) MHz.

  5. Example of the Inference result is displayed the same as:

    Selected model: resnet18_torch

[TIME] Pre Processing Time: 3.83 msec.
[TIME] AI Processing Time: 17.69 msec.
Output data type : FP16.
Result -----------------------
Top 1 [ 66.0%] : [beagle]
Top 2 [ 13.0%] : [English foxhound]
Top 3 [ 11.4%] : [Walker hound, Walker foxhound]
Top 4 [  5.9%] : [basset, basset hound
Top 5 [  0.7%] : [bloodhound, sleuthhound]

Step 3: Close the Application and shutdown the RZ/V2H EVK

  1. To exit the application, tap the square icon at the bottom-right of the screen. When the screen shown below is displayed, swipe the application to the right. The CLEAR ALL button will appear on the left side of the screen. Tap this button. The application will close and return to the home screen.

    If you are using a touch panel, you can also close the application by flicking it up.

  2. To shutdown the RZ/V2H EVK, swipe down in the home screen. When the screen shown below is displayed, tap the power icon at the bottom center of the screen, then tap Power off. Once the "shutting down" message disappears, turn off SW2 and then SW3 to power off the RZ/V2H EVK.

Application: Configuration

AI Processing time

AI modelAI Processing time
resnet50_v1_onnxApproximately 7 ms
resnet18_torchApproximately 6 ms
resnet50_tfliteApproximately 50 ms
resnet50_v1_onnx_cpuApproximately 693 ms

Note: The AI ​​Processing time mentioned above does not include the AI Processing time of first time.

Processing

ProcessingDetails
Pre Processing TimeProcessed by DRP-AI.
AI Processing TimeProcessed by DRP-AI and CPU.

License

Apache License 2.0
For licensing information regarding AI models, please refer to the source from which each model was obtained.

This concludes the explanation of the ResNet Console Application for RZ/V2H Software Package for AOSP 15.

Shutdown device

Shutdown the device as shown:

Method 1: Shutdown via board's console

On board's console:

1) $ reboot -p

2) Switch the RESET switch (SW2) and POWER switch (SW3) off after the display shows no signal

Method 2: Shutdown via adb

On Ubuntu Host PC

1) $ adb -s shell svc power shutdown

2) Switch the RESET switch (SW2) and POWER switch (SW3) off after the display shows no signal

Method 3: Shutdown via Android GUI

On Android GUI

  1. Swipe down in the home screen. When the screen shown below is displayed, tap the power icon at the bottom center of the screen, then tap Power off.

  2. Once the "shutting down" message disappears, turn SW2 to OFF.

  3. Turn SW3 to OFF.