nrfjprog wants JLinkARM.dll on linux

RE: nrfjprog wants JLinkARM.dll on linux

gamnes — Wed, 09 Aug 2017 17:16:26 GMT

Adding the libjlinkarm.so to /usr/lib can be done with ln command; Enter /usr/lib, type: > ln -s {/path/to/segger-lib-file-name} {segger-lib-file-name}

RE: nrfjprog wants JLinkARM.dll on linux

gamnes — Wed, 09 Aug 2017 17:14:23 GMT

I believe the original problem of this post was due to a bug in the nrfjprog executable and the executable being placed inside the SEGGER/JLink folder, and it saying the .dll was needed and not a .so. This should have been resolved, but i would still not recommend placing the nrfjprog files inside the SEGGER/JLink folder structure as this structure can change based on how SEGGER releases their tools.

Creating a link to libjlinkarm.so inside the nrfjprogs folder should also work, but then i would rather suggest adding this link to the /usr/lib or /lib folder as would be the proper way to get this working. nrfjprog uses dlopen() as mentioned here: infocenter.nordicsemi.com/index.jsp, and dlopen() will automatically search /lib and /usr/lib.

RE: nrfjprog wants JLinkARM.dll on linux

tralamazza — Tue, 08 Aug 2017 16:11:38 GMT

Simply create a link to libjlinkarm.so inside nrfjprog's folder.

RE: nrfjprog wants JLinkARM.dll on linux

Juha Okkonen — Tue, 27 Oct 2015 14:20:18 GMT

Yeahh, I just did that and it started working.

RE: nrfjprog wants JLinkARM.dll on linux

gamnes — Tue, 27 Oct 2015 14:04:15 GMT

Hi Juha,

There is a problem is you place the nrfjprog .so files inside the SEGGER/JLink folder. So please put those files in another place and it should work.

RE: nrfjprog wants JLinkARM.dll on linux

gamnes — Tue, 27 Oct 2015 13:24:58 GMT

Could you try and move the nrfjprog.so files away from the SEGGER JLink folder to somewhere else? It seems that if you leave the nrfjprog files within the SEGGER folder, it will not work

RE: nrfjprog wants JLinkARM.dll on linux

Juha Okkonen — Tue, 27 Oct 2015 13:15:27 GMT

And I do have both JLink and nrfjprog in /opt/SEGGER/JLink-directory, so it should work. But the strange thing is that nrfjprog doesn't event try to read libjlinkarm.so from anywhare. Last operation it does is reading /opt/SEGGER/JLink/libnrfjprogdll.so.7 for 832 bytes worth and then closes it and gives irrelevant error message.

RE: nrfjprog wants JLinkARM.dll on linux

gamnes — Tue, 27 Oct 2015 12:33:56 GMT

If you want, you can use the python module instead of the executable; pynrfjprog; which will allow you to provide the PATH to the segger shared library in the open(...) function call. This will forward the provided path to the nrfjprog DLLs and use this one. Thus, if you install the SEGGER shared library in for example /usr/lib and only provide libjlinkarm.so as path to the pynrfjprog open, our shared libraries should find it.

RE: nrfjprog wants JLinkARM.dll on linux

gamnes — Tue, 27 Oct 2015 12:27:24 GMT

Hi Juha, The reason for the hardcoded link to the SEGGER shared library is that the implementation currently has been done in a "windows" way. This will be fixed in future releases allowing the SEGGER shared library to be located in for example /usr/lib, but the executable will for example still also look in /opt/SEGGER/JLink, sorry if this causes issue for you right now.

This has only been tested on Ubuntu: If you download the .tar from our website, and extract it into a folder, for example: ~/Documents/nrfjprog_linux/ If the segger software is installed in /opt/SEGGER/JLink/ by using their .deb installer (which will place it there); Then you should be able to run from within the nrfjprog_linux folder: ./nrfjprog -r And it should work fine.

RE: nrfjprog wants JLinkARM.dll on linux

Juha Okkonen — Tue, 27 Oct 2015 12:26:10 GMT

I could correct the code if you just point me to nrfjprog sources. :)

RE: nrfjprog wants JLinkARM.dll on linux

Juha Okkonen — Tue, 27 Oct 2015 12:20:42 GMT

Copied original directoris ( both 32 bit and 64 bit versions ) into expected paths, but no success.....

RE: nrfjprog wants JLinkARM.dll on linux

Juha Okkonen — Tue, 27 Oct 2015 12:16:40 GMT

I'm not using Python programs so version doesn't matter. Nrfjprog files are located in the same directory with JLink files. And I found from the strace output the requirement for hardcoded directory name /opt/SEGGER/JLink which seems bit ridiculous!! I did that with link so I'll test renaming the actual directory....

RE: nrfjprog wants JLinkARM.dll on linux

gamnes — Tue, 27 Oct 2015 10:58:50 GMT

The problem here was that the nrfjprog files were placed in the /opt/SEGGER/JLink/ folder. This does not work with the current release and thus caused the executable to crash. Will probably be fixed in a future release. Solution for now is to not place the nrfjprog files in the /opt/SEGGER/JLink folder.

Hi Juha, have you looked at this recent blog post regarding the current limitations of the Linux version of nRF5x-Tools? nRF5x-Tools and nRF5x-Pynrfjprog Includes Linux and Python 3 Support

Have you placed your nrfjprog files inside the SEGGER folder as well? Where are your nrfjprog - .so files located, and where is the nrfjprog executable located?