Bug 10218

Apollo Lake BSP was developed using Poky Jethro. You may skip the installation of latest Yocto Project build system release on your build machine. The setup.sh script provided in bsp-apollolake-i will fetch the poky source from correct revision when it is run.

Please follow the wiki guide to setup SSH connection to GitHub before you start the build.
https://github.com/01org/bsp-apollolake-i/wiki/Setting-Up-Guide

You also need to get access to linux-apollolake-i repo in order to build the BSP.

Going through the “Setting Up Guide”, the steps required the use of proxy connection to access remote GIT repositories without the use of username/password. However, in an environment where the information to proxy IP address and port is confidential and restricted, an alternative method may need to be provided to the users.

Follow the steps in “Setting Up Guide”, and generated the SSH keys using instructions in:

https://help.github.com/articles/generating-an-ssh-key/

Login to the website "https://github.com" using my corporate email and my account password, and added the SSH keys to my GitHub account using instructions in:

https://help.github.com/articles/adding-a-new-ssh-key-to-your-github-account/

Testing my SSH connection using instructions in:

https://help.github.com/articles/testing-your-ssh-connection/

$ ssh -T git@github.com
/bin/bash: proxy: No such file or directory
ssh_exchange_identification: Connection closed by remote host
$

SSH connection to GitHub.com failed and therefore proceed to edit the local SSH config file and comment out the proxycommand line,

$ vi ~/.ssh/config
#proxycommand /bin/nc -X connect -x <proxy server IP or DNS>:<http port number> %h %p

tcpkeepalive yes

compression yes

connectionattempts 3
$ 

Run the SSH connection test again, and the connection was successful,

$ ssh -T git@github.com
Hi <myusername>! You've successfully authenticated, but GitHub does not provide shell access.
$

Continue with the “Setting Up Guide”, clone the bsp-apollolake-I repo using the terminal command:

$ git clone git@github.com:01org/bsp-apollolake-i.git

Changed to the cloned folder and run “setup.sh” to start a build,

$ cd bsp-apollolake-i
$ ./setup.sh
Select an option:
1. Build kernel image with CAVS HD Audio driver (Default)
2. Build kernel image with CAVS SSP Audio driver
3. Build kernel image with legacy HD Audio driver
Default option is build kernel image with CAVS HD Audio driver. If no input is received within 20 secs, default will be used.
1

Select an option:
1. core-image-sato-sdk (Default)
2. core-image-sato
3. linux-kernel
4. custom
Default build target is core-image-sato-sdk. If no input is received within 20 secs, default target will be built.
2

--2016-09-09 12:01:34--  http://git.yoctoproject.org/cgit/cgit.cgi/meta-jarvis/tree/meta-jarvis/jarvis.bb
Resolving git.yoctoproject.org (git.yoctoproject.org)... 140.211.169.56
Connecting to git.yoctoproject.org (git.yoctoproject.org)|140.211.169.56|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ‘jarvis.bb’

    [ <=>                                                      ] 3,410       --.-K/s   in 0s

2016-09-09 12:01:35 (255 MB/s) - ‘jarvis.bb’ saved [3410]

SUCCESS: wget test is healthy.
Creating new build directory ...
Proceed to update ingredients ...
rm: cannot remove ‘unsetup.sh’: No such file or directory
Building BSP with core-image-sato image ...
Fetching in Apollo Lake BSP ingredient now
[12:01:47] cloning https://github.com/meta-qt5/meta-qt5 to repo-ext/meta-qt5
Cloning into 'repo-ext/meta-qt5'...
remote: Counting objects: 6881, done.
remote: Compressing objects: 100% (7/7), done.
remote: Total 6881 (delta 0), reused 0 (delta 0), pack-reused 6874
Receiving objects: 100% (6881/6881), 1.88 MiB | 566.00 KiB/s, done.
Resolving deltas: 100% (4251/4251), done.
Checking connectivity... done.
[12:01:54] cloning https://github.com/flihp/meta-measured.git to repo-ext/meta-measured
Cloning into 'repo-ext/meta-measured'...
remote: Counting objects: 1432, done.
remote: Total 1432 (delta 0), reused 0 (delta 0), pack-reused 1432
Receiving objects: 100% (1432/1432), 881.10 KiB | 534.00 KiB/s, done.
Resolving deltas: 100% (701/701), done.
Checking connectivity... done.
[12:01:58] cloning git://git.openembedded.org/meta-openembedded to repo-ext/meta-openembedded
Cloning into 'repo-ext/meta-openembedded'...
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
Traceback (most recent call last):
  File "setup/combo-layer", line 597, in <module>
    ret = main()
  File "setup/combo-layer", line 593, in main
    actions.get(args[1], action_error)(confdata, args[1:])
  File "setup/combo-layer", line 178, in action_init
    subprocess.check_call("git clone -b %s %s %s" % (branch, conf.repos[name]['src_uri'], ldir), shell=True)
  File "/usr/lib/python2.7/subprocess.py", line 540, in check_call
    raise CalledProcessError(retcode, cmd)
CalledProcessError: Command 'git clone -b jethro git://git.openembedded.org/meta-openembedded repo-ext/meta-openembedded' returned non-zero exit status 128
Initial Repo Population: Apollo Lake BSP for linux-yocto ver-4.1

Combo-layer configuration:
[poky]
src_uri = git://git.yoctoproject.org/poky
local_repo_dir = repo-ext/poky
dest_dir = .
branch = jethro
last_revision = 40376446904ae3529be41737fed9a0b650ed167d
file_filter = bitbake documentation LICENSE meta meta-yocto meta-yocto-bsp oe-init-build-env scripts

[meta-openembedded]
src_uri = git://git.openembedded.org/meta-openembedded
local_repo_dir = repo-ext/meta-openembedded
dest_dir = meta-openembedded
branch = jethro
last_revision = cb7e68f2a39fa6f24add48fc7b8d38fb7291bb44
file_filter = meta-oe meta-gnome meta-python meta-xfce meta-filesystems meta-multimedia meta-networking

[meta-qt5]
src_uri = https://github.com/meta-qt5/meta-qt5
local_repo_dir = repo-ext/meta-qt5
dest_dir = meta-qt5
branch = jethro
last_revision = ea37a0bc987aa9484937ad68f762b4657c198617

[meta-measured]
src_uri = https://github.com/flihp/meta-measured.git
local_repo_dir = repo-ext/meta-measured
dest_dir = meta-measured
branch = master
last_revision = 66aca6bc94e35f3c5896455d2feed2a35f428d28

[meta-intel-iot-middleware]
src_uri = git://git.yoctoproject.org/meta-intel-iot-middleware
local_repo_dir = repo-ext/meta-intel-iot-middleware
dest_dir = meta-intel-iot-middleware
branch = master
last_revision = 821cf14c8304669d9ce0c5b87b9be5a6eecff6e5
file_filter = COPYING.MIT MAINTAINERS README conf recipes-devtools/mraa recipes-devtools/swig recipes-devtools/upm
fatal: Not a git repository (or any parent up to mount point /yocto-projects)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
Patching BSP meta layer ...
fatal: Not a git repository (or any parent up to mount point /yocto-projects)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
fatal: Not a git repository (or any parent up to mount point /yocto-projects)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
=========================================================================
By default, this setup script will create a brand new repo which combines
meta-intel BSP layer and Yocto Project poky distro.
If you don't need git tracking, please 'rm -rf .git' now
=========================================================================
./build.sh: line 70: oe-init-build-env: No such file or directory

local.conf: machine: CAVS HD-Audio -- intel-corei7-64-cavs-hda

./build.sh: line 93: bitbake: command not found
Entering build status checker ...
./setup.sh: line 279: cd: ../yocto_build/build/tmp/deploy/images/intel-corei7-64-cavs-hda/: No such file or directory
BSP Build: FAILED!!!
HDDIMG was not generated!
Please check the build log for detailed failure.
$

The build process showed following issues:
1. See error message “rm: cannot remove ‘unsetup.sh’: No such file or directory”

2. The cloning of repo “git://git.openembedded.org/meta-openembeded” failed as the host machine could not read from this remote directory. As a result, the other remaining repos, “poky” and “meta-intel-iot-middleware” are not checked out.

3. See error message:
fatal: Not a git repository (or any parent up to mount point /yocto-projects)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).

To resolve issue 2, edited the file “bsp-apollolake-i/setup/combolayer.conf” as below:
 [poky]
-  src_uri = git://git.yoctoproject.org/poky
+  src_uri = http://git.yoctoproject.org/cgit/cgit.cgi/poky

[meta-openembedded]
-  src_uri = git://git.openembedded.org/meta-openembedded
+  src_uri = http://git.openembedded.org/meta-openembedded

[meta-intel-iot-middleware]
-  src_uri = git://git.yoctoproject.org/meta-intel-iot-middleware
+  src_uri = http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel-iot-middleware

Restart the build again,

$ cd bsp-apollolake-i/
$ ./setup.sh
create mode 100644 setup/bsp-conf/local.conf.sample
 create mode 100755 setup/combo-layer
 create mode 100644 setup/combolayer.conf
Patching BSP meta layer ...
/usr/lib/git-core/git-am: 209: /usr/lib/git-core/git-am: cannot open /yocto-projects/apl-gold-test/yocto_build/setup/patchset/bsp-meta/*.patch: No such file
/usr/lib/git-core/git-am: 209: /usr/lib/git-core/git-am: cannot open /yocto-projects/apl-gold-test/yocto_build/setup/patchset/oe-meta/*.patch: No such file
=========================================================================
By default, this setup script will create a brand new repo which combines
meta-intel BSP layer and Yocto Project poky distro.
If you don't need git tracking, please 'rm -rf .git' now
=========================================================================
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.

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>'

Supported target:
        core-image-sato
        core-image-sato-dev
        core-image-sato-sdk

Note: The output is at build/tmp/deploy/images/intel-corei7-64/

local.conf: machine: CAVS HD-Audio -- intel-corei7-64-cavs-hda

ERROR: ExpansionError during parsing /yocto-projects/apl-gold-test/yocto_build/meta-measured/recipes-tpm/tpm2.0-tss/tpm2.0-tss_git.bb: Failure expanding variable SRCPV, expression was ${@bb.fetch2.get_srcrev(d)} which triggered exception FetchError: Fetcher failure: Fetch command failed with exit code 128, output:
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.


Summary: There was 1 ERROR message shown, returning a non-zero exit code.
Entering build status checker ...
./setup.sh: line 279: cd: ../yocto_build/build/tmp/deploy/images/intel-corei7-64-cavs-hda/: No such file or directory
BSP Build: FAILED!!!
HDDIMG was not generated!
Please check the build log for detailed failure.
$

The build failed with error message:
--------------------------------------------------------------------------------
ERROR: ExpansionError during parsing /yocto-projects/apl-gold-test/yocto_build/meta-measured/recipes-tpm/tpm2.0-tss/tpm2.0-tss_git.bb: Failure expanding variable SRCPV, expression was ${@bb.fetch2.get_srcrev(d)} which triggered exception FetchError: Fetcher failure: Fetch command failed with exit code 128, output:
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
--------------------------------------------------------------------------------

This issue is found on a private repo. IoTG customer support has been notified and take over.

Verified that the SSH key I am using is attached to my GitHub User account,

$ ssh -T git@github.com
Hi <my_github_username>! You've successfully authenticated, but GitHub does not provide shell access.
$

Execute task do_fetch() from recipe “meta-intel-leafhill/common/recipes-kernel/linux/linux-yocto_4.1.bb”, noticed error message “Could not read from remote repository”,

$ bitbake -b /yocto-projects/yocto-apl/poky-jethro/meta-intel-leafhill/common/recipes-kernel/linux/linux-yocto_4.1.bb –c fetch

--------------------------------------------------------------------------------
WARNING: Failed to fetch URL git://github.com/01org/linux-apollolake-i.git;protocol=ssh;branch=gold;name=machine, attempting MIRRORS if available
ERROR: Fetcher failure: Fetch command failed with exit code 128, output:
Cloning into bare repository '/yocto-projects/yocto-apl/yocto_build/downloads/git2/github.com.01org.linux-apollolake-i.git'...
Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

ERROR: Function failed: Fetcher failure for URL: 'git://github.com/01org/linux-apollolake-i.git;protocol=ssh;branch=gold;name=machine'. Unable to fetch URL from any source.
ERROR: Logfile of failure stored in: /yocto-projects/yocto-apl/yocto_build/tmp/work/kontron_apl-poky-linux/linux-yocto/4.1.27+apollolake-gitAUTOINC+41fc98f785-r0.15/temp/log.do_fetch.29600
ERROR: Task 0 (/yocto-projects/yocto-apl/poky-jethro/meta-intel-leafhill/common/recipes-kernel/linux/linux-yocto_4.1.bb, do_fetch) failed with exit code '1'
NOTE: Tasks Summary: Attempted 1 tasks of which 0 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
  /yocto-projects/yocto-apl/poky-jethro/meta-intel-leafhill/common/recipes-kernel/linux/linux-yocto_4.1.bb, do_fetch
Summary: There were 2 WARNING messages shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
--------------------------------------------------------------------------------

Look at the SRC_URI in the recipe file,

SRC_URI = "git://github.com/01org/linux-apollolake-i.git;protocol=ssh;branch=gold;name=machine"

Tried to clone this repository manually, and it failed with error message “Repository not found”

$ git clone git://github.com/01org/linux-apollolake-i.git;protocol=ssh;branch=gold;name=machine
Cloning into 'linux-apollolake-i'...
fatal: remote error:
  Repository not found.
$

Then, tried to clone manually using “https” protocol and the repository is cloned successfully,

$ git clone https://github.com/01org/linux-apollolake-i.git;protocol=ssh;branch=gold;name=machine
Cloning into 'linux-apollolake-i'...
Username for 'https://github.com': <my_github_username>
Password for 'https://<my_github_username>@github.com':
remote: Counting objects: 4252532, done.
remote: Compressing objects: 100% (3/3), done.
Receiving objects:   0% (27626/4252532), 12.22 MiB | 1.03 MiB/s
$

However, if we modified the SRC_URI in the recipe file to fetch file from internet,

#SRC_URI = "git://github.com/01org/linux-apollolake-i.git;protocol=ssh;branch=gold;name=machine"
SRC_URI = https://github.com/01org/linux-apollolake-i.git;protocol=ssh;branch=gold;name=machine

Run the do_fetch() task from the recipe “meta-intel-leafhill/common/recipes-kernel/linux/linux-yocto_4.1.bb” again, we noticed the similar "ExpansionError" error message as we previously reported,

$ bitbake linux-yocto_4.1.bb -c fetch
Loading cache: 100% |############################################################################################################################| ETA:  00:00:00
Loaded 2279 entries from dependency cache.
NOTE: Error during finalise of /yocto-projects/yocto-apl/poky-jethro/meta-intel-leafhill/common/recipes-kernel/linux/linux-yocto_4.1.bb          | ETA:  --:--:--
ERROR: ExpansionError during parsing /yocto-projects/yocto-apl/poky-jethro/meta-intel-leafhill/common/recipes-kernel/linux/linux-yocto_4.1.bb: Failure expanding variable bbfatal_log: ExpansionError: Failure expanding variable SRCPV, expression was ${@bb.fetch2.get_srcrev(d)} which triggered exception FetchError: Fetcher failure: SRCREV was used yet no valid SCM was found in SRC_URI

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