Revision History
Contents
1. KBCBASE meta kbc ppc sources n Ka delete sources after build to save disk space NHERIT rm work set meta oe layer with lowest priority BBFILE PRIORITY openembedded layer 1 LES rn COREBASE meta COREBASE meta yocto COREBASE meta fsl ppc COREBASE meta fsl ppc private COREBASE meta oe meta oe KBCBASE meta kbc ppc inc files include WORKDIR temp directory and bb and inc files only include WORKDIR temp SOURCE ARCHIVE LOG WITH SCRIPTS SOURCE_ARCHIVE LOG WITH SCRIPTS logs with _scripts a an an Page 12 of 122. process may require the user s attention The default is to use xterm Examples of the occasions this may happen are when resolving patches which cannot be applied to use the devshell or the kernel menuconfig If you do not use or have installed xterm you will need to uncomment these variables and set them to the terminal you wish to use Supported shell prefixes for TERMCMD and TERMCMDRUN are GNOME SCREEN XTERM and KONSOLE Note currently Konsole support only works for KDE 3 x due to the way newer Konsole versions behave TERMCMD S XTERM TERMCMD TERMCMDRUN S XTERM _TERMCMDRUN By default disable interactive patch resolution tasks will just fail instead PATCHRESOLVE noop Shared state files from other locations As mentioned above shared state files are prebuilt cache data objects which can used to accelerate build time This variable can be used to configure the system This can be a filesystem directory or a remote url such as http or ftp These would contain the sstate cache results from previous builds possibly from other machines This variable works like fetcher MIRRORS PREMIRRORS and points to the cache locations to check for the shared objects SSTATE MIRRORS file http someserver tld share sstate n file file some local dir sstate n file file COREBASE sstate cache use xz instead of gzip for sstate cache SSTATE PKG SUFFIX txz SSTATE PKG T
3. to the configuration If changes were made to the configuration only shared state files where the state was still valid would be used done using checksums The default is a sstate cache directory under TOPDIR state cache output re the bulk of the building work should be done and KR where BitBake should place its temporary files and output Keep in mind that this includes the extraction and complation of many applications and the toolchain which can use Gigabytes of hard disk space ctory under TOPDIR controls which policy settings are used as defaults for general Yocto project use at least initially custom policy people will likely end up subclassing s there is a bleeding egde policy configuration et to the absolute latest code from the upstream source control systems This is just mentioned here an an example its not Package Management configuration packaging formats to enable Multiple package backends d the first item listed in the variable will be used systems an style deb files This directory files are used by opkg a debian style embedded package manager style packages package rpm package deb package_ipk Page 9 of 12 Kontron We default to rpm dbg pkgs dev pkgs tools sdk tools debug tools profile tools testapps debug tweaks image mklibs image prelink image swab if listing mklibs amp prelink both then make sure mklibs is before preli
4. ARZIPPROG xz Archiving source code configuration can be enabled by uncommenting one of the following lines NHERIT archive patched source NHERIT archive configured source NHERIT archive original source nm d ype of archive SOURCE ARCHIVE PACKAGE TYPE srpm SOURCE ARCHIVE PACKAGE TYPE tar Kontron to search other mirror locations for these objects before it builds the data itself The following variables control which files to archive and the type to archive to generate There are three basic class defintions of common operations that might be desired and these Page 11 of 12 cvs svn git ftp Appendix B bblayers conf sample LAYER CONF VERSION is increased each time build conf bblayers conf changes incompatibly LCONF_ VERSION 4 BBE BB Kontron Logs Whether to include WORKDIR temp logs_with_scripts CONF_VERSION is increased each time build conf changes incompatibly and is used to track the version of this file when it was generated This can safely be ignored if this doesn t mean anything to you CONF VERSION 1 use sources supplied by Freescale SDK PREMIRRORS_prepend file COREBASE sources n file COREBASE sources n file COREBASE sources n file COREBASE sources n http file COREBASE sources An https file COREBASE sources n file file
5. Application Note G kontron COMe cP2020 S1000 D0481 Com Express Module supporting Version 3 P1020 P1011 P2010 and P2020 2014 09 19 RalfKihm Buildin the Yocto Layer meta kbc Revision History Date ____ Revision Author TL Chapters affected Remarks 2012 12 21 Ralf Kihm Initial Draft 2013 02 27 Ralf Kihm Release for LIN_BSP R20 2014 09 19 RalfKihm Kontron Page 1 of 12 Table of Content Revision History anh eka ahi es A 1 at geet E 3 Gelee ee EOE EER ArT RE HE da Kada koana Creer 3 EI 4 PTS TCU KEE Scare ccc eae ta EE 4 Installing Freescale SDK 1 3 ccsssssssssssssessssscsecsecsessessssessecesscsesssssesuesseseeseescesscsesseseaeeseeseasenesueeseseeaeeseeneeseeeeneaeeass 4 Joek leao E 4 Installing Kontron BSP Layer meta KD Pp eens 4 Build Directory and Sample Configuration les EEN 4 Adapt the Configuration Files sicccsisisissicstecccsssleissicedececossdadsccusdecesscelavesesblabesscedednssusiedaccsededesedhsuduetsnduedeaanlustuniaiaateiles 5 Shared State SSTATE Mirror Confteuration ENEE 5 Setup the Build Environ eN tersane EENEN ESENE nneaninnnninaiincarianiiaceed 5 Building the BSP tees esess ees set cncscaeusce canst see ex tude stat vec ia i ia cuveasu tae a E ctateenduateeatae 6 EA To 6 Build WEE 6 Building the Freescale Toolchain Eer 7 IER Te 7 eege 7 Appendix A local confisampple ccscsscsssssssscsessesssssssssssssessesesssssssssssesesssseesseseesesesesesseesesueseeneeeeesseseesseaeeneesesea
6. R gt g BASEDIR build_d0481_ release conf bblayers conf Shared State SSTATE Mirror Configuration Optionally you may want to benefit from the Freescale provided prebuilt binaries In that case append sstate mirror configuration to the end ofyour local conf file echo SSTATE MIRRORS file file SDKBASE sstate cache n gt gt BASEDIR build_d0481 release conf local conf Setup the Build Environment The following command line setups the build environment and changestothe BASEDIR build_d0481_release source SDKBASE oe init build env BASEDIR build_d0481 release Kontron Page 5 of 12 Building the BSP Building bitbake kbc image Build Results The build results are available from the directory BASEDIR build_d0481_release deploy Kontron Page 6 of 12 Building the Freescale Toolchain Building bitbake fsl toolchain Build Results The toolchain is available from BASEDIR build_d0481_release deploy sdk Kontron Page 7 of 12 Appendix A local conf sample This file is your local configuration file and is where all local user settings are placed The comments in this file give some guide to the options a new user to the system might want to change but pretty much any configuration option can be set in this file More adventurous users can look at local conf extended which contains other examples of configuration which can be placed in this file but new users like
7. ain tests TEST _SCEN sanity bat sanity boot toolchain Because of the QEMU booting slowness issue see bug 646 and 618 may suffer a timeout issue when running sanity test We introduce variable TEST SERIALIZE here to reduce the time on sanity test pkgconfig etc oprofile lttng valgrind Ca print aplay arecord etc make an image for suitable of development ssh root access has a blank password There are other application targets that can be uses here too meta classes core image bbclass and meta recipes core tasks task core bb for more details We default to enabling the debugging tweaks XTRA_IMAGE FEATURES x86 only debug tweaks to reduce shared library files size for an image in order to prelink the filesystem image see local conf extended an emulator after any root filesystems are created and run tests against those images enable this uncomment this line IMAGETEST autobuilder It is by default set Page 10 of 12 to 1 This will start image and run cases in the same image without reboot or kill If it is set to 0 the image will be copied and tested for each case which will take longer but be more precise TEST SERIALIZE 1 Interactive shell configuration Under certain circumstances the system may need input from you and to do this it can launch an interactive shell It needs to do this since the build is multithreaded and needs to be able to handle the case where more than one parallel
8. eeases 8 Appendix B bblayers confisample csssssscsecsessessssssscsecsecsesssssssssecessesseassesasssessessesseseeasesseseesesueseeaseneeneeeeeseeasens 12 Kontron Page 2 of 12 Introduction The Kontron provided BSP layer meta kbc ppc is an additional layer that adds support for the Kontron COMe cP2020 modules on top of the Freescale SDK 1 3 Kontron provides the meta kbc layer on request Please contact lt support keu kontron com gt Additional Resources Freescale Technical Information Center http Avww freescale com infocenter topic gfamily sdk index html Yocto Project Homepage https www yoctoproject org BitBake User Manual http docs openembedded org bitbake html Kontron Page 3 of 12 Preparation Prerequisites Python 2 6 must be available from the default search path Installing Freescale SDK 1 3 The Freescale SDK 1 3 is not provided by Kontron but available from Freescale s homepage Please contact your Freescale FAE for more information http www freescale com weba sps site prod_summary jsp code SDKLINUX The location of the Freescale SDK 1 3 installation on the local file system is referenced as SDKDIR in the following text Basic Setup The following examples use shell variables that point to the installation directory of the original Freescale SDK and tothe directory that holds intermediate and build results These variables have to be set properly before following the ste
9. ly don t need any of them initially Lines starting with the character are commented out and in some cases the default values are provided as comments to show people example syntax Enabling the option is a question of removing the character and making any change to the variable as required Parallelism Options These two options control how much parallelism BitBake should use The first option determines how many tasks bitbake should run in parallel BB NUMBER THREADS 4 The second option controls how many processes make should run in parallel when running compile tasks PARALLEL MAKE Wee a For a quadcore BB NUMBER THREADS AT PARALLEL MAKE j 4 would be appropriate for example BB NUMBER THREADS VE PARALLEL MAKE Wey aY Machine Selection You need to select a specific machine to target the build with There are a selection emulated machines available which can boot and run in the QEMU emulator MACHINE qemuarm MACHINE qemumips MACHINE qemuppc MACHINE qemux86 MACHINE qemux86 64 There are also the following hardware board target machines included for demonstration purposes MACHINE atom pc MACHINE beagleboard MACHINE mpc8315e rdb MACHINE routerstationpro This sets the default machine to be d0481 if no other machine is selected MACHINE d0481 Where to place downloads During a first build the system will download many differernt source code
10. nk NOTE mklibs also needs to be explicitly enabled for a given image SER CLASSES image mklibs image prelink PACKAGE CLASSES package rpm SDK ADT target architecture This variable specified the architecture to build SDK ADT items for and means you can build the SDK packages for architectures other than the machine you are running the build on i e building i686 packages on an x86 64 host _ Supported values are i686 and x86 64 SDKMACHINE i686 Extra image configuration defaults The EXTRA IMAGE FEATURES variable allows extra packages to be added to the generated Some of these options are added to certain image types automatically The variable can contain the following options dbg packages for all installed packages ds symbol information for debugging profiling dev packages for all installed packages useful if you want to develop against libs in the image development tools debugging tools profiling tools useful testing tools Additional image features The following is a list of additional classes to use when building images which enable extra features Some available options which can be included in this variable to perform host system intrusion detection Runtime testing of images The build system can test booting virtual machine images under qemu This variable controls which tests are run against virtual images if enabled The following would enable bat oot test case under sanity suite and toolch
11. ps in this Application Note Shell Variable SDKBASE Point to the location of the Freescale SDK installation BASEDIR Points to the folder that holds your intermediate and buildresults Installing Kontron BSP Layer meta kbc ppc Extract the Kontron provided tar archive toa temporary folder this folder is referenced as BASEDIR in the following text tar xzf meta kbc ppc tgz C BASEDIR Build Directory and Sample Configuration Files Kontron provides the sample configuration files local conf sample and bblayers conf sample within the meta kbc ppc layer directory Create your local build directory by copying the sample configuration files into the new build directory install D BASEDIR meta kbc ppc conf local conf sample BASEDIR build_d0481 release conf local conf install D BASEDIR meta kbc ppc conf bblayers conf sample BASEDIR build_d0481 release conf bblayers conf Kontron Page 4 of 12 Adapt the Configuration Files The sample configuration files still contain the placeholders COREBASE and KBCBASE that have to be replaced withthe absolute paths that reflectyour build environment s gt COREBASE gt S SDKBASE gt g BASEDIR build _d0481_ release conf local conf s gt KBCBASE gt S BASEDIR gt g BASEDIR build_d0481 release conf local conf s gt COREBASE gt S SDKBASE gt g BASEDIR build_d0481_ release conf bblayers conf s gt KBCBASE gt S BASEDI
12. tarballs from various upstream projects This can take a while particularly if your network connection is slow These are all stored in DL DIR When wiping and rebuilding you Kontron Page 8 of 12 is safe to share between SSTATE DIR S TOPDIR s Where to place the build his option specifies whe The default is a tmp dire TMPDIR S TOPDIR tmp Default policy config The distribution setting The default value is fine Ultimately when creating these defaults DISTRO poky As an exable of a subclas where many versions are s useful to most new users DISTRO poky bleeding DISTRO fsl This variable lists which can be enabled at once an to generate the root file Options are package deb for debi package ipk for ipk package rpm for rpm E g PACKAGE CLASSES Kontron can preserve this directory to speed up this part of subsequent builds multiple builds on the same machine too The default is a downloads directory under TOPDIR which is the build directory DL DIR TOPDIR downloads Where to place shared state files BitBake has the capability to accelerate builds based on previously built output This is done using shared state files which can be through of as cache objects and this option determines where those files are placed You can wipe out TMPDIR leaving this directory intact and the build would regenerate from these files if no chages were made
Download Pdf Manuals
Related Search