6.8. WHAT TO INCLUDE IN THE LAB REPORT
69
• How to read from a special purpose registers with address 0xC000 in C-code:
asm volatile("l.mfspr %0,%1,0x0" : "=r"(result) : "r"(0xc000))
• If you are writing inline assembler with more than one instruction you should
read the following paragraph for information about input and output operands[16]:
Unless an output operand has the & constraint modifier, GCC
may allocate it in the same register as an unrelated input operand, on
the assumption the inputs are consumed before the outputs are pro-
duced. This assumption may be false if the assembler code actually
consists of more than one instruction. In such a case, use & for each
output operand that may not overlap an input.
6.8 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 graph of the
FSM.
We would also like you to discuss the following questions in detail somewhere in
your lab report:
• How does your hardware work?
• How did you verify that your set bit hardware worked?
• What is the performance with and without the set bit hardware? This should
include measurements of both the entire application and the set bit instruction
by itself, assuming good code in a software implementation (take a look at how
the software solution in jpegfiles).
• How much of the FPGA does your hardware use?
• How would your design change if you had to achieve even higher speed using
more hardware?
• How would your design change if you had to use less har dware at the cost of a
slower solution?
• What are the problems with using your new hardware in a multitasking operating
system? How can the problem(s) be solved?
• What is the performance of your final system?
• What was the hardest problems you encountered during the entire lab course?
And if you want to, we would appreciate some comments on the following ques-
tions, either in the lab report or by some other means of communications:
• What did you think of the TSEA44 course?
• What was good?
Kommentare zu diesen Handbüchern