> For the complete documentation index, see [llms.txt](https://wiki.libreelec.tv/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.libreelec.tv/hardware/allwinner.md).

# Allwinner

## Disclaimer

* **Only nightly releases are available right now. Use at your own risk!**
* **Boards/STBs with less than 1GiB of RAM are not supported**

## Boards Supported

### **A64 based boards**

* OrangePi Win
* Pine64
* Pine64 LTS
* Pine64 Plus

### **H3 based boards**

* BananaPi M2+
* Beelink X2
* Libretech ALL-H3-CC (Tritium)
* NanoPi M1
* OrangePi 2
* OrangePi PC
* OrangePi PC plus
* OrangePi Plus/Plus 2
* OrangePi Plus 2E

### H5 based boards

* OrangePi PC 2

### **H6 based boards**

* Beelink GS1
* OrangePi 3
* OrangePi 3 LTS
* OrangePi Lite 2
* OrangePi One Plus
* Pine H64
* Tanix TX6

### **R40 based boards**

* BananaPi M2 Ultra


---

# 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://wiki.libreelec.tv/hardware/allwinner.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.