Difference between revisions of "F21: Flame Over"

From Embedded Systems Learning Academy
Jump to: navigation, search
(Schedule)
(Schedule)
Line 156: Line 156:
 
! scope="row"| 6
 
! scope="row"| 6
 
|
 
|
*11/16/2021  
+
*11/23/2021  
 
|  
 
|  
*11/23/2021
+
*11/30/2021
 
|
 
|
* Integration of circuit boards and microcontroller
+
*Interface all the sensors, MP3 audio, Bluetooth module, joystick
* Work on Game logic development
+
*Test the whole implementation after integrating all the modules
* Testing and debugging the game logic
+
*Debug and Test all the gaming functionalities for each module
 +
*Add the developed game logic
 +
*Test the game after adding the logic
 
|
 
|
 +
* <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>
 
* <span style="color:red">Not started</span>
Line 170: Line 174:
 
! scope="row"| 7
 
! scope="row"| 7
 
|  
 
|  
* 11/23/2021
+
* 12/01/2021
  
 
|  
 
|  
* 11/30/2021
+
* 12/06/2021
 
|
 
|
* Integrate game logic code with LED matrix
+
*Start working on Project report
* Integrate game sounds with game logic
+
*Finalize the video game
 
|
 
|
 
* <span style="color:red">Not started</span>
 
* <span style="color:red">Not started</span>
Line 183: Line 187:
 
! scope="row"| 8
 
! scope="row"| 8
 
|  
 
|  
* 11/30/2021
+
* 12/07/2021
 
|  
 
|  
* 12/06/2021
+
* 12/13/2021
 
|
 
|
  
* Keep working on the game logic
+
*Test the game logic
* Testing
+
*Check for the bug fixes
* Bug fixes
+
*Update Wiki page
* Update the wiki page.
+
*Work on project report
 +
*Update the GIT repo with the final code
 
|
 
|
 +
* <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>
Line 200: Line 206:
 
! scope="row"| 9
 
! scope="row"| 9
 
|  
 
|  
* 12/06/2021
+
* 12/14/2021
 
|  
 
|  
* 12/15/2021
+
* 12/16/2021
 
|
 
|
* Finalize the gameplay
+
* Final demo
 
* Update git repo with final code
 
* Update git repo with final code
* Ready for demo
+
* Update the Wiki page with game demo link
* Update the wiki page.
 
 
|
 
|
 
* <span style="color:red">Not started</span>
 
* <span style="color:red">Not started</span>

Revision as of 23:26, 9 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
  • 10/15/2021
  • 10/22/2021
  • Read previous projects, gather information.
  • Discussion on RGB LED matrix and Audio Decoder.
  • Gathering information regarding Bluetooth module and Joystick interface.
  • Finalize part list
  • Decide and distribute major roles among team members
  • Decide and re-phrase the game rules
  • Completed
  • Completed
  • Completed
  • Completed
  • Completed
  • Completed
2
  • 10/23/2021
  • 11/04/2021
  • Order necessary parts
  • Plan first draft of Wiki schedule
  • Review RGB LED Matrix datasheet.
  • Review Audio MP3 decoder datasheet.
  • Review the extra hardware needed for RGB LED matrix(Power Adapter)
  • Create Gitlab repository
  • Create a shared google drive for the team to share available resources
  • Completed
  • Completed
  • Completed
  • Completed
  • Completed
  • Completed
  • Completed
3
  • 11/05/2021
  • 11/09/2021
  • Read and familiarize with Bluetooth module(HC-05)
  • Start driver implementation for RGB LED matrix
  • Test the driver for single row
  • Implement functions for all the rows and columns in RGB LED matrix
  • Decide the graphics and character images for the game
  • Finalize the Wiki Schedule
  • Completed
  • Completed
  • Completed
  • Completed
  • Completed
  • Completed
4
  • 11/10/2021
  • 11/15/2021
  • Start designing the PCB circuit using a PCB design software.
  • Test the LED driver functioning and should display one of the character from game
  • review the Audio MP3 functioning
  • Interface of joystick and SJtwo board
  • Bluetooth module interface with joystick and SJtwo board
  • Test bluetooth module functioning by sending and receiving data to the SJtwo board
  • Discuss the techniques to handle obstacles
  • Finalize PCB design circuit
  • Not started
  • Not started
  • Not started
  • Not started
  • Not started
  • Not started
  • Not started
  • Not started
5
  • 11/16/2021
  • 11/22/2021
  • Implementation of the game screens on the RGB LED matrix
  • Read some audio from SD card and send to Audio MP3 shield
  • Synchronize the Audio MP3 with the game graphics
  • Start PCB soldering and testing each part after fixing
  • RGB LED matrix should handle graphics for different game levels
  • Finalize sounds for different scenarios in the game
  • Test each module separately and review the code
  • Not started
  • Not started
  • Not started
  • Not started
  • Not started
  • Not started
  • Not started
6
  • 11/23/2021
  • 11/30/2021
  • Interface all the sensors, MP3 audio, Bluetooth module, joystick
  • Test the whole implementation after integrating all the modules
  • Debug and Test all the gaming functionalities for each module
  • Add the developed game logic
  • Test the game after adding the logic
  • Not started
  • Not started
  • Not started
  • Not started
  • Not started
7
  • 12/01/2021
  • 12/06/2021
  • Start working on Project report
  • Finalize the video game
  • Not started
  • Not started
8
  • 12/07/2021
  • 12/13/2021
  • Test the game logic
  • Check for the bug fixes
  • Update Wiki page
  • Work on project report
  • Update the GIT repo with the final code
  • Not started
  • Not started
  • Not started
  • Not started
  • Not started
9
  • 12/14/2021
  • 12/16/2021
  • Final demo
  • Update git repo with final code
  • Update the Wiki page with game demo link
  • 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.