aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--book/en/src/by-example/app.md8
-rw-r--r--ui/task-priority-too-high.stderr2
2 files changed, 8 insertions, 2 deletions
diff --git a/book/en/src/by-example/app.md b/book/en/src/by-example/app.md
index 50f2842c..5fd1c250 100644
--- a/book/en/src/by-example/app.md
+++ b/book/en/src/by-example/app.md
@@ -53,6 +53,12 @@ $ cargo run --example init
{{#include ../../../../ci/expected/init.run}}
```
+> **NOTE**: Remember to specify your chosen target device by passing a target
+> triple to cargo (e.g `cargo run --example init --target thumbv7m-none-eabi`) or
+> configure a device to be used by default when building the examples in `.cargo/config.toml`.
+> In this case, we use a Cortex M3 emulated in QEMU so the target is `thumbv7m-none-eabi`.
+> See [`Starting a new project`](./new.md) for more info.
+
## `idle`
A function marked with the `idle` attribute can optionally appear in the
@@ -120,7 +126,7 @@ crate. When the `priority` argument is omitted, the priority is assumed to be
`1`. The `idle` task has a non-configurable static priority of `0`, the lowest priority.
> A higher number means a higher priority in RTIC, which is the opposite from what
-> Cortex-M does in the NVIC peripheral.
+> Cortex-M does in the NVIC peripheral.
> Explicitly, this means that number `10` has a **higher** priority than number `9`.
When several tasks are ready to be executed the one with highest static
diff --git a/ui/task-priority-too-high.stderr b/ui/task-priority-too-high.stderr
index 984d3fac..e0978f71 100644
--- a/ui/task-priority-too-high.stderr
+++ b/ui/task-priority-too-high.stderr
@@ -4,4 +4,4 @@ error[E0080]: evaluation of constant value failed
3 | #[rtic::app(device = lm3s6965)]
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ attempt to compute `8_usize - 9_usize`, which would overflow
|
- = note: this error originates in an attribute macro (in Nightly builds, run with -Z macro-backtrace for more info)
+ = note: this error originates in the attribute macro `rtic::app` (in Nightly builds, run with -Z macro-backtrace for more info)