* These devices do not have a separate development kit and share the NRF52 DK
Development
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.
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.
nrf-rs/nrf-hal
nrf-halPlease refer to the changelog to see what changed in the last releases.
Crates
Every nRF chip has its own crate, listed below:
nrf51-halthumbv6m-none-eabinrf52810-halthumbv7em-none-eabinrf52811-halthumbv7em-none-eabinrf52832-halthumbv7em-none-eabihfnrf52833-halthumbv7em-none-eabihfnrf52840-halthumbv7em-none-eabihfnrf9160-halthumbv8m.main-none-eabihfDevice Reference Manuals from Nordic
nRF52810v1.3v1.3.1*nRF52811v1.0v1.3.1*nRF52832v1.4v1.3.1*nRF52833v1.3v1.0.1nRF52840v1.1v1.2nRF9160v2.0v0.9.3* These devices do not have a separate development kit and share the NRF52 DK
Development
Be sure to copy and edit the
Cargo.example.tomlfile toCargo.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.jsonfile when used in the context of Visual Studio Code. By default, all of these files are configured to work with the nRF52840 target.License
Licensed under either of
at your option.
Contribution
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.