Difference between revisions of "IoTGateway/BSP/Linux/Quark/Getting BSP from GitHub"
From ESS-WIKI
| Line 21: | Line 21: | ||
= Fetching the BSP = | = Fetching the BSP = | ||
| − | :Please refer to [[IoTGateway/BSP/Linux/iMX6/Yocto_LBV7_User_Guide# | + | :Please refer to [[IoTGateway/BSP/Linux/iMX6/Yocto_LBV7_User_Guide#Setting_up_the_repo_utility|this]] to setup repo first |
<div style="margin-left: 2em"><syntaxhighlight lang="bash"> | <div style="margin-left: 2em"><syntaxhighlight lang="bash"> | ||
$ mkdir ~/adv-quark-bsp | $ mkdir ~/adv-quark-bsp | ||
Revision as of 19:34, 26 November 2016
Contents
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
Fetching the BSP
- Please refer to this to setup repo first
$ mkdir ~/adv-quark-bsp
$ cd ~/adv-quark-bsp
$ repo init -u https://github.com/ADVANTECH-Corp/adv-quark-bsp -m ${INTEL_BSP_VER}.xml
$ repo sync
$ cd meta-clanton_${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.