Here is simple exmplanation to use Altera simulation.
(1) In windows, you should double click "QuartusII" short cut, or
select "Programs" -> "Altera" -> "QuartusII".
(2) You will have QuartusII window.
(3) Choose "File"->"Open project". And point your ghostbuster/processor
directory and select "gb.quartus"
(4) Then please select "Processing"->"Compile mode"
Again, "processing" -> "Start compilation".
(5) If you succeed the compilation (if you don't touch anything
this must succeed),
you should choose "Processing" -> "simulation mode".
After that, "Processing" -> "start simulation" should be selected.
(6) Resulting, you will have a timing trace screen.
Of course, you need to change the input file of simulation (gb.vwf)
if you want to prove new firmware works well.
In order to change the input file, you have gb.py file in processor
directory.
This is python-based file to create Altera simulation file made by
Bill Ashmanskas.
It's quite smart file because you don't have to create input file
"by hand as manual said". (What a smart)
To create gbq.vwf (input file), please type,
"python gbq.py" in your linux machine. That all you need.
Eventually, you have another output file from gbq.py, that is
"gbinput.dat" as a text file below mentioned.
In fact, gbq.py creates quite good random track packets mimic
the TF output.
[Track packets for CDF_SVT (ps)].
Mentor Graphics also needs simulation input file.
As was surprised, this can be prepared from Bill Ashmanskas's another
python program.
That is located in "ghostbuster/mentor_graphics/qsim_gb.py".
Same as gbq.py, you only need type "python qsim_gb.py gb".
So, you have input file, "qsim_gb.ff". (You need copy this file
to "/designs/CDF_SVT/.")
One thing mainly different from "gbq.py" is that we have to create
track input by hand for "qsim_gb.py" case.
Hereafter, I explain how to modified mif-file and vho-file for Mentor
Graphics.
Mif-file is used to initialize the Flush Memory data.
Currently, (1) Flush Memory #1 uses fram1.mif, (2) #2 uses fram2.mif and
(3) #3 uses fram3.mif in th e/designs/CDF_SVT/GhostBuster/.
If you need change the stored data in Flush RAM, you also need change
this mif files. Otherwise, you cannot simulate correctly.
vho-file are VHDL file created from Altera simulation.
Mentor Graphics simulation only allows VHDL language, so that we need
translate the AHDL using Altera simulation.
At present, QuartusII version 1.1 can only translate this well.
Thus, please use version1.1 for Mentor Graphics.
After compilation of Altera part, you have simulation/vss/{gb.vho,
gb_vhd.sdo} under the processor/ directory. These are translated files.
These files shold be copied to /designs/CDF_SVT/GhostBuster/. also.
Unfortunately, situation is getting complicated after August-2002.
Because I divide functionalities of each 3 chips.
Therefore, now, we need to create {gb1.vho, gb2.vho, gb3.vho} and {
gb1_vhd.sdo, gb3_vhd.sdo, gb3_vhd.sdo}.
One way to create these files is "cp -r /processor processor_1" and so
on, and change character "gb"->"gb1" in the files
{gb.csf* gb.psf* gb.quartus* gb.tdf* idprom.tdf*}.
Then compile, gb1.tdf, gb2.tdf and gb3.tdf to create.
Now I use processor_1 (copy of processor directory) as a chip#1 vho,
utility_2,3 (copy of utility directory) as chip#2,3 cho-file.
Finally, I talk about how to change the viewpoint of GB schematic.
This handing is quite rare case, but is useful for something.
For example, I assume I'd like to change reading mif-file, from
"y:/CDF_SVT/GhostBuster/fram1.mif" to "y:\CDF_SVT\GhostBuster\fram1.mif".
(1) Please open the schematic of GhostBuster Board using "open sheet" in
timing trace window (right-side).
(2) Select "chip sheet" and "ctrl-F8".
(3) You can select Altera-chip, FRAM and so on. In this time, you select
FRAM.
(4) Button right-side mouse, and select "Edit"->"Property"->"Change".
(5) You can change mif-file name now.
(6) In main screen, you choose "File"->"save"->"design changes".
(7) Also "File"->"save"->"setup".
I know this explanation is quite imcomplete. If I can, I will update. (In particular, chip divided functionalities and schematic topics. sorry)