Type Alias VeeRChip

pub type VeeRChip = VeeR<'static, VeeRDefaultPeripherals>;

Aliased Type

struct VeeRChip { /* private fields */ }

Implementations

impl<'a, I> VeeR<'a, I>

where I: InterruptService + 'a,

pub unsafe fn new( pic_interrupt_service: &'a I, mtimer: &'static Clint<'_, Freq32KHz>, ) -> VeeR<'a, I>

Safety

Accesses memory-mapped registers.

pub fn enable_pic_interrupts(&self)

Trait Implementations

impl<'a, I> Chip for VeeR<'a, I>

where I: InterruptService + 'a,

type MPU = PMPUserMPU<4, SimplePMP<8>>

The particular Memory Protection Unit (MPU) for this chip.

type UserspaceKernelBoundary = SysCall

The implementation of the interface between userspace and the kernel for this specific chip. Likely this is architecture specific, but individual chips may have various custom requirements.

fn mpu(&self) -> &<VeeR<'a, I> as Chip>::MPU

Returns a reference to the implementation for the MPU on this chip.

fn userspace_kernel_boundary(&self) -> &SysCall

Returns a reference to the implementation for the interface between userspace and kernelspace.

fn service_pending_interrupts(&self)

The kernel calls this function to tell the chip to check for all pending interrupts and to correctly dispatch them to the peripheral drivers for the chip.

fn has_pending_interrupts(&self) -> bool

Ask the chip to check if there are any pending interrupts.

fn sleep(&self)

Called when there is nothing left for the chip to do and it should enter a low power sleep state. This low power sleep state should allow interrupts to still be active so that the next interrupt event wakes the chip and resumes the scheduler.

unsafe fn atomic<F, R>(&self, f: F) -> R

where F: FnOnce() -> R,

Run a function in an atomic state, which means that interrupts are disabled so that an interrupt will not fire during the passed in function’s execution.

unsafe fn print_state(&self, writer: &mut dyn Write)

Print out chip state (system registers) to a supplied writer. This does not print out the execution context (data registers), as this depends on how they are stored; that is implemented by syscall::UserspaceKernelBoundary::print_context. This also does not print out a process memory state, that is implemented by process::Process::print_memory_map. The MPU state is printed by the MPU’s implementation of the Display trait. Used by panic.