Hello,
Any and all help will be appreciated.
yocto beaglebone build no uImage to DOS partition.
My questions are do you need the a uImage on DOS partition and should you
use core-image-sato-sdk with the beaglebone since it has no display on
board, but you want the SDK? My beaglebone booted okay but I did see that
the xserver failed. My pandaboard build is failing currently but I have
had successful builds in the past in early Jan with same process outlined
below.
Downloaded both poky and meta-ti
cd /home/vidal/POKY/build022813_
panda
git clone git://git.yoctoproject.org/poky.git
cd /home/vidal/POKY/build022813_panda/poky
git log
commit d7b248e715d99766bf8602ff9f038f8b0afa5e78
Author: Constantin Musca <constantinx.mu...@intel.com>
Date: Mon Feb 25 17:29:15 2013 +0200
cd /home/vidal/POKY/build022813_panda/poky
git clone git://git.yoctoproject.org/meta-ti
git log
commit 4d99e63181c6f58b5bb41eb830c7af75b097e10e
Author: Franklin S. Cooper Jr <fcoo...@ti.com>
Date: Mon Feb 18 22:45:16 2013 -0600
Modifications to file
/home/vidal/POKY/build022813/poky/build/conf/local.conf
Added the following three lines at the beginning of the file.
MACHINE ?= "beaglebone"
MACHINE ?= "pandaboard"
BBMASK ?= ".*/meta-ti/recipes-(misc|bsp/formfactor|graphics/mesa)/"
Mofified the following 3 lines as shown below.
#BB_NUMBER_THREADS = "4" --> BB_NUMBER_THREADS = "8"
#PARALLEL_MAKE = "-j 4" --> PARALLEL_MAKE = "-j 8"
#DL_DIR ?= "${TOPDIR}/downloads" --> DL_DIR ?=
"/home/vidal/POKY/linux_src_dnloads_panda/downloads"
Modification done to
/home/vidal/POKY/build022813/poky/build/conf/bblayers.conf
Added the line
/home/vidal/POKY/build022813_panda/poky/meta-ti \
After the line
/home/vidal/POKY/build022813_panda/poky/meta-yocto \
Built on Fedora 18 x86_64 system.
MACHINE=beaglebone bitbake core-image-sato-sdk -vDD
NOTE: recipe core-image-sato-sdk-1.0-r0: task do_rootfs: Succeeded
DEBUG: Marking task 12
(/home/vidal/POKY/build022813_panda/poky/meta/recipes-sato/images/
core-image-sato-sdk.bb, do_build) as buildable
DEBUG: Stampfile
/home/vidal/POKY/build022813_panda/poky/build/tmp/stamps/beaglebone-poky-linux-gnueabi/core-image-sato-sdk/1.0-r0.do_build.43a176d7b0f28fabd0275a4afba65cd3
not available
NOTE: Running noexec task 6534 of 6534 (ID: 12,
/home/vidal/POKY/build022813_panda/poky/meta/recipes-sato/images/
core-image-sato-sdk.bb, do_build)
NOTE: Tasks Summary: Attempted 6534 tasks of which 543 didn't need to be
rerun and all succeeded.
Build Configuration:
BB_VERSION = "1.17.1"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "Unknown"
TARGET_SYS = "arm-poky-linux-gnueabi"
MACHINE = "beaglebone"
DISTRO = "poky"
DISTRO_VERSION = "1.3+snapshot-20130228"
TUNE_FEATURES = "armv7a vfp neon"
TARGET_FPU = "vfp-neon"
meta
meta-yocto = "master:d7b248e715d99766bf8602ff9f038f8b0afa5e78"
meta-ti = "master:4d99e63181c6f58b5bb41eb830c7af75b097e10e"
meta-yocto-bsp = "master:d7b248e715d99766bf8602ff9f038f8b0afa5e78"
Transferred the following files to boot partition from
/home/vidal/POKY/build022813_panda/poky/build/tmp/deploy/images/
MLO-beaglebone-2011.09+git* --> MLO
u-boot.img -> u-boot-beaglebone-2011.09+git-r30.img* --> u-boot.img
Untarred the file
/home/vidal/POKY/build022813_panda/poky/build/tmp/deploy/images/core-image-sato-sdk-beaglebone-20130228230414.rootfs.tar.bz2
to /run/media/vidal/Angstrom
If anyone wants any additional information feel free to ask at
vidal.devel...@gmail.com or devel...@sbcglobal.net.
On Thu, Mar 7, 2013 at 2:42 AM, Chris Swainson <chris.swain...@marel.com>wrote:
> Hi All,
>
> I am trying to build a new kernel for the BeagleBone.
>
> I do the following:
>
>
> git clone git://github.com/Angstrom-distribution/setup-scripts.git
> cd setup-scripts
> MACHINE=beaglebone ./oebb.sh config beaglebone
> MACHINE=beaglebone ./oebb.sh update
> MACHINE=beaglebone ./oebb.sh bitbake virtual/kernel
>
> But get this towards the end of the build
>
> ----------------------------------------------------------------------------------
>
> | make: Entering directory
> `/home/developer/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/work/beaglebone-angstrom-linux-gnueabi/linux-ti33x-psp-3.2.34-r18a+gitr720e07b4c1f687b61b147b31c698cb6816d72f01/image/usr/src/kernel'
> | CLEAN .
> | CLEAN arch/arm/kernel
> | CLEAN firmware
> | CLEAN kernel
> | CLEAN lib/raid6
> | CLEAN lib
> | CLEAN usr
> | CLEAN arch/arm/boot/compressed
> | CLEAN arch/arm/boot
> | CLEAN drivers/tty/vt
> | CLEAN drivers/video/logo
> | CLEAN vmlinux System.map
> | xargs: rm: Argument list too long
> | make: *** [clean] Error 126
> | make: Leaving directory
> `/home/developer/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/work/beaglebone-angstrom-linux-gnueabi/linux-ti33x-psp-3.2.34-r18a+gitr720e07b4c1f687b61b147b31c698cb6816d72f01/image/usr/src/kernel'
> | ERROR: oe_runmake failed
> NOTE: package
> linux-ti33x-psp-3.2.34-r18a+gitr720e07b4c1f687b61b147b31c698cb6816d72f01:
> task do_install: Failed
> ERROR: Task 2
> (/home/developer/setup-scripts/sources/meta-ti/recipes-kernel/linux/
> linux-ti33x-psp_3.2.bb, do_install) failed with exit code '1'
> NOTE: Tasks Summary: Attempted 904 tasks of which 236 didn't need to be
> rerun and 1 failed.
>
> Summary: 1 task failed:
> /home/developer/setup-scripts/sources/meta-ti/recipes-kernel/linux/
> linux-ti33x-psp_3.2.bb, do_install
> Summary: There were 9 WARNING messages shown.
> Summary: There was 1 ERROR message shown, returning a non-zero exit code.
>
> ---------------------------------------------------------------------------------
>
> Am I doing something stupid here?
>
> Any help would be appreciated.
>
> Thanks,
>
> Chris
>
>
> _______________________________________________
> Angstrom-distro-devel mailing list
> Angstrom-distro-devel@linuxtogo.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
>
_______________________________________________
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
