Trouble using nrfjprog

Question

I am moving from SES to Visual Studio Code and having trouble connecting to my device. In nRF for Desktop Connect (V 4.1.2) I tried Programmer (V3.0.9) to connect to a custom board to which I can connect to using SES (using the dropdown connect to device in SES). The Programmer log shows: 
 
 16:14:29.493 
 Using nrf-device-lib-js version: 0.6.12

16:14:29.494 
 Using nrf-device-lib version: 0.15.3

16:14:29.495 
 Using nrfjprog DLL version: 10.19.1

16:14:29.495 
 Using JLink version: JLink_V7.88l

16:14:29.784 
 Installed JLink version does not match the provided version (V7.80c) 
 
 And I cannot see a device connected; all the option drop-down are gray.

Within Visual Studio, under devices connected I see:

When I try to flash a simple example code (UART-Bluetooth sample), Visual Studio shows: 
 
 Executing task: nRF Connect: Flash: central_uart/build (active) Flashing build to 4294967295 /bin/sh -c west flash -d /Users/wadesmith/Documents/GitHub/HP_V5/central_uart/build --skip-rebuild --dev-id 4294967295 -- west flash: using runner nrfjprog -- runners.nrfjprog: Flashing file: /Users/ws/Documents/GitHub/HP_V5/central_uart/build/zephyr/zephyr.hex [error] [ Client] - Encountered error -102: Command connect_to_emu_with_snr executed for 49 milliseconds with result -102 ERROR: Unable to connect to a debugger. [error] [ Worker] - An unknown error. ERROR: JLinkARM DLL reported an error. Try again. If error condition ERROR: persists, run the same command again with argument --log, contact Nordic ERROR: Semiconductor and provide the generated log.log file to them. NOTE: For additional output, try running again with logging enabled (--log). NOTE: Any generated log error messages will be displayed. FATAL ERROR: command exited with status 33: nrfjprog --program /Users/wadesmith/Documents/GitHub/HP_V5/central_uart/build/zephyr/zephyr.hex --sectoranduicrerase --verify -f NRF52 --snr 4294967295 
 
 Here is the version of nrfjprog: 
 
 % nrfjprog --version 
 nrfjprog version: 10.22.1 external 
 JLinkARM.dll version: 7.88l

In terminal I enter the same call to nrfjprog and it produces the same error as follows:

% nrfjprog --program /Users/ws/Documents/GitHub/HP_V5/central_uart/build/zephyr/zephyr.hex --sectoranduicrerase --verify -f NRF52 --snr 4294967295 
 [error] [ Client] - Encountered error -102: Command connect_to_emu_with_snr executed for 47 milliseconds with result -102 
 ERROR: Unable to connect to a debugger. 
 [error] [ Worker] - An unknown error. 
 ERROR: JLinkARM DLL reported an error. 
 
 This is on a Mac Silicon M1 (Ventura 13.4.1); I installed the universal J-Link tool. Thoughts about what I am doing wrong? I appreciate the help.

Vidar Berg · Accepted Answer

[2023-Jul-28 09:53:46] [trace] [ JLink] - JLINK_GetSN() [2023-Jul-28 09:53:46] [trace] [ JLink] - - 0.007ms returns -1 
 
 Thank you for providing the log file. The issue arises because the debugger's serial number is set to 4294967295, which equals 0xFFFFFFFF. This corresponds to "-1" when it is interpreted as a two's complement value by the J-Link library, and negative values are treated as errors. I guess SES must be ignoring this error. 
 Please contact Segger support if this is a genuine debug probe. The serial number is supposed to be set during production.

wade smith · Answer

Thank you Vidar for figuring this out. I will check with SEGGER- I bought the probe from them.

Trouble using nrfjprog

Top Replies