Difference between revisions of "F24: Survival Dodge"

From Embedded Systems Learning Academy
Jump to: navigation, search
(Created page with "Contents 1 Grading Criteria 2 Project Title 3 Abstract 4 Objectives & Introduction 4.1 Team Members & Responsibilities 5 Schedule 6 Parts List & Cost 7 Design & Implementation...")
 
(→‎Schedule)
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
−
Contents
+
=== Grading Criteria ===
−
1 Grading Criteria
+
<font color="green">
−
2 Project Title
+
*  How well is Software & Hardware Design described?
−
3 Abstract
+
*  How well can this report be used to reproduce this project?
−
4 Objectives & Introduction
+
*  Code Quality
−
4.1 Team Members & Responsibilities
+
*  Overall Report Quality:
−
5 Schedule
+
**  Software Block Diagrams
−
6 Parts List & Cost
+
**  Hardware Block Diagrams
−
7 Design & Implementation
+
**:  Schematic Quality
−
7.1 Hardware Design
+
**  Quality of technical challenges and solutions adopted.
−
7.2 Hardware Interface
+
</font>
−
7.3 Software Design
 
−
7.4 Implementation
 
−
8 Testing & Technical Challenges
 
−
8.1 <Bug/issue name>
 
−
9 Conclusion
 
−
9.1 Project Video
 
−
9.2 Project Source Code
 
−
10 References
 
−
10.1 Acknowledgement
 
−
10.2 References Used
 
−
10.3 Appendix
 
−
Grading Criteria
 
  
−
How well is Software & Hardware Design described?
+
== Project Title ==
−
How well can this report be used to reproduce this project?
+
Survival Dodge
−
Code Quality
 
−
Overall Report Quality:
 
−
Software Block Diagrams
 
−
Hardware Block Diagrams
 
−
Schematic Quality
 
−
Quality of technical challenges and solutions adopted.
 
  
−
Project Title
+
== Abstract ==
−
Bounce Tales
+
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.
  
−
Abstract
+
== Objectives & Introduction ==
−
Bounce Tales is a classic mobile game reminiscent of the Nokia era, featuring a bouncing character navigating through levels filled with obstacles. This project aims to recreate the game experience using the SJ-2 board and an LED matrix display. Players will control the character’s movement using buttons or a joystick, while the game will include levels, obstacles, and scoring. The implementation will focus on real-time movement, collision detection, and level progression.
+
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.
  
−
Objectives & Introduction
+
=== Team Members & Responsibilities ===
−
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.
+
*  Uday Kumar Reddy Pesala
 +
** 
 +
*  Chandra Sekhar Naidu Gorle
 +
** 
 +
*  Adi Siva Prasad Reddy Korivi
 +
**
  
−
Team Members & Responsibilities
+
== Schedule ==
−
Vaidehi
 
−
Shashank
 
−
Manvendra
 
−
Schedule
 
−
Week# Start Date End Date Task Status
 
−
1
 
−
10/12/2020
 
−
10/13/2020
 
−
10/18/2020
 
−
10/13/2020
 
−
Read previous projects, gather information and discuss among the group members.
 
−
Create GitLab repository for project
 
−
Completed
 
−
In progress
 
−
2
 
−
10/19/2020
 
−
10/20/2020
 
−
Order necessary parts
 
−
In progress
 
−
3
 
−
10/26/2020
 
−
11/01/2020
 
−
Read and familiarize with LED Matrix Datasheet
 
−
Not started
 
  
 +
{| class="wikitable"
 +
|-
 +
! scope="col"| Week#
 +
! scope="col"| Start Date
 +
! scope="col"| End Date
 +
! scope="col"| Task
 +
! scope="col"| Status
 +
|-
 +
! scope="row"| 1
 +
|
 +
* 10/20/2024
 +
* 10/27/2024
 +
|
 +
* 10/20/2024
 +
* 10/27/2024
 +
|
 +
* Read previous projects, gather information and discuss among the group members.
 +
* Create GitLab repository for project - https://gitlab.com/cmpe-240-advanced-computer-design/survival-dodge-group-8
 +
|
 +
* <span style="color:green">Completed</span>
 +
* <span style="color:orange">In progress</span>
 +
|-
 +
! scope="row"| 2
 +
|
 +
*10/27/2024 
 +
|
 +
*11/02/2024
 +
|
  
−
4
+
*Order necessary parts - LED Matrix , Speaker , Accelerometer
−
11/02/2020
+
|
−
11/08/2020
+
* <span style="color:orange">In progress</span>
−
Develop graphics driver for LED matrix and implement initial game objects
+
|-
−
Not started
+
! scope="row"| 3
−
5
+
|
−
11/09/2020
+
*11/02/2024
−
11/09/2020
+
|
−
11/09/2020
+
*11/08/2024
−
11/09/2020
+
|
−
11/10/2020
+
*Read and familiarize with LED Matrix Datasheet
−
11/15/2020
+
|
−
11/15/2020
+
* <span style="color:red">Not started</span>
−
11/15/2020
 
−
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
 
−
Not started
 
−
Not started
 
−
Not started
 
−
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/13/2020
 
−
Address bugs during testing of integrated system
 
−
Test pause/play functionality
 
−
Not started
 
−
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.
+
! scope="row"| 4
 +
|
 +
* 11/02/2020
 +
|
 +
* 11/08/2020
 +
|
 +
* Develop graphics driver for LED matrix and implement initial game objects
 +
|
 +
* <span style="color:red">Not started</span>
 +
|-
 +
! scope="row"| 5
 +
|
 +
*11/09/2020
 +
*11/09/2020
 +
*11/09/2020
 +
*11/09/2020
 +
|
 +
*11/10/2020
 +
*11/15/2020
 +
*11/15/2020
 +
*11/15/2020
 +
|
 +
* 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
 +
|
 +
* <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>
 +
|-
 +
! scope="row"| 6
 +
|
 +
*11/16/2020
 +
|
 +
*11/22/2020
 +
|
 +
*Integration of circuit boards and microcontroller
 +
* Game logic development
 +
* Testing and debugging the game logic
 +
|
 +
* <span style="color:red">Not started</span>
 +
* <span style="color:red">Not started</span>
 +
* <span style="color:red">Not started</span>
 +
|-
 +
! scope="row"| 7
 +
|
 +
* 11/23/2020
  
−
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.
+
* 11/29/2020
 +
|
 +
* Integrate game logic code with LED matrix
 +
* Integrate game sounds with game logic
 +
|
 +
* <span style="color:red">Not started</span>
 +
* <span style="color:red">Not started</span>
 +
|-
 +
! scope="row"| 8
 +
|
 +
* 11/30/2020
 +
|
 +
* 12/06/2020
 +
|
  
−
Hardware Design
+
* Integrate subsystem
−
Discuss your hardware design here. Show detailed schematics, and the interface here.
+
* Finalizing the video game
 +
* Update the wiki page.
 +
|
 +
* <span style="color:red">Not started</span>
 +
* <span style="color:red">Not started</span>
 +
* <span style="color:red">Not started</span>
 +
|-
 +
! scope="row"| 9
 +
|
 +
* 12/07/2020
 +
|
 +
* 12/13/2020
 +
|
 +
* Address bugs during testing of integrated system
 +
* 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>
 +
|-
 +
! scope="row"| 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
 +
|
  
−
Hardware Interface
+
*Final Demo
−
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.
+
*Update Gitlab repo with final code.
 +
*Update test video.
 +
*Update the wiki page.
 +
|
 +
* <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>
 +
|-
 +
|}
  
−
Software Design
+
<HR>
−
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.
+
<BR/>
  
−
Implementation
+
== Parts List & Cost ==
−
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.
+
Give a simple list of the cost of your project broken down by components. Do not write long stories here.
  
−
Testing & Technical Challenges
+
== Design & Implementation ==
−
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.
+
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:
 
Include sub-sections that list out a problem and solution, such as:
  
−
<Bug/issue name>
+
=== <Bug/issue name> ===
 
Discuss the issue and resolution.
 
Discuss the issue and resolution.
  
−
Conclusion
+
== 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?
+
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
+
=== Project Video ===
 
Upload a video of your project and post the link here.
 
Upload a video of your project and post the link here.
  
−
Project Source Code
+
=== Project Source Code ===
−
Sourceforge Source Code Link
+
*  [https://sourceforge.net/projects/sjsu/files/CmpE_S2016/ Sourceforge Source Code Link]
−
References
+
 
−
Acknowledgement
+
== References ==
 +
=== Acknowledgement ===
 
Any acknowledgement that you may wish to provide can be included here.
 
Any acknowledgement that you may wish to provide can be included here.
  
−
References Used
+
=== References Used ===
 
List any references used in project.
 
List any references used in project.
  
−
Appendix
+
=== Appendix ===
 
You can list the references you used.
 
You can list the references you used.

Latest revision as of 21:06, 3 November 2024

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# Start Date End Date Task Status
1
  • 10/20/2024
  • 10/27/2024
  • 10/20/2024
  • 10/27/2024
  • Completed
  • In progress
2
  • 10/27/2024
  • 11/02/2024
  • Order necessary parts - LED Matrix , Speaker , Accelerometer
  • In progress
3
  • 11/02/2024
  • 11/08/2024
  • Read and familiarize with LED Matrix Datasheet
  • Not started


4
  • 11/02/2020
  • 11/08/2020
  • Develop graphics driver for LED matrix and implement initial game objects
  • Not started
5
  • 11/09/2020
  • 11/09/2020
  • 11/09/2020
  • 11/09/2020
  • 11/10/2020
  • 11/15/2020
  • 11/15/2020
  • 11/15/2020
  • 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
  • Not started
  • Not started
  • Not started
  • 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/13/2020
  • Address bugs during testing of integrated system
  • Test pause/play functionality
  • Not started
  • 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.

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