
5.2. WHAT TO INCLUDE IN THE LAB REPORT
59
5.2 What to Include in the Lab Report
The lab report should contain all source code that you have written. (The source code
should of course be commented.) We would also like you to include a block diagram
of your hardware. If you have written any FSM you should include a state diagram
graph of the FSM.
We would also like you to discuss the following questions in detail somewhere in
your lab report
1
:
• How does your hardware work?
• How did you verify that your hardware worked?
• How did you modify the software?
• A timing diagram.
• What is the utilization of your accelerator?
• What is the performance of jpegtest with DMA enabled?
• How long does it take (on average) to read a macroblock into the DCT acceler-
ator via DMA?
• How much is the wishbone bus used by the DMA unit and how much is the bus
used by the CPU?
And of course, the normal parts of a lab report such as a table of contents, an intro-
duction, a conclusion, etc. The source code that you have written should be included
in appendices and referred to from the main document.
1
In order to answer some of these questions you will probably have to modify the performance coun-
ters you added in lab 1 and add support for (at least) the DMA bus master to it.
Comentarios a estos manuales