aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDario Nieuwenhuis <[email protected]>2023-10-18 02:59:48 +0000
committerGitHub <[email protected]>2023-10-18 02:59:48 +0000
commit51708c8ed1962618ac7bc244a3f5e7ceced28182 (patch)
treecec7ba11a7ee77e90b1ab8cac119f93732f8da37
parentf24a1b62bb94da990cefe28256c28ad47b0c4de8 (diff)
parent10f08445e499f733c2d32bbcb72708809a7d8dc9 (diff)
Merge pull request #2089 from artisdom/patch-1
Update basic_application.adoc
-rw-r--r--docs/modules/ROOT/pages/basic_application.adoc2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/modules/ROOT/pages/basic_application.adoc b/docs/modules/ROOT/pages/basic_application.adoc
index 3f4f16e28..73774c71b 100644
--- a/docs/modules/ROOT/pages/basic_application.adoc
+++ b/docs/modules/ROOT/pages/basic_application.adoc
@@ -48,7 +48,7 @@ The `Spawner` is the way the main application spawns other tasks. The `Periphera
48include::example$basic/src/main.rs[lines="22..-1"] 48include::example$basic/src/main.rs[lines="22..-1"]
49---- 49----
50 50
51What happens when the `blinker` task has been spawned and main returns? Well, the main entry point is actually just like any other task, except that you can only have one and it takes some specific type arguments. The magic lies within the `#[embassy::main]` macro. The macro does the following: 51What happens when the `blinker` task has been spawned and main returns? Well, the main entry point is actually just like any other task, except that you can only have one and it takes some specific type arguments. The magic lies within the `#[embassy_executor::main]` macro. The macro does the following:
52 52
53. Creates an Embassy Executor 53. Creates an Embassy Executor
54. Initializes the microcontroller HAL to get the `Peripherals` 54. Initializes the microcontroller HAL to get the `Peripherals`