mirror of https://github.com/wolfSSL/wolfBoot.git
The comment labeled IMG_STATE_TESTING as an 'ELF loading state', but the constant is wolfBoot's general dual-bank confirm/rollback marker: it is set on the BOOT partition after every swap (update_flash.c, update_flash_hwswap.c, update_ram.c - none ELF-specific) and cleared by wolfBoot_success(); if still present at the next boot it triggers a rollback. A maintainer trusting the old comment could have treated the state as inert on non-ELF targets and disabled the anti-brick path. Reword to the accurate description already used in docs/flash_partitions.md, keeping the note that it only lives on the boot partition so it cannot conflict with IMAGE_STATE_UPDATING. Comment-only change; no code or behavior changes. |
||
|---|---|---|
| .. | ||
| arm_tee_api.h | ||
| dice.h | ||
| version.h | ||
| wc_secure.h | ||
| wcs_fwtpm.h | ||
| wcs_pkcs11.h | ||
| wcs_wolfhsm.h | ||
| wolfboot.h | ||
| wolfhsm_flash_hal.h | ||