Framework-Laptop-13 VS EmbeddedController

You definitely could. All the details are available on the FrameworkComputer github org and you could either use what they have as a basis for a chassis or design your own custom chassis that fits the framework parts.

https://github.com/FrameworkComputer/Framework-Laptop-13

You can also buy mainboards[1] and expansion cards[2] (usb-c, hdmi etc.) from the same website. Depending on how beefy of a computer you want there are mainboards from 299 USD to 700 USD. So for ~500 USD you can get a very powerful tiny-ish computer. It obviously won't have the IO capabilities of pi-like hobby boards but it'll function great as a thin client for running linux / home automation stuff.

[1]: https://frame.work/marketplace/mainboards

Framework themselves do sell older mainboards at a discount.

So if this isn't the EC firmware flash, where is that? I peeked under all the components on the top side of the board that I could (fan, etc.) but couldn't find any other flash chips. I tried looking at the schematic, and while it mentions two flash ROMs, it doesn't mention where to find them. Reluctantly, I took out the mainboard and checked the under-side.

You can also buy a framework mainboard. It’s basically the motherboard of a laptop without screen, keyboard and trackpad.

And I don't mean ideologically, though that's good too. Their top end AMD Ryzen 7 main board upgrade kit is $700 and that's what you'd pay for a mid range business laptop. Add $40 for a mainboard case which basically gets you a new computer and it's not a bad deal at all.

What I don't get about your comments is that you're opposing upgradeability and repairability, when it's really just the same concept stretched further: instead of there being one spare part for anything that can break in a given model, you have multiple tiers for parts that effectively make the laptop more of a modular series than a single model, like Framework does. And to answer your question from a further comment, you can indeed upgrade to a later gen mainboard, in fact you can even go AMD.

If you are still looking for a place to start you should check out framework's github. They have a bunch of 3d models already designed. You can modify them and framework even has a process to submit possible upgrades for their designs. https://github.com/FrameworkComputer/Framework-Laptop-13

git clone --depth 1 https://github.com/FrameworkComputer/EmbeddedController cd EmbeddedController make utils sudo ./build/bds/util/ectool #USE AT YOUR OWN RISK - YOU CAN BRICK YOUR LAPTOP

When I was getting ready to flash again, I noticed an issue about the compiler version used to build the firmware binary. I followed the advice, but more importantly I noticed that the issue has been recently fixed, and in the resolution, the maintainer says "Next release (hx20 3.19, hx30 3.07) will include them". It reminded me of something crucial: the Framework EC firmware source code repo doesn't have any particular indication of its level of stability at any given commit. Which commits could be considered fully tested releases? What if the head of the branch introduces a bug that they're working on fixing?

The EC code on the normal Framework devices is already based on the Chrome EC code anyway. https://github.com/FrameworkComputer/EmbeddedController

EC firmware is open sourced by framework: https://github.com/FrameworkComputer/EmbeddedController

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.

I tried the pre-compiled `ectool` from the TamtamHero's repository as we and comiled the EmeddedController from Framework (from this repository). Both give the same error message.

Great reminder that (as of right now) we're far removed from hardware that is 100% free (as in freedom). The closest we've got is probably provided by Raptor Computing Systems. However not everyone in the world is privileged enough to own such devices unfortunately. And I haven't dabbled into other possible mishaps that come with using such devices. The lack of "free-hardware" is a major concern though. I'd argue that there aren't enough reasons to be optimistic about this as of right now. Therefore our best bet is to not let good be the enemy of perfect; light at the end of the tunnel...

As far as I'm aware the only way to manually change the fan speed is using `ectool` from https://github.com/FrameworkComputer/EmbeddedController/

We open sourced our Embedded Controller (EC) firmware and made it available on GitHub for you to modify if you wish.