Step #1) Visit http://www.angstrom-distribution.org/narcissus/
Step #2) Select:
Machine:
beagleboard
Image name: your choice
Complexity: advanced
Release (default): 2011.03 (FYI, this is the old stable branch that will give you the 2.6.32 kernel that works with some of the camera modules)
Base system (default): regular (task-base)
/dev manager (default): udev
Type of image: OMAP SD image
Software manifest: yes
SDK type: full SDK for generated filesystem
SDK hostsystem (default): 32bit Intel
User environment selection: X11
X11 desktop environment: (OK to leave blank)
Additional packages:
Platform specific packages:
OMAP Display Sub System (DSS) Documentation
BeagleBoard validation GUI extras
BeagleBoard validation GNOME image
Step #3) Click the button and WAIT
I've been waiting about 2 hours myself (and must leave to go catch a plane to California), so be patient and walk away from it a bit.
Step #4) Download all of the images and web pages.
There should be a Angstrom-2011.04-narcissus-beagleboard-i686-XXXX-image-sdk.tar.gz image with the SDK.
There should be a XXXX-image-beagleboard.tar.gz image with the file system contents.
There should be a XXXX-image-manifest.html manifest file with links to all the sources that aren't in OE in the "Obtained from" section.
You should download all of those source files ideally such that you can provide those sources to satisfy any GPL compliance requests.
There should be a XXXX-image-beagleboard-sd-1GiB.img.gz is a 1GB SD card image.
There should be a XXXX-image-beagleboard-sd-4GiB.img.gz is a 4GB SD card image.
Step #4) Program the SD card
Use the instructions at http://code.google.com/p/beagleboard/wiki/BeagleBoardDiagnosticsNext#Preparing_the_validation_SD_card, but utilize your newly created 4GB SD card image instead of the validation or demo image mentioned on that page.
Step #5) Boot the image
This will take a long time the first time it boots.
Step #6) Update /media/mmcblk0p1/UENV.TXT
I recommend the following:
dvimode="hd720 omapfb.vram=0:8M,1:4M,2:4M"
vram=16M
optargs="consoleblank=0"
console="tty0 console=ttyS2,115200n8"
Using gedit on the BeagleBoard is probably the best approach.
Step #7) Reboot it and make sure it works well. I suggest running the tests on the page with the instructions on programming the SD card mentioned above.
Step #8) Extract the booted contents of the SD card back to an SD card image
Use the same utility as used to program the SD card.
Compress the image.
Step #9) Upload not just the final image, but all of the files to a public website.
http://beagleboard.org/twitter
> Step #1) Visit http://www.angstrom-distribution.org/narcissus/
Since we're only after a filesystem, let's not make the server spend a lot of time assembling the manifest and sdk, right?
> Step #2) Select:
> Machine: beagleboard
> Image name: your choice
> Complexity: advanced
> Release (default): 2011.03 (FYI, this is the old stable branch that will give you the 2.6.32 kernel that works with some of the camera modules)
> Base system (default): regular (task-base)
> /dev manager (default): udev
> Type of image: OMAP SD image
> Software manifest: yes
Choose 'no' here, which is the default
> SDK type: full SDK for generated filesystem
Choose 'none' here, which is the default
> SDK hostsystem (default): 32bit Intel
> User environment selection: X11
> X11 desktop environment: (OK to leave blank)
> Additional packages:
> Platform specific packages:
> OMAP Display Sub System (DSS) Documentation
That one is included by default already.
> <image001.png>
> http://beagleboard.org/twitter
>
>
> --
> You received this message because you are subscribed to the Google Groups "Beagle Board" group.
> To post to this group, send email to beagl...@googlegroups.com.
> To unsubscribe from this group, send email to beagleboard...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/beagleboard?hl=en.
>
> Op 5 apr 2011, om 18:29 heeft Kridner, Jason het volgende geschreven:
>
>> Step #1) Visit http://www.angstrom-distribution.org/narcissus/
>
> Since we're only after a filesystem, let's not make the server spend a lot of time assembling the manifest and sdk, right?
Wouldn't it be helpful if the manifest and SDK were archived in association with the image? I want to make sure educative can teach how to create software for the SD card on the board and not need to instruct any image assembly.
put it all in one place avoid so many repeat questions on the list --- On Tue, 4/5/11, Jason Kridner <jkri...@beagleboard.org> wrote: |
|
|
|