nRFConnect fail on linux

RE: nRFConnect fail on linux

pabigot — Wed, 23 Oct 2019 14:37:51 GMT

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

RE: nRFConnect fail on linux

Juha Okkonen — Fri, 05 Jul 2019 08:10:46 GMT

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.

RE: nRFConnect fail on linux

Per Kristian Schanke — Fri, 08 Sep 2017 12:27:34 GMT

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

RE: nRFConnect fail on linux

Mike — Wed, 06 Sep 2017 14:26:11 GMT

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