Unable to build ESP Matter with ESP-IDF

[real_mon2]

Hello. Have a few days of failed attempts to setup and compile the ESP Matter IP with ESP-IDF.

Using an Ubuntu box and following this thread:

https://docs.espressif.com/projects/esp ... oping.html

Setup crashes and burns at assorted spots. Was this setup tested?

Also, can ESP32-C5 support MATTER CONTROLLER? The gitup shows only a configuration file for the ESP32-S3 target. The AI searches sometimes will show that ESP32-C5 can support being a MATTER CONTROLLER but this forum AI states it is not supported.

We are attempting to build a prototype for a product line with MATTER and the ESP32-C5 is currently on our custom PCB layout. Should we replace the module with the ESP32-S3 or is ESP32-C5 (preferred) supported?

Will keep trying for a fix.

failed_ESP1.png (60.98 KiB) Viewed 1639 times

[real_mon2]

AI is reporting to:

git submodule sync && git submodule update --init

to fix the above fault. Will attempt and update this thread.

[real_mon2]

Crash and burn again. Not surprised.

failed_ESP2.png (78.56 KiB) Viewed 1637 times

[real_mon2]

From here:

https://github.com/espressif/esp-matter/issues/212

Try deleting the esp-matter/connectedhomeip/connectedhomeip/.environment folder manually and try install.sh again. It worked for me.

Results in:

failed_ESP3.png (69.47 KiB) Viewed 1633 times

From this:

https://stackoverflow.com/questions/669 ... to-install

Can confirm, I have been installing ns3 V3.33 and around [2447/2973] compilation this error came out.

For the solution I doubled the base memory of my VM (2048mb -> 4096mb), then the compilation finished successfully.

Do we need to have more ram in our VM?

server.png (9.57 KiB) Viewed 1633 times

[real_mon2]

The VM cloud server is fine with the selected resources.

Installed the ESP-IDF and the ESP-MATTER toolchain ok.

Attempting to compile for ESP32C5 which is under '--preview' mode. Fine.

idf.py --preview set-target esp32c5

Created the build files.

Ran:

idf.py build ; to create the .bin files.

Crashes.

/root/esp-matter/components/esp_matter/data_model_provider/clusters/network_commissioning_integration.cpp:51:49: error: static assertion failed: NetworkCommissioningCluster count must be more than 0
51 | static_assert(kNetworkCommissioningClusterCount > 0, "NetworkCommissioningCluster count must be more than 0");
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~

[real_mon2]

On this day # 3 of trying to compile..

Changed the target to: esp32S3

idf.py set-target esp32S3

Results in a successful completion.

[1275/1276] Generating binary image from built executable
esptool.py v4.10.0
Creating esp32s3 image...
Merged 2 ELF sections
Successfully created esp32s3 image.
Generated /root/esp-matter/examples/controller/build/controller.bin
[1276/1276] cd /root/esp-matter/examples/controller/build/esp-idf/esptool_py && ...le/partition-table.bin /root/esp-matter/examples/controller/build/controller.bin
controller.bin binary size 0x1d3110 bytes. Smallest app partition is 0x200000 bytes. 0x2cef0 bytes (9%) free.

Project build complete. To flash, run:
idf.py flash
or
idf.py -p PORT flash
or
python -m esptool --chip esp32s3 -b 460800 --before default_reset --after hard_reset write_flash --flash_mode dio --flash_size 8MB --flash_freq 80m 0x0 build/bootloader/bootloader.bin 0x8000 build/partition_table/partition-table.bin 0x1d000 build/ota_data_initial.bin 0x20000 build/controller.bin
or from the "/root/esp-matter/examples/controller/build" directory
python -m esptool --chip esp32s3 -b 460800 --before default_reset --after hard_reset write_flash "@flash_args"

Summary: ESP32C5 is NOT properly supported for this project and this MATTER CONTROLLER IP.

Any ETA on a working solution? We are also reviewing the NXP RW612 solution. Will shelve this module till there is stability.

[real_mon2]

bump.

Does Espressif have a local (USA/Canada) matter guru available for a quick chat?

Some additional questions to the list are:

1) Can any ESP32 matter based client send a cluster command to another node on the same fabric? Or does this local ESP32 matter client be a matter controller? Espressif has a specific project for 'matter controller' which appears to compile fine when the target is the ESP32-S3. Fails with errors if the target is ESP32-C5. This may be linked to esp-idf 5.4 (rather than 5.5.1) showing in our toolchain installation. Need to look into this on our side.

2) What exactly needs to be configured inside of the menuconfig for the ESP32-C5 / -S3 targets to allow for showing commissioning logs and use as a matter controller.

3) Is the matter controller with LCD GUI project for the S3 BOX public? Saw this demo in one of the videos but not sure if the code is public. With this IP, we do not require homekit or alexa, etc.?

4) Can we use the ESP-MATTER SDK to extract the IDs of any node on the same fabric so that our ESP32 widget can control the same remote matter node device? Or can we do this only with CHIP-TOOL? Can chip-tool run on ESP32 or only with Linux on PC, RPI, etc.?

[real_mon2]

bump

Installed ESP-IDF 5.5.2

idf.py set-target esp32s3 ; works to build a .bin file ok

idf.py set-target esp32c5 ; crashes and burns

idf.py --preview set-target esp32c5 ; crashes and burns

Fairly confident to state that the ESP32C5 is not supported for this project. Support must be in the witness protection program or early CNY holidays.