Executing J-Link Script Files - Segger J-Link User Manual

132
5.10.5.7 Jump statements
The following jump statements are supported by the J-Link script file language:
• return
5.10.5.8 Sample script files
The J-Link software and documentation package comes with sample script files for
different devices. The sample script files can be found at $JLINK_INST_DIR$\Sam-
ples\JLink\Scripts.

5.10.6 Executing J-Link script files

5.10.6.1 In J-Link commander
When J-Link commander is started it searches for a script file called
Default.JLinkScript. If this file is found, it is executed instead of the standard
auto detection of J-Link. If this file is not present, J-Link commander behaves as
before and the normal auto-detection is performed.
5.10.6.2 In debugger IDE environment
To execute a script file out of your debugger IDE, simply select the script file to exe-
cute in the Settings tab of the J-Link control panel and click the save button (after
the debug session has been started). Usually a project file for J-Link is set by the
debugger, which allows the J-Link DLL to save the settings of the control panel in this
project file. After selecting the script file restart your debug session. From now on,
the script file will be executed when starting the debug session.
5.10.6.3 In GDB Server
In order to execute a script file when using J-Link GDB Server, simply start the GDB
Server, using the following command line paramter:
-scriptfile <file>
For more information about the -scriptfile command line parameter, please refer
to UM08005, chapter "command line options".
J-Link / J-Trace (UM08001)
CHAPTER 5
© 2004-2011 SEGGER Microcontroller GmbH & Co. KG
Working with J-Link and J-Trace