Development for 10393
Development for 10393
Created page with "===Setup environment=== ===Flash vs micro SD=== * micro SD cards work best for development ** replaceable ** changes get written to the card, no extra sync required * flash..."
New page
===Setup environment======Flash vs micro SD===
* micro SD cards work best for development
** replaceable
** changes get written to the card, no extra sync required
* flash works best for a production system:
** non-replaceable
** limited write cycles
** because of overlayfs changes need an extra sync (overlay_sync) and a proper reboot to get written to the flash.
===Kernel===
===Applications===
===Projects structure===
[[Category:393]] Oleg
Poky 2.0 manual
Compile devicetree
← Older revision Revision as of 20:01, 28 March 2017 (7 intermediate revisions by the same user not shown)Line 60: Line 60: * '''rootfs.ubifs''', '''rootfs.ubi''', '''rootfs.tar.gz''' - rootfs in different formats * '''rootfs.ubifs''', '''rootfs.ubi''', '''rootfs.tar.gz''' - rootfs in different formats −They are found poky's deploy directory '''elphel393/poky/build/tmp/deploy/images/elphel393/''', linked to+They are found at '''elphel393/bootable-images/''', which is a link (for convenience) to poky's deploy directory '''elphel393/poky/build/tmp/deploy/images/elphel393/''' −'''elphel393/bootable-images/''' for convenience. * complete set of files for rootfs in NAND Flash: ''elphel393/bootable-images/nand/'' * complete set of files for rootfs in NAND Flash: ''elphel393/bootable-images/nand/'' Line 81: Line 80: ==<font color="blue">Setup</font>== ==<font color="blue">Setup</font>== −* <font size='2'> <font size='2'> git clone https://git.elphel.com/Elphel/elphel393.git git clone https://git.elphel.com/Elphel/elphel393.git Line 91: Line 89: </font> </font> −==<font color="blue">Compare '''built''' vs '''running on target system''' software</font>==+'''Notes:''' −*+* The last line builds all targets. + +==<font color="blue">Compare '''built''' vs '''deployed''' software versions</font>== <font size='2'> <font size='2'> cd elphel393 cd elphel393 Line 98: Line 98: </font> </font> −==<font color="blue">Build bootloader</font>==+'''Notes:''' +* '''deployed''' = running on the target system + +==<font color="blue">Build</font>== + +===<font color="blue">All targets</font>=== + bitbake u-boot device-tree linux-xlnx core-image-elphel393 + +===<font color="blue">Bootloader</font>=== <font size='2'> <font size='2'> − bitbake u-boot-ezynq − or bitbake u-boot bitbake u-boot − or − bitbake virtual/bootloader </font> </font> ====Output==== ====Output==== Line 111: Line 115: ====Notes==== ====Notes==== −* Since Poky 1.5.1 switched from u-boot-xlnx to u-boot - some of the u-boot-xlnx reached the upstream+* Since Poky 1.5.1: switched from u-boot-xlnx to u-boot - some of the u-boot-xlnx reached the upstream −* Since Poky 1.5.1 u-boot introduced Kconfig and currently (as of 2016/01/22) is still migrating from autoconf - keeping both build methods working together.+* Since Poky 1.5.1: u-boot introduced Kconfig and currently (as of 2016/01/22) is still migrating from autoconf - keeping both build methods working together. * Current u-boot uses the board's device tree blob to make a stripped version for itself - uncompiled device tree files are present in the u-boot sources * Current u-boot uses the board's device tree blob to make a stripped version for itself - uncompiled device tree files are present in the u-boot sources −==<font color="blue">Compile devicetree</font>==+===<font color="blue">Device tree</font>=== <font size='2'> <font size='2'> bitbake device-tree bitbake device-tree Line 122: Line 126: * '''devicetree.dtb''' * '''devicetree.dtb''' −==<font color="blue">Build kernel</font>==+===<font color="blue">Kernel</font>=== <font size='2'> <font size='2'> bitbake linux-xlnx bitbake linux-xlnx − or − bitbake virtual/kernel </font> </font> ====Output==== ====Output==== Line 136: Line 138: * Uncompiled device tree files are present in the linux sources provided by linux-xlnx * Uncompiled device tree files are present in the linux sources provided by linux-xlnx −==<font color="blue">Build ramdisk.image.gz</font>==+===<font color="blue">Rootfs</font>=== <font size='2'> <font size='2'> bitbake core-image-elphel393 bitbake core-image-elphel393 </font> </font> ====Output==== ====Output==== −* '''uramdisk.image.gz''' (the file has *.u-boot extension after it's built)+* '''rootfs.tar.gz''' −* '''rootfs.ubi'''+* '''rootfs.ubi''','''rootfs.ubifs''' −* '''rootfs.ubifs''' ==<font color="blue">Notes</font>== ==<font color="blue">Notes</font>== OlegPoky 2.0 manual
Build kernel
← Older revision Revision as of 19:40, 28 March 2017 (4 intermediate revisions by the same user not shown)Line 81: Line 81: ==<font color="blue">Setup</font>== ==<font color="blue">Setup</font>== −* <font size='2'> <font size='2'> git clone https://git.elphel.com/Elphel/elphel393.git git clone https://git.elphel.com/Elphel/elphel393.git Line 92: Line 91: ==<font color="blue">Compare '''built''' vs '''running on target system''' software</font>== ==<font color="blue">Compare '''built''' vs '''running on target system''' software</font>== −* <font size='2'> <font size='2'> cd elphel393 cd elphel393 Line 100: Line 98: ==<font color="blue">Build bootloader</font>== ==<font color="blue">Build bootloader</font>== <font size='2'> <font size='2'> − bitbake u-boot-ezynq − or bitbake u-boot bitbake u-boot − or − bitbake virtual/bootloader </font> </font> ====Output==== ====Output==== Line 111: Line 105: ====Notes==== ====Notes==== −* Since Poky 1.5.1 switched from u-boot-xlnx to u-boot - some of the u-boot-xlnx reached the upstream+* Since Poky 1.5.1: switched from u-boot-xlnx to u-boot - some of the u-boot-xlnx reached the upstream −* Since Poky 1.5.1 u-boot introduced Kconfig and currently (as of 2016/01/22) is still migrating from autoconf - keeping both build methods working together.+* Since Poky 1.5.1: u-boot introduced Kconfig and currently (as of 2016/01/22) is still migrating from autoconf - keeping both build methods working together. * Current u-boot uses the board's device tree blob to make a stripped version for itself - uncompiled device tree files are present in the u-boot sources * Current u-boot uses the board's device tree blob to make a stripped version for itself - uncompiled device tree files are present in the u-boot sources Line 125: Line 119: <font size='2'> <font size='2'> bitbake linux-xlnx bitbake linux-xlnx − or − bitbake virtual/kernel </font> </font> ====Output==== ====Output==== OlegEyesis4Pi 393 User Guide - Recording
Stop
← Older revision Revision as of 01:59, 28 March 2017 (5 intermediate revisions by the same user not shown)Line 42: Line 42: Important Notice: Use a fan to cool the camera's pole when shooting indoors. Important Notice: Use a fan to cool the camera's pole when shooting indoors. </b> </b> +{| +|[[File:Eyesis4pi393 gui access.png|thumb|500px|GUI access]] +|} + <br/><br/> <br/><br/> Line 187: Line 191: <br> <br> + +== Troubleshooting == + <!-- <!-- == Downloading IMU/GPS Log == == Downloading IMU/GPS Log == Line 205: Line 212: '''''Note:''' Missing files most likely means that the FPS is too high''. '''''Note:''' Missing files most likely means that the FPS is too high''. --> --> + == Links == == Links == OlegEyesis4Pi 393 User Guide - Recording
Power On
← Older revision Revision as of 01:06, 28 March 2017 (2 intermediate revisions by the same user not shown)Line 6: Line 6: git clone https://git.elphel.com/Elphel/eyesis4pi-393-gui.git git clone https://git.elphel.com/Elphel/eyesis4pi-393-gui.git git pull (repeat any time to get the latest) git pull (repeat any time to get the latest) −GitHub.com:+https://git.elphel.com: − https://github.com/Elphel/eyesis4pi-393-gui+ https://git.elphel.com/Elphel/eyesis4pi-393-gui/tree/master Follow the instructions in INSTALL.txt: Follow the instructions in INSTALL.txt: Line 33: Line 33: == Power On == == Power On == −* Connect the camera's ethernet cables to the switch.+* Connect all cables - power, network, eSATA. −* Power on: switch, SSD enclosure, Eyesis4Pi. Boot takes about 1 min.+* Power on: switch, SSD enclosure, Eyesis4Pi393. Boot takes about 1 min. −* Setup PC IP+* Setup PC IP (can be done beforehand). −* Refresh GUI after camera boots.+* Refresh GUI after camera boots + Note 1: If GUI is refreshed before subcamera has mounted SSD it will not display SSD free space. Refresh in a few moments or until SSD gets mounted. <b> <b> Line 56: Line 57: <font size="2"></font> '''''Note:''' Eyesis4Pi 393 default IP addresses: 192.168.0.161-163'' <br><br> <font size="2"></font> '''''Note:''' Eyesis4Pi 393 default IP addresses: 192.168.0.161-163'' <br><br> + +== Tests == + +... <!-- <!-- Line 134: Line 139: <br><br> <br><br> --> --> + == Setting recording parameters: camera settings == == Setting recording parameters: camera settings == OlegEyesis4Pi 393 User Guide - Recording
Power On
← Older revision Revision as of 01:06, 28 March 2017 (4 intermediate revisions by the same user not shown)Line 6: Line 6: git clone https://git.elphel.com/Elphel/eyesis4pi-393-gui.git git clone https://git.elphel.com/Elphel/eyesis4pi-393-gui.git git pull (repeat any time to get the latest) git pull (repeat any time to get the latest) −GitHub.com:+https://git.elphel.com: − https://github.com/Elphel/eyesis4pi-393-gui+ https://git.elphel.com/Elphel/eyesis4pi-393-gui/tree/master Follow the instructions in INSTALL.txt: Follow the instructions in INSTALL.txt: Line 33: Line 33: == Power On == == Power On == −* Connect the camera's ethernet cables to the switch.+* Connect all cables - power, network, eSATA. −* Power on: switch, SSD enclosure, Eyesis4Pi. Boot takes about 1 min.+* Power on: switch, SSD enclosure, Eyesis4Pi393. Boot takes about 1 min. +* Setup PC IP (can be done beforehand). +* Refresh GUI after camera boots + Note 1: If GUI is refreshed before subcamera has mounted SSD it will not display SSD free space. Refresh in a few moments or until SSD gets mounted. + <b> <b> Important Notice: Use a fan to cool the camera's pole when shooting indoors. Important Notice: Use a fan to cool the camera's pole when shooting indoors. Line 53: Line 57: <font size="2"></font> '''''Note:''' Eyesis4Pi 393 default IP addresses: 192.168.0.161-163'' <br><br> <font size="2"></font> '''''Note:''' Eyesis4Pi 393 default IP addresses: 192.168.0.161-163'' <br><br> + +== Tests == + +... <!-- <!-- Line 131: Line 139: <br><br> <br><br> --> --> + == Setting recording parameters: camera settings == == Setting recording parameters: camera settings == OlegEyesis4Pi 393 User Guide - Recording
Power On
← Older revision Revision as of 01:06, 28 March 2017 (5 intermediate revisions by the same user not shown)Line 4: Line 4: Terminal: Terminal: cd <any-path> cd <any-path> − git clone https://github.com/Elphel/eyesis4pi-393-gui.git+ git clone https://git.elphel.com/Elphel/eyesis4pi-393-gui.git git pull (repeat any time to get the latest) git pull (repeat any time to get the latest) −GitHub.com:+https://git.elphel.com: − https://github.com/Elphel/eyesis4pi-393-gui+ https://git.elphel.com/Elphel/eyesis4pi-393-gui/tree/master Follow the instructions in INSTALL.txt: Follow the instructions in INSTALL.txt: Line 33: Line 33: == Power On == == Power On == −* Connect the camera's ethernet cables to the switch.+* Connect all cables - power, network, eSATA. −* Power on: switch, SSD enclosure, Eyesis4Pi. Boot takes about 1 min.+* Power on: switch, SSD enclosure, Eyesis4Pi393. Boot takes about 1 min. +* Setup PC IP (can be done beforehand). +* Refresh GUI after camera boots + Note 1: If GUI is refreshed before subcamera has mounted SSD it will not display SSD free space. Refresh in a few moments or until SSD gets mounted. + <b> <b> Important Notice: Use a fan to cool the camera's pole when shooting indoors. Important Notice: Use a fan to cool the camera's pole when shooting indoors. Line 53: Line 57: <font size="2"></font> '''''Note:''' Eyesis4Pi 393 default IP addresses: 192.168.0.161-163'' <br><br> <font size="2"></font> '''''Note:''' Eyesis4Pi 393 default IP addresses: 192.168.0.161-163'' <br><br> + +== Tests == + +... <!-- <!-- Line 131: Line 139: <br><br> <br><br> --> --> + == Setting recording parameters: camera settings == == Setting recording parameters: camera settings == OlegEyesis4Pi 393 User Guide - Recording
Power On
← Older revision Revision as of 17:11, 27 March 2017 (2 intermediate revisions by the same user not shown)Line 4: Line 4: Terminal: Terminal: cd <any-path> cd <any-path> − git clone https://github.com/Elphel/eyesis4pi-393-gui.git+ git clone https://git.elphel.com/Elphel/eyesis4pi-393-gui.git git pull (repeat any time to get the latest) git pull (repeat any time to get the latest) GitHub.com: GitHub.com: Line 35: Line 35: * Connect the camera's ethernet cables to the switch. * Connect the camera's ethernet cables to the switch. * Power on: switch, SSD enclosure, Eyesis4Pi. Boot takes about 1 min. * Power on: switch, SSD enclosure, Eyesis4Pi. Boot takes about 1 min. +* Setup PC IP +* Refresh GUI after camera boots. + <b> <b> Important Notice: Use a fan to cool the camera's pole when shooting indoors. Important Notice: Use a fan to cool the camera's pole when shooting indoors. OlegEyesis4Pi 393 User Guide - Recording
Power On
← Older revision Revision as of 17:10, 27 March 2017 (One intermediate revision by the same user not shown)Line 4: Line 4: Terminal: Terminal: cd <any-path> cd <any-path> − git clone https://github.com/Elphel/eyesis4pi-393-gui.git+ git clone https://git.elphel.com/Elphel/eyesis4pi-393-gui.git git pull (repeat any time to get the latest) git pull (repeat any time to get the latest) GitHub.com: GitHub.com: Line 38: Line 38: Important Notice: Use a fan to cool the camera's pole when shooting indoors. Important Notice: Use a fan to cool the camera's pole when shooting indoors. </b> </b> +* Refresh GUI after camera boots. <br/><br/> <br/><br/> OlegPoky 2.0 manual
Notes
← Older revision Revision as of 19:35, 22 March 2017 Line 173: Line 173: or or recipe-class-inside-task: <font size='2' color='green'><b>d.setVarFlag('do_compile', 'nostamp', '1')</b></font> recipe-class-inside-task: <font size='2' color='green'><b>d.setVarFlag('do_compile', 'nostamp', '1')</b></font> + +* clone git repo over https in a recipe + SRC_URI = "git://git.elphel.com/project.git;protocol=https;branch=master" ==<font color="blue">Errors</font>== ==<font color="blue">Errors</font>== OlegEyesis4Pi 393 User Guide - Firmware Update
Eyesis4Pi 393 User Guide - Firmware Update
Eyesis4Pi 393 User Guide - Firmware Update
Created page with "==Update== 1. Boot from micro SD 2. http://192.168.0.161/update_software.html upload rootfs.ubi and uImage only 3. mount ssh root@192.168.0.161 ubiattach /dev/ubi_ctrl -m..."
New page
==Update==1. Boot from micro SD
2. http://192.168.0.161/update_software.html
upload rootfs.ubi and uImage only
3. mount
ssh root@192.168.0.161
ubiattach /dev/ubi_ctrl -m 4
mount -t ubifs /dev/ubi0_0 /mnt/ubi
4. edit
nano /mnt/ubi/etc/init.d/init_elphel393
#set \"eyesis\":1
CTRL-X
CTRL-Y, ENTER
sync
5. unmount
umount /mnt/ubi
6. repeat 2.-5. for 162 & 163 Oleg
Features 393
Eyesis4Pi 393 Panorama Previewer
changed repository url
← Older revision Revision as of 03:36, 20 March 2017 Line 12: Line 12: ==Source== ==Source== −Available for direct downloading from the [https://github.com/Elphel/eyesis4pi393-panorama-previewer.git GitHub] or from a terminal window provided GIT client is installed:+Available for direct downloading from the [https://git.elphel.com/Elphel/eyesis4pi393-panorama-previewer.git Elphel Git] or from a terminal window provided GIT client is installed: <font size='2'> <font size='2'> − git clone https://github.com/Elphel/eyesis4pi393-panorama-previewer.git panorama_preview+ git clone https://git.elphel.com/Elphel/eyesis4pi393-panorama-previewer.git panorama_preview </font> </font> Andrey.filippovEyesis4Pi 393 Footage Procedures page
changed repository url
← Older revision Revision as of 03:34, 20 March 2017 Line 20: Line 20: ==Download== ==Download== −Available for direct downloading from the [https://github.com/Elphel/eyesis4pi393-footage-procedures.git GitHub] or from a terminal window provided the GIT is installed:+Available for direct downloading from the [https://git.elphel.com/Elphel/eyesis4pi393-footage-procedures.git Elphel Git] or from a terminal window provided the GIT is installed: <font size='2'> <font size='2'> − git clone https://github.com/Elphel/eyesis4pi393-footage-procedures.git footage_procedures+ git clone https://git.elphel.com/Elphel/eyesis4pi393-footage-procedures.git footage_procedures </font> </font> Andrey.filippovFeatures 393
changed repository url
← Older revision Revision as of 03:33, 20 March 2017 Line 51: Line 51: * Firmware development tools: * Firmware development tools: −** [https://eclipse.org Eclipse IDE] + [https://github.com/Elphel/vdt-plugin VDT-Plugin]+** [https://eclipse.org Eclipse IDE] + [https://git.elphel.com/Elphel/vdt-plugin VDT-Plugin] ** [http://www.xilinx.com/products/design-tools/vivado.html Vivado WebPACK Edition] ** [http://www.xilinx.com/products/design-tools/vivado.html Vivado WebPACK Edition] ** [http://iverilog.icarus.com/ IVerilog] ** [http://iverilog.icarus.com/ IVerilog] Line 59: Line 59: ** [https://www.yoctoproject.org/tools-resources/projects/poky Yocto Poky] ** [https://www.yoctoproject.org/tools-resources/projects/poky Yocto Poky] * Sources: * Sources: −** [https://github.com/Elphel GitHub/Elphel]+** [https://git.elphel.com/Elphel Elphel Git] * Tools installation docs * Tools installation docs ** [[Poky_2.0_manual|Set up development environment]] ** [[Poky_2.0_manual|Set up development environment]] Andrey.filippovFormat SSD MMC
changed repository url
← Older revision Revision as of 03:32, 20 March 2017 Line 70: Line 70: ==<font color="blue">Useful links</font>== ==<font color="blue">Useful links</font>== −* [https://github.com/Elphel/elphel-tools-update github:elphel-tools-update] - '''write_bootable_mmc.py'''+* [https://git.elphel.com/Elphel/elphel-tools-update git:elphel-tools-update] - '''write_bootable_mmc.py''' ** the script is used to create a bootable MMC from a PC (the camera doesn't have ''parted'' and ''kpartx'' installed) ** the script is used to create a bootable MMC from a PC (the camera doesn't have ''parted'' and ''kpartx'' installed) ** it has examples of using '''dd''', '''parted''', '''mkfs''', '''kpartx''' ** it has examples of using '''dd''', '''parted''', '''mkfs''', '''kpartx''' Andrey.filippov