Don't follow Derek's instructions as they are slightly out of date. To
build a Angstrom console image on an SD-card:
Angstrom Master
=============
Master Branch: v2013.06-yocto1.4
This guide details the process of building a Angstrom linux console image
from source on an Xubuntu 12.04.3 32-bit Linux host. Your computer must be
connected to the Internet. The build will take a number of hours and more
than 600 MB of data and source code will be downloaded.
The angstrom console image includes udev, systemd, connman, ofono, ppp,
busybox and some package management tools. It is a good starting point to
evaluate Angstrom linux for use in embedded systems.
Prerequisites
We need some host development tools:
sudo apt-get install sed wget cvs subversion git-core coreutils
unzip texi2html texinfo docbook-utils gawk python-pysqlite2 diffstat
help2man make gcc build-essential g++ desktop-file-utils chrpath
/bin/sh (ls -l /bin/sh) is symbolically linked to dash. "dash" is a POSIX
compliant shell that is much smaller than "bash". Some broken shell scripts
still make use of bash extensions while calling into /bin/sh. To work
around this issue call "sudo dpkg-reconfigure dash" and select No when it
asks you to install dash as /bin/sh.
Download Angstrom Distribution and Build
To download the master branch of the distribution and configure for the
beaglebone (both white and black) , enter the following commands:
cd ~/Projects (or your preferred directory)
mkdir Angstrom
cd ./Angstrom
git clone git://github.com/Angstrom-distribution/setup-scripts.git
cd setup-scripts
MACHINE=beaglebone ./oebb.sh config beaglebone
And to compile the console image:
. ./environment-angstrom-v2013.06
bitbake console-image
The previous command creates the root file system, modules, kernel and boot
files in the deployment directory ():
Angstrom-console-image-eglibc-ipk-v2013.06-beaglebone.rootfs.tar.gz
(the root filesystem)
Angstrom-console-image-eglibc-ipk-v2013.06-beaglebone.rootfs.tar.xz
(the root filesystem)
MLO-beaglebone-2014.01
(first stage of the boot loader)
modules--3.8.13-r23z.2-beaglebone-20140116020947.tgz
(device modules; the exact filename is dependent upon date)
u-boot-beaglebone-2014.01-r0.img
(second stage of the boot loader)
zImage--3.8.13-r23z.2-beaglebone-20140116020947.bin
(compressed kernel; the exact filename is dependent upon date)
SD Card Creation
=============
Installing on SD card manually
Use the gnome disk utility application to create the partitions on a blank
micro SD card and mount them.
Create DOS Partition with following:
Size: 4.000 MB
Type: FAT
Name: boot
Then edit the DOS partition with the following:
Partition Label:
Type: W95 FAT32 (LBA) (0x0c)
Bootable: Check this tickbox
Create a Linux partition to fill the rest of the SD card:
Size: 7.880 GB (for my 8 GB card)
Type: Ext4
Name: rootfs
Take Ownership of filesystem: Not checked
Encrypt underlying device: Not checked
Mount both partitions. The dos partition will be mounted at /media/boot and
the Linux partition will be mounted at /media/rootfs
Copy the Angstrom distribution files to the SD card:
cd ~/Projects/Angstrom/setup-scripts/deploy/eglibc/images/beaglebone
cp MLO-beaglebone-2014.01 /media/boot/MLO
cp u-boot-beaglebone-2014.01-r0.img /media/boot/u-boot.img
sudo tar zxv -C /media/rootfs -f
Angstrom-console-image-eglibc-ipk-v2013.06-beaglebone.rootfs.tar.gz
sudo tar zxv -C /media/rootfs -f
modules--3.8.13-r23z.2-beaglebone-20140116020947.tgz
The SD card now is ready for the Beaglebone. Unmount the partitions.
When you power up the Beaglebone make sure you are holding down the boot
switch. This ensure the boot loader components on the SD card are loaded
and run in preference to the eMMC.
Make sure when the system boots for the first time to run:
depmod -a
Unless there is a specific requirement, there is no need to include the
kernel image or compiled device tree in the dos boot partition. The second
stage of the boot loader u-boot.img will attempt to load the compressed
kernel image from the boot directory in the ext4 partition. Also, I have no
current need for a uEnv.txt file.
It is possible to include development tools in the image by modifying some
of the image recipe files.
There are scripts that will do this also, but I'm quite happy to do it
manually.
Creating an SD-card Flasher
=====================
It's not that hard. Download the latest flasher image and copy it to the
SD-card. Mount the SD-card on your desktop machine and look at the
contents. The key areas to examine are:
the build directory in the linux partition, which contains the scripts and
components to be loaded on the emmc
the emmc.service file in /lib/systemd/system
emmc.sh in /usr/bin directory
You could build a script to create a flasher image automatically, but I'm
quite happy to do it manually. You could create an Angstrom based flasher
to install debian/ubuntu/freebsd/arch or whatever ... You could create a
debian based flasher to install whatever.
Just do it.
On Friday, February 28, 2014 6:29:23 PM UTC+11, [email protected] wrote:
>
> Robert,
>
> Have you resolved any of these mysteries in the mean time?
>
> I got into this by trying to "bitbake" a simpler image, such as
> console-image, since I need no graphics or fancy webserver with node.js
> foo. So far I have failed to boot from the SD card with anything which has
> been made by the oebb.sh script or bitbake build system. Even Derek's
> 2-year-old
> instructions<http://derekmolloy.ie/building-angstrom-for-beaglebone-from-source/>seem
> not to work for "console-image".
>
> After I succeed at booting the BBB with my own custom image, I plan on
> updating u-boot to allow "fastboot", an feature more commonly supported by
> Android which allows one to boot or flash over USB, ethernet, etc. Maybe we
> can become free from SD cards in the near future for BBB development.
>
> Cheers,
> Joe
>
> On Friday, July 12, 2013 8:30:29 AM UTC-4, Robert P. J. Day wrote:
>>
>> On Fri, 12 Jul 2013, Chris Morgan wrote:
>>
>> > On Friday, July 12, 2013, Koen Kooi wrote:
>> >
>> > Op 12 jul. 2013, om 13:46 heeft Robert P. J. Day <
>> [email protected]> het
>> > volgende geschreven:
>> >
>> > > On Fri, 12 Jul 2013, Koen Kooi wrote:
>> > >
>> > >> It's all in the SRM, but for people too lazy to read that:
>> > >>
>> > >> � � �Read
>> http://www.angstrom-distribution.org/building-angstrom and follow the
>> > steps outlined there.
>> > >
>> > > �gaaaaaah ... i am not interested in the general philosophy
>> of how to
>> > > build angstrom, that's *not* the question on the table. the
>> question
>> > > is, which *particular* configuration of angstrom is the one
>> that
>> > > matches what is currently shipping on the BBB?
>> >
>> > The one I linked above. There is only one configuration of
>> angstrom per release and
>> > the above matches the release that ships with the bones.
>> >
>> >
>> > Hello.
>> >
>> > I followed those instructions and, although I had selected the yocto
>> > 2013 release, I ended up with the component files in the deploy/
>> > directory but as rootfs and ubi files, not card images.
>> >
>> > The information yesterday about the emmc-prepare.sh and other
>> > scripts has helped informationaly, I think I'll be able to build a
>> > sd card image today using those steps, but at this point it seems
>> > like a multi step process after following the angstrom build steps.
>>
>> actually, that's what i would have expected ... the primary purpose
>> of OE/yocto is to build the fundamental images or objects, not so much
>> to create the final bootable SD card image based on them, since some
>> people might not want an SD card, they might be, say, trying to
>> populate a TFTP or NFS server with those images.
>>
>> rday
>>
>> --
>>
>> ========================================================================
>> Robert P. J. Day Ottawa, Ontario, CANADA
>> http://crashcourse.ca
>>
>> Twitter: http://twitter.com/rpjday
>> LinkedIn: http://ca.linkedin.com/in/rpjday
>> ========================================================================
>
>
--
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/groups/opt_out.
