Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Latest commit

413: Correct eb3b96b with a useful function signature for try_wait r=jonas-schievink a=nospam2678

This is embarrassing. It appears my quality assurance for #412, while existent, was way flawed and insufficient.

Having a `try_` method take ownership over self makes it impossible call it more than once. Clearly a mutable reference was what was indented and required to actually make the method meaningful.

It would be a good idea to either merge this PR, or revert the previous one, prior to making the next release.

Co-authored-by: Martin <>

Git stats


Failed to load latest commit information.


HAL for the nRF51, nRF52 and nRF91 families of microcontrollers


Please refer to the changelog to see what changed in the last releases.


Every nRF chip has its own crate, listed below:

Crate Docs target
nrf51-hal thumbv6m-none-eabi
nrf52810-hal thumbv7em-none-eabi
nrf52811-hal thumbv7em-none-eabi
nrf52832-hal thumbv7em-none-eabihf
nrf52833-hal thumbv7em-none-eabihf
nrf52840-hal thumbv7em-none-eabihf
nrf9160-hal thumbv8m.main-none-eabihf

Device Reference Manuals from Nordic

Device Product Specification DK Reference Guide
nRF52810 v1.3 v1.3.1*
nRF52811 v1.0 v1.3.1*
nRF52832 v1.4 v1.3.1*
nRF52833 v1.3 v1.0.1
nRF52840 v1.1 v1.2
nRF9160 v2.0 v0.9.3

* These devices do not have a separate development kit and share the NRF52 DK


Be sure to copy and edit the Cargo.example.toml file to Cargo.toml. The file will require editing dependent on the target you wish to work with and contains some further instructions. Similarly, check out the .vscode/settings.json file when used in the context of Visual Studio Code. By default, all of these files are configured to work with the nRF52840 target.


Licensed under either of

at your option.


Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.