cortex-m
cortex-m copied to clipboard
rust-embedded
Low level access to Cortex-M processors
RP2040 starts execution on both cores. If entry function contains a "special" definition of `static mut` variable, each core takes a mutable reference to it, which is illegal from the...
To be able to place strings and similar in areas of the ELF file that will not be loaded, eg for the use in instrumentation tools, an INFO marked section...
See: https://git-scm.com/book/en/v2/Git-Internals-Plumbing-and-Porcelain Perhaps cortex-m and cortex-m-rt could be split into two pieces in a different way. We would have one crate which is the plumbing for Cortex-M - it would...
Not providing this is unsound, so we should make sure this is on by default before 1.0. This was already implemented in the past, but was removed with the switch...
# Summary [summary]: #summary Change the syntax of interrupt and exception handlers provided by `cortex-m-rt` to be more obvious, more internally consistent, and closer to RTFM's: * **Resource Syntax**: Resources...
Currently, *any* user of this crate has to pay for a small Assembly trampoline that provides access to the `&ExceptionFrame` to the `HardFault` handler (even if they don't use the...
Or rather, it builds successfully. The reason is that these `!` do not work with `errexit`, so a successful build has no consequences: https://github.com/rust-embedded/cortex-m-rt/blob/5ac023dd9261d67aafbeab018241b4bcc4742152/ci/script.sh#L44-L48 Caught by shellcheck [SC2251](https://github.com/koalaman/shellcheck/wiki/SC2251).
Hello! When using cortex-m-rtfm, I found it incredibly useful and intuitive that the peripherals from the respective device crate are passed into the `init` function. It's like taking `argc` and...
## Summary Change how the memory layout of `cortex-m-rt` programs is defined. Let the user specify memory regions and linker sections using a high level API from build scripts. ##...
