Using CLI


In order to use the KNoT CLI, it is necessary to fulfill the requirements.

There are many commands that you can call when using the knot script ( Some of their functions are:

Set default target board

  • You can set the default target board with the command:

$ knot board {BOARD}


Currently, KNoT support dk (nrf52840_pca10056) or dongle (nrf52840_pca10059) board. Replace {BOARD} with one of them.

Set external OpenThread path

To avoid downloading the OpenThread repo on every new build, set an external path.

  • Clone Openthread Github repository:

$ git clone
  • Checkout to the compatible hash and set it as default:

$ cd openthread
$ git checkout -b knot_hash f9d757a161fea4775d033a1ce88cf7962fe24a93
$ knot ot-path `pwd`

Clear project and building

The user can delete old building files before compiling again.


This is especially useful when the project had important changes like different target board or dependency repository.

  • Clear old files and compiling:

$ knot make --clean

Compile for your target board


The build command must be run from an application folder.

Currently, KNoT supports dk (nrf52840_pca10056) or dongle (nrf52840_pca10059) board. Replace {BOARD} by one of them.

$ knot make -b {BOARD}


If you already set the default board is not necessary compile with -b option.

Flash board when done

The user can flash the board just after building it.

  • Flash board after building:

$ knot make --flash


This option also flashes the bootloader when targeting the Dongle.

Flash bootloader

When using the DK, it’s possible for the board to be flashed without the bootloader. To fix that, the user should flash it separately.

  • Flash bootloader to board:

$ knot mcuboot


This option also erases the main app when targeting the Dongle.

Other commands

These and the other commands are described when using the help command:

$ knot --help