CBFS: Automate ROM image layout and remove hardcoded offsets
Non-x86 boards currently need to hardcode the position of their CBFS
master header in a Kconfig. This is very brittle because it is usually
put in between the bootblock and the first CBFS entry, without any
checks to guarantee that it won't overlap either of those. It is not fun
to debug random failures that move and disappear with tiny alignment
changes because someone decided to write "ORBC1112" over some part of
your data section (in a way that is not visible in the symbolized .elf
binaries, only in the final image). This patch seeks to prevent those
issues and reduce the need for manual configuration by making the image
layout a completely automated part of cbfstool.
Since automated placement of the CBFS header means we can no longer
hardcode its position into coreboot, this patch takes the existing x86
solution of placing a pointer to the header at the very end of the
CBFS-managed section of the ROM and generalizes it to all architectures.
This is now even possible with the read-only/read-write split in
ChromeOS, since coreboot knows how large that section is from the
CBFS_SIZE Kconfig (which is by default equal to ROM_SIZE, but can be
changed on systems that place other data next to coreboot/CBFS in ROM).
Also adds a feature to cbfstool that makes the -B (bootblock file name)
argument on image creation optional, since we have recently found valid
use cases for CBFS images that are not the first boot medium of the
device (instead opened by an earlier bootloader that can already
interpret CBFS) and therefore don't really need a bootblock.
BRANCH=None
BUG=None
TEST=Built and booted on Veyron_Pinky, Nyan_Blaze and Falco.
Change-Id: Ib715bb8db258e602991b34f994750a2d3e2d5adf
Signed-off-by: Patrick Georgi <pgeorgi@chromium.org>
Original-Commit-Id: e9879c0fbd57f105254c54bacb3e592acdcad35c
Original-Change-Id: Ifcc755326832755cfbccd6f0a12104cba28a20af
Original-Signed-off-by: Julius Werner <jwerner@chromium.org>
Original-Reviewed-on: https://chromium-review.googlesource.com/229975
Reviewed-on: http://review.coreboot.org/9620
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
diff --git a/util/cbfstool/cbfs_image.c b/util/cbfstool/cbfs_image.c
index 1f60d68..0230d80 100644
--- a/util/cbfstool/cbfs_image.c
+++ b/util/cbfstool/cbfs_image.c
@@ -66,13 +66,6 @@
{0, NULL},
};
-static uint32_t align_up(uint32_t value, uint32_t align)
-{
- if (value % align)
- value += align - (value % align);
- return value;
-}
-
static const char *lookup_name_by_type(const struct typedesc_t *desc, uint32_t type,
const char *default_value)
{
@@ -180,6 +173,7 @@
{
struct cbfs_header header;
struct cbfs_file *entry;
+ int32_t *rel_offset;
uint32_t cbfs_len;
size_t entry_header_len;
void *header_loc;
@@ -207,9 +201,6 @@
"header=0x%x, entries_offset=0x%x\n",
bootblock_offset, header_offset, entries_offset);
- if (align == 0)
- align = 64; // default align size.
-
// Prepare bootblock
if (bootblock_offset + bootblock->size > size) {
ERROR("Bootblock (0x%x+0x%zx) exceed ROM size (0x%zx)\n",
@@ -226,7 +217,7 @@
bootblock->size);
// Prepare header
- if (header_offset + sizeof(header) > size) {
+ if (header_offset + sizeof(header) > size - sizeof(int32_t)) {
ERROR("Header (0x%x+0x%zx) exceed ROM size (0x%zx)\n",
header_offset, sizeof(header), size);
return -1;
@@ -242,6 +233,14 @@
header_loc = (image->buffer.data + header_offset);
cbfs_put_header(header_loc, image->header);
+ // The last 4 byte of the image contain the relative offset from the end
+ // of the image to the master header as a 32-bit signed integer. x86
+ // relies on this also being its (memory-mapped, top-aligned) absolute
+ // 32-bit address by virtue of how two's complement numbers work.
+ assert(size % sizeof(int32_t) == 0);
+ rel_offset = (int32_t *)(image->buffer.data + size - sizeof(int32_t));
+ *rel_offset = header_offset - size;
+
// Prepare entries
if (align_up(entries_offset, align) != entries_offset) {
ERROR("Offset (0x%x) must be aligned to 0x%x.\n",
@@ -256,8 +255,8 @@
}
entry = (struct cbfs_file *)(image->buffer.data + entries_offset);
// To calculate available length, find
- // e = min(bootblock, header, size) where e > entries_offset.
- cbfs_len = size;
+ // e = min(bootblock, header, rel_offset) where e > entries_offset.
+ cbfs_len = size - sizeof(int32_t);
if (bootblock_offset > entries_offset && bootblock_offset < cbfs_len)
cbfs_len = bootblock_offset;
if (header_offset > entries_offset && header_offset < cbfs_len)
@@ -772,17 +771,21 @@
{
size_t offset;
int found = 0;
- uint32_t x86sig;
+ int32_t rel_offset;
struct cbfs_header *header, *result = NULL;
- // Try x86 style (check signature in bottom) header first.
- x86sig = *(uint32_t *)(data + size - sizeof(uint32_t));
- offset = (x86sig + (uint32_t)size);
- DEBUG("x86sig: 0x%x, offset: 0x%zx\n", x86sig, offset);
+ // Try finding relative offset of master header at end of file first.
+ rel_offset = *(int32_t *)(data + size - sizeof(int32_t));
+ offset = size + rel_offset;
+ DEBUG("relative offset: %#zx(-%#zx), offset: %#zx\n",
+ (size_t)rel_offset, (size_t)-rel_offset, offset);
if (offset >= size - sizeof(*header) ||
ntohl(((struct cbfs_header *)(data + offset))->magic) !=
- CBFS_HEADER_MAGIC)
+ CBFS_HEADER_MAGIC) {
+ // Some use cases append non-CBFS data to the end of the ROM.
+ DEBUG("relative offset seems wrong, scanning whole image...\n");
offset = 0;
+ }
for (; offset + sizeof(*header) < size; offset++) {
header = (struct cbfs_header *)(data + offset);
@@ -793,14 +796,15 @@
// Probably not a real CBFS header?
continue;
}
- found++;
- result = header;
+ if (!found++)
+ result = header;
}
- if (found > 1) {
- ERROR("multiple (%d) CBFS headers found!\n",
+ if (found > 1)
+ // Top-aligned images usually have a working relative offset
+ // field, so this is more likely to happen on bottom-aligned
+ // ones (where the first header is the "outermost" one)
+ WARN("Multiple (%d) CBFS headers found, using the first one.\n",
found);
- result = NULL;
- }
return result;
}