diff options
| author | Henrik Tjäder <henrik@tjaders.com> | 2023-03-02 22:38:25 +0100 |
|---|---|---|
| committer | Henrik Tjäder <henrik@tjaders.com> | 2023-03-02 22:38:25 +0100 |
| commit | f03aede2f5a926bdb26d052766492c32454a60dd (patch) | |
| tree | 77e13743b4dd0b8b9cac3a2a600b16e7c5ccf1ce /book/en/src/by-example/hardware_tasks.md | |
| parent | 4a3f7ea123aa4ed2f89531b4cd25773264301ff8 (diff) | |
Fixes for repo rename to rtic
Diffstat (limited to 'book/en/src/by-example/hardware_tasks.md')
| -rw-r--r-- | book/en/src/by-example/hardware_tasks.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/book/en/src/by-example/hardware_tasks.md b/book/en/src/by-example/hardware_tasks.md index c902267..75dd1a4 100644 --- a/book/en/src/by-example/hardware_tasks.md +++ b/book/en/src/by-example/hardware_tasks.md @@ -10,7 +10,7 @@ All tasks bound to an explicit interrupt are called *hardware tasks* since they Specifying a non-existing interrupt name will cause a compilation error. The interrupt names are commonly defined by [PAC or HAL][pacorhal] crates. -Any available interrupt vector should work. Specific devices may bind specific interrupt priorities to specific interrupt vectors outside user code control. See for example the [nRF “softdevice”](https://github.com/rtic-rs/cortex-m-rtic/issues/434). +Any available interrupt vector should work. Specific devices may bind specific interrupt priorities to specific interrupt vectors outside user code control. See for example the [nRF “softdevice”](https://github.com/rtic-rs/rtic/issues/434). Beware of using interrupt vectors that are used internally by hardware features; RTIC is unaware of such hardware specific details. |