prj_set.stp

realview22.rar

# 622 ; Settings allow special control over the application when debugging
# it. These include load controls, breakpoints to set, etc.
[TEMPLATE=&SETTINGS]
# 603 ; Open_load defines what action to take when the project is opened
# into a connection (either from Project Open request or when a
# matching connection is opened). The default is to register the
# application filename with the connection. Then, a subsequent
# reload, go, or step will cause the file to be loaded. This
# field allows forcing the file to be loaded as soon as the
# connection is made. It can be loaded fully (symbols+image) or
# just symbols.
open_load=K(register_name,load_full,load_symbols)0 \\ Action to take on project open \
                                \K Only register filename (auto-loads on Go or reload), \
                                   Load file (symbols and image), \
                                   Load symbols only
# 439 ; Auto_close causes the project to close when the last connection
# using it is disconnected. This can be used with the project open
# control in the board-file which allows auto-open of a project
# on connect.
auto_close=B0                   \\ Close project when last connection using it closes
# 557 ; When the lock field is set to version (under source control), this
# field allows control over the action to take when the project settings
# are to be edited. The default is to ask (when the file is read-only)
# if you want it checked out from source control. You can have it 
# automatically checkout the file or do nothing.
vers_checkout=K(prompt,force,never)0    \\ Action to take for versioned projects on Edit \
                                \K Prompt if checkout desired, \
                                   Always checkout on Edit, \
                                   Never checkout on Edit
# 520 ; When the lock field is set to version (under source control), this
# field allows control over the action to take when the project settings
# are saved and the settings window closed. The default is to ask if
# you want to have the file checked back into source control. You can
# have it always check it back in or do nothing.
vers_checkin=K(prompt,force,never)0 \\ Action to take on Save \
                                \K Prompt if checkin desired, \
                                   Always checkin on Save, \
                                   Never checkin on Save
# 519 ; Image load controls download of target application images. It
# allows override of behavior when RVDEBUG is downloading the 
# image (actual values).
{.Image_load                    \\ Controls application image load
  # 686 ; Load-act controls the action on a full download. A full load is
  # one where the image and symbols are loaded (vs. reload). The
  # default action is normally to disable interrupts to allow the
  # application initialization code an opportunity to get setup
  # before any interrupts come in. It is possible to disable this
  # here. It is also possible to instead have the chip reset on
  # load (after the load).
  load_act=K(default,noimask,reset,pre_reset)0 \\ Action to take on full load \
                                \K Default action (may disable interrupts), \
                                   Do not disable interrupts, \
                                   Do a processor reset after load, \
                                   Do a processor reset before load
  # 641 ; The PC is normally set on full download. It will also be set
  # when loading symbols. This allows overriding that behavior to
  # always or never set the PC. It also allows forcing the PC to
  # a specified default location.
  set_pc=K(auto,never,always,use_def)0\\ Controls setting entry point on load
  # 569 ; If no entry point is defined, the behavior will be based on the
  # processor in use. This allows specifying a PC to use in that
  # case.
  default_pc=V                  \\ Default if no entry specified in file
  # 588 ; The load command will normally set certain registers based
  # on processor issues (such as reset behavior). This allows
  # specifying other registers (including memory mapped) to set
  # on load. The syntax is "@reg=0x1234". These will be performed
  # before the load.
  load_reg_set=LS               \\ Registers to set on load
  # 640 ; The restart command normally just sets the PC to the entry
  # point of the application. Some programs are not restartable
  # this way due to the use of initialized data. This allows changing
  # restart to perform a reload instead. You can have it reload only
  # the data or code+data.
  restart_act=K(set_pc,reload,reload_data)0 \\ Action on Restart request \
                                \K Set the PC to the entry point, \
                                   Reload whole image (same as reload), \
                                   Reload only data (not code)
  # 506 ; The restart command normally just moves the PC. You can also
  # have it reload usinug the restart_act field. With this field,
  # you can have it reset the processor prior to the restart.
  restart_reset=B0              \\ Reset the processor before a restart
  # 460 ; By default, RVDEBUG will verify the load by reading back the
  # 4 bytes (or 8 on some processors) at the beginning and end
  # of each section or download block (2K usually). This can be
  # disabled or made stronger. Note that below you can change
  # a verify failure from an error to a warning.
  verify=K(none,fast,full)1     \\ Read-back verify on download \
                                \K Do not verify, \
                                   Just start/end of sections (default),\
                                   Verify all data written
  # 698 ; 
  verify_warns=B0               \\ Only warn (vs. fail) on bad verify.
  # 1001 ; 
  imagecache_enabled=B1  \\Enables\Disables the image cache.
}
# 697 ; Auto_set breaks are ones that are set as soon as a symbol is
# matched (or on any load if no symbol). These can be used to
# set at exit points or in special error handlers.
{Auto_Set_Breaks                \\ Automatically set breakpoints
  # 438 ; The symbol field defines a symbol name to match. If set,
  # it will be looked up after each load. If matched, the
  # break will be set (optionally prompting 1st). If not set,
  # the break will be set on connect.
  symbol=S                      \\ Optional symbol to match
  # 495 ; The cmd field defines the exact break command to use. An
  # example is 'bi my_location'.
  cmd=S                         \\ Break command to use
  # 685 ; 
  description=S                 \\ Description message to print to command area
  # 437 ; If prompt is True, the user will be shown the list of prompt
  # Auto_set breaks to confirm setting them.
  prompt=B                      \\ True if ask user 1st before setting
}
# 723 ; Named breaks are defined as ones that the user would want
# to set often. The Named Breakpoints menu item will show
# a list of these. It will grey any that have the symbol specified
# and it is not currently loaded. This allows the user to easily
# set breaks that are specific to the application, an RTOS, 
# library, or subsystem.
{Named_Breaks                   \\ Named breakpoints from menu
  # 535 ; The symbol field defines a symbol name to match. If set,
  # it will be looked up when the user raises the list dialog
  # to validate if this breakpoint is possible. If not, it
  # will be shown grey. If the symbol field is empty, the
  # item will always show.
  symbol=S                      \\ Optional symbol to match
  # 666 ; The cmd field defines the exact break command to use. An
  # example is 'bi my_location'.
  cmd=S                         \\ Break command to use
  # 518 ; 
  description=S                 \\ Description shown in selection list
}
# 652 ; The Runtime_Control block contains settings to control the behavior
# at runtime. This includes arguments to the application, semihosting,
# vector catching, etc. The specific items supported will depend on the
# processor and vehicle in use.
{.Runtime_Control               \\ Controls for runtime use
  # 413 ; The command line is used to define a command line for the application
  # when started. It is important to consult the vehicle and language
  # runtime to see if the command line will be used and what the parsing
  # rules are (what separates tokens and what is allowed in the character
  # set).
  Command_line=S                \\ Application command line (when supported)
  # 708 ; Semihosting refers to services that allow that target application to
  # access the host computer through the connection. This is intrusive
  # and may stop the application for extended periods of time. The field
  # here allows you to leave the semi-hosting state alone, have it
  # auto-detected (when possible), or force it On or Off. You need to
  # check for your processor and compiler/assembler to see if supported.
  semihosting=K(default,auto,on,off)0 \\ If semi-hosting allowed (when supported)
  # 498 ; Top_memory is used to allow the ARM semi-hosting mechanism to
  # return the top of stack and base of heap. If not defined
  # here or in the board-file, the default for each tool is 
  # used (different among Angel, MultiICE, ARMulator). If 
  # defined here, it will be set into the connection to force this 
  # address base when possible (see vehicle properties). 
  ARM_top_memory=V              \\ Set top of memory for ARM stack/heap use.
  # 409 ; Vector_catching is used to catch possible program errors
  # by setting breakpoints on (or otherwise trapping) the 
  # vectors. The default is to catch error-type vectors but
  # leave external and software interrupts alone. Note that 
  # for ARM, SWI will be caught separately by semi-hosting if 
  # enabled. To use this feature, the vectors may need to be 
  # writable (depending on processor and vehicle). Also note
  # that some vehicles/processors do not support this concept.
  # The auto setting means that the vectors will be set only
  # if the program does not write them in on load (not available
  # on all processors).
  vector_catch=K(default,auto,on,off)0 \\ If vector catching allowed (when supported)
  # 578 ; If vector_catch is On, the fields within this block allow
  # individual control over each vector. Not all vectors apply to all
  # processors. 
  {.Vectors                     \\ defines state of individual vectors for catching
    # 707 ; 
    Reset=B1                    \\ True if should catch Reset vector
    # 631 ; 
    Undefined=B1                \\ True if should catch Undefined/Illegal Instructions
    # 539 ; 
    SWI=B0                      \\ True if should catch Software Interrupts
    # 706 ; 
    P_Abort=B1                  \\ True if should catch Prefetch type Aborts
    # 606 ; 
    D_Abort=B1                  \\ True if should catch Data/Bus Aborts
    # 577 ; 
    Address=B1                  \\ True if should catch Address Exceptions
    # 576 ; 
    External=B0                 \\ True if should catch normal interrupts
    # 466 ; 
    Fast_external=B0            \\ True if should catch fast interrupts
    # 605 ; 
    Error=B1                    \\ True if should catch Errors
  }
  # 390 ; Vector_base allows specifying where the vectors will be located
  # when the processor allows moving them.
  vector_base=V                 \\ Position of vectors when moved
}