Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
aesl_label_sethost capability.wasm-moduleUpdate Module with bounded streaming, monotonic versions, atomic A/B activation, rollback and boot recovery.native_sim, Renode and RT1170 product build profiles, artifact tooling, security-boundary documentation, and fast hosted CI for the maintained WAMR/Mender contract and package failure paths.Test plan
./scripts/build-wamr-rt1170.shand./scripts/test-wamr-renode.sh./scripts/test-native-sim-wamr.sh- v7 to v8, downgrade denied, rollback to v7, corrupt-active recovery to v7, no reboot.mendergenerationwasm-module, compatible typemimxrt1170_evk, providerootfs.wasm-module.version: 8python3 scripts/check-wasm-contract.pyPAYLOAD=/nonexistent/ci-fallback.wasm ./scripts/test-wasm-package.shThe simulator proof deliberately uses deterministic test entropy. Production hardware builds retain CAAM support. The activation-state CRC protects against corruption, not an attacker with arbitrary flash-write access; secure anti-rollback needs an EdgeLock/OTP-backed version floor.
Assisted-by: Codex (OpenAI)