UM1250 GDB command files
Defines the commands for connecting to all the targets supported by the ST40 Micro Toolset including simulated targets.
See
Section 1.1: Target connection overview on page 10
.
2.78 sh4targets-attach.cmd
Defines the commands for attaching to a running target using the resettype=break reset
type of the STMC1 or STMCLite (see
Table 7: Common STMC configuration commands on page 15
and
Table 18: ST TargetPack STMC configuration commands on page 24
). These
commands do not reconfigure the target, instead they allow the user to take control of a
running target, see
Table 19
.
Table 95.
sh4targets-attach.cmd
Command
attach-sh4be attach-sh4le attach-sh4 attach-st40300be attach-st40300le attach-st40300
Description
Attach to a generic SH-4 target (big endian).
Attach to a generic SH-4 target (little endian).
As above but for a target with an ST40-300 core.
attach-stb7100-bypass attach-stb7100-stmmx
(1) attach-sti7200-bypass
attach-sti7200-stmmx
(1)
attach-stv0498-bypass
Attach to an STi5202/STb7100/STb7109 target where the STMC is configured for a direct connection to the
ST40 CPU. See stb7100_bypass_setup_attach in
stb7100jtag.cmd on page 65
.
Attach to an STi5202/STb7100/STb7109 target where the STMC1 is configured to use the ST MultiCore/MUX device to connect to the ST40 CPU. See stb7100_stmmx_setup_attach
in
stb7100jtag.cmd on page 65
.
Attach to an STi7200 target where the STMC is configured for a direct connection to the ST40 CPU. See sti7200_bypass_setup_attach
in
sti7200jtag.cmd on page 66
.
Attach to an STi7200 target where the STMC1 is configured to use the ST MultiCore/MUX device to connect to the ST40 CPU. See sti7200_stmmx_setup_attach
in
sti7200jtag.cmd on page 66
.
Attach to an STV0498 target where the STMC is configured for a direct connection to the ST40 CPU. See stv0498_bypass_setup_attach
in
stv0498jtag.cmd on page 66
.
1.
Only supported by the STMC1.
8045872 Rev 9 67/87
GDB command files
Note:
UM1250
The equivalent sh4be and sh4le commands are listed in
Table 96
.
Table 96.
ST40 sh4be and sh4le equivalents
Command connectsh4be/connectsh4le equivalent
attach-sh4be attach-sh4le attach-sh4 attach-st40300be attach-st40300le attach-st40300 attach-stb7100-bypass attach-stb7100-stmmx attach-sti7200-bypass attach-sti7200-stmmx attach-stv0498-bypass sh4be $arg0 "resettype=break ondisconnect=restart" sh4le $arg0 "resettype=break ondisconnect=restart" st40300be $arg0 "resettype=break ondisconnect=restart" st40300le $arg0 "resettype=break ondisconnect=restart" sh4le $arg0 "resettype=break ondisconnect=restart jtagpinout=st40
-inicommand stb7100_bypass_setup_attach" sh4le $arg0 "resettype=break ondisconnect=restart jtagpinout=stmmx tdidelay=1 -inicommand stb7100_stmmx_setup_attach" sh4le $arg0 "resettype=break ondisconnect=restart jtagpinout=st40
-inicommand sti7200_bypass_setup_attach" sh4le $arg0 "resettype=break ondisconnect=restart jtagpinout=stmmx tdidelay=1 -inicommand sti7200_stmmx_setup_attach" sh4le $arg0 "resettype=break ondisconnect=restart jtagpinout=st40
-inicommand stv0498_bypass_setup_attach"
In
Table 96 , $arg0 is the name (or IP address) of the ST Micro Connect.
The attach commands do not perform any target-specific customization (unlike the target-specific connection commands, see
Section 1.1: Target connection overview on page 10
). As a result, no GDB convenience variables are defined for the memory-mapped configuration registers. To define these convenience variables, invoke the appropriate SoC command for the target (see
Section 2.1: register40.cmd on page 29
). For example, to
define the memory-mapped configuration registers for an STb7109E-Ref board (MB448), invoke the stb7109_si_regs command.
For convenience, the attach command and SoC command can be combined by the user into a new GDB user command to provide a target-specific attach command. For example: define attach-mb448
source register40.cmd
source display40.cmd
attach-stb7100-bypass $arg0
stb7109_si_regs end
68/87 8045872 Rev 9
