Difference between revisions of "Yocto tests"
From ElphelWiki
m |
m |
||
| Line 1: | Line 1: | ||
| + | ==About== | ||
| + | * in Kubuntu 13.04 | ||
| + | * Building Linux images for Zynq platform - ARMv7 | ||
| + | |||
==GIT== | ==GIT== | ||
<font size='2'> | <font size='2'> | ||
| Line 74: | Line 78: | ||
**To fix the '''ERROR'''="'''Could not inherit file classes/vala.bbclass'''" in bitbake copy vala.bbclass from oe-core? or delete the conflicting recipes (2?)? | **To fix the '''ERROR'''="'''Could not inherit file classes/vala.bbclass'''" in bitbake copy vala.bbclass from oe-core? or delete the conflicting recipes (2?)? | ||
**To fix the '''ERROR'''="'''Failed to parse krb5_1.11.3.bb'''" in bitbake delete the directory ''meta-oe/meta-oe/recipes-connectivity/krb5'' | **To fix the '''ERROR'''="'''Failed to parse krb5_1.11.3.bb'''" in bitbake delete the directory ''meta-oe/meta-oe/recipes-connectivity/krb5'' | ||
| + | * '''The default ramdisk size for zynq is 16MB - once it gets bigger you get KERNEL PANIC - the solution is [http://forums.xilinx.com/t5/Embedded-Linux/Need-bigger-ramdisk-32MB-on-ZC702/m-p/303457#M5775 modifying the device tree]:''' | ||
| + | *.dts, add to '''bootargs''' parameter ''ramdisk_size=32768'' (in KB), example: | ||
| + | bootargs = "console=ttyPS0,115200 root=/dev/ram rw ip=192.168.1.10 earlyprintk '''ramdisk_size=32768'''"; | ||
</font> | </font> | ||
</font> | </font> | ||
| − | |||
| − | |||
==Build toolchain== | ==Build toolchain== | ||
Revision as of 11:34, 8 November 2013
Contents
About
- in Kubuntu 13.04
- Building Linux images for Zynq platform - ARMv7
GIT
git clone -b dylan git://git.yoctoproject.org/poky.git git clone -b dylan https://github.com/Xilinx/meta-xilinx.git meta-xilinx git clone git://git.code.sf.net/p/elphel/meta-elphel393 meta-elphel393
Configure
- Step 1: Init environment
cd poky . ./oe-init-build-env
- Step 2: Edit build/conf/bblayers.conf - add paths to BBLAYERS:
<absolute-path>/meta-xilinx \ <absolute-path>/meta-xilinx/meta-zedboard \ <absolute-path>/meta-elphel393 \
- Step 3: Edit build/conf/local.conf - set MACHINE and other things:
BB_NUMBER_THREADS = "8" (depends on the PC's CPU) PARALLEL_MAKE = "-j 8" (depends on the PC's CPU) MACHINE ?= "zedboard"
Notes
- MACHINE="zedboard" is used to build the kernel. Doesn't matter for ramdisk.image.gz because the recipes don't have any bbappends for core-images.
Build kernel
bitbake linux-xlnx
Build ramdisk.image.gz
bitbake elphel393
Notes
- Current packages:
elphel393.bb:
IMAGE_INSTALL = "packagegroup-core-boot python-core ${ROOTFS_PKGMANAGE_BOOTSTRAP} ${CORE_IMAGE_EXTRA_INSTALL}"
- Also works:
elphel393.bb:
IMAGE_INSTALL = "packagegroup-core-boot ${ROOTFS_PKGMANAGE_BOOTSTRAP} ${CORE_IMAGE_EXTRA_INSTALL}"
IMAGE_INSTALL_append = "python-core"
- Why python-core and not just python?
- poky/meta/recipes-devtools/python/python-2.7-manifest.inc has a list in PACKAGES items from which should go into IMAGE_INSTALL
- Among all there's no python in the PACKAGES list.
- Does hob install all the PACKAGES if python is checked? Haven't tried, also the used hob version doesn't support saving recipes.
- (Is there a better solution?) Adding packages : apache2, php and i2c-tools, steps:
- Clone meta-oe from OpenEmbedded:
git clone -b dylan https://github.com/openembedded/meta-oe.git
- Lines to bblayers.conf:
<absolute-path>/meta-oe/meta-oe \ <absolute-path>/poky/meta-oe/meta-perl \ <absolute-path>/poky/meta-oe/meta-webserver \
- elphel393.bb (some discussions mention the leading space is mandatory but somehow it works even without it):
IMAGE_INSTALL_append = "<mandatory space?>python-core \
i2c-tools \
modphp \
apache2 \
php-cli"
- Why php-cli and not just php?
meta-oe/meta-oe/recipes-devtools/php/php.inc:
PACKAGES = "${PN}-dbg ${PN}-cli ${PN}-cgi ${PN}-fpm ${PN}-fpm-apache2 ${PN}-pear ${PN}-dev ${PN}-staticdev ${PN}-doc ${PN}"
- PACKAGES includes php. What is installed? (No php-cli: missing /usr/bin/php) Didn't investigate.
- What does hob build if php is checked? Didn't test.
- Using php-cli installs php in the /usr/bin/. Tested.
- Using php-cli increases the unpacked image size from ~16MB to ~50MB.
- To fix the ERROR="Could not inherit file classes/vala.bbclass" in bitbake copy vala.bbclass from oe-core? or delete the conflicting recipes (2?)?
- To fix the ERROR="Failed to parse krb5_1.11.3.bb" in bitbake delete the directory meta-oe/meta-oe/recipes-connectivity/krb5
- The default ramdisk size for zynq is 16MB - once it gets bigger you get KERNEL PANIC - the solution is modifying the device tree:
*.dts, add to bootargs parameter ramdisk_size=32768 (in KB), example: bootargs = "console=ttyPS0,115200 root=/dev/ram rw ip=192.168.1.10 earlyprintk ramdisk_size=32768";
Build toolchain
- Step 1: build
bitbake meta-toolchain
- Step 2: install - launch installer from <some-path>/poky/build/tmp/deploy/
