Configuration of the firmware

[pipiche38]

I'm interresting to understand how the configuration looks like for the firmware. For exemple routing table ? source routing ? tx Power .... ?

IS there any source that we can have access to as regards to the firmware provided in the data/ folder ?

[Hedda]

@pipiche38 FYI, some of the other community firmware developers do provide some more information about those, see example:

https://github.com/grobasoz/zigbee-firmware/ -> https://github.com/grobasoz/zigbee-firmware/blob/master/EFR32%20Series%201/README.md

https://github.com/xsp1989/zigbeeFirmware/ -> https://github.com/xsp1989/zigbeeFirmware/blob/master/firmware/Zigbee3.0_Dongle-NoSigned/EZSP/README.md

https://github.com/zha-ng/EZSP-Firmware

https://github.com/MattWestb/EFR32-FW

You can also figure out some of the detailed based on the common abbreviations used in the files in community builds:

Abbreviations legend:

Commonly used shorthand and acronyms community firmware developers use in image file names for Silabs based adapters:

• ncp = NCP (Network Co-Processor) - if Silabs means standard NCP design with EZSP (EmberZNet Serial Protocol) host interface.
• rcp = RCP (Radio Co-Processor) made for use offload to host CPU daemon called cpcd to zigbeed (and OpenThread daemon), see -> https://github.com/zigpy/zigpy/discussions/894
• s2 = EFR32 Series 2 (eg. EFR32MG2x such as EFR32MG21)
• s1 = EFR32 Series 1 (eg. EFR32MG1x)
• F1024 = 1024k Flash Size
• F512 = 512k Flash Size
• F256 = 256k Flash Size
• com = Combined (necessary for EFR32 Series 1)
• USW - Uart interface, Software Flow Control
• uart = UART interface
• nsw = no flow control
• sw = software flow control (XON/XOFF flow control)
• hw = hardware flow control (RTS/CTS flow control)
• 655 / 678 / 679 = EmberZNet Version which also indoicate version for EZSP (EmberZNet Serial Protocol)
• 115200 = Baud rate speed set to 115200
• 57600 = Baud rate speed set to 57600
• std = Standalone
• btl = Bootloader
• pb0-pb1 = Port used for TX/TXD (Transceive Data) and RX/RXD (Receive Data)
• pa0 = Bootloader GPIO Activation

[Hedda]

IS there any source that we can have access to as regards to the firmware provided in the data/ folder ?

Oh, and you guys might also be interested in these related discussions regarding a standard way of building and compiling FW:

https://github.com/zigpy/zigpy/discussions/1042

https://github.com/grobasoz/zigbee-firmware/issues/30

[Hedda]

Ah, and example app code is on Silicon Labs GitHub for their Gecko SDK:

https://github.com/SiliconLabs/gecko_sdk/tree/gsdk_4.1/protocol/zigbee/

https://github.com/SiliconLabs/gecko_sdk/releases

However I think that you still first need to buy and register one of the official Silicon Labs compatible Zigbee development kit (dev kit) or starter kits to your (free) silabs account in order to get the license needed to access Zigbee EmberZNet SDK, see https://www.silabs.com/development-tools/wireless where I think the least expensive is the EFR32xG22 devkit for $99 (US-dollar), see https://www.cnx-software.com/2020/06/25/efr32xg22-wireless-gecko-starter-kit-targets-bluetooth-zigbee-and-proprietary-wireless-development/?amp=1

Again, the Gecko SDK (GSDK) is now available on Silicon Labs GitHub (which it was not before) but I believe that you might still need to have registered at least one Zigbee development board / starter kit to show that you own one of their official products:

https://github.com/SiliconLabs/gecko_sdk

https://github.com/SiliconLabs