mirror of
https://github.com/rtic-rs/rtic.git
synced 2024-12-01 16:04:33 +01:00
Expand lock explanation
Co-authored-by: Henrik Tjäder <henrik@tjaders.com>
This commit is contained in:
parent
c8d60d2910
commit
60132495d9
1 changed files with 7 additions and 4 deletions
|
@ -2,10 +2,13 @@
|
||||||
|
|
||||||
While RTIC can currently target all Cortex-m devices there are some key architecure differences that
|
While RTIC can currently target all Cortex-m devices there are some key architecure differences that
|
||||||
users should be aware of. Namely the absence of Base Priority Mask Register (`BASEPRI`) which lends itself exceptionally well to the hardware priority ceiling support used in RTIC, in the
|
users should be aware of. Namely the absence of Base Priority Mask Register (`BASEPRI`) which lends itself exceptionally well to the hardware priority ceiling support used in RTIC, in the
|
||||||
ARMv6-M and ARMv8-M-base architectures requires a few tweaks from RTIC to deliver the same
|
ARMv6-M and ARMv8-M-base architectures, which forces RTIC to use source masking instead. For each implementation of lock and a detailed commentary of pros and cons, see the implementation of [lock in src/export.rs][src_export].
|
||||||
features. These differences result in two flavors of critical sections: priority ceiling, and source
|
|
||||||
masking. Table 1 below shows a list of Cortex-m processors and which type of critical section they
|
[src_export]: https://github.com/rtic-rs/cortex-m-rtic/blob/master/src/export.rs
|
||||||
employ.
|
|
||||||
|
These differences influence how critical sections are realized, but functionality should be the same except that ARMv6-M/ARMv8-M-base cannot have tasks with shared resources bound to exception handlers, as these cannot be masked in hardware.
|
||||||
|
|
||||||
|
Table 1 below shows a list of Cortex-m processors and which type of critical section they employ.
|
||||||
|
|
||||||
#### *Table 1: Critical Section Implementation by Processor Architecture*
|
#### *Table 1: Critical Section Implementation by Processor Architecture*
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue