Struct LOCK_SPEC 

pub struct LOCK_SPEC;

Once a LOCK bit is written to 1, ACCESSCTRL silently ignores writes from that master. LOCK is writable only by a Secure, Privileged processor or debugger. LOCK bits are only writable when their value is zero. Once set, they can never be cleared, except by a full reset of ACCESSCTRL Setting the LOCK bit does not affect whether an access raises a bus error. Unprivileged writes, or writes from the DMA, will continue to raise bus errors. All other accesses will continue not to.

You can read this register and get lock::R. You can reset, write, write_with_zero this register using lock::W. You can also modify this register. See API.

Trait Implementations

impl RegisterSpec for LOCK_SPEC

type Ux = u32

Raw register type (u8, u16, u32, …).

impl Resettable for LOCK_SPEC

reset() method sets LOCK to value 0x04

const RESET_VALUE: u32 = 4u32

Reset value of the register.

fn reset_value() -> Self::Ux

Reset value of the register.

impl Writable for LOCK_SPEC

write(|w| ..) method takes lock::W writer structure

const ZERO_TO_MODIFY_FIELDS_BITMAP: u32 = 0u32

Specifies the register bits that are not changed if you pass 1 and are changed if you pass 0

const ONE_TO_MODIFY_FIELDS_BITMAP: u32 = 0u32

Specifies the register bits that are not changed if you pass 0 and are changed if you pass 1

type Safety = Unsafe

Is it safe to write any bits to register

impl Readable for LOCK_SPEC

read() method returns lock::R reader structure