6 Replies Latest reply on Nov 12, 2015 7:45 AM by Intel_Alvarado

    edison-image unavailable to bitbake

    s89

      I’m following the BSP user guide and trying to compile my first image. When I run `bitbake edison-image`, I get an error: Nothing PROVIDES 'edison-image'. How to proceed?

        • 1. Re: edison-image unavailable to bitbake
          s89

          Fixed by starting all over, not sure what went wrong in my first attempt.

          • 2. Re: edison-image unavailable to bitbake
            Intel_Alvarado

            Hi,

             

            Are you adding any third party packages to the image? In what OS are you running these tests? What is the complete error message you receive? What previous steps from the guide have you followed?

            EDIT: I noticed you already have found the solution for your question. In the future, if you have any other questions don't hesitate to contact us.

             

            Sergio

            • 3. Re: edison-image unavailable to bitbake
              Tayc

              I'm having this same problem, I tried doing all the steps again, but to no avail.

              I'm trying to build basic image before I add other packages. At this point I have not.
              I'm using poky 1.7.2 , Ubuntu 14.04 64 bit and this is the error message:

               

              me@mycomputer:~/poky/edison-src/build$ bitbake edison-image
              Parsing recipes: 100% |#########################################| Time: 00:00:54
              Parsing of 891 .bb files complete (0 cached, 891 parsed). 1287 targets, 40 skipped, 0 masked, 0 errors.
              ERROR: Nothing PROVIDES 'edison-image'
              
              Summary: There was 1 ERROR message shown, returning a non-zero exit code.
              

               

              I can post all the steps I did if this isn't enough...

              • 4. Re: edison-image unavailable to bitbake
                Intel_Alvarado

                Hi Tayc,

                 

                Yes, please post all the steps you followed prior to this error.

                 

                Sergio

                • 5. Re: edison-image unavailable to bitbake
                  Tayc

                  This is everything I have @Intel_

                  god@dv6:~/poky$ cd edison-src/
                  god@dv6:~/poky/edison-src$ mkdir bb_dl_dir && mkdirbb_ss_dir
                  mkdirbb_ss_dir: command not found
                  god@dv6:~/poky/edison-src$ mkdir bb_dl_dir && mkdir bb_ss_dir
                  mkdir: cannot create directory ‘bb_dl_dir’: File exists
                  god@dv6:~/poky/edison-src$ ./meta-intel-edison/setup.sh --dl_dir=/home/god/poky/edison-src/bb_dl_dir --sstate_dir=/home/god/poky/edison-src/bb_ss_dir
                  ERROR: '/home/god/poky/edison-src/bb_ss_dir' directory does not exist
                  Setup build environment for building the Edison Device Software
                  
                  ./setup.sh
                      -h --help            display this help and exit
                      --dl_dir=/home/god/poky/edison-src/bb_dl_dir    define the directory (absolute path) where bitbake places downloaded files
                      --sstate_dir=/home/god/poky/edison-src/bbcache/sstate-cache    define the directory (absolute path) where bitbake places shared-state files
                      --bb_number_thread=4        define how many tasks bitbake should run in parallel
                      --parallel_make=4        define how many processes make should run in parallel when running compile tasks
                      --mode=external            define whether we are working in development mode, i.e. with local version of the yocto recipes. Possible values are 'devenv' for setupping a development environment and 'external' for a regular build.
                      --build_name=Custom Edison build by god@dv6 2015-11-03 08:17:11 EST    defines custom build name which can then be retrieved on a running linux in /etc/version
                      --sdk_host=linux64        choose host machine on which the generated SDK and cross compiler will be run. Must be one of [linux32 linux64 win32 win64 macosx]
                      -l --list_sdk_hosts        list availables sdk host supported machines
                      --create_src_archive        when set, copies sources of all deployed packages into build/tmp/deploy/sources
                      --deb_packages        when set, use .deb package format instead of .ipk
                  
                  god@dv6:~/poky/edison-src$ mkdir bb_ss_dir
                  god@dv6:~/poky/edison-src$ ./meta-intel-edison/setup.sh --dl_dir=/home/god/poky/edison-src/bb_dl_dir --sstate_dir=/home/god/poky/edison-src/bb_ss_dir
                  We are building in external mode
                  Cloning into bare repository 'poky-mirror.git'...
                  remote: Counting objects: 290708, done.
                  remote: Compressing objects: 100% (71975/71975), done.
                  remote: Total 290708 (delta 214017), reused 289783 (delta 213092)
                  Receiving objects: 100% (290708/290708), 115.19 MiB | 763.00 KiB/s, done.
                  Resolving deltas: 100% (214017/214017), done.
                  Checking connectivity... done.
                  Cloning into bare repository 'meta-mingw-mirror.git'...
                  remote: Counting objects: 256, done.
                  remote: Compressing objects: 100% (191/191), done.
                  remote: Total 256 (delta 98), reused 203 (delta 45)
                  Receiving objects: 100% (256/256), 62.01 KiB | 0 bytes/s, done.
                  Resolving deltas: 100% (98/98), done.
                  Checking connectivity... done.
                  Cloning into bare repository 'meta-darwin-mirror.git'...
                  remote: Counting objects: 577, done.
                  remote: Compressing objects: 100% (329/329), done.
                  remote: Total 577 (delta 244), reused 522 (delta 189)
                  Receiving objects: 100% (577/577), 6.90 MiB | 745.00 KiB/s, done.
                  Resolving deltas: 100% (244/244), done.
                  Checking connectivity... done.
                  Cloning into bare repository 'meta-intel-iot-middleware-mirror.git'...
                  remote: Counting objects: 1008, done.
                  remote: Compressing objects: 100% (534/534), done.
                  remote: Total 1008 (delta 506), reused 880 (delta 380)
                  Receiving objects: 100% (1008/1008), 5.60 MiB | 685.00 KiB/s, done.
                  Resolving deltas: 100% (506/506), done.
                  Checking connectivity... done.
                  Cloning Poky in the /home/god/poky/edison-src/out/linux64/poky directory
                  Cloning into 'poky'...
                  done.
                  Note: checking out 'yocto-1.7.2'.
                  
                  You are in 'detached HEAD' state. You can look around, make experimental
                  changes and commit them, and you can discard any commits you make in this
                  state without impacting any branches by performing another checkout.
                  
                  If you want to create a new branch to retain commits you create, you may
                  do so (now or later) by using -b with the checkout command again. Example:
                  
                    git checkout -b new_branch_name
                  
                  HEAD is now at 29812e6... busybox: unbreak tar of uncompressed files
                  Cloning Mingw layer to /home/god/poky/edison-src/out/linux64/poky/meta-mingw directory from local cache
                  Cloning into 'meta-mingw'...
                  done.
                  Cloning Darwin layer to /home/god/poky/edison-src/out/linux64/poky/meta-darwin directory from local cache
                  Cloning into 'meta-darwin'...
                  done.
                  Note: checking out '29b5ff31cee24e796f2eb2d2fd1269e3e92c831c'.
                  
                  You are in 'detached HEAD' state. You can look around, make experimental
                  changes and commit them, and you can discard any commits you make in this
                  state without impacting any branches by performing another checkout.
                  
                  If you want to create a new branch to retain commits you create, you may
                  do so (now or later) by using -b with the checkout command again. Example:
                  
                    git checkout -b new_branch_name
                  
                  HEAD is now at 29b5ff3... gcc-runtime: Don't pollute global export namespace
                  Cloning meta-intel-iot-middleware layer to /home/god/poky/edison-src/out/linux64/poky/meta-intel-iot-middleware directory from local cache
                  Cloning into 'meta-intel-iot-middleware'...
                  done.
                  Note: checking out 'c6d681475e76107e6c04c5f7a06034dc9e772d1e'.
                  
                  You are in 'detached HEAD' state. You can look around, make experimental
                  changes and commit them, and you can discard any commits you make in this
                  state without impacting any branches by performing another checkout.
                  
                  If you want to create a new branch to retain commits you create, you may
                  do so (now or later) by using -b with the checkout command again. Example:
                  
                    git checkout -b new_branch_name
                  
                  HEAD is now at c6d6814... upm: Update to 0.3.1
                  Cloning meta-arduino layer to /home/god/poky/edison-src directory from GitHub.com/01org/meta-arduino
                  Cloning into 'meta-arduino'...
                  remote: Counting objects: 72, done.
                  remote: Total 72 (delta 0), reused 0 (delta 0), pack-reused 72
                  Unpacking objects: 100% (72/72), done.
                  Checking connectivity... done.
                  Already on '1.6.x'
                  Your branch is up-to-date with 'origin/1.6.x'.
                  Applying patch on poky
                  Initializing yocto build environment
                  Setting up yocto configuration file (in build/conf/local.conf)
                  ** Success **
                  SDK will be generated for linux64 host
                  Now run these two commands to setup and build the flashable image:
                  cd /home/god/poky/edison-src/out/linux64
                  source poky/oe-init-build-env
                  bitbake edison-image
                  *************
                  god@dv6:~/poky/edison-src$ source /home/god/poky/oe-init-build-env
                  You had no conf/local.conf file. This configuration file has therefore been
                  created for you with some default values. You may wish to edit it to use a
                  different MACHINE (target hardware) or enable parallel build options to take
                  advantage of multiple cores for example. See the file for more information as
                  common configuration options are commented.
                  
                  The Yocto Project has extensive documentation about OE including a reference manual
                  which can be found at:
                      http://yoctoproject.org/documentation
                  
                  For more information about OpenEmbedded see their website:
                      http://www.openembedded.org/
                  
                  You had no conf/bblayers.conf file. The configuration file has been created for
                  you with some default values. To add additional metadata layers into your
                  configuration please add entries to this file.
                  
                  The Yocto Project has extensive documentation about OE including a reference manual
                  which can be found at:
                      http://yoctoproject.org/documentation
                  
                  For more information about OpenEmbedded see their website:
                      http://www.openembedded.org/
                  
                  
                  
                  ### Shell environment set up for builds. ###
                  
                  You can now run 'bitbake <target>'
                  
                  Common targets are:
                      core-image-minimal
                      core-image-sato
                      meta-toolchain
                      adt-installer
                      meta-ide-support
                  
                  You can also run generated qemu images with a command like 'runqemu qemux86'
                  god@dv6:~/poky/edison-src/build$ bitbake edison-image
                  Parsing recipes: 100% |#########################################| Time: 00:00:54
                  Parsing of 891 .bb files complete (0 cached, 891 parsed). 1287 targets, 40 skipped, 0 masked, 0 errors.
                  ERROR: Nothing PROVIDES 'edison-image'
                  
                  Summary: There was 1 ERROR message shown, returning a non-zero exit code.
                  god@dv6:~/poky/edison-src/build$
                  
                  
                  
                  • 6. Re: edison-image unavailable to bitbake
                    Intel_Alvarado

                    Hi,

                     

                    I ran the test with the latest image and followed the similar steps. Notice in the log is a section that says:

                    ** Success ** 
                    SDK will be generated for linux64 host 
                    Now run these two commands to setup and build the flashable image: 
                    cd /home/god/poky/edison-src/out/linux64 
                    source poky/oe-init-build-env 
                    bitbake edison-image 
                    ************* 
                    

                     

                    I ran the commands for my settings and didn’t receive any errors. Go to the linux64 folder instead of the edison-src folder and then run the source and bitbake commands.

                    Let me know your results.

                     

                    Sergio

                    1 of 1 people found this helpful