Features which are currently supported include:

  • Design entry support
    • Syntax Highlighting
    • Auto-Completion
    • Outlines
  • Design navigation
    • Instantiation graph (on fully elaborated model)
    • Open design unit through instantiation graph
    • Open design unit by hierarchical path
    • Open signal declaration by hierarchical path
  • Simulation
    • Waveform Viewer
    • Source back-annotation of simulation values
    • Waveform file import
      • VCD
    • Built-in reference simulator (not yet complete)
  • Design Analysis
    • Reference Search
      • for instatiated modules
      • for signals across hierarchy levels in the design
    • Declaration Search
    • File caching to mitigate latencies
    • Many features which the eclipse framework provides

The designer community expressed many feature requests in the analysis and design integration area which can be implemented as extensions on the existing codebase. The analysis requests push the requirement for a scripting interface such that a design team can choose from a set of analysis scripts or write their own.

Design principles for zamiaCAD are:

  • Non-invasive: do not enforce that all members of a team have to use zamiaCAD, if one member uses zamiaCAD
    • The only data format is VHDL
    • Works on pre-existing projects with minimal configuration effort
    • Suitable for incremental adoption
  • Scalable: caches and persistent data structures allow processing of very large designs
  • Robust: JUnit tests exists for many parts of the Java framework

Currently zamiaCAD is under heavy development and we have very few early adopters. It has no problems handling processor chips or ASIC chips (even when part of the units contain VHDL netlists).

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer