Stack Configuration#

The Connect stack loads various configuration values at bootup. These values can be configured in three different places.

Component Options in the Connect Stack Group#

Many components in the Connect stack group have configuration options like this for the Parent Support component.

screenshotscreenshot

The configuration options are generated into a logically named header (for example, parent-support-config.h) under the config folder of the project.

Compile-Time Macros#

The Connect stack uses several macros that are not configurable as component options. These are documented in the Connect API documentation. If a configuration macro is not defined at compilation, a default value will be used from protocol/flex/stack/config/ember-configuration-defaults.h.

Compile-time macros can be added under the project properties as shown in the following figure.

screenshotscreenshot

Manufacturing Tokens#

The Connect stack also checks several manufacturing tokens to configure itself. These are tokens that are usually written once in the lifetime of the application but can be written independently from the firmware. For more information, see AN961: Bringing Up Custom Devices for the EFR32MG and EFR32FG Families and AN1154: Using Tokens for Non-Volatile Data Storage.

The following manufacturing tokens are supported:

  • TOKEN_MFG_CUSTOM_EUI_64

  • TOKEN_MFG_CTUNE

  • TOKEN_MFG_SECURE_BOOTLOADER_KEY (for Gecko bootloader)

  • TOKEN_MFG_SIGNED_BOOTLOADER_KEY_X (for Gecko bootloader)

  • TOKEN_MFG_SIGNED_BOOTLOADER_KEY_Y (for Gecko bootloader)

For more information on each manufacturing token, see AN961: Bringing Up Custom Devices for the EFR32MG and EFR32FG Families.