Difference between revisions of "F22: Embedded Gamers"
(→Implementation) |
(→Technical Responsibilities) |
||
Line 24: | Line 24: | ||
{| class="wikitable" style="margin-left: 0px; margin-right: auto;" | {| class="wikitable" style="margin-left: 0px; margin-right: auto;" | ||
|- style="vertical-align: top;" | |- style="vertical-align: top;" | ||
− | ! colspan="5"| | + | ! colspan="5"| Technical Roles |
|- | |- | ||
! style="text-align: left;" | | ! style="text-align: left;" | | ||
Line 40: | Line 40: | ||
! style="text-align: left;" | | ! style="text-align: left;" | | ||
* MP3 Decoder | * MP3 Decoder | ||
− | | | + | | Phil Bloxom |
|- | |- | ||
! style="text-align: left;" | | ! style="text-align: left;" | | ||
* Enclosure | * Enclosure | ||
− | | | + | | Phil Bloxom |
|- | |- | ||
! style="text-align: left;" | | ! style="text-align: left;" | |
Revision as of 02:12, 23 November 2022
Contents
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
Guardians of the Galaxy
Abstract
A horizontal type of space invader game. Players can control the spaceship on the screen composed of an LED matrix in a rectangular shape. The spaceship can shoot horizontally from left to right in order to destroy its enemies. The entire map will flow in the opposite direction of where the spaceship is flying. The speed of the map flow and the number of enemies will increase at higher difficulty levels. The spaceship takes damage from colliding with enemies themselves or their bullets. The game will end when the health of the controlled spaceship is depleted.
Objectives & Introduction
Technical Responsibilities
Technical Roles | ||||
---|---|---|---|---|
|
Bruce Jiang | |||
|
Bruce Jiang | |||
|
Ritu Patil | |||
|
Phil Bloxom | |||
|
Phil Bloxom | |||
|
Bruce Jiang & Phil Bloxom |
Administrative Responsibilities
Administrative Roles | ||||
---|---|---|---|---|
|
Ritu Patil | |||
|
Bruce Jiang | |||
|
Phil Bloxom | |||
|
Bruce Jiang | |||
|
Ritu Patil |
Schedule
Week# | Start Date | End Date | Task | Status |
---|---|---|---|---|
1 |
|
|
|
|
2 |
|
|
|
|
3 |
|
|
|
|
4 |
|
|
|
|
5 |
|
|
|
|
6 |
|
|
|
|
7 |
|
|
|
|
8 |
|
|
|
|
9 |
|
|
|
|
10 |
|
|
|
|
Bill of Materials (General Parts)
Part Name | Part Model & Source | Quantity | Cost Per Unit (USD) |
---|---|---|---|
|
|
|
|
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
|
Overall Design
Hardware Design
Hardware Interface
- LED Matrix Display: 13 GPIO channel on SJ2 (1)
- Joystick connection: 2 ADC channel on SJ2 (1)
- Bluetooth sender connection: 1 set UART, RX and TX on SJ2 (1)
- Bluetooth receiver connection: 1 set UART, RX and TX on SJ2 (2)
- MP3 Decoder connection: SPI communication, MOSI, CS, SCK, on SJ2 (2)
- Speaker connection: AUX cord
Software Design
- LED Matrix:
- 1. Initialized LED matrix connected pins to board IOs.
- 2. Designed matrix driver for screen display by reading an matrix.
- Joystick:
- 1. Initialized 2 ADC channels for taking the x reading and y reading from joystick.
- 2. Decoded voltage readings into joystick movement commands.
- Buttons:
- 1. Initialized several gpio for taking binary command from button pressed.
- 2. Enabled interrupts for each botton pressed.
Implementation
- LED Matrix driver functions:
- 1. display_update: reload matrix display for refreshing the changes from the backend matrix.
- 2. display_clear: erase all matrix values, and sets them to zeros.
- 3. overwrite_pattern_to_screen: overite a given pattern onto the existing matrix
- 4. append_pattern_to_screen: append a given pattern onto the existing matrix
- 5. clear_pattern_on_screen: clear the pattern from screen by giving the pattern's current location and width and height.
- Joystick driver:
- 1. joystick_running: run ADC capture on joystick continuesly to monitor user inputs.
- Buttons driver:
- 1. Button 1: starts a game.
- 2. Button 2: ends existing game.
- 3. Button 3: shuts out bullet.
RGB LED Matrix
Hardware Design
Below are symbol and footprint for custom component-part in EasyEDA tool. These parts would be used in future PCB design.
Hardware Interface
The 32x64 LED matrix is from Adafruit, with user mannual. It is composed of two upper and lower sectional LED pannels. Each pannel has R, G, B led channels and A, B, C, and D row control registers. Addtionally, column shift is controlled by Latch bit, clock is controled by CLK, and OE turns LED off when switching rows.
Connectivity Table LED Matrix to Sj2 Board:
|
Software Design
LED matrix io and driver is developed for communication between boards and LED matrix. IO driver consists of pin inialization by using gpio.h for each rgb channels, row selection register, CLK, LAT, and OE pins. By using "led_matrix_io.h" developers can using public function led_matrix_io_init and other basic controller functions.
For LED matrix driver, it is based on the previous IO driver to provide LED screen update, clean, init, and draw functionalities.
Implementation
Rtos Tasks:
- Updating Display: for display to continuously updating screen, a task is assigned for running the display_update function from the driver every 500 milliseconds.
Joystick and Buttons
Hardware Design
Hardware Interface
Connectivity Table LED Matrix to Sj2 Board:
|
Software Design
Joystick with voltage input produces two analog channels of outputs from the x and y axises of the joystick. Designed a driver to convert these two analog outputs and convert them into digital signals, then decoded as user movment such as move up, move down, move left, move right, move right up, move right down, move left up, and move left down.
Implementation
Rtos Tasks:
- JoyStick Running: Keep recieving two channels of analog signals and decode them into agent moves corresponding to right, left, up, down, right up, right left, left up, and left down.
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.