3 releases
0.1.2 | Apr 2, 2019 |
---|---|
0.1.1 | Apr 2, 2019 |
0.1.0 | Apr 2, 2019 |
#1107 in Embedded development
16KB
110 lines
Shared
A macro for safely sharing data between application and interrupt context on cortex-m systems
NOTE: This code is still an early work in progress!
What it looks like now
use nrf52832_pac::Interrupt;
use bare_metal;
use cortex_m;
// Tuples are of the format:
// (VARIABLE_NAME, VARIABLE_TYPE, CORRESPONDING_INTERRUPT),
shared!(
(RADIO_PKTS, usize, Interrupt::RADIO),
(WALL_CLOCK, usize, Interrupt::RTC0),
);
#[entry]
fn main() {
// Using a `shared` data item in non-interrupt context
// requires a token. This is a singleton, sort of like
// the peripherals from a peripheral access crate
let mut token = RADIO_PKTS::set_initial(27).unwrap();
// You access the data from within a closure. The interrupt
// this data is shared with is disabled for the duration of
// the closure. Other interrupts may still occur.
token.modify_app_context(|y| {
*y -= 1;
y
}).unwrap();
}
#[interrupt]
fn RADIO() {
// Within an interrupt, access is only granted if it matches
// the declared interrupt. Inside the `RADIO` interrupt here,
// only `RADIO_PKTS` is accessible.
//
// Access from within an interrupt doesn't require a token.
RADIO_PKTS::modify_int_context(|x| {
*x += 1;
x
}).unwrap();
}
#[interrupt]
fn RTC0() {
// If `set_initial` was never called, then all attempts to
// access will return an `Err`. This code would panic at
// runtime!
BAZ::modify_int_context(|x| {
*x += 1;
x
}).unwrap();
}
The original idea
The following is the desired end goal of this project. We're not there yet.
Stage 1 - Moving data to interrupts
use nrf52832_pac::Interrupt;
use something::Queue;
// Done at global scope, only specify types
cmim!(
Interrupt::RADIO: bool,
Interrupt::TIMER0: u128,
Interrupt::UARTE0_UARTE: Queue::Producer,
);
fn main() {
let (prod, cons) = Queue::new().split();
// Sets the value described in `cmim!()`.
// This is a "move" operation.
// If the interrupt is currently active, an Error is returned.
cmim_set!(
Interrupt::UARTE0_UARTE,
prod
).unwrap();
NVIC::enable(Interrupt::UARTE0_UARTE);
loop {
let _ = cons.pop();
// ..
}
}
#[interrupt]
fn UARTE0_UARTE() {
// Gets a mutable reference to the value described in `cmim!()`
// This is a "borrow" operation.
// This checks the currently active interrupt. If Interrupt::UARTE0_UARTE is not active, an error is returned
// There is no other mutex.
let data: &mut Producer = cmim_get!(Interrupt::UARTE0_UARTE).unwrap();
data.push(0x00);
}
Stage 2 - Sharing data with a single interrupt
use nrf52832_pac::Interrupt;
// Done at global scope, only specify types
cmim!(
Interrupt::RADIO: bool,
Interrupt::TIMER0: u128,
Interrupt::UARTE0_UARTE: bbqueue::Producer,
);
fn main() {
// Same as above for setting, Interrupt must be disabled
cmim_set!(
Interrupt::RADIO,
false
).unwrap();
NVIC::enable(Interrupt::RADIO);
loop {
// Access the data in a critical section. Radio is disabled during the closure
// This can only be called from non-interrupt context. If ANY interrupt is active,
// an error is returned. This prevents higher prio interrupts messing with the data
let data_copy = cmim_borrow!(
Interrupt::RADIO,
|data: &mut bool| {
// trigger some flag
*data = true;
}
).unwrap();
}
}
#[interrupt]
fn RADIO() {
// Gets a mutable reference to the value described in `cmim!()`
// This is a "borrow" operation.
// This checks the currently active interrupt. If Interrupt::RADIO is not active, an error is returned
// There is no other mutex.
let data: &mut bool = cmim_get!(Interrupt::RADIO).unwrap();
if *data {
// ...
}
}
Stage 3 - Sharing data between interrupts
I have no idea how to do this without the possibility of deadlock. Maybe specify multiple interrupts in cmim!()
, and critical section all of them at once? Maybe do priority elevation like RTFM?
Dependencies
~1MB
~12K SLoC