Skip to content

Latest commit

 

History

History

nrf52

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
clock
clock
 
 
hw_crypto
hw_crypto
 
 
src
src
 
 
.gitignore
.gitignore
 
 
CMakeLists.txt
CMakeLists.txt
 
 
Dockerfile
Dockerfile
 
 
README.md
README.md
 
 
prj.conf
prj.conf
 
 
stateless_rp
stateless_rp
 
 

README.md

nrf52-libmicrofido2 Example

A small Zephyr app for the Nordic nRF52840 Development Kit using libmicrofido2.

Build Preparation

See the attached Dockerfile that builds a container being able to compile, flash and debug the project. This container image can be built using the following command:

sudo DOCKER_BUILDKIT=1 docker build -t nrf52-sdk .

Building

  1. Navigate to this directory.
  2. Run sudo docker run --rm -v $PWD/../../:/libmicrofido2 nrf52-sdk west -v build -b nrf52840dk_nrf52840 -d /libmicrofido2/examples/nrf52/build /libmicrofido2/examples/nrf52.

Flashing

  1. Connect the Devkit to the computer.
  2. It should be shown with lsusb as SEGGER J-LINK. It should also be found as ACM device in /dev/ttyACM? (remember the number).
  3. Run sudo docker run --rm -v $PWD/../../:/libmicrofido2 --privileged --device=/dev/ttyACM? nrf52-sdk west flash -d /libmicrofido2/examples/nrf52/build.

Debugging

An interactive GDB session can be started with sudo docker run --rm -it -v $PWD/../../:/libmicrofido2 --privileged --device=/dev/ttyACM? nrf52-sdk west debug -d /libmicrofido2/examples/nrf52/build. You can additionally connect to the serial console output / log via sudo docker run --rm -it --privileged --device=/dev/ttyACM0 nrf52-sdk minicom -D /dev/ttyACM0 -b 115200.

Hardware Cryptography

As the nRF52840 has a Cryptocell 310 hardware cryptography co-processor, this example is able to use it. Hardware crypto can be enabled by setting the CONFIG_NRF_SECURITY=y in prj.conf. When set to n, software implementations will be used.