Skip to content
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

Update esp_encrypted_img Component Version (CON-1588) #1318

Open
leandropg opened this issue Mar 7, 2025 · 5 comments
Open

Update esp_encrypted_img Component Version (CON-1588) #1318

leandropg opened this issue Mar 7, 2025 · 5 comments

Comments

@leandropg
Copy link

Currently, I am developing a product using the ESP Matter SDK. For the characteristic of the project, I am using HTTPS OTA and specifically the OTA Upgrades with Pre-Encrypted Firmware.

In the example pre_encrypted_ota it uses the the external component espressif/esp_encrypted_img in the latest version 2.3.0.

But this configuration in the ESP Matter SDK restrict to use in the project only the version 2.1.0:

espressif/esp_encrypted_img:
version: "2.1.0"
require: public
rules:
- if: "idf_version >=4.4"

Hence when I configured in my project to use the latest version 2.3.0.

espressif/esp_encrypted_img: ^2.3.0

I obtained this error in compilation time:

CMake Error at /home/user/esp-idf/tools/cmake/build.cmake:552 (message):
  ERROR: Because project depends on both espressif/esp_encrypted_img (^2.3.0)
  and espressif/esp_encrypted_img (2.1.0), version solving failed.

Could you update this configuration to set the latest version available 2.3.0?

Thanks in advance.

@github-actions github-actions bot changed the title Update esp_encrypted_img Component Version Update esp_encrypted_img Component Version (CON-1588) Mar 7, 2025
@shubhamdp
Copy link
Contributor

Could you update this configuration to set the latest version available 2.3.0?

I do not see any feature addition in the changelog of esp_encrypted_img, apart from a minor cmake fix + a get header size API.

Do you have any specific need for using v2.3.0?

Purpose of pinning the exact version was to make sure that connectedhomeip do not break when esp_encrypted_img keeps moving ahead.

For a quick fix, please change the version in this file and give it a go: esp-matter/connectedhomeip/connectedhomeip/config/esp32/components/chip/idf_component.yml

Please let me know it this works for you, so that I can put up the changes in connectedhomeip and then roll the submodule in esp-matter

@leandropg
Copy link
Author

Hi @shubhamdp The reason of the requirement is that the example use this definition in the configuration and it uses the function esp_encrypted_img_get_header_size() only available from the version 2.2.0

https://github.com/espressif/esp-idf/blob/9b74d1aca5f2154c4ea609d6e36d513dcf91148b/examples/system/ota/pre_encrypted_ota/main/pre_encrypted_ota.c#L147

I will make the change and I will confirm you if it worked.

@shubhamdp
Copy link
Contributor

@leandropg appreciate the efforts for pointing out the breakage. Please let us know if it works, and I'll roll up the version, do some tests, and update the submodule here.

Also, which esp-matter branch/commit are you using? It would help decide releases for back porting this change.

@leandropg
Copy link
Author

Hi @shubhamdp Changing the version there to 2.3.0, now the system can download the right component in the version 2.3.0 and now I can compile the project. The system recognize now the function esp_encrypted_img_get_header_size().

Currently my Matter environment is pointing to main branch and specifically the commit 05831a3 (Tue Jan 7 14:45:36 2025).

@shubhamdp
Copy link
Contributor

I have raised the PR here: project-chip/connectedhomeip#37950, PTAL!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants