I am unable to program modem firmware (.zip) file to my device when there is no application firmware (.hex) file installed on said device. However, I have no issue programming the modem firmware file when an application firmware file is already installed on the same device. Why is this? See attached error log.
Error code's attachment did not upload. Here is the content of the error .txt file:
2023-07-19T20:25:43.471Z DEBUG Application data folder: C:\Users\jdavid\AppData\Roaming\nrfconnect\pc-nrfconnect-programmer
2023-07-19T20:25:43.603Z DEBUG App pc-nrfconnect-programmer v3.0.9 local
2023-07-19T20:25:43.603Z DEBUG App path: C:\Users\jdavid\.nrfconnect-apps\node_modules\pc-nrfconnect-programmer
2023-07-19T20:25:43.603Z DEBUG nRFConnect 4.1.1, required by the app is (>=4.0.0)
2023-07-19T20:25:43.603Z DEBUG nRFConnect path: C:\Users\jdavid\AppData\Local\Programs\nrfconnect\resources\app.asar
2023-07-19T20:25:43.603Z DEBUG HomeDir: C:\Users\jdavid
2023-07-19T20:25:43.603Z DEBUG TmpDir: C:\Users\jdavid\AppData\Local\Temp
2023-07-19T20:25:45.372Z INFO Installed JLink version does not match the provided version (V7.80c)
2023-07-19T20:25:45.471Z INFO Using nrf-device-lib-js version: 0.6.8
2023-07-19T20:25:45.472Z INFO Using nrf-device-lib version: 0.14.13
2023-07-19T20:25:45.472Z INFO Using nrfjprog DLL version: 10.19.1
2023-07-19T20:25:45.472Z INFO Using JLink version: JLink_V7.88i
2023-07-19T20:25:45.783Z INFO Getting serialport options from persistent store 000052000943.pc-nrfconnect-programmer
2023-07-19T20:25:45.784Z INFO Getting serialport options from persistent store A50285BI.pc-nrfconnect-programmer
2023-07-19T20:25:45.785Z INFO Getting serialport options from persistent store {00000000-0000-0000-FFFF-FFFFFFFFFFFF}.pc-nrfconnect-programmer
2023-07-19T20:25:47.809Z INFO Using @nordicsemiconductor/nrf-device-lib-js to communicate with target via JLink
2023-07-19T20:25:47.810Z INFO JLink OB firmware version J-Link V12 compiled Jun 21 2023 09:20:55
2023-07-19T20:25:47.810Z INFO Device family NRF91_FAMILY
2023-07-19T20:25:47.810Z INFO Device version NRF9160_xxAA_REV2
2023-07-19T20:25:47.810Z INFO Board version Unknown
2023-07-19T20:25:47.811Z INFO Loading readback protection status for Application core
2023-07-19T20:25:48.479Z DEBUG Client Id: 97b0bfe9-b688-43fe-83cf-b9cf16679967
2023-07-19T20:25:48.936Z INFO Readback protection status: NRFDL_PROTECTION_STATUS_NONE
2023-07-19T20:25:49.716Z INFO Modem detected
2023-07-19T20:25:49.719Z INFO Parse memory regions for Application core
2023-07-19T20:25:49.722Z INFO Update files regions according to Application core
2023-07-19T20:25:49.722Z INFO Parse memory regions for file
2023-07-19T20:25:49.726Z INFO Device is loaded and ready for further operation
2023-07-19T20:25:49.728Z INFO Reading memory for NRFDL_DEVICE_CORE_APPLICATION core
2023-07-19T20:25:51.242Z DEBUG Google Analytics for category pc-nrfconnect-programmer has initialized
2023-07-19T20:25:57.739Z INFO Reading memory for NRFDL_DEVICE_CORE_APPLICATION core completed
2023-07-19T20:25:57.741Z INFO Parse memory regions for Application core
2023-07-19T20:25:58.516Z INFO Resetting device completed
2023-07-19T20:26:17.149Z INFO Checking ZIP file: C:\Users\jdavid\Desktop\SnT VI's\mfw_nrf9160_1.3.2.zip
2023-07-19T20:26:17.161Z INFO File was last modified at 6/14/2023, 1:44:09 PM
2023-07-19T20:26:28.479Z INFO Modem DFU starts to write...
2023-07-19T20:26:28.479Z INFO Writing C:\Users\jdavid\Desktop\SnT VI's\mfw_nrf9160_1.3.2.zip to device 000052000943
2023-07-19T20:26:29.251Z ERROR Modem DFU failed with error: async task failure for id: 401286653 msg: [jlink] NOT_AVAILABLE_BECAUSE_TRUST_ZONE (Origin: "Error when running device operation program")
2023-07-19T20:26:29.253Z ERROR async task failure for id: 401286653 msg: [jlink] NOT_AVAILABLE_BECAUSE_TRUST_ZONE (Origin: "Error when running device operation program")
2023-07-19T20:26:29.254Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open jlink OB version","label":"J-Link V12 compiled Jun 21 2023 09:20:55"}
2023-07-19T20:26:29.257Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open jlink device family","label":"NRF91_FAMILY"}
2023-07-19T20:26:29.259Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open jlink device version","label":"NRF9160_xxAA_REV2"}
2023-07-19T20:26:29.261Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open jlink device board version","label":"Unknown"}
2023-07-19T20:26:29.262Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open device","label":"jlink"}
2023-07-19T20:26:29.264Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"architecture","label":"x64"}
2023-07-19T20:26:29.265Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Report error","label":"win32; x64; v3.0.9; async task failure for id: 401286653 msg: [jlink] NOT_AVAILABLE_BECAUSE_TRUST_ZONE (Origin: \"Error when running device operation program\")"}
I do follow these steps. The weird issue that happens is I am unable to update modem firmware (.zip) when there is no .hex file installed first.
Is that also trye if you erase the device?
From the guide:
"If you experience problems updating the modem firmware, click Erase all in the DEVICE section of the side panel and try updating again."
Yes, even after erase or erase all, the modem firmware will not update without a .hex file installed first.