• State Verified Answer
  • Replies 18 replies
  • Subscribers 74 subscribers
  • Views 3009 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 313716
Options

Chip tool debugging device error

DoubleAmaing

Hi，

I have a problem, please help me, I can't see where is the problem 。

refer to

Working with the CHIP Tool — Matter documentation (nRF Connect SDK) (nordicsemi.com)

Environment:

Raspberry Pie (Border Router)

router

PC (Win10) - VirtualBox (Ubuntu 22.04)

Board (Light_Blub)

Chih TooL: 

Using pre compiled, version 2.4.1

Releases · nrfconnect/sdk-connectedhomeip (github.com)

The error is as follows:

yd@yd-VirtualBox:~/chip-tool-linux_x64$ ./chip-tool-debug pairing ble-thread 1 hex:0e08000000000001000035060004001fffe00708fd5ea4308ad9f2d40c0402a0f7f8051000112233445566778899aabbccddeeff03104f70656e5468726561644d61747465720410b02285723920d515813e00fa447e4ec7000300000f0208111111112222222201021234 20202021 3840
[1693281548.188769][5543:5543] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_kvs
[1693281548.194245][5543:5543] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_factory.ini
[1693281548.194434][5543:5543] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_config.ini
[1693281548.194632][5543:5543] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_counters.ini
[1693281548.195042][5543:5543] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-rNwByq)
[1693281548.196393][5543:5543] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
[1693281548.196433][5543:5543] CHIP:DL: NVS set: chip-counters/reboot-count = 2 (0x2)
[1693281548.196860][5543:5543] CHIP:DL: Got Ethernet interface: enp0s3
[1693281548.197063][5543:5543] CHIP:DL: Found the primary Ethernet interface:enp0s3
[1693281548.197721][5543:5543] CHIP:DL: Failed to get WiFi interface
[1693281548.197791][5543:5543] CHIP:DL: Failed to reset WiFi statistic counts
[1693281548.198828][5543:5543] CHIP:IN: UDP::Init bind&listen port=0
[1693281548.198960][5543:5543] CHIP:IN: UDP::Init bound to port=34870
[1693281548.198969][5543:5543] CHIP:IN: UDP::Init bind&listen port=0
[1693281548.199010][5543:5543] CHIP:IN: UDP::Init bound to port=47444
[1693281548.199017][5543:5543] CHIP:IN: BLEBase::Init - setting/overriding transport
[1693281548.199020][5543:5543] CHIP:IN: TransportMgr initialized
[1693281548.199040][5543:5543] CHIP:FP: Initializing FabricTable from persistent storage
[1693281548.206252][5543:5543] CHIP:TS: Last Known Good Time: 2023-07-11T07:57:00
[1693281548.212065][5543:5543] CHIP:FP: Fabric index 0x1 was retrieved from storage. Compressed FabricId 0xC3F8DB39D71B1829, FabricId 0x0000000000000001, NodeId 0x000000000001B669, VendorId 0xFFF1
[1693281548.216526][5543:5543] CHIP:ZCL: Using ZAP configuration...
[1693281548.220250][5543:5543] CHIP:DL: Avahi client registered
[1693281548.221826][5543:5543] CHIP:CTL: System State Initialized...
[1693281548.223314][5543:5543] CHIP:CTL: Stopping commissioning discovery over DNS-SD
[1693281548.223357][5543:5543] CHIP:CTL: Setting attestation nonce to random value
[1693281548.223375][5543:5543] CHIP:CTL: Setting CSR nonce to random value
[1693281548.223642][5543:5545] CHIP:DL: CHIP task running
[1693281548.223761][5543:5545] CHIP:DL: HandlePlatformSpecificBLEEvent 32784
[1693281548.223893][5543:5545] CHIP:CTL: Stopping commissioning discovery over DNS-SD
[1693281548.224037][5543:5545] CHIP:CTL: Setting attestation nonce to random value
[1693281548.224061][5543:5545] CHIP:CTL: Setting CSR nonce to random value
[1693281548.229926][5543:5545] CHIP:CTL: Generating NOC
[1693281548.236726][5543:5545] CHIP:FP: Validating NOC chain
[1693281548.276048][5543:5545] CHIP:FP: NOC chain validation successful
[1693281548.276157][5543:5545] CHIP:FP: Updated fabric at index: 0x1, Node ID: 0x000000000001B669
[1693281548.276350][5543:5545] CHIP:TS: Last Known Good Time: 2023-07-11T07:57:00
[1693281548.276435][5543:5545] CHIP:TS: New proposed Last Known Good Time: 2021-01-01T00:00:00
[1693281548.276440][5543:5545] CHIP:TS: Retaining current Last Known Good Time
[1693281548.279811][5543:5545] CHIP:FP: Metadata for Fabric 0x1 persisted to storage.
[1693281548.283222][5543:5545] CHIP:TS: Committing Last Known Good Time to storage: 2023-07-11T07:57:00
[1693281548.285262][5543:5545] CHIP:CTL: Joined the fabric at index 1. Fabric ID is 0x0000000000000001 (Compressed Fabric ID: C3F8DB39D71B1829)
[1693281548.297085][5543:5545] CHIP:CTL: Setting thread operational dataset from parameters
[1693281548.297371][5543:5545] CHIP:CTL: Setting attestation nonce to random value
[1693281548.297960][5543:5545] CHIP:CTL: Setting CSR nonce to random value
[1693281548.297977][5543:5545] CHIP:CTL: Commission called for node ID 0x0000000000000001
[1693281548.310807][5543:5544] CHIP:DL: TRACE: Bus acquired for name C-15a7
[1693281573.317555][5543:5544] CHIP:DL: FAIL: Error getting object manager client: Error calling StartServiceByName for org.bluez: Timeout was reached
[1693281573.318147][5543:5545] CHIP:DL: PlatformBlueZInit init success
[1693281573.318165][5543:5545] CHIP:DIS: Closing all BLE connections
[1693281573.318194][5543:5545] CHIP:BLE: No adapter available for new connection establishment
[1693281573.318201][5543:5545] CHIP:DL: Long dispatch time: 25021 ms, for event type 2
[1693281668.226041][5543:5543] CHIP:CTL: Shutting down the commissioner
[1693281668.226358][5543:5543] CHIP:CTL: Stopping commissioning discovery over DNS-SD
[1693281668.226458][5543:5543] CHIP:CTL: Shutting down the controller
[1693281668.226471][5543:5543] CHIP:IN: Expiring all sessions for fabric 0x1!!
[1693281668.226476][5543:5543] CHIP:FP: Forgetting fabric 0x1
[1693281668.226488][5543:5543] CHIP:TS: Pending Last Known Good Time: 2023-07-11T07:57:00
[1693281668.226557][5543:5543] CHIP:TS: Previous Last Known Good Time: 2023-07-11T07:57:00
[1693281668.226561][5543:5543] CHIP:TS: Reverted Last Known Good Time to previous value
[1693281668.226573][5543:5543] CHIP:CTL: Shutting down the commissioner
[1693281668.226576][5543:5543] CHIP:CTL: Stopping commissioning discovery over DNS-SD
[1693281668.226579][5543:5543] CHIP:CTL: Shutting down the controller
[1693281668.226582][5543:5543] CHIP:CTL: Shutting down the System State, this will teardown the CHIP Stack
[1693281668.227063][5543:5543] CHIP:DMG: All ReadHandler-s are clean, clear GlobalDirtySet
[1693281668.227191][5543:5543] CHIP:BLE: BleConnectionDelegate::CancelConnection is not implemented.
[1693281668.227207][5543:5543] CHIP:FP: Shutting down FabricTable
[1693281668.227214][5543:5543] CHIP:TS: Pending Last Known Good Time: 2023-07-11T07:57:00
[1693281668.227252][5543:5543] CHIP:TS: Previous Last Known Good Time: 2023-07-11T07:57:00
[1693281668.227257][5543:5543] CHIP:TS: Reverted Last Known Good Time to previous value
[1693281668.227409][5543:5543] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-ed2AOW)
[1693281668.228819][5543:5543] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
[1693281668.228932][5543:5543] CHIP:DL: NVS set: chip-counters/total-operational-hours = 0 (0x0)
[1693281668.228943][5543:5543] CHIP:DL: Inet Layer shutdown
[1693281668.228947][5543:5543] CHIP:DL: BLE shutdown

(process:5543): GLib-GObject-CRITICAL **: 12:01:08.228: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
[1693281668.229205][5543:5543] CHIP:DL: System Layer shutdown
[1693281668.229612][5543:5543] CHIP:TOO: Run command failure: examples/chip-tool/commands/common/CHIPCommand.cpp:537: CHIP Error 0x00000032: Timeout

  • 0 in reply to DoubleAmaing

    Hi,

    Glad to hear that you feel you're progressing! I see that you've had some success here, but just a few questions from so I am on the same page as you.

    1. Were you able to flash a Bluetooth sample on the the E73-2G4M08S1C module, for instance the peripheral_uart sample? Where you able to connect with the nRF Connect application for either Android or iOS?
    2. Have you implemented all of the changes since my previous reply on a 52840DK, which the images you've posted suggest, or is it on the E73 module?
    3. I will see if I find some more information regarding CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC. I see that in the original case they were using NCS v1.7.0, which is 2 years old, so this feature request may have been implemented in newer NCS versions. Based on what you describe, it looks like it may still be required. I will investigate the status on this request.
    DoubleAmaing said:
    Was it successful?

    The commissioning of the device looks successful based on initial looks at the logs. Are you able to communicate with the node using CHIP tool? Can you see the device when you list all nodes in the network?

    Kind regards,
    Andreas

  • 0 in reply to AHaug

    Hi,

    thank you for your help.

    At present, my tests are all performed on E73-2G4M08S1C (I don't have nRF52840DK).

    The schematic diagram is very simple: we use 3.3V to supply power to E73-2G4M08S1C, and lead out Reset, GND, SWDIO, SWCLK for flash programs; in addition, Reset (p0.18) pin connects a capacitor (104) to GND; XL1, XL2 are not connected to 32K crystal oscillator, XC1, XC2 are connected to 32M crystal oscillator;

    Were you able to flash a Bluetooth sample on the the E73-2G4M08S1C module, 
for instance the peripheral_uart sample? 
Where you able to connect with the nRF Connect application for either Android or iOS?

    Reply：Yes, I can download bluetooth program on E73-2G4M08S1C. After I added CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC, I can connect to E73-2G4M08S1C using nRF connect for Mobile.

    nRF connect for mobile download link: https://www.nordicsemi.com/Products/Development-tools/nrf-connect-for-mobile

    Have you implemented all of the changes since my previous reply on a 52840DK, 
which the images you've posted suggest, or is it on the E73 module?

    Reply:

    I am using the matter example (Light_Blub), I just added: CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y

    CONFIG_SOC_ENABLE_LFXO=n

    No other modifications are made.

    I will see if I find some more information regarding CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC.
I see that in the original case they were using NCS v1.7.0, 
which is 2 years old, so this feature request may have been implemented in newer NCS versions. 
Based on what you describe, it looks like it may still be required. 
I will investigate the status on this request.

    Reply：

    CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC, does this configuration enable the internal crystal oscillator?

    My XL1 and XL2 are not connected to a crystal oscillator

    The commissioning of the device looks successful based on initial looks at the logs. 
Are you able to communicate with the node using CHIP tool? 
Can you see the device when you list all nodes in the network?

    Reply:

    Yes, i can see him and i use command ./chip-tool-debug onoff toggle 1 1 to control it;

    I measure the output of the IO with a meter, and I can see it flipping 0V or 3.3V;

    ---------------------------

    Sorry I have so many questions, thanks for helping me out. I have another question to attach to you, please help me:

    I use matter's example (Light_Blub), the board can't run when power on, because I don't see any information printed through the J-Link console. However, when I send the "Reset Board" command through the Vs Code (CONNECTED DEVICES) interface, I can see the terminal print a lot of information, and I know the board is working. I have connected a 104 capacitor to GND on the P0.18/Reset pin of the board, what else should I do? My schematic is as stated above, and it's pretty simple, so I'm not sure if it's my hardware reset that isn't working perfectly enough.

  • 0 in reply to DoubleAmaing

    Thank you for clarifying. In step 4 in your previous reply where you added an image showing the flash button there was a 52840DK listed, which caused some confusion to me.

    CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y enables the LFRC instead of LFXO. I suspect that the E73 module does not have an LFXO or that there are some issues with a capacitor/it's missing a capacitor

    Disconnect reason 0x3e is a typical sign that this is the issue, caused by issues with the LF clock since you will not be able to send and receive packs at the correct timings. This leads to the loss of connection

    DoubleAmaing said:
    Sorry I have so many questions, thanks for helping me out. I have another question to attach to you, please help me:

    No worries about the amount of questions :) We're here to support you. But in some cases it might be good to separate the questions into multiple cases and for instance to separate software-related questions and hardware relate questions so we can allocate our experts properly

    DoubleAmaing said:
    I use matter's example (Light_Blub), the board can't run when power on, because I don't see any information printed through the J-Link console.

    Are you able to monitor the device with an RTT monitor? Could you share the contents of your prj.conf?

    Kind regards,
    Andreas

Related
Terms of service