How to use custom application token in EmberZnet?
When customers develop their Zigbee application, most of them need to store nonvolatile data, so that these data can’t be lost after reset or power cycle. Because EM35x and Mighty Gecko process technology does not offer an internal EEPROM, a simulated EEPROM is implemented to use a section of internal flash memory for stack and application token storage. So customer can use custom application token to store these nonvolatile data. Here is example to help customers to use custom application token step by step.
// APP CREATORS #define CREATOR_APP_VERSION_INFO (0x6730) //BASIC #define NVM3KEY_APP_VERSION_INFO (NVM3KEY_DOMAIN_ZIGBEE |0x6730) typedef uint16_t tokenTypeAppVersionInfo; DEFINE_BASIC_TOKEN(APP_VERSION_INFO, tokenTypeAppVersionInfo, 0x0000)
For more information, please review the following documentation: