4 Replies Latest reply on Jun 10, 2015 11:03 AM by CMata_Intel

    Getting Error while building Yocto OS for Intel Galileo Gen 2 using BSP provided by Intel.

    Swamy_Govinda

      Hi,

      I am trying to build yocto os for Intel Galileo Gen 2 uing the BSP provided by Intel,

      I downloaded all the necessary files(Board_Support_Package_Sources_for_Intel_Quark_v1.1.0.7z)

      from the website https://downloadcenter.intel.com/download/23197.

      I executed

      # tar -xvf meta-clanton*.tar.gz

      # cd meta-clanton*

      # ./setup.sh

       

      But after executing "./setup.sh" command

      I am getting the following error.

       

      iot@iot-desktop:/tmp/meta-clanton_v1.1.0-dirty$ ./setup.sh

      Fetching in Quark SW ingredients Now

      [20:28:54] cloning git://git.yoctoproject.org/meta-intel-iot-devkit to repo-ext/meta-intel-iot-devkit

      Cloning into 'repo-ext/meta-intel-iot-devkit'...

      fatal: unable to connect to git.yoctoproject.org:

      git.yoctoproject.org[0: 140.211.169.56]: errno=Connection timed out

       

      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 devkit-daisy-1.6.1 git://git.yoctoproject.org/meta-intel-iot-devkit repo-ext/meta-intel-iot-devkit' returned non-zero exit status 128

      iot@iot-desktop:/tmp/meta-clanton_v1.1.0-dirty$

       

       

       

      As I am behind a corporate network,

      I followed all the instructions in this website https://wiki.yoctoproject.org/wiki/Working_Behind_a_Network_Proxy

      and changed the proxy details accordingly.

       

      Still I am getting the same error..

      Is there anything extra to modify?