[SOLVED] JLinkGDBServer -xc reports "Unsupported remote command" for all commands in gdb script

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

  • [SOLVED] JLinkGDBServer -xc reports "Unsupported remote command" for all commands in gdb script

    Hello,
    I'm working in an environment that supports debugging many embedded projects. I'm attempting to run JLinkGDBServerCL, but I need to avoid polluting `~/.gdbinit` as much as possible. Helpfully, JLinkGDBServer provides the `-xc` switch for executing gdb command files. Unfortunately, none of the commands seem to be accepted when I use this switch:

    Source Code

    1. SEGGER J-Link GDB Server V7.54d Command Line Version
    3. JLinkARM.dll V7.54d (DLL compiled Sep 28 2021 16:18:25)
    5. WARNING: Unknown command line parameter /home/vagrant/Documents/product/build/product/bin/product_main_application.out found.
    6. Command line: -nosilent -device AT91SAM7S256 -endian little -if JTAG -speed auto -port 2159 -swoport 2160 -telnetport 2161 -timeout 15000 -singlerun -halt -xc /home/vagrant/Documents/product/build/product/etc/gdb/reset.gdbinit -ir -vd /home/vagrant/Documents/product/build/product/bin/product_main_application.out
    7. -----GDB Server start settings-----
    8. GDBInit file: /home/vagrant/Documents/product/build/product/etc/gdb/reset.gdbinit
    9. GDB Server Listening port: 2159
    10. SWO raw output listening port: 2160
    11. Terminal I/O port: 2161
    12. Accept remote connection: yes
    13. Generate logfile: off
    14. Verify download: on
    15. Init regs on start: on
    16. Silent mode: off
    17. Single run mode: on
    18. Target connection timeout: 15000 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: AT91SAM7S256
    25. Target interface: JTAG
    26. Target interface speed: auto
    27. Target endian: little
    29. Connecting to J-Link...
    30. J-Link is connected.
    31. Firmware: J-Link V9 compiled May 7 2021 16:26:12
    32. Hardware: V9.30
    33. S/N: 609300498
    34. Feature(s): RDI, FlashBP, FlashDL, JFlash, GDB
    35. Checking target voltage...
    36. Target voltage: 3.09 V
    37. Listening on TCP/IP port 2159
    38. Connecting to target...
    40. J-Link found 1 JTAG device, Total IRLen = 4
    41. JTAG ID: 0x3F0F0F0F (ARM7)
    42. Connected to target
    43. Waiting for GDB connection...Connected to 127.0.0.1
    44. Executing script file [/home/vagrant/Documents/product/build/product/etc/gdb/reset.gdbinit] ...
    45. WARNING: Unsupported remote command "monitor sleep 500"
    46. WARNING: Unsupported remote command "monitor halt"
    47. WARNING: Unsupported remote command "load"
    48. WARNING: Unsupported remote command "set mem inaccessible-by-default off"
    49. WARNING: Unsupported remote command "monitor flash download = 1"
    50. WARNING: Unsupported remote command "monitor flash breakpoints = 1"
    51. WARNING: Unsupported remote command "tb main"
    52. WARNING: Unsupported remote command "monitor reset"
    53. Reading all registers
    54. Read 4 bytes @ address 0x00000000 (Data = 0x00000000)
    55. Read 4 bytes @ address 0xFFFFFFFC (Data = 0x00000000)
    56. Read 4 bytes @ address 0x00000000 (Data = 0x00000000)
    57. Read 4 bytes @ address 0xFFFFFFFC (Data = 0x00000000)
    58. Read 2 bytes @ address 0x00000000 (Data = 0x0000)
    59. Read 2 bytes @ address 0xFFFFFFFE (Data = 0x0000)
    60. Read 2 bytes @ address 0xFFFFFFFC (Data = 0x0000)
    61. Read 2 bytes @ address 0x00000000 (Data = 0x0000)
    62. Read 2 bytes @ address 0xFFFFFFFE (Data = 0x0000)
    63. Read 2 bytes @ address 0xFFFFFFFC (Data = 0x0000)
    64. Read 4 bytes @ address 0x00000000 (Data = 0x00000000)
    65. Read 4 bytes @ address 0xFFFFFFFC (Data = 0x00000000)
    66. Read 4 bytes @ address 0x00000000 (Data = 0x00000000)
    67. Read 4 bytes @ address 0xFFFFFFFC (Data = 0x00000000)
    68. Read 4 bytes @ address 0x00000000 (Data = 0x00000000)
    69. Read 4 bytes @ address 0x00000000 (Data = 0x00000000)
    70. Read 4 bytes @ address 0x00000000 (Data = 0x00000000)
    71. Downloading 112 bytes @ address 0x00101400 - Verified OK
    72. Downloading 15952 bytes @ address 0x00101600 - Verified OK
    73. Downloading 16016 bytes @ address 0x00105450 - Verified OK
    74. Downloading 15888 bytes @ address 0x001092E0 - Verified OK
    75. Downloading 16080 bytes @ address 0x0010D0F0 - Verified OK
    76. Downloading 16064 bytes @ address 0x00110FC0 - Verified OK
    77. Downloading 16096 bytes @ address 0x00114E80 - Verified OK
    78. Downloading 16048 bytes @ address 0x00118D60 - Verified OK
    79. Downloading 16032 bytes @ address 0x0011CC10 - Verified OK
    80. Downloading 16000 bytes @ address 0x00120AB0 - Verified OK
    81. Downloading 16032 bytes @ address 0x00124930 - Verified OK
    82. Downloading 16032 bytes @ address 0x001287D0 - Verified OK
    83. Downloading 2444 bytes @ address 0x0012C670 - Verified OK
    84. Downloading 7248 bytes @ address 0x0012CFFC - Verified OK
    85. Downloading 2 bytes @ address 0x0013FFFE - Verified OK
    86. Writing register (PC = 0x 101400)
    Display All

    The gdb script in question is as follows:

    Source Code

    1. monitor sleep 500
    2. monitor halt
    3. load
    4. set mem inaccessible-by-default off
    5. monitor flash download = 1
    6. monitor flash breakpoints = 1
    7. tb main
    8. monitor reset
    I tried wrapping the commands in `eval "<line>"` to no avail. The `-x` flag yields the same result. How can I make JLinkGDBServer execute this gdb script upon connection? Thanks for your time.

  • The -xc option is for GDB not GDBServer.
    These are 2 different products from 2 different vendors.
    gdbinit files are for GDB, not GDBServer.

    I need to check why the "GDBInit file:" output for GDBServer actually exists because it does not really make any sense.
    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.