99d19c7dcf
I've renamed the channel module for the MPMC as mpmc. There was a previous debate about this, but I feel that the strategy here avoids importing `channel::channel`. The change leaves `signal::Signal`, but I think that's ok. It is all a bit subjective of course. The bottom line for me is that I really like the term mpmc - it means something to me and aligns with broader naming e.g. in Tokio.
53 lines
1.4 KiB
Rust
53 lines
1.4 KiB
Rust
#![no_std]
|
|
#![no_main]
|
|
#![feature(type_alias_impl_trait)]
|
|
|
|
use defmt::unwrap;
|
|
use embassy::blocking_mutex::raw::NoopRawMutex;
|
|
use embassy::channel::mpmc::{Channel, Receiver, Sender};
|
|
use embassy::executor::Spawner;
|
|
use embassy::time::{Duration, Timer};
|
|
use embassy::util::Forever;
|
|
use embassy_nrf::gpio::{AnyPin, Level, Output, OutputDrive, Pin};
|
|
use embassy_nrf::Peripherals;
|
|
|
|
use defmt_rtt as _; // global logger
|
|
use panic_probe as _;
|
|
|
|
enum LedState {
|
|
On,
|
|
Off,
|
|
}
|
|
|
|
static CHANNEL: Forever<Channel<NoopRawMutex, LedState, 1>> = Forever::new();
|
|
|
|
#[embassy::task]
|
|
async fn send_task(sender: Sender<'static, NoopRawMutex, LedState, 1>) {
|
|
loop {
|
|
sender.send(LedState::On).await;
|
|
Timer::after(Duration::from_secs(1)).await;
|
|
sender.send(LedState::Off).await;
|
|
Timer::after(Duration::from_secs(1)).await;
|
|
}
|
|
}
|
|
|
|
#[embassy::task]
|
|
async fn recv_task(led: AnyPin, receiver: Receiver<'static, NoopRawMutex, LedState, 1>) {
|
|
let mut led = Output::new(led, Level::Low, OutputDrive::Standard);
|
|
|
|
loop {
|
|
match receiver.recv().await {
|
|
LedState::On => led.set_high(),
|
|
LedState::Off => led.set_low(),
|
|
}
|
|
}
|
|
}
|
|
|
|
#[embassy::main]
|
|
async fn main(spawner: Spawner, p: Peripherals) {
|
|
let channel = CHANNEL.put(Channel::new());
|
|
|
|
unwrap!(spawner.spawn(send_task(channel.sender())));
|
|
unwrap!(spawner.spawn(recv_task(p.P0_13.degrade(), channel.receiver())));
|
|
}
|