# Framework Laptop 13 Ryzen 7040 BIOS 3.09 Release **URL:** \ **Category:** Framework Laptop 13\ **Tags:** bios-announcement, amd-7040\ **Created:** [May 2, 2025, 7:56am UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-09-release/68601 "2025-05-02T07:56:00Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Quin\_Chou](https://avatars.discourse-cdn.com/v4/letter/q/cdc98d/32.png) [@Quin\_Chou](https://community.frame.work/u/Quin_Chou)\ **Post date:** [May 2, 2025, 7:56am UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-09-release/68601/1 "2025-05-02T07:56:00Z")
**NOTE:** Once you update to 3.09, you cannot downgrade to 3.05 or the version earlier than 3.05. ## Highlights Please note this #1~#6 are copied from 3.07. Delta is 3.05-\>3.09. 1. Fixes for battery extender functionality introduced in 3.06. 2. Modified the charge limit functionality to allow a 5% float range on the battery. 3. Fixed 5 security vulnerabilities. 4. Fixed ALS sensor communication failures. 5. Fixed IRQ1 wake issues on Linux. 6. Fixed diagnostic compatibility issue with 2.8K displays. 7. Fixed the battery extender setting overwritten battery charge limit on boot. 8. Fixed battery charging limit is reset by the battery extender reset timer. You can check your current BIOS version [following the steps here](https://knowledgebase.frame.work/en_us/how-to-check-the-bios-version-on-windows-linux-bios-ryupu8HT3) to determine if you are on the latest release. ### Subscribing to release notifications If you want to subscribe to new release notifications you can now opt in through [this link](https://manage.kmail-lists.com/subscriptions/subscribe?a=LNYsui&g=VskBpF) to receive an email when we release a new BIOS or driver update for your Framework Laptop. ### Battery Extender functionality With the high energy density on the 61Wh battery, leaving it at 100% state of charge for an extended period of time can shorten the lifetime of the battery. To prevent this, we have added a new feature that automatically limits the maximum state of charge if the system is left plugged into power for more than 5 days. The timer is reset after the system is disconnected from a power adapter for more than 30 minutes. | Battery Extender Duration | Battery State of Charge | | --- | --- | | 0-5\< Days | 99% → 100% | | 5-7 Days | 90% → 95% | | \>7+ Days | 85% → 87% | This functionality also reduces cycling of the battery by allowing the battery to discharge by several percent before charging again. Note that in addition to this automatic setting, you can also manually set a lower charge limit on your battery in BIOS to further preserve battery longevity. This feature can be disabled or enabled in the BIOS Advanced menu. ![](https://us1.discourse-cdn.com/flex001/uploads/framework3/original/3X/6/4/648e3e162113e554862b2e7afa2215d436da3b38.jpeg) Battery Extender: This option is enabled by default. If disabled, the system will always keep the battery fully charged. Battery Extender Trigger: This option sets the number of days that must pass before the battery state of charge is reduced automatically to extend the battery life. Battery Extender Reset: This option sets the number of minutes that the system is running on battery before the extender is reset, causing the system to charge to 100% when attached to power again. ### Battery Charge Limit Functionality This release modifies the battery charge limit functionality to add a 5% float range. This allows us to reduce the number of microcycles on the battery when the CPU turbos. Previously to the change in 3.07, the battery would be held at the target state of charge, so if a large power draw happened for a short time, such as when the CPU turbos, the battery would drain slightly and then charge again. Introduced in this version, the battery will not start to charge until the battery has dropped 5% below the charge limit. As an example, if the user sets the battery charge limit to 80%, the battery will maintain a state of charge between 80% and 75%. And will not charge up to 80% until it has discharged to 75% while the system is on. If this is activated while the battery state of charge is above the limit, the battery will discharge without drawing power from the adapter until the upper limit is reached. ## Downloads ### Windows | Download Link | SHA256 | | --- | --- | | [Framework\_Laptop\_13\_Ryzen7040\_BIOS\_3.09.exe](https://downloads.frame.work/bios/Framework_Laptop_13_Ryzen7040_BIOS_3.09.exe) | 23C7D8023E92A61449D6D7486B431427C541455A77B3A62205E3A756EA393102 | 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 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.09\_efi.zip](https://downloads.frame.work/bios/Framework_Laptop_13_Ryzen7040_BIOS_3.09_efi.zip) | 46B2D3AFFA14ACB88AD7C99A2E2CAF8C874742D62009AD199BC01C0D41FC1132 | 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. ![](https://us1.discourse-cdn.com/flex001/uploads/framework3/original/3X/9/9/990026ff1e71573f31a2ed63da1fa64b65b9ed5e.jpeg) The Updater will update the PD controller that is not connected to the power source. ![](https://us1.discourse-cdn.com/flex001/uploads/framework3/original/3X/1/7/177cd75aacfeb773be66f39f2e9cda722aae79a0.jpeg) You will see one PD controller will fail the update with the X, and “update complete” is displayed, but the bios will restart. ![](https://us1.discourse-cdn.com/flex001/uploads/framework3/original/3X/b/1/b1bb702a4b3b42ae95aafe3926cf798733f1922f.jpeg) #### 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. ![|1646.5198237885463x924.4386077586989](https://us1.discourse-cdn.com/flex001/uploads/framework3/original/3X/d/5/d5bee9cba02a7d86a465fcad73fa59df59173975.jpeg) Press the power button, and the second PD update will complete. ![](https://us1.discourse-cdn.com/flex001/uploads/framework3/original/3X/f/f/ff92c92b4edb366c27c0207b0419e74c6eff39ab.jpeg) After this, the system will reboot, and your bios update is complete. ## Security Fixes | Module Name | Vulnerability | Score | | --- | --- | --- | | UefiPxeBcDxe | CVE-2023-45234 | 8.8 | | Dhcp6Dxe | CVE-2023-45230 | 8.8 | | IP6Dxe | CVE-2023-45232 | 7.5 | | IP6Dxe | CVE-2023-45233 | 7.5 | | AMD PI | CVE-2023-31315 | 7.5 | ## Enhancements 1. Modified the charge limit functionality to allow a 5% float range on the battery. If the battery charge limit is set to 80%, now the battery will float between 75%-80%, reducing wear. 2. Lower the screen minimum brightness on Linux. This updates the minimum brightness PWM value in the bios, to allow the screen to default to a lower minimum brightness. Please note that this is not enforced in windows as the AMD graphics driver overrides the minimum brightness setting in the bios. ## Fixes 1. Fixes for battery extender functionality. This release fixes the battery extender functionality bug when enabled with battery charge limit set below 100%. 2. Bug: If the charge limit was below the extender limit, and the extender triggered, the battery would charge above the extender limit. 3. The charging LED would toggle between White/Orange when reaching the charge limit. 4. Fix ACPI thermal\_zone3 reporting incorrect values occasionally. 5. Update driver certificate for org.uefi.Driver.RtkUndiDxe 6. Fixed the battery extender setting overwritten battery charge limit on boot. 7. Fixed battery charging limit is reset by battery extender reset timer. ## 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. | Firmware | Version | Update? | | --- | --- | --- | | BIOS | 3.09 | Updated | | EC | ec\_309\_c25de | Updated | | PD | 0.0.1C | Same | | AMD PI | 1.1.0.3 | Same | ## Reporting Issues To report issues we have created a public issue tracker on github. [GitHub · Where software is built](https://github.com/FrameworkComputer/SoftwareFirmwareIssueTracker/issues) 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. ---
**Author:** ![Rei](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/rei/32/13593_2.png) [@Rei](https://community.frame.work/u/Rei)\ **Post date:** [May 2, 2025, 10:29am UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-09-release/68601/2 "2025-05-02T10:29:05Z")
👏 👏 👏 ---
**Author:** ![inffy](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/inffy/32/39079_2.png) [@inffy](https://community.frame.work/u/inffy)\ **Post date:** [May 2, 2025, 1:04pm UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-09-release/68601/3 "2025-05-02T13:04:08Z")
Doesn’t seem to be available in lvfs-testing yet ---
**Author:** ![BigT](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/bigt/32/17143_2.png) [@BigT](https://community.frame.work/u/BigT)\ **Post date:** [May 2, 2025, 7:06pm UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-09-release/68601/7 "2025-05-02T19:06:52Z")
I’m sure some folks wouldn’t like to see the battery cycling constantly between charing and not, but I think the main reason for doing this is that it’s harder on the battery to have it frequently cycle between charging and discharging. ---
**Author:** ![Matthew\_Shapiro](https://avatars.discourse-cdn.com/v4/letter/m/c37758/32.png) [@Matthew\_Shapiro](https://community.frame.work/u/Matthew_Shapiro)\ **Post date:** [May 2, 2025, 8:29pm UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-09-release/68601/8 "2025-05-02T20:29:00Z")
fwupdmgr finds no update following instructions at the top of the thread. But today it worked. ---
**Author:** ![dimitris](https://avatars.discourse-cdn.com/v4/letter/d/db5fbb/32.png) [@dimitris](https://community.frame.work/u/dimitris)\ **Post date:** [May 2, 2025, 9:04pm UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-09-release/68601/9 "2025-05-02T21:04:20Z")
If it works as intended, it is precicesly what’s needed (and other laptops, including thinkpads, enable/do). That’s because: - The battery [recalibrates itself](https://community.frame.work/t/tracking-battery-flipping-between-charging-and-discharging-draws-from-battery-even-on-ac/22484/244) frequently, so the reported charge can move in either direction. If you haven’t already, go through that thread, especially the most recent half of it, it’s very informative. - It’s preferable to keep the battery idle (not charging _or_ discharging) as much as possible. If the machine is plugged into an adapter that provides enough power, let’s let the battery slooooooowly discharge (self discharge) which should be days per 1% of charge. ---
**Author:** ![James3](https://avatars.discourse-cdn.com/v4/letter/j/b5e925/32.png) [@James3](https://community.frame.work/u/James3)\ **Post date:** [May 2, 2025, 9:13pm UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-09-release/68601/10 "2025-05-02T21:13:57Z")
@Quin_Chou I am curious about a little clarification regarding how the battery extender is supposed to behave. If your battery is fully charged at 100% with the battery limit set to 100%, if left fully charged, it can damage the battery, so one would want the battery to discharge itself to say 90%. What is supposed to happen if the battery currently has a 80% charge? Its not at 100%, so not going to damage the battery. In this use-case, what happens. It seems to me, that if the battery is at 80% charge, the battery extender should not trigger at all, because its not providing any benefit. So, the clarification question is: If the current battery charge is 80%, is the battery extender supposed to trigger, or is it not supposed to trigger at all? ---
**Author:** ![inffy](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/inffy/32/39079_2.png) [@inffy](https://community.frame.work/u/inffy)\ **Post date:** [May 3, 2025, 6:09am UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-09-release/68601/13 "2025-05-03T06:09:45Z")
This is still not available from lvfs-testing or has someone managed to update to this from LVFS? ---
**Author:** ![Douglas\_Walrath](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/douglas_walrath/32/36119_2.png) [@Douglas\_Walrath](https://community.frame.work/u/Douglas_Walrath)\ **Post date:** [May 3, 2025, 8:45am UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-09-release/68601/14 "2025-05-03T08:45:19Z")
that’s not quite correct because wear isn’t the same across the battery percentage during charging, the higher the battery percentage the higher the wear, charging the battery at 75% provides less wear than charging the battery at 80%, so a bunching of charging cycles near 80% can cause more total wear than discharging to 75% and then charging back up to 80% because in the first scenario the battery spends more time being charged at the higher percentage ---
**Author:** ![Quin\_Chou](https://avatars.discourse-cdn.com/v4/letter/q/cdc98d/32.png) [@Quin\_Chou](https://community.frame.work/u/Quin_Chou)\ **Post date:** [May 3, 2025, 2:31pm UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-09-release/68601/15 "2025-05-03T14:31:02Z")
LVFS is ready for download. ---
**Author:** ![Nathan\_Yuen](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/nathan_yuen/32/23532_2.png) [@Nathan\_Yuen](https://community.frame.work/u/Nathan_Yuen)\ **Post date:** [May 3, 2025, 7:14pm UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-09-release/68601/16 "2025-05-03T19:14:18Z")
Hmm still not seeing it via `fwupdmgr` after enabling `lvfs-testing` ---
**Author:** ![James3](https://avatars.discourse-cdn.com/v4/letter/j/b5e925/32.png) [@James3](https://community.frame.work/u/James3)\ **Post date:** [May 3, 2025, 10:29pm UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-09-release/68601/18 "2025-05-03T22:29:17Z")
You can set the range yourself. `sudo ectool chargecontrol normal ` Where the lower and upper are in integer percent. ---
**Author:** ![Guldoman](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/guldoman/32/18204_2.png) [@Guldoman](https://community.frame.work/u/Guldoman)\ **Post date:** [May 3, 2025, 10:38pm UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-09-release/68601/19 "2025-05-03T22:38:44Z")
Was the ChromeOS charge control support removed? I can’t seem to be able to set the charge limits anymore from Linux using the `cros_charge-control` driver anymore. It was working on 3.08. ---
**Author:** ![dimitris](https://avatars.discourse-cdn.com/v4/letter/d/db5fbb/32.png) [@dimitris](https://community.frame.work/u/dimitris)\ **Post date:** [May 4, 2025, 12:23am UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-09-release/68601/20 "2025-05-04T00:23:28Z")
> **Showed up here after a refresh** > > ```txt > $ fwupdmgr refresh # may need the --force option if you'fe refreshed too recently > Updating lvfs-testing > Downloading… [***************************************] > Updating lvfs > Downloading… [-] > Successfully downloaded new metadata: 3 local devices supported > $ fwupdmgr get-updates > Devices with no available firmware updates: > • SSD 990 PRO 2TB > • TPS DMC Family > • TPS6598X PD#0 > • TPS6598X PD#1 > • USB3.0 Hub > Devices with the latest available firmware version: > • Fingerprint Sensor > • UEFI dbx > Framework Laptop 13 (AMD Ryzen 7040Series) > │ > └─System Firmware: > │ Device ID: 1e4fa9cea0b89e613370cf9657ffa0b6d3f37fec > │ Summary: UEFI System Resource Table device (Updated via capsule-on-disk) > │ Current version: 0.0.3.5 > │ Minimum Version: 0.0.0.1 > │ Vendor: Framework (DMI:INSYDE Corp.) > │ Update State: Success > │ GUID: b5f7dcc1-568c-50f8-a4dd-e39d1f93fda1 > │ Device Flags: • Internal device > │ • Updatable > │ • System requires external power source > │ • Supported on remote server > │ • Needs a reboot after installation > │ • Cryptographic hash verification is available > │ • Device is usable for the duration of the update > │ Device Requests: • Message > │ > ├─Laptop 13 AMD Ryzen 7040 System Update: > │ New version: 0.0.3.9 > │ Remote ID: lvfs-testing > │ Release ID: 111845 > │ Summary: Framework Laptop 13 System Firmware for AMD Ryzen 7040 Mainboards > │ License: Proprietary > │ Size: 36.1 MB > │ Created: 2025-04-22 > │ Urgency: High > │ Tested by Framework: > │ Tested: 2025-04-23 > │ Distribution: fedora 41 (workstation) > │ Old version: 0.0.3.9 > │ Version[fwupd]: 1.9.29 > │ Vendor: Framework > │ Duration: 2 minutes > │ Release Flags: • Trusted metadata > │ • Is upgrade > │ • Tested by trusted vendor > │ Description: > │ This firmware update includes the following changes: > │ > │ • Fixed battery charging limitation cannot work when battery extender function disabled. > │ • Fixed battery charging limit is reset by battery extender reset timer. > │ Checksum: 9a9b6b23623227b1a2b5906030de4a1c08990ef3b57a65df101dab6ea4169b47 > │ > ├─Laptop 13 AMD Ryzen 7040 System Update: > │ New version: 0.0.3.8 > ... > > ``` ---
**Author:** ![Nathan\_Yuen](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/nathan_yuen/32/23532_2.png) [@Nathan\_Yuen](https://community.frame.work/u/Nathan_Yuen)\ **Post date:** [May 4, 2025, 1:56am UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-09-release/68601/21 "2025-05-04T01:56:20Z")
I guess my pull earlier was stale All good now ---
**Author:** ![SCdF](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/scdf/32/20281_2.png) [@SCdF](https://community.frame.work/u/SCdF)\ **Post date:** [May 4, 2025, 6:42am UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-09-release/68601/22 "2025-05-04T06:42:39Z")
Are you able to clarify the expected relationship between the charge limit and the battery extender? Does having a charge limit override and effectively disable the battery extender? ---
**Author:** ![Seesi](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/seesi/32/29629_2.png) [@Seesi](https://community.frame.work/u/Seesi)\ **Post date:** [May 4, 2025, 8:18am UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-09-release/68601/23 "2025-05-04T08:18:58Z")
So update seems stable? I am eager to update but I know it’s still BETA😅 ---
**Author:** ![Douglas\_Walrath](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/douglas_walrath/32/36119_2.png) [@Douglas\_Walrath](https://community.frame.work/u/Douglas_Walrath)\ **Post date:** [May 4, 2025, 9:14am UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-09-release/68601/24 "2025-05-04T09:14:38Z")
the charge limit is the maximum charge % the battery will be allowed to reach, not the minimum, so yes set it to 75% ---
**Author:** ![Douglas\_Walrath](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/douglas_walrath/32/36119_2.png) [@Douglas\_Walrath](https://community.frame.work/u/Douglas_Walrath)\ **Post date:** [May 4, 2025, 9:20am UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-09-release/68601/25 "2025-05-04T09:20:54Z")
how do i get ectool on linux mint? ---
**Author:** ![Kan-Ru\_Chen](https://avatars.discourse-cdn.com/v4/letter/k/c0e974/32.png) [@Kan-Ru\_Chen](https://community.frame.work/u/Kan-Ru_Chen)\ **Post date:** [May 4, 2025, 1:07pm UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-09-release/68601/26 "2025-05-04T13:07:55Z")
Fedora 42 - updated via LVFS-testing to 3.09 Enabled both charging limit and battery extender and set the limit to 80% Everything looks good so far. Charging limit is respected and status shows as charging. [Next page](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-09-release/68601.md?page=2)