Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.
You said it edif is just a very small language that allows to describe electronic netlists .this means that it allows to describe synthaxically the conections of electronic components (BUT NOT THEIR BEHAVIOR).This type of format is really necessary because .All cads implement their own graphical format .So in order to interface Schematic cads to other tools A more general type of format is necessary.Edif is not the only one but the more widely accepted . There is EDIF 2 EDIF3 and even EDIF4 ..But the most widely spread is still EDIF2 ..
This is the thirdparty standard file format for netlist. For example, if you use leonardo spectrum to perform synthesis, once completed, you need to import the .edf file into quartus to perform place and route and get .sof file.
The Electronic Design Interchange Format (EDIF) is a format used to exchange design data between different CAD systems, and between CAD systems and Printed Circuit fabrication and assembly . The `Electronic' refers to the type of data, i.e. design data for electronic systems and not the mechanism of interchange. Of course, an EDIF file is machine readable and may be interchanged electronically. Such CAD systems are often referred to as Electronic CAD (ECAD) systems or Electronic Design Automation (EDA) Systems.
The EDIF format is designed to be written and read by computer programs that are constituent parts of EDA systems or tools, or by software that is part of front end manufacturing systems (CAM stations) . Its syntax has been designed for easy machine parsing and is similar to LISP. By their very nature, the EDIF standards are behind the scenes for most EDA users. The development of EDIF has involved input from EDA vendors, designers and large user companies . Software to check conformance to the standard is available to help ensure that EDIF exchanges are as effective as possible.
The format was standardized initially by the Electronic Industries Alliance (the EIA), a US based industry association, responsible for a number of electronics related standards. (Some familiar ones may be JEDEC and RS-232).
Both EDIF Version 3 0 0 and EDIF Version 4 0 0 are ANSI standards and also IEC standards. EDIF Version 3 0 0 is formally IEC 61690-1; EDIF Version 4 0 0 is formally IEC 61690-2.
Well main Idea was to do advanture...writing EDIF description by hand and than by GUI app in java that
draw Schematic and can work with spice.
where I can find IEC EDIF LRM(aka standard doc) *free of cost* (on EDABoard?). Also a book in "plain english", as standard docs are mostly written in greek!
One thing I donot understand, if lang. doesnot describe the behavior,only connections b/w devices...then what about modules (like standard TTL MSI for example)?
what about the module description...how they exchange module descrition--"here is that NAND gate" and this (I think) require some behavioral description?
what is the relation or difference between edif file and spice netlist(or cdl file ect.)
I think all these netlist files only describe the connections of modules(or transistors) in your design,but it need some other files to descripe your modules .My question is how can the modules exchange between the CADs,if it can not, does the netlist file any use?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
