Failing to connect Connecting Light Bulb sample to HomePod Mini, possibly due to 46336 [SVR]Cannot load binding table

[CartBlanche]

I'm able to build and deploy my app to the nRF52840 board. 

On start-up the QR code link is listed and the pairing code and on my Android phone, under Bluetooth, I can see the board listed

But the logs then says...

533 [DL]CHIP task running
I: 536 [DIS]Updating services using commissioning mode 0
D: 541 [DL]Using Thread extended MAC for hostname.
D: 545 [DL]Using Thread extended MAC for hostname.
I: 550 [DIS]Advertise commission parameter vendorID=65521 productID=32772 discriminator=3840/15 cm=0
E: 559 [DIS]Failed to advertise extended commissionable node: 3
E: 565 [DIS]Failed to finalize service update: 1c

***** BUS FAULT *****
E: Imprecise data bus error
E: r0/a1: 0x00001000 r1/a2: 0x40010604 r2/a3: 0x6e524635
E: r3/a4: 0x00000001 r12/ip: 0x00000000 r14/lr: 0x2000041f
E: xpsr: 0x01000000
E: s[ 0]: 0x00000000 s[ 1]: 0x00000000 s[ 2]: 0x00000000 s[ 3]: 0x00000000
E: s[ 4]: 0x00000000 s[ 5]: 0x00000000 s[ 6]: 0x00000000 s[ 7]: 0x00000000
E: s[ 8]: 0x00000000 s[ 9]: 0x00000000 s[10]: 0x00000000 s[11]: 0x00000000
E: s[12]: 0x00000000 s[13]: 0x00000000 s[14]: 0x00000000 s[15]: 0x00000000
E: fpscr: 0x00000000
E: Faulting instruction address (r15/pc): 0x20000430
E: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0
E: Current thread: 0x20011ed8 (CHIP)
E: Halting system
I: Initialize binding Handler
I: 46336 [SVR]Cannot load binding table: a0

In short I just want to recreate this demo ( have a nanoleaf lightbulb). 

https://www.youtube.com/watch?v=yLkkeVM0Guo

I'm new to working with this board, so unsure if I'm doing something wrong or if I need to do something else (setup wise) for the demos (created from SDK v2.2.0) to work. and be detected by HomePod mini etc.

So any help in pointing me in the right direction, would be greatly appreciated!

[Marte Myrvold]

Hi,

Have you made any changes to the light bulb sample?

Please try following this guide for testing with Apple HomePod:  Matter: Testing the nRF Connect platform with Apple, Google and Samsung ecosystems .

Best regards,

Marte

[CartBlanche]

Hi Marte,

  I just wanted to be clarify that I'm using the light_switch demo and not the light_bulb demo. Which demo was used in the video I linked to? I thought it would have been the light_switch demo. Am I wrong?

D.

[Marte Myrvold]

Hi Dominique,

The issue in that case, which might be what you are seeing as well, is that Apple Home is not able to recognize the device type Light Switch. So the alternative is to use the Generic Switch device type instead. In order to to this, you can add another endpoint to the device, for example endpoint 2, and add a Generic Switch device to this endpoint. You can look at this to see how this device is added there: https://github.com/lats1980/fw-nrfconnect-nrf/commits/demo/matter-generic-switch.

You can also use the ZAP tool to add it. Follow the guide in Adding clusters to Matter application, but create a Generic Switch instead of a Temperature Sensor:

Best regards,

Marte

[CartBlanche]

Hi Marte,

  I added the 2 GitHub code commits (I copied the zap file contents) that you linked to. It builds and deploys to the board just fine. But HomePod still says unsupported.

You mentioned above "you can also use the zap tool to add it". Is that instead of the code changes or as well as the code changes?

Is my understanding correct that the .zap file generate the .matter file and a few helper*.h/cpp files??

D.

[Marte Myrvold]

Hi Dominique,

I see that the customer in the ticket you referred to was not able to get it to work using endpoint 2, so they had to remove the Dimmer Switch endpoint and make some changes. Please also be aware that the commits are from v2.1.0, so there might be some changes you have to do for it to work with v2.2.0.

Using the ZAP tool is another option. This will do the same as the first of the two commits. However, you will still need to implement the generic switch control, as is done in the last commit.

CartBlanche said:

Is my understanding correct that the .zap file generate the .matter file and a few helper*.h/cpp files??

Yes. When you first use the ZAP tool, you will edit the .zap file. This is when you run the run_zaptool.sh command in the guide I linked to (step 2.4). The .zap file will then be used to generate the .matter file as well as the files located inside the zap-generated directory when you run generate.py (step 2.10).

Best regards,

Marte

[CartBlanche]

Hi Marte,

  I'm unfortunately still struggling to get this last part working. Do Nordic offer paid support? If so who should I contact about this, that could help me get past this last part??

Best Regards,

Dominique 

[Marte Myrvold]

Hi Dominique,

We do not offer paid support, but you can fill out the contact form under 'Sales related questions' here: https://www.nordicsemi.com/About-us/Contact-Us and one of our regional sales managers can help you get in contact with consultants that have experience with Nordic.

Can you explain what about the last part you are struggling to get working?

Best regards,
Marte

[CartBlanche]

Hi Marte,

  I'm struggling to get the zap changes to regenerate the appropriate .c/.h files. I'm using the installed zap command line tool, but seems I'm not using it correctly.

Thanks,

Dominique.

[Marte Myrvold]

Hi Dominique,

Which files are not generated correctly?
What operating system are you using?

Please share the output logs from the commands.

Best regards,
Marte

[CartBlanche]

I'll run it again over the weekend and get back to you.

[Marte Myrvold]

Hi Dominique,

Have you been able to run it again?

Best regards,
Marte

[CartBlanche]

 Marte Myrvold I'll be working on Matter integration again this week, so will get back to you then.