How to Set Up the Project:

1. take the 'pacoblaze-2.2' directory and put it in a new directory. this new directory will help us later on.

2. in the folder 'pacoblaze-2.2/pacoblaze' is a Makefile. inside of it you can understand which files are needed for the project. for example if you wanted pacoblaze3 test bench then you can see the line 53 in the Makefile:

pacoblaze3_tb.vcd: blockram.v pacoblaze3.v pacoblaze3_tb.v

Now create a new project in ISE and set the project folder inside the new directory we created in step 1.
Add each of the files mentioned in the Makefile, for ex. the pacoblaze3 testbench will require the files blockram.v, pacoblaze3.v and pacoblaze3_tb.v. You need to add them through the 'Add Source' option (don't foregt to add the ones from the directory we moved into our new directory).

3. There is a line we need to fix in pacoblaze3_tb.v (or any other test bench fiel your using). In the file pacoblaze3_tb.v it is in line 115 but you can find it easily by searching for 'dumpvars':

$dumpvars(-1, dut);

It needs to be changed to the following line:

$dumpvars(0, dut);

The purpose of this line is for debugging purposes, but the ISE package doesn't support the -1 parameter.

4. Now you can run the simulator. Notice that some of the output will be unknown ("x" value). look in the console part and you will see that there will proably be an error that says it can't find the file "adc_ctrl.rmh". This is the test file that the processor tries to run by default. The reason it can't find the file is because we need to adjust the path. look for the string "`define TEST_FILE" in the test bench file, you will probably find the line (in pacoblaze3_tb.v it is number 115):

`define TEST_FILE "../test/adc_ctrl.rmh"

you need to fix the ".." part to signify the new path of the file (for ex. "pacoblaze_playground/pacoblaze-2.2/pacoblaz/test/adc_ctrl.rmh".

5. Your All Done! the simulation should now run great and all the output should be actual binary values. Now you can change the filename from step 4 to include your own test files which you assembled.

Additional Tips:
1. show instructions executed - add the string "HAS_DEBUG" to the -d field inside the 'Process Properties" (last entry when right click on the menu 'Behavioural Check Syntex' in the simulation lower pane).