Brick Breaker is an embedded implementation of the classic Breakout game built on the CC3200 microcontroller. The system integrates real-time gameplay, hardware input, and cloud connectivity into a complete arcade-style experience.
This project reinforced how hardware, real-time input, and cloud services can be combined into a complete system. It strengthened my understanding of embedded design, event-driven programming, and system integration.
This project was built on top of a sequence of embedded systems labs that introduced core hardware and software concepts, which were later integrated into the final system.
These foundational components were integrated into the final system, combining hardware interfaces, real-time input handling, and cloud communication into a cohesive embedded application.
The system integrates hardware components, gameplay logic, and cloud services. The diagrams below illustrate the wiring, game flow, and overall architecture.
CC3200 connected to IR sensor, OLED display, and buzzer.
Idle → Game → Game Over → Initials → Upload → Restart.
Hardware inputs feed into gameplay logic and AWS services to power the leaderboard.
The game tracks ball position, paddle movement, and brick states. Collisions are computed using bounding logic, and bricks are stored as structured objects with HP and state.
After game over, player initials are entered via IR remote and sent to AWS using HTTP POST. Data is stored in DynamoDB and retrieved to display a leaderboard.
This demo showcases gameplay, accelerometer-based paddle control, power-ups, and leaderboard integration.
Demonstrates accelerometer input (I2C), OLED rendering (SPI), gameplay logic, and AWS leaderboard integration.
Debugging unexpected “ghost balls” and tuning PWM frequencies for audio were key challenges. Integrating AWS services and configuring permissions and CORS for leaderboard access also required careful debugging.
Repository kept private due to collaboration constraints and sensitive deployment configuration. Code snippets and implementation details are available upon request. This project was primarily designed and implemented independently, with a separate web interface developed collaboratively to display final results. Documentation includes design and implementation details as well as a bill of materials needed.