coreboot VS coreboot-builder-scripts

Why BIOS (did you mean UEFI?) when it runs the best boot loader, which is Coreboot¹. Many users would love to re-flash their bios/uefi for it, if it’s supported.

1: https://www.coreboot.org/

Coreboot is 0.6% C++.

NovaCustom ; some models come with Dasharo a coreboot distribution.

You can also use Mr. Chromebox Script to install Coreboot on your chromebook to get a UEFI BIOS on your Chromebook and then you can go an install either a linux distro or even Windows if you want. It's a pretty straightforward process and also reversable if you want to go back to just using ChromeOS.

Some models are available with Dasharo a [coreboot]https://www.coreboot.org/) distribution.

why no haswell_ult_dmi_registers for broadwell? in https://github.com/coreboot/coreboot/blob/master/util/inteltool/pcie.c

use croshfirmware.sh from https://github.com/coreboot/coreboot/tree/master/util/chromeos

There may be other protections to restrict SPI flash access for security reasons (so you might not be able to flash your custom firmware in the OS), but worst case you can use a HW flasher (or maybe USB flashback). Still, this doesn't address the elephant in the room - platform initialization code might be open-sourced, but that isn't everything. You'll still need to figure out the board-specific stuff (the Super I/O chip, chipset GPIOs, other peripherals, etc.). Using coreboot as an example, Intel provides the Firmware Support Package blob to handle platform initialization. I think AGESA is somewhat similar to this, though Intel publicly releases the binaries for use in coreboot/etc. Thanks to the FSP, coreboot has support for recent Intel chipsets. However, there is only support for two recent consumer boards: the MSI PRO Z690-A WiFi DDR4 and DDR5.

does anyone know what is https://github.com/coreboot/coreboot/blob/b12caef23bc1b29c2e658f2b728cc4beac1e62b9/src/northbridge/intel/haswell/vcu_mailbox.c

Download crosfirmware.sh and run it from command line: bash crosfirmware.sh droid

Have you tried building just coreboot for the w541 yet? I would suggest doing that if you haven't. I need to update it, but this what I used. Due to flaky connections to the chromebook images, I sourced the mrc.bin from skulls. This is the proper way to do it.

You can Skull's build scripts are based on my coreboot-builder-scripts, which does rely on x86 Docker. You can build on coreboot on an RPi but you need to compile crossgcc. I have not done this myself in sometime and the only tutorial I know if the Karl Cordes's x220 tutoial. While the dependencies are outdated the crossgcc build command is likely the same.

I finally got it! Long story short, I used the coreboot-sdk docker image for the toolchain through the great coreboot-builder-scripts repository (it needs a couple adjustments that I've detailed in this other thread: OpenBSD in Thinkpad x220 with Coreboot 4.7.

We can use the https://github.com/Thrilleratplay/coreboot-builder-scripts to use the coreboot-sdk toolchain and compile Coreboot 4.7, however we need to make a couple of adjustments:

Docker images can be built and/or pulled from a repository like hub.docker.com. Here is the link to coreboot-sdk but would suggest looking at other Docker images like the official NextCloud image to get a better sense of how standalone Docker image applications can be configured. If you want a better idea of how to use the coreboot-sdk, I use it in my coreboot-builder-scripts