120 likes | 228 Views
Embedded Systems Design. Summer 1 2013. Instructor Info. Instructor: George Rudolph Office Hours: T,Th ½ hour before class Contact 225 Thompson Hall george.rudolph@citadel.edu 953-5032. Course Overview. In-class activities 3 projects 1 Exam 1 Final Some Homework. Goals.
E N D
Embedded Systems Design Summer 1 2013
Instructor Info • Instructor: George Rudolph • Office Hours: T,Th ½ hour before class • Contact • 225 Thompson Hall • george.rudolph@citadel.edu • 953-5032
Course Overview • In-class activities • 3 projects • 1 Exam • 1 Final • Some Homework Instructor: George Rudolph, Summer 2006
Goals Give you skills, concepts and information that will • Make you a better engineer • Add to your value as an employee • Light your fire Education is not the filling of a pail, but the lighting of a fire. William Butler Yeats Instructor: George Rudolph, Summer 2006
Goals • Learn tools • Can use them, not an expert • Primary focus is software development • Learn Embedded Systems Concepts • Deal Intelligently with Concepts/Issues • Generalize skills learned in this course • Hands-on fun • Get close to modern hardware • Real-time Java programming • Build with Legos Instructor: George Rudolph, Summer 2006
Course Mechanics • Course is project-driven • Work in teams • Activities and Lectures will be interleaved during class • Minimize time spent outside class on projects • Testable Material • Questions from Lectures • Variations from • Tutorials • Papers Instructor: George Rudolph, Summer 2006
“ Housekeeping lssues” • CitLearn logins • CWID • Password • Call helpdesk if you have issues • Used for • Grades • Exams • submissions Instructor: George Rudolph, Summer 2006
Successful ES Programmer Practices (Know & Do) • Hardware Architecture • Core hardware (processor/controller) • Peripherals (what is being controlled) • Tools & Toolchains • Real-time embedded programming • Good concepts, techniques, habits Instructor: George Rudolph, Summer 2006
Assessment Activity What is your experience with • Hardware (alot, some, none) • Windows or Linux OS (alot, some, none) • Other OS (alot, some, none) • Programming (a lot, some, none) • Java (alot, some, none) • Embedded Systems (a lot, some, none) Instructor: George Rudolph, Summer 2006
Why Use Legos? • Popular • Readily available • No soldering required • Quickly experiment with alternate physical designs • Mindstorms, Technics, etc. are easy to program Instructor: George Rudolph, Summer 2006
Why High-level Language? • Fewer bugs by design • Productivity b/c of library support • Abstractions • Use if you can • Dive lower if you need to • Optimize with care • Profile first Instructor: George Rudolph, Summer 2013
Why Choose Java? • See http://www.practicalembeddedjava.com/WhyJava.html • Lejos NXJ is a *really* nice tool with Libraries for programming Lego robots/devices • Java runs on millions of devices now Instructor: George Rudolph, Summer 2006