I did as link "Re: Customizing Kernel", but got errors:
BB_VERSION = "1.24.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "Ubuntu-16.04"
TARGET_SYS = "i586-poky-linux"
MACHINE = "edison"
DISTRO = "poky-edison"
DISTRO_VERSION = "1.7.3"
TUNE_FEATURES = "m32 core2"
TARGET_FPU = ""
meta-yocto-bsp = "<unknown>:<unknown>"
NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
WARNING: Failed to fetch URL http://gnome-build-stage-1.googlecode.com/files/uuid-1.6.2.tar.gz, attempting MIRRORS if available
WARNING: Failed to fetch URL http://zlib.net/pigz/pigz-2.3.1.tar.gz, attempting MIRRORS if available
WARNING: Failed to fetch URL http://www.hboehm.info/gc/gc_source/gc-7.4.2.tar.gz, attempting MIRRORS if available
WARNING: Failed to fetch URL ftp://ftp.debian.org/debian/pool/main/b/base-passwd/base-passwd_3.5.29.tar.gz, attempting MIRRORS if available
WARNING: QA Issue: cacao-native: configure was passed unrecognised options: --with-classpath-libdir --with-classpath-includedir --with-classpath-classes [unknown-configure-option]
WARNING: Failed to fetch URL http://downloads.sourceforge.net/project/libpng/libpng16/1.6.13/libpng-1.6.13.tar.xz, attempting MIRRORS if available
ERROR: Function failed: do_configure (log file is located at /home/user/work/edison35/iot-devkit-yp-poky-edison-20160606/build_edison/tmp/work/x86_64-linux/qemu-native/2.1.0-r0/temp/log.do_configure.59808)
ERROR: Logfile of failure stored in: /home/user/work/edison35/iot-devkit-yp-poky-edison-20160606/build_edison/tmp/work/x86_64-linux/qemu-native/2.1.0-r0/temp/log.do_configure.59808
Log data follows:
| DEBUG: Executing python function sysroot_cleansstate
| DEBUG: Python function sysroot_cleansstate finished
| DEBUG: Executing shell function autotools_preconfigure
| DEBUG: Shell function autotools_preconfigure finished
| DEBUG: Executing python function autotools_copy_aclocals
| DEBUG: Python function autotools_copy_aclocals finished
| DEBUG: Executing shell function do_configure
| ERROR: alsa check failed
| Make sure to have the alsa libs and headers installed.
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_configure (log file is located at /home/user/work/edison35/iot-devkit-yp-poky-edison-20160606/build_edison/tmp/work/x86_64-linux/qemu-native/2.1.0-r0/temp/log.do_configure.59808)
ERROR: Task 2427 (virtual:native:/home/user/work/edison35/iot-devkit-yp-poky-edison-20160606/build_edison/../poky/meta/recipes-devtools/qemu/qemu_2.1.0.bb, do_configure) failed with exit code '1'
I myself never managed to build the image like this.
Intel has provided a setup script to start the edison build correctly. Before source oe-init-build-env use poky/meta-intel-edison/setup.sh then follow the instructions given by the script.
Very strange solutions are offered by Intel for building the image. I was confused
Solution 1: From the official documentation I need to download "edison-src.tgz", but it is not present in the download section of Intel site.
Solution 2: There is a the repository (http://iotdk.intel.com/), which I found in google, not in documentation.
This resource (http://iotdk.intel.com/) contains archive (http://iotdk.intel.com/src/3.5/edison/iot-devkit-yp-poky-edison-20160606.zip),
which is also not build.
Where is the official (by 2016 year) "HowToGuide" to build image of Edison?
The archive I used was this:
This is the source of the complete Yocto build environment. The edison system is a special subset of the many possible yocto outcomes (layers).
What do you aim exactly? This source image is for those, who want to build their own edison file system image. You may need it if you want to reconfigure (and rebuild) the kernel, or want your own system to install in a multitude of Edisons, or want to have a copy on your desktop machine for cross-compilation. You download the source, build it, then flash the result Edison file system to the board. Now modify it, and rebuild - this time it goes way faster - and flash again.
To achieve this, follow the instructions in: http://www.intel.com/content/dam/support/us/en/documents/edison/sb/edisonbsp_ug_331188007.pdf
However, to simply re-flash the Edison with the latest image, you don't need to build it from scratch, a ready edison image will do. Sorry, but this moment I don't know the link to the latest image. If this is what you need, I can look it up later.
What do you aim exactly?
I want to build own Edison's image. But ... instructions from http://www.intel.com/content/dam/support/us/en/documents/edison/sb/edisonbsp_ug_331188007.pdf at 2015 year and iot-devkit-yp-poky-edison-20160606.zip at 2016 year ARE DIFFERENT.
In consequence of this divergence to build the image (20160606.zip) by the instructions does not work. Where can I find instructions for build 20160606.zip.
Maybe someone can me write a sequence of steps for build 20160606 which he made in terminal. Maybe someone can write the log terminal sequences of commands, which he actually performed?
I have been down this route lately. The BSP document is the best guideline, though I found it too a bit outdated.
After several error messages I finally managed. The process you can read here:
NFS server on Edison The parts you may need, are from post 12.
My aim was the NFS server, which finally failed, but in the meantime I managed to build the 20160606 image.
Most likely you will meet some error messages in the process. Some you may find a solution in this blog, some may be new. To build an embedded linux image is newer a flawless process.
If you send me the error messages, I may be able to help you. (MAY be).
I have built an edison image with the latest source code(20160606) by the procedure described in the 2015 BSP doc( http://www.intel.com/content/dam/support/us/en/documents/edison/sb/edisonbsp_ug_331188007.pdf).
However, I've never flash it to my edison and I'm not sure if the built image is identical with the one available at the Intel's download site.
I share the info for some help.
Please refer to the post and try Step1 to Step5.
Then run the following command:
- sudo ../../../meta-intel-edison/utils/flash/postBuild.sh .
and you can find image files including flash scripts under ./toFlash dir.
I have the same，how to solve it？