Difference between revisions of "F19: Tetris"

From Embedded Systems Learning Academy
Jump to: navigation, search
(Technical Responsibilities)
(Technical Responsibilities)
Line 69: Line 69:
 
! style="text-align: left;" |  
 
! style="text-align: left;" |  
 
* <span style="color:#000000">PCB </span>
 
* <span style="color:#000000">PCB </span>
|<font color="Sky"><B> Lawrence Wan </B></font>
+
|<font color="purple"><B> Lawrence Wan </B></font>
 
|-
 
|-
 
! style="text-align: left;" |   
 
! style="text-align: left;" |   

Revision as of 03:19, 13 November 2019

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


Tetris.png

Abstract

Our project is creating the game of Tetris using the LED matrix as our display and creating the driver for the game using the SJSU2 board from the class.

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

Technical Responsibilities
  • Gaming Logic & Driver
Kevin Chan & Lawrence Wan & Yuming Cheng & James Din
  • Enclosing
Yuming Cheng & Lawrence Wan
  • PCB
Lawrence Wan
  • BGM
James Din

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
Complete
In progress
3 5 Nov 2019 11 Nov 2019

Finalize the Wiki schedule for submission
Driver for the Tetris
Gaming Logic for the Tetris

In progress
Complete (Basic function complete)
In Progress (working on rotation)
4 12 Nov 2019 18 Nov 2019

Received the PCB and start working on connections
Implementing the new features (Save piece, preview pieces)
Update the diagram onto the wiki when possible
Updating the Wiki
Ordering the Enclosing Materials

In progress ( Waiting for PCB )
In progress
In progress
In progress
In progress
5 19 Nov 2019 25 Nov 2019

Starting to assemble the enclosing
Finish the Gaming logic and achieve the basic feature of Tetris
Add additional features
Create the Test Cases for the possible errors.
Include the BGM effects if there are no other additional features to add.

Waiting for Materials
In progress
In progress
Not Started
Not Started (Debating accordingly to our progress)
6 26 Nov 2019 2 Dec 2019

Polishing the Hardware and Software for project.
Revise and improve on small details or minor bugs discovered
Updating the Report, Cost, References, and circuit design.
Update the Wiki Schedule.

Not Started
Not Started
Not Started
In progress
7 3 Dec 2019 9 Dec 2019

FIELD TESTING - CRITICAL WEEK
Test all the possible test cases to debug.
Establish complete connection on PCB
Update wiki with details.

Not Started
Not Started
Not Started
Not Started
8 10 Dec 2019 17 Dec 2019

All hands on testing and final bug fixes.
Finish all the progress that's not finished
Create the semester long project activity video and upload to YouTube.
Update and finalize wiki.

Not Started
Not Started
Not Started
Not Started
Final 18 Dec 2019

DEMO: Final Project
SUBMISSION: Final Project Wiki

In progress
In progress

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 (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 of $14.61 for each member is not included )
  • Power Supply - 12V/5V (2A)
  • Sparkfun
  • 1 ( To increase the progress of project )
  • $ 11.94 each ( Total: $ 11.94 shipment cost of $14.61 is not included )
  • PCB Assembly & Sample
  • Online
  • 5
  • $ 1.728 Each for Assembly + $1.46 each for Sample ( Total: $ 32.75 shipment cost of $16.81 is included )
  • Voltage Regulator
  • Digi-Key
  • 3
  • $ 1.49 each ( Total: $ 4.47 shipment cost of $4.99 is not included )
  • 4 Pins Molex Connecter
  • Digi-Key
  • 3
  • $ 1.6 each ( Total: $ 4.80 shipment cost of $4.99 is not included )
  • SparkFun ATX Power Connector Breakout Board
  • SparkFun
  • 1
  • $ 1.95 each ( Total: $ 1.95 shipment cost of $13.33 is not included )
  • Screw Terminals 5mm Pitch (2-Pin)
  • SparkFun
  • 2
  • $ 0.95 each ( Total: $ 1.90 shipment cost of $13.33 is not included )
  • DC Barrel Power Jack/ Connector (SMD)
  • SparkFun
  • 3
  • $ 1.50 each ( Total: $ 4.50 shipment cost of $13.33 is not included )
  • ATX Right Angle Connector - PTH 4-pIn
  • SparkFun
  • 1
  • $ 0.50 each ( Total: $ 0.50 shipment cost of $13.33 is not included )
  • Wall Adapter Power Supply - 5V DC, 2A (Barrel Jack)
  • SparkFun
  • 1
  • $ 5.95 each ( Total: $ 5.95 shipment cost of $13.33 is not included )


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

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.