Repository navigation
Clarification on MCUboot Image Compression Support and Integration (Update Modes, Dependencies, Testing) #2686
Unanswered
durgagopisetty00-ops
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
We are evaluating MCUboot image compression mechanism and would like clarification on a few points:
1. Update mode support
Our understanding is that image compression is supported only in overwrite‑only mode and not in any of the swap modes. Could you please confirm if this is correct?
2. Zephyr dependency
Compression appears to rely on Zephyr’s compression/decompression stack.
When using MCUboot outside Zephyr, are there any additional dependencies or integration requirements to use the same compression algorithm from different stack?
3. Testing / validation
Are there existing test cases or references for validating compression(along with encryption) support, especially for non‑Zephyr RTOS or bare‑metal integrations?
Could you please share the current maturity level of the image compression feature in MCUboot? Specifically, has it been extensively tested/validated (e.g., in production use or across multiple platforms), or is it still considered experimental?
Any pointers to documentation, code references would be appreciated.
All reactions