• 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. Functional Verification
  3. mixed language simulation

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 65
  • Views 14534
  • 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

mixed language simulation

josephbell
josephbell over 15 years ago

Hello all

 i am doing verification of a blocks that has vhdl modules instantiated in the verilog top module. the vhdl modules are using the xilinx libraries like unisims / corelib. i have compiled the libraries and vhdl modules are picking up those libraries. i am having problem while elaborating the design. i am using following commands for simulating the design: ncvhdl -v93 -f filelist_vhdl 

ncvlog -f filelist_ver 

ncelab -access +rw +mixedlang tb_module -v93 

while elaborating i am getting following error:  ncelab: *E,CFIGTC saying the VHDL generic bit_vector type is not compatible with verilog. and the bit_vector is declared in the xilinx library primitives. 

i cannot change the type bit_vector to std_logic_vector  as these are standard libraries and ihave no permission to modify them.

can anybody help me out. 

thanks

vishal 

 

  • Cancel
Parents
  • jenkinrob
    jenkinrob over 15 years ago
    We worked with somebody else now who noticed the exact same issue while you. Within the end it turned out to be he had been utilizing a Verilog style, using the VHDL unisim library.Afterhe changed his cds.lib in order to indicate unisim_ver rather than unisim, it proved helpful Ok.

    Because you state your style is VHDL, possibly you could check your compact disks.lib to determine for those who have unisim_ver within currently; if so, swap it to unisim.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • jenkinrob
    jenkinrob over 15 years ago
    We worked with somebody else now who noticed the exact same issue while you. Within the end it turned out to be he had been utilizing a Verilog style, using the VHDL unisim library.Afterhe changed his cds.lib in order to indicate unisim_ver rather than unisim, it proved helpful Ok.

    Because you state your style is VHDL, possibly you could check your compact disks.lib to determine for those who have unisim_ver within currently; if so, swap it to unisim.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

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