Attachments (0)
Nordic Case Info
  • Case ID: 312649
Options

Matter Over thread [chip-tool error]

Sushi_27

Hi,

I want to test Matter over Thread, with the Matter: Light Bulb example from nRF Connect. The Border Router and controller are on the same device RPi 3 Model B+.

I've referred https://www.youtube.com/watch?v=9Ar13rMxGIk  

The border router is working correctly, and I tested Matter over Thread and Matter binding as explained in the above video. 

When I try to do it again, it gives the error which I am not able to solve even after referring to devzone tickets eg  RE: Matter : unable to de-commisioning a device  Matter over Thread Commissioning failed ,  RE: Matter device pairing issue with chip-tool  

Environment:

- nRF Connect for Desktop  ncs version 2.4.0

- Chip-Tool (controller) version 2.4.0, compile it from source on Ubuntu 22.04.

- Same RPi 3 Model B+ as Threat Border Router coupled with nRF52840dk as radio co-processor

- nRF5340dk as Light Bulb and nRF5340dk as Light Switch

Matter Light-Bulb logs : 

Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
uart:~$ *** Booting Zephyr OS build v3.3.99-ncs1 ***
I: Init CHIP stack
I: 486 [DL]BLE address: D6:D4:2D:E5:96:79
I: 508 [DL]OpenThread started: OK
I: 511 [DL]Setting OpenThread device type to ROUTER
I: 516 [SVR]Subscription persistence not supported
I: 521 [SVR]Server initializing...
I: 524 [TS]Last Known Good Time: 2023-08-07T15:17:34
I: 529 [DMG]AccessControl: initializing
I: 533 [DMG]Examples::AccessControlDelegate::Init
I: 538 [DMG]AccessControl: setting
I: 541 [DMG]DefaultAclStorage: initializing
I: 545 [DMG]DefaultAclStorage: 0 entries loaded
D: 549 [IN]UDP::Init bind&listen port=5540
E: 553 [IN]SO_REUSEPORT failed: 109
D: 556 [IN]UDP::Init bound to port=5540
D: 560 [IN]BLEBase::Init - setting/overriding transport
D: 565 [IN]TransportMgr initialized
D: 570 [DL]Using Thread extended MAC for hostname.
I: 575 [ZCL]Using ZAP configuration...
I: 581 [DMG]AccessControlCluster: initializing
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Chip tool error log : 

Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
lenovo@lenovo-ThinkPad-L470:~/Downloads$ ./chip-tool-debug pairing ble-thread 1 hex:0e080000000000010000000300001035060004001fffe002081cea9dccaac89edc0708fdaa96d09e1b690405101416c358c6964dcc95d99f3d4d068a93030f4f70656e5468726561642d3561376601025a7f0410fe82415a7b2f71353c3b468190356fde0c0402a0f7f8 20202021 3840
[1691403080.695655][7870:7870] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_kvs
[1691403080.695798][7870:7870] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_factory.ini
[1691403080.695830][7870:7870] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_config.ini
[1691403080.695850][7870:7870] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_counters.ini
[1691403080.695955][7870:7870] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-vbHOcT)
[1691403080.696120][7870:7870] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
[1691403080.696133][7870:7870] CHIP:DL: NVS set: chip-counters/reboot-count = 27 (0x1B)
[1691403080.696265][7870:7870] CHIP:DL: Got Ethernet interface: enp0s31f6
[1691403080.696358][7870:7870] CHIP:DL: Found the primary Ethernet interface:enp0s31f6
[1691403080.696460][7870:7870] CHIP:DL: Got WiFi interface: wlp5s0
[1691403080.698000][7870:7870] CHIP:DL: Found the primary WiFi interface:wlp5s0
[1691403080.698021][7870:7870] CHIP:IN: UDP::Init bind&listen port=0
[1691403080.698044][7870:7870] CHIP:IN: UDP::Init bound to port=59227
[1691403080.698049][7870:7870] CHIP:IN: UDP::Init bind&listen port=0
[1691403080.698066][7870:7870] CHIP:IN: UDP::Init bound to port=43359
[1691403080.698070][7870:7870] CHIP:IN: BLEBase::Init - setting/overriding transport
[1691403080.698075][7870:7870] CHIP:IN: TransportMgr initialized
[1691403080.698086][7870:7870] CHIP:FP: Initializing FabricTable from persistent storage
[1691403080.698137][7870:7870] CHIP:TS: Last Known Good Time: 2023-06-01T07:38:45
[1691403080.698280][7870:7870] CHIP:FP: Fabric index 0x1 was retrieved from storage. Compressed FabricId 0xCEFAD72140B20CDA, FabricId 0x0000000000000001, NodeId 0x000000000001B669, VendorId 0xFFF1
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

I've tried 

1. Factory reset the nRF 5340dk board

2. Reboot the Border Router

3. Try to unpair the node device in Chip-tool (it gave error : retry resolve)

Still, the error is not resolved

Am I missing something?

Need Help

  • 0

    Hi,

    Could you verify if you're using a the same node ID every time you attempt this? The error might be due to issues caused by chip-tool cache. You can try to remove the chip-tool cache with "rm -rf /tmp/chip_*" or to try with a new unique Node ID

    Kind regards,
    Andreas

  • +1 in reply to AHaug

    Hello

    I've tried to remove the chip-tool cache with "rm -rf /tmp/chip_*" and  then chip tool pairing ble-thread command.

    Still it gave the error : ble scan error

  • 0 in reply to Sushi_27
    AHaug said:
    Could you verify if you're using a the same node ID every time you attempt this?

    Could you please answer this question as well?

    Kind regards,
    Andreas

  • 0 in reply to AHaug

    Yes, I was using the same node ID every time.

    As per your reply, I've cleared chip-tool cache and try chip tool pairing ble-thread command which result in ble scan error

  • 0 in reply to Sushi_27

    Thank you,

    I will keep looking into the logs to see if I can find any hints of what is going on. In the meanwhile could you verify if you have at any point in time had the network and devices up and running, or has this issue been present since the start?

    Kind regards,
    Andreas

1 2 3
Terms of service