[yocto] beagleboard not booting
Hello, On a previous posting Bruce Ashfield posted *** I know that we had to disable PREEMPT to get some of the mmc's to detect and boot, but I can't tell if this is the same thing from the trace. *** I did not understand. Which PREEMPT. in the file /home/vidal/poky/build/tmp/work/beagleboard-poky-linux-gnueabi/linux-yocto-3.0.32+git1+d282029891bba5440630a885b940dea5e34e3e2c_1+3ab688a78cac7b2e32afc83376a53370f2bd13b7-r4.0/linux-beagleboard-standard-build/.config # CONFIG_PREEMPT_RCU is not set CONFIG_PREEMPT_NONE=y # CONFIG_PREEMPT_VOLUNTARY is not set # CONFIG_PREEMPT is not set For beagleboard XM should this value be CONFIG_PREEMPT_NONE=n What would be the be the process to modify this and cause bitbake to build a new kernel?. Regards, Thanks for any help on getting this to boot. ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] beagleboard not booting
Hi, On 07/18/2012 03:54 AM, Edward Vidal wrote: Hello, The beagleboard that I am using is XM. Which revison? C? Can you try to build a mainline 3.4.x kernel and a mainline u-boot and see what happens? ...I'm afraid that I've seen too many people fix bugs by looking at debugger output, and that almost inevitably leads to fixing the symptoms rather than the underlying problems. --Linus My public pgp key is available at: http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0x90320BF1 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] beagleboard not booting
Hello, Close to the USB I see a C and close to speaker XM I am assuming the This is XM-C What would be the process to use 3.4.x kernel and a mainline u-boot. I am new to poky and don't know much about bit bake and openembedded. Can you suggest where to read about using a different kernel. Thanks every thing helps. ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] meta-baryon flexibility
On Tue, Jul 17, 2012 at 6:19 PM, Joshua Lock j...@linux.intel.com wrote:
On Tue, 2012-07-17 at 15:24 -0400, Jim Abernathy wrote:
In an effort to explore how independent a layer could be to the
underlying hardware, I took the meta-baryon NAS layer and got it built
from master using the n450 BSP. With that working I decided to replace
the n450 with sugarbay. While the n450 can support X11 and sato, it was
not generated by design in the baryon build.
However, when I changed to sugarbay, the build stops because X11 is
needed. To get around this I had to comment out some things in the
conf/machine/sugarbay.conf file in the BSP.
#XSERVER ?= ${XSERVER_IA32_BASE} \
# ${XSERVER_IA32_EXT} \
# ${XSERVER_IA32_I965} \
#
#VA_FEATURES ?= gst-va-intel va-intel
#MACHINE_EXTRA_RRECOMMENDS += ${VA_FEATURES}
Why didn't I have to do this in the n450??
The key piece is the MACHINE_EXTRA_RRECOMMENDS, which is telling Poky to
recommend the gst-va-intel and va-intel recipes when building this
machine.
RRECOMMENDS are automatically installed as a dependency (in this case,
of task-machine-base, see task-base.bbclass) but can be removed without
causing the package which pulled it in to be removed (see the Poky
reference manual glossary on *_RRECOMMENDS).
http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html
I'd suggest the RRECOMMENDS actually be added at a more granular level
than the machine. Perhaps you could file a bug against the BSP?
So if I understand this, it would be better for one of the image.bb files
that focused on media to include this particular RRECOMMENDS statement.
That way others not interested in media and graphic could still use the BSP
unchanged.
In my case the baryon build would work without modifiying the BSP
Jim A
Cheers,
Joshua
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Error: PATH contains '.' or '', which will break the build, please remove this.
On 18 July 2012 12:44, Axel Beierlein belatro...@freenet.de wrote: Hello, when i start bitbake core-image-minimal i get the Error PATH contains '.' or '', which will break the build, please remove this. But there is definitly no '' a whitespace or a point in my PATH. That error could be phrased better... If you don't have a . element, you probably have an empty element (which is what the '' is trying to say). For example: /usr/bin:/bin::/home/ross/bin The :: after /bin is bad, and it's this which needs to be removed. This is normally due to bad concatenation when extending $PATH. Ross ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] beagleboard not booting
On 07/18/2012 02:27 PM, Edward Vidal wrote: Hello, Close to the USB I see a C and close to speaker XM I am assuming the This is XM-C OK What would be the process to use 3.4.x kernel and a mainline u-boot. I am new to poky and don't know much about bit bake and openembedded. Can you suggest where to read about using a different kernel. Thanks every thing helps. I know people here will beat me up for my suggestion, but just use the toolchain you get with Yocto/Poky and build kernel/u-boot as ususal without it. Regards, Robert ...Rules of Optimization: Rule1: Don't do it. Rule 2 (for experts only): Don't do it yet. - M.A. Jackson (not the singer) My public pgp key is available at: http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0x90320BF1 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [Solved] Re: Error: PATH contains '.' or '', which will break the build, please remove this.
Hello, i've solved the Problem. A few posts ago there was a hint with a trailing : in a PATH Var. This was my Problem. Deleting the last : an it works! This hint could be also integrated in the error message. Regards Axel Am 18.07.2012 13:44, schrieb Axel Beierlein: Hello, when i start bitbake core-image-minimal i get the Error PATH contains '.' or '', which will break the build, please remove this. But there is definitly no '' a whitespace or a point in my PATH. What could be the reason for this Error? Regards Axel ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [Solved] Re: Error: PATH contains '.' or '', which will break the build, please remove this.
On 18 July 2012 13:07, Axel Beierlein belatro...@freenet.de wrote: Hello, i've solved the Problem. A few posts ago there was a hint with a trailing : in a PATH Var. This was my Problem. Deleting the last : an it works! This hint could be also integrated in the error message. I'm working on a patch to display the parsed PATH so you'll see the trailing empty element in that case. Ross ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] beagleboard not booting
On Wed, Jul 18, 2012 at 7:27 AM, Edward Vidal vidal.devel...@gmail.com wrote: Hello, Close to the USB I see a C and close to speaker XM I am assuming the This is XM-C What would be the process to use 3.4.x kernel and a mainline u-boot. I am new to poky and don't know much about bit bake and openembedded. We are just about to update preferred version of the kernel for the beagleboard to 3.4 .. but are just finishing with the other hardware references first. But everything you need for 3.4.x support is in the linux-yocto-3.4 standard/beagleboard branch. If you just change meta-yocto/conf/machine/beagleboard.conf to prefer the 3.4 yocto kernel, you are most of the way there, it currently points at 3.0 PREFERRED_VERSION_linux-yocto ?= 3.0% (you can also do this in your local.conf .. etc). Cheers, Bruce Can you suggest where to read about using a different kernel. Thanks every thing helps. ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto -- Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [RFC 1/8] plugins/sdk.doc.user: Added plugin for the yocto project documentation
From: Timo Mueller timo.muel...@bmw-carit.de This currently empty plugin will in the future contain the documentation of the yocto project converted to the eclipse help format. --- plugins/org.yocto.sdk.doc.user/.classpath |6 plugins/org.yocto.sdk.doc.user/.project| 28 .../.settings/org.eclipse.jdt.core.prefs |8 + .../org.yocto.sdk.doc.user/META-INF/MANIFEST.MF|7 + .../OSGI-INF/l10n/bundle.properties|3 ++ plugins/org.yocto.sdk.doc.user/build.properties|4 +++ plugins/org.yocto.sdk.doc.user/plugin.xml |4 +++ 7 files changed, 60 insertions(+), 0 deletions(-) create mode 100644 plugins/org.yocto.sdk.doc.user/.classpath create mode 100644 plugins/org.yocto.sdk.doc.user/.project create mode 100644 plugins/org.yocto.sdk.doc.user/.settings/org.eclipse.jdt.core.prefs create mode 100644 plugins/org.yocto.sdk.doc.user/META-INF/MANIFEST.MF create mode 100644 plugins/org.yocto.sdk.doc.user/OSGI-INF/l10n/bundle.properties create mode 100644 plugins/org.yocto.sdk.doc.user/build.properties create mode 100644 plugins/org.yocto.sdk.doc.user/plugin.xml diff --git a/plugins/org.yocto.sdk.doc.user/.classpath b/plugins/org.yocto.sdk.doc.user/.classpath new file mode 100644 index 000..bc74aab --- /dev/null +++ b/plugins/org.yocto.sdk.doc.user/.classpath @@ -0,0 +1,6 @@ +?xml version=1.0 encoding=UTF-8? +classpath + classpathentry kind=con path=org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/JavaSE-1.6/ + classpathentry kind=con path=org.eclipse.pde.core.requiredPlugins/ + classpathentry kind=output path=bin/ +/classpath diff --git a/plugins/org.yocto.sdk.doc.user/.project b/plugins/org.yocto.sdk.doc.user/.project new file mode 100644 index 000..d361cd4 --- /dev/null +++ b/plugins/org.yocto.sdk.doc.user/.project @@ -0,0 +1,28 @@ +?xml version=1.0 encoding=UTF-8? +projectDescription + nameorg.yocto.sdk.doc.user/name + comment/comment + projects + /projects + buildSpec + buildCommand + nameorg.eclipse.jdt.core.javabuilder/name + arguments + /arguments + /buildCommand + buildCommand + nameorg.eclipse.pde.ManifestBuilder/name + arguments + /arguments + /buildCommand + buildCommand + nameorg.eclipse.pde.SchemaBuilder/name + arguments + /arguments + /buildCommand + /buildSpec + natures + natureorg.eclipse.pde.PluginNature/nature + natureorg.eclipse.jdt.core.javanature/nature + /natures +/projectDescription diff --git a/plugins/org.yocto.sdk.doc.user/.settings/org.eclipse.jdt.core.prefs b/plugins/org.yocto.sdk.doc.user/.settings/org.eclipse.jdt.core.prefs new file mode 100644 index 000..f90fa9c --- /dev/null +++ b/plugins/org.yocto.sdk.doc.user/.settings/org.eclipse.jdt.core.prefs @@ -0,0 +1,8 @@ +#Fri Mar 04 13:59:33 CET 2011 +eclipse.preferences.version=1 +org.eclipse.jdt.core.compiler.codegen.inlineJsrBytecode=enabled +org.eclipse.jdt.core.compiler.codegen.targetPlatform=1.6 +org.eclipse.jdt.core.compiler.compliance=1.6 +org.eclipse.jdt.core.compiler.problem.assertIdentifier=error +org.eclipse.jdt.core.compiler.problem.enumIdentifier=error +org.eclipse.jdt.core.compiler.source=1.6 diff --git a/plugins/org.yocto.sdk.doc.user/META-INF/MANIFEST.MF b/plugins/org.yocto.sdk.doc.user/META-INF/MANIFEST.MF new file mode 100644 index 000..6bece6b --- /dev/null +++ b/plugins/org.yocto.sdk.doc.user/META-INF/MANIFEST.MF @@ -0,0 +1,7 @@ +Manifest-Version: 1.0 +Bundle-ManifestVersion: 2 +Bundle-Name: %plugin.name +Bundle-SymbolicName: org.yocto.sdk.doc.user;singleton:=true +Bundle-Version: 1.2.0.qualifier +Bundle-Vendor: %plugin.provider +Bundle-RequiredExecutionEnvironment: JavaSE-1.6 diff --git a/plugins/org.yocto.sdk.doc.user/OSGI-INF/l10n/bundle.properties b/plugins/org.yocto.sdk.doc.user/OSGI-INF/l10n/bundle.properties new file mode 100644 index 000..61e70de --- /dev/null +++ b/plugins/org.yocto.sdk.doc.user/OSGI-INF/l10n/bundle.properties @@ -0,0 +1,3 @@ +#Properties file for org.yocto.sdk.doc.user +Bundle-Vendor = yoctoproject.org +Bundle-Name = Yocto Project Documentation diff --git a/plugins/org.yocto.sdk.doc.user/build.properties b/plugins/org.yocto.sdk.doc.user/build.properties new file mode 100644 index 000..31e0140 --- /dev/null +++ b/plugins/org.yocto.sdk.doc.user/build.properties @@ -0,0 +1,4 @@ +bin.includes = plugin.xml,\ + .,\ + META-INF/,\ + OSGI-INF/ diff --git a/plugins/org.yocto.sdk.doc.user/plugin.xml b/plugins/org.yocto.sdk.doc.user/plugin.xml new file mode 100644 index 000..f422d55 ---
[yocto] [RFC 2/8] plugins/sdk.doc.user: Added empty table of contents
From: Timo Mueller timo.muel...@bmw-carit.de This is the preparation needed for adding documentation from the yocto project later on. --- .../org.yocto.sdk.doc.user/META-INF/MANIFEST.MF|1 + plugins/org.yocto.sdk.doc.user/build.properties|2 ++ plugins/org.yocto.sdk.doc.user/plugin.xml |7 +++ plugins/org.yocto.sdk.doc.user/toc.xml |3 +++ 4 files changed, 13 insertions(+), 0 deletions(-) create mode 100644 plugins/org.yocto.sdk.doc.user/toc.xml diff --git a/plugins/org.yocto.sdk.doc.user/META-INF/MANIFEST.MF b/plugins/org.yocto.sdk.doc.user/META-INF/MANIFEST.MF index 6bece6b..b28168f 100644 --- a/plugins/org.yocto.sdk.doc.user/META-INF/MANIFEST.MF +++ b/plugins/org.yocto.sdk.doc.user/META-INF/MANIFEST.MF @@ -5,3 +5,4 @@ Bundle-SymbolicName: org.yocto.sdk.doc.user;singleton:=true Bundle-Version: 1.2.0.qualifier Bundle-Vendor: %plugin.provider Bundle-RequiredExecutionEnvironment: JavaSE-1.6 +Require-Bundle: org.eclipse.help diff --git a/plugins/org.yocto.sdk.doc.user/build.properties b/plugins/org.yocto.sdk.doc.user/build.properties index 31e0140..cc18fce 100644 --- a/plugins/org.yocto.sdk.doc.user/build.properties +++ b/plugins/org.yocto.sdk.doc.user/build.properties @@ -1,4 +1,6 @@ bin.includes = plugin.xml,\ .,\ META-INF/,\ + toc.xml,\ OSGI-INF/ +src.includes = toc.xml diff --git a/plugins/org.yocto.sdk.doc.user/plugin.xml b/plugins/org.yocto.sdk.doc.user/plugin.xml index f422d55..367962c 100644 --- a/plugins/org.yocto.sdk.doc.user/plugin.xml +++ b/plugins/org.yocto.sdk.doc.user/plugin.xml @@ -1,4 +1,11 @@ ?xml version=1.0 encoding=UTF-8? ?eclipse version=3.4? plugin + extension + point=org.eclipse.help.toc +toc + file=toc.xml + primary=true +/toc + /extension /plugin diff --git a/plugins/org.yocto.sdk.doc.user/toc.xml b/plugins/org.yocto.sdk.doc.user/toc.xml new file mode 100644 index 000..4d30d0d --- /dev/null +++ b/plugins/org.yocto.sdk.doc.user/toc.xml @@ -0,0 +1,3 @@ +?xml version=1.0 encoding=UTF-8? +toc label=The Yocto Project Documentation +/toc -- 1.7.7.6 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [RFC 0/8] Integrate yocto documentation into eclipse
From: Timo Mueller timo.muel...@bmw-carit.de Hi, the documentation of the yocto project can currently be viewed online or as a separate pdf. When using the eclipse ide to develop software on base of a yocto sysroot and toolchain it would be convenient to access the relevant parts of the documentation from within the ide. In order to achieve this, I've generated eclipse help from yocto's documentation (adt-manual, yocto-project-qs). I have intergrated this documentation in the ide and it can now be accessed through the eclipse help center (Help - Help Contents). Please let me know what you think about it? Yocto's documentation is licensed under the Creative Commons Attribution-Share Alike 2.0 UK: England Wales (CCA-SA), which is incompatible to the Eclipse Public License 1.0. Thus I've created a standalone feature to simply redistribute the documentation avoiding licensing issues. Do you agree on the way this is structured? Cheers, Timo Timo Mueller (8): plugins/sdk.doc.user: Added plugin for the yocto project documentation plugins/sdk.doc.user: Added empty table of contents feature/sdk.doc: Added feature containing yocto documentation plugins feature/sdk.doc: Added org.yocto.sdk.doc.user plugin plugins/sdk.doc.user: Added yocto quick start guide feature/sdk: Added org.yocto.sdk.doc feature. features/sdk.site: Added eclipse help feature to update site plugins/sdk.doc.user: Added yocto adt manual features/org.yocto.sdk.doc/.project| 17 + features/org.yocto.sdk.doc/build.properties|5 + features/org.yocto.sdk.doc/feature.properties | 208 ++ features/org.yocto.sdk.doc/feature.xml | 40 ++ features/org.yocto.sdk.doc/license.html| 237 +++ .../sourceTemplateFeature/feature.properties | 208 ++ .../sourceTemplateFeature/license.html | 237 +++ features/org.yocto.sdk.site/category.xml |6 + features/org.yocto.sdk.site/site.xml |3 + features/org.yocto.sdk/feature.xml |5 + plugins/org.yocto.sdk.doc.user/.classpath |6 + plugins/org.yocto.sdk.doc.user/.project| 28 + .../.settings/org.eclipse.jdt.core.prefs |8 + .../org.yocto.sdk.doc.user/META-INF/MANIFEST.MF|8 + .../OSGI-INF/l10n/bundle.properties|3 + plugins/org.yocto.sdk.doc.user/about.html | 82 +++ plugins/org.yocto.sdk.doc.user/adt-manual-toc.xml | 61 ++ plugins/org.yocto.sdk.doc.user/build.properties| 14 + .../html/adt-manual/ch01.html | 90 +++ .../html/adt-manual/ch01s02.html | 166 + .../html/adt-manual/ch02.html | 450 + .../html/adt-manual/ch02s02.html | 56 ++ .../html/adt-manual/ch02s03.html | 182 ++ .../html/adt-manual/ch03.html | 97 +++ .../html/adt-manual/ch03s02.html | 78 +++ .../html/adt-manual/ch04.html | 675 .../html/adt-manual/ch04s02.html | 94 +++ .../html/adt-manual/ch04s03.html | 77 +++ .../html/adt-manual/ch04s04.html | 37 ++ .../html/adt-manual/ch04s05.html | 65 ++ .../html/adt-manual/ch04s06.html | 100 +++ .../html/adt-manual/ch04s07.html | 161 + .../html/adt-manual/ch04s08.html | 184 ++ .../html/adt-manual/ch05.html | 112 .../html/adt-manual/ch05s02.html | 41 ++ .../html/adt-manual/index.html | 260 plugins/org.yocto.sdk.doc.user/html/book.css |1 + .../yocto-project-qs/figures/building-an-image.png | Bin 0 - 14891 bytes .../figures/using-a-pre-built-image.png| Bin 0 - 12733 bytes .../yocto-project-qs/figures/yocto-environment.png | Bin 0 - 73095 bytes .../figures/yocto-project-transp.png | Bin 0 - 8626 bytes .../html/yocto-project-qs/index.html | 542 plugins/org.yocto.sdk.doc.user/plugin.xml | 19 + plugins/org.yocto.sdk.doc.user/toc.xml |9 + .../yocto-project-qs-toc.xml | 32 + 45 files changed, 4704 insertions(+), 0 deletions(-) create mode 100644 features/org.yocto.sdk.doc/.project create mode 100644 features/org.yocto.sdk.doc/build.properties create mode 100644 features/org.yocto.sdk.doc/feature.properties create mode 100644 features/org.yocto.sdk.doc/feature.xml create mode 100644 features/org.yocto.sdk.doc/license.html create mode 100644 features/org.yocto.sdk.doc/sourceTemplateFeature/feature.properties create mode 100644 features/org.yocto.sdk.doc/sourceTemplateFeature/license.html create mode 100644 plugins/org.yocto.sdk.doc.user/.classpath create mode 100644
[yocto] [RFC 4/8] feature/sdk.doc: Added org.yocto.sdk.doc.user plugin
From: Timo Mueller timo.muel...@bmw-carit.de The added plugin will contain the official documentation of the yocto project. --- features/org.yocto.sdk.doc/feature.xml |8 1 files changed, 8 insertions(+), 0 deletions(-) diff --git a/features/org.yocto.sdk.doc/feature.xml b/features/org.yocto.sdk.doc/feature.xml index f4b7605..1300f55 100644 --- a/features/org.yocto.sdk.doc/feature.xml +++ b/features/org.yocto.sdk.doc/feature.xml @@ -29,4 +29,12 @@ import plugin=org.eclipse.ui.cheatsheets/ import plugin=org.eclipse.help/ /requires + + plugin + id=org.yocto.sdk.doc.user + download-size=0 + install-size=0 + version=0.0.0 + unpack=false/ + /feature -- 1.7.7.6 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [RFC 3/8] feature/sdk.doc: Added feature containing yocto documentation plugins
From: Timo Mueller timo.muel...@bmw-carit.de The project documentation of yocto is licensed under the Create Commons Attribution Share Alike 2.0 (CCA-SA). Because the plugins containing this documentation cannot be licensed under the Eclipse Public License 1.0, as it is not compatible to the CCA-SA, this feature will contain all plugins licensed by the CCA-SA. The idea is to cleanly separate content licensed by the different licenses. --- features/org.yocto.sdk.doc/.project| 17 ++ features/org.yocto.sdk.doc/build.properties|5 + features/org.yocto.sdk.doc/feature.properties | 208 + features/org.yocto.sdk.doc/feature.xml | 32 +++ features/org.yocto.sdk.doc/license.html| 237 .../sourceTemplateFeature/feature.properties | 208 + .../sourceTemplateFeature/license.html | 237 7 files changed, 944 insertions(+), 0 deletions(-) create mode 100644 features/org.yocto.sdk.doc/.project create mode 100644 features/org.yocto.sdk.doc/build.properties create mode 100644 features/org.yocto.sdk.doc/feature.properties create mode 100644 features/org.yocto.sdk.doc/feature.xml create mode 100644 features/org.yocto.sdk.doc/license.html create mode 100644 features/org.yocto.sdk.doc/sourceTemplateFeature/feature.properties create mode 100644 features/org.yocto.sdk.doc/sourceTemplateFeature/license.html diff --git a/features/org.yocto.sdk.doc/.project b/features/org.yocto.sdk.doc/.project new file mode 100644 index 000..7418615 --- /dev/null +++ b/features/org.yocto.sdk.doc/.project @@ -0,0 +1,17 @@ +?xml version=1.0 encoding=UTF-8? +projectDescription + nameorg.yocto.sdk.doc/name + comment/comment + projects + /projects + buildSpec + buildCommand + nameorg.eclipse.pde.FeatureBuilder/name + arguments + /arguments + /buildCommand + /buildSpec + natures + natureorg.eclipse.pde.FeatureNature/nature + /natures +/projectDescription diff --git a/features/org.yocto.sdk.doc/build.properties b/features/org.yocto.sdk.doc/build.properties new file mode 100644 index 000..b0439e2 --- /dev/null +++ b/features/org.yocto.sdk.doc/build.properties @@ -0,0 +1,5 @@ +bin.includes = feature.xml,\ + feature.properties,\ + license.html + +generate.feat...@org.yocto.sdk.doc.source=org.yocto.sdk.doc diff --git a/features/org.yocto.sdk.doc/feature.properties b/features/org.yocto.sdk.doc/feature.properties new file mode 100644 index 000..c15adce --- /dev/null +++ b/features/org.yocto.sdk.doc/feature.properties @@ -0,0 +1,208 @@ +featureName=Yocto Documentation Plugin for Eclipse +providerName=yoctoproject.org + +updateSiteName=Yocto Update Site + +description=\ +Eclipse plug-ins containing the documentation for developing embedded \ +applications for Yocto based embedded Linux. + +copyright=\ +Copyright (c) 2010 Intel, Inc. and others. \ +All rights reserved. This program and the accompanying materials \ +are made available under the terms of the Creative Commons Attribution-Share \ +Alike 2.0 UK: England Wales which accompanies this distribution, \ +and is available at \ +http://creativecommons.org/licenses/by-sa/2.0/uk/legalcode + +licenseURL=license.html +license=\ +Creative Commons Attribution-Share Alike 2.0 UK: England Wales\n\ +\n\ +THE WORK (AS DEFINED BELOW) IS PROVIDED UNDER THE TERMS OF THIS \ +CREATIVE COMMONS PUBLIC LICENCE (CCPL OR LICENCE). THE WORK IS \ +PROTECTED BY COPYRIGHT AND/OR OTHER APPLICABLE LAW. ANY USE OF THE \ +WORK OTHER THAN AS AUTHORIZED UNDER THIS LICENCE OR COPYRIGHT LAW IS \ +PROHIBITED. BY EXERCISING ANY RIGHTS TO THE WORK PROVIDED HERE, YOU \ +ACCEPT AND AGREE TO BE BOUND BY THE TERMS OF THIS LICENCE. THE \ +LICENSOR GRANTS YOU THE RIGHTS CONTAINED HERE IN CONSIDERATION OF YOUR \ +ACCEPTANCE OF SUCH TERMS AND CONDITIONS. \ +\n\ +This Creative Commons England and Wales Public Licence enables You \ +(all capitalised terms defined below) to view, edit, modify, translate \ +and distribute Works worldwide, under the terms of this licence, \ +provided that You credit the Original Author. \ +\n\ +'The Licensor' [one or more legally recognised persons or entities \ +offering the Work under the terms and conditions of this Licence] \ +\n \ +and \ +\n \ +'You' \ +\n \ +agree as follows: \ +\n \ +1. Definitions \ +\n \ +Attribution means acknowledging all the parties who have contributed \ +to and have rights in the Work or Collective Work under this Licence. \ +Collective Work means the Work in its entirety in unmodified form \ +along with a number of other separate and independent works, assembled \ +into a collective whole. Derivative Work means any work created by \ +the editing, modification, adaptation or translation of the Work in \ +any media (however a
[yocto] [RFC 6/8] feature/sdk: Added org.yocto.sdk.doc feature.
From: Timo Mueller timo.muel...@bmw-carit.de The feature is added to the yocto main feature so it will be part of the build. Also when installing the documentation feature will also be installed. To be able to install the documentation feature is has to be available via an eclipse update site. It is currently not part of the official yocto update site. Therefor the feature has to be installed manually until it is part of the yocto update site. --- features/org.yocto.sdk/feature.xml |5 + 1 files changed, 5 insertions(+), 0 deletions(-) diff --git a/features/org.yocto.sdk/feature.xml b/features/org.yocto.sdk/feature.xml index 0fce8db..7ee6575 100644 --- a/features/org.yocto.sdk/feature.xml +++ b/features/org.yocto.sdk/feature.xml @@ -8,6 +8,7 @@ Contributors: Intel - initial API and implementation +BMW Car IT GmbH - added yocto documentation feature -- feature id=org.yocto.sdk @@ -34,6 +35,10 @@ includes id=org.yocto.sdk.source/ + includes + id=org.yocto.sdk.doc + version=0.0.0/ + requires import plugin=org.eclipse.core.runtime/ import plugin=org.eclipse.osgi/ -- 1.7.7.6 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [RFC 7/8] features/sdk.site: Added eclipse help feature to update site
From: Timo Mueller timo.muel...@bmw-carit.de Using the update site the user is able to install the documentation feature. As it is required by yocto's main feature it will be automatically installed during the main features installation. --- features/org.yocto.sdk.site/category.xml |6 ++ features/org.yocto.sdk.site/site.xml |3 +++ 2 files changed, 9 insertions(+), 0 deletions(-) diff --git a/features/org.yocto.sdk.site/category.xml b/features/org.yocto.sdk.site/category.xml index 9fb50b2..e21f3fb 100644 --- a/features/org.yocto.sdk.site/category.xml +++ b/features/org.yocto.sdk.site/category.xml @@ -6,5 +6,11 @@ feature url=features/org.yocto.sdk.source_@featureVerion@.jar id=org.yocto.sdk.source version=@featureVerion@ category name=Yocto SDK/ /feature + feature url=features/org.yocto.sdk.doc_@featureVerion@.jar id=org.yocto.sdk.doc version=@featureVerion@ + category name=Yocto SDK/ + /feature + feature url=features/org.yocto.sdk.doc.source_@featureVerion@.jar id=org.yocto.sdk.doc.source version=@featureVerion@ + category name=Yocto SDK/ + /feature category-def name=Yocto SDK label=Development tools amp; SDKs for Yocto Linux/ /site diff --git a/features/org.yocto.sdk.site/site.xml b/features/org.yocto.sdk.site/site.xml index 59ebbd5..e33e91a 100644 --- a/features/org.yocto.sdk.site/site.xml +++ b/features/org.yocto.sdk.site/site.xml @@ -6,5 +6,8 @@ feature url=features/org.yocto.sdk_@genVerion@.jar id=org.yocto.sdk version=@genVerion@ category name=Yocto SDK/ /feature + feature url=features/org.yocto.sdk.doc_@genVerion@.jar id=org.yocto.sdk.doc version=@genVerion@ + category name=Yocto SDK/ + /feature category-def name=Yocto SDK label=Development tools amp; SDKs for Yocto Linux/ /site -- 1.7.7.6 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [Solved] Re: Error: PATH contains '.' or '', which will break the build, please remove this.
On Wed, Jul 18, 2012 at 6:37 AM, Burton, Ross ross.bur...@intel.com wrote: On 18 July 2012 13:13, Burton, Ross ross.bur...@intel.com wrote: I'm working on a patch to display the parsed PATH so you'll see the trailing empty element in that case. How's this? It's still slightly hard to spot there. I wonder if something like this would be easier for the user? ERROR: Invalid PATH entry at character N: /usr/bin:/bin: ^ In other words, formatted like a syntax error. -- Christopher Larson ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [Solved] Re: Error: PATH contains '.' or '', which will break the build, please remove this.
On 18 July 2012 14:46, Chris Larson clar...@kergoth.com wrote: On Wed, Jul 18, 2012 at 6:37 AM, Burton, Ross ross.bur...@intel.com wrote: On 18 July 2012 13:13, Burton, Ross ross.bur...@intel.com wrote: I'm working on a patch to display the parsed PATH so you'll see the trailing empty element in that case. How's this? It's still slightly hard to spot there. I wonder if something like this would be easier for the user? ERROR: Invalid PATH entry at character N: /usr/bin:/bin: That would be easier for the user, but harder to implement. :) Ross ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 0/1] meta: update crownbay.scc for newer emgd driver
On Mon, 2012-07-16 at 22:57 -0700, nitin.a.kam...@intel.com wrote: From: Nitin A Kamble nitin.a.kam...@intel.com This commit changes emgd kernel driver for crownbay bsp to the emgd-1.14. Nitin, Doesn't switching this over in the kenrnel require emgd-1.14 userspace recipe updates to work? Did I miss those? Tom Thanks, Nitin The following changes since commit c2b5ee363bf2612932301488f3ac0644ff70fc7c: meta: disable CONFIG_MTD_NAND_VERIFY_WRITE (2012-07-14 00:21:49 -0400) are available in the git repository at: git://git.yoctoproject.org/linux-yocto-2.6.37-contrib nitin/meta http://git.yoctoproject.org/cgit.cgi/linux-yocto-2.6.37-contrib/log/?h=nitin/meta Nitin A Kamble (1): meta: crownbay.scc change emgd branch name .../bsp/crownbay/crownbay-standard.scc |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Problem building Yocto Hello World demo on imx53QSB
Hi Jessica, downgrading from Ubuntu 11.04 (32 bit) to Ubuntu 10.04 (32 bit) and following the ADT manual procedure HelloWorld demo works. I noticed that ADT creates an armv5 tool chain instead building the toolchain using Freescale layer (because I need to deploy the application on a iMX53QSB) it creates an armv7 tool chain (that is the right processor architecture). Can this create problems? Thanks Giovanni -- Dott. Ing. Giovanni Foiani Cell:+39-349-3577515 Phone:+39-0532-97-4106 mail:giovanni.foi...@unife.it CenTec - Corso Guercino, 47 - 44042 Cento (FE) On Tue, Jul 17, 2012 at 5:12 PM, Zhang, Jessica jessica.zh...@intel.comwrote: Hi Giovanni, ** ** Can you following the ADT manual and use the built 1.2.1 toolchain tar ball? The meta-ide-support is supposed to be used under build tree instead of copied over to /opt/poky. ** ** Cheers, Jessica ** ** *From:* yocto-boun...@yoctoproject.org [mailto: yocto-boun...@yoctoproject.org] *On Behalf Of *Giovanni Foiani *Sent:* Tuesday, July 17, 2012 2:29 AM *To:* yocto@yoctoproject.org *Subject:* [yocto] Problem building Yocto Hello World demo on imx53QSB ** ** Hi, ** ** I need to deploy a C application that I have made on a Freescale iMX53 QSB. First I wanted to test the cross-compilation environment building the Hello World demo but I got some issues. I made the following steps: - download yocto denzil - source oe-init-build-env - edit local.conf and bblayers.conf files - run 'bitbake meta-ide-support' - copied the resultant sdk in /opt/poky - installed Yocto Eclipse plugin - Configured the plugin as following - toolchain root location: /opt/poky/1.2.1 - sysroot location: /opt/poky/1.2.1/sysroots/armv7a-vfp-neon-poky-linux-gnueabi When I build the project I get the following error: ** ** *Invoking autogen.sh in build directory: /home/gfoiani/workspace/idea-c-application* ** ** *Command-line environment variables:* ***CFLAGS= -g -O0 -march=armv7-a -fno-tree-vectorize -mthumb-interwork -mfloat-abi=softfp -mfpu=neon -mtune=cortex-a8 --sysroot=/opt/poky/1.2.1/sysroots/armv7a-vfp-neon-poky-linux-gnueabi CXXFLAGS= -g -O0 -march=armv7-a -fno-tree-vectorize -mthumb-interwork -mfloat-abi=softfp -mfpu=neon -mtune=cortex-a8 --sysroot=/opt/poky/1.2.1/sysroots/armv7a-vfp-neon-poky-linux-gnueabi LDFLAGS= --sysroot=/opt/poky/1.2.1/sysroots/armv7a-vfp-neon-poky-linux-gnueabi CPPFLAGS= -march=armv7-a -fno-tree-vectorize -mthumb-interwork -mfloat-abi=softfp -mfpu=neon -mtune=cortex-a8 --sysroot=/opt/poky/1.2.1/sysroots/armv7a-vfp-neon-poky-linux-gnueabi * ** ** *sh /home/gfoiani/workspace/idea-c-application/autogen.sh --with-libtool-sysroot=/opt/poky/1.2.1/sysroots/armv7a-vfp-neon-poky-linux-gnueabi --target=arm-poky-linux-gnueabi --host=arm-poky-linux-gnueabi --build=i686-linux --with-libtool-sysroot=/opt/poky/1.2.1/sysroots/armv7a-vfp-neon-poky-linux-gnueabi * *configure.ac:24: error: AC_SUBST: `idea-c-application_CFLAGS' is not a valid shell variable name* *configure.ac:24: the top level* *autom4te: m4 failed with exit status: 1* *aclocal: autom4te failed with exit status: 1* *configure.ac:24: error: AC_SUBST: `idea-c-application_CFLAGS' is not a valid shell variable name* *configure.ac:24: the top level* *autom4te: m4 failed with exit status: 1* *configure.ac:24: error: AC_SUBST: `idea-c-application_CFLAGS' is not a valid shell variable name* *configure.ac:24: the top level* *autom4te: m4 failed with exit status: 1* *autoheader: '/opt/poky/1.2.1/sysroots/i686-pokysdk-linux/usr/bin/autom4te' failed with exit status: 1* *configure.ac:24: error: AC_SUBST: `idea-c-application_CFLAGS' is not a valid shell variable name* *configure.ac:24: the top level* *autom4te: m4 failed with exit status: 1* *automake: autoconf failed with exit status: 1* */home/gfoiani/workspace/idea-c-application/autogen.sh: line 9: ./configure: No such file or directory* ** ** *Configuration failed with error* ** ** What Am I doing wrong? ** ** Thanks ** ** Giovanni -- Dott. Ing. Giovanni Foiani Cell:+39-349-3577515 Phone:+39-0532-97-4106 mail:giovanni.foi...@unife.it CenTec - Corso Guercino, 47 - 44042 Cento (FE) ** ** ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [Solved] Re: Error: PATH contains '.' or '', which will break the build, please remove this.
On Wed, Jul 18, 2012 at 6:57 AM, Burton, Ross ross.bur...@intel.com wrote: On 18 July 2012 14:46, Chris Larson clar...@kergoth.com wrote: On Wed, Jul 18, 2012 at 6:37 AM, Burton, Ross ross.bur...@intel.com wrote: On 18 July 2012 13:13, Burton, Ross ross.bur...@intel.com wrote: I'm working on a patch to display the parsed PATH so you'll see the trailing empty element in that case. How's this? It's still slightly hard to spot there. I wonder if something like this would be easier for the user? ERROR: Invalid PATH entry at character N: /usr/bin:/bin: That would be easier for the user, but harder to implement. :) It'd be something like https://gist.github.com/3136618, no doubt. But the problem is the assumption of the length of the prefix, that is, assumption of the final formatting to the user, which isn't ideal. What we should do, I think, is teach the UI log formatter to indent subsequent lines based on its own prefix, so that foo\nbar would show up like this: ERROR: foo bar Rather than: ERROR: foo bar -- Christopher Larson ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [RFC 0/8] Integrate yocto documentation into eclipse
Hi, This seems like a very cool idea. What about when things change structurally for the Yocto Docs? For example, right now I am restructuring much of the Eclipse information that is in the ADT manual to move it to the development manual as part of an application development flow. It looks like your patch here includes the ADT manual and the Quick Start. The changes I am working on will eventually require the YP development manual as well. Scott -Original Message- From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On Behalf Of m...@timomueller.eu Sent: Wednesday, July 18, 2012 6:03 AM To: yocto@yoctoproject.org Cc: Timo Mueller Subject: [yocto] [RFC 0/8] Integrate yocto documentation into eclipse From: Timo Mueller timo.muel...@bmw-carit.de Hi, the documentation of the yocto project can currently be viewed online or as a separate pdf. When using the eclipse ide to develop software on base of a yocto sysroot and toolchain it would be convenient to access the relevant parts of the documentation from within the ide. In order to achieve this, I've generated eclipse help from yocto's documentation (adt-manual, yocto-project-qs). I have intergrated this documentation in the ide and it can now be accessed through the eclipse help center (Help - Help Contents). Please let me know what you think about it? Yocto's documentation is licensed under the Creative Commons Attribution-Share Alike 2.0 UK: England Wales (CCA-SA), which is incompatible to the Eclipse Public License 1.0. Thus I've created a standalone feature to simply redistribute the documentation avoiding licensing issues. Do you agree on the way this is structured? Cheers, Timo Timo Mueller (8): plugins/sdk.doc.user: Added plugin for the yocto project documentation plugins/sdk.doc.user: Added empty table of contents feature/sdk.doc: Added feature containing yocto documentation plugins feature/sdk.doc: Added org.yocto.sdk.doc.user plugin plugins/sdk.doc.user: Added yocto quick start guide feature/sdk: Added org.yocto.sdk.doc feature. features/sdk.site: Added eclipse help feature to update site plugins/sdk.doc.user: Added yocto adt manual features/org.yocto.sdk.doc/.project| 17 + features/org.yocto.sdk.doc/build.properties|5 + features/org.yocto.sdk.doc/feature.properties | 208 ++ features/org.yocto.sdk.doc/feature.xml | 40 ++ features/org.yocto.sdk.doc/license.html| 237 +++ .../sourceTemplateFeature/feature.properties | 208 ++ .../sourceTemplateFeature/license.html | 237 +++ features/org.yocto.sdk.site/category.xml |6 + features/org.yocto.sdk.site/site.xml |3 + features/org.yocto.sdk/feature.xml |5 + plugins/org.yocto.sdk.doc.user/.classpath |6 + plugins/org.yocto.sdk.doc.user/.project| 28 + .../.settings/org.eclipse.jdt.core.prefs |8 + .../org.yocto.sdk.doc.user/META-INF/MANIFEST.MF|8 + .../OSGI-INF/l10n/bundle.properties|3 + plugins/org.yocto.sdk.doc.user/about.html | 82 +++ plugins/org.yocto.sdk.doc.user/adt-manual-toc.xml | 61 ++ plugins/org.yocto.sdk.doc.user/build.properties| 14 + .../html/adt-manual/ch01.html | 90 +++ .../html/adt-manual/ch01s02.html | 166 + .../html/adt-manual/ch02.html | 450 + .../html/adt-manual/ch02s02.html | 56 ++ .../html/adt-manual/ch02s03.html | 182 ++ .../html/adt-manual/ch03.html | 97 +++ .../html/adt-manual/ch03s02.html | 78 +++ .../html/adt-manual/ch04.html | 675 .../html/adt-manual/ch04s02.html | 94 +++ .../html/adt-manual/ch04s03.html | 77 +++ .../html/adt-manual/ch04s04.html | 37 ++ .../html/adt-manual/ch04s05.html | 65 ++ .../html/adt-manual/ch04s06.html | 100 +++ .../html/adt-manual/ch04s07.html | 161 + .../html/adt-manual/ch04s08.html | 184 ++ .../html/adt-manual/ch05.html | 112 .../html/adt-manual/ch05s02.html | 41 ++ .../html/adt-manual/index.html | 260 plugins/org.yocto.sdk.doc.user/html/book.css |1 + .../yocto-project-qs/figures/building-an-image.png | Bin 0 - 14891 bytes .../figures/using-a-pre-built-image.png| Bin 0 - 12733 bytes .../yocto-project-qs/figures/yocto-environment.png | Bin 0 - 73095 bytes .../figures/yocto-project-transp.png | Bin 0 - 8626 bytes .../html/yocto-project-qs/index.html | 542 plugins/org.yocto.sdk.doc.user/plugin.xml | 19 +
Re: [yocto] meta-baryon flexibility
On 18/07/12 04:40, James Abernathy wrote:
On Tue, Jul 17, 2012 at 6:19 PM, Joshua Lock j...@linux.intel.com
mailto:j...@linux.intel.com wrote:
On Tue, 2012-07-17 at 15:24 -0400, Jim Abernathy wrote:
In an effort to explore how independent a layer could be to the
underlying hardware, I took the meta-baryon NAS layer and got it
built
from master using the n450 BSP. With that working I decided to
replace
the n450 with sugarbay. While the n450 can support X11 and sato,
it was
not generated by design in the baryon build.
However, when I changed to sugarbay, the build stops because X11 is
needed. To get around this I had to comment out some things in the
conf/machine/sugarbay.conf file in the BSP.
#XSERVER ?= ${XSERVER_IA32_BASE} \
# ${XSERVER_IA32_EXT} \
# ${XSERVER_IA32_I965} \
#
#VA_FEATURES ?= gst-va-intel va-intel
#MACHINE_EXTRA_RRECOMMENDS += ${VA_FEATURES}
Why didn't I have to do this in the n450??
The key piece is the MACHINE_EXTRA_RRECOMMENDS, which is telling Poky to
recommend the gst-va-intel and va-intel recipes when building this
machine.
RRECOMMENDS are automatically installed as a dependency (in this case,
of task-machine-base, see task-base.bbclass) but can be removed without
causing the package which pulled it in to be removed (see the Poky
reference manual glossary on *_RRECOMMENDS).
http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html
I'd suggest the RRECOMMENDS actually be added at a more granular level
than the machine. Perhaps you could file a bug against the BSP?
So if I understand this, it would be better for one of the image.bb
http://image.bb files that focused on media to include this particular
RRECOMMENDS statement. That way others not interested in media and
graphic could still use the BSP unchanged.
Arguably, yes. But (devil's advocate) what about image recipes which
aren't part of the core? i.e. if you've been using a different board to
develop a custom image and then switch to using the sugarbay wouldn't
you want the accelerated video to just work?
I'd suggest a possible solution would be to define an opt-in
IMAGE_FEATURES[1][2] for multimedia which the sugarbay BSP can add these
recipes to.
Joshua
1.
http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html#var-IMAGE_FEATURES
2.
http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html#ref-features-image
--
Joshua Lock
Yocto Project
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 0/1] meta: update crownbay.scc for newer emgd driver
On 12-07-18 10:13 AM, Tom Zanussi wrote: On Mon, 2012-07-16 at 22:57 -0700, nitin.a.kam...@intel.com wrote: From: Nitin A Kamblenitin.a.kam...@intel.com This commit changes emgd kernel driver for crownbay bsp to the emgd-1.14. Nitin, Doesn't switching this over in the kenrnel require emgd-1.14 userspace recipe updates to work? Did I miss those? Good question. I'm holding on merging and pushing this until we are sure that the whole stack will work .. Cheers, Bruce Tom Thanks, Nitin The following changes since commit c2b5ee363bf2612932301488f3ac0644ff70fc7c: meta: disable CONFIG_MTD_NAND_VERIFY_WRITE (2012-07-14 00:21:49 -0400) are available in the git repository at: git://git.yoctoproject.org/linux-yocto-2.6.37-contrib nitin/meta http://git.yoctoproject.org/cgit.cgi/linux-yocto-2.6.37-contrib/log/?h=nitin/meta Nitin A Kamble (1): meta: crownbay.scc change emgd branch name .../bsp/crownbay/crownbay-standard.scc |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Problem building Yocto Hello World demo on imx53QSB
Please see my comments below... From: Giovanni Foiani [mailto:fno...@unife.it] Sent: Wednesday, July 18, 2012 7:25 AM To: Zhang, Jessica Cc: yocto@yoctoproject.org Subject: Re: [yocto] Problem building Yocto Hello World demo on imx53QSB Hi Jessica, downgrading from Ubuntu 11.04 (32 bit) to Ubuntu 10.04 (32 bit) and following the ADT manual procedure HelloWorld demo works. [JZ] This I'm assuming you strictly follow the ADT manual and use the Yocto project built out toolchain, right? Why downgrade from Ubuntu 11.04 to 10.04? I don't think you need to do that unless 10.04 is what you want. I noticed that ADT creates an armv5 tool chain instead building the toolchain using Freescale layer (because I need to deploy the application on a iMX53QSB) it creates an armv7 tool chain (that is the right processor architecture). Can this create problems? [JZ] In that case, you need to build out an armv7 toolchain. The key is to add the Freescale layer and set target MACHINE appropriately. And use that toolchain for your cross development. It should work. Thanks Giovanni -- Dott. Ing. Giovanni Foiani Cell:+39-349-3577515 Phone:+39-0532-97-4106 mail:giovanni.foi...@unife.itmailto:giovanni.foi...@unife.it CenTec - Corso Guercino, 47 - 44042 Cento (FE) On Tue, Jul 17, 2012 at 5:12 PM, Zhang, Jessica jessica.zh...@intel.commailto:jessica.zh...@intel.com wrote: Hi Giovanni, Can you following the ADT manual and use the built 1.2.1 toolchain tar ball? The meta-ide-support is supposed to be used under build tree instead of copied over to /opt/poky. Cheers, Jessica From: yocto-boun...@yoctoproject.orgmailto:yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.orgmailto:yocto-boun...@yoctoproject.org] On Behalf Of Giovanni Foiani Sent: Tuesday, July 17, 2012 2:29 AM To: yocto@yoctoproject.orgmailto:yocto@yoctoproject.org Subject: [yocto] Problem building Yocto Hello World demo on imx53QSB Hi, I need to deploy a C application that I have made on a Freescale iMX53 QSB. First I wanted to test the cross-compilation environment building the Hello World demo but I got some issues. I made the following steps: * download yocto denzil * source oe-init-build-env * edit local.conf and bblayers.conf files * run 'bitbake meta-ide-support' * copied the resultant sdk in /opt/poky * installed Yocto Eclipse plugin * Configured the plugin as following *toolchain root location: /opt/poky/1.2.1 *sysroot location: /opt/poky/1.2.1/sysroots/armv7a-vfp-neon-poky-linux-gnueabi When I build the project I get the following error: Invoking autogen.sh in build directory: /home/gfoiani/workspace/idea-c-application Command-line environment variables: CFLAGS= -g -O0 -march=armv7-a -fno-tree-vectorize -mthumb-interwork -mfloat-abi=softfp -mfpu=neon -mtune=cortex-a8 --sysroot=/opt/poky/1.2.1/sysroots/armv7a-vfp-neon-poky-linux-gnueabi CXXFLAGS= -g -O0 -march=armv7-a -fno-tree-vectorize -mthumb-interwork -mfloat-abi=softfp -mfpu=neon -mtune=cortex-a8 --sysroot=/opt/poky/1.2.1/sysroots/armv7a-vfp-neon-poky-linux-gnueabi LDFLAGS= --sysroot=/opt/poky/1.2.1/sysroots/armv7a-vfp-neon-poky-linux-gnueabi CPPFLAGS= -march=armv7-a -fno-tree-vectorize -mthumb-interwork -mfloat-abi=softfp -mfpu=neon -mtune=cortex-a8 --sysroot=/opt/poky/1.2.1/sysroots/armv7a-vfp-neon-poky-linux-gnueabi sh /home/gfoiani/workspace/idea-c-application/autogen.sh --with-libtool-sysroot=/opt/poky/1.2.1/sysroots/armv7a-vfp-neon-poky-linux-gnueabi --target=arm-poky-linux-gnueabi --host=arm-poky-linux-gnueabi --build=i686-linux --with-libtool-sysroot=/opt/poky/1.2.1/sysroots/armv7a-vfp-neon-poky-linux-gnueabi configure.ac:24http://configure.ac:24: error: AC_SUBST: `idea-c-application_CFLAGS' is not a valid shell variable name configure.ac:24http://configure.ac:24: the top level autom4te: m4 failed with exit status: 1 aclocal: autom4te failed with exit status: 1 configure.ac:24http://configure.ac:24: error: AC_SUBST: `idea-c-application_CFLAGS' is not a valid shell variable name configure.ac:24http://configure.ac:24: the top level autom4te: m4 failed with exit status: 1 configure.ac:24http://configure.ac:24: error: AC_SUBST: `idea-c-application_CFLAGS' is not a valid shell variable name configure.ac:24http://configure.ac:24: the top level autom4te: m4 failed with exit status: 1 autoheader: '/opt/poky/1.2.1/sysroots/i686-pokysdk-linux/usr/bin/autom4te' failed with exit status: 1 configure.ac:24http://configure.ac:24: error: AC_SUBST: `idea-c-application_CFLAGS' is not a valid shell variable name configure.ac:24http://configure.ac:24: the top level autom4te: m4 failed with exit status: 1 automake: autoconf failed with exit status: 1 /home/gfoiani/workspace/idea-c-application/autogen.sh: line 9: ./configure:
Re: [yocto] [RFC 0/8] Integrate yocto documentation into eclipse
Hi Timo, Can you send me the link to the branch that I can take a look at this new plug-in? Thanks, Jessica -Original Message- From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On Behalf Of m...@timomueller.eu Sent: Wednesday, July 18, 2012 6:03 AM To: yocto@yoctoproject.org Cc: Timo Mueller Subject: [yocto] [RFC 0/8] Integrate yocto documentation into eclipse From: Timo Mueller timo.muel...@bmw-carit.de Hi, the documentation of the yocto project can currently be viewed online or as a separate pdf. When using the eclipse ide to develop software on base of a yocto sysroot and toolchain it would be convenient to access the relevant parts of the documentation from within the ide. In order to achieve this, I've generated eclipse help from yocto's documentation (adt-manual, yocto-project-qs). I have intergrated this documentation in the ide and it can now be accessed through the eclipse help center (Help - Help Contents). Please let me know what you think about it? Yocto's documentation is licensed under the Creative Commons Attribution-Share Alike 2.0 UK: England Wales (CCA-SA), which is incompatible to the Eclipse Public License 1.0. Thus I've created a standalone feature to simply redistribute the documentation avoiding licensing issues. Do you agree on the way this is structured? Cheers, Timo Timo Mueller (8): plugins/sdk.doc.user: Added plugin for the yocto project documentation plugins/sdk.doc.user: Added empty table of contents feature/sdk.doc: Added feature containing yocto documentation plugins feature/sdk.doc: Added org.yocto.sdk.doc.user plugin plugins/sdk.doc.user: Added yocto quick start guide feature/sdk: Added org.yocto.sdk.doc feature. features/sdk.site: Added eclipse help feature to update site plugins/sdk.doc.user: Added yocto adt manual features/org.yocto.sdk.doc/.project| 17 + features/org.yocto.sdk.doc/build.properties|5 + features/org.yocto.sdk.doc/feature.properties | 208 ++ features/org.yocto.sdk.doc/feature.xml | 40 ++ features/org.yocto.sdk.doc/license.html| 237 +++ .../sourceTemplateFeature/feature.properties | 208 ++ .../sourceTemplateFeature/license.html | 237 +++ features/org.yocto.sdk.site/category.xml |6 + features/org.yocto.sdk.site/site.xml |3 + features/org.yocto.sdk/feature.xml |5 + plugins/org.yocto.sdk.doc.user/.classpath |6 + plugins/org.yocto.sdk.doc.user/.project| 28 + .../.settings/org.eclipse.jdt.core.prefs |8 + .../org.yocto.sdk.doc.user/META-INF/MANIFEST.MF|8 + .../OSGI-INF/l10n/bundle.properties|3 + plugins/org.yocto.sdk.doc.user/about.html | 82 +++ plugins/org.yocto.sdk.doc.user/adt-manual-toc.xml | 61 ++ plugins/org.yocto.sdk.doc.user/build.properties| 14 + .../html/adt-manual/ch01.html | 90 +++ .../html/adt-manual/ch01s02.html | 166 + .../html/adt-manual/ch02.html | 450 + .../html/adt-manual/ch02s02.html | 56 ++ .../html/adt-manual/ch02s03.html | 182 ++ .../html/adt-manual/ch03.html | 97 +++ .../html/adt-manual/ch03s02.html | 78 +++ .../html/adt-manual/ch04.html | 675 .../html/adt-manual/ch04s02.html | 94 +++ .../html/adt-manual/ch04s03.html | 77 +++ .../html/adt-manual/ch04s04.html | 37 ++ .../html/adt-manual/ch04s05.html | 65 ++ .../html/adt-manual/ch04s06.html | 100 +++ .../html/adt-manual/ch04s07.html | 161 + .../html/adt-manual/ch04s08.html | 184 ++ .../html/adt-manual/ch05.html | 112 .../html/adt-manual/ch05s02.html | 41 ++ .../html/adt-manual/index.html | 260 plugins/org.yocto.sdk.doc.user/html/book.css |1 + .../yocto-project-qs/figures/building-an-image.png | Bin 0 - 14891 bytes .../figures/using-a-pre-built-image.png| Bin 0 - 12733 bytes .../yocto-project-qs/figures/yocto-environment.png | Bin 0 - 73095 bytes .../figures/yocto-project-transp.png | Bin 0 - 8626 bytes .../html/yocto-project-qs/index.html | 542 plugins/org.yocto.sdk.doc.user/plugin.xml | 19 + plugins/org.yocto.sdk.doc.user/toc.xml |9 + .../yocto-project-qs-toc.xml | 32 + 45 files changed, 4704 insertions(+), 0 deletions(-) create mode 100644 features/org.yocto.sdk.doc/.project create mode 100644 features/org.yocto.sdk.doc/build.properties create mode 100644
Re: [yocto] 1.1.2 Full Pass consolidated Test Report
Ok, so I've found downgrading coreutils package to the last working
version (from CentOS 5.6) makes this issue go away:
$ wget
http://vault.centos.org/5.6/os/x86_64/CentOS/coreutils-5.97-23.el5_4.2.x86_64.rpm
$ sudo rpm -Uvh --oldpackage coreutils-5.97-23.el5_4.2.x86_64.rpm
I've looked at the changelog of coreutils package for centos and
nothing stands out as causing the issue. The most likely candiate is:
https://bugzilla.redhat.com/show_bug.cgi?id=523923
$ rpm -q --changelog coreutils
* Wed Mar 14 2012 Ondrej Vasik ova...@redhat.com 5.97-34.1
- fix backup of the individual files (broken by backupdir
patch - #803356)
* Wed May 11 2011 Ondrej Vasik ova...@redhat.com 5.97-34
- su: fix shell suspend in tcsh (#681598)
* Fri Apr 29 2011 Ondrej Vasik ova...@redhat.com 5.97-33
- workaround wrong workarounds for the runcon argument
reordering (related #628953)
* Tue Apr 19 2011 Ondrej Vasik ova...@redhat.com 5.97-32
- fix descriptor leak in fts tight cycle fix (#537463)
* Thu Apr 14 2011 Ondrej Vasik ova...@redhat.com 5.97-31
- improve error chmod handling in ro xattrs fix (#525199)
* Thu Mar 31 2011 Ondrej Vasik ova...@redhat.com 5.97-30
- improve the fix for preserving xattrs in read only mode
(#525199)
* Fri Mar 25 2011 Ondrej Vasik ova...@redhat.com 5.97-28
- fix incorrect output of ls -1U with more than one
argument(#515499)
- runuser documentation improved (#524805)
- cp/mv: preserving xattrs should work on read only
files too (#525199)
- fix failure of rmdir --ignore-fail-on-non-empty on vxfs
filesystem (#664895)
- mv: fix confusing 'subdirectory of itself' error message
(#658839)
- don't reorder runcon arguments (#628953)
- clarify mkdir --mode behaviour in info documentation
(#610559)
- improve escaping in colorls scriptlets(#586957)
- add info documentation for chcon and runcon(#660186)
- document that groups are not reflecting changes within
existing login session (#584802)
- pwd: add support for -P (physical) and -L (logical) (#582774)
- cp/mv: do not inform about ACL preserving failure, when
preserving not explicitely requested (#513153)
- du using ghosted automounted directory no longer
results in 'No such file or directory' (#537463)
- fix segfault in sort if LC_TIME differs from the rest
of locales(#684249)
- speed up deleting many files (#523923)
- allow mv backups for directories (#627285)
* Wed Jan 26 2011 Ondrej Vasik ova...@redhat.com 5.97-27
- fix exit status of terminated child processes in su with
pam(#559098)
* Mon Jan 10 2011 Ondrej Vasik ova...@redhat.com 5.97-26
- add support for iflag=fullblock in dd (#668247)
- fix the build with gettext-0.17
* Mon Feb 22 2010 Ondrej Vasik ova...@redhat.com 5.97-25
- readlink cannot handle recursive symlinks(#510809)
* Mon Oct 12 2009 Ondrej Vasik ova...@redhat.com 5.97-24
- fixed regression where df -l device as regular user
cause Permission denied (#520630, introduced by fix for
rhbz #497830)
On Tue, Jul 17, 2012 at 12:35 PM, Matthew McClintock m...@freescale.com wrote:
On Tue, Jul 17, 2012 at 9:57 AM, Matthew McClintock m...@freescale.com
wrote:
On Tue, Jul 17, 2012 at 12:51 AM, Khem Raj raj.k...@gmail.com wrote:
On Mon, Jul 16, 2012 at 10:31 PM, McClintock Matthew-B29882
b29...@freescale.com wrote:
}
- rm -rf ${SSTATE_BUILDDIR}
+ strace rm -rf ${SSTATE_BUILDDIR}
strace is probably eating the return value
And you would be right
I want to point out running the
./tmp/work/ppc603e-poky-linux/eglibc-locale-2.13-r16/temp/run.sstate_create_package.17463
generated script directly does not fail (without the strace
modification)
Also, the follow does work:
diff --git a/meta/classes/sstate.bbclass b/meta/classes/sstate.bbclass
index d2a45c3..92a1e4d 100644
--- a/meta/classes/sstate.bbclass
+++ b/meta/classes/sstate.bbclass
@@ -463,7 +463,14 @@ sstate_create_package () {
mv $TFILE ${SSTATE_PKG}
cd ${WORKDIR}
- rm -rf ${SSTATE_BUILDDIR}
+ for i in `find ${SSTATE_BUILDDIR} -type f`; do
+ bbnote deleting $i
+ rm -rf $i
+ done
+ for i in `find ${SSTATE_BUILDDIR} -type d -depth`; do
+ bbnote rmdir $i
+ rmdir $i
+ done
}
Still debugging
-M
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [ANNOUNCEMENT] Yocto 1.2.1 Released
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
We are pleased to announce the point release of the Yocto Project Denzil
release.
The full test report for this release is available here:
https://wiki.yoctoproject.org/wiki/Yocto_1.2.1_Test_Report
You can download this release from either the main Yocto Project download
site:
http://downloads.yoctoproject.org/releases/yocto/yocto-1.2.1/poky-denzil-7.0.1.tar.bz2
or the kernel.org mirror:
http://mirrors.kernel.org/yocto/yocto/yocto-1.2.1/poky-denzil-7.0.1.tar.bz2
Git tags gpg key information is available at:
http://pgp.mit.edu:11371/pks/lookup?op=vindexsearch=0x4C8AF84FCC12440F
Thank you everyone, especially the 1.2.1 maintainer, Scott Garman, for all
their hard work!
Elizabeth Flanagan
Yocto Build and Release
elizabeth.flana...@intel.com
-
denzil-7.0.1 Errata
-
Release Name: eclipse-poky-denzil-7.0.1
Branch: denzil
Tag: denzil-7.0.1
Hash: 1d05505e0653aa70f7e38239951b4e19ce0438e1
md5: e9802851b85bcbe2783aef50eca42067 eclipse-poky-denzil-7.0.1.tar.bz2
Weight: 1.0241x10^3 yoctograms
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-1.2.1/eclipse-poky-denzil-7.0.1.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-1.2.1/eclipse-poky-denzil-7.0.1.tar.bz2
Release Name: meta-qt3-denzil-7.0.1
Branch: denzil
Tag: denzil-7.0.1
Hash: f8475d5c5935695d4d1dfff1d7be30f49e162094
md5: e50851b264d2fcac9276ba0fef2f1de8 meta-qt3-denzil-7.0.1.tar.bz2
Weight: 24.4988 yoctograms
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-1.2.1/meta-qt3-denzil-7.0.1.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-1.2.1/meta-qt3-denzil-7.0.1.tar.bz2
Release Name: poky-denzil-7.0.1
Branch: denzil
Tag: denzil-7.0.1
Hash: 73cdebf60df225ee10f2eb215935be3b61e1b831
md5: ef0c859fac1a32b2271d395ed9046fe3 poky-denzil-7.0.1.tar.bz2
Weight: 1.9323.4843x10^4 yoctograms
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-1.2.1/poky-denzil-7.0.1.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-1.2.1/poky-denzil-7.0.1.tar.bz2
-
Features
-
This release consists of 35 bugfixes, including:
BUG# SUMMARY
* 1465 bitbake cannot fetch local files from SRC_URI when -b is used
* 1858 Rootfs creation broken when using package_deb as primary
PACKAGE_CLASSES with non
Debian-OS build system
* 1892 Beagleboard doesn't boot
* 1906 [QEMU]loses focus in qemux86-64 terminal When I press key
[CTRL+L]
* 1912 [Beagleboard C4]Segmentation fault when reboot the system
with 3.0 kernel
* 1937 oe-core build of python 2.7.2 is broken
* 2142 bitbake not be stoped when force exit hob in early parising
recipes after selected
a new arch
* 2173 [Hob2] Hob needs documentation for the release.
* 2219 [yocto-kernel] fail to find bblayers if TOPDIR is not build
* 2297 fotowall parallel make race
* 2298 ncurses failure non-gplv3 build (race issue)
* 2311 SRC checksums are not being checked
* 2329 Forwarding only sometimes works from qemu connman-based images
* 2330 Yocto BSP Tools: add doc and error message for meta-intel BSPs
* 2334 [Hob2] BB_NUMBER_THREADS not getting set in Hob?
* 2335 [Hob2] The working animated gif appears to have mis-ordered
images
* 2336 Proxy sanity check message is getting burried
* 2340 [Hob2] Top screen (i) doesn't work on Hob in the Build Appliance
* 2341 [Hob2] weird 18 second delay when parsing recipes
* 2352 Security vulnerability in libpng 1.2.46
* 2355 [multilib] lib64 core-sato-sdk build against qemux86 fails at
qt4-x11-free
* 2356 [multilib] fonts corrupted with ipk build for 32bit connman
against qemux86-64
* 2360 PACKAGE_ARCHS cause wrong packages installed into image
* 2362 pseudo-native failed to compile on opensuse12.1 64bit
* 2363 duplicated bash causes do_rootfs failed on Fedora 17
* 2366 meta-yocto/recipes-core/netbase/netbase_4.45.bbappend misses
${PV}
* 2368 Security vulnerability in openssl 1.0.0h
* 2371 [Hob]Handle out of memory exception in HOB
* 2372 [eclipse]Can't import or create Bitbake Commander Project if
sanity network check fail
* 2374 [eglibc] mtrace should be packaged on it's own
* 2384 Update distro version warning to not warn about new
Ubuntu/Fedora/OpenSUSE releases
* 2385 live image install doesn't work with mmcblk devices
* 2411 Buildhistory multiple commits broken
* 2437 Yocto-bsp tool in Eclipse fail to create BSP
* 2468 Security vulnerabilities in freetype 2.4.8
-
Known Issues
-
The Yocto project uses an implementation of Bugzilla at
Re: [yocto] ERROR: QA Issue: Architecture did not match (62 to 3) for linux-yocto_3.2.bb
-Original Message- From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com] Sent: Tuesday, July 17, 2012 5:35 PM To: Bodke, Kishore K Cc: yocto@yoctoproject.org; Zanussi, Tom; Darren Hart Subject: Re: ERROR: QA Issue: Architecture did not match (62 to 3) for linux- yocto_3.2.bb On 12-07-17 8:32 PM, Bodke, Kishore K wrote: -Original Message- From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com] Sent: Tuesday, July 17, 2012 5:30 PM To: Bodke, Kishore K Cc: yocto@yoctoproject.org; Zanussi, Tom; Darren Hart Subject: Re: ERROR: QA Issue: Architecture did not match (62 to 3) for linux- yocto_3.2.bb On 12-07-17 8:25 PM, Bodke, Kishore K wrote: -Original Message- From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com] Sent: Tuesday, July 17, 2012 5:21 PM To: Bodke, Kishore K Cc: yocto@yoctoproject.org Subject: Re: ERROR: QA Issue: Architecture did not match (62 to 3) for linux- yocto_3.2.bb On 12-07-17 8:16 PM, Bodke, Kishore K wrote: Hi, I am using local clone for 3.2 kernel and I get build fail for Linux-yocto_3.2.bb. WARNING: For recipe linux-yocto, the following files/directories were installed but not shipped in any package: WARNING: /etc ERROR: QA Issue: Architecture did not match (62 to 3) on /work//linux-yocto- 3.2.18+git1+20958298c233d15b1d705e7b0eb93282d6ecb5de_1+7d26ac083cb2 55888536b42b622b97fb438753ad-r1/packages-split/kernel- vmlinux/boot/vmlinux-3.2.18-yocto-standard ERROR: QA run found fatal errors. Please consider fixing them. ERROR: Function failed: do_package_qa Any idea why I get this? It means you've managed to get a 32 bit object in a 64 bit build. Have you tweaked the configuration ? I have not edited any configuration. I am using all 64 bit only. Can anyone else confirm this ? What BSP is this ? either it isn't listed above .. or I missed it. Tom ? Darren ? I don't have a build handy to check. I am building a new BSP which is not listed here. That is the reason I am using local clone. I cloned 3.2 kernel and created a new BSP based on ROMLEY. Without seeing your configuration, I can't say more. It looks like the tuning for userspace is 64 and you've built a 32 bit kernel, or vice versa. I tried rebuilding from scratch. It built fine. Not sure why it failed for the first time, Though it was the same configurations settings I had. Thanks Kishore. Darren/Tom may be able to help more. Cheers, Bruce Thanks Kishore. I can start a build overnight to try and see what is happening, if you send the details about what you are building here. Cheers, Bruce Cheers, Bruce Thanks Kishore. ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] beagleboard not booting
Release Date: 2011-11-04 X Protocol Version 11, Revision 0 Build Operating System: Linux 3.3.4-5.fc17.x86_64 x86_64 Current Operating System: Linux beagleboard 3.2.18-yocto-standard #1 Wed Jul 18 15:18:53 MDT 2012 armv7l Kernel command line: console=tty0 console=ttyO2,115200n8 mpurate=auto vram=16M o mapfb.mode=dvi:hd720 omapfb.vram=0:8M,1:4M,2:4M omapfb.debug=y omapdss.def_disp= dvi root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait Build Date: 15 July 2012 12:32:41PM Current version of pixman: 0.26.2 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Wed Jul 18 21:55:10 2012 (==) Using config file: /etc/X11/xorg.conf (==) Using system config directory /usr/share/X11/xorg.conf.d (EE) Failed to load module extmod (module does not exist, 0) (EE) Failed to load module dbe (module does not exist, 0) (EE) Failed to load module glx (module does not exist, 0) Starting advanced power management daemon: (EE) Failed to load module record ( module does not exist, 0) (EE) Failed to load module dri (module does not exist, 0) (EE) Failed to load module dri2 (module does not exist, 0) apmd. apmd[921]: apmd 3.2.1 interfacing with apm driver 1.13 and APM BIOS 1.2 (EE) omapfb(0): Failed to open /dev/fb2: No such file or directory (EE) omapfb(0): XVScreenInit failed Starting syslogd/klogd: done * Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon ...done. Starting Telephony daemon Stopping Bootlog daemon: bootlogd. D-BUS per-session daemon address is: unix:abstract=/tmp/dbus-YSsZ7bMMnl,guid=80b 47e1ed801ed95e922788b00b7 Yocto (Built by Poky 7.0) 1.2+snapshot-20120718 beagleboard ttyO2 beagleboard login: [settings daemon] Forking. run with -n to prevent fork matchbo x: Cant find a keycode for keysym 269025056 matchbox: ignoring key shortcut XF86C alendar=!$contacts matchbox: Cant find a keycode for keysym 2809 matchbox: ignorin g key shortcut telephone=!$dates matchbox: Cant find a keycode for keysym 2690250 50 matchbox: ignoring key shortcut XF86Start=!matchbox-remote -desktop ** (matchbo x-desktop:1007): WARNING **: Error loading icon: Icon 'computer' not present in theme ** (matchbox-desktop:1007): WARNING **: Error loading icon: Icon 'system-fi le-manager' not present in theme Thanks for any help I saw in the boot log that the x-server was started but nothing was displayed on the display. Any help will be appreciated. ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Manually fetching files (and disabling the sanity-checker)
Hi all, I've given up trying to work around Sony's firewall. After repeated attempts I still can't get any 'git:'-based URLS to work through the firewall. I vaguely recall the last time I worked on this (about 5.0 timeframe) there was a mirror where tarballs could be downloaded, if the git fetch didn't work. Is this mirror still available? If not, is there any way to disable the sanity-checker, and have bitbake tell me what repositories it's looking for, so I can manually construct a local mirror for yoctoproject to work off of? Is there any way to extract the tarballs from a build appliance image? Any advice or pointers would be appreciated. -- Tim = Tim Bird Architecture Group Chair, CE Workgroup of the Linux Foundation Senior Staff Engineer, Sony Network Entertainment = ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Manually fetching files (and disabling the sanity-checker)
On 07/18/2012 04:50 PM, Tim Bird wrote: Hi all, I've given up trying to work around Sony's firewall. After repeated attempts I still can't get any 'git:'-based URLS to work through the firewall. I vaguely recall the last time I worked on this (about 5.0 timeframe) there was a mirror where tarballs could be downloaded, if the git fetch didn't work. Is this mirror still available? If not, is there any way to disable the sanity-checker, and have bitbake tell me what repositories it's looking for, so I can manually construct a local mirror for yoctoproject to work off of? To disable the sanity check you can set CONNECTIVITY_CHECK_URIS to and that will cause it to be skipped. Regarding the mirroring, have you tried to just set the PREMIRRORS to use only http* and ftp in your local.conf: PREMIRRORS = \ ftp://.*/.* http://downloads.yoctoproject.org/mirror/sources/ \n \ http://.*/.* http://downloads.yoctoproject.org/mirror/sources/ \n \ https://.*/.*http://downloads.yoctoproject.org/mirror/sources/ \n I am not sure, but this might force protocols. You could try a bitbake -c fetchall universe I am going have Michael H. get you the information about where the the Downloads are. Let me know how it goes. Sau! Is there any way to extract the tarballs from a build appliance image? Any advice or pointers would be appreciated. -- Tim = Tim Bird Architecture Group Chair, CE Workgroup of the Linux Foundation Senior Staff Engineer, Sony Network Entertainment = ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] beagleboard not booting
Hello, Not getting any X display. As root I was able to ssh -Y 19.168.0.104 root@beagleboard:uname -a Linux beagleboard 3.2.18-yocto-standard #1 Wed Jul 18 15:18:53 MDT 2012 armv7l GNU/Linux # /etc/inittab: init(8) configuration. # $Id: inittab,v 1.91 2002/01/25 13:35:21 miquels Exp $ # The default runlevel. id:5:initdefault: # Boot-time system configuration/initialization script. # This is run first except when booting in emergency (-b) mode. si::sysinit:/etc/init.d/rcS # What to do in single-user mode. ~~:S:wait:/sbin/sulogin # /etc/init.d executes the S and K scripts upon change # of runlevel. # # Runlevel 0 is halt. # Runlevel 1 is single-user. # Runlevels 2-5 are multi-user. # Runlevel 6 is reboot. l0:0:wait:/etc/init.d/rc 0 l1:1:wait:/etc/init.d/rc 1 l2:2:wait:/etc/init.d/rc 2 l3:3:wait:/etc/init.d/rc 3 l4:4:wait:/etc/init.d/rc 4 l5:5:wait:/etc/init.d/rc 5 l6:6:wait:/etc/init.d/rc 6 # Normally not reached, but fallthrough in case of emergency. z6:6:respawn:/sbin/sulogin S:2345:respawn:/sbin/getty 115200 ttyO2 # /sbin/getty invocations for the runlevels. # # The id field MUST be the same as the last # characters of the device (after tty). # # Format: # id:runlevels:action:process # 1:2345:respawn:/sbin/getty 38400 tty1 root@beagleboard:/etc# startx xauth: file /home/root/.serverauth.667 does not exist X.Org X Server 1.11.2 Release Date: 2011-11-04 X Protocol Version 11, Revision 0 Build Operating System: Linux 3.3.4-5.fc17.x86_64 x86_64 Current Operating System: Linux beagleboard 3.2.18-yocto-standard #1 Wed Jul 18 15:18:53 MDT 2012 armv7l Kernel command line: console=tty0 console=ttyO2,115200n8 mpurate=auto vram=16M omapfb.mode=dvi:hd720 omapfb.vram=0:8M,1:4M,2:4M omapfb.debug=y omapdss.def_disp=dvi root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait Build Date: 15 July 2012 12:32:41PM Current version of pixman: 0.26.2 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.1.log, Time: Wed Jul 18 23:09:59 2012 (==) Using config file: /etc/X11/xorg.conf (==) Using system config directory /usr/share/X11/xorg.conf.d (EE) Failed to load module extmod (module does not exist, 0) (EE) Failed to load module dbe (module does not exist, 0) (EE) Failed to load module glx (module does not exist, 0) (EE) Failed to load module record (module does not exist, 0) (EE) Failed to load module dri (module does not exist, 0) (EE) Failed to load module dri2 (module does not exist, 0) (EE) omapfb(0): Failed to open /dev/fb2: No such file or directory (EE) omapfb(0): XVScreenInit failed /usr/lib/X11/xinit/xinitrc: line 56: exec: xterm: not found /usr/lib/X11/xinit/xinitrc: line 53: xclock: command not found /usr/lib/X11/xinit/xinitrc: line 52: twm: command not found /usr/lib/X11/xinit/xinitrc: line 54: xterm: command not found /usr/lib/X11/xinit/xinitrc: line 55: xterm: command not found xinit: connection to X server lost waiting for X server to shut down Server terminated successfully (0). Closing log file. root@beagleboard:/etc# dmesg Initializing cgroup subsys cpuset Initializing cgroup subsys cpu Linux version 3.2.18-yocto-standard (vi...@ws009.swbell.net) (gcc version 4.7.2 20120615 (prerelease) (GCC) ) #1 Wed Jul 18 15:18:53 MDT 2012 CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7d CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache Machine: OMAP3 Beagle Board Reserving 16777216 bytes SDRAM for VRAM Memory policy: ECC disabled, Data cache writeback On node 0 totalpages: 126976 free_area_init_node: node 0, pgdat c070d074, node_mem_map c0753000 Normal zone: 1024 pages used for memmap Normal zone: 0 pages reserved Normal zone: 125952 pages, LIFO batch:31 OMAP3630 ES1.2 (l2cache iva sgx neon isp 192mhz_clk ) Clocking rate (Crystal/Core/MPU): 26.0/332/600 MHz pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768 pcpu-alloc: [0] 0 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 125952 Kernel command line: console=tty0 console=ttyO2,115200n8 mpurate=auto vram=16M omapfb.mode=dvi:hd720 omapfb.vram=0:8M,1:4M,2:4M omapfb.debug=y omapdss.def_disp=dvi root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait PID hash table entries: 2048 (order: 1, 8192 bytes) Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) allocated 2097152 bytes of page_cgroup please try 'cgroup_disable=memory' option if you don't want memory cgroups Memory: 496MB = 496MB total Memory: 493824k/493824k available, 30464k reserved, 0K highmem Virtual kernel memory layout: vector : 0x - 0x1000 ( 4 kB) fixmap : 0xfff0 - 0xfffe ( 896 kB) vmalloc : 0xe080 - 0xf800 ( 376 MB) lowmem : 0xc000 - 0xe000 (
Re: [yocto] Manually fetching files (and disabling the sanity-checker)
On 07/18/2012 04:50 PM, Tim Bird wrote: Hi all, I've given up trying to work around Sony's firewall. After repeated attempts I still can't get any 'git:'-based URLS to work through the firewall. I vaguely recall the last time I worked on this (about 5.0 timeframe) there was a mirror where tarballs could be downloaded, if the git fetch didn't work. Sources the autobuilder uses are made available via http at http://downloads.yoctoproject.org/mirror/sources/ and can be used as a premirror. The directions in the following post should help you with set up, https://lists.yoctoproject.org/pipermail/yocto/2012-May/008966.html Michael Halstead Yocto Project / Sys Admin Is this mirror still available? If not, is there any way to disable the sanity-checker, and have bitbake tell me what repositories it's looking for, so I can manually construct a local mirror for yoctoproject to work off of? Is there any way to extract the tarballs from a build appliance image? Any advice or pointers would be appreciated. -- Tim = Tim Bird Architecture Group Chair, CE Workgroup of the Linux Foundation Senior Staff Engineer, Sony Network Entertainment = ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto smime.p7s Description: S/MIME Cryptographic Signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 0/1] meta: update crownbay.scc for newer emgd driver
-Original Message- From: Zanussi, Tom Sent: Wednesday, July 18, 2012 7:43 PM To: Kamble, Nitin A Cc: yocto@yoctoproject.org; bruce.ashfi...@windriver.com Subject: Re: [PATCH 0/1] meta: update crownbay.scc for newer emgd driver On Mon, 2012-07-16 at 22:57 -0700, nitin.a.kam...@intel.com wrote: From: Nitin A Kamble nitin.a.kam...@intel.com This commit changes emgd kernel driver for crownbay bsp to the emgd- 1.14. Nitin, Doesn't switching this over in the kenrnel require emgd-1.14 userspace recipe updates to work? Did I miss those? Tom Tom, I am holding the emgd 1.14 userspace commits until the kernel repository change goes upstream. The kernel recipe will need new SRCREV (with emgd 1.14 kernel parts) for the user level emgd 1.14 parts to work. And that dependency will get satisfied once this commit is in. Nitin ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 0/1] meta: update crownbay.scc for newer emgd driver
On Wed, 2012-07-18 at 19:58 -0700, Kamble, Nitin A wrote: -Original Message- From: Zanussi, Tom Sent: Wednesday, July 18, 2012 7:43 PM To: Kamble, Nitin A Cc: yocto@yoctoproject.org; bruce.ashfi...@windriver.com Subject: Re: [PATCH 0/1] meta: update crownbay.scc for newer emgd driver On Mon, 2012-07-16 at 22:57 -0700, nitin.a.kam...@intel.com wrote: From: Nitin A Kamble nitin.a.kam...@intel.com This commit changes emgd kernel driver for crownbay bsp to the emgd- 1.14. Nitin, Doesn't switching this over in the kenrnel require emgd-1.14 userspace recipe updates to work? Did I miss those? Tom Tom, I am holding the emgd 1.14 userspace commits until the kernel repository change goes upstream. The kernel recipe will need new SRCREV (with emgd 1.14 kernel parts) for the user level emgd 1.14 parts to work. And that dependency will get satisfied once this commit is in. Yeah, I understand, the crownbay is typically the most complicated update for all of those reasons - simultaneous new kernel version/recipe, new emgd branch, and new emgd userspace recipe all at the same time. In the past I've submitted them all at the same time for simultaneous review and some coordination with Bruce - once the kernel parts are in, the kernel recipe and the userspace parts can then be pulled in along with a simple follow-on patch to update the SRCREVs Bruce give us. The thing is that if Bruce pulls in the patch to switch to emgd-1.14 and only at that point do you post the userspace recipe, and it ends up needing some rework, in the meantime the graphics remain non-functional (I know, they already are, thanks to the package re-ordering patches breaking the current recipe, but hopefully the 1.14 changes will be in and we don't have to worry about it any more.). Does that make sense, and can you just post the userspace and kernel recipe parts before we give Bruce the go-ahead in making the kernel changes? (I'd also like to try it out myself as well...). Thanks, Tom Nitin ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] beagleboard not booting
B3NzaC1yc2EDAQABgwDCWs+/VxG1kpFFXea8eexz+ZMftcG8eDYv93TjeNhf NSJATNo9p14jnOAmLdfdZEkEJQbku1qvDWrQoZ2/IeE89SaRm45tAQEnZbfZKIFoAphvNhy2EDuT0pal Qff0GdQjeP3N9nqHpCgcsPviLK2YVng2XItWUOGbq/p3SmHLZ0CT root@beagleboard Fingerprint: md5 92:4e:e7:4c:fe:e9:5e:d4:71:1e:1e:76:b0:56:e9:da dropbear. X.Org X Server 1.11.2 Release Date: 2011-11-04 X Protocol Version 11, Revision 0 Build Operating System: Linux 3.3.4-5.fc17.x86_64 x86_64 Current Operating System: Linux beagleboard 3.2.18-yocto-standard #1 Wed Jul 18 15:18:53 MDT 2012 armv7l Kernel command line: console=tty0 console=ttyO2,115200n8 mpurate=auto vram=16M o mapfb.mode=dvi:hd720 omapfb.vram=0:8M,1:4M,2:4M omapfb.debug=y omapdss.def_disp= dvi root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait Build Date: 15 July 2012 12:32:41PM Current version of pixman: 0.26.2 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Wed Jul 18 21:55:10 2012 (==) Using config file: /etc/X11/xorg.conf (==) Using system config directory /usr/share/X11/xorg.conf.d (EE) Failed to load module extmod (module does not exist, 0) (EE) Failed to load module dbe (module does not exist, 0) (EE) Failed to load module glx (module does not exist, 0) Starting advanced power management daemon: (EE) Failed to load module record ( module does not exist, 0) (EE) Failed to load module dri (module does not exist, 0) (EE) Failed to load module dri2 (module does not exist, 0) apmd. apmd[921]: apmd 3.2.1 interfacing with apm driver 1.13 and APM BIOS 1.2 (EE) omapfb(0): Failed to open /dev/fb2: No such file or directory (EE) omapfb(0): XVScreenInit failed Starting syslogd/klogd: done * Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon ...done. Starting Telephony daemon Stopping Bootlog daemon: bootlogd. D-BUS per-session daemon address is: unix:abstract=/tmp/dbus-YSsZ7bMMnl,guid=80b 47e1ed801ed95e922788b00b7 Yocto (Built by Poky 7.0) 1.2+snapshot-20120718 beagleboard ttyO2 beagleboard login: [settings daemon] Forking. run with -n to prevent fork matchbo x: Cant find a keycode for keysym 269025056 matchbox: ignoring key shortcut XF86C alendar=!$contacts matchbox: Cant find a keycode for keysym 2809 matchbox: ignorin g key shortcut telephone=!$dates matchbox: Cant find a keycode for keysym 2690250 50 matchbox: ignoring key shortcut XF86Start=!matchbox-remote -desktop ** (matchbo x-desktop:1007): WARNING **: Error loading icon: Icon 'computer' not present in theme ** (matchbox-desktop:1007): WARNING **: Error loading icon: Icon 'system-fi le-manager' not present in theme Thanks for any help I saw in the boot log that the x-server was started but nothing was displayed on the display. Any help will be appreciated. ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Manually fetching files (and disabling the sanity-checker)
On Wed, Jul 18, 2012 at 6:50 PM, Tim Bird tim.b...@am.sony.com wrote: Hi all, I've given up trying to work around Sony's firewall. After repeated attempts I still can't get any 'git:'-based URLS to work through the firewall. I vaguely recall the last time I worked on this (about 5.0 timeframe) there was a mirror where tarballs could be downloaded, if the git fetch didn't work. Is this mirror still available? If not, is there any way to disable the sanity-checker, and have bitbake tell me what repositories it's looking for, so I can manually construct a local mirror for yoctoproject to work off of? Is there any way to extract the tarballs from a build appliance image? Any advice or pointers would be appreciated. Another less fun option is to create a siteconfig of some sort and start overriding git SRC_URI... SRC_URI_pn-linux-yocto = proto://some/internal/mirror/you/setup.git This might be useful for stuff that's not yet mirrored on yp.org -M ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
