nRF Connect Linux Desktop J-Link issues

RE: nRF Connect Linux Desktop J-Link issues

Håkon Alseth — Thu, 16 Dec 2021 09:15:47 GMT

Hi,

[quote user="swisst"]

12:43:14.681 Application data folder: /home/vvs/.config/nrfconnect/pc-nrfconnect-programmer

12:43:14.722 Using nrfjprog library 10.12.1, pc-nrfjprog-js 1.7.6

12:43:23.940 Using nrfjprog to communicate with target

12:43:23.944 Could not fetch memory size of target devkit: Error: Error occured when get library info. Errorcode: CouldNotOpenDevice (0x4) Lowlevel error: Unknown value (ffffff5e)

[/quote][quote user="swisst"]From other hand if I specify exact path to JLink dll like:[/quote]

It seems that you are the victim of a bug with the older nrfjprog:

https://devzone.nordicsemi.com/f/nordic-q-a/64956/nrfjprog-on-linux-support-for-ld_library_path-broken-from-10-5-0-onwards-and-opt-segger-jlink-hardcoded-instead

It expects the libjlinkarm.so to be in $PATH or at /opt/SEGGER/JLink.

If you symlink your path/to/nrf-tools/JLink_Linux_V688..../ to /opt/SEGGER/JLink, it should be able to pick it up in nrf connect for desktop as well. This issue is fixed in newer versions of nrfjprog.

Kind regards,

Håkon

RE: nRF Connect Linux Desktop J-Link issues

swisst — Wed, 15 Dec 2021 16:25:06 GMT

If I use the command you ask to execute I get such output to log

[2021-Dec-15 18:13:46] [ info] --------------------------------------------------------------------------------
[2021-Dec-15 18:13:46] [ info] nrfjprog --memrd 0 -f nrf52 --log 
[2021-Dec-15 18:13:46] [ info] nrfjprog version 10.12.1 
[2021-Dec-15 18:13:46] [ info] --------------------------------------------------------------------------------
[2021-Dec-15 18:13:46] [debug] [ nRF0x0] - open_dll
[2021-Dec-15 18:13:46] [ info] [ nRF0x0] - Load library at /opt/nrfjprog/libjlinkarm_nrf52_nrfjprogdll.so.
[2021-Dec-15 18:13:46] [ info] [ nRF0x0] - Library loaded, loading member functions.
[2021-Dec-15 18:13:46] [ info] [ nRF0x0] - Member functions succesfully loaded.
[2021-Dec-15 18:13:46] [ info] [Backend] - Logger callback at 0x55e38e9b1130 registered in Segger backend logger.
[2021-Dec-15 18:13:46] [ info] [  JLink] - [Info    ] [JLink     ] Logger callback at 0x55e38e9b1130 registered in JLink logger.
[2021-Dec-15 18:13:46] [debug] [nRF520x0] - open
[2021-Dec-15 18:13:46] [debug] [Backend] - open_dll
[2021-Dec-15 18:13:46] [ info] [Backend] - No J-Link DLL path was provided. Attempting to auto detect.
[2021-Dec-15 18:13:46] [ info] [Backend] - Load library at libjlinkarm.so.
[2021-Dec-15 18:13:46] [ info] [Backend] - Dll failed to open.
[2021-Dec-15 18:13:46] [debug] [Backend] - close
[2021-Dec-15 18:13:46] [debug] [Backend] - Segger Backend closed.
[2021-Dec-15 18:13:46] [debug] [nRF520x0] - close
[2021-Dec-15 18:13:46] [debug] [nRF520x0] - nRF family DLL closed
[2021-Dec-15 18:13:46] [debug] [ nRF0x0] - close_dll

From other hand if I specify exact path to JLink dll like:

nrfjprog --jdll <project path>/nrf-tools/JLink_Linux_V688a_x86_64/libjlinkarm.so --memrd 0 -f nrf52

I get valid output like

0x00000000: 20000400

RE: nRF Connect Linux Desktop J-Link issues

Håkon Alseth — Wed, 15 Dec 2021 14:50:10 GMT

Hi,

[quote user="swisst"]

I still have issues with the second use case: Programmer application + JLink + nrf52840 target. Even after downgrade and with attached target I can not make it work and get an error in log output ( specified above)

[/quote]

My apologies for misunderstanding. Are you able to access the debugger + nrf directly using other tools?

Like nrfjprog:

nrfjprog --memrd 0 -f nrf52

Kind regards,

Håkon

RE: nRF Connect Linux Desktop J-Link issues

swisst — Wed, 15 Dec 2021 14:45:54 GMT

Hi Håkon

Thank you for reply. I believe you did not get my previous message correctly - anyway I'll try to explain from scratch.

I use nRF USB dongle with Bluetooth Low Energy application. Regarding this part all issues were solved after I downgrade connect for Desktop to 3.7.1 ( with all apps ).

Answer for your recent question: It is not my case but even so all works as expected after downgrade. nRF USB dongle is visible in both applications I use ( BLE and programmer ), it can be put into bootloader and re-flashed with both applications.

[quote userid="99142" url="~/f/nordic-q-a/82579/nrf-connect-linux-desktop-j-link-issues/343030#343030"]

12:43:14.681 Application data folder: /home/vvs/.config/nrfconnect/pc-nrfconnect-programmer

12:43:14.722 Using nrfjprog library 10.12.1, pc-nrfjprog-js 1.7.6

12:43:23.940 Using nrfjprog to communicate with target

12:43:23.944 Could not fetch memory size of target devkit: Error: Error occured when get library info. Errorcode: CouldNotOpenDevice (0x4) Lowlevel error: Unknown value (ffffff5e)

[/quote]

Best regards

RE: nRF Connect Linux Desktop J-Link issues

Håkon Alseth — Mon, 13 Dec 2021 12:34:54 GMT

Hi,

[quote user="swisst"]

12:43:14.681 Application data folder: /home/vvs/.config/nrfconnect/pc-nrfconnect-programmer

12:43:14.722 Using nrfjprog library 10.12.1, pc-nrfjprog-js 1.7.6

12:43:23.940 Using nrfjprog to communicate with target

12:43:23.944 Could not fetch memory size of target devkit: Error: Error occured when get library info. Errorcode: CouldNotOpenDevice (0x4) Lowlevel error: Unknown value (ffffff5e)

[/quote]

Are you able to see a successful detection of the dongle, ie. that it's in bootloader mode?

Here's some pictures on how it should look:

https://devzone.nordicsemi.com/guides/short-range-guides/b/getting-started/posts/nrf52840-dongle-programming-tutorial

Kind regards,

Håkon

RE: nRF Connect Linux Desktop J-Link issues

swisst — Sun, 12 Dec 2021 10:44:55 GMT

Thank you for quick reply

The manual via your link worked good for Bluetooth Low Energy application - it works as expected

The only concern is that - Delete bond information is not active for selected adapter ( adapter was re-flashed on application startup, 1 device was bonded )

Regarding Programmer application - the issue still exist but with other log message

12:43:14.681 Application data folder: /home/vvs/.config/nrfconnect/pc-nrfconnect-programmer

12:43:14.722 Using nrfjprog library 10.12.1, pc-nrfjprog-js 1.7.6

12:43:23.940 Using nrfjprog to communicate with target

12:43:23.944 Could not fetch memory size of target devkit: Error: Error occured when get library info. Errorcode: CouldNotOpenDevice (0x4) Lowlevel error: Unknown value (ffffff5e)

2 last lines come after programmer device selected

RE: nRF Connect Linux Desktop J-Link issues

Håkon Alseth — Fri, 10 Dec 2021 12:25:04 GMT

Hello,

Unfortunately, we have a known issue with latest versions of nRF connect for Desktop (3.8.0 and 3.9.0), where the workaround is to downgrade to 3.7.0 at this time, and install the corresponding application versions for this version.

More details and howto do this is described here:

https://devzone.nordicsemi.com/f/nordic-q-a/81700/how-to-downgrade-nrf-connect

Could you try this and report back if you still run into any issues?

Kind regards,

Håkon