Digi Board

This demo demonstrates the Uniquid Identity and Access Management SDK using the uidcore-c library on ConnectCore 6UL SBC Express Digi board.

Requirements

  • Ubuntu 14.04+ with standard development tools

  • cmake to compile new firmware

  • Digi ConnectCore 6UL SBC Express with internet connection (link)

  • some software packages from digi.com (next steps)

  • libcurl

  • libpthread (usually already installed)

Install Prerequisites

Install these packages on your machine

sudo apt install cmake
sudo apt install libcurl4-openssl-dev

Setup of the board

For a more detailed documentation on the board setup please refer to the DIGI web site

Setup of Development Environment

  1. download the toolchain installer from the Digi support page

  2. give execution permission to the installer

  3. install the toolchain on your host PC

  4. source the environment setup script, run this command each time you wish to use the SDK in a new shell session

Download and build the demo source code on host PC

  1. clone the demo repo two options:

  2. change directory

  3. download and patch the dependancy

  4. build the project, the binaries created by this command will be put on the bin directory

Transfer the executables on the board

  1. power on the board using the provided USB cable

  2. connect to the board using a serial terminal emulator (115200N81) or ssh

  3. create the demo directory under /home/root

  4. transfer all the content of the bin directory from the host PC to the /home/root/demo directory on the board using scp

Copy certificate and configuration files

Copy in the demo directory the configuration file (aws_device_cfg.json) and the root CA for the mqtt broker (caChain-xxxxxxxxxxxxxx.crt) from your host PC to the board:

both these files has been generated by the uniquid deploy aws command you run some steps ago.

Run

  1. connect to the board over terminal emulator or ssh and go to the demo directory

  2. run the demo

    if you want to run the demo at the board boot copy the above script into the /etc/rc5.d directory

  3. you can check the log running tail command

  4. to allow the board to publish the led status on aws IoT you have to create a contract between the board (user) and the authorizer (provider)

  5. check here for published messages (please note that the link provided is for the us-east-2 AWS region, you may need to switch to the one you have defined on aws configure)

  6. you can use the button on the board to switch on/off the led status

To remotely interact with the board you have to install the related application.

Last updated