HI Troy,

We have a pretty universal default of boolean attributes to false. In this case the doc was done to minimize the amount of XML attributes in practice. These two goals conflict here. In order to minimize unintended bloat in designs, we'll change the doc to say the default is false, which will indeed still require that the attributes are required to "enable" all the desired property behavior. Otherwise the "easy way" of specifying properties would produce the most overhead, which we don't want.

Thanks,

Jim





On 3/8/12 8:50 PM, Ziersch, Troy (Contractor) wrote:

*UNCLASSIFIED*

Hi Jim,
A non-critical bug report for you. Hopefully I'm not reporting something that's recently been fixed. I tried making a component spec which only sets Name and Type in the Property elements as docs say Readable and Writable default to true.
<Properties>
<Property Name="Ctrl"  Type="ULong"  />
</Properties>
Which results in a WCI interface with no data port in defs.vh file:
  // The WCI interface named "ctl", with "fmc150" acting as OCP slave:
  // WIP attributes for this WCI interface are:
  //   Clock: this interface has its own clock, named "wci_Clk"
  //   SizeOfConfigSpace: 4 (0x4)
  //   WritableConfigProperties: false
  //   ReadableConfigProperties: false
  //   Sub32BitConfigProperties: false
  //   ControlOperations (in addition to the required "start"):
  //   ResetWhileSuspended: false
  wci_Clk,                // input
  wci_MAddr,              // input  [  4:0]
  wci_MAddrSpace,         // input  [  0:0]
  wci_MCmd,               // input  [  2:0]
  wci_MFlag,              // input  [  1:0]
  wci_MReset_n,           // input
  wci_SFlag,              // output [  1:0]
  wci_SResp,              // output [  1:0]
  wci_SThreadBusy,        // output [  0:0]
And to double check its not anything else in my xml, only changing the following:
<Properties>
<Property Name="Ctrl" Type="ULong" Readable="true" Writable="true"/>
</Properties>
Gives an WCI with a data port:
 // The WCI interface named "ctl", with "fmc150" acting as OCP slave:
  // WIP attributes for this WCI interface are:
  //   Clock: this interface has its own clock, named "wci_Clk"
  //   SizeOfConfigSpace: 4 (0x4)
  //   WritableConfigProperties: true
  //   ReadableConfigProperties: true
  //   Sub32BitConfigProperties: false
  //   ControlOperations (in addition to the required "start"):
  //   ResetWhileSuspended: false
  wci_Clk,                // input
  wci_MAddr,              // input  [  4:0]
  wci_MAddrSpace,         // input  [  0:0]
  wci_MCmd,               // input  [  2:0]
  wci_MData,              // input  [ 31:0]
  wci_MFlag,              // input  [  1:0]
  wci_MReset_n,           // input
  wci_SData,              // output [ 31:0]
  wci_SFlag,              // output [  1:0]
  wci_SResp,              // output [  1:0]
  wci_SThreadBusy,        // output [  0:0]
Cheers,
Troy

*IMPORTANT*: This email remains the property of the Department of Defence and is subject to the jurisdiction of section 70 of the Crimes Act 1914. If you have received this email in error, you are requested to contact the sender and delete the email.



_______________________________________________
opencpi_dev mailing list
[email protected]
http://lists.opencpi.org/listinfo.cgi/opencpi_dev-opencpi.org

_______________________________________________
opencpi_dev mailing list
[email protected]
http://lists.opencpi.org/listinfo.cgi/opencpi_dev-opencpi.org

Reply via email to