Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chip-tool unable to commission M5 all clusters app and error messages are not helpful #13336

Closed
wahajsyed opened this issue Jan 6, 2022 · 5 comments · Fixed by #13339
Closed
Labels
stale Stale issue or PR V1.X

Comments

@wahajsyed
Copy link
Contributor

wahajsyed commented Jan 6, 2022

Problem

  • chip-tool on raspberry Pi unable to commission M5 stack running all clusters app.
Logs:
ubuntu@ubuntu:~/connectedhomeip/examples/chip-tool/out/debug$ ./chip-tool pairing ble-wifi 0x12345678 SSID_Test password65 20202021 3840
[1639785253.731323][123238:123238] CHIP:DL: writing settings to file (/tmp/chip_factory.ini-3zeEhT)
[1639785253.732682][123238:123238] CHIP:DL: renamed tmp file to file (/tmp/chip_factory.ini)
[1639785253.733078][123238:123238] CHIP:DL: writing settings to file (/tmp/chip_config.ini-HmYnVS)
[1639785253.733635][123238:123238] CHIP:DL: renamed tmp file to file (/tmp/chip_config.ini)
[1639785253.734446][123238:123238] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-Pc5xqS)
[1639785253.734718][123238:123238] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
[1639785253.735873][123238:123238] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-8UPZSS)
[1639785253.736890][123238:123238] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
[1639785253.736976][123238:123238] CHIP:DL: NVS set: chip-counters/reboot-count = 1 (0x1)
[1639785253.737316][123238:123238] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-6yWL1T)
[1639785253.768903][123238:123238] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
[1639785253.770061][123238:123238] CHIP:DL: NVS set: chip-counters/total-operational-hours = 0 (0x0)
[1639785253.770601][123238:123238] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-8zSYWQ)
[1639785253.771492][123238:123238] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
[1639785253.771894][123238:123238] CHIP:DL: NVS set: chip-counters/boot-reason = 0 (0x0)
[1639785253.772324][123238:123238] CHIP:DL: writing settings to file (/tmp/chip_config.ini-oeDpsT)
[1639785253.772986][123238:123238] CHIP:DL: renamed tmp file to file (/tmp/chip_config.ini)
[1639785253.773269][123238:123238] CHIP:DL: NVS set: chip-config/regulatory-location = 0 (0x0)
[1639785253.773638][123238:123238] CHIP:DL: writing settings to file (/tmp/chip_config.ini-KPpdMU)
[1639785253.786642][123238:123238] CHIP:DL: renamed tmp file to file (/tmp/chip_config.ini)
[1639785253.786740][123238:123238] CHIP:DL: NVS set: chip-config/location-capability = 0 (0x0)
[1639785253.787674][123238:123238] CHIP:DL: Got Ethernet interface: eth0
[1639785253.788410][123238:123238] CHIP:DL: Found the primary Ethernet interface:eth0
[1639785253.789109][123238:123238] CHIP:DL: Got WiFi interface: wlan0
[1639785253.789191][123238:123238] CHIP:DL: Failed to reset WiFi statistic counts
[1639785253.789333][123238:123238] CHIP:IN: UDP::Init bind&listen port=5542
[1639785253.789452][123238:123238] CHIP:IN: UDP::Init bound to port=5542
[1639785253.789508][123238:123238] CHIP:IN: UDP::Init bind&listen port=5542
[1639785253.789614][123238:123238] CHIP:IN: UDP::Init bound to port=5542
[1639785253.789662][123238:123238] CHIP:IN: TransportMgr initialized
[1639785253.789764][123238:123238] CHIP:DIS: Init fabric pairing table with server storage
[1639785253.790219][123238:123238] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-Xz0TAU)
[1639785253.791047][123238:123238] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
[1639785253.791563][123238:123238] CHIP:DL: NVS set: chip-counters/GlobalMCTR = 1000 (0x3E8)
[1639785253.791770][123238:123238] CHIP:ZCL: Using ZAP configuration...
[1639785253.804303][123238:123238] CHIP:DL: Avahi connecting
[1639785253.804427][123238:123238] CHIP:CTL: System State Initialized...
[1639785253.810053][123238:123238] CHIP:CTL: Generating NOC
[1639785253.810488][123238:123238] CHIP:CTL: Generating ICAC
[1639785253.810756][123238:123238] CHIP:CTL: Generating RCAC
[1639785253.811904][123238:123238] CHIP:-: ../../third_party/connectedhomeip/src/platform/Linux/DnssdImpl.cpp:329: CHIP Error 0x00000003: Incorrect state at ../../commands/common/CHIPCommand.cpp:205
[1639785253.812016][123238:123238] CHIP:-: ../../third_party/connectedhomeip/src/platform/Linux/DnssdImpl.cpp:329: CHIP Error 0x00000003: Incorrect state at ../../commands/common/CHIPCommand.cpp:58
[1639785253.812065][123238:123238] CHIP:TOO: Run command failure: ../../third_party/connectedhomeip/src/platform/Linux/DnssdImpl.cpp:329: CHIP Error 0x00000003: Incorrect state
[1639785253.815557][123238:123238] CHIP:SPT: VerifyOrDie failure at ../../third_party/connectedhomeip/src/inet/InetLayer.h:121: sEndPointPool.Allocated() == 0
Aborted (core dumped)

Proposed Solution

  • Improve error reporting to make it clear that the problem was that the avahi client was not found.
@andy31415
Copy link
Contributor

Is this an SDK issue? sounds like it is an issue in preparing a raspberry pi ubuntu image.

@bzbarsky-apple bzbarsky-apple changed the title chip-tool unable to commission M5 all clusters app chip-tool unable to commission M5 all clusters app and error messages are not helpful Jan 6, 2022
@bzbarsky-apple
Copy link
Contributor

Made it clearer what the issue is about: we should be usefully reporting the error, not just segfaulting.

@stale
Copy link

stale bot commented Jul 21, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the stale Stale issue or PR label Jul 21, 2022
@bzbarsky-apple bzbarsky-apple removed the stale Stale issue or PR label Jul 21, 2022
@stale
Copy link

stale bot commented Jan 20, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the stale Stale issue or PR label Jan 20, 2023
@stale
Copy link

stale bot commented Feb 4, 2023

This stale issue has been automatically closed. Thank you for your contributions.

@stale stale bot closed this as completed Feb 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Stale issue or PR V1.X
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants