Our device is configured with MCUboot in direct-xip mode with revert. We want to flash a build that contains both a test firmware and the main application, with the expectation that the system will boot the test firmware first and then transition to the main firmware.
This flow is blocked by the current version-based image selection. If the test firmware has a lower version than the main app, MCUboot immediately boots the main app and skips the test firmware. If the test firmware has a higher version, it boots correctly into the test firmware, but afterward it is not possible to update to the main app because its version is lower.
As a result, it is not possible to guarantee the intended sequence (test firmware first, then main firmware) in a combined image. We are looking for guidance on whether MCUboot can be configured or extended to support this flow, or if a different approach is recommended.
Environment nRF Connect SDK v3.1.0 and MCUboot v2.1.0.
