VS Code & nrfjprog (nRF Connect SDK) problem on Linux

[salihonur]

Hi,

I get the error like below on the Linux XFCE 64-bit platform (Pardus 21.2 distro latest version). It works fine on Windows but having a problem on linux. How can I solve it?

[Account01]

I'm encountering something similar...
I have tried both using "PATH" (I set PATH=$PATH:/opt/nrf-command-line-tools/bin before executing code.) and specifying "/opt/nrf-command-line-tools/bin" when specifying toolchain.

1: Using PATH (with the toolchain already in the PATH env variable) will give "nrfjprog is required" error
2: Using "/opt/nrf-command-line-tools/bin" it will give an "Invalid Toolchain Installation." without an explanation.
3: If I run the tools from the command line, they will execute as expected.

[Einar Thorsrud]

Which platform are you using? If you use the latest nRF Command Line Tools you should automatically get it in your path, as a symlink should be created in /usr/local/bin/, an din that case there is no need to add it to your path in any other way (assuming /usr/local/bin is in the path from before, which it should normally always be).

If this does not work, can you show what you PATH looks like without any additional configuration, and also let me know which Linux distro you are using?

[Account01]

Sure. I'm running x86_64 Ubuntu 20.04, and my PATH shows as:

/home/*user*/bin:/home/*user*/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/home/*user*/go/bin

When I run "which nrfjprog" without setting environment variables, it returns, "/usr/local/bin/nrfjprog"

[EdAtm021]

Same issue here, running in x86_64 Ubuntu 20.04. That's not a PATH issue, I have two paths to nrfjprog in my PATH, neither works. And I have installed the last version using 'apt install ./nrf-command-line-tools_10.18.0_amd64.deb', To me, it seems like the build for nrf-command-line-tools_10.18.0_amd64.deb  is broken, if we run nrfjprog the output is an error, trying to execute a dll, it's very strange seeing that under UNIX universe, I expected a shared-object or shared-library, not a dll.

 

[Einar Thorsrud]

Hi,

Did you install the J-Link Software and Documentation Pack well as nRF Command Line Tools?

(The reference to dll is a bit odd but not an issue, and this comes from SEGGER. I is obviously not a DLL on Linux, but they call their shared library files DLL on all platforms for some reason.)

[Account01]

I know this is a small difference, but have you tried installing the package with "dpkg -i" instead of "apt install"? Maybe some odd repo dependency is interfering, although that would be an oddity.

Also, have you run "nm -D" to check that the function symbol actually exists:

$ nm -D /opt/nrf-command-line-tools/lib/libnrfjprogdll.so | grep read_cpu_arch
000000000020ed50 T NRFJPROG_read_cpu_architecture_inst

Hope you figure this out!

[Account01]

Hey... have you tried downgrading to Command Line Tools 10.17?