-
-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[7.4.x] SLZB-06M inconsistencies when setting config IDs on startup #90
Comments
Its strange that is only happening with SLZB-06M, and for settings that are already set! however I can easily reproduce here on 7.4.1. Also tried with 7.4.2 I only get a single error (which is actually the only value that is changed compared to firmware):
Now I have updated settings to match ZBDongle-E (7.4.3 doesnt appear to have any changes in Zigbee firmware compared to 7.4.2) Let me know if that resolves the issues for people. |
This is happening on the Skyconnect as well on 7.4.x (all tested). `[2024-05-10 21:35:31] info: zh:ember:ezsp: ======== EZSP started ======== [2024-05-10 21:35:32] warning: zh:ember: [EzspConfigId] Failed to SET "APS_UNICAST_MESSAGE_COUNT" TO "32" with status=ERROR_OUT_OF_MEMORY. Firmware value will be used instead. Thanks |
Hi, just updated today and saw this in the logs. any update on fixing it? |
Seems Silabs made some changes to their firmware which made a lot of values impossible to increase, only decrease. In 8.0.x, it appears, most can also no longer be set to the same value as the firmware's built-in. Remains the issues of the SLZB-06M that sets these values just fine in 7.4.x except sometimes after an NCP reset, when it fails on multiple ones (the ones in first post here). Seems there is an actual issue in this specific scenario (some improper state after reset? might be linked to stress prior to reset). |
Is this still happening with updated config, that sets all values in OP as default? Which incidentally was the default config on my ZBDongle-E builds for a long time. |
It is, but on restart, after an error triggered said restart (seems to be the pattern anyway); as described in first post. Might be more about memory, than the configs themselves. |
Reporting this since I've seen a few logs now, from different users, that show this. (I don't have the device myself, so I can't run any test.)
Seems something is going wrong, that first one is the first being set during startup sequence, and is set to the same as the firmware default. Not sure why it would return as out of memory at that point?
I'm guessing the
ERROR_INVALID_VALUE
forSOURCE_ROUTE_TABLE_SIZE
is a bug in silabs firmware, reporting the wrong status, and is likely reallyERROR_OUT_OF_MEMORY
too.When the device is in a state where it does this during startup (it doesn't always do it seems like), it then misbehaves in various ways.
Any ideas?
The text was updated successfully, but these errors were encountered: