Interface Requirements and Relevant Documentation

Requirement List

  • Should NOT instantiate hardware: - Question - do people agree with this premise? -- BAH - 2012-11-13
    • VHDL+ provides instantiated interfases:
      • defines an Interface 'between' any number of end types (including 1).
      • Interfaces connect via an 'interface port' list, additional in 'component' and 'entity' declarations (leads on to 'interface map' and 'interface signal' extras).
    • SystemVerilog provides instantiated interfaces:
  • An Interface should reference a composite (sub)type:
    • an interface is a bundle of signals.
    • the purpose of the interface is to group these signals together in order to improve connectivity and code comprehension.
  • An Interface should provide directional port mode definability for each element of said composite type (records and arrays):
    • an interface needs to be able to define various I/O modes, at its simplest master and slave.
    • an interface should not necessarily be limited to just two I/O mode types.
    • an interface should be able to connect to just one port, e.g. to provide protocol validation/stimulation
  • An Interface should provide support for interface protocol testing
  • An Interface should not be too complex in syntax, in order to provide simple interfaces, e.g. a record of Std_Logic type elements (reset, clock)

Relevant Email threads:

Relevant Proposals:

Relevant Documents:

Edit | Attach | Print version | History: r14 | r12 < r11 < r10 < r9 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r1 - 2016-01-14 - 06:51:27 - TWikiGuest
 
Copyright © 2008-2025 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback