Wiki Recent Changes

Track the most recent changes to the wiki in this feed. MediaWiki 1.28.0

URL: https://wiki.elphel.com/wiki/Special:RecentChanges

Updated: 8 min 31 sec ago

Camera Accessories

Tue, 12/03/2013 - 13:46

Lenses:

← Older revision Revision as of 20:46, 3 December 2013 (One intermediate revision not shown)Line 129: Line 129: | [[Image:Vd-4 5mm-F1 8-m12-adapters.jpeg|thumb|left|190px]] | [[Image:Vd-4 5mm-F1 8-m12-adapters.jpeg|thumb|left|190px]] | | -'''Vision Dimension''' +'''Evetar Lens''' -EFL=4.5mm, F/1.8, with IR cut-off filter. +N125B04518W EFL=4.5mm, F/1.8, with IR cut-off filter. Barrel threaded M12 + M12 adapter for C-Mount (price includes assembly) Barrel threaded M12 + M12 adapter for C-Mount (price includes assembly) Line 159: Line 159: | [[Image:T H2Z0414C-MP.jpg|thumb|left|120px]] | [[Image:T H2Z0414C-MP.jpg|thumb|left|120px]] | | -'''Computar Vari-focal Lens''' +'''Computar Vari-focal Lens, Megapixel''' 4-8mm, F/1.4, Manual Iris, Vari-Focal, C-Mount, Megapixel 4-8mm, F/1.4, Manual Iris, Vari-Focal, C-Mount, Megapixel Line 172: Line 172: | [[Image:2202161 big.jpg|thumb|left|190px]] | [[Image:2202161 big.jpg|thumb|left|190px]] | | -'''Computar Vari-focal Lens''' +'''Computar Vari-focal Lens, 3MPix''' 4.5-13.2mm, F/1.8, Manual Iris, Vari-Focal, CS-Mount, 3 MPix, Day/Night, IR 4.5-13.2mm, F/1.8, Manual Iris, Vari-Focal, CS-Mount, 3 MPix, Day/Night, IR Line 183: Line 183: |} |} + + + + +'''Computar Vari-focal Lens, 5 MPix''' + +1/1.8" 4.5-13.2mm F1.8 Manual Iris Vari-Focal Lens CS-Mount, 5 MPix, Day/Night, IR + + + +Product Code: E3Z4518CS-MPIR + +Price: $275 + Olga

Camera Accessories

Tue, 12/03/2013 - 12:54

← Older revision Revision as of 19:54, 3 December 2013 Line 159: Line 159: | [[Image:T H2Z0414C-MP.jpg|thumb|left|120px]] | [[Image:T H2Z0414C-MP.jpg|thumb|left|120px]] | | -'''Computar Vari-focal Lens''' +'''Computar Vari-focal Lens, Megapixel''' 4-8mm, F/1.4, Manual Iris, Vari-Focal, C-Mount, Megapixel 4-8mm, F/1.4, Manual Iris, Vari-Focal, C-Mount, Megapixel Line 172: Line 172: | [[Image:2202161 big.jpg|thumb|left|190px]] | [[Image:2202161 big.jpg|thumb|left|190px]] | | -'''Computar Vari-focal Lens''' +'''Computar Vari-focal Lens, 3MPix''' 4.5-13.2mm, F/1.8, Manual Iris, Vari-Focal, CS-Mount, 3 MPix, Day/Night, IR 4.5-13.2mm, F/1.8, Manual Iris, Vari-Focal, CS-Mount, 3 MPix, Day/Night, IR Line 183: Line 183: |} |} + + + + +'''Computar Vari-focal Lens, 5 MPix''' + +1/1.8" 4.5-13.2mm F1.8 Manual Iris Vari-Focal Lens CS-Mount, 5 MPix, Day/Night, IR + + + +Product Code: E3Z4518CS-MPIR + +Price: $275 + Olga

Yocto tests

Sat, 11/23/2013 - 16:42

← Older revision Revision as of 23:42, 23 November 2013 (One intermediate revision not shown)Line 68: Line 68: ====Notes==== ====Notes==== -* Is there a way to build it by running ''bitbake elphel393'' (elphel393 is the name of the ramdisk core image - currently coincides with the name of the MACHINE)+* Is there a way to build it by running ''bitbake core-image-elphel393'' Line 92: Line 92: -* When linux-xlnx is 'clean' it is built with the ramdisk.image.gz by ''bitbake elphel393'', however the boot.bin does not, why?+* When linux-xlnx is 'clean' it is built with the ramdisk.image.gz by ''bitbake core-image-elphel393'', however the boot.bin does not, why? Line 99: Line 99: ==Build ramdisk.image.gz== ==Build ramdisk.image.gz== - bitbake elphel393+ bitbake core-image-elphel393 ====Output==== ====Output==== Line 160: Line 160: ==Build everything all together== ==Build everything all together== - bitbake ezynq-u-boot linux-xlnx elphel393+ bitbake ezynq-u-boot linux-xlnx core-image-elphel393 Line 242: Line 242: **'''(Is there a better solution for kubuntu 13.04? in kubuntu 12.10 there is no such error - or is it just newer version?)''' 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?)? **'''(Is there a better solution for kubuntu 13.04? in kubuntu 12.10 there is no such error - or is it just newer version?)''' 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?)? **'''(Is there a better solution for kubuntu 13.04? in kubuntu 12.10 there is no such error - or is it just newer version?)''' To fix the '''ERROR'''="'''Failed to parse krb5_1.11.3.bb'''" in bitbake delete the directory ''meta-oe/meta-oe/recipes-connectivity/krb5'' **'''(Is there a better solution for kubuntu 13.04? in kubuntu 12.10 there is no such error - or is it just newer version?)''' To fix the '''ERROR'''="'''Failed to parse krb5_1.11.3.bb'''" in bitbake delete the directory ''meta-oe/meta-oe/recipes-connectivity/krb5'' + +==RTC config example in DTS== +http://www.denx.de/wiki/DULG/Appendix Oleg

Yocto tests

Thu, 11/21/2013 - 16:37

← Older revision Revision as of 23:37, 21 November 2013 Line 68: Line 68: ====Notes==== ====Notes==== -* Is there a way to build it by running ''bitbake elphel393'' (elphel393 is the name of the ramdisk core image - currently coincides with the name of the MACHINE)+* Is there a way to build it by running ''bitbake core-image-elphel393'' Line 92: Line 92: -* When linux-xlnx is 'clean' it is built with the ramdisk.image.gz by ''bitbake elphel393'', however the boot.bin does not, why?+* When linux-xlnx is 'clean' it is built with the ramdisk.image.gz by ''bitbake core-image-elphel393'', however the boot.bin does not, why? Line 99: Line 99: ==Build ramdisk.image.gz== ==Build ramdisk.image.gz== - bitbake elphel393+ bitbake core-image-elphel393 ====Output==== ====Output==== Line 160: Line 160: ==Build everything all together== ==Build everything all together== - bitbake ezynq-u-boot linux-xlnx elphel393+ bitbake ezynq-u-boot linux-xlnx core-image-elphel393 Oleg

Yocto tests

Wed, 11/20/2013 - 22:09

Setup:

← Older revision Revision as of 05:09, 21 November 2013 Line 32: Line 32: git clone -b dora git://git.yoctoproject.org/poky.git git clone -b dora git://git.yoctoproject.org/poky.git - cd poky (just for convenience)+ cd poky # (just for convenience) git clone git://git.code.sf.net/p/elphel/meta-elphel393 meta-elphel393 git clone git://git.code.sf.net/p/elphel/meta-elphel393 meta-elphel393 git clone git://git.code.sf.net/p/elphel/meta-ezynq meta-ezynq git clone git://git.code.sf.net/p/elphel/meta-ezynq meta-ezynq Andrey.filippov

Yocto tests

Wed, 11/20/2013 - 18:58

← Older revision Revision as of 01:58, 21 November 2013 (6 intermediate revisions not shown)Line 3: Line 3: * Building Linux images for Zynq platform - ARMv7 * Building Linux images for Zynq platform - ARMv7 - +==Required packages== + +[http://www.yoctoproject.org/docs/1.5/ref-manual/ref-manual.html#required-packages-for-the-host-development-system src link]: +* Essentials. Packages needed to build an image on a headless system: + sudo apt-get install gawk wget git-core diffstat unzip texinfo build-essential chrpath +* Graphical Extras. Packages recommended if the host system has graphics support: + sudo apt-get install libsdl1.2-dev xterm +* Documentation. Packages needed if you are going to build out the Yocto Project documentation manuals: + sudo apt-get install make xsltproc docbook-utils fop dblatex xmlto +* ADT Installer Extras. Packages needed if you are going to be using the Application Development Toolkit (ADT) Installer: + sudo apt-get install autoconf automake libtool libglib2.0-dev + ==Output targets== ==Output targets== Line 20: Line 31: * Step 1: * Step 1: - git clone -b dylan git://git.yoctoproject.org/poky.git+ git clone -b dora git://git.yoctoproject.org/poky.git cd poky (just for convenience) cd poky (just for convenience) git clone git://git.code.sf.net/p/elphel/meta-elphel393 meta-elphel393 git clone git://git.code.sf.net/p/elphel/meta-elphel393 meta-elphel393 git clone git://git.code.sf.net/p/elphel/meta-ezynq meta-ezynq git clone git://git.code.sf.net/p/elphel/meta-ezynq meta-ezynq - git clone -b dylan https://github.com/openembedded/meta-oe.git+ git clone -b dora https://github.com/openembedded/meta-oe.git * Step 2: Init environment * Step 2: Init environment Line 47: Line 58: ====Notes==== ====Notes==== * Currently having 4 MACHINES: elphel393, microzed, zc706 and zedboard * Currently having 4 MACHINES: elphel393, microzed, zc706 and zedboard - - ==Build ezynq-u-boot== ==Build ezynq-u-boot== Line 104: Line 113: IMAGE_INSTALL = "packagegroup-core-boot ${ROOTFS_PKGMANAGE_BOOTSTRAP} ${CORE_IMAGE_EXTRA_INSTALL}" IMAGE_INSTALL = "packagegroup-core-boot ${ROOTFS_PKGMANAGE_BOOTSTRAP} ${CORE_IMAGE_EXTRA_INSTALL}" IMAGE_INSTALL_append = "python-core" IMAGE_INSTALL_append = "python-core" -+ * Why ''python-core'' and not ''python''? * Why ''python-core'' and not ''python''? ** ''poky/meta/recipes-devtools/python/python-2.7-manifest.inc'' has a list in PACKAGES, items from which should go into IMAGE_INSTALL ** ''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. ** 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. ** Does '''hob''' install all the PACKAGES if ''python'' is checked? Haven't tried, also the used '''hob''' version doesn't support saving recipes. + * Steps for adding packages: * Steps for adding packages: ** ''elphel393.bb'' '''(some discussions mention the leading space is mandatory but somehow it works even without it)''': ** ''elphel393.bb'' '''(some discussions mention the leading space is mandatory but somehow it works even without it)''': Line 123: Line 133: PACKAGES = "${PN}-dbg ${PN}-cli ${PN}-cgi ${PN}-fpm ${PN}-fpm-apache2 ${PN}-pear ${PN}-dev ${PN}-staticdev ${PN}-doc ${PN}" PACKAGES = "${PN}-dbg ${PN}-cli ${PN}-cgi ${PN}-fpm ${PN}-fpm-apache2 ${PN}-pear ${PN}-dev ${PN}-staticdev ${PN}-doc ${PN}" *** PACKAGES list includes ''php''. What is installed? (No ''php-cli'': missing /usr/bin/php) Didn't investigate. *** PACKAGES list 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. *** What does hob build if ''php'' is checked? Didn't test. *** Using ''php-cli'' increases the unpacked image size from ~16MB to ~50MB. *** Using ''php-cli'' increases the unpacked image size from ~16MB to ~50MB. -**'''(Is there a better solution for kubuntu 13.04? in kubuntu 12.10 there is no such error - or is it just newer version?)''' 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?)? -**'''(Is there a better solution for kubuntu 13.04? in kubuntu 12.10 there is no such error - or is it just newer version?)''' To fix the '''ERROR'''="'''Failed to parse krb5_1.11.3.bb'''" in bitbake delete the directory ''meta-oe/meta-oe/recipes-connectivity/krb5'' Line 209: Line 218: * Try to add "_append" & "_prepend" to functions * Try to add "_append" & "_prepend" to functions * If some do_function is incompatible just rewrite it * If some do_function is incompatible just rewrite it + + +==Switch to dora branch== + cd poky; git checkout dora + cd meta-oe; git checkout dora + cd meta-elphel393; git checkout master + +==Branching in git== + +* switch to a branch: + git checkout <name> +* create a new local branch + git checkout -b <new-branch> <existing-branch> +* delete a local branch + git branch -D <name> +* create a new remote branch (from existing local) + git push origin <name> +* delete a remote branch + git push origin :<name> + + +==Disappeared errors== +**'''(Is there a better solution for kubuntu 13.04? in kubuntu 12.10 there is no such error - or is it just newer version?)''' 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?)? +**'''(Is there a better solution for kubuntu 13.04? in kubuntu 12.10 there is no such error - or is it just newer version?)''' To fix the '''ERROR'''="'''Failed to parse krb5_1.11.3.bb'''" in bitbake delete the directory ''meta-oe/meta-oe/recipes-connectivity/krb5'' Oleg

Yocto tests

Wed, 11/20/2013 - 14:15

← Older revision Revision as of 21:15, 20 November 2013 (5 intermediate revisions not shown)Line 20: Line 20: * Step 1: * Step 1: - git clone -b dylan git://git.yoctoproject.org/poky.git+ git clone -b dora git://git.yoctoproject.org/poky.git cd poky (just for convenience) cd poky (just for convenience) git clone git://git.code.sf.net/p/elphel/meta-elphel393 meta-elphel393 git clone git://git.code.sf.net/p/elphel/meta-elphel393 meta-elphel393 git clone git://git.code.sf.net/p/elphel/meta-ezynq meta-ezynq git clone git://git.code.sf.net/p/elphel/meta-ezynq meta-ezynq - git clone -b dylan https://github.com/openembedded/meta-oe.git+ git clone -b dora https://github.com/openembedded/meta-oe.git * Step 2: Init environment * Step 2: Init environment Line 47: Line 47: ====Notes==== ====Notes==== * Currently having 4 MACHINES: elphel393, microzed, zc706 and zedboard * Currently having 4 MACHINES: elphel393, microzed, zc706 and zedboard - - ==Build ezynq-u-boot== ==Build ezynq-u-boot== Line 104: Line 102: IMAGE_INSTALL = "packagegroup-core-boot ${ROOTFS_PKGMANAGE_BOOTSTRAP} ${CORE_IMAGE_EXTRA_INSTALL}" IMAGE_INSTALL = "packagegroup-core-boot ${ROOTFS_PKGMANAGE_BOOTSTRAP} ${CORE_IMAGE_EXTRA_INSTALL}" IMAGE_INSTALL_append = "python-core" IMAGE_INSTALL_append = "python-core" -+ * Why ''python-core'' and not ''python''? * Why ''python-core'' and not ''python''? ** ''poky/meta/recipes-devtools/python/python-2.7-manifest.inc'' has a list in PACKAGES, items from which should go into IMAGE_INSTALL ** ''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. ** 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. ** Does '''hob''' install all the PACKAGES if ''python'' is checked? Haven't tried, also the used '''hob''' version doesn't support saving recipes. + * Steps for adding packages: * Steps for adding packages: ** ''elphel393.bb'' '''(some discussions mention the leading space is mandatory but somehow it works even without it)''': ** ''elphel393.bb'' '''(some discussions mention the leading space is mandatory but somehow it works even without it)''': Line 123: Line 122: PACKAGES = "${PN}-dbg ${PN}-cli ${PN}-cgi ${PN}-fpm ${PN}-fpm-apache2 ${PN}-pear ${PN}-dev ${PN}-staticdev ${PN}-doc ${PN}" PACKAGES = "${PN}-dbg ${PN}-cli ${PN}-cgi ${PN}-fpm ${PN}-fpm-apache2 ${PN}-pear ${PN}-dev ${PN}-staticdev ${PN}-doc ${PN}" *** PACKAGES list includes ''php''. What is installed? (No ''php-cli'': missing /usr/bin/php) Didn't investigate. *** PACKAGES list 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. *** What does hob build if ''php'' is checked? Didn't test. *** Using ''php-cli'' increases the unpacked image size from ~16MB to ~50MB. *** Using ''php-cli'' increases the unpacked image size from ~16MB to ~50MB. -**'''(Is there a better solution for kubuntu 13.04? in kubuntu 12.10 there is no such error - or is it just newer version?)''' 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?)? -**'''(Is there a better solution for kubuntu 13.04? in kubuntu 12.10 there is no such error - or is it just newer version?)''' To fix the '''ERROR'''="'''Failed to parse krb5_1.11.3.bb'''" in bitbake delete the directory ''meta-oe/meta-oe/recipes-connectivity/krb5'' Line 209: Line 207: * Try to add "_append" & "_prepend" to functions * Try to add "_append" & "_prepend" to functions * If some do_function is incompatible just rewrite it * If some do_function is incompatible just rewrite it + + +==Switch to dora branch== + cd poky; git checkout dora + cd meta-oe; git checkout dora + cd meta-elphel393; git checkout master + +==Branching in git== + +* switch to a branch: + git checkout <name> +* create a new local branch + git checkout -b <new-branch> <existing-branch> +* delete a local branch + git branch -D <name> +* create a new remote branch (from existing local) + git push origin <name> +* delete a remote branch + git push origin :<name> + + +==Disappeared errors== +**'''(Is there a better solution for kubuntu 13.04? in kubuntu 12.10 there is no such error - or is it just newer version?)''' 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?)? +**'''(Is there a better solution for kubuntu 13.04? in kubuntu 12.10 there is no such error - or is it just newer version?)''' To fix the '''ERROR'''="'''Failed to parse krb5_1.11.3.bb'''" in bitbake delete the directory ''meta-oe/meta-oe/recipes-connectivity/krb5'' Oleg

Yocto tests

Wed, 11/20/2013 - 14:03

Setup:

← Older revision Revision as of 21:03, 20 November 2013 (3 intermediate revisions not shown)Line 20: Line 20: * Step 1: * Step 1: - git clone -b dylan git://git.yoctoproject.org/poky.git+ git clone -b dora git://git.yoctoproject.org/poky.git cd poky (just for convenience) cd poky (just for convenience) git clone git://git.code.sf.net/p/elphel/meta-elphel393 meta-elphel393 git clone git://git.code.sf.net/p/elphel/meta-elphel393 meta-elphel393 git clone git://git.code.sf.net/p/elphel/meta-ezynq meta-ezynq git clone git://git.code.sf.net/p/elphel/meta-ezynq meta-ezynq - git clone -b dylan https://github.com/openembedded/meta-oe.git+ git clone -b dora https://github.com/openembedded/meta-oe.git * Step 2: Init environment * Step 2: Init environment Line 47: Line 47: ====Notes==== ====Notes==== * Currently having 4 MACHINES: elphel393, microzed, zc706 and zedboard * Currently having 4 MACHINES: elphel393, microzed, zc706 and zedboard - - ==Build ezynq-u-boot== ==Build ezynq-u-boot== Line 209: Line 207: * Try to add "_append" & "_prepend" to functions * Try to add "_append" & "_prepend" to functions * If some do_function is incompatible just rewrite it * If some do_function is incompatible just rewrite it + + +==Switch to dora branch== + cd poky; git checkout dora + cd meta-oe; git checkout dora + cd meta-elphel393; git checkout master Oleg

Yocto tests

Tue, 11/19/2013 - 17:51

← Older revision Revision as of 00:51, 20 November 2013 (2 intermediate revisions not shown)Line 24: Line 24: git clone git://git.code.sf.net/p/elphel/meta-elphel393 meta-elphel393 git clone git://git.code.sf.net/p/elphel/meta-elphel393 meta-elphel393 git clone git://git.code.sf.net/p/elphel/meta-ezynq meta-ezynq git clone git://git.code.sf.net/p/elphel/meta-ezynq meta-ezynq - git clone -b dylan https://github.com/openembedded/meta-oe.git+ git clone https://github.com/openembedded/meta-oe.git * Step 2: Init environment * Step 2: Init environment Line 209: Line 209: * Try to add "_append" & "_prepend" to functions * Try to add "_append" & "_prepend" to functions * If some do_function is incompatible just rewrite it * If some do_function is incompatible just rewrite it + + +==Switch to dora branch== + cd poky; git checkout dora + cd meta-oe; git checkout dora + cd meta-elphel393; git checkout master Oleg

Yocto tests

Fri, 11/15/2013 - 12:15

← Older revision Revision as of 19:15, 15 November 2013 Line 24: Line 24: git clone git://git.code.sf.net/p/elphel/meta-elphel393 meta-elphel393 git clone git://git.code.sf.net/p/elphel/meta-elphel393 meta-elphel393 git clone git://git.code.sf.net/p/elphel/meta-ezynq meta-ezynq git clone git://git.code.sf.net/p/elphel/meta-ezynq meta-ezynq - git clone -b dylan https://github.com/openembedded/meta-oe.git+ git clone https://github.com/openembedded/meta-oe.git * Step 2: Init environment * Step 2: Init environment Oleg

Elphel camera parts 0353-30

Thu, 11/14/2013 - 14:25

0353-30-24 - Silicone Gasket for M40.5 filter:

← Older revision Revision as of 21:25, 14 November 2013 (One intermediate revision not shown)Line 122: Line 122: ---- ---- -=== 0353-30-24 - Silicone Gasket for M40.5 filter ===+=== 0353-30-24 - Silicone Gasket for M40.5 filter (replaced with 0343-30-27) === t=0.8mm OD=42.5mm, ID=40mm, Cut from McMaster 2633T11 30A or equivalent t=0.8mm OD=42.5mm, ID=40mm, Cut from McMaster 2633T11 30A or equivalent {{Cad4|0353-30-24}} {{Cad4|0353-30-24}} ---- ---- + === 0353-30-25 - Silicone Gasket for M72 filter === === 0353-30-25 - Silicone Gasket for M72 filter === t=0.8mm OD=76mm, ID=71.5mm, Cut from McMaster 2633T11 30A or equivalent t=0.8mm OD=76mm, ID=71.5mm, Cut from McMaster 2633T11 30A or equivalent Line 132: Line 133: ---- ---- -=== 0353-30-27 - Silicone Gasket for M34 filter ===+=== 0353-30-27 - Silicone Gasket for M34 filter (used for M40.5 filter)=== t=0.8mm OD=36mm, ID=33.5mm, Cut from McMaster 2633T11 30A or equivalent t=0.8mm OD=36mm, ID=33.5mm, Cut from McMaster 2633T11 30A or equivalent {{Cad4|0353-30-27}} {{Cad4|0353-30-27}} Olga

Yocto tests

Wed, 11/13/2013 - 14:21

Show changes Oleg

Yocto tests

Wed, 11/13/2013 - 01:57

Add a patch to a recipe:

Show changes Oleg

Yocto tests

Wed, 11/13/2013 - 01:27

Show changes Oleg

Yocto tests

Tue, 11/12/2013 - 15:15

Show changes Oleg

Yocto tests

Tue, 11/12/2013 - 12:41

Add a patch to a recipe:

Show changes Oleg

Yocto tests

Tue, 11/12/2013 - 01:19

← Older revision Revision as of 08:19, 12 November 2013 (10 intermediate revisions not shown)Line 3: Line 3: * Building Linux images for Zynq platform - ARMv7 * Building Linux images for Zynq platform - ARMv7 +==Output targets== +These names are as they appear in the u-boot configuration header file - actual output files have different names: +* '''boot.bin''' - u-boot as the first stage bootloader +* '''devicetree.dtb''' - device tree with described interfaces, zynq registers, interrupts and drivers +* '''uImage''' - kernel, drivers +* '''uramdisk.image.gz''' - applications +Copy them on the micro SD card > run '''boot''' once in the u-boot command line. ==GIT== ==GIT== git clone -b dylan git://git.yoctoproject.org/poky.git git clone -b dylan git://git.yoctoproject.org/poky.git - git clone -b dylan https://github.com/Xilinx/meta-xilinx.git meta-xilinx+ cd poky (just for convenience) + git clone -b dylan https://github.com/Xilinx/meta-xilinx.git meta-xilinx (not needed) git clone git://git.code.sf.net/p/elphel/meta-elphel393 meta-elphel393 git clone git://git.code.sf.net/p/elphel/meta-elphel393 meta-elphel393 + git clone git://git.code.sf.net/p/elphel/meta-ezynq meta-ezynq + git clone -b dylan https://github.com/openembedded/meta-oe.git Line 21: Line 31: <absolute-path>/meta-xilinx/meta-zedboard \ <absolute-path>/meta-xilinx/meta-zedboard \ <absolute-path>/meta-elphel393 \ <absolute-path>/meta-elphel393 \ + <absolute-path>/meta-ezynq \ * Step 3: Edit ''build/conf/local.conf'' - set MACHINE and other things: * Step 3: Edit ''build/conf/local.conf'' - set MACHINE and other things: Line 26: Line 37: BB_NUMBER_THREADS = "8" (depends on the PC's CPU) BB_NUMBER_THREADS = "8" (depends on the PC's CPU) PARALLEL_MAKE = "-j 8" (depends on the PC's CPU) PARALLEL_MAKE = "-j 8" (depends on the PC's CPU) - MACHINE ?= "zedboard"+ MACHINE ?= "elphel393" (based on MACHINE="zedboard" ) ====Notes==== ====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.+* Does ''./oe-init-build-env'' scan all the meta-* dirs in poky? Unlikely. + + +==Build ezynq-u-boot== + + bitbake ezynq-u-boot + +====Output==== +* boot.bin + +====Notes==== + +* Is there a way to build it by running ''bitbake elphel393'' (elphel393 is the name of the ramdisk core image - currently coincides with the name of the MACHINE) Line 37: Line 60: bitbake linux-xlnx bitbake linux-xlnx +====Output==== +* uImage (kernel) +* devicetree.dtb (or some *.dtb) ====Notes==== ====Notes==== -* The '''dtc''' script for converting device tree between *.dts and *.dtb formats is built along with the kernel.+* When linux-xlnx is 'clean' it is built with the ramdisk.image.gz by ''bitbake elphel393'', however the boot.bin does not, why? Line 47: Line 73: bitbake elphel393 bitbake elphel393 +===Output==== +* uramdisk.image.gz (the file has *.u-boot extension after it's built) + ====Notes==== ====Notes==== Line 57: Line 86: IMAGE_INSTALL = "packagegroup-core-boot ${ROOTFS_PKGMANAGE_BOOTSTRAP} ${CORE_IMAGE_EXTRA_INSTALL}" IMAGE_INSTALL = "packagegroup-core-boot ${ROOTFS_PKGMANAGE_BOOTSTRAP} ${CORE_IMAGE_EXTRA_INSTALL}" IMAGE_INSTALL_append = "python-core" IMAGE_INSTALL_append = "python-core" -* Why ''python-core'' and not just ''python''?+* Why ''python-core'' and not ''python''? -** ''poky/meta/recipes-devtools/python/python-2.7-manifest.inc'' has a list in PACKAGES items from which should go into IMAGE_INSTALL+** ''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. ** 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. ** 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''', '''i2c-tools''', '''mtd-utils''', '''net-tools''' steps:+* '''(Is there a better solution for kubuntu 13.04? in kubuntu 12.10 there are no errors mentioned below - or is it just newer version?)''' Steps for adding packages: -**Clone '''meta-oe''' from OpenEmbedded: +**Clone '''meta-oe''' from OpenEmbedded (ia already cloned in the GIT-step): git clone -b dylan https://github.com/openembedded/meta-oe.git git clone -b dylan https://github.com/openembedded/meta-oe.git **Lines to ''bblayers.conf'': **Lines to ''bblayers.conf'': <absolute-path>/meta-oe/meta-oe \ <absolute-path>/meta-oe/meta-oe \ - <absolute-path>/poky/meta-oe/meta-perl \ <absolute-path>/poky/meta-oe/meta-webserver \ <absolute-path>/poky/meta-oe/meta-webserver \ ** ''elphel393.bb'' '''(some discussions mention the leading space is mandatory but somehow it works even without it)''': ** ''elphel393.bb'' '''(some discussions mention the leading space is mandatory but somehow it works even without it)''': Line 73: Line 101: mtd-utils \ mtd-utils \ net-tools \ net-tools \ + openssh \ modphp \ modphp \ apache2 \ apache2 \ Line 79: Line 108: meta-oe/meta-oe/recipes-devtools/php/php.inc: 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 = "${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.+*** PACKAGES list 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. *** 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. *** 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'''="'''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'' + + ====U-boot and device tree related notes==== ====U-boot and device tree related notes==== * '''The default UNPACKED ramdisk max 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] - then recompile into DTB:''' * '''The default UNPACKED ramdisk max 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] - then recompile into DTB:''' *.dts, add to '''bootargs''' parameter ''ramdisk_size=32768'' (takes KB), example: *.dts, add to '''bootargs''' parameter ''ramdisk_size=32768'' (takes KB), example: - bootargs = "console=ttyPS0,115200 root=/dev/ram rw ip=192.168.1.10 earlyprintk '''ramdisk_size=32768'''";+ bootargs = "console=ttyPS0,115200 root=/dev/ram rw ip=192.168.1.10 earlyprintk '''ramdisk_size=65536'''"; * '''The default COMPRESSED ramdisk max size for zynq is 10MB set in u-boot''' - change according to your needs, example: * '''The default COMPRESSED ramdisk max size for zynq is 10MB set in u-boot''' - change according to your needs, example: ''zynq_zed.h'': ''zynq_zed.h'': Line 102: Line 132: devicetree = 0x3000000 - 0x2A00000 = 0x600000 = 6MB devicetree = 0x3000000 - 0x2A00000 = 0x600000 = 6MB -+==Build everything all together== -+ bitbake ezynq-u-boot linux-xlnx elphel393 - +==Build toolchain (not necessary)== -==Build toolchain==+ * Step 1: build * Step 1: build Oleg

Ezynq

Sun, 11/10/2013 - 19:43

← Older revision Revision as of 02:43, 11 November 2013 Line 11: Line 11: * '''boot.bin''' (fsbl is not required to boot) * '''boot.bin''' (fsbl is not required to boot) -==Install meta-toolchain (Ubuntu 13.04)==+==Install meta-toolchain (Kubuntu 13.04)== * * Line 23: Line 23: * Run installation script in ''build/tmp/deploy/'' * Run installation script in ''build/tmp/deploy/'' -==Install ezynq (Ubuntu 13.04)==+==Install ezynq (Kubuntu 13.04)== git clone git://git.code.sf.net/p/elphel/ezynq ezynq git clone git://git.code.sf.net/p/elphel/ezynq ezynq Oleg

Yocto tests

Sun, 11/10/2013 - 19:41

← Older revision Revision as of 02:41, 11 November 2013 (12 intermediate revisions not shown)Line 1: Line 1: +==About== +* All of the described things happen in Kubuntu 13.04 +* Building Linux images for Zynq platform - ARMv7 + ==GIT== ==GIT== git clone -b dylan git://git.yoctoproject.org/poky.git git clone -b dylan git://git.yoctoproject.org/poky.git - git clone -b dylan https://github.com/Xilinx/meta-xilinx.git poky/meta-xilinx+ git clone -b dylan https://github.com/Xilinx/meta-xilinx.git meta-xilinx - git clone git://git.code.sf.net/p/elphel/meta-elphel393 poky/meta-elphel393+ git clone git://git.code.sf.net/p/elphel/meta-elphel393 meta-elphel393 Line 14: Line 18: * Step 2: Edit ''build/conf/bblayers.conf'' - add paths to BBLAYERS: * Step 2: Edit ''build/conf/bblayers.conf'' - add paths to BBLAYERS: - <absolute-path>/poky/meta-xilinx \+ <absolute-path>/meta-xilinx \ - <absolute-path>/poky/meta-xilinx/meta-zedboard \+ <absolute-path>/meta-xilinx/meta-zedboard \ - <absolute-path>/poky/meta-elphel393 \+ <absolute-path>/meta-elphel393 \ * Step 3: Edit ''build/conf/local.conf'' - set MACHINE and other things: * Step 3: Edit ''build/conf/local.conf'' - set MACHINE and other things: Line 22: Line 26: BB_NUMBER_THREADS = "8" (depends on the PC's CPU) BB_NUMBER_THREADS = "8" (depends on the PC's CPU) PARALLEL_MAKE = "-j 8" (depends on the PC's CPU) PARALLEL_MAKE = "-j 8" (depends on the PC's CPU) - MACHINE ?= "zedboard" '''(?)'''+ 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. Line 28: Line 36: bitbake linux-xlnx bitbake linux-xlnx + + +====Notes==== + +* The '''dtc''' script for converting device tree between *.dts and *.dtb formats is built along with the kernel. Line 33: Line 46: bitbake elphel393 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''', '''i2c-tools''', '''mtd-utils''', '''net-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 \ + mtd-utils \ + net-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'' +====U-boot and device tree related notes==== +* '''The default UNPACKED ramdisk max 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] - then recompile into DTB:''' + *.dts, add to '''bootargs''' parameter ''ramdisk_size=32768'' (takes KB), example: + bootargs = "console=ttyPS0,115200 root=/dev/ram rw ip=192.168.1.10 earlyprintk '''ramdisk_size=32768'''"; +* '''The default COMPRESSED ramdisk max size for zynq is 10MB set in u-boot''' - change according to your needs, example: + ''zynq_zed.h'': + "sdboot=echo Copying Linux from SD to RAM... && " \ + "mmcinfo && " \ + "fatload mmc 0 0x3000000 ${kernel_image} && " \ + "fatload mmc 0 0x2A00000 ${devicetree_image} && " \ + "fatload mmc 0 0x2000000 ${ramdisk_image} && " \ + "bootm 0x3000000 0x2000000 0x2A00000\0" \ + + So, the max sizes: + compressed ramdisk = 0x2A00000 - 0x2000000 = 0xA00000 = 10MB + devicetree = 0x3000000 - 0x2A00000 = 0x600000 = 6MB + + Oleg

Yocto tests

Fri, 11/08/2013 - 16:53

← Older revision Revision as of 23:53, 8 November 2013 (9 intermediate revisions not shown)Line 1: Line 1: +==About== +* All of the described things happen in Kubuntu 13.04 +* Building Linux images for Zynq platform - ARMv7 + ==GIT== ==GIT== git clone -b dylan git://git.yoctoproject.org/poky.git git clone -b dylan git://git.yoctoproject.org/poky.git - git clone -b dylan https://github.com/Xilinx/meta-xilinx.git poky/meta-xilinx+ git clone -b dylan https://github.com/Xilinx/meta-xilinx.git meta-xilinx - git clone git://git.code.sf.net/p/elphel/meta-elphel393 poky/meta-elphel393+ git clone git://git.code.sf.net/p/elphel/meta-elphel393 meta-elphel393 Line 14: Line 18: * Step 2: Edit ''build/conf/bblayers.conf'' - add paths to BBLAYERS: * Step 2: Edit ''build/conf/bblayers.conf'' - add paths to BBLAYERS: - <absolute-path>/poky/meta-xilinx \+ <absolute-path>/meta-xilinx \ - <absolute-path>/poky/meta-xilinx/meta-zedboard \+ <absolute-path>/meta-xilinx/meta-zedboard \ - <absolute-path>/poky/meta-elphel393 \+ <absolute-path>/meta-elphel393 \ * Step 3: Edit ''build/conf/local.conf'' - set MACHINE and other things: * Step 3: Edit ''build/conf/local.conf'' - set MACHINE and other things: Line 22: Line 26: BB_NUMBER_THREADS = "8" (depends on the PC's CPU) BB_NUMBER_THREADS = "8" (depends on the PC's CPU) PARALLEL_MAKE = "-j 8" (depends on the PC's CPU) PARALLEL_MAKE = "-j 8" (depends on the PC's CPU) - MACHINE ?= "zedboard" '''(?)'''+ 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. Line 28: Line 36: bitbake linux-xlnx bitbake linux-xlnx + + +===Notes=== + +* The '''dtc''' script for converting device tree between *.dts and *.dtb formats is built along with the kernel. Line 33: Line 46: bitbake elphel393 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''', '''i2c-tools''', '''mtd-utils''', 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 \ + mtd-utils \ + 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'' +===U-boot and device tree related notes=== +* '''The default UNPACKED ramdisk max 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] - then recompile into DTB:''' + *.dts, add to '''bootargs''' parameter ''ramdisk_size=32768'' (takes KB), example: + bootargs = "console=ttyPS0,115200 root=/dev/ram rw ip=192.168.1.10 earlyprintk '''ramdisk_size=32768'''"; +* '''The default COMPRESSED ramdisk max size for zynq is 10MB set in u-boot''' - change according to your needs, example: + ''zynq_zed.h'': + "sdboot=echo Copying Linux from SD to RAM... && " \ + "mmcinfo && " \ + "fatload mmc 0 0x3000000 ${kernel_image} && " \ + "fatload mmc 0 0x2A00000 ${devicetree_image} && " \ + "fatload mmc 0 0x2000000 ${ramdisk_image} && " \ + "bootm 0x3000000 0x2000000 0x2A00000\0" \ + + So, the max sizes: + compressed ramdisk = 0x2A00000 - 0x2000000 = 0xA00000 = 10MB + devicetree = 0x3000000 - 0x2A00000 = 0x600000 = 6MB + + Oleg

Secondary menu

Elphel Development Blog

Elphel GIT logs

Elphel CVS logs

Who's online

Camera Accessories

Camera Accessories

Yocto tests

Yocto tests

Yocto tests

Yocto tests

Yocto tests

Yocto tests

Yocto tests

Yocto tests

Elphel camera parts 0353-30

Yocto tests

Yocto tests

Yocto tests

Yocto tests

Yocto tests

Yocto tests

Ezynq

Yocto tests

Yocto tests

Pages