The stack allocate the unused ram for The Packet buffer and stack tables on NCP. EZSP_ERROR_OUT_OF_MEMORY means the unused ram size is not enough for your buffer/table configration. Please check what is the unused ram size of your project.
Some recommendations when building firmware images for production:
Build a single manufacturing hex file for each device with bootloader, application image, flash protection patches, and any tokens.
Enable write protection on the bootloader flash area (0-0x4000) by clearing the lower eight bits of the first byte in the lock bits page (0x0fe04000). Each bit represents 2KB of flash, so 8 bits represents 16KB total for the standard bootloader: --patch 0x0fe04000:0x00
Disable the debug port on the EFR32MG1 by clearing the four LSBs of the DLW register in the lock bits page. This prevents debugger access from reading/writing to the device. Debug access can only be gained again by erasing the device. --patch 0x0fe041FC:0xF0
Program the AES/encryption key (if applicable) and the ECDSA public key tokens. These can be in the same token file as any other tokens you are programming. --tokenfile keyfile.txt
Lock the lock bits page on EFR32MG1 by clearing bit 1 of the ULW register in the lock bits page. This is a requirement to secure the AES and ECDSA tokens which reside in the lock bits page. --patch 0x0fe041F8:0xFD
It is possible to combine these patches into a single hex file for manufacturing with a Simplicity Commander command, which can be put into a batch file or post-build script. For example:
Some recommendations when building firmware images for production:
Build a single manufacturing hex file for each device with bootloader, application image, flash protection patches, and any tokens.
Enable write protection on the bootloader flash area (0-0x4000) by clearing the lower eight bits of the first byte in the lock bits page (0x0fe04000). Each bit represents 2KB of flash, so 8 bits represents 16KB total for the standard bootloader: --patch 0x0fe04000:0x00
Disable the debug port on the EFR32MG1 by clearing the four LSBs of the DLW register in the lock bits page. This prevents debugger access from reading/writing to the device. Debug access can only be gained again by erasing the device. --patch 0x0fe041FC:0xF0
Program the AES/encryption key (if applicable) and the ECDSA public key tokens. These can be in the same token file as any other tokens you are programming. --tokenfile keyfile.txt
Lock the lock bits page on EFR32MG1 by clearing bit 1 of the ULW register in the lock bits page. This is a requirement to secure the AES and ECDSA tokens which reside in the lock bits page. --patch 0x0fe041F8:0xFD
It is possible to combine these patches into a single hex file for manufacturing with a Simplicity Commander command, which can be put into a batch file or post-build script. For example:
Network analyer may parse this command incorrectly. could you provide the setps to reproduce this issue. I will setup a reproducer for furrher investigation.
EmberZnet doesn't handle frequency agility in stack level. You can try to deal with it in your application. Try to refer to discussions in " How can i test frequency agility in zigbee ? "
If the isd file is too big, Simplicity Studio can't open the whole file directly. but you can use the below way to open the selected interval of the isd file.
1. open the isd file with Simplicity Studio, it shows as below.
2. disable the "Auto-zoom' option.
3.drag the mouse from start timestamp to the end timestamp to select the interval.
4. click Open interval button, the selected interval of the isd file will be opened.
5.Click the "Save Segments" to save this segment of the packet trace.
The content listed below is grouped together into categories to make it easier for you to find what you are looking for. The popular KBAs for each category have been listed as below on this page, more KBAs and relevant documentation can be found under other child page for each category if you click on the name of each category.
The category index numbers are as follows:
Zigbee General
Zigbee 3.0
Zigbee Routing
Zigbee Security
Zigbee Gateway/Trust Center
Zigbee Host/NCP
Zigbee End Device
Zigbee Bootloader
Zigbee OTA
Zigbee Token
Zigbee DMP
Zigbee Green Power
Zigbee Smart Energy
Zigbee Certification
LQI/RSSI
Sleep
RF
Plugins
Peripheral
Dev Tools
Hardware
Hands on
EM35x
Thread
Chinese
Note: Do you want to get automatic notifications when new content is added to the list? Just click the Follow button in upper right corner to subscribe to email notifications. We will make comments when new content is created to trigger those notifications.
