-
Notifications
You must be signed in to change notification settings - Fork 179
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
Change light example from WiFi to Thread? (CON-1611) #1340
Comments
@olavt You can simply change the target to esp32h2 to switch from WiFi to thread, you can refer to this file for thread device configuration https://github.com/espressif/esp-matter/blob/main/examples/light/sdkconfig.defaults.esp32h2 the command set target is: idf.py set-target esp32h2 |
Does this mean that I could either change the settings according to the link above OR change the target device from ESP32-C6 to ESP32-H2? Are all other settings identical between ESP32-C6 and ESP32-H2? |
I set the Espressif Device Target to "espp32h2" and still got these build errors: /Users/olavt/esp/v5.4/esp-idf/components/openthread/openthread/src/core/meshcop/secure_transport.cpp: In member function 'ot::Error ot::MeshCoP::SecureTransport::Setup(bool)':
|
@olavt If you want to run a thread device on esp32c6, you can use the sdkconfig.defaults.c6_thread, the command is: |
@Jerry-ESP I use VS Code with the Esptressif ESP-IDF Extension with Matter support. I executed the command and got quite a few warnings and when I build the project I still get errors: olavt@Olavs-MacBook-Pro light % idf.py -D SDKCONFIG_DEFAULTS="sdkconfig.defaults.c6_thread" set-target esp32c6 From Build: /Users/olavt/esp/v5.4/esp-idf/components/openthread/openthread/src/core/meshcop/secure_transport.cpp:340:5: error: 'mbedtls_ssl_conf_handshake_timeout' was not declared in this scope; did you mean 'mbedtls_ssl_conf_read_timeout'?
|
Please share your current esp-matter and esp-idf commit-id. |
ESP-IDF:olavt@Mac esp-idf % git log -1
ESP-MATTER:olavt@Mac esp-matter % git log -1
|
I have tried on my side, it seems have some issue in this idf version, can you change a idf version, latest release/v5.3, release/v5.4 , v5.2.3, v5.3.2 ... are OK |
Using "release/v5.4" worked" What's the difference between "v5.4" and "release/v5.4"? Does "release/v5.4" contain some changes that was committed after "v5.4" was released? |
The release/v5.4 branch will keep update, after release v5.4 tag, it should have many commits. For other newer idf version, as we haven't tested fully, there maybe some unknown issues. |
Where can I see that the current version is v5.2.3? Normally I would assume that the release with the highest version number (v5.4) would be the current version and that it have been fully tested. |
Another related question: I want to change the sensors example from WiFi to Thread, but there is no "sdkconfig.defaults.c6_thread" file in the sensors example. Can I copy the file from the light example and use it with the sensor example with no problems? I tried and it failed with: FAILED: partition_table/partition-table.bin /Users/olavt/Source/Repos/sensors/build/partition_table/partition-table.bin
I didn't see any settings related to the flash size in "sdkconfig.defaults.c6_thread". |
In our esp-matter SDK, we have the specified idf version in the readme.md |
From the log, the issue is that in the partition.csv, Partitions tables occupies 3.9MB of flash (4087808 bytes), but in your sdkconfig, the flash size you specified is 2M, you should change the flash size to 4MB in the sdkconfig. If it still not work, you can show me your operation step by step, and share me the logs. |
What changes are required to change the light example from WiFi to Thread?
I tried to change the following in the SDK Configuration editor:
But, I get build errors like these:
/Users/olavt/esp/v5.4/esp-idf/components/openthread/openthread/src/core/meshcop/secure_transport.cpp:340:5: error: 'mbedtls_ssl_conf_handshake_timeout' was not declared in this scope; did you mean 'mbedtls_ssl_conf_read_timeout'?
340 | mbedtls_ssl_conf_handshake_timeout(&mConf, 8000, 60000);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| mbedtls_ssl_conf_read_timeout
/Users/olavt/esp/v5.4/esp-idf/components/openthread/openthread/src/core/meshcop/secure_transport.cpp:349:9: error: 'mbedtls_ssl_conf_dtls_cookies' was not declared in this scope; did you mean 'mbedtls_ssl_conf_dn_hints'?
349 | mbedtls_ssl_conf_dtls_cookies(&mConf, mbedtls_ssl_cookie_write, mbedtls_ssl_cookie_check, &mCookieCtx);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| mbedtls_ssl_conf_dn_hints
/Users/olavt/esp/v5.4/esp-idf/components/openthread/openthread/src/core/meshcop/secure_transport.cpp:365:16: error: 'mbedtls_ssl_set_hs_ecjpake_password' was not declared in this scope
365 | rval = mbedtls_ssl_set_hs_ecjpake_password(&mSsl, mPsk, mPskLength);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/Users/olavt/esp/v5.4/esp-idf/components/openthread/openthread/src/core/meshcop/secure_transport.cpp: In member function 'ot::Error ot::MeshCoP::SecureTransport::SetClientId(const uint8_t*, uint8_t)':
/Users/olavt/esp/v5.4/esp-idf/components/openthread/openthread/src/core/meshcop/secure_transport.cpp:746:16: error: 'mbedtls_ssl_set_client_transport_id' was not declared in this scope; did you mean 'mbedtls_ssl_conf_transport'?
746 | int rval = mbedtls_ssl_set_client_transport_id(&mSsl, aClientId, aLength);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| mbedtls_ssl_conf_transport
/Users/olavt/esp/v5.4/esp-idf/components/openthread/openthread/src/core/meshcop/secure_transport.cpp: In member function 'void ot::MeshCoP::SecureTransport::Process()':
/Users/olavt/esp/v5.4/esp-idf/components/openthread/openthread/src/core/meshcop/secure_transport.cpp:1126:17: error: 'mbedtls_ssl_set_hs_ecjpake_password' was not declared in this scope
1126 | mbedtls_ssl_set_hs_ecjpake_password(&mSsl, mPsk, mPskLength);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[264/1679] Performing build step for 'chip_gn'
The text was updated successfully, but these errors were encountered: