BeagleBoardAndOpenEmbeddedGit - Revision history

CountDown: /* Booting */

2009-12-10T23:29:29Z

‎Booting

2009-12-10T23:17:39Z

‎Preparing the system for booting

2009-12-10T23:14:13Z

‎Create partitions and format the SD-card

2009-12-10T22:57:26Z

‎Preparing the system for booting

2009-11-04T12:04:27Z

I'm getting tired of pointing out this stuff is either wrong or duplicated, so just remove it.

2009-10-29T16:53:42Z

‎Booting

2009-09-01T02:11:45Z

‎Running

2009-09-01T02:11:13Z

‎Running

2009-09-01T02:09:22Z

‎Prerequisites

2009-09-01T02:07:04Z

‎Prerequisites

@@ Line 57: / Line 57: @@
   mmc init
   setenv bootargs 'console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw rootdelay=1'
-  fatload mmc 0:1 0x80000000  uImage
+  fatload mmc 0:1 0x80300000 uImage
   saveenv
-  bootm
+  bootm 0x80300000
 ===One very important note:===

@@ Line 13: / Line 13: @@
 == Preparing the system for booting ==
-The output of the bitbake command will ultimately be found under the $OE_HOME/angstrom-dev/deploy/glibc/images/beagleboard. In there you can find at least 3 interesting files:
+The output of the bitbake command will ultimately be found under the $OE_HOME/angstrom-dev/deploy/glibc/images/beagleboard. In there you can find at least two interesting files:
-* console-image-beagleboard.tar
+* console-image-beagleboard.tar.bz2
-* console-image-beagleboard.jffs2 and
 * uImage-beagleboard.bin
-The console images are representations of a full and self containing file system *including* a kernel. The uImage is a linux kernel image that is suitable to be loaded by the U-boot bootloader. The difference between the tar file and the jffs2 image is that the later is better suited to directly put on a raw partition.
+The console image represents of a full and self-contained file system, *including* a kernel. The uImage is a Linux kernel image suitable for loading by the U-boot bootloader.
 We are going to use the U-boot that is already provided in the NAND flash of the beagleboard as that one already support the MMC can load kernel images from a fat file system.

@@ Line 43: / Line 43: @@
 Mount the ext2 file system and unpack the archive. Do not forget the -C option.
    mount /dev/mmcblk0p2  /mnt
-   tar xvf system/angstrom/deploy/glibc/images/beagleboard/console-image-beagleboard.tar -C /mnt
+   tar xvjpf $OE_HOME/angstrom-dev/deploy/glibc/images/beagleboard/console-image-beagleboard.tar.bz2 -C /mnt
    umount /mnt

@@ Line 13: / Line 13: @@
 == Preparing the system for booting ==
-The output of the bitbake command will ultimately be found under the $OE_HOME/tmp/deploy/glibc/images/beagleboard. In there you can find at least 3 interesting files:
+The output of the bitbake command will ultimately be found under the $OE_HOME/angstrom-dev/deploy/glibc/images/beagleboard. In there you can find at least 3 interesting files:
 * console-image-beagleboard.tar
 * console-image-beagleboard.jffs2 and

@@ Line 224: / Line 224: @@
   coninfo
-  mmcinit
+  mmc init
-  setenv bootargs console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw rootdelay=1
+  setenv bootargs 'console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw rootdelay=1'
   fatload mmc 0:1 0x80000000  uImage
   bootm

@@ Line 174: / Line 174: @@
-If this goes well your computer will be compiling for a long time.  A long time can be several hours. Once this works try using the x11-image target (bitbake x11-image) this will give you a more complete distribution
+*If this goes well your computer will be compiling for a long time.  A long time can be several hours. Once this works try using the x11-image target (bitbake x11-image) this will give you a more complete distribution
-If you receive an error of the form "ERROR: Unable to open conf/bitbake.conf" check that your profile.sh created earlier has the correct BBPATH setting (copy/pasting from this page may cause a line-break between the export command and the BBPATH var).
+*If you receive an error of the form "ERROR: Unable to open conf/bitbake.conf" check that your profile.sh created earlier has the correct BBPATH setting (copy/pasting from this page may cause a line-break between the export command and the BBPATH var).
-if you receive an error with module-init-utils-cross and you are running fedora 11, the glibc-static rpm has not been installed, see the list of fedora 11 packages that need to be installed above.
+*if you receive an error with module-init-utils-cross and you are running fedora 11, the glibc-static rpm has not been installed, see the list of fedora 11 packages that need to be installed above.
 == Preparing the system for booting ==

← Older revision		Revision as of 02:11, 1 September 2009
Line 177:		Line 177:

	If you receive an error of the form "ERROR: Unable to open conf/bitbake.conf" check that your profile.sh created earlier has the correct BBPATH setting (copy/pasting from this page may cause a line-break between the export command and the BBPATH var).		If you receive an error of the form "ERROR: Unable to open conf/bitbake.conf" check that your profile.sh created earlier has the correct BBPATH setting (copy/pasting from this page may cause a line-break between the export command and the BBPATH var).
		+
		+	if you receive an error with module-init-utils-cross and you are running fedora 11, the glibc-static rpm has not been installed, see the list of fedora 11 packages that need to be installed above.

	== Preparing the system for booting ==		== Preparing the system for booting ==

@@ Line 30: / Line 30: @@
 Fedora 11 - Needed Packages
 <pre>
-su -c "yum install python m4 make wget curl ftp cvs subversion tar bzip2 gzip unzip python-psyco ccache perl texinfo texi2html diffstat openjade docbook-style-dsssl docbook-style-xsl docbook-dtds docbook-utils sed bison bc glibc-devel glibc-static gcc binutils pcre pcre-devel git quilt groff linuxdoc-tools patch linuxdoc-tools gcc gcc-c++ help2man perl-ExtUtils-MakeMaker"
+su -c "yum install python m4 make wget curl ftp cvs subversion tar bzip2 gzip unzip python-psyco ccache perl"
 </pre>

← Older revision		Revision as of 02:07, 1 September 2009
Line 27:		Line 27:

	OE tries to be as self supporting as possible. OE will both compile the cross compiler and the tools needed to compile a whole system. Still some dependencies are to be met using the "host" system. During the install we will be able to run almost all the commands as normal user but right now we will install the basic set of packages that are required to make OE to be happy.		OE tries to be as self supporting as possible. OE will both compile the cross compiler and the tools needed to compile a whole system. Still some dependencies are to be met using the "host" system. During the install we will be able to run almost all the commands as normal user but right now we will install the basic set of packages that are required to make OE to be happy.
		+
		+	Fedora 11 - Needed Packages
		+	<pre>
		+	su -c "yum install python m4 make wget curl ftp cvs subversion tar bzip2 gzip unzip python-psyco ccache perl texinfo texi2html diffstat openjade docbook-style-dsssl docbook-style-xsl docbook-dtds docbook-utils sed bison bc glibc-devel glibc-static gcc binutils pcre pcre-devel git quilt groff linuxdoc-tools patch linuxdoc-tools gcc gcc-c++ help2man perl-ExtUtils-MakeMaker"
		+	</pre>

	Host tools to install:		Host tools to install: