|
9 | 9 | HAL (meaning **H**ardware **A**bstraction **L**ayer) is a generic term used in many contexts,
|
10 | 10 | but in the specific context of this crate, it is meant to abstract away the control exposed
|
11 | 11 | by the devices "[peripheral access crate](`crate::pac`)" to simplify initialization routines,
|
12 |
| - with a robust interface avoiding miss-configurations while still not abstracting to much away. |
| 12 | + with a robust interface avoiding miss-configurations while still not abstracting away too much. |
13 | 13 |
|
14 |
| - Also this crate's goal is to integrate well with the rest of the rust embedded ecosystem, |
15 |
| - for example by implementing the [`embedded_hal`] traits or using crates, like [`embedded_time`], |
| 14 | + Also, this crate's goal is to integrate well with the rest of the rust embedded ecosystem, |
| 15 | + for example by implementing the [`embedded_hal`] traits or using crates like [`embedded_time`], |
16 | 16 | or [`rtcc`].
|
17 | 17 |
|
18 | 18 | [stm]: https://www.st.com/en/microcontrollers-microprocessors/stm32f3-series.html
|
|
101 | 101 |
|
102 | 102 | Enable functions, which leverage [`enumset`](https://crates.io/crates/enumset).
|
103 | 103 | This is especially usefull to get all set status events at once,
|
104 |
| - see for example [`crate::serial::Serial::triggered_events()`] |
| 104 | + see for example [`serial::Serial::triggered_events()`] |
105 | 105 |
|
106 | 106 | ### `defmt`
|
107 | 107 |
|
|
118 | 118 | [Application Setup]: https://defmt.ferrous-systems.com/setup-app.html
|
119 | 119 | [defmt]: https://github.com/knurling-rs/defmt
|
120 | 120 | [filter]: https://defmt.ferrous-systems.com/filtering.html
|
| 121 | + [`serial::Serial::triggered_events`]: `crate::serial::Serial::triggered_events` |
121 | 122 | */
|
122 | 123 | #![no_std]
|
123 | 124 | #![allow(clippy::upper_case_acronyms)]
|
|
0 commit comments