make application slot range explicit

also start tracking application slot usage in dabao target
This commit is contained in:
bunnie 2026-06-08 23:47:19 +08:00
parent b8f3aad1d9
commit 509bf08c0a
3 changed files with 14 additions and 0 deletions

View file

@ -134,6 +134,7 @@ pub const THE_FLAG_1: SlotIndex = SlotIndex::Data(260, PartitionAccess::Fw0, RwP
// NOTE: COLLATERAL is from 261..265, but it is in the "common" page
// [384..=1919] are unused and available for third party use
pub const APPLICATION: SlotIndex = crate::offsets::APPLICATION;
pub const NUISANCE_KEYS_1: SlotIndex =
SlotIndex::DataRange(1920..2048, PartitionAccess::Fw0, RwPerms::ReadWrite);

View file

@ -300,3 +300,6 @@ pub const CLOCK_SCRAMBLE_PARAMS: SlotIndex = SlotIndex::Data(272, PartitionAcces
// - "end" bits [47:40] == 0x08
//
// Furthermore, IFR slot 0x14, bits [127:120] should have 0x3a in it to enforce write disable on boot0
/// Application slots are available to end users for use, and not reserved for OS or security
pub const APPLICATION: SlotIndex = SlotIndex::DataRange(384..1920, PartitionAccess::Open, RwPerms::ReadWrite);

View file

@ -54,3 +54,13 @@ pub use crate::baosec::{
pub const KEY_SLOTS: [SlotIndex; 6] =
[THE_FLAG_1, ROOT_SEED, RMA_KEY, NUISANCE_KEYS_0, NUISANCE_KEYS_1, CHAFF_KEYS];
// [384..=1919] are unused and available for third party use
pub const APPLICATION: SlotIndex = crate::offsets::APPLICATION;
// offsets into the application slot range for storing BIO config
pub const APP_BIO_CLK_INDEX: usize = 0;
pub const APP_BIO_PINS_INDEX: usize = 1;
pub const APP_BIO_CODE_VALID: usize = 2;
// total length is 0xf00 = 120 slots
pub const APP_BIO_CODE_INDICES: core::ops::Range<usize> = 3..123;