10 Replies Latest reply on Mar 15, 2014 9:05 AM by AlexT_Intel

    How to use full_yocto_archive to build yocto image-full?

    Jacker.Wang

      I downloaded Board_Support_Package_Sources_for_Intel_Quark_v0.7.5_full_yocto_archive.tar.gz. Don't know how to use it.

      Is there any document or simple description on how to use it?

      I am in China, some websites are blocked, so always find some errors in building yocto image. Hope the full_yocto_archieve can solve the problem.

       

       

      thanks,

      Jacker

        • 1. Re: How to use full_yocto_archive to build yocto image-full?
          BillS

          For version 0.7.5 of the BSP

          the guide is "Quark_BSPBuildGuide_329687_001.pdf"

          There's a copy at

          https://communities.intel.com/servlet/JiveServlet/previewBody/21882-102-1-25153/Quark_BSPBuildGuide_329687_001.pdf

          For version 0.9.0, the guide is "Quark_BSP_BuildGuide_329687_004.pdf",

          the archive "Board_Support_Package_Sources_for_Intel_Quark_v0.9.0.7z"

          Both these "0.9.0"  files are at

          https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=23197

           

          If you can work with version 0.9.0 rather than 0.7.5,

          you can follow the instructions in chapter/section 5 of
          Quark_BSP_BuildGuide_329687_004.pdf

          But as a 'user' rather than as 'root'!

           

          They are:
          tar -xvf meta-clanton*.tar.gz
          cd meta-clanton*
          ./setup.sh

          source poky/oe-init-build-env yocto_build
          bitbake image-full-galileo

           

          These instructions worked for me on Scientific Linux 6.5

           

          Bill S.

          • 2. Re: How to use full_yocto_archive to build yocto image-full?
            Jacker.Wang

            Hi Bill,

            The instruction you listed is for standard building process. My question is how to use Board_Support_Package_Sources_for_Intel_Quark_v0.7.5_full_yocto_archive.tar.gz to build? It's different.

             

            I assume all dependency package source files are included in xxx_full_yocto_archive file, so the bitbake can get source file from local file system instead of from network.

             

            thanks,

            Jacker

            • 4. Re: How to use full_yocto_archive to build yocto image-full?
              AlexT_Intel

              It's more than 900MB, so I'm not ready to download it just to check :-)

               

              Please show me what's inside of that file, I may be able to advise better based on that information.

              • 5. Re: How to use full_yocto_archive to build yocto image-full?
                yuanpu

                directory like this, 900MB is not so large for china, other words our internet is fast then before?

                 

                in each dir include some gz file like gcc-runtime-4.7.2-r20 have gcc-runtime-4.7.2-r20.diff.gz and gcc-runtime-4.7.2-r20.showdata.dump

                 

                this is full yocto archive file tree:

                Board_Support_Package_Sources_for_Intel_Quark_v0.7.5_full_yocto_archive.tar.gz

                -GPL_COMPLIANCE

                ├─licenses

                │  ├─acl

                │  ├─acl-native

                │  ├─alsa-lib

                │  ├─alsa-state

                │  ├─alsa-tools

                │  ├─alsa-utils

                │  ├─apr-native

                │  ├─apr-util-native

                │  ├─attr

                │  ├─attr-native

                │  ├─autoconf-native

                │  ├─autogen-native

                │  ├─automake-native

                │  ├─base-files

                │  ├─base-passwd

                │  ├─bash

                │  ├─bdwgc-native

                │  ├─beecrypt-native

                │  ├─binutils-cross

                │  ├─binutils-native

                │  ├─bison-native

                │  ├─bluez-hcidump

                │  ├─bluez4

                │  ├─busybox

                │  ├─bzip2

                │  ├─bzip2-native

                │  ├─cdrtools-native

                │  ├─cmake-native

                │  ├─core-image-minimal-initramfs-clanton-20131010050201

                │  ├─curl

                │  ├─db

                │  ├─db-native

                │  ├─dbus

                │  ├─dbus-glib

                │  ├─dbus-glib-native

                │  ├─dbus-native

                │  ├─depmodwrapper-cross

                │  ├─diffutils

                │  ├─dosfstools-native

                │  ├─e2fsprogs

                │  ├─e2fsprogs-native

                │  ├─elfutils-native

                │  ├─ethtool

                │  ├─expat

                │  ├─expat-native

                │  ├─file-native

                │  ├─flac

                │  ├─flex-native

                │  ├─galileo-target

                │  ├─gawk

                │  ├─gcc-cross

                │  ├─gcc-cross-initial

                │  ├─gcc-runtime

                │  ├─gdbm

                │  ├─gdbm-native

                │  ├─genext2fs-native

                │  ├─gettext

                │  ├─gettext-minimal-native

                │  ├─gettext-native

                │  ├─glib-2.0

                │  ├─glib-2.0-native

                │  ├─gmp-native

                │  ├─gnu-config-native

                │  ├─gnu-efi

                │  ├─gnutls

                │  ├─gnutls-native

                │  ├─gperf-native

                │  ├─grub

                │  ├─grub-conf

                │  ├─grub-efi-i586-native

                │  ├─gtk-doc-stub-native

                │  ├─guile-native

                │  ├─guilt-native

                │  ├─icu-native

                │  ├─image-full

                │  ├─image-full-clanton-20131010050201

                │  ├─init-ifupdown

                │  ├─initramfs-live-boot

                │  ├─initscripts

                │  ├─jpeg

                │  ├─kern-tools-native

                │  ├─kmod

                │  ├─kmod-native

                │  ├─liba52

                │  ├─libav

                │  ├─libcap

                │  ├─libcap-native

                │  ├─libcheck

                │  ├─libdrm

                │  ├─libffi

                │  ├─libffi-native

                │  ├─libgcc

                │  ├─libgcrypt

                │  ├─libgcrypt-native

                │  ├─libgpg-error

                │  ├─libgpg-error-native

                │  ├─libiconv

                │  ├─libmpc-native

                │  ├─libnl

                │  ├─libogg

                │  ├─libpcap

                │  ├─libpciaccess

                │  ├─libpcre

                │  ├─libpcre-native

                │  ├─libpng

                │  ├─libpthread-stubs

                │  ├─libsamplerate0

                │  ├─libsdl

                │  ├─libsndfile1

                │  ├─libtasn1

                │  ├─libtasn1-native

                │  ├─libtheora

                │  ├─libtool

                │  ├─libtool-cross

                │  ├─libtool-native

                │  ├─libunistring-native

                │  ├─libusb-compat

                │  ├─libusb1

                │  ├─libvorbis

                │  ├─libvpx

                │  ├─libxml2-native

                │  ├─libxslt-native

                │  ├─linux-firmware

                │  ├─linux-libc-headers

                │  ├─linux-yocto-clanton

                │  ├─linuxptp

                │  ├─lzo

                │  ├─lzo-native

                │  ├─m4-native

                │  ├─makedepend-native

                │  ├─makedevs-native

                │  ├─mesa

                │  ├─mklibs-native

                │  ├─modutils-initscripts

                │  ├─mpfr-native

                │  ├─mtd-utils

                │  ├─mtools-native

                │  ├─ncurses

                │  ├─ncurses-native

                │  ├─neon-native

                │  ├─netbase

                │  ├─nodejs

                │  ├─ocf-linux

                │  ├─ocf-linux-native

                │  ├─opencv

                │  ├─openssh

                │  ├─openssl

                │  ├─openssl-native

                │  ├─opkg

                │  ├─opkg-collateral

                │  ├─opkg-config-base

                │  ├─opkg-native

                │  ├─opkg-utils-native

                │  ├─ossp-uuid-native

                │  ├─packagegroup-core-boot

                │  ├─pciutils

                │  ├─pigz-native

                │  ├─pkgconfig-native

                │  ├─pointercal

                │  ├─poky-feed-config-opkg

                │  ├─popt-native

                │  ├─ppp

                │  ├─prelink-native

                │  ├─pseudo-native

                │  ├─python

                │  ├─python-argparse-native

                │  ├─python-native

                │  ├─python-nose

                │  ├─python-numpy

                │  ├─python-setuptools-native

                │  ├─qemuwrapper-cross

                │  ├─quilt-native

                │  ├─readline

                │  ├─readline-native

                │  ├─rpm-native

                │  ├─run-postinsts

                │  ├─shadow

                │  ├─shadow-native

                │  ├─shadow-securetty

                │  ├─shadow-sysroot

                │  ├─sqlite3

                │  ├─sqlite3-native

                │  ├─strace

                │  ├─subversion-native

                │  ├─swig

                │  ├─swig-native

                │  ├─sysvinit

                │  ├─sysvinit-inittab

                │  ├─tiff

                │  ├─tslib

                │  ├─uclibc

                │  ├─uclibc-initial

                │  ├─udev

                │  ├─udev-extraconf

                │  ├─unifdef-native

                │  ├─update-rc.d

                │  ├─update-rc.d-native

                │  ├─usbutils

                │  ├─util-linux

                │  ├─util-linux-native

                │  ├─util-macros

                │  ├─util-macros-native

                │  ├─v4l-utils

                │  ├─wayland

                │  ├─wayland-native

                │  ├─wireless-tools

                │  ├─wpa-supplicant

                │  ├─x264

                │  ├─xproto-native

                │  ├─xz

                │  ├─xz-native

                │  ├─yasm-native

                │  ├─zlib

                │  └─zlib-native

                └─source

                    ├─acl-2.2.51-r3

                    ├─alsa-lib-1.0.26-r0

                    ├─alsa-tools-1.0.26.1-r1

                    ├─attr-2.4.46-r4

                    ├─base-files-3.0.14-r73

                    ├─bluez4-4.101-r5

                    ├─busybox-1.20.2-r8

                    ├─e2fsprogs-1.42.7-r0

                    ├─flac-1.2.1-r4

                    ├─galileo-target-0.1-r0

                    ├─gawk-4.0.2-r0

                    ├─gcc-runtime-4.7.2-r20

                    ├─gdbm-1.10-r3

                    ├─glib-2.0-1_2.34.3-r2

                    ├─gnutls-2.12.23-r8.4

                    ├─init-ifupdown-1.0-r0

                    ├─initscripts-1.0-r140

                    ├─libcap-2.22-r5

                    ├─libgcc-4.7.2-r20

                    ├─libgcrypt-1.5.0-r2

                    ├─libgpg-error-1.11-r0

                    ├─libnl-1_3.2.21-r0

                    ├─libsdl-1.2.15-r2

                    ├─libsndfile1-1.0.25-r1

                    ├─libtasn1-2.14-r1

                    ├─linux-libc-headers-3.8-r0

                    ├─linux-yocto-clanton-3.8-r0

                    ├─linuxptp-20121116-r0

                    ├─netbase-1_5.0-r0

                    ├─ppp-2.4.5-r6

                    ├─python-nose-1.2.1-r0

                    ├─sysvinit-inittab-2.88dsf-r9

                    ├─tslib-1.0+gitrAUTOINC+e17263ef401ee885a27d649b90b577cfb44500e0-r1

                    ├─udev-182-r7

                    ├─util-linux-2.22.2-r3

                    ├─wireless-tools-1_29-r4

                    ├─x264-r2230+git-r1

                    └─xz-5.1.2alpha-r0

                • 6. Re: How to use full_yocto_archive to build yocto image-full?
                  AlexT_Intel

                  Well, my internet link is not that bad :-) It's just not immediate still with 900MB file :-)

                   

                  The contents is apparently not the same as what the usual build process generates or uses as the sources, so I'm afraid without detailed digging in I won't be able to advise more and unfortunately I won't have time for that for at least nearest couple of weeks...

                   

                  How could I help you, let me think... Aren't there any readmes in that archive, which would shed some light onto that?

                   

                  At the end of the day, if nothing else works and you have some web space of about 10-20GB, I can just run a build once on a freshly unpacked sources (that will fetch all the respective pieces), then compress the whole thing and upload it for you. That would take quite some time, but if that helps you, well, why not :-)

                  • 7. Re: How to use full_yocto_archive to build yocto image-full?
                    yuanpu

                    it is really nice, i build clanton v0.9 on ubuntu failed, v1.0 on ubuntu failed, v1.0 on debian succeed but does not boot on galileo.

                     

                    i just want use c instead of arduino ide, so you can help me out may lead to a  word peace come true.

                      thank you again.

                    • 8. Re: How to use full_yocto_archive to build yocto image-full?
                      AlexT_Intel

                      Ah, okay, so your goal is to compile C programs? If so, you don't really need the Yocto stuff. You could generate the cross-toolchain out of it, true, but there's something more interesting I think.

                       

                      On MWC they've introduced something called IoT Developer Kit, which is a USB thumbdrive image with cross-toolchain and Eclipse and necessary utilities to make it easier to upload programs directly to Galileo. I'd suggest you to give it a try, as it seems to be the best match for your needs.

                       

                      Check it out here: IoT Developer Kit

                      • 9. Re: How to use full_yocto_archive to build yocto image-full?
                        yuanpu

                        yes, you are right  my first goal is compile C programs. and 2 is fun(see what galileo can do with full image.)

                        i am downloading devkit-live-img-final.bin and as a newbie a read the Intel-DeveKit-Tutorial-Guide.pdf, and i learned that

                        make a cross-toolchain and compile C programs on galileo may not be a best choice, after all desktop laptop may be more quick to do that.

                        i am waiting for intel give as a zip file like LINUX_IMAGE_FOR_SD_Intel_Galileo_v0.7.5.7z enable us to have fun with full feature of clanton linux on galileo, because i built it with 3 of different distribution of linux and failed.

                        as loT Developer Kit, i think i will unzip it ,and copy eclipse and uclibc lib and compile to my windows 7 and compile C programs first make some interesting things.

                         

                        and thank you again, you such Enthusiasts(from google translate)hope can help more new to galileo like me .

                        • 10. Re: How to use full_yocto_archive to build yocto image-full?
                          AlexT_Intel

                          You are welcome :-) Feel free to ask here if you face any further problems.