Assignment 2: “Basketball” video game
Set by: Distributed to students: Submission deadline: Feedback: Submission mode:
Assignment objectives
Dr Xiaojun Zhai week 21
three weeks from submission deadline electronic only via FASer
This document specifies the second coursework assignment to be submitted by students taking CE339. This assignment is more challenging than the first one and it is meant to provide an opportunity to improve the knowledge of the VHDL language and, more importantly, to design a digital “system”. You will be expected to learn to: a) implement digital system design in VHDL code; b) synthesise and download it to the target hardware; c) test, debug, and verify that the design meets the specifications; d) report about your design.
You are required to design code for your target hardware (a Digilent Basys3 board with a Xilinx Artix 7 FPGA) in order to implement a design that meets the specifications (below). You are required to submit working and correct code and you are strongly encouraged to use a modular coding style (allowing for greater flexibility, maintainability, modularity, and reusability). To show that you master all aspects of the language, your code should prevalently use concurrent statements for combinatorial circuits and sequential code for sequential circuits. Additionally, the use of non- standard packages (e.g. STD_LOGIC_ARITH, STD_LOGIC_UNSIGNED, STD_LOGIC_SIGNED) and BUFFER ports is forbidden, while the use of INOUT ports is accepted only when strictly necessary.
You are supposed to gain familiarity with VHDL coding during the supporting CE339 lectures and through self-study hours, also with the help of the recommended textbooks or any other book about VHDL. You are expected to work on this assignment mostly during lab hours. Your design project should be stored in the Gitlab repository that was assigned to you at the beginning of the course. You are supposed to commit often and describe your progress in the commit messages. In order to promote a learning scheme that values the learning process in addition to the submitted final design, your weekly progress (as traced back by the commit logs) will contribute to your assignment mark.
Design specifications
Your task for this assignment is to implement a “Basketball” video game. To make the assignment feasible within the time frame available for this module, you are not required to implement the full game, but only a simplification of the phase of the game when a player is awarded free throws.
The basic layout should include a basket, a ball, and a player. The shapes representing these three elements can be very simple, like those in the mock-up in Figure 1. The player (represented as a green rectangle in the figure) throws the ball towards the basket. The ball flies, following a parabolic trajectory, towards the basket. If the ball enters the basket a point is awarded. In the interest of time, this condition can be simplified and a point be awarded whenever the ball somehow hits the rim of the basket (in red in the figure).
By using the controls available on the Basys3 board, the user determines the direction and intensity of the throw. In “debug mode”, the 4 leftmost switches encode the initial horizontal speed
CSEE – University of Essex
Github
Figure 1: Mock-up for the simplified “Basketball” game, final result of this assignment.
of the ball, the next 4 switches encode its vertical speed, and the central button is used to throw the ball. In “play mode”, it is left to the student to decide the details of the user interface and how to make the game more challenging.
These specifications should be interpreted as guidelines and should not constrain you from improving the game by designing better graphics, more realistic criteria for awarding the point, and other modifications that you think would result in a better “product”.
You should write a report introducing the project and then describing your codings and designs for the assignment. It should first describe the design at a higher level and then detail the implementa- tion of each module in a top-down fashion (rather than in chronological order). Also report if your code worked at the first attempt, what was wrong and how you fixed it. The Gitlab repository log (if you used it properly) should help you considerably in this task. Your report should also include a discussion of design alternatives that you considered and the motivations for your final choice.
Your document should have a title page and be sub-divided into appropriately headed sections. It MUST contain references to material used in your work (e.g., VHDL code or information available in books or on the Internet). All of the VHDL code submitted should be included in the report in the form of code appendices and be typeset in Courier font (or a suitable fixed-width alternative font of your choice). Your report should consist of approximately 1500–2000 words of narrative (i.e. excluding references, code fragments, pictures, diagrams and schematics). Please write registration number and word count on the title page of your report.
Submission
Your work must be submitted to the university’s online FASer submission system at the address https://faser.essex.ac.uk/ by the deadline given on the system. No other mode of submission is acceptable. You are strongly advised to upload a draft submission before the last lab hours prior to the deadline, and then update it up to the deadline.
You are required to submit one ZIP archive (not RAR or other formats) containing the following files:
1. All source files needed to synthesize your project (but not the temporary files created by Vivado);
2. A report document submitted in PDF format. DO NOT SUBMIT THIS FILE IN .DOC OR .DOCX OR SIMILAR FORMATS – SUBMIT PDF.
Programming Help
3. Your repository log in .TXT format or screenshot.
4. If you want (in your own interest, see next section), submit a .TXT or .PDF file with the transcripts of relevant forum discussions you contributed to.
DO NOT WAIT UNTIL CLOSE TO THE DEADLINE TO MAKE YOUR FIRST SUBMIS- SION. Difficulties with the submission system will not be accepted as an excuse for a missing submission.
Marking criteria
This assignment is worth 40% of the module mark. Marks will be awarded for the VHDL code, including coding style and quality, and for the descriptive document, including content, presentation, and discussions. In addition to the report, each students will be expected to demonstrate and explain her/his design with confidence and competence during a demo lab session. Marks will be assessed based on:
• Implementation
– Quality of the implementation …………………………………………….15% – Modular design …………………………………………………………..6% – Generic and re-usable code ……………………………………………….. 6% – Proper use of comments …………………………………………………..6% – Steady progress, adequate use of GIT ……………………………………….6% – Quality and confidence of demonstration ………………………………….. 15%
– Correctness and completeness of report …………………………………….12% – Clarity of presentation ………………………………………………….. 12% – Organisation of report ……………………………………………………12% – Quality of diagrams and schematics …………………………………………8%
– Compliance with submission instructions …………………………………… 2%
Marks below 100% can earn additional credits if the student actively engaged in forum discus- sions asking pertinent questions and giving competent answers to questions raised by classmates.
Late Submission and Plagiarism
Please refer to the Students’ Handbook for details of the Departmental policy regarding submission and University regulations regarding plagiarism.
Revision 1.0 21/12/2022 Xiaojun Zhai
浙大学霸代写 加微信 cstutorcs