Failed compilation of esp-matter v1.4.2 light example project with ESP-IDF v5.4.1

[Nicola_Bizzotto]

Hello,

I'm testing ESP32-C6 (ESP32-C6-DevKitC-1) with Espressif's SDK for Matter.

My project requires to use Matter version 1.4.2 and Matter-over-Thread communication.
I have configured a development environment inside a Virtual Machine with Ubuntu 24.04.3 LTS.
I got the required repositories (ESP-IDF v5.4.1 + esp-matter release/v1.4.2) as described here https://docs.espressif.com/projects/esp ... oping.html.
I'm using Visual Studio Code with ESP-IDF extension version 1.11.1.

I've tried the esp-matter light example project, selected esp32c6 target and set the following in SDK config:

• CONFIG_OPENTHREAD_ENABLED=y
• CONFIG_ENABLE_WIFI_STATION=n
• CONFIG_USE_MINIMAL_MDNS=n

When compiling I get this error:

compilation_fail.txt

(18.7 KiB) Downloaded 14 times

The error seems to be related to openthread component. Retracing the cloning procedure of the esp-idf repository, I believe that the problem is linked to the fact that it was not possible to perform the checkout on commit 005c5cefc22aaf0396e4327ee7f2e0ad32a7733b of the 'components/openthread/openthread' submodule, like it is visible from the following log

esp_idf_clone_log.txt

(32.6 KiB) Downloaded 13 times

What am I doing wrong?

I've tried using ESP-IDF v5.4.2 instead and, without changing anything else, I'm able to compile the esp-matter light example project, which then runs correctly on the ESP32-C6-DevKitC-1. I would like to know if I can continue with ESP-IDF v5.4.2 or how I can resolve the problems with v5.4.1, which should be the recommended version to use for esp-matter 1.4.2.

Thank you.
Best regards.

[Nicola_Bizzotto]

I managed to complete compilation with ESP-IDF v5.4.1 by manually downloading and replacing the openthread submodule:

openthread.jpg (75.81 KiB) Viewed 323 times

So my problem is basically solved. Anyway, could you please elaborate a bit about the problem with openthread checkout? Is this a known problem or did I do something wrong?

Thank you.
Best regards.

[wangqx]

Hi, I am not sure why your submodule updating fails, It is possible that the remote repo URL of openthread is wrong so that it cannot find the commit ID. You can try to use `git submodule sync --recursive` to make git use the right URL for the openthread submodule.

[Nicola_Bizzotto]

Thank you for your reply.
I tried using 'git submodule sync --recursive' prior to 'git submodule update --init --recursive' but this didn't solve the problem: the checkout of '005c5cefc22aaf0396e4327ee7f2e0ad32a7733b' of openthread still fails.