Zigbee_OnOff_Router_NVM example on WB55CGU6 custom board and Tuya Zigbee network

[ginobambino]

Hi. I`m using Zigbee_OnOff_Router_NVM example on WB55CGU6 custom board with existing Zigbee network in my home, but seems that my device not act as router. I mean that it not extends range of my network. What i do wrong?

i checked:

• Set config.startupControl to ZbStartTypeJoin on M4 side.
• Flash Zigbee FFD copro binary on M0 side

 

[tl_mbox.c][OutputDbgTrace][829] sys evt: 0xFF
[tl_mbox.c][OutputDbgTrace][830] subevtcode: 0x9200
[tl_mbox.c][OutputDbgTrace][833] payload: 00
[tl_mbox.c][OutputDbgTrace][838]
\x1B[0m[M4 APPLICATION] APP_ZIGBEE_Init
\x1B[0m[M4 APPLICATION] **********************************************************
\x1B[0m[M4 APPLICATION] WIRELESS COPROCESSOR FW:
\x1B[0m[M4 APPLICATION] VERSION ID = 1.20.0
\x1B[0m[M4 APPLICATION] FW Type : FFD Zigbee stack
\x1B[0m[M4 APPLICATION] Application flashed: ..
\x1B[0m[M4 APPLICATION] Channel used: 13
\x1B[0m[M4 APPLICATION] Link Key: ZigBeeAlliance09
\x1B[0m[M4 APPLICATION] Link Key value: 5a 69 67 42 65 65 41 6c 6c 69 61 6e 63 65 30 39
\x1B[0m[M4 APPLICATION] Clusters allocated are:
\x1B[0m[M4 APPLICATION] OnOff Server on Endpoint 17
\x1B[0m[M4 APPLICATION] **********************************************************
\x1B[0m[M4 APPLICATION] Flash starting address = 8070000
\x1B[0m[M4 APPLICATION] EE_init status = 0
\x1B[0;92m [M0] \x1B[0;92m[00000000.000][API] Init_ZigbeeStack_Infrastructure
\x1B[0;92m [M0] \x1B[0;92m[00000000.000][LLD] !! PHY_allocateRxBuffer() FAILED. Status: 0x7
\x1B[0m[M4 APPLICATION] APP_ZIGBEE_StackLayersInit
\x1B[0;92m [M0] \x1B[0;92m[00000000.000][LLD] !! PHY_allocateRxBuffer() FAILED. Status: 0x7
\x1B[0m[M4 APPLICATION] Retrieving persistent data from FLASH
\x1B[0m[M4 APPLICATION] READ PERSISTENT DATA LEN = 15
\x1B[0m[M4 APPLICATION] APP_ZIGBEE_ZbStartupPersist: restoring stack persistence
\x1B[0;92m [M0] \x1B[0;92m[00000000.000][LLD] !! PHY_allocateRxBuffer() FAILED. Status: 0x7
\x1B[0;92m [M0] \x1B[0;92m[00000000.000][LLD] !! PHY_allocateRxBuffer() FAILED. Status: 0x7
\x1B[0m[M4 APPLICATION] ZbStartupPersist: FAILED to restart from persistence with status: 0xc1
\x1B[0m[M4 APPLICATION] Network config : APP_STARTUP_CENTRALIZED_ROUTER
\x1B[0;92m [M0] \x1B[0;92m[00000000.018][PLATFORM] ZbNlmeResetReq : NLME-RESET.request (warmStart = 0)
\x1B[0;92m [M0] \x1B[0;92m[00000000.000][LLD] !! PHY_allocateRxBuffer() FAILED. Status: 0x7
\x1B[0;92m [M0] \x1B[0;92m[00000000.019][PLATFORM] zb_startup_join_nwk_disc : Attempting network discovery. Scans = 3, Duration = 4
\x1B[0;92m [M0] \x1B[0;92m[00000000.020][PLATFORM] nwk_scan_req : MLME-SCAN.request (wpan0): type=1, page=0, mask=0x07fff800, dur=4
\x1B[0;92m [M0] \x1B[0;92m[00000001.026][PLATFORM] zcl_persist_send_cache : Sending persist PUSH (ep = 242, cl = 0x0021, len = 6)
\x1B[0;92m [M0] \x1B[0;92m[00000004.239][PLATFORM] nwk_scan_req : MLME-SCAN.request (wpan0): type=1, page=0, mask=0x07fff800, dur=4
\x1B[0;92m [M0] \x1B[0;92m[00000008.458][PLATFORM] nwk_scan_req : MLME-SCAN.request (wpan0): type=1, page=0, mask=0x07fff800, dur=4
\x1B[0;92m [M0] \x1B[0;92m[00000000.000][LLD] !! PHY_allocateRxBuffer() FAILED. Status: 0x7
\x1B[0;92m [M0] \x1B[0;92m[00000000.018][PLATFORM] nwk_join_try_next : Associating (src=0x0080e125016cc576) to 0x0000 (epid = 0x3e2e977f3a1d8b40, lqi = 189, ch = 15)
\x1B[0;92m [M0] \x1B[0;92m[00000000.530][PLATFORM] ZbMonitorHandleTransKeyInd : Adding network key, sequence number = 0
\x1B[0;92m [M0] \x1B[0;92m[00000000.532][PLATFORM] ZbZdoDeviceAnnce : Sending Device_Annce for 0x389f
\x1B[0;92m [M0] \x1B[0;92m[00000000.643][PLATFORM] zcl_handle_command : ZCL Command: cluster=0x0000, dst=0xff, fc_manuf=0, fc_dir=0, cmd=0x00
\x1B[0;92m [M0] \x1B[0;92m[00000000.644][PLATFORM] ZbZclHandleReadAttr : Handling ZCL Read of cl = 0x0000, attr = 0x0004
\x1B[0;92m [M0] \x1B[0;92m[00000000.645][PLATFORM] ZbZclHandleReadAttr : Handling ZCL Read of cl = 0x0000, attr = 0x0000
\x1B[0;92m [M0] \x1B[0;92m[00000000.646][PLATFORM] ZbZclHandleReadAttr : Handling ZCL Read of cl = 0x0000, attr = 0x0001
\x1B[0;92m [M0] \x1B[0;92m[00000000.647][PLATFORM] ZbZclHandleReadAttr : Handling ZCL Read of cl = 0x0000, attr = 0x0005
\x1B[0;92m [M0] \x1B[0;92m[00000000.647][PLATFORM] ZbZclHandleReadAttr : Handling ZCL Read of cl = 0x0000, attr = 0x0007
\x1B[0;92m [M0] \x1B[0;92m[00000000.649][PLATFORM] zcl_handle_command : ZCL Command: cluster=0x0000, dst=0xff, fc_manuf=0, fc_dir=0, cmd=0x00
\x1B[0;92m [M0] \x1B[0;92m[00000000.649][PLATFORM] ZbZclHandleReadAttr : Handling ZCL Read of cl = 0x0000, attr = 0x0004
\x1B[0;92m [M0] \x1B[0;92m[00000000.650][PLATFORM] ZbZclHandleReadAttr : Handling ZCL Read of cl = 0x0000, attr = 0x0000
\x1B[0;92m [M0] \x1B[0;92m[00000000.651][PLATFORM] ZbZclHandleReadAttr : Handling ZCL Read of cl = 0x0000, attr = 0x0001
\x1B[0;92m [M0] \x1B[0;92m[00000000.652][PLATFORM] ZbZclHandleReadAttr : Handling ZCL Read of cl = 0x0000, attr = 0x0005
\x1B[0;92m [M0] \x1B[0;92m[00000000.653][PLATFORM] ZbZclHandleReadAttr : Handling ZCL Read of cl = 0x0000, attr = 0x0007
\x1B[0;92m [M0] \x1B[0;92m[00000001.176][PLATFORM] zcl_send_response : Sending Default Response, ep = 18 to 1, cl = 0x0006, dst = 0x0000, seq = 13, cmd = 0x06, status = 0xc3
\x1B[0;92m [M0] \x1B[0;92m[00000001.222][PLATFORM] zcl_handle_command : ZCL Command: cluster=0x0000, dst=0x11, fc_manuf=0, fc_dir=0, cmd=0x02
\x1B[0;92m [M0] \x1B[0;92m[00000001.223][PLATFORM] ZbZclAttrWrite : Failed to write cl = 0x0000, attr = 0xffde (cannot find attribute)
\x1B[0;92m [M0] \x1B[0;92m[00000002.589][PLATFORM] ZbApsmeAddEndpoint : Adding endpoint 254 (0xfe), profile = 0x0104, mem = 128
\x1B[0;92m [M0] \x1B[0;92m[00000002.590][PLATFORM] ZbZclAttrAppendList : Allocating attribute (cl=0x0003, attr=0xfffd) = 26
\x1B[0;92m [M0] \x1B[0;92m[00000002.591][PLATFORM] zcl_cluster_bind : Creating filter rule (endpoint = 254, profile = 0x0104, cluster = 0x0003)
\x1B[0;92m [M0] \x1B[0;92m[00000002.592][PLATFORM] zb_startup_join_findbind_start : Initiating Finding & Binding in 10000 mS
\x1B[0;92m [M0] \x1B[0;92m[00000002.597][PLATFORM] zcl_command_state_timeout : ZCL command request timed-out (zcl_seq=2, cluster=0x0003, dst_ep=255, status=0x94)
\x1B[0;92m [M0] \x1B[0;92m[00000012.593][PLATFORM] zb_findbind_identify_query_req : Sending Identify Query Request
\x1B[0;92m [M0] \x1B[0;92m[00000018.143][PLATFORM] ZbApsBindTick : ZDO IEEE ADDR request (0x0000) to verify address map for binding entry (0x847127fffec5afec)
\x1B[0;92m [M0] \x1B[0;92m[00000018.357][PLATFORM] ZbApsBindTick : ZDO IEEE ADDR request (0x0000) to verify address map for binding entry (0x847127fffec5afec)
\x1B[0;92m [M0] \x1B[0;92m[00000018.570][PLATFORM] ZbApsBindTick : ZDO IEEE ADDR request (0x0000) to verify address map for binding entry (0x847127fffec5afec)
\x1B[0;92m [M0] \x1B[0;92m[00000018.789][PLATFORM] ZbApsBindTick : ZDO IEEE ADDR request (0x0000) to verify address map for binding entry (0x847127fffec5afec)
\x1B[0;92m [M0] \x1B[0;92m[00000020.583][PLATFORM] zcl_handle_command : ZCL Command: cluster=0x0000, dst=0x11, fc_manuf=0, fc_dir=0, cmd=0x00
\x1B[0;92m [M0] \x1B[0;92m[00000020.584][PLATFORM] ZbZclHandleReadAttr : Handling ZCL Read of cl = 0x0000, attr = 0x0001
\x1B[0m[M4 APPLICATION] ZbStartup Callback (status = 0x00)
\x1B[0m[M4 APPLICATION] Binding entries created: 4
\x1B[0m[M4 APPLICATION] Notification to save persistent data requested from stack
\x1B[0m[M4 APPLICATION] APP_ZIGBEE_persist_save: Persistence written in cache RAM (num writes = 1) len=746
\x1B[0m[M4 APPLICATION] WRITTEN PERSISTENT DATA LEN = 746
\x1B[0m[M4 APPLICATION] APP_ZIGBEE_persist_save: Persistent data FLASHED
\x1B[0m[M4 APPLICATION] LED_RED ON
\x1B[0m[M4 APPLICATION] LED_RED OFF

[STTwo-32]

Hello @ginobambino 

I'm not able to understand exactly your issue. If you are toking about this error message " \x1B[0;92m [M0] \x1B[0;92m[00000000.000][LLD] !! PHY_allocateRxBuffer() FAILED. Status: 0x7". This is a Known regression on the Version 1.20.0 of the STM32CubeWB. It should be solved on the next release but Even if you are getting this message, the application behaves as expected and the OnOff Zigbee application remains fully functional. If you have another error please give more details. For the Bad signals, it can be due to Noisy environment, Interference from other devices, RF RX sensitivity or Complex Network topologie. 

For internal tracking, we have the internal ticket number 181532.

Best Regards.

STTwo-32

[ginobambino]

Thank you for your response, @STTwo-32. I agree that the application is working correctly and I have no errors. I posted the logs for informational purposes. As I mentioned earlier, my problem is that I cannot confirm that my device is functioning as a router in my home Zigbee network.

The image on the right shows the actual situation, where My_Dev is physically located roughly halfway between "WIATROLAP" and "GARAZ", but it is not visible in the Tuya app. Therefore, I conclude that it is not functioning as a router.

 Thanks for support.

[ginobambino]

I have tried many things regarding this topic, and it seems that with the Tuya application, only the on_off_switch is visible and responds to callbacks, meaning that it's possible to activate the output using the button in the application, and that's about it. This topic is explained quite thoroughly on the forum: https://community.st.com/t5/stm32-mcus-wireless/stm32wb5mm-dk-connecting-to-tuya-gateway-with-zigbee-part-2/td-p/630003