[coreboot] Burn 2MB coreboot.rom on 8MB flash chip

Nico Huber nico.h at gmx.de
Wed Sep 26 17:28:25 CEST 2018


On 9/26/18 9:19 AM, Jose Trujillo via coreboot wrote:
> No, don't change it, you change the size of coreboot only if during the
> building process "make" complain that there is not enough space but in
> your case your build was already successful leave it like that.

this advice seems very weird to me. I'm not experienced with Bay Trail.
But unless there is a bug in the Bay Trail code, you should always set
the correct ROM_SIZE (to the full flash chip size). Otherwise you may
introduce bugs in code that relies on this setting (e.g. saving the
MRC cache might fail and so would S3 resume).

CBFS_SIZE however is the setting to adjust according to your needs. It
should be at most the size of the BIOS region.

> In the rare circumstance that more space is required you can increase
> coreboot size to 4MB and istill will fit into your system 5MB of space
> available.
> "ifdtool" will inject coreboot in the top of the BYT_orig.bin and save
> as BYT_orig.bin.new that you can flash to your system.

I assume this doesn't work oob if you set ROM_SIZE correctly. But it is
unnecessary to craft a single file by hand. You can either only flash
the BIOS region (recommended) or add the other regions in coreboot's
config (HAVE_{IFD,ME,GBE}_BIN).


More information about the coreboot mailing list