Fails to verify device in QuickStart 1.2.0

[perage]

Hi,

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)

I tried to follow the quickstart again, but same issue. Then I turned the device off/on and tried again, after deleting the provisioning profiles created earlier.

Now It get stuck on step 4 - verify with error "Failed to verify device". If I skip that step, it stops also on providing a token.

2025-01-16T08:26:21.514Z INFO Initialising the bundled nrfutil device
2025-01-16T08:26:21.522Z DEBUG Started watching devices
2025-01-16T08:26:22.259Z INFO Using the bundled core version for nrfutil device: 7.13.0
2025-01-16T08:26:22.282Z INFO Using nrfutil-device version: 2.7.5
2025-01-16T08:26:22.282Z INFO Using nrf-device-lib version: 0.17.41
2025-01-16T08:26:22.282Z INFO Using nrfjprog DLL version: Unknown
2025-01-16T08:26:22.282Z INFO Using JLink version: JLink_V8.12a
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.
2025-01-16T08:26:24.516Z DEBUG Selected device: Nordic Thingy:91 X
2025-01-16T08:26:24.527Z DEBUG Changed step: Info
2025-01-16T08:26:26.297Z DEBUG Changed step: Rename
2025-01-16T08:26:28.187Z DEBUG Changed step: Program
2025-01-16T08:26:31.263Z ERROR [jlink] [NRFJPROG][nRF][-] Exception encountered while attempting to initialize multiprocess client: Operation not permitted
2025-01-16T08:26:31.263Z ERROR [jlink] NRFJPROG_open_dll_inst returned -254
2025-01-16T08:26:31.267Z ERROR [jlink] [NRFJPROG][nRF][-] Exception encountered while attempting to initialize multiprocess client: Operation not permitted
2025-01-16T08:26:31.267Z ERROR plugin(jlink) enumerate failed with error: 9, msg: [jlink] INTERNAL_ERROR
2025-01-16T08:26:32.381Z ERROR [mcuboot] delete package returns error 607
2025-01-16T08:27:54.023Z DEBUG Changed step: Verify
2025-01-16T08:27:57.062Z INFO Opened port with options: {"path":"/dev/tty.usbmodem1102","baudRate":115200}
2025-01-16T08:27:58.066Z ERROR Error: Received ERROR as return value from AT command
2025-01-16T08:27:58.069Z INFO Closed port: /dev/tty.usbmodem1102
2025-01-16T08:31:02.258Z DEBUG Changed step: Program
2025-01-16T08:31:03.512Z DEBUG Changed step: Verify
2025-01-16T08:31:04.609Z DEBUG Changed step: SIM
2025-01-16T08:31:05.853Z DEBUG Changed step: Verify
2025-01-16T08:31:06.774Z INFO Opened port with options: {"path":"/dev/tty.usbmodem1102","baudRate":115200}
2025-01-16T08:31:07.775Z ERROR Error: Received ERROR as return value from AT command
2025-01-16T08:31:07.777Z INFO Closed port: /dev/tty.usbmodem1102
2025-01-16T08:31:15.597Z INFO Opened port with options: {"path":"/dev/tty.usbmodem1102","baudRate":115200}
2025-01-16T08:31:15.628Z DEBUG Shell Parser: loadToBuffer: Shell prompt has not been set
2025-01-16T08:31:15.628Z DEBUG Shell Parser: loadToBuffer: Shell prompt has not been set
2025-01-16T08:31:15.628Z DEBUG Shell Parser: loadToBuffer: Shell prompt has not been set
2025-01-16T08:31:15.628Z DEBUG Shell Parser: loadToBuffer: Shell prompt has not been set
2025-01-16T08:31:15.628Z DEBUG Shell Parser: loadToBuffer: Shell prompt has not been set
2025-01-16T08:31:15.628Z DEBUG Shell Parser: loadToBuffer: Shell prompt has not been set
2025-01-16T08:31:15.628Z DEBUG Shell Parser: loadToBuffer: Shell prompt has not been set
2025-01-16T08:31:15.629Z DEBUG Shell Parser: loadToBuffer: Shell prompt has not been set
2025-01-16T08:31:15.629Z DEBUG Shell Parser: loadToBuffer: Shell prompt has not been set
2025-01-16T08:31:15.629Z DEBUG Shell Parser: loadToBuffer: Shell prompt has not been set
2025-01-16T08:31:15.629Z DEBUG Shell Parser: loadToBuffer: Shell prompt has not been set
2025-01-16T08:31:15.629Z DEBUG Shell Parser: loadToBuffer: Shell prompt has not been set
2025-01-16T08:31:15.629Z DEBUG Shell Parser: loadToBuffer: Shell prompt has not been set
2025-01-16T08:31:15.629Z DEBUG Shell Parser: loadToBuffer: Shell prompt has not been set
2025-01-16T08:31:15.629Z DEBUG Shell Parser: loadToBuffer: Shell prompt has not been set
2025-01-16T08:31:15.629Z DEBUG Shell Parser: loadToBuffer: Shell prompt has not been set
2025-01-16T08:31:15.629Z DEBUG Shell Parser: loadToBuffer: Shell prompt has not been set
2025-01-16T08:31:15.629Z DEBUG Shell Parser: loadToBuffer: Shell prompt has not been set
2025-01-16T08:31:15.629Z DEBUG Shell Parser: loadToBuffer: Shell prompt has not been set
2025-01-16T08:31:15.629Z DEBUG Shell Parser: found shell prompt: "uart:~$ "
2025-01-16T08:31:16.598Z ERROR Error: Received ERROR as return value from AT command
2025-01-16T08:31:16.600Z INFO Closed port: /dev/tty.usbmodem1102
2025-01-16T08:31:17.659Z DEBUG Changed step: SIM
2025-01-16T08:31:19.187Z DEBUG Changed step: Evaluate
2025-01-16T08:31:19.224Z INFO Opened port with options: {"path":"/dev/tty.usbmodem1102","baudRate":115200}
2025-01-16T08:31:19.583Z DEBUG Shell Parser: loadToBuffer: Shell prompt has not been set
2025-01-16T08:31:19.583Z DEBUG Shell Parser: loadToBuffer: Shell prompt has not been set
2025-01-16T08:31:19.583Z DEBUG Shell Parser: loadToBuffer: Shell prompt has not been set
2025-01-16T08:31:19.583Z DEBUG Shell Parser: loadToBuffer: Shell prompt has not been set
2025-01-16T08:31:19.583Z DEBUG Shell Parser: loadToBuffer: Shell prompt has not been set
2025-01-16T08:31:19.583Z DEBUG Shell Parser: loadToBuffer: Shell prompt has not been set
2025-01-16T08:31:19.583Z DEBUG Shell Parser: loadToBuffer: Shell prompt has not been set
2025-01-16T08:31:19.583Z DEBUG Shell Parser: loadToBuffer: Shell prompt has not been set
2025-01-16T08:31:19.583Z DEBUG Shell Parser: loadToBuffer: Shell prompt has not been set
2025-01-16T08:31:19.583Z DEBUG Shell Parser: loadToBuffer: Shell prompt has not been set
2025-01-16T08:31:19.583Z DEBUG Shell Parser: loadToBuffer: Shell prompt has not been set
2025-01-16T08:31:19.583Z DEBUG Shell Parser: loadToBuffer: Shell prompt has not been set
2025-01-16T08:31:19.584Z DEBUG Shell Parser: loadToBuffer: Shell prompt has not been set
2025-01-16T08:31:19.584Z DEBUG Shell Parser: loadToBuffer: Shell prompt has not been set
2025-01-16T08:31:19.584Z DEBUG Shell Parser: loadToBuffer: Shell prompt has not been set
2025-01-16T08:31:19.584Z DEBUG Shell Parser: loadToBuffer: Shell prompt has not been set
2025-01-16T08:31:19.584Z DEBUG Shell Parser: loadToBuffer: Shell prompt has not been set
2025-01-16T08:31:19.584Z DEBUG Shell Parser: loadToBuffer: Shell prompt has not been set
2025-01-16T08:31:19.584Z DEBUG Shell Parser: loadToBuffer: Shell prompt has not been set
2025-01-16T08:31:19.584Z DEBUG Shell Parser: found shell prompt: "uart:~$ "
2025-01-16T08:31:20.225Z ERROR Error: Received ERROR as return value from AT command
2025-01-16T08:31:20.227Z INFO Closed port: /dev/tty.usbmodem1102
2025-01-16T08:31:28.112Z DEBUG Changed step: SIM
2025-01-16T08:31:29.224Z DEBUG Changed step: Verify

I connected a nRF9151DK and tried that, and it stops on the program step as well. 

2025-01-16T14:40:13.714Z INFO Initialising the bundled nrfutil device
2025-01-16T14:40:13.717Z DEBUG Started watching devices
2025-01-16T14:40:14.111Z INFO Using the bundled core version for nrfutil device: 7.13.0
2025-01-16T14:40:14.135Z INFO Using nrfutil-device version: 2.7.5
2025-01-16T14:40:14.135Z INFO Using nrf-device-lib version: 0.17.41
2025-01-16T14:40:14.135Z INFO Using nrfjprog DLL version: Unknown
2025-01-16T14:40:14.135Z INFO Using JLink version: JLink_V7.94i
2025-01-16T14:40:16.715Z DEBUG Selected device: nRF9151 DK
2025-01-16T14:40:16.729Z DEBUG Changed step: Info
2025-01-16T14:40:17.940Z DEBUG Changed step: Rename
2025-01-16T14:40:18.448Z DEBUG Changed step: Program
2025-01-16T14:40:20.765Z ERROR [jlink] [NRFJPROG][nRF][-] Exception encountered while attempting to initialize multiprocess client: Operation not permitted
2025-01-16T14:40:20.765Z ERROR [jlink] NRFJPROG_open_dll_inst returned -254
2025-01-16T14:40:20.769Z ERROR [jlink] [NRFJPROG][nRF][-] Exception encountered while attempting to initialize multiprocess client: Operation not permitted
2025-01-16T14:40:20.769Z ERROR plugin(jlink) enumerate failed with error: 9, msg: [jlink] INTERNAL_ERROR
2025-01-16T14:40:21.363Z ERROR [jlink] [NRFJPROG][nRF][-] Exception encountered while attempting to initialize multiprocess client: Operation not permitted

I've tried to install both latest, and newer versions of Segger, but the problem persists.

System: Mac ARM (M2, latest macOS)

Please advice! 

[Michal]

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

[perage]

Hi!

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

[Michal]

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

[perage]

Hi Michal! 

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

[Øyvind]

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

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)

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?

I tried to follow the quickstart again, but same issue.

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