diff options
| author | bors[bot] <26634292+bors[bot]@users.noreply.github.com> | 2020-10-02 11:17:56 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-10-02 11:17:56 +0000 |
| commit | 97eae45fa571ba1c470e9ab649ba7570beb963b0 (patch) | |
| tree | 10730f3d24e43fa70294d15ba1382003e6fd7898 /book/en/src/by-example/app.md | |
| parent | 4981af8a4bfe5ee5442521794d851b0dc0313488 (diff) | |
| parent | baa2edfe72ec2e33a84dfebc6c4baf2c2b8d55c2 (diff) | |
Merge #375
375: close console text blocks on a new line r=AfoHT a=dcarosone
fixes #369
Co-authored-by: Daniel Carosone <Daniel.Carosone@gmail.com>
Diffstat (limited to 'book/en/src/by-example/app.md')
| -rw-r--r-- | book/en/src/by-example/app.md | 12 |
1 files changed, 8 insertions, 4 deletions
diff --git a/book/en/src/by-example/app.md b/book/en/src/by-example/app.md index 9a073ac..344cefc 100644 --- a/book/en/src/by-example/app.md +++ b/book/en/src/by-example/app.md @@ -55,7 +55,8 @@ process. ``` console $ cargo run --example init -{{#include ../../../../ci/expected/init.run}}``` +{{#include ../../../../ci/expected/init.run}} +``` ## `idle` @@ -86,7 +87,8 @@ in LLVM which miss-optimizes empty loops to a `UDF` instruction in release mode. ``` console $ cargo run --example idle -{{#include ../../../../ci/expected/idle.run}}``` +{{#include ../../../../ci/expected/idle.run}} +``` ## Hardware tasks @@ -107,7 +109,8 @@ mut` variables are safe to use within a hardware task. ``` console $ cargo run --example hardware -{{#include ../../../../ci/expected/hardware.run}}``` +{{#include ../../../../ci/expected/hardware.run}} +``` So far all the RTIC applications we have seen look no different than the applications one can write using only the `cortex-m-rt` crate. From this point @@ -139,7 +142,8 @@ The following example showcases the priority based scheduling of tasks. ``` console $ cargo run --example preempt -{{#include ../../../../ci/expected/preempt.run}}``` +{{#include ../../../../ci/expected/preempt.run}} +``` Note that the task `gpiob` does *not* preempt task `gpioc` because its priority is the *same* as `gpioc`'s. However, once `gpioc` terminates the execution of |