> 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/v3000/sbc-platform/bedrock-v3000-technical-documentation/software-bedrock-v3000/bios-bedrock-v3000/bedrock-v3000-bios-image-files.md).

# Bedrock V3000 BIOS Image Files

## Bedrock V3000 BIOS Image Files

{% hint style="info" %}
Please follow [BIOS update procedure](/amd/v3000/sbc-platform/bedrock-v3000-technical-documentation/software-bedrock-v3000/bios-bedrock-v3000/bios-update-procedure.md) carefully. Incorrect BIOS update might lead to BIOS corruption that cannot be recovered and would require an RMA.
{% endhint %}

{% hint style="info" %}
Before updating BIOS, you are advised to [check current BIOS version](#how-to-check-bios-version)
{% endhint %}

## Current BIOS version

### BIOS V1.22 Release for Bedrock V3000

**File name**: 0ACSK122\_SOLIDRUN\_RELEASE.rom

**Release date**: 12-OCT-2026

**MD5**: 60ea1b6e17c7f20bf01121e56f6547bf

**sha256:** 90ff12e6909144c3c9ebcd4b7f051b4b55b9d7b338fbaac4d74be7e74cd0581b

{% file src="/files/qZ0TcCdtW5AWdygQHNI3" %}

#### Release notes

1. Moved PBS menu back up.
2. Made Bifurcation correct for COM7 Build.
3. Fixed ACPI SPCR to work correctly.
4. Removed Chipset tab.
5. Fixed Non functional console on first boot after BIOS flash that looks like a hang.
6. Improved BMC <-> bios ssif communication.
7. Updated To AGESA 1.0.0.Be.
8. Fixed Issue where the fTPM screen was not visible in console appearing as a hang.
9. Removed all Redundant reboots on BIOS first flash.
10. Fixed ocasional reboot loop due to incorrect KBRST pull.

## Older BIOS versions

### BIOS V1.03 Release for Bedrock V3000

**File name**: BIOS\_BDV3000\_RELEASE\_V1.03\_SIGNED.BIN

**Release date**: 26-MAR-2024

**MD5**: 64ce5d561001dda950843c0af03af243

{% file src="/files/iBSuPl8OCFjWMgG2Uk5N" %}

#### Revision notes

* Disable ASPM for all PCI devices

### BIOS V1.01 Release for Bedrock V3000

**File name**: BIOS\_BDV3000\_RELEASE\_V1.01\_SIGNED.BIN

**Release date**: 15-Feb-2024

**MD5**: ee49a250859b8e36fe138efff553d746

{% file src="/files/V9IGAn7c4wGoadAsCJkN" %}

#### Revision notes

* Fix V3000 CPUs boot failures with ECC memory

### BIOS V1.0 Release for Bedrock V3000

**File name**: BIOS\_BDV3000\_RELEASE\_V1\_SIGNED.BIN

**Release date**: 15-OCT-2023

**MD5**: 68f94b371618e942a529187b19ebbfbc

{% file src="/files/YcoPVLKnYt5MCGxhjU4q" %}

#### Revision notes

* AGESA 1.0.0.5
* Console encoding was set to VT-UTF8

{% hint style="info" %}
Early Bedrock V3000 samples shipped before 25-Aug-2023 (serial number B3D-230825 or smaller) may have an issue with BIOS update due to signature incompatibility. If you have such a Bedrock V3000 sample and need to update BIOS please contact SolidRun.
{% endhint %}


---

# 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/amd/v3000/sbc-platform/bedrock-v3000-technical-documentation/software-bedrock-v3000/bios-bedrock-v3000/bedrock-v3000-bios-image-files.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.