Академический Документы
Профессиональный Документы
Культура Документы
Kactus2
Woke
Tutorials
Examples
About
Contact
Kactus2 fits to your product design flow. There's no need to change specification, synthesis, verification or
other critical tools. You can start gradually using the unifying metadata and Kactus2 as the user interface
to it. Productivity is improved as re-use becomes real.
You don't lock-in with Kactus2, because you own data and can freely access it at any time. Kactus2 is
based on IEEE1685/IP-XACT metadata with our free and open extensions. Kactus2 comes with a core for
managing components and designs plus plugins for automation. Our ambition is the best usability among
EDA/ESL tools.
To whom
Small and mid-size vendor and integrator companies that now have only the traditional toolset: office
tools (doc, xls, ppt) for specification/documentation and Verilog/VHDL, C/C++, FPGA tools for designs.
Kactus2 helps taking a step to metadata based design that keeps products much better manageable
while still using also the familiar tools.
Universities and research laboratories that implement new content (IP bocks, SW modules). Kactus2
helps packetizing the content in a standard way for (re)using it much easier by others, specifically when
the original contributor leave after e.g. a PhD project.
Bigger companies and tool providers that already have modern design tool flows and resources for
developing higher abstraction methods. Kactus2 offers a great R&D environment for trying new
methodology ideas and user interface innovations. Kactus2 leads the way among metadata-based tools.
Quickly draft block diagram blueprints for product boards (PCB), chips, system-on-chip, IPs and get
them stored in IP-XACT format
Draft communication channel abstraction endpoint design for all processors and fixed IPs in a
product
For new IP-blocks generate code templates (VHDL entities, headers) from IP-XACT components
defined in Kactus2
Packetize IP for reuse and exchange
Create "electronic datasheets" of your existing IPs for library as templates and blocks ready for
integration
Import, export and integrity check IP libraries from any standard compatible IP vendor
Analyze file dependencies between IP's source files and easily see changes in any file
Create MP-SoC products
What is Metadata?
Kactus2 follows the general platform based design paradigm with extensive use of metadata. Product is
created by assembling application components on platforms, and all are packetized to a library with
metadata. Metadata makes sure unambiguous interoperability between partners and tools and makes
design automation possible.
Metadata for a component is formal, vendor and technology independent description of the component.
It includes references to source files and other related information. Components are in practice HW blocks
and SW codes in different abstraction and granularity levels.
Metadata for a design is a formal structural description. It includes references to component metadata,
tools, configurations and other design related information.
In brief, metadata is like an electronic datasheet + product + project documentation.Read more on our
white paper or presentation on MeCoES'12 workshop.
Metadata benefits
Metadata-based design flow makes selling, buying, integrating and reusing IPs and complete
designs much less error prone
Saves time and effort when managing several configurations and variants of the products
Machine readable documentation also for the tools, languages and environments for backup and
maintenance
Increased design automation and standard compatibility
Embedded system products consists of HW and SW design data and plenty of process and other auxiliary
information. We consider the product as a hierarchy of its physical realization. Environments refer to the
context in which products are specified, verified, tested and finally used. Each product level include
associated information like documentation, source codes, tools, configurations and production data.
Our product hierarchy model consists of boards containing chips that are fixed-function or they can
accommodate a system-on-chip (SoC), which are built up from IP-blocks. All levels include both HW and
SW related information.
The scope of IEEE1685/IP-XACT is on the IP and SoC levels, but we apply the standard also to other
levels, aiming at product level information management (PDM, product data management).