diff options
| author | bors[bot] <bors[bot]@users.noreply.github.com> | 2018-12-16 21:05:56 +0000 |
|---|---|---|
| committer | bors[bot] <bors[bot]@users.noreply.github.com> | 2018-12-16 21:05:56 +0000 |
| commit | 3511e915b5261ca11928ced3c05fa5ce1cabb138 (patch) | |
| tree | 46081c204b0424802ed88ce61f6e750105aa91e2 /book/src/by-example/timer-queue.md | |
| parent | c2fbb2848851e32b78e79ff9e919538b7d5ab8a0 (diff) | |
| parent | 22140fbc49b16e422652542371d3b389b2a5fbeb (diff) | |
Merge #116
116: v0.4.0 r=japaric a=japaric
Co-authored-by: Jorge Aparicio <jorge@japaric.io>
Diffstat (limited to 'book/src/by-example/timer-queue.md')
| -rw-r--r-- | book/src/by-example/timer-queue.md | 12 |
1 files changed, 10 insertions, 2 deletions
diff --git a/book/src/by-example/timer-queue.md b/book/src/by-example/timer-queue.md index a9c3622..f8066c2 100644 --- a/book/src/by-example/timer-queue.md +++ b/book/src/by-example/timer-queue.md @@ -1,8 +1,16 @@ # Timer queue When the `timer-queue` feature is enabled the RTFM framework includes a *global -timer queue* that applications can use to *schedule* software tasks to run some -time in the future. +timer queue* that applications can use to *schedule* software tasks to run at +some time in the future. + +> **NOTE**: The timer-queue feature can't be enabled when the target is +> `thumbv6m-none-eabi` because there's no timer queue support for ARMv6-M. This +> may change in the future. + +> **NOTE**: When the `timer-queue` feature is enabled you will *not* be able to +> use the `SysTick` exception as a hardware task because the runtime uses it to +> implement the global timer queue. To be able to schedule a software task the name of the task must appear in the `schedule` argument of the context attribute. When scheduling a task the |