nrfjprog not working on raspberry pi 4

[picatostas]

Hi

I am trying to setup a raspberry pi 4 for flashing nrf devices. But Nrfjprog doesn't seem to work.

I am using a Raspberry Pi 4 with 2021-05-07-raspios-buster-armhf-lite

I have fetched Segger and nrfjprog deb packages using :

wget --post-data 'accept_license_agreement=accepted&non_emb_ctr=confirmed&submit=Download+software' www.segger.com/.../JLink_Linux_arm.deb

wget www.nordicsemi.com/.../nRF-Command-Line-Tools_10_14_0_LinuxArm.zip

installed them using:

sudo dpkg -i ~/nRF-Command-Line-Tools_10_14_0_LinuxArm/nrf-command-line-tools_10.14.0_armhf.deb

sudo dpkg -i JLink_Linux_arm.deb

I can detect the target using JLinkExe:

but when running nrfjprog I run into this:

log file as follows:

running ldd I get the following

What am I missing ?

If you need anymore details from my setup, let me know.

[picatostas]

Hi Simon,
installing that package drops a later dependency issue for "libXrender.so.1". I am currently operating the rpi over ssh without X forwarding, so I don't need the gui. Are those packages still required for using nrfjprog ?

[Nikil Rao]

@picatostas I think this is an unrelated error because you entered the wrong device name (nRF9160_xxAA should be the device name you use with JLinkExe) and if you had a GUI, JLink would have opened a dialog box with a list of device names. So you get the GUI library errors

[picatostas]

yeah, it is unrelated. Did you manage to use JLinkExe without nrfjprog ?

[Nikil Rao]

Yes

JLinkExe 
SEGGER J-Link Commander V7.52d (Compiled Aug 17 2021 17:19:03)
DLL version V7.52d, compiled Aug 17 2021 17:18:47

Connecting to J-Link via USB...O.K.
Firmware: J-Link V11 compiled Oct  6 2021 11:22:15
Hardware version: V11.00
S/N: 51010127
License(s): GDB
VTref=3.613V


Type "connect" to establish a target connection, '?' for help
J-Link>connect
Please specify device / core. <Default>: Unspecified
Type '?' for selection dialog
Device>nRF9160_xxAA
Please specify target interface:
  J) JTAG (Default)
  S) SWD
  T) cJTAG
TIF>S
Specify target interface speed [kHz]. <Default>: 4000 kHz
Speed>
Device "NRF9160_XXAA" selected.


Connecting to target via SWD
ConfigTargetSettings() start
---Setting ROM table---
ConfigTargetSettings() end
Found SW-DP with ID 0x6BA02477
DPIDR: 0x6BA02477
Scanning AP map to find all available APs
AP[7]: Stopped AP scan as end of AP map has been reached
AP[0]: AHB-AP (IDR: 0x84770001)
AP[1]: AHB-AP (IDR: 0x24770011)
AP[2]: JTAG-AP (IDR: 0x12880000)
AP[3]: APB-AP (IDR: 0x54770002)
AP[4]: JTAG-AP (IDR: 0x12880000)
AP[5]: JTAG-AP (IDR: 0x12880000)
AP[6]: MEM-AP (IDR: 0x128800A1)
Iterating through AP map to find AHB-AP to use
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xE00FF000
CPUID register: 0x410FD212. Implementer code: 0x41 (ARM)
Feature set: Mainline
Found Cortex-M33 r0p2, Little endian.
FPUnit: 8 code (BP) slots and 0 literal slots
Security extension: implemented
Secure debug: enabled
CoreSight components:
ROMTbl[0] @ E00FF000
ROMTbl[0][0]: E000E000, CID: B105900D, PID: 000BBD21 Cortex-M33
ROMTbl[0][1]: E0001000, CID: B105900D, PID: 000BBD21 DWT
ROMTbl[0][2]: E0002000, CID: B105900D, PID: 000BBD21 FPB
ROMTbl[0][3]: E0000000, CID: B105900D, PID: 000BBD21 ITM
ROMTbl[0][5]: E0041000, CID: B105900D, PID: 002BBD21 ETM
ROMTbl[0][6]: E0042000, CID: B105900D, PID: 000BBD21 CSS600-CTI
Cortex-M33 identified.

[Simonr]

Okay, it seems like this "missing library" might come from the Segger pop-up asking you to choose the emulator to connect to. I think this can be confirmed by running the J-Link configurator. Qt (which is the GUI library used by SEGGER AFAIK), needs the libsm6 shared library to show the pop-up. I think this is an issue with Segger not embedding their shared library in their distributable. Try adding this required package as well.

Best regards,

Simon