Difference between revisions of "F20: Bubble Shooter"
Proj user7 (talk | contribs) |
Proj user7 (talk | contribs) |
||
Line 430: | Line 430: | ||
! scope="col"| Connection to SJTwo board | ! scope="col"| Connection to SJTwo board | ||
|- | |- | ||
+ | ! scope="col"| R0 | ||
! scope="col"| Pin 0.1 | ! scope="col"| Pin 0.1 | ||
− | ! scope="col"| | + | |- |
+ | ! scope="col"| G0 | ||
+ | ! scope="col"| Pin 1.1 | ||
+ | |- | ||
+ | ! scope="col"| B0 | ||
+ | ! scope="col"| Pin 1.4 | ||
+ | |- | ||
+ | ! scope="col"| R1 | ||
+ | ! scope="col"| Pin 4.28 | ||
+ | |- | ||
+ | ! scope="col"| B1 | ||
+ | ! scope="col"| Pin 0.6 | ||
+ | |- | ||
+ | ! scope="col"| G1 | ||
+ | ! scope="col"| Pin 0.8 | ||
|- | |- | ||
|} | |} |
Revision as of 14:07, 16 December 2020
Contents
Abstract
Bubble shooter is an arcade game that has bubbles or balls present on the screen. The bubbles are of different colors and the goal is to clear them by forming a group of bubbles (3 or more) of the same color. Points are earned upon clearing the bubbles and increases with the number of bubbles cleared in a single shot. The player wins upon clearing the screen and loses when the bubbles touch the bottom of the screen.
Objectives & Introduction
The objective of this project is to develop a simple, single-player 2D game using LPC 4078 microcontroller on an LED matrix display. It focuses on integrating the micro-controller peripheral drivers, led drivers, MP3 player, button and joystick controller interface and the application software in FreeRTOS. The button controller interface consists of the joystick for moving the shooter left and right. The button is used to fire the ball.
Team Members
Technical Responsibilities
|
Hisaam Hashim, Amiraj Nigam, Anirudh Ashrit, Akshat Bhutiani |
---|---|
|
Anirudh Ashrit |
|
Hisaam Hashim |
|
Hisaam Hashim, Akshat Bhutiani |
|
Amiraj Nigam, Anirudh Ashrit |
|
Akshat Bhutiani |
|
Amiraj Nigam, Hisaam Hashim |
Administrative Responsibilities
|
Hisaam Hashim |
---|---|
|
Akshat Bhutiani & Anirudh Ashrit |
|
Hisaam Hashim |
|
Amiraj Nigam & Anirudh Ashrit |
|
Akshat Bhutiani |
Schedule
Week# | Start Date | End Date | Task | Status |
---|---|---|---|---|
1 |
|
|
|
|
2 |
|
|
|
|
3 |
|
|
|
|
4 |
|
|
|
|
5 |
|
|
|
|
6 |
|
|
|
|
7 |
|
|
|
|
8 |
|
|
|
|
9 |
|
|
|
|
10 |
|
|
|
|
Bill Of Materials
Item# | Part Description | Part Model & Vendor | Quantity | Cost |
---|---|---|---|---|
1 | Microcontroller Boards | SJ2 Boards (Purchased from Preet Kang) | 1 | $50.00 |
2 | LED Matrix Display | RGB LED Matrix Panel - 32X64 | 1 | $55.00 |
3 | Audio decoder Breakout Board | MP3 PLayer Shield | 1 | $26.95 |
4 | Analog 2-axis Thumb Joystick | Analog 2-axis Joystick | 1 | $10.36 |
5 | Power Supply | 5V/3A Power Supply | 1 | $8.99 |
PCB Design
The board is designed to connect modules in the game directly. Autodesk's Eagle software is used to design the Schematics and Board layout. The board has 2 layers(Top and Bottom). JLCPCB is the manufacturer of the PCB board.
Hardware Design & Implementation
Analog Joystick
An ADA512 2-axis Analog Joystick and Button is used for controlling the movement of the launcher and shooting the ball. The data from the joystick is read using the ADC pins of the SJTwo board. The button switch is detected using a digital pin on the board.
X values & Mapping | Y values & Mapping |
---|---|
2297 (center) | 2295 (center) |
43 (left) | 45 (up) |
4095 (right) | 4090 (down) |
VS1053B MP3 Decoder Interfacing
Label | Name | Function | Pin Connection |
---|---|---|---|
1 | MP3-DREQ | Decoder Data Request | Pin 0.1 |
2 | MP3-CS | VS1053B Chip Select | Pin 0.22 |
3 | MP3-DCS | VS1053B Data CS | Pin 0.0 |
4 | MP3-RST | VS1053 Reset | Pin 0.10 |
5 | MOSI | SPI Bus (Master Output Slave Input) | Pin 0.18 |
6 | MISO | SPI Bus (Master Input Slave Output) | Pin 0.17 |
7 | SCK | SPI Clock | Pin 0.15 |
8 | +5V | +5V | PCB Vout |
9 | GND | GND | GND |
LED Matrix Interfacing
LED Matrix Pins | Connection to SJTwo board |
---|---|
R0 | Pin 0.1 |
G0 | Pin 1.1 |
B0 | Pin 1.4 |
R1 | Pin 4.28 |
B1 | Pin 0.6 |
G1 | Pin 0.8 |
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 the exact code, but you may show pseudocode and fragments of code. Keep in mind that you are showing the 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 implementations.
Testing & Technical Challenges
Describe the challenges of your project. What advice would you give yourself or someone else if your project can be started from scratch again? Make a smooth transition to the 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
This project was a fun and strenuous application of our engineering and project management skills.
After completing the driver labs during CMPE 244, we felt confident that we could develop a driver, for the Adafruit LED matrix, without using any third party libraries. We researched the hardware operations of the LED matrix and how to drive the RGB LED's. Once we could control LED's one at a time, the project evolved from an engineering problem into more of a creative exercise.
Overall I think the biggest lessons that we learned is project management based. We spent a lot of time choosing between various game designs and it forced us to start our final iteration later than we would have liked. However, we bonded together and worked hard and managed to get the game working.
Project Video
Upload a video of your project and post the link here.
Project Source Code
References
Acknowledgement
We would like to sincerely thank Professor Preetpal Kang for his allround guidance, feedback and support. His classroom lectures were significant in imparting knowledge on embedded systems. Further, we would like to thank the ISA team for their advice.