embedded-trainings-2020/boards/dk
Jorge Aparicio 17ebad4a3c adapt to breaking changes in cortex-m-rtic 0.5.x
at some point cortex-m-rtic fixed a memory safety bug: RTIC was not marking the
cortex_m::Peripherals singleton as "taken" in its pre-init code. This made it possible to create two
instances of the singleton, e.g. by calling `cortex_m::Peripherals::take` in an RTIC app.

the fix included a breaking change: it makes `Peripherals::take` return `None` from within an RTIC
app. This breaks the use of `dk::init`, which `take`s those `Peripherals`, within an RTIC app and
thus breaks most of the exercises / examples in the advanced workshop

this PR fixes the issue by making `dk::init` not `take` the `Peripherals`. For more details read
in-line comments in the diff
2021-01-28 16:02:53 +01:00
..
src adapt to breaking changes in cortex-m-rtic 0.5.x 2021-01-28 16:02:53 +01:00
build.rs squashed 2020-06-09 11:58:27 +02:00
Cargo.toml bump cortex-m versions 2021-01-21 14:03:57 +01:00
memory.x squashed 2020-06-09 11:58:27 +02:00
README.md squashed 2020-06-09 11:58:27 +02:00

dk

Board Support Crate for the nRF52840 Development Kit (DK)

Getting familiar with the hardware

TODO