Difference between revisions of "F21: Skeh-lleybones"

From Embedded Systems Learning Academy
Jump to: navigation, search
(Schedule)
(Schedule)
Line 62: Line 62:
 
|
 
|
 
* <span style="color:green">Completed</span>
 
* <span style="color:green">Completed</span>
* <span style="color:orange">In progress</span>
+
* <span style="color:green">Completed</span>
* <span style="color:orange">In progress</span>
+
* <span style="color:green">Completed</span>
 
|-
 
|-
 
! scope="row"| 3
 
! scope="row"| 3
Line 74: Line 74:
 
* Finalize game design (powerups, scoring system, boss?)
 
* Finalize game design (powerups, scoring system, boss?)
 
|
 
|
* <span style="color:red">Not started</span>
+
* <span style="color:green">Completed</span>
* <span style="color:red">Not started</span>
+
* <span style="color:green">Completed</span>
 
|-
 
|-
 
! scope="row"| 4
 
! scope="row"| 4
Line 87: Line 87:
 
* Preliminary enclosure design
 
* Preliminary enclosure design
 
|
 
|
* <span style="color:red">Not started</span>
+
* <span style="color:green">Completed</span>
* <span style="color:red">Not started</span>
+
* <span style="color:green">Completed</span>
* <span style="color:red">Not started</span>
+
* <span style="color:green">Completed</span>
 
|-
 
|-
 
! scope="row"| 5
 
! scope="row"| 5
Line 101: Line 101:
 
* Enclosure design finalized
 
* Enclosure design finalized
 
|
 
|
* <span style="color:red">Not started</span>
+
* <span style="color:green">Completed</span>
* <span style="color:red">Not started</span>
+
* <span style="color:green">Completed</span>
* <span style="color:red">Not started</span>
+
* <span style="color:green">Completed</span>
 
|-
 
|-
 
! scope="row"| 6
 
! scope="row"| 6
Line 114: Line 114:
 
* Final game implementation finished
 
* Final game implementation finished
 
|
 
|
* <span style="color:red">Not started</span>
+
* <span style="color:green">Completed</span>
* <span style="color:red">Not started</span>
+
* <span style="color:orance">In Progress</span>
 
|-
 
|-
 
! scope="row"| 7
 
! scope="row"| 7
Line 126: Line 126:
 
* Bug fixes
 
* Bug fixes
 
|
 
|
* <span style="color:red">Not started</span>
+
* <span style="color:orange">In Progress</span>
 
|-
 
|-
 
! scope="row"| 8
 
! scope="row"| 8
Line 136: Line 136:
 
* Finish wiki report
 
* Finish wiki report
 
|
 
|
* <span style="color:red">Not started</span>
+
* <span style="color:orange">In Progress</span>
 
|-
 
|-
 
! scope="row"| 9
 
! scope="row"| 9
Line 142: Line 142:
 
* 12/16/2021
 
* 12/16/2021
 
|  
 
|  
* 12/18/2021
+
* 12/16/2021
 
|
 
|
 
* Demo
 
* Demo

Revision as of 00:41, 16 December 2021

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.

Block Breaker

Block Breaker is a fun game in which you control a paddle and destroy blocks with a moving ball. The player controlled paddle deflects the ball at different angles to target different blocks and destroy them.

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 & Responsibilities

Prabhjyot Obhi

  • Objectives here

Justin Stokes

  • Objectives here

Manas Abhyankar

  • Objectives here


Schedule

Week# Start Date End Date Task Status
1
  • 11/1/2021
  • 11/5/2021
  • Read previous projects, gather information and discuss among the group members.
  • Create GitLab repository for project
  • Finalize Parts list
  • Completed
  • Completed
  • Completed
2
  • 11/5/2021
  • 11/9/2021
  • All parts ordered
  • Decide final pinout
  • PCB generated and ordered
  • Completed
  • Completed
  • Completed
3
  • 11/9/2021
  • 11/12/2021
  • Simple display driver finished (display pixel at given coordinate)
  • Finalize game design (powerups, scoring system, boss?)
  • Completed
  • Completed
4
  • 11/12/2021
  • 11/17/2021
  • Fully functional display driver
  • Game menu finish
  • Preliminary enclosure design
  • Completed
  • Completed
  • Completed
5
  • 11/17/2021
  • 11/26/2021
  • Basic game implementation finished
  • Verify PCB
  • Enclosure design finalized
  • Completed
  • Completed
  • Completed
6
  • 11/26/2021
  • 12/3/2021
  • Enclosure printed and tested
  • Final game implementation finished
  • Completed
  • In Progress
7
  • 12/3/2021
  • 12/10/2021
  • Free week to allow for schedule shifting
  • Bug fixes
  • In Progress
8
  • 12/10/2021
  • 12/16/2021
  • Finish wiki report
  • In Progress
9
  • 12/16/2021
  • 12/16/2021
  • Demo
  • Not started


Parts List & Cost

    • PLACEHOLDER**

It worked out well when we put a table here that listed various things, like our part name, a description, purchase source, and 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.