J-Link does not recognize the chip, but can write and debug normally：
The modem fails to write：
J-Link does not recognize the chip, but can write and debug normally：
The modem fails to write：
Can you enable verbose logging, and send us the log?
Verbose logging can be enabled in the "About" panel:
Hi，
Here is the verbose log：
14:49:37.363 [PID:24372] nrfutil-device (version = 2.0.3, platform = x86_64-pc-windows-msvc) invoked with device-info --serial-number 000059406895 --json --log-output=stdout --log-level trace
14:49:38.132 [PID:24372] Loaded plugin C:\Users\RandomSky\AppData\Roaming\nrfconnect\nrfutil-sandboxes\device\2.0.3\lib\nrfutil-device\10-nrfdl-jlink-plugin.nrfdl, starting to resolve symbols
14:49:38.689 [PID:24372] close plugin dll at path: C:\Users\RandomSky\AppData\Roaming\nrfconnect\nrfutil-sandboxes\device\2.0.3\lib\nrfutil-device\10-nrfdl-jlink-plugin.nrfdl
14:49:38.833 Using nrfutil device to communicate with target via JLink
14:49:38.833 JLink OB firmware version J-Link V9 compiled May 7 2021 16:26:12
14:49:38.833 Device family
14:49:38.833 Device version NRF9161_xxAA_REV3
14:49:38.833 Board version
14:49:38.855 Update files regions according to Application core
14:49:38.855 Parse memory regions for file
14:49:39.113 [PID:18780] nrfutil-device (version = 2.0.3, platform = x86_64-pc-windows-msvc) invoked with protection-get --generate --core Application --json --log-output=stdout --log-level trace
14:49:39.426 [PID:33732] nrfutil-device (version = 2.0.3, platform = x86_64-pc-windows-msvc) invoked with x-execute-batch --serial-number 000059406895 --batch-json {"operations":[{"operationId":"0","core":"NRFDL_DEVICE_CORE_APPLICATION","operation":{"type":"protection-get"}}]} --json --log-output=stdout --log-level trace
14:49:40.175 [PID:33732] Loaded plugin C:\Users\RandomSky\AppData\Roaming\nrfconnect\nrfutil-sandboxes\device\2.0.3\lib\nrfutil-device\10-nrfdl-jlink-plugin.nrfdl, starting to resolve symbols
14:49:40.488 Reading readback protection status for Application core
14:49:40.488 Reading readback protection status for Application core 0%
14:49:40.490 Reading readback protection status for Application core 100%
14:49:40.490 Application core protection status 'NRFDL_PROTECTION_STATUS_NONE'
14:49:40.491 Reading readback protection status for Application core completed
14:49:40.613 [PID:33732] close plugin dll at path: C:\Users\RandomSky\AppData\Roaming\nrfconnect\nrfutil-sandboxes\device\2.0.3\lib\nrfutil-device\10-nrfdl-jlink-plugin.nrfdl
14:49:41.084 [PID:19792] nrfutil-device (version = 2.0.3, platform = x86_64-pc-windows-msvc) invoked with core-info --generate --core Application --json --log-output=stdout --log-level trace
14:49:41.114 [PID:34776] nrfutil-device (version = 2.0.3, platform = x86_64-pc-windows-msvc) invoked with reset --generate --core Application --reset-kind RESET_DEBUG --json --log-output=stdout --log-level trace
14:49:41.416 [PID:20992] nrfutil-device (version = 2.0.3, platform = x86_64-pc-windows-msvc) invoked with x-execute-batch --serial-number 000059406895 --batch-json {"operations":[{"operationId":"0","core":"NRFDL_DEVICE_CORE_APPLICATION","operation":{"type":"core-info"}},{"operationId":"1","core":"NRFDL_DEVICE_CORE_APPLICATION","operation":{"option":"RESET_DEBUG","type":"reset"}}]} --json --log-output=stdout --log-level trace
14:49:42.157 [PID:20992] Loaded plugin C:\Users\RandomSky\AppData\Roaming\nrfconnect\nrfutil-sandboxes\device\2.0.3\lib\nrfutil-device\10-nrfdl-jlink-plugin.nrfdl, starting to resolve symbols
14:49:42.497 Loading core information for Application core
14:49:42.498 Loading core information for Application core 0%
14:49:42.499 Update files regions according to Application core
14:49:42.499 Parse memory regions for file
14:49:42.532 Loading core information for Application core 100%
14:49:42.532 Loading core information for Application core completed
14:49:42.534 Update files regions according to Application core
14:49:42.534 Parse memory regions for file
14:49:42.660 [PID:20992] close plugin dll at path: C:\Users\RandomSky\AppData\Roaming\nrfconnect\nrfutil-sandboxes\device\2.0.3\lib\nrfutil-device\10-nrfdl-jlink-plugin.nrfdl
14:49:43.180 [PID:23260] nrfutil-device (version = 2.0.3, platform = x86_64-pc-windows-msvc) invoked with protection-get --generate --core Application --json --log-output=stdout --log-level trace
14:49:43.495 [PID:13236] nrfutil-device (version = 2.0.3, platform = x86_64-pc-windows-msvc) invoked with x-execute-batch --serial-number 000059406895 --batch-json {"operations":[{"operationId":"0","core":"NRFDL_DEVICE_CORE_APPLICATION","operation":{"type":"protection-get"}}]} --json --log-output=stdout --log-level trace
14:49:44.198 [PID:13236] Loaded plugin C:\Users\RandomSky\AppData\Roaming\nrfconnect\nrfutil-sandboxes\device\2.0.3\lib\nrfutil-device\10-nrfdl-jlink-plugin.nrfdl, starting to resolve symbols
14:49:44.522 Reading readback protection status for Application core
14:49:44.522 Reading readback protection status for Application core 0%
14:49:44.537 Reading readback protection status for Application core 100%
14:49:44.538 Application core protection status 'NRFDL_PROTECTION_STATUS_NONE'
14:49:44.538 Reading readback protection status for Application core completed
14:49:44.642 [PID:13236] close plugin dll at path: C:\Users\RandomSky\AppData\Roaming\nrfconnect\nrfutil-sandboxes\device\2.0.3\lib\nrfutil-device\10-nrfdl-jlink-plugin.nrfdl
14:49:44.868 Device is loaded and ready for further operation
14:49:52.145 Checking ZIP file: D:\ZZY\ZIP\nrf9161dk_fw_2023-10-26_1fae141f.zip
14:49:52.145 File was last modified at 2023/12/14 13:52:14
14:49:54.886 [PID:23400] nrfutil-device (version = 2.0.3, platform = x86_64-pc-windows-msvc) invoked with recover --generate --core Application --json --log-output=stdout --log-level trace
14:49:54.917 [PID:28884] nrfutil-device (version = 2.0.3, platform = x86_64-pc-windows-msvc) invoked with core-info --generate --core Application --json --log-output=stdout --log-level trace
14:49:54.934 [PID:24000] nrfutil-device (version = 2.0.3, platform = x86_64-pc-windows-msvc) invoked with reset --generate --core Application --reset-kind RESET_DEBUG --json --log-output=stdout --log-level trace
14:49:55.227 [PID:2292] nrfutil-device (version = 2.0.3, platform = x86_64-pc-windows-msvc) invoked with x-execute-batch --serial-number 000059406895 --batch-json {"operations":[{"operationId":"0","core":"NRFDL_DEVICE_CORE_APPLICATION","operation":{"type":"recover"}},{"operationId":"1","core":"NRFDL_DEVICE_CORE_APPLICATION","operation":{"type":"core-info"}},{"operationId":"2","core":"NRFDL_DEVICE_CORE_APPLICATION","operation":{"option":"RESET_DEBUG","type":"reset"}}]} --json --log-output=stdout --log-level trace
14:49:55.955 [PID:2292] Loaded plugin C:\Users\RandomSky\AppData\Roaming\nrfconnect\nrfutil-sandboxes\device\2.0.3\lib\nrfutil-device\10-nrfdl-jlink-plugin.nrfdl, starting to resolve symbols
14:49:56.355 Recovering Application core
14:49:56.358 Recovering Application core 0%
14:49:56.358 [PID:2292] [jlink] Using firmware image for recovery to keep device unlocked.
14:49:57.112 [PID:2292] [jlink] [NRFJPROG][nRF91][000059406895] Encountered error while disabling AP-protect, retrying. -21:APPROTECT is still active after CTRL-AP eraseall has finished.
14:49:58.245 Recovering Application core 100%
14:49:58.245 Recovering Application core completed
14:49:58.245 Loading core information for Application core
14:49:58.245 Loading core information for Application core 0%
14:49:58.247 Update files regions according to Application core
14:49:58.247 Parse memory regions for file
14:49:58.276 Loading core information for Application core 100%
14:49:58.277 Loading core information for Application core completed
14:49:58.277 Update files regions according to Application core
14:49:58.277 Parse memory regions for file
14:49:58.389 [PID:2292] close plugin dll at path: C:\Users\RandomSky\AppData\Roaming\nrfconnect\nrfutil-sandboxes\device\2.0.3\lib\nrfutil-device\10-nrfdl-jlink-plugin.nrfdl
14:49:58.859 [PID:29228] nrfutil-device (version = 2.0.3, platform = x86_64-pc-windows-msvc) invoked with device-info --serial-number 000059406895 --json --log-output=stdout --log-level trace
14:49:59.614 [PID:29228] Loaded plugin C:\Users\RandomSky\AppData\Roaming\nrfconnect\nrfutil-sandboxes\device\2.0.3\lib\nrfutil-device\10-nrfdl-jlink-plugin.nrfdl, starting to resolve symbols
14:50:00.163 [PID:29228] close plugin dll at path: C:\Users\RandomSky\AppData\Roaming\nrfconnect\nrfutil-sandboxes\device\2.0.3\lib\nrfutil-device\10-nrfdl-jlink-plugin.nrfdl
14:50:00.345 Update files regions according to Application core
14:50:00.345 Parse memory regions for file
14:50:00.614 [PID:27232] nrfutil-device (version = 2.0.3, platform = x86_64-pc-windows-msvc) invoked with protection-get --generate --core Application --json --log-output=stdout --log-level trace
14:50:00.894 [PID:6892] nrfutil-device (version = 2.0.3, platform = x86_64-pc-windows-msvc) invoked with x-execute-batch --serial-number 000059406895 --batch-json {"operations":[{"operationId":"0","core":"NRFDL_DEVICE_CORE_APPLICATION","operation":{"type":"protection-get"}}]} --json --log-output=stdout --log-level trace
14:50:01.635 [PID:6892] Loaded plugin C:\Users\RandomSky\AppData\Roaming\nrfconnect\nrfutil-sandboxes\device\2.0.3\lib\nrfutil-device\10-nrfdl-jlink-plugin.nrfdl, starting to resolve symbols
14:50:01.976 Reading readback protection status for Application core
14:50:01.976 Reading readback protection status for Application core 0%
14:50:01.986 Reading readback protection status for Application core 100%
14:50:01.986 Application core protection status 'NRFDL_PROTECTION_STATUS_NONE'
14:50:01.986 Reading readback protection status for Application core completed
14:50:02.083 [PID:6892] close plugin dll at path: C:\Users\RandomSky\AppData\Roaming\nrfconnect\nrfutil-sandboxes\device\2.0.3\lib\nrfutil-device\10-nrfdl-jlink-plugin.nrfdl
Thanks.
The problem is probably that the underlying library only uses the serial number of the debugger to determine if the device supports writing modem FW or not.
As a temporary workaround until we can fix the issue, can you try to use the Debug Out port on your nRF9161DK instead of a stand-alone debugger?
Thanks.
May I have an approximate time for the problem? If possible, could you tell me the progress on devzone？
So how to connect the development board hardware can use the debug port on the 9160DK?
You can find more information about the debug out headers here: https://infocenter.nordicsemi.com/topic/ug_nrf91_dk/UG/nrf91_DK/hw_debug_out.html