hi Brian, coreboot support is extremely hardware specific by nature, so there are no generic platform targets (other than the emulation ones).
In order to use coreboot on your board, you'd first need to ensure that Bootguard (or similar signature checking schemes) are not being used, which would prevent loading unsigned firmware. Then you'd need to dump the hardware config of the device in order to build a board profile (devicetree, GPIO assignments, etc). cbfstool isn't going to recognize a dump of your vendor firmware as it doesn't contain a CBFS (coreboot filesystem). You'll need to use other tools if you need to dump/extract bits from the vendor firmware, though that's not always necessary, given that FSP does most of the heavy lifting and is included as part of the build process for (most) platforms that use it cheers, Matt On Tue, Sep 14, 2021 at 12:42 PM Brian Milliron <brian.milli...@foresite.com> wrote: > > I've run into 2 problems with trying to set up coreboot for an HP > Probook 440 G7. The first is that I don't see this model listed as an > option in the menuconfig. It is a newer Intel Cometlake CPU/chipset and > most of what I see listed as options are much older machines. Is there > a "generic cometlake" config I can try or am I just out of luck on this? > > The 2nd problem is that cbfstool doesn't recognize the bios dump I did > from the mainboard. I get the error "Selected image region is not a > valid CBFS." I'm pretty sure the the dump is valid because I can read > it using the Intel FIT tool or ME_Analyzer. I'm going to need to pull > the various binary blobs out of the current firmware and this is the > only way I know how. Is there another option here? > _______________________________________________ > coreboot mailing list -- coreboot@coreboot.org > To unsubscribe send an email to coreboot-le...@coreboot.org _______________________________________________ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
