> For the complete documentation index, see [llms.txt](https://docs.earthdefenderstoolkit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.earthdefenderstoolkit.com/device-setup/single-board-computers.md).

# Single-board-computers

The process for a single-board-computer (SBC) is much simpler, and only requires burning an sd card.

**Recomended devices:**

* [Raspberry Pi 4](https://www.raspberrypi.com/products/raspberry-pi-4-model-b/)
* [RockPi 4 B+](https://wiki.radxa.com/Rock4/4abplus)

#### Needed hardware

* Any of [supported devices](http://releases.earthdefenderstoolkit.com/)
* Class 10 micro sd card with at least 32gb
* A computer with a sd card reader
* Internet connection through ethernet cable

#### Needed software

* Image burner, recommended: [Balena Etcher](https://www.balena.io/etcher/)

#### Preparing USB flash drive

Download the appropriate image for your device: [http://releases.earthdefenderstoolkit.com](http://releases.earthdefenderstoolkit.com/)

Use the image burner to burn the image to the sd card.

#### Installing the Offline Toolkit

* Insert the flashed sd card into the computer
* Insert the ethernet cable with Internet coming from your router into the computer
* Check the [Balena Dashboard](https://dashboard.balena-cloud.com/) for the device to come online, or check if a new WiFi hotspot has appeared


---

# 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://docs.earthdefenderstoolkit.com/device-setup/single-board-computers.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.