> 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/solidsense-aiot/solidsense-aiot-rz-v2n.md).

# SolidSense AIOT (RZ/V2N)

## Device Tree Overlays — SolidSense AIOT (RZ/V2N)

The SolidSense AIOT base device tree (`r9a09g056n48-solidsense-aiot.dtb`) describes the bare carrier. Optional hardware — the **Flash Card (J6)** and the **IMX678 MIPI-CSI cameras** on **J8** and **J17** — is enabled at boot by applying one or more device tree overlays via the `FDTOVERLAYS` line in `extlinux/extlinux.conf`. Overlays are built into `freescale/`… *(rzv2n: `renesas/`)* on the boot partition.

The Flash Card carries an LM3645 IR illuminator (driven by `leds-lm3645`, exposed as `/sys/class/leds/ir:flash` and a V4L2 flash sub-device), plus the OPT4001 light sensor and HDC3022 temp/humidity sensor. When a camera overlay is paired with the Flash Card, the IR illuminator is linked to that sensor (`flash-leds`) so the V4L2 pipeline can drive it during capture.

### Choosing an overlay

| Configuration               | `FDTOVERLAYS` entry                                            |
| --------------------------- | -------------------------------------------------------------- |
| Camera **J8** only          | `…/rzv2n-solidsense-aiot-csi-camera-imx678-j8.dtbo`            |
| Camera **J17** only         | `…/rzv2n-solidsense-aiot-csi-camera-imx678-j17.dtbo`           |
| **Dual** cameras J8 + J17   | `…/…-csi-camera-imx678-j8.dtbo …/…-csi-camera-imx678-j17.dtbo` |
| **Flash Card** only         | `…/rzv2n-solidsense-aiot-addon-flash-card.dtbo`                |
| Flash Card + camera **J8**  | `…/rzv2n-solidsense-aiot-addon-flash-card-cam-j8.dtbo`         |
| Flash Card + camera **J17** | `…/rzv2n-solidsense-aiot-addon-flash-card-cam-j17.dtbo`        |

Example `extlinux.conf` line (Flash Card + J8 camera):

```
FDTOVERLAYS ../renesas/rzv2n-solidsense-aiot-addon-flash-card-cam-j8.dtbo
```

Dual cameras (no Flash Card) — apply both single-camera overlays, space-separated:

```
FDTOVERLAYS ../renesas/rzv2n-solidsense-aiot-csi-camera-imx678-j8.dtbo ../renesas/rzv2n-solidsense-aiot-csi-camera-imx678-j17.dtbo
```

{% hint style="info" %}
**Why dual cameras stack but Flash Card + camera does not:** the J8 and J17 camera overlays touch independent nodes, so they can be applied together. A Flash Card + camera combination uses a *single* combined overlay because the camera node references the flash (`flash-leds = <&camera_flash>`), which only resolves when both are in the same overlay.
{% endhint %}

{% hint style="warning" %}
**Flash Card supports a single camera only.** With the Flash Card assembled, use *either* `…-cam-j8` *or* `…-cam-j17` — not both. Dual cameras are only supported when the Flash Card is **not** assembled.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://dev.solid-run.com/solidsense-aiot/solidsense-aiot-rz-v2n.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.