Forum Discussion
Failed to create SystemVerilog interface in _hw.tcl in Platform Designer
- 3 years ago
Hi Chunxi,
Done testing. Yes, the top-level port feature that you want can be done by Pro version hw.tcl SystemVerilog interface command.
I had checked internally that this feature only be implemented starting from Pro version 17.1. That's why you'll see package require -exact qsys 17.1 in both the Standard and Pro example given https://www.intel.com/content/www/us/en/docs/programmable/683364/18-1/declaring-systemverilog-interfaces-in-hw-tcl.html and https://www.intel.com/content/www/us/en/docs/programmable/683609/22-4/declaring-systemverilog-interfaces-in-hw-tcl.html
If you check the hw.tcl generated by latest Standard version 22.1.2, you'll see it still use this package require -exact qsys 16.1. Means that Standard version not yet supports this feature and document mistake (I'll report this to internal team). Probably this feature will be supported in future Standard release.
So for now, have to stick with traditional method (SV interface used inside the RTL) for Standard version.
Thanks,
Best Regards,
Sheng
Hi Chunxi ,
In component editor, add the <systemverilog_interface>.sv and <systemverilog_top_module>.sv. Then, set attribute of <systemverilog_top_module>.sv to Top-level File and click Analyze Synthesis File will do. Systemverilog interface module will be linked to systemverilog top module automatically. Attached file for your reference.
Thanks,
Best Regards,
Sheng
Hi Sheng,
I see your attachement. It is an example of SV interface used inside the RTL but not as a top-level port.
Instead of this:
Is it possible for Platform Designer to extract signals and corresponds them to IP component interface from below code?
Or is the "add sv interface" command in Prime pro edition unable to do this either?
Thanks,
Chunxi