Difference between revisions of "IoTGateway/BSP/Linux/Quark/Getting BSP from GitHub"

From ESS-WIKI
Jump to: navigation, search
Line 1: Line 1:
 +
 
{{DISPLAYTITLE:Some notices for getting the BSP from GitHub ADVANTECH-Corp}}
 
{{DISPLAYTITLE:Some notices for getting the BSP from GitHub ADVANTECH-Corp}}
  
Line 24: Line 25:
 
$ cd ${INTEL_BSP_VER}
 
$ cd ${INTEL_BSP_VER}
 
</syntaxhighlight></div>
 
</syntaxhighlight></div>
== Prebuilt image pack ==
+
== <s>Prebuilt image pack</s> ==
  
:There is no prebuilt image pack in the [[#Fetching_the_BSP|BSP fetched from GitHub]], so [[IoTGateway/BSP/Linux/Quark/Yocto_LBV2_User_Guide#To_build_all_image_files|creating all image files]] from the ground up.
+
:There is no prebuilt image pack in [[#Fetching_the_BSP|the BSP fetched from GitHub]], so [[IoTGateway/BSP/Linux/Quark/Yocto_LBV2_User_Guide#To_build_all_image_files|creating all image files]] from the ground up.
  
== setup.sh ==
+
== <s>setup.sh</s> ==
  
:There is no setup.sh in the [[#Fetching_the_BSP|BSP fetched from GitHub]], so there is no need to run setup.sh while [[IoTGateway/BSP/Linux/Quark/Yocto_LBV2_User_Guide#To_create_one_new_build_environment|creating one new build environment]].
+
:There is no setup.sh in [[#Fetching_the_BSP|the BSP fetched from GitHub]], so there is no need to run setup.sh while [[IoTGateway/BSP/Linux/Quark/Yocto_LBV2_User_Guide#To_create_one_new_build_environment|creating one new build environment]].

Revision as of 06:59, 21 November 2016



Getting Started

Conventions

${INTEL_BSP_VER} : the Intel Quark BSP version
e.g. v1.2.1.1
${BSP_HOME} : the home directory the BSP located to
e.g. ~/adv-quark-bsp/meta-clanton_${INTEL_BSP_VER}

Supported version

based on Intel Quark BSP v1.2.1.1

Fetching the BSP

$ mkdir ~/adv-quark-bsp
$ cd ~/adv-quark-bsp 
$ repo init -u https://github.com/ADVANTECH-Corp/adv-quark-bsp -m ${INTEL_BSP_VER}.xml
$ cd ${INTEL_BSP_VER}

Prebuilt image pack

There is no prebuilt image pack in the BSP fetched from GitHub, so creating all image files from the ground up.

setup.sh

There is no setup.sh in the BSP fetched from GitHub, so there is no need to run setup.sh while creating one new build environment.