# SystemVerilog Interface Syntesis

**URL:** <https://verificationacademy.com/forums/t/systemverilog-interface-syntesis/36823>\
**Category:** SystemVerilog\
**Tags:** HDL-designer-systemverilog-interface, synthesis, SystemVerilog, Interfaces\
**Created:** [November 19, 2019, 10:10pm UTC](https://verificationacademy.com/forums/t/systemverilog-interface-syntesis/36823 "2019-11-19T22:10:29Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Mark\_Curry](https://verificationacademy.com/forums/letter_avatar_proxy/v4/letter/m/c57346/32.png) [@Mark\_Curry](https://verificationacademy.com/forums/u/Mark_Curry)\
**Post date:** [November 19, 2019, 11:20pm UTC](https://verificationacademy.com/forums/t/systemverilog-interface-syntesis/36823/2 "2019-11-19T23:20:44Z")

</div>

_In reply to [ghertz](https://verificationacademy.com/forums/t/systemverilog-interface-syntesis/36823):_

Strictly from a language point of view - No you cannot synthesize a top level design with a SystemVerilog Interface. As the error message in the reference link shows, an interface port of a module must be connected to an actual interface (there’s elaboration time checking happening between the port type and the connected interface).

An interface can only be instantiated at the calling module (or above). Since the synthesizer is only looking at module “top” there’s nothing above it to actually instantiate an interface.

From a practical point of view as well, the answer is NO as well. Most post-synthesis implementation tools, in practice, break down with anything other than than the most basic of port types at the top-level (think single-dimension vectors at most).

We use SystemVerilog Interfaces (and arrays thereof) heavily in our designs. But not at the top level.

Regards,

Mark

---

_[View the full topic](https://verificationacademy.com/forums/t/systemverilog-interface-syntesis/36823)._
