Matter Light Bulb Crashes when adding multiple ON/OFF endpoints

Hi All,

Setup Used

  • nRF Connect SDK v2.7
  • VsCode 
  • Ubuntu 20.04
  • Google Nest Hub2 
  • Android 12 Smartphone + Google Home App
  • nRF 5340 DK



Endpoint-0 -------------- Root

Endpoint-1 ------------- MA-LightDimmer

The above default combination works and device is successfully connect and controlled using Google Nest + SmartPhone.


Endpoint-0 -------------- Root

Endpoint-1 ------------- MA-LightDimmer

Endpoint-2 -------------- MA-OnOffLight

The above default combination works and device is successfully connect and controlled using Google Nest + SmartPhone.

But as soon as I add another endpoint-3. The nRF-5340-DK restarts/crashes unexpedlty and commissioning falis.

Endpoint-0 -------------- Root

Endpoint-1 ------------- MA-LightDimmer

Endpoint-2 -------------- MA-OnOffLight

Endpoint-3 -------------- MA-OnOffLight

I am using nRF Matter-Light-Bulb sample and trying to add new endpoints (endpoint-3) to the project. The project compiles and flashed to my nRF-5340-DK board. When I try to connect/commission it crashes/restarts the nRF-5340-DK board and On Google-Nest-Hub2 the last status is 'Connecting device to Google Home'. As you can see from the error logs. the device restarted unexpectedly.

I: 90300 [EM]<<< [E:28473r S:23036 M:198639457 (Ack:58483730)] (S) Msg TX to 1:000000007B91329D [7730] [UDP:[fd10:8db5:6457:d759:710d:8560:da8:18e8]:52994] --- Type 0001:05 (IM:ReportData)
I: 90437 [EM]>>> [E:28473r S:23036 M:58483731 (Ack:198639457)] (S) Msg RX from 1:000000007B91329D [7730] --- Type 0000:10 (SecureChannel:StandaloneAck)
I: 90454 [EM]>>> [E:28474r S:23036 M:58483732] (S) Msg RX from 1:000000007B91329D [7730] --- Type 0001:0a (II: 90466 [EM]<<< [E:28474r S:23036 M:198639458 (Ack:58483732)] (S) Msg TX to 1:000000007B91329D [7730] [UDP:[fd10:8db5:6457:d759:710d:8560:da8:18e8]:52994] --- Type 0001:01 (IM:StatusResponse)
I: 90552 [EM]>>> [E:28474r S:23036 M:58483733 (Ack:198639458)] (S) Msg RX from 1:000000007B91329D [7730] --- Type 0001:08 (IM:InvokeCommandRequeI: 90566 [FS]GeneralCommissioning: Received ArmFailSafe (1s)
I: 90572 [EM]<<< [E:28474r S:23036 M:198639459 (Ack:58483733)] (S) Msg TX to 1:000000007B91329D [7730] [UDP:[fd10:8db5:6457:d759:710d:8560:da8:18e8]:52994] --- Type 0001:09 (IM:InvokeCommandResponse)
I: 90643 [EM]>>> [E:28474r S:23036 M:58483734 (Ack:198639459)] (S) Msg RX from 1:000000007B91329D [7730] --- Type 0000:10 (SecureChannel:StandalI: 91571 [FS]Fail-safe timer expired
E: 91574 [SVR]Failsafe timer expired
D: 91578 [IN]SecureSession[0x20004660]: MarkForEviction Type:1 LSID:'kPendingEviction'
D: 91593 [IN]SecureSession[0x20004660]: Released - Type:1 LSID:23035
E: 91599 [SVR]Commissioning failed (attempt 1): 32

Note:
- I didn't made any-other firmware change to the default(base) matter-light-bulb sample. Other than, adding two new endpoint-2 and endpoint-3 using 'west zap-gui' and generating the updated files using 'west zap-generated' and the project compiles.

- The restarting/crash always happens when endpoint-3 is used.

- I also tried increasing the stack and heap in prj.conf. But it does not help.

CONFIG_MAIN_STACK_SIZE=8192

CONFIG_HEAP_MEM_POOL_SIZE=16384

CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=4096

- I have also uploaded my project + Full-Logs to the Google-Drive-Link

https://drive.google.com/drive/folders/1_R4OKHOeulXDlRZcNGKJnku7eot0Y5fu?usp=sharing

Parents Reply
  • Hi,

    There seems no logs in the attached Google Drive link, but according to the provided logs above I can say, that there is no crash.

    The failsafe timer expired and caused the commissioning to fail, and as a consequence, the device should reboot to open the new commissioning window once again, so it restarted as expected. Unfortunately, I can't see the reason on those logs, it may fail for many reasons and finish this way. Please share the full logs for further check.
    Best regards,

    Charlie

Children
Related