USER MANUAL RC188x-GPR
2019 Radiocrafts AS
RIIM User Manual (rev.1.2)
Page
11
of
23
7.2. Creating and Uploading the User Application
The following example shows how to create (compile) an unencrypted user application image and upload it to the
node using the bootloader over USB.
$
make
$
make uploadImage
<USER MUST RESET THE MODULE>
7.3. Encrypting the User Application
The user application can be encrypted to protect the users Intellectual Property and secure the product from
fraudulent software. To enable encryption of the user application, two criteria must be met:
The encryption key must be programmed into the bootloader
The user application image must be created with the same key
This is achieved using the scripts provided with the development environment from Radiocrafts. The example
assumes that there exist a key file called
encryption.key
in the same folder as the application. The following
sequence must be followed:
$
make encrypted
$
make uploadAppKey
<USER MUST RESET THE MODULE>
$
make uploadImage
7.4. Locking the module
Locking the module means that no one can upload unencrypted images to the module anymore. This feature helps
protect the application and is NOT reversible. It may be feasible to not lock the module if the user is actively
developing on the module. Locking should be done before shipping the product to disable possible tampering.
$
make lock
<USER MUST RESET THE MODULE>
7.5. Network Key
Network key can also be loaded into the bootloader. This key is used in the network so that only approved units
can join the network. All nodes in the network must have the same key to be able to use this feature. The key can
be distributed pre-shared via the bootloader or can be updated by the user application itself. The latter enables the
possibility of using key exchange algorithms. A file called
network.key
is assumed to be present in the same
directory.
$
make uploadNWKey
<USER MUST RESET THE MODULE>
