Most likely you will need also this:
select VBOOT_VBNV_CMOS select VBOOT_NO_BOARD_SUPPORT select GBB_FLAG_DISABLE_LID_SHUTDOWN select GBB_FLAG_DISABLE_PD_SOFTWARE_SYNC select GBB_FLAG_DISABLE_EC_SOFTWARE_SYNC select GBB_FLAG_DISABLE_FWMP select RTC select VBOOT_STARTS_IN_ROMSTAGE
Under config VBOOT. And define the CMOS offset for vboot in Kconfig as in the patch linked earlier. AGESA binary typically have to reside under certain offset in the binary, so you have to pass the AGESA name to be added to RO partition only in menuconfig of vboot, since it should probably reside there.
On 13.11.2019 14:37, Jorge Fernandez Monteagudo wrote:
Hi Michal!
Thanks for the info!
Yes, I'm using the amd/bettong mainboard. I've changed the Kconfig adding
config VBOOT select VBOOT_STARTS_IN_ROMSTAGE select VBOOT_NO_BOARD_SUPPORT select VBOOT_MEASURED_BOOT select AMDFW_OUTSIDE_CBFS
config VBOOT_SLOTS_RW_A default y
config FMDFILE string default "src/mainboard/$(CONFIG_MAINBOARD_DIR)/vboot-rwa.fmd" if VBOOT
Now, I get an error processing the CBFS. As you said, I suppose I need to modify the sizes to adapt it to my requirements. Where can I found info about the fmap files? This, and the cmos layout files are unknown areas to me, and I don't know where to begin to modify it.
The error I get is:
Created CBFS (capacity = 5083096 bytes) Created CBFS (capacity = 2031512 bytes) CBFS AGESA CBFS fallback/romstage CBFS fallback/ramstage CBFS cmos_layout.bin CBFS pci1002,9874.rom CBFS fallback/dsdt.aml CBFS fallback/payload CBFS AGESA E: Could not add [3rdparty/blobs/pi/amd/00660F01/FP4/AGESA.bin, 690436 bytes (674 KB)@0x540000]; too big? E: Failed to add '3rdparty/blobs/pi/amd/00660F01/FP4/AGESA.bin' into ROM image. E: Failed while operating on 'FW_MAIN_A' region! E: The image will be left unmodified.
Regards, Jorge _______________________________________________ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-leave@coreboot.org