Framework Desktop AMD Ryzen™ AI Max+ PRO 400 Series — BIOS 3.00
Downloads
Section titled “Downloads”- Initial public release
Component Versions
Section titled “ Component Versions ”This BIOS update is a bundle of updates to multiple embedded components in the system. Not all of them use the same version number.
| Component | Version | |
|---|---|---|
| EC | ec_300_20f4929 | |
| PD | 0.0.10 | |
| AMD PI | GorgonHaloPI-FP11 1.0.0.0b |
Windows Driver Component Versions
Section titled “ Windows Driver Component Versions ”| Driver | Version | |
|---|---|---|
| AMD Chipset Driver | 8.07.28.629 | |
| AMD Graphics Driver | 32.0.31032.3 | |
| Realtek Audio Driver | 6.0.10023.1 | |
| Realtek Audio Console | 1.54.397.0 | |
| RZ717 WiFi Driver | 5.7.0.6028 | |
| RZ717 Bluetooth Driver | 1.1146.0.608 | |
| WiFi ACX Driver | 1.6.0.50 | |
| Realtek Ethernet Lan | 1126.031.50.603 | |
| AMD DRTM Driver | 1.0.19.5 | |
| Framework EC | 0.0.0.6 | |
| Realtek Ethernet (Expansion Card) | 11013_20_07272023_08042023 | |
| SD Card Reader (Expansion Card) | v4_5_10_201 | |
| 2nd Gen uSD Card Reader (Expansion Card) | v4_5_10_202 |
Installation
Section titled “Installation”You can check your current BIOS version following the steps here to determine if you are on the latest release.
Framework firmware is published to LVFS and updates via fwupd, which ships by default on most modern distributions.
fwupdmgr refresh --forcefwupdmgr get-updatesfwupdmgr updateWindows
Section titled “Windows”- Download the Framework Desktop AMD Ryzen™ AI Max+ Pro 400 Series BIOS 3.00 Windows Installer.
- Run the
.exeand click "Yes" when prompted to reboot. - Wait for the firmware progress bar to complete — the system will reboot automatically. Do not interrupt.
- Download and install the Windows Driver Bundle v1.00 for your system if you are currently using a previous Driver Bundle release, or you are installing the Driver Bundle for the first time.
EFI Shell Update
Section titled “ EFI Shell Update ”- Download the EFI Shell Update v3.00.
- Extract contents of zip folder to a FAT32 formatted USB drive. Cleanly unmount the drive before physically removing it, otherwise the BIOS update may not function correctly.
- Boot your system while pressing F12 and boot from the thumb drive.
- Let startup.nsh run automatically.
- Follow the instructions to install the update.
BIOS Crisis Recovery Functionality
Section titled “BIOS Crisis Recovery Functionality”At the end of POST, the BIOS hands control off to your operating system. Crisis Recovery is a special alternative mode: instead of booting an OS, the BIOS looks for a firmware update file and re-flashes itself.
Crisis Recovery allows the system to repair its own firmware after a failed or corrupted BIOS flash, for example if a BIOS update was interrupted by a power loss and the machine no longer boots normally.
Prepare the Recovery Drive
Section titled “Prepare the Recovery Drive”On a working system:
- Insert the USB flash drive and format it as FAT32. (This erases the drive)
- On the drive, create the folder path
\EFI\FWK(an EFI folder, and inside it an FWK folder). - Download the EFI Shell Update (BIOS v3.00) and locate the CAP file.
Rename the recovery file to
Framework_Desktop_AMD_Ryzen_AI_Max_400_RECOVERY.fdand copy it into the\EFI\FWKfolder.- Safely eject the drive.
Perform the Crisis Recovery
Section titled “Perform the Crisis Recovery”On a target system:
- Power off the affected system completely.
- Insert the prepared recovery drive into a USB port on the affected system.
- Power on the system. If the BIOS is corrupted it will enter recovery automatically at power-on.
- Wait for the update to complete and the system to restart. The system should then boot to the operating system normally.
Known Issues
Section titled “ Known Issues ”- N/A
Reporting Issues
Section titled “Reporting Issues”Please use the public issue tracker on GitHub to report issues.
If you experience an issue with the update that is related to your system firmware, please post as complete a description as you can, including relevant system information and external peripherals. Please note that we do not currently have a SLA for responding to issues on github, but we will be reviewing them through the bios release process, and will review them for future updates as well.
Please contact support if you have an issue regarding hardware, broken devices, returns, etc.