Difference between revisions of "Embedded Linux, Rose-Hulman"

From eLinux.org
Jump to: navigation, search
m (Switched to Monday Due date)
m (Some minor grammar and spelling fixes.)
Line 8: Line 8:
 
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.
 
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.  
+
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.
Line 20: Line 20:
 
'''ECE 497 32-bit Embedded Linux 4R-0L-4C S Pre: Consent of instructor'''
 
'''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 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. 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.
  
 
=== Calendar and Exercises ===
 
=== Calendar and Exercises ===
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: [[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.
 
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.
Line 30: Line 30:
 
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://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.   
  
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 daily exercises [[ECE497 Calendar and Exercises]], a couple of minor projects and a major Beagle-based project and your portfolio. 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.
+
Your portfolio is a collection of what you, as an individual, have contributed to the community and the team.
  
 
{| style="color:green; background-color:#ffffcc;" cellpadding="10" cellspacing="0" border="1"
 
{| style="color:green; background-color:#ffffcc;" cellpadding="10" cellspacing="0" border="1"
Line 66: Line 66:
 
# End with a few sentences of concluding remarks.  What did you learn?  What else would you like to learn? What do you suggest for other related exercises? What extra interesting things did you do?
 
# End with a few sentences of concluding remarks.  What did you learn?  What else would you like to learn? What do you suggest for other related exercises? What extra interesting things did you do?
  
You grade for each exercise will be based on what you report in your memo. No need for the memo to be long.  Just make it clear about what you have done.
+
Your grade for each exercise will be based on what you report in your memo. No need for the memo to be long.  Just make it clear about what you have done.
  
 
{{YoderFoot}}
 
{{YoderFoot}}

Revision as of 11:26, 29 August 2013

thumb‎ Embedded Linux Class by Mark A. Yoder


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 Electrical and Computer Engineering Department at 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.

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. 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.

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

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

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 daily exercises ECE497 Calendar and Exercises, a couple of minor projects and a major Beagle-based project and your portfolio. 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.

Labs and Exercises 25%
Mini Projects 25%
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

A Weekly Status Memo is due on Monday of each week. This memo is to document all that you have done during the previous week. Here are things I look for in a memo.

  1. Have To, From, Date, and Subject field on the top.
  2. Use a meaningful subject. Week 2, Exercises 02, 04 and 10 is meaningful. Exercise Memo is not.
  3. Have a section of each exercise that is completed.
  4. Start with a couple sentence introduction giving an overview of what the exercise is about.
  5. Answer all the questions in the exercise.
  6. Use tables.
  7. Clearly state which parts of the exercise you were able to complete.
  8. Note any parts of the exercise you were unable to complete and explain why.
  9. End with a few sentences of concluding remarks. What did you learn? What else would you like to learn? What do you suggest for other related exercises? What extra interesting things did you do?

Your grade for each exercise will be based on what you report in your memo. No need for the memo to be long. Just make it clear about what you have done.




thumb‎ Embedded Linux Class by Mark A. Yoder