tree fc49927caa08aa50796f000e453e9920521157fb
parent 195ededb0478c545088e714828486f84ea10ec65
author Arkadiusz Bałys <arkadiusz.balys@nordicsemi.no> 1693311844 +0200
committer GitHub <noreply@github.com> 1693311844 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJk7eNkCRBK7hj4Ov3rIwAAnCAIACSMFNFTo20Xa00pv/T/7WAl
 xZdom1xAV+eYWYaa4hN8dZ2XU09c2B620MnSdzqp77wH0ilq9zsQBd8HWnTeH8/0
 KS8fZ4D69tRy0enkW4UNdueDg/AxQ3J3YNuOT+pQ4Wf2cYPBgYTH/DRCEJobT20S
 xd9a7tGysFlRm5UWuMXTmc3PAfHt7ySMCqo6Xe1QroxyrwVkN3SkVmXt4YuSsKr4
 kU6vQqKqLW5bq3DBvdlWUyriVuPchRKBM0bKb/v++ZIuVpg8sjEklzQQqoLydlG8
 PHcTI3nW13HfgUf38h4pAlDzuIX6+2Le2pyAQ16K3+ZWZxsdWk7k0hwp7wtHpM0=
 =5K4l
 -----END PGP SIGNATURE-----
 

[nrfconnect] [OTA] Confirm the new image in the app init. (#28924)

The nRF5340 target requires 4kB of FPROTECT block size (SPU limitation)
and after making a restriction for the factory data partition the new
image cannot be confirmed after the OTA update finishes.
Due to that, we need to confirm the current OTA image before factory
data initialization.
To do it we should allow confirming the image in the other place
rather than during posting the OTAStateChange event and then we should
inform the image processor of the confirmation status.