diff options
| author | Henrik Tjäder <henrik@tjaders.com> | 2020-01-24 15:34:41 +0000 |
|---|---|---|
| committer | Henrik Tjäder <henrik@tjaders.com> | 2020-01-24 15:34:41 +0000 |
| commit | 1a1a1e21674d136a335d3955e0caf250d6af31eb (patch) | |
| tree | b09fa3e86010e56db5edc438bfd19e0d34acc2a9 | |
| parent | 1e827e24d024e910b44f6cc6db278e4c66a77683 (diff) | |
Reference the correct example
| -rw-r--r-- | book/en/src/by-example/app.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/book/en/src/by-example/app.md b/book/en/src/by-example/app.md index f687194..5cace37 100644 --- a/book/en/src/by-example/app.md +++ b/book/en/src/by-example/app.md @@ -103,7 +103,7 @@ mut` variables are safe to use within a hardware task. ``` ``` console -$ cargo run --example interrupt +$ cargo run --example hardware {{#include ../../../../ci/expected/hardware.run}}``` So far all the RTFM applications we have seen look no different that the @@ -135,7 +135,7 @@ The following example showcases the priority based scheduling of tasks. ``` ``` console -$ cargo run --example interrupt +$ cargo run --example preempt {{#include ../../../../ci/expected/preempt.run}}``` Note that the task `gpiob` does *not* preempt task `gpioc` because its priority |