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

Cannot pair M5 board (all cluster app) via scanning QR code #19191

Closed
phonnakasturi-apple opened this issue Jun 3, 2022 · 2 comments
Closed

Comments

@phonnakasturi-apple
Copy link

With SHA 891afbf

Cannot pair M5 board (all cluster app) via scanning QR code.

Steps to reproduce:

  1. cd ~/connectedhomeip

  2. git reset --hard 891afbf

  3. git clean -Xdf

  4. git submodule update --init

  5. export PKG_CONFIG_PATH="/opt/homebrew/opt/openssl@3/lib/pkgconfig"

  6. source scripts/bootstrap.sh

  7. source scripts/activate.sh

  8. cd ~/tools

  9. cd esp-idf

  10. git checkout v4.4

  11. git submodule update --init --recursive
    ./install.sh
    . ./export.sh

  12. cd ~/connectedhomeip/examples/all-clusters-app/esp32

  13. idf.py build

  14. idf.py menuconfig -> Demo -> choose M5 stack.

  15. idf.py -D 'SDKCONFIG_DEFAULTS=sdkconfig_m5stack.defaults' erase_flash build flash monitor

  16. Build chiptool app on iPhone via Xcode

  17. Launch chiptool app on iPhone and scan the QR code from M5 board

Attaching the complete M5 board logs:

M5_Error_logs.txt

@bzbarsky-apple
Copy link
Contributor

@phonnakasturi-apple Is this different from #19135 ? It looks like the same exact issue to me. There's no log from the controller side, but the device log shows:

I (34900) chip[ZCL]: OpCreds: Received a CSRRequest command
I (36170) chip[ZCL]: OpCreds: NewCertificateSigningRequest succeeded
I (36810) chip[ZCL]: OpCreds: CSRRequest successful.

which is longer than 2s to process the command and hence would result in the controller timing out.

This should have been fixed by #19137. Please retest on a SHA after that merged?

@phonnakasturi-apple
Copy link
Author

Yes this was fixed with SHA dd636ad
I will close this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants