uploaded "[[File:0353-70-481.stp.tar.gz]]"

Oleg

← Older revision Revision as of 17:35, 9 May 2014 Line 21: Line 21: | [[Elphel_camera_parts_0353-26#0353-26-08_-_Camera_mount_spacer|0353-26-08 ]]|| Camera mount spacer  || 8 ||   | [[Elphel_camera_parts_0353-26#0353-26-08_-_Camera_mount_spacer|0353-26-08 ]]|| Camera mount spacer  || 8 ||   |- |- -| [[Elphel_camera_parts_0353-23#0353-23-10_-_SFE_insert_holder|0353-23-10 ]]|| SFE insert holder  || 4 ||  +| [[Elphel_camera_parts_0353-23#0353-23-10A_-_SFE_insert_holder|0353-23-10A ]]|| SFE insert holder  || 4 ||   |- |- | [[Elphel_camera_parts_0353-23#0353-23-11_-_SFE_insert_assembly_plate|0353-23-11 ]]|| SFE insert assembly plate || 4 ||   | [[Elphel_camera_parts_0353-23#0353-23-11_-_SFE_insert_assembly_plate|0353-23-11 ]]|| SFE insert assembly plate || 4 ||   Olga

← Older revision Revision as of 00:50, 30 April 2014 Line 44: Line 44:           git clone -b master git://git.code.sf.net/p/elphel/meta-elphel393 meta-elphel393   git clone -b master git://git.code.sf.net/p/elphel/meta-elphel393 meta-elphel393 -  cd meta-elphel393; git checkout 777ee20496edebc0f83981e5755d551c46466833; cd ..+  cd meta-elphel393; git checkout 9e09294803fc370657424235b395d205dd0994a3; cd ..           '''#Part 2 : init environment and auto-fill Yocto's conf-files'''   '''#Part 2 : init environment and auto-fill Yocto's conf-files''' Oleg

Install meta-toolchain (Kubuntu 13.04):

← Older revision Revision as of 22:07, 25 April 2014 Line 46: Line 46: <font size='2'> <font size='2'>   sudo apt-get install texinfo chrpath   sudo apt-get install texinfo chrpath -  git clone -b dylan git://git.yoctoproject.org/poky+  git clone -b dora git://git.yoctoproject.org/poky   cd poky   cd poky   . ./oe-init-build-env   . ./oe-init-build-env Line 53: Line 53: * Run installation script in ''build/tmp/deploy/'' * Run installation script in ''build/tmp/deploy/'' -  ==Install Ezynq (Kubuntu 13.04)== ==Install Ezynq (Kubuntu 13.04)== Oleg

Setup:

← Older revision Revision as of 20:35, 25 April 2014 (One intermediate revision not shown)Line 32: Line 32:           git clone -b dora git://git.yoctoproject.org/poky.git poky   git clone -b dora git://git.yoctoproject.org/poky.git poky -  cd poky; git checkout f1276b066223e7f501f7f711680215ff8edee252+  cd poky; git checkout 50e9ccb2aff7b9f9dca4fda99a6832c60f64de3b           git clone -b dora https://github.com/openembedded/meta-oe.git meta-oe   git clone -b dora https://github.com/openembedded/meta-oe.git meta-oe -  cd meta-oe; git checkout 40e0f371f3eb1628655c484feac0cebf810737b4; cd ..+  cd meta-oe; git checkout ee173678383683e972c7d4d6f0ef5790bfa50274; cd ..           git clone -b dora https://github.com/Xilinx/meta-xilinx.git meta-xilinx   git clone -b dora https://github.com/Xilinx/meta-xilinx.git meta-xilinx Line 41: Line 41:           git clone -b master git://git.code.sf.net/p/elphel/meta-ezynq meta-ezynq   git clone -b master git://git.code.sf.net/p/elphel/meta-ezynq meta-ezynq -  cd meta-ezynq; git checkout 33d8ebb91d6c2882ad79f7794641d7eb7e2effbe; cd ..+  cd meta-ezynq; git checkout b046b97faaee5cf5f83b554ae0a24d5cce8606c6; cd ..           git clone -b master git://git.code.sf.net/p/elphel/meta-elphel393 meta-elphel393   git clone -b master git://git.code.sf.net/p/elphel/meta-elphel393 meta-elphel393 Oleg

Setup:

← Older revision Revision as of 18:47, 25 April 2014 Line 32: Line 32:           git clone -b dora git://git.yoctoproject.org/poky.git poky   git clone -b dora git://git.yoctoproject.org/poky.git poky -  cd poky; git checkout f1276b066223e7f501f7f711680215ff8edee252+  cd poky; git checkout 50e9ccb2aff7b9f9dca4fda99a6832c60f64de3b           git clone -b dora https://github.com/openembedded/meta-oe.git meta-oe   git clone -b dora https://github.com/openembedded/meta-oe.git meta-oe -  cd meta-oe; git checkout 40e0f371f3eb1628655c484feac0cebf810737b4; cd ..+  cd meta-oe; git checkout ee173678383683e972c7d4d6f0ef5790bfa50274; cd ..           git clone -b dora https://github.com/Xilinx/meta-xilinx.git meta-xilinx   git clone -b dora https://github.com/Xilinx/meta-xilinx.git meta-xilinx Oleg

Setup:

← Older revision Revision as of 23:46, 9 April 2014 (5 intermediate revisions not shown)Line 27: Line 27: ==<font color="blue">Setup</font>== ==<font color="blue">Setup</font>== -* Step 1:+* Step 1: Copy into '''some_script.sh''', modify and run: -<font size='2'>+ - git clone -b dora git://git.yoctoproject.org/poky.git+ - 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-ezynq meta-ezynq+ - git clone -b dora https://github.com/openembedded/meta-oe.git+ - git clone -b dora https://github.com/Xilinx/meta-xilinx.git+ -</font>+ -* Step 2: Init environment+ <font size='2'> <font size='2'>  + '''#Part 1'''  +  + git clone -b dora git://git.yoctoproject.org/poky.git poky  + cd poky; git checkout f1276b066223e7f501f7f711680215ff8edee252  +  + git clone -b dora https://github.com/openembedded/meta-oe.git meta-oe  + cd meta-oe; git checkout 40e0f371f3eb1628655c484feac0cebf810737b4; cd ..  +  + git clone -b dora https://github.com/Xilinx/meta-xilinx.git meta-xilinx  + cd meta-xilinx; git checkout aa7d677515ab7d45bbd3bdd6c5383f4143147c6d; cd ..  +  + git clone -b master git://git.code.sf.net/p/elphel/meta-ezynq meta-ezynq  + cd meta-ezynq; git checkout 33d8ebb91d6c2882ad79f7794641d7eb7e2effbe; cd ..  +  + git clone -b master git://git.code.sf.net/p/elphel/meta-elphel393 meta-elphel393  + cd meta-elphel393; git checkout 777ee20496edebc0f83981e5755d551c46466833; cd ..  +  + '''#Part 2 : init environment and auto-fill Yocto's conf-files'''  +  + CURRENT_PATH=$(dirname $(readlink -f "$0"))  + . ./oe-init-build-env  +  + BBLAYERS_CONF="conf/bblayers.conf"  +  + echo "BBLAYERS = \" \\" >> $BBLAYERS_CONF  + echo "  $CURRENT_PATH/meta \\" >> $BBLAYERS_CONF  + echo "  $CURRENT_PATH/meta-yocto \\" >> $BBLAYERS_CONF  + echo "  $CURRENT_PATH/meta-yocto-bsp \\" >> $BBLAYERS_CONF  + echo "  $CURRENT_PATH/meta-elphel393 \\" >> $BBLAYERS_CONF  + echo "  $CURRENT_PATH/meta-ezynq \\" >> $BBLAYERS_CONF  + echo "  $CURRENT_PATH/meta-oe/meta-oe \\" >> $BBLAYERS_CONF  + echo "  $CURRENT_PATH/meta-oe/meta-webserver \\" >> $BBLAYERS_CONF  + echo "  $CURRENT_PATH/meta-oe/meta-networking \\" >> $BBLAYERS_CONF  + echo "  $CURRENT_PATH/meta-xilinx \\" >> $BBLAYERS_CONF  + echo "  \"" >> $BBLAYERS_CONF  +  + LOCAL_CONF="conf/local.conf"  +  + # number of parallel tasks (including compiles)  + echo "BB_NUMBER_THREADS ?= \"'''8'''\"" >> $LOCAL_CONF  + # number of parallel compiles  + echo "PARALLEL_MAKE ?= \"-j '''8'''\"" >> $LOCAL_CONF  + # <font color='red'>change the MACHINE</font>  + echo "MACHINE ?= \"'''elphel393'''\"" >> $LOCAL_CONF  + # <font color='red'>Elphel's MIRROR website, '''\n''' is important</font>  + echo "MIRRORS =+ \"http://.*/.*    http://mirror.elphel.com/elphel393_mirror/ \n \"" >> $LOCAL_CONF  +  +* Step 2: re-init environment   cd poky   cd poky   . ./oe-init-build-env   . ./oe-init-build-env  +  +* Step 3: build bootable image (3 targets)  + bitbake u-boot-ezynq linux-xlnx core-image-elphel393 </font> </font> -* Step 3: Edit ''build/conf/bblayers.conf'' - add paths to BBLAYERS:  -<font size='2'>  - <absolute-path>/poky/meta-elphel393 \  - <absolute-path>/poky/meta-ezynq \  - <absolute-path>/poky/meta-oe/meta-oe \  - <absolute-path>/poky/meta-oe/meta-webserver \  - <absolute-path>/poky/meta-oe/meta-networking \  - <absolute-path>/poky/meta-xilinx \  -</font>  -* Step 4: Edit ''build/conf/local.conf'' - set MACHINE and other things:  -<font size='2'>  -  BB_NUMBER_THREADS = "8"# (depends on the PC's CPU)  -  PARALLEL_MAKE = "-j 8" # (depends on the PC's CPU)  -  MACHINE ?= "elphel393" # (based on MACHINE="zedboard" )  -</font>  -  ====Notes==== ====Notes==== * Currently having 4 MACHINES: elphel393, microzed, zc706 and zedboard * Currently having 4 MACHINES: elphel393, microzed, zc706 and zedboard Oleg

Setup:

← Older revision Revision as of 02:04, 9 April 2014 (4 intermediate revisions not shown)Line 27: Line 27: ==<font color="blue">Setup</font>== ==<font color="blue">Setup</font>== -* Step 1:+* Step 1: Copy into '''some_script.sh''', modify and run: -<font size='2'>+ - git clone -b dora git://git.yoctoproject.org/poky.git+ - 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-ezynq meta-ezynq+ - git clone -b dora https://github.com/openembedded/meta-oe.git+ - git clone -b dora https://github.com/Xilinx/meta-xilinx.git+ -</font>+ -* Step 2: Init environment+ <font size='2'> <font size='2'>  + '''#Part 1'''  +  + git clone -b dora git://git.yoctoproject.org/poky.git poky  + cd poky; git checkout f1276b066223e7f501f7f711680215ff8edee252  +  + git clone -b dora https://github.com/openembedded/meta-oe.git meta-oe  + cd meta-oe; git checkout 40e0f371f3eb1628655c484feac0cebf810737b4; cd ..  +  + git clone -b dora https://github.com/Xilinx/meta-xilinx.git meta-xilinx  + cd meta-xilinx; git checkout aa7d677515ab7d45bbd3bdd6c5383f4143147c6d; cd ..  +  + git clone -b master git://git.code.sf.net/p/elphel/meta-ezynq meta-ezynq  + cd meta-ezynq; git checkout 33d8ebb91d6c2882ad79f7794641d7eb7e2effbe; cd ..  +  + git clone -b master git://git.code.sf.net/p/elphel/meta-elphel393 meta-elphel393  + cd meta-elphel393; git checkout 9f46f7d66fa5ecbce018d5dc53e2cce51e1fdae2; cd ..  +  + '''#Part 2 : init environment and auto-fill Yocto's conf-files'''  +  + CURRENT_PATH=$(dirname $(readlink -f "$0"))  + . ./oe-init-build-env  +  + BBLAYERS_CONF="conf/bblayers.conf"  +  + echo "BBLAYERS = \" \\" >> $BBLAYERS_CONF  + echo "  $CURRENT_PATH/meta \\" >> $BBLAYERS_CONF  + echo "  $CURRENT_PATH/meta-yocto \\" >> $BBLAYERS_CONF  + echo "  $CURRENT_PATH/meta-yocto-bsp \\" >> $BBLAYERS_CONF  + echo "  $CURRENT_PATH/meta-elphel393 \\" >> $BBLAYERS_CONF  + echo "  $CURRENT_PATH/meta-ezynq \\" >> $BBLAYERS_CONF  + echo "  $CURRENT_PATH/meta-oe/meta-oe \\" >> $BBLAYERS_CONF  + echo "  $CURRENT_PATH/meta-oe/meta-webserver \\" >> $BBLAYERS_CONF  + echo "  $CURRENT_PATH/meta-oe/meta-networking \\" >> $BBLAYERS_CONF  + echo "  $CURRENT_PATH/meta-xilinx \\" >> $BBLAYERS_CONF  + echo "  \"" >> $BBLAYERS_CONF  +  + LOCAL_CONF="conf/local.conf"  +  + # number of parallel tasks (including compiles)  + echo "BB_NUMBER_THREADS ?= \"'''8'''\"" >> $LOCAL_CONF  + # number of parallel compiles  + echo "PARALLEL_MAKE ?= \"-j '''8'''\"" >> $LOCAL_CONF  + # <font color='red'>change the MACHINE</font>  + echo "MACHINE ?= \"'''elphel393'''\"" >> $LOCAL_CONF  + # <font color='red'>Elphel's MIRROR website, '''\n''' is important</font>  + echo "MIRRORS =+ \"http://.*/.*    http://mirror.elphel.com/elphel393_mirror/ \n \"" >> $LOCAL_CONF  +  +* Step 2: re-init environment   cd poky   cd poky   . ./oe-init-build-env   . ./oe-init-build-env  +  +* Step 3: build bootable image (3 targets)  + bitbake u-boot-ezynq linux-xlnx core-image-elphel393 </font> </font> -* Step 3: Edit ''build/conf/bblayers.conf'' - add paths to BBLAYERS:  -<font size='2'>  - <absolute-path>/poky/meta-elphel393 \  - <absolute-path>/poky/meta-ezynq \  - <absolute-path>/poky/meta-oe/meta-oe \  - <absolute-path>/poky/meta-oe/meta-webserver \  - <absolute-path>/poky/meta-oe/meta-networking \  - <absolute-path>/poky/meta-xilinx \  -</font>  -* Step 4: Edit ''build/conf/local.conf'' - set MACHINE and other things:  -<font size='2'>  -  BB_NUMBER_THREADS = "8"# (depends on the PC's CPU)  -  PARALLEL_MAKE = "-j 8" # (depends on the PC's CPU)  -  MACHINE ?= "elphel393" # (based on MACHINE="zedboard" )  -</font>  -  ====Notes==== ====Notes==== * Currently having 4 MACHINES: elphel393, microzed, zc706 and zedboard * Currently having 4 MACHINES: elphel393, microzed, zc706 and zedboard Oleg

← Older revision Revision as of 00:03, 9 April 2014 (3 intermediate revisions not shown)Line 27: Line 27: ==<font color="blue">Setup</font>== ==<font color="blue">Setup</font>== -* Step 1:+* Step 1: Copy into '''some_script.sh''', modify and run: -<font size='2'>+ - git clone -b dora git://git.yoctoproject.org/poky.git+ - 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-ezynq meta-ezynq+ - git clone -b dora https://github.com/openembedded/meta-oe.git+ - git clone -b dora https://github.com/Xilinx/meta-xilinx.git+ -</font>+ -* Step 2: Init environment+ <font size='2'> <font size='2'>  + '''#Part 1'''  +  + git clone -b dora git://git.yoctoproject.org/poky.git poky  + cd poky; git checkout f1276b066223e7f501f7f711680215ff8edee252  +  + git clone -b dora https://github.com/openembedded/meta-oe.git meta-oe  + cd meta-oe; git checkout 40e0f371f3eb1628655c484feac0cebf810737b4; cd ..  +  + git clone -b dora https://github.com/Xilinx/meta-xilinx.git meta-xilinx  + cd meta-xilinx; git checkout aa7d677515ab7d45bbd3bdd6c5383f4143147c6d; cd ..  +  + git clone -b master git://git.code.sf.net/p/elphel/meta-ezynq meta-ezynq  + cd meta-ezynq; git checkout 33d8ebb91d6c2882ad79f7794641d7eb7e2effbe; cd ..  +  + git clone -b master git://git.code.sf.net/p/elphel/meta-elphel393 meta-elphel393  + cd meta-elphel393; git checkout 32a711b4e61a371f1bbccd0d26fd1b14a74387bc; cd ..  +  + '''#Part 2 : init environment and auto-fill Yocto's conf-files'''  +  + CURRENT_PATH=$(dirname $(readlink -f "$0"))  + . ./oe-init-build-env  +  + BBLAYERS_CONF="conf/bblayers.conf"  +  + echo "BBLAYERS = \" \\" >> $BBLAYERS_CONF  + echo "  $CURRENT_PATH/meta \\" >> $BBLAYERS_CONF  + echo "  $CURRENT_PATH/meta-yocto \\" >> $BBLAYERS_CONF  + echo "  $CURRENT_PATH/meta-yocto-bsp \\" >> $BBLAYERS_CONF  + echo "  $CURRENT_PATH/meta-elphel393 \\" >> $BBLAYERS_CONF  + echo "  $CURRENT_PATH/meta-ezynq \\" >> $BBLAYERS_CONF  + echo "  $CURRENT_PATH/meta-oe/meta-oe \\" >> $BBLAYERS_CONF  + echo "  $CURRENT_PATH/meta-oe/meta-webserver \\" >> $BBLAYERS_CONF  + echo "  $CURRENT_PATH/meta-oe/meta-networking \\" >> $BBLAYERS_CONF  + echo "  $CURRENT_PATH/meta-xilinx \\" >> $BBLAYERS_CONF  + echo "  \"" >> $BBLAYERS_CONF  +  + LOCAL_CONF="conf/local.conf"  +  + # number of parallel tasks (including compiles)  + echo "BB_NUMBER_THREADS ?= \"'''8'''\"" >> $LOCAL_CONF  + # number of parallel compiles  + echo "PARALLEL_MAKE ?= \"-j '''8'''\"" >> $LOCAL_CONF  + # <font color='red'>change the MACHINE</font>  + echo "MACHINE ?= \"'''elphel393'''\"" >> $LOCAL_CONF  + # <font color='red'>Elphel's MIRROR website, '''\n''' is important</font>  + echo "MIRRORS =+ \"http://.*/.*    http://mirror.elphel.com/elphel393_mirror/ \n \"" >> $LOCAL_CONF  +  +* Step 2: re-init environment   cd poky   cd poky   . ./oe-init-build-env   . ./oe-init-build-env  +  +* Step 3: build bootable image (3 targets)  + bitbake u-boot-ezynq linux-xlnx core-image-elphel393 </font> </font> -* Step 3: Edit ''build/conf/bblayers.conf'' - add paths to BBLAYERS:  -<font size='2'>  - <absolute-path>/poky/meta-elphel393 \  - <absolute-path>/poky/meta-ezynq \  - <absolute-path>/poky/meta-oe/meta-oe \  - <absolute-path>/poky/meta-oe/meta-webserver \  - <absolute-path>/poky/meta-oe/meta-networking \  - <absolute-path>/poky/meta-xilinx \  -</font>  -* Step 4: Edit ''build/conf/local.conf'' - set MACHINE and other things:  -<font size='2'>  -  BB_NUMBER_THREADS = "8"# (depends on the PC's CPU)  -  PARALLEL_MAKE = "-j 8" # (depends on the PC's CPU)  -  MACHINE ?= "elphel393" # (based on MACHINE="zedboard" )  -</font>  -  ====Notes==== ====Notes==== * Currently having 4 MACHINES: elphel393, microzed, zc706 and zedboard * Currently having 4 MACHINES: elphel393, microzed, zc706 and zedboard Oleg

University of Geneva

Monday, April 14, 2014 – 18:15 at Uni-Mail, room MR070, University of Geneva.

Elphel, Inc. is giving a conference entitled “High Performance Open Hardware for Scientific Applications”. Following the conference, you will be invited to attend a round-table discussion to debate the subject with people from Elphel and Javier Serrano from CERN.

Javier studied Physics and Electronics Engineering. He is the head of the Hardware and Timing section in CERN’s Beams Control group, and the founder of the Open Hardware Repository. Javier has co-authored the CERN Open Hardware Licence. He and his colleagues have also recently started contributing improvements to KiCad, a free software tool for the design of Printed Circuit Boards

Elphel Inc. is invited by their partner specialized in stereophotogrammetry applications – the Swiss company Foxel SA, from April 14-21 in Geneva, Switzerland.

You can enjoy a virtual tour of the Geneva University by clicking on the links herein below:
(make sure to use the latest version of Firefox or Chromium to view the demos)

• Uni-mail outside view
• Uni-mail inside view

Foxel’s team would be delighted to have all of Elphel’s clients and followers to participate in the conference.
A chat can also be organized in the next few days. Please contact us at Foxel SA.

If you do not have the opportunity to visit us in Geneva, the conference will be streamed live and the recording will be available.

Build bootloader:

← Older revision Revision as of 20:47, 24 March 2014 (One intermediate revision not shown)Line 20: Line 20: These names are as they appear in the u-boot configuration header file - actual output files have different names: 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+* '''boot.bin'''+('''u-boot.img''') - u-boot as the first stage bootloader = Secondary Program Loader tha boots '''u-boot.img''' * '''devicetree.dtb''' - device tree with described interfaces, zynq registers, interrupts and drivers * '''devicetree.dtb''' - device tree with described interfaces, zynq registers, interrupts and drivers * '''uImage''' - kernel, drivers * '''uImage''' - kernel, drivers * '''uramdisk.image.gz''' - applications * '''uramdisk.image.gz''' - applications Copy them on the micro SD card > run '''boot''' once in the u-boot command line. Copy them on the micro SD card > run '''boot''' once in the u-boot command line. -  -  ==<font color="blue">Setup</font>== ==<font color="blue">Setup</font>== Line 72: Line 70: ====Output==== ====Output==== * poky/build/tmp/deploy/images/'''boot.bin''' * poky/build/tmp/deploy/images/'''boot.bin'''  +* poky/build/tmp/deploy/images/'''u-boot.img''' ====Notes==== ====Notes==== Oleg

← Older revision Revision as of 22:36, 10 March 2014 (14 intermediate revisions not shown)Line 1: Line 1: ==Decription== ==Decription== [https://sourceforge.net/p/elphel/ezynq Ezynq] project is started to create a bootloader for systems based on the Xilinx Zynq SoC without the inconvenience of the non-free tools and/or files. The goal is not just to "free" the code, but to provide users with the higher degree of flexibility in fine-tuning of the configuration parameters. [https://sourceforge.net/p/elphel/ezynq Ezynq] project is started to create a bootloader for systems based on the Xilinx Zynq SoC without the inconvenience of the non-free tools and/or files. The goal is not just to "free" the code, but to provide users with the higher degree of flexibility in fine-tuning of the configuration parameters.  +  +====="Free" the code part=====  +Ezynq addresses the potential legal problems with distribution of a product/software based on Zynq platform:  +* FSBL is under Xilinx's copyright  +* The current (2014/02/23) official SPL implementation in the [https://github.com/Xilinx/u-boot-xlnx/tree/master-next u-boot-xlnx master-next 54fee227ef141214141a226efd17ae0516deaf32] branch is FSBL-less but it requires to use the files (<b>ps7_init.c/h</b>) that come under Xilinx's copyright which makes u-boot noncompliant with its GPL license.  + ==Supported boards== ==Supported boards== -* [http://microzed.org Avnet MicroZed] - Zynq 7Z010+{| class="wikitable" -* [http://www.xilinx.com/products/boards-and-kits/EK-Z7-ZC706-G.htm Xilinx ZC706] - Zynq 7Z045+|- -* [http://www.zedboard.org/ Digilent/Avnet ZedBoard] - Zynq 7Z020 (not tested)+! Board !! Chip !! Manufacturer !! Tested? -* [http://blog.elphel.com/2013/11/nc393-development-progress-testing-the-hardware/ Elphel 10393] - Zynq 7Z030+|-  +| style="padding:0px 15px 0px 15px;" | [http://microzed.org MicroZed]  +| style="padding:0px 15px 0px 15px;" | Zynq 7Z010    +| style="padding:0px 15px 0px 15px;" | Avnet  +| style="padding:0px 15px 0px 15px;" | <font color='green'>Y</font>  +|-  +| style="padding:0px 15px 0px 15px;" | [http://www.xilinx.com/products/boards-and-kits/EK-Z7-ZC706-G.htm ZC706]  +| style="padding:0px 15px 0px 15px;" | Zynq 7Z045    +| style="padding:0px 15px 0px 15px;" | Xilinx  +| style="padding:0px 15px 0px 15px;" | <font color='green'>Y</font>  +|-  +| style="padding:0px 15px 0px 15px;" | [http://www.zedboard.org/ ZedBoard]  +| style="padding:0px 15px 0px 15px;" | Zynq 7Z020    +| style="padding:0px 15px 0px 15px;" | Digilent/Avnet  +| style="padding:0px 15px 0px 15px;" | <font color='orange'>N</font>  +|-  +| style="padding:0px 15px 0px 15px;" | [http://blog.elphel.com/2013/11/nc393-development-progress-testing-the-hardware/ 10393]  +| style="padding:0px 15px 0px 15px;" | Zynq 7Z030    +| style="padding:0px 15px 0px 15px;" | Elphel  +| style="padding:0px 15px 0px 15px;" | <font color='green'>Y</font>  +|}  +  ==Output== ==Output== -* '''boot.bin''' (fsbl is not required to boot)+* '''boot.bin''' (SPL) - loads u-boot.img, no FSBL needed.  +* '''u-boot.img''' (u-boot image)  +   +Boot: Copy them to SD card in order to boot from it.  +  ==Install meta-toolchain (Kubuntu 13.04)== ==Install meta-toolchain (Kubuntu 13.04)== -*+* Build: <font size='2'> <font size='2'>   sudo apt-get install texinfo chrpath   sudo apt-get install texinfo chrpath Line 23: Line 54: * Run installation script in ''build/tmp/deploy/'' * Run installation script in ''build/tmp/deploy/'' -==Install ezynq (Kubuntu 13.04)==+   +==Install Ezynq (Kubuntu 13.04)== <font size='2'> <font size='2'>   git clone git://git.code.sf.net/p/elphel/ezynq ezynq   git clone git://git.code.sf.net/p/elphel/ezynq ezynq Line 30: Line 62: </font> </font> -==Generate boot.bin==+   +==Build== * Edit ''initenv'' according to the built meta-toolchain * Edit ''initenv'' according to the built meta-toolchain -*+* Build: <font size='2'> <font size='2'>   cd u-boot-xlnx   cd u-boot-xlnx Line 44: Line 77: * The generated files are: * The generated files are: -** '''boot.bin''' - the bootloader image+** '''boot_head.bin''' - contains values for RBL register initialization  +** '''boot.bin''' - the SPL image  +** '''u-boot.img''' - the u-boot image ** '''u-boot.html''' - configuration settings overview ** '''u-boot.html''' - configuration settings overview ** '''u-boot.map''' - the bootloader's memory map ** '''u-boot.map''' - the bootloader's memory map ** '''u-boot''' - ELF file ** '''u-boot''' - ELF file -==Develop (add boards support)==+   +==Develop (add support for new boards)== * Add a new board record to the list in the ''boards.cfg'' (or leave as is if the item already exists). * Add a new board record to the list in the ''boards.cfg'' (or leave as is if the item already exists). * Create a configuration file for the new board - use ''include/configs/zynq_microzed.h'' as a reference * Create a configuration file for the new board - use ''include/configs/zynq_microzed.h'' as a reference Line 56: Line 92:   include/configs/ezynq/ezynq_XC7Z010_1CLG400.h   include/configs/ezynq/ezynq_XC7Z010_1CLG400.h   include/configs/ezynq/zed_ezynq.h   include/configs/ezynq/zed_ezynq.h -*+* Build: -  <font size='2'>./makeuboot</font>+  <font size='2'>./makeuboot <new_board>_config</font> -<font color='red'>'''IMPORTANT:''' Only '''192KB''' of zynq's series on-chip memory are available at boot. It is the maximal size of '''u-boot.bin''' (not the final '''boot.bin''') - the python script will throw just a warning.</font>  ==Known issues== ==Known issues== Oleg

Generate boot.bin:

← Older revision Revision as of 21:46, 10 March 2014 (6 intermediate revisions not shown)Line 3: Line 3: ==Supported boards== ==Supported boards== -* [http://microzed.org Avnet MicroZed] - Zynq 7Z010+{| class="wikitable" -* [http://www.xilinx.com/products/boards-and-kits/EK-Z7-ZC706-G.htm Xilinx ZC706] - Zynq 7Z045+|- -* [http://www.zedboard.org/ Digilent/Avnet ZedBoard] - Zynq 7Z020 (not tested)+! Board !! Chip !! Manufacturer -* [http://blog.elphel.com/2013/11/nc393-development-progress-testing-the-hardware/ Elphel 10393] - Zynq 7Z030+|-  +| style="padding:0px 15px 0px 15px;" | [http://microzed.org MicroZed]  +| style="padding:0px 15px 0px 15px;" | Zynq 7Z010    +| style="padding:0px 15px 0px 15px;" | Avnet  +|-  +| style="padding:0px 15px 0px 15px;" | [http://www.xilinx.com/products/boards-and-kits/EK-Z7-ZC706-G.htm ZC706]  +| style="padding:0px 15px 0px 15px;" | Zynq 7Z045    +| style="padding:0px 15px 0px 15px;" | Xilinx  +|-  +| style="padding:0px 15px 0px 15px;" | [http://www.zedboard.org/ ZedBoard]  +| style="padding:0px 15px 0px 15px;" | Zynq 7Z020    +| style="padding:0px 15px 0px 15px;" | Digilent/Avnet  +|-  +| style="padding:0px 15px 0px 15px;" | [http://blog.elphel.com/2013/11/nc393-development-progress-testing-the-hardware/ 10393]  +| style="padding:0px 15px 0px 15px;" | Zynq 7Z030    +| style="padding:0px 15px 0px 15px;" | Elphel  +|} ==Output== ==Output== -* '''boot.bin''' (fsbl is not required to boot)+* '''boot.bin''' (SPL) - loads u-boot.img, no FSBL needed.  +* '''u-boot.img''' (u-boot image) ==Install meta-toolchain (Kubuntu 13.04)== ==Install meta-toolchain (Kubuntu 13.04)== Line 30: Line 47: </font> </font> -==Generate boot.bin==+==Build== * Edit ''initenv'' according to the built meta-toolchain * Edit ''initenv'' according to the built meta-toolchain * * Line 44: Line 61: * The generated files are: * The generated files are: -** '''boot.bin''' - the bootloader image+** '''boot_head.bin'''  +** '''boot.bin''' - the SPL image  +** '''u-boot.img''' - u-boot image (if '''boot.bin''' built with SPL support) ** '''u-boot.html''' - configuration settings overview ** '''u-boot.html''' - configuration settings overview ** '''u-boot.map''' - the bootloader's memory map ** '''u-boot.map''' - the bootloader's memory map ** '''u-boot''' - ELF file ** '''u-boot''' - ELF file  +  +==Boot==  +* Copy '''boot.bin''' & '''u-boot.img''' (if generated) to SD card. Boot from it. ==Develop (add boards support)== ==Develop (add boards support)== Oleg

Supported boards:

← Older revision Revision as of 20:25, 10 March 2014 (4 intermediate revisions not shown)Line 3: Line 3: ==Supported boards== ==Supported boards== -* [http://microzed.org Avnet MicroZed] - Zynq 7Z010+{| class="wikitable" -* [http://www.xilinx.com/products/boards-and-kits/EK-Z7-ZC706-G.htm Xilinx ZC706] - Zynq 7Z045+|- -* [http://www.zedboard.org/ Digilent/Avnet ZedBoard] - Zynq 7Z020 (not tested)+! Board !! Chip !! Manufacturer -* [http://blog.elphel.com/2013/11/nc393-development-progress-testing-the-hardware/ Elphel 10393] - Zynq 7Z030+|-  +| style="padding:0px 15px 0px 15px;" | [http://microzed.org MicroZed]  +| style="padding:0px 15px 0px 15px;" | Zynq 7Z010    +| style="padding:0px 15px 0px 15px;" | Avnet  +|-  +| style="padding:0px 15px 0px 15px;" | [http://www.xilinx.com/products/boards-and-kits/EK-Z7-ZC706-G.htm ZC706]  +| style="padding:0px 15px 0px 15px;" | Zynq 7Z045    +| style="padding:0px 15px 0px 15px;" | Xilinx  +|-  +| style="padding:0px 15px 0px 15px;" | [http://www.zedboard.org/ ZedBoard]  +| style="padding:0px 15px 0px 15px;" | Zynq 7Z020    +| style="padding:0px 15px 0px 15px;" | Digilent/Avnet  +|-  +| style="padding:0px 15px 0px 15px;" | [http://blog.elphel.com/2013/11/nc393-development-progress-testing-the-hardware/ 10393]  +| style="padding:0px 15px 0px 15px;" | Zynq 7Z030    +| style="padding:0px 15px 0px 15px;" | Elphel  +|} ==Output== ==Output== -* '''boot.bin''' (fsbl is not required to boot)+* '''boot.bin''' (fsbl is not required to boot, this boots u-boot.img (SPL))  +* '''u-boot.img''' (u-boot) ==Install meta-toolchain (Kubuntu 13.04)== ==Install meta-toolchain (Kubuntu 13.04)== Line 45: Line 62: * The generated files are: * The generated files are: ** '''boot.bin''' - the bootloader image ** '''boot.bin''' - the bootloader image  +** '''u-boot.img''' - u-boot image (if '''boot.bin''' built with SPL support) ** '''u-boot.html''' - configuration settings overview ** '''u-boot.html''' - configuration settings overview ** '''u-boot.map''' - the bootloader's memory map ** '''u-boot.map''' - the bootloader's memory map ** '''u-boot''' - ELF file ** '''u-boot''' - ELF file  +  +==Boot==  +* Copy '''boot.bin''' & '''u-boot.img''' (if generated) to SD card. Boot from it. ==Develop (add boards support)== ==Develop (add boards support)== Oleg

Boot:

← Older revision Revision as of 03:40, 7 March 2014 (3 intermediate revisions not shown)Line 9: Line 9: ==Output== ==Output== -* '''boot.bin''' (fsbl is not required to boot)+* '''boot.bin''' (fsbl is not required to boot, this boots u-boot.img (SPL))  +* '''u-boot.img''' (u-boot) ==Install meta-toolchain (Kubuntu 13.04)== ==Install meta-toolchain (Kubuntu 13.04)== Line 45: Line 46: * The generated files are: * The generated files are: ** '''boot.bin''' - the bootloader image ** '''boot.bin''' - the bootloader image  +** '''u-boot.img''' - u-boot image (if '''boot.bin''' built with SPL support) ** '''u-boot.html''' - configuration settings overview ** '''u-boot.html''' - configuration settings overview ** '''u-boot.map''' - the bootloader's memory map ** '''u-boot.map''' - the bootloader's memory map ** '''u-boot''' - ELF file ** '''u-boot''' - ELF file  +  +==Boot==  +* Copy '''boot.bin''' & '''u-boot.img''' (if generated) to SD card. Boot from it. ==Develop (add boards support)== ==Develop (add boards support)== Oleg

ImageJ and Elphel plugins for imageJ:

← Older revision Revision as of 20:27, 1 February 2014 Line 283: Line 283: You may download ImageJ bundled with Java from the [http://rsbweb.nih.gov/ij/download.html download page]: You may download ImageJ bundled with Java from the [http://rsbweb.nih.gov/ij/download.html download page]: ==== With 32-bit Java ====   ==== With 32-bit Java ====   -cd ~/Download; wget "http://rsbweb.nih.gov/ij/download/linux/ij146-x86.tar.gz" ; tar zxvf ij146-x86.tar.gz+cd ~/Download; wget "http://rsbweb.nih.gov/ij/download/linux/ij147-linux32.zip" ; unzip ij147-linux32.zip ==== With 64-bit Java ==== ==== With 64-bit Java ==== -cd ~/Download; wget "http://rsbweb.nih.gov/ij/download/linux/ij146-linux64.tar.gz" ; tar zxvf ij146-linux64.tar.gz+cd ~/Download; wget "http://rsbweb.nih.gov/ij/download/linux/ij147-linux64.zip" ; unzip ij147-linux64.zip '''If any of the two direct download links above are broken, please use the [http://rsbweb.nih.gov/ij/download.html] to get the new ImageJ version''' '''If any of the two direct download links above are broken, please use the [http://rsbweb.nih.gov/ij/download.html] to get the new ImageJ version''' Polto

Setup:

← Older revision Revision as of 02:36, 31 December 2013 Line 54: Line 54: * Step 4: Edit ''build/conf/local.conf'' - set MACHINE and other things: * Step 4: Edit ''build/conf/local.conf'' - set MACHINE and other things: <font size='2'> <font size='2'> -   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 ?= "elphel393" (based on MACHINE="zedboard" )+   MACHINE ?= "elphel393" # (based on MACHINE="zedboard" ) </font> </font> Andrey.filippov

dzhimiev committed changes to the Elphel project elphel353-8.0 CVS:
MDI/MDIx setting mode fixes

• Modified net_mii rev1.2 - added one line, removed one line
• Modified net4.sh rev1.2 - added 16 lines, removed 8 lines

Where to Get?:

← Older revision Revision as of 01:49, 27 December 2013 Line 10: Line 10: == Where to Get? == == Where to Get? == The first more or less functional version is available at  SoureForge: The first more or less functional version is available at  SoureForge: -[https://sourceforge.net/project/showfiles.php?group_id=105686&package_id=184538 Eclipse/ExDT/VDT sources, work files and documentation]+[http://sourceforge.net/p/excelsior-vdt/wiki/Home/ Eclipse/ExDT/VDT sources, work files and documentation] == Invitation for Discussion == == Invitation for Discussion == You are welcome to try the product and to discuss all issues of its concepts, current state and usage techniques with its developers! You are welcome to try the product and to discuss all issues of its concepts, current state and usage techniques with its developers! Do it right here, in discussion section! Do it right here, in discussion section! Andrey.filippov

The software used in the previous Elphel cameras was based on the GNU/Linux distribution supported By Axis Communications for their ETRAX processors. Of course it was heavily modified, we developed new code and ported many applications to run in the camera. Over the years we worked on making it easier to install, use and update, provided customized Live GNU/Linux distributions so those with zero experience with this operating system can still use the camera development software. Originally we used Knoppix-based CD, then DVD, then switched to Kubuntu when it became available and stable. And DVDs were eventually replaced by the USB flash drives.

Knoppix and Kubuntu are for the host computer, the cameras themselves used the same non-standard, mostly home-brewed distribution, that became more and more difficult to maintain especially when Axis abandoned their processors. So even during the first attempt to move to a new platform we really hoped to be able to use modern distribution for the embedded systems. And get rid of the nightmare of porting ourselves such applications as PHP and then doing mostly the same all over again when the new revisions became available. To be able to use the latest Linux kernel and not to spend time modifying the IDE driver myself to provide support for the large block hard drives when most manufacturers abandoned 512 byte ones – 2.6.19 kernel does not have it and there is not easy to use the later drivers.

Oleg is now working on adapting the OpenEmbedded distribution and the work flow for the new camera distribution, and while embracing the power of “bitbaking” we are trying to preserve the features we implemented in the NC353 camera software. And while the OpenEmbedded-based Yocto Project is for embedded system developers, we need the software for Elphel camera users – software that can be easily installed by a single script (at least on a particular GNU/Linux distribution) or come pre-installed on a flash media. It should work “out of the box” for the users with no prior GNU/Linux experience – most of the camera users have different OS on their computers. We would also like to keep what we believe has an important practical use – a feature behind our /*source is inside*/ logo on the cameras. Each camera keeps the source code of the modifications archived in the internal flash file system, so running the downloaded from the camera script by the user results in virtually identical binary image, even if some software in the camera was custom-modified from the official (supported through Elphel git repositories) distribution.

There is still a lot left in the OE that we do not fully understand, but we are trying to do it right from the very beginning, understanding how important it is from our experience of making some major re-organizing code for the previous products. And Oleg is doing a good progress, there is a wiki page and Git repositories: meta-elphel393, meta-ezynq that document our work on this.

I did not succumb to a temptation to start working on the FPGA code immediately – there are some new ideas we want to try as well as some left for a future major “revolution” when updating the existing cameras FPGA code for the new sensors and applications. Anyway – we are not under pressure to demonstrate images from the new camera and we are confident that this job will be done in the expected time and will have the NC393 operational by the second half of the 2014. And the time is working for us – there are many people working now with Xilinx Zynq, and the active development weeds out bugs at a high rate. Failing to upgrade to the latest version already took a whole week of development time – the bug in the Xilinx Ethernet driver turned out to be already fixed.

While Oleg was immersing himself into the OpenEmbedded I was looking into the kernel driver development, what changed since the 2.6.19 era I dealt with when working on the previous camera software. There turned out to be quite a few changes and I decided to learn the new features working on a simpler drivers that we needed for the new boards. First of all I was pleased to find out that of the 7 of the I²C chips used on the 10393+10389 boards 3 were supported by the available kernel drivers – had just to specify them in the Device Tree and the supercap-powered real time clock was immediately recognized by the system – so did the temperature sensor/EEPOM and GPIO ports. Of the remaining ones with no available drivers the most challenging turned out to be SI5338 (clock generator) and I tried to add support for this device, using sysfs to control it, Device Tree (DT) to initialize it, and dynamic debug to facilitate development – none of these interfaces were used in the previous cameras.

The SI5338 had all the needed documentation available on the manufacturer’s web site, ready for download. But the device itself turned out not to be to so easy to control, and the recommended procedure included generation of the register map with the ClockBuilder software (for MS Windows), then loading the data to the device registers and initializing it with rather simple code, for which Silicon Labs provides the source. That did not seem very convenient so I tried to implement the driver that can be controlled at run time directly, calculating the particular register values from the high-level data on the fly. Most features are now supported in the si5338.c driver, it is also possible to load the register data generated by the ClockBuilder software (it is possible to run it with Wine) after converting the file with the Python script. It took me more time than I expected to develop this driver to the usable state, but I hope this work will be useful for others too. SI5338 is an excellent device that deserves better support in the Linux kernel. And having the driver working – it eliminates the last remaining obstacle to start working on the FPGA code. Or one of the last remaining – there are still a few minor ones left.