Empty ZED

Theory of Operation

The empty ZED application is intended as a blank slate starting point that has only the required pieces to build and run. There are no zigbee clusters or attributes and the only plugins that this app utilizes are the CLI and debug print plugins.

Pressing either button on the DKNCM11 board will result in a debug print message and the blue LED toggling state.

By default, builds will be created for the Trident DKNCM11 board and for a custom PCB target when doing a project build. Both configurations are identical to start but this provides a way for users to build their applications for both targets as custom device development begins. This allows easier transition between different PCB targets which can be useful if a user ever wants Trident to help debug issues. Being able to run on the DKNCM11 board will allow Trident support to more quickly reproduce issues and support customers without needing the custom hardware target. To remove either hardware target from the build, simply delete or rename the hal_config_<board>T32CM11C directory. The build system looks for the hal_config directory and builds all of them for the specified chip target (T32CM11C).

ZCL Configuration

This application has no ZCL configuration.

Trident Plugins

Enabled Plugins	Implemented Callbacks
Command Line Interface (CLI)	–
Debug Print	–
–	tr_app_init_cb

User Interface on the DKNCM11C10

USB-C Interface

Plugging a USB-C cable from a computer into the DKNCM11C10 will enable a COM port to appear on the computer. This can be connected used to open a connection to the CLI that is running on the device.

COM Port Settings
Baud	115200
Data Bits	8
Stop Bits	1
Parity	None
Flow Control	None

Buttons

Button	Action	Description
BTN0	Press	Hardware reset
BTN1	Press	Toggle blue LED
BTN2	Press	Toggle blue LED

LEDs

LED	Behavior	Description
Green	Not used	Not used
Red	Not used	Not used
Blue	Changes state	Toggles when BTN1 or BTN2 are pressed

Example CLI Commands

This sample application includes a cli submenu of example commands. These commands

Command	Description
example one	Example custom command one usage: one -a arg value [-s string value] [-o option <default=0>] -a arg_value is a mandatory option used to show how to get the value of an numeric option argument -s "string" is an optional option used to show how to get the value of an string option argument -o is an optional option used to show how to use options that do not have arguments
example sub-command two	Example custom sub-command two shows how to create nested cli commands tables usage: two [-a arg value (default=0)] -a arg_value is an optional option used to show how to get the value of an numeric option argument

Custom APP Tokens

This project contains an example of how to create custom APP tokens that can be used from the application and can be interacted with externally via elcap. As long as the project_app_tokens.h exists in the project src directory, the application tokens will be added to the project and the APP token definition file needed for interacting with these tokens via elcap will be generated into the build directory. The APP token definition file looks like T32CM11C_app_token_def.json.