Summary of the Examples

Here follows a brief description of each demo for quick reference. For a more in-depth explanation on how the peripherals work please refer to the device reference manuals linked above, the readme for each demo and the comments in the demo code itself.

Demo	Category	Description
blinky-button-demo	Hello World	Blinky button demo
ccm-demo	Encryption	Cipher block chaining - message authentication code (CCM) mode demo
comp-demo	Analog Pins	Voltage comparator peripheral demo
ecb-demo	Encryption	AES electronic codebook mode encryption demo
gpiote-demo	Digital Pins	General-Purpose Input Output Tasks and Events module demo
i2s-controller-demo	Audio	Inter-IC Sound interface "controller mode (aka master mode)" demo
i2s-peripheral-demo	Audio	Inter-IC Sound interface "peripheral mode (aka slave mode)" demo
lpcomp-demo	Analog Pins	Low power voltage comparator demo
ppi-demo	Channels	Programmable peripheral interconnect (PPI) demo
pwm-demo	Digital Pins	Pulse width modulation demo
qdec-demo	Sensor Decoding	Quadrature sensor decoder (QDEC) demo
rtic-demo	Framework	The Real-Time Interrupt-driven Concurrency framework demo
spi-demo	Digital Pins	Serial peripheral interface master (SPIM) with EasyDMA demo
spis-demo	Digital Pins	Serial peripheral interface slave (SPIS) demo
twi-ssd1306	Digital Pins	I2C compatible Two-Wire Interface with the SSD1306 OLED Display demo
twim-demo	Digital Pins	I2C compatible Two-Wire Interface Master mode demo
twis-demo	Digital Pins	I2C compatible Two-Wire Interface Slave mode demo
wdt-demo	Timer	Watchdog timer demo

Running the Examples

Each demo readme should contain instructions on how to run it. However, the information below describes the technologies used and can be used to troubleshoot your system setup. Run the demos from within their respective project directories. E.g. to run ccm-demo, you must be in the nrf-hal/examples/ccm-demo/ directory.

Since the demos are stand-alone projects you would NOT typically run them with cargo run --example xyz-demo like some cargo projects are configured to do.

Once Off System Setup

Install the cross compilation toolchain to target your device. You would typically pass the target as a parameter to cargo or explicitly set it in your cargo config file. If you get compilation errors about eh_personality then you have not set the target correctly. Here is an example of the target for a nRF52840 chip:

$ rustup target add thumbv7em-none-eabihf

Install the tools to flash the device.

$ cargo install cargo-embed

For Every Project (optional)

Setup the Cargo.toml file to use the correct features. Features allow for conditional compilation which is essential for a library like this that supports multiple different devices. Under the [features] section add the following line default = ["52840"] for the nRF52840-DK device or whatever other feature is applicable for your device. This is optional but it will allow you to simply call cargo run and cargo build instead of cargo run --features 52840 and cargo build --features 52840 respectively. Note that some demo projects do not have features so this step may not be necessary. If you get a whole bunch of compilation errors or plugins like rust-analyzer are not working then check that you have set the chip features correctly.

Alternative flashing methods

The primary way for flashing the devices is through cargo embed, as often detailed in the examples' README files.

Several alternatives are available, depending on one's setup:

• Programmers thar are "Mbed Enabled" usually support flashing .hex (Intel Hex) files by simply copying them onto the virtual USB storage device.

  Suitable files are created by converting the built ELF files:

  $ cargo build --target thumbv7em-none-eabihf
  $ arm-none-eabi-objcopy -O ihex target/thumbv7em-none-eabihf/debug/blinky-button-demo.elf /media/${USER}/JLINK/blinky-button-demo.hex
  

• When using debuggers in a stand-alone way, these usually need to be passed the .elf file produced by cargo build.