element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet & Tria Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • About Us
    About the element14 Community
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Japan
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      •  Vietnam
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
WaRP7
  • Products
  • Dev Tools
  • Single-Board Computers
  • WaRP7
  • More
  • Cancel
WaRP7
Blog Warp7 Yocto : Part1 : setup, configure and generate Warp7 binaries
  • Blog
  • Forum
  • Documents
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join WaRP7 to participate - click to join for free!
  • Share
  • More
  • Cancel
Group Actions
  • Group RSS
  • More
  • Cancel
Engagement
  • Author Author: tusharp
  • Date Created: 16 Sep 2016 7:30 AM Date Created
  • Views 9974 views
  • Likes 4 likes
  • Comments 89 comments
  • tusharp
  • imx7
  • yocto
  • image
  • bitbake
  • warp7
  • embedded
  • yocto-bsp
  • linux
Related
Recommended

Warp7 Yocto : Part1 : setup, configure and generate Warp7 binaries

tusharp
tusharp
16 Sep 2016

Contents

1. Warp7 Yocto Part1 <-- You are here

2. Warp7 Yocto Part2

3. Warp7 Sensors demo - mpl3115a2

4. Warp7 Sensors demo - fxos8700cq

5. Warp7 IoT demo

 

The Warp7 is a next generation Wearable and IoT development platform.

plz refer  NXP and element14 website for more platform related information.

 

Warp7 Board

fd53fb.jpg

CPU Board

34nmm39.jpg

IO Board

2dkfsao.jpg

 

In this blog we will

1. Download warp7 yocto sources.

2. Setup required environment.

3. add/customise warp7 machine configs.

4. Compile and generate binaries.

 

 

A bit on yocto before we start :

oq9937.jpg

 

If you are new to yocto , plz make sure to check the yocto project before proceeding.

 

Platform Setup:

I am using Ubuntu 14.04 x86_64 for the build process. you can use do this from a Virtual Machine (vmware, virtualbox) also.

 

We need to install some packages on which yocto depends for the build process.

sudo apt-get install gawk wget git-core diffstat unzip texinfo gcc-multilib build-essential chrpath socat libsdl1.2-dev \
xterm sed cvs subversion coreutils texi2html python-pysqlite2 help2man make gcc g++ desktop-file-utils libgl1-mesa-dev \
libglu1-mesa-dev mercurial autoconf automake groff curl lzop u-boot-tools

 

vr90kz.jpg

 

Download repo:

We need to have a repo tool to pull yocto sources.

 

mkdir ~/bin
curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo
export PATH=~/bin:$PATH

 

Download Yocto:

following steps will help download yocto sources from NXP(Freescale) official repository:

 

mkdir warp7_yocto
cd warp7_yocto
repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b krogoth
repo sync

 

Before building the yocto bsp we need to update the yocto build with warp7 config.

To configure we need to pass the proper MACHINE name as a macro.

 

Determine machine name:

echo; ls sources/*/conf/machine/*.conf | sed s/\.conf//g | sed -r 's/^.+\///' | xargs -I% echo -e "\t%" | grep imx

 

1444o6p.jpg

 

The Warp7 machine name is imx7s-warp .

 

 

Setting up the environment:

 

MACHINE=imx7s-warp source setup-environment build

 

2useno7.jpg

 

Select "Y" to accept the EULA license and complete the machine config setup.

 

9bi39u.jpg

 

Now a build directory is created under ~/warp7_yocto directory.

It contains the build system settings for warp7 machine(i.e local.conf) and yocto bitbake layers path information (i.e bblayers.conf).

 

local.conf

1z4a4vn.jpg

 

bblayers.conf

141tfeq.jpg

 

 

Customise warp7 machine config:

Now edit the kernel source in warp7 machine configuration file.

 

in ~/warp7_yocto/sources/meta-fsl-arm-extra/conf/machine/imx7s-warp.conf file, edit as below.

Replace

PREFERRED_PROVIDER_virtual/kernel ?= "linux-fslc-imx"

with

PREFERRED_PROVIDER_virtual/kernel ?= "linux-warp"

 

Now the kernel source will be pulled from the linux-warp%%  bitbake recipe.

Create a directory named "linux-warp7-4.1" and recipe named "linux-warp7_4.1.bb" in below path.

~/warp7_yocto/sources/meta-fsl-arm-extra/recipes-kernel/linux/

 

mkdir ~/warp7_yocto/sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-warp7-4.1
touch ~/warp7_yocto/sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-warp7_4.1.bb

 

 

Populating warp7 recipe:

populate the recipe "linux-warp7_4.1.bb" with below contents.

# Released under the MIT license (see COPYING.MIT for the terms)

 

include recipes-kernel/linux/linux-imx.inc

include recipes-kernel/linux/linux-dtb.inc

 

DEPENDS += "lzop-native bc-native"

 

SRCBRANCH = "4.1-1.0.x-imx"

SRCREV = "fa571312b4271e368ca99ffcdf7992247d534e55"

 

SRC_URI = "git://github.com/WaRP7/linux-fslc.git;branch=${SRCBRANCH} \

           file://defconfig"

 

COMPATIBLE_MACHINE = "(imx7s-warp)"

 

In above recipe we setup 4.1-1.0.x-imx as source branch for our kernel and file defconfig will be the default kernel config file.

Next copy the defconfig file (in attachment) into the linux-warp7-4.1 directory.

 

 

Downloading yocto packages:

If you want to build images offline, its a good idea to download the packages first.

bitbake core-image-minimal -c fetchall

 

 

Build:

bitbake core-image-minimal

 

Now build, it will take several hours to complete depending on your PC configuration.

 

While kernel build is in process you might encounter an error wrt imx7s-warp.dtb.

This will happen is there is no imx7s-warp.dts file in below directory.

~/warp7_yocto/build/tmp/work/imx7s_warp-poky-linux-gnueabi/linux-warp7/4.1-r0/git/arch/arm/boot/dts

 

below is a snapshot from the log file that captured the above  error.

90avr7.jpg

 

In that case copy the imx7s-warp.dts from the attachments to the below directory:

~/warp7_yocto/build/tmp/work/imx7s_warp-poky-linux-gnueabi/linux-warp7/4.1-r0/git/arch/arm/boot/dts

 

2s7dqv4.jpg

 

Now hit build again.

 

After build completed, the images build are found in ~/warp7_yocto/build/tmp/deploy/images/imx7s-warp

noajk7.jpg

 

 

Let us know any challenges faced during build procedure through comments.

 

Next time we will flash the generated images.

 

Happy Warping.

Attachments:
warp7_attachments.zip
  • Sign in to reply

Top Comments

  • bwelsby
    bwelsby over 9 years ago in reply to Jan Cumps +1
    Jan Cumps wrote: bitbake -fetch finished successful (14 hours on the raspberry pi to complete all 189 jobs. it used 4 job threads to allocate tasks on this board), now up to the next step: build That's…
  • bheemarao
    bheemarao over 9 years ago +1
    I tried building the same as shown steps below bheema@Bheema:~/warp7_yocto$ MACHINE=imx7s-warp source setup-environment build-warp7 then by default the kernel will fetch from "include recipes-kernel/linux…
  • Jan Cumps
    Jan Cumps over 9 years ago in reply to Jan Cumps +1
    Installing the dependencies. Once I'm at the bitbake line, I'll switch to bheemarao 's steps...
  • bwelsby
    bwelsby over 9 years ago in reply to Jan Cumps

    Hmmm at the point where you had the error I had:

     

    NOTE: Fetching uninative binary shim from http://downloads.yoctoproject.org/releases/uninative/1.0.1/i686-nativesdk-libc.tar.bz2;sha256sum=de51bc9162b07694d3462352ab25f636a6b50235438c1b09440d7569e009123b

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • Jan Cumps
    Jan Cumps over 9 years ago in reply to Jan Cumps

    To resolve ERROR: Uninative selected but not configured correctly, please set UNINATIVE_CHECKSUM[armv7l]:

    I'm following advice on this issue report: https://github.com/openbmc/openbmc/issues/500

    and added at the end of ~/warp7_yocto/build/conf/local.conf :

    INHERIT_remove = "uninative"

     

    There's another issue that suggests a different approach that I haven't tried:

    https://github.com/openbmc/openbmc/issues/640#issuecomment-270523012

     

    These issues are raised for non-warp7 builds

     

    This time the Pi died during the bitcake, Restarting it...

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • Jan Cumps
    Jan Cumps over 9 years ago in reply to Jan Cumps

    I undid the change in imx7s-warp.conf.

    It goes a significant step further now, then ends with bitcace throwing a different error Uninative selected but not configured correctly, please set UNINATIVE_CHECKSUM[armv7l]

     

    image

     

     

    bitbake core-image-minimal -c fetchall

     

    ERROR: Uninative selected but not configured correctly, please set UNINATIVE_CHECKSUM[armv7l]
    
    
    Summary: There was 1 WARNING message shown.
    Summary: There was 1 ERROR message shown, returning a non-zero exit code.

     

    I'll google-fu for a solution...

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • bwelsby
    bwelsby over 9 years ago in reply to Jan Cumps

    Jan Cumps wrote:

     

    Yes, that was there in my file too. I did follow the instructions and replaced it though. I backed up the original, so I can give it a try...

    now running bitbake core-image-minimal,

    currently building all the packages on task 305 of 2066  with no errors so far image

     

    Brian

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • Jan Cumps
    Jan Cumps over 9 years ago in reply to bwelsby

    Yes, that was there in my file too. I did follow the instructions and replaced it though. I backed up the original, so I can give it a try...

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
<>
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2026 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube