Subversion Repositories zipcpu

#       Useful targets of this makefile include:

#

#       zippy_tb (default)

#               This is the test bench program / simulator that is built by

#               this directory.

#

#       test

#               Runs the simulator on a test program found in the trunk/sw/zasm

#               directory.  That program needs to be built via 'make test' in

#               that directory before this make test will work.  Changes to the

#               test itself will require a 'make test' in trunk/sw/zasm as well

#               as 'make test' in this directory.

#

#               The test itself consists of two tests.  The first, the "step"

#               test, tests whether the test works via "step"ing the CPU.

#               This would be the interface to the CPU were the CPU placed in

#               a device.

#

#               The second test is an internal test which works by just running

#               the CPU without step instructions.

#

#               In either case the test is over upon reaching either a HALT

#               or a BUSY instruction.  A HALT instruction indicates success,

#               BUSY a failure.

#

#       stest

#               Runs the test in "step" mode as described above.

#

#       itest

#               Runs the test file in interactive mode.  The CPU will not

#               execute any instructions without user interaction.  This is

#               useful for actually debugging the test.  The other two modes

#               are useful for quickly determining that the CPU does (or

#               doesn't) work.

#

#       dhrystone

#               Runs a hand-optimized version of the dhrystone benchmark.

#               Using the instructions at the top of the dhrystone assembly

#               file, you should be able to convert the result to DMIPS or even

#               DMIPS/MHz.

#

#       div_tb

#               A raw test bench to test the divide unit separate from the

#               rest of the CPU.  This test will fail with a failed assert()

#               if unsuccessful, or complete with no error (but lots of

#               debugging output) if successful.  To actually run this test,

#               you'll need to run ./div_tb (no arguments necessary).

#

#       pdump

#               zippy_tb can be configured to produce a profile output that is

#               very useful when debugging the Dhrystone benchmark.  (It is

#               so configured by default.)  This file will be name pfile.bin.

#               pdump is a very simple program designed to read this file and

#               produce some (very raw) information from it.  To use this,

#               type pdump and the name of the executable file, such as

#               ../asm/zipdhry.z, and examine how many times each instruction

#               was executed, and how many stalls took place between each

#               instruction and the next.

#

#       clean

#               Removes all products of compilation--specifically zippy_tb,

#               pdump and div_tb.

#