There are many paths one could take in such a course. I've decided to
lead my students down one path while pointing out many other paths
they could follow. The course ends with a major project. Each team
will have a difference project, a project I hope will contribute
significantly to the open source world.
I have some 20 students enrolled. About half have Linux experience
(not embedded). The other half has embedded experience. I hope to
form teams of 2 or 3 that will have complementary skills. It should
be a fun class, if I survive it!
Has anyone else use the Beagle in this way? Am I heading down the
right path?
--Mark
ECE 597 Embedded 32-bit Linux 4R-0L-4C S Pre: ECE130, CSSE120, or
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 addressing boot time reduction,
power management and root filesystem support. Streaming media on an
embedded processor. Using a DSP co-processor to improve performance.
Software development in the C programming language with an IDE. Design
project. Previous Linux experience not needed, but helpful.
as someone with a long history in training and even being a member
of faculty in CS at a canadian university once upon a time, some
thoughts and questions.
* if one wants to participate in the ongoing delivery of this
course, is there a mailing list one could join to follow along? or
is the option to keep an ongoing thread going on the beagle mailing
list?
* i'm leery of your posting a number of wiki pages at elinux.org
that are specific to your course because they might have a tendency to
get lost in the shuffle. for instance, there's this page:
that would, based on its page name, *seem* to be a general page on
embedded linux software setup, but it's clearly specific to your
course. would it not make more sense to centralize your
course-specific pages in one place? perhaps even at a wiki at
rose-hulman?
i have a few more observations, but i'll hold off until there's a
consensus on how to proceed since i see this having the potential of
being a fairly active topic so it should be done right.
Good practice would be to place this into a sandbox and not make it a
part of this public Wiki. This also makes it easier to delete
completely after your course...
Robert:
Thanks for the feedback. I've gotten the same from my students with
wiki experience. This morning I moved everything and now all pages
start with ECE597_. I've also put them in the ECE597 Category so all
the pages can be seen at http://elinux.org/index.php?title=Category:ECE597.
I don't have a mailing list, yet. What would be the best way to do
it? I could see keeping a thread going here for course announcements,
etc. and using a local mailing list of details that aren't of general
interest.
I think I have two audiences here. One is the Beagle/Linux beginners
that need a clear path and some hand holding to get going. The other
group is faculty who are teaching, or considering teaching a Beagle-
based course. (They too will need some hand holding, I know I did!)
The second group would have some interest in how the class is
structured, etc.
I'll be creating some powerpoint, but I haven't figured out here to
post it. I've considered recording my class. Do you think ppt with
audio what have any value?
I'm happy to hear any other observations you (and others) have.
