nrf Connect Terminal LD_LIBRARY_PATH problem

[Reid666]

nrf Connect Terminal overwrites LD_LIBRARY_PATH. I have added SEGGER JLink path to it so nrfjprog and JLink can dynamically link to the JLink dot so files. This works on Bash and ZSH outside nrf Connect terminal. 

Please see the screenshots below from the terminal window in VSCode:

I have found below template hoping that I can somehow insert JLink library path:

"nrf-connect.terminalProfile.shell": {

"path": "/usr/bin/zsh",

"args": []

},

however I'm not sure whether LD_LIBRARY_PATH is append-able for nrf Connect Terminal. How can I fix this problem ? 

[Sigurd Hellesvik]

Hi,

nrf Connect Terminal overwrites LD_LIBRARY_PATH.

Let us first look into this. It might be that it does not overwrite it, but that it loads some different configuration files for the terminal than what is done normally by bash. Not saying that is better, but if we know which one it is we can better fix this issue.

Where do you set LD_LIBRARY_PATH in your system?

Regards,
Sigurd Hellesvik

[Reid666]

Right now I have set my LD_LIBRARY_PATH in .zprofile and I launch VSCode from command line in ZSH. I have tried setting it in .bash_profile and .zshrc. It seems PATH in .zprofile works fine because I set it in .zprofile and I can launch nrfjprog in nrf Connect Terminal.

export PATH="$HOME/local/nrf-command-line-tools/bin:$HOME/local/JLink_Linux_V794e_x86_64:$PATH"
export LD_LIBRARY_PATH="$HOME/local/JLink_Linux_V794e_x86_64:$LD_LIBRARY_PATH"

[Sigurd Hellesvik]

I remember something about our VS Code extension running .bashrc specifically. Can you try to put it there and see if that is picked up?

[Reid666]

I still have the same problem:

nrfjprog -v
[error] [SeggerBackend] - Error in dlopen: libjlinkarm.so: cannot open shared object file: No such file or directory
[error] [ Worker] - Dll failed to open.
[error] [ Client] - Encountered error -101: Command open executed for 11 milliseconds with result -101
ERROR: JLinkARM DLL load failed. Try again. If it keeps failing, please
ERROR: reinstall latest JLinkARM from Segger webpage.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.

[Sigurd Hellesvik]

Good to know.

Try nrf-connect.west.env. If this does not work, I will report what you see to the devs as a bug.