[yocto] RPI VideoCore IV bare-metal release
Hello All.When Ultibo core was first released at the start of 2016 perhaps the most surprising thing for us was how much interest there was in using graphics and displaying information on screen, the questions began almost from day one and have persisted to this day. We had initially envisaged Ultibo as an IoT platform to be hidden away and used for sensing, controlling and monitoring often without any console, display or visual output at all. Of course IoT means many things to many people so our vision of network connected gadgets didn’t quite take account of the true potential offered by the Raspberry Pi.It is with great pleasure that we announce today the release of Ultibo core 2.0, the Beetroot release, and the inclusion of full support for the VideoCore IV GPU in all models of the Raspberry Pi. Anyone who has read about this subject will have seen a lot of information, some of it true, some of it not so true and others just plain wrong. Along the way we’ve seen many claims, there is no documentation, it’s all a secret and closed source or it can’t be done because they won’t release the details. We are not about to try and tell you this was an easy task but with a lot of research, reading, exploration and experimentation we have arrived at a result that we are very proud of. Once again it shows that anything can be done if you really want it to happen.Today we pass the baton to you, the Ultibo community, it’s your turn to show us what you can do now that you have some of the most powerful graphics features at your disposal. Let’s get the message out to the world and show everyone what is possible if you have a little bit of imagination, it’s time to make something amazing.As always the latest installer is available from the download page, get your copy now and try it out. For those who might prefer to build their own version for Windows or for Linux see the wiki for instructions. https://ultibo.org/Let me know if you have any questions. Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Bare metal Ultibo with openjjpeg with TFTP Server & Remote shell
Hello All,This should work on either a RPi2B or RPi3BThe micro sd-card that I used was 8GB with 1 partition.A 4GB micro sd-card should work just as well. Device Boot Start End Sectors Size Id Type/dev/sda1 * 2048 8390655 8388608 4G b W95 FAT32 https://github.com/develone/jpeg-2000-test/tree/master/bare-metal/openjp/sd-card these 5 files are needed on micro sd-card bootcode.bin fixup.dat MyBitmap.bmp This is a 2048 x 2048 lena in RGB format start.elf kernel7.img This file was created with Free Pascal Compiler FPC. A monitor needs to be connected on the HDMI connector to display the bootprocess. The RJ-45 connector needs to be connected to network that providesDHCP and NTP services. If the RJ-45 is not connected it will take a bitlonger to boot and the TFTP & Remote shell will not be available. This will require the transfer of files with USB apdater. This is the latest version with a compression ratio of 125:1 12583034 --> 100660 This will create the file test.j2k tftp xx.xx.xx.xx binary get test.j2k this md5sum should be c38b036fc5dbd84082f9490deb45c59e test.j2k running the test_tile_decoder ~/t_ultibo/build/bin/test_tile_decoder 0 0 2048 2048 test.j2k create test_wr.bmp https://github.com/develone/jpeg-2000-test/tree/master/bare-metal/openjp/decomp-sd-card Adding the files kernel7.img & t_1024_125r.j2k to the sd-card. The file t_1024_125r.j2k on Raspbian pi@raspberrypi3:~/t_ultibo/build/bin $ "./opj_compress -r 125 -i ~/jpeg-2000-test/bare-metal/LibC/lena_rgb_1024.bmp -o t_1024_125r.j2k" When rebooted the display will appear like 1024_1024.jpg The file test_wr.bmp will be created on Ultibo RPi Let me know if you have any questions. I look forward to hearing your comments on this.I have tested with a compression of 400:1 which further reduces the image transfer to about a 0.1 sec. Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] RPi fails when build is with deb packages works okay with rpm packages.
Hello All,Does anyone know if recipes are available for gcc-arm-none-eabi & binutils-arm-none-eabi? My build works okay when I use package_rpm and fails with package_deb. My bblayers.conf & local.conf are at https://github.com/develone/raspberrypi2_yocto/tree/master/poky2.2/raspberrypi2/conf_files Any and all help is appreciated. Parsing recipes: 100% |##| Time: 0:00:46 ~/wkg/yocto/RaspberryPi2/poky/build$ diff conf/local.conf ~/wkg/raspberrypi2_yocto/poky2.2/raspberrypi2/conf_files/local.conf 124c124 < PACKAGE_CLASSES ?= "package_deb" --- > PACKAGE_CLASSES ?= "package_rpm" Parsing of 1931 .bb files complete (0 cached, 1931 parsed). 2616 targets, 170 skipped, 0 masked, 0 errors. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "1.32.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "Ubuntu-16.04" TARGET_SYS = "arm-poky-linux-gnueabi" MACHINE = "raspberrypi2" DISTRO = "poky" DISTRO_VERSION = "2.2" TUNE_FEATURES = "arm armv7ve vfp thumb neon vfpv4 callconvention-hard cortexa7" TARGET_FPU = "hard" meta meta-poky meta-yocto-bsp = "morty:5aa481dfedfd089f0d6e8a3bae1b84134d5dff4c" meta-raspberrypi = "master:6bd1bfe472ea491c0edeb7c854d1c0cc5192afeb" meta-oe meta-python meta-multimedia meta-gnome = "morty:5aa481dfedfd089f0d6e8a3bae1b84134d5dff4c" meta-browser = "master:1edcce7791b4cee9a515c1f11b351753a4f8b12e" Initialising tasks: 100% |###| Time: 0:00:19 NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks ERROR: core-image-sato-1.0-r0 do_rootfs: Unable to install packages. Command '/home/vidal/wkg/yocto/RaspberryPi2/poky/build/tmp/sysroots/x86_64-linux/usr/bin/apt-get install --force-yes --allow-unauthenticated opencv xchat gsl packagegroup-base-extended psplash-raspberrypi libftdi1-2 libgtk-3.0 apt geany libmad0 texinfo pv minicom cmake libmtp9 python-pip ghostscript packagegroup-core-sdk python-imaging git dpkg tcl v4l-utils yasm packagegroup-core-ssh-dropbear rsync linux-firmware lame gtkmm packagegroup-core-x11-base packagegroup-core-x11-sato iproute2 gperf liba52-0 iputils vlc packagegroup-core-boot packagegroup-core-standalone-sdk-target packagegroup-core-x11-sato-games tk xterm squashfs-tools gnuplot tar chkconfig openjpeg tree man libgtk-2.0' returned 100: Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: packagegroup-core-x11-base : Depends: packagegroup-core-x11-utils but it is not going to be installed vlc : Depends: libgl-mesa (>= 12.0.1) but it is not going to be installed E: Unable to correct problems, you have held broken packages. ERROR: core-image-sato-1.0-r0 do_rootfs: Function failed: do_rootfs ERROR: Logfile of failure stored in: /home/vidal/wkg/yocto/RaspberryPi2/poky/build/tmp/work/raspberrypi2-poky-linux-gnueabi/core-image-sato/1.0-r0/temp/log.do_rootfs.2105 ERROR: Task (/home/vidal/wkg/yocto/RaspberryPi2/poky/meta/recipes-sato/images/core-image-sato.bb:do_rootfs) failed with exit code '1' Thanks in advance. Cheers, Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Raspberrypi bare-metal interfaced to PMod GPS receiver
Hello All Just completed the interface of a http://store.digilentinc.com/pmod-gps-gps-receiver/$39.99 with RPi 2B Running Ultibo Bare metal on Raspberrypi2B & PMOD GPS with just 4 fileskernel7.img, start.elf, bootcode.bin, and fixup.dat.Receives GPS data on UART and sends message on Ethernet using UDP.More information see https://ultibo.org/ on bare metal project and https://github.com/develone/ultibo_serial_testingOn what creates the kernel7.img, see the README.md One of many messages sent by GPS receiver. $GPGGA,132531.000,3145.5590,N,10620.5407,W,2,9,0.89,1209.1,M,-26.2,M,,*5Btime 132531.000Latitude 3145.5590 NLongitude 10620.5407 WElevation 1209.1 MThe program calls C to compute the checksum. The Check sum of the character between the "$" and the "*"81 bytes readThe checksum of ch_sum_test.dat is 0x5bComputed by taking the checksum Exclusive or with each character. Let me know if this of interest.. Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] bare-metal RPi2B & RPI3B
Hello All, As of now I have been able to get the library of openjpeg running in bare-metal RPi2B or RPi3B.With just 5 files on a RPi2B or RPi3B the compression of bitmap is done.bootcode.bin fixup.dat kernel7.img MyBitmap.bmp start.elf.In addition this provides a TFTP server and Telnet services.In 26 sec the RPi3B boots and does a compression of a 1024 x 1024 image.The compression takes 5 sec These files are found at https://github.com/develone/jpeg-2000-test/tree/master/bare-metal/openjp/sd-card/see https://github.com/develone/jpeg-2000-test/blob/master/bare-metal/LibC/LibC.pdfand the openjpeg library https://github.com/develone/openjpeg/blob/ultibo/openjpeg.odtI forked the openjpeg repo and created a ultibo branch.The compiler used is arm-none-eabi tools to compile the C code and Free Pascal Compiler to compile and link kernel7.img. This is the documentation to date. pi@raspberrypi3:~ $ export PATH=/home/pi/ultibo/core/fpc/bin:$PATHpi@raspberrypi3:~ $ cd jpeg-2000-test/bare-metal/openjp/pi@raspberrypi3:~/jpeg-2000-test/bare-metal/openjp $ ./compile.sh Thu 13 Apr 11:36:26 UTC 2017Word count arm-none-eabi-ar -t libopenjp2.acopied from /home/pi/t_ultibo/src/lib/openjp2 22 22 180Target OS: UltiboCompiling DWT_LIFT_RPi2.lprCompiling uTFTP.pasAssembling utftpCompiling uliftbitmap.pasCompiling uBufferToC.pasAssembling uliftbitmapAssembling dwt_lift_rpi2Linking DWT_LIFT_RPi21086 lines compiled, 4.7 sec, 2733156 bytes code, 89252 bytes data-rw-r--r-- 1 pi pi 7364 Apr 13 11:36 dwtlift.o-rwxr-xr-x 1 pi pi 2808540 Apr 13 11:36 kernel7.img-rw-r--r-- 1 pi pi 356242 Apr 13 11:36 libdwtlift.a-rw-r--r-- 1 pi pi 356242 Apr 13 11:36 libopenjp2.awhen ./compile.sh is executed should be 23Word count libopenjp2_obj.txt in /home/pi/t_ultibo/src/lib/openjp2plus dwtlift.o 23 23 190 libopenjp2_obj.txt Does Wine run in Yocto? This would make Ultibo the Bare-metal project work in Yocto. Let me know if you have any questions. Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613 On Friday, February 3, 2017 12:37 AM, "yocto-requ...@yoctoproject.org" <yocto-requ...@yoctoproject.org> wrote: Send yocto mailing list submissions to yocto@yoctoproject.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.yoctoproject.org/listinfo/yocto or, via email, send a message with subject or body 'help' to yocto-requ...@yoctoproject.org You can reach the person managing the list at yocto-ow...@yoctoproject.org When replying, please edit your Subject line so it is more specific than "Re: Contents of yocto digest..." Today's Topics: 1. Re: Ruby and OpenSSL version mismatch? (Khem Raj) 2. bare-metal RPi2B & RPI3B (Edward Vidal) 3. [meta-cgl][PATCH 3/3] initramfs: fix parsing issue with do to uboot inclusion (Armin Kuster) 4. [meta-cgl][PATCH 1/3] iscsi-initiator-utils: make it DISTRO_FEATURE dependent (Armin Kuster) -- Message: 1 Date: Thu, 02 Feb 2017 22:47:40 + From: Khem Raj <raj.k...@gmail.com> To: Takashi Matsuzawa <tmatsuz...@xevo.com>, "yocto@yoctoproject.org" <yocto@yoctoproject.org> Subject: Re: [yocto] Ruby and OpenSSL version mismatch? Message-ID: <camkf1sr4go-8_9k+1d32jkzsewkguc9s+iz94vk_ifkrv_-...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" Send a back port request On Thu, Feb 2, 2017 at 5:32 AM Takashi Matsuzawa <tmatsuz...@xevo.com> wrote: > Hello, I just tried and the below seems to be the fix. > > > https://patchwork.openembedded.org/patch/11/ > > -- > *From:* Takashi Matsuzawa > *Sent:* Thursday, February 2, 2017 3:25 PM > *To:* yocto@yoctoproject.org > *Subject:* Ruby and OpenSSL version mismatch? > > > Hello, Yocto. > > I am trynig a build of fido based yocto image, with openssl 1.0.2j for > security reason. > The openssl recipe itself builds successfully, but later in the build I > see error in jscore. > In fact, ruby is complaining that 'OPENSSL_1.0.0' is not available. > > | > /xxx/sysroots/x86_64-linux/usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in > `require': > /xxx/sysroots/x86_64-linux/usr/lib/ruby/2.2.0/x86_64-linux-gnu/digest/../../../../libcrypto.so.1.0.0: > version `OPENSSL_1.0.0' not found (required by > /xxx/sysroots/x86_64-linux/usr/lib/ruby/2.2.0/x86_64-linux-gnu/digest/sha1.so) > - > /xxx/sysroots/x86_64-linux/usr/lib/ruby/2.2.0/x86_64-linux-gnu/digest/sha1.so > (LoadError) > | from > /xxx/sysroots/x86_64-linux/usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in > `require' > | from > /xxx/work/core2-32-poky-linux/qtwebkit/5.5.0+gitAUTOINC+0d592678ba-r0/git/Source/JavaScriptCore/offlineasm/generate_offset_extractor.rb:30:in > `' >
[yocto] bare-metal RPi2B & RPI3B
Hello All, Today I was able to get the lifting step in bare-metal. With just 5 files on a RPi2B the lifting step was done. bootcode.bin fixup.dat kernel7.img MyBitmap.bmp start.elf These files are found at https://github.com/develone/jpeg-2000-test/tree/master/bare-metal/LibC/sd-card/RPi2 see https://github.com/develone/jpeg-2000-test/blob/master/bare-metal/LibC/LibC.pdf This is the documentation to date. Let me know if you have any questions. Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Adding Fortran to Raspberrypi2
Hi,
I tried building on the target RPi2B.The config.log and the steps that I did
are found at
https://gist.github.com/develone/bfa03e975f173a07b9fcb22a4d817df6
I tried reporting the bug but the acct creation is restricted.Let me know if I
can provide adding information,Thanks,
Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613
On Friday, December 9, 2016 9:04 AM, "yocto-requ...@yoctoproject.org"
<yocto-requ...@yoctoproject.org> wrote:
Send yocto mailing list submissions to
yocto@yoctoproject.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.yoctoproject.org/listinfo/yocto
or, via email, send a message with subject or body 'help' to
yocto-requ...@yoctoproject.org
You can reach the person managing the list at
yocto-ow...@yoctoproject.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of yocto digest..."
Today's Topics:
1. Adding Fortran to Raspberrypi2 (Edward Vidal)
2. Re: Kernel config incremental modification not working.
(Bruce Ashfield)
3. Re: update mechanisms (Patrick Ohly)
4. Re: update mechanisms (Stefano Babic)
--
Message: 1
Date: Fri, 9 Dec 2016 13:28:35 +0000 (UTC)
From: Edward Vidal <devel...@sbcglobal.net>
To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: [yocto] Adding Fortran to Raspberrypi2
Message-ID: <405620911.1114427.1481290115...@mail.yahoo.com>
Content-Type: text/plain; charset="utf-8"
Hi
Trying to add fortran to 6.2.0 branch morty for a Raspberrypi2
Step 1 modified meta/recipes-devtools/gcc/gcc-6.2.inc
-FORTRAN = ""
+FORTRAN = ",fortran"
bitbake core-image-sato created the image
Testing on target. I see fortran in the command gcc -v.
gcc -v --enable-languages=c,c++,fortran gcc version 6.2.0 (GCC)
With the command ./configure for octave.
checking whether a usable Fortran compiler was found... no
configure: error: A Fortran compiler is required
Step 2 Checking the mailing list.
??? |Hi
??? |
??? |On Mon, 8 Feb 2016 08:19:53 +
??? |"Liubchynskyi, Stanislav (Nokia - PL/Wroclaw)" wrote:
??? |
??? |> Hi,
??? |> I want to add fortran support to yocto build. I try different way whitch
describe in the ethernet but enyone does't work. I use fido branch and gcc 4.9.
Can you describe me step by step how to enable fortran in yocto or where I can
find work instruction.
??? |> Thanks for help.
??? |Fortran support in gcc is disabled by default, to enable it add the
following line to your config, then build the libgfortran package.
??? |FORTRAN_forcevariable = ",fortran"
??? |>
??? |>
??? |>
??? |> Best regards,
??? |>
??? |> Stanislav Liubchynskyi
??? |> Software Developer, LFS, OPSW Wroclaw
??? |> Mobile Broadband, Nokia Networks>?
I added FORTRAN_forcevariable = ",fortran" to my config.? Still no fortran.
I added libgfortran to variable IMAGE_INSTALL_append and I get the following
error
?
ERROR: oe_runmake failed
../../../../../../../../work-shared/gcc-6.2.0-r0/gcc-6.2.0/libgfortran/runtime/backtrace.c:37:33:
fatal error: backtrace-supported.h: No such file or directory
?#include "backtrace-supported.h"
^
compilation terminated.
Thanks in advance,
?Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.yoctoproject.org/pipermail/yocto/attachments/20161209/644f3ef0/attachment-0001.html>
--
Message: 2
Date: Fri, 9 Dec 2016 08:37:47 -0500
From: Bruce Ashfield <bruce.ashfi...@windriver.com>
To: Bent Bisballe Nyeng <x...@mjolner.dk>, "yocto@yoctoproject.org"
<yocto@yoctoproject.org>
Subject: Re: [yocto] Kernel config incremental modification not
working.
Message-ID: <1f6d8fc5-2853-072f-72d5-785c5bd78...@windriver.com>
Content-Type: text/plain; charset="windows-1252"; format=flowed
On 2016-12-09 02:25 AM, Bent Bisballe Nyeng wrote:
> On 12/08/2016 05:06 PM, Bruce Ashfield wrote:
>> On 2016-12-08 09:06 AM, Bent Bisballe Nyeng wrote:
>>> Hi list
>>>
>>> I am working on a project based on the iMX6UL-EVK using the meta-fsl-arm
>>> layer for the kernel.
>>> In a local layer I have a bbappend recipe containing a patch for an
>>> extra kernel feature (a framebuffer device) in that kernel as well as a
>>> .cfg enabling said feature.
>>> The bbappend recipe is located in
>>> recipes-kernel/linux/linux-fslc-imx_%.bbappend and looks like this:
>>> FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
>>>
>>> SRC_URI += " \
>>> file://0001-mxc-4.1.patch \
>
[yocto] Adding Fortran to Raspberrypi2
Hi Trying to add fortran to 6.2.0 branch morty for a Raspberrypi2 Step 1 modified meta/recipes-devtools/gcc/gcc-6.2.inc -FORTRAN = "" +FORTRAN = ",fortran" bitbake core-image-sato created the image Testing on target. I see fortran in the command gcc -v. gcc -v --enable-languages=c,c++,fortran gcc version 6.2.0 (GCC) With the command ./configure for octave. checking whether a usable Fortran compiler was found... no configure: error: A Fortran compiler is required Step 2 Checking the mailing list. |Hi | |On Mon, 8 Feb 2016 08:19:53 + |"Liubchynskyi, Stanislav (Nokia - PL/Wroclaw)" wrote: | |> Hi, |> I want to add fortran support to yocto build. I try different way whitch describe in the ethernet but enyone does't work. I use fido branch and gcc 4.9. Can you describe me step by step how to enable fortran in yocto or where I can find work instruction. |> Thanks for help. |Fortran support in gcc is disabled by default, to enable it add the following line to your config, then build the libgfortran package. |FORTRAN_forcevariable = ",fortran" |> |> |> |> Best regards, |> |> Stanislav Liubchynskyi |> Software Developer, LFS, OPSW Wroclaw |> Mobile Broadband, Nokia Networks> I added FORTRAN_forcevariable = ",fortran" to my config. Still no fortran. I added libgfortran to variable IMAGE_INSTALL_append and I get the following error ERROR: oe_runmake failed ../../../../../../../../work-shared/gcc-6.2.0-r0/gcc-6.2.0/libgfortran/runtime/backtrace.c:37:33: fatal error: backtrace-supported.h: No such file or directory #include "backtrace-supported.h" ^ compilation terminated. Thanks in advance, Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] raspberry pi gtkmm_3.0.bb
Hello All, Thanks to Piotr Lewicki who noticed package version (PV) is "3.0-r0=" and not "3.0-r0" ?? Maybe this "=" sign causes some problem. There were 2 occurrences and 7 without the "=" /poky/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/gtkmm/3.0-r0=/usr He recommended that I add PR = "r0" to the recipe. The log indicates arm-poky-linux-gnueabi-libtool: warning: library '/home/vidal/wkg/yocto/RaspberryPi2/poky/build/tmp/sysroots/raspberrypi2/usr/lib/libatkmm-1.6.la' was moved. arm-poky-linux-gnueabi-libtool: error: cannot find the library '/usr/lib/libatk-1.0.la' or unhandled argument '=/usr/lib/libatk-1.0.la' Makefile:748: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/home/vidal/wkg/yocto/RaspberryPi2/poky/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/gtkmm/3.0-r0/build' Makefile:534: recipe for target 'all' failed make: *** [all] Error 2 Thanks in advance. Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613 On Friday, November 18, 2016 8:04 AM, "yocto-requ...@yoctoproject.org" <yocto-requ...@yoctoproject.org> wrote: Send yocto mailing list submissions to yocto@yoctoproject.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.yoctoproject.org/listinfo/yocto or, via email, send a message with subject or body 'help' to yocto-requ...@yoctoproject.org You can reach the person managing the list at yocto-ow...@yoctoproject.org When replying, please edit your Subject line so it is more specific than "Re: Contents of yocto digest..." Today's Topics: 1. raspberry pi gtkmm_3.0.bb (Edward Vidal) 2. Re: populate_sdk_ext: Unable to locate package nativesdk-buildtools-perl-dummy (Paul Eggleton) 3. uninative vs. BB_NO_NETWORK (Vuille, Martin (Martin)) 4. Re: undefined references to `__dso_handle' (Daniel.) ------ Message: 1 Date: Thu, 17 Nov 2016 21:01:33 + (UTC) From: Edward Vidal <devel...@sbcglobal.net> To: "yocto@yoctoproject.org" <yocto@yoctoproject.org> Subject: [yocto] raspberry pi gtkmm_3.0.bb Message-ID: <1211982120.2332029.1479416493...@mail.yahoo.com> Content-Type: text/plain; charset="utf-8" Hello All, I working with software that needs gtkmm_3.0. Poky 2.2 provides gtkmm_2.24.3 in meta-oe/reipes-gnome/gtk+ I used recipetool and created gtkmm_3.0.bb I modified some lines and was able to get the recipe to fetch, unpack, and configure. when it tries to compile I am getting errors. Makefile:748: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/home/vidal/wkg/yocto/RaspberryPi2/poky/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/gtkmm/3.0-r0/build' Makefile:534: recipe for target 'all' failed make: *** [all] Error 2 ERROR: Function failed: do_compile (log file is located at /home/vidal/wkg/yocto/RaspberryPi2/poky/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/gtkmm/3.0-r0/temp/log.do_compile.17760) The recipe that I am trying to create is https://gist.github.com/develone/ffa79327ccd49e9aa9f5c07e4db9ad7d Any an all help is appreciated. Thanks in advance ?Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613 -- next part -- An HTML attachment was scrubbed... URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20161117/e682ad6a/attachment-0001.html> -- Message: 2 Date: Fri, 18 Nov 2016 14:46:07 +1300 From: Paul Eggleton <paul.eggle...@linux.intel.com> To: Michel D'HOOGE <michel.dho...@free.fr> Cc: yocto@yoctoproject.org Subject: Re: [yocto] populate_sdk_ext: Unable to locate package nativesdk-buildtools-perl-dummy Message-ID: <4182204.zx1rafn...@peggleto-mobl.ger.corp.intel.com> Content-Type: text/plain; charset="us-ascii" Hi Michel, On Wed, 16 Nov 2016 11:48:21 Michel D'HOOGE wrote: > I try to produce an extensible SDK for core-image-sato with the following > configuration: > > BB_VERSION = "1.32.0" > BUILD_SYS = "x86_64-linux" > NATIVELSBSTRING = "universal" > TARGET_SYS = "x86_64-poky-linux" > MACHINE = "vtc7200" > DISTRO = "poky-systemd" > DISTRO_VERSION = "2.2" > TUNE_FEATURES = "m64 corei7" > > The machine is based on an intel-corei7, with some features removed. And the > distro is poky-based, with only systemd (as detailed in the ref manual). > And I get the following error: > > > ERROR : buildtools-tarball-1.0-r0 do_populate_sdk: Unable to install > packages. Command '/mnt/Yocto/vedecom-x86/build/tmp/sysroots/x86_ > 64-linux/usr/bin/apt-get install --force-yes --allow-unauthenticated > nativesdk-locale-base-en-
[yocto] raspberry pi gtkmm_3.0.bb
Hello All, I working with software that needs gtkmm_3.0. Poky 2.2 provides gtkmm_2.24.3 in meta-oe/reipes-gnome/gtk+ I used recipetool and created gtkmm_3.0.bb I modified some lines and was able to get the recipe to fetch, unpack, and configure. when it tries to compile I am getting errors. Makefile:748: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/home/vidal/wkg/yocto/RaspberryPi2/poky/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/gtkmm/3.0-r0/build' Makefile:534: recipe for target 'all' failed make: *** [all] Error 2 ERROR: Function failed: do_compile (log file is located at /home/vidal/wkg/yocto/RaspberryPi2/poky/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/gtkmm/3.0-r0/temp/log.do_compile.17760) The recipe that I am trying to create is https://gist.github.com/develone/ffa79327ccd49e9aa9f5c07e4db9ad7d Any an all help is appreciated. Thanks in advance Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] meta-raspberry build fails with either VLC or FireFire.
Hi All,
My earlier build included VLC and FireFox.
meta-yocto-bsp = "fido:0f8d89ce66cfffccc9911d6c61470a585173b79d"
meta-raspberrypi = "master:7457bf182c8fd550ec877ecd786a3edd16e65495"
meta-oe
meta-python
meta-multimedia
meta-gnome = "fido:0f8d89ce66cfffccc9911d6c61470a585173b79d"
These were pulled a day ago.
I upgraded to the following and now VLC & FireFox causes errors
meta-yocto-bsp = "master:dd282d475cb4fde4f4e6fd7afe437dc001584587"
meta-raspberrypi = "master:f2cff839f52a6e6211337fc45c7c3eabf0fac113"
meta-oe
meta-python
meta-multimedia
meta-gnome = "master:dd282d475cb4fde4f4e6fd7afe437dc001584587"
meta-browser = "master:ca96f4326345dcd779fc539877a04f069f431749"
Since VLC & FireFox depend on gtk+3-3.18.2 In the above repos.
They fail in do_configure when I add to IMAGE_INSTALL_append
in my local.conf file.
These are the what I added in added local.conf
#MACHINE ??= "qemux86"
ENABLE_SPI_BUS = "1"
MACHINE ??= "raspberrypi2"
GPU_MEM = "16"
PREFERRED_PROVIDER_virtual/egl ?= "vc-graphics-hardfp"
PREFERRED_PROVIDER_virtual/libgles2 ?= "vc-graphics-hardfp"
PREFERRED_PROVIDER_jpeg = "libjpeg-turbo"
PREFERRED_PROVIDER_jpeg-native = "libjpeg-turbo-native"
#adding the XSTOOLs depends
IMAGE_INSTALL_append = " xterm git \
intelhex python-bitstring pyusb PyPubSub xstools \
chkconfig v4l-utils python-imaging socat lame \
linux-firmware jasper gsl hexedit man iproute2 \
gperf tree cmake tar pv openjpeg squashfs-tools \
rsync yasm gparted tcl tk rpi-gpio geany python-pip iputils \
opencv opencv-samples opencv-apps python-opencv devmem2 \
"
#DL_DIR ?= "${TOPDIR}/downloads"
DL_DIR ?= "/home/vidal/wkg/yocto/kernel_test/downloads"
EXTRA_IMAGE_FEATURES = "debug-tweaks dev-pkgs tools-sdk doc-pkgs qt4-pkgs"
This what is in bblayers.conf
# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly
LCONF_VERSION = "6"
BBPATH = "${TOPDIR}"
BBFILES ?= ""
BBLAYERS ?= " \
/home/vidal/wkg/yocto/kernel_test/poky/meta \
/home/vidal/wkg/yocto/kernel_test/poky/meta-yocto \
/home/vidal/wkg/yocto/kernel_test/poky/meta-yocto-bsp \
/home/vidal/wkg/yocto/kernel_test/poky/meta-raspberrypi \
/home/vidal/wkg/yocto/kernel_test/poky/meta-oe \
/home/vidal/wkg/yocto/kernel_test/poky/meta-python \
/home/vidal/wkg/yocto/kernel_test/poky/meta-multimedia \
/home/vidal/wkg/yocto/kernel_test/poky/meta-gnome \
/home/vidal/wkg/yocto/kernel_test/poky/meta-browser \
"
BBLAYERS_NON_REMOVABLE ?= " \
/home/vidal/wkg/yocto/kernel_test/poky/meta \
/home/vidal/wkg/yocto/kernel_test/poky/meta-yocto \
"
Any and all help is appreciated.
This is the goal of the build.
Transferred to my google dropbox core-image-sato120815.zip
If you do not access let me know and I will add you to share list.
The sha1sum should be the following:
12dc5b4e9cb737696b71c6502ffd095f5a896720 core-image-sato120815.zip
In the file sha1sum.txt
1.4 GB (1,449,293,907 bytes)
This is what I used to transfer to a micro SD card.
"gzip -dc /home/vidal/wkg/yocto/core-image-sato120815.zip | pv | dd bs=16M
of=/dev/sdb"
3.64GB 0:08:01 [7.74MB/s]
The root passwd is raspberrypi
This will fit on 4GB micro SD card.
Provides the Linux 4.1.10 Kernel, git, gcc-5.2.0, OpenCV, Myhdl, Iverilog,
gsl, yosys, arachne-pnr, CAT-Board, rhea, Xstools and Gtkwave.
CAT-Board Features
* Lattice iCE40-HX8K FPGA in 256-pin BGA.
* 32 MByte SDRAM (16M x 16).
* Serial configuration flash (at least 2 Mbit).
* Three Grove connectors.
* Two PMOD connectors.
* One 20x2 header with 3.3V, ground and 18 FPGA I/Os.
* Two SATA headers (for differential signals; don't know if they would work
with SATA HDDs.)
* DIP switch with four SPST switches.
* Two momentary pushbuttons.
* Four LEDs.
* 100 MHz oscillator.
* 5.0 V jack for external power supply.
* 3.3 V and 1.2 V regulators.
* Adjustable voltage on one bank of FPGA I/O pins.
* 32 KByte HAT EEPROM.
* 40-pin RPi GPIO header.
See Driving an Array of LED Digits with the CAT Board at
https://hackaday.io/project/7982-cat-board.
The prototype has been tested with Yocto & RaspBian on RPi2B.
With these tools, this combo is a complete development system, to develop, test
and program
FPGA applications completly on the RPi2B and CAT-Board.
The schematic is available at
https://raw.githubusercontent.com/xesscorp/CAT-Board/master/docs/Manual/pics/CAT_schematic.pdf
This should be around the cost as the StickIt-MB & XulA2-LX9. Dave will be
finalizing the price soon.
The led digit provides a good method to test the CAT-Board and RPi2B.
see xess.com
Cheers,
Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Problem using unix source in do_compile
Kherm, I did follow Paul recommendations. The issue was not just using the source unix command. When I changed source to '.', a new error occurred. do_compile) failed with exit code '1' What is the unexpected > operator? This error was caused by not having a gmake. Searching to resolve the gmake issue, which some recommend linking to make. On this problem I have been working for quite some time. I don't now if this is related to dash bash issue or not. I was working on a Fedora system which uses bash. My binutils 2.23.2-r4 was most likely built on the Fedora system. I needed to switch to an O/S that support Xilinx Tools, so I copied my working tree to a Ubuntu system. I have removed from tmp down several times trying different things and bitbake core-image-sato rebuilds the tmp area. I wanted to remove from build, but then is when my binutils 2.23.2-r4 would failed. I had to restore my build/buildhistory build/cache build/conf build/sanity_info build/sstate-cache and then tmp was rebuilt with bitbake core-image-sato. I really do appreciate all the help that the folks on this mailing list and meta-xilinx mailing list. Thanks for all the help, Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613 On Monday, November 30, 2015 1:21 PM, Khem Raj <raj.k...@gmail.com> wrote: On Nov 25, 2015 7:30 PM, "Edward Vidal" <devel...@sbcglobal.net> wrote: > > Hello all, > After a long time of trying to get Michael Looijmans fpga-image-adi.bb from > meta-topic to work. I wanted to share the fix. I was running Ubuntu 12.04. > which sh > /bin/sh > cd /bin > ls -la sh > lrwxrwxrwx 1 root root 4 May 16 2015 sh -> dash > ln -sf bash sh > ls -la /bin/sh > lrwxrwxrwx 1 root root 4 Nov 25 17:28 /bin/sh -> bash > which gmake > /usr/bin/gmake > cd /usr/bin > ln -sf make gmake > ls -la /usr/bin/gmake > Thanks for all the help.There are better ways to switch default sh to be bash > or dash dpkg-reconfigure dash would offer you the selection choice. But why > did you not try Paul's suggestions > > Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613 > > -- > ___ > 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] Problem using unix source in do_compile
Hi all,I am trying to use run the bitbake on a recipe that in the do_compile uses the unix command source.This is the error that I am getting. Log data follows:| DEBUG: Executing shell function do_compile | /home/vidal/POKY/dora_build/poky/build/tmp/work/zedboard-poky-linux-gnueabi/fpga-image-adi/1.AUTOINC-3e6cfd4858-r0/temp/run.do_compile.25492: 112: /home/vidal/POKY/dora_build/poky/build/tmp/work/zedboard-poky-linux-gnueabi/fpga-image-adi/1.AUTOINC-3e6cfd4858-r0/temp/run.do_compile.25492: source: not found | WARNING: exit code 127 from a shell command. | ERROR: Function failed: do_compile (log file is located at /home/vidal/POKY/dora_build/poky/build/tmp/work/zedboard-poky-linux-gnueabi/fpga-image-adi/1.AUTOINC-3e6cfd4858-r0/temp/log.do_compile.25492)At github I have the original inc file that is used by the recipe fpga-image-adi.bb 87a75850b6f36bf1f09ac0f071587629ba630c1ehttps://github.com/develone/zedboard_yocto/commits/master/fpga-image.inc I made some changes which allows me to manually run the Xilinx commands and then re-run the bitbake fpga-image-adithe version e199e9ce0806dc257fcafdda26de29f4cd443e24regards, Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] raspberry pi do rootfs
Hi Raj,This works for me. I first do bitbake core-image-sato. I first delete all partitions from the SD card using fdisk /dev/sdx as user root or sudo.where x is what I see using fdisk -l for the SD card as user root or sudo. Then I use the following command"dd if=tmp/deploy/images/raspberrypi2/core-image-sato-raspberrypi2.rpi-sdimg | pv | sudo dd of=/dev/sdb bs=16M"as user root or sudo.Hope this helps.Cheers, Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613 On Wednesday, November 11, 2015 6:28 AM, "yocto-requ...@yoctoproject.org" <yocto-requ...@yoctoproject.org> wrote: Send yocto mailing list submissions to yocto@yoctoproject.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.yoctoproject.org/listinfo/yocto or, via email, send a message with subject or body 'help' to yocto-requ...@yoctoproject.org You can reach the person managing the list at yocto-ow...@yoctoproject.org When replying, please edit your Subject line so it is more specific than "Re: Contents of yocto digest..." Today's Topics: 1. Re: raspberry pi do rootfs (Raj Jar) 2. external-toolchain (Virgilia Eigner) 3. Re: external-toolchain (Virgilia Eigner) 4. Re: raspberry pi do rootfs (Andrei Gherzan) -- Message: 1 Date: Wed, 11 Nov 2015 13:39:02 +0530 From: Raj Jar <jarraj...@gmail.com> To: yocto@yoctoproject.org Subject: Re: [yocto] raspberry pi do rootfs Message-ID:
[yocto] openjpeg on github
Hello All,When a project is using git instead of tar file which branch is
used?Is best to be using git or tar file with yocto?
Openjepeg is now on github. The openjpeg 2.1.0 was at SRC_URI =
"${SOURCEFORGE_MIRROR}/project/${BPN}.mirror/${PV}/${BPN}-${PV}.tar.gz". I
did the following to create a new recipe.
recipetool create -o
/home/vidal/wkg/yocto/RaspberryPi2/poky/meta-oe/recipes-graphics/openjpeg/openjpeg_git.bb
https://github.com/uclouvain/openjpeg.git
# Recipe created by recipetool
# This is the basis of a recipe and may need further editing in order to be
fully functional.
# (Feel free to remove these comments when editing.)
#
# Unable to find any files that looked like license statements. Check the
accompanying
# documentation and source headers and set LICENSE and LIC_FILES_CHKSUM
accordingly.
#
# NOTE: LICENSE is being set to "CLOSED" to allow you to at least start
building - if
# this is not accurate with respect to the licensing of the software being
built (it
# will not be in most cases) you must specify the correct value before using
this
# recipe for anything other than initial testing/development!
LICENSE = "CLOSED"
LIC_FILES_CHKSUM = ""
SRC_URI = "https://github.com/uclouvain/openjpeg.git;
SRC_URI[md5sum] = "9ad2bb8d9e833bfd74b4885a0f1d3882"
SRC_URI[sha256sum] =
"af9d33bcc1485f1938ceb13464e66041dc4538dccc8edf02320141b0da9f95c6"
inherit cmake
DEPENDS = "libpng tiff lcms"
# NOTE: no Makefile found, unable to determine what needs to be done
do_configure () {
# Specify any needed configure commands here
mkdir build
}
do_compile () {
# Specify compilation commands here
cd build
cmake ../
}
do_install () {
# Specify install commands here
}
When I try bitbake openjpeg I get several errors.
The INSTALL file Using cmake (see www.cmake.org)
Type:
cmake .
makeOn my system I created a buildcd build
cmake ../makeThis builds okay.
Any and all help is appreaciated.Cheers
Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] meta-raspberrypi no soud output
Hello All,Does any have snd working on Raspberry Pi 2B? I have tried aplay speech_dft.wavPLAYING WAVE: 'speech_dft.wav' : Signed 16 bit Little Endian, rate 22050 Hz Monowith ear plugs or speaker no snd.Any and all help appreciated. Regards. Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] yocto Digest, Vol 61, Issue 13
Hi All, After installing linux-firmware and "rfkill unblock all".Then at the console Enabled wireless and provided the psk manually the wireless is working.I now have 2 Raspberry Pi 2B running RaspBian and 1 Raspberry Pi 2B running Yocto core-image-sato all wireless. Thanks for the help. Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613 On Friday, October 2, 2015 3:38 PM, "yocto-requ...@yoctoproject.org" <yocto-requ...@yoctoproject.org> wrote: Send yocto mailing list submissions to yocto@yoctoproject.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.yoctoproject.org/listinfo/yocto or, via email, send a message with subject or body 'help' to yocto-requ...@yoctoproject.org You can reach the person managing the list at yocto-ow...@yoctoproject.org When replying, please edit your Subject line so it is more specific than "Re: Contents of yocto digest..." Today's Topics: 1. Re: [meta-raspberrypi][PATCH] userland: Fix multiple inline issues while building with gcc 5.x (Andrei Gherzan) 2. Re: [meta-raspberrypi] compiling userland (Andrei Gherzan) 3. Re: [meta-raspberrypi] compiling userland (Andrei Gherzan) 4. Re: wpa_supplicant on Raspberry Pi 2B (Edward Vidal) -- Message: 1 Date: Fri, 2 Oct 2015 23:29:46 +0200 From: Andrei Gherzan <and...@gherzan.ro> To: Tom Doehring <tool...@googlemail.com> Cc: yocto@yoctoproject.org Subject: Re: [yocto] [meta-raspberrypi][PATCH] userland: Fix multiple inline issues while building with gcc 5.x Message-ID: <20151002212946.GA11827@resin> Content-Type: text/plain; charset=us-ascii On Sun, Sep 27, 2015 at 03:34:14PM +0200, Tom Doehring wrote: > Building userland source with gcc 5.x causes multiple issues such as: > > vcos_thread.h:186:15: warning: inline function 'vcos_thread_get_affinity' > declared but never defined > | VCOS_UNSIGNED vcos_thread_get_affinity(VCOS_THREAD_T *thread); > > The following patches fixes these issues and allows building userland on the > current > poky master branch. > > Signed-off-by: Tom Doehring <tool...@googlemail.com> > --- > .../userland/0001-Use-newer-POSIX-macro.patch | 35 >-- > .../userland/0001-fix-gcc-5.x-inlines.patch | 26 > .../userland/userland/0002-fix-musl-build.patch | 22 ++ > .../0003-fix-alloc-size-uninitialized.patch | 13 > recipes-graphics/userland/userland_git.bb | 13 +--- > 5 files changed, 70 insertions(+), 39 deletions(-) > delete mode 100644 >recipes-graphics/userland/userland/0001-Use-newer-POSIX-macro.patch > create mode 100644 >recipes-graphics/userland/userland/0001-fix-gcc-5.x-inlines.patch > create mode 100644 >recipes-graphics/userland/userland/0002-fix-musl-build.patch > create mode 100644 >recipes-graphics/userland/userland/0003-fix-alloc-size-uninitialized.patch > Tested on GCC 5.2.0 and worked fine. Merged to master. Thank you. -- Andrei Gherzan -- Message: 2 Date: Fri, 2 Oct 2015 23:33:35 +0200 From: Andrei Gherzan <and...@gherzan.ro> To: Tom Martin <t.mar...@eins-plus.de> Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org> Subject: Re: [yocto] [meta-raspberrypi] compiling userland Message-ID: <20151002213335.GA3484@resin> Content-Type: text/plain; charset=us-ascii Hi Tom, On Fri, Sep 25, 2015 at 01:19:43AM +0200, Tom Martin wrote: > i'm completly new to yocta and doing my first steps. > > plan is to build a system with a small footprint for low-latency video > wifibroadcast. > > first steps are trying to build rpi-test-image including omxplayer. but > compiling fails when compiling userland. > > last lines before the failure are. am i missing just something basic? This should be now fixed in master. Could you give it a try? -- Andrei Gherzan -- Message: 3 Date: Fri, 2 Oct 2015 23:34:56 +0200 From: Andrei Gherzan <and...@gherzan.ro> To: Andreas M?ller <schnitzelt...@googlemail.com> Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org> Subject: Re: [yocto] [meta-raspberrypi] compiling userland Message-ID: <20151002213456.GB3484@resin> Content-Type: text/plain; charset=iso-8859-1 On Sun, Sep 27, 2015 at 10:24:28PM +0200, Andreas M?ller wrote: > On Fri, Sep 25, 2015 at 6:42 AM, Khem Raj <raj.k...@gmail.com> wrote: > > Can you try the patches from > > https://github.com/kraj/meta-raspberrypi/commits/kraj/master > > > Hi Khem, > > Because of running into same issues I've tried your branch and get > errors as attached with current oe-core. > > Off-topic note: I think this layer is
[yocto] wpa_supplicant on Raspberry Pi 2B
Hello all,I am using a Wi-Pi wireless adapter.
My image has the following packages installed.
wpa-supplicant-2.4-r0.cortexa7hf_vfp_vfpv4_neon
wpa-supplicant-cli-2.4-r0.cortexa7hf_vfp_vfpv4_neon
wpa-supplicant-dev-2.4-r0.cortexa7hf_vfp_vfpv4_neon
wpa-supplicant-doc-2.4-r0.cortexa7hf_vfp_vfpv4_neon
wpa-supplicant-passphrase-2.4-r0.cortexa7hf_vfp_vfpv4_neon
Do I need any additional packages?
My wired eth0 works okay.
Which document has the most current information on setting up wireless
networking?From the information at
http://trac.gateworks.com/wiki/Yocto/Wireless
I modified my /etc/wpa_supplicant.conf as below without success.
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
update_config=1
network={
scan_ssid=1
ssid="myssid"
psk="mypsk"
proto=WPA
key_mgmt=WPA-PSK
}Below is the results I get when I run iwconfig.
iwconfig
wlan0 IEEE 802.11bgn ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
lo no wireless extensions.
eth0 no wireless extensions.
Thanks in advance. Any help is appreciated.
Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] wpa_supplicant on Raspberry Pi 2B
Hi Philip & Daniel,I modified interface diff -u interfaces.orig interfaces --- interfaces.orig 2015-09-15 04:53:28.759998719 + +++ interfaces 2015-09-15 04:54:16.98700 + @@ -8,8 +8,8 @@ iface wlan0 inet dhcp wireless_mode managed wireless_essid any - wpa-driver wext - wpa-conf /etc/wpa_supplicant.conf + wpa-driver nl80211 + wpa-conf /etc/wpa_supplicant.conf iface atml0 inet dhcp Also ran the wpa_cli stat root@raspberrypi2:/etc/network# wpa_cli stat Failed to connect to non-global ctrl_ifname: (nil) error: Success and wpa_cli -i wlan0 wpa_cli v2.4 Copyright (c) 2004-2015, Jouni Malinen <j...@w1.fi> and contributors This software may be distributed under the terms of the BSD license. See README for more details. Interactive mode Could not connect to wpa_supplicant: wlan0 - re-tryingStill no success. Thanks Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613 On Friday, October 2, 2015 9:09 AM, "yocto-requ...@yoctoproject.org" <yocto-requ...@yoctoproject.org> wrote: Send yocto mailing list submissions to yocto@yoctoproject.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.yoctoproject.org/listinfo/yocto or, via email, send a message with subject or body 'help' to yocto-requ...@yoctoproject.org You can reach the person managing the list at yocto-ow...@yoctoproject.org When replying, please edit your Subject line so it is more specific than "Re: Contents of yocto digest..." Today's Topics: 1. Release Candidate Build for yocto-2.0.rc1.rc1 now available. (Poky Build User) 2. Re: Safely cleaning 'downloads' (Laurentiu Palcu) 3. Re: [linux-yocto] [raspberryp2] Error during the build of linux kernel (Trevor Woerner) 4. wpa_supplicant on Raspberry Pi 2B (Edward Vidal) 5. Re: wpa_supplicant on Raspberry Pi 2B (Philip Balister) 6. Re: wpa_supplicant on Raspberry Pi 2B (Daniel.) -- Message: 1 Date: Fri, 02 Oct 2015 07:04:04 + From: "Poky Build User" <pokybu...@fedora21.osl.yoctoproject.org> To: yocto@yoctoproject.org Cc: ota...@ossystems.com.br Subject: [yocto] Release Candidate Build for yocto-2.0.rc1.rc1 now available. Message-ID: <20151002070407.d2b43e00...@yocto-www.yoctoproject.org> Content-Type: text/plain; charset=us-ascii A release candidate build for yocto-2.0.rc1 is now available at: http://autobuilder.yoctoproject.org/pub/releases/yocto-2.0.rc1 Please begin QA on this build as soon as possible. Build hash information: meta-intel : 84c049b9cb80b50fd32b716c2ae97e3f0d4e3cd7 meta-fsl-arm : 10471566d2868b07f8ac832b94d5e98a463826ba meta-minnow : 9c965ef5252e383843d796cd8b50c61b3034b6ae meta-qt3 : 5233565c80db869f6f539f37f26ea6662d9dc5f6 meta-fsl-ppc : 59fc0c33d2de5db65af4c09c4d28fd78fa0f7b4f poky : eac61f37e36099f74485dab398b57f3812826d17 This is an automated message from The Yocto Project Autobuilder Git: git://git.yoctoproject.org/yocto-autobuilder Email: elizabeth.flana...@intel.com -- Message: 2 Date: Fri, 2 Oct 2015 14:43:37 +0300 From: Laurentiu Palcu <laurentiu.pa...@intel.com> To: Gary Thomas <g...@mlbassoc.com> Cc: Yocto Project <yocto@yoctoproject.org> Subject: Re: [yocto] Safely cleaning 'downloads' Message-ID: <20151002114337.GG15509@lpalcu-desk> Content-Type: text/plain; charset=us-ascii Hi Garry, It's probably a little late (I'm not reading the Yocto mailing lists very often now) but sometime ago I ran out of space myself and I wrote this script that I sent out on oe-core mailing list. It did the job for me. For some reason it didn't make it in master but maybe you find it useful. I didn't test it since then though. Maybe things changed, I don't know. Give it a try if you wish. If you want to play safe, I recommend making a copy of your downloads directory (if you have space left). :) http://lists.openembedded.org/pipermail/openembedded-core/2015-June/106026.html laurentiu On Wed, Sep 30, 2015 at 06:13:39AM -0600, Gary Thomas wrote: > Over time, I tend to build in the same build tree many, many > times. This leads to some really big trees as many things are > duplicated, especially in the 'downloads' directory. > > I use local mirrors and hence my 'downloads' directory is > _mostly_ populated with symbolic links. However, there are > also expanded SCM packages, e.g. git2/xxx > > How can I safely clean up the 'downloads' directory? I already > copy any created tarballs (I use BB_GENERATE_MIRROR_TARBALLS="1" > to preclude unneeded downloads) to my mirror, but I'd like to > periodically clean out the whole directory (without disturbing > my builds of course). I've found out the hard way that just > emptying seems to be unsafe, at least for some recipes like > the [RaspberryPi]
Re: [yocto] wpa_supplicant on Raspberry Pi 2B
-0.0+git0+3161bfa479-r0.all +linux-firmware-ath6k-0.0+git0+3161bfa479-r0.all +linux-firmware-ath9k-0.0+git0+3161bfa479-r0.all +linux-firmware-atheros-license-0.0+git0+3161bfa479-r0.all +linux-firmware-bcm4329-0.0+git0+3161bfa479-r0.all +linux-firmware-bcm4330-0.0+git0+3161bfa479-r0.all +linux-firmware-bcm4334-0.0+git0+3161bfa479-r0.all +linux-firmware-broadcom-license-0.0+git0+3161bfa479-r0.all +linux-firmware-dev-0.0+git0+3161bfa479-r0.all +linux-firmware-iwlwifi-135-6-0.0+git0+3161bfa479-r0.all +linux-firmware-iwlwifi-3160-7-0.0+git0+3161bfa479-r0.all +linux-firmware-iwlwifi-3160-8-0.0+git0+3161bfa479-r0.all +linux-firmware-iwlwifi-3160-9-0.0+git0+3161bfa479-r0.all +linux-firmware-iwlwifi-6000-4-0.0+git0+3161bfa479-r0.all +linux-firmware-iwlwifi-6000g2a-5-0.0+git0+3161bfa479-r0.all +linux-firmware-iwlwifi-6000g2a-6-0.0+git0+3161bfa479-r0.all +linux-firmware-iwlwifi-6000g2b-5-0.0+git0+3161bfa479-r0.all +linux-firmware-iwlwifi-6000g2b-6-0.0+git0+3161bfa479-r0.all +linux-firmware-iwlwifi-6050-4-0.0+git0+3161bfa479-r0.all +linux-firmware-iwlwifi-6050-5-0.0+git0+3161bfa479-r0.all +linux-firmware-iwlwifi-7260-7-0.0+git0+3161bfa479-r0.all +linux-firmware-iwlwifi-7260-8-0.0+git0+3161bfa479-r0.all +linux-firmware-iwlwifi-7260-9-0.0+git0+3161bfa479-r0.all +linux-firmware-iwlwifi-7265-8-0.0+git0+3161bfa479-r0.all +linux-firmware-iwlwifi-7265-9-0.0+git0+3161bfa479-r0.all +linux-firmware-iwlwifi-license-0.0+git0+3161bfa479-r0.all +linux-firmware-license-0.0+git0+3161bfa479-r0.all +linux-firmware-marvell-license-0.0+git0+3161bfa479-r0.all +linux-firmware-radeon-0.0+git0+3161bfa479-r0.all +linux-firmware-radeon-license-0.0+git0+3161bfa479-r0.all +linux-firmware-ralink-0.0+git0+3161bfa479-r0.all +linux-firmware-ralink-license-0.0+git0+3161bfa479-r0.all +linux-firmware-rtl-license-0.0+git0+3161bfa479-r0.all +linux-firmware-rtl8192ce-0.0+git0+3161bfa479-r0.all +linux-firmware-rtl8192cu-0.0+git0+3161bfa479-r0.all +linux-firmware-rtl8192su-0.0+git0+3161bfa479-r0.all +linux-firmware-sd8686-0.0+git0+3161bfa479-r0.all +linux-firmware-sd8787-0.0+git0+3161bfa479-r0.all +linux-firmware-sd8797-0.0+git0+3161bfa479-r0.all +linux-firmware-ti-connectivity-license-0.0+git0+3161bfa479-r0.all +linux-firmware-vt6656-0.0+git0+3161bfa479-r0.all +linux-firmware-vt6656-license-0.0+git0+3161bfa479-r0.all +linux-firmware-wl12xx-0.0+git0+3161bfa479-r0.all +linux-firmware-wl18xx-0.0+git0+3161bfa479-r0.all Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberry] HDL tools for Raspberry PI 2 B
Hi all, I need recipes for the GTKWAVE, Iverilog, and (Yosys, arachne-pnr, and icebox). The missing packages are compiled on target P2 B. Plus the recipes that I already have working below. These were built on a custom image for the Raspberry Pi 2 B with Yocto. The following are the recipes that I have created # meta/recipes-devtools/python/PyPubSub_3.1.3.bb # meta/recipes-devtools/python/intelhex_1.5.bb # meta/recipes-devtools/python/python-bitstring_3.1.3.bb # meta/recipes-devtools/python/pyusb_1.0.0a3.bb # meta/recipes-devtools/python/rhea_0.1.0.bb # meta/recipes-devtools/python/xsconnect_0.1.3.bb # meta/recipes-devtools/python/xstools_0.1.30.bb Most are the depends are for XSTOOLS. This supports the XuLA2-LX9 & XuLA2-LX25 with StickIt-MB. http://www.xess.com/ This would be a great addition to the Yocto tools. What are the steps to add recipes to the Yocto Project? I am using a Fido branch of Yocto that fetch on 07/20/15.The image is created in 4hrs. on 6 core AMD running Ubuntu 12.04. I just completed building the tools (Yosys, arachne-pnr, and icebox) for the Lattice ICE-40. The complete image fits on a 4GB SD card. With the board that XESS is making this will be a standalone HDL development system with GTKWave, XSTOOLs, MyDHDl, Iverilog, arachne-pnr(place and route), Yosys (Yosys is a framework for Verilog RTL synthesis), icebox(this will not be needed since XESS is going to push the bit file with GPIO instead of USB), and MyHDL. These fit on a 4GB SD card. With the board that XESS is making this will be a standalone HDL development system with GTKWave, XSTOOLs, MyDHDl, Iverilog, arachne-pnr(place and route), Yosys (Yosys is a framework for Verilog RTL synthesis), icebox(this will not be needed since XESS is going to push the bit file with GPIO instead of USB), and MyHDL. Dave Vandenbout completed the layout of the ICE-40 board a few days ago. Lattice iCE40-HX8K FPGA in 256-pin BGA. 32 MByte SDRAM (16M x 16). Serial configuration flash (at least 2 Mbit). Three Grove connectors. Two PMOD connectors. One 20x2 header with 3.3V, ground and 18 FPGA I/Os. Two SATA headers (for differential signals; don't know if they would work with SATA HDDs.) DIP switch with four SPST switches. Two momentary pushbuttons. Four LEDs. 32 KByte HAT EEPROM. 40-pin RPi GPIO header. Chris Felton provided MyHDL code to take python generates a verilog or VHDL and the synthesis, place and route and creates a bin file. Below are the bench marks for Pi 2B and 2 systems running Ubuntu 12.04. Yocto Pi 2B real 0m20.943s user 0m12.210s sys 0m0.500s Ubuntu 2 core real 0m5.310s user 0m1.865s sys 0m0.197s Ubuntu 6 core real 0m3.956s user 0m1.093s sys 0m0.120s These were built on a custom image for the Raspberry Pi 2 B with Yocto. These tools would apply to other boards such a Zynq 7000. I am also running openCV with 2 C920 cameras. If you have any questions feel free to contact me. Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi] rootfs fails
Hello All,Thanks after doing "bitbake core-image-sato -c cleansstate"followed by "bitbake core-image-sato" was able to get the image.During the core-image-sato with no IMAGE_INSTALL_append = I did see a few warnings that I have not seen before (see below). WARNING: QA Issue: gstreamer1.0-plugins-bad: configure was passed unrecognised options: --with-egl-window-system [unknown-configure-option] WARNING: QA Issue: /home/vidal/wkg/yocto/RaspberryPi2/poky/build/ tmp/work/cortexa7hf-vfp-vfpv4-neon-poky-linux-gnueabi/perl/ 5.22.0-r0/packages-split/perl-ptest/usr/lib/perl/ptest/hints/ epix.sh is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated] Another strange happening is python is missing items to do "python setup.py install" on package both repo072015 & repo091015 are using python 2.7.9-r1 -python-distribute-0.6.32 is missing and 2 new RPMs are installed +python-pip-7.1.0 is now being using instead of python-pip-1.5.6 +python-setuptools-18.2 is now being used.Could this be related to rootfs failing at times?Regards, Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi] rootfs fails
Hello All, My rootfs is failing when adding liba52, libmad, libav. x264, and libav. This is for a raspberrypi2. I updated the meta data on 09/10/15. meta-yocto-bsp = "fido:d4585fa23d56a58c583ee33db067a23177a936b1" meta-raspberrypi = "fido:17dad9328b100beda1cf870c9075e509b5cbfa90" meta-oe meta-multimedia meta-python meta-gnome = "fido:d4585fa23d56a58c583ee33db067a23177a936b1" meta-browser = "fido:ca96f4326345dcd779fc539877a04f069f431749" This is the IMAGE_INSTALL_append in my local.conf IMAGE_INSTALL_append = " intelhex python-bitstring pyusb PyPubSub git \ chkconfig tar v4l-utils tree python-imaging python-pip \ jasper gsl hexedit man openjpeg tcl tk liba52 libmad libav x264 libav" This errors below occurred when I added the following liba52 libmad libav x264 libav to my IMAGE_INSTALL_append WARNING: QA Issue: ELF binary '/home/vidal/wkg/yocto/RaspberryPi2/poky/build/tmp/work/cortexa7hf-vfp-vfpv4-neon-poky-linux-gnueabi/x264/r2491+gitAUTOINC+c8a773ebfc-r0/packages-split/x264/usr/lib/libx264.so.144' has relocations in .text [textrel] WARNING: QA Issue: ELF binary '/home/vidal/wkg/yocto/RaspberryPi2/poky/build/tmp/work/cortexa7hf-vfp-vfpv4-neon-poky-linux-gnueabi/libav/9.18-r0/packages-split/libavcodec/usr/lib/libavcodec.so.54.35.0' has relocations in .text [textrel] ERROR: Error: The image creation script '/home/vidal/wkg/yocto/RaspberryPi2/poky/build/tmp/work/raspberrypi2-poky-linux-gnueabi/core-image-sato/1.0-r0/temp/create_image.rpi-sdimg' returned 2: expr: non-integer argument WARNING: exit code 2 from a shell command. ERROR: Function failed: do_rootfs ERROR: Logfile of failure stored in: /home/vidal/wkg/yocto/RaspberryPi2/poky/build/tmp/work/raspberrypi2-poky-linux-gnueabi/core-image-sato/1.0-r0/temp/log.do_rootfs.1142 In the ~/wkg/yocto/RaspberryPi2/poky/build/tmp/work/cortexa7hf-vfp-vfpv4-neon-poky-linux-gnueabi I can see that the deploy-rpms were generated in each folder liba52 libmad libav x264 libav. The file core-image-sato-raspberrypi2-20150911214448.rootfs.tar.bz2 gets generated which can see in the /home/vidal/wkg/yocto/RaspberryPi2/poky/build/tmp/work/raspberrypi2-poky-linux-gnueabi/core-image-sato/1.0-r0/temp/log.do_rootfs.1142These and other packages were added with the meta-data I had download on 07/20/15. I am using the fido branch. Thanks in advance for your help in solving this problems. Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] missing certificates
Hello All,In July 2015, several messages were posted with regard to missing certificatesfrom Gary Thomas, Christopher Larson, and Aníbal Limón.I am working with a Raspberry Pi 2 B and having a problem with fetching a bitbucket repository using HG (Mercurial) which is certificate issue. Is this a python or O/S issue. I have been checking the site mentioned by Aníbal Limón https://www.python.org/dev/peps/pep-0476/ I noticed that very bottom there is a link https://hg.python.org/peps/file/tip/pep-0476.txt date Wed, 02 Sep 2015 15:00:42 -0400 (20 hours ago).After reading this several times I am still not sure how to proceed.This problem occurs when I am trying to install "yosys" which during the build process tries "hg clone https://bitbucket.org/alanmi/abc abc" How best to get this working on my core-image-sato.Thanks in advance. Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] kernel src included in core-image
Hello All,I am working on Raspberry Pi 2 B and need the kernel src included.This is what I currently including on core-image-sato build. kernel-dev xterm git \ jasper gsl gsl-dev python-netserver python-pygtk python-pygtk-dev \ python-numpy liba52 liba52-dev libmad libmad-dev libmad-staticdev \ chkconfig v4l-utils python-imaging parted python-distribute \ python-pyrex python-pexpect gperf tree libav libav-dev \ x264 x264-dev libav libav-dev opencv opencv-samples cmake \ opencv-apps python-opencv tcl tk rpi-gpio python-myhdl python-bitstring \ PyPubSub tar intelhex pyusb argparse pv openjpeg libftdiI am working on a fido buildmeta-yocto-bsp = fido:0f8d89ce66cfffccc9911d6c61470a585173b79d meta-raspberrypi = fido:7457bf182c8fd550ec877ecd786a3edd16e65495 meta-oe = fido:0f8d89ce66cfffccc9911d6c61470a585173b79d I see many rpms in this area poky/build/tmp/work/raspberrypi2-poky-linux-gnueabi/linux-raspberrypi/3.18.11+gitd64fa8121fca9883d6fb14ca06d2abf66496195e-r0/deploy-rpms/raspberrypi2The installed rpm with kernel is 1381. Thanks in advance. Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] python-matplotlib core-image-sato.
Hello All,I added meta-python from meta-openembedded to my poky tree.python-matplotlib was fetched and installed on my core-image-sato.Build Configuration: BB_VERSION = 1.27.1 BUILD_SYS = x86_64-linux NATIVELSBSTRING = Ubuntu-12.04 TARGET_SYS = arm-poky-linux-gnueabi MACHINE = raspberrypi2 DISTRO = poky DISTRO_VERSION = 1.8+snapshot-20150808 TUNE_FEATURES = arm armv7a vfp thumb neon callconvention-hard vfpv4 cortexa7 TARGET_FPU = vfp-vfpv4-neon meta meta-yocto meta-yocto-bsp = fido:0f8d89ce66cfffccc9911d6c61470a585173b79d meta-raspberrypi = fido:7457bf182c8fd550ec877ecd786a3edd16e65495 meta-oe meta-python = fido:0f8d89ce66cfffccc9911d6c61470a585173b79d NOTE: Preparing RunQueue NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks NOTE: Tasks Summary: Attempted 6470 tasks of which 6432 didn't need to be rerun and all succeeded. After booting I added some examples that I had from raspbian build g...@github.com:develone/raspberrypi2_yocto.git When I execute I do not get any errors but no plot appears. Has anyone been able to get python-matplotlib working?Thanks in advance. Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Compile with ADT and recipe fails builds on target.
Hello All,
Trying to use ADT to compile a package. The package compiles and installs on
the target core-image-sato for the Raspberry Pi 2 B. Also trying to create a
recipe. see
recipe_gtkwave/gtkwave/gtkwave_3.6.66.bb at
https://github.com/develone/raspberrypi2_yocto.git
The recipe downloads the source code, unpacks and runs do_configure, but fails
at
ERROR: Function failed: do_qa_configure.
1.) cd wkg/yocto/RaspberryPi2/poky/
2.) . oe-init-build-env
3.) bitbale core-image-sato -c populate_sdk
4.) sudo
tmp/deploy/sdk/poky-glibc-x86_64-core-image-sato-cortexa7hf-vfp-vfpv4-neon-toolchain-1.8+snapshot.sh
5.) cd ~/
6.) tar xfz wkg/yocto/downloads/gtkwave-3.3.66.tar.gz
7.) cd gtkwave-3.3.66/
8.) source
/opt/poky/1.8+snapshot/environment-setup-cortexa7hf-vfp-vfpv4-neon-poky-linux-gnueabi
9.a) ./configure ${CONFIGURE_FLAGS}
checking for Tcl configuration... configure: error: Can't find Tcl
configuration definitions. Use --with-tcl to specify a directory containing
tclConfig.sh
Should the ADT be able to find theses since they are located at
ls
/opt/poky/1.8+snapshot/sysroots/cortexa7hf-vfp-vfpv4-neon-poky-linux-gnueabi/usr/lib/tclConfig.sh
ls
/opt/poky/1.8+snapshot/sysroots/cortexa7hf-vfp-vfpv4-neon-poky-linux-gnueabi/usr/lib/tkConfig.sh
without have to set the path
9.b) ./configure ${CONFIGURE_FLAGS}
--with-tcl=/home/vidal/wkg/yocto/RaspberryPi2/poky/build/tmp/sysroots/raspberrypi2/usr/lib
--with-tk=/home/vidal/wkg/yocto/RaspberryPi2/poky/build/tmp/sysroots/raspberrypi2/usr/lib
This goes further with the following warning
config.status: executing depfiles commands
configure: WARNING: unrecognized options: --with-libtool-sysroot
Thanks in advance. Edward Vidal Jr.
e-mail devel...@sbcglobal.net
915-595-1613--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] gtkwave recipe fails in do_configure
Hello All,
I am trying to add gtkwave with a bitbake recipe
gtkwave_3.6.66.bb found at https://github.com/develone/raspberrypi2_yocto.git
in the folder
receipe_gtkwave.
I need to add the following trying to get do_configure working.
EXTRA_OECONF =
--with-tcl=/home/vidal/wkg/yocto/RaspberryPi2/poky/build/tmp/sysroots/raspberrypi2/usr/lib
--with-tk=/home/vidal/wkg/yocto/RaspberryPi2/poky/build/tmp/sysroots/raspberrypi2/usr/lib
I tried replacing /home/vidal/wkg/yocto/RaspberryPi2/poky/build with
${BUILDDIR}.
I still get the error
| checking for Tcl configuration... configure: error:
/tmp/sysroots/raspberrypi2/usr/lib directory doesn't contain tclConfig.sh
I get further with the full path as above.
Which leads to a new error.
ERROR: This autoconf log indicates errors, it looked at host include and/or
library paths while determining system capabilities.
Rerun configure task after fixing this. The path was
'/home/vidal/wkg/yocto/RaspberryPi2/poky/build/tmp/work/cortexa7hf-vfp-vfpv4-neon-poky-linux-gnueabi/gtkwave/3.6.66-r0/build'
ERROR: Function failed: do_qa_configure
ERROR: Logfile of failure stored in:
/home/vidal/wkg/yocto/RaspberryPi2/poky/build/tmp/work/cortexa7hf-vfp-vfpv4-neon-poky-linux-gnueabi/gtkwave/3.6.66-r0/temp/log.do_configure.22672
ERROR: Task 5
(/home/vidal/wkg/yocto/RaspberryPi2/poky/meta/recipes-devtools/gtkwave/gtkwave_3.6.66.bb,
do_configure) failed with exit code '1'
I tried autotools-brokensep instead of autotools same results.
Thanks in advance. Edward Vidal Jr.
e-mail devel...@sbcglobal.net
915-595-1613
log.do_configure.22672
Description: Binary data
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Recipes not in poky gtkwave fails on configure depends
Hello All All of my work is at https://github.com/develone/raspberrypi2_yocto.git. see the gtkwave_3.6.66.bb I am working on a few tools for FPGA Development. This include MyHDL, GTKWAVE, Iverilog, and XSTOOLs. These tools (MyHDL) lets you create either verilog or VHDL files. MyHDL also provides Simulation Co-Simulation of HDL. MyHDL is Python package, I have already created a recipe python-myhdl_1.0.0.bb that generated an RPM which I installed on core-image-sato. I want to thank Gary Thomas and Ross Burton for the help on the core-image-sato for the RaspBerry Pi 2 B. and getting the python-myhdl_1.0.0.bb working. In addition, GTKWAVE provides a Graphical visual of the Signals used in the Simulation. I installed GTKWAVE from source on a core-image-sato with (./configure, make and make install). The core-image-sato had the following apps kernel-dev xterm git \ jasper gsl gsl-dev python-netserver python-pygtk python-pygtk-dev \ python-numpy liba52 liba52-dev libmad libmad-dev libmad-staticdev \ chkconfig v4l-utils python-imaging parted python-distribute \ python-pyrex python-pexpect gperf tree libav libav-dev \ x264 x264-dev libav libav-dev opencv opencv-samples cmake \ opencv-apps python-opencv tcl tk I have a recipe gtkwave_3.6.66.bb that fectchs gtkwave source from sourceforge but fails on With the following error. checking for Tcl configuration... configure: error: Can't find Tcl configuration definitions. Use --with-tcl to specify a directory containing tclConfig.sh Configure failed. The contents of all config.log files follows to aid debugging ERROR: oe_runconf failed XSTOOLs provides the capability to transfer to XulA2 the bit file and to communicate with the FPGA during the run-time. Iverilog provides the Co-Simulated to work with MyHDL. I have installed this from source on the above core-image-sato the has several apps. I believe that this would be a great addition to the Yocto effort. Let me what needs to be done to get this apps into the Yocto framework. Thanks in advance. Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] (no subject)
Hello All,Thanks to Ross Burton see the files https://github.com/develone/raspberrypi2_yocto.git in recipe_myhdl folder. Now have an rpm to install myhdl on a yocto build. let me know if you have any questions. Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] recipe md5sum and sha256sum changing
Hello All, I used the following to create a recipe. recipetool create -o /home/vidal/wkg/yocto/myhdl_recipe/poky/meta/recipes-devtools/python/python-myhdl_1.0.0.bb https://github.com/jandecaluwe/myhdl.git This provided the following: LICENSE = CLOSED LIC_FILES_CHKSUM = SRC_URI = https://github.com/jandecaluwe/myhdl.git; SRC_URI[md5sum] = 6f56a9bcbd03a9c8036f87f32f9adc47 SRC_URI[sha256sum] = 7766c49947c6574c8fb35d0dfcd795ada1e4e457ab5b15499d7000909b8e46e9 When I run bitbake python-mydhl the md5sum and sha256sum change everytime I run the command. WARNING: Renaming /home/vidal/wkg/yocto/myhdl_recipe/poky/build/downloads/myhdl.git to /home/vidal/wkg/yocto/myhdl_recipe/poky/build/downloads/myhdl.git_bad-checksum_a4b1db68cde5b996661caa6abce2cb45 ERROR: Fetcher failure for URL: 'https://github.com/jandecaluwe/myhdl.git'. Checksum mismatch! File: '/home/vidal/wkg/yocto/myhdl_recipe/poky/build/downloads/myhdl.git' has md5 checksum a4b1db68cde5b996661caa6abce2cb45 when 6f56a9bcbd03a9c8036f87f32f9adc47 was expected File: '/home/vidal/wkg/yocto/myhdl_recipe/poky/build/downloads/myhdl.git' has sha256 checksum dc35dc44e0a480097eb1c4dd3df739396e96c8d7648bd9b9d347d02d34bbcd01 when 7766c49947c6574c8fb35d0dfcd795ada1e4e457ab5b15499d7000909b8e46e9 was expected If this change is expected (e.g. you have upgraded to a new version without updating the checksums) then you can use these lines within the recipe: SRC_URI[md5sum] = a4b1db68cde5b996661caa6abce2cb45 SRC_URI[sha256sum] = dc35dc44e0a480097eb1c4dd3df739396e96c8d7648bd9b9d347d02d34bbcd01 Otherwise you should retry the download and/or check with upstream to determine if the file has become corrupted or otherwise unexpectedly modified. ERROR: Function failed: Fetcher failure for URL: 'https://github.com/jandecaluwe/myhdl.git'. Unable to fetch URL from any source. ERROR: Logfile of failure stored in: /home/vidal/wkg/yocto/myhdl_recipe/poky/build/tmp/work/cortexa7hf-vfp-vfpv4-neon-poky-linux-gnueabi/python-myhdl/1.0.0-r0/temp/log.do_fetch.6277 ERROR: Task 4 (/home/vidal/wkg/yocto/myhdl_recipe/poky/meta/recipes-devtools/python/python-myhdl_1.0.0.bb, do_fetch) failed with exit code '1' NOTE: Tasks Summary: Attempted 421 tasks of which 413 didn't need to be rerun and 1 failed. Waiting for 0 running tasks to finish: Summary: 1 task failed: /home/vidal/wkg/yocto/myhdl_recipe/poky/meta/recipes-devtools/python/python-myhdl_1.0.0.bb, do_fetch Summary: There were 3 WARNING messages shown. Summary: There were 2 ERROR messages shown, returning a non-zero exit code. Thanks in advance Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] ADT and ast issue.
Hello All, I am trying to use the ADT to build myhdl a python library.To obtain myhdl I use git clone https://github.com/jandecaluwe/myhdl.git I first setup the ADT. source /opt/poky/1.8+snapshot/environment-setup-cortexa7hf-vfp-vfpv4-neon-poky-linux-gnueabi The working python is appears to be the one I created with the bitbake meta-toolchain. vidal@ws009:~/yocto_adt/build_myhdl/myhdl$ python Python 2.7.9 (default, Jul 27 2015, 06:41:40) [GCC 4.9.3] on linux2 Type help, copyright, credits or license for more information. I see ast in the path of the ADT. find /opt/poky/ -name ast* /opt/poky/1.8+snapshot/sysroots/x86_64-pokysdk-linux/usr/lib/python2.7/compiler/ast.pyc /opt/poky/1.8+snapshot/sysroots/x86_64-pokysdk-linux/usr/lib/python2.7/compiler/ast.py This is the error that I am seeing. vidal@ws009:~/yocto_adt/build_myhdl/myhdl$ python setup.py install Traceback (most recent call last): File setup.py, line 3, in modulepython setup.py install import ast ImportError: No module named ast When I use sudo to execute the command sudo python setup.py install It appears to be using the system python not the ADT python. python Python 2.7.3 (default, Sep 26 2013, 20:03:06) [GCC 4.6.3] on linux2 Type help, copyright, credits or license for more information. import ast This works okay without the using the ADT. Thanks in advance. Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] fido LICENSE error opencv
Hello All, I was able to fix the license error in fido by adding commercial_x264 to LICENSE_FLAGS_WHITELIST variable. LICENSE_FLAGS_WHITELIST = commercial_libmad commercial_mpeg2dec commercial_libav commercial_ffmpeg commercial_x264 Opencv was installed on the Raspberry core-image-sato with the following changes git diff meta/recipes-sato/images/core-image-sato.bb diff --git a/meta/recipes-sato/images/core-image-sato.bb b/meta/recipes-sato/ima index e3246d2..f4b2286 100644 --- a/meta/recipes-sato/images/core-image-sato.bb +++ b/meta/recipes-sato/images/core-image-sato.bb @@ -8,4 +8,9 @@ LICENSE = MIT inherit core-image -IMAGE_INSTALL += packagegroup-core-x11-sato-games +IMAGE_INSTALL += packagegroup-core-x11-sato-games kernel-dev xterm git \ + jasper gsl gsl-dev python-netserver python-pygtk python-pygtk-dev \ + python-numpy liba52 liba52-dev libmad libmad-dev libmad-staticdev \ + chkconfig v4l-utils python-imaging parted python-distribute \ + python-pyrex python-pexpect gperf tree libav libav-dev \ + x264 x264-dev libav libav-dev opencv opencv-samples cmake What is the preferred method of creating an image with additional software installed? Thanks for all the help. Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] ADT python build
Hello All,
On Raspberry Pi target and earlier version of myhdl was getting a
ImportError: No module named py_compile (see py_compile error attached)
Trying to install a python module using the ADT enviornment.
name=myhdl,
version=version,
description=Python as a Hardware Description Language,
long_description=See home page.,
author=Jan Decaluwe,
author_email=j...@jandecaluwe.com,
url=http://www.myhdl.org;
The following are the steps that result in an error using the ADT and Raspberry
Pi target.
mkdir build_myhdl
cd build_myhdl/
git clone https://github.com/jandecaluwe/myhdl.git
cd myhdl/
source
/opt/poky/1.8+snapshot/environment-setup-cortexa7hf-vfp-vfpv4-neon-poky-linux-gnueabi
python setup.py install
which python
/opt/poky/1.8+snapshot/sysroots/x86_64-pokysdk-linux/usr/bin/python
python setup.py install
Traceback (most recent call last):
File setup.py, line 3, in module
import ast
ImportError: No module named ast
Thanks in advance. Edward Vidal Jr.
e-mail devel...@sbcglobal.net
915-595-1613python setup.py install
starts out okay.
writing manifest file 'myhdl.egg-info/SOURCES.txt'
installing library code to build/bdist.linux-armv7l/egg
running install_lib
running build_py
creating build/lib
creating build/lib/myhdl
copying myhdl/_Signal.py - build/lib/myhdl
copying myhdl/_util.py - build/lib/myhdl
copying myhdl/_Cosimulation.py - build/lib/myhdl
copying myhdl/_compat.py - build/lib/myhdl
copying myhdl/_Waiter.py - build/lib/myhdl
copying myhdl/__init__.py - build/lib/myhdl
copying myhdl/_tristate.py - build/lib/myhdl
copying myhdl/_bin.py - build/lib/myhdl
.
.
.
many more lines
.
.
.
copying build/lib/myhdl/_resolverefs.py - build/bdist.linux-armv7l/egg/myhdl
copying build/lib/myhdl/_resize.py - build/bdist.linux-armv7l/egg/myhdl
copying build/lib/myhdl/_ShadowSignal.py - build/bdist.linux-armv7l/egg/myhdl
copying build/lib/myhdl/_simulator.py - build/bdist.linux-armv7l/egg/myhdl
Traceback (most recent call last):
File setup.py, line 60, in module
'Programming Language :: Python :: 3.4',
File /usr/lib/python2.7/distutils/core.py, line 151, in setup
dist.run_commands()
File /usr/lib/python2.7/distutils/dist.py, line 953, in run_commands
self.run_command(cmd)
File /usr/lib/python2.7/distutils/dist.py, line 972, in run_command
cmd_obj.run()
File
/usr/lib/python2.7/site-packages/distribute-0.6.32-py2.7.egg/setuptools/command/install.py,
line 73, in run
self.do_egg_install()
File
/usr/lib/python2.7/site-packages/distribute-0.6.32-py2.7.egg/setuptools/command/install.py,
line 93, in do_egg_install
self.run_command('bdist_egg')
File /usr/lib/python2.7/distutils/cmd.py, line 326, in run_command
self.distribution.run_command(command)
File /usr/lib/python2.7/distutils/dist.py, line 972, in run_command
cmd_obj.run()
File
/usr/lib/python2.7/site-packages/distribute-0.6.32-py2.7.egg/setuptools/command/bdist_egg.py,
line 179, in run
cmd = self.call_command('install_lib', warn_dir=0)
File
/usr/lib/python2.7/site-packages/distribute-0.6.32-py2.7.egg/setuptools/command/bdist_egg.py,
line 166, in call_command
self.run_command(cmdname)
File /usr/lib/python2.7/distutils/cmd.py, line 326, in run_command
self.distribution.run_command(command)
File /usr/lib/python2.7/distutils/dist.py, line 972, in run_command
cmd_obj.run()
File
/usr/lib/python2.7/site-packages/distribute-0.6.32-py2.7.egg/setuptools/command/install_lib.py,
line 24, in run
self.byte_compile(outfiles)
File /usr/lib/python2.7/distutils/command/install_lib.py, line 138, in
byte_compile
dry_run=self.dry_run)
File /usr/lib/python2.7/distutils/util.py, line 437, in byte_compile
from py_compile import compile
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] fido LICENSE error opencv
Hello All,I got openCV to detect 2 C920 cameras using a python api.I started a repository https://github.com/develone/raspberrypi2_yocto I am currently using fido branch.The things that I have been able to createbitbake rpi-basic-image bitbake core-image-sato with addition additional libs and applications see the file wkg_conf_files/core-image-sato.bbbitbake meta-toolchainIf you have any questions feel free to contract me. Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613 On Monday, July 27, 2015 9:53 AM, Victor Rodriguez vm.ro...@gmail.com wrote: On Mon, Jul 27, 2015 at 7:34 AM, Edward Vidal devel...@sbcglobal.net wrote: Hello All, I was able to fix the license error in fido by adding commercial_x264 to LICENSE_FLAGS_WHITELIST variable. LICENSE_FLAGS_WHITELIST = commercial_libmad commercial_mpeg2dec commercial_libav commercial_ffmpeg commercial_x264 Opencv was installed on the Raspberry core-image-sato with the following changes git diff meta/recipes-sato/images/core-image-sato.bb diff --git a/meta/recipes-sato/images/core-image-sato.bb b/meta/recipes-sato/ima index e3246d2..f4b2286 100644 --- a/meta/recipes-sato/images/core-image-sato.bb +++ b/meta/recipes-sato/images/core-image-sato.bb @@ -8,4 +8,9 @@ LICENSE = MIT inherit core-image -IMAGE_INSTALL += packagegroup-core-x11-sato-games +IMAGE_INSTALL += packagegroup-core-x11-sato-games kernel-dev xterm git \ + jasper gsl gsl-dev python-netserver python-pygtk python-pygtk-dev \ + python-numpy liba52 liba52-dev libmad libmad-dev libmad-staticdev \ + chkconfig v4l-utils python-imaging parted python-distribute \ + python-pyrex python-pexpect gperf tree libav libav-dev \ + x264 x264-dev libav libav-dev opencv opencv-samples cmake What is the preferred method of creating an image with additional software installed? Thanks for all the help. Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto Hi I had the same problem with opencv in yocto . There is a trend about this in mailign list: https://www.mail-archive.com/yocto@yoctoproject.org/msg24746.html I am pushing to do a change in opencv receipt Hope it helps -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] fido LICENSE error opencv
Hello all When I previously created opencv in dylan dora builds I used the following in my local.conf LICENSE_FLAGS_WHITELIST = commercial_libmad commercial_mpeg2dec commercial_libav commercial_ffmpeg With fido the following error is occurring when I add opencv opencv-samples IMAGE_INSTALL items. ERROR: Nothing PROVIDES 'x264' (but /home/vidal/wkg/yocto/RaspberryPi2/poky/meta/recipes-multimedia/libav/libav_9.18.bb DEPENDS on or otherwise requires it) ERROR: x264 was skipped: because it has a restricted license not whitelisted in LICENSE_FLAGS_WHITELIST NOTE: Runtime target 'opencv-samples' is unbuildable, removing... Missing or unbuildable dependency chain was: ['opencv-samples', 'opencv', 'libav', 'x264'] ERROR: Required build target 'core-image-sato' has no buildable providers. Missing or unbuildable dependency chain was: ['core-image-sato', 'opencv-samples', 'opencv', 'libav', 'x264'] This is the Build Configuration: BB_VERSION = 1.27.1 BUILD_SYS = x86_64-linux NATIVELSBSTRING = Ubuntu-12.04 TARGET_SYS = arm-poky-linux-gnueabi MACHINE = raspberrypi2 DISTRO = poky DISTRO_VERSION = 1.8+snapshot-20150725 TUNE_FEATURES = arm armv7a vfp thumb neon callconvention-hard vfpv4 cortexa7 TARGET_FPU = vfp-vfpv4-neon meta meta-yocto meta-yocto-bsp = fido:0f8d89ce66cfffccc9911d6c61470a585173b79d meta-raspberrypi = fido:7457bf182c8fd550ec877ecd786a3edd16e65495 meta-oe = fido:0f8d89ce66cfffccc9911d6c61470a585173b79d Is there something else that I must provide for fido? Thanks in advance. Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] raspberry Pi core-image-sato
Hi Gary,
Thanks for the help.
I executed the command
bitbake userland -c cleansstate
This completed successful.
5: userland-git-r5 do_compile (pid 17332)
Did not know how to apply the patch.
I tried in poky folder
patch --dry-run ~/Downloads/attachment-0001.bin
patch ~/Downloads/attachment-0001.bin
git apply --stat ~/Downloads/attachment-0001.bin
Could not get the patch so I did manually.
git diff
diff --git a/meta-yocto/conf/distro/poky.conf b/meta-yocto/conf/distro/poky.conf
index e3d3c78..238b553 100644
--- a/meta-yocto/conf/distro/poky.conf
+++ b/meta-yocto/conf/distro/poky.conf
@@ -72,6 +72,7 @@ CONNECTIVITY_CHECK_URIS ?= \
SANITY_TESTED_DISTROS ?= \
poky-1.7 \n \
poky-1.8 \n \
+ Ubuntu-12.04 \n \
Ubuntu-14.04 \n \
Ubuntu-14.10 \n \
Ubuntu-15.04 \n \
diff --git a/meta/recipes-graphics/libepoxy/libepoxy_git.bb b/meta/recipes-graph
index 9816257..0330a7b 100644
--- a/meta/recipes-graphics/libepoxy/libepoxy_git.bb
+++ b/meta/recipes-graphics/libepoxy/libepoxy_git.bb
@@ -16,7 +16,7 @@ PV = 1.2+git${SRCPV}
S = ${WORKDIR}/git
-inherit autotools pkgconfig
+inherit autotools pkgconfig python3native
DEPENDS = util-macros virtual/egl
bitbake core-image-sato failed with same error.
| WARNING: exit code 1 from a shell command.
| ERROR: oe_runconf failed
| ERROR: Function failed: do_configure (log file is located at
/home/vidal/wkg/yocto/RaspberryPi2/poky/build/tmp/work/cortexa7hf-vfp-vfpv4-neon-poky-linux-gnueabi/libepoxy/1.2+gitAUTOINC+20062c25e7-r0/temp/log.do_configure.27821)
ERROR: Task 4597
(/home/vidal/wkg/yocto/RaspberryPi2/poky/meta/recipes-graphics/libepoxy/libepoxy_git.bb,
do_configure) failed with exit code '1'
Waiting for 1 running tasks to finish:
These are the layers that I am using.
meta-yocto-bsp = fido:0f8d89ce66cfffccc9911d6c61470a585173b79d
meta-raspberrypi = fido:7457bf182c8fd550ec877ecd786a3edd16e65495
Do these need to upated I got them on the 20th of this month.
Thanks appreciate all the help. Edward Vidal Jr.
e-mail devel...@sbcglobal.net
915-595-1613
On Wednesday, July 22, 2015 6:24 PM, yocto-requ...@yoctoproject.org
yocto-requ...@yoctoproject.org wrote:
Send yocto mailing list submissions to
yocto@yoctoproject.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.yoctoproject.org/listinfo/yocto
or, via email, send a message with subject or body 'help' to
yocto-requ...@yoctoproject.org
You can reach the person managing the list at
yocto-ow...@yoctoproject.org
When replying, please edit your Subject line so it is more specific
than Re: Contents of yocto digest...
Today's Topics:
1. [meta-raspberrypi][PATCH 1/1] packagegroup-rpi-test: Add
pi-blaster (Petter Mab?cker)
2. [meta-raspberrypi][PATCH 0/1] packagegroup-rpi-test: Add
pi-blaster (Petter Mab?cker)
3. VMDK image not booting (Daniel Kuhne)
4. Re: [oe] Bug in Open CV receipt (Otavio Salvador)
5. Re: Exporting kernel header from patch (gamma.d...@emerson.com)
6. raspberry Pi core-image-sato (Edward Vidal)
7. Re: raspberry Pi core-image-sato (Gary Thomas)
--
Message: 1
Date: Wed, 22 Jul 2015 23:29:52 +0200
From: Petter Mab?cker pet...@technux.se
To: yocto@yoctoproject.org
Subject: [yocto] [meta-raspberrypi][PATCH 1/1] packagegroup-rpi-test:
Add pi-blaster
Message-ID:
7c508bdaa77ecacf897f5470c85767ed6702fd6e.1437600372.git.pet...@technux.se
Content-Type: text/plain; charset=UTF-8
Ensure that pi-blaster is built and included by default when building
'rpi-test-image'.
Signed-off-by: Petter Mab?cker pet...@technux.se
---
recipes-core/packagegroups/packagegroup-rpi-test.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/recipes-core/packagegroups/packagegroup-rpi-test.bb
b/recipes-core/packagegroups/packagegroup-rpi-test.bb
index e16e79e..d8d311f 100644
--- a/recipes-core/packagegroups/packagegroup-rpi-test.bb
+++ b/recipes-core/packagegroups/packagegroup-rpi-test.bb
@@ -10,6 +10,7 @@ RDEPENDS_${PN} = \
wiringpi \
rpio \
rpi-gpio \
+ pi-blaster \
RRECOMMENDS_${PN} = \
--
1.9.1
--
Message: 2
Date: Wed, 22 Jul 2015 23:29:51 +0200
From: Petter Mab?cker pet...@technux.se
To: yocto@yoctoproject.org
Subject: [yocto] [meta-raspberrypi][PATCH 0/1] packagegroup-rpi-test:
Add pi-blaster
Message-ID: cover.1437600372.git.pet...@technux.se
Content-Type: text/plain; charset=UTF-8
The following changes since commit 7457bf182c8fd550ec877ecd786a3edd16e65495:
wiringpi: Bump SRCREV (2015-07-19 14:53:27 +0200)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib petmab/rpi_minor_fix
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=petmab/rpi_minor_fix
Petter Mab?cker (1):
packagegroup-rpi-test: Add pi-blaster
recipes-core/packagegroups/packagegroup-rpi-test.bb | 1
[yocto] raspberry Pi core-image-sato
Hi Gary,Is this the log that you need?I also ran the bitbake -DD core-image-sato and have the log for that run. | WARNING: exit code 1 from a shell command. | ERROR: oe_runconf failed | ERROR: Function failed: do_configure (log file is located at /home/vidal/wkg/yocto/RaspberryPi2/poky/build/tmp/work/cortexa7hf-vfp-vfpv4-neon-poky-linux-gnueabi/libepoxy/1.2+gitAUTOINC+20062c25e7-r0/temp/log.do_configure.9672) ERROR: Task 4597 (/home/vidal/wkg/yocto/RaspberryPi2/poky/meta/recipes-graphics/libepoxy/libepoxy_git.bb, do_configure) failed with exit code '1' Let me know what I can provide.Thanks for the help Regards,Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613 log.do_configure.9672 Description: Binary data -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] raspberry Pi core-image-sato booted okay
i Gary,
I added to my the 2 lines mentioned in the e-mail to my conf/local.conf
PREFERRED_PROVIDER_virtual/egl ?= vc-graphics-hardfp
PREFERRED_PROVIDER_virtual/libgles2 ?= vc-graphics-hardfp
I had saved the original local.conf in ~/wkg/yocto/local.conf before making any
changes.
diff -u ~/wkg/yocto/local.conf conf/local.conf
--- /home/vidal/wkg/yocto/local.conf 2015-07-21 08:15:40.228867905 -0600
+++ conf/local.conf 2015-07-23 09:11:45.095116784 -0600
@@ -10,6 +10,25 @@
# default values are provided as comments to show people example syntax.
Enabling
# the option is a question of removing the # character and making any change
to the
# variable as required.
+PREFERRED_PROVIDER_virtual/egl ?= vc-graphics-hardfp
+PREFERRED_PROVIDER_virtual/libgles2 ?= vc-graphics-hardfp
+#
+# Parallelism Options
+#
+# These two options control how much parallelism BitBake should use. The first
+# option determines how many tasks bitbake should run in parallel:
+#
+BB_NUMBER_THREADS = 12
+#
+# The second option controls how many processes make should run in parallel
when
+# running compile tasks:
+#
+PARALLEL_MAKE = -j 12
+#
+# For a quad-core machine, BB_NUMBER_THREADS = 4, PARALLEL_MAKE = -j 4
would
+# be appropriate for example.
+
+#
#
# Machine Selection
@@ -34,7 +53,10 @@
#MACHINE ?= edgerouter
#
# This sets the default machine to be qemux86 if no other machine is selected:
-MACHINE ??= qemux86
+#MACHINE ??= qemux86
+#MACHINE = raspberrypi2
+MACHINE ??= raspberrypi2
+GPU_MEM = 16
#
# Where to place downloads
@@ -48,7 +70,7 @@
# The default is a downloads directory under TOPDIR which is the build
directory.
#
#DL_DIR ?= ${TOPDIR}/downloads
-
+DL_DIR ?= /home/vidal/wkg/yocto/downloads
#
# Where to place shared-state files
#
bitbake userland -c cleansstate
bitbake core-image-sato
WARNING: QA Issue: gstreamer1.0-plugins-bad: configure was passed unrecognised
options: --with-egl-window-system [unknown-configure-option]
NOTE: Tasks Summary: Attempted 5356 tasks of which 4131 didn't need to be rerun
and all succeeded.
Summary: There was 1 WARNING message shown.
As root I created the SD
dd if=tmp/deploy/images/raspberrypi2/core-image-sato-raspberrypi2.rpi-sdimg |
pv | sudo dd of=/dev/sdb bs=16M
The Raspberry Pi 2 B boot to graphical sato interface.
Is there anything else that I can provide.
How do you when to use -c cleansstate on a recipe? This appears to be a handy
command.Thanks for all the help!!
Regards
Edward Vidal Jr.
e-mail devel...@sbcglobal.net
915-595-1613
local.conf
Description: Binary data
bblayers.conf
Description: Binary data
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] raspberry Pi core-image-sato
HiStill having errors with bitbake core-image-satoThis occurs at | checking for X11... yes | checking for EGL... no | configure: error: Package requirements (egl) were not met: ERROR: Task 4856 (/home/vidal/wkg/yocto/RaspberryPi2/poky/meta/recipes-graphics/libepoxy/libepoxy_git.bb, do_configure) failed with exit code '1'I tried adding /conf/machine/raspberrypi2.conf which I found on the internet.+PREFERRED_PROVIDER_virtual/egl ?= vc-graphics-hardfp +PREFERRED_PROVIDER_virtual/libgles2 ?= vc-graphics-hardfpThis caused several more errors.Any and all help is appreciated. Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] core-image-sato raspberrypi2
Hi all,In the file poky/meta/recipes-graphics/libepoxy/libepoxy_git.bb I tried to add --disable-egl, with no success PACKAGECONFIG[x11] = --enable-glx, --disable-glx, virtual/libx11 | checking for EGL... no | configure: error: Package requirements (egl) were not met: | | No package 'egl' found | | Consider adjusting the PKG_CONFIG_PATH environment variable if you | installed software in a non-standard prefix. | | Alternatively, you may set the environment variables EGL_CFLAGS | and EGL_LIBS to avoid the need to call pkg-config. | See the pkg-config man page for more details. | Configure failed. The contents of all config.log files follows to aid debugging | WARNING: exit code 1 from a shell command. | ERROR: oe_runconf failed | ERROR: Function failed: do_configure (log file is located at /home/vidal/wkg/yocto/RaspberryPi2/poky/build/tmp/work/cortexa7hf-vfp-vfpv4-neon-poky-linux-gnueabi/libepoxy/1.2+gitAUTOINC+20062c25e7-r0/temp/log.do_configure.23311) ERROR: Task 4597 (/home/vidal/wkg/yocto/RaspberryPi2/poky/meta/recipes-graphics/libepoxy/libepoxy_git.bb, do_configure) failed with exit code '1' NOTE: Tasks Summary: Attempted 3158 tasks of which 3080 didn't need to be rerun and 1 failed. Waiting for 0 running tasks to finish: Summary: 1 task failed: /home/vidal/wkg/yocto/RaspberryPi2/poky/meta/recipes-graphics/libepoxy/libepoxy_git.bb, do_configure Summary: There were 2 ERROR messages shown, returning a non-zero exit code. I found on the web reference to userland do I need this layer?Thanks for all the help. Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] core-image-sato raspberrypi2
Hi all,I created a rpi-basic-img for RaspberryPi 2 which was created and booted okay. I am using meta-yocto-bsp = fido:0f8d89ce66cfffccc9911d6c61470a585173b79d meta-raspberrypi = master:7457bf182c8fd550ec877ecd786a3edd16e65495. Can the core-image-sato be created for the RaspBerry 2 B? First i tried bitbake core-image-sato which was getting errors. Then I bitbake core-image-sato -c fetchall. NOTE: Tasks Summary: Attempted 626 tasks of which 626 didn't need to be rerun and all succeeded. Does this mean that all the depends have been downloaded? Now when I run I am missing checking for EGL... no in libepoxy do I need another layer before building core-image-sato?As always any and all help is appreciated.Regards. Edward Vidal Jr.e-mail devel...@sbcglobal.net 915-595-1613-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] RaspberryPi 2
Hello,It has been a while since I built any Yocto images. I have been trying to learn Hardware Description Language HDL.I have a raspberry working with Debian. I am using a couple of products from http://www.xess.com/ XESS XulA2-LX9, StickIt-MB which combines a Spartan 6 with a Raspberry Pi. I have MyHDL (generates HDL co-simulation) , Iverilog (co-simulator), GTKWAVE (viewing of FPGA signals), GNURadio, OpenCV (with 2 C920 cameras doing face detection), many Python libs (numpy, scipy, matplotlib) and git, This makes a great development platform for FPGA work.I am following the instructions at http://www.cnx-software.com/2015/02/27/yocto-project-raspberry-pi-2-board-minimal-image/ I have modified the local.conf. bblayers.conf, and poky.conf filesdiff local.conf.orig poky/raspberrypi2/conf/local.conf 37c37diff bblayers.conf.orig poky/raspberrypi2/conf/bblayers.conf 15a16 /home/vidal/wkg/yocto/RaspberryPi2/poky/meta-raspberrypi \,39 MACHINE ??= qemux86 --- #MACHINE ??= qemux86 MACHINE ?= raspberrypi2 GPU_MEM = 16 diff poky.conf.orig poky/meta-yocto/conf/distro/poky.conf 74a75 Ubuntu-12.04 \n \ bitbake rpi-basic-image sudo apt-get installdiffstatsudo apt-get installtexinf cd wkg/ tar xfzpi/SDL2-2.0.3.tar.gz cd SDL2-2.0.3/ ./configure make sudo make install sudo ldconfig I continue to get the following error.bitbake rpi-basic-image ERROR: OE-core's config sanity checker detected a potential misconfiguration. Either fix the cause of this error or at your own risk disable the checker (see sanity.conf). Following is the list of potential problems / advisories: Please set a valid MACHINE in your local.conf or environment libsdl-native is set to be ASSUME_PROVIDED but sdl-config can't be found in PATH. Please either install it, or configure qemu not to require sdl. Summary: There was 1 ERROR message shown, returning a non-zero exit code. Any and all help is appreciated.If you have any questions feel free to contact me.Regards. Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] RaspberryPi 2
Hi all, I made the following changes in local.conf--- ../../local.conf.orig 2015-07-20 07:01:42.835320506 -0600 +++ conf/local.conf 2015-07-20 10:50:00.129187741 -0600 @@ -34,7 +34,10 @@ #MACHINE ?= edgerouter # # This sets the default machine to be qemux86 if no other machine is selected: -MACHINE ??= qemux86 +#MACHINE ??= qemux86 +MACHINE = raspberrypi2 +MACHINE ??= raspberrypi2 +GPU_MEM = 16 I did not understand the comment by Gary ThomasYes, I use it all the time. Make the assignment immediate/firm though: MACHINE = raspberrypi2 bitbake rpi-basic-image ERROR: OE-core's config sanity checker detected a potential misconfiguration. Either fix the cause of this error or at your own risk disable the checker (see sanity.conf). Following is the list of potential problems / advisories: Please set a valid MACHINE in your local.conf or environment Summary: There was 1 ERROR message shown, returning a non-zero exit code. I also tried setting the MACHINE variable with the same results.Any and all help is appreciated. Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] RaspberryPi 2
Hi all,Gary Thomas recommended installing apt-get install libsdl1.2. which helped withThe libsdl-native error. Is MACHINE ??= raspberrypi2 a valid machine.bitbake rpi-basic-image ERROR: OE-core's config sanity checker detected a potential misconfiguration. Either fix the cause of this error or at your own risk disable the checker (see sanity.conf). Following is the list of potential problems / advisories: Please set a valid MACHINE in your local.conf or environment Summary: There was 1 ERROR message shown, returning a non-zero exit code. As always any and all help is appreciated.Thanks Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Raspberry 2 Pi
Hi all,Finally making progress. My problem was conf/bblayers.confI had the poky/meta-raspberrypi in the BBLAYERS_NON_REMOVABLE ?= \ Instead BBLAYERS ?= \ Currently working on 1965 tasks Build Configuration: BB_VERSION = 1.27.1 BUILD_SYS = x86_64-linux NATIVELSBSTRING = Ubuntu-12.04 TARGET_SYS = arm-poky-linux-gnueabi MACHINE = raspberrypi2 DISTRO = poky DISTRO_VERSION = 1.8+snapshot-20150721 TUNE_FEATURES = arm armv7a vfp thumb neon callconvention-hard vfpv4 cortexa7 TARGET_FPU = vfp-vfpv4-neon meta meta-yocto meta-yocto-bsp = master:0f8d89ce66cfffccc9911d6c61470a585173b79d meta-raspberrypi = master:7457bf182c8fd550ec877ecd786a3edd16e65495 Is anyone working on a compute module for the Pi using Yocto?Any and all help will be appreciated. Regards, Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] How to run c++ programs?
Hello, In the poky/documentation folder I execute the following: #!/bin/bash make DOC=adt-manual make DOC=kernel-dev make DOC=mega-manual make DOC=bsp-guide make DOC=kernel-manual make DOC=ref-manual make DOC=yocto-project-qs make DOC=dev-manual make DOC=profile-manual find . -name *.pdf This generates my documentation for yocto . What you need is the adt-manual. see Chapter 4. Using the Command Line. You also need to build SDK with bitbake. Then a script in images/sdk which you installs in /opt/poky/1. Hope this helps. I also am using a zedboard. I recently got sound, 2 C920 cameras, openCV, gnuplot, gsl, vlc, and gnuradio working with meta-topic instead of meta-xilinx thanks to Mike Looijmans on the meta-xilinx mailing list. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] gnuradio dora
Hello all, On dora branch GNU Radio Companion 3.6.5 starts to bring up the window and shuts down with the following error. gnuradio-companion ** (process:1166): WARNING **: Trying to register gtype 'GMountMountFlags' as enum when in fact it is of type 'GFlags' ** (process:1166): WARNING **: Trying to register gtype 'GDriveStartFlags' as enum when in fact it is of type 'GFlags' ** (process:1166): WARNING **: Trying to register gtype 'GSocketMsgFlags' as enum when in fact it is of type 'GFlags' Welcome to GNU Radio Companion 3.6.5 Error: 'options' Failure Traceback (most recent call last): File /usr/lib/python2.7/site-packages/gnuradio/grc/gui/MainWindow.py, line 172, in new_page flow_graph = self._platform.get_new_flow_graph() File /usr/lib/python2.7/site-packages/gnuradio/grc/base/Platform.py, line 152, in get_new_flow_graph def get_new_flow_graph(self): return self.FlowGraph(platform=self) File /usr/lib/python2.7/site-packages/gnuradio/grc/python/FlowGraph.py, line 31, in __init__ _FlowGraph.__init__(self, **kwargs) File /usr/lib/python2.7/site-packages/gnuradio/grc/base/FlowGraph.py, line 35, in __init__ self.import_data() File /usr/lib/python2.7/site-packages/gnuradio/grc/base/FlowGraph.py, line 176, in import_data self._options_block = self.get_parent().get_new_block(self, 'options') File /usr/lib/python2.7/site-packages/gnuradio/grc/base/Platform.py, line 162, in get_new_block def get_new_block(self, flow_graph, key): return self.Block(flow_graph, n=self._blocks_n[key]) File /usr/lib/python2.7/site-packages/gnuradio/grc/base/odict.py, line 34, in __getitem__ return self._data[key] KeyError: 'options' Also needed to include additional packages not needed in dylan branch python-pygtk, python-lxml. and python-cheetah Any and all help is appreciated. Thanks ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] EXTRA_IMAGE_FEATURES dora branch local.conf
Hello all, I am working on dora branch The EXTRA_IMAGE_FEATURES = debug-tweaks tools-sdk dev-pkgs appears to have an error. I am having to include the dev on the IMAGE_INSTALL line of my custom-image. IMAGE_INSTALL += kernel-dev fpga-image-adi adi-hdmi-load \ kernel-modules modutils-loadscript zed-audio v4l-utils gsl gsl-dev gnuplot \ chkconfig git jasper fluidsynth liba52 boost \ qt-mobility-x11 libmad python-netserver gnuradio xterm \ python-pygtk python-pygtk-dev python-lxml opencv opencv-samples \ gnuradio-dev opencv-apps opencv-dev opencv-samples-dev \ gnuradio-doc gnuradio-examples \ opencv-staticdev python-cheetah x264 lua5.1 libav This was not needed in dylan branch. BB_VERSION= 1.20.0 BUILD_SYS = x86_64-linux NATIVELSBSTRING = Ubuntu-12.04 TARGET_SYS= arm-poky-linux-gnueabi MACHINE = zedboard DISTRO= poky DISTRO_VERSION= 1.5.1 TUNE_FEATURES = armv7a vfp neon TARGET_FPU= vfp-neon meta meta-yocto= dora:c3cccbea7abd4af3d603b2be42b0c7291ff21946 meta-topic= master:9af0ecd7e756b367e0ec80263319247b6c2d69c3 meta-oe meta-multimedia meta-gnome= dora:191499a2b54d04855284347ce5a067f998646be4 meta-yocto-bsp= dora:c3cccbea7abd4af3d603b2be42b0c7291ff21946 Any and all help is appreciated. Thanks ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] meta-oe x264
Hello All, In Dec 13 I used meta-oe on a dylan branch and x264 was included as part of meta-oe/meta-oe/recipes-multimedia/x264. Build Configuration: BB_VERSION= 1.18.0 BUILD_SYS = x86_64-linux NATIVELSBSTRING = Fedora-18 TARGET_SYS= arm-poky-linux-gnueabi MACHINE = zedboard DISTRO= poky DISTRO_VERSION= 1.4.2 TUNE_FEATURES = armv7a vfp neon zynq TARGET_FPU= vfp-neon meta meta-yocto= dylan:4e399f08d596197859214fdb3b06403b87bf8789 meta-oe meta-multimedia = dylan:44754206632dd5b0725aeb43e99e4ff9e0245dca meta-xilinx meta-kc705 meta-zc702 meta-zedboard = dylan:cf9571203be0af5fc654952d3f00e0a7e0fb1174 I am working with the dora branch and this is now not included. Does anyone know the reason that x264 was removed from the dora branch or has is just not been added. My custom-image includes it and it built okay. Build Configuration: BB_VERSION= 1.20.0 BUILD_SYS = x86_64-linux NATIVELSBSTRING = Ubuntu-12.04 TARGET_SYS= arm-poky-linux-gnueabi MACHINE = zedboard DISTRO= poky DISTRO_VERSION= 1.5.1 TUNE_FEATURES = armv7a vfp neon TARGET_FPU= vfp-neon meta meta-yocto= dora:c3cccbea7abd4af3d603b2be42b0c7291ff21946 meta-topic= master:9af0ecd7e756b367e0ec80263319247b6c2d69c3 meta-oe meta-multimedia meta-gnome= dora:191499a2b54d04855284347ce5a067f998646be4 meta-yocto-bsp= dora:c3cccbea7abd4af3d603b2be42b0c7291ff21946 If I can provide any additional information just let me know. Any and all help is appreciated. Thanks ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Fwd: meta-topic meta-zynq
-- Forwarded message -- From: Edward Vidal vidal.devel...@gmail.com Date: Wed, Jan 22, 2014 at 9:37 AM Subject: meta-topic meta-zynq To: meta-xil...@yoctoproject.org Hello All Not able to source or . in a bitbake receipe. When source is used the error is source not found. When . is used the path is not set and xps can not be found. Could the be a ubuntu problem. I just recently changed from Fedora19 x86_64 to precise1-Ubuntu SMP Wed Aug 14 16:19:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux. 1.) MACHINE=zedboard bitbake virtual/kernel okay 2.) MACHINE=zedboard bitbake u-boot-zynq okay 3.) MACHINE=zedboard bitbake sd-bootscript okay 4.) MACHINE=zedboard bitbake fpga-image fails I can manually do the following steps to obtain a fpga.bin file. 1.) cd zynq_oe/build/tmp-eglibc/work/zedboard-oe-linux-gnueabi/fpga-image/5.AUTOINC-0a90b0d42e-r0/git/cf_adv7511_zed/ 2.) . /opt/Xilinx/14.4/ISE_DS/settings64.sh 3.) xps -nw system.xmp 4.) run bits 5.) run exporttosdk 6.) python ../../fpga-bit-to-bin.py --flip implementation/system.bit ../../../5.AUTOINC-0a90b0d42e-r0/fpga.bin Design name: system.ncd;HW_TIMEOUT=FALSE;UserID=0x Partname 7z020clg484 Date 2014/01/22 Time 08:20:03 found binary data: 4045564 After deleting fpga-image from meta-zynq/receipes-core/images/my-image.bb MACHINE=zedboard bitbake my-image okay Thanks ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] booting zedboard dora build
hello All,
My boot starts to boot then I get a data abort see below.
md5sums of files where they source to be put on /run/media/vidal/ZED_BOOT/
These should match the md5sums on /run/media/vidal/ZED_BOOT/
d34217fdf453c318a11bada96464a014 yocto010514/BOOT.BIN
7a1525c3a1a63fcffbb172348cdd4221
zedboard_support_files/boot_files_yocto_wmyled/devicetree.dtb
7cf4e3eea28ce84886d4618856703979 yocto010514/zedboard-zynq7/uImage
md5sum /run/media/vidal/ZED_BOOT/*
d34217fdf453c318a11bada96464a014 /run/media/vidal/ZED_BOOT/BOOT.BIN
u-boot created with poky bootgen
yocto010514/bootimage.bif
the_ROM_image:
{
[bootloader]/home/vidal/yocto010514/FSBL.elf
/home/vidal/yocto010514//system.bit
/home/vidal/yocto010514/zedboard-zynq7/u-boot.elf
}
7a1525c3a1a63fcffbb172348cdd4221
/run/media/vidal/ZED_BOOT/devicetree.dtb linux-digilent
105fce435d72233f63a35aeba7b8eab1 /run/media/vidal/ZED_BOOT/uEnv.txt
This the contents of uEnv.txt
devtreeld=fatload mmc 0 0x2A0 devicetree.dtb
kerload=fatload mmc 0 0x8000 uImage
mmcboot=run devtreeld; run kerload; bootm 0x8000 - 0x2A0
7cf4e3eea28ce84886d4618856703979 /run/media/vidal/ZED_BOOT/uImage
created with poky
mkimage -l /home/vidal/yocto010514/zedboard-zynq7/uImage
Image Name: Linux-3.8.11-xilinx
Created: Sun Jan 5 15:56:08 2014
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size:2858760 Bytes = 2791.76 kB = 2.73 MB
Load Address: 8000
Entry Point: 8000
ls -la /run/media/vidal/ZED_BOOT/*
-rw-r--r--. 1 vidal users 4372888 Jan 7 13:04
/run/media/vidal/ZED_BOOT/BOOT.BIN
-rw-r--r--. 1 vidal users9720 Jan 7 12:39
/run/media/vidal/ZED_BOOT/devicetree.dtb
-rw-r--r--. 1 vidal users 154 Jan 7 14:05
/run/media/vidal/ZED_BOOT/uEnv.txt
-rw-r--r--. 1 vidal users 2858824 Jan 7 13:27 /run/media/vidal/ZED_BOOT/uImage
After the uEnv.txt has been read
* - * Qodem 0.1.2 Capture Generated Tue, 07 Jan 2014 14:17:21 -0700 BEGIN * - *
echo $mmcboot
run devtreeld; run kerload; bootm 0x8000 - 0x2A0
zynq-uboot echo $devtreeld
fatload mmc 0 0x2A0 devicetree.dtb
zynq-uboot echo $kerload
fatload mmc 0 0x8000 uImage
zynq-uboot setenv modeboot mmcboot
zynq-uboot boot
Now when I boot using mmcboot this is the output
reading devicetree.dtb
9720 bytes read in 18 ms (527.3 KiB/s)
reading uImage
2858824 bytes read in 444 ms (6.1 MiB/s)
## Booting kernel from Legacy Image at 8000 ...
Image Name: Linux-3.8.11-xilinx
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size:2858760 Bytes = 2.7 MiB
Load Address: 8000
Entry Point: 8000
Verifying Checksum ... OK
## Flattened Device Tree blob at 02a0
Booting using the fdt blob at 0x2a0
XIP Kernel Image ... OK
Loading Device Tree to 1fb4f000, end 1fb545f7 ... OK
Starting kernel ...
data abort
MAYBE you should read doc/README.arm-unaligned-accesses
pc : [1ff7624c] lr : [1ff777d0]
sp : 3ffc ip : fp : 00020205
r10: 1ffaeaf0 r9 : f345364f r8 : 0080
r7 : r6 : 8000 r5 : 1ffaeaf0 r4 :
r3 : 2614 r2 : 1fb4f000 r1 : baefa2ee r0 : 11acb1b4
Flags: nzcv IRQs on FIQs on Mode SVC_32
Resetting CPU ...
resetting ...
Xilinx First Stage Boot Loader
Release 14.3 Sep 29 2013-13:27:28
Devcfg driver initialized
Silicon Version 1.0
Boot mode is SD
SD Init Done
Flash BaseAddress E010
Reboot status register 0x6000
ImageStartAddress =
PartitionNumber =
flash read base addr E010, image base 0
FSBL main: Skip partition
Reboot status register 0x6100
ImageStartAddress =
PartitionNumber = 0001
flash read base addr E010, image base 0
Reset USB...
SUCCESSFUL_HANDOFF
FSBLStatus = 0x1
U-Boot 2013.07 (Jan 06 2014 - 10:40:34)
Memory: ECC disabled
DRAM: 512 MiB
WARNING: Caches not enabled
MMC: zynq_sdhci: 0
SF: Detected S25FL256S_64K with page size 64 KiB, total 32 MiB
*** Warning - bad CRC, using default environment
In:serial
Out: serial
Err: serial
Net: Gem.e000b000
Hit any key to stop autoboot: 3 2 1 0
Device: zynq_sdhci
Manufacturer ID: 2
OEM: 544d
Name: SA32G
Tran Speed: 5000
Rd Block Len: 512
SD version 3.0
High Capacity: Yes
Capacity: 29.3 GiB
Bus Width: 4-bit
reading uEnv.txt
154 bytes read in 9 ms (16.6 KiB/s)
Loaded environment from uEnv.txt
Importing environment from SD ...
Copying Linux from SD to RAM...
reading uImage
2858824 bytes read in 448 ms (6.1 MiB/s)
reading devicetree.dtb
9720 bytes read in 19 ms (499 KiB/s)
reading uramdisk.image.gz
** Unable to read file uramdisk.image.gz **
zynq-uboot
* - * Qodem 0.1.2 Capture Generated Tue, 07 Jan 2014 14:19:21 -0700 END * - *
Any and all help is appreciated.
Thanks
Ed Vidal
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] zedboard gnuradio already stripped error
Hello All, I just built a dora custom-image for the Zedboard. Back in July and error appeared zedboard gnuradio *Tue Jul 16 07:47:03 PDT 2013* Paul helped with the following Hi Edward, On Tuesday 16 July 2013 08:47:03 Edward Vidal wrote: * ERROR: QA Issue: File '/usr/plugins/designer/libqwt_designer_plugin.so' ** from qwt was already stripped, this will prevent future debugging! ** ERROR: QA Issue: File '/usr/lib/libqwt.so.6.0.1' from qwt was already ** stripped, this will prevent future debugging! ** ERROR: QA Issue: File '/usr/lib/libqwtmathml.so.6.0.1' from qwt was already ** stripped, this will prevent future debugging! * poky.conf now marks this QA issue as an error instead of a warning in order to pick up on quality issues when running builds. You can either: a) Fix the recipe so that qwt gets built without stripping its output binaries, or b) set your own value for ERROR_QA and WARN_QA so that already-stripped appears in WARN_QA rather than ERROR_QA Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre I used option b) then and in the recent build today. ERROR_QA = already-stripped moved to WARN_QA = in the file /home/vidal/POKY/kernel_build/poky/meta-yocto/conf/distro/poky.conf Can some please pass to meta-oe group since I do not have access to that list. This error does not occur with dylan branch I just switched to dora. Thanks. ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] toolchain
Hello all,
I am currently working with the zedboard using a rootfs generated with a
dylan branch of yocto (gsl, gnuplot, gnuradio, java, vlc, v4l-utils, and
openCV with C920 camera). My zImage and devicetree.dtb were built with
yocto sdk. My BOOT.BIN (FSBL system.bit and u-boot) were built with 14.4
of Xilinx Tools. This requires dual booting a CentOS 6.4 x86_64 (Xilinx
Tools) and Fedora19 x86_64 (Yocto). I have not been able to run Yocto on
CentOS since the need for higher version of python.
Is it possible to generate a BOOT.BIN with the files generated with
Yocto?
This requires 2 toolchains. I was checking the difference between the 2
see the attached files.
Should the difference between the toolchains be of concern going forward?
My Xilinx tools are node locked and I can only use on a single system.
Is there a method to run Yocto on CentOS6.4 x86_64?
Any and all help will be appreciated.
Thanks
arm-poky-linux-gnueabi-gcc -v
Using built-in specs.
COLLECT_GCC=arm-poky-linux-gnueabi-gcc
COLLECT_LTO_WRAPPER=/opt/poky/1.4.3/sysroots/x86_64-pokysdk-linux/usr/libexec/armv7a-vfp-neon-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.7.2/lto-wrapper
Target: arm-poky-linux-gnueabi
Configured with:
/home/vidal/POKY/dylan_build/poky/build/tmp/work-shared/gcc-4.7.2-r20/gcc-4.7.2/configure
--build=x86_64-linux
--host=x86_64-pokysdk-linux
--target=arm-poky-linux-gnueabi
--prefix=/opt/poky/1.4.3/sysroots/x86_64-pokysdk-linux/usr
--exec_prefix=/opt/poky/1.4.3/sysroots/x86_64-pokysdk-linux/usr
--bindir=/opt/poky/1.4.3/sysroots/x86_64-pokysdk-linux/usr/bin/armv7a-vfp-neon-poky-linux-gnueabi
--sbindir=/opt/poky/1.4.3/sysroots/x86_64-pokysdk-linux/usr/bin/armv7a-vfp-neon-poky-linux-gnueabi
--libexecdir=/opt/poky/1.4.3/sysroots/x86_64-pokysdk-linux/usr/libexec/armv7a-vfp-neon-poky-linux-gnueabi
--datadir=/opt/poky/1.4.3/sysroots/x86_64-pokysdk-linux/usr/share
--sysconfdir=/opt/poky/1.4.3/sysroots/x86_64-pokysdk-linux/etc
--sharedstatedir=/opt/poky/1.4.3/sysroots/x86_64-pokysdk-linux/com
--localstatedir=/opt/poky/1.4.3/sysroots/x86_64-pokysdk-linux/var
--libdir=/opt/poky/1.4.3/sysroots/x86_64-pokysdk-linux/usr/lib/armv7a-vfp-neon-poky-linux-gnueabi
--includedir=/opt/poky/1.4.3/sysroots/x86_64-pokysdk-linux/usr/include
--oldincludedir=/opt/poky/1.4.3/sysroots/x86_64-pokysdk-linux/usr/include
--infodir=/opt/poky/1.4.3/sysroots/x86_64-pokysdk-linux/usr/share/info
--mandir=/opt/poky/1.4.3/sysroots/x86_64-pokysdk-linux/usr/share/man
--disable-silent-rules
--disable-dependency-tracking
--with-libtool-sysroot=/home/vidal/POKY/dylan_build/poky/build/tmp/sysroots/x86_64-nativesdk-pokysdk-linux
--with-gnu-ld
--enable-shared
--enable-languages=c,c++
--enable-threads=posix
--enable-multilib
--enable-c99
--enable-long-long
--enable-symvers=gnu
--enable-libstdcxx-pch
--program-prefix=arm-poky-linux-gnueabi-
--without-local-prefix
--enable-target-optspace
--enable-lto
--enable-libssp
--disable-bootstrap
--disable-libmudflap
--with-system-zlib
--with-linker-hash-style=gnu
--enable-linker-build-id
--with-ppl=no
--with-cloog=no
--enable-checking=release
--enable-cheaders=c_global
--with-gxx-include-dir=/opt/poky/1.4.3/sysroots/armv7a-vfp-neon-poky-linux-gnueabi/usr/include/c++
--with-build-time-tools=/home/vidal/POKY/dylan_build/poky/build/tmp/sysroots/x86_64-linux/usr/arm-poky-linux-gnueabi/bin
--with-sysroot=/opt/poky/1.4.3/sysroots/armv7a-vfp-neon-poky-linux-gnueabi
--with-build-sysroot=/home/vidal/POKY/dylan_build/poky/build/tmp/sysroots/zedboard
--disable-libunwind-exceptions
--disable-libssp
--disable-libgomp
--disable-libmudflap
--with-mpfr=/home/vidal/POKY/dylan_build/poky/build/tmp/sysroots/x86_64-nativesdk-pokysdk-linux
--with-mpc=/home/vidal/POKY/dylan_build/poky/build/tmp/sysroots/x86_64-nativesdk-pokysdk-linux
--enable-nls
Thread model: posix
gcc version 4.7.2 (GCC)
arm-xilinx-linux-gnueabi-gcc -v
Using built-in specs.
COLLECT_GCC=arm-xilinx-linux-gnueabi-gcc
COLLECT_LTO_WRAPPER=/opt/Xilinx/14.4/SDK/SDK/gnu/arm/lin/bin/../libexec/gcc/arm-xilinx-linux-gnueabi/4.6.3/lto-wrapper
Target: arm-xilinx-linux-gnueabi
Configured with:
/scratch/janisjo/2012.03-xilinx-linux-lite/src/gcc-4.6-2012.03/configure
--build=i686-pc-linux-gnu
--host=i686-pc-linux-gnu
--target=arm-xilinx-linux-gnueabi
--enable-threads
--disable-libmudflap
--disable-libssp
--disable-libstdcxx-pch
--enable-extra-sgxxlite-multilibs
--with-arch=armv5te
--with-cpu=cortex-a9
--with-float=softfp
--with-fpu=neon-fp16
--disable-multilib
--with-gnu-as
--with-gnu-ld
--with-specs='%{save-temps: -fverbose-asm}
%{funwind-tables|fno-unwind-tables|mabi=*|ffreestanding|nostdlib:;:-funwind-tables}
-D__CS_SOURCERYGXX_MAJ__=2012 -D__CS_SOURCERYGXX_MIN__=3
-D__CS_SOURCERYGXX_REV__=79 %{O2:%{!fno-remove-local-statics:
-fremove-local-statics}} %{O*:%{O|O0|O1|O2|Os:;:%{!fno-remove-local-statics:
-fremove-local-statics}}}'
--enable-languages=c,c++
--enable-shared
--enable-lto
[yocto] boot zedboard with dylan yocto
Hello, Has anyone booted with the following files built with bitbake. custom-image-zedboard-20131223033354.rootfs.cpio custom-image-zedboard-20131223033354.rootfs.ext2 custom-image-zedboard-20131223033354.rootfs.ext2.gz custom-image-zedboard-20131223033354.rootfs.ext2.gz.u-boot custom-image-zedboard.cpio custom-image-zedboard.ext2 custom-image-zedboard.ext2.gz custom-image-zedboard.ext2.gz.u-boot modules--3.8-xilinx+git0+6a0bedad60e2bca8d9b50bf81b9895e29e31a6d7-r1-zedboard-2013134334.tgz README_-_DO_NOT_DELETE_FILES_IN_THIS_DIRECTORY.txt uImage uImage--3.8-xilinx+git0+6a0bedad60e2bca8d9b50bf81b9895e29e31a6d7-r1-zedboard-2013134334.bin uImage--3.8-xilinx+git0+6a0bedad60e2bca8d9b50bf81b9895e29e31a6d7-r1-zynq-zed-2013134334.dtb uImage-zedboard.bin uImage-zynq-zed.dtb I have used the custom-image-zedboard-20131223033354.rootfs.ext2 with linux-digilent kernel and u-boot-digilent. In my dtb file I have set the following model = Xilinx Zynq ZC702; compatible = xlnx,zynq-zc702; by editing my dts file. The following is the error I am getting. Error: unrecognized/unsupportedmachine ID (r1 = 0x1fb694ec). Available machine support: ID (hex)NAME ARM-Versatile Express 08e0ARM-Versatile Express 0d32Xilinx Zynq Platform Also does anyone have sound working on the zedboard. Any and all help is appreciated. Thanks ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Development of Yocto Project Kernel outside of Intel?
Hello Bob, Bob wrote Can someone please share with me the forecast (or any info) on whether the Yocto Project Kernel methodology will be picked up by additional non Intel cores / companies in 2014 or beyond? I am currently using the dylan branch with the zedboard. Build Configuration: BB_VERSION= 1.18.0 BUILD_SYS = x86_64-linux NATIVELSBSTRING = Fedora-19 TARGET_SYS= arm-poky-linux-gnueabi MACHINE = zedboard DISTRO= poky DISTRO_VERSION= 1.4.3 TUNE_FEATURES = armv7a vfp neon zynq TARGET_FPU= vfp-neon meta meta-yocto= dylan:544c58df358b03dda007700b83ffe2e5f07a7bbb meta-browser = dylan:2140f2a114f7009f86479afb12a524bb157cbb0e meta-gnome meta-oe meta-multimedia = dylan:44754206632dd5b0725aeb43e99e4ff9e0245dca meta-xilinx meta-kc705 meta-zc702 meta-zedboard = dylan:cf9571203be0af5fc654952d3f00e0a7e0fb1174 meta-yocto-bsp= dylan:544c58df358b03dda007700b83ffe2e5f07a7bbbmeta-yocto-bsp= (detachedfromorigin/dylan):57e6d537e847b88e4f89cd01be8a2926953b0082 I have used earlier yocto dylan branch with beaglebone, beagleboard ,and pandaboard. devel...@sbcglobal.net or vidal.devel...@gmail.com ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] deploy/images
Hello all, I have a few questions about the files in deploy/images. When working with beagleboard I would see MLO u-boot and uImage. I would copy these to DOS partition. Now Working with ZedBoard I have been using the BOOT.bin, devicetree.dtb and zImage. The BOOT.bin was created with xilinx FSBL and system.bit using the Xilinx tools. The zImage and devicetree.dtb were created with a kernel that was modified from linux-digilent . https://github.com/Digilent/linux-digilent.git. Yocto item that I have been using is custom-image-zedboard-20131214212545.rootfs.ext2. What tools do I need to use The files in deploy/images custom-image-zedboard-20131214212545.rootfs.cpio custom-image-zedboard-20131214212545.rootfs.ext2 custom-image-zedboard-20131214212545.rootfs.ext2.gz custom-image-zedboard-20131214212545.rootfs.ext2.gz.u-boot custom-image-zedboard.cpio custom-image-zedboard.ext2 custom-image-zedboard.ext2.gz custom-image-zedboard.ext2.gz.u-boot modules--3.8-xilinx+git0+6a0bedad60e2bca8d9b50bf81b9895e29e31a6d7-r1-zedboard-20131214164131.tgz README_-_DO_NOT_DELETE_FILES_IN_THIS_DIRECTORY.txt uImage uImage--3.8-xilinx+git0+6a0bedad60e2bca8d9b50bf81b9895e29e31a6d7-r1-zedboard-20131214164131.bin uImage--3.8-xilinx+git0+6a0bedad60e2bca8d9b50bf81b9895e29e31a6d7-r1-zynq-zed-20131214164131.dtb uImage-zedboard.bin uImage-zynq-zed.dtb Is uImage-zedboard.bin a u-boot type file? Which manual should I read about transferring these files to the mmc. Any and all help will be appreciated. Thanks ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] poky tree
Thanks for the information. When I removed poky/build/tmp everything worked okay. My build was quick and I did not need to recompile. My question is what relation between poky/build/tmp/work and poky/build/tmp/sysroot? Thanks for all the great work On Tue, Dec 10, 2013 at 2:18 PM, Burton, Ross ross.bur...@intel.com wrote: On 10 December 2013 20:38, Edward Vidal vidal.devel...@gmail.com wrote: Hello, I have a poky tree that I have used for several builds. What is the command to clean out the poky/build/tmp area. I am on the dylan branch. My conf files are configured and my custom-image are okay. I want to pull meta-oe, meta-broswer, and meta-xiiinx, and poky with a clean work area. Can I just delete poky/build or poky/build/tmp? Deleting poky/build/tmp is safe assuming that you've copied out everything you want to keep (images, etc). By default sstate-cache is next to tmp not underneath it, so the first build after wiping tmp will be reconstructed from sstate instead of needing to recompile anything. Ross ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Fedora19
Hello, I addedFedora-19 \n \ to poky/meta-yocto/conf/distro/poky.conf. MACHINE=zedboard bitbake custom-image Pseudo is not present but is required, building this first before the main build ERROR: OE-core's config sanity checker detected a potential misconfiguration. Either fix the cause of this error or at your own risk disable the checker (see sanity.conf). Following is the list of potential problems / advisories: Please install the following missing utilities: C++ Compiler (g++) ERROR: Execution of event handler 'check_sanity_eventhandler' failed What else is needed? Any and all help will be appreciated. Thanks ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] poky tree
Hello, I have a poky tree that I have used for several builds. What is the command to clean out the poky/build/tmp area. I am on the dylan branch. My conf files are configured and my custom-image are okay. I want to pull meta-oe, meta-broswer, and meta-xiiinx, and poky with a clean work area. Can I just delete poky/build or poky/build/tmp? Thanks ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] same recipe name which is correct
Hello, meta/recipes-gnome/gnome/libgnome-keyring_2.32.0.bb and meta-oe/meta-gnome/recipes-gnome/libgnome/libgnome-keyring_2.32.0.bb on the dylan branch have the same name but one is r0 and the other is r3. diff meta/recipes-gnome/gnome/libgnome-keyring_2.32.0.bbmeta-oe/meta-gnome/recipes-gnome/libgnome/ libgnome-keyring_2.32.0.bb 1,3c1,4 DESCRIPTION = Compatibility library for accessing secrets HOMEPAGE = http://www.gnome.org/; BUGTRACKER = https://bugzilla.gnome.org/; --- DESCRIPTION = Gnome keyring library LICENSE = LGPLv2 GPLv2 LIC_FILES_CHKSUM = file://COPYING.GPL;md5=94d55d512a9ba36caa9b7df079bae19f \ file://COPYING;md5=0914b9d3ebaba41ef2e3e0ae16f296cf 5,9c6 LICENSE = LGPLv2 LGPLv2+ LGPLv2.1+ LIC_FILES_CHKSUM = file://COPYING;md5=0914b9d3ebaba41ef2e3e0ae16f296cf \ file://library/gnome-keyring.h;endline=25;md5=68ea64f81c160d670c37da5f137be4fb \ file://library/gnome-keyring.c;endline=26;md5=8d7a4fb674aaa012ea5a98e7c368b4a5 \ file://egg/egg-dh.h;endline=22;md5=1626c16af2a8da1f88324cf3ced33f08 --- SECTION = x11/gnome 11,16c8 SECTION = x11/gnome/libs PR = r3 inherit gnome gtk-doc DEPENDS = dbus libgcrypt glib-2.0 intltool-native --- inherit gnome lib_package perlnative 19a12 I got 55 errors similar to ERROR: Package version for package libgnome-keyring-dbg went backwards which would break package feeds from (0:2.32.0-r3 to 0:2.32.0-r0) My custom-image still was created using the following RPMs libgnome-keyring-dev-2.32.0-r0.armv7a_vfp_neon.rpm libgnome-keyring-locale-en-gb-2.32.0-r0.armv7a_vfp_neon.rpm libgnome-keyring0-2.32.0-r0.armv7a_vfp_neon.rpm The packages I was trying to added were firefox chromium which needed meta-gnome. Any and all help will be appreciated. Thanks ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] firefox
Hello,
I am trying to add firefox to my build
cd meta-browser
git checkout -b dylan origin/dylan
Below is my bblayers.conf where I added meta-browser
# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly
LCONF_VERSION = 6
BBPATH = ${TOPDIR}
BBFILES ?=
BBLAYERS ?= \
/home/vidal/POKY/dylan_build/poky/meta \
/home/vidal/POKY/dylan_build/poky/meta-yocto \
/home/vidal/POKY/dylan_build/poky/meta-browser \
/home/vidal/POKY/dylan_build/poky/meta-oe/meta-oe \
/home/vidal/POKY/dylan_build/poky/meta-oe/meta-multimedia \
/home/vidal/POKY/dylan_build/poky/meta-xilinx \
/home/vidal/POKY/dylan_build/poky/meta-xilinx/meta-kc705 \
/home/vidal/POKY/dylan_build/poky/meta-xilinx/meta-zc702 \
/home/vidal/POKY/dylan_build/poky/meta-xilinx/meta-zedboard \
/home/vidal/POKY/dylan_build/poky/meta-yocto-bsp \
BBLAYERS_NON_REMOVABLE ?= \
/home/vidal/POKY/dylan_build/poky/meta \
/home/vidal/POKY/dylan_build/poky/meta-yocto \
MACHINE=zedboard bitbake firefox
Loading cache: 100% |###| ETA:
00:00:00
Loaded 1717 entries from dependency cache.
Parsing recipes: 100% |#| Time:
00:00:01
Parsing of 1348 .bb files complete (1253 cached, 95 parsed). 1716 targets,
50 skipped, 0 masked, 0 errors.
ERROR: No recipes available for:
/home/vidal/POKY/dylan_build/poky/meta-browser/recipes-gnome/gnome-settings-daemon/gnome-settings-daemon_2.32.1.bbappend
ERROR: Command execution failed: Exited with 1
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
[vidal@ws009 build]$ less
../meta-browser/recipes-gnome/gnome-settings-daemon/gnome-settings-daemon_2.32.1.bbappend
[vidal@ws009 build]$ cat
../meta-browser/recipes-gnome/gnome-settings-daemon/gnome-settings-daemon_2.32.1.bbappend
DEPENDS += nss
CFLAGS += -I${STAGING_INCDIR}/mozilla/nss
I have a gnome-settings-daemon_2.32.1.bbappend file what would be causing
the error.
Any and all help will be appreciated.
Thanks
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] firefox
: Package version for package libgnome-keyring-locale-mn went backwards which would break package feeds from (0:2.32.0-r3 to 0:2.32.0-r0) ERROR: Package version for package libgnome-keyring-locale-ms went backwards which would break package feeds from (0:2.32.0-r3 to 0:2.32.0-r0) ERROR: Package version for package libgnome-keyring-locale-nb went backwards which would break package feeds from (0:2.32.0-r3 to 0:2.32.0-r0) ERROR: Package version for package libgnome-keyring-locale-nds went backwards which would break package feeds from (0:2.32.0-r3 to 0:2.32.0-r0) ERROR: Package version for package libgnome-keyring-locale-nl went backwards which would break package feeds from (0:2.32.0-r3 to 0:2.32.0-r0) ERROR: Package version for package libgnome-keyring-locale-nn went backwards which would break package feeds from (0:2.32.0-r3 to 0:2.32.0-r0) ERROR: Package version for package libgnome-keyring-locale-pa went backwards which would break package feeds from (0:2.32.0-r3 to 0:2.32.0-r0) ERROR: Package version for package libgnome-keyring-locale-pl went backwards which would break package feeds from (0:2.32.0-r3 to 0:2.32.0-r0) ERROR: Package version for package libgnome-keyring-locale-pt went backwards which would break package feeds from (0:2.32.0-r3 to 0:2.32.0-r0) ERROR: Package version for package libgnome-keyring-locale-pt-br went backwards which would break package feeds from (0:2.32.0-r3 to 0:2.32.0-r0) ERROR: Package version for package libgnome-keyring-locale-ro went backwards which would break package feeds from (0:2.32.0-r3 to 0:2.32.0-r0) ERROR: Package version for package libgnome-keyring-locale-ru went backwards which would break package feeds from (0:2.32.0-r3 to 0:2.32.0-r0) ERROR: Package version for package libgnome-keyring-locale-sk went backwards which would break package feeds from (0:2.32.0-r3 to 0:2.32.0-r0) ERROR: Package version for package libgnome-keyring-locale-sl went backwards which would break package feeds from (0:2.32.0-r3 to 0:2.32.0-r0) ERROR: Package version for package libgnome-keyring-locale-sr went backwards which would break package feeds from (0:2.32.0-r3 to 0:2.32.0-r0) ERROR: Package version for package libgnome-keyring-locale-sr+latin went backwards which would break package feeds from (0:2.32.0-r3 to 0:2.32.0-r0) ERROR: Package version for package libgnome-keyring-locale-sv went backwards which would break package feeds from (0:2.32.0-r3 to 0:2.32.0-r0) ERROR: Package version for package libgnome-keyring-locale-ta went backwards which would break package feeds from (0:2.32.0-r3 to 0:2.32.0-r0) ERROR: Package version for package libgnome-keyring-locale-th went backwards which would break package feeds from (0:2.32.0-r3 to 0:2.32.0-r0) ERROR: Package version for package libgnome-keyring-locale-uk went backwards which would break package feeds from (0:2.32.0-r3 to 0:2.32.0-r0) ERROR: Package version for package libgnome-keyring-locale-zh-cn went backwards which would break package feeds from (0:2.32.0-r3 to 0:2.32.0-r0) ERROR: Package version for package libgnome-keyring-locale-zh-hk went backwards which would break package feeds from (0:2.32.0-r3 to 0:2.32.0-r0) ERROR: Package version for package libgnome-keyring-locale-zh-tw went backwards which would break package feeds from (0:2.32.0-r3 to 0:2.32.0-r0) poky/meta/recipes-gnome/libgnome-keyring_2.32.0.bb DESCRIPTION = Compatibility library for accessing secrets HOMEPAGE = http://www.gnome.org/; BUGTRACKER = https://bugzilla.gnome.org/; LICENSE = LGPLv2 LGPLv2+ LGPLv2.1+ LIC_FILES_CHKSUM = file://COPYING;md5=0914b9d3ebaba41ef2e3e0ae16f296cf \ file://library/gnome-keyring.h;endline=25;md5=68ea64f81c160d670c37da5f137be4fb \ file://library/gnome-keyring.c;endline=26;md5=8d7a4fb674aaa012ea5a98e7c368b4a5 \ file://egg/egg-dh.h;endline=22;md5=1626c16af2a8da1f88324cf3ced33f08 SECTION = x11/gnome/libs PR = r3 inherit gnome gtk-doc DEPENDS = dbus libgcrypt glib-2.0 intltool-native SRC_URI[archive.md5sum] = c42b2ca66204835d901d3dbfc1fa5ae6 SRC_URI[archive.sha256sum] = 56388c0d81ddfdb57d30e4963c83ecc1c18498aab99395420e0fff69929a0f0c poky/meta-oe/meta-gnome/recipes-gnome/libgnome/libgnome-keyring_2.32.0.bb DESCRIPTION = Gnome keyring library LICENSE = LGPLv2 GPLv2 LIC_FILES_CHKSUM = file://COPYING.GPL;md5=94d55d512a9ba36caa9b7df079bae19f \ file://COPYING;md5=0914b9d3ebaba41ef2e3e0ae16f296cf SECTION = x11/gnome inherit gnome lib_package perlnative SRC_URI[archive.md5sum] = c42b2ca66204835d901d3dbfc1fa5ae6 SRC_URI[archive.sha256sum] = 56388c0d81ddfdb57d30e4963c83ecc1c18498aab99395420e0fff69929a0f0c What would be the steps to correct these errors. Thanks On Sun, Dec 8, 2013 at 12:20 PM, Khem Raj raj.k...@gmail.com wrote: On Sun, Dec 8, 2013 at 10:52 AM, Edward Vidal vidal.devel...@gmail.com wrote: /home/vidal/POKY/dylan_build/poky/meta-browser/recipes-gnome/gnome-settings-daemon/gnome-settings-daemon_2.32.1.bbappend you probably are missing meta-gnome in your BBLAYERS mix
[yocto] chkconfig
Hello all, Is chkconfig part of any image? Also to force what is the best procedure? In my /etc/network/interfaces I have tried the following auto eth0 iface eth0 inet static address 192.168.0.29 hwaddress ether 00:0A:35:00:00:00 netmask 255.255.255.0 network 192.168.0.0 gateway 192.168.0.1 Since I have a router on my network I get an IP using dhcp, if I ifdown eth0 and ifup eth0 then the 192.168.0.29 get setup. Thanks ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] dbus-glib gdk-pixbuf and python-pygobject errors
Hello all, My question is if the errors are in meta what does the priority of meta-xilinx play in the build? Also who should determine the priority of layers? The error would not manifest until the custom-image was used. The custum-image extended core-image-sato-sdk with v4l-utils boost qt-mobility-x11 gsl gnuplot gnuradio jasper lua5.1 fluidsynth liba52 x264 libmad vlc. After using the dylan branch and adding meta-oe/meta-oe, meta-oe/meta-multimedia, meta-xilinx, meta-xilinx/meta-kc705, meta-xilinx/meta-zc702, and meta-xilinx/meta-zedboard I was getting the following errors. After serveral attempts I lowered the priorty of meta-xilinx from 8 to 4. This appears to be the fix to my problem. Summary: 3 tasks failed: virtual:native:/home/vidal/POKY/dylan_build/poky/meta/recipes-core/dbus/ dbus-glib_0.100.2.bb, do_compile virtual:native:/home/vidal/POKY/dylan_build/poky/meta/recipes-gnome/gdk-pixbuf/ gdk-pixbuf_2.26.5.bb, do_compile virtual:native:/home/vidal/POKY/dylan_build/poky/meta/recipes-devtools/python/ python-pygobject_2.27.91.bb, do_compile Summary: There were 3 ERROR messages shown, returning a non-zero exit code. layer path priority == meta /home/vidal/POKY/dylan_build/poky/meta5 meta-yocto/home/vidal/POKY/dylan_build/poky/meta-yocto 5 meta-oe /home/vidal/POKY/dylan_build/poky/meta-oe/meta-oe 6 meta-multimedia /home/vidal/POKY/dylan_build/poky/meta-oe/meta-multimedia 6 meta-xilinx /home/vidal/POKY/dylan_build/poky/g...@github.com:gnuradio/gnuradio.git 8 meta-kc705 /home/vidal/POKY/dylan_build/poky/meta-xilinx/meta-kc705 8 meta-zc702 /home/vidal/POKY/dylan_build/poky/meta-xilinx/meta-zc702 8 meta-zedboard /home/vidal/POKY/dylan_build/poky/meta-xilinx/meta-zedboard 8 meta-yocto-bsp/home/vidal/POKY/dylan_build/poky/meta-yocto-bsp 5 lowered the priorty of meta-xilinx from 8 to 4 layer path priority == meta /home/vidal/POKY/dylan_build/poky/meta5 meta-yocto/home/vidal/POKY/dylan_build/poky/meta-yocto 5 meta-oe /home/vidal/POKY/dylan_build/poky/meta-oe/meta-oe 6 meta-multimedia /home/vidal/POKY/dylan_build/poky/meta-oe/meta-multimedia 6 meta-xilinx /home/vidal/POKY/dylan_build/poky/meta-xilinx 4 meta-kc705 /home/vidal/POKY/dylan_build/poky/meta-xilinx/meta-kc705 4 meta-zc702 /home/vidal/POKY/dylan_build/poky/meta-xilinx/meta-zc702 4 meta-zedboard /home/vidal/POKY/dylan_build/poky/meta-xilinx/meta-zedboard 4 meta-yocto-bsp/home/vidal/POKY/dylan_build/poky/meta-yocto-bsp 5 Any and all help is appreciated. ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] wrong version of busybox after adding new layers.
Hello, Gary Thomas recommended that I do a refresh meta-oe. I did git pull on poky meta-oe.both of these are dylan branch poky commit 4e399f08d596197859214fdb3b06403b87bf8789 Author: Chen Qi qi.c...@windriver.com Date: Fri Aug 30 10:31:42 2013 +0800 meta-oe commit 44754206632dd5b0725aeb43e99e4ff9e0245dca Author: Javier Viguera javier.vigu...@digi.com Date: Thu Sep 5 14:49:01 2013 + now with MACHINE=beagleboard bitbake core-image-sato I am getting the following error. ERROR: Task 3660 (virtual:native:/home/vidal/POKY/dylan_build/poky/meta/recipes-core/dbus/ dbus-glib_0.100.2.bb, do_compile) failed with exit code '1' My last successful build was poky commit 64273e53f2789d2ea8393fc80909ac7086f168a7 Author: Peter Kjellerstedt peter.kjellerst...@axis.com Date: Mon Jul 8 10:17:51 2013 +0100 meta-oe commit ed84e64d22400595b68da4e75b48ab7ecc342aa9 Author: Martin Jansa martin.ja...@gmail.com Date: Tue Jun 11 18:44:22 2013 +0200 When I try a build on my custom-image (added packages to core-image-sato-sdk) I get the following errors. ERROR: Task 5762 (virtual:native:/home/vidal/POKY/dylan_build/poky/meta/recipes-core/dbus/ dbus-glib_0.100.2.bb, do_compile) failed with exit code '1' ERROR: Function failed: do_compile (see /home/vidal/POKY/dylan_build/poky/build/tmp/work/x86_64-linux/python-pygobject-native/2.27.91-r6/temp/log.do_compile.952 for further information) ERROR: Logfile of failure stored in: /home/vidal/POKY/dylan_build/poky/build/tmp/work/x86_64-linux/python-pygobject-native/2.27.91-r6/temp/log.do_compile.952 Any and all help will be appreciated. thanks On Sun, Nov 17, 2013 at 5:17 PM, Edward Vidal vidal.devel...@gmail.comwrote: Hello, MACHINE=zedboard bitbake core-image-sato builds okay. Build Configuration: BB_VERSION= 1.19.1 BUILD_SYS = x86_64-linux NATIVELSBSTRING = Fedora-18 TARGET_SYS= arm-poky-linux-gnueabi MACHINE = zedboard DISTRO= poky DISTRO_VERSION= 1.4+snapshot-20131117 TUNE_FEATURES = armv7a vfp neon zynq TARGET_FPU= vfp-neon meta meta-yocto= wkg:3dee534f1e25109e0bdb681de0746c336f4b8840 meta-xilinx meta-kc705 meta-zc702 meta-zedboard = wkg:46f4c79d6d55b556a90bb0fd89c2c09acf2aebff meta-yocto-bsp= wkg:3dee534f1e25109e0bdb681de0746c336f4b8840 NOTE: Running noexec task 5589 of 5595 (ID: 3428, /home/vidal/POKY/build111613_zedboard/poky/meta/recipes-multimedia/gstreamer/ gst-meta-base_0.10.bb, do_build) NOTE: Running noexec task 5590 of 5595 (ID: 3103, /home/vidal/POKY/build111613_zedboard/poky/meta/recipes-multimedia/gstreamer/ gst-plugins-good_0.10.31.bb, do_build) NOTE: Running noexec task 5591 of 5595 (ID: 2804, /home/vidal/POKY/build111613_zedboard/poky/meta/recipes-sato/owl-video-widget/ libowl-av_git.bb, do_build) NOTE: Running noexec task 5592 of 5595 (ID: 1583, /home/vidal/POKY/build111613_zedboard/poky/meta/recipes-sato/gaku/ gaku_git.bb, do_build) NOTE: Running noexec task 5593 of 5595 (ID: 313, /home/vidal/POKY/build111613_zedboard/poky/meta/recipes-sato/packagegroups/ packagegroup-core-x11-sato.bb, do_build) NOTE: Running task 5594 of 5595 (ID: 7, /home/vidal/POKY/build111613_zedboard/poky/meta/recipes-sato/images/ core-image-sato.bb, do_rootfs) NOTE: recipe core-image-sato-1.0-r0: task do_rootfs: Started NOTE: recipe core-image-sato-1.0-r0: task do_rootfs: Succeeded NOTE: Running noexec task 5595 of 5595 (ID: 12, /home/vidal/POKY/build111613_zedboard/poky/meta/recipes-sato/images/ core-image-sato.bb, do_build) NOTE: Tasks Summary: Attempted 5595 tasks of which 404 didn't need to be rerun and all succeeded. busybox: meta 1.21.1 was used. After adding these 2 lines to bblayers.conf /home/vidal/POKY/build111613_zedboard/poky/meta-oe/meta-oe \ /home/vidal/POKY/build111613_zedboard/poky/meta-oe/meta-multimedia \ bitbake-layers show-layers layer path priority == meta /home/vidal/POKY/build111613_zedboard/poky/meta 5 meta-yocto /home/vidal/POKY/build111613_zedboard/poky/meta-yocto 5 meta-oe /home/vidal/POKY/build111613_zedboard/poky/meta-oe/meta-oe 6 meta-multimedia /home/vidal/POKY/build111613_zedboard/poky/meta-oe/meta-multimedia 6 meta-xilinx /home/vidal/POKY/build111613_zedboard/poky/meta-xilinx 8 meta-kc705 /home/vidal/POKY/build111613_zedboard/poky/meta-xilinx/meta-kc705 8 meta-zc702 /home/vidal/POKY/build111613_zedboard/poky/meta-xilinx/meta-zc702 8 meta-zedboard /home/vidal/POKY/build111613_zedboard/poky/meta-xilinx/meta-zedboard 8 meta-yocto-bsp /home/vidal/POKY/build111613_zedboard/poky/meta-yocto-bsp 5 [vidal@ws009 build]$ bitbake-layers show-recipes Parsing recipes..ERROR: No recipes available for: /home/vidal/POKY/build111613_zedboard/poky/meta-oe/meta-oe/recipes-core/busybox/busybox_1.20.2.bbappend What is the procedure to us
Re: [yocto] wrong version of busybox after adding new layers.
Hello, This is the first time that I have used the git bisect. I hope this helps git bisect start git bisect good 64273e53f2789d2ea8393fc80909ac7086f168a7 git bisect bad 4e399f08d596197859214fdb3b06403b87bf8789 secting: 43 revisions left to test after this (roughly 6 steps) [7a3b4c55410b49a02945c72b554102a483095405] gst-plugins-base: add missing dependency on glib-2.0-native git bisect bad Bisecting: 21 revisions left to test after this (roughly 5 steps) [b4ba3269102424b614d91ca8be10501176042f62] external-sourcery: add missing providers git bisect bad Bisecting: 10 revisions left to test after this (roughly 3 steps) [4d47a1e6445b2a4839bae7c3ba8fa69f1b32f602] gst-plugins-good: add PACKAGECONFIG for jack git bisect bad Bisecting: 4 revisions left to test after this (roughly 2 steps) [dea3e6964949c2d7269570d2f19c74033e54200e] mesa: fix EGL compilation without X11 headers git bisect isecting: 2 revisions left to test after this (roughly 1 step) [d6d12689c0628f11a282c2b54ebcb8aa3ab8c673] populate_sdk_base: fix bashism git bisect bad Bisecting: 0 revisions left to test after this (roughly 0 steps) [eb5ec8899d41d2df7fb9d9918d2d93042a678d97] populate_sdk_base, adt_installer: abort install if path contains spaces git bisect bad eb5ec8899d41d2df7fb9d9918d2d93042a678d97 is the first bad commit commit eb5ec8899d41d2df7fb9d9918d2d93042a678d97 Author: Laurentiu Palcu laurentiu.pa...@intel.com Date: Tue Jun 25 14:59:05 2013 +0300 populate_sdk_base, adt_installer: abort install if path contains spaces Spaces are not handled properly in some parts of oe-core and it's safer to abort toolchain installation if path contains spaces. Even though we fix space handling in the toolchain installation script, there are various other parts in the toolchain (perl scripts, sysroot path passed to toolchain binaries, shebang lines) that would need special handling. So, for now, just bail out if path contains spaces. The checking for spaces in the path is done after expanding relative paths to absolute and tilde conversion. [YOCTO #4488] (From OE-Core master rev: 8c35ba2d3048ce69f74f72cb2676e4bc162cfb63) (From OE-Core rev: 407e57879ea2f931bff32993b850c9d59d228303) Signed-off-by: Laurentiu Palcu laurentiu.pa...@intel.com Signed-off-by: Richard Purdie richard.pur...@linuxfoundation.org :04 04 d48370d500ce89a9b3ba7194b5e5beda216a926d db610074307067f3882a9faabb342fe2a541 M meta I hope this helps. As always all help is appreciated. Thanks On Mon, Nov 18, 2013 at 1:09 PM, Edward Vidal vidal.devel...@gmail.comwrote: Hello, Gary Thomas recommended that I do a refresh meta-oe. I did git pull on poky meta-oe.both of these are dylan branch poky commit 4e399f08d596197859214fdb3b06403b87bf8789 Author: Chen Qi qi.c...@windriver.com Date: Fri Aug 30 10:31:42 2013 +0800 meta-oe commit 44754206632dd5b0725aeb43e99e4ff9e0245dca Author: Javier Viguera javier.vigu...@digi.com Date: Thu Sep 5 14:49:01 2013 + now with MACHINE=beagleboard bitbake core-image-sato I am getting the following error. ERROR: Task 3660 (virtual:native:/home/vidal/POKY/dylan_build/poky/meta/recipes-core/dbus/ dbus-glib_0.100.2.bb, do_compile) failed with exit code '1' My last successful build was poky commit 64273e53f2789d2ea8393fc80909ac7086f168a7 Author: Peter Kjellerstedt peter.kjellerst...@axis.com Date: Mon Jul 8 10:17:51 2013 +0100 meta-oe commit ed84e64d22400595b68da4e75b48ab7ecc342aa9 Author: Martin Jansa martin.ja...@gmail.com Date: Tue Jun 11 18:44:22 2013 +0200 When I try a build on my custom-image (added packages to core-image-sato-sdk) I get the following errors. ERROR: Task 5762 (virtual:native:/home/vidal/POKY/dylan_build/poky/meta/recipes-core/dbus/ dbus-glib_0.100.2.bb, do_compile) failed with exit code '1' ERROR: Function failed: do_compile (see /home/vidal/POKY/dylan_build/poky/build/tmp/work/x86_64-linux/python-pygobject-native/2.27.91-r6/temp/log.do_compile.952 for further information) ERROR: Logfile of failure stored in: /home/vidal/POKY/dylan_build/poky/build/tmp/work/x86_64-linux/python-pygobject-native/2.27.91-r6/temp/log.do_compile.952 Any and all help will be appreciated. thanks On Sun, Nov 17, 2013 at 5:17 PM, Edward Vidal vidal.devel...@gmail.comwrote: Hello, MACHINE=zedboard bitbake core-image-sato builds okay. Build Configuration: BB_VERSION= 1.19.1 BUILD_SYS = x86_64-linux NATIVELSBSTRING = Fedora-18 TARGET_SYS= arm-poky-linux-gnueabi MACHINE = zedboard DISTRO= poky DISTRO_VERSION= 1.4+snapshot-20131117 TUNE_FEATURES = armv7a vfp neon zynq TARGET_FPU= vfp-neon meta meta-yocto= wkg:3dee534f1e25109e0bdb681de0746c336f4b8840 meta-xilinx meta-kc705 meta-zc702 meta-zedboard = wkg:46f4c79d6d55b556a90bb0fd89c2c09acf2aebff meta-yocto-bsp= wkg:3dee534f1e25109e0bdb681de0746c336f4b8840 NOTE: Running noexec task 5589
Re: [yocto] wrong version of busybox after adding new layers.
Hello Still was getting error. Thinking it might be my download area. Started with a clean down load area and new work area. Build Configuration: BB_VERSION= 1.18.0 BUILD_SYS = x86_64-linux NATIVELSBSTRING = Fedora-18 TARGET_SYS= arm-poky-linux-gnueabi MACHINE = zedboard DISTRO= poky DISTRO_VERSION= 1.4.2 TUNE_FEATURES = armv7a vfp neon zynq TARGET_FPU= vfp-neon meta meta-yocto= dylan:4e399f08d596197859214fdb3b06403b87bf8789 meta-oe meta-multimedia = dylan:44754206632dd5b0725aeb43e99e4ff9e0245dca meta-xilinx meta-kc705 meta-zc702 meta-zedboard = dylan:cf9571203be0af5fc654952d3f00e0a7e0fb1174 meta-yocto-bsp= dylan:4e399f08d596197859214fdb3b06403b87bf8789 ERROR: Function failed: Fetcher failure for URL: ' http://files.ettus.com/binaries/uhd_stable/releases/uhd_003.005.002-release/uhd-images_003.005.002-release.tar.gz'. Unable to fetch URL from any source. uhd-images_003.005.002-release.tar.gz_bad-checksum_2912c1c7cde099f2671f2f8f24879b82 Downloaded manually and in fact the md5sum is shown below Can someone please pass to meta-oe since this site is currently blocked to new u sers. md5sum uhd-images_003.005.002-release.tar.gz 2912c1c7cde099f2671f2f8f24879b82 uhd-images_003.005.002-release.tar.gz Any and all help is appreciated. Thanks On Mon, Nov 18, 2013 at 4:10 PM, Edward Vidal vidal.devel...@gmail.comwrote: Hello, This is the first time that I have used the git bisect. I hope this helps git bisect start git bisect good 64273e53f2789d2ea8393fc80909ac7086f168a7 git bisect bad 4e399f08d596197859214fdb3b06403b87bf8789 secting: 43 revisions left to test after this (roughly 6 steps) [7a3b4c55410b49a02945c72b554102a483095405] gst-plugins-base: add missing dependency on glib-2.0-native git bisect bad Bisecting: 21 revisions left to test after this (roughly 5 steps) [b4ba3269102424b614d91ca8be10501176042f62] external-sourcery: add missing providers git bisect bad Bisecting: 10 revisions left to test after this (roughly 3 steps) [4d47a1e6445b2a4839bae7c3ba8fa69f1b32f602] gst-plugins-good: add PACKAGECONFIG for jack git bisect bad Bisecting: 4 revisions left to test after this (roughly 2 steps) [dea3e6964949c2d7269570d2f19c74033e54200e] mesa: fix EGL compilation without X11 headers git bisect isecting: 2 revisions left to test after this (roughly 1 step) [d6d12689c0628f11a282c2b54ebcb8aa3ab8c673] populate_sdk_base: fix bashism git bisect bad Bisecting: 0 revisions left to test after this (roughly 0 steps) [eb5ec8899d41d2df7fb9d9918d2d93042a678d97] populate_sdk_base, adt_installer: abort install if path contains spaces git bisect bad eb5ec8899d41d2df7fb9d9918d2d93042a678d97 is the first bad commit commit eb5ec8899d41d2df7fb9d9918d2d93042a678d97 Author: Laurentiu Palcu laurentiu.pa...@intel.com Date: Tue Jun 25 14:59:05 2013 +0300 populate_sdk_base, adt_installer: abort install if path contains spaces Spaces are not handled properly in some parts of oe-core and it's safer to abort toolchain installation if path contains spaces. Even though we fix space handling in the toolchain installation script, there are various other parts in the toolchain (perl scripts, sysroot path passed to toolchain binaries, shebang lines) that would need special handling. So, for now, just bail out if path contains spaces. The checking for spaces in the path is done after expanding relative paths to absolute and tilde conversion. [YOCTO #4488] (From OE-Core master rev: 8c35ba2d3048ce69f74f72cb2676e4bc162cfb63) (From OE-Core rev: 407e57879ea2f931bff32993b850c9d59d228303) Signed-off-by: Laurentiu Palcu laurentiu.pa...@intel.com Signed-off-by: Richard Purdie richard.pur...@linuxfoundation.org :04 04 d48370d500ce89a9b3ba7194b5e5beda216a926d db610074307067f3882a9faabb342fe2a541 M meta I hope this helps. As always all help is appreciated. Thanks On Mon, Nov 18, 2013 at 1:09 PM, Edward Vidal vidal.devel...@gmail.comwrote: Hello, Gary Thomas recommended that I do a refresh meta-oe. I did git pull on poky meta-oe.both of these are dylan branch poky commit 4e399f08d596197859214fdb3b06403b87bf8789 Author: Chen Qi qi.c...@windriver.com Date: Fri Aug 30 10:31:42 2013 +0800 meta-oe commit 44754206632dd5b0725aeb43e99e4ff9e0245dca Author: Javier Viguera javier.vigu...@digi.com Date: Thu Sep 5 14:49:01 2013 + now with MACHINE=beagleboard bitbake core-image-sato I am getting the following error. ERROR: Task 3660 (virtual:native:/home/vidal/POKY/dylan_build/poky/meta/recipes-core/dbus/ dbus-glib_0.100.2.bb, do_compile) failed with exit code '1' My last successful build was poky commit 64273e53f2789d2ea8393fc80909ac7086f168a7 Author: Peter Kjellerstedt peter.kjellerst...@axis.com Date: Mon Jul 8 10:17:51 2013 +0100 meta-oe commit ed84e64d22400595b68da4e75b48ab7ecc342aa9 Author: Martin Jansa
[yocto] wrong version of busybox after adding new layers.
Hello, MACHINE=zedboard bitbake core-image-sato builds okay. Build Configuration: BB_VERSION= 1.19.1 BUILD_SYS = x86_64-linux NATIVELSBSTRING = Fedora-18 TARGET_SYS= arm-poky-linux-gnueabi MACHINE = zedboard DISTRO= poky DISTRO_VERSION= 1.4+snapshot-20131117 TUNE_FEATURES = armv7a vfp neon zynq TARGET_FPU= vfp-neon meta meta-yocto= wkg:3dee534f1e25109e0bdb681de0746c336f4b8840 meta-xilinx meta-kc705 meta-zc702 meta-zedboard = wkg:46f4c79d6d55b556a90bb0fd89c2c09acf2aebff meta-yocto-bsp= wkg:3dee534f1e25109e0bdb681de0746c336f4b8840 NOTE: Running noexec task 5589 of 5595 (ID: 3428, /home/vidal/POKY/build111613_zedboard/poky/meta/recipes-multimedia/gstreamer/ gst-meta-base_0.10.bb, do_build) NOTE: Running noexec task 5590 of 5595 (ID: 3103, /home/vidal/POKY/build111613_zedboard/poky/meta/recipes-multimedia/gstreamer/ gst-plugins-good_0.10.31.bb, do_build) NOTE: Running noexec task 5591 of 5595 (ID: 2804, /home/vidal/POKY/build111613_zedboard/poky/meta/recipes-sato/owl-video-widget/ libowl-av_git.bb, do_build) NOTE: Running noexec task 5592 of 5595 (ID: 1583, /home/vidal/POKY/build111613_zedboard/poky/meta/recipes-sato/gaku/ gaku_git.bb, do_build) NOTE: Running noexec task 5593 of 5595 (ID: 313, /home/vidal/POKY/build111613_zedboard/poky/meta/recipes-sato/packagegroups/ packagegroup-core-x11-sato.bb, do_build) NOTE: Running task 5594 of 5595 (ID: 7, /home/vidal/POKY/build111613_zedboard/poky/meta/recipes-sato/images/ core-image-sato.bb, do_rootfs) NOTE: recipe core-image-sato-1.0-r0: task do_rootfs: Started NOTE: recipe core-image-sato-1.0-r0: task do_rootfs: Succeeded NOTE: Running noexec task 5595 of 5595 (ID: 12, /home/vidal/POKY/build111613_zedboard/poky/meta/recipes-sato/images/ core-image-sato.bb, do_build) NOTE: Tasks Summary: Attempted 5595 tasks of which 404 didn't need to be rerun and all succeeded. busybox: meta 1.21.1 was used. After adding these 2 lines to bblayers.conf /home/vidal/POKY/build111613_zedboard/poky/meta-oe/meta-oe \ /home/vidal/POKY/build111613_zedboard/poky/meta-oe/meta-multimedia \ bitbake-layers show-layers layer path priority == meta /home/vidal/POKY/build111613_zedboard/poky/meta 5 meta-yocto /home/vidal/POKY/build111613_zedboard/poky/meta-yocto 5 meta-oe /home/vidal/POKY/build111613_zedboard/poky/meta-oe/meta-oe 6 meta-multimedia /home/vidal/POKY/build111613_zedboard/poky/meta-oe/meta-multimedia 6 meta-xilinx /home/vidal/POKY/build111613_zedboard/poky/meta-xilinx 8 meta-kc705 /home/vidal/POKY/build111613_zedboard/poky/meta-xilinx/meta-kc705 8 meta-zc702 /home/vidal/POKY/build111613_zedboard/poky/meta-xilinx/meta-zc702 8 meta-zedboard /home/vidal/POKY/build111613_zedboard/poky/meta-xilinx/meta-zedboard 8 meta-yocto-bsp /home/vidal/POKY/build111613_zedboard/poky/meta-yocto-bsp 5 [vidal@ws009 build]$ bitbake-layers show-recipes Parsing recipes..ERROR: No recipes available for: /home/vidal/POKY/build111613_zedboard/poky/meta-oe/meta-oe/recipes-core/busybox/busybox_1.20.2.bbappend What is the procedure to us busybox_1.20.2 with the new layers? Any and all help is appreciated. Thanks ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] meta data sources
Hello, I am trying to determine which meta data to use. I am currently using meta-oe/meta-oe and meta-oe/meta-multimedia see below git log at meta-oe commit ed84e64d22400595b68da4e75b48ab7ecc342aa9 Author: Martin Jansa martin.ja...@gmail.com Date: Tue Jun 11 18:44:22 2013 +0200 openssh: Rename bbappend to match new version from oe-core Signed-off-by: Martin Jansa martin.ja...@gmail.com The beagleboard build is used to generate the RPMs for my zedboard this add 159 RPMs to provide v4l-utils boost qt-mobility-x11 gsl gnuplot gnuradio jasper lua5.1 fluidsynth liba52 x264 libmad vlc Build Configuration: BB_VERSION= 1.18.0 BUILD_SYS = x86_64-linux NATIVELSBSTRING = Fedora-18 TARGET_SYS= arm-poky-linux-gnueabi MACHINE = beagleboard DISTRO= poky DISTRO_VERSION= 1.4.1 TUNE_FEATURES = armv7a vfp neon TARGET_FPU= vfp-neon meta meta-yocto= wkg_dylan:64273e53f2789d2ea8393fc80909ac7086f168a7 meta-oe meta-multimedia = wkg_dylan:ed84e64d22400595b68da4e75b48ab7ecc342aa9 meta-java = wkg_dylan:59696d89fd33df6953dcb2dd54ccd3b362513f28 meta-yocto-bsp= wkg_dylan:64273e53f2789d2ea8393fc80909ac7086f168a7 I am adding to custom core-image-sato-sdk the following items. v4l-utils boost qt-mobility-x11 gsl gnuplot gnuradio jasper lua5.1 fluidsynth liba52 x264 libmad vlc this required in local.conf LICENSE_FLAGS_WHITELIST = commercial_libmad commercial_mpeg2dec to get the packages to build. I noticed that angstrom uses meta-openembedded/meta-oe and meta-openembedded/meta-multimedia Any and all help is appreciated. Thanks ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Yocto zedboard v4l-utils 3.6.0 kernel with C920 webcam sucess
Hello all, I finally was able to get the modules needed to support the C920 webcam. The modules needed were a total of eight. tree 3.6.0-digilent-13.01-2-g06b3889 3.6.0-digilent-13.01-2-g06b3889 ├── kernel │ └── drivers │ └── media │ └── video │ ├── gspca │ │ └── gspca_main.ko │ ├── uvc │ │ └── uvcvideo.ko │ ├── v4l2-common.ko │ ├── v4l2-int-device.ko │ ├── videobuf2-core.ko │ ├── videobuf2-memops.ko │ ├── videobuf2-vmalloc.ko │ └── videodev.ko ├── myled.ko └── pmodoled-gpio.ko 6 directories, 10 files I built the core-image-sato for the zedboard which installed 1463 RPMs. I built a core-image-sato-sdk for the beagleboard with boost qt-mobility-x11 gsl gnuplot gnuradio boost, v4l-utils and python-netserver which I installed with the rpm command increased the package count to 1559. I used the boneCV for capture routine Modifications, added the -F mode for H264 capture and associated help detail * www.derekmolloy.ie on the zedboard and raw2mpg4 on Fedora18x86_64. ffmpeg is my next task. git remote show origin * remote origin Fetch URL: https://github.com/derekmolloy/boneCV.git Push URL: https://github.com/derekmolloy/boneCV.git HEAD branch: master Remote branch: master tracked Local branch configured for 'git pull': master merges with remote master Local ref configured for 'git push': master pushes to master (up to date) Thanks all for all the support. ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] dora 1.5 builds for beagleboard no lsusb, /dev/fb0, networking, or sato display on monitor.
Hello All, This is a continued effort with adding a udev entry for a camera uImage instead of zImage posting in Oct 13. 2 of my with dora 1.5 are showing same problem lsusb --verbose unable to initialize libusb: -99 Error opening /dev/fb0: No such file or directory during boot. These builds have no networking or sato display. The kernel 3.10.11 works with a dylan 1,4 but no /dev/video0 This was what I ended up with in my uEnv.txt to boot the zImage instead of uImage dvimode=hd720 omapfb.vram=0:8M,1:4M,2:4M loaduimage=run mmcargs;mmc rescan ; fatload mmc 0:1 0x8030 zImage vram=16M mpurate=1000 mmcboot=echo Booting from mmc ...; bootz 0x8030 Now I do not have manually run mmcboot The new file that was introduce with dora 1.5 *.dtb. Does this just need to be in the same place as MLO u-boot.img or u-boot.bin, uEnv.txt and zImage. Is anything needed in the bootargs or other env variables? A question had been asked by Diego Sueiro about a module uvcvideo which in not in any of the kernels that I have been working with 3.2.28 (an angstrom build), 3.4.43 (dylan 1.4.1) or 3.10.11 (dora 1.5.0). If anyone know which kernel my have the code and what would be the configuration options that would be welcomed. Any and all help will be appreciated. Thanks commit faf8f8660fae26a14578738b642fdeb08bcb9d54 Author: Richard Purdie richard.pur...@linuxfoundation.org Date: Fri Oct 11 23:12:32 2013 +0100 BB_VERSION= 1.20.0 BUILD_SYS = x86_64-linux NATIVELSBSTRING = Fedora-18 TARGET_SYS= arm-poky-linux-gnueabi MACHINE = beagleboard DISTRO= poky DISTRO_VERSION= 1.5 TUNE_FEATURES = armv7a vfp neon TARGET_FPU= vfp-neon meta meta-yocto= wkg_dora:faf8f8660fae26a14578738b642fdeb08bcb9d54 meta-oe = wkg-dora:513e7ca20ddd0a5c3b649bf292a67c3e0473d3a8 meta-yocto-bsp= wkg_dora:faf8f8660fae26a14578738b642fdeb08bcb9d54 commit 75bed4086eb83f1d24c31392f3dd54aa5c3679b1 Author: Maxin B. John maxin.j...@enea.com Date: Thu Oct 31 15:01:25 2013 + BB_VERSION= 1.20.0 BUILD_SYS = x86_64-linux NATIVELSBSTRING = Fedora-18 TARGET_SYS= arm-poky-linux-gnueabi MACHINE = beagleboard DISTRO= poky DISTRO_VERSION= 1.5 TUNE_FEATURES = armv7a vfp neon TARGET_FPU= vfp-neon meta meta-yocto= wkg_dora:75bed4086eb83f1d24c31392f3dd54aa5c3679b1 meta-oe = wkg-dora:513e7ca20ddd0a5c3b649bf292a67c3e0473d3a8 meta-yocto-bsp= wkg_dora:75bed4086eb83f1d24c31392f3dd54aa5c3679b1 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] adding a udev entry for a camera
Hello All,
Some progress getting the zImage to boot which was another problem before
not getting /dev/video0.
for the camera.
I have been trying to get 3.10.11 from dora to boot.
This kinda of works the following is in my uEnv.txt.
vram=16M
mpurate=1000
mmcboot=echo Booting from mmc ...; run mmcargs;mmc rescan ; fatload mmc 0:1
0x8030 zImage; bootz 0x8030
This will now boot with the command run mmcboot
These are the files on my /run/media/vidal/BOOT
3.2.28 3.4.43 MLO u-boot.img uEnv.txt zImage.
With 3.2.28 and 3.4.43 I was just switching uImage,.u-boot.bin MLO worked
okay with either kernel.
With 3.10.11 I needed to replace uImage with zImage and MLO and u-boot.img
This kernel is not working as well as 3.4.36 no lsusb
root@beagleboard:~# lsusb --verbose
unable to initialize libusb: -99
No /dev/video0.
see attached.
My next steps will be using the rootfs that was built with dora and 3.10.11
kernel,
I will be adding the zImage-omap3-beagle-xm.dtb that was introduce with my
dora.
The attached file has the boot and dmesg.
Any any all help will be welcomed..
Have a great weekend
On Thu, Oct 31, 2013 at 5:27 PM, Diego Sueiro diego.sue...@gmail.comwrote:
Edward,
Is uvcvideo module loaded?
What is lsmod and dmesg output when webcam is connected?
Regards,
--
*dS
Diego Sueiro
/*long live rock 'n roll*/
2013/10/31 Edward Vidal vidal.devel...@gmail.com
Hello,
I had just recently built angstrom a few days ago. I tried the kernel
that was built with 3.2.28 with the same results still not getting a
/dev/video0.
I did the following steps since angstrom uses meta-beagleboard, in hopes
of getting a kernel 3.8 version.
git commit -a
git checkout -b wkg-angstrom-v2013.06-yocto1.4
origin/angstrom-v2013.06-yocto1.4
./oebb.sh config beagleboard
./oebb.sh update
. .oe/environment-angstrom-v2013.06
MACHINE=beagleboard bitbake console-image
rm -rf build/tmp-angstrom_v2012_12-eglibc/
Even with meta-beagleboard at
commit cdaa65dba20da97be7793404bcc90c498771fb04
Author: Koen Kooi k...@dominion.thruhere.net
Date: Wed Oct 30 18:31:21 2013 +0100
contrib: bone-flash-tool: use --numeric-owner with tar to keep file
ownershi
Signed-off-by: Koen Kooi k...@dominion.thruhere.net
Which is a dylan branch it still was building a 3.2.28 kernel
git checkout -b 3.8 feb3ea180018d0f
commit feb3ea180018d0f64f406f208827413b91122b07
Author: Koen Kooi k...@dominion.thruhere.net
Date: Sun Oct 27 17:17:06 2013 +0100
linux-mainline 3.8: ADC and MIDI cape patches
Signed-off-by: Koen Kooi k...@dominion.thruhere.net
It still tries to build a 3.2.28 kernel.
What should I do to force it to build the 3.8 kernel?
Any and all help will be appreciated.
Thanks to all
On Thu, Oct 31, 2013 at 11:08 AM, Khem Raj raj.k...@gmail.com wrote:
On Thu, Oct 31, 2013 at 9:54 AM, Edward Vidal vidal.devel...@gmail.com
wrote:
hello,
I removed the bus
udevadm test --action=add /usr/src/kernel/sysfs
run_command: calling: test
adm_test: version 182
This program is for debugging only, it does not run any program,
specified by a RUN key. It may show incorrect results, because
some values may be different, or not available at a simulation run.
builtin_kmod_init: load module index
add_matching_files: unable to open '/var/run/udev/rules.d': No such
file or
directory
parse_file: reading '/etc/udev/rules.d/10-c920.rules' as rules file
still no /dev/video0
cat /etc/udev/rules.d/10-c920.rules
SUBSYSTEM==video4linux, ATTRS{idvendor}==0x046d,
ATTRS{idProduct}==0x082d, NAME=video0, MODE:=0660,
RUN=/bin/mknod
/dev/video0 c 81 0
still no /dev/video0
The camera is working correctly on my fedora 18 x86_64.
OK so atleast your rules file is correct syntax wise. Why not try the
3.8 kernel from meta-beagleboard ?
Note:
* Before camera connected
** After camera connected
Linux sim4.swbell.net 3.9.2-200.fc18.x86_64 #1 SMP Mon May 13
13:59:47 UTC
2013 x86_64 x86_64 x86_64 GNU/Linux
Module Size Used by
**snd_usb_audio 145223 1
**snd_usbmidi_lib24713 1 snd_usb_audio
**snd_rawmidi29531 1 snd_usbmidi_lib
*snd_hwdep 17650 1 snd_hda_codec
**snd_hwdep 17650 2 snd_usb_audio,snd_hda_codec
*snd_seq_device 14136 1 snd_seq
**snd_seq_device 14136 2 snd_seq,snd_rawmidi
*snd79379 19
snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_hda_codec,snd_hda_intel,snd_seq_device
**snd79379 24
snd_hda_codec_realtek,snd_usb_audio,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_rawmidi,snd_usbmidi_lib,snd_hda_codec,snd_hda_intel,snd_seq_device
*video 18991 0
**video 18991 0
This is the beagleboard
lsmod
Module Size Used by
nls_iso8859_1 3673 1
nls_cp437 5339 1
Re: [yocto] adding a udev entry for a camera
Hello all,
less /etc/udev/rules.d/10-c920.rules
WARNING: terminal is not fully functional
SUBSYSTEM==video4linux, BUS==usb, ATTRS{idvendor}==0x046d,
ATTRS{idProduct
}==0x082d, NAME=video0, MODE:=0660
It appears the key BUS is not correct based on the tests below.
My mknod is /bin/mknod.
find / -name sysfs
/usr/include/sysfs
/usr/src/kernel/fs/sysfs
udevadm test --action=add /usr/include/sysfs or udevadm test --action=add
/usr/src/kernel/fs/sysfs unable to open device
'/sys/usr/src/kernel/fs/sysfs'
run_command: calling: test
adm_test: version 182
This program is for debugging only, it does not run any program,
specified by a RUN key. It may show incorrect results, because
some values may be different, or not available at a simulation run.
builtin_kmod_init: load module index
add_matching_files: unable to open '/var/run/udev/rules.d': No such file or
directory
parse_file: reading '/etc/udev/rules.d/10-c920.rules' as rules file
add_rule: unknown key 'BUS' in /etc/udev/rules.d/10-c920.rules:1
add_rule: invalid rule '/etc/udev/rules.d/10-c920.rules:1'
lots of output
udev_rules_new: rules use 18408 bytes tokens (1534 * 12 bytes), 12756 bytes
buffer
udev_rules_new: temporary index used 12800 bytes (640 * 20 bytes)
unable to open device '/sys/usr/include/sysfs'
builtin_kmod_exit: unload module index
Do I add RUN+=/bin/mknod /dev/video0 c 81 0 see below new version of
1--c920.rules
cat 10-c920.rules
SUBSYSTEM==video4linux, BUS==usb, ATTRS{idvendor}==0x046d,
ATTRS{idProduct}==0x082d, NAME=video0, MODE:=0660, RUN+=/bin/mknod
/dev/video0 c 81 0
udevadm test --action=add /usr/src/kernel/fs/sysfs
run_command: calling: test
adm_test: version 182
This program is for debugging only, it does not run any program,
specified by a RUN key. It may show incorrect results, because
some values may be different, or not available at a simulation run.
builtin_kmod_init: load module index
add_matching_files: unable to open '/var/run/udev/rules.d': No such file or
directory
parse_file: reading '/etc/udev/rules.d/10-c920.rules' as rules file
add_rule: unknown key 'BUS' in /etc/udev/rules.d/10-c920.rules:1
add_rule: invalid rule '/etc/udev/rules.d/10-c920.rules:1'
Where do you find information for working with rules other than just some
examples?
Thanks
On Thu, Oct 31, 2013 at 8:41 AM, Khem Raj raj.k...@gmail.com wrote:
On Wed, Oct 30, 2013 at 6:12 PM, Edward Vidal vidal.devel...@gmail.com
wrote:
Hello,
This is when I connect the camera
udevadm monitor test
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent
KERNEL[803.263336] add
/devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4 (usb)
KERNEL[803.267456] add
/devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.0
(usb)
KERNEL[803.269287] add
/devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.1
(usb)
KERNEL[803.269958] add
/devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.2
(usb)
KERNEL[803.270721] add
/devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.3
(usb)
KERNEL[803.276214] add
/devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/usb_device/usbdev1.15
(usb_device)**
UDEV [803.277191] add
/devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4 (usb)
UDEV [803.306091] add
/devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/usb_device/usbdev1.15
(usb_device)
UDEV [803.318603] add
/devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.2
(usb)
UDEV [803.324249] add
/devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.1
(usb)
UDEV [803.329712] add
/devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.0
(usb)
UDEV [803.333160] add
/devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.3
(usb)
still no /dev/video0
ls -la /dev/v*
crw-rw 1 root tty 7, 0 Jan 1 2000 /dev/vcs
crw-rw 1 root tty 7, 1 Jan 1 2000 /dev/vcs1
crw-rw 1 root tty 7, 2 Jan 1 2000 /dev/vcs2
crw-rw 1 root tty 7, 3 Oct 29 13:51 /dev/vcs3
crw-rw 1 root tty 7, 128 Jan 1 2000 /dev/vcsa
crw-rw 1 root tty 7, 129 Jan 1 2000 /dev/vcsa1
crw-rw 1 root tty 7, 130 Jan 1 2000 /dev/vcsa2
crw-rw 1 root tty 7, 131 Oct 29 13:51 /dev/vcsa3
root@beagleboard:~# lsusb
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 004: ID 0409:0059 NEC Corp. HighSpeed Hub
Bus 001 Device 005: ID 413c:2005 Dell Computer Corp. RT7D50 Keyboard
Bus 001 Device 006: ID 046d:c001 Logitech, Inc. N48/M-BB48 [FirstMouse
Plus]
Bus 001 Device 015: ID 046d:082d Logitech
Re: [yocto] adding a udev entry for a camera
hello,
I removed the bus
udevadm test --action=add /usr/src/kernel/sysfs
run_command: calling: test
adm_test: version 182
This program is for debugging only, it does not run any program,
specified by a RUN key. It may show incorrect results, because
some values may be different, or not available at a simulation run.
builtin_kmod_init: load module index
add_matching_files: unable to open '/var/run/udev/rules.d': No such file or
directory
parse_file: reading '/etc/udev/rules.d/10-c920.rules' as rules file
still no /dev/video0
cat /etc/udev/rules.d/10-c920.rules
SUBSYSTEM==video4linux, ATTRS{idvendor}==0x046d,
ATTRS{idProduct}==0x082d, NAME=video0, MODE:=0660, RUN=/bin/mknod
/dev/video0 c 81 0
still no /dev/video0
The camera is working correctly on my fedora 18 x86_64.
Note:
* Before camera connected
** After camera connected
Linux sim4.swbell.net 3.9.2-200.fc18.x86_64 #1 SMP Mon May 13 13:59:47 UTC
2013 x86_64 x86_64 x86_64 GNU/Linux
Module Size Used by
**snd_usb_audio 145223 1
**snd_usbmidi_lib24713 1 snd_usb_audio
**snd_rawmidi29531 1 snd_usbmidi_lib
*snd_hwdep 17650 1 snd_hda_codec
**snd_hwdep 17650 2 snd_usb_audio,snd_hda_codec
*snd_seq_device 14136 1 snd_seq
**snd_seq_device 14136 2 snd_seq,snd_rawmidi
*snd79379 19
snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_hda_codec,snd_hda_intel,snd_seq_device
**snd79379 24
snd_hda_codec_realtek,snd_usb_audio,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_rawmidi,snd_usbmidi_lib,snd_hda_codec,snd_hda_intel,snd_seq_device
*video 18991 0
**video 18991 0
This is the beagleboard
lsmod
Module Size Used by
nls_iso8859_1 3673 1
nls_cp437 5339 1
I am going to be checking the video is a module or built into the kernel of
the
uname -a
Linux beagleboard 3.4.36-yocto-standard #1 Mon Oct 28 21:58:22 MDT 2013
armv7l GNU/Linux
Thanks
On Thu, Oct 31, 2013 at 10:23 AM, Khem Raj raj.k...@gmail.com wrote:
On Thu, Oct 31, 2013 at 8:45 AM, Edward Vidal vidal.devel...@gmail.com
wrote:
Do I add RUN+=/bin/mknod /dev/video0 c 81 0 see below new version of
1--c920.rules
cat 10-c920.rules
SUBSYSTEM==video4linux, BUS==usb, ATTRS{idvendor}==0x046d,
ATTRS{idProduct}==0x082d, NAME=video0, MODE:=0660, RUN+=/bin/mknod
/dev/video0 c 81 0
get rid of BUS construct there
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] adding a udev entry for a camera
Hello,
I had just recently built angstrom a few days ago. I tried the kernel that
was built with 3.2.28 with the same results still not getting a /dev/video0.
I did the following steps since angstrom uses meta-beagleboard, in hopes of
getting a kernel 3.8 version.
git commit -a
git checkout -b wkg-angstrom-v2013.06-yocto1.4
origin/angstrom-v2013.06-yocto1.4
./oebb.sh config beagleboard
./oebb.sh update
. .oe/environment-angstrom-v2013.06
MACHINE=beagleboard bitbake console-image
rm -rf build/tmp-angstrom_v2012_12-eglibc/
Even with meta-beagleboard at
commit cdaa65dba20da97be7793404bcc90c498771fb04
Author: Koen Kooi k...@dominion.thruhere.net
Date: Wed Oct 30 18:31:21 2013 +0100
contrib: bone-flash-tool: use --numeric-owner with tar to keep file
ownershi
Signed-off-by: Koen Kooi k...@dominion.thruhere.net
Which is a dylan branch it still was building a 3.2.28 kernel
git checkout -b 3.8 feb3ea180018d0f
commit feb3ea180018d0f64f406f208827413b91122b07
Author: Koen Kooi k...@dominion.thruhere.net
Date: Sun Oct 27 17:17:06 2013 +0100
linux-mainline 3.8: ADC and MIDI cape patches
Signed-off-by: Koen Kooi k...@dominion.thruhere.net
It still tries to build a 3.2.28 kernel.
What should I do to force it to build the 3.8 kernel?
Any and all help will be appreciated.
Thanks to all
On Thu, Oct 31, 2013 at 11:08 AM, Khem Raj raj.k...@gmail.com wrote:
On Thu, Oct 31, 2013 at 9:54 AM, Edward Vidal vidal.devel...@gmail.com
wrote:
hello,
I removed the bus
udevadm test --action=add /usr/src/kernel/sysfs
run_command: calling: test
adm_test: version 182
This program is for debugging only, it does not run any program,
specified by a RUN key. It may show incorrect results, because
some values may be different, or not available at a simulation run.
builtin_kmod_init: load module index
add_matching_files: unable to open '/var/run/udev/rules.d': No such file
or
directory
parse_file: reading '/etc/udev/rules.d/10-c920.rules' as rules file
still no /dev/video0
cat /etc/udev/rules.d/10-c920.rules
SUBSYSTEM==video4linux, ATTRS{idvendor}==0x046d,
ATTRS{idProduct}==0x082d, NAME=video0, MODE:=0660, RUN=/bin/mknod
/dev/video0 c 81 0
still no /dev/video0
The camera is working correctly on my fedora 18 x86_64.
OK so atleast your rules file is correct syntax wise. Why not try the
3.8 kernel from meta-beagleboard ?
Note:
* Before camera connected
** After camera connected
Linux sim4.swbell.net 3.9.2-200.fc18.x86_64 #1 SMP Mon May 13 13:59:47
UTC
2013 x86_64 x86_64 x86_64 GNU/Linux
Module Size Used by
**snd_usb_audio 145223 1
**snd_usbmidi_lib24713 1 snd_usb_audio
**snd_rawmidi29531 1 snd_usbmidi_lib
*snd_hwdep 17650 1 snd_hda_codec
**snd_hwdep 17650 2 snd_usb_audio,snd_hda_codec
*snd_seq_device 14136 1 snd_seq
**snd_seq_device 14136 2 snd_seq,snd_rawmidi
*snd79379 19
snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_hda_codec,snd_hda_intel,snd_seq_device
**snd79379 24
snd_hda_codec_realtek,snd_usb_audio,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_rawmidi,snd_usbmidi_lib,snd_hda_codec,snd_hda_intel,snd_seq_device
*video 18991 0
**video 18991 0
This is the beagleboard
lsmod
Module Size Used by
nls_iso8859_1 3673 1
nls_cp437 5339 1
I am going to be checking the video is a module or built into the kernel
of
the
uname -a
Linux beagleboard 3.4.36-yocto-standard #1 Mon Oct 28 21:58:22 MDT 2013
armv7l GNU/Linux
Thanks
On Thu, Oct 31, 2013 at 10:23 AM, Khem Raj raj.k...@gmail.com wrote:
On Thu, Oct 31, 2013 at 8:45 AM, Edward Vidal vidal.devel...@gmail.com
wrote:
Do I add RUN+=/bin/mknod /dev/video0 c 81 0 see below new version of
1--c920.rules
cat 10-c920.rules
SUBSYSTEM==video4linux, BUS==usb, ATTRS{idvendor}==0x046d,
ATTRS{idProduct}==0x082d, NAME=video0, MODE:=0660,
RUN+=/bin/mknod
/dev/video0 c 81 0
get rid of BUS construct there
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] adding a udev entry for a camera
Hello,
I am trying to add a c920 camera to my systems. I am not getting a
/dev/video0.
lsusb --verbose shows the HD Pro Webcam C920
Bus 001 Device 007: ID 046d:082d Logitech, Inc.
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 239 Miscellaneous Device
bDeviceSubClass 2 ?
bDeviceProtocol 1 Interface Association
bMaxPacketSize064
idVendor 0x046d Logitech, Inc.
idProduct 0x082d
bcdDevice0.11
iManufacturer 0
iProduct2 HD Pro Webcam C920
iSerial 1 211EF9AF
bNumConfigurations 1
plus much more information
I created /etc/udev/rules.d/10-c920.rules
SUBSYSTEM==video4linux, BUS==usb, ATTRS{idvendor}==0x046d,
ATTRS{idProduct}==0x082d, NAME=video0, MODE:=0660
mknod /dev/video0 c 81 0
when I v4l2-ctl --all error no /dev/video0
Any and all help will be appreciated.
Thanks
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] adding a udev entry for a camera
Hello, This is when I connect the camera udevadm monitor test monitor will print the received events for: UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[803.263336] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4 (usb) KERNEL[803.267456] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.0 (usb) KERNEL[803.269287] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.1 (usb) KERNEL[803.269958] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.2 (usb) KERNEL[803.270721] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.3 (usb) KERNEL[803.276214] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/usb_device/usbdev1.15 (usb_device)** UDEV [803.277191] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4 (usb) UDEV [803.306091] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/usb_device/usbdev1.15 (usb_device) UDEV [803.318603] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.2 (usb) UDEV [803.324249] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.1 (usb) UDEV [803.329712] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.0 (usb) UDEV [803.333160] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.3 (usb) still no /dev/video0 ls -la /dev/v* crw-rw 1 root tty 7, 0 Jan 1 2000 /dev/vcs crw-rw 1 root tty 7, 1 Jan 1 2000 /dev/vcs1 crw-rw 1 root tty 7, 2 Jan 1 2000 /dev/vcs2 crw-rw 1 root tty 7, 3 Oct 29 13:51 /dev/vcs3 crw-rw 1 root tty 7, 128 Jan 1 2000 /dev/vcsa crw-rw 1 root tty 7, 129 Jan 1 2000 /dev/vcsa1 crw-rw 1 root tty 7, 130 Jan 1 2000 /dev/vcsa2 crw-rw 1 root tty 7, 131 Oct 29 13:51 /dev/vcsa3 root@beagleboard:~# lsusb Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. Bus 001 Device 004: ID 0409:0059 NEC Corp. HighSpeed Hub Bus 001 Device 005: ID 413c:2005 Dell Computer Corp. RT7D50 Keyboard Bus 001 Device 006: ID 046d:c001 Logitech, Inc. N48/M-BB48 [FirstMouse Plus] Bus 001 Device 015: ID 046d:082d Logitech, Inc. *** udevadm monitor --udev monitor will print the received events for: UDEV - the event which udev sends out after rule processing camera removed* UDEV [1325.916811] remove /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.1 (usb) UDEV [1325.918489] remove /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.0 (usb) UDEV [1325.919282] remove /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.2 (usb) UDEV [1325.923005] remove /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.3 (usb) UDEV [1325.928437] remove /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/usb_device/usbdev1.15 (usb_device) UDEV [1325.932709] remove /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4 (usb) camera added *** UDEV [1329.344727] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4 (usb) UDEV [1329.376313] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/usb_device/usbdev1.16 (usb_device) UDEV [1329.389008] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.2 (usb) UDEV [1329.396241] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.1 (usb) UDEV [1329.401795] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.0 (usb) UDEV [1329.406739] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.3 (usb) This is what I get in /var/log/messages Oct 29 14:17:28 beagleboard user.info kernel: usb 1-2.3.4: USB disconnect, device number 16 Oct 29 14:17:31 beagleboard user.info kernel: usb 1-2.3.4: new high-speed USB device number 17 using ehci-omap Is there anything else that I can test / provide Thanks On Wed, Oct 30, 2013 at 5:58 PM, Khem Raj raj.k...@gmail.com wrote: On Wed, Oct 30, 2013 at 1:51 PM, Edward Vidal vidal.devel...@gmail.com wrote: Hello, I am trying to add a c920 camera to my systems. I am not getting a /dev/video0. lsusb --verbose shows the HD Pro Webcam C920 Bus 001 Device 007: ID 046d:082d Logitech, Inc. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 239 Miscellaneous Device bDeviceSubClass 2 ? bDeviceProtocol 1
Re: [yocto] uimage instead of zImage
Hello, My 2nd partition on the mmc is linux ext3. This is what I have been using to transfer the rootfs to my mmc tar jxvf beagleboard/core-image-minimal-beagleboard-20131024171447.rootfs.tar.bz2 Did something change since the 21 st of last month. Testing dora which was not part of dylan? No matter what I do when i the kernel to start it is always is looking for UBIFS my mmcrootfstype=ext3 rootwait and mmcroot/dev/mmcblk0p2 rw bootcmd=mmc rescan 0 ; fatload mmc 0:1 0x80008000 zImage; bootz 0x80008000 when I execute manually it does seem to like mmc rescan 0 sometimes mmc rescan 0 mmc - MMC sub system Usage: mmc read addr blk# cnt mmc write addr blk# cnt mmc erase blk# cnt mmc rescan mmc part - lists available partition oncurrentmmc device mmc dev[dev] [part] - show or set current mmc device [partition] mmc list - lists available devices mmc rescan works okay. ThumbEE CPU extension supported. VDVI: incomplete constraints, leaving on VDAC: incomplete constraints, leaving on UBI error: ubi_init: UBI error:cannot initialize UBI, error -19 console [netcon0] enabled netconsole: network logging started twl_rtctwl_rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800) ALSA device list: #0: omap3beagle VFS: Cannot open root device ubi0:rootfs or unknown-block(0,0): error -19 Please append acorrect root= boot option; here are the available partitions: VFS: Unable to mount root fs onunknown-block(0,0) User configuration error - no valid root filesystem found Kernel panic - not syncing: Invalid configuration from end userprevents continu ing Thanks On Wed, Oct 23, 2013 at 10:09 AM, Rudolf Streif rstr...@linuxfoundation.org wrote: 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 zImage; bootz 0x8030 Why are you setting all the variables to . You really only have to overwrite the ones you need to change. dvimode=hd720 omapfb.vram=0:8M,1:4M,2:4M optargs=consoleblank=0 console=ttyO2 console=tty0,115200n8 vram=16M saveenv printenv It appears that some of variable get written with other data ie vram I am setting to 16M but sometimes I see it set to 12M see at the end I have tried setting the variables manually and executing saveenv All the ones I don't want set setenv name and then saveenv still see the same values when I was using uImage and no this is what I used for my uEnv.txt mpurate=auto Are you still trying to solve the problem with the rootfs or is that another problem? mmcroot=/dev/mmcblk0p2 rw mmcrootfstype=ext3 rootwait According to these settings your kernel is passed information to look for an ext3 root file system on the second partition of the an SD card on /dev/mmcblk0. Are you booting from an SD card? However, in your first boot it seems to look for an ubifs. I am not sure what you are looking for. Maybe you can attach an new boot log. :rjs ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] threads set in local.conf
Hello All, As Philip suggested adding more RAM helps The system model name: AMD Phenom(tm) II X6 1090T Processor w/16GB of RAM. In 1 hour it ran 4391 of 8016 tasks or 54% This was a core-image-sato-sdk-ex (my receipe) with gnuplot, gsl, boost, qt-mobility-x11, java, and gnuradio.The full build was taking close to 4 hours with 6 threads and 8GB of RAM. Regards On Sun, Oct 20, 2013 at 7:39 AM, Philip Balister phi...@balister.orgwrote: On 10/19/2013 08:59 AM, Edward Vidal wrote: Hello all, Is this loading what others on a similar system are experiencing (see below)? I first was setting my threads to 6 on a AMD 6 core system. In the mega-manual i found 5.4. Configuring the local.conf File Briefly, set BB_NUMBER_THREADS and PARALLEL_MAKE to twice your host processor's number of cores. I am creating an image with 8017 tasks for the beagleboard. I set threads to 12 and now the build is proceeding much more rapid than when threads were set to 6. In 30 minutes the build has completed 2435 tasks or about 25%. I am seeing a fairly high load 35. 30. 24 and the fan is been at high speed since the build started. The system has 8G of memory and now it is using and it was using about 13800 of swap space. Any and all help will be appreciated. I'm not sure what problem you are trying to solve here. I'd suggest adding more RAM though, that will ease the disk usage. Philip Thanks ___ 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] uimage instead of zImage
Hello,
I see some values when I do printenv
These are the files on my dos partition
MLO u-boot.img uEnv.txtzImage zImage-omap3-beagle-xm.dtb
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 zImage; bootz 0x8030
dvimode=hd720 omapfb.vram=0:8M,1:4M,2:4M
optargs=consoleblank=0
console=ttyO2 console=tty0,115200n8
vram=16M
saveenv
printenv
It appears that some of variable get written with other data ie vram I am
setting to 16M but sometimes I see it set to 12M see at the end
I have tried setting the variables manually and executing saveenv
All the ones I don't want set setenv name and then saveenv
still see the same values
when I was using uImage and no
this is what I used for my uEnv.txt
mpurate=auto
bootcmd=mmc rescan 0; fatload mmc 0:1 0x8030 uImage; bootm 0x8030
dvimode=hd720 omapfb.vram=0:8M,1:4M,2:4M
vram=16M
optargs=consoleblank=0
console=ttyO2 console=tty0,115200n8
These were the file on the dos partition
MLO u-boot.img uEnv.txtuImage
This was on a build on 09/21/13
Any and all help will be appreciated.
Thanks
U-Boot SPL 2013.07 (Oct 19 2013 - 09:14:36)
OMAP SD/MMC: 0
reading u-boot.img
reading u-boot.img
U-Boot 2013.07 (Oct 19 2013 - 09:14:36)
OMAP3630/3730-GP ES1.2, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz
OMAP3 Beagle board + LPDDR/NAND
I2C: ready
DRAM: 512 MiB
NAND: 0 MiB
MMC: OMAP SD/MMC: 0
*** Warning - readenv() failed, using default environment
In:serial
Out: serial
Err: serial
Beagle xM Rev C
No EEPROM on expansion board
Die ID #15829ff80160a7450b02602d
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split,
HB-ISO
Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 1.800
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Peripheral mode controller at 480ab000 using PIO, IRQ 0
Net: usb_ether
Hit any key to stop autoboot: 3 2 1 0
OMAP3 beagleboard.org # l printenv
baudrate=115200
beaglerev=xMC
bootcmd=mmc dev ${mmcdev}; if mmc rescan; then if run userbutton; then
setenv bo
otenv uEnv.txt;else setenv bootenv user.txt;fi;echo SD/MMC found on device
${mmc
dev};if run loadbootenv; then echo Loaded environment from ${bootenv};run
import
bootenv;fi;if test -n $uenvcmd; then echo Running uenvcmd ...;run
uenvcmd;fi;if
run loaduimage; then run mmcboot;fi;fi;run nandboot;
bootdelay=3
bootenv=uEnv.txt
bootfile=uImage.beagle
buddy=none
camera=none
console=ttyO2,115200n8
defaultdisplay=dvi
dieid#=15829ff80160a7450b02602d
dvimode=640x480MR-16@60
ethact=usb_ether
importbootenv=echo Importing environment from mmc ...; env import -t
$loadaddr $
filesize
loadaddr=0x8020
loadbootenv=fatload mmc ${mmcdev} ${loadaddr} ${bootenv}
loadramdisk=fatload mmc ${mmcdev} ${rdaddr} ramdisk.gz
loaduimage=ext2load mmc ${mmcdev}:2 ${loadaddr} /boot/uImage
loaduimagefat=fatload mmc ${mmcdev} ${loadaddr} uImage
mmcargs=setenv bootargs console=${console} ${optargs} mpurate=${mpurate}
buddy=$
{buddy} camera=${camera} vram=${vram} omapfb.mode=dvi:${dvimode}
omapdss.def_dis
p=${defaultdisplay} root=${mmcroot} rootfstype=${mmcrootfstype}
mmcboot=echo Booting from mmc ...; run mmcargs; bootm ${loadaddr}
mmcdev=0
mmcroot=/dev/mmcblk0p2 rw
mmcrootfstype=ext3 rootwait
mpurate=auto
nandargs=setenv bootargs console=${console} ${optargs} mpurate=${mpurate}
buddy=
${buddy} camera=${camera} vram=${vram} omapfb.mode=dvi:${dvimode}
omapdss.def_di
sp=${defaultdisplay} root=${nandroot} rootfstype=${nandrootfstype}
nandboot=echo Booting from nand ...; run nandargs; nand read ${loadaddr}
28
40; bootm ${loadaddr}
nandroot=ubi0:rootfs ubi.mtd=4
nandrootfstype=ubifs
ramargs=setenv bootargs console=${console} ${optargs} mpurate=${mpurate}
buddy=$
{buddy} vram=${vram} omapfb.mode=dvi:${dvimode}
omapdss.def_disp=${defaultdispla
y} root=${ramroot} rootfstype=${ramrootfstype}
ramboot=echo Booting from ramdisk ...; run ramargs; bootm ${loadaddr}
ramroot=/dev/ram0 rw ramdisk_size=65536 initrd=0x8100,64M
ramrootfstype=ext2
rdaddr=0x8100
stderr=serial
stdin=serial
stdout=serial
usbtty=cdc_acm
userbutton=if gpio input 173; then run userbutton_xm; else run
userbutton_nonxm;
fi;
userbutton_nonxm=gpio input 7;
userbutton_xm=gpio input 4;
vram=12M
Environment size: 2359/131068 bytes
OMAP3 beagleboard.org #
* - * Qodem 0.1.2 Capture Generated Sun, 20 Oct 2013 10:59:54 -0600 END * -
*
On Sat, Oct 19, 2013 at 1:09 PM, Rudolf Streif
rstr...@linuxfoundation.orgwrote:
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; here are the available
partitions:
VFS: Unable to mount root fs on unknown-block(0,0)
User
[yocto] threads set in local.conf
Hello all, Is this loading what others on a similar system are experiencing (see below)? I first was setting my threads to 6 on a AMD 6 core system. In the mega-manual i found 5.4. Configuring the local.conf File Briefly, set BB_NUMBER_THREADS and PARALLEL_MAKE to twice your host processor's number of cores. I am creating an image with 8017 tasks for the beagleboard. I set threads to 12 and now the build is proceeding much more rapid than when threads were set to 6. In 30 minutes the build has completed 2435 tasks or about 25%. I am seeing a fairly high load 35. 30. 24 and the fan is been at high speed since the build started. The system has 8G of memory and now it is using and it was using about 13800 of swap space. Any and all help will be appreciated. Thanks ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] uimage instead of zImage
Hello all, I made some changes to my uEnv.txt mpurate=auto bootcmd=mmc rescan 0; fatload mmc 0:1 0x8030 uImage; bootm 0x8030 dvimode=hd720 omapfb.vram=0:8M,1:4M,2:4M vram=16M optargs=consoleblank=0 console=ttyO2 console=tty0,115200n8 chgs uImage to zImage in the bootcmd line above. Still would not boot? setenv bootcmd mmc rescan 0; fatload mmc 0:1 0x8020 zImage; bootz 0x8020 setenv vram 16M setenv bootfile zImage printenv echo $vram echo $bootfile echo $bootcmd run bootcmd If I make the above setenv at the u-boot prompt I get the kernel to boot, but get a kernel panic. VFS: Cannot open root device ubi0:rootfs or unknown-block(0,0): error -19 Please append a correct root= boot option; here are the available partitions: VFS: Unable to mount root fs on unknown-block(0,0) User configuration error - no valid root filesystem found Kernel panic - not syncing: Invalid configuration from end user prevents continu ing CPU: 0 PID: 1 Comm: swapper Not tainted 3.10.11-yocto-standard #1 [c00145c8] (unwind_backtrace+0x0/0xec) from [c0011b9c] (show_stack+0x20/0x24 ) [c0011b9c] (show_stack+0x20/0x24) from [c0602c90] (dump_stack+0x20/0x28) [c0602c90] (dump_stack+0x20/0x28) from [c05fea4c] (panic+0x84/0x1c0) [c05fea4c] (panic+0x84/0x1c0) from [c08d30e4] (mount_block_root+0x1fc/0x244) [c08d30e4] (mount_block_root+0x1fc/0x244) from [c08d33b4] (prepare_namespace +0x94/0x1c4) [c08d33b4] (prepare_namespace+0x94/0x1c4) from [c08d2c9c] (kernel_init_freea ble+0x1e8/0x238) [c08d2c9c] (kernel_init_freeable+0x1e8/0x238) from [c05fdc10] (kernel_init+0 x1c/0xf4) [c05fdc10] (kernel_init+0x1c/0xf4) from [c000db18] (ret_from_fork+0x14/0x20) zImage-omap3-beagle.dtb is the name of my dtb file. This is a new file that I had seen before in my beagleboard until dora build. I had seen in my zedboard build. Any and all help will be appreciated. Thanks ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] uImage instead of zImage
hello all, I am trying to get a uImage instead of zImage My beagleboard before created a uImage now with dora I get a zImage. in the mega-manual I see the following . KERNEL_IMAGETYPE The type of kernel to build for a device, usually set by the machine configuration files and defaults to zImage. This variable is used when building the kernel and is passed to make as the target to build. . /home/vidal/POKY/build101613_dora/poky/meta/conf/machine/include/arm/arch-arm.inc I have tried KERNEL_IMAGETYPE ?= uImage KERNEL_IMAGETYPE = uImage and nothing changes I still get a zImage. Also tried in local.conf Any and all help will be appreciated. Thanks ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Fwd: uImage instead of zImage
-- Forwarded message -- From: Robert P. J. Day rpj...@crashcourse.ca Date: Fri, Oct 18, 2013 at 9:44 AM Subject: Re: [yocto] uImage instead of zImage To: Edward Vidal vidal.devel...@gmail.com On Fri, 18 Oct 2013, Edward Vidal wrote: Hello When I changed the uEnv.txt file I get the same error. I also have a zImage-omap3-beagle-xm.dtb which is new with this build is this the correct name. MLO u-boot.img zImage uEnv.txt and zImage-omap3-beagle-xm.dtb are the files on my DOS partition. Thanks you should not be emailing to me directly, you should respond to this on the mailing list so that others can benefit from the discussion. rday ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] meta-xilinx
Hello,
I got the following error.
DEBUG: Executing shell function do_compile
NOTE: make -C
/home/vidal/POKY/build101613_zedboard/poky/build/tmp/sysroots/zedboard-zynq7/usr/src/kernel/tools/perf
O=/home/vidal/POKY/build101613_zedboard/poky/build/tmp/work/zedboard_zynq7-poky-linux-gnueabi/perf/1.0-r8/perf-1.0
CROSS_COMPILE=arm-poky-linux-gnueabi- ARCH=arm
CC=arm-poky-linux-gnueabi-gcc -march=armv7-a -mthumb-interwork
-mfloat-abi=softfp -mfpu=neon
--sysroot=/home/vidal/POKY/build101613_zedboard/poky/build/tmp/sysroots/zedboard-zynq7
AR=arm-poky-linux-gnueabi-ar perfexecdir=/usr/lib/perf NO_GTK2=1 NO_DWARF=1
prefix=/usr bindir=/usr/bin sharedir=/usr/share sysconfdir=/etc
perfexecdir=/usr/lib/perf/perf-core ETC_PERFCONFIG=../etc sharedir=share
mandir=share/man infodir=share/info all
CHK -fstack-protector-all
CHK -Wstack-protector
CHK -Wvolatile-register-var
CHK bionic
CHK libelf
CHK libdw
make: Entering directory
`/home/vidal/POKY/build101613_zedboard/poky/build/tmp/sysroots/zedboard-zynq7/usr/src/kernel/tools/perf'
Makefile:554: No libdw.h found or old libdw.h found or elfutils is older
than 0.138, disables dwarf support. Please install new
elfutils-devel/libdw-dev
CHK libunwind
Makefile:570: No libunwind found, disabling post unwind support. Please
install libunwind-dev[el] = 0.99
I installed libunwind-devel-1.0.1-5.fc18.x86_64
Is this a zedboard-zynq specific error? Is this an error in building the
kernel?
I did not see this when building for the beagleboard. I installed
libunwind-devel-1.0.1-5.fc18.x86_64
I removed the package libunwind-devel-1.0.1-5.fc18.x86_64 since nothing
improved with the package installed.
I am in the process of running a clean build after all repository were
loaded in clean folder.
I appreciate any and all help.
Regards
On Wed, Oct 16, 2013 at 5:06 PM, Edward Vidal vidal.devel...@gmail.comwrote:
Hello Khem,
Thanks for the help after modifying my local.conf
MACHINE ?= zedboard-zynq7
My build MACHINE=zedboard-zynq7 bitbake core-image-sato is in the
process now 295 of 5076 tasks
should take a short time to complete.
regards
On Wed, Oct 16, 2013 at 4:45 PM, Khem Raj raj.k...@gmail.com wrote:
On Oct 16, 2013, at 2:57 PM, Edward Vidal vidal.devel...@gmail.com
wrote:
Hello,
I built a zedboard core-image-sato on 09/21/13 with meta-xilinx at that
time I had the following folders.
meta-kc705
meta-zc702
meta-zedboard
Build Configuration:
BB_VERSION= 1.19.1
BUILD_SYS = x86_64-linux
NATIVELSBSTRING = Fedora-18
TARGET_SYS= arm-poky-linux-gnueabi
MACHINE = zedboard
DISTRO= poky
DISTRO_VERSION= 1.4+snapshot-20130921
TUNE_FEATURES = armv7a vfp neon zynq
TARGET_FPU= vfp-neon
meta
meta-yocto=
(nobranch):3dee534f1e25109e0bdb681de0746c336f4b8840
meta-xilinx
meta-kc705
meta-zc702
meta-zedboard = master:46f4c79d6d55b556a90bb0fd89c2c09acf2aebff
meta-yocto-bsp=
(nobranch):3dee534f1e25109e0bdb681de0746c336f4b8840
With the dora release I did a new clone of git://
git.yoctoproject.org/meta-xilinx
now I do not see
meta-kc705
meta-zc702
meta-zedboard
When I execute MACHINE=zedboard bitbake core-image-sato
ERROR: OE-core's config sanity checker detected a potential
misconfiguration.
Either fix the cause of this error or at your own risk disable the
checker (see sanity.conf).
Following is the list of potential problems / advisories:
Please set a valid MACHINE in your local.conf or environment
ERROR: Execution of event handler 'check_sanity_eventhandler' failed
In my local.conf I have the following.
MACHINE ?= zedboard
bblayers.conf
# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly
LCONF_VERSION = 6
BBPATH = ${TOPDIR}
BBFILES ?=
BBLAYERS ?= \
/home/vidal/POKY/build101613_zedboard/poky/meta \
/home/vidal/POKY/build101613_zedboard/poky/meta-yocto \
/home/vidal/POKY/build101613_zedboard/poky/meta-xilinx \
/home/vidal/POKY/build101613_zedboard/poky/meta-yocto-bsp \
BBLAYERS_NON_REMOVABLE ?= \
/home/vidal/POKY/build101613_zedboard/poky/meta \
/home/vidal/POKY/build101613_zedboard/poky/meta-yocto \
Any help will be appreciated.
Regards
it seems like layer went thru some restructuring e.g. see
commit d9617006376d73e37f1db17857ee06c24e6b7c03
Author: Nathan Rossi nathan.ro...@xilinx.com
Date: Fri Aug 2 12:41:14 2013 +1000
meta-*: Remove deprecated sublayers
* The machines supported in the sublayer BSPs are now supported in
the base
meta-xilinx layer, these sublayers are no longer required.
* Relevant documentation has also been relocated into
meta-xilinx/docs/*.
So may be zedboard - zedboard-zynq7
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] meta-xilinx
Hello,
I built a zedboard core-image-sato on 09/21/13 with meta-xilinx at that
time I had the following folders.
meta-kc705
meta-zc702
meta-zedboard
Build Configuration:
BB_VERSION= 1.19.1
BUILD_SYS = x86_64-linux
NATIVELSBSTRING = Fedora-18
TARGET_SYS= arm-poky-linux-gnueabi
MACHINE = zedboard
DISTRO= poky
DISTRO_VERSION= 1.4+snapshot-20130921
TUNE_FEATURES = armv7a vfp neon zynq
TARGET_FPU= vfp-neon
meta
meta-yocto= (nobranch):3dee534f1e25109e0bdb681de0746c336f4b8840
meta-xilinx
meta-kc705
meta-zc702
meta-zedboard = master:46f4c79d6d55b556a90bb0fd89c2c09acf2aebff
meta-yocto-bsp= (nobranch):3dee534f1e25109e0bdb681de0746c336f4b8840
With the dora release I did a new clone of git://
git.yoctoproject.org/meta-xilinx
now I do not see
meta-kc705
meta-zc702
meta-zedboard
When I execute MACHINE=zedboard bitbake core-image-sato
ERROR: OE-core's config sanity checker detected a potential
misconfiguration.
Either fix the cause of this error or at your own risk disable the
checker (see sanity.conf).
Following is the list of potential problems / advisories:
Please set a valid MACHINE in your local.conf or environment
ERROR: Execution of event handler 'check_sanity_eventhandler' failed
In my local.conf I have the following.
MACHINE ?= zedboard
bblayers.conf
# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly
LCONF_VERSION = 6
BBPATH = ${TOPDIR}
BBFILES ?=
BBLAYERS ?= \
/home/vidal/POKY/build101613_zedboard/poky/meta \
/home/vidal/POKY/build101613_zedboard/poky/meta-yocto \
/home/vidal/POKY/build101613_zedboard/poky/meta-xilinx \
/home/vidal/POKY/build101613_zedboard/poky/meta-yocto-bsp \
BBLAYERS_NON_REMOVABLE ?= \
/home/vidal/POKY/build101613_zedboard/poky/meta \
/home/vidal/POKY/build101613_zedboard/poky/meta-yocto \
Any help will be appreciated.
Regards
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] meta-xilinx
Hello Khem,
Thanks for the help after modifying my local.conf
MACHINE ?= zedboard-zynq7
My build MACHINE=zedboard-zynq7 bitbake core-image-sato is in the process
now 295 of 5076 tasks
should take a short time to complete.
regards
On Wed, Oct 16, 2013 at 4:45 PM, Khem Raj raj.k...@gmail.com wrote:
On Oct 16, 2013, at 2:57 PM, Edward Vidal vidal.devel...@gmail.com
wrote:
Hello,
I built a zedboard core-image-sato on 09/21/13 with meta-xilinx at that
time I had the following folders.
meta-kc705
meta-zc702
meta-zedboard
Build Configuration:
BB_VERSION= 1.19.1
BUILD_SYS = x86_64-linux
NATIVELSBSTRING = Fedora-18
TARGET_SYS= arm-poky-linux-gnueabi
MACHINE = zedboard
DISTRO= poky
DISTRO_VERSION= 1.4+snapshot-20130921
TUNE_FEATURES = armv7a vfp neon zynq
TARGET_FPU= vfp-neon
meta
meta-yocto= (nobranch):3dee534f1e25109e0bdb681de0746c336f4b8840
meta-xilinx
meta-kc705
meta-zc702
meta-zedboard = master:46f4c79d6d55b556a90bb0fd89c2c09acf2aebff
meta-yocto-bsp= (nobranch):3dee534f1e25109e0bdb681de0746c336f4b8840
With the dora release I did a new clone of git://
git.yoctoproject.org/meta-xilinx
now I do not see
meta-kc705
meta-zc702
meta-zedboard
When I execute MACHINE=zedboard bitbake core-image-sato
ERROR: OE-core's config sanity checker detected a potential
misconfiguration.
Either fix the cause of this error or at your own risk disable the
checker (see sanity.conf).
Following is the list of potential problems / advisories:
Please set a valid MACHINE in your local.conf or environment
ERROR: Execution of event handler 'check_sanity_eventhandler' failed
In my local.conf I have the following.
MACHINE ?= zedboard
bblayers.conf
# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly
LCONF_VERSION = 6
BBPATH = ${TOPDIR}
BBFILES ?=
BBLAYERS ?= \
/home/vidal/POKY/build101613_zedboard/poky/meta \
/home/vidal/POKY/build101613_zedboard/poky/meta-yocto \
/home/vidal/POKY/build101613_zedboard/poky/meta-xilinx \
/home/vidal/POKY/build101613_zedboard/poky/meta-yocto-bsp \
BBLAYERS_NON_REMOVABLE ?= \
/home/vidal/POKY/build101613_zedboard/poky/meta \
/home/vidal/POKY/build101613_zedboard/poky/meta-yocto \
Any help will be appreciated.
Regards
it seems like layer went thru some restructuring e.g. see
commit d9617006376d73e37f1db17857ee06c24e6b7c03
Author: Nathan Rossi nathan.ro...@xilinx.com
Date: Fri Aug 2 12:41:14 2013 +1000
meta-*: Remove deprecated sublayers
* The machines supported in the sublayer BSPs are now supported in the
base
meta-xilinx layer, these sublayers are no longer required.
* Relevant documentation has also been relocated into
meta-xilinx/docs/*.
So may be zedboard - zedboard-zynq7
___
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] preempt-rt zedboard
Hello, I am working on a zedboard and trying to use preempt-rt patch. The working kernel (Linux zedboard 3.6.0-digilent-13.01-2-g06b3889-dirty #4 SMP PREEMPT Sun Oct 6 12:23:48 MDT 2013 armv7l GNU/Linux) that I have is from a repository maintain by digilent git remote show origin * remote origin Fetch URL: https://github.com/Digilent/linux-digilent.git I assuming the main changes are in the area of arch/arm/boot/dts I did a git clone git:// git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git and downloaded the patch-3.6.11.1-2 I have tried the following git checkout -b v3.6.11.1-2 which branch or tag actually goes to this new branch git apply --stat ~/Downloads/patch-3.6.11.1-2 this seems to work git apply --check ~/Downloads/patch-3.6.11.1-2 This shows lots of errors. What would be the steps to take the changes in the linux-digilent repository and the changes for linux-steps-rt to create my repository for testing? I am interested in testing performance with and without the patch. For Real Time systems is this the best approach? Any and all help will be welcomed. Thanks ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] preempt-rt zedboard
Hello, after many attempts I create a script to test if the patch would work. #!/bin/bash echo removing older version rm -rf linux-stable-rt echo extracting a clean version tar xfz linux-stable-rt.tgz echo going to toplevel dir cd linux-stable-rt echo checkout of version before the patch git checkout v3.6.11.1 echo checking which files will be patched git apply --stat ~/Downloads/patch-3.6.11.1-2 echo checking if the patch can be applied without errors git apply --check ~/Downloads/patch-3.6.11.1-2 if I did not get errors then I executed make ARCH=arm CROSS_COMPILE=arm-xilinx-linux-gnueabi- menuconfig Kernel Features Preemption Model (Voluntary Kernel Preemption (Desktop)) --- ─ Voluntary Kernel Preemption (Desktop) ─┐ │ CONFIG_PREEMPT_VOLUNTARY: │ │ │ │ This option reduces the latency of the kernel by adding more │ │ explicit preemption points to the kernel code. These new │ │ preemption points have been selected to reduce the maximum │ │ latency of rescheduling, providing faster application reactions, │ │ at the cost of slightly lower throughput. │ │ │ │ This allows reaction to interactive events by allowing a │ │ low priority process to voluntarily preempt itself even if it │ │ is in kernel mode executing a system call. This allows │ │ applications to run more 'smoothly' even when the system is │ │ under load. │ │ │ │ Select this if you are building a kernel for a desktop system. git apply ~/Downloads/patch-3.6.11.1-2 stdin:5054: new blank line at EOF. + warning: 1 line adds whitespace errors. After the patch was applied nothing seem to have changed. I am thinking this should be the option selected instead of the one above. Preemptible Kernel (Low-Latency Desktop) ┐ │ CONFIG_PREEMPT: │ │ │ │ This option reduces the latency of the kernel by making │ │ all kernel code (that is not executing in a critical section) │ │ preemptible. This allows reaction to interactive events by │ │ permitting a low priority process to be preempted involuntarily │ │ even if it is in kernel mode executing a system call and would │ │ otherwise not be about to reach a natural preemption point. │ │ This allows applications to run more 'smoothly' even when the │ │ system is under load, at the cost of slightly lower throughput │ │ and a slight runtime overhead to kernel code. │ │ │ │ Select this if you are building a kernel for a desktop or │ │ embedded system with latency requirements in the milliseconds │ │ range. I still have not figured out how to merge the linux-digilent with the patched linux-stable-rt kernel. Any and all help will be appreciated. Thanks ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] yocto armhf armel on zedboard
Hello While trying to add additional software I came across a problem. Ubuntu uses armhf and the packages I had built with Yocto use armel. Is there a license issue with building with armhf instead of armel with Yocto? I just received my zedboard this past week. Testing has been going okay so far. I built the kernel devicetree.dtb using Xilinx sdk. The kernel sources were obtained at git clone https://github.com/Digilent/linux-digilent.git. Ubuntu and BusyBox booted okay with linaro-precise-ubuntu-desktop-20120923-436.tar.gz rootfs and ramdisk8M.image.gz rootfs. I also used the BOOT.BIN provided for BusyBox tests. I then created 2 rootfs wih Yocto both of which booted okay. MACHINE=zedboard bitbake core-image-minimal and MACHINE=zedboard bitbake core-image-sato using the zImage devicetree.dtb builted Xilinx sdk. The kernel sources were obtained at git clone https://github.com/Digilent/linux-digilent.git. zcat core-image-minimal-zedboard-20130915191921.rootfs.ext2.gz /dev/sdb2 MACHINE=zedboard bitbake core-image-sato zcat core-image-sato-zedboard-20130918125052.rootfs.ext2.gz /dev/sdb2 Build Configuration: BB_VERSION= 1.19.1 BUILD_SYS = x86_64-linux NATIVELSBSTRING = Fedora-18 TARGET_SYS= arm-poky-linux-gnueabi MACHINE = zedboard DISTRO= poky DISTRO_VERSION= 1.4+snapshot-20130918 TUNE_FEATURES = armv7a vfp neon zynq TARGET_FPU= vfp-neon meta meta-yocto= master:3dee534f1e25109e0bdb681de0746c336f4b8840 meta-xilinx meta-kc705 meta-zc702 meta-zedboard = master:46f4c79d6d55b556a90bb0fd89c2c09acf2aebff meta-oe = master:c383d6230942bb1558cee02764bced09031cb70f meta-java = master:59696d89fd33df6953dcb2dd54ccd3b362513f28 meta-yocto-bsp= master:3dee534f1e25109e0bdb681de0746c336f4b8840 Any and all help will be appreciated. Thanks Ed Vidal vidal.devel...@gmail.com ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] state machine for X86_64 beaglebone zedboard pic32.
is thinking Philosopher 4 is thinking 00 PHILO_STAT: 0 thinking 00 PHILO_STAT: 1 thinking 00 PHILO_STAT: 2 thinking 00 PHILO_STAT: 3 thinking 00 PHILO_STAT: 4 thinking Q_INIT : Obj=l_table Source=QHsm_top Target=Table_serving Q_ENTRY: Obj=l_table State=Table_serving 00 ==Init: Obj=l_table New=Table_serving Philosopher 4 is hungry Philosopher 4 is eating 00 Disp==: Obj=l_philo[4] Sig=TIMEOUT_SIG Active=Philo_thinking Q_ENTRY: Obj=l_philo[4] State=Philo_hungry 00 ==Tran: Obj=l_philo[4] Sig=TIMEOUT_SIG Source=Philo_thinking New=Philo_hungry 00 Disp==: Obj=l_table Sig=HUNGRY_SIG Active=Table_serving 00 PHILO_STAT: 4 hungry 00 Disp==: Obj=l_philo[4] Sig=EAT_SIG Active=Philo_hungry Q_ENTRY: Obj=l_philo[4] State=Philo_eating 00 ==Tran: Obj=l_philo[4] Sig=EAT_SIG Source=Philo_hungry New=Philo_eating 00 Disp==: Obj=l_philo[3] Sig=EAT_SIG Active=Philo_thinking 00 Intern : Obj=l_philo[3] Sig=EAT_SIG Source=Philo_thinking 00 Disp==: Obj=l_philo[2] Sig=EAT_SIG Active=Philo_thinking 00 Intern : Obj=l_philo[2] Sig=EAT_SIG Source=Philo_thinking 00 Disp==: Obj=l_philo[1] Sig=EAT_SIG Active=Philo_thinking 00 Intern : Obj=l_philo[1] Sig=EAT_SIG Source=Philo_thinking 00 Disp==: Obj=l_philo[0] Sig=EAT_SIG Active=Philo_thinking 00 Intern : Obj=l_philo[0] Sig=EAT_SIG Source=Philo_thinking 00 PHILO_STAT: 4 eating 00 Intern : Obj=l_table Sig=HUNGRY_SIG Source=Table_serving Philosopher 0 is hungry If you have any questions feel free to contact me. Edward Vidal Jr vidal.devel...@gmail.com or devel...@sbcglobal.net ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Fwd: zedboard gnuradio
-- Forwarded message -- From: Edward Vidal vidal.devel...@gmail.com Date: Thu, Jul 18, 2013 at 12:21 PM Subject: Re: [yocto] zedboard gnuradio To: Paul Eggleton paul.eggle...@linux.intel.com Hello Any and all help is appreciated. This is for java and core-image-sato-ex build Adding additional packages to my build Is this a similar problem since the new version of poky has added stricter testing. ERROR: QA Issue: perf: The compile log indicates that host include and/or library paths were used. Please check the log '/home/vidal/POKY/build071813_zedboard/poky/build/tmp/work/zedboard-poky-linux-gnueabi/perf/1.0-r8/temp/log.do_compile' for more information. ERROR: QA run found fatal errors. Please consider fixing them. ERROR: Function failed: do_package_qa ERROR: Logfile of failure stored in: /home/vidal/POKY/build071813_zedboard/poky/build/tmp/work/zedboard-poky-linux-gnueabi/perf/1.0-r8/temp/log.do_package.25012 ERROR: Task 3305 (/home/vidal/POKY/build071813_zedboard/poky/meta/recipes-kernel/perf/perf.bb, do_package) failed with exit code '1' NOTE: Tasks Summary: Attempted 7086 tasks of which 531 didn't need to be rerun and 1 failed. Waiting for 0 running tasks to finish: Summary: 1 task failed: /home/vidal/POKY/build071813_zedboard/poky/meta/recipes-kernel/perf/ perf.bb, do_package Summary: There were 14 WARNING messages shown. Summary: There were 3 ERROR messages shown, returning a non-zero exit code. Thanks On Tue, Jul 16, 2013 at 5:17 PM, Paul Eggleton paul.eggle...@linux.intel.com wrote: On Tuesday 16 July 2013 13:18:07 Edward Vidal wrote: On Tue, Jul 16, 2013 at 11:50 AM, Paul Eggleton paul.eggle...@linux.intel.com wrote: On Tuesday 16 July 2013 08:47:03 Edward Vidal wrote: ERROR: QA Issue: File '/usr/plugins/designer/libqwt_designer_plugin.so' from qwt was already stripped, this will prevent future debugging! ERROR: QA Issue: File '/usr/lib/libqwt.so.6.0.1' from qwt was already stripped, this will prevent future debugging! ERROR: QA Issue: File '/usr/lib/libqwtmathml.so.6.0.1' from qwt was already stripped, this will prevent future debugging! poky.conf now marks this QA issue as an error instead of a warning in order to pick up on quality issues when running builds. You can either: a) Fix the recipe so that qwt gets built without stripping its output binaries, or b) set your own value for ERROR_QA and WARN_QA so that already-stripped appears in WARN_QA rather than ERROR_QA I opted for options b.) modifying /home/vidal/POKY/build071613_zedboard/poky/meta-yocto/conf/distro/poky.conf mvoing already-stripped from ERROR_QA to WARN_QA . Build is currently in progress. My question will option a.) need to be done to prevent this from occurring in future releases. The recipe in question is part of meta-oe and thus is maintained by OpenEmbedded rather than the Yocto Project, so ultimately someone in the OpenEmbedded community should fix it, yes. Fixing already stripped issues usually isn't too hard, it just depends on how the software in question is being built. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Qt4.8 - qt4-x11-free does not compile if host has qt-mobility installed
Hello, see my post zedboard gnuradio. see the reply provided by Paul I know gnuradio depends on qt-mobile Let me know if this helps. cheers ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] zedboard gnuradio
Hello, Any and all help will be appreciated. testing not having to revert back to boost-1.53.0 The new pull of poky, meta-oe, boost-1.54.0 compiled okay. pull on 07/16/13 of all meta_data_from_remotes cd POKY/build071613_zedboard/ cp -R ~/POKY/meta_data_from_remotes/poky/ . cd poky/ cp -R ~/POKY/meta_data_from_remotes/meta-oe/ . cp -R ~/POKY/meta_data_from_remotes/meta-xilinx/ . p -R ~/POKY/meta_data_from_remotes/meta-java . . oe-init-build-env cp ~/POKY/build071613_zedboard/local.conf conf/ cp ~/POKY/build071613_zedboard/bblayers.conf conf/ cp ../../core-image-minimal-ex.bb ../meta/recipes-core/images/ /home/vidal/POKY/poky/patch_sato_gnuplot MACHINE=zedboard bitbake core-image-minimal-ex 4333 tasks Build Configuration: BB_VERSION= 1.19.1 BUILD_SYS = x86_64-linux NATIVELSBSTRING = Fedora-18 TARGET_SYS= arm-poky-linux-gnueabi MACHINE = zedboard DISTRO= poky DISTRO_VERSION= 1.4+snapshot-20130716 TUNE_FEATURES = armv7a vfp neon zynq TARGET_FPU= vfp-neon meta meta-yocto= master:3dee534f1e25109e0bdb681de0746c336f4b8840 meta-xilinx meta-kc705 meta-zc702 meta-zedboard = master:46f4c79d6d55b556a90bb0fd89c2c09acf2aebff meta-oe = master:c383d6230942bb1558cee02764bced09031cb70f meta-java = master:59696d89fd33df6953dcb2dd54ccd3b362513f28 meta-yocto-bsp= master:3dee534f1e25109e0bdb681de0746c336f4b8840 WARNING: QA Issue: Found library in wrong location: /usr/bin/qt4/examples/tools/plugandpaint/plugins/libpnp_extrafilters.so Found library in wrong location: /usr/bin/qt4/examples/tools/plugandpaint/plugins/.debug/libpnp_extrafilters.so Found library in wrong location: /usr/bin/qt4/examples/tools/styleplugin/styles/libsimplestyleplugin.so Found library in wrong location: /usr/bin/qt4/examples/tools/styleplugin/styles/.debug/libsimplestyleplugin.so Found library in wrong location: /usr/bin/qt4/examples/tools/echoplugin/plugin/libechoplugin.so Found library in wrong location: /usr/bin/qt4/examples/tools/echoplugin/plugin/.debug/libechoplugin.so Found library in wrong location: /usr/bin/qt4/examples/declarative/cppextensions/qwidgets/QWidgets/libqmlqwidgetsplugin.so Found library in wrong location: /usr/bin/qt4/examples/declarative/cppextensions/qwidgets/QWidgets/.debug/libqmlqwidgetsplugin.so Found library in wrong location: /usr/bin/qt4/examples/declarative/cppextensions/plugins/libqmlqwidgetsplugin.so Found library in wrong location: /usr/bin/qt4/examples/declarative/cppextensions/plugins/.debug/libqmlqwidgetsplugin.so Found library in wrong location: /usr/bin/qt4/examples/declarative/cppextensions/plugins/com/nokia/TimeExample/libqmlqtimeexampleplugin.so Found library in wrong location: /usr/bin/qt4/examples/declarative/cppextensions/plugins/com/nokia/TimeExample/.debug/libqmlqtimeexampleplugin.so Found library in wrong location: /usr/bin/qt4/examples/declarative/cppextensions/imageprovider/ImageProviderCore/libqmlimageproviderplugin.so Found library in wrong location: /usr/bin/qt4/examples/declarative/cppextensions/imageprovider/ImageProviderCore/.debug/libqmlimageproviderplugin.so ERROR: QA Issue: File '/usr/plugins/designer/libqwt_designer_plugin.so' from qwt was already stripped, this will prevent future debugging! ERROR: QA Issue: File '/usr/lib/libqwt.so.6.0.1' from qwt was already stripped, this will prevent future debugging! ERROR: QA Issue: File '/usr/lib/libqwtmathml.so.6.0.1' from qwt was already stripped, this will prevent future debugging! WARNING: QA Issue: Found library in wrong location: /usr/plugins/designer/libqwt_designer_plugin.so ERROR: QA run found fatal errors. Please consider fixing them. ERROR: Function failed: do_package_qa ERROR: Logfile of failure stored in: /home/vidal/POKY/build071613_zedboard/poky/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/qwt/6.0.1-r1/temp/log.do_package.27159 ERROR: Task 1126 (/home/vidal/POKY/build071613_zedboard/poky/meta-oe/meta-oe/recipes-qt/qwt/ qwt_6.0.1.bb, do_package) failed with exit code '1' NOTE: Tasks Summary: Attempted 4315 tasks of which 368 didn't need to be rerun and 1 failed. Waiting for 0 running tasks to finish: Summary: 1 task failed: /home/vidal/POKY/build071613_zedboard/poky/meta-oe/meta-oe/recipes-qt/qwt/ qwt_6.0.1.bb, do_package Summary: There were 5 WARNING messages shown. Summary: There were 5 ERROR messages shown, returning a non-zero exit code. I will be looking where the qt libs need to be installed. Thanks ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] zedboard gnuradio
Paul, I opted for options b.) modifying /home/vidal/POKY/build071613_zedboard/poky/meta-yocto/conf/distro/poky.conf mvoing already-stripped from ERROR_QA to WARN_QA . Build is currently in progress. My question will option a.) need to be done to prevent this from occurring in future releases. Thanks not working with the variables would have made this extremely difficult to find and fix. On Tue, Jul 16, 2013 at 11:50 AM, Paul Eggleton paul.eggle...@linux.intel.com wrote: Hi Edward, On Tuesday 16 July 2013 08:47:03 Edward Vidal wrote: ERROR: QA Issue: File '/usr/plugins/designer/libqwt_designer_plugin.so' from qwt was already stripped, this will prevent future debugging! ERROR: QA Issue: File '/usr/lib/libqwt.so.6.0.1' from qwt was already stripped, this will prevent future debugging! ERROR: QA Issue: File '/usr/lib/libqwtmathml.so.6.0.1' from qwt was already stripped, this will prevent future debugging! poky.conf now marks this QA issue as an error instead of a warning in order to pick up on quality issues when running builds. You can either: a) Fix the recipe so that qwt gets built without stripping its output binaries, or b) set your own value for ERROR_QA and WARN_QA so that already-stripped appears in WARN_QA rather than ERROR_QA Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] zedboard gnuradio
Hello, with the change that Paul recommended the errors turned into 4 warnings ERROR: QA Issue: File '/usr/plugins/designer/libqwt_designer_plugin.so' from qwt was already stripped, this will prevent future debugging! ERROR: QA Issue: File '/usr/lib/libqwt.so.6.0.1' from qwt was already stripped, this will prevent future debugging! ERROR: QA Issue: File '/usr/lib/libqwtmathml.so.6.0.1' from qwt was already stripped, this will prevent future debugging! WARNING: QA Issue: Found library in wrong location: /usr/plugins/designer/libqwt_designer_plugin.so ERROR: QA run found fatal errors. Please consider fixing them. ERROR: Function failed: do_package_qa ERROR: Logfile of failure stored in: /home/vidal/POKY/build071613_zedboard/poky/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/qwt/6.0.1-r1/temp/log.do_package.27159 ERROR: Task 1126 (/home/vidal/POKY/build071613_zedboard/poky/meta-oe/meta-oe/recipes-qt/qwt/ qwt_6.0.1.bb, do_package) failed with exit code '1' WARNING: QA Issue: File '/usr/plugins/designer/libqwt_designer_plugin.so' from qwt was already stripped, this will prevent future debugging! WARNING: QA Issue: File '/usr/lib/libqwt.so.6.0.1' from qwt was already stripped, this will prevent future debugging! WARNING: QA Issue: File '/usr/lib/libqwtmathml.so.6.0.1' from qwt was already stripped, this will prevent future debugging! WARNING: QA Issue: Found library in wrong location: /usr/plugins/designer/libqwt_designer_plugin.so NOTE: Tasks Summary: Attempted 4333 tasks of which 3960 didn't need to be rerun and all succeeded Thanks for all the help.. On Tue, Jul 16, 2013 at 1:18 PM, Edward Vidal vidal.devel...@gmail.comwrote: Paul, I opted for options b.) modifying /home/vidal/POKY/build071613_zedboard/poky/meta-yocto/conf/distro/poky.conf mvoing already-stripped from ERROR_QA to WARN_QA . Build is currently in progress. My question will option a.) need to be done to prevent this from occurring in future releases. Thanks not working with the variables would have made this extremely difficult to find and fix. On Tue, Jul 16, 2013 at 11:50 AM, Paul Eggleton paul.eggle...@linux.intel.com wrote: Hi Edward, On Tuesday 16 July 2013 08:47:03 Edward Vidal wrote: ERROR: QA Issue: File '/usr/plugins/designer/libqwt_designer_plugin.so' from qwt was already stripped, this will prevent future debugging! ERROR: QA Issue: File '/usr/lib/libqwt.so.6.0.1' from qwt was already stripped, this will prevent future debugging! ERROR: QA Issue: File '/usr/lib/libqwtmathml.so.6.0.1' from qwt was already stripped, this will prevent future debugging! poky.conf now marks this QA issue as an error instead of a warning in order to pick up on quality issues when running builds. You can either: a) Fix the recipe so that qwt gets built without stripping its output binaries, or b) set your own value for ERROR_QA and WARN_QA so that already-stripped appears in WARN_QA rather than ERROR_QA Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] zedboard gnuradio
Hello,
Any and all help will be appreciated. I am trying to build gnuradio for
the zedboard.
After removing poky to clean out older builds
cd ~/POKY/build071513_zedboard/
cp -R ~/POKY/meta_data_from_remotes/poky/ .
cd poky/
cp -R ~/POKY/meta_data_from_remotes/meta-xilinx/ .
cp -R ~/POKY/meta_data_from_remotes/meta-oe/ .
cp -R ~/POKY/meta_data_from_remotes/meta-java/ .
. oe-init-build-env
cp ~/POKY/build071513_zedboard/local.conf conf/
cp ~/POKY/build071513_zedboard/bblayers.conf conf/
~/POKY/build071513_zedboard/core-image-minimal-ex.bb
DESCRIPTION = A small image just capable of allowing a device to boot.
IMAGE_INSTALL = packagegroup-core-boot ${ROOTFS_PKGMANAGE_BOOTSTRAP}
${CORE_IMAGE_EXTRA_INSTALL} gnuradio python-netserver
IMAGE_LINGUAS =
LICENSE = MIT
inherit core-image
IMAGE_ROOTFS_SIZE = 8192
cp
~/POKY/build071513_zedboard/core-image-minimal-ex.bb../meta/recipes-core/images/
**reverting back to boost-1.53.0*
cd ../meta/recipes-support/boost/
mkdir tmp
mv bjam-native_1.54.0.bb tmp/
mv boost_1.54.0.bb tmp/
mv boost-1.54.0.inc tmp/
mv boost.inc tmp/
mv files/ tmp/
/home/vidal/POKY/build071513_zedboard/poky/meta/recipes-support/boost
ls -la
total 36
drwxr-xr-x 4 vidal users 4096 Jul 15 16:02 .
drwxr-xr-x 59 vidal users 4096 Jul 15 15:53 ..
-rw-r--r-- 1 vidal users 261 Jul 15 16:02 bjam-native_1.53.0.bb
-rw-r--r-- 1 vidal users 109 Jul 15 16:02 boost_1.53.0.bb
-rw-r--r-- 1 vidal users 840 Jul 15 16:02 boost-1.53.0.inc
-rw-r--r-- 1 vidal users 6413 Jul 15 16:02 boost.inc
drwxr-xr-x 2 vidal users 4096 Jul 15 16:02 files
drwxr-xr-x 3 vidal users 4096 Jul 15 15:58 tmp
ls -la tmp/
total 32
drwxr-xr-x 3 vidal users 4096 Jul 15 15:58 .
drwxr-xr-x 4 vidal users 4096 Jul 15 16:02 ..
-rw-r--r-- 1 vidal users 261 Jul 15 15:53 bjam-native_1.54.0.bb
-rw-r--r-- 1 vidal users 98 Jul 15 15:53 boost_1.54.0.bb
-rw-r--r-- 1 vidal users 839 Jul 15 15:53 boost-1.54.0.inc
-rw-r--r-- 1 vidal users 6413 Jul 15 15:53 boost.inc
drwxr-xr-x 2 vidal users 4096 Jul 15 15:53 files
**reverting back to boost-1.53.0*
cd /home/vidal/POKY
cd test_meta/poky/meta/recipes-support/boost/
cp -R * ~/POKY/build071513_zedboard/poky/meta/recipes-support/boost/
cd ~/POKY/build071513_zedboard/poky/
. oe-init-build-env
MACHINE=zedboard bitbake core-image-minimal-ex see contents of file above.
Build Configuration:
BB_VERSION= 1.19.1
BUILD_SYS = x86_64-linux
NATIVELSBSTRING = Fedora-18
TARGET_SYS= arm-poky-linux-gnueabi
MACHINE = zedboard
DISTRO= poky
DISTRO_VERSION= 1.4+snapshot-20130715
TUNE_FEATURES = armv7a vfp neon zynq
TARGET_FPU= vfp-neon
meta
meta-yocto= master:4285e856aa073979bf046168a75188ccf5a1e7d4
meta-xilinx
meta-kc705
meta-zc702
meta-zedboard = master:0a210a7ea2bebd95d928f8c647b551a3f6abeffe
meta-oe = master:9d53e8111db2a1dc2a3df05926d90988c08e7dbe
meta-java = master:59696d89fd33df6953dcb2dd54ccd3b362513f28
meta-yocto-bsp= master:4285e856aa073979bf046168a75188ccf5a1e7d4
The above build consists 4341 tasks
During the compile of gnuradio-3.6.5 The following warning was displayed.
WARNING: QA Issue: Found library in wrong location:
/usr/bin/qt4/examples/tools/plugandpaint/plugins/libpnp_extrafilters.so
Found library in wrong location:
/usr/bin/qt4/examples/tools/plugandpaint/plugins/.debug/libpnp_extrafilters.so
Found library in wrong location:
/usr/bin/qt4/examples/tools/styleplugin/styles/libsimplestyleplugin.so
Found library in wrong location:
/usr/bin/qt4/examples/tools/styleplugin/styles/.debug/libsimplestyleplugin.so
Found library in wrong location:
/usr/bin/qt4/examples/tools/echoplugin/plugin/libechoplugin.so
Found library in wrong location:
/usr/bin/qt4/examples/tools/echoplugin/plugin/.debug/libechoplugin.so
Found library in wrong location:
/usr/bin/qt4/examples/declarative/cppextensions/qwidgets/QWidgets/libqmlqwidgetsplugin.so
Found library in wrong location:
/usr/bin/qt4/examples/declarative/cppextensions/qwidgets/QWidgets/.debug/libqmlqwidgetsplugin.so
Found library in wrong location:
/usr/bin/qt4/examples/declarative/cppextensions/plugins/libqmlqwidgetsplugin.so
Found library in wrong location:
/usr/bin/qt4/examples/declarative/cppextensions/plugins/.debug/libqmlqwidgetsplugin.so
Found library in wrong location:
/usr/bin/qt4/examples/declarative/cppextensions/plugins/com/nokia/TimeExample/libqmlqtimeexampleplugin.so
Found library in wrong location:
/usr/bin/qt4/examples/declarative/cppextensions/plugins/com/nokia/TimeExample/.debug/libqmlqtimeexampleplugin.so
Found library in wrong location:
/usr/bin/qt4/examples/declarative/cppextensions/imageprovider/ImageProviderCore/libqmlimageproviderplugin.so
Found library in wrong location:
/usr/bin/qt4/examples/declarative/cppextensions/imageprovider/ImageProviderCore/.debug/libqmlimageproviderplugin.so
The following errors prevented the completion of the tasks 4341
ERROR: QA Issue:
[yocto] poky and gnuradio
Hello, What is the best method to you the dylan branch of meta-oe with an gnuradio from meta-oe = (nobranch):ed84e64d22400595b68da4e75b48ab7ecc342aa9? Any and all help will be appreciated. Build Configuration: BB_VERSION= 1.18.0 BUILD_SYS = x86_64-linux NATIVELSBSTRING = Fedora-18 TARGET_SYS= arm-poky-linux-gnueabi MACHINE = beagleboard DISTRO= poky DISTRO_VERSION= 1.4.1 TUNE_FEATURES = armv7a vfp neon TARGET_FPU= vfp-neon meta meta-yocto= dylan:64273e53f2789d2ea8393fc80909ac7086f168a7 meta-oe = dylan:13ae5105ee30410136beeae66ec41ee4a8a2e2b0 meta-java = master:59696d89fd33df6953dcb2dd54ccd3b362513f28 meta-yocto-bsp= dylan:64273e53f2789d2ea8393fc80909ac7086f168a7 The above build gets the following errors. ERROR: Fetcher failure for URL: ' http://files.ettus.com/binaries/uhd_stable/releases/uhd_003.005.002-release/uhd-images_003.005.002-release.tar.gz'. Checksum mismatch! ERROR: Function failed: Fetcher failure for URL: ' http://files.ettus.com/binaries/uhd_stable/releases/uhd_003.005.002-release/uhd-images_003.005.002-release.tar.gz'. Unable to fetch URL from any source. ERROR: Logfile of failure stored in: /home/vidal/POKY/build070913_dylan/poky/build/tmp/work/all-poky-linux/uhd-firmware/1_003.005.002-r0/temp/log.do_fetch.28656 ERROR: Task 3499 (/home/vidal/POKY/build070913_dylan/poky/meta-oe/meta-oe/recipes-connectivity/uhd/ uhd-firmware_003.005.002.bb, do_fetch) failed with exit code '1' I went back to a meta-oe branch that I had built for the beagleboard, beaglebone, and pandaboard. Build Configuration: BB_VERSION= 1.18.0 BUILD_SYS = x86_64-linux NATIVELSBSTRING = Fedora-18 TARGET_SYS= arm-poky-linux-gnueabi MACHINE = beagleboard DISTRO= poky DISTRO_VERSION= 1.4.1 TUNE_FEATURES = armv7a vfp neon TARGET_FPU= vfp-neon meta meta-yocto= dylan:64273e53f2789d2ea8393fc80909ac7086f168a7 meta-oe = (nobranch):ed84e64d22400595b68da4e75b48ab7ecc342aa9 meta-java = master:59696d89fd33df6953dcb2dd54ccd3b362513f28 meta-yocto-bsp= dylan:64273e53f2789d2ea8393fc80909ac7086f168a7 Thanks ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] poky and gnuradio
Phillip, This just started after a git pull of meta-oe This is what I found in /home/vidal/POKY/build070913_dylan/poky/build/tmp/work/all-poky-linux/uhd-firmware/1_003.005.002-r0/temp/less log.do_fetch.28656 wget -t 2 -T 30 -nv --passive-ftp --no-check-certificate -P /home/vidal/POKY/linux_src_dnloads/downloads ' http://sources.openembedded.org/uhd-images_003.005.002-release.tar.gz' http://sources.openembedded.org/uhd-images_003.005.002-release.tar.gz: 2013-07-09 19:08:10 ERROR 404: Not Found. I tried the above in a shell. I also tried with firefox ' http://sources.openembedded.org/uhd-images_003.005.002-release.tar.gz' I get the same error. This new version of branch dylan does not include the gsl-1.15 (that you added for me) instead it has gsl-1.12. I also have not the upgrade of gnuplot-4.4.4 to gnuplot-4.6.3 Let me know if I can provide other information. Thanks On Tue, Jul 9, 2013 at 6:49 PM, Philip Balister phi...@balister.org wrote: It is not clear from your email if the failure is only with dylan. Does one work and another build fail? Can you wget the url it is trying to fetch? Philip On 07/09/2013 08:38 PM, Edward Vidal wrote: Hello, What is the best method to you the dylan branch of meta-oe with an gnuradio from meta-oe = (nobranch):ed84e64d22400595b68da4e75b48ab7ecc342aa9? Any and all help will be appreciated. Build Configuration: BB_VERSION= 1.18.0 BUILD_SYS = x86_64-linux NATIVELSBSTRING = Fedora-18 TARGET_SYS= arm-poky-linux-gnueabi MACHINE = beagleboard DISTRO= poky DISTRO_VERSION= 1.4.1 TUNE_FEATURES = armv7a vfp neon TARGET_FPU= vfp-neon meta meta-yocto= dylan:64273e53f2789d2ea8393fc80909ac7086f168a7 meta-oe = dylan:13ae5105ee30410136beeae66ec41ee4a8a2e2b0 meta-java = master:59696d89fd33df6953dcb2dd54ccd3b362513f28 meta-yocto-bsp= dylan:64273e53f2789d2ea8393fc80909ac7086f168a7 The above build gets the following errors. ERROR: Fetcher failure for URL: ' http://files.ettus.com/binaries/uhd_stable/releases/uhd_003.005.002-release/uhd-images_003.005.002-release.tar.gz '. Checksum mismatch! ERROR: Function failed: Fetcher failure for URL: ' http://files.ettus.com/binaries/uhd_stable/releases/uhd_003.005.002-release/uhd-images_003.005.002-release.tar.gz '. Unable to fetch URL from any source. ERROR: Logfile of failure stored in: /home/vidal/POKY/build070913_dylan/poky/build/tmp/work/all-poky-linux/uhd-firmware/1_003.005.002-r0/temp/log.do_fetch.28656 ERROR: Task 3499 (/home/vidal/POKY/build070913_dylan/poky/meta-oe/meta-oe/recipes-connectivity/uhd/ uhd-firmware_003.005.002.bb, do_fetch) failed with exit code '1' I went back to a meta-oe branch that I had built for the beagleboard, beaglebone, and pandaboard. Build Configuration: BB_VERSION= 1.18.0 BUILD_SYS = x86_64-linux NATIVELSBSTRING = Fedora-18 TARGET_SYS= arm-poky-linux-gnueabi MACHINE = beagleboard DISTRO= poky DISTRO_VERSION= 1.4.1 TUNE_FEATURES = armv7a vfp neon TARGET_FPU= vfp-neon meta meta-yocto= dylan:64273e53f2789d2ea8393fc80909ac7086f168a7 meta-oe = (nobranch):ed84e64d22400595b68da4e75b48ab7ecc342aa9 meta-java = master:59696d89fd33df6953dcb2dd54ccd3b362513f28 meta-yocto-bsp= dylan:64273e53f2789d2ea8393fc80909ac7086f168a7 Thanks ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
