ok, after a bit of testing ...
> http://www.crashcourse.ca/wiki/index.php/BeagleBoard-xM#Rebuilding_ML…
> i haven't tested ethernet yet, so it's possible that that is still
> an issue. but regarding what i've documented, does it seem
> reasonable? it works reliably for me, so if there's still some
> underlying problem with what i've tested, i'd like to know what it
> is so i can mention it.
some comments on your wiki:
toolchains: I think the easiest to get/use are the stock Ubuntu and
Linaro ones, they are also fairly recent
on my updated 64-bit ubuntu 11.10 system, i just tested with the
gcc-arm-linux-gnueabi package and the u-boot git repo and it seems to
build. i'm puzzled. i could have sworn that this didn't work several
days ago, which is why i reverted to an earlier ELDK toolchain. so
why does it work *now*? anyone recall the issue with ubuntu's stock
arm toolchain from just a couple weeks ago? i thought it was
something related specifically to gcc 4.6.1 that was going to be
resolved in 4.6.2. but it seems to work now. weird.
Rebuilding MLO: I'd mention CROSS_COMPILE= for the 'make
omap3_beagle_config'
at the risk of being slightly repetitive, let me explain again why i
started those wiki pages. i'm not trying to duplicate what's out
there, i just want to summarize and coalesce stuff that is absolutely,
positively known to *work* so that others don't need to fight with
stuff.
i don't want to get into the lengthy discussions of how one verifies
what works, i just want to describe the end result. and more to the
point, i don't want to repeat all of the perfectly respectable
newbie-level docs that are out there.
that is, i don't want to start writing stuff like, "to install the
toolchain on ubuntu, type 'sudo apt-get install ...', then set the
CROSS_COMPILE variable to ...". i'd like to assume some working
knowledge so i can keep things brief. i want to be able to write
stuff like:
* start with circuitco xM 4_25 image here
(http://circuitco.com/support/index.php?title=BeagleBoard-xM)
* install ubuntu arm toolchain package 'gcc-arm-linux-gnueabi'
* git clone u-boot from [link], set build environment
$ make omap3_beagle_config
$ make
* results:
new MLO
new u-boot.img
* copy to boot partition
that's it, that's all i want to document. i'll get into more detail
when i start writing the courseware based on that, but for now, i want
things concise that are known to work.
so if you have bits of info you've discovered, feel free to send
them along. eventually, those wiki pages will get fairly
comprehensive but, for now, i'd like to just be able to hand out
recipes that should work for evryone.
rday
p.s. recall that my eventual goal is to write some courseware that
uses things like the beagle and panda for embedded linux classes.
because of that, i'm going to be very focused on writing recipes for
just two platforms:
* bb xM Rev C
* panda ES
so for better or worse, i'm not going to care much about what happens
with the original beagle or panda boards. i need to concentrate on
precisely the platforms i plan on using, so i should be able to
guarantee that recipes work. (i'm already going through mark yoder's
class and testing everything there as well.)
anyway, feel free to read and critique what's on the wiki pages -- i
want to make sure it's correct.