# \[Resolved\] Embedded Controller Source Updates?

**URL:** <https://community.frame.work/t/resolved-embedded-controller-source-updates/78804>\
**Category:** Creators & Developers\
**Tags:** bios\
**Created:** [December 12, 2025, 4:54am UTC](https://community.frame.work/t/resolved-embedded-controller-source-updates/78804 "2025-12-12T04:54:08Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![ryanpetris](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/ryanpetris/32/6963_2.png) [@ryanpetris](https://community.frame.work/u/ryanpetris)\
**Post date:** [December 12, 2025, 4:54am UTC](https://community.frame.work/t/resolved-embedded-controller-source-updates/78804/1 "2025-12-12T04:54:08Z")

</div>

I happened to notice that the [EmbeddedController git repository](https://github.com/FrameworkComputer/EmbeddedController/) hasn’t been updated since May, and several bios updates have come out since then with EC updates. Is Framework no longer providing the source code for EC firmware?

For instance, the [Framework 16 3.05 bios update](https://community.frame.work/t/framework-laptop-16-ryzen-7040-bios-3-05-release/60735) had EC version ec\_305\_227507, which corresponds to [commit hash 227507](https://github.com/FrameworkComputer/EmbeddedController/commit/227507). However the latest [4.02 bios](https://community.frame.work/t/framework-laptop-16-bios-v4-02-and-driver-v3-01-releases-amd-ryzen-7040-series-stable/77774) has EC version ec\_402\_c8091da, yet the commit hash c8091da is nowhere to be found.

Edit: Looks like it’s been updated. Thank you!

---

<div class="post-metadata">

**Author:** ![Conor](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/conor/32/29835_2.png) [@Conor](https://community.frame.work/u/Conor)\
**Post date:** [December 12, 2025, 11:31pm UTC](https://community.frame.work/t/resolved-embedded-controller-source-updates/78804/2 "2025-12-12T23:31:34Z")

</div>

Tagging @Daniel_Schaefer as he looks to be a significant contributor to the EC repo.

I’ve seen a few people ask about this in separate threads, so it may be a helpful answer.

---

<div class="post-metadata">

**Author:** ![James3](https://avatars.discourse-cdn.com/v4/letter/j/b5e925/32.png) [@James3](https://community.frame.work/u/James3)\
**Post date:** [December 13, 2025, 10:02am UTC](https://community.frame.work/t/resolved-embedded-controller-source-updates/78804/3 "2025-12-13T10:02:55Z")

</div>

FW don’t seem to be answering questions about this. They answer most other questions about bios releases except this one.  
I have made modifications to my FW16 7840HS that make it behave in a more stable fashion. Some others are also using my changes, as it removes stutter problems while gaming.  
I am stuck on BIOS 3.05 because FW have not updated the EC repo.  
I am waiting impatiently for them to update the repo.  
Being that i was instrumental to highlighting EC firmware bugs that were damaging batteries, i think there is considerable benefit to FW by continued open source firmware.  
There are still major bugs in the EC firmware. E.g. stuck at 550Mhz and problems like that. I can fix those sorts of bugs, but not without the repo updated to the latest by FW.

---

<div class="post-metadata">

**Author:** ![Guest68](https://avatars.discourse-cdn.com/v4/letter/g/a88e4f/32.png) [@Guest68](https://community.frame.work/u/Guest68)\
**Post date:** [December 14, 2025, 7:38am UTC](https://community.frame.work/t/resolved-embedded-controller-source-updates/78804/4 "2025-12-14T07:38:45Z")

</div>

Soon, apparently. Disappointing that it’s been so long after releases without a source update though.

> [@James3](#):
>
> FW don’t seem to be answering questions about this. They answer most other questions about bios releases except this one.

See here:

> [@Framework Laptop 13 Ryzen 7040 BIOS 3.17 Release STABLE](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-17-release-stable/78216/12):
>
> I will begin working on the release process by the end of this week, immediately following the stable release.

---

<div class="post-metadata">

**Author:** ![ryanpetris](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/ryanpetris/32/6963_2.png) [@ryanpetris](https://community.frame.work/u/ryanpetris)\
**Post date:** [December 14, 2025, 12:42pm UTC](https://community.frame.work/t/resolved-embedded-controller-source-updates/78804/5 "2025-12-14T12:42:58Z")

</div>

I see, well good that they plan on releasing it, however as you are I’m still disappointed it’s taking this long.

If Framework truly intends to keep the EC open source though then what I’d like to see is for development to happen in the open, even if features aren’t ready yet. It should be common knowledge that running untagged/unreleased code could have dire consequences especially on embedded systems like an EC and so any concern of not wanting people to run unfinished code shouldn’t be. Additionally, I’m pretty sure manually flashing non-official EC releases voids the warranty anyway (I could be wrong but I remember reading that somewhere) so I personally don’t see the harm in releasing it early.

The only thing I can think of why they wouldn’t is hints at new releases or features they don’t want public yet, but those can be held back in unpublished branches while still releasing regular updates for everything else…

Anyway, I hope it’s released soon, not because I want to fiddle with it myself, mainly for the principal of it.

---

<div class="post-metadata">

**Author:** ![James3](https://avatars.discourse-cdn.com/v4/letter/j/b5e925/32.png) [@James3](https://community.frame.work/u/James3)\
**Post date:** [December 20, 2025, 1:31pm UTC](https://community.frame.work/t/resolved-embedded-controller-source-updates/78804/6 "2025-12-20T13:31:47Z")

</div>

Is the latest EC firmware here for lotus and azalea (FW13 AMD and FW16 AMD 7040):  
New Branch: fwk-tulip-29169

It mentions “lotus” and “azalea” so, maybe it replaces the branch lotus-azalea-19573 ?

---

<div class="post-metadata">

**Author:** ![ryanpetris](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/ryanpetris/32/6963_2.png) [@ryanpetris](https://community.frame.work/u/ryanpetris)\
**Post date:** [December 21, 2025, 1:22pm UTC](https://community.frame.work/t/resolved-embedded-controller-source-updates/78804/7 "2025-12-21T13:22:52Z")

</div>

Looks like this was updated a few days ago! Thank you!!

---

<div class="post-metadata">

**Author:** ![ryanpetris](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/ryanpetris/32/6963_2.png) [@ryanpetris](https://community.frame.work/u/ryanpetris)\
**Post date:** [December 21, 2025, 1:29pm UTC](https://community.frame.work/t/resolved-embedded-controller-source-updates/78804/8 "2025-12-21T13:29:43Z")

</div>

> [@James3](#):
>
> Is the latest EC firmware here for lotus and azalea (FW13 AMD and FW16 AMD 7040):  
> New Branch: fwk-tulip-29169
> 
> It mentions “lotus” and “azalea” so, maybe it replaces the branch lotus-azalea-19573 ?

The text at the end of the EC firmware version is the commit hash, which you can use to lookup the exact commit in GitHub. For instance the 4.02 bios for the 7040 16 inch has ec version `ec_402_c8091da`, and so [this](https://github.com/FrameworkComputer/EmbeddedController/commit/c8091da) would be the commit it corresponds to. That one does indeed exist in the `fwk-tulip-29169` branch. The commit/branch for the 13 inch should be able to be found similarly.

---

<div class="post-metadata">

**Author:** ![James3](https://avatars.discourse-cdn.com/v4/letter/j/b5e925/32.png) [@James3](https://community.frame.work/u/James3)\
**Post date:** [December 21, 2025, 4:12pm UTC](https://community.frame.work/t/resolved-embedded-controller-source-updates/78804/9 "2025-12-21T16:12:03Z")

</div>

Did you get fwk-tulip-29169 to compile? It won’t compile for me.

---

<div class="post-metadata">

**Author:** ![ryanpetris](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/ryanpetris/32/6963_2.png) [@ryanpetris](https://community.frame.work/u/ryanpetris)\
**Post date:** [December 21, 2025, 5:01pm UTC](https://community.frame.work/t/resolved-embedded-controller-source-updates/78804/10 "2025-12-21T17:01:52Z")

</div>

I haven’t tried to compile it; I merely wanted the source code available. I’d imagine though you could follow the same steps that are in the github workflow though: [EmbeddedController/.github/workflows/zephyr-build.yml at fwk-tulip-29169 · FrameworkComputer/EmbeddedController · GitHub](https://github.com/FrameworkComputer/EmbeddedController/blob/fwk-tulip-29169/.github/workflows/zephyr-build.yml)
