Hi,
I'm currently developing a nr9160 full modem DFU based on sdk v1.5.0 and "fmu_fdev" (https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.5.0/nrf/include/dfu/fmfu_fdev.html#lib-fmfu-fdev). My implementation uses a custom serial protocol to get the modem update image from UART, as I'm using an old devkit (with SoC rev B0) which doesn't have the external flash storage.
I can successfully update my nrf9160 modem from v1.2.0 to v1.3.0 using the ".cbor" image from https://www.nordicsemi.com/-/media/Software-and-other-downloads/Dev-Kits/nRF9160-DK/nRF9160-modem-FW/mfw_nrf9160_1.3.0.zip.
However, when using http://nrfconnectsdk.s3.eu-central-1.amazonaws.com/fmfu_1.2.1.bin or http://nrfconnectsdk.s3.eu-central-1.amazonaws.com/fmfu_1.2.2.bin from the http_update/full_Modem_update sample (https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.5.0/nrf/samples/nrf9160/http_update/full_modem_update/README.html) the "nrf_modem_full_dfu_verify()" function returns -1, with errno= 1 (NRF_EPERM).
If I skip the pre-validation, the modem update successfully, and the "AT+CGMR" command reports "mfw_nrf9160_1.2.1" or "mfw_nrf9160_1.2.2".
Is there something different with the v1.2.1 and v1.2.2 images provided with the "full_modem_update_sample" compared to the v1.3.0?
Thanks,
Louis
