Adjust some parameters for MG24

[darkxst]

No description provided.

[jorisvervuurt]

Hi @darkxst, I was wondering why SL_ZIGBEE_MAX_END_DEVICE_CHILDREN was reduced from 64 to 32? Is this as a result of issues?

[darkxst]

it was causing issues on EFR32MG24 switching from router back to NCP firmware.

[Nerivec]

@darkxst I haven't seen any troubles on MG24 (slzb07mg24 and tubeszb mgm24) with switching (and I've switched a lot), but I do have the same configs on router and ncp builds. You might want to try aligning both builds instead.
Example: https://github.com/Nerivec/silabs-firmware-builder/blob/v2024.6.2-update6/manifests/smlight/smlight_slzb07Mg24_zigbee_router.yaml

---

I did notice some troubles with saved network data though. If you have a NCP network saved on the adapter, then flash the router build, you may end up with some issues (not always, depends on previous tables usage) when pairing (more specifically, when binding).
That affects all series, not just MG24.
Easiest way to fix it is to clear the NVM3 (cleaner anyway).
I built support for it into ember-zli but you can find the GBLs here if needed.

[darkxst]

Certain configurations cause corrrupt NVM3 when switching. However I have since been advised by Silabs that we should be clearing NVM3 whenever switching firmware types. I have a simple app that clears nvm3 ( bit faster than your brute force method) that will be implementing.

btw they are also looking into software flow control issues on 2024.12.x, they were not previously aware of this issues!