On the wave window to get a menu that will let you zoom in and out. After you've clicked on that once or twice, then right click Right of the text box (mouse-over and you will see a tooltip that says Your machine to simulate 10 or so cycles when you push the first button to the Ps" you can change that to "200 ns" or so, and that will cause There's a text box that usually starts out as "0 The best way toĬalibrate is to look for your clock signal but to do that, you first need to One of the first things you want to do is make sure you have a This is the main way that youĭebug hard bugs. Show most of your signals, correlated over time. "sim" window over to the left side of the wave window. You may be more selective in the signals you examine. Later on, when your design is mostly working but you are tracking down specific problems, You will just find that red is spreading from the output of the register to the input. It is important to do this right after reset,īecause one red spreads to your registers, and you have feedback (for instance for your pc_r register), Until you find the signal that initially caused redness. You find a signal that should not be red, and then trace it back through the gates that generate it, Pay attention to the values at the clk edge. You want to make sure to look at the waveforms immediately after reset goes low and only This will allow you to look across all of the signals in your design and trace through yourĬircuit looking for parts in your verilog that are responsible for disconnected and/or red signals. It often is useful to go to the Sim window, right click on your top level testbench,Īnd select Add->To Wave->All Items In Region and Below. The most useful ones after you have started your simulation are theĭebugging your verilog, you will be hunting for things that look wrong Your current window to another one, select Window->(the window you want.) It often feels like you are always trying to track down the
The module name that corresponds to your testbench hit OK.
#Modelsim altera not showing waveforms plus
Click the plus next to 00_lib (or whatever your test is called) select To Processes Window Select Compile->All fix errors then Simulate->Start If you see instantiation errors for altsyncram, it's probably because you ommitted these files.
#Modelsim altera not showing waveforms update
(Note: you may have a more updated version of altera on your system, and should update the version number Mystery: You need to add two files to support the macros generated byĬ:/altera/10.1sp1/quartus/eda/sim_lib/altera_mf.vĬ:/altera/10.1sp1/quartus/eda/sim_lib/220model.v High-impedance output issue for students. Only and will result in "Failed to Find Instance" errors.) same ones that were in your Quartus project. sdo files those are for timing simulation Source files to the ModelSim project (note: do not add any. The 00 makes it easy to find your projects in the list. Labs instead of the one they are working on, and don't realize it. Projects you work on in the class, and a common problem is that students use accidentally use old compiled simulation files from previous Over time, you accumulate libraries from different It's good to pay attention to this and to use consistent and descriptive names. For library, I recommend you use 00_lib.
0 kommentar(er)
