# 185 ; Template file for rvdebug.brd files. This provides the templates for
# managing and editing board files for ARM and DSP processors.
# This file is read in by the settings window when a file has $rvdebug
# near the top.

# 185 ; CONNECTION is used by emulators, monitors, and simulators to get a list 
# of one or more devices. For a JTAG emulator, this is the list of devices
# in the scan chain. For a monitor or simulator, this is the processor
# that is to be accessed. The Configuration file serves three 
# purposes: it provides the type of the device, the position of the 
# device in the chain, and a name used to specify what to connect to.
# In some Configuration file forms, additional information such as speed 
# adjust may be spcified as well. 
[TEMPLATE=CONNECTION] \\ JTAG Scan file or Configuration using processor manufacturer format
=CONFIG
# 206 ; The Configuration name or pathname is used to specify a specific JTAG scan
# or Configuration file. The default is to search for the file with the same name as 
# this group (after the "=" sign) in the local directory, your home directory,
# and the <install>/etc directory. The name in this field does not have to
# be the same as the name of this group. If the file specified here is
# a full pathname, then only that location will be used, else searched.
configuration=F(JTAG Files [*.dat;*.jtg]Config files [*.cnf])   \\ Optional full pathname of Configuration file (else searches).
aux_Configuration=F(Auxiliary File [*.dat;*.cfg;*.cnf;*.jtg]) \\ Optional full pathname of Configuration file (else searches).
# 225 ; Auto_connect is used to expand the list of devices on the target board
# using the information from the Configuration file (e.g. arm.jtg or armulate.cnf).
# The  list of devices will be shown in the Connection Control Window. The 
# devices can then be connected-to with a single click. 
auto_connect=B0         \\ Show devices in file at startup.
# 143 ; Pre-connect is used to force an order for device connection. When an
# attempt is made to connect to a device within the Configuration file, 
# this can be used to insure that a specific one or ones are connected 
# first, no matter which was selected to connect to. This allows pre-setup 
# of the specific devices to insure proper operation (such as initializations).
# The device(s) to connect to first may be specified by name, by 
# processor name, or by processor type.
pre_connect=LS          \\ Connect named device or type before any others
!CONFIG
=CONNECT
# 186 ;
description=S           \\ Description of what board/processor/emulator this is for.
# 309 ; Connect With is used to specify the emulator/EVM or simulator to
# use when connecting to a target device. The manufacturer name is 
# selected along with the type of emulator/EVM in use. An I/O value
# may be provided as well if not the default.
{.connect_with          \\ How to connect to target (which EMU/EVM or simulator).
  # 324 ; The manufacturer specifies the name of the EMUlator or EVM board (or
  # Simulator) and what type of emulator/EVM (e.g. PP for parallel port).
  # The list presented is based on what could be connected to but does not
  # verify you have the license or hardware to connect to it.
  manufacturer=K($MANU_LIST) \\ Manufacturer name and connection type.
  # 315 ; The IOdevice field contains the information needed to connect to
  # HW. The meaning depends on what you are connecting to. It is normally
  # an ISA/PCI port address for cards, a COM/LPT port for serial and 
  # parallel (1, 2, etc), a SCSI id or SBus id for workstations, etc. 
  # You need to consult your emulator/EVM/monitor manufacturer for details. 
  # This can be left empty for the default setting as defined by the
  # manufacturer. For simulators, this
  # may be set to a family id when the simulator is treated as a
  # device (see also family id in RVBROKER group). For family details, check
  # the documentation on the simulator. 
  IOdevice=V            \\ I/O Device or port if not default.
  # 164 ; Speed can be used to set the emulation speed for some emulators. This
  # will allow running the emulation clock slower when the device(s) 
  # are running too slow. You only need to set this when the default
  # does not work. The lower numbers are faster, the higher numbers
  # are slower.
  Speed=V(1-20)         \\ Emulator Speed if required
  # 281 ; 
  {.Ethernet            \\ Ethernet Network based emulator
    # 267 ; this is the 'hostname' of the emulator as a name registered with
    # the local operating system (NIS or DNS or hosts file) or an IP
    # address expressed in 0.0.0.0 format (where each 0 is replaced 
    # with the correct number). If you do not know the hostname of
    # the emulator, you can check with System Administration.
    hostname=S          \\ hostname or IP address of emulator
    # 282 ;
    port=V              \\ port number of emulator, else default.
  }
}
# 166 ; The project field is used to auto-open one or more projects when
# connecting to this board. Note that if more than one device is in
# the scan-chain and they are the same processor type, you must set
# the 'specific device' field of the project to bind the project to
# the correct device(s). If the devices are different processor
# types, this is not necessary.
project=LF(Projects [*.prj])    \\ Project(s) to open when connecting
!CONNECT
=REMOTE
# 142 ; 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
  # 272 ; 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
  # 235 ; 
  port=V0               \\ TCP/IP Port if overriding default
}
# 325 ;
disabled=B0             \\ Disabled stops this entry from being shown in the Connection Control Window
# 310 ; 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
# 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 information. 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
!REMOTE
=ADVANCED
# 224 ; The family select field is used to ensure the correct family member is
# used (for memory mapping, registers, etc) when the silicon id is
# ambiguous. Some chip families do not use a different silicon ID for
# different members of the family, and this field allows you to specify
# which you are using. The format of this field can be to specify the
# family member using one of three forms: name=family_name, family_name,
# and silicon_id. The name=family_name form allows you to specify the name
# of the device (by name in the Configuration file or processor name) - this
# is used when multiple chips are together but from different families.
# The family_name is the name of the family member from a builtin list.
# The silicon_id can be expressed as num.num.num form or as a value.
family_select=LS        \\ Coerce family member for ambiguous chips
# 184 ; Advanced Information is used to provide extended details about the 
# target system under debug. It allows provision of specific details
# such as extended memory mapping, mapped registers, peripherals, and
# so on. Because more than one device may be present, and each may have 
# different details, you may create more than one information block. The 
# base block is called "Default" and will be used if no other name
# is provided. Named entries may be the same as a processor or device names
# in the Configuration file (arm.jtg or armulate.cnf type files). The order 
# of  matching is always device name, else processor name, else "default". 
# If any are called "all", these will always be used no matter which 
# name is otherwise selected.
# Note that advanced information can be nested such that one may refer to 
# another which may refer to another using the boardChip_name field. These 
# references will cause the information to be appended together. 
{Advanced_Information   \\ Extra details about target processor and board.
  # 245 ; Pre-connect is used to force an order for device connection. When an
  # attempt is made to connect to a device within the Configuration file, 
  # this can be used to insure that a specific one or ones are connected 
  # first, no matter which was selected to connect to. This allows pre-setup of the
  # specific devices to insure proper operation (such as initializations).
  # The device(s) to connect to first may be specified by name, by 
  # processor name, or by processor type.
  pre_connect=LS        \\ Connect named device or type before this one connects
  # 264 ; The commands entry allows specification of RVDEBUG commands to run
  # after connect. The most common example is the "include" command
  # which includes commands from a file. The commands will be run just
  # after the connection is completed. If Pre-connect is used, and the
  # pre-connected device is running this command, the command will
  # execute *before* the original device is connected.
  commands=LS           \\ RVDEBUG commands to run after connect
  # 308 ; The Connect_mode field is used to determine how to connect to the
  # target (within what is supported by the vehicle). If a connection
  # mode is selected that is not supported, it will default to the
  # normal behavior and warn.
  connect_mode=K(no_reset_and_stop,no_reset_and_no_stop,reset_and_stop,reset_and_no_stop,prompt) \\ How to connect (if vehicle supports)
  # 163 ; The Disconnect_mode field is used to determine how to disconnect from
  # the target (within what is supported by the vehicle). If a disconnect
  # mode is selected that is not supported, it will default to the
  # normal behavior and warn.
  disconnect_mode=K(as_is_with_debug,as_is_without_debug,prompt) \\ How to disconnect (if vehicle supports)
  # 256 ; Application load is used to change the way that an application program
  # executable image is loaded into target memory. The default is to 
  # write the memory via the emulator or EVM board. This allows overriding 
  # that model to disable all image load (for pure ROM/EPROM systems) or 
  # to run an external program to do the load.
  {.Application_Load    \\ Overrides normal application load technique
    # 177 ; 
    load_using=K(normal,symbols_only,shell_command)0 \\ How to perform load \
                        \KNormal load via the emulator/EVM,Do not load image,\
                        Load using shell command
    # 215 ; The load command is a shell command to run to perform the load. The
    # command may contain "$" variables which will be substituted by
    # RVDEBUG before calling. The allowed $ variables are: $D for the
    # directory of the application, $P for the full path of the application,
    # $F for the filename of the application, $N for the name of the
    # application without the extension. If the command starts with an
    # exclamation sign ("!"), the return value of the shell command will
    # not be used to stop the load, otherwise a non-0 return will abort
    # the load. In all cases, the output of the command will be shown
    # in the output log.
    load_command=S      \\ Shell command to run to perform load
    # 205 ; Load Set PC is used to control how the program counter is initialized
    # during a load. The default is to set the PC to the entry point if
    # an entry point defined and symbols are loaded and this is not an
    # appended load (it is replace or new). This allows disabling setting
    # the PC under any situation or setting it specifically to address 0. 
    load_set_pc=K(normal,none,to_zero)0 \\ controls setting of program counter \
                        \KUse normal rules,Disable setting PC,\
                        Set PC to address 0
  }
  # 223 ; The Chip-id (or silicon-id) is loaded from the processor normally. 
  # For cases of special custom chips, it may be necessary to force the 
  # id to get the correct behavior. The id can be expressed as a 16 bit 
  # number or in num.num.num form. It can also be expressed as a name
  # of the family member if known.
  id_c*hip=N            \\ Chip-id override to load chip/peripheral information.
  # 323 ; The ID-Match field is the expected silicon ID from the processor. If
  # it does not match this value, the user is prompted to decide whether to
  # continue the connect or not. The id can be expressed as a 16 bit 
  # number or in num.num.num form.
  id_ma*tch=N           \\ Chip-id expected to match for load.
  # 255 ; The Chip-id is used to determine the manufacturer name of the actual
  # device (such as family name or core name). The chip-name field allows
  # specifying a name to use in messages and Manager lists. It does not
  # enforce the chip family selection. For that, you use the id_chip
  # field.
  chip_name=N           \\ Expected name of chip/device to show.
  # 157 ; The Memory_block entries are used to build up fixed, enabled, or based
  # memory regions. A fixed block is one that refers to memory that is
  # always enabled and always at the same place and size. An enabled
  # memory block is enabled/disabled by a register value (see Map_rule).
  # A based memory block has its start or length adjusted/set by a 
  # register's content; the content may be added to an offset or may
  # refer to the actual meaning.
  {Memory_block         \\ Define an external/ASIC memory region
    # 158 ; The start address is the base address that the block maps at. If
    # the block is mapped via a register, this is the offset from that
    # register.
    *start=V            \\ Start address/offset of memory block