Framework Laptop 13 Ryzen 7040 BIOS 3.20 Release BETA

[Quin_Chou]

Highlights

1. Added support for Framework Laptop 13 Pro features - Enabled compatibility for the haptic touchpad, touch panel, and 74W battery.
2. Updated the audio verb table to support the new speakers in the Framework Laptop 13 Pro chassis.
3. Updated AMD PhoenixPI-FP8-FP7_1.2.0.0f.
4. Fixed an issue where the system was unable to boot from partially locked self-encrypting drives (SEDs)
5. Fixed an issue where the Battery Extender status was reported incorrectly following a reboot, hibernation, or shutdown after the timer had expired.
6. Fixed an issue where the system boots with blackscreen when plugged Dell U2725QE monitor with mouse.
7. Supported 16bits postcode.
8. Fixed an issue where system audio volume was lower on 3.19 beta.
9. Security Fixed - CVE-2025-54502, CVE-2025-29949, CVE-2025-0040, CVE-2024-36355, CVE-2024-36310

Note:

1. Once you update to 3.20, you can only downgrade to 3.06 or above.

You can check your current BIOS version following the steps here to determine if you are on the latest release.

After the beta release, we will monitor community feedback, and publish this release to our stable release channel after approximately one week if no major issues are reported.

Subscribing to release notifications

If you want to subscribe to new release notifications you can now opt in through this link to receive an email when we release a new BIOS or driver update for your Framework Laptop.

Downloads

Windows

Download Link	SHA256
Framework_Laptop_13_Ryzen7040_BIOS_3.20.exe	E7A088E2D22015659A49F02660E71E05ECF74BC9B9273F3164B2F5D8311BA397

Instructions for Windows Installer:

1. Run the .exe.
2. Click yes to reboot.
3. Wait for the firmware progress bar to complete, and then the system will reboot.
4. If you are updating a system in standalone mode, please pay careful attention to the standalone update process below.

Please note that you must update with a charger attached.

Linux/LVFS

Updating via LVFS is available in the testing channel during the beta period.

You can enable updates from testing by running

fwupdmgr enable-remote lvfs-testing

Please note that you must update with a charger attached, then run:

fwupdmgr refresh --force

then

fwupdmgr get-updates

then

fwupdmgr update

Please note that you must update with a charger attached.

LVFS may not update if the battery is 100% charged. LVFS uses the battery status to determine if it is safe to apply updates. However if our battery is at 100% and the charger is off, we set the battery charging status to false. In this case you can discharge your battery a few percent, then plug in AC again and run fwupdmgr update.

Linux/Other/UEFI Shell update

Download Link	SHA256
Framework_Laptop_13_Ryzen7040_BIOS_3.20_EFI.zip	BE01CCA148C9F9754F73DF5CBD0641B3CA097A59970C483A6E24CBEAF50504DF

Note that if you use the EFI shell update with Windows, you should suspend Bitlocker if enabled before updating using the EFI updater.

Instructions for EFI shell update:

1. 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.
2. Attach a charger to your device while updating.
3. Boot your system while pressing F12 and boot from the thumb drive.
4. Let startup.nsh run automatically.
5. Follow the instructions to install the update.

Updating a Mainboard outside of a laptop

This release supports standalone updates without a battery attached. After rebooting, please follow the onscreen instructions to update your BIOS when in standalone mode, which will require moving the power source between both sides of the Mainboard to allow PD firmware to update correctly.

Please note that the power and display output must be connected to the same side during standalone updates. Failure to do this may result in no display output during the update process.

We recommend the following update flow for standalone updates:

Part 1

Ensure that standalone operation is enabled in the bios advanced setup menu.

Display connected to upper left port.
Power connected to the lower left port.
Run the updater from EFI/Windows updater.

After rebooting into the updater the update will commence:

The updater will update the BIOS and EC.

The Updater will update the PD controller that is not connected to the power source.

You will see one PD controller will fail the update with the X, and “update complete” is displayed, but the bios will restart.

Part 2

At this screen, the bios update will stop. You must disconnect the display and power source, and move them to the other side.
The display should be connected to the top right.
Power should be connected to the bottom right.

Press the power button, and the second PD update will complete.

After this, the system will reboot, and your bios update is complete.

Security Fixes

CVE	Note	Score (CVSS Version 3.x)
CVE-2025-54502	Incorrect use of boot service in the AMD Platform Configuration Blob (APCB) SMM driver could allow a privileged attacker with local access (Ring 0) to achieve privilege escalation potentially resulting in arbitrary code execution.	N/A
CVE-2025-29949	Insufficient input parameter sanitization in AMD Secure Processor (ASP) Boot Loader (legacy recovery mode only) could allow an attacker to write out-of-bounds to corrupt Secure DRAM potentially resulting in denial of service.	N/A
CVE-2025-0040	Improper access control between the Joint Test Action Group (JTAG) and Advanced Extensible Interface (AXI) could allow an attacker with physical access to read or overwrite the contents of cross-chip debug (XCD) registers potentially resulting in loss of data integrity or confidentiality.	N/A
CVE-2024-36355	Improper input validation in the SMM handler could allow an attacker with Ring0 access to write to SMRAM and modify execution flow for S3 (sleep) wake up, potentially resulting in arbitrary code execution.	N/A
CVE-2024-36310	Improper input validation in the SMM communications buffer could allow a privileged attacker to perform an out of bounds read or write to SMRAM potentially resulting in loss of confidentiality or integrity.	N/A

Enhancements

1. Added support for Framework Laptop 13 Pro features - Enabled compatibility for the haptic touchpad, touch panel, and 74W battery.
2. Updated the audio verb table to support the new speakers in the Framework Laptop 13 Pro chassis.
3. Updated AMD PhoenixPI-FP8-FP7_1.2.0.0f.
4. Supported 16bits postcode.

Fixes

1. Fixed an issue where the system was unable to boot from partially locked self-encrypting drives (SEDs)
2. Fixed an issue where the Battery Extender status was reported incorrectly following a reboot, hibernation, or shutdown after the timer had expired.
3. Fixed an issue where the system boots with blackscreen when plugged Dell U2725QE monitor with mouse.
4. Fixed an issue where system audio volume was lower on 3.19 beta.
5. Security Fixed - CVE-2025-54502, CVE-2025-29949, CVE-2025-0040, CVE-2024-36355, CVE-2024-36310

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.

BIOS	3.20	Updated
EC	ec_320_e0a4f	Updated
PD	0.0.1C	Same
AMD PI	1.2.0.0f	Updated

Reporting Issues

To report issues we have created a public issue tracker on github. Issues · FrameworkComputer/SoftwareFirmwareIssueTracker · GitHub We hope that this is a better way to track issues with community involvement moving forward as we have found it difficult to both gather relevant information about issues people are reporting on the forums, and track the issues through their lifecycle in a transparent way.
If you do 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.

If you have an issue regarding hardware, broken devices, returns, etc, this is not the place, please contact support.

Known Issues

• BIOS display output may not show up in standalone mode when booting the first time. To work around this issue we suggest booting into the OS and then restarting and pressing F2 to enter the setup menu.
• When updating in standalone mode, there may be no display output after updating one side’s PD firmware. Suggest connecting power and display on the same side when performing a BIOS update in standalone mode.
• Connecting with iPhones over type-c may be unstable.

[Adrian_Joachim]

Is this just 3.19 with the audio fix or have there been other significant changes?

[Quin_Chou]

Yes, only base on 3.19, then add the audio fix.

[Figo]

Updated to 3.20 Everything seems to work fine, also the audio

[DataBase]

@Figo

Updated to 3.20 Everything seems to work fine, also the audio

Me too. I updated from 3.19 to 3.20 using the .exe from inside Windows 11.
At the end the screen did stay black for long enough to send my anxiety level sky-high, but it did come back without any intervention after not too long.

[Russ_S]

Fedora 44. FM13 7840. Updated from 3.19 to 3.20. Sound issue is fixed. Everything else seems fine.

[dimitris]

Another FW13 7840U here, Fedora 44, 3.19 → 3.20, all seems good. Audio from laptop speakers sounded louder in a brief test.

[Rei]

@Quin_Chou thank you for the on-time release of 3.20!

Machine is 7640U here. Upgraded from 3.18 to 3.20 via UEFI shell. no issue, audio works as expected.

I didn’t install 3.19

[Andrew_Kahn]

Works fine, like others have noted at first boot there is a black screen for a very long time. It’s no problem but your heart may sink.

[grfgh]

Updated 3.18 → 3.20 using fwupdmgr from NixOS, 7640u.
So far no issues.

(NB. bound TPM got reset during this update, as usually expected)

[DataBase]

@Andrew_Kahn

first boot there is a black screen for a very long time.

Re-training for SODIMM memory timings perhaps?

I’m not actually sure how long mine took, since I left it on its own once I had, fairly quickly, realised it was just stressing me out.

[Andrew_Kahn]

No clue, but probably?