• State Verified Answer
  • Locked Locked
  • Replies 23 replies
  • Subscribers 77 subscribers
  • Views 7092 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 278395
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

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

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.
  • 0 in reply to Simonr

    I can connect to the device with JLinkExe, but Issue with nrfjprog remains. Any hints ? Can you reproduce this on your end ?

  • 0 in reply to Nikil Rao

    Okay me too

    J-Link>connect
Device "NRF52832_XXAA" selected.


Connecting to target via SWD
InitTarget() start
InitTarget() end
Found SW-DP with ID 0x2BA01477
DPIDR: 0x2BA01477
Scanning AP map to find all available APs
AP[2]: Stopped AP scan as end of AP map has been reached
AP[0]: AHB-AP (IDR: 0x24770011)
AP[1]: JTAG-AP (IDR: 0x02880000)
Iterating through AP map to find AHB-AP to use
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xE00FF000
CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)
Found Cortex-M4 r0p1, Little endian.
FPUnit: 6 code (BP) slots and 2 literal slots
CoreSight components:
ROMTbl[0] @ E00FF000
[0][0]: E000E000 CID B105E00D PID 000BB00C SCS-M7
[0][1]: E0001000 CID B105E00D PID 003BB002 DWT
[0][2]: E0002000 CID B105E00D PID 002BB003 FPB
[0][3]: E0000000 CID B105E00D PID 003BB001 ITM
[0][4]: E0040000 CID B105900D PID 000BB9A1 TPIU
[0][5]: E0041000 CID B105900D PID 000BB925 ETM
Cortex-M4 identified.
J-Link>exit

  • 0

    Hi again

    No, I'm afraid we've not been able to reproduce it here. We have nRF command line tools 10.14.0 installed with the J-Link version you're using, and are not able to reproduce the issue. We can only assume something is off with the system setup on your end. Our recommendation is to update to the latest version of nRF command line tools using the .deb package and try again.

    Best regards,

    Simon

  • 0 in reply to Simonr

    I switched from accessing the RPi over SSH and connected it to a monitor and keyboard and nrfjprog now works for some reason! Could there be any reason why it wouldn't work over SSH?

  • 0 in reply to Simonr

    I can use nrfjprog commands now but there's still an error thrown when I use pynrfjprog

    Does running the 10.14.0 .deb package also install pynrfjprog? I think there's also a bug in the latest pynrfjprog repo where the new armhf libraries are not installed even though they are present in the pynrfjprog/lib_armhf folder. I don't see  the lib_armhf package included here - github.com/.../setup.py

Related
Terms of service