Skip to content

[rom_ext] Add bl0 boot diagnostics to boot_log#30373

Open
cfrantz wants to merge 1 commit into
lowRISC:earlgrey_1.0.0from
cfrantz:more_boot_log
Open

[rom_ext] Add bl0 boot diagnostics to boot_log#30373
cfrantz wants to merge 1 commit into
lowRISC:earlgrey_1.0.0from
cfrantz:more_boot_log

Conversation

@cfrantz

@cfrantz cfrantz commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

This commit:

  • Fixes the static assertions in boot_log.h to match the new layout.
  • Updates boot_log_unittest.cc to initialize and verify all fields of boot_log_t using memcmp.
  • Updates the E2E test position_owner_slot_b to verify that bl0_failure_reason is correctly populated.
  • Commits the previous changes to boot_log.h, rom_ext.c, boot_test.c, and boot_log.rs that added the bl0_firmware_domain and bl0_failure_reason fields.

TAG=agy
CONV=add60186-d4ca-48b7-b9b8-d777ef5b71f4

@cfrantz cfrantz requested review from korran and moidx June 11, 2026 18:17
@cfrantz cfrantz requested review from a team as code owners June 11, 2026 18:17
@cfrantz cfrantz requested review from timothytrippel and removed request for a team June 11, 2026 18:17
@cfrantz cfrantz force-pushed the more_boot_log branch 2 times, most recently from 7cee181 to 0489875 Compare June 11, 2026 22:14
This commit:
- Fixes the static assertions in boot_log.h to match the new layout.
- Updates boot_log_unittest.cc to initialize and verify all fields of boot_log_t using memcmp.
- Updates the E2E test position_owner_slot_b to verify that bl0_failure_reason is correctly populated.
- Commits the previous changes to boot_log.h, rom_ext.c, boot_test.c, and boot_log.rs that added the bl0_firmware_domain and bl0_failure_reason fields.

TAG=agy
CONV=add60186-d4ca-48b7-b9b8-d777ef5b71f4

Signed-off-by: Chris Frantz <cfrantz@google.com>
@moidx moidx removed the request for review from a team June 13, 2026 01:16
return kErrorRomExtBootFailed;
}
const owner_application_key_t *key = keyring.key[verify_key];
boot_log->bl0_firmware_domain = key->key_domain;

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should bl0_firmware_domain be initialized?

}
const owner_application_key_t *key = keyring.key[verify_key];
boot_log->bl0_firmware_domain = key->key_domain;
boot_log_digest_update(boot_log);

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it make sense to update the digest whenever the bl0_failure_reason is updated?

@moidx moidx requested a review from sasdf June 13, 2026 04:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants