NRF Connect for Desktop Programmer cannot find nrfutil unless ran using sudo on Mac

Hello,

After an update to the NRF connect for Desktop the Programmer application can no longer program my nRF52840 dev kit (PCA10056, 3.0.0).  Trying to revert the update I still cannot get it working again and see the same error messages in the logs.  

NRF Connect for Desktop Version 5.1.0

Programmer version 4.4.2

I took logs from the Programmer app when I ran NRF Connect for Desktop with and without sudo.

NO sudo (some details removed for privacy)

2024-12-04T17:04:31.207Z INFO Initialising the bundled nrfutil device
2024-12-04T17:04:31.237Z DEBUG Application data folder: /Users/$USER/Library/Application Support/nrfconnect/pc-nrfconnect-programmer
2024-12-04T17:04:31.364Z DEBUG Sending event "programmer: running nrfutil device"
2024-12-04T17:04:31.364Z DEBUG App pc-nrfconnect-programmer v4.4.2 (official)
2024-12-04T17:04:31.364Z DEBUG App path: /Users/$USER/.nrfconnect-apps/node_modules/pc-nrfconnect-programmer
2024-12-04T17:04:31.364Z DEBUG nRFConnect 5.1.0, required by the app is (>=5.0.2)
2024-12-04T17:04:31.364Z DEBUG nRFConnect path: /Applications/nRF Connect for Desktop.app/Contents/Resources/app.asar
2024-12-04T17:04:31.365Z DEBUG HomeDir: /Users/$USER
2024-12-04T17:04:31.365Z DEBUG TmpDir: /var/folders/6x/t9pchjp97szf_wl7h1ndd1n80000gp/T/
2024-12-04T17:04:31.431Z DEBUG Sending event "programmer: running nrfutil device"
2024-12-04T17:04:32.577Z DEBUG Sending event "programmer: running nrfutil device"
2024-12-04T17:04:32.577Z DEBUG Sending event "programmer: running nrfutil device"
2024-12-04T17:04:32.578Z DEBUG Sending event "programmer: running nrfutil device"
2024-12-04T17:04:32.785Z INFO Using nrfutil-device version: 2.6.4
2024-12-04T17:04:32.785Z INFO Using nrf-device-lib version: 0.17.35
2024-12-04T17:04:32.786Z WARN Unable to detect version of nrfjprog DLL.
2024-12-04T17:04:32.786Z INFO Using JLink version: JLink_V7.94i
2024-12-04T17:04:32.821Z INFO Using the bundled core version for nrfutil device: 7.13.0
2024-12-04T17:04:39.918Z INFO Getting serial port options from the persistent store for 001050216005.pc-nrfconnect-programmer
2024-12-04T17:04:39.920Z DEBUG Sending event "programmer: device connected"
2024-12-04T17:04:40.220Z INFO Getting serial port options from the persistent store for 001050216005.pc-nrfconnect-programmer
2024-12-04T17:04:40.222Z DEBUG Sending event "programmer: device connected"
2024-12-04T17:04:40.240Z INFO Getting serial port options from the persistent store for 001050216005.pc-nrfconnect-programmer
2024-12-04T17:04:40.241Z DEBUG Sending event "programmer: device connected"
2024-12-04T17:04:44.908Z INFO Selecting device with the serial number 001050216005
2024-12-04T17:04:44.916Z DEBUG Sending event "programmer: running nrfutil device"
2024-12-04T17:04:45.304Z ERROR Error: Failed with exit code 1.
Failed to device info one or more devices:
 * 1050216005: [jlink] INTERNAL_ERROR, code: Nrfjlink.
Message: Operation device-info failed, [jlink] INTERNAL_ERROR.
2024-12-04T17:04:45.304Z INFO Selected device with the serial number 001050216005
2024-12-04T17:04:45.304Z INFO Using nrfutil device to communicate with target via JLink
2024-12-04T17:04:45.306Z DEBUG Sending event "programmer: device selected"
2024-12-04T17:04:45.307Z DEBUG Sending event "programmer: running nrfutil device"
2024-12-04T17:04:45.475Z DEBUG Sending event "programmer: running nrfutil device"
2024-12-04T17:04:45.801Z INFO Reading readback protection status for Application core
2024-12-04T17:04:45.801Z ERROR Failed "reading readback protection status for application core". Error: code: 9, description: Nrfjlink, message: Batch task protection-get failed, [jlink] INTERNAL_ERROR
2024-12-04T17:04:45.806Z ERROR Error: Failed with exit code 1.
One or more batch tasks failed:
 - [jlink] INTERNAL_ERROR, code: Nrfjlink.
Message: Batch task protection-get failed, [jlink] INTERNAL_ERROR.
2024-12-04T17:04:45.806Z ERROR Error: Failed with exit code 1.
One or more batch tasks failed:
 - [jlink] INTERNAL_ERROR, code: Nrfjlink.
Message: Batch task protection-get failed, [jlink] INTERNAL_ERROR.

Here are the logs when ran w/sudo

09:09:18.657	Initialising the bundled nrfutil device
09:09:20.279	Using the bundled core version for nrfutil device: 7.13.0
09:09:20.439	Using nrfutil-device version: 2.6.4
09:09:20.439	Using nrf-device-lib version: 0.17.35
09:09:20.440	Using nrfjprog DLL version: 10.24.2
09:09:20.440	Using JLink version: JLink_V7.94i
09:09:26.013	Getting serial port options from the persistent store for 001050216005.pc-nrfconnect-programmer
09:09:26.320	Getting serial port options from the persistent store for 001050216005.pc-nrfconnect-programmer
09:09:26.421	Getting serial port options from the persistent store for 001050216005.pc-nrfconnect-programmer
09:09:32.793	Selecting device with the serial number 001050216005
09:09:33.464	Selected device with the serial number 001050216005
09:09:33.464	Using nrfutil device to communicate with target via JLink
09:09:33.464	JLink OB firmware version J-Link OB-nRF5340-NordicSemi compiled Oct 9 2024 11:01:34
09:09:33.464	Device family NRF52_FAMILY
09:09:33.464	Device version NRF52840_xxAA_REV3
09:09:33.464	Board version PCA10056
09:09:34.029	Reading readback protection status for Application core
09:09:34.031	Reading readback protection status for Application core 0%
09:09:34.032	Reading readback protection status for Application core 100%
09:09:34.032	Application core protection status 'NRFDL_PROTECTION_STATUS_NONE'
09:09:34.033	Reading readback protection status for Application core completed
09:09:34.704	Loading core information for Application core
09:09:34.705	Loading core information for Application core 0%
09:09:34.745	Loading core information for Application core 100%
09:09:34.745	Loading core information for Application core completed
09:09:34.748	Reading memory for Application core
09:09:34.749	Reading memory for Application core 0%
09:09:41.897	Reading memory for Application core 100%
09:09:43.504	Reading memory for Application core completed
09:09:43.506	Parse memory regions for Application core
09:09:43.506	SoftDevice detected, id 0xCE (S340 v7.0.1)
09:09:44.064	Reading readback protection status for Application core
09:09:44.065	Reading readback protection status for Application core 0%
09:09:44.067	Reading readback protection status for Application core 100%
09:09:44.067	Application core protection status 'NRFDL_PROTECTION_STATUS_NONE'
09:09:44.067	Reading readback protection status for Application core completed
09:09:44.146	Device is loaded and ready for further operation
09:09:44.758	Unable to open the log file: Error: Command failed: open /var/root/Library/Application\ Support/nrfconnect/pc-nrfconnect-programmer/logs/2024-12-04T17_09_18.509Z-log.txt _LSOpenURLsWithCompletionHandler() failed with error -5000 for the file /var/root/Library/Application Support/nrfconnect/pc-nrfconnect-programmer/logs/2024-12-04T17_09_18.509Z-log.txt.

  • Hi Jamie,

    There's been some similar experiences both internal and external on this behaviour and we are investigating. Assumption is that there's some part of the support for the nRF54L15 that conflicts with programming other devices in some situations. However, the way out is to open a powershell or terminal and run "nrfutil device recover"

    After that, you should be able to use your device again as normal. We are working on finding the cause and updating the SW deliveries from us.

    Best regards

    Asbjørn

  • Hi Asbjørn,

    Thanks for the response.  I am able to work around this using sudo like I mentioned.  My nrf52840 DK is running just fine with the ANT+ heart rate monitor example from nRF5 SDK 17.1.0.  I ported it to use  soft device version s340.  I was using nrf Connect for Desktop to flash the soft device before flashing the app from Segger Embedded Studio and then ran into this issue on my second day of development after installing an nrf Connect for Desktop update.  I raised this ticket because I assumed other's might run into this issue after updating the desktop app. 

    Thanks,

    -Jamie

  • Hi Jamie,
    I'm glad you found a way around and that you have a working setup. We will hopefully see less of this, but great to have a reference for others.
    Thank you
    Asbjørn
Related