From d25017a59cfd7a59019e7b8cc2724e8353df1221 Mon Sep 17 00:00:00 2001 From: Emil Fresk Date: Thu, 12 Nov 2020 18:42:07 +0100 Subject: Fixed spawn and timer queue docs --- book/en/src/by-example/timer-queue.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) (limited to 'book/en/src/by-example/timer-queue.md') diff --git a/book/en/src/by-example/timer-queue.md b/book/en/src/by-example/timer-queue.md index 482aebc..2964175 100644 --- a/book/en/src/by-example/timer-queue.md +++ b/book/en/src/by-example/timer-queue.md @@ -29,9 +29,7 @@ on the built-in CYCle CouNTer (CYCCNT). Note that this is a 32-bit timer clocked at the frequency of the CPU and as such it is not suitable for tracking time spans in the order of seconds. -To be able to schedule a software task from a context the name of the task must -first appear in the `schedule` argument of the context attribute. When -scheduling a task the (user-defined) `Instant` at which the task should be +When scheduling a task the (user-defined) `Instant` at which the task should be executed must be passed as the first argument of the `schedule` invocation. Additionally, the chosen `monotonic` timer must be configured and initialized -- cgit v1.2.3