| Add Proposal | Edit Analysis | Edit Class, Environment, or Release |
| Number | 396
|
| Category | errata
|
| Synopsis | Errata on VPI configuration properties
|
| State | analyzed
|
| Class | errata-ptf
|
| Arrival-Date | Jul 17 2003
|
| Originator | Hemant Gupta <hgupta@cadence.com>
|
| Release | 2001b
|
| Environment |
|
| Description |
Hi, It seems that the LRM needs to clarify the following with respect to vpiProperties for Verilog configurations. 1. The vpiLibrary, vpiCell and vpiConfig properties have been defined for objects of type vpiModule only. As per Section 13 of the LRM, it is possible to bind an instance to a primitive cell. Hence, can these properties be applied to objects of type vpiUdp? Similarly, if configurations support binding of an array of instances, the above properties should be extended for vpiModuleArray and vpiUdpArray objects. 2. The vpiConfig can be clarified with respect to hierarchical configurations. eg. Consider the following hierarhical configuration- config bot; design lib2.bot2; endconfig config top; design rtlLib.top; instance top.bot use lib1.bot:config; endconfig Should vpiConfig property for vpiModule object "top.bot" return "top" or "bot"? It seems that vpiConfig should return "top" because instance "top.bot" is configured by the instance statement in config "top". The vpiLibrary and vpiCell properties for "top.bot" shall return "lib2" and "bot2", respectively. regards, Hemant. |
| Fix |
|
| Audit-Trail |
Analyzed by etf@boyd.com on Mon Dec 1 12:27:15 2003 On the first issue, it also seems to me that the properties should be defined on primitives of type udp. For module arrays and primitive arrays, the config file should be enhanced to support providing configurations for module and primitive arrays. Without this Verilog language enhancement, we cannot define the VPI behaviour of these properties on instance arrays. On the definitional issue of the property vpiConfig, I found that section 13.6 defines it as: vpiConfig - the library.cell name of the config controlling the binding of the module instance. Therefore, in your example, the property vpiConfig applied to the module instance top.bot should return lib1.bot (which is the library and cell name of the config applied to the module instance top.bot. Similarly the vpiConfig applied to module instance top should return <libname>.top where libname is the library which contains the configuration named top. There may not be a config controlling the binding of a module instance, in that case, the vpiConfig should return null. Francoise ' From: Shalom Bresticker <Shalom.Bresticker@motorola.com> To: Francoise Martinolle <fm@cadence.com> Cc: ptf-bugs@boyd.com, etf@boyd.com Subject: Re: errata/396: ANALYZED - Errata on VPI configuration properties Date: Tue, 02 Dec 2003 12:09:42 +0200 > For module arrays and primitive arrays, the config file should > be enhanced to support providing configurations for module and primitive arrays. > Without this Verilog language enhancement, we cannot define the VPI behaviour of these properties > on instance arrays. Perhaps you should file an ETF errata on that issue. -- Shalom Bresticker Shalom.Bresticker@motorola.com Design & Reuse Methodology Tel: +972 9 9522268 Motorola Semiconductor Israel, Ltd. Fax: +972 9 9522890 POB 2208, Herzlia 46120, ISRAEL Cell: +972 50 441478 |
| Unformatted |
|
Hosted by Boyd Technology