This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

LP-CC2652R7: 我在跑官方提供的matter例程,用chiptool命令会报错

Part Number: LP-CC2652R7
Other Parts Discussed in Thread: CC2652R7

我在边界路由上面执行下面这条命令配对不上,请问我要如何操作。

现在RCP已经搭建好,matter Device也正常的,我想用chiptool工具执行配对不行。

  • 非常抱歉,网络有点问题,导致发了三次帖

  • 您好,

    感谢您的提问。我们有几个问题想要咨询您:

    1. 您这边的连接到ZNP的Linux Matter host是什么,尝试连接的Matter设备是什么?
    2. 您是否确认 OpenThread 边界路由器正在运行?
    3. 可以的话您能提供 chiptool 的终端日志和 CC2652R7 Matter设备的 UART 日志吗?

    期待您的回复。

  • 我确认OenThread边界路由已经正常运行,下面我给出我的chiptool的日志和Matter Device的串口日志

    • 在边界路由上运行chiptool的日志
      Fullscreen
      1
      2
      3
      4
      5
      6
      7
      8
      9
      10
      11
      12
      13
      14
      15
      16
      17
      18
      19
      20
      21
      ubuntu@raspberrypi:~/matter/out$ ls
      args.gn build.ninja build.ninja.d build.ninja.stamp chip-tool chip-tool-utils.a chip-tool.map gen lib liblogging-stdio.a obj python relative_path_transformations.json toolchain.ninja
      ubuntu@raspberrypi:~/matter/out$
      ubuntu@raspberrypi:~/matter/out$
      ubuntu@raspberrypi:~/matter/out$
      ubuntu@raspberrypi:~/matter/out$
      ubuntu@raspberrypi:~/matter/out$
      ubuntu@raspberrypi:~/matter/out$ ./chip-tool
      [1689126501.963905][6142:6142] CHIP:TOO: Missing cluster name
      Usage:
      ./chip-tool cluster_name command_name [param1 param2 ...]
      +-------------------------------------------------------------------------------------+
      | Clusters: |
      +-------------------------------------------------------------------------------------+
      | * accesscontrol |
      | * accountlogin |
      | * actions |
      | * administratorcommissioning |
      | * any |
      | * applicationbasic |
      XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
    • Matter Device打印的串口日志
      Fullscreen
      1
      2
      3
      4
      5
      6
      7
      8
      9
      10
      11
      12
      13
      14
      15
      16
      17
      18
      19
      20
      21
      Xshell 7 (Build 0099)
      Copyright (c) 2020 NetSarang Computer, Inc. All rights reserved.
      Type `help' to learn how to use Xshell prompt.
      [C:\~]$
      Connecting to COM4...
      Connected.
      ÿOpenThread started: OK
      Setting OpenThread device type to MINIMAL END DEVICE
      Initialize Server
      Server initializing...
      Last Known Good Time: 2023-07-03T16:02:44
      AccessControl: initializing
      Examples::AccessControlDelegate::Init
      AccessControl: setting
      DefaultAclStorage: initializing
      DefaultAclStorage: 0 entries loaded
      Using ZAP configuration...
      AccessControlCluster: initializing
      XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
  • 您好,

    感谢您的快速回复。

    我们需要根据您提供的信息跟进一下这个问题,这可能需要一点时间,有结论会及时联系您。

  • 您好,

    最直接的问题是matter chip-tool 的主机无法访问OTBR thread network。您可以查看chip-tool日志中的 "CHIP Error 0x000000AC: Internal error" 

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    [1689139871.572581][10800:10802] CHIP:DMG: Received Command Response Data, Endpoint=0 Cluster=0x0000_0031 Command=0x0000_0005
    [1689139871.572742][10800:10802] CHIP:CTL: Received NetworkConfig response, networkingStatus=1
    [1689139871.572808][10800:10802] CHIP:CTL: Error on commissioning step 'ThreadNetworkSetup': '../examples/chip-tool/third_party/connectedhomeip/src/controller/CHIPDeviceController.cpp:2050: CHIP Error 0x000000AC: Internal error'
    [1689139871.572850][10800:10802] CHIP:CTL: Failed to perform commissioning step 15
    [1689139871.572897][10800:10802] CHIP:CTL: Going from commissioning step 'ThreadNetworkSetup' with lastErr = '../examples/chip-tool/third_party/connectedhomeip/src/controller/CHIPDeviceController.cpp:2050: CHIP Error 0x000000AC: Internal error' -> 'Cleanup'
    [1689139871.572956][10800:10802] CHIP:CTL: Performing next commissioning step 'Cleanup' with completion status = '../examples/chip-tool/third_party/connectedhomeip/src/controller/CHIPDeviceController.cpp:2050: CHIP Error 0x000000AC: Internal error'
    [1689139871.573000][10800:10802] CHIP:CTL: Successfully finished commissioning step 'Cleanup'
    [1689139871.573054][10800:10802] CHIP:TOO: Device commissioning Failure: ../examples/chip-tool/third_party/connectedhomeip/src/controller/CHIPDeviceController.cpp:2050: CHIP Error 0x000000AC: Internal error
    [1689139871.573148][10800:10802] CHIP:DMG: ICR moving to [AwaitingDe]
    [1689139871.573511][10800:10800] CHIP:CTL: Shutting down the commissioner
    [1689139871.573565][10800:10800] CHIP:CTL: Stopping commissioning discovery over DNS-SD
    [1689139871.573760][10800:10800] CHIP:DIS: Closing all BLE connections
    [1689139871.573804][10800:10800] CHIP:IN: Clearing BLE pending packets.
    [1689139871.573910][10800:10800] CHIP:BLE: Auto-closing end point's BLE connection.
    [1689139871.573952][10800:10800] CHIP:DL: Closing BLE GATT connection (con 0xffffb405e080)
    [1689139871.574032][10800:10800] CHIP:IN: SecureSession[0xffffac014f10]: MarkForEviction Type:1 LSID:56629
    [1689139871.574074][10800:10800] CHIP:SC: SecureSession[0xffffac014f10]: Moving from state 'kActive' --> 'kPendingEviction'
    [1689139871.574154][10800:10800] CHIP:IN: SecureSession[0xffffac014f10]: Released - Type:1 LSID:56629
    [1689139871.574204][10800:10800] CHIP:CTL: Shutting down the controller
    [1689139871.574246][10800:10800] CHIP:IN: Expiring all sessions for fabric 0x1!!
    [1689139871.574284][10800:10800] CHIP:FP: Forgetting fabric 0x1
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    如果您使用的是最新的TI matter repository,那么 CHIPDeviceController.cpp 会失败并在 OnNetworkConfigResponse 内报错 CHIP_ERROR_INTERNAL。

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    void DeviceCommissioner::OnNetworkConfigResponse(void * context,
    const NetworkCommissioning::Commands::NetworkConfigResponse::DecodableType & data)
    {
    CommissioningDelegate::CommissioningReport report;
    CHIP_ERROR err = CHIP_NO_ERROR;
    ChipLogProgress(Controller, "Received NetworkConfig response, networkingStatus=%u", to_underlying(data.networkingStatus));
    if (data.networkingStatus != NetworkCommissioning::NetworkCommissioningStatus::kSuccess)
    {
    err = CHIP_ERROR_INTERNAL;
    report.Set<NetworkCommissioningStatusInfo>(data.networkingStatus);
    }
    DeviceCommissioner * commissioner = static_cast<DeviceCommissioner *>(context);
    commissioner->CommissioningStageComplete(err, report);
    }
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    您正在测试的树莓派上有多少可用 RAM?运行 OTBR 的是同一个设备吗? Chip-tool 和OTBR是否连接到同一路由下?

  • 我使用的是最新版的TI matter repository,我应该下载哪个版本的才可以消除这个报错。

    我现在的树莓派是4GB版本的,现在的树莓派就是我的OTBR,我在树莓派上面运行chiptool命令

  • Fullscreen
    1
    ./chip-tool pairing ble-thread <nodeID - e.g. 1> hex:<complete dataset from starting the OTBR> 20202021 3840
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    这条命令里面nodeID我应该写什么,是随便写一个还是,要根据matter Device的ID来写,例如下面是我的Matter Device信息

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    Device Configuration:
    Serial Number: TEST_SN
    Vendor Id: 65521 (0xFFF1)
    Product Id: 32774 (0x8006)
    Hardware Version: 0
    Setup Pin Code (0 for UNKNOWN/ERROR): 20202021
    Setup Discriminator (0xFFFF for UNKNOWN/ERROR): 3840 (0xF00)
    Manufacturing Date: (not set)
    Device Type: 65535 (0xFFFF)
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    我应该在这个用Prodeuct id或者 Vendor Id来替换这个node ID吗

  • 您好,

    我曾经也使用过和您一样的软硬件去配置没有发生什么问题。我想我们来排除一些干扰。您使用的RCP是我们给的还是您自己编译的?您是否能启动OTBR并加入thread设备?您可以使用 Thread Border Router Setup SimpleLink Academy Lab (Task 3到Task 5) 和 Thread 示例来做评估。树莓派是通过 WiFi 还是网线连接到路由器?

    最新的chiptool的指令模式略有更新所以您需要将 "hex:" 放在Thread 操作数据集之前。

    之前我由遇到过相同的错误,因为chip-tool日志并没有指出错误,但在调试第15步(查找 Thread 网络)时会失败。所以您的命令代码应如下:

    Fullscreen
    1
    ./chip-tool pairing ble-thread 1 hex:000300000f35060004001fffe00208dead00beef00cafe0708fde2f55f8122e830051000112233445566778899aabbccddeeff030f4f70656e5468726561642d37386237010212340410104810e2315100afd6bc9215a6bfac530c0402a0f7f80e080000000000010000 20202021 3840
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • 还是不行没有解决,chiptool要能够调试matter设备需要哪些条件,我目前按照官方给的文档来操作的

  • 这是matter设备打印出来的日志

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    ÿOpenThread ifconfig up and thread start
    OpenThread started: OK
    Setting OpenThread device type to MINIMAL END DEVICE
    Initialize Server
    Server initializing...
    Last Known Good Time: 2023-07-03T16:02:44
    Fabric index 0x1 was retrieved from storage. Compressed FabricId 0xB07ED91A051673C2, FabricId 0x0000000000000001, NodeId 0x0000000000000001, VendorId 0xFFF1
    AccessControl: initializing
    Examples::AccessControlDelegate::Init
    AccessControl: setting
    DefaultAclStorage: initializing
    DefaultAclStorage: 1 entries loaded
    Using ZAP configuration...
    AccessControlCluster: initializing
    Initiating Admin Commissioning cluster.
    Door Lock server initialized
    Cluster callback: 0x0000_0030
    Cluster callback: 0x0000_002B
    Fabric already commissioned. Disabling BLE advertisement
    Updating services using commissioning mode 0
    Advertise operational node B07ED91A051673C2-0000000000000001
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • 运行chiptool是否一定要让我的树莓派要连接上wifi

  • 您好,

    从您的matter 设备log来说没有发现什么明显的问题。您可以使用额外的log记录来看是否有记录下一些意外情况:matter\examples\lock-app\cc13x2x7_26x2x7\args.gni

        chip_progress_logging = true

        chip_detail_logging = true

        chip_automation_logging = true

    wifi不是必须的,但是您的设备必须连接到路由器,没有互联网连接也没事。

  • 这种警告有什么关系没


  • 这种是不是表示配对成功了


  • 这个命令 ./chip-tool doorlock lock-door destination-id endpoint-id-ignored-for-group-commands 
    后面两个参数应该写什么

  • 您好

    前三张图表示与OTBR建立连接时存在问题,就像之前的chip-tool logs所表示的一样。

    后面的几张图表示Matter设备测试成功。

    README中提供了chip-toollock-app示例交互的示例。您也可以参考CHIP Tool Guide。如果节点是endpoint1,那么可以将这两个参数设置为一个参数来测试您的环境是否正确。

  •  这张图表示我连接成功了 我在下次要调试的时候还需要重连吗 比如我的边界路由和设备关机了之后 我想重新调试 应该怎么操作

  • 刚刚提问的这个问题已经解决了

  • ./chip-tool doorlock   <attribute-name> <attribute-values> <destination-id> <endpoint-id-ignored-for-group-commands>

    麻烦帮我问下,这个命令里面的attribute-values是什么,实在是不知道,看文档里面也没说。

  • 我运行./chiptool doorlock lock-door 10 endpoint确实不知道怎么获取,没看到教程提到

  • 您好,

    这个命令里面的attribute-values是什么

    这取决于所引用的attribute-name,CHIP Tool Guide 第8章中有一节就是关于读取Matter设备信息,the lock-app README 提供了写入属性的示例(锁门和开锁)。您还可以参考Matter设备规范,了解有关可能的设备类型、属性和命令的更多信息。

    我运行./chiptool doorlock lock-door 10 endpoint确实不知道怎么获取,没看到教程提到

    您这边运行什么,获取什么,能明确一下吗?

  • 你好!我想问下下面这条命令

    ./chip-tool doorlock set-user 0 1 TST 6452 1 0 0 1 1  --timedInteractionTimeoutMs 1000

    请问这个--timedInteractionTimeoutMs 1000在这里是什么意思, 在这条命令中必须要加上吗

  • 您好,

    这是 Matter 结构上的命令交互将超时的时间(以毫秒为单位),它应该是可选的,因此您可以测试删除它或增加值。

  • 我想问下chiptool有保存节点的功能吗,我在树莓派上使用chiptool工具,当我的边界路由和设备关机了之后,我重新上电。发现又要重新使用chiptool配对一次设备才能操作调试,怎样设置能让我断电关机之后,我重新开启树莓派能继续使用

  • 您好,

    感谢您的提问。本问题和本帖主题不是很相关,希望您能重新开帖提问,也方便他人查询该问题。

    谢谢您的配合,本帖将关闭。