JLinkExe segfaults on Raspberry Pi (ARM)

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • JLinkExe segfaults on Raspberry Pi (ARM)

      In a bash script on Ubuntu x86_64, I have no problem doing:

      Source Code

      1. (JLinkExe -if swd -device nrf52 -AutoConnect 1 -speed 4000 </dev/null >/dev/null &)
      2. telnet localhost 19021
      But on a Raspberry Pi it crashes when stdin is set to /dev/null:

      Source Code

      1. $ uname -a
      2. Linux raspberrypi 4.14.70-v7+ #1144 SMP Tue Sep 18 17:34:46 BST 2018 armv7l GNU/Linux
      3. $ JLinkExe </dev/null
      4. SEGGER J-Link Commander V6.44i (Compiled May 17 2019 17:39:37)
      5. DLL version V6.44i, compiled May 17 2019 17:39:21
      6. Connecting to J-Link via USB...O.K.
      7. Firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Jan 7 2019 14:07:15
      8. Hardware version: V1.00
      9. S/N: 682780248
      10. VTref=3.300V
      11. Type "connect" to establish a target connection, '?' for help
      12. J-Link>Segmentation fault
      13. $ valgrind -v JLinkExe </dev/null
      14. ==2364==
      15. ...
      16. /lib/arm-linux-gnueabihf/libgcc_s.so.1 due to munmap()
      17. O.K.
      18. Firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Jan 7 2019 14:07:15
      19. Hardware version: V1.00
      20. S/N: 682780248
      21. VTref=3.300V
      22. Type "connect" to establish a target connection, '?' for help
      23. ==2369== Conditional jump or move depends on uninitialised value(s)
      24. ==2369== at 0x484AA1C: rindex (vg_replace_strmem.c:199)
      25. ==2369== by 0x12863: ??? (in /usr/local/bin/JLinkExe)
      Display All
    • Hello,

      Thank you for your inquiry.
      If I understand you correctly you are trying to use J-Link software on ARM Linux on a Raspberry PI, is that correct?
      Did you install the ARM version of J-Link software (see attached picture)?
      segger.com/downloads/jlink/#J-…twareAndDocumentationPack

      Best regards,
      Nino
      Images
      • Capture.PNG

        25.85 kB, 832×173, viewed 22 times
      Please read the forum rules before posting: Forum Rules

      Keep in mind, this is not a support forum. Its main purpose is user to user interaction.
      Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
      Should you be entitled to support contact us per e-mail.
      Alternatively our support system can be used as well: segger.com/ticket/
    • Yes, I used the tar.gz package for ARM. Perhaps, J-Link should include the architecture nomenclature [[armv71]] in the startup output:

      Source Code

      1. $ JLinkExe </dev/null
      2. SEGGER J-Link Commander V6.44i (Compiled May 17 2019 17:39:37) [[armv71]
      3. DLL version V6.44i, compiled May 17 2019 17:39:21
      4. Connecting to J-Link via USB...O.K.
      5. Firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Jan 7 2019 14:07:15
      6. ...
      It has been used successfully on all our Pi's. The bug I've run into is redirecting standard input from /dev/null, "</dev/null". Which does work properly on an x86 system (using the appropriate .deb) package.