#[repr(transparent)]pub struct PageLock1(pub u32);
Expand description
Lock configuration MSBs for page 63 (rows 0xfc0 through 0xfff). Locks are stored with 3-way majority vote encoding, so that bits can be set independently. This OTP location is always readable, and is write-protected by its own permissions.
Tuple Fields§
§0: u32
Implementations§
Source§impl PageLock1
impl PageLock1
Sourcepub const fn lock_s(&self) -> PageLock
pub const fn lock_s(&self) -> PageLock
Lock state for Secure accesses to this page. Thermometer-coded, so lock state can be advanced permanently from any state to any less-permissive state by programming OTP. Software can also advance the lock state temporarily (until next OTP reset) using the SW_LOCKx registers.
Sourcepub fn set_lock_s(&mut self, val: PageLock)
pub fn set_lock_s(&mut self, val: PageLock)
Lock state for Secure accesses to this page. Thermometer-coded, so lock state can be advanced permanently from any state to any less-permissive state by programming OTP. Software can also advance the lock state temporarily (until next OTP reset) using the SW_LOCKx registers.
Sourcepub const fn lock_ns(&self) -> PageLock
pub const fn lock_ns(&self) -> PageLock
Lock state for Non-secure accesses to this page. Thermometer-coded, so lock state can be advanced permanently from any state to any less-permissive state by programming OTP. Software can also advance the lock state temporarily (until next OTP reset) using the SW_LOCKx registers. Note that READ_WRITE and READ_ONLY are equivalent in hardware, as the SBPI programming interface is not accessible to Non-secure software. However, Secure software may check these bits to apply write permissions to a Non-secure OTP programming API.
Sourcepub fn set_lock_ns(&mut self, val: PageLock)
pub fn set_lock_ns(&mut self, val: PageLock)
Lock state for Non-secure accesses to this page. Thermometer-coded, so lock state can be advanced permanently from any state to any less-permissive state by programming OTP. Software can also advance the lock state temporarily (until next OTP reset) using the SW_LOCKx registers. Note that READ_WRITE and READ_ONLY are equivalent in hardware, as the SBPI programming interface is not accessible to Non-secure software. However, Secure software may check these bits to apply write permissions to a Non-secure OTP programming API.
Sourcepub const fn lock_bl(&self) -> PageLock
pub const fn lock_bl(&self) -> PageLock
Dummy lock bits reserved for bootloaders (including the RP2350 USB bootloader) to store their own OTP access permissions. No hardware effect, and no corresponding SW_LOCKx registers.
Sourcepub fn set_lock_bl(&mut self, val: PageLock)
pub fn set_lock_bl(&mut self, val: PageLock)
Dummy lock bits reserved for bootloaders (including the RP2350 USB bootloader) to store their own OTP access permissions. No hardware effect, and no corresponding SW_LOCKx registers.