Recommended
Related

Rust bindings to nrf52 series

Coleman McFarland

In mid-2017, I came across this project by James Munns. It essentially wraps the C SDK for nRF52 development boards, and provides bindings that can be called from Rust. James gave a talk to the Rust DC Meetup, remotely over video conference. This talk inspired me to buy a couple of nRF52 dev boards.

I'd like to announce that here, in Nordic's official channels, because I'd like more embedded developers to become aware of it. Rust is a language that has the ability to compile down to native code with zero runtime, and no operating system. In other words, Rust can run on bare metal hardware. Today.

My ultimate dream is for hardware manufacturers themselves to provide official support. My understanding is that supporting Rust will be much more akin to supporting C, and not really like providing a special runtime for embedded Python or JavaScript.

Some challenges we will face (you can help!):

  1. We do not have a clear path for upgrading our Nordic SDK. We simply check in the C code, and there's some manual work around collecting all the headers for input to code generation.
  2. Speaking of code generation, bindgen, the tool that takes C header files and generates rust types, has been evolving rapidly. On one occasion the changes to generated code caused breaking changes in our nrf52 bindings library.
  3. We have a few examples to test blinking lights and connecting via bluetooth, but perhaps we might benefit from a more structured list of things to test to ensure we provide working bindings to the whole nrf52 dev kit.
  4. Related to 3, just kick the tires and open issues if you need help!

If you are interested, here are some links to learn more:

Here is a link to the GitHub repository

Here is a link to the full video recording of the DC Meetup talk. It offers a detailed overview of our embedded development workflow.

Finally, here is a recent talk about using "unsafe" code in Rust. This is relevant, because in the embedded context a lot of code involves usage of the unsafe keyword. This talk explains why that's necessary and not as scary as it sounds.

Parents

  • Why Rust? Language designers have learned a lot in 40 years. Rust has:

    • Built in tooling for compilation against different targets. Managing toolchains for different targets is officially supported
    • Built in, standard package manager
    • A type system that gives you abstraction without necessarily requiring indirection or additional memory cost. It's possible to get the compiler assurance of abstractions, but with zero-sized types.
    • compile time checking of race conditions and dangling pointers (although less important in single-threaded/no-heap environments).

    It's true that C++ has most/all of the "features" Rust has, but there is a benefit to using a language with a design that feels modern, and with strong built in tooling.

Comment

  • Why Rust? Language designers have learned a lot in 40 years. Rust has:

    • Built in tooling for compilation against different targets. Managing toolchains for different targets is officially supported
    • Built in, standard package manager
    • A type system that gives you abstraction without necessarily requiring indirection or additional memory cost. It's possible to get the compiler assurance of abstractions, but with zero-sized types.
    • compile time checking of race conditions and dangling pointers (although less important in single-threaded/no-heap environments).

    It's true that C++ has most/all of the "features" Rust has, but there is a benefit to using a language with a design that feels modern, and with strong built in tooling.

Children
No Data