Difference between revisions of "F22: Thunder Flash"

From Embedded Systems Learning Academy
Jump to: navigation, search
Line 52: Line 52:
  
 
<br>
 
<br>
 +
 +
== '''Administrative Responsibilities''' ==
 +
{| class="wikitable" style="margin-left: 0px; margin-right: auto;"
 +
|- style="vertical-align: top;"
 +
! colspan="5" style="background:#588ecc" | <span style="color:#FFFFFF"> Administrative Roles </span>
 +
|-
 +
! style="text-align: left;" | 
 +
* <span style="color:#000000">Finance Manager</span>
 +
|<font color="black"> Noel Smith </font>
 +
|-
 +
! style="text-align: left;" |
 +
* <span style="color:#000000">Git Repository Manager </span>
 +
|<font color="black"> Pinky Mathew </font>
 +
|-
 +
! style="text-align: left;" |
 +
* <span style="color:#000000">Wiki Report Manager </span>
 +
|<font color="black"> Shreya Kulkarni </font>
 +
|-
 +
! style="text-align: left;" |
 +
* <span style="color:#000000">Bill of Materials Manager </span>
 +
|<font color="black"> Pushkar Deodhar </font>
 +
|}
  
 
    
 
    

Revision as of 04:06, 6 November 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

Bow and Arrow

Abstract

Bow and arrow is a fun, aiming archery game that we Millennials all played during our childhood. Our goal is to produce a similar version of ‘Bow and Arrow’ where the archer aims the arrow at the targets (balloons) using the bow. The game would have different levels and the archer would get 3 lives to score maximum points. As the level increases the challenges and speed of the game increase. In the later levels, there would be monsters coming onto the archer. In the later levels, there would be monsters coming onto the archer, and the archer should make sure he dodges those obstacles to save his life and hit the balloons to earn points. This is all displayed on the LED matrix acting as the screen.

Objectives & Introduction

The main objective of this project was to create the “Bow and Arrow” video game displayed on a 64X64 RGB LED matrix, with one SJ2 board as a graphics processor/matrix controller, and another SJ2 board as a controller. Other objectives are the following:

  • Design custom PCBs for both the gamepad and matrix controller SJ2 boards.
  • Use the FreeRTOS Real-Time Operating System on both SJ2 boards.
  • Establish UART communications through Xbee between the two SJ-Two Microcontrollers.
  • Create simple coding logic for displaying required characters and game objects.
  • Add background music to the game to enhance the gameplay experience.


Team Members & Technical Responsibilities

  • Shreya Kulkarni
    • Integrating of Graphics Driver
    • Game logic design
    • Joystick and button Implementation
  • Pinky Mathew
    • Interfacing of LED Matrix and driver design
    • Game logic design
    • Joystick and button Implementation
  • Pushkar Deodhar
    • Zigbee module
    • Integrating MP3 module with the Game
    • Hardware Designing & PCB Integration
  • Noel Smith
    • MP3 Audio Encoder/Decoder
    • Integrating MP3 player with the Game
    • Hardware Designing & PCB Integration


Administrative Responsibilities

Administrative Roles
  • Finance Manager
Noel Smith
  • Git Repository Manager
Pinky Mathew
  • Wiki Report Manager
Shreya Kulkarni
  • Bill of Materials Manager
Pushkar Deodhar


Schedule

Week# Start Date End Date Task Status
1
  • 10/16/2022
  • 10/23/2022
  • Analyze previous projects, gather information, and discussion among the group members.
  • Discuss and source parts for the game. Start ordering parts. Create a GitLab repository.
  • In progress
2
  • 10/24/2022
  • 10/29/2022
  • Discuss and plan down the project into modules and assign responsibilities
  • Familiarize with relevant hardware datasheets
  • Not started
3
  • 10/30/2022
  • 11/05/2022
  • Develop drivers for the hardware required in the project
  • Develop a driver for LED display
  • Not started


4
  • 11/06/2022
  • 11/12/2022
  • Continue developing drivers
  • Read and familiarize with LED Matrix Datasheet.
  • Read and familiarize with MP3 Decoder Datasheet.
  • Not started
5
  • 11/13/2022
  • 11/19/2022
  • Finalize wiki schedule
  • Order circuit boards components and complete the design for printing
  • circuit board and component assembly
  • Circuit board testing
  • Additional accessories if required and finalization of hardware
  • Start developing game logic
  • Not started
  • Not started
  • Not started
  • Not started
  • Not started
6
  • 11/20/2022
  • 11/23/2022
  • Integration of circuit boards and microcontroller
  • Continue game logic development
  • Testing and debugging the game logic
  • Not started
  • Not started
  • Not started
7
  • 11/27/2022
  • 12/03/2022
  • Integrate game logic code with LED matrix
  • Integrate game sounds with game logic
  • Not started
  • Not started
8
  • 12/04/2022
  • 12/10/2022
  • Integrate subsystem
  • Finalizing the video game
  • Update the wiki page.
  • Not started
  • Not started
  • Not started
9
  • 12/07/2022
  • 12/13/2022
  • Address bugs during testing of integrated system
  • Test pause/play functionality
  • Not started
  • Not started
  • Not started
10
  • 12/14/2022
  • 12/15/2022
  • 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.