Framework Laptop 13 Ryzen 7040 BIOS 3.18 Release STABLE

Framework Laptop 13
,
1

Highlights

  1. Updated AMD PhoenixPI-FP8-FP7_1.2.0.0e.
  2. Modified the F2 key in the F12 Boot Menu to go to the setup menu instead of the settings menu to allow easier navigation to secure boot settings.
  3. Enhanced the Power On AC behavior, allowing the feature to work correctly without requiring the system to boot into the Operating System at least once for initialization.
  4. Enhanced fan detection logic within the Input Module app.

Note:

  1. Once you update to 3.18, 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.

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.18.exe 91E6A69C848FBCB0E493A215F617124316685F26576C733A571658329F4F45EA

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.18_EFI.zip B5D9E7D0A20C34B308CFE62D27B2B4E9705EDFFBFD693DF0A58A834FD46F9408

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

N/A

Enhancements

N/A

Fixes

  1. Updated AMD PhoenixPI-FP8-FP7_1.2.0.0e.
  2. Modified the F2 key in the F12 Boot Menu to go to the setup menu instead of the settings menu to allow easier navigation to secure boot settings.
  3. Enhanced the Power On AC behavior, allowing the feature to work correctly without requiring the system to boot into the Operating System at least once for initialization.
  4. Enhanced fan detection logic within the Input Module app.

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 Updated?
BIOS 3.18 Updated
EC ec_318_76610 Updated
PD 0.0.1C Same
AMD PI 1.2.0.0e Updated

Reporting Issues

To report issues we have created a public issue tracker on github. GitHub · Where software is built 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.
2 Likes
I want to support Framework, but where to start?
2

I installed it on mine. No difficulties to report besides the usual having to disconnect and reconnect the USB-C monitor to restore the high-speed data channels.

3

battery charging/discharging flipping hast been adressed in this bios version

1 Like
4

Not seeing any major issues yet, the update took quite some time. Will be monitoring to see if the CPU speed lock-ups have been fixed.

1 Like
5

The embedded controller repository needs to be updated with the EC firmware in this release…

2 Likes
6

I updated yesterday and it seems to be working fine for me.

ADDED LATER: I updated from Windows 11 using the .exe file.

7

Just updated and it killed the laptop, won’t boot anymore, the power led flashes some sequence… Edit: looks like white and 12 green, which would indicate that all tests have passed and yet it doesn’t POST.

Was on version 3.0.17, firmware update done from Fedora 43. Ran the update, found the laptop some time later with fans audibly spinning and a black screen, had this happen many times during updates with no issues. Turned it off, turned on again, but it wouldn’t boot. Will have to reach out to support, unless anyone has a suggestion on how to recover.

8

I successfully updated yesterday, but today, after powering on the laptop with my Lenovo Thunderbolt docking station connected, it wouldn’t boot to Windows 11. I just saw a flashing sequence of orange and green LEDs. After disconnecting the docking station and restarting the laptop, it booted up successfully and is now working with the docking station connected.

I’m considering downgrading to version 3.17.

9

I think it is important to not have any devices connected except the power adapter during a firmware update.

1 Like
10

You’re probably referring to Mathias’s case, but in my case I only had the power adapter connected, nothing else

1 Like
11

@Fn1
How long was “some time later” ?

12

~10-15 minutes

13

It might be safer to wait a bit longer next time. e.g. 30 mins.
I guess each BIOS update is updating different bits, so sometimes it is quick, sometimes it takes a lot longer.

14

After the update, I also lost my internal speaker and microphone. I did another shutdown and boot, but experienced the same problems when the docking station was connected. The LED sequence begins about one minute after pressing the power button and looks like this: ggggggggggggogbgbbgg.

After downgrading to 3.17, the mic and speakers returned. I haven’t tried rebooting yet.

The missing speaker occurred with and without the dock. Realtek Audio was completely missing from the Windows Device Manager.

Framework 13 7840u hanging on POST when a mouse is plugged into a daisy-chained USB hub and an unacceptable support experience
15

Blockquote

I don’t think that’s a sound strategy, I left it once like this for an hour and it was the same thing - non responsive - fans blasting full on and nothing on the screen. After powering off and on it was fine. Framework should fix this behaviour rather than relying on community trying to guess what the safe number of minutes may be.

16

It seems to be normal for the fans to bow quite hard during the update.

Presumably the hardware that actually writes the flash memory is not interrupt driven and requires the CPU to continually poll it.

17

Things seem to be running smoothly.

Build Details: 7840u, 64GB RAM (Framework RAM), 990Pro SSD (2TB)

18

If there’s something showing on the screen sure, but if you all you see after it seemingly completes the update is a blank screen and non-responsive keyboard what would you do?

19

If it’s like that for more than about 20 seconds, you’re probably already screwed. But maybe you should wait longer in case it is retraining the RAM for some reason.
(This is from my experience with upgrading with the .exe file on Windows)

20

This has been the case for every upgrade I had from Linux on this laptop, first time it happened I let it sit like that for over an hour thinking it’s still doing something, then finally turned it off and on and it worked fine , same with every sequential update up to this one.

1 Like