Difference between revisions of "F19: Space Impact"

Revision as of 16:10, 23 October 2019

Project Title

Space Impact - Game using FreeRTOS

Abstract

Space Impact is a classic game from the days of the Nokia era. Our objective is to design a game in which a player is prompted to protect a spaceship from incoming missiles by moving the ship up and down. The player will also have the ability to fire back at the incoming enemies. The enemy ship's movements will speed up as the game progresses, increasing the difficulty of the game.

Example Link: https://www.youtube.com/watch?v=jh49RWFnZHk

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

Nikhil Pabbisetty
Hari Haran Kura
Daniel Tsai

Schedule

Week#	Date	Task	Current Progress	Actual Completion Date
1	10/01/2019	Project Proposal Submission.	Completed	10/01/2019
2	10/15/2019	Create our own Wiki page of Space Impact. Discuss the various challenges that might come up with during the design phase and report it as top questions. Discuss what kind of components would be needed for our design.	Completed	10/15/2019
3	10/22/2019	Finalize the Bill of Materials. Place order for Hardware components. Downloading All the Software and Document(Datasheet) required for designing and field testing.	In Progress	N/A
4	10/29/2019	Delegation of tasks to each team member. Reading the 64x64 LED-Matrix datasheet. Study LED Driver Source code Found in GitHub, absorbing the content and coding our own.	In Progress	N/A
5	11/05/2019	Test LED Matrix by writing GPIO driver. Initial PCB Circuit and Design using Eagle.	In Progress	N/A
6	11/12/2019	Implement Drivers for input controls. Display the spaceship and control its movement using input buttons. Generate projectiles from the spaceship on user input.	In Progress	N/A
7	11/19/2019	Randomizer to generate enemies at random locations at end of the screen. Move the enemies towards space ship and generate enemy bullets.	In Progress	N/A
8	11/26/2019	Collision detection between 1) Spaceship and enemy (Game Over) 2) Spaceship's bullets and enemies (Kill enemies) 3) Spaceship and enemies' bullets (Reduce health of spaceship) 4) Spaceship's bullets and enemies' bullets (The bullets should cancel out each other)	In Progress	N/A
9	12/03/2019	Add Score counter and health meter.	In Progress	N/A
10	12/10/2019	Final testing and Fine-tuning.	In Progress	N/A

Parts List & Cost

S.No.	Parts	Seller	Quantity	Price
1	SJTwo Microcontroller	Preetpal Kang	1	$50
2	RGB LED Matrix Panel - 64x64	Sparkfun	1	$85
3	PCB	PCB Way	1	$10

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

Our design for LED control would base on below simplified diagram, First we need a LED Matrix controller(or GPIO Extender, for reason that we only need to signal 0/1 to turn on or turn off each unit of our Matrix), IC1, as shown in the middle of the pics, then wire the input side interface to our SJ-2 Board, using the protocol we have learned in CMPE244 course (I2C or SPI) to interfacing with the controller, telling controller which unit should be update, then after receiving command from Host side(SJ-2 Board), the controller would decide which unit of LED Matrix should be turn on or which unit should be turn off. And then we can form our LED animation base on above transmission pattern.

P.S: The diagram is for 8x8 Matrix case, so for our case, we need to find a controller with at least 128 GPIOs output pin.

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

Sourceforge Source Code Link

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.

@@ Line 147: / Line 147: @@
 === Hardware Design ===
-Our design for LED control would base on below simplified diagram, First we need a LED Matrix controller(or GPIO Extender, for we only need to signal 0/1 to turn on or turn off each unit of our Matrix), as shown in the middle of the pics, then wire the input side interface to our SJ-2 Board, using the protocol we have learned in CMPE244 course (I2C or SPI) to interfacing with the controller, then controller would decide which unit of LED Matrix should be turn on or which unit should be turn off.
+Our design for LED control would base on below simplified diagram, First we need a LED Matrix controller(or GPIO Extender, for reason that we only need to signal 0/1 to turn on or turn off each unit of our Matrix), IC1, as shown in the middle of the pics, then wire the input side interface to our SJ-2 Board, using the protocol we have learned in CMPE244 course (I2C or SPI) to interfacing with the controller, telling controller which unit should be update, then after receiving command from Host side(SJ-2 Board), the controller would decide which unit of LED Matrix should be turn on or which unit should be turn off. And then we can form our LED animation base on above transmission pattern.
 # P.S: The diagram is for 8x8 Matrix case, so for our case, we need to find a controller with at least 128 GPIOs output pin.