I have successfully created a schematic and compiled it without any error. I can see that Quartus II created a *.vho file in modelsim/simulation directory. However when I ask for RTL sim, it says that it can't find the HDL file even though it created it in the same Project. it is asking me to "run_eda_simulation_tool eda_opts_hash".
where do I run it? I can't find anything in the dropdown menu that is remotely connected to this. What am I doing wrong?連結已複製
Correct. Modelsim has no concept of schematics.
What you need to do is convert the .bdf to a HDL file. If I recall correctly, there is a button somewhere that does this - basically creates either a Verilog or VHDL file based on the block diagram which you can then use for simulation. You will also have to set the HDL file to be the top level block instead of the .bdf file so that when it compiles for simulation it uses the correct file.Thank you for the link. I can now create a vhd file. However I still get a message that the Nativelink does not see the VHDL file. How does Nativelink know where to look. It's right there in the first directory of the project.
Thankfully I can get outside the Quartus II and invoke Modelsim directly from my PC It works well. However it's a royal pain. I wish I could figure how to make the Native link work. Any help would be welcome.) the problem exist and for me. The first launch Quartus Prime Lite allow to run Modelsim NativeLink after compiling. but subsequent only try to start the GUI of Modelsim, the 3 process appear in taskmanager but no GUI appear. if you choose command-line for Modelsim all will be fine. If you launch Modelsim from startmenu it works well. what does prevent correct nativelink launching?
When I go the Synthesis route, it creates a vho file which Modelsim does not recongize. I created the vhd file directly without going the synthesis and timing route. This is accepted by Modelsim in the standalone mode.
I am sorry I don't understand what you are asking me to do. I think you are saying that Quartus has a bug. I can bypass all that by simply launching Modelsim separately. It's working for me, and I will move on. Thanks for your help.
