Difference between revisions of "ECE434 Spotify Box"

From eLinux.org
Jump to: navigation, search
Line 44: Line 44:
== Packaging ==
== Packaging ==
Packaging not really possible as wifi dongle didn't work with spotify
Packaging not really possible as wifi dongle didn't work with spotify
[[File:SpotifyBoxFritzing.PNG|thumb|Spotify Box Fritzing Design]]
== Installation Instructions ==
== Installation Instructions ==

Revision as of 18:06, 17 November 2020

thumb‎ Embedded Linux Class by Mark A. Yoder

Team members: Aman Bajaj and Eric Kirby

Grading Template

I'm using the following template to grade. Each slot is 10 points. 0 = Missing, 5=OK, 10=Wow!

09 Executive Summary
09 Packaging
09 Installation Instructions 
09 User Instructions
09 Highlights
09 Theory of Operation
09 Work Breakdown
09 Future Work/Conclusions
09 Hackster.io
09 Demo/Poster
00 Late
Comments: Have a good day.

Score:  90/100

(Inline Comment)

Executive Summary

This project is making a device using the Beaglebone which can stream music through spotify. The final result displays a mopidy interface on an LCD screen that can be controlled using buttons as GPIO into the Beaglebone. This is done using Mopidy, specifically the Mopidy-spotify, Mopidy-touchscreen and Mopidy-GPIO extensions. In order to adapt the existing code to our project, we created our own mopidy extension and tailored the code so that it works the way we want it to. The output audio is controlled using PulseAudio and comes out from the USB port through a USB-AUX adapter.


  • 10/29 - Order Parts
  • 11/3 - Receive Parts
  • 11/5 - Install necessary packages on Bone
  • 11/6 - Play music from Spotify
  • 11/9 - Display Pygame on the LCD
  • 11/13 - Create an interface for the LCD
  • 11/18 - Finish documentation


Packaging not really possible as wifi dongle didn't work with spotify

Spotify Box Fritzing Design

Installation Instructions

Give step by step instructions on how to install your project.

  • Include your github path as a link like this to the read-only git site: https://github.com/MarkAYoder/gitLearn.
  • Be sure your README.md is includes an up-to-date and clear description of your project so that someone who comes across you git repository can quickly learn what you did and how they can reproduce it.
  • Include a Makefile for your code if using C.
  • Include any additional packages installed via apt. Include install.sh and setup.sh files.
  • Include kernel mods.
  • If there is extra hardware needed, include links to where it can be obtained.

User Instructions

Once everything is installed, how do you use the program? Give details here, so if you have a long user manual, link to it here.

Consider making it autostart for full credit.


Here is where you brag about what your project can do.

Include a YouTube demo the audio description.

Theory of Operation

Give a high level overview of the structure of your software. Are you using GStreamer? Show a diagram of the pipeline. Are you running multiple tasks? Show what they do and how they interact.

Work Breakdown

List the major tasks in your project and who did what.

Also list here what doesn't work yet and when you think it will be finished and who is finishing it.

Future Work

Suggest addition things that could be done with this project.


Give some concluding thoughts about the project. Suggest some future additions that could make it even more interesting.

thumb‎ Embedded Linux Class by Mark A. Yoder