The Perl Toolchain Summit needs more sponsors. If your company depends on Perl, please support this very important event.
<html xmlns:v="urn:schemas-microsoft-com:vml"
xmlns:o="urn:schemas-microsoft-com:office:office"
xmlns:w="urn:schemas-microsoft-com:office:word"
xmlns="http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=Content-Type content="text/html; charset=windows-1252">
<meta name=ProgId content=Word.Document>
<meta name=Generator content="Microsoft Word 9">
<meta name=Originator content="Microsoft Word 9">
<link rel=File-List href="./vregs_spec_files/filelist.xml">
<title>Vregs Example Specification</title>

<style>

</style>

</head>

<body lang=EN-US link=blue vlink=purple>

<div class=Section1>

<div>

<h1><a name="_Toc509199472"></a><a name="_Toc503876542"><![if !supportLists]>1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<![endif]>Vregs</a></h1>

</div>

<p class=MsoNormal></p>

<p class=MsoNormal>This document shows example register layouts
that the SystemC::Vregs package understands.</p>

<p class=MsoNormal></p>

<p class=MsoNormal>Please see</p>

<p class=MsoNormal>            man
vreg</p>

<p class=MsoNormal>and</p>

<p class=MsoNormal>            man
SystemC::Vregs</p>

<p class=MsoNormal>and/or</p>

<p class=MsoNormal>            <a
href="http://www.veripool.org/vregs">http://www.veripool.org/vregs</a></p>

<p class=MsoNormal></p>

<p class=MsoNormal>for information on the program and package.</p>

<div>

<h1><![if !supportLists]>2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<![endif]>Package Attributes</h1>

</div>

<p class=RegDescHead><b>Description</b></p>

<p class=RegDescBody>A “package” header specifies an optional
global header which vregs uses to establish overall information about the
specification.  This may be put into
“hidden” text if the word processor supports it.</p>

<p class=RegDescHead><b>Package</b></p>

<p class=RegDescBody>vregs_spec</p>

<p class=RegDescHead><b>Attributes</b></p>

<p class=RegDescBody>-netorder</p>

<p class=RegDescBody></p>

<p class=RegDescBody>A header called “Attributes” specifies
special actions for the entire package.<br>
<![if !supportLineBreakNewLine]><br>
<![endif]></p>

<table border=1 cellspacing=0 cellpadding=0 width=459>
 <tr>
  <td valign=top>
  <p class=RegDescBody><b>Attribute</b></p>
  </td>
  
  <td valign=top>
  <p class=RegDescBody><b>Description</b></p>
  </td>
  
 </tr>
 <tr>
  <td valign=top>
  <p class=RegDescBody>-v2k</p>
  </td>
  
  <td valign=top>
  <p class=RegDescBody>For Verilog files, use Verilog-2001
  constructs, namely localparam instead of parameter. </p>
  </td>
  
 </tr>
 <tr>
  <td valign=top>
  <p class=RegDescBody>-netorder</p>
  </td>
  
  <td valign=top>
  <p class=RegDescBody>Store all structures in network
  order.  Have all accessor functions
  pack and unpack to host order.</p>
  </td>
  
 </tr>
</table>

<p class=RegDescBody></p>

<p class=RegDescBody></p>

<p class=MsoNormal></p>

<p class=MsoNormal></p>

<div>

<h1><![if !supportLists]>3&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<![endif]>Definitions </h1>

</div>

<h2><![if !supportLists]>3.1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <![endif]>Description</h2>

<p class=RegDescBody>A definition section starts with the word
“Defines” alone on a line.  Vregs will
create #define statements for each mnemonic/constant pair.  The name following the Defines header is
prepended to all defines, thus in the example below CMP_ will be
prepended.  If this is not desired, use
a single _ instead of the “CMP” below.</p>

<p class=RegDescBody>A header called “Attributes” before the
header specifies special actions for the enum.<br>
<![if !supportLineBreakNewLine]><br>
<![endif]></p>

<table border=1 cellspacing=0 cellpadding=0 width=459>
 <tr>
  <td valign=top>
  <p class=RegDescBody><b>Attribute</b></p>
  </td>
  
  <td valign=top>
  <p class=RegDescBody><b>Description</b></p>
  </td>
  
 </tr>
 <tr>
  <td valign=top>
  <p class=RegDescBody>-freeform</p>
  </td>
  
  <td valign=top>
  <p class=RegDescBody>Allow free-form text in the constant
  section.  Without this attribute,
  vregs will assume all constants are Verilog-format numbers.</p>
  </td>
  
 </tr>
</table>

<p class=RegDescBody>There are three columns for each
define.  Columns can be in any order.</p>

<p class=RegDescBody>The constant column is the value for the
define.  Numeric values are in Verilog
format, with the width and a h/d/b for hex, decimal and binary,
respectively.  Underscores can be used
to separate digits; they are ignored. String and other formats are not supported
yet.</p>

<p class=RegDescBody>The mnemonic column is the name of the
define, appended to the Defines prefix. 
The Mnemonic must be all upper case.</p>

<p class=RegDescBody>The definition column is a comment on what
the define is used for.  The first
sentence is added as a comment to the output files.  Italizing this first sentence is useful in highlighting this
extraction. </p>

<p class=RegDescBody>Any additional columns must have header
titles in parenthesis.  If data in that
column contains alphanumeric data, the data will be added as an attribute to
the define.  This is not used by vregs
itself, but is useful for locally written extentions.</p>

<p class=RegDescBody>If constants are being defined for a
series of values, a enumeration is probably a better way to do it.  </p>

<p class=RegDescBody></p>

<h2><![if !supportLists]>3.2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <![endif]>Example
Definitions </h2>

<p class=RegDescHead><b>Description</b></p>

<p class=RegDescBody>This table shows an example definition
table.   The information in the header
below is prepended with a underscore to all mnemonics, to prevent the global
name space of defines from causing trouble.</p>

<p class=RegDescHead><b>Defines</b></p>

<p class=RegDescBody>CMP</p>

<p class=MsoNormal></p>

<table border=1 cellspacing=0 cellpadding=0>
 <tr>
  <td valign=top>
  <p class=TableHeading>Constant<br>
  <![if !supportLineBreakNewLine]><br>
  <![endif]></p>
  </td>
  
  <td valign=top>
  <p class=TableHeading>Mnemonic</p>
  </td>
  
  <td valign=top>
  <p class=TableHeading>Definition<br>
  (header comments in parenthesis)</p>
  </td>
  
 </tr>
 <tr>
  <td valign=top>
  <p class=TableBody>4’d1</p>
  </td>
  
  <td valign=top>
  <p class=TableBody>DEFINED_ONE</p>
  </td>
  
  <td valign=top>
  <p class=TableBody><i>Definition One</i>.  Text up to the first period will be
  annotated into the output files.</p>
  </td>
  
 </tr>
 <tr>
  <td valign=top>
  <p class=TableBody>48’hfeed</p>
  </td>
  
  <td valign=top>
  <p class=TableBody>DEFINED_FOOD</p>
  </td>
  
  <td valign=top>
  <p class=TableBody><i>Definition of Food</i>.</p>
  </td>
  
 </tr>
 <tr>
  <td valign=top>
  <p class=TableBody></p>
  </td>
  
  <td valign=top>
  <p class=TableBody></p>
  </td>
  
  <td valign=top>
  <p class=TableBody></p>
  </td>
  
 </tr>
</table>

<h2><![if !supportLists]>3.3&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <![endif]>More
Definitions </h2>

<p class=RegDescHead><b>Description</b></p>

<p class=RegDescBody>This table shows an example freeform
definition table. </p>

<p class=RegDescHead><b>Defines</b></p>

<p class=RegDescBody>FREE</p>

<p class=RegDescHead><b>Attributes</b></p>

<p class=RegDescBody>-allowlc -freeform</p>

<p class=MsoNormal></p>

<table border=1 cellspacing=0 cellpadding=0>
 <tr>
  <td valign=top>
  <p class=TableHeading>Constant<br>
  <![if !supportLineBreakNewLine]><br>
  <![endif]></p>
  </td>
  
  <td valign=top>
  <p class=TableHeading>Mnemonic</p>
  </td>
  
  <td valign=top>
  <p class=TableHeading>Definition<br>
  (header comments in parenthesis)</p>
  </td>
  
 </tr>
 <tr>
  <td valign=top>
  <p class=TableBody>-1.2345</p>
  </td>
  
  <td valign=top>
  <p class=TableBody>DOUBLE</p>
  </td>
  
  <td valign=top>
  <p class=TableBody><i>Definition</i>.  Text up to the first period will be
  annotated into the output files.</p>
  </td>
  
 </tr>
 <tr>
  <td valign=top>
  <p class=TableBody>Foobar</p>
  </td>
  
  <td valign=top>
  <p class=TableBody>Stringdef</p>
  </td>
  
  <td valign=top>
  <p class=TableBody><i>Definition.</i></p>
  </td>
  
 </tr>
</table>

<div>

<h1><![if !supportLists]>4&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<![endif]>Enumerations </h1>

</div>

<h2><![if !supportLists]>4.1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <![endif]>Description</h2>

<p class=RegDescBody>A enumeration triggers off from the word
“Enum” alone on a line.  Vregs will
create a C++ enumeration for the values, and Verilog #defines for each of the
values in the enumeration.</p>

<p class=RegDescBody>A header called “Attributes” before the
header specifies special actions for the enum.<br>
<![if !supportLineBreakNewLine]><br>
<![endif]></p>

<table border=1 cellspacing=0 cellpadding=0 width=459>
 <tr>
  <td valign=top>
  <p class=RegDescBody><b>Attribute</b></p>
  </td>
  
  <td valign=top>
  <p class=RegDescBody><b>Description</b></p>
  </td>
  
 </tr>
 <tr>
  <td valign=top>
  <p class=RegDescBody>-descfunc</p>
  </td>
  
  <td valign=top>
  <p class=RegDescBody>Create a C++ function to retrieve the
  description given the enumeration value.</p>
  </td>
  
 </tr>
</table>

<p class=RegDescBody></p>

<p class=RegDescBody>There are three columns for each value in
the enumeration.  Columns can be in any
order.</p>

<p class=RegDescBody>The constant column is the value for the
mnemonic.  Values are in Verilog format,
with the width and a h/d/b for hex, decimal and binary, respectively.  Underscores can be used to separate digits;
they are ignored.</p>

<p class=RegDescBody>The mnemonic column is the name of this
enumeration value.  The Mnemonic must be
all upper case.  Underscores are acceptable,
but discouraged.</p>

<p class=RegDescBody>The definition column is a comment on what
the enumeration value is used for.  The
first sentence is added as a comment to the output files.  Italizing this first sentence is useful in
highlight ing this extraction. </p>

<p class=RegDescBody>Any additional columns must have header
titles in parenthesis.  If data in that
column contains alphanumeric data, the data will be added as an attribute to
the define.  This is not used by vregs
itself, but is useful for locally written extentions.</p>

<p class=RegDescBody>A table row may have a empty mnemonic
column if the definition contains the text “reserved”.  </p>

<h2><![if !supportLists]>4.2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <![endif]>Example
Enumeration (This header is ignored) </h2>

<p class=RegDescHead><b>Description</b></p>

<p class=RegDescBody>This table shows an example enumeration
table.  </p>

<p class=RegDescHead><b>Enum</b></p>

<p class=RegDescBody>ExEnum</p>

<p class=RegDescHead><b>Attributes</b></p>

<p class=RegDescBody>-descfunc</p>

<p class=MsoNormal></p>

<table border=1 cellspacing=0 cellpadding=0>
 <tr>
  <td valign=top>
  <p class=TableHeading>Constant<br>
  (comments)</p>
  </td>
  
  <td valign=top>
  <p class=TableHeading>Mnemonic</p>
  </td>
  
  <td valign=top>
  <p class=TableHeading>Definition<br>
  (header comments in parenthesis)</p>
  </td>
  
 </tr>
 <tr>
  <td valign=top>
  <p class=TableBody>4’b0000</p>
  </td>
  
  <td valign=top>
  <p class=TableBody></p>
  </td>
  
  <td valign=top>
  <p class=TableBody><i>Reserved</i></p>
  </td>
  
 </tr>
 <tr>
  <td valign=top>
  <p class=TableBody>4’b0001</p>
  </td>
  
  <td valign=top>
  <p class=TableBody>ONE</p>
  </td>
  
  <td valign=top>
  <p class=TableBody><i>Command One</i>.  Text up to the first period will be
  annotated into the output files.</p>
  </td>
  
 </tr>
 <tr>
  <td valign=top>
  <p class=TableBody>4’b0010</p>
  </td>
  
  <td valign=top>
  <p class=TableBody>TWO</p>
  </td>
  
  <td valign=top>
  <p class=TableBody><i>Command Two</i>.</p>
  </td>
  
 </tr>
 <tr>
  <td valign=top>
  <p class=TableBody>4’d5</p>
  </td>
  
  <td valign=top>
  <p class=TableBody>FIVE</p>
  </td>
  
  <td valign=top>
  <p class=TableBody><i>Command Five</i>.  Number in decimal.</p>
  </td>
  
 </tr>
 <tr>
  <td valign=top>
  <p class=TableBody>4’he</p>
  </td>
  
  <td valign=top>
  <p class=MsoNormal>FOURTEEN</p>
  </td>
  
  <td valign=top>
  <p class=MsoNormal><i>Command Fourteen</i>.  Number in hex.</p>
  </td>
  
 </tr>
</table>

<h2><![if !supportLists]>4.3&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <![endif]>Another
Enumeration</h2>

<p class=RegDescHead><b>Description</b></p>

<p class=RegDescBody>This table shows an enumeration  that references another enumeration.  </p>

<p class=RegDescHead><b>Enum</b></p>

<p class=RegDescBody>ExSuperEnum</p>

<p class=RegDescHead><b>Attributes</b></p>

<p class=RegDescBody>-descfunc</p>

<p class=MsoNormal></p>

<table border=1 cellspacing=0 cellpadding=0>
 <tr>
  <td valign=top>
  <p class=TableHeading>Constant<br>
  (comments)</p>
  </td>
  
  <td valign=top>
  <p class=TableHeading>Mnemonic</p>
  </td>
  
  <td valign=top>
  <p class=TableHeading>Definition<br>
  (header comments in parenthesis)</p>
  </td>
  
 </tr>
 <tr>
  <td valign=top>
  <p class=TableBody>8’h0_0</p>
  </td>
  
  <td valign=top>
  <p class=TableBody></p>
  </td>
  
  <td valign=top>
  <p class=TableBody><i>Reserved.</i></p>
  </td>
  
 </tr>
 <tr>
  <td valign=top>
  <p class=TableBody>8’h2_0</p>
  </td>
  
  <td valign=top>
  <p class=TableBody>A</p>
  </td>
  
  <td valign=top>
  <p class=TableBody><i>Sub Enum A 
  ENUM:ExEnum</i>.  References that values
  under the enumeration ExEnum should be included here, starting at 8’h2_0 upto
  8’h2_F.</p>
  </td>
  
 </tr>
 <tr>
  <td valign=top>
  <p class=TableBody>(8’h2_F)</p>
  </td>
  
  <td valign=top>
  <p class=TableBody></p>
  </td>
  
  <td valign=top>
  <p class=TableBody>(Just a comment so users know that the previous enum extends up
  through 2F.)</p>
  </td>
  
 </tr>
 <tr>
  <td valign=top>
  <p class=TableBody>8’h3_0</p>
  </td>
  
  <td valign=top>
  <p class=TableBody>B</p>
  </td>
  
  <td valign=top>
  <p class=TableBody><i>Sub Enum B 
  ENUM:ExEnum</i>.  References that values
  under the enumeration ExEnum should be included here, starting at 8’h3_0 upto
  8’h3_F.</p>
  </td>
  
 </tr>
 <tr>
  <td valign=top>
  <p class=TableBody>(8’h3_F)</p>
  </td>
  
  <td valign=top>
  <p class=TableBody></p>
  </td>
  
  <td valign=top>
  <p class=TableBody>(Just a comment so users know that the previous enum extends up
  through 3F.)</p>
  </td>
  
 </tr>
 <tr>
  <td valign=top>
  <p class=TableBody>8’hF_E</p>
  </td>
  
  <td valign=top>
  <p class=MsoNormal>PRELAST</p>
  </td>
  
  <td valign=top>
  <p class=MsoNormal><i>Simple values</i>.  Simple values are fine too.</p>
  </td>
  
 </tr>
</table>

<div>

<h1><![if !supportLists]>5&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<![endif]>Class Definitions</h1>

</div>

<h2><![if !supportLists]>5.1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <![endif]>Description</h2>

<p class=RegDescBody>Class Declarations key off the word
“Class” alone on a line.  Classes can
inherit other classes by using C++ syntax: “DerrivedClass : BaseClass”</p>

<p class=RegDescBody>A header called “Attributes” before the
header specifies special actions for the class.<br>
<![if !supportLineBreakNewLine]><br>
<![endif]></p>

<table border=1 cellspacing=0 cellpadding=0 width=459>
 <tr>
  <td valign=top>
  <p class=RegDescBody><b>Attribute</b></p>
  </td>
  
  <td valign=top>
  <p class=RegDescBody><b>Description</b></p>
  </td>
  
 </tr>
 <tr>
  <td valign=top>
  <p class=RegDescBody>-variablelen</p>
  </td>
  
  <td valign=top>
  <p class=RegDescBody>The class is of variable length, with
  data words appended to the end of the structure.  (Future)</p>
  </td>
  
 </tr>
 <tr>
  <td valign=top>
  <p class=RegDescBody>-netorder</p>
  </td>
  
  <td valign=top>
  <p class=RegDescBody>The structure longwords are in network
  order. (Big endian).</p>
  </td>
  
 </tr>
 <tr>
  <td valign=top>
  <p class=RegDescBody>-noarray</p>
  </td>
  
  <td valign=top>
  <p class=RegDescBody>For register types, declares the region
  as consisting of raw bytes, rather than a array of memory.  Thus when asking what the name of a
  address within the space is, the return will be something like “Ram+0x10”
  rather than “Ram[4]”.</p>
  </td>
  
 </tr>
 <tr>
  <td valign=top>
  <p class=RegDescBody>-stretchable</p>
  </td>
  
  <td valign=top>
  <p class=RegDescBody>Allow derrived classes to increase the
  size of the final structure, rather than just overlaying.</p>
  </td>
  
 </tr>
</table>

<p class=RegDescBody></p>

<p class=RegDescBody>There are six columns for each bitfield in
the class.  Columns can be in any order.</p>

<p class=RegDescBody>The bit column defines which bits the
field occupies.  Bit numbers are then
expressed in MSB:LSB order.  Bits can be
of any width; there is no restriction of their being less than 32.  For readability w#[] indicates the bits in
the brackets are in a given 32-bit word, 32 times the # will be added to the
bit numbers in the brackets.  Likewise
b# for 8-bit bytes, h# for 16-bit halfwords, and d# for 64-bit doublewords. For
example w3[10] is bit 10 in longword 3, equivalent to writing [106]  (3*32+10 = 106). Fields may consist of
multiple disjoint segments, separated by commas.  (w0[15:13] or w0[15,14,13] or w0[15],w0[14],w0[13] are all
equivalent.)</p>

<p class=RegDescBody>The mnemonic column is the name of this
field.  The Mnemonic must begin with
upper case, and can contain mixed case. 
Underscores are not acceptable, use mixed case instead.</p>

<p class=RegDescBody>The type is the C++ type of the
field.  If left blank, single bit fields
will be assumed to be “bool” and multiple bit fields will be unsigned
integers.  The entire column may be
deleted if the default is acceptable for all of the fields.</p>

<p class=RegDescBody>The constant column is used to specify the
given bit range always contains a certain value.  Often it will be expressed as a enumeration, such as when
specifing a command number field inside the layout of one specific command.</p>

<p class=RegDescBody>The optional product column is used to
select which product the definition applies to.  Entries in this column will add the “-Product={x}” attribute to
the bit entries.  When vregs is run with
the –if-product option, this setting if specified must match the if-product
setting.  For example a bitfield with
Product=Chipb+ will only be included in the output files when there is no
–if-product, when –if-product=Chipb, or when –if-product is anything lexically
greater than “Chipb” (because of the + appended to Chipb.)</p>

<p class=RegDescBody>The definition column is a comment on what
the field is used for.  The first
sentence is added as a comment to the output files.  Italizing this first sentence is useful in highlight ing this
extraction.</p>

<p class=RegDescBody>Any additional columns must have header
titles in parenthesis.  If data in that
column contains alphanumeric data, the data will be added as an attribute to
the define.  This is not used by vregs
itself, but is useful for locally written extentions.</p>

<p class=RegDescBody></p>

<h2><![if !supportLists]>5.2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <![endif]>Example
Base Class </h2>

<p class=RegDescHead><b>Description</b></p>

<p class=RegDescBody>This is an example base class
definition.  In this example, we’ll
define ExBase which is a generic format of a message, then we’ll define
specific messages.</p>

<p class=RegDescHead><b>Class</b></p>

<p class=RegDescBody>ExBase</p>

<p class=RegDescHead><b>Attributes</b></p>

<p class=RegDescBody>-netorder -stretchable</p>

<p class=MsoNormal></p>

<table border=1 cellspacing=0 cellpadding=0 width=579>
 <tr>
  <td valign=top>
  <p class=TableHeading>Bit</p>
  </td>
  
  <td valign=top>
  <p class=TableHeading>Mnemonic</p>
  </td>
  
  <td valign=top>
  <p class=TableHeading>Product</p>
  </td>
  
  <td valign=top>
  <p class=TableHeading>Type</p>
  </td>
  
  <td valign=top>
  <p class=TableHeading>Constant</p>
  </td>
  
  <td valign=top>
  <p class=TableHeading>Definition</p>
  </td>
  
 </tr>
 <tr>
  <td valign=top>
  <p class=TableBody>w0[31:28]</p>
  </td>
  
  <td valign=top>
  <p class=TableBody>Cmd</p>
  </td>
  
  <td valign=top>
  <p class=TableBody></p>
  </td>
  
  <td valign=top>
  <p class=TableBody>ExEnum</p>
  </td>
  
  <td valign=top>
  <p class=TableBody>&nbsp;</p>
  </td>
  
  <td valign=top>
  <p class=TableBody><i>Command Number</i>.  Encoding is in the ExMnem table.  You’ll see in later derived classes how
  this specifies which command this generic class represents.</p>
  </td>
  
 </tr>
 <tr>
  <td valign=top>
  <p class=TableBody>w0[28]</p>
  </td>
  
  <td valign=top>
  <p class=TableBody>CmdAck</p>
  </td>
  
  <td valign=top>
  <p class=TableBody></p>
  </td>
  
  <td valign=top>
  <p class=TableBody>&nbsp;</p>
  </td>
  
  <td valign=top>
  <p class=TableBody>&nbsp;</p>
  </td>
  
  <td valign=top>
  <p class=TableBody><i>Command Needs Acknowledge.</i>  <i>Overlaps Cmd.</i> This is a Boolean field, since it’s one
  bit and has no specified type.  The
  “overlaps Cmd” field turns off the normal warning that bit 28 is used
  twice.  This is done in this example
  as one bit of the command always indicates a specific piece of information
  that we want to extract.</p>
  </td>
  
 </tr>
 <tr>
  <td valign=top>
  <p class=TableBody>w0[27:24]</p>
  </td>
  
  <td valign=top>
  <p class=TableBody>FiveBits</p>
  </td>
  
  <td valign=top>
  <p class=TableBody>Chipb+</p>
  </td>
  
  <td valign=top>
  <p class=TableBody>&nbsp;</p>
  </td>
  
  <td valign=top>
  <p class=TableBody></p>
  </td>
  
  <td valign=top>
  <p class=TableBody><i>Five Bits. </i>This field will become a
  unsigned int.</p>
  </td>
  
 </tr>
 <tr>
  <td valign=top>
  <p class=TableBody>w0[15:0],<br>
  w1[31:0]</p>
  </td>
  
  <td valign=top>
  <p class=TableBody>Address</p>
  </td>
  
  <td valign=top>
  <p class=TableBody></p>
  </td>
  
  <td valign=top>
  <p class=TableBody>Address</p>
  </td>
  
  <td valign=top>
  <p class=TableBody></p>
  </td>
  
  <td valign=top>
  <p class=TableBody>Address.  This field spans two
  words to make a wide 48-bit field.</p>
  </td>
  
 </tr>
</table>

<p class=MsoNormal></p>

<br
clear=all>


<p class=MsoNormal></p>

<h2><a
name="_Toc509118594"><![if !supportLists]>5.3&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<![endif]>Example Class </a></h2>

<p class=RegDescHead><b>Description</b></p>

<p class=RegDescBody>This
shows a class which inherits the base class defined earlier. </p>

<p class=RegDescHead><b>Class</b></p>

<p class=RegDescBody>ExClassOne
: ExBase</p>

<p class=RegDescBody></p>

<table border=1 cellspacing=0 cellpadding=0 width=577>
 <tr>
  <td valign=top>
  <p class=TableHeading>Bit</p>
  </td>
  
  <td valign=top>
  <p class=TableHeading>Mnemonic</p>
  </td>
  
  <td valign=top>
  <p class=TableHeading>Type</p>
  </td>
  
  <td valign=top>
  <p class=TableHeading>Constant</p>
  </td>
  
  <td valign=top>
  <p class=TableHeading>Definition</p>
  </td>
  
 </tr>
 <tr>
  <td valign=top>
  <p class=TableBody>w0[31:28]</p>
  </td>
  
  <td valign=top>
  <p class=TableBody>Cmd</p>
  </td>
  
  <td valign=top>
  <p class=TableBody>ExEnum</p>
  </td>
  
  <td valign=top>
  <p class=TableBody>&nbsp;ONE</p>
  </td>
  
  <td valign=top>
  <p class=TableBody><i>Command Number</i>. This field is a constant, as it indicates that this is message type
  ONE. </p>
  </td>
  
 </tr>
 <tr>
  <td valign=top>
  <p class=TableBody></p>
  </td>
  
  <td valign=top>
  <p class=TableBody></p>
  </td>
  
  <td valign=top>
  <p class=TableBody></p>
  </td>
  
  <td valign=top>
  <p class=TableBody></p>
  </td>
  
  <td valign=top>
  <p class=TableBody></p>
  </td>
  
 </tr>
</table>

<h2><![if !supportLists]>5.4&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <![endif]>Another
Example Class</h2>

<p class=RegDescHead><b>Description</b></p>

<p class=RegDescBody>This
is another example class.  Note it
extends the size of the base class.</p>

<p class=RegDescHead><b>Class</b></p>

<p class=RegDescBody>ExClassTwo
: ExBase</p>

<p class=RegDescBody></p>

<table border=1 cellspacing=0 cellpadding=0 width=577>
 <tr>
  <td valign=top>
  <p class=TableHeading>Bit</p>
  </td>
  
  <td valign=top>
  <p class=TableHeading>Mnemonic</p>
  </td>
  
  <td valign=top>
  <p class=TableHeading>Type</p>
  </td>
  
  <td valign=top>
  <p class=TableHeading>Constant</p>
  </td>
  
  <td valign=top>
  <p class=TableHeading>Definition</p>
  </td>
  
 </tr>
 <tr>
  <td valign=top>
  <p class=TableBody>w0[31:28]</p>
  </td>
  
  <td valign=top>
  <p class=TableBody>Cmd</p>
  </td>
  
  <td valign=top>
  <p class=TableBody>ExEnum</p>
  </td>
  
  <td valign=top>
  <p class=TableBody>&nbsp;TWO</p>
  </td>
  
  <td valign=top>
  <p class=TableBody><i>Command Number</i>.  Indicates the second
  command.</p>
  </td>
  
 </tr>
 <tr>
  <td valign=top>
  <p class=TableBody>w0[27:24]</p>
  </td>
  
  <td valign=top>
  <p class=TableBody>FiveBits</p>
  </td>
  
  <td valign=top>
  <p class=TableBody>&nbsp;</p>
  </td>
  
  <td valign=top>
  <p class=TableBody></p>
  </td>
  
  <td valign=top>
  <p class=TableBody><i>Five Bits. </i>You can redeclare fields in the base class, but they must have the
  same name and mnemonic.</p>
  </td>
  
 </tr>
 <tr>
  <td valign=top>
  <p class=TableBody>w2[31:0]</p>
  </td>
  
  <td valign=top>
  <p class=TableBody>Payload</p>
  </td>
  
  <td valign=top>
  <p class=TableBody></p>
  </td>
  
  <td valign=top>
  <p class=TableBody></p>
  </td>
  
  <td valign=top>
  <p class=TableBody>Another field that this
  message tacks onto the end of the base class.</p>
  </td>
  
 </tr>
</table>



<h2><![if !supportLists]>5.5&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <![endif]>Expanded
Class </h2>

<p class=RegDescHead><b>Description</b></p>

<p class=RegDescBody>This
shows an example class which expands its subclasses.</p>

<p class=RegDescHead><b>Class</b></p>

<p class=RegDescBody>ExExpand</p>

<p class=MsoNormal></p>

<table border=1 cellspacing=0 cellpadding=0 width=625>
 <tr>
  <td valign=top>
  <p class=TableHeading>Bit</p>
  </td>
  
  <td valign=top>
  <p class=TableHeading>Mnemonic</p>
  </td>
  
  <td valign=top>
  <p class=TableHeading>Type</p>
  </td>
  
  <td valign=top>
  <p class=TableHeading>Constant</p>
  </td>
  
  <td valign=top>
  <p class=TableHeading>Definition</p>
  </td>
  
 </tr>
 <tr>
  <td valign=top>
  <p class=TableBody>w0[0]</p>
  </td>
  
  <td valign=top>
  <p class=TableBody>Base1</p>
  </td>
  
  <td valign=top>
  <p class=TableBody>ExBase</p>
  </td>
  
  <td valign=top>
  <p class=TableBody>&nbsp;</p>
  </td>
  
  <td valign=top>
  <p class=TableBody><i>Base 1</i>.  Expand Class.  The ‘expand class’ keyword causes the
  entire contents of ExBase to be expanded into this class.</p>
  </td>
  
 </tr>
 <tr>
  <td valign=top>
  <p class=TableBody>w2[0]</p>
  </td>
  
  <td valign=top>
  <p class=TableBody>Base2</p>
  </td>
  
  <td valign=top>
  <p class=TableBody>ExBase</p>
  </td>
  
  <td valign=top>
  <p class=TableBody>&nbsp;</p>
  </td>
  
  <td valign=top>
  <p class=TableBody><i>Base 2.</i>  Expand Class.</p>
  </td>
  
 </tr>
</table>

<p class=MsoNormal></p>

<p class=MsoNormal></p>

<div>

<h1><![if !supportLists]>6&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<![endif]>Register Declarations</h1>

</div>

<h2><![if !supportLists]>6.1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <![endif]>Definition</h2>

<p class=RegDescBody>Register declarations key off the word
“Register” alone on a line.  Registers
always start with R_, then a name beginning with a capital, and containing no
additional underscores.  They can also
have attributes like the Class Declarations.</p>

<p class=RegDescBody>Registers can also inherit other registers
using the C++ like “DerrivedReg : BaseReg” format.  This allows a field definition to be shared among many nearly
identical registers.  If all the fields
are identical to the base register, the derrived register can completely
eliminate  it’s field table.  As a extension of this, you can specify a
wildcard “Derrived* : Base*”; which will pull all Base registers into the
Derrived section; when this is done, the address specified is added to the
address specified in the Base’s declaration, and the end address is checked
against the Base’s ending address.</p>

<p class=RegDescBody>The address is specified in hex, with a
leading 0x.  The maximum width of the
address is coded into the vregs program; it defaults to 40 bits, which is
sufficient for most projects.</p>

<p class=RegDescBody>A attribute of –noimplementation specifies
the register has not been implemented, and should be ignored by Vregs.  A attribute of –noregtest specifies testing
for the register should be suppressed.</p>

<p class=RegDescBody>The table indicates the bit layout, in the
same format as a Class declaration.  The
Bit, Mnemonic, Type, and Definition columns are all described in the Class
declaration chapter.  The other columns
are as follows:</p>

<p class=RegDescBody>Reset indicates the value after chip
reset.  X or N/A indicates not reset.
FW0 or FW-(some perl expression) indicates that the value is loaded in by
firmware during initialization.</p>

<p class=RegDescBody>Access indicates read/write, read-only,
etc.  Read side effects indicate that
reading the register can change the value in the register or cause other
effects.  Write side effects indicate
that changing the value may change other registers, and is only used to tell the
register testing to skip writing this register.<br>
<![if !supportLineBreakNewLine]><br>
<![endif]></p>

<table border=1 cellspacing=0 cellpadding=0 width=446>
 <tr>
  <td valign=top>
  <p class=RegDescBody><b>Access</b></p>
  </td>
  <td valign=top>
  <p class=RegDescBody><b>Read Action</b></p>
  </td>
  <td valign=top>
  <p class=RegDescBody><b>Write Action</b></p>
  </td>
 </tr>
 <tr>
  <td valign=top>
  <p class=RegDescBody>R (or RO)</p>
  </td>
  <td valign=top>
  <p class=RegDescBody>Read Only</p>
  </td>
  <td valign=top>
  <p class=RegDescBody>Ignored</p>
  </td>
 </tr>
 <tr>
  <td valign=top>
  <p class=RegDescBody>RW</p>
  </td>
  <td valign=top>
  <p class=RegDescBody>Read</p>
  </td>
  <td valign=top>
  <p class=RegDescBody>Write</p>
  </td>
 </tr>
 <tr>
  <td valign=top>
  <p class=RegDescBody>RWS</p>
  </td>
  <td valign=top>
  <p class=RegDescBody>Read</p>
  </td>
  <td valign=top>
  <p class=RegDescBody>Write Side Effect</p>
  </td>
 </tr>
 <tr>
  <td valign=top>
  <p class=RegDescBody>RS</p>
  </td>
  <td valign=top>
  <p class=RegDescBody>Read Side Effect</p>
  </td>
  <td valign=top>
  <p class=RegDescBody>Ignored</p>
  </td>
 </tr>
 <tr>
  <td valign=top>
  <p class=RegDescBody>RSW</p>
  </td>
  <td valign=top>
  <p class=RegDescBody>Read Side Effect</p>
  </td>
  <td valign=top>
  <p class=RegDescBody>Write</p>
  </td>
 </tr>
 <tr>
  <td valign=top>
  <p class=RegDescBody>RW1C</p>
  </td>
  <td valign=top>
  <p class=RegDescBody>Read</p>
  </td>
  <td valign=top>
  <p class=RegDescBody>Write 1 to clear</p>
  </td>
 </tr>
 <tr>
  <td valign=top>
  <p class=RegDescBody>RH</p>
  </td>
  <td valign=top>
  <p class=RegDescBody>Read Hardwired (never changes)</p>
  </td>
  <td valign=top>
  <p class=RegDescBody>Ignored</p>
  </td>
 </tr>
 <tr>
  <td valign=top>
  <p class=RegDescBody>W (or RO)</p>
  </td>
  <td valign=top>
  <p class=RegDescBody>Indeterminate return</p>
  </td>
  <td valign=top>
  <p class=RegDescBody>Write</p>
  </td>
 </tr>
 <tr>
  <td valign=top>
  <p class=RegDescBody>WS</p>
  </td>
  <td valign=top>
  <p class=RegDescBody>Indeterminate return</p>
  </td>
  <td valign=top>
  <p class=RegDescBody>Write Side Effect</p>
  </td>
 </tr>
 <tr>
  <td valign=top>
  <p class=RegDescBody>L</p>
  </td>
  <td colspan=2 valign=top>
  <p class=RegDescBody>Flag on any other access indicates this
  field needs to be written after all other registers.  For example a unit “enable” needs to be
  written after all of the unit’s other registers are written.</p>
  </td>
 </tr>
</table>

<p class=RegDescBody></p>

<h2><![if !supportLists]>6.2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <![endif]>Example
Register</h2>

<p class=RegDescHead><b>Description</b></p>

<p class=RegDescBody>This is an example register declaration.</p>

<p class=RegDescHead><b>Register</b></p>

<p class=RegDescBody>R_ExReg1</p>

<p class=RegDescHead><b>Address</b></p>

<p class=RegDescBody>0x18_FFFF_0000</p>

<p class=MsoNormal></p>

<table border=1 cellspacing=0 cellpadding=0 width=579>
 <tr>
  <td valign=top>
  <p class=TableHeading>Bit</p>
  </td>
  <td valign=top>
  <p class=TableHeading>Mnemonic</p>
  </td>
  <td valign=top>
  <p class=TableHeading>Access</p>
  </td>
  <td valign=top>
  <p class=TableHeading>Reset</p>
  </td>
  <td valign=top>
  <p class=TableHeading>Type</p>
  </td>
  <td valign=top>
  <p class=TableHeading>Definition</p>
  </td>
 </tr>
 <tr>
  <td valign=top>
  <p class=TableHeading align=left>31:28</p>
  </td>
  <td valign=top>
  <p class=TableHeading align=left>LastCmd</p>
  </td>
  <td valign=top>
  <p class=TableHeading align=left>RW</p>
  </td>
  <td valign=top>
  <p class=TableHeading align=left>X</p>
  </td>
  <td valign=top>
  <p class=TableHeading align=left>ExEnum</p>
  </td>
  <td valign=top>
  <p class=TableHeading align=left><i>Enumerated field.  </i>This field has a value represented by a complex type, in this case an
  enumeration.</p>
  </td>
 </tr>
 <tr>
  <td valign=top>
  <p class=TableBody>21</p>
  </td>
  <td valign=top>
  <p class=TableBody>ReadHard</p>
  </td>
  <td valign=top>
  <p class=TableBody>RH</p>
  </td>
  <td valign=top>
  <p class=TableBody>X</p>
  </td>
  <td valign=top>
  <p class=TableBody></p>
  </td>
  <td valign=top>
  <p class=TableBody><i>Read
  Only Bits.</i>  This field is not writable and is not
  initialized during reset.</p>
  </td>
 </tr>
 <tr>
  <td valign=top>
  <p class=TableBody>20</p>
  </td>
  <td valign=top>
  <p class=TableBody>ReadOnly</p>
  </td>
  <td valign=top>
  <p class=TableBody>R</p>
  </td>
  <td valign=top>
  <p class=TableBody>1</p>
  </td>
  <td valign=top>
  <p class=TableBody></p>
  </td>
  <td valign=top>
  <p class=TableBody><i>Read
  hardwired Bits.</i>  This field is not writable
  and is hardwired; the read result will never change.</p>
  </td>
 </tr>
 <tr>
  <td valign=top>
  <p class=TableBody>3:0</p>
  </td>
  <td valign=top>
  <p class=TableBody>LowBits</p>
  </td>
  <td valign=top>
  <p class=TableBody>RW</p>
  </td>
  <td valign=top>
  <p class=TableBody>0</p>
  </td>
  <td valign=top>
  <p class=TableBody></p>
  </td>
  <td valign=top>
  <p class=TableBody><i>Random
  Low Bits</i>.  This field takes the whole register.  As with Enums and everywhere else, only
  the first sentence is used to comment the output code.</p>
  </td>
 </tr>
</table>

<p class=MsoNormal></p>

<h2><![if !supportLists]>6.3&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<![endif]>Another Register, Ranged</h2>

<p class=RegDescHead><b>Description</b></p>

<p class=RegDescBody>This is another register, but it consists
of 8 identical arrayed registers.  The
special optional comment (Add 0x10 per entry) indicates that each entry is 16
bytes apart, rather than the default dense packing of 4 bytes.</p>

<p class=RegDescHead><b>Register</b></p>

<p class=RegDescBody>R_ExRegTwo[7:0]</p>

<p class=RegDescHead><b>Address</b></p>

<p class=RegDescBody>0x18_FFFF_1000 – 0x18_FFFF_1070 (Add 0x10
per entry)</p>

<p class=MsoNormal></p>

<table border=1 cellspacing=0 cellpadding=0 width=579>
 <tr>
  <td valign=top>
  <p class=TableHeading>Bit</p>
  </td>
  <td valign=top>
  <p class=TableHeading>Mnemonic</p>
  </td>
  <td valign=top>
  <p class=TableHeading>Access</p>
  </td>
  <td valign=top>
  <p class=TableHeading>Reset</p>
  </td>
  <td valign=top>
  <p class=TableHeading>Type</p>
  </td>
  <td valign=top>
  <p class=TableHeading>Definition</p>
  </td>
 </tr>
 <tr>
  <td valign=top>
  <p class=TableBody>31:0</p>
  </td>
  <td valign=top>
  <p class=TableBody>WideField</p>
  </td>
  <td valign=top>
  <p class=TableBody>RW</p>
  </td>
  <td valign=top>
  <p class=TableBody>0</p>
  </td>
  <td valign=top>
  <p class=TableBody></p>
  </td>
  <td valign=top>
  <p class=TableBody><i>Wide
  Field</i>.  This field takes the whole register.</p>
  </td>
 </tr>
</table>

<p class=MsoNormal></p>

<p class=MsoNormal></p>

<h2><![if !supportLists]>6.4&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <![endif]>Another
Register, 64 bits</h2>

<p class=RegDescHead><b>Description</b></p>

<p class=RegDescBody>This is another register, but it consists
of a 64 bit wide register.  The special
optional comment (Add 0x8 per entry) indicates that each entry is 8 bytes
apart, rather than the default dense packing of 4 bytes.</p>

<p class=RegDescHead><b>Register</b></p>

<p class=RegDescBody>R_ExRegQuad[7:0]</p>

<p class=RegDescHead><b>Address</b></p>

<p class=RegDescBody>0x18_FFFF_2000 – 0x18_FFFF_2038 (Add 0x8
per entry)</p>

<p class=MsoNormal></p>

<table border=1 cellspacing=0 cellpadding=0 width=579>
 <tr>
  <td valign=top>
  <p class=TableHeading>Bit</p>
  </td>
  <td valign=top>
  <p class=TableHeading>Mnemonic</p>
  </td>
  <td valign=top>
  <p class=TableHeading>Access</p>
  </td>
  <td valign=top>
  <p class=TableHeading>Reset</p>
  </td>
  <td valign=top>
  <p class=TableHeading>Type</p>
  </td>
  <td valign=top>
  <p class=TableHeading>Definition</p>
  </td>
 </tr>
 <tr>
  <td valign=top>
  <p class=TableBody>31:0</p>
  </td>
  <td valign=top>
  <p class=TableBody>WideField</p>
  </td>
  <td valign=top>
  <p class=TableBody>RW</p>
  </td>
  <td valign=top>
  <p class=TableBody>0</p>
  </td>
  <td valign=top>
  <p class=TableBody></p>
  </td>
  <td valign=top>
  <p class=TableBody><i>Wide
  Field</i>.  This field takes the whole register.</p>
  </td>
 </tr>
 <tr>
  <td valign=top>
  <p class=TableBody>63</p>
  </td>
  <td valign=top>
  <p class=TableBody>Bit63</p>
  </td>
  <td valign=top>
  <p class=TableBody>RW</p>
  </td>
  <td valign=top>
  <p class=TableBody>0</p>
  </td>
  <td valign=top>
  <p class=TableBody></p>
  </td>
  <td valign=top>
  <p class=TableBody><i>Bit
  63.</i></p>
  </td>
 </tr>
 <tr>
  <td valign=top>
  <p class=TableBody>w1[30]</p>
  </td>
  <td valign=top>
  <p class=TableBody>Bit62</p>
  </td>
  <td valign=top>
  <p class=TableBody>RW</p>
  </td>
  <td valign=top>
  <p class=TableBody>0</p>
  </td>
  <td valign=top>
  <p class=TableBody></p>
  </td>
  <td valign=top>
  <p class=TableBody><i>Bit
  62.  </i>Using alternate syntax to
  indicate bit 30 in word number 1.<i></i></p>
  </td>
 </tr>
</table>

<p class=MsoNormal></p>

<p class=MsoNormal></p>

</div>

</body>

</html>