This Wiki is about a college-level embedded processor class being taught using the BeagleBoard. It's being taught by Professor Mark A. Yoder in the [http://ece-1.rose-hulman.edu/ecemm/ Electrical and Computer Engineering Department] at [http://www.rose-hulman.edu Rose-Hulman Institute of Technology]. Rose is a small, private, undergraduate engineering school that focuses on undergraduate education.

+

−

A major part of the class is learning how to work with and leverage off of the open source community. The course requires a major project which will either significantly contribute and an existing open source project, or launch a new one.

+

=== Introduction ===

+

+

This Wiki is about a college-level embedded processor class being taught using the BeagleBoard. It's being taught by Professor Mark A. Yoder in the [http://www.rose-hulman.edu/academics/academic-departments/electrical-computer-engineering.aspx Electrical and Computer Engineering Department] at [http://www.rose-hulman.edu Rose-Hulman Institute of Technology]. Rose is a small, private, undergraduate engineering school that focuses on undergraduate education.

+

+

A major part of the class is learning how to work with and leverage off of the open source community. The course requires a major project which will either significantly contribute to an existing open source project, or launch a new one.

If you teach a similar course, I'd like to hear from you. [[ECE497 Instructor Guide]] explains the various choices I made in what to cover in the course, which distribution to use, etc.

If you teach a similar course, I'd like to hear from you. [[ECE497 Instructor Guide]] explains the various choices I made in what to cover in the course, which distribution to use, etc.

+

+

Here ([[:Category:ECE497]]) is a list of all the pages I've posted on eLinux for this class. Take a look at it.

Brief introduction to Linux on a 32-bit embedded processor. Detailed study of what happens from power up the fully running X-Windows. Adapting Linux to a given application including: boot time reduction, power management and root filesystem support. Streaming media on an embedded processor. Using a DSP co-processor to improve performance. Design project. Previous Linux experience not required, but helpful. C programming, operating system and hardware experience required.

+

* Brief introduction to Linux on a 32-bit embedded processor.

+

* Detailed study of what happens from power up to fully running X-Windows.

+

* Adapting Linux to a given application including: boot time reduction, power management and root filesystem support.

This is dynamic course, so the calendar may change as we discover interesting new things. It will be updated as we go. You can see it here: [[ECE497 Calendar and Exercises]]

+

This is a dynamic course, so the calendar may change as we discover interesting new things. It will be updated as we go. You can see it here: [https://docs.google.com/document/d/1SJL2_0Fc8yXHZZ3AVWREOHfK7jfidzBHG-lVuYfif9k/edit#heading=h.mud7eogux2sr ECE497 Calendar and Exercises]

−

+

−

There are many things you will have to do to get your computer set up, etc. [[ECE497 Calendar and Exercises]] also gives the step-by-step details along with due dates.

+

=== Textbook ===

=== Textbook ===

−

We'll be using the text [http://books.google.com/books?id=1U5yQAAACAAJ&source=gbs_book_other_versions Embedded Linux Primer], by ''Christopher Hallinan'', 2<sup>nd</sup> edition, published by Pearson Prentice Hall.

+

We'll be using the text [http://www.amazon.com/Embedded-Linux-Primer-Practical-Real-World/dp/0137017839 Embedded Linux Primer], by ''Christopher Hallinan'', 2<sup>nd</sup> edition, published by Pearson Prentice Hall.

−

The text is not Beagle specific, rather it pulls examples from many embedded processors. It has many listings which detail the outputs from various processors. One of your tasks will be to reproduce the listing for the BeagleBoard.

+

The text is not Beagle specific; rather, it pulls examples from many embedded processors. It has many listings which detail the outputs from various processors. One of your tasks will be to reproduce the listing for the BeagleBoard.

=== Grades ===

=== Grades ===

−

Grades in the class aren't based on the traditional homework and exams, rather, they are based some daily exercises [[ECE497 Calendar and Exercises]], a couple of minor projects and a major Beagle-based project and your portfolio. The projecst will be done with teams of 2 or 3 people. We have people in the class with strong embedded backgrounds and others with strong Linux background. The goal is to have teams include complementary skills.

+

Grades in the class aren't based on the traditional homework and exams; rather, they are based on some weekly memos reporting the daily exercises [[ECE497 Calendar and Exercises]], weekly homework and a major Beagle-based project. The projects will be done with teams of 2 or 3 people. We have people in the class with strong embedded backgrounds and others with strong Linux background. The goal is to have teams include complementary skills.

−

+

−

Your portfolio is a collection of what you, as an individual, have contributed to the community and the team.

The Calendar gives the due dates. I'll give a 10% reward to being early and 10% per day penalty for being late. You must complete all the labs to pass the course.

+

The Calendar gives the due dates. I'll give a reward to being early and 10% per day penalty for being late. You must complete all the exercises to pass the course.

+

+

=== Weekly Status Memos ===

+

+

A Weekly Status Memo is due on Monday of each week. See [[ECE497_Weekly_Status_Memos]] for details.

+

+

=== D114 Lab ===

+

Solid sole footwear must be worn at all times while in the lab for any reason. Glove or finger footwear is not considered as closed toe or solid sole and thus is not permitted at anytime within the lab.

+

+

Additionally, closed toe, solid sole footwear must be worn within 4 ft. of the lab benches. No loose fitting clothing (e.g. ties, scarfs, long necklaces) are allowed within 4 ft. of the lab benches. Long hair must be tied such that it is not loose or hanging in such a way that it could potentially get caught in the moving equipment when within 4 ft. of the lab benches.

+

No food or drinks are permitted within 4 feet of any lab bench. Food and drinks are allowed to be placed on the front table and tables in center of room. Anyone with drinks and/or food stuffs must remove or dispose of the material at the conclusion of their lab period(s). Food and/or drinks contained in backpacks and/or closed or sealed containers/packages may be kept on the floor during the lecture/lab period but MAY NOT be opened or consumed within 4 ft. of lab benches, food and drinks allowed on front table and tables in center of room.

Lab usage permitted testing available between 8:00 AM and 5:10 PM Monday through Friday. Lab usage at other times must be approved in writing by the ECE department chair or ECE department faculty member.

−

== Links ==

+

At least two students must be present within the lab at anytime lab equipment is being used or testing is being conducted. Devices, circuits, systems under test may NOT be left unattended unless all test equipment has been turned off. Any material left unattended in the lab is done so at the individuals own risk. The ECE department is not responsible for material left unattended in the lab.

−

Since we are working with the open source community, you need to know where the action is. Here are some useful links to what's happening in the Beagle community.

+

Taken from \\rose-hulman.edu\dfs\AcademicAffairs\ECE\lab-safety

−

* [http://groups.google.com/group/beagleboard/browse_thread/thread/c5a631c6582119b8 State of the Beagle 2011], learn about the Beagle's past, present and future.

+

{{YoderFoot}}

−

* [http://BeagleBoard.org BeagleBoard.org], the starting point for all thing Beagle.

+

−

* [http://groups.google.com/group/beagleboard Beagle Discussion Group], lot's of good information here, but you'll have to dig a bit. Subscribe and follow the discussion.

+

−

* [http://beagleboard.blogspot.com/ blogspot], see what is being said about the Beagle.

+

−

* [http://elinux.org/BeagleBoard eLinux], this is where this page is being hosted. It's about embedded Linux in general, not just the BeagleBoard.

A major part of the class is learning how to work with and leverage off of the open source community. The course requires a major project which will either significantly contribute to an existing open source project, or launch a new one.

If you teach a similar course, I'd like to hear from you. ECE497 Instructor Guide explains the various choices I made in what to cover in the course, which distribution to use, etc.

Here (Category:ECE497) is a list of all the pages I've posted on eLinux for this class. Take a look at it.

Here's the official description of the course.

Course Description

ECE 497 32-bit Embedded Linux 4R-0L-4C S Pre: Consent of instructor

Brief introduction to Linux on a 32-bit embedded processor.

Detailed study of what happens from power up to fully running X-Windows.

Adapting Linux to a given application including: boot time reduction, power management and root filesystem support.

Calendar and Exercises

This is a dynamic course, so the calendar may change as we discover interesting new things. It will be updated as we go. You can see it here: ECE497 Calendar and Exercises

Textbook

We'll be using the text Embedded Linux Primer, by Christopher Hallinan, 2nd edition, published by Pearson Prentice Hall.

The text is not Beagle specific; rather, it pulls examples from many embedded processors. It has many listings which detail the outputs from various processors. One of your tasks will be to reproduce the listing for the BeagleBoard.

Grades

Grades in the class aren't based on the traditional homework and exams; rather, they are based on some weekly memos reporting the daily exercises ECE497 Calendar and Exercises, weekly homework and a major Beagle-based project. The projects will be done with teams of 2 or 3 people. We have people in the class with strong embedded backgrounds and others with strong Linux background. The goal is to have teams include complementary skills.

Status Reports

10%

Homework

40%

Project

40%

Giving to Community

10 %

The Calendar gives the due dates. I'll give a reward to being early and 10% per day penalty for being late. You must complete all the exercises to pass the course.

Weekly Status Memos

D114 Lab

Solid sole footwear must be worn at all times while in the lab for any reason. Glove or finger footwear is not considered as closed toe or solid sole and thus is not permitted at anytime within the lab.

Additionally, closed toe, solid sole footwear must be worn within 4 ft. of the lab benches. No loose fitting clothing (e.g. ties, scarfs, long necklaces) are allowed within 4 ft. of the lab benches. Long hair must be tied such that it is not loose or hanging in such a way that it could potentially get caught in the moving equipment when within 4 ft. of the lab benches.
No food or drinks are permitted within 4 feet of any lab bench. Food and drinks are allowed to be placed on the front table and tables in center of room. Anyone with drinks and/or food stuffs must remove or dispose of the material at the conclusion of their lab period(s). Food and/or drinks contained in backpacks and/or closed or sealed containers/packages may be kept on the floor during the lecture/lab period but MAY NOT be opened or consumed within 4 ft. of lab benches, food and drinks allowed on front table and tables in center of room.

Lab usage permitted testing available between 8:00 AM and 5:10 PM Monday through Friday. Lab usage at other times must be approved in writing by the ECE department chair or ECE department faculty member.

At least two students must be present within the lab at anytime lab equipment is being used or testing is being conducted. Devices, circuits, systems under test may NOT be left unattended unless all test equipment has been turned off. Any material left unattended in the lab is done so at the individuals own risk. The ECE department is not responsible for material left unattended in the lab.