Using AWS OTA with ESP-Matter (CON-840)

[anuarrozman]

Im planning on using AWS OTA features with Matter. My OTA function is ready and has been tested. Ive created my AWS OTA as component in ESP-Matter. Any resources or help i can get regarding this thing ?

[shubhamdp]

We have a some docs which talks about Matter OTA. It also includes how to use encrypted OTA, you can take a look at that.

You may need to increment version number which matter basic information cluster reads. Take a look at this FAQ.

[anuarrozman]

Thanks a bunch !! Ive done ESP AWS OTA demo and it works just fine. I've managed to make the AWS OTA as a component in my Matter project folder. When running with Matter, it has problem on connecting to my AWS endpoint which is not an issue when running AWS OTA without Matter.

[anuarrozman]

From my reading, Matter CSA allows any method of OTA update right ? Not strictly bind to their OTA method.

[shubhamdp]

13.5. Firmware
a. Nodes SHALL support OTA firmware updates, either using Matter-provided means (see Section 11.19, “Over-the-Air (OTA) Software Update”) or proprietary means. [CM58 for T59, T226]

This is from Matter Core Specification v1.2.

There has to be some means to OTA the device either Matter OTA or proprietary one.

[dhrishi]

Closing as the question is answered

[shubhamdp]

Thanks a bunch !! Ive done ESP AWS OTA demo and it works just fine. I've managed to make the AWS OTA as a component in my Matter project folder. When running with Matter, it has problem on connecting to my AWS endpoint which is not an issue when running AWS OTA without Matter.

Can you check the free memory when using Matter. You can refer the below snippet for getting the values.

esp-matter/components/esp_matter_console/esp_matter_console_diagnostics.cpp

Lines 27 to 38 in 9bada61

	static esp_err_t mem_dump_console_handler(int argc, char *argv[])
	{
	printf("\tDescription\tInternal\tSPIRAM\n");
	printf("Current Free Memory\t%d\t\t%d\n",
	heap_caps_get_free_size(MALLOC_CAP_8BIT) - heap_caps_get_free_size(MALLOC_CAP_SPIRAM),
	heap_caps_get_free_size(MALLOC_CAP_SPIRAM));
	printf("Largest Free Block\t%d\t\t%d\n", heap_caps_get_largest_free_block(MALLOC_CAP_8BIT | MALLOC_CAP_INTERNAL),
	heap_caps_get_largest_free_block(MALLOC_CAP_SPIRAM));
	printf("Min. Ever Free Size\t%d\t\t%d\n", heap_caps_get_minimum_free_size(MALLOC_CAP_8BIT | MALLOC_CAP_INTERNAL),
	heap_caps_get_minimum_free_size(MALLOC_CAP_SPIRAM));
	return ESP_OK;
	}

[dhrishi]

When running with Matter, it has problem on connecting to my AWS endpoint which is not an issue when running AWS OTA without Matter.

Sorry for missing this. I have reopened the issue

[anuarrozman]

Hiii, Thanks for the responses.

13.5. Firmware
a. Nodes SHALL support OTA firmware updates, either using Matter-provided means (see Section 11.19, “Over-the-Air (OTA) Software Update”) or proprietary means. [CM58 for T59, T226]

This is from Matter Core Specification v1.2.

There has to be some means to OTA the device either Matter OTA or proprietary one.

Yeap, Ive read this and think this could work.

Thanks a bunch !! Ive done ESP AWS OTA demo and it works just fine. I've managed to make the AWS OTA as a component in my Matter project folder. When running with Matter, it has problem on connecting to my AWS endpoint which is not an issue when running AWS OTA without Matter.

Can you check the free memory when using Matter. You can refer the below snippet for getting the values.

esp-matter/components/esp_matter_console/esp_matter_console_diagnostics.cpp

Lines 27 to 38 in 9bada61

	static esp_err_t mem_dump_console_handler(int argc, char *argv[])
	{
	printf("\tDescription\tInternal\tSPIRAM\n");
	printf("Current Free Memory\t%d\t\t%d\n",
	heap_caps_get_free_size(MALLOC_CAP_8BIT) - heap_caps_get_free_size(MALLOC_CAP_SPIRAM),
	heap_caps_get_free_size(MALLOC_CAP_SPIRAM));
	printf("Largest Free Block\t%d\t\t%d\n", heap_caps_get_largest_free_block(MALLOC_CAP_8BIT | MALLOC_CAP_INTERNAL),
	heap_caps_get_largest_free_block(MALLOC_CAP_SPIRAM));
	printf("Min. Ever Free Size\t%d\t\t%d\n", heap_caps_get_minimum_free_size(MALLOC_CAP_8BIT | MALLOC_CAP_INTERNAL),
	heap_caps_get_minimum_free_size(MALLOC_CAP_SPIRAM));
	return ESP_OK;
	}

For this, Ive check the heap memory using ESP_LOGI(TAG, "[APP] Free memory: %"PRIu32" bytes", esp_get_free_heap_size()); this one is from ESP-IDF. When running both Matter and AWS, free heap memory during establishing connection to AWS is around 40000 - 50000 bytes. Without Matter, establishing connection to AWS will left around 100000+ bytes of free heap memory. Can this be the cause ? Sometimes when esp try to reestablish the AWS connection to the endpoint, the free heap memory become 900 bytes only, this is status when running with Matter.

[anuarrozman]

Thanks a bunch !! Ive done ESP AWS OTA demo and it works just fine. I've managed to make the AWS OTA as a component in my Matter project folder. When running with Matter, it has problem on connecting to my AWS endpoint which is not an issue when running AWS OTA without Matter.

Can you check the free memory when using Matter. You can refer the below snippet for getting the values.

esp-matter/components/esp_matter_console/esp_matter_console_diagnostics.cpp

Lines 27 to 38 in 9bada61

	static esp_err_t mem_dump_console_handler(int argc, char *argv[])
	{
	printf("\tDescription\tInternal\tSPIRAM\n");
	printf("Current Free Memory\t%d\t\t%d\n",
	heap_caps_get_free_size(MALLOC_CAP_8BIT) - heap_caps_get_free_size(MALLOC_CAP_SPIRAM),
	heap_caps_get_free_size(MALLOC_CAP_SPIRAM));
	printf("Largest Free Block\t%d\t\t%d\n", heap_caps_get_largest_free_block(MALLOC_CAP_8BIT | MALLOC_CAP_INTERNAL),
	heap_caps_get_largest_free_block(MALLOC_CAP_SPIRAM));
	printf("Min. Ever Free Size\t%d\t\t%d\n", heap_caps_get_minimum_free_size(MALLOC_CAP_8BIT | MALLOC_CAP_INTERNAL),
	heap_caps_get_minimum_free_size(MALLOC_CAP_SPIRAM));
	return ESP_OK;
	}

Thanks @shubhamdp , I currently looking at this.

[shubhamdp]

the free heap memory become 900 bytes only, this is status when running with Matter

This could be a problem. You may need to optimize the RAM usage. There's a guide from esp-idf to minimize the RAM usage. There's another blog post which talks about the minimizing the memory. Please take a look at them and see if you can reduce the RAM usage.

Also, can you share the following details, which could help to try out this situation?
Environment

• ESP-Matter Commit Id:
• ESP-IDF Commit Id:
• AWS IoT Commit Id:
• SoC (eg: ESP32 or ESP32-C3):
• Device Logs (Please attach the log file):
• Host Machine OS:
• Commissioner app and versions if present:
• Commissioner's logs if present:

[anuarrozman]

Hi @shubhamdp, Im so sorry for the late response. I tried to recreate the RAM issues as well as unable to reconnect to AWS endpoint after device completed the update but suddenly no RAM issue. RAM start at around 199Kb at the start of the firmware, once ble deinit (matter) and RAM value at the start of OTA function is around 85Kb to 90Kb which is enough. I cant find my previous log where the problem occured but I'll just provide with you guys the commit hash of my ESP-Matter and ESP-IDF. I'll also provide the same RAM issue on my team environment.

Here are my environment details:
ESP-Matter Commit Id: 198db12
ESP-IDF Commit Id: ea5e0ff298e6257b31d8e0c81435e6d3937f04c7
AWS IoT Commit Id: d37fd63002b4fda99523e1ac4c9822fce485e76d
SoC (eg: ESP32 or ESP32-C3): ESP32S3

Here are one of my team environment details:
ESP-Matter Commit Id: cd325c6
ESP-IDF Commit Id: ea5e0ff298e6257b31d8e0c81435e6d3937f04c7
AWS IoT Commit Id: d37fd63002b4fda99523e1ac4c9822fce485e76d
SoC (eg: ESP32 or ESP32-C3): ESP32S3

The log i provide is one of my team, since I cant recreate the issue.
idf_py_stdout_output_68121.txt

[dhrishi]

@anuarrozman With the latest main branch, some RAM optimizations are done. Please check those out. Please close the issue if resolved.

[dhrishi]

@anuarrozman Any updates you can share?