book
book copied to clipboard
Documentation on how to use the Rust Programming Language to develop firmware for bare metal (microcontroller) devices
I already read #326. I wonder if it is okay to proceed with the procedure left by @eldruin on the issue. #326 I want to translate it into Korean. thank...
This PR expands the publishing step to also publish a (very partial) Danish translation of the book. The result of this can be seen here: https://mgeisler.github.io/rust-embedded-book/da/intro/index.html. The infrastructure uses the...
The [section on writing to memory-mapped registers using a PAC](https://docs.rust-embedded.org/book/start/registers.html#writing) says that the argument of the closure passed to the `write()` function gives read-write access to the various sub-fields within...
It would likely be good to point out in this book that `log` works in `no_std` environments, and can have handlers for RTT, semihosting, ITM, UART, etc. Imho this is...
https://docs.rust-embedded.org/book/concurrency/index.html talks about sharing data, and hand-waves over what to do on a multi-core system. We should introduce `critical-section` here, which specifically resolves this issue.
Hello I am having problems to check my installation this is the output: Obs: I am using stm32f407, I also changed stm32f3x.cfg -> stm32f4x.cfg and also doesn't work openocd -f...
  ](https://user-images.githubusercontent.com/38847726/196359344-70223890-f7ce-425b-b409-a627b48bc3b1.png)  using with the multiarch setup on ubuntu 22.04
https://doc.rust-lang.org/nightly/rustc/platform-support/arm-none-eabi.html has been updated to have detailed documentation for every Arm Cortex-M related bare-metal target. We should link to that from https://docs.rust-embedded.org/book/intro/install.html rather than try and replicate it.
I got a stm32f4 and wrote some code to it, then tried to run openocd and got this error C:\Users\eyala\Documents\OpenOCD-20240916-0.12.0\bin>openocd.exe -f openocd.cfg Open On-Chip Debugger 0.12.0 (2024-09-16) [https://github.com/sysprogs/openocd] Licensed under...
As explained e.g. [here](https://swatinem.de/blog/future-size/), futures can easily turn into unpleasant memory hog surprises. One possible easy way to investigate problematic code is to add a `future-size-threshold = 100` (or whichever...