CSEE 4840 Embedded System Design Spring 2015 |
Class meets Tuesdays and Thursdays, 2:40 - 3:55 PM in 602 Hamilton.
Mudd 1235 is the lab, which is filled with Linux workstations and FPGA boards. Registered students will receive accounts on these machines and 24-hour badge access to this room.
Do the labs in pairs. Project groups should be three students or more.
Name | Office hours | Location | |
---|---|---|---|
Prof. Stephen A. Edwards | sedwards@cs.columbia.edu | By appt. | 462 CSB or 1235 Mudd |
Richard Townsend | rtownsend@cs.columbia.edu | T 12-2 | 1235 Mudd |
Lianne Lairmore | lairmore@cs.columbia.edu | Th 12-2 | 1235 Mudd |
Kuangya Zhai | kyzhai@cs.columbia.edu | W 2-4 | 1235 Mudd |
Kaiwei Zhang | kz2229@columbia.edu | M 2-4 | 1235 Mudd |
Prerequisites: ELEN E3910 or COMS W3843 or the equivalent. Embedded system architecture and programming. I/O, analog and digital interfacing, and peripherals. Weekly laboratory sessions and term project on design of a microprocessor-based embedded system including at least one custom peripheral. Knowledge of C programming and digital logic required. Lab required.
The goal of this class is to introduce you to issues in hardware/software interfacing, practical microprocessor-based system design issues such as bus protocols and device drivers, and practical digital hardware design using modern logic synthesis tools. You will put all of this to use in the lab where you will be given the opportunity to implement, using a combination of C and the SystemVerilog hardware description langauge, a small embedded system.
This is a lab course done in two parts. During the first part of the class, each student will implement the same "canned" designs designed by the instructor and be given substantial guidance. These are meant as an opportunity for you to learn the development tools and basic concepts. In the second part of the class, you will divide up into teams and each will design and implement a comparable project of their own with guidance from the instructor and TAs.
This course is a capstone in which students will integrate their knowledge of digital logic, programming, and system design to produce a real system. It is intended to complement ELEN 4340, Computer Hardware Design. 4840 focuses more on system-design issues and include a large section on hardware/software integration. Students in 4840 will use gates, processors, peripherals, software, and operating systems as building blocks.
CSEE 3827, Fundamentals of Computer Systems or the equivalent. You must understand digital logic design. Prior experience with hardware description languages, FPGAs, or embedded processors is not required.
COMS 3157, Advanced Programming or the equivalent. Specifically, C programming experience. While 4840 will teach you advanced aspects of embedded C programming, you need to come in with significant C experience.
COMS W4823, Advanced Digital Logic Design. While not a formal prerequisite, you are strongly encouraged to take it. In it, you will learn advanced logic design and HDL coding, both of which are crucial to success in 4840.
You'll perform a design-it-yourself project in the second half of the class. There are five deliverables for the project:
Project groups should be three students or more.
This is a critical part of the project and will be a substantial fraction of the grade.
Include the following sections:
Include all of this in a single .pdf file (don't print it out) and email it to me on the due date.
Also create a .tar.gz file (see the online documentation for the `tar' program to see how to create such a file. Briefly, create a file called `myfile' with the names of all the files you want to include in the archive and run tar zcf project.tar.gz `cat myfiles` to create the archive.) that just includes the files necessary to build your project, such as I did for the labs. Also email this to me by the due date.
BlazePPS:
Blaze Packet Processing System (Stephen) Proposal Design Report Presentation Files Christopher Campbell, Sheng Qian, Valeh Valiollahpour Amiri, and Yuanpei Zhang |
EmbeddedSpikeSorter:
Spike sorter: classifying brain activity (Lianne) Proposal Design Report Presentation Files Zhewei Jiang and Jamis Johnson |
Eskimo-Farm:
Side-Scrolling Shoot-em-up (Richard) Proposal Design Report Presentation Files Shruti Ramesh, Prachi Shukla, and Miguel Yanez |
Flappy-Bird:
That Game on an FPGA (Richard) Proposal Design Report Presentation Files YenHsi Lin, Junhui Zhang, Gaoyuan Zhang, and Wei Zheng |
HFT2:
High-speed trading algorithm (Stephen) Proposal Design Report Presentation Files Nathan Abrams, Alexander Gazman, and Hang Guan |
Labyrinth:
Dijkstra's Shortest Path in Hardware (Stephen) Proposal Design Report Presentation Files Michelle Andrade Valente da Silva, Ariel Faria, Utkarsh Gupta, and Veton Saliu |
PLazeR:
Planar Laser Rangefinder (Lianne) Proposal Design Report Presentation Files Xingzhou He, Peiqian Li, MinhTrang Nguyen, and Robert Ying |
PSHFT:
Pocket-Sized High Frequency Trader (Stephen) Proposal Design Report Presentation Files DavidNaveenDh Arthur, Gabriel Blanco Cabassa, Brian Bourn, and Suchith Vasudevan |
RSAB:
RSA Cryptographic Accelerator (Kuangya) Proposal Design Report Presentation Files Adam Incera, Jaykar Nayeck, Emilia Pakulski, and Noah Stebbins |
Smile:
Genetic Algorithm on an FPGA (Kaiwei) Proposal Design Report Presentation Files Jian Jiao, Jihua Li, Wenbei Yu, and Yini Zhou |
TYRION:
Singular Value Decomposition Accelerator (Kuangya) Proposal Design Report Presentation Files E. Jubb and Ruchir Khaitan |
Tank:
Battle City Game (Richard) Proposal Design Han Cui and James Thompson |
battlecity:
Battle City Game Report Files Li Qi |
breakout:
Simple Brick Breaker Game (Kuangya) Proposal Design Report Presentation Files Wanding Li, Mingrui Liu, Fengyi Song, and Junchao Zhang |
racing:
Car Racing Game (Lianne) Proposal Design Report Presentation Files Mingxin Huo, Yifan Li, Jing Shi, and Siwei Su |
My favorites
Mark Zwolinski. |
James K. Peckol. |
Grading | 30% Labs |
10% Milestone 1 | |
15% Milestone 2 | |
20% Milestone 3 | |
25% Final Report and presentation | |
Late Policy | Zero credit for anything handed in after it is due without explicit approval of the instructor. |
Collaboration Policy | Work in pairs on the labs. You may consult others, but do not copy files or data. You may collaborate with anybody on the project, but must cite sources if you use code. |