Skip to main content

Developer Access (Debug Mode)

STICKER is an open platform built on the Zephyr RTOS. A debug build of the firmware adds an interactive shell console over RTT, which developers use to configure the device and run diagnostics directly over a debug connection.

Debug Mode​

The STICKER can be delivered in Debug Mode, which is intended primarily for developers. In this configuration, the device is supplied in an open state, allowing direct access for development, so you can explore, modify, and extend its functionality.

info

End users normally configure STICKER over NFC with a smartphone, with no cable or console required. See the NFC Configurator APP. The pages below are for firmware development and shell-based configuration.

Getting started​

To set up the firmware locally, flash a debug image, and open the console, follow Firmware Setup.

Firmware v1.4.0

Several of the shell commands below — clock, history, the dynamic alarm rules, settings erase, and the renamed ats diagnostics — are new in the upcoming STICKER firmware v1.4.0.

Shell command reference​

Once the console is open, configuration and diagnostics are entered as shell commands. Each command has its own page:

  • Configuration - the config command: intervals, LoRaWAN, sensors, capabilities, pulse counters, device identity.
  • Alarm Rules - the alarm command and the alarm uplink limits.
  • Sensor History - the history command and store-and-forward recording.
  • Real-time Clock - the clock command.
  • Maintenance - the settings command: save, reset, erase.
  • Diagnostics - the ats command: device info, sensor and LED tests, LoRaWAN status.