mirror/rtic
1
0
Fork 0
mirror of https://github.com/rtic-rs/rtic.git synced 2024-11-25 21:19:35 +01:00
Code Issues Projects Releases Packages Wiki Activity

Fix #699

Browse source
This commit is contained in:
datdenkikniet 2023-04-22 19:54:42 +02:00
parent d22faec870
commit ed465b0c3b
2 changed files with 17 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
book/en/src/by-example/channel.md
View file

@ -1,6 +1,6 @@
# Communication over channels. # Communication over channels.
Channels can be used to communicate data between running *software* tasks. The channel is essentially a wait queue, allowing tasks with multiple producers and a single receiver. A channel is constructed in the `init` task and backed by statically allocated memory. Send and receive endpoints are distributed to *software* tasks: Channels can be used to communicate data between running tasks. The channel is essentially a wait queue, allowing tasks with multiple producers and a single receiver. A channel is constructed in the `init` task and backed by statically allocated memory. Send and receive endpoints are distributed to *software* tasks:
``` rust ``` rust
... ...
@ -16,6 +16,8 @@ const CAPACITY: usize = 5;
In this case the channel holds data of `u32` type with a capacity of 5 elements. In this case the channel holds data of `u32` type with a capacity of 5 elements.
Channels can also be used from *hardware* tasks, but only in a non-`async` manner using the [Try API](#try-api).
## Sending data ## Sending data
The `send` method post a message on the channel as shown below: The `send` method post a message on the channel as shown below:
@ -107,11 +109,11 @@ $ cargo run --target thumbv7m-none-eabi --example async-channel-no-receiver --fe
{{#include ../../../../rtic/ci/expected/async-channel-no-receiver.run}} {{#include ../../../../rtic/ci/expected/async-channel-no-receiver.run}}
``` ```
## Try API ## Try API
In cases you wish the sender to proceed even in case the channel is full. To that end, a `try_send` API is provided. Using the Try API, you can send or receive data from or to a channel without requiring that the operation succeeds, and in non-`async` contexts.
This API is exposed through `Receiver::try_recv` and `Sender::try_send`.
``` rust ``` rust
{{#include ../../../../rtic/examples/async-channel-try.rs}} {{#include ../../../../rtic/examples/async-channel-try.rs}}

13
rtic/examples/async-channel-try.rs
View file

@ -18,7 +18,9 @@ mod app {
struct Shared {} struct Shared {}
#[local] #[local]
struct Local {} struct Local {
sender: Sender<'static, u32, CAPACITY>,
}
const CAPACITY: usize = 1; const CAPACITY: usize = 1;
#[init] #[init]
@ -28,7 +30,7 @@ mod app {
receiver::spawn(r).unwrap(); receiver::spawn(r).unwrap();
sender1::spawn(s.clone()).unwrap(); sender1::spawn(s.clone()).unwrap();
(Shared {}, Local {}) (Shared {}, Local { sender: s.clone() })
} }
#[task] #[task]
@ -45,4 +47,11 @@ mod app {
hprintln!("Sender 1 try sending: 2 {:?}", sender.try_send(2)); hprintln!("Sender 1 try sending: 2 {:?}", sender.try_send(2));
debug::exit(debug::EXIT_SUCCESS); // Exit QEMU simulator debug::exit(debug::EXIT_SUCCESS); // Exit QEMU simulator
} }
// This interrupt is never triggered, but is used to demonstrate that
// one can (try to) send data into a channel from a hardware task.
#[task(binds = GPIOA, local = [sender])]
fn hw_task(cx: hw_task::Context) {
cx.local.sender.try_send(3).ok();
}
} }