[SOLVED] JLink GDB Server version 6.54 introduces error code "9" and terminates

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

  • [SOLVED] JLink GDB Server version 6.54 introduces error code "9" and terminates

    Hi,

    I use the JLink GDB Server to perform debugging from Jetbrains CLion. Up until version 6.54, this worked fine :

    Source Code

    1. /Applications/SEGGER/JLink_V652e/JLinkGDBServerCLExe -device STM32F411VE -endian little -if SWD -select usb=778137274 -ir -localhostonly 1 -port 2331 -speed 2000 -vd -nosilent -swoport 2332 -telnetport 2333 -halt
    2. SEGGER J-Link GDB Server V6.52e Command Line Version
    4. JLinkARM.dll V6.52e (DLL compiled Oct 16 2019 12:33:11)
    6. Command line: -device STM32F411VE -endian little -if SWD -select usb=778137274 -ir -localhostonly 1 -port 2331 -speed 2000 -vd -nosilent -swoport 2332 -telnetport 2333 -halt
    7. -----GDB Server start settings-----
    8. GDBInit file: none
    9. GDB Server Listening port: 2331
    10. SWO raw output listening port: 2332
    11. Terminal I/O port: 2333
    12. Accept remote connection: localhost only
    13. Generate logfile: off
    14. Verify download: on
    15. Init regs on start: on
    16. Silent mode: off
    17. Single run mode: off
    18. Target connection timeout: 0 ms
    19. ------J-Link related settings------
    20. J-Link Host interface: USB
    21. J-Link script: none
    22. J-Link settings file: none
    23. ------Target related settings------
    24. Target device: STM32F411VE
    25. Target interface: SWD
    26. Target interface speed: 2000kHz
    27. Target endian: little
    29. Connecting to J-Link...
    30. Error during pretty printers setup: Undefined info command: "pretty-printer". Try "help info".
    32. Some features and performance optimizations will not be available.
    34. J-Link is connected.
    35. Firmware: J-Link STLink V2 compiled Jun 26 2017 10:34:41
    36. Hardware: V1.00
    37. S/N: 778137274
    38. Checking target voltage...
    39. Target voltage: 3.30 V
    40. Listening on TCP/IP port 2331
    41. Connecting to target...Connected to target
    42. Waiting for GDB connection...Connected to 127.0.0.1
    Display All


    As you can see it complains about "pretty-printer" but ignores this and proceeds to the connection.
    With version 6.54, I cannot connect any more :

    Source Code

    1. /Applications/SEGGER/JLink_V654/JLinkGDBServerCLExe -device STM32F411VE -endian little -if SWD -select usb=778137274 -ir -localhostonly 1 -port 2331 -speed 2000 -vd -nosilent -swoport 2332 -telnetport 2333 -halt
    2. SEGGER J-Link GDB Server V6.54 Command Line Version
    4. GDB Server stopped, exit code 9
    5. Error during pretty printers setup: Undefined info command: "pretty-printer". Try "help info".
    7. Some features and performance optimizations will not be available.
    10. Process finished with exit code 0

    The error code "9" is not listed in the manual, so I cannot tell what has happened. Does anyone know what is going on?

    Ewout Boks

  • Hi Ewout,
    Thank you for your inquiry.

    Ewout206 wrote:

    Connecting to J-Link...
    Error during pretty printers setup: Undefined info command: "pretty-printer". Try "help info".

    Some features and performance optimizations will not be available.

    Ewout206 wrote:

    GDB Server stopped, exit code 9
    Error during pretty printers setup: Undefined info command: "pretty-printer". Try "help info".

    Some features and performance optimizations will not be available.

    These both are no log entries that come from J-Link GDB Server.
    We have neither an exit code 9, nor do we have any code in our application that could produce these strings.

    Could you make sure that you do not have any other GDB Server running?
    Where do these log entries come from?


    Could you please send us a J-Link log file? How to enable:
    wiki.segger.com/J-Link_DLL#Enable_J-Link_Log_File

    Best regards,
    Fabian
    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,

    sorry for not responding sooner.
    The log comes from Jetbrains CLion, in which I start the JLink GDB server (see attachment 1).

    The error only occurs with version 6.54. With 6.52 and now the new version 6.56, connection is made without the error code 9 (attachment 2).

    Concluding from this I supsect the error code 9 comes from GDB itself through the GDB server. Anyway, the problem disappeared with the new JLink version.

    Thanks for responding!

    Ewout
    Images

    • Schermafbeelding 2019-11-22 om 20.40.21.png

      196.08 kB, 3,218×758, viewed 560 times

    • Schermafbeelding 2019-11-22 om 20.41.28.png

      200.43 kB, 3,182×690, viewed 522 times