Sounds different from traditional teaching Robert, but also sounds like a good thing to me. Seems like it would help teach critical thinking (troubleshooting). Something that many students need, and often lack now days.
On Sun, Jan 25, 2015 at 8:13 AM, William Pretty Security < [email protected]> wrote: > Thanks for the advice Robert! > > I am currently working thru the same page, more or less as a student :-) > And you suggestions sound excellent. I would be interested to hear you > advice on selecting > Kernel build options, from the menu. Do you think there is such a thing as > a > "default" configuration ?? > > Bill > > currently working my way through RCN's eewiki beaglebone page here: > > https://eewiki.net/display/linuxonarm/BeagleBone+Black > > and for others who also teach EL classes, here's something i do that seems > to be a bit different from most presentations (and online pages) i've seen. > > most presentations seem to like downloading and building > *everything* (MLO, u-boot, kernel, dtb and rootfs) before getting around to > formatting an SD card, copying it all on, then testing. > > when i'm presenting this, i prefer to do the creation and testing in > bite-size pieces to isolate build errors much faster. for instance, i will > get students to do nothing more than download u-boot source, possibly patch > it, cross-compile, then copy MLO and u-boot.img to the SD card and try to > boot that. > > as long as the class has access to the serial port (i'm assuming that), > the only test they'll be making is if u-boot comes up, and they can stop > there and look around. they'll know they can't go any further, but that's > all right -- that at least verifies that their build and install of u-boot > seems to be fine, and if it isn't, debugging should be easy. > > once that's verified, move on to format the rest of the SD card and copy, > say, just the kernel and dtb file, then try to boot *that*. > again, students will understand there's no rootfs but all they're testing > is > if the kernel seems to load and boot. and if it fails, once again, > debugging > should be easy. > > finally, add the rootfs. anyway, that's the approach i prefer, and it > seems to work as students like to be able to build *and test* something > fairly quickly, rather than just doing a massive amount of work, and > wondering if it will work in the end. > > rday > > -- > > ======================================================================== > Robert P. J. Day Ottawa, Ontario, CANADA > http://crashcourse.ca > > Twitter: http://twitter.com/rpjday > LinkedIn: http://ca.linkedin.com/in/rpjday > ======================================================================== > > > ----- > No virus found in this message. > Checked by AVG - www.avg.com > Version: 2015.0.5645 / Virus Database: 4273/8997 - Release Date: 01/25/15 > > ----- > No virus found in this message. > Checked by AVG - www.avg.com > Version: 2015.0.5645 / Virus Database: 4260/8941 - Release Date: 01/16/15 > Internal Virus Database is out of date. > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
