> 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/amd/rai300/com-som/honeycomb-com-6-errata.md).

# HoneyComb COM 6 Errata

### Device fails to Boot after it is powered off and power button is pressed <a href="#device-fails-to-boot-after-it-is-powered-off-and-power-button-is-pressed" id="device-fails-to-boot-after-it-is-powered-off-and-power-button-is-pressed"></a>

#### Symptom <a href="#symptom" id="symptom"></a>

After powering off the device and powering it on using the power button / remote power button, the device fails to boot. In console you will see:

<a class="button secondary">Copy</a>

```
ABL BP[80000000]
```

#### Solution <a href="#solution" id="solution"></a>

Disconnect power and connect it back to the unit.

#### Root cause <a href="#root-cause" id="root-cause"></a>

Unknown

***

### Device fails to boot Memtest86 <a href="#device-fails-to-boot-memtest86" id="device-fails-to-boot-memtest86"></a>

#### Symptom <a href="#symptom-1" id="symptom-1"></a>

The device will not boot Memtest86 with an error saying: "failed to calibrate CPU frequencies".

#### Solution <a href="#solution-1" id="solution-1"></a>

None

#### Root cause <a href="#root-cause-1" id="root-cause-1"></a>

HPET is disabled in order to allow Linux to boot. (temporary)

***

### USB 2.0 header is not functional <a href="#device-fails-to-boot-memtest86" id="device-fails-to-boot-memtest86"></a>

#### Symptom <a href="#symptom-1" id="symptom-1"></a>

The USB 2.0 header is nt functional

#### Solution <a href="#solution-1" id="solution-1"></a>

None

#### Root cause <a href="#root-cause-1" id="root-cause-1"></a>

Work in progress


---

# 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://dev.solid-run.com/amd/rai300/com-som/honeycomb-com-6-errata.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.