F19: Tetris

Grading Criteria

How well is Software & Hardware Design described?
How well can this report be used to reproduce this project?
Code Quality
Overall Report Quality:
- Software Block Diagrams
- Hardware Block Diagrams
  Schematic Quality
- Quality of technical challenges and solutions adopted.

Project Title

LED Matrix Tetris

Abstract

This section should be a couple lines to describe what your project does.

Objectives & Introduction

Show list of your objectives. This section includes the high level details of your project. You can write about the various sensors or peripherals you used to get your project completed.

Team Members & Main Responsibilities

Administrative Roles
Team Lead	Kevin Chan & Lawrence Wan
Finance Manager	Yuming Cheng
Git Repository Manager	Lawrence Wan
Wiki Report Manager	Yuming Cheng & James Ding
Bill of Materials Manager	Kevin Chan
Grammar Check	Lawrence Wan & Kevin Chan

Technical Responsibilities

Schedule

Show a simple table or figures that show your scheduled as planned before you started working on the project. Then in another table column, write down the actual schedule so that readers can see the planned vs. actual goals. The point of the schedule is for readers to assess how to pace themselves if they are doing a similar project.

Team Deliverables Schedule

WEEK	START DATE	END DATE	TASK DETAILS	STATUS
1	8 Oct 2019	21 Oct 2019	Create and establish GitLab repository Establish slack channel and invite Preet Look through previous years projects and study it Distribute major roles among team members Select and order Parts Start rough version of Wiki Schedule	In Progress In Progress In Progress Complete Complete Complete
2	22 Oct 2019	4 Nov 2019	Create a Bill of Materials. Reading on the Data sheet of LED matrix Create the rough version of Report and Presentation slide	In Progress In progress In progress
3	5 Nov 2019	11 Nov 2019	Finalize the Wiki schedule for submission	In progress
4	12 Nov 2019	18 Nov 2019
5	19 Nov 2019	25 Nov 2019
6	26 Nov 2019	2 Dec 2019	' ' ' ' ' Update the Wiki Schedule.
7	3 Dec 2019	9 Dec 2019	FIELD TESTING - CRITICAL WEEK Check overall robustness of the complete system. Establish complete connection on PCB Update wiki with details.
8	10 Dec 2019	17 Dec 2019	All hands on testing and final bug fixes. Check for tuning or calibration of sensors if required. Complete end-to-end testing for various scenarios and conditions. Create the semester long project activity video and upload to YouTube. Update and finalize wiki.
Final	18 Dec 2019		DEMO: Final Project SUBMISSION: Final Project Wiki

Parts List & Cost

Give a simple list of the cost of your project broken down by components. Do not write long stories here.

PART NAME	PART MODEL & SOURCE	QUANTITY	COST PER UNIT (USD)
SJSUDEV2 Board	LPC 4078 (Purchased from Preet Kang)	4 ( One for each group member )	$ 50.00 each ( Total: $ 200 )
RGB LED Matrix Panel 32x32	Sparkfun	3 ( To increase the progress of project )	$ 55.90 each ( Total: $ 167.70* shipment cost for each member is not included* )
Power Supply - 12V/5V (2A)	Sparkfun	3 ( To increase the progress of project )	$ 11.94 each ( Total: $ 35.82* shipment cost for each member is not included* )
something	Place purchase	Quantity	Price
Total Cost:			Price:

Design & Implementation

The design section can go over your hardware and software design. Organize this section using sub-sections that go over your design and implementation.

Hardware Design

Discuss your hardware design here. Show detailed schematics, and the interface here.

Hardware Interface

In this section, you can describe how your hardware communicates, such as which BUSes used. You can discuss your driver implementation here, such that the Software Design section is isolated to talk about high level workings rather than inner working of your project.

Software Design

Show your software design. For example, if you are designing an MP3 Player, show the tasks that you are using, and what they are doing at a high level. Do not show the details of the code. For example, do not show exact code, but you may show psuedocode and fragments of code. Keep in mind that you are showing DESIGN of your software, not the inner workings of it.

Implementation

This section includes implementation, but again, not the details, just the high level. For example, you can list the steps it takes to communicate over a sensor, or the steps needed to write a page of memory onto SPI Flash. You can include sub-sections for each of your component implementation.

Testing & Technical Challenges

Describe the challenges of your project. What advise would you give yourself or someone else if your project can be started from scratch again? Make a smooth transition to testing section and described what it took to test your project.

Include sub-sections that list out a problem and solution, such as:

<Bug/issue name>

Discuss the issue and resolution.

Conclusion

Conclude your project here. You can recap your testing and problems. You should address the "so what" part here to indicate what you ultimately learnt from this project. How has this project increased your knowledge?

Project Video

Upload a video of your project and post the link here.

Project Source Code

Sourceforge Source Code Link

References

Acknowledgement

Any acknowledgement that you may wish to provide can be included here.

References Used

List any references used in project.

Appendix

You can list the references you used.