> 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/marvell/a38x/sbc-platform/a388-software/a388-buildroot.md).

# A388 Buildroot

## Description

Buildroot is a simple, efficient and easy-to-use tool to generate embedded Linux systems through cross-compilation.

This wiki page describes the build of complete minimal SD card image, that\
includes U-Boot, kernel, and filesystem ready to boot.

## Build Instructions

## **1. Download and extract the source of Buildroot version 2018.11:**

```
wget https://buildroot.org/downloads/buildroot-2018.11.tar.bz2
tar xf buildroot-2018.11.tar.bz2
cd buildroot-2018.11/
```

**2. Configure and build the SD card image:**

```
make solidrun_clearfog_defconfig
make
```

At the end of the build, the SD card image file is at `output/images/sdcard.img`.

## Deploy Instructions

1\. Write the image that Buildroot generated to your SD card with the following command as root:

```
dd if=output/images/sdcard.img of=/dev/sdX bs=1M conv=fdatasync
```

{% hint style="info" %}
Note that `/dev/sdX` must match the device node of the SD card on your PC host.
{% endhint %}

2\. Set the Clearfog board DIP switches to boot from SD. See the [ClearFog A388 Boot Select](https://dev.solid-run.com/marvell/a38x/sbc-platform/a388-other-articles/clearfog-a388-boot-select.md) article for details.

3\. Insert your SD card to the SD card slot, and power up the board.

## Customization and Package Selection

To install other software packages and customize the filesystem image, use the Buildroot configuration menu, and build again:

```
make menuconfig
make clean all
```

* For more details on Buildroot customization options see the [Buildroot user manual](https://buildroot.org/downloads/manual/manual.html).


---

# 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/marvell/a38x/sbc-platform/a388-software/a388-buildroot.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.
