Hi Timon_guo,

You can also open the network with command "plugin network-creator-security open-with-key [eui64:8] [joiningLinkKey:-1]" instead of using command "plugin network-creator-security open-network".

Hi wang chaoqun,

A new version of Simplicity Commander has been released that contains the fix for using external Segger J-Link debug adapters.  The new version is not yet included in Simplicity Studio, but this Knowledge Base Article describes how to download it and replace the internal Simplicity Studio version: https://www.silabs.com/community/software/simplicity-studio/knowledge-base.entry.html/2020/05/21/how_to_update_thesimplicitycommanderversioninc-UkQc

The Simplicity Studio release containing the updated version of commander should be made in a few weeks if you prefer to wait for it.

If you choose to update commander based on the KBA, please let me know if:
A. There are any issues following the procedure
B. It doesn't fix the problem when using the external Segger J-Link
 

If you choose to use WSTK, please perform a device recover following YK's suggestion.

Thanks,

Jim

Hi Tung Hoang, Sorry for the late response. Yes, you can find it in plugin "ZCL framework core". I'm glad you find it.

Thanks,

Jim

Hi kentmartin99_gm,  these configurations are not supposed to be changed at run-time. 

May I know why you need to do this ?

Thanks,

Jim

Hi sam luo,

I can import your .sls file, but can't open the isc file. In your hardware configurator, please don't use TIMER0 as it is already used by the stack.

https://www.silabs.com/community/wireless/zigbee-and-thread/knowledge-base.entry.html/2016/07/08/peripheral_utilizati-n9VT

And also you need to create a bootloader project and flash it into your board.

Jim

Hi Kandarp Rastey, please check my reply on your salesforce ticket.

EM4 is not completely supported in EmberZnet SDK for series 2, but it's coming soon.  You can use EM2 instead and this is the default sleep mode for sleepy end devices in EmberZnet. Below is the waveform tested on BRD4308A.  When you press button1, the device will sleep. But as the LED1 will be turned on when you press button1, the current is still higher than expected (normally it should be less than 10uA). The reason is in BRD4308A, the button1 and LED1 is using the same pin.     

Hi Kandarp Rastey,  can you elaborate it ? 

Yes, you're right. Here is an function in the SDK. You can check this code and understand this mask.

static EmberStatus setJoinPolicy(EmberJoinDecision decision)
{
  EzspDecisionBitmask policy = EZSP_DECISION_BITMASK_DEFAULT_CONFIGURATION;
  uint8_t textId = 0;

  if (decision == EMBER_USE_PRECONFIGURED_KEY) {
    policy = (EZSP_DECISION_ALLOW_JOINS | EZSP_DECISION_ALLOW_UNSECURED_REJOINS);
    textId = 1;
  } else if (decision == EMBER_SEND_KEY_IN_THE_CLEAR) {
    policy = (EZSP_DECISION_ALLOW_JOINS | EZSP_DECISION_ALLOW_UNSECURED_REJOINS | EZSP_DECISION_SEND_KEY_IN_CLEAR);
    textId = 2;
  }
  return emberAfSetEzspPolicy(EZSP_TRUST_CENTER_POLICY,
                              policy,
                              "Trust Center Policy",
                              ezspJoinPolicyText[textId]);
}

Hi Nguyễn Cao Bái, 

1. To perform a "factory reset", we need to clear all the saved information. As those info are saved as tokens, we just need to erase the token and load them with default value.  There are two storage mechanisms used.

• Simulate EEPROM. If you enabled plugin "Simulate EEPROM Version 1" or "Simulate EEPROM Version 2", you are actually using the simulate EEPROM to store the network info. In this case, you can call the following function with the parameter "forceRebuildAll" to be true.

•  NVM3. If you enabled plugin "NVM3", you are actually using this mechanism. In this case, you can call the following function to erase. For the parameter, you can use nvm3_defaultHandle defined in C:\SiliconLabs\SimplicityStudio\v4\developer\sdks\gecko_sdk_suite\v2.7\platform\emdrv\nvm3\inc\nvm3_default.h

bool    nvm3_repackNeeded(nvm3_Handle_t *h);

Thanks,

Jim