On Tue, 4 Sep 2001, Hamish Moffatt wrote:
> On Sat, Sep 01, 2001 at 09:23:34PM -0700, Stephen Williams wrote:
> > [EMAIL PROTECTED] said:
> > > I believe what you want are the Xilinx "Unified Libraries".
> >
> > I actually have a printed copy, and that is what I use when
> > generating XNF. Unfortunately, it is not clear to me how to
> > reference the unified library via EDIF (the external library
> > name, for example).
>
> I think the library guide is pretty much it. It lists all the
> primitives and the macros in the library. However, I think
> the back end tools (NGDBUILD/MAP/PAR etc) expect macros
> to have been expanded by the netlist writer, so you can't
> use those in your EDIF. You can use all the primitives though.
Actually, in case of Atmel device, it is possible to reference macros in
an edif file. The way it works is that you declare a certain cell in the
library and skip it's contents part. The edif reader magically knows what
the cell expands to. Needless to say this is very vendor dependent.
Stephen, can I try to persuade you to invent a way to attach EDIF
descriptions to modules (ala attribute usage for signals) ? This way the
user can simply include a vendor specific library and, if they want, can
also modify cell edif descriptions if they want.
Furthermore, I suspect that at the moment you are after LPM devices. With
the scheme above you can (for example) simply reference IVERILOG_ADD in
your edif netlister output and the description of IVERILOG_ADD would be
included with vendor (and device) specific library.
best
Vladimir Dergachev
>
> The libraries guide should document the properties -- IOB,
> INIT, etc.
>
>
>
> regards
> Hamish
> --
> Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
>
