> For the complete documentation index, see [llms.txt](https://dev.solid-run.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dev.solid-run.com/renesas/rz-v2n/sbc-platform/solidsense-aiot-and-rz-v2n-som-quick-start-guide.md).

# Solidsense AIOT & RZ/V2N SOM Quick Start Guide

<figure><img src="/files/LCHGZtpf4jCw4G0vjuqF" alt=""><figcaption></figcaption></figure>

## Introduction

The following quick start guide provides background information about the Solidsense AIOT.

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**       |
| ---------- | --------- | ------------ | --------------- |
| 9 Jul 2026 | Yazan     | 1.0          | Initial release |

## Hardware Setup

### Product specifications

|                                                 | SolidSense AIoT V2N                                                                                                                                                                         |
| ----------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <p><strong>Processor</strong><br></p>           | <p>Renesas RZ/V2N Quad Core Arm Cortex A55, up to 1.8GHz,<br>1x Cortex M33</p>                                                                                                              |
| <p><strong>Neural Network Core</strong><br></p> | <p>Arm Mali-G31, AI Accelerator DRP-AI3<br>(15 Sparse TOPS / 4 Dense TOPS)</p>                                                                                                              |
| <p><strong>Vision Subsystem</strong><br></p>    | 4x IF LEDs                                                                                                                                                                                  |
| <p><strong>Memory & Storage</strong><br></p>    | <p>Up to 8GB LPDDR4<br>Up to 128GB eMMC<br>MicroSD</p>                                                                                                                                      |
| <p><strong>Camera Interface</strong><br></p>    | 2x MIPI-CSI 4 lanes                                                                                                                                                                         |
| <p><strong>Camera Sensor</strong><br></p>       | <p>IMX678 Lens with/out IR CUT<br>Other options upon request<br></p>                                                                                                                        |
| <p><strong>Optional Sensors</strong><br></p>    | PIR, Ambient Light, Humidity & Temperature, Accelerometer, Ultrasonic Microphone                                                                                                            |
| <p><strong>Networking</strong><br></p>          | <p>802.11 a/b/g/n/ac/ax WiFi<br>Bluetooth 5.3<br>LTE Cat1bis (nanoSIM)</p>                                                                                                                  |
| <p><strong>I/Os</strong><br></p>                | <p>USB 2.0<br>I2C<br></p>                                                                                                                                                                   |
| <p><strong>Misc.</strong><br></p>               | <p>ULP MCU<br>RTC (Part of MCU)<br>EEPROM<br>Battery Management and Charger<br>Dual Microphone (Audio In)<br>Mono Speaker (Audio Out)<br>IR LED FLASH (for low light image capture)<br></p> |
| <p><strong>Power</strong><br></p>               | <p>Li-Ion 3.6V nominal<br>USB-C input charging port</p>                                                                                                                                     |
| **Temperature**                                 | Industrial: -40°C to 85°C                                                                                                                                                                   |
| **Enclosure**                                   | Plastic ABS IP64 Rated                                                                                                                                                                      |
|                                                 | [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](/renesas/rz-v2n/com-som/rz-v2n-som-hardware-user-manual.md).
{% endhint %}

#### Block Diagram

The following figure describes the Solidsense AIOT Block Diagram.<br>

<figure><img src="/files/NgFIzVDZfsIjVAxsWrio" alt=""><figcaption></figcaption></figure>

#### Visual features overview

Please see below the features overview of the connector side of the Solidsense AIOT & RZ/V2N SOM.

<figure><img src="/files/YwpX7RJ1l9L9FRYhXVsU" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/vvC8rZVlNa5O2roS2y87" alt=""><figcaption></figcaption></figure>

**Flash Card (IR Flash & Sensors)**

<figure><img src="/files/S83XMMFWSg9z4LOxvM00" alt=""><figcaption></figcaption></figure>

### Powering Up the SolidSense AIOT

The SolidSense AIOT can be powered from any one of three independent sources — pick whichever fits your setup.

#### Power Options

<table><thead><tr><th width="48">#</th><th width="150">Source</th><th width="127">Connector</th><th>Notes</th></tr></thead><tbody><tr><td>1</td><td><strong>DC input</strong></td><td><strong>J1</strong> — HDR 2×1, 3.50 mm</td><td>Wide range <strong>5 V–12 V</strong>.</td></tr><tr><td>2</td><td><strong>Battery</strong></td><td><strong>J2</strong> — HDR 2×1, 2.0 mm</td><td>For portable / embedded use, no wall adapter needed.</td></tr><tr><td>3</td><td><strong>USB Type-C</strong></td><td>Type-C port</td><td>Powers the board <strong>and</strong> provides the serial console over one cable (onboard FTDI).</td></tr></tbody></table>

{% hint style="info" %}
Only **one** power source is necessary at a time, but it is also acceptable to connect **multiple sources** simultaneously.
{% endhint %}

**DC Power \[J1]**

<div align="left"><figure><img src="/files/oGckY1LI3MOeGruxNLUy" alt=""><figcaption></figcaption></figure></div>

**Power Input Polarity \[J1]:**

* **Connector Type**: Green two-terminal connector \[J1].
* **Voltage Range**: 5V-12V.
* **Polarity**:
  * **+ (Positive)**: Left terminal (as marked in the image).
  * **- (Negative)**: Right terminal (as marked in the image).
* **Mating plug:** 2-position terminal block plug, female sockets, 0.138″ (3.50 mm) pitch

<div align="left"><figure><img src="/files/xrBGuSIywW7etcvdxO8n" alt="" width="140"><figcaption><p>like <a href="https://www.digikey.co.il/he/products/detail/w-rth-elektronik/691361300002/2060572">this</a></p></figcaption></figure></div>

{% hint style="info" %}
The board includes **reverse-polarity protection**, so an accidentally reversed connection will not damage it. Still, wire J1 with the correct polarity for normal operation.
{% endhint %}

## Software Setup

### Cable Setup & Prerequisites

You will need:

* A **Linux or Windows PC**
* **SolidSense AIOT with SOM** (SolidSense AIOT carrier + module)
* **12 V power adapter** — wide input **5 V–12 V**; or power via **USB Type-C** or **batteries 3.7V+.**
* **Type-C to USB cable** for the console — the onboard **FTDI chip** provides serial-console access over the same cable

## Boot Select

<figure><img src="/files/6qhwMw8ySIHSU5Ctdi7L" alt=""><figcaption></figcaption></figure>

Before powering up the board for the first time it is recommended to select the boot media using onboard DIP switch **S1**:

| **Switch**            | <p><strong>1</strong><br>(MD0)</p> | <p><strong>2</strong><br>(MD1)</p> | <p><strong>3</strong><br>N/A</p> | <p><strong>4</strong><br>N/A</p> | <p><strong>5</strong><br>(VDD\_3.3V)</p> | <p><strong>6</strong><br>(VDD\_1.8V)</p> |
| --------------------- | ---------------------------------- | ---------------------------------- | -------------------------------- | -------------------------------- | ---------------------------------------- | ---------------------------------------- |
| **SPI**               | OFF                                | **ON**                             | X                                | X                                | OFF                                      | **ON**                                   |
| **eMMC**              | **ON**                             | OFF                                | X                                | X                                | OFF                                      | **ON**                                   |
| **Serial Downloader** | **ON**                             | **ON**                             | X                                | X                                | OFF                                      | **ON**                                   |

{% hint style="info" %}
**MDx = BOOT\_MODEx.**\
**VDD\_BOOT** can be either **1.8V** or **3.3V** (selectable via **S1\[5]** or **S1\[6]**).

* **BOOT\_MODE2 = ‘1’** → fixed to **1.8V** at the SOM level
* **BOOT\_MODE3** and **BOOT\_MODE4** → fixed to **GND** at the SOM level
  {% 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:

![image-20251120-125321.png](/files/LeIaEuvHv73jZVm4QjFD)

{% 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/RZ/Yocto/vlp4/2026-07-07_adfb4ad/rzv2n-sr-som/core-image-full-cmdline-rzv2n-sr-som.rootfs.wic.gz
```

* For more Debian releases, please visit <https://images.solid-run.com/RZ/Yocto/vlp4>.

2. **Writing the image to the SD card**

Use the following commands for writing the image to an SD card:

```
gunzip -dc core-image-full-cmdline-rzv2n-sr-som.rootfs.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:

![image-20251120-160133.png](/files/4QD38aynEBr9gG8oZW2k)

* In order to be able to log in, please insert “**root**” as a username and password.

## Streaming 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 `<LAPTOP_IP>` 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=<LAPTOP_IP> 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) <a href="#bootloader-firmware-flashing-bl2--fip" id="bootloader-firmware-flashing-bl2--fip"></a>

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 <a href="#flashing-methods" id="flashing-methods"></a>

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 <a href="#build-artifacts" id="build-artifacts"></a>

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**                           |                                                                                                                                                      |
| -------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
| ![](/files/ImHWJmfF4P3oYZioMt5Z) | [GitHub - SolidRun/build\_rzg2lc at rzv2n-dev](https://github.com/SolidRun/build_rzg2lc/tree/rzv2n-dev)                                              |
| ![](/files/PlmAE45Q3UFzqgv7QbHP) | [GitHub - SolidRun/meta-solidrun-arm-rzg2lc at scarthgap\_rzv2n\_dev](https://github.com/SolidRun/meta-solidrun-arm-rzg2lc/tree/scarthgap_rzv2n_dev) |
| ![](/files/njazv9ZRULsuUuzHC3CU) | [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

Use the attached file below for additional product documentation.

{% file src="/files/uypWfUJLFwcgBX28DZVb" %}

{% file src="/files/iolwfTXQHSZQd7hHcBhz" %}

[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
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://dev.solid-run.com/renesas/rz-v2n/sbc-platform/solidsense-aiot-and-rz-v2n-som-quick-start-guide.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.