As you may know, we can use the EZSP frame setPreinstalledCbkeData(0xA2) and setPreinstalledCbkeData283k1(0xED) to set the device's CA public key and 283k1 curve CA public key, which has been mentioned in UG100(page107). The associated APIs are ezspSetPreinstalledCbkeData() and ezspSavePreinstalledCbkeData283k1().

Please note, there is a difference between these two APIs.

Regarding the ezspSetPreinstalledCbkeData(), you can call it directly after inputing the three parameters (caPublic, myCert, myKey). But regarding the ezspSavePreinstalledCbkeData283k1(), it can't. You need set EZSP_VALUE_CERTIFICATE_283K1/ EZSP_VALUE_PUBLIC_KEY_283K1/ EZSP_VALUE_PRIVATE_KEY_283K1 firstly before you call the ezspSavePreinstalledCbkeData283k1(). Actually, we have an new API(emberSetPreinstalledCbkeData283k1) to implement the funciton. Please refer to below code.

// sample code in ezsp.c
EmberStatus emberSetPreinstalledCbkeData283k1(EmberPublicKey283k1Data *caPublic,
                                              EmberCertificate283k1Data *myCert,
                                              EmberPrivateKey283k1Data *myKey)
{
  ezspSetValue(EZSP_VALUE_CERTIFICATE_283K1, EMBER_CERTIFICATE_283K1_SIZE, emberCertificate283k1Contents(myCert));
  ezspSetValue(EZSP_VALUE_PUBLIC_KEY_283K1, EMBER_PUBLIC_KEY_283K1_SIZE, emberPublicKey283k1Contents(caPublic));
  ezspSetValue(EZSP_VALUE_PRIVATE_KEY_283K1, EMBER_PRIVATE_KEY_283K1_SIZE, emberPrivateKey283k1Contents(myKey));
  return ezspSavePreinstalledCbkeData283k1();
}

The CBKE Data associated with ECC 283k1 is sent in three separate EZSP commands because the total length of the combined data is greater than the max EZSP message length (133).  The first EZSP command will contain the certificate followed next by the public key and finally the private key. Once all the data has been received by the NCP a 4th command is sent by the host indicating to push the data into permanent storage.

As you may know, we can use the EZSP frame setPreinstalledCbkeData(0xA2) and setPreinstalledCbkeData283k1(0xED) to set the device's CA public key and 283k1 curve CA public key, which has been mentioned in UG100(page107). The associated API is ezspSetPreinstalledCbkeData() and ezspSavePreinstalledCbkeData283k1(). Please note, there is a difference between these two APIs.

Regarding the ezspSetPreinstalledCbkeData(), you can call it directly after input the three parameters (caPublic, myCert, myKey). But regarding ezspSavePreinstalledCbkeData283k1(), it doesn’t. You need set EZSP_VALUE_CERTIFICATE_283K1/ EZSP_VALUE_PUBLIC_KEY_283K1/ EZSP_VALUE_PRIVATE_KEY_283K1 firstly before you call the ezspSavePreinstalledCbkeData283k1(). Actually, we have an new API(emberSetPreinstalledCbkeData283k1) can implement the funciton.

// sample code in ezsp.c
EmberStatus emberSetPreinstalledCbkeData283k1(EmberPublicKey283k1Data *caPublic,
                                              EmberCertificate283k1Data *myCert,
                                              EmberPrivateKey283k1Data *myKey)
{
  ezspSetValue(EZSP_VALUE_CERTIFICATE_283K1, EMBER_CERTIFICATE_283K1_SIZE, emberCertificate283k1Contents(myCert));
  ezspSetValue(EZSP_VALUE_PUBLIC_KEY_283K1, EMBER_PUBLIC_KEY_283K1_SIZE, emberPublicKey283k1Contents(caPublic));
  ezspSetValue(EZSP_VALUE_PRIVATE_KEY_283K1, EMBER_PRIVATE_KEY_283K1_SIZE, emberPrivateKey283k1Contents(myKey));
  return ezspSavePreinstalledCbkeData283k1();
}

The CBKE Data associated with ECC 283k1 is sent in three separate EZSP commands because the total length of the combined data is greater than the max EZSP message length (133).  The first EZSP command will contain the certificate followed next by the public key and finally the private key. Once all the data has been received by the NCP a 4th command is sent by the host indicating to push the data into permanent storage.

In 802.15.4 specification, it mentions the PHY shall provide the capability to perform CCA. Zigbee stack is based on 802.15.4, what is the CCA threshold for Zigbee device? The default CCA threshold of GB868 SubGHz is -87dBm, and the default CCA threshold of 2.4GHz is -75dBm.

As you may know there is a MFG token (TOKEN_MFG_CCA_THRESHOLD) can be set to override the default CCA threshold(s) by setting this token if your design uses a Low-Noise Amplifier (LNA). An LNA changes the gain on the radio input which results in the radio “seeing” a different energy level than if no LNA was used. If you use an LNA in your design, you will need add the gain of LNA to the default CCA threshold, then write to this MFG token. Please refer to the AN961 for more information.

You may have question where the two default values come from? Actually, these two values are defined by specification, 802.15.4-2006 mentioned the ED threshold shall correspond to a received signal power of at most 10 dB above the specified receiver sensitivity. Sensitivity requirement for 2.4 GHz is -85dBm, hence CCA threshold = -75dBm, GB868 sensitivity is -97dBm per Zigbee R22 spec, hence CCA threshold =-87dBm.

In 8.2.15.4 specification, it mentions the PHY shall provide the capability to perform CCA. Zigbee stack is based on 802.15.4, what is the CCA threshold for Zigbee device? The default CCA threshold of GB868 SubGHz is -87dBm, and the default CCA threshold of 2.4GHz is -75dBm.

As you may know there is a MFG token (TOKEN_MFG_CCA_THRESHOLD) can be set to override the default CCA threshold(s) by setting this token if your design uses a Low-Noise Amplifier (LNA). An LNA changes the gain on the radio input which results in the radio “seeing” a different energy level than if no LNA was used. If you use an LNA in your design, you will need add the gain of LNA to the default CCA threshold, then write to this MFG token. Please refer to the AN961 for more information.

You may have question where the two default values come from? Actually, these two values are defined by specification, 802.15.4-2006 mentioned the ED threshold shall correspond to a received signal power of at most 10 dB above the specified receiver sensitivity. Sensitivity requirement for 2.4 GHz is -85dBm, hence CCA threshold = -75dBm, GB868 sensitivity is -97dBm per Zigbee R22 spec, hence CCA threshold =-87dBm.

You may meet problem when you develop the project with IAS zone server in EmberZnet 6.3.1. The IAS zone server plugin is grayed and can't be chose even you enable the IAS zone server cluster in *.isc file.

This is a known bug in EmberZnet 6.3.1, and it is easy to fix it by deleting `emberAfWwahAppEventRetryManagerConfigBackoffParamsCallback`and `emberAfWwahAppEventRetryManagerSetBackoffParamsToDefault` from the implemented callbacks in plugin.properties.

I also attach the plugin.properties, so that you can easily to replace the plugin.properties in C:\SiliconLabs\SimplicityStudio\v4\developer\sdks\gecko_sdk_suite\v2.3\protocol\zigbee\app\framework\plugin\ias-zone-server\.

After you do that, restart the Simplicity Stduio, and the  IAS Zone Server plugin is appeared now.

Please feel free to contact Silicon Labs if you have further problem. 

You may meet problem when you develop the project with IAS zone server in EmberZnet 6.3.1. The IAS zone server plugin is grayed and can't be chose even you enable the IAS zone server cluster in *.isc file.

This is a known bug in EmberZnet 6.3.1, and it is easy to fix it by deleting `emberAfWwahAppEventRetryManagerConfigBackoffParamsCallback`and `emberAfWwahAppEventRetryManagerSetBackoffParamsToDefault` from the implemented callbacks in plugin.properties.

I also attach the plugin.properties, so that you can easily to replace the plugin.properties in C:\SiliconLabs\SimplicityStudio\v4\developer\sdks\gecko_sdk_suite\v2.3\protocol\zigbee\app\framework\plugin\ias-zone-server\.

After you do that, restart the Simplicity Stduio, and the  IAS Zone Server plugin is appeared now.

Please feel free to contact Silicon Labs if you have further problem. 

You may meet problem when you develop the project with IAS zone server in EmberZnet 6.3.1. The IAS zone server plugin is grayed and can't be chose even you enable the IAS zone server cluster in *.isc file.

This is a known bug in EmberZnet 6.3.1, and it is easy to fix it by deleting `emberAfWwahAppEventRetryManagerConfigBackoffParamsCallback`and `emberAfWwahAppEventRetryManagerSetBackoffParamsToDefault` from the implemented callbacks in plugin.properties.

I also attach the plugin.properties, so that you can easily to replace the plugin.properties in C:\SiliconLabs\SimplicityStudio\v4\developer\sdks\gecko_sdk_suite\v2.3\protocol\zigbee\app\framework\plugin\ias-zone-server\.

After you do that, restart the Simplicity Stduio, and the  IAS Zone Server plugin is appeared now.

Please feel free to contact Silicon Labs if you have further problem. 

You may meet problem when you develop the project with IAS zone server in EmberZnet 6.3.1. The IAS zone server plugin is grayed and can't be chose even you enable the IAS zone server cluster in *.isc file.

This is a known bug in EmberZnet 6.3.1, and it is easy to fix it by deleting `emberAfWwahAppEventRetryManagerConfigBackoffParamsCallback`and `emberAfWwahAppEventRetryManagerSetBackoffParamsToDefault` from the implemented callbacks in plugin.properties.

I also attach the plugin.properties, so that you can easily to replace the plugin.properties in C:\SiliconLabs\SimplicityStudio\v4\developer\sdks\gecko_sdk_suite\v2.3\protocol\zigbee\app\framework\plugin\ias-zone-server\.

After you do that, restart the Simplicity Stduio, and the  IAS Zone Server plugin is appeared now.

Please feel free to contact Silicon Labs if you have further problem. 

You may meet problem when you develop the project with IAS zone server in EmberZnet 6.3.1. The IAS zone server plugin is grayed and can't be chose even you enable the IAS zone server cluster in *.isc file.

This is a known bug in EmberZnet 6.3.1, and it is easy to fix it by deleting `emberAfWwahAppEventRetryManagerConfigBackoffParamsCallback`and `emberAfWwahAppEventRetryManagerSetBackoffParamsToDefault` from the implemented callbacks in plugin.properties.

I also attach the plugin.properties, so that you can easily to replace the plugin.properties in C:\SiliconLabs\SimplicityStudio\v4\developer\sdks\gecko_sdk_suite\v2.3\protocol\zigbee\app\framework\plugin\ias-zone-server\.

After you do that, restart the Simplicity Stduio, and the  IAS Zone Server plugin is appeared now.

Please feel free to contact Silicon Labs if you have further problem.