Difference between revisions of "F22: Embedded Gamers"

From Embedded Systems Learning Academy
Jump to: navigation, search
(Schedule)
(Schedule)
Line 145: Line 145:
 
! scope="row"| 9
 
! scope="row"| 9
 
|  
 
|  
 +
* 12/07/2020
 
* 12/07/2020
 
* 12/07/2020
 
|  
 
|  
 +
* 12/13/2020
 
* 12/13/2020
 
* 12/13/2020
 
|
 
|
Line 152: Line 154:
 
* Test pause/play functionality
 
* Test pause/play functionality
 
|
 
|
* <span style="color:red">Not started</span>
 
 
* <span style="color:red">Not started</span>
 
* <span style="color:red">Not started</span>
 
* <span style="color:red">Not started</span>
 
* <span style="color:red">Not started</span>

Revision as of 18:34, 14 October 2022

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

Guardians of the Galaxy

Abstract

A horizontal type of space invader game. Players can control the spaceship on the screen composed of an LED matrix in a rectangular shape. The spaceship can shoot horizontally from left to right in order to destroy its enemies. The entire map will flow in the opposite direction of where the spaceship is flying. The speed of the map flow and the number of enemies will increase at higher difficulty levels. The spaceship takes damage from colliding with enemies themselves or their bullets. The game will end when the health of the controlled spaceship is depleted.

Objectives & Introduction

Team Members & Responsibilities

  • Bruce Jiang
  • Phil Bloxom
  • Ritu Patil

Schedule

Week# Start Date End Date Task Status
1
  • 10/03/2022
  • 10/03/2022
  • 10/8/2022
  • 10/8/2022
  • Read previous projects, gather information and discuss among the group members.
  • Create GitLab repository for project
  • Completed
  • In progress
2
  • 10/10/2022
  • 10/15/2022
  • Order necessary parts
  • In progress
3
  • 10/17/2022
  • 10/22/2022
  • Read and familiarize with LED Matrix Datasheet
  • Not started


4
  • 10/31/2022
  • 11/05/2022
  • Develop graphics driver for LED matrix and implement initial game objects
  • Not started
5
  • 11/07/2022
  • 11/07/2022
  • 11/12/2022
  • 11/12/2022
  • Finalize wiki schedule
  • Additional accessories if required and finalization of hardware
  • Not started
  • Not started
6
  • 11/16/2020
  • 11/22/2020
  • Integration of circuit boards and microcontroller
  • Game logic development
  • Testing and debugging the game logic
  • Not started
  • Not started
  • Not started
7
  • 11/23/2020
  • 11/29/2020
  • Integrate game logic code with LED matrix
  • Integrate game sounds with game logic
  • Not started
  • Not started
8
  • 11/30/2020
  • 12/06/2020
  • Integrate subsystem
  • Finalizing the video game
  • Update the wiki page.
  • Not started
  • Not started
  • Not started
9
  • 12/07/2020
  • 12/07/2020
  • 12/13/2020
  • 12/13/2020
  • Address bugs during testing of integrated system
  • Test pause/play functionality
  • Not started
  • Not started
10
  • 12/16/2020
  • 12/14/2020
  • 12/14/2020
  • 12/14/2020
  • 12/16/2020
  • 12/16/2020
  • 12/16/2020
  • 12/16/2020
  • Final Demo
  • Update Gitlab repo with final code.
  • Update test video.
  • Update the wiki page.
  • Not started
  • Not started
  • Not started
  • Not started


Parts List & Cost

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

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.