Matter Light Switch Sample - Kernel panic

RE: Matter Light Switch Sample - Kernel panic

Tonyll — Wed, 12 Aug 2026 08:23:01 GMT

Hi Maria,

Many thanks for helping me with this, it is much appreciated.

Kind regards,

Tony

RE: Matter Light Switch Sample - Kernel panic

Maria Gilje — Wed, 12 Aug 2026 08:05:58 GMT

Hi Tony,

Thank you for checking that the Matter versions matched.

Our developers confirmed that the binding table printing has a bug and they will prepare a bugfix. It will not be patched into NCS, but the relevant commit can be applied manually. In essence, the fix includes verifying that entry.clusterId.HasValue() is true before trying to fetch the ID.

Thank you for bringing this to our attention.

Best regards,

Maria

RE: Matter Light Switch Sample - Kernel panic

Tonyll — Tue, 11 Aug 2026 11:19:13 GMT

Hi Maria,

I have looked further into the Matter 1.5 standard.

My understanding is that a binding can exist which specifies the end node (or group) without giving a cluster number. The binding node app will then be able to control any available cluster on the end node or group.

The image shows an example given in the Matter spec where a group is specified but the nodes and clusters are omitted.

The HA Matter server creates a single binding table where the controlling node and end node are included but the cluster number is omitted. I thank this is correct but is why the "print binding table" function fails becaue it expects a cluster number.

Best regards

Tony

RE: Matter Light Switch Sample - Kernel panic

Tonyll — Tue, 11 Aug 2026 09:05:38 GMT

Hi Maria,

HA's Matter Server which creates the bindings and allows all relevant clusters to be bound with one command is using "matter.js" (https://github.com/matter-js/matter.js) and is based on Matter 1.5.1

The work around at the moment is to not use the "all relevant" option but to create two bindings, one for onoff and one for level. The sample app works fine with the "all relevant" binding option and controls the light for both onoff and level, it is only when the "print binding table" gets called that the fault occurs.

Best regards

Tony

RE: Matter Light Switch Sample - Kernel panic

Maria Gilje — Tue, 11 Aug 2026 07:39:51 GMT

Hi Tony,

Thank you for sharing your status. Do you know which Matter version HA and the light are using? nRF Connect SDK v3.4.0 is using Matter v1.5.0, so I want to check if there is some incompatibility there.

Best regards,

Maria

RE: Matter Light Switch Sample - Kernel panic

Tonyll — Wed, 05 Aug 2026 15:58:35 GMT

Hi Maria

I've made some progress from the information you sent.

If I comment-out the call to print the binding table (in binding_handler.cpp) then the error doesn't occur. I couldn't get the compiler to recognise .ValueOr().

Also I checked the binding process using Home Assistant.

HA allows binding to all eligible clusters. This works initially but fails wnen the board is reset and the binding table print is called. Works find if the print binding table is not called.

If only the on/off cluster (06) is specified with HA then the print binding table works OK.

Obviously binding to more than one cluster needs to be possible so the print binding table does need to be able to handle this.

Regards

Tony

RE: Matter Light Switch Sample - Kernel panic

Maria Gilje — Wed, 05 Aug 2026 13:26:22 GMT

Hi Tony,

I have not been able to reproduce this issue, but what I have asked for verification on if it is a possible fix, is to use .ValueOr() instead of .value() on the clusterId here.

Best regards,

Maria

RE: Matter Light Switch Sample - Kernel panic

Tonyll — Wed, 05 Aug 2026 08:57:33 GMT

Thanks Maria,

Do you have a solution or a work around that I can use to get a working device?

Thanks Tony

RE: Matter Light Switch Sample - Kernel panic

Maria Gilje — Fri, 31 Jul 2026 12:39:52 GMT

Hi Tony,

My apologies for the delay. We currently have reduced staffing due to summer holidays.

The code is aborted when printing the information for the bound device, that is here: https://github.com/nrfconnect/sdk-nrf/blob/v3.4.0/samples/matter/common/src/binding/binding_handler.cpp#L123-L129. Preliminary investigation suggests that this is because the switch has no cluster ID saved for the light in the binding table. I will forward this finding internally to get a second opinion on this issue.

[quote user="Tonyll"]

I found the addr2line doesn't run from nRF Connect as given in Lesson 2, (vscode for windows with sdk 3.4.0 installed, I needed to find the program in the toolchain directory and run

c:\ncs\toolchains\dcbdc366a1\opt\zephyr-sdk\gnu\arm-zephyr-eabi\bin\arm-zephyr-eabi-addr2line -e build_dk/light_switch/zephyr/zephyr.elf 0x0001cb54

Also the zephyr.elf file is in a sub directory of the build folder under the project name (different from Lesson 2)

[/quote]

The specific method is described in more detail in exercise 2, but I do notice that the path in the exercise is missing the "gnu" directory. I'll report this internally.

Best regards,

Maria

RE: Matter Light Switch Sample - Kernel panic

Tonyll — Fri, 31 Jul 2026 08:36:54 GMT

Please can someone respond to my enquiry

Regards

Tony

RE: Matter Light Switch Sample - Kernel panic

Tonyll — Wed, 29 Jul 2026 09:31:50 GMT

Any feedback from my addr2line information?

Regards

Tony

RE: Matter Light Switch Sample - Kernel panic

Tonyll — Fri, 24 Jul 2026 14:26:39 GMT

Hi,

The output of addr2line is - C:/ncs/v3.4.0/zephyr/lib/libc/common/source/stdlib/abort.c:14

I found the addr2line doesn't run from nRF Connect as given in Lesson 2, (vscode for windows with sdk 3.4.0 installed, I needed to find the program in the toolchain directory and run

c:\ncs\toolchains\dcbdc366a1\opt\zephyr-sdk\gnu\arm-zephyr-eabi\bin\arm-zephyr-eabi-addr2line -e build_dk/light_switch/zephyr/zephyr.elf 0x0001cb54

Also the zephyr.elf file is in a sub directory of the build folder under the project name (different from Lesson 2)

Best regards

Tony

RE: Matter Light Switch Sample - Kernel panic

Maria Gilje — Fri, 24 Jul 2026 12:32:05 GMT

Hello,

[quote user=""]E: Faulting instruction address (r15/pc): 0x0001cb54[/quote]

Could you please follow the Addr2line method described in nRF Connect SDK Intermediate Lesson 2 to find out exactly where the fatal error occurs?

Best regards,

Maria