I thought I'd start a new thread as we are getting closer to something
that can be pounded upon and documented for validating the hardware.
The 'ec2build.sh' script is starting to finally provide some results.
There was a bug in 'oebb.sh' (that I created) that was causing it to
not update the OE source tree, which is why some fixes that had gone
into OE didn't show up in the last test image. This one should be a
bit better:
http://beagleboard-validation.s3.amazonaws.com/sd/beagleboard-validation-201008051716.img/list.html
I hope that anyone testing will move to this version and apply fixes
to it. However, it doesn't currently boot automatically, so you'll
need to halt u-boot and give it the following help:
mmc init
setenv console ttyS2,115200n8
run loaduimage
run loadramdisk
run ramboot
I still need to work out the errors with user.scr, such as how to use
comparisons to ${beaglerev} in a script and why setting ${optargs}
generates a syntax error, but I'll do that after pulling in Steve
Kipisz's patches that he sent me privately for enabling the camera
port.
At the login prompt, just give 'root' as the user name.
Networking almost works, but I need to add an 'auto usb0' to make it
automatic. Here's the current behavior:
root@beagleboard:~# ifup usb0
udhcpc (v1.13.2) started
Sending discover...
[ 95.123352] usb0: link up, 100Mbps, full-duplex, lpa 0x45E1
Sending discover...
Sending select for 192.168.1.9...
Lease of 192.168.1.9 obtained, lease time 86400
adding dns 192.168.1.1
oot@beagleboard:~# ping www.google.com
PING www.google.com (209.85.225.103): 56 data bytes
64 bytes from 209.85.225.103: seq=0 ttl=52 time=44.313 ms
64 bytes from 209.85.225.103: seq=1 ttl=52 time=44.830 ms
64 bytes from 209.85.225.103: seq=2 ttl=52 time=43.580 ms
^C
Next, I'm working to add the test scripts that I promised in the ESC
classes. 'testled' and 'testaudio' don't work in the image, but they
are working in the git repo. I'll get all of these working and
include the guts of them in the wiki documentation on the board
validation. Having them in scripts will also help me quickly go back
and check everything on Rev C and Rev B. Please let me know if we
should have some more specific tests.
Finally, I need some support from Koen and others to build the demo
partition automatically (removing the manual steps), as well as a bit
more clean-up in the scripts to be sure that everyone can rebuild all
of the bits reliably. I believe that all of this will allow us to
keep an up-to-date version of this image with everyone's feedback and
help us verify things aren't broken as we push everything into the
mainlines of each project.