rvdebug.stp

realview22.rar

      vector=V8         \\ Address of SWI vector catch to use
      # 135 ; 
      arm_swi_num=V0x123456 \\ SWI instruction for semi-hosting
      # 301 ; 
      thumb_swi_num=V0xAB \\ Thumb SWI instruction for semi-hosting
    }
    # 286 ; 
    {.Armulator
      # 211 ; 
      clock_speed=S0.00 \\ clock speed in MHz as num.num
      # 191 ; 
      fpoint_emu=B      \\ True if floating point emulation
      # 190 ; 
      config_file=D     \\ location for armul.cnf (default: install lib directory)
    }
    # 230 ; Properties allow free-form definition of properties needed
    # by vehicle (emulator, monitor, simulator). The form of the
    # string will be "name=value" where name is the name for the
    # property as defined by the vehicle and the value will be a
    # numeric value in hex or decimal.
    properties=LS       \\ general properties for vehicle.
  }
  # 270 ;
  endianess=K(b*ig,l*ittle)0\\ ARM Sim only: Endianess of processor 
  # 236 ; The Logic Analyzer block allows selection of a logic analyzer
  # to use with the device or devices. It also controls when to
  # load the DLL. This can only be used if the logic analyzer DLL
  # is installed and licensed and if the logic analyzer is attached
  # to the same board. Note that you should consult your logic
  # analyzer vendor's instructions for proper setup.
  {.Logic_Analyzer      \\ Controls use of Logic Analyzer
    # 271 ; 
    vendor=K(ARM,AGL,TEK) \\ Chose manufacturer of analyzer \
                        \K ARM Trace Port Analyzers, Agilent Logic Analyzers,\
                           Tektronix Logic Analyzers
    # 299 ; 
    machine=S           \\ Name of Analyzer, pod, or device (if needed)
    # 179 ; 
    config=F            \\ Name of Analyzer Configuration file to load
    # 146 ; 
    load_when=K(connect,image_load,symbol_match,first_use) \
                        When to load DLL and attach to Logic Analyzer \
                        \K When connecting to device/board, \
                        When loading application to target, \
                        When loaded application contains the named symbols \
                        When first attempt to use analyzer from RVDEBUG
    # 249 ; 
    sym_match=LS        \\ Name of symbol to match
  }
  # 312 ; Cross triggering allows for HW mechanisms to stop one core/chip
  # when another stops (on break or for other reasons). This insures
  # that one can see the context of a problem that is multi-processor
  # related. Here you setup debugger commands to enable and disable
  # input and output triggering. This normally writes to a register.
  # Examples include: "ce @event_reg |= 1" and "ce @event_reg &= ~1"
  {.Cross_trigger
    # 300 ; 
    trig_in_ena=LS      \\ commands to enable trigger input
    # 159 ; 
    trig_in_dis=LS      \\ commands to disable trigger input
    # 285 ; 
    trig_out_ena=LS     \\ commands to enable trigger output
    # 148 ; 
    trig_out_dis=LS     \\ commands to disable trigger output
  }
  # 189 ; The RTOS block allows for automatic loading of RTOS/kernel
  # awareness. This block allows for forced loading of RTOS
  # support or symbol hooked. Symbol hooked means that the
  # RTOS support is only loaded when the RTOS (or its symbols)
  # are loaded to the target. Consult you vendors instructions
  # for proper setup. If supporting your own RTOS/Kernel, use
  # the setup that best matches your DLL.
  {.RTOS                \\ Controls use of RTOS/Kernel
    # 294 ; 
    vendor=S            \\ 3 letter name of RTOS/Kernel Vendor
    # 132 ;
    load_when=K(connect,image_load) \
                        When to load DLL to support RTOS/Kernel \
                        \K When connecting to device/board, \
                        When loading application to target, \
                        When loaded application contains the named symbols
    # 316 ; Base_address is used to force a base address for the RTOS. It
    # should only be used when the default location mechanism is not
    # valid or usable. For most RTOSes, the default is based on a
    # symbol or by following an anchor (such as vector).
    base_address=S      \\ Expression defining a base address override
    # 1000 ;
    cpu_id=S                    \\ Expression defining the cpu id
    # 167 ;
    Exit_Options=K(End_on_Disconnect,End_RSD_on_Unload,End_on_Unload,Prompt_on_Unload)3 \
                                                  \\ Decide when and how RTOS support is disabled
    # 208 ;
    RSD=K(Enable,Disable)1                    \\ Enable or disable Running System Debug support
    # 207 ;
    System_Stop=K(Never,Prompt,Don't_prompt)2 \\ Behavior when trying to stop the processor while RSD is enabled
  }
  # 1022 ; Monitor activation
  {.Monitor            \\ Controls debug monitor configuration
    # 1023 ; 
    type=K(none,RealMonitor) \\ Determines which monitor type to connect to.
    # 1024 ; 
    option=S                 \\ Passes monitor-specific configuration options.
  }
}
!ADVANCED

# 133 ; RDICONNECTION is used for RDI targets only. The fields can be modified
# for changing characteristics such as boardChip_name. But, the actual
# Targets and configurations should only be created using the 
# "Add/Remove/Edit Devices" menu.
[TEMPLATE=^RDICONNECTION] \\ Configuration of an RDI Debug Target
?CONFIG
?CONNECT
?REMOTE
?ADVANCED

# 122 ; DEVICE entries are used when only one device is used on the scan chain
# or when a lot of information is to be specified for a specific device.
# The CONNECTION entry can always be used instead as it will create these
# entries automatically. The name of this group must be a name within
# the Configuration file.
[TEMPLATE=DEVICE]       \\ Specification of a specific device
?CONNECT
# 226 ; Configuration is the name of a JTAG device or Configuration file.
# If no name given, the default name for the processor manufacturer will
# be used. If a path name is not given, it will be searched for in: the 
# local directory, your home directory, and then the install location's 
# etc directory. Note that the named device in this group must match the
# name in the file.
configuration=F(JTAG Files [*.dat;*.jtg]Config files [*.cnf])\\ Name/pathname of Configuration file (else default name)
aux_Configuration=F(Auxiliary File [*.dat;*.cfg;*.cnf;*.jtg]) \\ Name/pathname of Configuration file (else default name)
## 292 ; Remote allows specification of a remote workstation or PC to use to
# connect to the emulator, EVM board, or simulator. It is not needed
# when the entry is accessed via a RVBROKER group since that will specify
# the information automatically.
{.remote                \\ Remote details if explicit
  # 283 ; The hostname is the name of a remote workstation or PC that is
  # used to access this target. You can select from the list of
  # RVBROKER servers setup or enter a hostname (or IP number) directly.
  hostname=K(localhost,$GROUP=RVBROKER)\\ Host name or IP address
  # 293 ; 
  port=V0               \\ TCP/IP Port if overriding default
}
# 122 ; 
disabled=B0             \\ Disabled is used to stop this entry from being shown
# 317 ; The shared field allows this entry to be seen by remote users who
# connect via RVBROKER. RVBROKER will only show them the entries marked as
# shared in the Connection Control Window. They can still connect to
# emulators and EVMs on this host by specifying the information in their
# own board file however.
shared=B0               \\ Allows this entry to be seen remotely
?ADVANCED
# 165 ; Board_chip_name refers to the BOARD, CHIP, or COMPONENT group this is derived
# from, if any. You can refer to a BOARD/CHIP/COMPONENT name and/or define local
# advanced info. Advanced info allows support of specific chips or boards.
# See the properties on Advanced info for more details.
# Note that if the BOARD/CHIP/COMPONENT group has more than one name
# separated by '/' (such as ID/name), any of them may be used. 
boardChip_name=LK($GROUP=BOARD/CHIP/COMPONENT)\\ Pull Advanced information from BOARD/CHIP/COMPONENT entry


# 269 ; BOARD and CHIP are used when a standard board or chip (core+asics) 
# exists, either commercial or custom. A DERIVED group can refer to this
# entry by name (or ID). A CONNECTION group can refer to this entry 
# automatically using board ID lookup information. A reference to one
# of these groups allows automatic use of the Configuration file, settings, 
# and advanced information (ASIC/peripherals/memory). This entry can spefify
# the default connection information which can be overridden by the
# CONNECTION group.
[TEMPLATE=BOARD/CHIP/COMPONENT] \\ Commercial/Custom board or chip with all info
# 297 ; Configuration is the name of a JTAG device or Configuration file.
# If no name given, the default name for the processor manufacturer will
# be used. Any name can be used, and you should use one based on the 
# name of the board or chip used. If a path name is not given, it will be 
# searched for in: the local directory, your home directory, and then the
# install location's etc directory.
configuration=F(JTAG Files [*.dat;*.jtg]Config files [*.cnf])\\ Name or pathname of Configuration file (will search if not path)
aux_Configuration=F(Auxiliary File [*.dat;*.cfg;*.cnf;*.jtg]) \\ Name or pathname of Configuration file (will search if not path)
?CONNECT
?ADVANCED
# 169 ; Board_chip_name refers to a BOARD, CHIP, or COMPONENT group this is sub-derived
# from, if any. This can be used to define a board and then reference
# a custom chip or component on that board. Note that if the BOARD/CHIP/COMPONENT group has 
# more than one name separated by '/' (such as ID/name), any of them 
# may be used. 
boardChip_name=LK($GROUP=BOARD/CHIP/COMPONENT)\\ Append Advanced information from another BOARD/CHIP/COMPONENT entry

# 227 ; RVBROKER entries are used to specify a remote host (or the local host for
# simulators) that allows access to its local emulators/EVMs as well as
# simulators. The entry normally only needs to give the name of the host
# (localhost for the local PC/workstation).
[TEMPLATE=RVBROKER]     \\ Connection broker for remote/simulator use
# 296 ; Auto_connect is used to connect to this RVBROKER automatically at
# startup. The list of available simulators and target boards will be
# shown in the Connection Control Window.
auto_connect=B0         \\ Show remote simulators/emulators at startup
# 247 ; 
{.remote                \\ Remote details if explicit
  # 134 ; The hostname is the name of a remote workstation or PC that is
  # used to access this target. This is not normally needed since the
  # name of this group is usually the hostname. If this is filled in,
  # the group name is not used. This is most common when this contains
  # an IP address and the group name contains a name.
  hostname=N            \\ Host name or IP address (if diff than name)
  # 311 ; 
  port=V0               \\ TCP/IP Port if overriding default
}
# 216 ; 
description=SConnection Broker \\ Describes this host
# 295 ; The Simulator_info entry is used to provide special details just for
# simulators when we connect to them. The name of a Simulator_info entry
# is either the processor name (e.g. 470 for new_470) or a special 
# simulator container name (e.g. "Eagle" if there is a container named
# Eagle which connects multiple simulators together).
{Simulator_info         \\ Details for Instruction Set Simulators
  # 266 ; 
  sim_family=V          \\ member of processor family to use (else will ask)
  # 187 ; 
  sim_dll=LF(DLLs [*.dll]) \\ DLLs to load into simulator for ASIC/board simulations.
  # 257 ; 
  endianess=K(b*ig,l*ittle)0\\ ARM only: Endianess of processor
}
# 317 ; 
disabled=B0             \\ Disabled is used to stop this entry from being shown
[INCLUDE] (*.stc)