- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Has anybody successfully built Edison image with the latest version (iot-devkit-yp-poky-edison-20160315) yet?
I have downloaded the latest Edison BSP source package from http://iotdk.intel.com/src/3.0/edison/iot-devkit-yp-poky-edison-20160315.zip http://iotdk.intel.com/src/3.0/edison/iot-devkit-yp-poky-edison-20160315.zip.
I followed the steps indicated in the README file on the top level folder after unzip:
unzip iot-devkit-yp-poky-edison-20160315.zip
cd iot-devkit-yp-poky-edison-20160315/poky/
source oe-init-build-env ../build_edison/
bitbake edison-image u-boot
../poky/meta-intel-edison/utils/flash/postBuild.sh .
zip -r toFlash.zip toFlash
But I failed at step 4 (bold highlighted) with following errors:
ERROR: ExpansionError during parsing /home/labuser/Edison_BSP/iot-devkit-yp-poky-edison-20160315/build_edison/../poky/meta-intel-edison/meta-intel-edison-bsp/recipes-kernel/linux/linux-externalsrc.bb: Failure expanding variable do_patch: ExpansionError: Failure expanding variable do_patch, expression was cd /home/labuser/Edison_BSP/iot-devkit-yp-poky-edison-20160315/build_edison/../poky/linux-kernel
...
...
...
which triggered exception FetchError: Fetcher failure: Fetch command failed with exit code 128, output:
fatal: unable to access 'https://github.com/01org/edison-linux.git/%27: https://github.com/01org/edison-linux.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
My Linux version is Ubuntu 14.04. I compared the steps specified in BSP User Guide (http://www.intel.com/content/dam/support/us/en/documents/edison/sb/edisonbsp_ug_331188007.pdf http://www.intel.com/content/dam/support/us/en/documents/edison/sb/edisonbsp_ug_331188007.pdf) with the README file, they are almost the same.
@
Actually before to reach above step, I have encoutered several problems already after run "bitbake edison-image u-boot". Follwoing are the details:
1. "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."
I have resolved it by just comment following lines from "build_edison/conf/local.conf":
# PACKAGECONFIG_append_pn-qemu-native = " sdl"# PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl"
# ASSUME_PROVIDED += "libsdl-native"
2. "Failed to fetch test data from the network. Please ensure your network is configured correctly."
I have resolved it by re-define the variable CONNECTIVTY_CHECK_URIS to blank in "build_edison/conf/local.conf"
CONNECTIVITY_CHECK_URIS = ""
But for the problem which I said in the begining - Failure expanding variable do_patch, I have searched Edison Community as well as Internet, seems no useful clues yet.
Did anyone face the similar problem as me?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
There's already a thread on a very similar topic: and though your problems look different (as you're using a different build system version, 14.04 ve 16.x) I would suggest you to post there instead of multiplying threads on the same subject.
As for the error you have, it's better to post full bitbake log files (it should provide you with a path in the error message), as there might be additional details. For one, in the message you've posted it looks like it complains at a do_patch step, but at the very bottom of the message there's apparently a certificate validation error, which may be the actual reason.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
There's already a thread on a very similar topic: and though your problems look different (as you're using a different build system version, 14.04 ve 16.x) I would suggest you to post there instead of multiplying threads on the same subject.
As for the error you have, it's better to post full bitbake log files (it should provide you with a path in the error message), as there might be additional details. For one, in the message you've posted it looks like it complains at a do_patch step, but at the very bottom of the message there's apparently a certificate validation error, which may be the actual reason.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Hi Alex,
Thanks for your suggestion. I will post my situation to the topic also. Hope there would be more people look at this and aware the similar case if any.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Hi Alex,
Your doubt is quite helpful and finally it proves correct!
I found eventually the root cause is SSL certification failure when it tries to access "https://github.com/01org/edison-linux.git/%27: https://github.com/01org/edison-linux.git/".
The simplest way to resovle this problem I did is just
export GIT_SSL_NO_VERIFY=1# or
git config --global http.sslverify false
The building procedure continues. I know there will be new problems pop up but it's fun every time resolve one.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
My pleasure and glad to help.
I guess you might also want to update the CA certificates list for your host OS as generally speaking this shouldn't happen (unless you have a HTTP proxy which messes with HTTPS certificates).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page