[SOLVED] [ARM] Running the JLinkGDBServer program on Raspberry Pi 3

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

  • [SOLVED] [ARM] Running the JLinkGDBServer program on Raspberry Pi 3

    Hi,

    I know that Segger does not OFFICIALLY support the Raspberry Pi's when getting their arm version of the JLink series software to work. However, I would be very appreciative if anyone can guide me.

    I am running Raspbian Jessie(from here: downloads.raspberrypi.org/raspbian_latest) with PIXEL, and I have been able to get the JLinkExe to see the JLink Edu I have attached to the USB Port.

    However, when I try to run JLinkGDBServer, it starts initializing but then stops with the error: "Connecting to target...Error: No CPU core or Target device has been selected".

    I am trying to run JLinkGDBServer on a Raspberry Pi 3.

    The USB end of the J-Link is connected to the Raspberrry Pi 3. The "JTAG" end (with 26 pins) is attached to a Raspberry Pi 2.

    I am using the JLink_Linux_V614h_arm.tgz version of the JLink software.

    Can someone please advise as to what I should do next?

    Thank you for your time,
    KRL

    The post was edited 1 time, last by KRL ().

  • Hi KRL,


    what command line parameters to you pass to the GDB Server?


    Best regards,
    Niklas
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    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 you can contact us via our support system: segger.com/ticket/

    Or you can contact us via e-mail.
  • Hi,

    this will be fixed in the next version of the
    J-Link software & documentation pack
    J-Link software & documentation pack (beta)

    Best regards,
    Niklas
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    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 you can contact us via our support system: segger.com/ticket/

    Or you can contact us via e-mail.
  • Slightly different error from Ubuntu

    Hello, I just tried the latest (see the version below) JLinkGDBServer against Raspberry Pi 3. TDO is bouncing around in Logic Analyzer view (combination of 0x000000002 and 0x00000069A), so I think the GPIO pins have been remapped to JTAG (I wrote a little program to do this in U-Boot). Cortex-A53 should have the core debug registers no?

    parallels@ubuntu:~$ JLinkGDBServer -device cortex-a7
    SEGGER J-Link GDB Server V6.21a (beta) Command Line Version

    JLinkARM.dll V6.21a (DLL compiled Sep 29 2017 16:47:34)

    Command line: -device cortex-a7
    -----GDB Server start settings-----
    GDBInit file: none
    GDB Server Listening port: 2331
    SWO raw output listening port: 2332
    Terminal I/O port: 2333
    Accept remote connection: yes
    Generate logfile: off
    Verify download: off
    Init regs on start: off
    Silent mode: off
    Single run mode: off
    Target connection timeout: 0 ms
    ------J-Link related settings------
    J-Link Host interface: USB
    J-Link script: none
    J-Link settings file: none
    ------Target related settings------
    Target device: cortex-a7
    Target interface: JTAG
    Target interface speed: 1000kHz
    Target endian: little

    Connecting to J-Link...
    J-Link is connected.
    Firmware: J-Link ARM V8 compiled Nov 28 2014 13:44:46
    Hardware: V8.00
    S/N: 58009925
    Feature(s): RDI, FlashBP, FlashDL, JFlash, GDB
    Checking target voltage...
    Target voltage: 3.31 V
    Listening on TCP/IP port 2331
    Connecting to target...ERROR: Cortex-A/R-JTAG (connect): Could not determine address of core debug registers. Incorrect CoreSight ROM table in device?
    ERROR: Could not connect to target.
    Target connection failed. GDBServer will be closed...Restoring target state and closing J-Link connection...
    Shutting down...
    Could not connect to target.
    Please check power, connection and settings.
  • Hi Henry,

    this thread was about running the J-Link software on a Raspberry Pi, but not about using a Raspberry Pi as a target device.
    Thanks for opening a dedicated thread for this issue.


    Best regards,
    Niklas
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    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 you can contact us via our support system: segger.com/ticket/

    Or you can contact us via e-mail.