Embedded Linux Training

From: DaWorm 
Can anyone recommend a course, either brick and mortar in the Chattanooga
area, or online, that covers setting up a system with embedded Linux?

I'm looking for something that covers the build system, distro choices (if
any), device driver development, system startup tasks, display/graphics
issues, application startup, security, debugging and the like.  Something
that uses a Arm based dev board, such as a BeagleBoard, would be best.

I'm looking at a project that would involve LCD graphics and SSL networking
over wired LAN and cell modem, among other things, and it's getting to the
point that roll your own solutions are becoming too complex (for me,
especially the SSL).  I'm thinking of offloading the non-standard hardware
control to cheap (~$2 to $5) Arm Cortex CPU's with USB device capabilities
and purchasing off the shelf ARM boards for the computing/UI/control tasks,
coupled with a large USB hub to handle up to eight serial devices and two
discrete I/O devices (nothing with any serious real time constraints).
Embedded Linux seems like the safest way to go, but I'm going to need some
help getting started, so I figured a good class or two would be in order,
and you guys would be the ones to know if there are actually any out there.


=============================================================== From: Dan Lyke ------------------------------------------------------ On Thu, 17 Jan 2013 16:58:38 -0500 DaWorm wrote: Been there, done that... A lot of this depends on what architecture you're using. The various different chip makers have funded click-and-go build systems like Buildroot for Atmel chips that take care of creating the entire build environment. And for others with more community support, there are just packages you can apt-get. It has been two years, but my guess is that for boards like that (and I'll get a chance to verify this with a Pi in a couple of days) you don't have to worry about drivers unless you want to. As far as system startup, the kernel runs /sbin/init (or whatever you've compiled it to run or passed through in the kernel args), which on modern embedded distributions is BusyBox based. BusyBox behaves an awful lot like a lighter weight version of what you're used to, but I was amazed at how much USB and SD stuff just worked (and for the stuff that didn't, usually it was a matter of finding the right module name to give to "modprobe"). After that, debugging is GDB, security is what you make of it, /dev/framebuffer will often do what you want or you can put X or use SDL. As I said, I'm a few days out from my Raspberry Pi boards arriving, but I'm told they run a stripped down Debian, so at that point they may as well be a desktop machine. Does your projected number of deployed devices warrant the engineering costs over and above just using the Raspberry? Dan

=============================================================== From: James Nylen ------------------------------------------------------ I wouldn't even say stripped down. For me that would manifest as something not working like I expected it to, and so far the only problem I've experienced with my Pi is flaky USB support with some devices, which is pretty well-documented.