EmbeddedController

It's crazy, the last time any PRs got merged was back in January 2024 [0]. Seems it has just become a black hole completely ignored by anyone at framework. [0] https://github.com/FrameworkComputer/EmbeddedController/pull...

Ploopy is killing it. The trackpad and knob are also both very very high quality. The open firmware is just so ace, makes these devices so so so much better than everything commercial. The future is open source. Why make life bad for your customers? Why spend so much effort to do so so so much worse than high feature + freedom? QMK or bust. https://ploopy.co/knob/ https://ploopy.co/trackpad/ Keychron and System76 are also on the QMK train with their recent keyboards too. (I'm not 100%, would love to know if each of these can be flashed by users.) Framework is also on the QMK open-source firmware train, for their keyboard + trackpad combo. Also not a new trend for them: their newer laptops I believe all run Zephyr OS for the embedded controller (EC), & are themselves open source too. Before that, the open-source Chromebook EC. I believe i

> So, in theory, could the Framework laptop rival Apple? Yes in theory. Btw it seems that Framework has open sourced their embedded driver firmware source code: - https://frame.work/it/en/blog/open-sourcing-our-firmware - https://github.com/FrameworkComputer/EmbeddedController So again, in theory there could be a much better hardware/software (linux) integration. Not sure if there is anybody actually modding that firmware (would be cool to know).

Experimental and requires closed binary blobs, but Coreboot 24.05 shipped with some Framework 13 support. https://www.phoronix.com/news/Coreboot-24.05-Released https://www.phoronix.com/news/Framework-13-AMD-Coreboot-WIP Really hoping OpenSIL isnt dead in the water & that eventually it really is possible to have open init code for client and server Ryzens both. It's unclear what features are missing versus the binary blobs, and I don't think there's client device support, but at least the repo is around, and gets an occasional small update every couple months. I wish there were more signs of this really getting someplace someday. https://github.com/openSIL/openSIL It is nice that there's open source embedded controller (EC) firmware on the Framework. Would be neat to see users modifying or adding to the EC to interesting ends, or perhaps

No, the architecture of the Framework Laptop 13 is very different. There the keyboard input is handled by the embedded controller: https://github.com/FrameworkComputer/EmbeddedController/blob... On the 16 the keyboard is a USB keyboard that could even be used standalone, without the laptop.

:-D There was someone working on firmware that could remap keys (let me see if I can find a link... Welp, it looks like it can be remapped bios today https://community.frame.work/t/framework-and-open-source/107... and the firmware is open source https://github.com/FrameworkComputer/EmbeddedController) and https://community.frame.work/t/changed-my-keyboard-layout-in... I never did find the post I was thinking of (EDIT: Maybe this one: https://community.frame.work/t/a-qmk-configurable-keyboard/2...)

The FW's embedded controller's firmware has been open-sourced, is on Github, and you can flash your customized version if you wish so: https://github.com/FrameworkComputer/EmbeddedController

Glad to hear that you're enjoying it! On the CPU temperatures, Boost will deliberately and safely let the CPU run up to a maximum of 60W and 100C for a short period of time at the start of heavy load before dropping back to 28W (11th Gen) or 30W (12th Gen). On an open UEFI solution, that is on our long term roadmap, and we're currently hiring for firmware positions to speed up kicking off this work. Edit: Also, our Embedded Controller firmware is open, though that is somewhat orthogonal to UEFI: https://github.com/FrameworkComputer/EmbeddedController

Yep, we absolutely understand and respect Louis and community members' requests for full schematics, and we appreciate the folks who extend understanding as we work through constraints (including Louis as noted in that last video). We're continuing to make as much open as we can, and we're adding to that list as we go: * Mainboard partial schematics, drawings, and pinouts: https://github.com/FrameworkComputer/Mainboard * Expansion Card reference designs: https://github.com/FrameworkComputer/ExpansionCards * Embedded Controller firmware: https://github.com/FrameworkComputer/EmbeddedController On the list of things that we are exploring ways to improve on in the future: * More of the schematics, including of modules beyond the Mainboards. * Moving to open UEFI/BIOS solutions.

We've seen distro preference be too broad to make pre-loading efficient. Instead, we ship DIY Edition with no OS and publish guides for how to install and optimize the most popular distros. Our embedded controller firmware is open (see https://github.com/FrameworkComputer/EmbeddedController), and we're working with some community members on attempting a coreboot port.

Technically you can use the 50 pin header we have for the input system for GPIO, i2c, and USB. The webcam and display headers also have i2c and USB: https://github.com/FrameworkComputer/Mainboard/blob/main/Ele... The GPIO would require EC firmware development, but it is technically possible: https://github.com/FrameworkComputer/EmbeddedController

The i7-1185G7 SKU supports vPro: https://frame.work/products/mainboard?v=FRANFG000C We also have some additional debug support through a header that we've documented here: https://github.com/FrameworkComputer/EmbeddedController

I checked the keyboard debouncing logic [0] and it was fine. Some keyboards from other manufacturers, notably Lenovo Thinkpads, have absurd debouncing algorithms that scramble keys or add delays, so it's good to see Framework has a correct solution. [0]: https://github.com/FrameworkComputer/EmbeddedController/blob...