This document describes the internals of the embeNET demo application running on LAUNCHXL-CC1312R1 boards and provides information on how to modify and extend the demo.
How does the demo application work
The demo application uses the embeNET Node C API library to join the network and run two network services:
- ENMS: embeNET Network Management service that allows to gather information about the network operation from the nodes
- custom exemplary service, that sends out a simple message every 5 seconds and also reacts to some simple messages
NoRTOS operation
For simplicity, the demo is prepared without using any operating system. It uses TI's NoRTOS framework module.
Logging is available only in nodes
You will find several places in the code using printf that print out diagnostic messages. While the LAUNCHXL-CC1312R1 has two UARTs routed to COM ports when the board gets connected to a PC, one of them is used for programming/debugging (Auxilary Data Port). The user application is left with a single port (Application/User). In root node this port is used for communication with the border router application running on PC. This means that for root node there is no easy way of printing the log output and so this output is not enabled. By default the log is only configured in nodes (when IS_ROOT=0).
Initialization
First we initialize the board and its basic peripherals:
Board_initGeneral();
GPIO_init();
Next we configure UART2 for logging (but only for nodes, as the root uses it to communicate with host). Then we start the NoRTOS framework:
#if 1 != IS_ROOT
enable_logging();
#endif
NoRTOS_start();
Next the embeNET stack is initialized:
.onLeft = onLeft,
.onJoinAttempt = onJoinAttempt,
.onDataOnUnregisteredPort = dataOnUregisteredPort,
.onQuickJoinCredentialsObsolete = onQuickJoinCredentialsObsolete
};
printf("embeNET Node initialized\n");
} else {
printf("Failed to initialize embeNET Node\n");
}
EMBENET_Result EMBENET_NODE_Init(const EMBENET_NODE_EventHandlers *eventHandlers)
EMBENET_NODE_OnJoined onJoined
After that the ENMS service is initialized:
uint8_t hardwareId[16] = {0x00};
uint64_t uid = EMBENET_EUI64_Get();
memcpy(hardwareId+8, &uid, sizeof(uid));
if (ENMS_NODE_RESULT_OK ==
ENMS_NODE_Init(&enmsNode, ENMS_DEFAULT_PORT, hardwareId, 1, 0, 0)) {
printf("ENMS service initialized\n");
} else {
printf("Failed to initialize ENMS service!\n");
}
EnmsNodeResult ENMS_NODE_Init(EnmsNode *enmsNode, uint16_t port, const uint8_t hwId[16], const EnmsIndicationPolicy *indicationPolicy)
In case of root we just start it:
EMBENET_Result EMBENET_NODE_RootStart(void const *panData, size_t panDataSize)
In case of nodes we start the custom demo service and MQTT-SN service:
custom_service_init();
mqttsn_client_service_init();
EnmsNodeResult ENMS_NODE_RegisterService(EnmsNode *enmsNode, const char *serviceName, uint8_t serviceState)
Joining the network
In order to join the network the node has to setup the required network configuration:
.
k1.
val = { 0xc0, 0x8b, 0x76, 0x62, 0x77, 0x09, 0x9e, 0x7d, 0x7e, 0x9c, 0x02, 0x22, 0xf1, 0x68, 0xcc, 0x9e },
.psk.val = { 0x46, 0xd7, 0xdc, 0x94, 0xe8, 0xee, 0x74, 0x96, 0xce, 0xaf, 0x54, 0xa3, 0xab, 0x64, 0xcb, 0xeb },
};
EMBENET_Result EMBENET_NODE_Join(const EMBENET_NODE_Config *config)
The main loop
The application's main loop consists of a call to:
- embeNET Node processing function
- MQTT-SN service process (only needed for polling button status)
while (1) {
mqttsn_client_service_proc();
}
void EMBENET_NODE_Proc(void)
Network join event
Once the node joins the network an event callback will be called. In our demo application this callback simply starts the network services:
printf("Joined network with PANID: x%04" PRIx16 "\n", panId);
printf("Starting ENMS service\n");
if (ENMS_NODE_RESULT_OK != enmsStartStatus) {
printf("ENMS service failed to start with status %d\n", (int)enmsStartStatus);
}
custom_service_start();
mqttsn_client_service_start();
}
EnmsNodeResult ENMS_NODE_Start(EnmsNode *enmsNode)
Network leave event
In case when node gets disconnected from the network, another callback is called. In our demo application this callback stops the network services:
static void onLeft(void) {
printf("Node has left the network\n");
if (ENMS_NODE_RESULT_OK == enmsStopStatus) {
printf("ENMS service stopped\n");
} else {
printf("ENMS service failed to stop with status %d\n", (int)enmsStopStatus);
}
custom_service_stop();
mqttsn_client_service_stop();
}
EnmsNodeResult ENMS_NODE_Stop(EnmsNode *enmsNode)
Handling critical errors
In cases when the embeNET stack detects a critical condition, the following handler is called by the stack, giving a chance to react:
printf("Program aborted: %s %s:%i\n", why, file, line);
while(1) { ; }
__builtin_unreachable();
}
EXPECT_INTERNAL_NORETURN void EXPECT_OnAbortHandler(char const *why, char const *file, int line)
Customizing and extending the demo application
The structure of the firmware project is mostly generated by Code Composer IDE. This allows you to easily customize the peripherals for your demo project as needed.
>The only requirement is NOT to change configuration of peripherals used by the port implementation, i.e. RADIO, CRYP, TIM2.
Writing or extending a custom network service.
The best starting point is to look at implementation of the existing custom_service.
Disabling "zero rule"
In order to disable the "zero rule", delete the rule with "uid": 0,
from your config.json file, and add appropriate rules for your nodes, for example:
"join_rules": [
{
"uid": 2,
"psk": "0x1ccd738f70a35be9574738ad190f86f2"
},
{
"uid": 3,
"psk": "0xdc2eafe4016303ebb1aa1b4b2ed4fda0"
}
]
This will allow only nodes with uid = 2 and 3, to join the network, provided that their PSKs match those from config.json file.
Using custom name for network interface
You may specify the name of desired network interface in .json file, by adding on root level:
"interface_name": "your-name"
Limitations of embeNET demo application
The demo version of the embeNET stack allows to connect up to 10 nodes only, with network depth of max. 3 hops.