search

project-chip / certification-tool

A test harness and tooling designed to simplify development, testing, and certification for devices, guided by the Connectivity Standards Alliance.
https://csa-iot.org/
Apache License 2.0
41 stars 23 forks source link

[Bug] DUT failed to perform commissioning step 24 #316

Closed dylanrrmcguire119 closed 1 month ago

dylanrrmcguire119 commented 3 months ago

Describe the bug

Recently updated my test harness to use the v2.10.1+spring2024 branch of the project. Since then have been unable to connect to my DUT utilizing the chip tool commands, always fail with the error:

Error on commissioning step 'ThreadNetworkSetup': 'src/controller/CHIPDeviceController.cpp:2448: CHIP Error 0x000000AC: Internal error'

Steps to reproduce the behavior

Run the command:

./chip-tool pairing ble-thread 1 hex:0e08000000000001000035060004001fffe00708fd0a2c2e3157f522041051a184f7cd8a9df2cfe847b51e6f1d2c0c0402a0f7f8000300001901025b3502085b35dead5b35beef030435623335051000112233445566778899aabbccddeeff 97833935 2449 --trace_decode 1 --paa-trust-store-path /var/paa-root-certs/

Expected behavior

No response

Log files

Full log output. Cant_commision_bug.txt

PICS file

No response

Screenshots

No response

Environment

Rasperry Pi 4 running Ubuntu Server 22.04 LTS (64-bit) v2.10.1+spring2024 branch of the certification tool project nRF52840 dongle connected to the raspberry pi

DUT is a custom PCB utilizing the nRF52840 SOC

Additional Information

This is probably a duplicate of this issue but am not certain so adding in more information.

Previously, I had been able to connect to my PCB via the chip tool commands with no issue, only started having this problem when I updated to the latest released branch of the project.

An interesting tidbit of information is that a co-worker is able to commission the same device without issue. The difference with his setup is that he upgraded earlier than I did and so his certification tool folder is on commit 1788152d3fada9e45f525c0e4c4fd715c3500ff4 which lists as the HEAD -> v1.3-TE1, origin/v1.3-TE1 branch when he runs git show.

I attempted to checkout that specific commit by:

  1. Cloning the certification tool repository with git clone https://github.com/project-chip/certification-tool.git
  2. git checkout 1788152d3fada9e45f525c0e4c4fd715c3500ff4
  3. Running the auto install script ./certification-tool/scripts/pi-setup/auto-install.sh

Doing that failed to grab the necessary apps folder so I ultimately wasn't able to attempt to run the chiptool script.

hiltonlima commented 3 months ago

Hello @dylanrrmcguire119,

Are you able to run this script? ./scripts/OTBR/otbr_start.sh

If you can start successfully, try commissioning using the command. If possible, collect logs of the steps you take.

The result of this script may also help in the investigation: ./scripts/th/th-doctor.sh --complete

dylanrrmcguire119 commented 3 months ago

@hiltonlima

After rebooting my raspberry pi, running the command docker ps outputs:

image

So the front and back end containers appear to be starting up without issue. Running the otbr start script similarly seems to have no issues.

image

Now running the command:

./chip-tool pairing ble-thread 1 hex:0e08000000000001000035060004001fffe00708fddda80951f995c20410acd26331883dda5b361e20cc0da3a1c00c0402a0f7f8000300001901025b3502085b35dead5b35beef030435623335051000112233445566778899aabbccddeeff 97833935 2449 --trace_decode 1 --paa-trust-store-path /var/paa-root-certs/

Produces the following output (which matches the logs in my original comment).

second_try.txt

Running the th doctor script produces the following output:

test_harness_doctor.txt

Maybe some interesting things of note from that output: The certification tool cli, backend, and frontend commit SHA's match what I see listed on v2.10.1+spring2024 branch of the certification tool project so that seems correct to me. The eth0 interface is down (my raspberry pi is connected directly to my router) but the wlan0 interface is up. Not sure if that is an issue but is something I noticed, for clarity I am SSH'd into this raspberry pi.

Attempting to re-run the chip tool pairing command after running the test harness doctor script resulted in the same failure as all the other attempts.

A final interesting thing. When I ran the test harness doctor script I also noticed that the DUT section of the output does not match what is configured via the test harness tool itself.

image

image

I feel like this shouldn't matter since I am using the chip tool commands and not the test harness itself but thought I should point that out.

dylanrrmcguire119 commented 3 months ago

@hiltonlima @antonio-amjr

I had my co-worker clone his raspberry pi image and the chiptool commands now work for me as expected. Ran the test harness doctor script and received the following output.

You can see the commits for the cert tool, frontend, backend, and cli submodules so definitely seems like some bug between then and now.

Let me know if there is any other information you need me to capture.

Working version.docx

hiltonlima commented 1 month ago

@dylanrrmcguire119 sorry for this late response.

Can you try with the latest branch? v2.11-beta3.1+fall2024 This version require Ubuntu Server 24.04. Please do a fresh install on the sd card before install the TH from this branch.

fabiowmm commented 1 month ago

Seems originator has lost interest. Please reopen if you are still facing the problem.