Installing Command Line Tools 10.4.0 fails on MacOS (10.14.6)

RE: Installing Command Line Tools 10.4.0 fails on MacOS (10.14.6)

Anders Nelson — Sun, 15 Dec 2019 02:49:25 GMT

Yes I was using a JLink clone but I'm surprised nrfjprog checked the serial number, again considering the log implies it's not interested in the serial number.

I just bought a JLink EDU and the chain works as expected.

Thanks!

RE: Installing Command Line Tools 10.4.0 fails on MacOS (10.14.6)

Vidar Berg — Mon, 09 Dec 2019 13:49:14 GMT

Excellent, it looks to be correctly installed now. But the SN shouldn't be '-1', maybe you have a jlink clone? I found a similar forum post about that here: https://devzone.nordicsemi.com/f/nordic-q-a/43197/nrfjproj-error-jlinkarm-dll-reported-an-error. In that case I would consider to be a Nordic dev kit. It has an on-board Jlink lite.

RE: Installing Command Line Tools 10.4.0 fails on MacOS (10.14.6)

Anders Nelson — Sun, 08 Dec 2019 04:50:00 GMT

Hey Vidor,

I'm getting much further with 10.5.0, now it appears my JLinkARM device's serial number of '-1' is stopping things. I've attached the log here:

2019-Dec-07 23:39:11  --------------------------------------------------------------------------------
2019-Dec-07 23:39:11  ./nrfjprog --reset --program /Users/ufanders/Desktop/sketch_oct10a/sketch_oct10a.ino.feather_nrf52840_express.hex --sectorerase -f nrf52 --log 
2019-Dec-07 23:39:11  nrfjprog version 10.5.0 
2019-Dec-07 23:39:11  --------------------------------------------------------------------------------
2019-Dec-07 23:39:11  nRF_logger_open
2019-Dec-07 23:39:11  nRF_logger_open:	nRFJProg logger opened to callback at address 0X10C1C1AB0
2019-Dec-07 23:39:11  nRF_open_dll
2019-Dec-07 23:39:11  nRF_open_dll:	Load library at "/Applications/Nordic Semiconductor/nrfjprog/libjlinkarm_nrf52_nrfjprogdll.dylib".

2019-Dec-07 23:39:11  . nRF52_logger_open
2019-Dec-07 23:39:11  . nRF52_logger_open:	nRFJProg logger opened to callback at address 0X10C24A130
2019-Dec-07 23:39:11  . nRF52_open_dll
2019-Dec-07 23:39:11  . . Segger_logger_open
2019-Dec-07 23:39:11  . . Segger_logger_open:	nRFJProg logger opened to callback at address 0X10C282C50
2019-Dec-07 23:39:11  . . Segger_open_dll
2019-Dec-07 23:39:11  . . Segger_open_dll:	Load library at "/Applications/SEGGER/JLink/libjlinkarm.6.54.3.dylib".

2019-Dec-07 23:39:11  . . . Segger_dll_version
2019-Dec-07 23:39:11  . . Segger_set_core_data
2019-Dec-07 23:39:11  nRF_enum_emu_snr
2019-Dec-07 23:39:11  . nRF52_enum_emu_snr
2019-Dec-07 23:39:11  . . Segger_enum_emu_snr
2019-Dec-07 23:39:11  . . . Segger_enum_emu_snr
2019-Dec-07 23:39:11  . . . . Segger_get_num_emus
2019-Dec-07 23:39:11  nRF_connect_to_emu_with_snr
2019-Dec-07 23:39:11  . nRF52_connect_to_emu_with_snr
2019-Dec-07 23:39:11  . . Segger_connect_to_emu_with_snr
2019-Dec-07 23:39:11  . . . Segger_is_connected_to_emu
2019-Dec-07 23:39:11  . . . Segger_enum_emu_snr
2019-Dec-07 23:39:11  . . . . Segger_get_num_emus
2019-Dec-07 23:39:11  . . . Segger_connect_to_emu_with_snr
2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr
2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	Segger logging enabled with callback at 0x4498928512.

2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	JLink INFO	T167EE5C0 000:015.635   
2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	JLink INFO	Firmware: J-Link OB-STM32F072-CortexM compiled Jan  7 2019 14:09:37
2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	JLink INFO	T167EE5C0 000:023.725   
2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	JLink INFO	Hardware: V1.00
2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	JLink INFO	T167EE5C0 000:024.120   
2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	JLink INFO	S/N: 4294967295
2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	JLink INFO	T167EE5C0 000:024.364   
2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	JLink INFO	OEM: SEGGER
2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	JLink INFO	T167EE5C0 000:024.651   
2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	JLink INFO	Feature(s): GDB, RDI, FlashBP, FlashDL, JFlash, RDDI
2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	JLink INFO	T167EE5C0 000:027.583   
2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	JLink INFO	TELNET listener socket opened on port 19021
2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	JLink INFO	T167EE5C0 000:027.907   
2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	JLink INFO	WEBSRV Starting webserver
2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	JLink INFO	T167EE5C0 000:028.135   
2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	JLink INFO	WEBSRV Webserver running on local port 19080
2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	JLink INFO	T167EE5C0 000:028.291 
2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	JLink INFO	- 16.704ms returns O.K.  
2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	JLink INFO	T167EE5C0 000:028.447 
2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	JLink INFO	JLINK_GetHWStatus(...)  
2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	JLink INFO	T167EE5C0 000:029.040 
2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	JLink INFO	- 0.686ms returns 0x00  
2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	JLink INFO	T167EE5C0 000:029.233 
2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	JLink INFO	JLINK_ExecCommand("SetRestartOnClose = 0", ...).   
2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	JLink INFO	T167EE5C0 000:029.404 
2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	JLink INFO	- 0.096ms returns 0x01  
2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	JLink INFO	T167EE5C0 000:029.574 
2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	JLink INFO	JLINK_ExecCommand("DisableFlashDL", ...).   
2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	JLink INFO	T167EE5C0 000:029.738 
2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	JLink INFO	- 0.079ms returns 0x00  
2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	JLink INFO	T167EE5C0 000:029.884 
2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	JLink INFO	JLINK_ExecCommand("ExcludeFlashCacheRange 0x0-0xFFFFFFFF", ...).   
2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	JLink INFO	T167EE5C0 000:030.051 
2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	JLink INFO	- 0.078ms returns 0x00  
2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	JLink INFO	T167EE5C0 000:030.190   
2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	JLink INFO	JLINK_SetHookUnsecureDialog(...)
2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	JLink INFO	T167EE5C0 000:030.323 
2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	JLink INFO	- 0.197ms returns 0  
2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	JLink INFO	T167EE5C0 000:030.455 
2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	JLink INFO	JLINK_TIF_Select(JLINKARM_TIF_SWD)  
2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	JLink INFO	T167EE5C0 000:031.208 
2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	JLink INFO	- 0.837ms returns 0x00  
2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	JLink INFO	T167EE5C0 000:031.363 
2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	JLink INFO	JLINK_SetSpeed(2000)  
2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	JLink INFO	T167EE5C0 000:031.591 
2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	JLink INFO	- 0.297ms  
2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	JLinkARM.dll GetSN returned error -1.

2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	JLink INFO	T167EE5C0 000:042.044 
2019-Dec-07 23:39:11  . . . . Segger_connect_to_emu_without_snr:	JLink INFO	JLINK_Close()  
2019-Dec-07 23:39:11  nRF_close_dll
2019-Dec-07 23:39:11  . nRF52_close_dll
2019-Dec-07 23:39:11  . . Segger_close
2019-Dec-07 23:39:11  . . . Segger_disconnect_from_emu
2019-Dec-07 23:39:11  . . . . Segger_is_connected_to_emu
2019-Dec-07 23:39:11  . . Segger_close:	Freeing Library.

2019-Dec-07 23:39:11  nRF_close_dll:	Freeing Library.

nrfjprog seems intent on /not/ checking the serial number, so why is it halting on the result of "Segger_connect_to_emu_without_snr"?

Thanks,

RE: Installing Command Line Tools 10.4.0 fails on MacOS (10.14.6)

Vidar Berg — Mon, 02 Dec 2019 11:16:42 GMT

Please try to install nrfjprog v10.5.0 if you still see the issue. This release included some improvements that might be relevant to this. And if that doesn't help you may also try to install Jlink v.6.54c

RE: Installing Command Line Tools 10.4.0 fails on MacOS (10.14.6)

Anders Nelson — Fri, 22 Nov 2019 04:31:14 GMT

Yes:

$ cd /Applications/SEGGER/
$ ls -l
total 0
lrwxr-xr-x 1 root wheel 32 Nov 5 21:05 JLink -> /Applications/SEGGER/JLink_V654a
drwxr-xr-x 46 root wheel 1472 Nov 4 22:34 JLink_V650b
drwxr-xr-x 48 root wheel 1536 Nov 5 21:05 JLink_V654a

RE: Installing Command Line Tools 10.4.0 fails on MacOS (10.14.6)

Vidar Berg — Mon, 18 Nov 2019 10:10:21 GMT

Do you have a folder name just "JLink" in this folder which points to your JLink_V654a folder?

My current installation:

$ pwd

/Applications/SEGGER

$ ls -l

total 0

lrwxr-xr-x 1 root wheel 32 Nov 15 09:48 JLink -> /Applications/SEGGER/JLink_V654c

drwxr-xr-x 41 root wheel 1312 Jul 16 21:31 JLink_V644e

drwxr-xr-x 48 root wheel 1536 Nov 15 09:48 JLink_V654c

RE: Installing Command Line Tools 10.4.0 fails on MacOS (10.14.6)

Anders Nelson — Sun, 17 Nov 2019 20:08:58 GMT

When I first ran your suggestion, I got this:

$ nrfjprog -e --log
WARNING: No logging will be possible since nrfjprog.exe has no write permission
WARNING: to the current directory.
ERROR: JLinkARM DLL load failed. Try again. If it keeps failing, please
ERROR: reinstall latest JLinkARM from Segger webpage.

I then ran:

$ sudo ./nrfjprog -e --log
Password:
ERROR: JLinkARM DLL load failed. Try again. If it keeps failing, please
ERROR: reinstall latest JLinkARM from Segger webpage.

The log is here:

2019-Nov-17 15:10:05 --------------------------------------------------------------------------------
2019-Nov-17 15:10:05 ./nrfjprog -e --log
2019-Nov-17 15:10:05 nrfjprog version 10.4.1
2019-Nov-17 15:10:05 --------------------------------------------------------------------------------
2019-Nov-17 15:10:05 nRF_logger_open
2019-Nov-17 15:10:05 nRF_logger_open: nRFJProg logger opened to callback at address 0X10A16AD30
2019-Nov-17 15:10:05 nRF_open_dll
2019-Nov-17 15:10:05 nRF_open_dll: Load library at "/Applications/Nordic Semiconductor/nrfjprog/libjlinkarm_unknown_nrfjprogdll.dylib".

2019-Nov-17 15:10:05 . nRFXX_logger_open
2019-Nov-17 15:10:05 . nRFXX_logger_open: nRFJProg logger opened to callback at address 0X10A1EED40
2019-Nov-17 15:10:05 . . Segger_logger_open
2019-Nov-17 15:10:05 . . Segger_logger_open: nRFJProg logger opened to callback at address 0X10A221B00
2019-Nov-17 15:10:05 . . Segger_open_dll
2019-Nov-17 15:10:05 . . Segger_open_dll: Load library at "libjlinkarm.dylib".

2019-Nov-17 15:10:05 . . Segger_open_dll: Failed while loading a function from jlinkarm dll.

2019-Nov-17 15:10:05 . nRF_close_dll
2019-Nov-17 15:10:05 . . nRFXX_close_dll
2019-Nov-17 15:10:05 . nRF_close_dll: Freeing Library.

Here is the alias named ""libjlinkarm.dylib":

Any ideas?

RE: Installing Command Line Tools 10.4.0 fails on MacOS (10.14.6)

Vidar Berg — Fri, 15 Nov 2019 09:18:00 GMT

Anders Nelson, I haven't managed to replicate it on my mac, but I think the nrfjprog log may give us a hint of what the issue is. Could you run "nrfjprog -e --log" and check in the log if both the nRF_open_dll and Segger_open_dll load paths match your installation?

The log I got for reference:

2019-Nov-15 10:07:56  --------------------------------------------------------------------------------
2019-Nov-15 10:07:56  nrfjprog -e --log 
2019-Nov-15 10:07:56  nrfjprog version 10.5.0 
2019-Nov-15 10:07:56  --------------------------------------------------------------------------------
2019-Nov-15 10:07:56  nRF_logger_open
2019-Nov-15 10:07:56  nRF_logger_open:	nRFJProg logger opened to callback at address 0X1051FFAB0
2019-Nov-15 10:07:56  nRF_open_dll
2019-Nov-15 10:07:56  nRF_open_dll:	Load library at "/Applications/Nordic Semiconductor/nrfjprog/libjlinkarm_unknown_nrfjprogdll.dylib".

2019-Nov-15 10:07:56  . nRFXX_logger_open
2019-Nov-15 10:07:56  . nRFXX_logger_open:	nRFJProg logger opened to callback at address 0X105284130
2019-Nov-15 10:07:56  . . Segger_logger_open
2019-Nov-15 10:07:56  . . Segger_logger_open:	nRFJProg logger opened to callback at address 0X1052B60C0
2019-Nov-15 10:07:56  . . Segger_open_dll
2019-Nov-15 10:07:56  . . Segger_open_dll:	Load library at "/Applications/SEGGER/JLink/libjlinkarm.6.54.3.dylib".

RE: Installing Command Line Tools 10.4.0 fails on MacOS (10.14.6)

Anders Nelson — Wed, 13 Nov 2019 01:57:10 GMT

Hi Terje, here are some screenshots of the JLink apps working with my JLink programmer:

They work, but nrfjprog does not. The device and programmer are powered. I tried removing the flags as you suggested but it didn't help. I then shortened the command to simply erase the chip but the same error was displayed.

What else can I try?

RE: Installing Command Line Tools 10.4.0 fails on MacOS (10.14.6)

tesc — Fri, 08 Nov 2019 12:06:46 GMT

Hi,

What board are you using, and have nrfjprog worked previously with your setup?

It may be a different error from what is indicated in the error message. Can you double check that there is indeed a J-Link programmer connected to the device, that it is an nRF52 device, and that the programmer and device are powered? If an nRF52 DK, there programmer should be on the board.

Try without the "-f nrf52" flag as well. nrfjprog should be able to auto-detect the family, and we have seen in some situations that providing the family flag may fail.

Regards,
Terje

RE: Installing Command Line Tools 10.4.0 fails on MacOS (10.14.6)

Anders Nelson — Wed, 06 Nov 2019 01:56:34 GMT

Hi Tesc, nrfjprog still fails on my Mac after installing v10.4.1. The installer works fine, but running nrfjprog goes like this:

$ ./nrfjprog --reset --program /var/folders/tq/c6wwp0ks41zdg9d9w9t5y32w0000gn/T/arduino_build_392483/sketch_oct10a.ino.hex --sectorerase -f nrf52
ERROR: JLinkARM DLL load failed. Try again. If it keeps failing, please
ERROR: reinstall latest JLinkARM from Segger webpage.

I ran the JLink installer in the Nordic package, same effect.

I ran the official JLink installer from SEGGER, same effect.

Any ideas?

RE: Installing Command Line Tools 10.4.0 fails on MacOS (10.14.6)

tesc — Mon, 28 Oct 2019 14:27:45 GMT

Hi,

We have now released nRF Command Line Tools v10.4.1, where the issue of failing installer on MacOS is fixed.

The issue of nrfjprog failing on MacOS and GNU/Linux is also fixed.

For those of you using the nRF91 series this means you now have the fixes introduced in v10.4.0 working on all platforms.

Regards,
Terje

RE: Installing Command Line Tools 10.4.0 fails on MacOS (10.14.6)

tesc — Thu, 24 Oct 2019 09:19:02 GMT

Hi,

What board are you trying to flash?

There are some known issues for 10.3.0, especially with the nRF91 series, and the "too old" error message can be a bit misleading.

Adding (or removing) the correct family flag to the nrfjprog command may solve the issue, although that would only work if you are in control of the nrfjprog command. Also make sure that there is a powered device connected through a programmer to the PC of the correct family. Our DKs have programmer MCUs on board, but there may still be switches for providing power to the programmer MCU and/or selecting what device (on nRF91 DK, which one of nRF52840 or nRF9160,) to program.

Regards,
Terje

RE: Installing Command Line Tools 10.4.0 fails on MacOS (10.14.6)

Anders Nelson — Wed, 23 Oct 2019 18:38:41 GMT

I installed v10.3.0 but now I'm getting an error saying my version of the Jlink DLL is too old. I removed the later Jlink version and ran the Jlink installer that came with the NRF tools, but running the command again gave the same error as before.

I didn't remove the 10.4.0 Nordic tools folder before running the 10.3.0 installer, would this have any effect?

Still can't flash unfortunately!

RE: Installing Command Line Tools 10.4.0 fails on MacOS (10.14.6)

AkhilWadhwa — Wed, 23 Oct 2019 18:28:30 GMT

I am facing the exact same problem. I installed the previous version and it was installed just fine.

RE: Installing Command Line Tools 10.4.0 fails on MacOS (10.14.6)

Min-Ching Ho — Tue, 22 Oct 2019 18:24:47 GMT

Another data point here. I have seen the same issue on my Mac, version 10.14.6. After this, i can see nrfjprog under /usr/loca/bin. But, when i run the command, I got this error message "ERROR: nrfjprog.ini not found. Please reinstall nrfjprog.". FYI.

Reinstall 10.3.0 restored my dev environment. I'm going to keep this old version until the problem is fixed.

RE: Installing Command Line Tools 10.4.0 fails on MacOS (10.14.6)

tesc — Tue, 22 Oct 2019 08:29:08 GMT

Hi,

Does this happen only with nRF Command Line Tools v10.4.0, or does it happen with previous versions as well? Both the installer and nrfjprog should work for v10.3.0, so that is the workaround for now.

When a patched release is out I will let you know.

Regards,
Terje

RE: Installing Command Line Tools 10.4.0 fails on MacOS (10.14.6)

Anders Nelson — Tue, 22 Oct 2019 02:08:45 GMT

Same problem, installer fails and the tools that do get installed will not run:

I am running macOS Mojave 10.14.6.

I can use the JFlashLite app just fine.

Please let us know when the issue is resolved or a workaround is available!

RE: Installing Command Line Tools 10.4.0 fails on MacOS (10.14.6)

tesc — Fri, 18 Oct 2019 10:59:12 GMT

Hi,

From what I can tell, all of the issues mentioned thus far in this thread are due to one or more of three known issues:

Issue with installing nRF Command Line Tools (original topic of this thread.)
Issue with running nrfjprog on certain platforms (e.g. ERROR: nrfjprog.ini not found. Please reinstall nrfjprog.)
Issue with connecting nRF91 to the debugger. (As seen e.g. in this DevZone answer.)

We are currently working on fixing all of those.

Regards,
Terje

RE: Installing Command Line Tools 10.4.0 fails on MacOS (10.14.6)

Fredrik — Wed, 16 Oct 2019 12:58:05 GMT

I'm having the same problem, and found that flashing through the nRF Connect for desktop Programmer application works. It's not a permanent fix, but may help you get something onto your nRF91 board.

RE: Installing Command Line Tools 10.4.0 fails on MacOS (10.14.6)

hqtk — Wed, 16 Oct 2019 10:25:03 GMT

Thank you so much, I have been installing and uninstalling all kinds of versions to see which permutations that could work. I only have one programmer, modem is latest version and I do get a boot message in serial monitor.

Only fails when I try to flash..

Guess I'll just wait until someone fixes this upstream

RE: Installing Command Line Tools 10.4.0 fails on MacOS (10.14.6)

Pertti Kasanen — Wed, 16 Oct 2019 10:02:06 GMT

The error messages of nrfjprog are currently so bad that it is almost funny.

"Installed nrfjprog is too old for the device. Please upgrade nrfjprog" does not really mean that the version is wrong.
It could mean that you have another programmer connected and it gets confused, or that the nRF91 you are trying to flash is not powered on. It might even mean that it does not have the modem software or boot loader installed...

RE: Installing Command Line Tools 10.4.0 fails on MacOS (10.14.6)

hqtk — Wed, 16 Oct 2019 09:24:45 GMT

I'm getting the same error. I have managed to install 0.3.0, but when I run "west flash" I get this wonderful message:
ERROR: Installed nrfjprog is too old for the device. Please upgrade nrfjprog
ERROR: to a more recent version.
ERROR: command exited with status 2: nrfjprog --program /Users/haq/thingy91/manifest/build/zephyr/merged.hex -f NRF91 --snr 960058144 --sectorerase

I am on a mac, tested with west 0.6.0 and 0.6.3
nrfjprog version: 10.3.0
JLinkARM.dll version: 6.44e

RE: Installing Command Line Tools 10.4.0 fails on MacOS (10.14.6)

tesc — Mon, 14 Oct 2019 09:05:04 GMT

Hi,

Do you get the same error when trying to install all those versions?

Have any previous version worked on your system?

What OS are you running (with version number).

Regards,
Terje

RE: Installing Command Line Tools 10.4.0 fails on MacOS (10.14.6)

jeikki — Sun, 13 Oct 2019 19:52:32 GMT

I have the same problem. I tried also the 10.3.0 and 10.2.1 but nothing works. I think you have a bigger issue here.