!------------------------------------------------------------------------------ ! This file holds ranges of registers to be added to a register test coverage. ! Comments start with an exclamation mark ("!") anywhere on a line. ! See end of file for more syntax information. !------------------------------------------------------------------------------ ! Revision: 2-Feb-2001 ! This file is a template ! and list of the syntax rules for Register Test Range Definition Files CBus_MBA: 200 CBus_CA: 33 CBus_FA: 0 CBus_MBA: 169 CBus_CA: 33 CBus_FA: 16 To_CBus_FA: 27 CBus_FA: 32 To_CBus_FA: 43 CBus_FA: 48 To_CBus_FA: 59 CBus_FA: 64 To_CBus_FA: 75 CBus_CA: 35 CBus_FA: 16 To_CBus_FA: 27 Call_File: \users\default\Another.Rnd Call_File: \users\default\Another_one.Rnd !------------------------------------------------------------------------------ ! 2-Feb-2001 ! * Recommended file extension is ".CRT" (but not required). ! ! Syntax rules: ! ! - Blank lines are ignored. ! ! - Comments start after an exclamation mark ("!") anywhere on a line. ! ! * Recognized Keywords are (with colon required) ! CBus_MBA: (Mother Board Address; range 1-255) ! CBus_CA: (Card Address; range 1-63) ! CBus_FA: (Function Address; range 1-255) ! To_CBus_FA: (Optional upper Function Address in a range) ! Call_File: (Recursive call to another file) ! MilliSecond_Sleep: (Suspend execution of the command file) ! ! - Keywords are NOT case-sensitive. ! ! - Each Keyword must be followed by one and only one positive integer Value ! (with the exception of the Called_File Keyword). ! ! - One or more Keyword/Value pair may appear on a same line. ! ! - a Keyword and its matching Value may be separated by any number of spaces, ! and/or Tabs, but must appear on the same line. ! ! - Successive Keyword/Value pairs may be separated by any number of spaces, ! Tabs and/or Carriage_Returns (blank lines), or comments. ! ! * Register(s) will be added to the Test only when a "CBus_FA" or ! a "To_CBus_FA" Keyword is encountered. ! ! - All other Register Address Keywords must have been specified before a ! "CBus_FA" Keyword may be specified. ! ! * A "CBus_FA" Keyword must have been specified before a ! "To_CBus_FA" may be specified. ! ! * The "CBus_FA" and "To_CBus_FA" Values specify a Range of ! consecutive register addresses to add to the test coverage. ! ! * Each Register is checked for previous entry before it is added ! to the test coverage. This prevents duplicate entries. ! ! * Keyword/Values specified for a previous Register Range are still active ! for subsequent Register Selection until they are explicitely overwritten. ! Exception: A new "CBus_FA" Keyword must be specified after ! a "To_CBus_FA" Keyword has been specified before another ! "To_CBus_FA" Keyword may be specified. ! ! - The "MilliSecond_Sleep:" Keyword causes the execution of the command file ! to be suspended for the number of milliseconds specified in the associated ! value (integer values only). ! ! - The "Call_File" Keyword causes a recursive call to read the specified file. ! ! - Full local Keyword/Value context present before the "Call_File" Keyword ! is still valid after. i.e. Context changes made in the Called file are ! NOT propagated back to the Calling file. ! ! - The syntax rules within a called file are the same as described here. ! The local Keyword/Value context present before the Call_File Keyword ! is imported into the Called File. i.e. You can define some Keyword Values ! in the Calling File which will be valid inside the Called File. !------------------------------------------------------------------------------ ! ! * Mixed use of entering Register Ranges both manually through ! the Dialog Box and through a single (or multiple) Register Test Files: ! ! When additional registers are specified before or after executing ! a Register Range Test File, all corresponding registers will be ! added to the test coverage. Several Files can also be loaded one ! after the other and the sum of all the registers in these files ! will be included in the test coverage. ! ! As soon as a file parsing error or a register specification error ! is encountered during the execution of a Register Test File ! ALL previous entries are cleared and ALL the registers must be ! entered again. ! !------------------------------------------------------------------------------ ! - Symbol usage in command files: ! ! Symbols may be defined and used in command files. ! A symbol name must start with a dollar sign "$". ! ! A symbol is defined by giving it a numeric value. ! A symbol is defined using a Keyword/Value syntax where the Keyword is ! the symbol's name, starting with its own dollar sign but with an additional ! equal character appended to the end of the symbol name, while the value ! is the desired symbol value. ! e.g. To define a symbol named "$Slot_AONM" and give it a value "5" ! enter the following: ! $Slot_AONM= 5 ! The equal sign "=" is required and must appear directly after the last ! character of the symbol name, with no space or tab in-between. ! Any number of spaces, or tabs may appear between the symbol definition and ! its value, but the symbol and its value must appear on the same line. ! Previously defined symbols can be re-defined to change their value. ! Previously defined symbols cannot be un-defined. ! ! A symbol may be used anywhere a value is required, i.e. in any Keyword/Value ! pair and the symbol value will be substituted. e.g. ! CBus_MBA: $Slot_AONM ! A symbol must have been defined before it can be used. ! There are no predefined symbols. ! Symbols are NOT case sensitive. ! Symbol names may include any alpha numeric characters (e.g. _[(}./$< ), ! (but no space, tabs, or end of line). For clarity one should avoid ! using embedded quotation marks, equal signs, colon. ! A symbol value may be used to define another new symbol. ! ! All symbols defined before a "Call_File" Keyword are propagated into ! the Called File. i.e. You can define symbols in the Calling File ! and use those symbols (or modify them) inside the Called File. ! Symbols created or modified inside a Called File are NOT propagated ! back to the Calling file. !------------------------------------------------------------------------------