PhLuReh
commented
7 months ago Btw, I found this issue https://github.com/espressif/esp-idf/issues/2580 for the idf, but it was from 2018 and I think this one should be fixed.
Closed PhLuReh closed 7 months ago
PhLuReh
commented
7 months ago Btw, I found this issue https://github.com/espressif/esp-idf/issues/2580 for the idf, but it was from 2018 and I think this one should be fixed.
dhrishi
commented
7 months ago @PhLuReh Can you please upload your sdkconfig file? Is this with the standard light example (without any changes)? Also, does this occur everytime or in a random manner?
PhLuReh
commented
7 months ago this is my sdkconfig The problem is persistent. Everytime I try to commission the device with the chip-tool this error occurs.
I tried to run the light app from the examples, but I was not able to commission to the chip-tool. (I was using a ESP32S3 in favour of my ESP32 from my product im developing). The device is only getting connected via BLE and responds to chip-tool, but no Wifi-Credentials are set nor connected to the AP.
dhrishi
commented
7 months ago @PhLuReh Looks like some of the sdkconfig options do not match the Matter v1.1 codebase. Were you at some point working on v1.2 or main branch of Matter with the same example? If yes, can you delete your sdkconfig file and give it a try
$ cd /path/to/your_example
$ rm -rf sdkconfig sdkconfig.old build/
$ idf.py menuconfig #If required to change any options
$ idf.py erase-flash build flash monitornice, it's working again. I did idf.py fullclean and hoped this would also erase sdkconfig. I learned something new, like everyday...
So maybe it would be helpful, if you would comment what exactly lead you to this diagnose? I never thought about this solution and maybe someone else stumbles upon similar errors.
dhrishi
commented
7 months ago Your attached sdkconfig has
CONFIG_LWIP_TCPIP_CORE_LOCKING=y
CONFIG_LWIP_CHECK_THREAD_SAFETY=yThese options are enabled in Matter v1.2 and not in Matter v1.1. Now, when you used these options with v1.1, the corresponding code related to it is not present on the v1.1 branch and hence the errors.
Describe the bug After updating esp-matter to f511d226420f56a0565f7b147ebc399f88afc3ce with all its referenced submodules, the device is facing an assertion error in the LWIP while joining MDNS groups. This happens to a to-be-commissioned device after Wifi connection is established.
Could you assist in finding the correct build framework or even a fix?
here is a longer log: 20240228_DUT-log.txt
Environment
Linux version 6.1.29-1-MANJARO (builduser@fv-az292-908) (gcc (GCC) 12.2.1 20230201, GNU ld (GNU Binutils) 2.40) #1 SMP PREEMPT_DYNAMIC Wed May 17 14:00:55 UTC 2023Any additional details
As I suspect there is some dependency issue, here is a full list of the connectedhomeip subodule hashes: