F24: Survival Dodge

From Embedded Systems Learning Academy
Revision as of 23:14, 19 December 2024 by Proj user10 (talk | contribs) (→‎Design & Implementation)

Jump to: navigation, search

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

Survival Dodge

Abstract

Survival Dodge is a classic arcade-style game focused on quick reflexes and survival, reminiscent of retro gaming experiences. This project aims to recreate the intense and fast-paced gameplay using the SJ-2 board and an LED matrix display. In this game, players control a character (or an object) that must dodge incoming obstacles from multiple directions, with the speed and frequency of obstacles increasing over time. The objective is to survive as long as possible, setting high scores based on survival time. Players will use buttons or a joystick to maneuver, with core implementation focusing on responsive controls, real-time collision detection, and adaptive difficulty for sustained challenge.

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

  • Uday Kumar Reddy Pesala
  • Chandra Sekhar Naidu Gorle
  • Adi Siva Prasad Reddy Korivi

Schedule

Week# Date Task Status
1 10/14
2 10/21
  • To assign roles and responsibilities to each team member.
  • To decide the structure of the team and divide the project into different modules.
  • To finalize the deadlines and deliverables for the project.
  • Assigned roles and responsibilities to each member.
  • Created a test plan with tasks, deadlines and deliverables assigned to it.
3 10/28
  • To start designing the Master module which will take inputs from different players, take a decision and sends it to LED Matrix display.
  • Divided the project into different modules like Master, Player, Wireless, LED Display and Testing.
  • Started designing the Master module to take inputs from Players.
4 11/04
  • To understand the connections, read the datasheet for RGB LED Matrix.
  • Made a basic layout, pin connections, power requirements for 64x64 RGB LED Matrix.
5 11/11
  • Adding logic to test LED Matrix Functionality.
6 11/18
  • To test the Player and Master modules.
  • To understand addressing mode, latching, and clock functionality for RGB LED Matrix.
7 11/25
  • Adding Start page, end page and player score for the game.
8 12/02
  • To send and receive data between Player and Master.
  • To write the logic to glow a particular LED on the display matrix.
9 12/09
  • To implement RGB LED Matrix tasks and APIs for the Master module.
  • To integrate the layout of the application (UI, border, car design, obstacle design) to Master Module.
  • To generate random obstacles, score logic and implement other game functionalities (eg: game over scenario).
10 12/16
  • To keep moving the display down continuously for the obstacles.
  • To test the overall functionality of the project.
11 12/18
  • To Integration of all modules and end to end testing.
  • To fix bugs and optimize the code.
12 12/18
  • Adding extra functionalities and extra features for the project.
  • Test the extra features with overall project requirement.

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

LED Matrix Display:

The 64 x 64 LED matrix contains a total of 4096 pixels, with each pixel having 3 channels for red, green, and blue colors. Each group of 32 rows of the display is addressable by using a 5:32 decoder, where each 5-bit address actually selects 2 rows of the 64 x 64 display at a time. Therefore, the display can be considered to be split in two halves -- the upper display containing rows 0 to 31, and the lower half display comprised of rows 32 through 64. To turn each LED on, a HIGH must be asserted on the respective RGB pins and clocked into the respective bit of the 64-bit shift registers, where each bit position is relative to the 64 columns of the display. Since the display is split into two halves, pins R1, G1, and B2 control the color output for the upper display while pins R2, G2, and B2 control the output for the lower half of the matrix.

Momentary Press Buttons

For user input we used Weideer 16mm Push buttons that we found on Amazon. The buttons were tactile and had a amount of switch travel. Each button had two terminals. We connected one terminal of each button to three different GPIO pins on the SJ2 Board to receive input signals. The other terminal was connected to the 3.3V Vcc on the SJ2. Therefore, we enabled pull-down resistors in software for the switches to have no floating input when inactive.

Buttons.jpg



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.

Retrieved from "http://socialledge.com/sjsu/index.php?title=F24:_Survival_Dodge&oldid=72770"