JLinkARM DLL can't be found by the command "nrfutil device list" on Linux

[tylerh]

Hello,

I get this error when I try `nrfutil device list`, and any other nrfutil device command.

However, if I use `nrfutil device --jlink-dll /path/to/libjlinkarm.so list` for the correct version (JLink Linux V818), it works.

Where and how is nrfutil looking to find libjlinkarm.so file? I've tried modifying $LD_LIBRARY_PATH but that doesn't work. I have all of the latest versions of JLink installed in /usr/pack, and I'd prefer to have nrfutil look there.

Using the above workaround is fine for some things, but I have issues with lots of other nRF tools, such as nRF Connect Desktop, nRF Connect for VS Code, and west flash/west debug, etc.

[Vidar Berg]

Hello,

The Segger installer places the libraries in /opt/SEGGER/JLink, and that is also where nrfutil expects to find them. 

Best regards,

Vidar

[tylerh]

Hi Vidar,

Is it possible to configure nrfutil to look under another directory?

[Vidar Berg]

Unfortunately, no. You currently need to specify the path if you’re not using the default installation directory. I can create a feature request internally to check if this could be supported, but it would probably help if I could include some reasons and motivation for the request. 

[Markus Suvanto]

Hi Vidar

This hard coded path /opt/SEGGER/JLink breaks
network installation that is used to work like this:

cd /afs/.../amd64_linux26/segger
tar xvf /tmp/JLink_Linux_V866_x86_64.tgz

Developers source setting file where needed environment variables are set. For example LD_LIBRARY_PATH=/afs/.../amd64_linux26/segger/JLink_Linux_V866_x86_64

Now nrfutils will not work until developer make symbolic link in  local hard disk
/opt/SEGGER/JLink -> /afs/.../amd64_linux26/segger/JLink_Linux_V866_x86_64

-Markus