add some generation resources, add some feature descriptions
This commit is contained in:
parent
8b6c6c7df6
commit
9ea7a245e9
2 changed files with 25 additions and 9 deletions
|
@ -1,6 +1,17 @@
|
||||||
= Starting a new Embassy project
|
= Starting a new Embassy project
|
||||||
|
|
||||||
Once you’ve successfully xref:getting_started.adoc[run some example projects], the next step is to make a standalone Embassy project. The easiest way to do this is to adapt an example for a similar chip to the one you’re targeting.
|
Once you’ve successfully xref:getting_started.adoc[run some example projects], the next step is to make a standalone Embassy project.
|
||||||
|
|
||||||
|
There are some tools for generating Embassy projects: (WIP)
|
||||||
|
|
||||||
|
==== CLI
|
||||||
|
- link:https://github.com/adinack/cargo-embassy[cargo-embassy] (STM32 and NRF)
|
||||||
|
|
||||||
|
==== cargo-generate
|
||||||
|
- link:https://github.com/lulf/embassy-template[embassy-template] (STM32, NRF, and RP)
|
||||||
|
- link:https://github.com/bentwire/embassy-rp2040-template[embassy-rp2040-template] (RP)
|
||||||
|
|
||||||
|
But if you want to start from scratch:
|
||||||
|
|
||||||
As an example, let’s create a new embassy project from scratch for a STM32G474. The same instructions are applicable for any supported chip with some minor changes.
|
As an example, let’s create a new embassy project from scratch for a STM32G474. The same instructions are applicable for any supported chip with some minor changes.
|
||||||
|
|
||||||
|
|
|
@ -38,13 +38,18 @@ DEFMT_LOG = "trace" # <- can change to info, warn, or error
|
||||||
|
|
||||||
=== build.rs
|
=== build.rs
|
||||||
|
|
||||||
This is the build script for your project. It links defmt (what is defmt?) and the `memory.x` file if needed. This file is pretty specific for each chipset, just copy and paste from the corresponding link:https://github.com/embassy-rs/embassy/tree/main/examples[example].
|
This is the build script for your project. It links defmt (what is link:https://defmt.ferrous-systems.com[defmt]?) and the `memory.x` file if needed. This file is pretty specific for each chipset, just copy and paste from the corresponding link:https://github.com/embassy-rs/embassy/tree/main/examples[example].
|
||||||
|
|
||||||
=== Cargo.toml
|
=== Cargo.toml
|
||||||
|
|
||||||
This is your manifest file, where you can configure all of the embassy components to use the features you need.
|
This is your manifest file, where you can configure all of the embassy components to use the features you need.
|
||||||
|
|
||||||
TODO: someone should exhaustively describe every feature for every component!
|
==== Features
|
||||||
|
===== Time
|
||||||
|
- tick-hz-x: Configures the tick rate of `embassy-time`. Higher tick rate means higher precision, and higher CPU wakes.
|
||||||
|
- defmt-timestamp-uptime: defmt log entries will display the uptime in seconds.
|
||||||
|
|
||||||
|
...more to come
|
||||||
|
|
||||||
=== memory.x
|
=== memory.x
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue