# HummingBoard IIOT & RZ/V2N SOM Quick Start Guide
## Introduction
The following quick start guide provides background information about the HummingBoard IIOT.
The guide will give a technical overview about the product and by the end of it you should be able to boot an operating system and begin testing your application.
## Revision and Notes
| **Date** | **Owner** | **Revision** | **Notes** |
| ----------- | --------- | ------------ | --------------- |
| 20 Nov 2025 | Yazan | 1.0 | Initial release |
## Hardware Setup
#### Product specifications
| **Model** | HummingBoard RZ/V2N IIOT SBC |
| ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Processor** | Renesas RZ/V2N SOM 4 x Arm Cortex-A55
1 x Cortex-M33
Up to 1.8 GHz
|
| **Memory & Storage** | Up to 8GB LPDDR4
Up to 128GB eMMC
MicroSD
|
| **AI Accelerator** | DRP-AI3 (15 Sparse TOPS / 4 Dense TOPS) |
| **Display** | MIPI-DSI |
| **I/Os** | 2 x RS232, 2 x RS485, or RS232 + RS485
2 x CAN-FD
2 x USB2.0
1 x USB3.2
1 x MIPI-CSI 4 lanes
|
| **Networking** | 2 x Ethernet RJ45 10/100/1000
1 x 802.11 a/b/g/n/ac WiFi and Bluetooth (2.4/5 GHz)
|
| **Misc.** | GPIO
RTC
EEPROM
|
| **Power** | 7V – 32V
PoE sink support 802.3at
Reverse polarity support
|
| **Expansion card I/Os** | M.2 B-Key LTE modem
(eSIM, NanoSim)
|
| **Temperature** | Industrial: -40°C to 85°C |
| **Dimensions** | PCBA: 88 x 135 mm
Enclosure (Optional): 150 x 145 x 40mm
|
| **Enclosure** | Extruded aluminum |
| | [Buy Now](https://www.solid-run.com/contact-us/) |
{% hint style="info" %}
Supported with RZ/V2N SOM. For more detailed information about our SOM RZ/V2N series please visit this user manual : RZ/V2N SOM Hardware User Manual .
{% endhint %}
#### Block Diagram
The following figure describes the RZ/V2N Block Diagram.
#### Visual features overview
Please see below the features overview of the connector side of the HummingBoard IIOT & RZ/V2N SOM.
Print side connector overview of the HummingBoard IIOT & RZ/V2N SOM.
**Power Input Polarity \[J1]:**
* **Connector Type**: Green two-terminal connector \[J1].
* **Voltage Range**: 7V to 32V.
* **Polarity**:
* **+ (Positive)**: Left terminal (as marked in the image).
* **- (Negative)**: Right terminal (as marked in the image).
{% hint style="info" %}
Plug for connector **J1** : 2 Position Terminal Block Plug, Female Sockets 0.138" (3.50mm).
{% endhint %}
**J5004** {2x RS485, 2x CAN-FD, 2x RS232, DIG\_IN, DIG\_OUT}
{% hint style="info" %}
Plug for connector **J5004** : 20 Position Terminal Block Plug, Female Sockets 0.138" (3.50mm) like [this](https://www.digikey.com/en/products/detail/phoenix-contact/1738885/3606115).
{% endhint %}
## Software Setup
#### Cable setup and prerequisites
Here is what you will need to power up and use the board:
* Linux or Windows PC
* HummingBoard IIOT with SOM
* 12V Power adapter (HummingBoard IIOT has wide range input of 7V-28V), alternatively you can use a PoE injector to power on the device.
* Type-C to USB for console, the HummingBoard IIOT has an onboard FTDI chip.
* IP router or IP switch
## Boot Select
Before powering up the board for the first time it is recommended to select the boot media using onboard DIP switch **S5**:
| **Switch** | 1
(MD0)
| 2
(MD1)
| 3
N/A
| 4
N/A
| 5
(VDD\_3.3V)
| 6
(VDD\_1.8V)
|
| --------------------- | ---------------------------------- | ---------------------------------- | -------------------------------- | -------------------------------- | ---------------------------------------- | ---------------------------------------- |
| **SPI** | OFF | **ON** | X | X | OFF | **ON** |
| **eMMC** | **ON** | OFF | X | X | OFF | **ON** |
| **Serial Dowanloder** | **ON** | **ON** | X | X | OFF | **ON** |
{% hint style="info" %}
**MDx = BOOT\_MODEx.**\
**VDD\_BOOT** can be either **1.8V** or **3.3V** (selectable via **S5\[5]** or **S5\[6]**).
* **BOOT\_MODE2 = ‘1’** → fixed to **1.8V** at the SOM level
* **BOOT\_MODE3** and **BOOT\_MODE4** → fixed to **GND** at the SOM level **Note:** MD1 and MD0 are swapped between **PCB version 1.1** and **PCB version 1.0**.
{% endhint %}
{% hint style="warning" %}
**Note:** To boot from eMMC on the HummingBoard-IIoT, we need to account for the internal pull-up on **MD\_BOOT1**. To ensure **MD\_BOOT1** is pulled low to a valid logic ‘0’, the following resistor changes are required on the **HB-IIoT carrier board**:
* Replace **R42** from **100 kΩ** to **1 kΩ**
* Replace **R36** from **4.7 kΩ** to approximately **47 Ω**
These resistors are located close to the **S5 DIP switch**, as shown in the figure below.
{% endhint %}
## Booting from SPI and loading Yocto from uSD card
**Set the Boot Switch to SPI Boot Mode**
Here is the correct DIP switch position for SPI boot:
{% hint style="info" %}
Note: The black rectangle represents the switch position. The unit comes with a pre-programmed bootloader on the SPI NOR flash.
{% endhint %}
Once you set the switches, you can apply the following for booting from an SPI card.
1. **Downloading the Yocto image**
Download the Debian image by running the following command on your Linux/Windows PC:
```
wget https://solid-run-images.sos-de-fra-1.exo.io/renesas/rzv2n/core-image-weston-rzv2n-evk.rootfs-20251224162903.wic.gz
```
* For more Debian releases, please visit .
2. **Writing the image to the SD card**
Use the following commands for writing the image to an SD card:
```
gunzip -dc core-image-weston-rzv2n-evk.rootfs-20251224162903.wic.gz | dd of=/dev/sdX bs=4k conv=fdatasync
```
* For more information, please visit [Flashing an SD Card](/other-articles/flashing-an-sd-card.md) .
{% hint style="info" %}
Note: Plug a micro SD into your Linux PC, the following assumes that the micro SD is added as /dev/sdX and all it’s partitions are unmounted.
{% endhint %}
3. **SD card insertion**
Please Insert the SD card into your device.
4. **Power connection**
Connect your power adaptor to the DC jack, and then connect the adaptor to mains supply.
5. **Serial Connection**
Please insert the micro USB into your device, then you can refer to [Serial Connection](/other-articles/serial-connection.md) for installing necessary serial connection software in Linux/Windows.
Once you installed the necessary serial connection software, you should be able to see the following:
* In order to be able to log in, please insert “**root**” as a username and password.
## Streaming USB Webcam Video from RZ/V2N Yocto to a PC
This section describes how to stream live video from a USB webcam connected to a **SolidRun RZ/V2N** board running **Yocto Linux**, and display the video on a **remote PC** (Linux or Windows) over the network using **GStreamer**.\
The streaming pipeline uses **MJPEG over RTP**, which is supported by most USB webcams and does not require hardware H.264 encoding on the device.
GStreamer provides command-line tools for capturing, encoding, sending, receiving, and displaying video streams.
**1. Yocto Image Requirements**
* v4l2 support
* GStreamer core + good/bad/ugly plugins
* v4l-utils (recommended)
Suggested additions to `local.conf` if missing:
```
IMAGE_INSTALL:append = " gstreamer1.0 gstreamer1.0-plugins-good gstreamer1.0-plugins-bad gstreamer1.0-plugins-ugly v4l-utils "
```
**2. Installing GStreamer on the PC**
For Ubuntu/Debian distros:
```
sudo apt install gstreamer1.0-plugins-ugly gstreamer1.0-plugins-bad gstreamer1.0-libav
```
For Fedora/RHEL distros:
```
sudo dnf install gstreamer1 gstreamer1-plugins-base gstreamer1-plugins-good gstreamer1-plugins-bad-free gstreamer1-plugins-bad-free-gtk
```
For Windows:
* **Download the Installer**: Go to the [GStreamer official website](https://gstreamer.freedesktop.org/download/) and download the appropriate installer for your Windows version.
* **Run the Installer**: Execute the downloaded file. During installation, **select "Complete Installation"** to install all basic plugins.
* **Set Environment Variables**: To use GStreamer from the command line, add GStreamer to your system's PATH as described [here](https://gstreamer.freedesktop.org/documentation/installing/on-windows.html?gi-language=c).
{% hint style="info" %}
For Windows, you might need to configure the Firewall to allow the stream. Make sure that `10.0.0.2` is a private network.
{% endhint %}
**3. Verifying Webcam Detection on RZ/V2N (Yocto)**
Before streaming, verify that the USB webcam is detected.
**Check USB enumeration**
```
lsusb
```
Example:
```
Bus 001 Device 004: ID 046d:085c Logitech, Inc. C922 Pro Stream Webcam
```
**Check video devices**
```
ls /dev/video*
```
Expected:
```
/dev/video0
```
{% hint style="info" %}
**If no /dev/video0 found**
Enable UVC driver:
```
modprobe uvcvideo
```
{% endhint %}
**Check supported formats**
```
v4l2-ctl --list-formats -d /dev/video0
```
Typical output:
```
YUYV 4:2:2
MJPG
```
***Note**:* The Logitech C922 supports MJPEG, so MJPEG-over-RTP streaming is used.
**4. Network Streaming Overview**
1. The RZ/V2N board captures MJPEG frames from the USB webcam (`/dev/video0`).
2. Frames are packetized into **RTP** and sent via **UDP** to the PC on port **5000**.
3. The PC receives the RTP stream, extracts the MJPEG frames, decodes them, and displays the video.
**5. GStreamer Commands**
**5.1 On the RZ/V2N (Sender – Yocto)**
Replace `` with the IP address of the PC receiving the video.\
Example: `192.168.33.17`
```
gst-launch-1.0 -v \
v4l2src device=/dev/video0 ! \
image/jpeg,width=1280,height=720,framerate=30/1 ! \
rtpjpegpay ! \
udpsink host= port=5000 sync=false async=false
```
**Pipeline explanation**
* **v4l2src** – captures video from the webcam
* **image/jpeg** – requests MJPEG format
* **rtpjpegpay** – packetizes JPEG frames into RTP
* **udpsink** – sends RTP stream to the PC
***
**5.2 On the PC (Receiver)**
**Linux (Ubuntu, Fedora, Debian, etc.)**
```
gst-launch-1.0 -v \
udpsrc port=5000 caps="application/x-rtp,encoding-name=JPEG,payload=26" ! \
rtpjpegdepay ! \
jpegdec ! \
videoconvert ! \
autovideosink sync=false
```
**Windows (PowerShell)**
```
gst-launch-1.0 -v `
udpsrc port=5000 caps="application/x-rtp,encoding-name=JPEG,payload=26" ! `
rtpjpegdepay ! `
jpegdec ! `
videoconvert ! `
autovideosink sync=false
```
**Pipeline explanation**
* **udpsrc** – receives RTP packets
* **rtpjpegdepay** – extracts MJPEG frames
* **jpegdec** – decodes JPEG video
* **autovideosink** – displays the video on the PC
## TLV EEPROM Support
RZ/V2N SoMs are being programmed with identifying information such as the product name, MAC Address and SKUs to allow for programmatic identification of hardware.
## Bootloader Firmware Flashing (BL2 + FIP)
The SD card image only contains the Linux kernel and root filesystem. The bootloader firmware — BL2 (Trusted Firmware-A first stage) and FIP (U-Boot + BL31) — must be programmed separately to either SPI NOR flash or the eMMC boot partition.
#### Flashing Methods
The [Firmware Flashing Guide](https://github.com/SolidRun/meta-solidrun-arm-rzg2lc/blob/scarthgap_rzv2n_dev/docs/rzv2n_flashing_guide.md) covers three methods for programming the bootloader:
| **Serial Flash Writer** | Initial programming or recovery — board boots via SCIF in Serial Downloader mode |
| ----------------------- | ------------------------------------------------------------------------------------- |
| **U-Boot CLI** | Field updates from a USB drive — no host PC connection required |
| **Linux** | In-system updates from a running Linux image via MTD (SPI NOR) or mmcblk0boot0 (eMMC) |
Each method supports both **SPI NOR flash** and **eMMC** boot storage. See the [full guide](https://github.com/SolidRun/meta-solidrun-arm-rzg2lc/blob/scarthgap_rzv2n_dev/docs/rzv2n_flashing_guide.md) for step-by-step commands, flash memory layout, and DIP switch (S5) boot mode settings.
#### Build Artifacts
After a Yocto build, the firmware files are in `tmp/deploy/images/rzv2n-sr-som/`:
| File | Description |
| ------------------------------------------------ | ----------------------------------- |
| `bl2_bp_mmc-rzv2n-sr-som.bin` | BL2 for eMMC boot |
| `fip-rzv2n-sr-som.bin` | FIP image (TF-A BL31 + U-Boot) |
| `Flash_Writer_SCIF_RZV2N_SR_SOM_8GB_LPDDR4X.mot` | Flash Writer for serial programming |
## List Of Supported OS
| **OS** | |
| -------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
|  | [GitHub - SolidRun/build\_rzg2lc at rzv2n-dev](https://github.com/SolidRun/build_rzg2lc/tree/rzv2n-dev) |
|  | [GitHub - SolidRun/meta-solidrun-arm-rzg2lc at scarthgap\_rzv2n\_dev](https://github.com/SolidRun/meta-solidrun-arm-rzg2lc/tree/scarthgap_rzv2n_dev) |
|  | [GitHub - SolidRun/build\_rzg2lc at rzv2n-dev](https://github.com/SolidRun/build_rzg2lc/tree/rzv2n-dev) |
## Build from source
* [GitHub - SolidRun](https://github.com/SolidRun/)
## Documentation
| | File | Modified |
| - | ---- | -------- |
No files shared here yet.
* Drag and drop to upload or \[browse for files]
Upload file
File description
[Buy a Sample Now](https://shop.solid-run.com/?s=%22HummingBoard+Pulse%22\&post_type=product&_ga=2.156269240.2016484779.1641802897-2012112798.1622706355)
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://dev.solid-run.com/renesas/rz-v2n/sbc-platform/hummingboard-iiot-rz-v2n-som-quick-start-guide.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.