Fails to verify device in QuickStart 1.2.0

RE: Fails to verify device in QuickStart 1.2.0

Øyvind — Tue, 21 Jan 2025 10:27:16 GMT

Seems like the path to nrfjprog is missing if you are not able to initiate it from Terminal. That said, nrfjprog is deprecated and will be replaced with nrf util. Have you installed this?

RE: Fails to verify device in QuickStart 1.2.0

perage — Tue, 21 Jan 2025 07:17:39 GMT

Hi! I only get

zsh: command not found: nrfjprog

That seems strange since I've installed segger and did eventually manage to get Thingy up and running. Just 9151dk left now :)

RE: Fails to verify device in QuickStart 1.2.0

Øyvind — Mon, 20 Jan 2025 16:16:30 GMT

Discussing with our developers, this does seem like an issue with permission. It is plausible that the permissions for the folder /tmp/boost_interprocess/ needs to be edited. In your terminal, what do you get when running nrfjprog --ids?

[error] [    nRF] - Exception encountered while attempting to initialize multiprocess client: Operation not permitted
ERROR: An internal error has occurred, please try again.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.

If you get this output from the command, could you please try to change permissons to the folder using sudo chown <username> /tmp/boost_interprocess

Kind regards,
Øyvind

RE: Fails to verify device in QuickStart 1.2.0

perage — Fri, 17 Jan 2025 10:12:20 GMT

Hi!

To rewind, I'm trying both a Thingy91x and an nRF9151DK. If we focus on the latter, when I start nRF Connect for desktop, I choose quickStart (1.2.0) and follow the steps. At the program step, it the "Erase device" bar is green, but the three other bars (Modemcore Firmware 2.0.2, Application Core (nrf MultiCloud) and "Reset Device" steps are red with an error below "Failed to erase device". The development console of the app is empty.

The log is attached

2025-01-17T10:05:37.596Z INFO Initialising the bundled nrfutil device
2025-01-17T10:05:37.598Z DEBUG Started watching devices
2025-01-17T10:05:38.111Z INFO Using the bundled core version for nrfutil device: 7.13.0
2025-01-17T10:05:38.136Z INFO Using nrfutil-device version: 2.7.5
2025-01-17T10:05:38.136Z INFO Using nrf-device-lib version: 0.17.41
2025-01-17T10:05:38.136Z INFO Using nrfjprog DLL version: Unknown
2025-01-17T10:05:38.136Z INFO Using JLink version: JLink_V7.94i
2025-01-17T10:06:30.157Z DEBUG Selected device: nRF9151 DK
2025-01-17T10:06:30.172Z DEBUG Changed step: Info
2025-01-17T10:06:37.443Z DEBUG Changed step: Rename
2025-01-17T10:06:38.645Z DEBUG Changed step: Program
2025-01-17T10:06:41.789Z ERROR [jlink] [NRFJPROG][nRF][-] Exception encountered while attempting to initialize multiprocess client: Operation not permitted
2025-01-17T10:06:41.789Z ERROR [jlink] NRFJPROG_open_dll_inst returned -254
2025-01-17T10:06:41.792Z ERROR [jlink] [NRFJPROG][nRF][-] Exception encountered while attempting to initialize multiprocess client: Operation not permitted
2025-01-17T10:06:41.792Z ERROR plugin(jlink) enumerate failed with error: 9, msg: [jlink] INTERNAL_ERROR
2025-01-17T10:06:42.638Z ERROR [jlink] [NRFJPROG][nRF][-] Exception encountered while attempting to initialize multiprocess client: Operation not permitted

I assume there's something with the Jlink, affecting both nRF9151DK and the Thingy91x init.

RE: Fails to verify device in QuickStart 1.2.0

Øyvind — Fri, 17 Jan 2025 09:22:15 GMT

Hello, Michal is currently out of office and asked me to follow up with your ticket.

[quote user=""]I just received my Thingy91x. I followed the onboarding and created a provisioning profile in NRF Cloud. The device did not connect and no logs appeared in Serial terminal stating it did. (Only connected to serial port)[/quote]

Did you follow the steps and scan the QR code on the Thingy:91X? Did this not work to add the device to hello.nrfcloud.com? Or were you past that part and wanted to add this to your nRF Cloud account?

[quote user=""]I tried to follow the quickstart again, but same issue.[/quote]

Which of the four applications did you program the Thingy with?

I have seen issues with the verifying step failing before, usually a repeat of the steps have solved the issue. Could you please open the Developer tools in Quick Start with Command + Option + i and see if there are any messages, errors or similar while doing the verification?

Kind regards,
Øyvind

RE: Fails to verify device in QuickStart 1.2.0

perage — Fri, 17 Jan 2025 07:16:58 GMT

Hi Michal!

This is the log from the QuickStart in nRF Connect for mac 1.2.0

RE: Fails to verify device in QuickStart 1.2.0

Michal — Thu, 16 Jan 2025 19:56:20 GMT

Sorry, I have somehow managed to miss that in the second log, you are correct.

Which application provides those logs? Is it what you get when you open the serial terminal?

Best regards,

Michal

RE: Fails to verify device in QuickStart 1.2.0

perage — Thu, 16 Jan 2025 19:33:36 GMT

Hi!

I’ve tried multiple versions. Take a look at the second log. Tested version is used

RE: Fails to verify device in QuickStart 1.2.0

Michal — Thu, 16 Jan 2025 19:28:14 GMT

Hello,

From your log it seems like a JLink issue.

You should first try to do what the log says:

2025-01-16T08:26:22.282Z INFO Your version of SEGGER J-Link (8.12a) is newer than the one this app was tested with (7.94i). The tested version is not required, and your J-Link version will most likely work fine. If you get issues related to J-Link with your devices, use the tested version.

Best regards,

Michal