Re: [yocto] Olb Beagleboard support

To chime in: I successfully used kernel and root fs built by plain Yocto, meta and meta-yocto layers, for C4 and xM Beagleboards. On some C4 with certain MMC I had the issue that the kernel would not be able to mount the root fs and just sat there waiting. Unplugging and replugging the MMC resets t

Re: [yocto] do_fetch failure with libowl-0.1

Looks like the downloaded source file is corrupted although that should be caught by the checksum verification. Try to locate the source file in DL_DIR and unpack it manually. If it is corrupt delete the file, run a cleanall on the libowl recipe and run bitbake again. Rudi On Nov 14, 2012 10:39 AM

Re: [yocto] should users be able to run yocto's pre-built images standalone?

Hi Robert, > a basic question -- is it supported that users be able to download and > run yocto's pre-built QEMU images without having to download an entire > build system, and set up bitbake, etc? theoretically, of course, it > can be done, but it's not set up to do it conveniently (if it even

Re: [yocto] dev manual is confusing as to whether a layer *must* be named "meta-..."

The meta- prefix for layers is purely customary convention and has been adopted as best practice. There is no technical reason for it. The only place where the name of a layer directory is referenced is in bblayers.conf. Technically, you can give your layer any name you want to as long as it is com

Re: [yocto] Busybox still old version: Still looking for a clear understanding of an old mystery.

Brian, What are you exactly referring to as "new version"? The package version that bitbake builds is defined by the recipe, through the version designation in the recipe's file name or through explicitly setting PV. I think what you are trying to do is to modify the busybox configuration and the

[yocto] PROVIDES for Yocto Kernel Recipes

I apologize if that has been brought up before. The linux-yocto kernel recipes include the git tags into PV by explicitly setting: PV = "${LINUX_VERSION}+git${SRCPV}" This means that you cannot for example do bitbake linux-yocto-3.2 anymore because PROVIDES does not contain linux-yocto-3.2 but

Re: [yocto] PROVIDES for Yocto Kernel Recipes

an option since you would not get the bbappends. Cheers, Rudi On Thu, Feb 7, 2013 at 5:39 PM, Bruce Ashfield wrote: > > > > On Thu, Feb 7, 2013 at 8:22 PM, Rudolf Streif wrote: > >> I apologize if that has been brought up before. >> >> The linux-yocto kernel re

[yocto] [danny] core-image-minimal-dev is missing dev packages

This is weird and I do not have an explanation for it. For Danny: core-image-minimal-dev is missing the dev packages (pkg-dev) I build it but the packages are not there. The cause does not seem to be my setup because the core-image-minimal on the ADT download site is missing them too. The recipe

Re: [yocto] [danny] core-image-minimal-dev is missing dev packages

Thanks, Paul. Not sure however. I should have included that I used plain old i586 architecture. There should be no dashes/underscore issues there. :rjs On Feb 9, 2013 6:30 AM, "Paul Eggleton" wrote: > On Friday 08 February 2013 19:17:35 Rudolf Streif wrote: > > This is weir

Re: [yocto] [danny] core-image-minimal-dev is missing dev packages

I have not verified every single dev package but the linker files in /usr/lib/ and related are missing. You cannot link against a dev image sysroot. That used to work. :rjs On Feb 9, 2013 9:19 AM, "Rudolf Streif" wrote: > Thanks, Paul. Not sure however. I should have included that

Re: [yocto] [danny] core-image-minimal-dev is missing dev packages

that works. /usr/lib contains as expected arm-poky-linux-gnueabi. I am not sure what the status is for PPC and MIPS. I have not tried them. :rjs On Tue, Feb 12, 2013 at 1:42 AM, Paul Eggleton < paul.eggle...@linux.intel.com> wrote: > On Saturday 09 February 2013 09:25:09 Rudolf Str

Re: [yocto] hob error

Hi Andre, You may want to send the content for layer.conf and bblayers.conf. However, you may have a typo if you copied and pasted the error message: ${BBPATH}:/home/andre/fsl-community-bsp/soucers/meta-fsl-arm which triggered exception Exception: variable BBPATH reference itself! It says "souc

Re: [yocto] The Yocto Project at upcoming conferences

> It appears that there will be a 2-day training session following the > conference as well (Sat-Sun): > > See > http://events.linuxfoundation.org/events/embedded-linux-conference/schedule > : > [Add-On] Building Embedded Linux with the Yocto Project Crash Course > (LF404)

Re: [yocto] select installation packages

Hi Andre, There actually is no recipe for building the nano editor in YP by default. Unless you added one, bitbake -b nano would result in this output ERROR: Unable to find any recipe file matching 'nano' I have attached a recipe for you to build nano and a patch to handle a configuration mist

Re: [yocto] The Yocto Project at upcoming conferences

From:* yocto-boun...@yoctoproject.org [mailto: > yocto-boun...@yoctoproject.org] *On Behalf Of *Rudolf Streif > *Sent:* Thursday, February 14, 2013 8:39 AM > *To:* John Mehaffey > *Cc:* Yocto Project > *Subject:* Re: [yocto] The Yocto Project at upcoming conferences > >

Re: [yocto] Updating uboot to v2013.01

Satya, Simply look at the u-boot recipes in meta/recipes-bsp/u-boot such as u-boot_2012.04.01.bb. You can simply copy it and name it u-boot_2013.01.bband then modify SRCREV to the revision that corresponds to the tag 2013.01 or 2013.01.01 in git.denx.de: for 2013.01: 3a9d879f6f64585b819af728b53b

Re: [yocto] Updating uboot to v2013.01

gt;>> utils it picks up? >>>> Then it might be that since I/we build u-boot as a separate package, >>>> but kernel lifts in the mkimage stuff, it works but the wrong package >>>> was used. >>>> In my case obviously compatible, but not recommended I gue

Re: [yocto] Issue with Quick Start Guide and Bitbake

Hi Michael, You have most likely forgotten to source your build environment: source /oe-init-build-env Poky includes BitBake but from the error message it look as if you are calling a BitBake that is installed on your system in /usr/bin. Rudi On Thu, Feb 21, 2013 at 4:29 AM, Micheal Donohue

Re: [yocto] Updating uboot to v2013.01

nd we may discuss the situation depending on the problem, >> >> Greetings & Regards, >> Satya >> >> >> On Thu, Feb 21, 2013 at 5:28 PM, Rudolf Streif < >> rstr...@linuxfoundation.org> wrote: >> >>> Satya, >>> >&g

Re: [yocto] Updating uboot to v2013.01

device tree compiler. You should use the >> uboot tools/version as they come with the package. Not the one used by the >> host distro. To me this is not a proper solution. >> >> >> >> On Thu, Feb 21, 2013 at 5:28 PM, Rudolf Streif < >> rstr...@linuxfoundat

Re: [yocto] Updating uboot to v2013.01

gt; Greets, > Satya > > > On Tue, Feb 26, 2013 at 6:21 PM, Rudolf Streif < > rstr...@linuxfoundation.org> wrote: > >> Satya, >> >> So what exactly do you get when building the kernel? No image at all in >> tmp/deploy/images? What do the log

Re: [yocto] uboot.bin and rootfs but not uImage

Satya, your machine configuration file looks ok as far as I can tell. Did you get an error message when building the kernel? Did you try to build just the kernel e.g. bitbake linux-yocto? :rjs On Mon, Feb 25, 2013 at 11:31 PM, Satya Swaroop Damarla < swaroop.dama...@gmail.com> wrote: > Hello G

Re: [yocto] uboot.bin and rootfs but not uImage

%" That should do it. :rjs On Thu, Feb 28, 2013 at 11:21 AM, Satya Swaroop Damarla < swaroop.dama...@gmail.com> wrote: > Yes I got an error message when I was building the kernel... Actuallly I > have a kernel git given by the company.... I downloaded it and is in my > wor

Re: [yocto] Newbie trying to get started

Hi Paul, It does not matter where you unpack the meta-intel tarball to. All that matters is that you include it in the bblayers.conf file of your build environment. Yes, you are right that you want to create a new build environment for your new Atom project. Do so with cd yocto source poky/oe-i

Re: [yocto] linux 3.8

Bruce, On Fri, Mar 1, 2013 at 9:29 AM, Bruce Ashfield wrote: > But note, Greg is talking specifically about LTSI, we don't > expect more than one LTSI per year, and we are already locked into > the LTSI 3.4. > > However, as far as I understand it the 3.4 snapshot in git.yoctoproject.org is from

Re: [yocto] yocto beaglebone build no uImage on DOS partition.

Edward, Yes, you do need of course a uImage which is the Linux kernel image with the necessary wrapper for u-boot. If you do not have one after your build finishes in /tmp/deploy/images then building the Linux kernel failed and you should look for error messages. To build just the kernel you can

Re: [yocto] uboot.bin and rootfs but not uImage

t;> >> >> >>> One more thing is the skidata-carrier_defconfig is already in the >>> directory git I mentioned above at >>> "/home/damarla/linux-skidata.**git/arch/arm/configs/skidata-** >>> carrier_defconfig" >>> ... When compi

Re: [yocto] [poky] FW: Is there a guide for adding a board to the yocto system?

On Tue, Mar 5, 2013 at 5:19 PM, Rifenbark, Scott M < scott.m.rifenb...@intel.com> wrote: > Isn’t this a matter of creating a BSP layer for the desired board? If > so, doesn’t one try to find a similar board from one of the > supported/released yocto BSPs and then modify that to create the custom

Re: [yocto] Question about file systems

There is a major difference between ext3 and ext4 which is called "delayed (block) allocation." Delayed allocation of blocks increases the risk of data loss in certain circumstances. While ext3 typically syncs cache to disk every 5s, it can take 2min with ext4. On Wed, Mar 6, 2013 at 10:20 AM,

Re: [yocto] Hob and bitbake problem!

Hi Florin, You will need to look in the log file of the compile task for Qt4 to find out what's going on: see /home/user/poky-danny-8.0/ build/tmp/work/core2-poky-linux/qt4-x11-free-4.8.1-r47. 1/temp/log.do_compile.28027 In the log file you will see the output of qmake and the compiler. :rjs ___

Re: [yocto] RFC: Post build configuration

The process that you are describing is commonly called "device provisioning." I have experienced this process from different angles: working for a company making functional test equipment for electronics production lines and working for a company providing software for set-top boxes. >From this ex

Re: [yocto] i think the list of "required software" needs to be clarified

In a sense yes. From how I understand it, anything that is listed as a required utility in SANITY_REQUIRED_UTILITIES does not even have to be listed in ASSUME_PROVIDED. The required native utilites should fail the sanity test right away if they are not there. For any dependency listed in ASSUME_PR

Re: [yocto] RFC: Post build configuration

Ramana, Maybe I do not understand what exactly you are looking for. Maybe you have some concrete examples. Anything that somehow changes the configuration of the target has to go into the root file system one way or the other. You can easily include packages into the root file system by adding th

Re: [yocto] potentially confusing explanation of "defconfig" in kernel dev manual

That's how I interpret it: Wholesale = defconfig Incremental = configuration fragments Following kernel practices my defconfig files always have a working configuration and then I use configuration fragments to make adjustments. But of course you can have an incomplete configuration in defconfig

Re: [yocto] runqemu: Could not initialize SDL(No available video device) - exiting

If you do not have libsdl1.2-dev (Ubuntu) installed on your dev/host system then qemu will be built without video support. The newer YP reference manual lists that library as optional for host systems with graphics support. Rudi On Apr 17, 2013 8:15 PM, "Trevor Woerner" wrote: > On Mon, Apr 15,

Re: [yocto] runqemu: Could not initialize SDL(No available video device) - exiting

> I would have assumed that if something was missing from my host, then > I would not have been able to run the virtual machine using the > qemu-system-i386 that I had compiled for my host natively outside of > Yocto? As it happened, using my own qemu the images ran fine, but when > I tried using t

Re: [yocto] runqemu: Could not initialize SDL(No available video device) - exiting

> Should YP be trying to build its own copy of libSDL (with the -devel) > if it finds some part of libSDL (i.e. the header files) is missing > from the host? This is almost like a "host contamination" issue, no? > You are raising an interesting point to which I have no answer. YP has a recipe to b

Re: [yocto] Patching from .bbappend

You got it figured out? Simply add FILESEXTRAPATHS_prepend := "${THISDIR}/${P}:" SRC_URI += "mypatch.patch" PRINC := "${@int(PRINC) + 1}" to your bbappend and put your patch in a subdirectory - relative to the recipe. :rjs ___ yocto mailing list yocto

Re: [yocto] building the BitBake manual

Scott, On FC18 these packages are also called xmlto and dblatex. xmlto has a dependency on flex which the package manager should install automatically. dblatex has dependencies on texlive-*. :rjs On Wed, May 15, 2013 at 9:07 PM, Rifenbark, Scott M < scott.m.rifenb...@intel.com> wrote: > When

Re: [yocto] building the BitBake manual

And I hit the send button too early: on FC18 you also have to install texlive-multirow. :rjs On Wed, May 15, 2013 at 10:16 PM, Rudolf Streif wrote: > Scott, > > On FC18 these packages are also called xmlto and dblatex. > > xmlto has a dependency on flex which the package manager

Re: [yocto] ADT Install Issues

What root file system are you using with your Eclipse ADT setup? If you are using one of the default ones that you can specify in adt_installer.conf or your own? In any case it looks as if your root file system image is not suitable for development work. You would need to use image targets that en

Re: [yocto] ADT Install Issues

Jerry, Sorry for the delayed response. I am catching up with my email while traveling. The minimal-dev images should not be giving you the error that you mentioned in your original e-mail. They did not with the 1.2 Denzil release, at least not for i586 and ARM (I did not try PPC or MIPS). However

Re: [yocto] Documenting YP Development Environment in more detail

Hi Trever et al: > If I were writing a book about Yocto/OE, This is a project I am currently working on, a book about the Yocto Project. The goal is to enable readers to do practical projects with YP. As the subject matter for the project described in the book I have chosen a home automation p

Re: [yocto] Documenting YP Development Environment in more detail

Hi Trevor, On Mon, Jun 24, 2013 at 5:56 AM, Trevor Woerner wrote: > Awesome! That's great news! I was hoping someone would "beat me to it" > :-) I look forward to reading it once it's done. Do you have a > publisher or an expected release date? > > Yes, I do. Pearson and the release date is earl

Re: [yocto] Documenting YP Development Environment in more detail

> not integrate with yocto directly. but use it to 'manage' the set of trees > that are required when using OE/Yocto. The gumstix guys are using it, see > [1], and we are moving toward it at linaro too, to manage our builds [2] > > [1] https://github.com/gumstix/Gumstix-YoctoProject-Repo > [2] http

Re: [yocto] possible variations on building bootable SD card for BBB?

> so -- short form of the question -- how many ways are there to build > a bootable SD card for the BBB using different layers? There are many ways to skin a cat. I created my own BeagleBone BSP layer that builds u-boot and a 3.2 kernel. The idea being to demonstrate how to create a BSP layer.

[yocto] Task Build Issue

I created this task for test purposes: DESCRIPTION = "My Custom Tasks" LICENSE = "MIT" LIC_FILES_CHKSUM = "file://${COREBASE}/LICENSE;md5=3f40d7994397109285ec7b81fdeb3b58 \ file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420" PACKAGES = "\ task-mytask-apps \ task-my

Re: [yocto] Task Build Issue

Thank you, Khem. That does resolve the problem. Using just ALLOW_EMPTY = "1" would also cover the other packages, I suppose. :rjs On Fri, Feb 3, 2012 at 9:04 PM, Khem Raj wrote: > On Fri, Feb 3, 2012 at 9:03 PM, Khem Raj wrote: >> add ALLOW_EMPTY_ task-mytask-apps = "1" to your recipe > > no sp

Re: [yocto] Build Error

Hi Sean, icon-naming-utils fails because the download site does not have the source archive available. You can download it from h ttp://downloads.yoctoproject.org/mirror/sources/icon-naming-utils-0.8.7.tar.gz For the

Re: [yocto] Adding test files to an image

Jeff, Use hyphen instead of underscore for the subdirectory SRC_URI: SRC_URI = "file://myvideos-1.0/myvideos-**1.0.tar.gz" and of course for the subdirectory in the subdirectory where the recipe is located. The file fetcher copies the entire path myvideos-1.0/myvideos-1.0.tar.gz to ${WORKDIR}.

Re: [yocto] contradictory explanations of IMAGE_INSTALL in yocto manuals

I tried the versions _append and += as well as _prepend and =+ with the IMAGE_INSTALL and other variables. So far I have not run into any issues where one would behave differently from the other. The only thing you have to remember with the _append and _prepend versions is that you have to include

Re: [yocto] contradictory explanations of IMAGE_INSTALL in yocto manuals

P. J. Day wrote: > On Fri, 9 Mar 2012, Rudolf Streif wrote: > > > I tried the versions _append and += as well as _prepend and =+ with > > the IMAGE_INSTALL and other variables. So far I have not run into > > any issues where one would behave differently from the other. The &

Re: [yocto] contradictory explanations of IMAGE_INSTALL in yocto manuals

I tried the versions _append and += as well as _prepend and =+ with the IMAGE_INSTALL and other variables. So far I have not run into any issues where one would behave differently from the other. The only thing you have to remember with the _append and _prepend versions is that you have to include

Re: [yocto] tentative list of vars to be dropped from variable glossary

Another variable that seems to be dropped from the latest 1.1.1 revision of the Reference Manual is BBMASK. In previous versions of the manual it was explained that this variable can be used to remove packages from images. However, that did not work for me and it did not surprise me either. To inc

Re: [yocto] can all of the licensing discussion be centralized in an appendix?

> > >> there's *way* too much coverage of licensing sprinkled throughout. > >> most people are not going to care about licensing until the time comes > >> to maybe start distributing their BSP. > > The ability of collecting licensing information, tracking license changes and providing the license i

Re: [yocto] can all of the licensing discussion be centralized in an appendix?

fth section should then just reference the BSP manual for BSPs. Finally for my concept, we need to find a home for x32. I would put that under an "Advanced Topics" section which could act as a container for other stuff too such as multi-lib etc. Rudi > > > *From:* yocto-bou

Re: [yocto] tentative list of vars to be dropped from variable glossary

Thanks, Richard. Clearer now but not entirely. > >> BBMASK removes recipes from being parsed. It does not remove them from > >> images although that would I guess be an indirect result since you could > >>no longer build them. > > Yes, it removes it from being parsed. I used, for test although no

Re: [yocto] can all of the licensing discussion be centralized in an appendix?

> > ** ** > > I appreciate your help, > > Scott > > ** ** > > *From:* rstr...@linuxfoundation.org [mailto:rstr...@linuxfoundation.org] *On > Behalf Of *Rudolf Streif > *Sent:* Monday, March 26, 2012 4:02 PM > *To:* Rifenba

Re: [yocto] which yocto doc explains bitbake assignment variations?

Robert, I don't think that the YP manuals do. That's more Bitbake. However, here is some copied out of my docs. (List excuse the formatting. It's copied from an HTML page.) - *Variable Setting (=)* Set a variable by assigning it a value using the *=* sign. Values must be surrounded

Re: [yocto] which yocto doc explains bitbake assignment variations?

= following a ??= will set the variable. Just try it. Put a variable (FOO) in local.conf and use bitbake -e | grep FOO FOO ??= "bar" FOO ?= "barbar" :rjs On Thu, Mar 29, 2012 at 3:34 PM, Robert P. J. Day wrote: > > just to be absolutely clear so i don't misunderstand:

Re: [yocto] Network booting

> Is there an easy way to have a system boot and load the rootfs from a > network server? > > The classic way is to serve the root file system from an NFS server. You will have to pass the root=/dev/nfs and nfsroot=[:][,] to your kernel via boot loader. Every system you want to boot this way will

[yocto] [meta-freescale] [meta-fsl-ppc] MPC8572 Machine with Dylan

I am looking to build for MPC8572 with Dylan and checked out the meta-fsl-ppc BSP layer. Seems like support for that machine was removed in May [1]. The reason given was " *u-boot code base can not support mpc85xx for sdk 1.3.2". Howerver, that was contested in a follow-up e-mail. Interestingly, th

Re: [yocto] [meta-freescale] [meta-fsl-ppc] MPC8572 Machine with Dylan

; QorIQ SDK 1.3.2 uses denzil of Poky, you can use danny/denzil/edison for > image build of mpc85xx series. > > ** ** > > ** ** > > Best Regards, > > ** ** > > Zhenhua > > ** ** > > *From:* yocto-boun...@yoctoproject.org [mailto: > yocto-b

Re: [yocto] Custom defconfig is not used

Diego, You are appending a kernel recipe that uses the Linux Yocto tooling. The defconfig is essentially comprised of many different pieces from the meta branch of the Yocto kernel repository and optional configuration fragments that you provide. This tooling will not recognize a defconfig file yo

Re: [yocto] uimage instead of zImage

Edward, Your zImage is booting fine. The kernel starts and then tries to mount the root file system. But it cannot find it. It's looking for a UBIFS but cannot find it: . > VFS: Cannot open root device "ubi0:rootfs" or unknown-block(0,0): error -19 > Please append a correct "root=" boot option;

Re: [yocto] uimage instead of zImage

Hi Edward, This is what I have in the uEnv.txt file > > > bootcmd="" > bootfile="zImage" > ethact="" > loadaddr="" > nandboot="" > nandroot="" > nandrootfstype="" > nandargs="" > loaduimage="" > loaduimagefat="" > nandboot="" > mpurate="auto" > bootcmd="mmc rescan ; fatload mmc 0:1 0x8030 zIm

Re: [yocto] FW: curious about ref manual, sec 6.1.11, oe-init-build-env-memres

I am picking up this thread since I have been mocking around with the bitbake server. The use of the oe-init-build-env-memresscript is source oe-init-build-env-memres The documentation suggests that you can omit the portnumber in which case the script would use 12345. According to my tests wit

Re: [yocto] poky-tiny, boot and filesystems

John, What is your actual problem? You appended the tiny-init recipe and your changes do or do not get put into the rootfs? If you could post your recipe then folks can look at it. As far as boot time is concerned, you need to distinguish boot loader and kernel boot from user space. It looks as i

Re: [yocto] fetcher from gitpod

Hi Robert, Did you try something like SRC_URI = "git://gp@gitpod:linux-stable.git" The git fetcher supports authentication with a username, if that is your concern. Regards, Rudi On Thu, Jan 23, 2014 at 2:19 PM, Robert Berger < gm...@reliableembeddedsystems.com> wrote: > Hi, > > I would like

Re: [yocto] Dogfooding and usability testing Toaster

Hi Belen, That is exciting. I just ran with it and started a build with toaster in the background. A couple of observations from the get-go: - South 0.8.4 is also needed in addition to Django. The Toaster Wiki [1] does not say that but the Contribute to Toaster page [2] does. - You need

Re: [yocto] Question about remote debugging via gdbserver

Hi Federico, I knew that I can add source paths to the debugger. > Ok, if that's not the issue what exactly is not working for you? > I see in your debug profiles that you have some binaries eg "ls". Did you > import that binary from sysrootfs on your build machine? Can you please > tell me the

Re: [yocto] Question about remote debugging via gdbserver

with eclipse. Now, if I want to enter into a function of gstreamer > libs (e.g. gst_pipeline_new), > what should I have to do? > > Federico > > > > > > 2014-04-16 21:22 GMT+02:00 Rudolf Streif : > > Hi Federico, >> >> I knew that I can add source paths t

Re: [yocto] is anyone giving a yocto talk at linuxcon in chicago in august?

> > > i would think *someone* would be doing a yocto talk at linuxcon in > august. if not, i'll propose one since i need an excuse to go. if one > is already on the schedule, i'll propose something else. > > The typical target for YP (and the YP Dev Day) were the Embedded Linux Conferences not th

Re: [yocto] is anyone giving a yocto talk at linuxcon in chicago in august?

> > >> i think that's what i'm going to submit. tomorrow's the submission >> deadline so i have to get something in quick. i figure i'll submit >> something like "Building an Embedded Linux System Using YoctoProject", >> using the BeagleBone Black as the platform example. >> >> > I have done a PO

[yocto] How is the list in package.manifest derived?

I used poky-denzil-7.0 to build a core-image-minimal for the BeagleBoard. Now I am looking for a list of everything that went into my image together with the license information. The logical thing seems to be ${TMPDIR}/deploy/licenses/core-image-minimal-beagleboard-/package.manifest: base-files ba

Re: [yocto] How is the list in package.manifest derived?

Thanks for your response, Beth. I am using the default: RPM. :rjs On Tue, May 15, 2012 at 3:53 PM, Flanagan, Elizabeth < elizabeth.flana...@intel.com> wrote: > On Tue, May 15, 2012 at 3:38 PM, Rudolf Streif > wrote: > > I used poky-denzil-7.0 to build a core-image-minimal f

Re: [yocto] How is the list in package.manifest derived?

Related to that I have another question. If I use this recipe to create an image DESCRIPTION = "A small image with gcc" IMAGE_INSTALL = "task-core-boot gcc" LICENSE = "MIT" inherit core-image and call it myimage.bb ${TMPDIR}/deploy/icenses will contain a subdirectory named myimage. However, the

Re: [yocto] How is the list in package.manifest derived?

>> I think kernel and uboot are not bundled into image but kernel modules are why >> module-init-tools does not appear there might be a bug Yes, that is technically of course correct. However, the idea of package.manifest and license.manifest should be to provide a list of everything that goes in

[yocto] Building linux-yocto kernel for BeagleBone

Has anyone tried to build a linux-yocto kernel for the BeagleBone? I understand that there is the meta-ti layer to build an image for the BBone but the recipes are not utilizing the Yocto Project kernels. I know that the OMAP3 CPU of the BBoard is different form the AM355x CPU on the BBone. Howeve

Re: [yocto] Building linux-yocto kernel for BeagleBone

plain BeagleBoard kernel and MLO and u-boot.img created by Yocto and it did not work. Any suggestions would be appreciated. Rudi On Sun, May 27, 2012 at 12:34 PM, Sanyaade Adekoya wrote: > Hi, > According to Ti, BeagleBone is just a small BeagleBoard in a small factor > so a common ba

[yocto] [ADT] Sysroot setup issue

Hi, I am trying to setup the ADT using an ADT installer. I have downloaded the installer from http://downloads.yoctoproject.org/releases/yocto/yocto-1.2.1/adt_installer/ as well as created my own installer using a build environment with Denzil 7.0.1. The adt_installer.conf contains these settings

[yocto] [Eclipse ADT] Eclipse plugin download site is not a valid Eclipse site

The download site http://downloads.yoctoproject.org/releases/eclipse-plugin/1.2.1/indigo/ for the Eclipse plugin is not a correctly setup Eclipse download site. The site root does not have the correct layout for Eclipse to be able to recognize it: / content.jar artifacts.jar features/

[yocto] [ADT] Autotools: configure using --with-libtool-sysroot

I tried, according to the documentation at http://www.yoctoproject.org/docs/current/adt-manual/adt-manual.html#extracting-the-root-filesystem), to configure and compile the autotooled GNU Hello World Applcation for x86 and ARM with ./configure --host=i586-poky-linux --with-libtool-sysroot=${YOCTOD

Re: [yocto] [ADT] Sysroot setup issue

** > > Can you help answer or look into the boot dir missing kernel file issue > that Rudi’s reporting to see whether it’s a bug on our end? > > ** ** > > Thanks, > > Jessica > > ** ** > > *From:* yocto-boun...@yoctoproject.org [mailto: > yo

Re: [yocto] [ADT] Autotools: configure using --with-libtool-sysroot

Thanks, Richard. > Which libtoolize script/binary is being used (try "which libtoolize")? The one from the cross-toolchain: $ which libtoolize /opt/poky/1.2.1/sysroots/x86_64-pokysdk-linux/usr/bin/libtoolize > It probably works fine since your sample app isn't actually linking to > anything. Th

Re: [yocto] Beaglebone BSP for denzil?

Hey Scott, I am doing the same thing for a Linux Foundation class. The root filesystem that YP builds for the BBoard works just fine for the BBone. That's at least true for core-image-minimal. I tested that with the kernel that comes with the BBone. The kernel does not work. The BBoard has an OM

Re: [yocto] Beaglebone BSP for denzil?

Typo correction: the BBone has an AM3359 CPU. On Aug 31, 2012 6:44 PM, "Rudolf Streif" wrote: > Hey Scott, > > I am doing the same thing for a Linux Foundation class. > > The root filesystem that YP builds for the BBoard works just fine for the > BBone. That&#x

Re: [yocto] Beaglebone BSP for denzil?

Yes, there were a lot of patches that I applied to the upstream kernel. It worked but I do not think that they are all required. That's what I am currently trying to figure out. On Aug 31, 2012 8:03 PM, "Khem Raj" wrote: > On Fri, Aug 31, 2012 at 6:44 PM, Rudolf Streif >

Re: [yocto] Eclipse Juno Plugin?

Hi Axel, The autotools.ui package is there in Juno given that you installed Autotools support for CDT. However, it's a newer version and the YP Eclipse plugin 1.2 requires exactly version 1.0.0 of the CDT Autotools support. Until the 1.3 plugin is released and you can point Eclipse to the downloa

Re: [yocto] Beaglebone BSP for denzil?

nder wrote: > * Rudolf Streif [120901 08:15]: > > > Yes, there were a lot of patches that I applied to the upstream kernel. > It > > worked but I do not think that they are all required. That's what I am > > currently trying to figure out. > > Sounds interesti

[yocto] [linux-yocto] 'bitbake linux-yocto' after 'bitbake linux-yocto -c compile -f' does not create image

In Denil modifying kernel parameters and doing bitbake linux-yocto -c compile -f bitbake linux-yocto worked perfectly fine. The tasks after compile were rerun and the new kernel copied to tmp/deploy/images In Edison 7.0.1 this does not seem to work anymore. The tasks do not rerun and the kernel

Re: [yocto] [linux-yocto] 'bitbake linux-yocto' after 'bitbake linux-yocto -c compile -f' does not create image

t 8:06 AM, Rudolf Streif > wrote: > > bitbake linux-yocto -c compile -f > > bitbake linux-yocto > > > > worked perfectly fine. The tasks after compile were rerun and the new > kernel > > copied to tmp/deploy/images > > > > In Edison 7.0.1 this does

Re: [yocto] [linux-yocto] 'bitbake linux-yocto' after 'bitbake linux-yocto -c compile -f' does not create image

. So it's not isolated to one system only. Thanks, Rudi On Wed, Sep 12, 2012 at 9:01 AM, Paul Eggleton < paul.eggle...@linux.intel.com> wrote: > On Wednesday 12 September 2012 08:16:46 Rudolf Streif wrote: > > Thanks, Chris. From what bitbake version on is that command availabl

Re: [yocto] The term Package as used in the YP docs

+1 I agree with Scott's definition. In the general Linux context a Package is a compilation of binaries, documentation, development files, etc. wrapped up in a format that can be used by a package management system to install it on a target system. It is somewhat confusing that YP and OE use the

Re: [yocto] The term Package as used in the YP docs

[mailto: > yocto-boun...@yoctoproject.org] On Behalf Of Paul Eggleton > Sent: Friday, September 28, 2012 11:34 AM > To: Rudolf Streif > Cc: yocto@yoctoproject.org > Subject: Re: [yocto] The term Package as used in the YP docs > > On Friday 28 September 2012 11:27:37 Rudolf St

Re: [yocto] The BitBake equivalent of "Hello, World!"

Hi Patrick, I think I understand what you are looking for. I created this Bitbake Hello World for a training class. It just uses 'raw' Bitbake and a very basic recipe to build the Nano editor (including download from the project site). You need to have a couple of things in place to make this wor

[yocto] [Poky] Baking core-image-minimal with Poky from Master fails with libffi dependency

I checked out Poky from Master and tried to build core-image-minimal. do_rootfs failed on the libffi dependency [1]. Is that known/expected? :rjs [1] bitbake core-image-minimal Loading cache: 100% || ETA:

Re: [yocto] [Poky] Baking core-image-minimal with Poky from Master fails with libffi dependency

> On 10/03/2012 04:21 PM, Rudolf Streif wrote: > >> I checked out Poky from Master and tried to build core-image-minimal. >> do_rootfs failed on the libffi dependency [1]. Is that known/expected? >> >> This is interesting, I just tried it also, and it is working, see be

Re: [yocto] The BitBake equivalent of "Hello, World!"

[Warning: lengthy post, and probably boring to most.] My Bitbake "Hello World" is a little more than a basic "Hello World". It's idea is to incorporate a layer and use a structure similar to what OE and Yocto are using. You can do it simpler if you want to. I did this a while ago with Bitbake 1.12

Re: [yocto] [Poky] Baking core-image-minimal with Poky from Master fails with libffi dependency

feed > > http://lists.linuxtogo.org/pipermail/openembedded-core/2012-September/029759.html > > > 2. If 1. won't work, recompile libowl si libclutter as a workaround. > > wont fix it on target > > Cheers, > > > > > ag > > On Oct 4, 2012 4:40 AM, &qu

  1   2   >