> For the complete documentation index, see [llms.txt](https://openhd.gitbook.io/open-hd/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://openhd.gitbook.io/open-hd/hardware/cameras/radxa-cameras.md).

# Radxa Rock5

> ⚠️ **This documentation is outdated!** A current version is available at [openhdfpv.org](https://openhdfpv.org)
>
> [📖 **View Updated Version of This Page** →](https://openhdfpv.org)

***

## Overview

As the Rock5 is a distinct platform and MIPI is not a plug-and-play system, we are awaiting official camera releases for compatibility. We are actively dedicating resources to introduce more camera options in the future.

Currently, the camera support is limited to:

| Camera               | Recommended | Notes |
| -------------------- | :---------: | :---: |
| IMX219               |             |   1   |
| IMX415\*             |      \*     |       |
| Arducam IMX462 B0333 |      \*     |   1   |
| Arducam IMX708 B0310 |      \*     |   1   |

> **Note 1**: There currently appears to be no compatible adapter or camera with this sensor available for the Rock5.

We are working towards expanding the selection of supported cameras and adapters, and we appreciate your patience as we continue to develop and improve camera compatibility


---

# 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://openhd.gitbook.io/open-hd/hardware/cameras/radxa-cameras.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.