[MATTER] ZEPHYR FATAL error as commissioning to SmartThings apps

RE: [MATTER] ZEPHYR FATAL error as commissioning to SmartThings apps

Elfving — Fri, 10 Feb 2023 09:08:08 GMT

[quote user="Jeffery"] During programming, did multiprotocol_rpmsg hex be programmed to network core automatically?[/quote]

Exactly. The VSC Flashing 'Action' programs both cores.

[quote user="Jeffery"]2. Considering easy and simple programming in production line further, I used two batched files to program NRF5340.[/quote]

What is flashed to the network core isn't the default multiprotocol_rpmsg. If you want to split up the programming of the two cores you can try the hex file created in the child image of the matter sample (ie. in /window_covering/build/multiprotocol_rpmsg/zephyr/zephyr.hex), that should work.

Regards,

Elfving

RE: [MATTER] ZEPHYR FATAL error as commissioning to SmartThings apps

Jeffery — Fri, 10 Feb 2023 04:02:19 GMT

Hi Elfving

As ncs2.2.0 door lock sample, I tested two methods to program NRF5340.

1. If using flash at VS code, I found commissioning was successfully.

During programming, did multiprotocol_rpmsg hex be programmed to network core automatically?

2. Considering easy and simple programming in production line further, I used two batched files to program NRF5340.

step1. use batch net to program network core. The hex file was built form ncs2.2.0 multiprotocol_rpmsg sample.

step2. use batch app to program application core. The hex file was built form ncs2.2.0 door lock sample.

If using this method, the FATAL ERROR showed up during commissioning process,

Could you help me check these two batch files. Thanks.

devzone.nordicsemi.com/.../hexfiles_5F00_5340_5F00_doorlock.rar

RE: [MATTER] ZEPHYR FATAL error as commissioning to SmartThings apps

Elfving — Thu, 09 Feb 2023 13:12:41 GMT

Hello Jeff,

As I see that you are explicitly mentioning that you got the multiprotocol_rpmsg running on the network core, how are you building and flashing the device?

Regards,

Elfving