Re: [beagleboard] How are the production BBB images built?
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
Re: [beagleboard] How are the production BBB images built?
Hi, I'm now getting this error on v2013.12-yocto1.5 cloud9-image.bb, while compiling on xubuntu 32-bit 12.04.3. Disk exhaustion is not the cause and I don't think it is memory exhaustion. It may be an internal make error. *Are you compiling on a 32-bit or 64-bit platform?* I'll investigate further and maybe post the results on the Angstrom list. Other Angstrom images seem to be OK. Regards ... On Thursday, July 18, 2013 5:17:53 PM UTC+10, Dale Schaafsma wrote: I crossed my fingers, and resized partitions...got past the disk exhaustion, and strangely now my disk only has 22G. So somewhere between the old 30G and the now available 53G was the magic number. Now unfortunately I'm encountering a build failure with nodejs...google told me to raise ulimit -s for this...and that didn't work. The build machine is Debian Wheezy (linux 3.2 if I read things correctly), am I out of luck with the following? ERROR: Function failed: do_compile (see /home/dales/beagleBoneBlack/angstrom/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/armv7a-vfp-neon-angstrom-linux-gnueabi/nodejs-0.8.22-r0/temp/log.do_compile.16430 for further information) ERROR: Logfile of failure stored in: /home/dales/beagleBoneBlack/angstrom/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/armv7a-vfp-neon-angstrom-linux-gnueabi/nodejs-0.8.22-r0/temp/log.do_compile.16430 Log data follows: | DEBUG: Executing shell function do_compile | make -C out BUILDTYPE=Release V=1 | make[1]: Entering directory `/home/dales/beagleBoneBlack/angstrom/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/armv7a-vfp-neon-angstrom-linux-gnueabi/nodejs-0.8.22-r0/node-v0.8.22/out' | make[1]: execvp: printf: Argument list too long | make[1]: *** [/home/dales/beagleBoneBlack/angstrom/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/armv7a-vfp-neon-angstrom-linux-gnueabi/nodejs-0.8.22-r0/node-v0.8.22/out/Release/obj.target/deps/openssl/libopenssl.a] Error 127 | make[1]: Leaving directory `/home/dales/beagleBoneBlack/angstrom/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/armv7a-vfp-neon-angstrom-linux-gnueabi/nodejs-0.8.22-r0/node-v0.8.22/out' | make: *** [node] Error 2 | ERROR: Function failed: do_compile (see /home/dales/beagleBoneBlack/angstrom/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/armv7a-vfp-neon-angstrom-linux-gnueabi/nodejs-0.8.22-r0/temp/log.do_compile.16430 for further information) ERROR: Task 861 (/home/dales/beagleBoneBlack/angstrom/setup-scripts/sources/meta-openembedded/meta-oe/recipes-devtools/nodejs/ nodejs_0.8.22.bb, do_compile) failed with exit code '1' NOTE: Tasks Summary: Attempted 6529 tasks of which 6526 didn't need to be rerun and 1 failed. Waiting for 0 running tasks to finish: Thanks, Dale On Wednesday, July 17, 2013 3:16:37 PM UTC-5, Dale Schaafsma wrote: If I might ask...how much disk is taken up by the cloud9-gnome-image build? The machine I'm using is a little resource constrained and I've filled 30+G of disk in my attempt. The specific command I'm using is: MACHINE=beaglebone bitbake cloud9-gnome-image Thanks, Dale ps. FWIW, I was able to build virtual/kernel, but I haven't yet tried the resulting kernel, so I may have failed to setup something correctly. On Wednesday, July 17, 2013 12:53:09 PM UTC-5, chmo...@gmail.com wrote: Hi Martin. I took a look at your post and I can certainly follow it in terms of working with an existing image, but I don't believe that the appropriate images are created by Angstrom, or at least my eyes are failing me and I haven't spotted them. In this case I have a rootfs tarball, a uboot binary, the MLO etc, all of the separate components, and a blank microsd card, which I believe to be what the BBB recipes generate if you follow the instructions in the BB white srm and on the angstrom wiki with MACHINE=beaglebone. I'm trying to figure out how to generate the production programming image, the one on the wiki that boots and programs the production image to the emmc, as well as the bootable image, the one where you can boot the production image directly off of the microsd card. Clearly I can do everything by programming the existing image onto an sd card, mounting it and altering it. That doesn't seem like The Right Thing to do though. Chris On Wednesday, July 17, 2013 11:45:34 AM UTC-4, eskimobob wrote: Chris, I'm not entirely sure I am following the main thrust of your question but I may be able to help with a tiny part. It is possible to locally mount a disk image and write to it (assuming sudo) without having to write the image to a card and then mount that. You can use losetup to create a local loop. I've included details about that in a blog post about shrinking a disk image (herehttp://www.berriman.co.uk/bbb-mount-and-shrink-a-disk-image ). Hope it help Martin On Monday, 15 July 2013 21:16:07 UTC+1, chmo...@gmail.com wrote: Is this
Re: [beagleboard] How are the production BBB images built?
Two things. First, I have had success with my bitbaked images. After I grabbed my console serial cable from work it seemed my boot was failing to find /dtbs/am355x...dtb for the bbb, so I created the folder on the boot partition and added the dtb file and it has since worked. Second, while netboot is cool, it's not quite as cool as fastboot. Here is a fan review and tutorial for Android BBBhttp://wiresareobsolete.com/wordpress/2013/11/fastboot-on-the-beaglebone-black/ , AM335x eMMC bootinghttp://processors.wiki.ti.com/index.php/AM335x_Android_eMMC_booting#What_is_fastboot.3Fdoc by TI, and the succinct fastboot protocol herehttps://gitorious.org/rowboat/bootable-bootloader-legacy/source/076ef94d61f349f7cf0fe776e60456d8f232cca5:fastboot_protocol.txt . As it happens, I have just connected to u-boot from linux host using fastboot. Next steps are to see if I can boot or flash an Angstrom image over USB. Cheers, Joe Gorse On Friday, February 28, 2014 7:51:11 PM UTC-5, john3909 wrote: From: Brandon I brando...@gmail.com javascript: Reply-To: beagl...@googlegroups.com javascript: Date: Friday, February 28, 2014 at 4:34 PM To: beagl...@googlegroups.com javascript: Cc: jhg...@gmail.com javascript: Subject: Re: [beagleboard] How are the production BBB images built? Maybe we can become free from SD cards in the near future for BBB development. Doesn't uboot support network boot already? Hi Brandon, I use u-boot on my BBB to tftp zImage from my desktop and then mount rootfs via NFS on my desktop. Is that what you want? Regards, John On Thursday, February 27, 2014 11:29:23 PM UTC-8, jhg...@gmail.com 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 instructionshttp://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 rpj...@crashcourse.ca 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: ï¿1Ž2 ï¿1Ž2 ï¿1Ž2Read http://www.angstrom-distribution.org/building-angstrom and follow the steps outlined there. ï¿1Ž2gaah ... 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
Re: [beagleboard] How are the production BBB images built?
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 instructionshttp://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 rpj...@crashcourse.ca javascript: 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. �gaah ... 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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] How are the production BBB images built?
Maybe we can become free from SD cards in the near future for BBB development. Doesn't uboot support network boot already? On Thursday, February 27, 2014 11:29:23 PM UTC-8, jhg...@gmail.com 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 instructionshttp://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 rpj...@crashcourse.ca 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. �gaah ... 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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] How are the production BBB images built?
From: Brandon I brandon.ir...@gmail.com Reply-To: beagleboard@googlegroups.com Date: Friday, February 28, 2014 at 4:34 PM To: beagleboard@googlegroups.com Cc: jhgo...@gmail.com Subject: Re: [beagleboard] How are the production BBB images built? Maybe we can become free from SD cards in the near future for BBB development. Doesn't uboot support network boot already? Hi Brandon, I use u-boot on my BBB to tftp zImage from my desktop and then mount rootfs via NFS on my desktop. Is that what you want? Regards, John On Thursday, February 27, 2014 11:29:23 PM UTC-8, jhg...@gmail.com 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 rpj...@crashcourse.ca 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: ï¿1Ž2 ï¿1Ž2 ï¿1Ž2Read http://www.angstrom-distribution.org/building-angstrom and follow the steps outlined there. ï¿1Ž2gaah ... 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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- 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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
