Anatomy of a Failover coreboot v2 Image
Overview and according values
This is a pictorial view of FAILOVER_SIZE, _ROMBASE, ROM_IMAGE_SIZE, PAYLOAD_SIZE, ROM_SIZE, ROM_SECTION_SIZE, HAVE_FALLBACKBOOT, HAVE_FAILOVERBOOT for Options.lb and Config.lb.
XIP_ROM_BASE and XIP_ROM_SIZE are for MTRR setting during CAR to cache part of the ROM image. Speeds up anything with loops like copies and decompression.
On the timeline
The failover image...
- chooses to use normal or fallback.
- This choice depends on a value which is stored in NVRAM a.k.a CMOS.
- This code is at the moment mainboard specific and can normally be found in cache_as_ram.c or auto.c.
- runs normal or fallback.
Some Errors you might come across and probable solutions
coreboot input file larger than allowed size
./buildrom coreboot.strip coreboot.rom payload 0x70000 0x7f000 coreboot image is 458820 bytes; only 458752 allowed coreboot input file larger than allowed size!
Typically caused by crt0 having a .data segment. Make sure all ROM data is defined as constant.
section .id overlaps section .rom
gcc -m32 -nostdlib -nostartfiles -static -o linuxbios -T ldscript.ld crt0.o /usr/lib64/gcc/x86_64-suse-linux/4.3/../../../../x86_64-suse-linux/bin/ld: section .id [00000000ffffefd2 -> 00000000ffffefef] overlaps section .rom [00000000fffeed83 -> 00000000ffffff5f] /usr/lib64/gcc/x86_64-suse-linux/4.3/../../../../x86_64-suse-linux/bin/ld: linuxbios: section .id lma 0xffffefd2 overlaps previous sections /usr/lib64/gcc/x86_64-suse-linux/4.3/../../../../x86_64-suse-linux/bin/ld: linuxbios: section .reset lma 0xffffeff0 overlaps previous sections collect2: ld returned 1 exit status make: *** [linuxbios] Error 1 make: Leaving directory `/srv/svn/linuxbios-extra/tmp/LinuxBIOSv2-3021/util/abuild/linuxbios-builds/amd_serengeti_cheetah_fam10/fallback' make: *** [fallback/linuxbios.rom] Error 1
Increase the ROM_IMAGE_SIZE of the failing piece. In this case the fallback image.
See also the FAQ for a detailed description of a fix.