• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Digital Implementation
  3. Instance a vhdl module inside a verilog file

Stats

  • Locked Locked
  • Replies 0
  • Subscribers 91
  • Views 13718
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Instance a vhdl module inside a verilog file

jsaenznoval
jsaenznoval over 10 years ago

Hi everyone,

I want to instance a vhdl module(file) inside a verilog file. I have to do it because my functional view is a vhdl file and their digital test structure was developed in Verilog.

I have the following code:

`include "mux.vhd"
module pulse_controller_dft (

//pin definitions

)

//input definitions

mux   mux7(

.d0 (d0),

.d1 (d1),

.s(s),

.y(y)

);   // vhdl module to instance

// other modules to instance

endmodule

Inside the vhdl file, the name of entity was declared with the same filename of the vhdl.


My idea is synthesize both using an unificated verilog file. However executing a parsing check with ncverilog the following error appears:

pulse_controller_syncreset Ipc(.clk(clk),.rst_n(rst_n),.cmd_disable_n_i(cmd_disable_n_i),.addr_i(addr_i[1:0]),.cmd_enable_n_i(cmd_enable_n_i),.sp_n_i(sp_n_i),.ocp_i(ocp_i),.uvp_i(uvp_i),.otp_i(otp_i),.ohd_i(ohd_i[3:0]),.cmd_o(cmd_o[3:0]),.pulse_o(pulse_o),.double_o(double_o),.false_o(false_o),.fault_o(fault_o),.cmd_disable_o(cmd_disable_o));    
                                 |
ncelab: *E,CUVMUR (../jorge/smdh/rh_drv/frontend/pulse_controller_syncreset/pulse_controller_syncreset_dft.v,80|30): instance 'pulse_controller_dft.Ipc' of design unit 'pulse_controller_syncreset' is unresolved in 'worklib.pulse_controller_dft:v'.
ncverilog: *E,ELBERR: Error during elaboration (status 1), exiting.

Any suggestions?

Thanks

  • Cancel

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information