Framework Laptop 13 Ryzen 7040 BIOS 3.19 Release BETA

Framework Laptop 13
, , , ,
1

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. Security Fixed - CVE-2025-54502, CVE-2025-29949, CVE-2025-0040, CVE-2024-36355, CVE-2024-36310

Note:

  1. Once you update to 3.19, 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.19.exe 0162C78DB9D0977975490BFD7BC05BB6BBDB38DC799D96438DF7A6A16126E753

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.19_EFI.zip 2649BD4B76C5CFBD0A34AC7EC97B4C700E607F506892CD8ED7D3094486744861

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.

image
image1248Ă—702 59.5 KB

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

image
image1248Ă—702 59.6 KB

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

image
image1248Ă—702 64.2 KB

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.

image
image1380Ă—776 50.6 KB

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

image
image1248Ă—702 55.9 KB

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. 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.19 Updated
EC ec_319_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.
10 Likes
Framework Laptop 13 Ryzen 7040 BIOS 3.18 Release STABLE
Framework Laptop 13 Ryzen 7040 BIOS 3.18 Release STABLE
2

I installed this on my unit and I can confirm that it fixes the dock USB issue and that everything else seems to be working fine. The only issue I had was the usual one where the monitor has to be unplugged and replugged once after the firmware update to resume operation.

3 Likes
3

Looks good so far. Booting up (and resuming from s2idle) with the Dell WD25TB5 dock plugged in (includes USB keyboard) works without issues.

There’s an issue where boltctl doesn’t recognize the dock as thunderbolt on first cold boot but that was already the case under 3.17 - some race condition between the dock’s firmware, BIOS, and the Linux thunderbolt driver, I guess. Resolves with a power cycle on the dock.

2 Likes
4

NOTE: I only use Windows 11 on my Laptop 13.

My BIOS upgraded from 3.18 to 3.19 okay and hasn’t caused any major problems. I used the Windows .exe updater.

There could do to be a better warning that the reboot does not signal that the process is complete and the delay before the second reboot was also rather longer than I expected, but probably only 15 seconds or so. I don’t know if it would have mattered if I’d interrupted it, but I didn’t.

The sound level from the internal speakers seems a lot quieter with this BIOS. But turning the volume too 100 still exceeds any volume level I will need, so still usable, I just need the volume at 40 or 50 instead of at 20 now.

Maybe the Realtek loudness equalisation feature is changed (or broken) in BIOS 3.19? I’m sure turning on loudness equalisation used to make the speakers a lot louder, but now it only makes a slight difference.

Anyway something to do with the speakers has definitely changed, but at this stage I’m thinking it’s just something I’ll need to get used to, rather than a problem I have to learn to live with if I stay on BIOS 3.19. Perhaps after a while I’ll realise it’s actually better this way?

1 Like
5

Remember: report issues to GitHub as well.

https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-19-release-beta/82775#p-339392-reporting-issues-14

1 Like
6

I can confirm this release works with my CalDigit TS4. I can boot now without having to do the dock/undock/redock dance every time I’m starting my machine. I still don’t get why it took half a year to ship a fix.

7

Was just about to come and confirm the same, Caldigit TS4 now works with this release.

8

While it updated fine and also fixed the docking issue (Framework Laptop 13 Ryzen 7040 BIOS 3.18 Breaks Booting With Dock Connected · Issue #170 · FrameworkComputer/SoftwareFirmwareIssueTracker · GitHub), during the update, towards the end, I never saw the “Update Complete!!!” message, the display rather just went blank. I waited a minute and then rebooted using the power button, which worked. Just slightly scary. Thanks!

1 Like
9

Everything seems to be working thus far.

Windows 11, 25H2 - Framework 7840u, 2nd gen keyboard/trackpad, 2nd Gen webcam, 2.8k screen, 64GB of RAM, Samsung 990 Pro 2TB.

10

Everything seems to work so far, including my dock (Kensington SD5760T). I skipped 3.18, though, because reports of dock problems were already in.

With this version, the Battery Saver seems to work for the first time since many versions. This is interesting, because Framework support told me after a very thorough troubleshooting that I would need a new mainboard in order to get the Battery Saver to work.

1 Like
11

I am also disappointed with the speaker performance after the upgrade. Is is possible to ship multiple verb tables and have a selector in the UEFI to set which is used?

12

Please report the issue on GitHub; there is already an active issue there: Computer Issue Framework Laptop 13 AMD 7040 series BIOS 3.19 change in loudness of internal speakers · Issue #220 · FrameworkComputer/SoftwareFirmwareIssueTracker · GitHub

GitHub is the right place for problems. Maybe it will get fixed, and 3.19 will not switch to stable with known issues.

13

That’s my issue. So far it doesn’t look like they believe me, they claim it’s only a 2dB change in level, which is ridiculous, I probably wouldn’t even have noticed a 2dB change.

14

I’m now on 3.19; the update went well, and docking also works with my Lenovo Thunderbolt dock.

The speakers are noticeably quieter: the previous level 20 is now at about 50, and the previous 50 is now at level 100.

I did a simple measurement, using Phybox on a Samsung Galaxy S25, both with the same track on Spotify. You can see the bumps in the amplitude where I changed from level 20 to 50 and finally to 100. The left side is BIOS 3.17, and the right side is BIOS 3.19.

It’s not scientifically accurate :wink:

grafik
grafik1080Ă—1026 48.8 KB

2 Likes
15

Isn’t dB a logarithmic scale where every 3dB is roughly 2x? I think you might notice 2dB it’s maybe something like a 50% difference?

1 Like
16

The thing is dB is roughly human perception scale. We don’t perceive intensity linearly as well.

This graph however shows what seems to be a lot more than a 2 dB drop?

17

Ah, you’re right I guess it should be 10dBA for doubling perceived loudness.

18

Increasing sound output by 3dB requires 2x the amplifier power. Human ears will perceive 10dB difference as 2x (or 1/2) the loudness. 6dB change doubles the sound PRESSURE, so it requires 4x the amplifier power to double the sound PRESSURE. Physical world all kinds of messy. :melting_face:

19

Slight Edit, sound is much crisper on the FW13 but volume is waaaaaaaaaaaaay lower. Not a problem, but it’s notaceably quieter at higher volumes.

20

I have not updated yet, but I wonder what the split may be for the 2 different sets of speakers. If the adjustment is causing an issue with the original speakers v the 80db ones at a disproportionate level, or if that makes a difference at all. Especially as there is reporting surrounding different levels of clarity/loudness in the “stock” speakers on this mainboard back when it was released.