SDKZSPF LSI, SDKZSPF Datasheet - Page 188

• Manufacturer Part Number: SDKZSPF
• Manufacturer: LSI

Specifications of SDKZSPF

• Lead Free Status / Rohs Status: Supplier Unconfirmed

Table 9.2
9-2
Option
-mempcr=ADDR
-no_mempcr
-jtag_type=TYPE
-jtag_mapfile=FILE Makes the debugger look for the map file FILE, rather than
Special Options
where debugger name is the name of the desired debugger as listed in
Table
Table 9.1
The above command both invokes and initializes the debugger.
Command-line options only available in the SDK debuggers are listed in
Table
Use the following command to load the symbol table from the executable
file:
Next, select the debugger’s target execution environment (as described
in the following section). For example, to target the cycle-accurate
simulator:
Debugger
Copyright © 1999-2003 by LSI Logic Corporation. All rights reserved.
Debugger Name Use when debugging...
sdbug400
zdxbug
zdbug
Description
Sets the address of the mempcr register.
Specifies that the hardware target has no MEMPCR register sdbug400
Gives priority to the detection of the JTAG interface specified.
TYPE can be either pci (Corelis PCI JTAG), pcmcia (Corelis
PCMCIA JTAG), or raven (Macraigor Raven) By default,
SDBUG first attempts to use the PCMCIA JTAG card, then
the PCI JTAG card, then the Macraigor Raven interface.
the default called “mapfile” in the current directory and
SDSP_HOME/sdspI/misc.
(sdbug) file a.out
9.1.
9.2. All other options are described in Stallman, et. al.
Debugger Names
code written for devices based on the ZSP400 architecture.
code originally written for devices based on the ZSP400
architecture, but cross-compiled for the ZSPG2
architecture.
code designed for devices based on the ZSPG2
architecture.
Availability
sdbug400
sdbug400,
zdxbug
zdbug
sdbug400,
zdxbug,
zdbug