Out of memory (CHIP error 0x0b) when trying to commission Window Covering sample with GHA

RE: Out of memory (CHIP error 0x0b) when trying to commission Window Covering sample with GHA

abollaert — Fri, 07 Oct 2022 13:28:40 GMT

Hi Charlie,

in the mean time I took the window covering sample from the NCS v2.1.0 and backported it to the version that gets used for the examples used by the Google Home devguide (https://developers.home.google.com/matter/vendors/nordic-semiconductor). It appears to be using NCS version 5ea8f7fa9 (pretty speciflcally), and connected home ip version 6975d85c4.

So I patched up the CMakeLists to use said version of the connected home ip codebase in combination with said NCS version, patched up the code for missing bits and pieces, and it appears to be working (sort of, because I still see a whole bunch of 0x0b errors flying by). But at least I can set attributes from my Google Home app and Nest Hub.

So either something is broken in NCS, or GHA, I don't know, seems to have something to do with the counter retransmissions I think, haven't read the spec in detail yet.

Let me know what you find and have a nice weekend,

-Alex

RE: Out of memory (CHIP error 0x0b) when trying to commission Window Covering sample with GHA

Charlie — Fri, 07 Oct 2022 13:20:48 GMT

Hi Alex,

I will check with our development team to see if they can repeat this issue with Google Nest Hub 2.

Thanks for reporting this issue to us.

Best regards,

Charlie

RE: Out of memory (CHIP error 0x0b) when trying to commission Window Covering sample with GHA

abollaert — Thu, 06 Oct 2022 12:07:39 GMT

Did a bit more digging, and I don't think the memory error is the cause for the commissioning failure.

The commissioning succeeds (in that it gets added to my devices in google home), but interaction with the device always fails with an error "operation discovery failed: 32". In Google Home the device gets marked as "unavailable".

D: 119459 [CSM]UpdatePeerAddress: No existing OperationalSessionSetup instance found 
D: 119467 [CTL]OperationalSessionSetup[1:0000000056E421FF]: State change 1 --> 2 
I: 119475 [DIS]Resolving 0E9E8F8AAAEC283A:0000000056E421FF ... 
I: 119675 [DIS]Checking node lookup status after 201 ms 
D: 119819 [EM]Retransmitting MessageCounter:107169467 on exchange 8696r Send Cnt 2 
I: 119827 [IN]Sending encrypted msg 0x20005134 with MessageCounter:107169467 to 0x0000000056E421FF (1) at monotonic time: 000000000001D412 msec 
D: 120474 [EM]Retransmitting MessageCounter:107169467 on exchange 8696r Send Cnt 3 
I: 120481 [IN]Sending encrypted msg 0x20005134 with MessageCounter:107169467 to 0x0000000056E421FF (1) at monotonic time: 000000000001D6A1 msec 
D: 121500 [EM]Retransmitting MessageCounter:107169467 on exchange 8696r Send Cnt 4 
I: 121508 [IN]Sending encrypted msg 0x20005134 with MessageCounter:107169467 to 0x0000000056E421FF (1) at monotonic time: 000000000001DAA3 msec 
E: 123124 [EM]Failed to Send CHIP MessageCounter:107169467 on exchange 8696r sendCount: 4 max retries: 4 
D: 123133 [IN]SecureSession[0x20003670]: MarkAsDefunct Type:2 LSID:7749 
I: 123139 [SC]SecureSession[0x20003670]: Moving from state 'kActive' --> 'kDefunct' 
I: 134475 [DIS]Checking node lookup status after 15001 ms 
E: 134480 [DIS]OperationalSessionSetup[1:0000000056E421FF]: operational discovery failed: 32

For reference, my setup is an nRF52840 devkit for the sample, a Google Nest Hub 2 as the border router, commissioner and controller.

Kind regards,

-Alex

RE: Out of memory (CHIP error 0x0b) when trying to commission Window Covering sample with GHA

abollaert — Thu, 06 Oct 2022 09:59:11 GMT

I also did another test, this time using the light bulb sample, and I get the same issue. In fact the only sample I ever got working with Google Home is the one the Google developer guide points to (https://developers.home.google.com/matter/vendors/nordic-semiconductor).

Both samples I've tried included in the NCS itself seem to fail with CHIP error 0xb, for example this is the lighting app sample:

devzone.nordicsemi.com/.../log_2D00_lighting.txt

It first states it's "Generating Reports", and then you get an 0x0b.

So there must be some difference between the sample the Google development guide points to, and the (more recent) NCS samples, perhaps just a version difference, don't know.

Kind regards,

-Alex

RE: Out of memory (CHIP error 0x0b) when trying to commission Window Covering sample with GHA

abollaert — Thu, 06 Oct 2022 07:50:56 GMT

Hi Charlie,

sorry for the somewhat late reply, was working on something else the last few days.

I tested using the chiptool and that worked fine, but this test was specifically a test with Google Home.

I tested using the latest NCS (v2.1.0) and I also tested using main (v2.1.99). Results were the same for both (CHIP error 0xb when retrieving data from clusters).

Log file:

devzone.nordicsemi.com/.../5125.log.txt

Project configuration:

# General.
CONFIG_STD_CPP14=y
CONFIG_DK_LIBRARY=y
CONFIG_PWM=y

# OpenThread.
CONFIG_OPENTHREAD_PANID=4660
CONFIG_OPENTHREAD_CHANNEL=15
CONFIG_OPENTHREAD_NETWORK_NAME="OpenThread"
CONFIG_OPENTHREAD_XPANID="00:11:22:33:44:55:66:77"

# Bluetooth overrides
CONFIG_BT_DEVICE_NAME="MatterPOC"

# CHIP configuration
CONFIG_CHIP=y
CONFIG_CHIP_PROJECT_CONFIG="src/main/include/CHIPProjectConfig.h"
CONFIG_CHIP_DEVICE_PRODUCT_ID=32784

# Enable CHIP pairing automatically on application start.
CONFIG_CHIP_ENABLE_PAIRING_AUTOSTART=y

# Disable various debug options to reduce footprint.
CONFIG_SHELL=n
CONFIG_LOG_MODE_IMMEDIATE=n
CONFIG_LOG_MODE_MINIMAL=y
CONFIG_ASSERT_VERBOSE=n
CONFIG_ASSERT_NO_FILE_INFO=y
CONFIG_PRINTK=n
CONFIG_PRINTK_SYNC=n
CONFIG_THREAD_NAME=n
CONFIG_MATTER_LOG_LEVEL_INF=y

Kind regards and thanks,

-Alexander

RE: Out of memory (CHIP error 0x0b) when trying to commission Window Covering sample with GHA

Charlie — Mon, 03 Oct 2022 09:09:06 GMT

Hi Alexander,

Thanks for the feedback about your test.

Have you tested with other platforms(like Apple Homekit, or the Matter development environment mentioned by the NCS document)?

Did you test with the latest NCS2.1.0? Can you share your modification and complete log file?

Best regards,

Charlie