414 CHAPTER 15 Device specifics
J-Link / J-Trace (UM08001) ©
2004-2017 SEGGER Microcontroller GmbH & Co. KG
15.17.1.2Selecting the device when using GDBServer
When using the J-Link GDBServer, the device needs to be known before GDB con-
nects to the GDBServer since GDBServer connects to the device as soon as it is
started. So selecting the device via monitor command is too late. In order to select
the device before GDBServer connects to it, simply start it with the following com-
mand line:
-device <DeviceName>
Example: JLinkGDBServer -device AM3359
15.17.1.3Selecting the device when using J-Link Commander
For J-Link Commander, type:
device <DeviceName>
Then J-Link Commander will perform a reconnect with the device name selected
before.
15.17.1.4Known values for <DeviceName>
For a list of all supported devices, please refer to http://www.segger.com/
jlink_supported_devices.html
15.17.1.5Required J-Link hardware version
The special handling for the AM335x cannot be supported by some older hardware
versions of J-Link, so the device cannot be used with these versions.
The following hardware versions come with AM335x support:
• J-Link V8 or later
• J-Link PRO V3 or later
• J-Link ULTRA V4 or later
• Flasher ARM V4 or later
15.17.2 AM35xx / AM37xx
Script is not needed. Refer to AM335x special handling. Same needs to be done for
AM35xx / AM37xx.
15.17.3 OMAP4430
Script is not needed. Refer to AM335x special handling. Same needs to be done for
AM35xx / AM37xx.
15.17.4 OMAP-L138
Needs a J-Link script file to guarantee proper functionality.
J-Link script file can be found at
$JLINK_INST_DIR$\Samples\JLink\Scripts.
For more information about how to use J-Link script files, please refer to Executing J-
Link script files
on page 220.
15.17.5 TMS470M
Needs a J-Link script file to guarantee proper functionality.
J-Link script file can be found at
$JLINK_INST_DIR$\Samples\JLink\Scripts
For more information about how to use J-Link script files, please refer to Executing J-
Link script files
on page 220.
To Next Page
Loading...
