Segger J-Link User Manual page 77

77
Command line option
-nologtofile
-halt
-nohalt
-silent
-nosilent
-stayontop
-nostayontop
-timeout
-notimeout
-vd
-novd
Following additional command line options are available. These options are temporary for
each start of GDB Server.
Command line option
-excdbg
-jtagconf
-log
-rtos
-singlerun
-jlinkscriptfile
-select
-settingsfile
-strict
-x
-xc
-cpu
3.3.5.1 -cpu
Pre-select the CPU core of the connected device, so the GDB Server already knows the
register set, even before having established a connection to the CPU.
Note
Deprecated, please use
too.
Syntax
-CPU <CPUCore>
Example
jlinkgdbserver -CPU ARM7_9
Add. information
The following table lists all valid values for <CPUCore> :
J-Link / J-Trace (UM08001)
CHAPTER 3
Do not generate a GDB Server log file. (Default)
Halt the target on start of GDB Server.
Do not halt the target on start of GDB Server. (Default)
Do not show log output.
Show log output. (Default)
Set the GDB Server GUI to be the topmost window.
Do not be the topmost window. (Default)
Set the time after which the target has to be connected.
Set infinite timeout for target connection.
Verify after downloading.
Do not verify after downloading. (Default)
Enable exception debugging.
Configures a JTAG scan chain with multiple devices on it.
Logs the GDB Server communication to a specific file.
Selects a RTOS plugin (DLL file)
Starts GDB Server in single run mode.
Specifies a J-Link script file.
Selects the interface to connect to J-Link (USB/IP).
Selects the J-Link Settings File.
Starts GDB Server in strict mode.
Executes a gdb file on first connection.
Executes a gdb file on every connection.
Selects the CPU core. Deprecated, use
-device instead. Anyhow, it does not hurt if this option is set,
© 2004-2017 SEGGER Microcontroller GmbH & Co. KG
Explanation
Explanation
-device
J-Link GDB Server
instead.