nRFConnect fail on linux

[Mike]

Hi,

I have a well working cli environment under linux where i can compile, program and debug a nFR52 demo board.

I have installed RSSI Viewer (1.05) and Bluetooth Low Energy (2.0.1) in nRFConnect, but both fail when i try to open /dev/ttyACM0 with the message:

Error when validating firmware: Error occured when read. Errorcode: CouldNotOpenDLL (0x7) Lowlevel error: JLINKARM_DLL_NOT_FOUND (ffffff9c)

I have a symlink from JLink_Linux_V618d_x86_64/libjlinkarm.so to /usr/lib/libjlinkarm.so to make other tools work (for instance nrfjprog that works fine).

Can someone point me in the right direction?

Thanks, Mike

[Mike]

I figured it out with strace.

Apparently the path "/opt/SEGGER/JLink/" is hard coded somewhere. Copying the segger shared object libraries there solved the problem.

If someone at Nordic reads this: Hard coded paths are evil. Please update the install instructions.

Cheers, Mike

[Per Kristian Schanke]

Hi Mike,

We have found the error in our code and are working on a fix for it. The fix will be included in our next release of nRF Connect.

You are right about hard coded paths not being ideal, but there are times where you can not ignore them. In this case, the use of a hard coded path is warranted as it is not the only lookup used, but one of multiple strategies to find the location of the libjlinkarm.so.

Thanks for reporting.

Best regards, Per Kristian

[Juha Okkonen]

I just install nRF Connect version 3.0.0 and I had to copy JLink library files to /opt/SEGGER/JLink directory.

Setting LD_LIBRARY_PATH or creating conf file to /etc/ld.so.conf.d directory should have been enough but either didn't work.

[pabigot]

I can confirm this is still necessary with 3.2.0, and agree the two workarounds should have worked.