Hello Mark,
1. You can skip this step in your instructions. Instead, when running make menuconfig, look in Chipset / ChromeOS and select "Build for ChromeOS". This should cause Depthcharge to appear as a payload option. You can find the reason for this is in depthcharge/Kconfig.name. The "depends on" statement keeps it from being visible until the CHROMEOS condition is met. 2. I would probably keep this step, although I don't know veyron/speedy. You'll see one of the options under Depthcharge, "Use default libpayload config". That may move the build along, but I doubt it has the options you'll need as it works for x86.
Thanks, Marshall
On Wed, Feb 28, 2018 at 3:39 PM, Mark Wylde me@markwylde.co.uk wrote:
Hello
I'm trying to put together a step by step guide of building and flashing coreboot to a Chromebook C201.
If you look at the bugfixes part of my guide here ( https://gist.github.com/markwylde/4061eab71fa1ec7a27c40a87499924c4#bugfixs), you'll see I've added two problems I had with the master branch of coreboot:
- Depthcharge is not a payload. The `payloads/Kconfig` file doesn't have
an option for Depthcharge. However if you add it and run menuconfig, selecting the new payload, everything works great (well apart from issues 2)
- Coreboot/Depthcharge can't find a config file for veyron_speedy because
`payloads/libpayload/configs/config.veyron_speedy` is not present. If I clone `payloads/libpayload/configs/config.veyron` then it works perfectly.
When you run make you are going to get an error message, something like below:
I'm almost certain my "fixes" aren't actually fixes, and I'm just doing something wrong, if you could correct me I'd be so grateful.
Otherwise, if this is correct I'd be more than happy to try and workout submitting a pull request.
Thanks a lot
Mark
-- coreboot mailing list: coreboot@coreboot.org https://mail.coreboot.org/mailman/listinfo/coreboot