bitbake edison-image ERROR Failed to connect to android.googlesource.com port 443: Connection refused

whan2 · ‎02-22-2017

when i bitbake edison-image,android.googlesource.com Failed to connect

i don not konw why and how to Solve

please hlep me

thanks!

@@

log:

wq3028@ubuntu:~/edison-bsp/edison-src/out/linux64$ source poky/oe-init-build-env

# Shell environment set up for builds. #

You can now run 'bitbake '

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'

wq3028@ubuntu:~/edison-bsp/edison-src/out/linux64/build$ bitbake edison-image

Loading cache: 100% |# | ETA: 00:00:00

Loaded 1365 entries from dependency cache.

NOTE: Resolving any missing task queue dependencies

Build Configuration:

BB_VERSION = "1.24.0"

BUILD_SYS = "x86_64-linux"

NATIVELSBSTRING = "Ubuntu-14.04"

TARGET_SYS = "i586-poky-linux"

MACHINE = "edison"

DISTRO = "poky-edison"

DISTRO_VERSION = "1.7.2"

TUNE_FEATURES = "m32 core2"

TARGET_FPU = ""

meta

meta-yocto

meta-yocto-bsp = "(detachedfromyocto-1.7.2):29812e61736a95f1de64b3e9ebbb9c646ebd28dd"

meta-intel-edison-bsp

meta-intel-edison-distro = ":"

meta-intel-iot-middleware = "(detachedfromc6d6814):c6d681475e76107e6c04c5f7a06034dc9e772d1e"

meta-intel-arduino = ":"

meta-arduino = "1.6.x:541b127163acb243109f07141bf249da2ecdcd9a"

NOTE: Preparing runqueue

NOTE: Executing SetScene Tasks

NOTE: Executing RunQueue Tasks

ERROR: Function failed: Fetcher failure: Fetch command failed with exit code 128, output:

fatal: unable to access ' https://android.googlesource.com/platform/external/wpa_supplicant_8/': Failed to connect to android.googlesource.com port 443: Connection refused

ERROR: Logfile of failure stored in: /home/wq3028/edison-bsp/edison-src/out/linux64/build/tmp/work/core2-32-poky-linux/wpa-supplicant/android-4.4.4_r2.0.1-r1/temp/log.do_fetch.10856

Log data follows:

| DEBUG: Executing python function do_fetch

| DEBUG: Executing python function base_do_fetch

| DEBUG: Fetcher accessed the network with the command git -c core.fsyncobjectfiles=0 ls-remote https://android.googlesource.com/platform/external/wpa_supplicant_8 refs/heads/android-4.4.4_r2.0.1 refs/tags/android-4.4.4_r2.0.1^{}

| DEBUG: Running export PATH="/home/wq3028/edison-bsp/edison-src/out/linux64/poky/scripts:/home/wq3028/edison-bsp/edison-src/out/linux64/build/tmp/sysroots/x86_64-linux/usr/bin/i586-poky-linux:/home/wq3028/edison-bsp/edison-src/out/linux64/build/tmp/sysroots/edison/usr/bin/crossscripts:/home/wq3028/edison-bsp/edison-src/out/linux64/build/tmp/sysroots/x86_64-linux/usr/sbin:/home/wq3028/edison-bsp/edison-src/out/linux64/build/tmp/sysroots/x86_64-linux/usr/bin:/home/wq3028/edison-bsp/edison-src/out/linux64/build/tmp/sysroots/x86_64-linux/sbin:/home/wq3028/edison-bsp/edison-src/out/linux64/build/tmp/sysroots/x86_64-linux/bin:/home/wq3028/edison-bsp/edison-src/out/linux64/poky/scripts:/home/wq3028/edison-bsp/edison-src/out/linux64/poky/bitbake/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games"; export HOME="/home/wq3028"; git -c core.fsyncobjectfiles=0 ls-remote https://android.googlesource.com/platform/external/wpa_supplicant_8 refs/heads/android-4.4.4_r2.0.1 refs/tags/android-4.4.4_r2.0.1^{}

| DEBUG: Python function base_do_fetch finished

| DEBUG: Python function do_fetch finished

| ERROR: Function failed: Fetcher failure: Fetch command failed with exit code 128, output:

| fatal: unable to access ' https://android.googlesource.com/platform/external/wpa_supplicant_8/': Failed to connect to android.googlesource.com port 443: Connection refused

|

ERROR: Task 372 (/home/wq3028/edison-bsp/edison-src/meta-intel-edison/meta-intel-edison-distro/recipes-connectivity/wpa_supplicant/wpa-supplicant_android-4.4.4_r2.0.1.bb, do_fetch) failed with exit code '1'

NOTE: Tasks Summary: Attempted 1648 tasks of which 1643 didn't need to be rerun and 1 failed.

Waiting for 0 running tasks to finish:

Summary: 1 task failed:

/home/wq3028/edison-bsp/edison-src/meta-intel-edison/meta-intel-edison-distro/recipes-connectivity/wpa_supplicant/wpa-supplicant_android-4.4.4_r2.0.1.bb, do_fetch

Summary: There was 1 ERROR message shown, returning a non-zero exit code.

idata · ‎02-22-2017

Hi Wq3028,

Thanks for your interest in the Intel® Edison Platform.

Could you please provide us the steps or guide you are following? We are requesting it in order to try to help you with your issue. Also, we would like to know if you are trying to customize the image.

We'll be waiting for your reply.

Regards,

-Yermi A.

whan2 · ‎02-22-2017

Thank you for your help

BSP edison-src-ww25.5-15

ubuntu 1404

I am in accordance with the inter online edison-bsp Guide compiled.

Steps are as follows：

1. Install the prerequisite packages with the following command:

sudo apt-get install build-essential git diffstat gawk chrpath texinfo

libtool gcc-multilib

2. Download the BSP source package edison-src.tgz from the Intel® Edison Software Downloads page. The

package includes the full Yocto environment, and Intel® Edison-specific Yocto recipes to build the image

(including the Linux kernel), a bootloader, and all necessary packages. Download the BSP source package

to your working directory and decompress it.

tar xvf edison-src.tgz

cd edison-src/

3. Use the setup.sh script to initialize the build environment for Intel® Edison.

To create download and sstate directory, you can use mkdir command:

mkdir bitbake_download_dir

mkdir bitbake_sstate_dir

./meta-intel-edison/setup.sh --dl_dir=<=/</span>_to>/bitbake_download_dir

–-sstate_dir=<=/</span>/bitbake_sstate_dir

Optionally, you can move your download and build cache (also called sstate) directories from the default

location under the build directory, using the --dl_dir and --sstate_dir options. Doing this will make it easier

to share this data between build environments, and allow much faster build and download time when

rebuilding the full image, even after a full manual cleanup (by means of deleting everything under your

build directory). To create the sstate directory, use the mkdir command:

mkdir bitbake_download_dir

mkdir bitbake_sstate_dir

4. Configure the shell environment with the source command below. After the command executes, the

directory changes to the edison-src/build folder.

source poky/oe-init-build-env

5. Now you are ready to build the full Intel® Edison image with the bitbake command:

bitbake edison-image

idata · ‎02-23-2017

Hi Wq3028,

Thanks for all the information provided. We have found information regarding the "Connection Refused" message and it has two main causes: Nothing is listening on the IP: Port you are trying to connect or the port is blocked as it is mention in this link: http://serverfault.com/questions/725262/what-causes-the-connection-refused-message What causes the 'Connection Refused' message?, please take a look at that link and try the suggestions and let us know if it helps, we believe there you will find useful information.

Regards,

-Yermi A

idata · ‎02-27-2017

Hi Wq3028,

We would like to know if you have any updates, and if you checked the link of "What causes the Connection Refused message".

Regards,

-Yermi A.