J-Link GDB Server Command

J-Link GDB Server - SEGGER

Hilden, Germany – September 15th, 2011 – SEGGER Microcontroller today announced the free
availability of the J-Link GDB-Server. As the GNU-tool-chain gains ground in terms of performance and usability, GDB continues to grow in popularity. Per the numerous requests of this expanding community, SEGGER is now offering their professionally developed GDB-Server for free to all users of the SEGGER J-Link product line. The free GDB-server is now available for download as part of the J-Link Software and Documentation pack V4.35e.

“With the now free GDB-Server the GNU community has easier access to the fastest debug emulator in the market. For an unlimited debug experience we also offer Flash Breakpoints. This option is included in our non-commercial J-Link EDU, which is especially attractive to educational institutions”, says Dirk Akemann, Partnership Marketing Manager at SEGGER.

Full product specifications are available at: www.segger.com/jlink.html
The J-Link-Software is available at: www.segger.com/download_jlink.html.

J-Link GDB Server

The J-Link GDB Server is a remote server for the GDB which allows to use J-Link with GDB or any toolchain which uses GDB as debugging interface, such as Yagarto and Sourcery G++). The GDB and GDB Server communicate via a TCP/IP connection, using the standard GDB remote serial protocol. The GDB supports a standard set of commands like open elf/bin files, reading/writing memory, etc. Beside this, the GDB also supports so called monitor commands which are passed to the GDB Server and interpreted by it, allowing it to implement J-Link specific commands like reading/writing CP15 registers, enabling flash download via J-Link, using Unlimited Flash Breakpoints, enabling semihosting, etc. In general, the J-Link software and documentation package comes with two versions of the GDB Server: A GUI based one and a command-line version.

 Documentation download

GNU Project Debugger (GDB) overview

The GNU Project Debugger (GDB) is a freely available debugger, distributed under the terms of the GNU Public license (GPL). It connects to an emulator via a TCP/IP connection. It can connect to every emulator for which a GDB server software is available. The latest Unix version of the GDB is freely available from the GNU committee under: http://www.gnu.org/software/gdb/download/

Supported cores

Currently, the J-Link GDB Server can be used with the following CPU cores:

  • ARM7/9/11
  • Cortex-A5/A8/A9
  • Cortex-M0/M0+/M1/M3/M4/M7
  • Cortex-R4
  • Microchip PIC32
  • Renesas RX610, RX621, RX62N, RX62T, RX630, RX631, RX63N

Availability

J-Link GDB Server comes with cross-platform support and is available for Windows, Linux and Mac OS X.

Requirements

To use the J-Link GDB Server, you have to meet the following requirements:

J-Link GDB Server (GUI Version)

The J-Link GDB Server‘s user interface shows information about the debugging process and allows the user to configure some settings like target endianess, if memory reads should be cached in order to improve performance or if a logfile shall be generated.

J-Link GDB Server (Command Line Version)

The command line version of J-Link GDB Server is a special version of the J-Link GDB Server which does not provide any GUI interface and has been especially developed for J-Link Linux & MAC support. It basically provides the same features as the GUI Version of J-Link GDB Server. The command line version of the J-Link GDB Server is also available for Windows and comes with the regular J-Link software and documentation package.

Setting up the J-Link GDB Server

Typically, most of the GDB and target setup is done from GDB via remote commands (monitor) in the .gdbinit file. The commands used in the .gdbinit file are performed before the download of the application into the target memory is performed. This allows the user to perform initialization steps which might be necessary to enable the access to the target memory. The .gdbinit file also allows to use download into flash memory via J-Link and Unlimited Flash Breakpoints. Nevertheless, some options need to be setup when starting the GDB Server (Target endianess, device name for devices which need a special connect sequence) since this information is needed to guarantee a proper target connection

Protocol extensions

    • SWO support
      GDB Server supports transfer of SWO data (terminal output, instrumentation trace, PC samples, etc.)

J-Link GDB Server

The GNU Project Debugger (GDB) is a freely available and open source debugger. It can be used in command line mode, but is also integrated in many IDEs like emIDE
or Eclipse.
J-Link GDB Server is a remote server for GDB making it possible for GDB to connect to and communicate with the target device via J-Link.

GDB Server and GDB communicate via a TCP/IP connection, using the standard GDB remote protocol. GDB Server receives the GDB commands, does the J-Link communication and replies with the answer to GDB.

With J-Link GDB Server debugging in ROM and Flash of the target device is possible and the Unlimited Flash Breakpoints can be used.

It also comes with some functionality not directly implemented in the GDB. These can be accessed via monitor commands, sent directly via GDB, too.

The GNU Project Debugger (GDB) is a freely available debugger, distributed under the terms of the GPL. The latest Unix version of the GDB is freely available from the
GNU committee under: http://www.gnu.org/software/gdb/download/
J-Link GDB Server is distributed free of charge.

Setting up GDB Server GUI version

The GUI version of GDB Server is part of the Windows J-Link Software Package (JLinkGDBServer.exe).
When starting GDB Server a configuration dialog pops up letting you select the needed configurations to connect to J-Link and the target.

All configurations can optionally be given in the command line options.
Note:

To make sure the connection to the target device can be established corretly, the device, as well as the interface and interface speed have to be given on
start of GDB Server, either via command line options or the configuration dialog. If the target device option (-device) is given, the configuration dialog will not pop up.

GDB Server user interface

The J-Link GDB Server?s user interface shows information about the debugging process and the target and allows to configure some settings during execution.

It shows following information:

  • ? The IP address of host running debugger.
  • ? Connection status of J-Link.
  • ? Information about the target core.
  • ? Measured target voltage.
  • ? Bytes that have been downloaded.
  • ? Status of target.
  • ? Log output of the GDB Server (optional, if Show log window is checked).
  • ? Initial and current target interface speed.
  • ? Target endianess.

These configurations can be made from inside GDB Server:

  • ? Localhost only: If checked only connections from 127.0.0.1 are accepted.
  • ? Stay on top
  • ? Show log window.
  • ? Generate logfile: If checked, a log file with the GDB <-> GDB Server <-> J-Link communication will be created.
  • ? Verify download: If checked, the memory on the target will be verified afterdownload.
  • ? Init regs on start: If checked, the register values of the target will be set to a reasonable value before on start of GDB Server.

Supported remote (monitor) commands

J-Link GDB Server comes with some functionalities which are not part of the standard GDB.

These functions can be called either via a gdbinit file passed to GDB Server or via monitor commands passed directly to GDB, forwarding them to GDB Server.

To indicate to GDB to forward the command to GDB Server ’monitor’ has to be prepended to the call.

For example a reset can be triggered in the gdbinit file with "reset" or via GDB with "monitor reset".

Following remote commands are available:

Following remote commands are deprecated and only available for backward compability:

Note: The remote commands are case-insensitive.

Note: Optional parameters are set into square brackets.

Note: The examples are described as follows:

  • Lines starting with ’#’ are comments and not used in GDB / GDB Server.
  • Lines starting with ’>’ are input commands from the GDB.
  • Lines starting with ’<’ is the output from GDB Server as printed in GDB.
时间： 2024-11-07 04:58:57

J-Link GDB Server Command的相关文章

开发环境：vs2017+samba+gdb server

距离入职还有两周不到,接老大的任务,先自己学习 Linux 编程.作为一个渣渣,vim 这种编辑器之神完全驾驭不住,还是希望能够使用世界上最好的 IDE -- Visual Studio 继续我的开发工作.好在 VS 最新版本 2017 已经原生支持 Linux 开发,问题就在于如何配置起来. 具体情况是这样的: 编写代码的环境是 Windows 10 + Visual Studio 2017 Enterprise (不知道 Community 支不支持) 运行代码的环境是使用 VirtualB

GDB LLDB COMMAND MAP

Below is a table of GDB commands with the LLDB counterparts. The built in GDB-compatibility aliases in LLDB are also listed. The full lldb command names are often long, but any unique short form can be used. Instead of "breakpoint set", "br

linux 编译 freescale arm 的gdb server

1.官网下载 gdb-7.8.tar.gz http://ftp.gnu.org/gnu/gdb 2.解压 $ tar zxf gdb-7.8.tar.gz 参考 gdb-7.8/gdb/gdbserver/README,按如下描述进行配置. 3.新建空目录 $ mkdir s-clean-gdb$ cd s-clean-gdb 4.生成配置文件 s-clean-gdb$ export CC=arm-fsl-linux-gnueabi-gccs-clean-gdb$ ./../gdb-7.8/g

Chapter 5 MySQL Server Administration_1

Chapter 5 MySQL Server Administration Table of Contents 5.1 The MySQL Server 5.1.1 Configuring the Server 5.1.2 Server Configuration Defaults 5.1.3 Server Option and Variable Reference 5.1.4 Server Command Options 5.1.5 Server System Variables 5.1.6

实例学习gcc+gdb+make

1 小侃GCC 在正式使用gcc之前,我们先来侃侃gcc是啥玩意儿? 历史 现在的GCC是GNU Compiler Collection的简称,既然是Collection,就是指一些工具链的集合. 最初的GCC(当时还只有C编译器,GCC还是GNU C Comiler的简写)是由Richard Stallman开发的,Stallman也是GNU工程的首创者,那时还是在1984年. 随着程序设计语言的发展,GCC逐渐开始支持C语言之外的语言,如C++.Objective-C.Java.Fortra

学习的例子gcc+gdb+make

1 小侃GCC 在正式使用gcc之前,我们先来侃侃gcc是啥玩意儿? 历史 如今的GCC是GNU Compiler Collection的简称.既然是Collection,就是指一些工具链的集合. 最初的GCC(当时还仅仅有C编译器,GCC还是GNU C Comiler的简写)是由Richard Stallman开发的,Stallman也是GNUproject的首创者.那时还是在1984年. 随着程序设计语言的发展,GCC逐渐開始支持C语言之外的语言,如C++.Objective-C.Java.

Android gdb so

gdb debug an android application 1.gdb 要有gdbserver 一般模拟器默认装有gdbserver,如2.3.3的模拟器,看一下有没有: D:\Developer\sdk\platform-tools>adb shell ls -l /system/bin/gdb*-rwxr-xr-x root shell 5664 2010-07-01 05:03 gdbjithelpe-rwxr-xr-x root shell 151868 2010-05-11 09

arcmap Command

The information in this document is useful if you are trying to programmatically find a built-in command, menu, or toolbar. The ICommandBars::Find and ICommandBar::Find methods can be used to get a reference to a specific toolbar, menu, or command. B

linux下gcc编译多个源文件、gdb的使用方法（转）

原文 http://www.cnblogs.com/jiu0821/p/4483804.html 一. gcc常用编译命令选项 假设源程序文件名为test.c. 1. 无选项编译链接 用法:#gcc test.c 作用:将test.c预处理.汇编.编译并链接形成可执行文件.这里未指定输出文件,默认输出为a.out. 2. 选项 -o 用法:#gcc test.c -o test 作用:将test.c预处理.汇编.编译并链接形成可执行文件test.-o选项用来指定输出文件的文件名. 3. 选项 -