Difference between revisions of "F21: Flame Over"

From Embedded Systems Learning Academy
Jump to: navigation, search
(Schedule)
(Schedule)
Line 75: Line 75:
 
*Start working on MP3 Decoder
 
*Start working on MP3 Decoder
 
|
 
|
* <span style="color:red">Not started</span>
+
* <span style="color:orange">In Progress</span>
* <span style="color:red">Not started</span>
+
* <span style="color:orange">In Progress</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 02:52, 3 November 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.

Project Title

Flame Over

Abstract

A single-player mode game where the player moves a fire fighter around a non-scrolling screen with burning buildings in the background to destroy the fireballs that come shooting at the player using a water gun. The player is granted three lives at the start of the game. Player’s lives will decrease by one for every three misses. The player can purchase water cartridges or a bonus life with the coins earned from putting out the fires. The player also receives a free bonus life when the player catches a firefighter hat sent at random times during the game. The player transits to the next level when the Master fireball at the end of each level is destroyed. The number and speed of the fireballs vary between levels.

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

  • Naveena Sura
  • Suganya Nandakumar
  • Vaidehi Deshpande

Schedule

Week# Start Date End Date Task Status
1
  • 09/25/2021
  • 09/28/2021
  • Read previous projects, gather information. Come up with an idea
  • Completed
2
  • 10/19/2021
  • 10/26/2021
  • Order necessary parts
  • Create Gitlab repository
  • In Progress
  • Not started
3
  • 10/26/2021
  • 11/02/2021
  • Read and familiarize with LED Matrix Datasheet
  • Read and familiarize with Bluetooth module(HC-05)
  • Start working on Led driver
  • Start working on Joystick Driver
  • Start working on MP3 Decoder
  • In Progress
  • In Progress
  • Not started
  • Not started
4
  • 11/02/2021
  • 11/09/2021
  • Finalize the game logic
  • Complete the Led Driver
  • Complete the Joystick Driver
  • Complete the MP3 Decoder
  • Not started
  • Not started
  • Not started
  • Not started
5
  • 11/09/2021
  • 11/16/2021
  • Finalize wiki schedule
  • Order circuit boards components and complete the design for printing
  • Not started
  • Not started
6
  • 11/16/2021
  • 11/23/2021
  • Integration of circuit boards and microcontroller
  • Work on Game logic development
  • Testing and debugging the game logic
  • Not started
  • Not started
  • Not started
7
  • 11/23/2021
  • 11/30/2021
  • Integrate game logic code with LED matrix
  • Integrate game sounds with game logic
  • Not started
  • Not started
8
  • 11/30/2021
  • 12/06/2021
  • Keep working on the game logic
  • Testing
  • Bug fixes
  • Update the wiki page.
  • Not started
  • Not started
  • Not started
  • Not started
9
  • 12/06/2021
  • 12/15/2021
  • Finalize the gameplay
  • Update git repo with final code
  • Ready for demo
  • Update the wiki page.
  • 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.