https://wiki.elphel.com/api.php?action=feedcontributions&feedformat=atom&user=Andrey.filippovElphelWiki - User contributions [en]2026-08-15T02:28:25ZUser contributionsMediaWiki 1.43.9https://wiki.elphel.com/index.php?title=Elphel_camera_parts_0393-18&diff=19595Elphel camera parts 0393-182026-08-12T18:05:46Z<p>Andrey.filippov: /* 0393-18-80 - Camera Pod Push Bracket */</p>
<hr />
<div>[[Elphel_camera_parts_0393|Elphel NC393 series camera parts]]<br />
== 0393-18 - parts external other ==<br />
----<br />
=== 0353-18-01 - Vertical arm for H-camera ===<br />
{{Cad4a|0393-18-01}}<br />
----<br />
<br />
=== 0353-18-02 - Horizontal arm for H-camera ===<br />
{{Cad4a|0393-18-02}}<br />
----<br />
<br />
=== 0353-18-30 - tripod mount nut, 1/4-20 thread ===<br />
{{Cad4a|0393-18-30}}<br />
----<br />
<br />
=== 0353-18-31 - tripod mount plate ===<br />
{{Cad4a|0393-18-31}}<br />
----<br />
=== 0353-18-31A - tripod mount plate, Rev "A" ===<br />
{{Cad4a|0393-18-31A}}<br />
----<br />
<br />
=== 0393-18-50 - IMU enclosure ===<br />
{{Cad4a|0393-18-50}}<br />
----<br />
=== 0393-18-51 - Camera top with GPS ===<br />
{{Cad4a|0393-18-51}}<br />
----<br />
=== 0393-18-52 - Camera top without GPS ===<br />
{{Cad4a|0393-18-52}}<br />
----<br />
=== 0393-18-53 - GPS cap ===<br />
{{Cad4a|0393-18-53}}<br />
----<br />
=== 0393-18-53 - Fisheye lens shade ===<br />
{{Cad4a|0393-18-54}}<br />
----<br />
<br />
=== 0393-18-67 - 103993 PCBA Body ===<br />
{{Cad4a|0393-18-67}}<br />
----<br />
<br />
=== 0393-18-67A - 103993 PCBA Body, Rev A ===<br />
{{Cad4a|0393-18-67a}}<br />
----<br />
<br />
<br />
<br />
<!--=== 0393-18-695 - Adjustment Mount Cross Drilled ===<br />
{{Cad4a|0393-18-69}}<br />
---- --><br />
<br />
=== 0393-18-69A Adjustment Mount Cross Drilled, rev A ===<br />
{{Cad4a|0393-18-69A}}<br />
<br />
----<br />
<br />
=== 0393-18-69B Adjustment Mount Cross Drilled, Rev B ===<br />
{{Cad4a|0393-18-69B}}<br />
<br />
----<br />
<br />
=== 0393-18-70 - Adjustable Mount Base for Back Access ===<br />
{{Cad4a|0393-18-70}}<br />
----<br />
<br />
=== 0393-18-70B - Adjustable Mount Base for Back Access, Rev B ===<br />
{{Cad4a|0393-18-70B}}<br />
----<br />
<br />
=== 0393-18-70C - Adjustable Mount Base for Back Access, Rev C ===<br />
{{Cad4a|0393-18-70C}}<br />
----<br />
<br />
=== 0393-18-71 - Adjustment Mount Cross Threaded ===<br />
{{Cad4a|0393-18-71}}<br />
----<br />
<br />
=== 0393-18-72 - Adjustable Mount Base for Helmet ===<br />
{{Cad4a|0393-18-72}}<br />
----<br />
<br />
<!--=== 0393-18-73 - Adjustment Spherical Mount Inner ===<br />
{{Cad4a|0393-18-73}}<br />
------><br />
<br />
=== 0393-18-73A - Adjustment Spherical Mount Inner, Rev A ===<br />
{{Cad4a|0393-18-73A}}<br />
----<br />
<br />
=== 0393-18-73C - Adjustment Spherical Mount Inner, Rev C ===<br />
{{Cad4a|0393-18-73C}}<br />
----<br />
<br />
<br />
=== 0393-18-80 - Camera Pod Push Bracket ===<br />
{{Cad4a|0393-18-80}}<br />
----<br />
<br />
=== 0393-18-81 - Camera Pod Push Centerpiece ===<br />
{{Cad4a|0393-18-81}}<br />
----<br />
<br />
=== 0393-18-82 - Camera Pod Pull Bracket Front ===<br />
{{Cad4a|0393-18-82}}<br />
----<br />
<br />
<br />
=== 0393-18-83 - Camera Pod Pull Bracket Rear ===<br />
{{Cad4a|0393-18-83}}<br />
----<br />
<br />
=== 0393-18-84 - Guide Tube ===<br />
{{Cad4a|0393-18-84}}<br />
----<br />
<br />
=== 0393-18-85 - Push Rod ===<br />
{{Cad4a|0393-18-85}}<br />
----</div>Andrey.filippovhttps://wiki.elphel.com/index.php?title=Elphel_camera_parts_0393-18&diff=19594Elphel camera parts 0393-182026-08-12T18:01:32Z<p>Andrey.filippov: /* 0393-18-73C - Adjustment Spherical Mount Inner, Rev C */</p>
<hr />
<div>[[Elphel_camera_parts_0393|Elphel NC393 series camera parts]]<br />
== 0393-18 - parts external other ==<br />
----<br />
=== 0353-18-01 - Vertical arm for H-camera ===<br />
{{Cad4a|0393-18-01}}<br />
----<br />
<br />
=== 0353-18-02 - Horizontal arm for H-camera ===<br />
{{Cad4a|0393-18-02}}<br />
----<br />
<br />
=== 0353-18-30 - tripod mount nut, 1/4-20 thread ===<br />
{{Cad4a|0393-18-30}}<br />
----<br />
<br />
=== 0353-18-31 - tripod mount plate ===<br />
{{Cad4a|0393-18-31}}<br />
----<br />
=== 0353-18-31A - tripod mount plate, Rev "A" ===<br />
{{Cad4a|0393-18-31A}}<br />
----<br />
<br />
=== 0393-18-50 - IMU enclosure ===<br />
{{Cad4a|0393-18-50}}<br />
----<br />
=== 0393-18-51 - Camera top with GPS ===<br />
{{Cad4a|0393-18-51}}<br />
----<br />
=== 0393-18-52 - Camera top without GPS ===<br />
{{Cad4a|0393-18-52}}<br />
----<br />
=== 0393-18-53 - GPS cap ===<br />
{{Cad4a|0393-18-53}}<br />
----<br />
=== 0393-18-53 - Fisheye lens shade ===<br />
{{Cad4a|0393-18-54}}<br />
----<br />
<br />
=== 0393-18-67 - 103993 PCBA Body ===<br />
{{Cad4a|0393-18-67}}<br />
----<br />
<br />
=== 0393-18-67A - 103993 PCBA Body, Rev A ===<br />
{{Cad4a|0393-18-67a}}<br />
----<br />
<br />
<br />
<br />
<!--=== 0393-18-695 - Adjustment Mount Cross Drilled ===<br />
{{Cad4a|0393-18-69}}<br />
---- --><br />
<br />
=== 0393-18-69A Adjustment Mount Cross Drilled, rev A ===<br />
{{Cad4a|0393-18-69A}}<br />
<br />
----<br />
<br />
=== 0393-18-69B Adjustment Mount Cross Drilled, Rev B ===<br />
{{Cad4a|0393-18-69B}}<br />
<br />
----<br />
<br />
=== 0393-18-70 - Adjustable Mount Base for Back Access ===<br />
{{Cad4a|0393-18-70}}<br />
----<br />
<br />
=== 0393-18-70B - Adjustable Mount Base for Back Access, Rev B ===<br />
{{Cad4a|0393-18-70B}}<br />
----<br />
<br />
=== 0393-18-70C - Adjustable Mount Base for Back Access, Rev C ===<br />
{{Cad4a|0393-18-70C}}<br />
----<br />
<br />
=== 0393-18-71 - Adjustment Mount Cross Threaded ===<br />
{{Cad4a|0393-18-71}}<br />
----<br />
<br />
=== 0393-18-72 - Adjustable Mount Base for Helmet ===<br />
{{Cad4a|0393-18-72}}<br />
----<br />
<br />
<!--=== 0393-18-73 - Adjustment Spherical Mount Inner ===<br />
{{Cad4a|0393-18-73}}<br />
------><br />
<br />
=== 0393-18-73A - Adjustment Spherical Mount Inner, Rev A ===<br />
{{Cad4a|0393-18-73A}}<br />
----<br />
<br />
=== 0393-18-73C - Adjustment Spherical Mount Inner, Rev C ===<br />
{{Cad4a|0393-18-73C}}<br />
----<br />
<br />
<br />
=== 0393-18-80 - Camera Pod Push Bracket ===<br />
{{Cad4a|0393-18-80}}<br />
----</div>Andrey.filippovhttps://wiki.elphel.com/index.php?title=Elphel_camera_parts_0393-13&diff=12804Elphel camera parts 0393-132025-10-01T00:21:40Z<p>Andrey.filippov: /* UAS Mount */</p>
<hr />
<div>[[Elphel_camera_parts_0393|Elphel NC393 series camera parts]]<br />
=== 0393-13 - Camera back panels ===<br />
----<br />
==== 0393-13-01 - Back panel for NC393, connector openings for 10393A and 10389B connectors ====<br />
{{Cad4a|0393-13-01}}<br />
----<br />
==== 0393-13-01A - Back panel for NC393, Rev. "A", connector openings for 10393A and 10389B connectors ====<br />
{{Cad4a|0393-13-01a}}<br />
----<br />
<br />
==== 0393-13-02 - Back panel for NC393, connector openings for 10393 board only ====<br />
{{Cad4a|0393-13-02}}<br />
----<br />
<br />
==== 0393-13-03 - Camera back connection plate ====<br />
{{Cad4a|0393-13-03}}<br />
----<br />
<br />
==== 0393-13-14 - Half-plate for SFE mount ====<br />
{{Cad4a|0393-13-14}}<br />
----<br />
<br />
==== 0393-13-14A - Half-plate for SFE mount, Rev A ====<br />
{{Cad4a|0393-13-14A}}<br />
----<br />
<br />
==== 0393-13-15 - Sensor Assembly Cover ====<br />
{{Cad4a|0393-13-15}}<br />
----<br />
<br />
==== 0393-13-15B - Sensor Assembly Cover, rev B ====<br />
{{Cad4a|0393-13-15B}}<br />
----<br />
<br />
==== 0393-13-15C - Sensor Assembly Cover, rev CB ====<br />
{{Cad4a|0393-13-15C}}<br />
----<br />
<br />
==== 0393-13-16 - Flex Cables Cover, Side ====<br />
{{Cad4a|0393-13-16}}<br />
----<br />
<br />
==== 0393-13-17 - Flex Cables Cover, Bottom ====<br />
{{Cad4a|0393-13-17}}<br />
----<br />
<br />
==== 0393-13-18 - Flex Cable Cover Spacer, Corner ====<br />
{{Cad4a|0393-13-18}}<br />
----<br />
<br />
==== 0393-13-19 - Flex Cables Cover Spacer, Middle ====<br />
{{Cad4a|0393-13-19}}<br />
----<br />
<br />
==== 0393-13-20 - Back Mount Plate ====<br />
{{Cad4a|0393-13-20}}<br />
----<br />
<br />
==== 0393-13-21 - Camera Mount Plate, Upper ====<br />
{{Cad4a|0393-13-21}}<br />
----<br />
<br />
==== 0393-13-22 - Camera Support ====<br />
{{Cad4a|0393-13-22}}<br />
----<br />
<br />
==== 0393-13-23 - Camera Mount Plate, Bottom ====<br />
{{Cad4a|0393-13-23}}<br />
----<br />
==== 0393-13-25 - UAS Mount Bracket, Welded ====<br />
{{Cad4a|0393-13-25}}<br />
----<br />
==== 0393-13-26 - UAS Mount Bracket, Beam Long, Camera Side ====<br />
{{Cad4a|0393-13-26}}<br />
----<br />
==== 0393-13-27 - UAS Mount Bracket, Beam Left ====<br />
{{Cad4a|0393-13-27}}<br />
----<br />
==== 0393-13-28 - UAS Mount Bracket, Beam Right ====<br />
{{Cad4a|0393-13-28}}<br />
----<br />
==== 0393-13-29 - UAS Mount Bracket, Beam Vertical ====<br />
{{Cad4a|0393-13-29}}<br />
----<br />
==== 0393-13-30 - UAS Mount Bracket, Beam Top ====<br />
{{Cad4a|0393-13-30}}<br />
----</div>Andrey.filippovhttps://wiki.elphel.com/index.php?title=Poky_manual&diff=13115Poky manual2025-07-28T15:52:05Z<p>Andrey.filippov: </p>
<hr />
<div>==<font color="blue">Description</font>==<br />
Build the firmware for Elphel 10393 series camera systems from scratch.<br />
<br />
Prebuilt releases can be found [https://community.elphel.com/files/393/ here].<br />
<br />
==<font color="blue">Use cases</font>==<br />
* Update Linux Kernel when developing a driver<br />
* Include application to the default firmware package<br />
* Update Elphel's PHP extension<br />
* C/C++ applications if developed on PC require a cross-compiler and require Yocto installation or some other alternative.<br />
<br />
Other projects written in Python, PHP, Javascript, HTML, C/C++ (gcc is installed on the system board) can be developed on the camera. Installing the framework is not required but it can simplify the development process.<br />
<br />
==<font color="blue">Description</font>==<br />
<br />
* Building embedded Linux image for Zynq ARMv7 platform - Elphel 10393 board<br />
* Yocto Poky revision = 2.7.1 (Warrior) - <font color="green">builds in Kubuntu 20.04.</font> <font color="red">Older OSes are not supported. Roll back to get built in 16.04.</font><br />
* <s>Yocto Poky revision = 2.4 (Rocko) - <font color="green">builds in Kubuntu 16.04.</font> <font color="red">Won't build in 18.04 or 20.04.</font></s><br />
* <s>Yocto Poky revision = 2.0 (Jethro)</s><br />
<br />
==<font color="blue">Features</font>==<br />
* Environment is set up with a single script<br />
* All Elphel projects are configured for Eclipse IDE:<br />
** fpga projects (verilog)<br />
** kernel<br />
** applications projects<br />
* All steps for fpga projects are run from Eclipse IDE<br />
** Read about [http://blog.elphel.com/2016/05/tutorial-02-eclipse-based-fpga-development-environment-for-elphel-cameras/ setting up Eclipse based FPGA development]<br />
** [https://git.elphel.com/Elphel/vdt-plugin VDT Plugin repository]<br />
<br />
* Once everything is built it supports updating software projects (files and binaries) on the target system<br />
** access is set up in yocto's ''local.conf'' (see ''setup.py'' output) + ''ssh-copy-id''<br />
** ''bitbake some-app -c target_scp'' from the command line or Eclipse IDE - see examples in '''elphel-apps-...''' at [https://git.elphel.com/Elphel Git]<br />
<br />
==<font color="blue">Requirements</font>==<br />
* Kubuntu 20.04 x64<br />
* <s>Kubuntu 18.04 x64 (as of Dec 2018) - Poky: 2.7.1 Warrior (not tested but might build w/o problems)</s><br />
* <s>Kubuntu 16.04 x64 (as of Dec 2018) - Poky: 2.4 Rocko, 2.7.1 Warrior</s><br />
<br />
==<font color="blue">Output files</font>==<br />
The names are listed as they appear in the u-boot configuration header file - actual output files have different names:<br />
{| class="wikitable"<br />
|-<br />
! File(s)<br />
! Build Command<br />
! Description<br />
|-<br />
| <font color='darkblue'>'''boot.bin'''</font><br />
| ''bitbake u-boot''<br />
| u-boot as the first stage bootloader = Secondary Program Loader (SPL) that boots '''u-boot-dtb.img'''<br />
|-<br />
| <font color='darkblue'>'''u-boot-dtb.img'''</font><br />
| ''bitbake u-boot''<br />
| full size u-boot with a stripped device tree (''cat u-boot.img some_stripped_devicetree.dtb > u-boot-dtb.img'')<br />
|-<br />
|valign='top'| <font color='darkblue'>'''devicetree.dtb'''</font><br />
| bitbake device-tree<br />
| device tree with listed interfaces, zynq registers, interrupts and drivers<br />
* ''elphel393/bootable-images/mmc/devicetree.dtb'' - mount rootfs from mmc partition<br />
* ''elphel393/bootable-images/nand/devicetree.dtb'' - mount rootfs from NAND flash<br />
|-<br />
| <font color='darkblue'>'''uImage'''</font><br />
| ''bitbake linux-xlnx''<br />
| kernel, drivers<br />
|-<br />
| <font color='darkblue'>'''rootfs.ubifs''', '''rootfs.ubi''', '''rootfs.tar.gz'''</font><br />
| ''bitbake core-image-elphel393''<br />
| rootfs in different formats - *.ubi* for NAND, *.tar.gz for mmc<br />
|}<br />
<br />
The file are located at '''elphel393/bootable-images/''', which is a link to poky's deploy directory '''elphel393/poky/build/tmp/deploy/images/elphel393/'''<br />
<br />
* complete set of files for rootfs in NAND Flash: ''elphel393/bootable-images/nand/''<br />
* complete set of files for rootfs on MMC (micro SD card): ''elphel393/bootable-images/mmc/''<br />
<br />
==<font color="blue">Write files to media and boot</font>==<br />
===Boot from micro SD card===<br />
* Use recovery or regular &mu;SD card<br />
* EXT4 partition mounted as '''/'''<br />
[[Sd_boot_rootfs|Detailed instructions]]<br />
<br />
===Boot from NAND flash===<br />
* The default boot option - power on.<br />
* A UBIFS image is written to /dev/mtd4 - is mounted as '''/'''<br />
[[NAND_flash_boot_rootfs|Detailed instructions]]<br />
<br />
===Notes===<br />
* [[Boot_options_393|'''Read more''']] about boot options.<br />
<br />
==<font color="blue">Setup</font>==<br />
* Before building<br />
Installing some dependencies:<br />
sudo apt install git build-essential chrpath diffstat gawk texinfo zlib1g-dev python3-numpy libssl-dev<br />
Installing old python2.7 (bitbake snapshot that we used has problem with python3.8):<br />
sudo apt install python2.7<br />
sudo ln -s python2.7 python2<br />
sudo ln -s python2.7 python<br />
<br />
* Poky 2.7.1 Warrior (Kubuntu 20.04)<br />
<font size='2'><br />
git clone -b '''warrior''' https://git.elphel.com/Elphel/elphel393.git<br />
<br />
If you are a developer and plan to commit changes you should use ssh access instead:<br />
git clone -b warrior git@git.elphel.com:Elphel/elphel393.git<br />
<br />
We never use non-developer mode ourselves, so it may malfunction. Be careful not to forget "-b warrior", otherwise<br />
you will get <br />
SyntaxError: invalid syntax<br />
when running setup.py - main branch is broken. You may use "git checkout -b warrior" then.<br />
<br />
<br />
cd elphel393<br />
./setup.py<br />
cd poky<br />
. ./oe-init-build-env<br />
bitbake u-boot device-tree linux-xlnx core-image-elphel393<br />
</font><br />
<br />
* <s>Poky 2.4 Rocko (Kubuntu 16.04)<br />
<font size='2'><br />
git clone -b '''rocko''' https://git.elphel.com/Elphel/elphel393.git<br />
cd elphel393<br />
./setup.py<br />
cd poky<br />
. ./oe-init-build-env<br />
bitbake u-boot device-tree linux-xlnx core-image-elphel393<br />
<!--''Temporary: linux-xlnx in Rocko depends on branch 'lwir' for x393. Change in projects.json line 42 from 'master' to 'lwir'.''--><br />
</font></s><br />
<br />
* Notes (required actions are already listed above): When trying to run bitbake on a new install got problems with older bitbake version (current build uses specific snapshot) and python3.8. So I install old python2.7 and linked it:<br />
sudo apt install python2.7 python-numpy<br />
sudo ln -s python2.7 python2<br />
sudo ln -s python2.7 python<br />
<br />
After this bitbake just complained about missing tools (git, build-essential were already installed):<br />
<br />
sudo apt install chrpath diffstat gawk makeinfo<br />
<br />
Program test_mcntrl.py that builds x393.h header files from FPGA code that runs during ./setup.py requires numpy and results in error output if missing Still setup.py continues, you need to look through its output few lines after<br />
* x393<br />
git host: git.elphel.com<br />
Clone and checkout: x393<br />
<br />
You may install numpy with<br />
sudo apt install python3-numpy<br />
<br />
If you did not notice missing numpy, then during bitbake you will get error "build No rule to make target 'drivers/elphel/x393.o', needed by 'drivers/elphel/built-in.a'. Stop." in that case you need to install numpy, re-run setup.py (make sure numpy error is gone) then re-create linux kernel links during next build by erasing old ones:<br />
bitbake linux-xlnx -c clean<br />
and re-running<br />
bitbake linux-xlnx device-tree core-image-elphel393<br />
<br />
When building php: configure: error: zip support requires ZLIB. Use --with-zlib-dir=<DIR> to specify prefix where ZLIB include and library are located<br />
sudo apt install zlib1g-dev<br />
<br />
==<font color="blue">Compare '''built''' vs '''deployed''' software versions</font>==<br />
<font size='2'><br />
cd elphel393<br />
./check_versions.py root@192.168.0.9<br />
</font><br />
<br />
{|<br />
|[[File:Check versions.png|thumb|400px|check_versions.py output in terminal (web-393 revision on PC is ahead of the one installed on the camera)]]<br />
|}<br />
<br />
==<font color="blue">Details for development</font>==<br />
[[Development_for_10393|'''Development for 10393''']]<br />
<br />
<br />
==<font color="blue">Using local mirror to accelerate multiple builds/testing</font>==<br />
You may use the files in poky/build/downloads directory as a local mirror (it should be copied outside of the build tree) by editing local.conf:<br />
#if mirrors are local (file:///), downloads will contain symlinks, not copies<br />
#SOURCE_MIRROR_URL = "file:///home/elphel/git/elphel393_mirror/"<br />
SOURCE_MIRROR_URL = "https://mirror.elphel.com/elphel393_mirror/"<br />
to <br />
#if mirrors are local (file:///), downloads will contain symlinks, not copies<br />
SOURCE_MIRROR_URL = "file:///home/elphel/git/elphel393_mirror/"<br />
#SOURCE_MIRROR_URL = "https://mirror.elphel.com/elphel393_mirror/"<br />
and replacing file:/// link to your local mirror location (a copy of poky/build/downloads/). In that case the new build downloads folder will contain symlinks to the local mirror, not the copies.</div>Andrey.filippovhttps://wiki.elphel.com/index.php?title=Poky_manual&diff=13114Poky manual2025-07-25T20:28:34Z<p>Andrey.filippov: </p>
<hr />
<div>==<font color="blue">Description</font>==<br />
Build the firmware for Elphel 10393 series camera systems from scratch.<br />
<br />
Prebuilt releases can be found [https://community.elphel.com/files/393/ here].<br />
<br />
==<font color="blue">Use cases</font>==<br />
* Update Linux Kernel when developing a driver<br />
* Include application to the default firmware package<br />
* Update Elphel's PHP extension<br />
* C/C++ applications if developed on PC require a cross-compiler and require Yocto installation or some other alternative.<br />
<br />
Other projects written in Python, PHP, Javascript, HTML, C/C++ (gcc is installed on the system board) can be developed on the camera. Installing the framework is not required but it can simplify the development process.<br />
<br />
==<font color="blue">Description</font>==<br />
<br />
* Building embedded Linux image for Zynq ARMv7 platform - Elphel 10393 board<br />
* Yocto Poky revision = 2.7.1 (Warrior) - <font color="green">builds in Kubuntu 20.04.</font> <font color="red">Older OSes are not supported. Roll back to get built in 16.04.</font><br />
* <s>Yocto Poky revision = 2.4 (Rocko) - <font color="green">builds in Kubuntu 16.04.</font> <font color="red">Won't build in 18.04 or 20.04.</font></s><br />
* <s>Yocto Poky revision = 2.0 (Jethro)</s><br />
<br />
==<font color="blue">Features</font>==<br />
* Environment is set up with a single script<br />
* All Elphel projects are configured for Eclipse IDE:<br />
** fpga projects (verilog)<br />
** kernel<br />
** applications projects<br />
* All steps for fpga projects are run from Eclipse IDE<br />
** Read about [http://blog.elphel.com/2016/05/tutorial-02-eclipse-based-fpga-development-environment-for-elphel-cameras/ setting up Eclipse based FPGA development]<br />
** [https://git.elphel.com/Elphel/vdt-plugin VDT Plugin repository]<br />
<br />
* Once everything is built it supports updating software projects (files and binaries) on the target system<br />
** access is set up in yocto's ''local.conf'' (see ''setup.py'' output) + ''ssh-copy-id''<br />
** ''bitbake some-app -c target_scp'' from the command line or Eclipse IDE - see examples in '''elphel-apps-...''' at [https://git.elphel.com/Elphel Git]<br />
<br />
==<font color="blue">Requirements</font>==<br />
* Kubuntu 20.04 x64<br />
* <s>Kubuntu 18.04 x64 (as of Dec 2018) - Poky: 2.7.1 Warrior (not tested but might build w/o problems)</s><br />
* <s>Kubuntu 16.04 x64 (as of Dec 2018) - Poky: 2.4 Rocko, 2.7.1 Warrior</s><br />
<br />
==<font color="blue">Output files</font>==<br />
The names are listed as they appear in the u-boot configuration header file - actual output files have different names:<br />
{| class="wikitable"<br />
|-<br />
! File(s)<br />
! Build Command<br />
! Description<br />
|-<br />
| <font color='darkblue'>'''boot.bin'''</font><br />
| ''bitbake u-boot''<br />
| u-boot as the first stage bootloader = Secondary Program Loader (SPL) that boots '''u-boot-dtb.img'''<br />
|-<br />
| <font color='darkblue'>'''u-boot-dtb.img'''</font><br />
| ''bitbake u-boot''<br />
| full size u-boot with a stripped device tree (''cat u-boot.img some_stripped_devicetree.dtb > u-boot-dtb.img'')<br />
|-<br />
|valign='top'| <font color='darkblue'>'''devicetree.dtb'''</font><br />
| bitbake device-tree<br />
| device tree with listed interfaces, zynq registers, interrupts and drivers<br />
* ''elphel393/bootable-images/mmc/devicetree.dtb'' - mount rootfs from mmc partition<br />
* ''elphel393/bootable-images/nand/devicetree.dtb'' - mount rootfs from NAND flash<br />
|-<br />
| <font color='darkblue'>'''uImage'''</font><br />
| ''bitbake linux-xlnx''<br />
| kernel, drivers<br />
|-<br />
| <font color='darkblue'>'''rootfs.ubifs''', '''rootfs.ubi''', '''rootfs.tar.gz'''</font><br />
| ''bitbake core-image-elphel393''<br />
| rootfs in different formats - *.ubi* for NAND, *.tar.gz for mmc<br />
|}<br />
<br />
The file are located at '''elphel393/bootable-images/''', which is a link to poky's deploy directory '''elphel393/poky/build/tmp/deploy/images/elphel393/'''<br />
<br />
* complete set of files for rootfs in NAND Flash: ''elphel393/bootable-images/nand/''<br />
* complete set of files for rootfs on MMC (micro SD card): ''elphel393/bootable-images/mmc/''<br />
<br />
==<font color="blue">Write files to media and boot</font>==<br />
===Boot from micro SD card===<br />
* Use recovery or regular &mu;SD card<br />
* EXT4 partition mounted as '''/'''<br />
[[Sd_boot_rootfs|Detailed instructions]]<br />
<br />
===Boot from NAND flash===<br />
* The default boot option - power on.<br />
* A UBIFS image is written to /dev/mtd4 - is mounted as '''/'''<br />
[[NAND_flash_boot_rootfs|Detailed instructions]]<br />
<br />
===Notes===<br />
* [[Boot_options_393|'''Read more''']] about boot options.<br />
<br />
==<font color="blue">Setup</font>==<br />
* Before building<br />
Installing some dependencies:<br />
sudo apt install git build-essential chrpath diffstat gawk texinfo zlib1g-dev python3-numpy libssl-dev<br />
Installing old python2.7 (bitbake snapshot that we used has problem with python3.8):<br />
sudo apt install python2.7<br />
sudo ln -s python2.7 python2<br />
sudo ln -s python2.7 python<br />
<br />
* Poky 2.7.1 Warrior (Kubuntu 20.04)<br />
<font size='2'><br />
git clone -b '''warrior''' https://git.elphel.com/Elphel/elphel393.git<br />
<br />
If you are a developer and plan to commit changes you should use ssh access instead: git clone -b warrior git@git.elphel.com:Elphel/elphel393.git . We never use non-developer mode ourselves, so it may malfunction. Be careful not to forget "-b warrior", otherwise<br />
you will get <br />
SyntaxError: invalid syntax<br />
when running setup.py - main branch is broken. You may use "git checkout -b warrior" then.<br />
<br />
<br />
cd elphel393<br />
./setup.py<br />
cd poky<br />
. ./oe-init-build-env<br />
bitbake u-boot device-tree linux-xlnx core-image-elphel393<br />
</font><br />
<br />
* <s>Poky 2.4 Rocko (Kubuntu 16.04)<br />
<font size='2'><br />
git clone -b '''rocko''' https://git.elphel.com/Elphel/elphel393.git<br />
cd elphel393<br />
./setup.py<br />
cd poky<br />
. ./oe-init-build-env<br />
bitbake u-boot device-tree linux-xlnx core-image-elphel393<br />
<!--''Temporary: linux-xlnx in Rocko depends on branch 'lwir' for x393. Change in projects.json line 42 from 'master' to 'lwir'.''--><br />
</font></s><br />
<br />
* Notes (required actions are already listed above): When trying to run bitbake on a new install got problems with older bitbake version (current build uses specific snapshot) and python3.8. So I install old python2.7 and linked it:<br />
sudo apt install python2.7 python-numpy<br />
sudo ln -s python2.7 python2<br />
sudo ln -s python2.7 python<br />
<br />
After this bitbake just complained about missing tools (git, build-essential were already installed):<br />
<br />
sudo apt install chrpath diffstat gawk makeinfo<br />
<br />
Program test_mcntrl.py that builds x393.h header files from FPGA code that runs during ./setup.py requires numpy and results in error output if missing Still setup.py continues, you need to look through its output few lines after<br />
* x393<br />
git host: git.elphel.com<br />
Clone and checkout: x393<br />
<br />
You may install numpy with<br />
sudo apt install python3-numpy<br />
<br />
If you did not notice missing numpy, then during bitbake you will get error "build No rule to make target 'drivers/elphel/x393.o', needed by 'drivers/elphel/built-in.a'. Stop." in that case you need to install numpy, re-run setup.py (make sure numpy error is gone) then re-create linux kernel links during next build by erasing old ones:<br />
bitbake linux-xlnx -c clean<br />
and re-running<br />
bitbake linux-xlnx device-tree core-image-elphel393<br />
<br />
When building php: configure: error: zip support requires ZLIB. Use --with-zlib-dir=<DIR> to specify prefix where ZLIB include and library are located<br />
sudo apt install zlib1g-dev<br />
<br />
==<font color="blue">Compare '''built''' vs '''deployed''' software versions</font>==<br />
<font size='2'><br />
cd elphel393<br />
./check_versions.py root@192.168.0.9<br />
</font><br />
<br />
{|<br />
|[[File:Check versions.png|thumb|400px|check_versions.py output in terminal (web-393 revision on PC is ahead of the one installed on the camera)]]<br />
|}<br />
<br />
==<font color="blue">Details for development</font>==<br />
[[Development_for_10393|'''Development for 10393''']]<br />
<br />
<br />
==<font color="blue">Using local mirror to accelerate multiple builds/testing</font>==<br />
You may use the files in poky/build/downloads directory as a local mirror (it should be copied outside of the build tree) by editing local.conf:<br />
#if mirrors are local (file:///), downloads will contain symlinks, not copies<br />
#SOURCE_MIRROR_URL = "file:///home/elphel/git/elphel393_mirror/"<br />
SOURCE_MIRROR_URL = "https://mirror.elphel.com/elphel393_mirror/"<br />
to <br />
#if mirrors are local (file:///), downloads will contain symlinks, not copies<br />
SOURCE_MIRROR_URL = "file:///home/elphel/git/elphel393_mirror/"<br />
#SOURCE_MIRROR_URL = "https://mirror.elphel.com/elphel393_mirror/"<br />
and replacing file:/// link to your local mirror location (a copy of poky/build/downloads/). In that case the new build downloads folder will contain symlinks to the local mirror, not the copies.</div>Andrey.filippovhttps://wiki.elphel.com/index.php?title=Poky_manual&diff=13113Poky manual2025-07-25T20:18:55Z<p>Andrey.filippov: </p>
<hr />
<div>==<font color="blue">Description</font>==<br />
Build the firmware for Elphel 10393 series camera systems from scratch.<br />
<br />
Prebuilt releases can be found [https://community.elphel.com/files/393/ here].<br />
<br />
==<font color="blue">Use cases</font>==<br />
* Update Linux Kernel when developing a driver<br />
* Include application to the default firmware package<br />
* Update Elphel's PHP extension<br />
* C/C++ applications if developed on PC require a cross-compiler and require Yocto installation or some other alternative.<br />
<br />
Other projects written in Python, PHP, Javascript, HTML, C/C++ (gcc is installed on the system board) can be developed on the camera. Installing the framework is not required but it can simplify the development process.<br />
<br />
==<font color="blue">Description</font>==<br />
<br />
* Building embedded Linux image for Zynq ARMv7 platform - Elphel 10393 board<br />
* Yocto Poky revision = 2.7.1 (Warrior) - <font color="green">builds in Kubuntu 20.04.</font> <font color="red">Older OSes are not supported. Roll back to get built in 16.04.</font><br />
* <s>Yocto Poky revision = 2.4 (Rocko) - <font color="green">builds in Kubuntu 16.04.</font> <font color="red">Won't build in 18.04 or 20.04.</font></s><br />
* <s>Yocto Poky revision = 2.0 (Jethro)</s><br />
<br />
==<font color="blue">Features</font>==<br />
* Environment is set up with a single script<br />
* All Elphel projects are configured for Eclipse IDE:<br />
** fpga projects (verilog)<br />
** kernel<br />
** applications projects<br />
* All steps for fpga projects are run from Eclipse IDE<br />
** Read about [http://blog.elphel.com/2016/05/tutorial-02-eclipse-based-fpga-development-environment-for-elphel-cameras/ setting up Eclipse based FPGA development]<br />
** [https://git.elphel.com/Elphel/vdt-plugin VDT Plugin repository]<br />
<br />
* Once everything is built it supports updating software projects (files and binaries) on the target system<br />
** access is set up in yocto's ''local.conf'' (see ''setup.py'' output) + ''ssh-copy-id''<br />
** ''bitbake some-app -c target_scp'' from the command line or Eclipse IDE - see examples in '''elphel-apps-...''' at [https://git.elphel.com/Elphel Git]<br />
<br />
==<font color="blue">Requirements</font>==<br />
* Kubuntu 20.04 x64<br />
* <s>Kubuntu 18.04 x64 (as of Dec 2018) - Poky: 2.7.1 Warrior (not tested but might build w/o problems)</s><br />
* <s>Kubuntu 16.04 x64 (as of Dec 2018) - Poky: 2.4 Rocko, 2.7.1 Warrior</s><br />
<br />
==<font color="blue">Output files</font>==<br />
The names are listed as they appear in the u-boot configuration header file - actual output files have different names:<br />
{| class="wikitable"<br />
|-<br />
! File(s)<br />
! Build Command<br />
! Description<br />
|-<br />
| <font color='darkblue'>'''boot.bin'''</font><br />
| ''bitbake u-boot''<br />
| u-boot as the first stage bootloader = Secondary Program Loader (SPL) that boots '''u-boot-dtb.img'''<br />
|-<br />
| <font color='darkblue'>'''u-boot-dtb.img'''</font><br />
| ''bitbake u-boot''<br />
| full size u-boot with a stripped device tree (''cat u-boot.img some_stripped_devicetree.dtb > u-boot-dtb.img'')<br />
|-<br />
|valign='top'| <font color='darkblue'>'''devicetree.dtb'''</font><br />
| bitbake device-tree<br />
| device tree with listed interfaces, zynq registers, interrupts and drivers<br />
* ''elphel393/bootable-images/mmc/devicetree.dtb'' - mount rootfs from mmc partition<br />
* ''elphel393/bootable-images/nand/devicetree.dtb'' - mount rootfs from NAND flash<br />
|-<br />
| <font color='darkblue'>'''uImage'''</font><br />
| ''bitbake linux-xlnx''<br />
| kernel, drivers<br />
|-<br />
| <font color='darkblue'>'''rootfs.ubifs''', '''rootfs.ubi''', '''rootfs.tar.gz'''</font><br />
| ''bitbake core-image-elphel393''<br />
| rootfs in different formats - *.ubi* for NAND, *.tar.gz for mmc<br />
|}<br />
<br />
The file are located at '''elphel393/bootable-images/''', which is a link to poky's deploy directory '''elphel393/poky/build/tmp/deploy/images/elphel393/'''<br />
<br />
* complete set of files for rootfs in NAND Flash: ''elphel393/bootable-images/nand/''<br />
* complete set of files for rootfs on MMC (micro SD card): ''elphel393/bootable-images/mmc/''<br />
<br />
==<font color="blue">Write files to media and boot</font>==<br />
===Boot from micro SD card===<br />
* Use recovery or regular &mu;SD card<br />
* EXT4 partition mounted as '''/'''<br />
[[Sd_boot_rootfs|Detailed instructions]]<br />
<br />
===Boot from NAND flash===<br />
* The default boot option - power on.<br />
* A UBIFS image is written to /dev/mtd4 - is mounted as '''/'''<br />
[[NAND_flash_boot_rootfs|Detailed instructions]]<br />
<br />
===Notes===<br />
* [[Boot_options_393|'''Read more''']] about boot options.<br />
<br />
==<font color="blue">Setup</font>==<br />
* Before building<br />
Installing some dependencies:<br />
sudo apt install git build-essential chrpath diffstat gawk texinfo zlib1g-dev python3-numpy libssl-dev<br />
Installing old python2.7 (bitbake snapshot that we used has problem with python3.8):<br />
sudo apt install python2.7<br />
sudo ln -s python2.7 python2<br />
sudo ln -s python2.7 python<br />
<br />
* Poky 2.7.1 Warrior (Kubuntu 20.04)<br />
<font size='2'><br />
git clone -b '''warrior''' https://git.elphel.com/Elphel/elphel393.git<br />
<br />
If you are a developer and plan to commit changes you should use ssh access instead: git clone -b warrior git@git.elphel.com:Elphel/elphel393.git . We never use non-developer mode ourselves, so it may malfunction. Be careful not to forget "-b warrior", otherwise<br />
you will get <br />
SyntaxError: invalid syntax<br />
when running setup.py - main branch is broken. You may use "git checkout -b warrior" then.<br />
<br />
<br />
cd elphel393<br />
./setup.py<br />
cd poky<br />
. ./oe-init-build-env<br />
bitbake u-boot device-tree linux-xlnx core-image-elphel393<br />
</font><br />
<br />
* <s>Poky 2.4 Rocko (Kubuntu 16.04)<br />
<font size='2'><br />
git clone -b '''rocko''' https://git.elphel.com/Elphel/elphel393.git<br />
cd elphel393<br />
./setup.py<br />
cd poky<br />
. ./oe-init-build-env<br />
bitbake u-boot device-tree linux-xlnx core-image-elphel393<br />
<!--''Temporary: linux-xlnx in Rocko depends on branch 'lwir' for x393. Change in projects.json line 42 from 'master' to 'lwir'.''--><br />
</font></s><br />
<br />
* Notes (required actions are already listed above): When trying to run bitbake on a new install got problems with older bitbake version (current build uses specific snapshot) and python3.8. So I install old python2.7 and linked it:<br />
sudo apt install python2.7 python-numpy<br />
sudo ln -s python2.7 python2<br />
sudo ln -s python2.7 python<br />
<br />
After this bitbake just complained about missing tools (git, build-essential were already installed):<br />
<br />
sudo apt install chrpath diffstat gawk makeinfo<br />
<br />
Program test_mcntrl.py that builds x393.h header files from FPGA code that runs during ./setup.py requires numpy and results in error output if missing Still setup.py continues, you need to look through its output few lines after<br />
* x393<br />
git host: git.elphel.com<br />
Clone and checkout: x393<br />
<br />
You may install numpy with<br />
sudo apt install python3-numpy<br />
<br />
If you did not notice missing numpy, then during bitbake you will get error "build No rule to make target 'drivers/elphel/x393.o', needed by 'drivers/elphel/built-in.a'. Stop." in that case you need to install numpy, re-run setup.py (make sure numpy error is gone) then re-create linux kernel links during next build by erasing old ones:<br />
bitbake linux-xlnx -c clean<br />
and re-running<br />
bitbake linux-xlnx device-tree core-image-elphel393<br />
<br />
When building php: configure: error: zip support requires ZLIB. Use --with-zlib-dir=<DIR> to specify prefix where ZLIB include and library are located<br />
sudo apt install zlib1g-dev<br />
<br />
==<font color="blue">Compare '''built''' vs '''deployed''' software versions</font>==<br />
<font size='2'><br />
cd elphel393<br />
./check_versions.py root@192.168.0.9<br />
</font><br />
<br />
{|<br />
|[[File:Check versions.png|thumb|400px|check_versions.py output in terminal (web-393 revision on PC is ahead of the one installed on the camera)]]<br />
|}<br />
<br />
==<font color="blue">Details for development</font>==<br />
[[Development_for_10393|'''Development for 10393''']]</div>Andrey.filippovhttps://wiki.elphel.com/index.php?title=Poky_manual&diff=13112Poky manual2025-07-25T20:13:03Z<p>Andrey.filippov: </p>
<hr />
<div>==<font color="blue">Description</font>==<br />
Build the firmware for Elphel 10393 series camera systems from scratch.<br />
<br />
Prebuilt releases can be found [https://community.elphel.com/files/393/ here].<br />
<br />
==<font color="blue">Use cases</font>==<br />
* Update Linux Kernel when developing a driver<br />
* Include application to the default firmware package<br />
* Update Elphel's PHP extension<br />
* C/C++ applications if developed on PC require a cross-compiler and require Yocto installation or some other alternative.<br />
<br />
Other projects written in Python, PHP, Javascript, HTML, C/C++ (gcc is installed on the system board) can be developed on the camera. Installing the framework is not required but it can simplify the development process.<br />
<br />
==<font color="blue">Description</font>==<br />
<br />
* Building embedded Linux image for Zynq ARMv7 platform - Elphel 10393 board<br />
* Yocto Poky revision = 2.7.1 (Warrior) - <font color="green">builds in Kubuntu 20.04.</font> <font color="red">Older OSes are not supported. Roll back to get built in 16.04.</font><br />
* <s>Yocto Poky revision = 2.4 (Rocko) - <font color="green">builds in Kubuntu 16.04.</font> <font color="red">Won't build in 18.04 or 20.04.</font></s><br />
* <s>Yocto Poky revision = 2.0 (Jethro)</s><br />
<br />
==<font color="blue">Features</font>==<br />
* Environment is set up with a single script<br />
* All Elphel projects are configured for Eclipse IDE:<br />
** fpga projects (verilog)<br />
** kernel<br />
** applications projects<br />
* All steps for fpga projects are run from Eclipse IDE<br />
** Read about [http://blog.elphel.com/2016/05/tutorial-02-eclipse-based-fpga-development-environment-for-elphel-cameras/ setting up Eclipse based FPGA development]<br />
** [https://git.elphel.com/Elphel/vdt-plugin VDT Plugin repository]<br />
<br />
* Once everything is built it supports updating software projects (files and binaries) on the target system<br />
** access is set up in yocto's ''local.conf'' (see ''setup.py'' output) + ''ssh-copy-id''<br />
** ''bitbake some-app -c target_scp'' from the command line or Eclipse IDE - see examples in '''elphel-apps-...''' at [https://git.elphel.com/Elphel Git]<br />
<br />
==<font color="blue">Requirements</font>==<br />
* Kubuntu 20.04 x64<br />
* <s>Kubuntu 18.04 x64 (as of Dec 2018) - Poky: 2.7.1 Warrior (not tested but might build w/o problems)</s><br />
* <s>Kubuntu 16.04 x64 (as of Dec 2018) - Poky: 2.4 Rocko, 2.7.1 Warrior</s><br />
<br />
==<font color="blue">Output files</font>==<br />
The names are listed as they appear in the u-boot configuration header file - actual output files have different names:<br />
{| class="wikitable"<br />
|-<br />
! File(s)<br />
! Build Command<br />
! Description<br />
|-<br />
| <font color='darkblue'>'''boot.bin'''</font><br />
| ''bitbake u-boot''<br />
| u-boot as the first stage bootloader = Secondary Program Loader (SPL) that boots '''u-boot-dtb.img'''<br />
|-<br />
| <font color='darkblue'>'''u-boot-dtb.img'''</font><br />
| ''bitbake u-boot''<br />
| full size u-boot with a stripped device tree (''cat u-boot.img some_stripped_devicetree.dtb > u-boot-dtb.img'')<br />
|-<br />
|valign='top'| <font color='darkblue'>'''devicetree.dtb'''</font><br />
| bitbake device-tree<br />
| device tree with listed interfaces, zynq registers, interrupts and drivers<br />
* ''elphel393/bootable-images/mmc/devicetree.dtb'' - mount rootfs from mmc partition<br />
* ''elphel393/bootable-images/nand/devicetree.dtb'' - mount rootfs from NAND flash<br />
|-<br />
| <font color='darkblue'>'''uImage'''</font><br />
| ''bitbake linux-xlnx''<br />
| kernel, drivers<br />
|-<br />
| <font color='darkblue'>'''rootfs.ubifs''', '''rootfs.ubi''', '''rootfs.tar.gz'''</font><br />
| ''bitbake core-image-elphel393''<br />
| rootfs in different formats - *.ubi* for NAND, *.tar.gz for mmc<br />
|}<br />
<br />
The file are located at '''elphel393/bootable-images/''', which is a link to poky's deploy directory '''elphel393/poky/build/tmp/deploy/images/elphel393/'''<br />
<br />
* complete set of files for rootfs in NAND Flash: ''elphel393/bootable-images/nand/''<br />
* complete set of files for rootfs on MMC (micro SD card): ''elphel393/bootable-images/mmc/''<br />
<br />
==<font color="blue">Write files to media and boot</font>==<br />
===Boot from micro SD card===<br />
* Use recovery or regular &mu;SD card<br />
* EXT4 partition mounted as '''/'''<br />
[[Sd_boot_rootfs|Detailed instructions]]<br />
<br />
===Boot from NAND flash===<br />
* The default boot option - power on.<br />
* A UBIFS image is written to /dev/mtd4 - is mounted as '''/'''<br />
[[NAND_flash_boot_rootfs|Detailed instructions]]<br />
<br />
===Notes===<br />
* [[Boot_options_393|'''Read more''']] about boot options.<br />
<br />
==<font color="blue">Setup</font>==<br />
* Before building<br />
Installing some dependencies:<br />
sudo apt install git build-essential chrpath diffstat gawk texinfo zlib1g-dev python3-numpy libssl-dev<br />
Installing old python2.7 (bitbake snapshot that we used has problem with python3.8):<br />
sudo apt install python2.7<br />
sudo ln -s python2.7 python2<br />
sudo ln -s python2.7 python<br />
<br />
* Poky 2.7.1 Warrior (Kubuntu 20.04)<br />
<font size='2'><br />
git clone -b '''warrior''' https://git.elphel.com/Elphel/elphel393.git<br />
<br />
If you are a developer and plan to commit changes you should use ssh access instead: git clone -b warrior git@git.elphel.com:Elphel/elphel393.git . We never use non-developer mode ourselves, so it may malfunction.<br />
<br />
<br />
cd elphel393<br />
./setup.py<br />
cd poky<br />
. ./oe-init-build-env<br />
bitbake u-boot device-tree linux-xlnx core-image-elphel393<br />
</font><br />
<br />
* <s>Poky 2.4 Rocko (Kubuntu 16.04)<br />
<font size='2'><br />
git clone -b '''rocko''' https://git.elphel.com/Elphel/elphel393.git<br />
cd elphel393<br />
./setup.py<br />
cd poky<br />
. ./oe-init-build-env<br />
bitbake u-boot device-tree linux-xlnx core-image-elphel393<br />
<!--''Temporary: linux-xlnx in Rocko depends on branch 'lwir' for x393. Change in projects.json line 42 from 'master' to 'lwir'.''--><br />
</font></s><br />
<br />
* Notes (required actions are already listed above): When trying to run bitbake on a new install got problems with older bitbake version (current build uses specific snapshot) and python3.8. So I install old python2.7 and linked it:<br />
sudo apt install python2.7 python-numpy<br />
sudo ln -s python2.7 python2<br />
sudo ln -s python2.7 python<br />
<br />
After this bitbake just complained about missing tools (git, build-essential were already installed):<br />
<br />
sudo apt install chrpath diffstat gawk makeinfo<br />
<br />
Program test_mcntrl.py that builds x393.h header files from FPGA code that runs during ./setup.py requires numpy and results in error output if missing Still setup.py continues, you need to look through its output few lines after<br />
* x393<br />
git host: git.elphel.com<br />
Clone and checkout: x393<br />
<br />
You may install numpy with<br />
sudo apt install python3-numpy<br />
<br />
If you did not notice missing numpy, then during bitbake you will get error "build No rule to make target 'drivers/elphel/x393.o', needed by 'drivers/elphel/built-in.a'. Stop." in that case you need to install numpy, re-run setup.py (make sure numpy error is gone) then re-create linux kernel links during next build by erasing old ones:<br />
bitbake linux-xlnx -c clean<br />
and re-running<br />
bitbake linux-xlnx device-tree core-image-elphel393<br />
<br />
When building php: configure: error: zip support requires ZLIB. Use --with-zlib-dir=<DIR> to specify prefix where ZLIB include and library are located<br />
sudo apt install zlib1g-dev<br />
<br />
==<font color="blue">Compare '''built''' vs '''deployed''' software versions</font>==<br />
<font size='2'><br />
cd elphel393<br />
./check_versions.py root@192.168.0.9<br />
</font><br />
<br />
{|<br />
|[[File:Check versions.png|thumb|400px|check_versions.py output in terminal (web-393 revision on PC is ahead of the one installed on the camera)]]<br />
|}<br />
<br />
==<font color="blue">Details for development</font>==<br />
[[Development_for_10393|'''Development for 10393''']]</div>Andrey.filippovhttps://wiki.elphel.com/index.php?title=103891&diff=139741038912023-07-09T20:02:00Z<p>Andrey.filippov: Added A-D description</p>
<hr />
<div>103891 adapter board routes external sync I/O from the [[10389| 10389 interface board]] to the back panel 2.5mm barrel connector and provide 4-pic connector socket for 3.3V/5.0V fan. It is used in [[10393|Elphel 393 series cameras]]<br />
<br />
[[File:103891 top.jpeg|thumb|250px|Fig.1 top]]<br />
[[File:103891 bot.jpeg|thumb|250px|Fig.2 bot]]<br />
<br />
==Mechanical properties==<br />
* Dimensions: 58 x 38 x 9 mm (all connectors installed)<br />
* Weight: 3.0 g<br />
* Mechanical drawings and CAD files for the 103891 board: [[Elphel_camera_parts_0393-00#0393-00-23A_-_103891_rev_A_external_synchronization_and_fan_PCB_assembly|link]]<br />
<br />
{{Cad4a|0393-00-23A}}<br />
<br />
==Links==<br />
* [[10389|10389 board]]: interface board<br />
* [[Trigger_393]]: triggering NC393 camera<br />
* J2 connector: [http://www.digikey.com/product-detail/en/cui-inc/SJ1-42534-SMT-TR/CP1-42534SJTR-ND/659908 SJ1-42534-SMT-TR] ([http://www.cui.com/product/resource/sj1-4253x-smt-series.pdf datasheet])<br />
* Sync cable example: [http://www.digikey.com/product-detail/en/tensility-international-corp/10-00331/839-1029-ND/2350237 839-1029-ND]<br />
<br />
Connector provides high-current (up to 0.5A) dc-coupled 5V output and optoisolated I/O. When optoisolated pair is used used as an input (common use), external signal is applied between XSYNC1 (+) and XSYNC2(-). When the pair is used as an output (less common), external 5V power source should be connected in series with the receiver and 103891, so that "+" will be applied to XSYNC2, and "-" - to XSYNC1 (opposite to the input mode). Details are available in the circuit diagram of the [[10389]] board.<br />
<br />
Output synchronization can be just a pulse or carry additional timestamp data when used to synchronize multiple NC393 cameras. See [[Trigger_393]] for the settings. Pin A is the tip, B - next, then C and D is the closest to the connector housing.<br />
{| class='wikitable'<br />
|+Connector pinout<br />
|Name<br />
|Pin<br />
|Cable wire color<br />
|Description<br />
|-<br />
|XSYNC1<br />
|1 (D)<br />
|black<br />
|optoisolated, "+" input with respect to XSYNC2<br />
|-<br />
|SYNC_DRV<br />
|2 (A)<br />
|red<br />
|Sync output (DC-coupled), +5V pulses with respect to GND<br />
|-<br />
|GND<br />
|3 (B)<br />
|white<br />
|Output reference, connected to the camera system ground<br />
|-<br />
|XSYNC2<br />
|4 (C)<br />
|green<br />
|optoisolated, "-" input with respect to XSYNC1<br />
|}<br />
* [[Trigger_393#Internal_periodic_trigger_.284_fps.2C_from_fpga_generator.29_.2B_output_the_signal_to_external_port|How to output trigger signal to external port]]<br />
* [[Media:103891a.pdf|103891 Rev "A" Circuit Diagram, Parts List, PCB layout]]<br />
* [[Media:103891a gerber.tar.gz|103891 Rev "A" Gerber files]]<br />
<br />
[[Category:Boards 393]]</div>Andrey.filippovhttps://wiki.elphel.com/index.php?title=103891&diff=139731038912023-07-09T20:00:35Z<p>Andrey.filippov: Added A-B-C-D</p>
<hr />
<div>103891 adapter board routes external sync I/O from the [[10389| 10389 interface board]] to the back panel 2.5mm barrel connector and provide 4-pic connector socket for 3.3V/5.0V fan. It is used in [[10393|Elphel 393 series cameras]]<br />
<br />
[[File:103891 top.jpeg|thumb|250px|Fig.1 top]]<br />
[[File:103891 bot.jpeg|thumb|250px|Fig.2 bot]]<br />
<br />
==Mechanical properties==<br />
* Dimensions: 58 x 38 x 9 mm (all connectors installed)<br />
* Weight: 3.0 g<br />
* Mechanical drawings and CAD files for the 103891 board: [[Elphel_camera_parts_0393-00#0393-00-23A_-_103891_rev_A_external_synchronization_and_fan_PCB_assembly|link]]<br />
<br />
{{Cad4a|0393-00-23A}}<br />
<br />
==Links==<br />
* [[10389|10389 board]]: interface board<br />
* [[Trigger_393]]: triggering NC393 camera<br />
* J2 connector: [http://www.digikey.com/product-detail/en/cui-inc/SJ1-42534-SMT-TR/CP1-42534SJTR-ND/659908 SJ1-42534-SMT-TR] ([http://www.cui.com/product/resource/sj1-4253x-smt-series.pdf datasheet])<br />
* Sync cable example: [http://www.digikey.com/product-detail/en/tensility-international-corp/10-00331/839-1029-ND/2350237 839-1029-ND]<br />
<br />
Connector provides high-current (up to 0.5A) dc-coupled 5V output and optoisolated I/O. When optoisolated pair is used used as an input (common use), external signal is applied between XSYNC1 (+) and XSYNC2(-). When the pair is used as an output (less common), external 5V power source should be connected in series with the receiver and 103891, so that "+" will be applied to XSYNC2, and "-" - to XSYNC1 (opposite to the input mode). Details are available in the circuit diagram of the [[10389]] board.<br />
<br />
Output synchronization can be just a pulse or carry additional timestamp data when used to synchronize multiple NC393 cameras. See [[Trigger_393]] for the settings.<br />
{| class='wikitable'<br />
|+Connector pinout<br />
|Name<br />
|Pin<br />
|Cable wire color<br />
|Description<br />
|-<br />
|XSYNC1<br />
|1 (D)<br />
|black<br />
|optoisolated, "+" input with respect to XSYNC2<br />
|-<br />
|SYNC_DRV<br />
|2 (A)<br />
|red<br />
|Sync output (DC-coupled), +5V pulses with respect to GND<br />
|-<br />
|GND<br />
|3 (B)<br />
|white<br />
|Output reference, connected to the camera system ground<br />
|-<br />
|XSYNC2<br />
|4 (C)<br />
|green<br />
|optoisolated, "-" input with respect to XSYNC1<br />
|}<br />
* [[Trigger_393#Internal_periodic_trigger_.284_fps.2C_from_fpga_generator.29_.2B_output_the_signal_to_external_port|How to output trigger signal to external port]]<br />
* [[Media:103891a.pdf|103891 Rev "A" Circuit Diagram, Parts List, PCB layout]]<br />
* [[Media:103891a gerber.tar.gz|103891 Rev "A" Gerber files]]<br />
<br />
[[Category:Boards 393]]</div>Andrey.filippovhttps://wiki.elphel.com/index.php?title=Poky_manual&diff=13111Poky manual2022-06-01T19:22:15Z<p>Andrey.filippov: /* Setup */</p>
<hr />
<div>==<font color="blue">Description</font>==<br />
Build the firmware for Elphel 10393 series camera systems from scratch.<br />
<br />
Prebuilt releases can be found [https://community.elphel.com/files/393/ here].<br />
<br />
==<font color="blue">Use cases</font>==<br />
* Update Linux Kernel when developing a driver<br />
* Include application to the default firmware package<br />
* Update Elphel's PHP extension<br />
* C/C++ applications if developed on PC require a cross-compiler and require Yocto installation or some other alternative.<br />
<br />
Other projects written in Python, PHP, Javascript, HTML, C/C++ (gcc is installed on the system board) can be developed on the camera. Installing the framework is not required but it can simplify the development process.<br />
<br />
==<font color="blue">Description</font>==<br />
<br />
* Building embedded Linux image for Zynq ARMv7 platform - Elphel 10393 board<br />
* Yocto Poky revision = 2.7.1 (Warrior) - <font color="green">builds in Kubuntu 20.04.</font> <font color="red">Older OSes are not supported. Roll back to get built in 16.04.</font><br />
* <s>Yocto Poky revision = 2.4 (Rocko) - <font color="green">builds in Kubuntu 16.04.</font> <font color="red">Won't build in 18.04 or 20.04.</font></s><br />
* <s>Yocto Poky revision = 2.0 (Jethro)</s><br />
<br />
==<font color="blue">Features</font>==<br />
* Environment is set up with a single script<br />
* All Elphel projects are configured for Eclipse IDE:<br />
** fpga projects (verilog)<br />
** kernel<br />
** applications projects<br />
* All steps for fpga projects are run from Eclipse IDE<br />
** Read about [http://blog.elphel.com/2016/05/tutorial-02-eclipse-based-fpga-development-environment-for-elphel-cameras/ setting up Eclipse based FPGA development]<br />
** [https://git.elphel.com/Elphel/vdt-plugin VDT Plugin repository]<br />
<br />
* Once everything is built it supports updating software projects (files and binaries) on the target system<br />
** access is set up in yocto's ''local.conf'' (see ''setup.py'' output) + ''ssh-copy-id''<br />
** ''bitbake some-app -c target_scp'' from the command line or Eclipse IDE - see examples in '''elphel-apps-...''' at [https://git.elphel.com/Elphel Git]<br />
<br />
==<font color="blue">Requirements</font>==<br />
* Kubuntu 20.04 x64<br />
* <s>Kubuntu 18.04 x64 (as of Dec 2018) - Poky: 2.7.1 Warrior (not tested but might build w/o problems)</s><br />
* <s>Kubuntu 16.04 x64 (as of Dec 2018) - Poky: 2.4 Rocko, 2.7.1 Warrior</s><br />
<br />
==<font color="blue">Output files</font>==<br />
The names are listed as they appear in the u-boot configuration header file - actual output files have different names:<br />
{| class="wikitable"<br />
|-<br />
! File(s)<br />
! Build Command<br />
! Description<br />
|-<br />
| <font color='darkblue'>'''boot.bin'''</font><br />
| ''bitbake u-boot''<br />
| u-boot as the first stage bootloader = Secondary Program Loader (SPL) that boots '''u-boot-dtb.img'''<br />
|-<br />
| <font color='darkblue'>'''u-boot-dtb.img'''</font><br />
| ''bitbake u-boot''<br />
| full size u-boot with a stripped device tree (''cat u-boot.img some_stripped_devicetree.dtb > u-boot-dtb.img'')<br />
|-<br />
|valign='top'| <font color='darkblue'>'''devicetree.dtb'''</font><br />
| bitbake device-tree<br />
| device tree with listed interfaces, zynq registers, interrupts and drivers<br />
* ''elphel393/bootable-images/mmc/devicetree.dtb'' - mount rootfs from mmc partition<br />
* ''elphel393/bootable-images/nand/devicetree.dtb'' - mount rootfs from NAND flash<br />
|-<br />
| <font color='darkblue'>'''uImage'''</font><br />
| ''bitbake linux-xlnx''<br />
| kernel, drivers<br />
|-<br />
| <font color='darkblue'>'''rootfs.ubifs''', '''rootfs.ubi''', '''rootfs.tar.gz'''</font><br />
| ''bitbake core-image-elphel393''<br />
| rootfs in different formats - *.ubi* for NAND, *.tar.gz for mmc<br />
|}<br />
<br />
The file are located at '''elphel393/bootable-images/''', which is a link to poky's deploy directory '''elphel393/poky/build/tmp/deploy/images/elphel393/'''<br />
<br />
* complete set of files for rootfs in NAND Flash: ''elphel393/bootable-images/nand/''<br />
* complete set of files for rootfs on MMC (micro SD card): ''elphel393/bootable-images/mmc/''<br />
<br />
==<font color="blue">Write files to media and boot</font>==<br />
===Boot from micro SD card===<br />
* Use recovery or regular &mu;SD card<br />
* EXT4 partition mounted as '''/'''<br />
[[Sd_boot_rootfs|Detailed instructions]]<br />
<br />
===Boot from NAND flash===<br />
* The default boot option - power on.<br />
* A UBIFS image is written to /dev/mtd4 - is mounted as '''/'''<br />
[[NAND_flash_boot_rootfs|Detailed instructions]]<br />
<br />
===Notes===<br />
* [[Boot_options_393|'''Read more''']] about boot options.<br />
<br />
==<font color="blue">Setup</font>==<br />
* Before building<br />
Installing some dependencies:<br />
sudo apt install git build-essential chrpath diffstat gawk texinfo zlib1g-dev python3-numpy libssl-dev<br />
Installing old python2.7 (bitbake snapshot that we used has problem with python3.8):<br />
sudo apt install python2.7<br />
sudo ln -s python2.7 python2<br />
sudo ln -s python2.7 python<br />
<br />
* Poky 2.7.1 Warrior (Kubuntu 20.04)<br />
<font size='2'><br />
git clone -b '''warrior''' https://git.elphel.com/Elphel/elphel393.git<br />
<br />
If you are a developer and plan to commit changes you should use ssh access instead: git clone -b warrior git@git.elphel.com:Elphel/elphel393.git<br />
<br />
<br />
cd elphel393<br />
./setup.py<br />
cd poky<br />
. ./oe-init-build-env<br />
bitbake u-boot device-tree linux-xlnx core-image-elphel393<br />
</font><br />
<br />
* <s>Poky 2.4 Rocko (Kubuntu 16.04)<br />
<font size='2'><br />
git clone -b '''rocko''' https://git.elphel.com/Elphel/elphel393.git<br />
cd elphel393<br />
./setup.py<br />
cd poky<br />
. ./oe-init-build-env<br />
bitbake u-boot device-tree linux-xlnx core-image-elphel393<br />
<!--''Temporary: linux-xlnx in Rocko depends on branch 'lwir' for x393. Change in projects.json line 42 from 'master' to 'lwir'.''--><br />
</font></s><br />
<br />
* Notes (required actions are already listed above): When trying to run bitbake on a new install got problems with older bitbake version (current build uses specific snapshot) and python3.8. So I install old python2.7 and linked it:<br />
sudo apt install python2.7 python-numpy<br />
sudo ln -s python2.7 python2<br />
sudo ln -s python2.7 python<br />
<br />
After this bitbake just complained about missing tools (git, build-essential were already installed):<br />
<br />
sudo apt install chrpath diffstat gawk makeinfo<br />
<br />
Program test_mcntrl.py that builds x393.h header files from FPGA code that runs during ./setup.py requires numpy and results in error output if missing Still setup.py continues, you need to look through its output few lines after<br />
* x393<br />
git host: git.elphel.com<br />
Clone and checkout: x393<br />
<br />
You may install numpy with<br />
sudo apt install python3-numpy<br />
<br />
If you did not notice missing numpy, then during bitbake you will get error "build No rule to make target 'drivers/elphel/x393.o', needed by 'drivers/elphel/built-in.a'. Stop." in that case you need to install numpy, re-run setup.py (make sure numpy error is gone) then re-create linux kernel links during next build by erasing old ones:<br />
bitbake linux-xlnx -c clean<br />
and re-running<br />
bitbake linux-xlnx device-tree core-image-elphel393<br />
<br />
When building php: configure: error: zip support requires ZLIB. Use --with-zlib-dir=<DIR> to specify prefix where ZLIB include and library are located<br />
sudo apt install zlib1g-dev<br />
<br />
==<font color="blue">Compare '''built''' vs '''deployed''' software versions</font>==<br />
<font size='2'><br />
cd elphel393<br />
./check_versions.py root@192.168.0.9<br />
</font><br />
<br />
{|<br />
|[[File:Check versions.png|thumb|400px|check_versions.py output in terminal (web-393 revision on PC is ahead of the one installed on the camera)]]<br />
|}<br />
<br />
==<font color="blue">Details for development</font>==<br />
[[Development_for_10393|'''Development for 10393''']]</div>Andrey.filippovhttps://wiki.elphel.com/index.php?title=Poky_manual&diff=13110Poky manual2022-06-01T17:18:29Z<p>Andrey.filippov: /* Setup */</p>
<hr />
<div>==<font color="blue">Description</font>==<br />
Build the firmware for Elphel 10393 series camera systems from scratch.<br />
<br />
Prebuilt releases can be found [https://community.elphel.com/files/393/ here].<br />
<br />
==<font color="blue">Use cases</font>==<br />
* Update Linux Kernel when developing a driver<br />
* Include application to the default firmware package<br />
* Update Elphel's PHP extension<br />
* C/C++ applications if developed on PC require a cross-compiler and require Yocto installation or some other alternative.<br />
<br />
Other projects written in Python, PHP, Javascript, HTML, C/C++ (gcc is installed on the system board) can be developed on the camera. Installing the framework is not required but it can simplify the development process.<br />
<br />
==<font color="blue">Description</font>==<br />
<br />
* Building embedded Linux image for Zynq ARMv7 platform - Elphel 10393 board<br />
* Yocto Poky revision = 2.7.1 (Warrior) - <font color="green">builds in Kubuntu 20.04.</font> <font color="red">Older OSes are not supported. Roll back to get built in 16.04.</font><br />
* <s>Yocto Poky revision = 2.4 (Rocko) - <font color="green">builds in Kubuntu 16.04.</font> <font color="red">Won't build in 18.04 or 20.04.</font></s><br />
* <s>Yocto Poky revision = 2.0 (Jethro)</s><br />
<br />
==<font color="blue">Features</font>==<br />
* Environment is set up with a single script<br />
* All Elphel projects are configured for Eclipse IDE:<br />
** fpga projects (verilog)<br />
** kernel<br />
** applications projects<br />
* All steps for fpga projects are run from Eclipse IDE<br />
** Read about [http://blog.elphel.com/2016/05/tutorial-02-eclipse-based-fpga-development-environment-for-elphel-cameras/ setting up Eclipse based FPGA development]<br />
** [https://git.elphel.com/Elphel/vdt-plugin VDT Plugin repository]<br />
<br />
* Once everything is built it supports updating software projects (files and binaries) on the target system<br />
** access is set up in yocto's ''local.conf'' (see ''setup.py'' output) + ''ssh-copy-id''<br />
** ''bitbake some-app -c target_scp'' from the command line or Eclipse IDE - see examples in '''elphel-apps-...''' at [https://git.elphel.com/Elphel Git]<br />
<br />
==<font color="blue">Requirements</font>==<br />
* Kubuntu 20.04 x64<br />
* <s>Kubuntu 18.04 x64 (as of Dec 2018) - Poky: 2.7.1 Warrior (not tested but might build w/o problems)</s><br />
* <s>Kubuntu 16.04 x64 (as of Dec 2018) - Poky: 2.4 Rocko, 2.7.1 Warrior</s><br />
<br />
==<font color="blue">Output files</font>==<br />
The names are listed as they appear in the u-boot configuration header file - actual output files have different names:<br />
{| class="wikitable"<br />
|-<br />
! File(s)<br />
! Build Command<br />
! Description<br />
|-<br />
| <font color='darkblue'>'''boot.bin'''</font><br />
| ''bitbake u-boot''<br />
| u-boot as the first stage bootloader = Secondary Program Loader (SPL) that boots '''u-boot-dtb.img'''<br />
|-<br />
| <font color='darkblue'>'''u-boot-dtb.img'''</font><br />
| ''bitbake u-boot''<br />
| full size u-boot with a stripped device tree (''cat u-boot.img some_stripped_devicetree.dtb > u-boot-dtb.img'')<br />
|-<br />
|valign='top'| <font color='darkblue'>'''devicetree.dtb'''</font><br />
| bitbake device-tree<br />
| device tree with listed interfaces, zynq registers, interrupts and drivers<br />
* ''elphel393/bootable-images/mmc/devicetree.dtb'' - mount rootfs from mmc partition<br />
* ''elphel393/bootable-images/nand/devicetree.dtb'' - mount rootfs from NAND flash<br />
|-<br />
| <font color='darkblue'>'''uImage'''</font><br />
| ''bitbake linux-xlnx''<br />
| kernel, drivers<br />
|-<br />
| <font color='darkblue'>'''rootfs.ubifs''', '''rootfs.ubi''', '''rootfs.tar.gz'''</font><br />
| ''bitbake core-image-elphel393''<br />
| rootfs in different formats - *.ubi* for NAND, *.tar.gz for mmc<br />
|}<br />
<br />
The file are located at '''elphel393/bootable-images/''', which is a link to poky's deploy directory '''elphel393/poky/build/tmp/deploy/images/elphel393/'''<br />
<br />
* complete set of files for rootfs in NAND Flash: ''elphel393/bootable-images/nand/''<br />
* complete set of files for rootfs on MMC (micro SD card): ''elphel393/bootable-images/mmc/''<br />
<br />
==<font color="blue">Write files to media and boot</font>==<br />
===Boot from micro SD card===<br />
* Use recovery or regular &mu;SD card<br />
* EXT4 partition mounted as '''/'''<br />
[[Sd_boot_rootfs|Detailed instructions]]<br />
<br />
===Boot from NAND flash===<br />
* The default boot option - power on.<br />
* A UBIFS image is written to /dev/mtd4 - is mounted as '''/'''<br />
[[NAND_flash_boot_rootfs|Detailed instructions]]<br />
<br />
===Notes===<br />
* [[Boot_options_393|'''Read more''']] about boot options.<br />
<br />
==<font color="blue">Setup</font>==<br />
* Before building<br />
Installing some dependencies:<br />
sudo apt install git build-essential chrpath diffstat gawk texinfo zlib1g-dev python3-numpy<br />
Installing old python2.7 (bitbake snapshot that we used has problem with python3.8):<br />
sudo apt install python2.7<br />
sudo ln -s python2.7 python2<br />
sudo ln -s python2.7 python<br />
<br />
* Poky 2.7.1 Warrior (Kubuntu 20.04)<br />
<font size='2'><br />
git clone -b '''warrior''' https://git.elphel.com/Elphel/elphel393.git<br />
<br />
If you are a developer and plan to commit changes you should use ssh access instead: git clone -b warrior git@git.elphel.com:Elphel/elphel393.git<br />
<br />
<br />
cd elphel393<br />
./setup.py<br />
cd poky<br />
. ./oe-init-build-env<br />
bitbake u-boot device-tree linux-xlnx core-image-elphel393<br />
</font><br />
<br />
* <s>Poky 2.4 Rocko (Kubuntu 16.04)<br />
<font size='2'><br />
git clone -b '''rocko''' https://git.elphel.com/Elphel/elphel393.git<br />
cd elphel393<br />
./setup.py<br />
cd poky<br />
. ./oe-init-build-env<br />
bitbake u-boot device-tree linux-xlnx core-image-elphel393<br />
<!--''Temporary: linux-xlnx in Rocko depends on branch 'lwir' for x393. Change in projects.json line 42 from 'master' to 'lwir'.''--><br />
</font></s><br />
<br />
* Notes (required actions are already listed above): When trying to run bitbake on a new install got problems with older bitbake version (current build uses specific snapshot) and python3.8. So I install old python2.7 and linked it:<br />
sudo apt install python2.7 python-numpy<br />
sudo ln -s python2.7 python2<br />
sudo ln -s python2.7 python<br />
<br />
After this bitbake just complained about missing tools (git, build-essential were already installed):<br />
<br />
sudo apt install chrpath diffstat gawk makeinfo<br />
<br />
Program test_mcntrl.py that builds x393.h header files from FPGA code that runs during ./setup.py requires numpy and results in error output if missing Still setup.py continues, you need to look through its output few lines after<br />
* x393<br />
git host: git.elphel.com<br />
Clone and checkout: x393<br />
<br />
You may install numpy with<br />
sudo apt install python3-numpy<br />
<br />
If you did not notice missing numpy, then during bitbake you will get error "build No rule to make target 'drivers/elphel/x393.o', needed by 'drivers/elphel/built-in.a'. Stop." in that case you need to install numpy, re-run setup.py (make sure numpy error is gone) then re-create linux kernel links during next build by erasing old ones:<br />
bitbake linux-xlnx -c clean<br />
and re-running<br />
bitbake linux-xlnx device-tree core-image-elphel393<br />
<br />
When building php: configure: error: zip support requires ZLIB. Use --with-zlib-dir=<DIR> to specify prefix where ZLIB include and library are located<br />
sudo apt install zlib1g-dev<br />
<br />
==<font color="blue">Compare '''built''' vs '''deployed''' software versions</font>==<br />
<font size='2'><br />
cd elphel393<br />
./check_versions.py root@192.168.0.9<br />
</font><br />
<br />
{|<br />
|[[File:Check versions.png|thumb|400px|check_versions.py output in terminal (web-393 revision on PC is ahead of the one installed on the camera)]]<br />
|}<br />
<br />
==<font color="blue">Details for development</font>==<br />
[[Development_for_10393|'''Development for 10393''']]</div>Andrey.filippovhttps://wiki.elphel.com/index.php?title=Poky_manual&diff=13109Poky manual2022-06-01T16:59:57Z<p>Andrey.filippov: /* Setup */</p>
<hr />
<div>==<font color="blue">Description</font>==<br />
Build the firmware for Elphel 10393 series camera systems from scratch.<br />
<br />
Prebuilt releases can be found [https://community.elphel.com/files/393/ here].<br />
<br />
==<font color="blue">Use cases</font>==<br />
* Update Linux Kernel when developing a driver<br />
* Include application to the default firmware package<br />
* Update Elphel's PHP extension<br />
* C/C++ applications if developed on PC require a cross-compiler and require Yocto installation or some other alternative.<br />
<br />
Other projects written in Python, PHP, Javascript, HTML, C/C++ (gcc is installed on the system board) can be developed on the camera. Installing the framework is not required but it can simplify the development process.<br />
<br />
==<font color="blue">Description</font>==<br />
<br />
* Building embedded Linux image for Zynq ARMv7 platform - Elphel 10393 board<br />
* Yocto Poky revision = 2.7.1 (Warrior) - <font color="green">builds in Kubuntu 20.04.</font> <font color="red">Older OSes are not supported. Roll back to get built in 16.04.</font><br />
* <s>Yocto Poky revision = 2.4 (Rocko) - <font color="green">builds in Kubuntu 16.04.</font> <font color="red">Won't build in 18.04 or 20.04.</font></s><br />
* <s>Yocto Poky revision = 2.0 (Jethro)</s><br />
<br />
==<font color="blue">Features</font>==<br />
* Environment is set up with a single script<br />
* All Elphel projects are configured for Eclipse IDE:<br />
** fpga projects (verilog)<br />
** kernel<br />
** applications projects<br />
* All steps for fpga projects are run from Eclipse IDE<br />
** Read about [http://blog.elphel.com/2016/05/tutorial-02-eclipse-based-fpga-development-environment-for-elphel-cameras/ setting up Eclipse based FPGA development]<br />
** [https://git.elphel.com/Elphel/vdt-plugin VDT Plugin repository]<br />
<br />
* Once everything is built it supports updating software projects (files and binaries) on the target system<br />
** access is set up in yocto's ''local.conf'' (see ''setup.py'' output) + ''ssh-copy-id''<br />
** ''bitbake some-app -c target_scp'' from the command line or Eclipse IDE - see examples in '''elphel-apps-...''' at [https://git.elphel.com/Elphel Git]<br />
<br />
==<font color="blue">Requirements</font>==<br />
* Kubuntu 20.04 x64<br />
* <s>Kubuntu 18.04 x64 (as of Dec 2018) - Poky: 2.7.1 Warrior (not tested but might build w/o problems)</s><br />
* <s>Kubuntu 16.04 x64 (as of Dec 2018) - Poky: 2.4 Rocko, 2.7.1 Warrior</s><br />
<br />
==<font color="blue">Output files</font>==<br />
The names are listed as they appear in the u-boot configuration header file - actual output files have different names:<br />
{| class="wikitable"<br />
|-<br />
! File(s)<br />
! Build Command<br />
! Description<br />
|-<br />
| <font color='darkblue'>'''boot.bin'''</font><br />
| ''bitbake u-boot''<br />
| u-boot as the first stage bootloader = Secondary Program Loader (SPL) that boots '''u-boot-dtb.img'''<br />
|-<br />
| <font color='darkblue'>'''u-boot-dtb.img'''</font><br />
| ''bitbake u-boot''<br />
| full size u-boot with a stripped device tree (''cat u-boot.img some_stripped_devicetree.dtb > u-boot-dtb.img'')<br />
|-<br />
|valign='top'| <font color='darkblue'>'''devicetree.dtb'''</font><br />
| bitbake device-tree<br />
| device tree with listed interfaces, zynq registers, interrupts and drivers<br />
* ''elphel393/bootable-images/mmc/devicetree.dtb'' - mount rootfs from mmc partition<br />
* ''elphel393/bootable-images/nand/devicetree.dtb'' - mount rootfs from NAND flash<br />
|-<br />
| <font color='darkblue'>'''uImage'''</font><br />
| ''bitbake linux-xlnx''<br />
| kernel, drivers<br />
|-<br />
| <font color='darkblue'>'''rootfs.ubifs''', '''rootfs.ubi''', '''rootfs.tar.gz'''</font><br />
| ''bitbake core-image-elphel393''<br />
| rootfs in different formats - *.ubi* for NAND, *.tar.gz for mmc<br />
|}<br />
<br />
The file are located at '''elphel393/bootable-images/''', which is a link to poky's deploy directory '''elphel393/poky/build/tmp/deploy/images/elphel393/'''<br />
<br />
* complete set of files for rootfs in NAND Flash: ''elphel393/bootable-images/nand/''<br />
* complete set of files for rootfs on MMC (micro SD card): ''elphel393/bootable-images/mmc/''<br />
<br />
==<font color="blue">Write files to media and boot</font>==<br />
===Boot from micro SD card===<br />
* Use recovery or regular &mu;SD card<br />
* EXT4 partition mounted as '''/'''<br />
[[Sd_boot_rootfs|Detailed instructions]]<br />
<br />
===Boot from NAND flash===<br />
* The default boot option - power on.<br />
* A UBIFS image is written to /dev/mtd4 - is mounted as '''/'''<br />
[[NAND_flash_boot_rootfs|Detailed instructions]]<br />
<br />
===Notes===<br />
* [[Boot_options_393|'''Read more''']] about boot options.<br />
<br />
==<font color="blue">Setup</font>==<br />
* Before building<br />
Installing some dependencies:<br />
sudo apt install git build-essential chrpath diffstat gawk texinfo zlib1g-dev python3-numpy<br />
Installing old python2.7 (bitbake snapshot that we used has problem with python3.8):<br />
sudo apt install python2.7<br />
sudo ln -s python2.7 python2<br />
sudo ln -s python2.7 python<br />
<br />
* Poky 2.7.1 Warrior (Kubuntu 20.04)<br />
<font size='2'><br />
git clone -b '''warrior''' https://git.elphel.com/Elphel/elphel393.git<br />
<br />
If you are a developer and plan to commit changes you should use ssh access instead: git clone -b warrior git@git.elphel.com:Elphel/elphel393.git<br />
<br />
<br />
cd elphel393<br />
./setup.py<br />
cd poky<br />
. ./oe-init-build-env<br />
bitbake u-boot device-tree linux-xlnx core-image-elphel393<br />
</font><br />
<br />
* <s>Poky 2.4 Rocko (Kubuntu 16.04)<br />
<font size='2'><br />
git clone -b '''rocko''' https://git.elphel.com/Elphel/elphel393.git<br />
cd elphel393<br />
./setup.py<br />
cd poky<br />
. ./oe-init-build-env<br />
bitbake u-boot device-tree linux-xlnx core-image-elphel393<br />
<!--''Temporary: linux-xlnx in Rocko depends on branch 'lwir' for x393. Change in projects.json line 42 from 'master' to 'lwir'.''--><br />
</font></s><br />
<br />
* Notes (required actions are already listed above): When trying to run bitbake on a new install got problems with older bitbake version (current build uses specific snapshot) and python3.8. So I install old python2.7 and linked it:<br />
sudo apt install python2.7<br />
sudo ln -s python2.7 python2<br />
sudo ln -s python2.7 python<br />
<br />
After this bitbake just complained about missing tools (git, build-essential were already installed):<br />
<br />
sudo apt install chrpath diffstat gawk makeinfo<br />
<br />
Program test_mcntrl.py that builds x393.h header files from FPGA code that runs during ./setup.py requires numpy and results in error output if missing Still setup.py continues, you need to look through its output few lines after<br />
* x393<br />
git host: git.elphel.com<br />
Clone and checkout: x393<br />
<br />
You may install numpy with<br />
sudo apt install python3-numpy<br />
<br />
If you did not notice missing numpy, then during bitbake you will get error "build No rule to make target 'drivers/elphel/x393.o', needed by 'drivers/elphel/built-in.a'. Stop." in that case you need to install numpy, re-run setup.py (make sure numpy error is gone) then re-create linux kernel links during next build by erasing old ones:<br />
bitbake linux-xlnx -c clean<br />
and re-running<br />
bitbake linux-xlnx device-tree core-image-elphel393<br />
<br />
When building php: configure: error: zip support requires ZLIB. Use --with-zlib-dir=<DIR> to specify prefix where ZLIB include and library are located<br />
sudo apt install zlib1g-dev<br />
<br />
==<font color="blue">Compare '''built''' vs '''deployed''' software versions</font>==<br />
<font size='2'><br />
cd elphel393<br />
./check_versions.py root@192.168.0.9<br />
</font><br />
<br />
{|<br />
|[[File:Check versions.png|thumb|400px|check_versions.py output in terminal (web-393 revision on PC is ahead of the one installed on the camera)]]<br />
|}<br />
<br />
==<font color="blue">Details for development</font>==<br />
[[Development_for_10393|'''Development for 10393''']]</div>Andrey.filippovhttps://wiki.elphel.com/index.php?title=Adjusting_sensor_clock_phase&diff=2937Adjusting sensor clock phase2022-05-01T22:06:14Z<p>Andrey.filippov: /* Software interface for adjusting the sensor clock phase (firmware 8.0.x) */</p>
<hr />
<div>=== Elphel cameras architecture - separate computer and sensor boards ===<br />
Elphel cameras are designed so they can support multiple different sensors, including those that were not available when the particular camera model was first released. That is possible, because the camera functionality is split into the sensor-independent computer (see [[10353]]) and the sensor front end. This board is very simple for the CMOS images sensors, like [[10338]] - basically it includes just the image sensor itself, connector for the cable to the camera main board and the power conditioning circuitry. In other cameras (like Model 363) the high resolution CCD-based sensor front end is much more complex ([[10347]]+[[10342]]), but they all interface the main board through the 30-conductor flex cable that on the [[10353]] side is connected directly to the FPGA pins (all but power supply/ ground pins). That makes the interface universal, as functions of the FPGA pins can be changed with just a new code, no hardware changes are needed.<br />
<br />
=== Inter-board cable ===<br />
The inter-board connection is made of the flex cables (that are available in different length) provide freedom in mutual orientation of the main boards and the sensor front end, allowing the smaller sensor board to get into the tight spaces. But that 30-conductor cable has not enough conductors to make nice transmission lines - there is not enough of the return wires, number of ground+power lines is much less than the number of signal ones, but that is not a big issue for most camera applications where the cable is really short - less than 2 inches (50mm) long, but still the signals (in 5MPix sensor the output 12-bit data has a 96 mpix/sec, the clock lines run at 96MHz both directions) are used with reduced drive strength to reduce the EMI. Fortunately both FPGA and the sensor allow control over the drive strength. With the low output currents on the pins, it takes some time to recharge the parasitic capacitance of the cable wires, and the signals look far from "digital" rectangular shape - it takes most of the pixel period to just transition from "0" to "1" or back from "1" to "0", so the data on the other end should be sampled at a precise moment during each pixel period.<br />
<br />
=== Phase shift of the sensor clock input ===<br />
In the camera it is achieved by adding controlled phase shift between the clock that synchronizes operation of the sensor-related portion of the FPGA and the clock signal that is sent to the sensor. The sensor output signals have certain delay from that clock (unfortunately in 5MPix sensor that delay is very different for the pixel data and sync signals), so by varying the phase of a clock to sensor it is possible to adjust phase of the sensor data with respect to the FPGA pixel clock. The sensor pixel output clock is not used - it is more convenient when the FPGA clock does not depend on the state of the sensor. But that sensor output clock is connected to the FPGA and is sampled at different phases of the FPGA clock - that data can (and will) be used for the automatic phase adjustment, but current software does not support that yet.<br />
<br />
=== Effect of different cable lengths ===<br />
For the standard camera configuration the phase shift is programmed as a predefined constant, but that does not work when the cable length differs from the original one. If you try the camera with different cable length you may see image that looks like monochrome or purple - if the pixels are sampled at wrong time, red and green (also green and blue) pixels can swap, you may see horizontal lines when the sample moment is close to the pixel-to-pixel transition - in some lines pixels were sampled correctly, in some - colors are swapped (and remember - each pixel is represented by individual 12 bit lines, that can have slightly different delays to the clock). For some reasonable length cables (tested with 8" / 200mm) it is possible to re-adjust the phase shift, sample pixels in the middle of the pixel window and so restore the nice images.<br />
<br />
=== On-chip DCM (Digital Clock Management) for sensor clock phase adjustment ===<br />
Sensor phase control in the camera is achieved with one of the FPGA on-chip DCM (digital clock management) blocks by combining the fine phase adjustment with 4-to-1 multiplexor switching between on of the four outputs shifted by 90 degrees. The fine shift is not precisely known, for these chips it is specified in the 20-40 ps/step, while guaranteed number of phase shift steps (for 96MHz clock) is +/- 140 (so more than +/- 90 degrees in the worst case.<br />
<br />
=== Software interface for adjusting the sensor clock phase (firmware 8.0.x) ===<br />
Open the following URL in the browser (replace 192.168.0.9 if camera has different IP):<br />
<br />
[http://192.168.0.9/parsedit.php?embed=0.25&title=Parameters+for+groups:+phase&SENSOR_PHASE&SENSOR_REGS7&SENSOR_REGS7__0310&SENSOR_REGS7__0307&WOI_HEIGHT&WB_EN&THIS_FRAME http://192.168.0.9/parsedit.php?embed=0.25&title=Parameters+for+groups:+phase&SENSOR_PHASE&SENSOR_REGS7&SENSOR_REGS7__0310&SENSOR_REGS7__0307&WOI_HEIGHT&WB_EN&THIS_FRAME]<br />
<br />
That page combines several controls:<br />
*SENSOR_PHASE - phase shift between the FPGA pixel clock and the sensor pixel clock. Normal adjustment range is 0xff80 (-64) to 0x0080 (+64)<br />
*SENSOR_REGS7 - sensor register #7 that, among others control drive strengths of the sensor output. It is safer to modify selected bit fields of this register:<br />
*SENSOR_REGS7__0307 (bits 9:7) is the drive strength of clock output (not used in the current setup)<br />
*SENSOR_REGS7__0310 (bits 12:10) is the drive strength of all other outputs - pixel data, horizontal and vertical sync<br />
*WOI_HEIGHT - window if interest height is not related to sensor phase adjustment, but it can be used to restore system (sensor to FPGA) synchronization after it is lost when adjusting sensor phase (that involves restarting the sensor). Just reduce/increase it by 0x10 and press "refresh" button - that should restore the "broken" image caused by losing system sync.<br />
<br />
When you change phase and press "apply" the image would not reflect the new settings (changing phase requires complete sensor reset and the regular image acquisition sequence is aborted), so the following sequence is recommended:<br />
#modify SENSOR_PHASE value<br />
#press "apply"<br />
#change WOI_HEIGHT (alternate between 0x790 and 0x780 for the full frame)<br />
#press "apply"<br />
#monitor image quality - look for horizontal color stripes <br />
#repeat with different phase value<br />
<br />
If at some point camera will stop responding to http requests (actually requests to PHP scripts) you may restart PHP by issuing<br />
killall lighttpd<br />
from the telnet session - it kills the web server that will be restarted together with the instances of PHP.<br />
<br />
The phase default settings in the camera are optimized for a short cable (30 to 50mm), for longer cable it may need adjustment. You may also need to replace /etc/x353.bit file with the one that is generated with higher drive strength of the clock line from the FPGA to the sensor (that will also cause increase of the radiated EMI from the camera)<br />
<br />
=== Old instructions - valid for 7.1.x firmware ===<br />
The phase adjustment value passed to the driver is split into two parts - lower 16 bits represent (signed short) fine shift in steps (20..40ps), next 2 bits - 90-degrees additional shift, higher bits are "don't care". In default configuration bit 18 (0x40000) is set, because only non-zero values change the phase, so 0x40000 means "set 90-degree phase to 0, fine phase - to zero", while 0x0 means "no phase changes"<br />
<br />
The phase control parameter has index 513 (0x201), you may read the current value (see [[Driver_parameters]]) with the following command:<br />
<nowiki>http://<camera_ip>:81/senspars.php?cmd=read&addr=0x201</nowiki><br />
Default value is:<br />
513(0x201):327620(0x4ffc4)<br />
That is: no 90-degree shifts, fine shift is -60 steps.<br />
<br />
Supposing you would like to set new phase shift to +32:<br />
<br />
1: Write data to the driver "write" parameter<br />
<nowiki>http://<camera_ip>:81/senspars.php?cmd=write&addr=0x201&data=0x40020</nowiki><br />
<br />
You may verify it by reading<br />
<br />
<nowiki>http://<camera_ip>:81/senspars.php?cmd=read&addr=0x601</nowiki><br />
it will return<br />
1537(0x601):262176(0x40020)<br />
2. Driver "looks" at the phase shift value only there is a request to change the sensor clock frequency. Even as we do not need to change it, we write 96000000 (frequnecy in Hz) to the appropriate register - it will be replaced with zero (no changes required) when applied:<br />
<nowiki>http://<camera_ip>:81/senspars.php?cmd=write&addr=14&data=96000000</nowiki><br />
3. Now - apply changes:<br />
<nowiki>http://<camera_ip>:81/senspars.php?cmd=write&addr=0&data=3</nowiki><br />
<br />
That will cause sensor to be reset and then re-programmed to the current parameters (current settings are erased during reset). The sensor has to be reset after any clock changes, as it "assumes" that clock is stable after the reset signal (input pin or software command) is released. Experimentally we've found that the Micron 5MPix sensor can be confused if the clock frequency changes and in 50% instances develops a 1 pixel delay in the pixel output (effectively getting wrong colors). Strangely that applies only to the real sensor data, simulated test patters in the sensor are not influenced by this effect.</div>Andrey.filippovhttps://wiki.elphel.com/index.php?title=Adjusting_sensor_clock_phase&diff=2936Adjusting sensor clock phase2022-05-01T21:58:41Z<p>Andrey.filippov: /* Software interface for adjusting the sensor clock phase (firmware 8.0.x) */</p>
<hr />
<div>=== Elphel cameras architecture - separate computer and sensor boards ===<br />
Elphel cameras are designed so they can support multiple different sensors, including those that were not available when the particular camera model was first released. That is possible, because the camera functionality is split into the sensor-independent computer (see [[10353]]) and the sensor front end. This board is very simple for the CMOS images sensors, like [[10338]] - basically it includes just the image sensor itself, connector for the cable to the camera main board and the power conditioning circuitry. In other cameras (like Model 363) the high resolution CCD-based sensor front end is much more complex ([[10347]]+[[10342]]), but they all interface the main board through the 30-conductor flex cable that on the [[10353]] side is connected directly to the FPGA pins (all but power supply/ ground pins). That makes the interface universal, as functions of the FPGA pins can be changed with just a new code, no hardware changes are needed.<br />
<br />
=== Inter-board cable ===<br />
The inter-board connection is made of the flex cables (that are available in different length) provide freedom in mutual orientation of the main boards and the sensor front end, allowing the smaller sensor board to get into the tight spaces. But that 30-conductor cable has not enough conductors to make nice transmission lines - there is not enough of the return wires, number of ground+power lines is much less than the number of signal ones, but that is not a big issue for most camera applications where the cable is really short - less than 2 inches (50mm) long, but still the signals (in 5MPix sensor the output 12-bit data has a 96 mpix/sec, the clock lines run at 96MHz both directions) are used with reduced drive strength to reduce the EMI. Fortunately both FPGA and the sensor allow control over the drive strength. With the low output currents on the pins, it takes some time to recharge the parasitic capacitance of the cable wires, and the signals look far from "digital" rectangular shape - it takes most of the pixel period to just transition from "0" to "1" or back from "1" to "0", so the data on the other end should be sampled at a precise moment during each pixel period.<br />
<br />
=== Phase shift of the sensor clock input ===<br />
In the camera it is achieved by adding controlled phase shift between the clock that synchronizes operation of the sensor-related portion of the FPGA and the clock signal that is sent to the sensor. The sensor output signals have certain delay from that clock (unfortunately in 5MPix sensor that delay is very different for the pixel data and sync signals), so by varying the phase of a clock to sensor it is possible to adjust phase of the sensor data with respect to the FPGA pixel clock. The sensor pixel output clock is not used - it is more convenient when the FPGA clock does not depend on the state of the sensor. But that sensor output clock is connected to the FPGA and is sampled at different phases of the FPGA clock - that data can (and will) be used for the automatic phase adjustment, but current software does not support that yet.<br />
<br />
=== Effect of different cable lengths ===<br />
For the standard camera configuration the phase shift is programmed as a predefined constant, but that does not work when the cable length differs from the original one. If you try the camera with different cable length you may see image that looks like monochrome or purple - if the pixels are sampled at wrong time, red and green (also green and blue) pixels can swap, you may see horizontal lines when the sample moment is close to the pixel-to-pixel transition - in some lines pixels were sampled correctly, in some - colors are swapped (and remember - each pixel is represented by individual 12 bit lines, that can have slightly different delays to the clock). For some reasonable length cables (tested with 8" / 200mm) it is possible to re-adjust the phase shift, sample pixels in the middle of the pixel window and so restore the nice images.<br />
<br />
=== On-chip DCM (Digital Clock Management) for sensor clock phase adjustment ===<br />
Sensor phase control in the camera is achieved with one of the FPGA on-chip DCM (digital clock management) blocks by combining the fine phase adjustment with 4-to-1 multiplexor switching between on of the four outputs shifted by 90 degrees. The fine shift is not precisely known, for these chips it is specified in the 20-40 ps/step, while guaranteed number of phase shift steps (for 96MHz clock) is +/- 140 (so more than +/- 90 degrees in the worst case.<br />
<br />
=== Software interface for adjusting the sensor clock phase (firmware 8.0.x) ===<br />
Open the following URL in the browser (replace 192.168.0.9 if camera has different IP):<br />
192.168.0.9/parsedit.php?embed=0.25&title=Parameters+for+groups:+phase&SENSOR_PHASE&SENSOR_REGS7&SENSOR_REGS7__0310&SENSOR_REGS7__0307&WOI_HEIGHT&WB_EN&THIS_FRAME<br />
<br />
That page combines several controls:<br />
*SENSOR_PHASE - phase shift between the FPGA pixel clock and the sensor pixel clock. Normal adjustment range is 0xff80 (-64) to 0x0080 (+64)<br />
*SENSOR_REGS7 - sensor register #7 that, among others control drive strengths of the sensor output. It is safer to modify selected bit fields of this register:<br />
*SENSOR_REGS7__0307 (bits 9:7) is the drive strength of clock output (not used in the current setup)<br />
*SENSOR_REGS7__0310 (bits 12:10) is the drive strength of all other outputs - pixel data, horizontal and vertical sync<br />
*WOI_HEIGHT - window if interest height is not related to sensor phase adjustment, but it can be used to restore system (sensor to FPGA) synchronization after it is lost when adjusting sensor phase (that involves restarting the sensor). Just reduce/increase it by 0x10 and press "refresh" button - that should restore the "broken" image caused by losing system sync.<br />
<br />
When you change phase and press "apply" the image would not reflect the new settings (changing phase requires complete sensor reset and the regular image acquisition sequence is aborted), so the following sequence is recommended:<br />
#modify SENSOR_PHASE value<br />
#press "apply"<br />
#change WOI_HEIGHT (alternate between 0x790 and 0x780 for the full frame)<br />
#press "apply"<br />
#monitor image quality - look for horizontal color stripes <br />
#repeat with different phase value<br />
<br />
If at some point camera will stop responding to http requests (actually requests to PHP scripts) you may restart PHP by issuing<br />
killall lighttpd<br />
from the telnet session - it kills the web server that will be restarted together with the instances of PHP.<br />
<br />
The phase default settings in the camera are optimized for a short cable (30 to 50mm), for longer cable it may need adjustment. You may also need to replace /etc/x353.bit file with the one that is generated with higher drive strength of the clock line from the FPGA to the sensor (that will also cause increase of the radiated EMI from the camera)<br />
<br />
=== Old instructions - valid for 7.1.x firmware ===<br />
The phase adjustment value passed to the driver is split into two parts - lower 16 bits represent (signed short) fine shift in steps (20..40ps), next 2 bits - 90-degrees additional shift, higher bits are "don't care". In default configuration bit 18 (0x40000) is set, because only non-zero values change the phase, so 0x40000 means "set 90-degree phase to 0, fine phase - to zero", while 0x0 means "no phase changes"<br />
<br />
The phase control parameter has index 513 (0x201), you may read the current value (see [[Driver_parameters]]) with the following command:<br />
<nowiki>http://<camera_ip>:81/senspars.php?cmd=read&addr=0x201</nowiki><br />
Default value is:<br />
513(0x201):327620(0x4ffc4)<br />
That is: no 90-degree shifts, fine shift is -60 steps.<br />
<br />
Supposing you would like to set new phase shift to +32:<br />
<br />
1: Write data to the driver "write" parameter<br />
<nowiki>http://<camera_ip>:81/senspars.php?cmd=write&addr=0x201&data=0x40020</nowiki><br />
<br />
You may verify it by reading<br />
<br />
<nowiki>http://<camera_ip>:81/senspars.php?cmd=read&addr=0x601</nowiki><br />
it will return<br />
1537(0x601):262176(0x40020)<br />
2. Driver "looks" at the phase shift value only there is a request to change the sensor clock frequency. Even as we do not need to change it, we write 96000000 (frequnecy in Hz) to the appropriate register - it will be replaced with zero (no changes required) when applied:<br />
<nowiki>http://<camera_ip>:81/senspars.php?cmd=write&addr=14&data=96000000</nowiki><br />
3. Now - apply changes:<br />
<nowiki>http://<camera_ip>:81/senspars.php?cmd=write&addr=0&data=3</nowiki><br />
<br />
That will cause sensor to be reset and then re-programmed to the current parameters (current settings are erased during reset). The sensor has to be reset after any clock changes, as it "assumes" that clock is stable after the reset signal (input pin or software command) is released. Experimentally we've found that the Micron 5MPix sensor can be confused if the clock frequency changes and in 50% instances develops a 1 pixel delay in the pixel output (effectively getting wrong colors). Strangely that applies only to the real sensor data, simulated test patters in the sensor are not influenced by this effect.</div>Andrey.filippovhttps://wiki.elphel.com/index.php?title=10393_manual&diff=1355910393 manual2022-04-12T17:49:07Z<p>Andrey.filippov: /* Firmware images */</p>
<hr />
<div><!-- not anymore!<br />
==<font color="blue">Important Notes</font>==<br />
* As of 2016/12/15, the software ported from 10353 supports only 5MPix sensors, for 14MPix, please see:<br />
**[http://wiki.elphel.com/index.php?title=Tmp_manual&oldid=14676 older version of this manual with links to older software images]--><br />
<br />
<br />
<br />
==<font color="blue">In the package</font>==<br />
* 10393 camera system ([[Elphel_camera_assemblies|these 3D models]] might be helpful).<br />
{|<br />
|valign='top'|[[File:NC393-CS marked ports.jpeg|thumb|200px|Fig.1a 10393 interfaces]]<br />
|valign='top'|[[File:10393_boards_assembly.png|thumb|265px|Fig.1b Boards connections (NC393-F-CS)]]<br />
|valign='top'|[[File:10393 dev mmc.jpeg|thumb|150px|Fig.1c Micro SD card for development]]<br />
|}<br />
* Power supply options ([[10393_power|more information]]):<br />
{| class='wikitable'<br />
!Range<br />
!Power supply<br />
|-<br />
|align='left'|'''36-72V''' (default)<br />
| wall adapter (48V)<br />
|-<br />
|align='left'|'''18-75V'''<br />
| wall adapter (48V)<br />
|-<br />
|align='left'|'''12-36V'''<br />
| wall adapter, battery (12V)<br />
|-<br />
|align='left'|'''3.3V'''<br />
| direct, custom<br />
|}<br />
* CAT6 network cable<br />
* &mu;USB-to-USB cable<br />
* Recovery &mu;SD card<br />
* If the camera is calibrated the calibration data will be on a separate storage media or on the internal SSD (likely /mnt/sda1)<br />
<br />
==<font color="blue">Interfaces</font>==<br />
See Fig.1:<br />
{| class="wikitable"<br />
|-<br />
! GigE<br />
| gigabit network<br />
|-<br />
! &mu;SD <br />
| micro SD card slot - boot or storage<br />
|-<br />
! console<br />
| serial console port, use &mu;USB-to-USB cable<br />
|-<br />
! eSATA+USB<br />
| 2-in-1. Connect USB or eSATA device. USB2.0 host<br />
|-<br />
! &mu;USB<br />
| USB2.0 host<br />
|-<br />
! sync<br />
| sync multiple cameras or other devices - input/output trigger signal through a 4-conductor 2.5mm audio plug with cable (example: [http://www.digikey.com/products/en?keywords=839-1029-ND digikey])<br />
|}<br />
<br />
<br />
<br />
==<font color="blue">Power on</font>==<br />
* Plug in the power supply<br />
* Connect to LAN using the network cable<br />
<br />
====Notes====<br />
* Boot time: ~30s<br />
* No extra drivers are required on the host PC to operate the camera system. Can be operated from any network device with a browser.<br />
* The default boot is from the on-board NAND flash. [[Boot_options_393|More information]] on available boot options and recovery boot.<br />
* For a <font color='red'>'''production system'''</font> with rare changes to the file system it is recommended to boot from NAND flash. Changes to the file system require running an extra sync command (overlay_sync) followed by a proper reboot.<br />
* For <font color='red'>'''development'''</font>, one can boot from the &mu;SD recovery card and use it - saving changes does not require extra sync actions.<br />
* Camera's software includes gcc compiler - relatively small projects can be compiled on the camera.<br />
<br />
==<font color="blue">Defaults</font>==<br />
{| class="wikitable"<br />
|-<br />
! IP Address<br />
| 192.168.0.9<br />
|-<br />
! User <br />
| root<br />
|-<br />
! Password<br />
| pass<br />
|}<br />
<br />
* The default IP address is set in the ''/etc/elphel393/init_elphel393.py''.<br />
* If present the internal SSD will be formatted into 2 partitions:<br />
** /dev/sda1 - ext4 (~64-100GB)<br />
** /dev/sda2 - raw partition (no file system) for fast recording<br />
<br />
==<font color="blue">Command line access</font>==<br />
* ssh from PC's terminal:<br />
<font size='2em'><br />
user@hostname:~$ ssh root@192.168.0.9<br />
</font><br />
<br />
==<font color="blue">Serial console access</font>==<br />
* Use a ''microUSB-USB cable'' to connect '''console &mu;USB port''' (see Fig.1) to PC - the cable's end should be thin enough otherwise interferes with an inserted mmc ('''m'''ulti '''m'''edia '''c'''ard = &mu;SD card).<br />
<br />
* In Linux the '''minicom''' program can be used<br />
<font size='2em'><br />
$ minicom -c on<br />
</font><br />
Most likely the device will be <b>/dev/ttyUSB0</b>. Settings:<br />
* <b>115200 8N1, no</b> for hardware/software flow control<br />
Refer to the following article for more details on using '''minicom''': [http://wiki.elphel.com/index.php?title=Using_minicom_to_connect_to_Elphel393_camera Using minicom to connect to Elphel393 camera]<br />
<br />
==<font color="blue">Web user interface (camvc)</font>==<br />
'''http://192.168.0.9/'''<br />
* The page contains links to camvc user interface for each individual camera port.<br />
* camvc was ported from the 10353 camera series:<br />
** change parameters like image format, resolution, auto exposure, auto white balance and more. Alternative way to change parameters is described [[Tmp_manual#Change_parameters|below]].<br />
** pause compressor and search within buffered images<br />
** help tips available - see Fig.3 - select then mouse over a control element of interest<br />
{|<br />
| valign='top'|[[File:10393 starting page.png|thumb|600px|Fig.2 http://192.168.0.9]]<br />
| valign='top'|[[image:Help tips.jpeg|250px|thumb|Fig.3 enable camvc help tips]]<br />
| valign='top'|[[File:Controls with blank.jpeg|300px|thumb|Fig.4 camvc controls]]<br />
|}<br />
<br />
==<font color="blue">Download live images</font>==<br />
====camvc====<br />
* For a currently opened port (displayed in the window title and as "...sensor_port=0..." in the URL):<br />
{|<br />
|[[image:Camvc image capture.jpeg|250px|thumb|Fig.5 Acquire an image from the Camera Control Interface]]<br />
|}<br />
<br />
====browser====<br />
<font size='2'><br />
port 0: http://192.168.0.9:2323/img<br />
port 1: http://192.168.0.9:2324/img<br />
port 2: http://192.168.0.9:2325/img<br />
port 3: http://192.168.0.9:2326/img<br />
</font><br />
====command line====<br />
<font size='2'><br />
wget http://192.168.0.9:2323/img -O filename.jpeg<br />
wget http://192.168.0.9:2324/img -O filename.jpeg<br />
wget http://192.168.0.9:2325/img -O filename.jpeg<br />
wget http://192.168.0.9:2326/img -O filename.jpeg<br />
</font><br />
<br />
==<font color="blue">Video</font>==<br />
===Display===<br />
====Multipart JPEG stream====<br />
<font size='2'><br />
http://192.168.0.9:2323/mimg<br />
http://192.168.0.9:2324/mimg<br />
http://192.168.0.9:2325/mimg<br />
http://192.168.0.9:2326/mimg<br />
</font><br />
====RTSP====<br />
* Streams with either '''w''' or '''h''' >2040 might not get played - not supported by live555 often used by various media players. But there's a [https://git.elphel.com/Elphel/live555_patch live555_patch].<br />
* turn on:<br />
<font size='2'><br />
root@elphel393:~# /usr/bin/str<br />
</font><br />
* url:<br />
<font size='2'><br />
rtsp://192.168.0.9:554<br />
rtsp://192.168.0.9:556<br />
rtsp://192.168.0.9:558<br />
rtsp://192.168.0.9:560<br />
</font><br />
<br />
====GStreamer====<br />
<font size='2'><br />
gst-launch-1.0 -v playbin uri=rtsp://192.168.0.9:554 uridecodebin0::source::latency=0<br />
or<br />
gst-launch-1.0 souphttpsrc is-live=true location=http://192.168.0.9:2323/mimg ! jpegdec ! xvimagesink <br />
</font><br />
* mjpeg and rtsp<br />
* More examples at [[Using_gstreamer#Display|Using GStreamer]]<br />
<br />
====VLC====<br />
<font size='2'><br />
vlc rtsp://192.168.0.9:554 --network-caching=0<br />
</font><br />
<br />
===Record===<br />
* Recording is done by the [[Camogm|'''camogm''']] program<br />
* If recording to internal or external SSD, please, read about [[Tmp_manual#eSATA_port_switching|eSATA port switching]]<br />
* <font color='red'>important:</font> Event logger (GPS, IMU, IMG, EXT) recording is started/stopped separately. See [[Tmp_manual#Record_the_Event_Logger_data_.28GPS.2CIMU.2CIMG_.26_EXT.29|instructions]] below.<br />
* For SATA devices camogm supports:<br />
** recording to a partition with a file system - up to 80MB/s<br />
** (default) faster recording to a partition without a file system (raw partition) avoiding OS calls - up to 220MB/s<br />
* To extract data from a raw partition use '''dd''' or [https://github.com/Elphel/elphel-tools-x393 these scripts] to get the data and split it into images. Follow [[Extracting_images_from_raw_partition | this link]] for details.<br />
* Can record to an mmc partiton or usb.<br />
* <b><font size='3' color='red'>[[Using_camogm_with_Elphel393_camera|More info]]</font></b><br />
* If the ''prefix'' parameter, which is ''absolute path + prefix'', for a channel is not set the file will be written somewhere to rootfs. <br />
** if prefix is empty then the ''absolute path'' must end with a slash.<br />
<br />
====browser====<br />
Example 1: (provide a correct media mount point - /mnt/sda1/)<br />
<font size='2'><br />
* http://192.168.0.9/camogmgui.php<br />
</font><br />
Follow [[Camogmgui|this link]] for GUI description.<br />
<br />
====command line====<br />
Example:<br />
<font size='2'><br />
* '''/home/root''', file prefix='''test_''', '''1GB''' or '''10min''' files whichever occurs first<br />
** setup and start (in one line):<br />
echo "format=mov;status=/var/tmp/camogm.status;prefix=/home/root/test_;duration=600;length=1073741824;start" > /var/volatile/camogm_cmd<br />
** stop recording:<br />
echo "stop" > /var/volatile/camogm_cmd<br />
sync<br />
</font><br />
<br />
===Convert to a web cam stream===<br />
See this [https://blog.elphel.com/2020/06/convert-ip-cam-to-web-cam-in-linux-for-jitsi-zoom-etc/ tutorial].<br />
<br />
==<font color="blue">Store/restore configuration</font>==<br />
* http://192.168.0.9/autocampars.php - save/restore/initialize camera/sensor parameters per port. To (re)store parameters access the pages below:<br />
<font size='2'><br />
http://192.168.0.9/autocampars.php?sensor_port=0 (stores to /etc/elphel393/autocampars0.xml)<br />
http://192.168.0.9/autocampars.php?sensor_port=1 (stores to /etc/elphel393/autocampars1.xml)<br />
http://192.168.0.9/autocampars.php?sensor_port=2 (stores to /etc/elphel393/autocampars2.xml)<br />
http://192.168.0.9/autocampars.php?sensor_port=3 (stores to /etc/elphel393/autocampars3.xml)<br />
</font><br />
[[Autocampars 393|'''More information''']]<br />
* All stored parameters are automatically restored at boot<br />
<br />
==<font color="blue">Available programmable parameters</font>==<br />
To inspect all available reprogrammable parameters:<br />
1. http://192.168.0.9 -> Parameter Editor<br />
2. Follow a link for a particular port, e.g. http://192.168.0.9/autocampars.php?sensor_port=0<br />
3. Select groups of interest in the top table -> View/Edit Current<br />
<br />
==<font color="blue">Change parameters</font>==<br />
* http://192.168.0.9/parsedit.php - read/write parameters:<br />
** POST request<br />
<font size='2'><br />
Read: http://192.168.0.9/parsedit.php?sensor_port=0&PAR1&PAR2<br />
Change: http://192.168.0.9/parsedit.php?sensor_port=0&PAR1&PAR2 - update values - submit form<br />
</font><br />
** GET request - XML response<br />
<font size='2'><br />
Read: <br />
http://192.168.0.9/parsedit.php?immediate&sensor_port=0&PAR1&PAR2<br />
Change: <br />
http://192.168.0.9/parsedit.php?immediate&sensor_port=0&PAR1=VAL1&PAR2=VAL2<br />
Change for multiple ports at once:<br />
http://192.168.0.9/parsedit.php?immediate&sensor_port=0&PAR1=VAL1&*PAR1=MASK1&PAR2=VAL2&*PAR2=MASK2<br />
<br />
# A port bit mask is set by adding a '''*''' to a parameter name, like '''*PAR1''' - it is individual for each parameter.<br />
# The mask is 4 bits - 1 bit per port, bit[0] = port 0,... bit[3] = port 3, where 1 - enabled, 0 - disabled:<br />
# 0xf - the parameter's new value will be applied to all ports.<br />
# [[Parsedit.php#change_multiple_ports|'''More information''']]<br />
</font><br />
<br />
Note 1: if the parameter's value is specified in URL it will be applied. The call can have mixed specified and unspecified parameters.<br />
<br />
Note 2: The new value is read on the next call.<br />
<br />
Example:<br />
* set 10 fps and enable output trigger signal<br />
<font size='2'><br />
http://192.168.0.9/parsedit.php?sensor_port=0&immediate&TRIG_CONDITION=0&TRIG_OUT=0x66555&TRIG_PERIOD=10000000&TRIG=4<br />
</font><br />
[[Parsedit.php|'''More information''']]<br />
<br />
<br />
'''Notes:'''<br />
* parsedit.php and autocampars.php were ported from 353 camera series. There are a few changes from the originals related to 4x sensor ports:<br />
** parameters are individual for each sensor port - writing parameters to multiple port at once is controlled with a (bit-)'''mask''' input box<br />
** if opened w/o sensor_port specified the page will show links to available ports<br />
** '''sensor_port=x''', where x=0..3 - in the address string - for a single sensor camera it is normally 0<br />
<br />
==<font color="blue">Image formats</font>==<br />
====JPEG====<br />
* ''color'': YCbCr 4:2:0, 3x3 pixels<br />
* ''mono6'': monochrome - color YCbCr 4:2:0 with zeroed out color components<br />
* ''mono'' : monochrome - color YCbCr 4:0:0 with omitted color components<br />
<br />
Note: JPEG is not the best for processing since some information gets lost when demosaicing is applied.<br />
====JP4====<br />
* provides a quality of RAW with compression, no demosaicing<br />
* [[JP4|'''More information''']]<br />
<br />
==<font color="blue">Proper shutdown</font>==<br />
* if not properly shutdown - in a rare case the &mu;SD card can get corrupted (it's always safer to run '''sync''')<br />
<font size='2'><br />
~# sync<br />
~# shutdown -hP now<br />
</font><br />
Same effect:<br />
<font size='2'><br />
http://192.168.0.9/autocampars.php?reboot<br />
</font><br />
<br />
==<font color="blue">Temperature monitor</font>==<br />
* http://192.168.0.9/hwmon.html:<br />
** T<sub>shutdown</sub> - automatic shutdown temperature level (default is 90&deg;C)<br />
{|<br />
|[[File:10393_hwmon.jpeg|thumb|200px]]<br />
|}<br />
<br />
==<font color="blue">Event Logger (GPS, IMU, IMG & EXT)</font>==<br />
<br />
The FPGA-based Event Logger uses local clock for time-stamping data from Image Acquisition, External (Trigger) Input, GPS and IMU.<br />
<br />
* [[Event_logger|'''More information''']]<br />
===Record===<br />
====web====<br />
* Start: <br />
http://192.168.0.9/logger_launcher.php?cmd=start&file=/mnt/sda1/test.log&index=1&n=10000000<br />
* Stop:<br />
http://192.168.0.9/logger_launcher.php?cmd=stop<br />
* Help:<br />
http://192.168.0.9/logger_launcher.php<br />
<br />
====command line====<br />
* start:<br />
<font size='2'><br />
root@elphel393:~# cat /dev/imu > /path/filename.log<br />
</font><br />
* stop - CTRL-C or kill the process<br />
<br />
===Read===<br />
* http://192.168.0.9/read_imu_log.php (will display help)<br />
** on the first access creates /www/pages/logs/ (http://192.168.0.9/logs/)<br />
** link the recorded logs to /www/pages/logs/<br />
** refresh http://192.168.0.9/read_imu_log.php<br />
<br />
==<font color="blue">Set system time</font>==<br />
<br />
===Command line from PC===<br />
<font size='2'># Compare PC and camera clocks<br />
~$ ssh root@192.168.0.9 date;date -u<br />
# Write PC time into camera clock<br />
~$ ssh root@192.168.0.9 "date -s @`( date -u +"%s" )` && hwclock -w"<br />
<br />
===PHP===<br />
If in the current firmware includes '''http://192.168.0.9/utils.php''' then the clock is checked every time the index page is opened ('''http://192.168.0.9'''). The clock is then updated if the browser time differs from the camera time by more than 24h.<br />
<br />
It's also possible to force apply time using the following GET request:<br />
<nowiki>http://192.168.0.9/utils.php?cmd=time&apply&ts=<timestamp_in_ms></nowiki><br />
#example:<br />
<nowiki>http://192.168.0.9/utils.php?cmd=time&apply&ts=1589913066650</nowiki><br />
<br />
==<font color="blue">eSATA port switching</font>==<br />
* requres [[10389]]<br />
* available connections:<br />
** camera <=> internal SSD (default)<br />
** camera <=> external drive (external drive requires a separate power source)<br />
** PC <=> internal SSD<br />
* [[Sata_multiplexer_10389|'''More information''']]<br />
<br />
==<font color="blue">Firmware/software update</font>==<br />
[[Poky_2.0_manual#Write_files_to_media_and_boot|'''More information''']]<br />
<br />
==<font color="blue">Firmware images</font>==<br />
* [https://community.elphel.com/files/393/20220412/ '''20220412''']<br />
* [https://community.elphel.com/files/393/20210628/ 20210628]<br />
* [https://community.elphel.com/files/393/20200903/ 20200903]<br />
* [https://community.elphel.com/files/393/20200520/ 20200520]<br />
* [https://community.elphel.com/files/393/20200508/ 20200508]<br />
<br />
===Changelog===<br />
<font size='1'>'''==20220412=='''<br />
* Added websockets test<br />
* More options in format_disk (single partition, reformat already formatted disk,...)<br />
* Bug fixes<br />
<font size='1'>'''==20210628=='''<br />
* Added support for FLIR Boson sensors<br />
* Added decimation to external synchronization (triggering on each N-th incoming pulse). That was needed to run slower RGB sensors @12 Hz with Boson as a master at 60Hz<br />
* Enhanced inter-camera synchronization, added related kernel and PHP extension functionality.<br />
<font size='1'>'''==20200903=='''<br />
* switched to warrior branch for build<br />
* updated to kernel 4.19. This build was being under test for a while.<br />
'''==20200520=='''<br />
(rocko build)<br />
* Set time on main page access - taking browser time and writing to 10393 if times differ by 24h+.<br />
* Added script for sensor testing (switch to test pattern, check md5sum).<br />
Supporting MT9P006. Linked to main page.<br />
* Main page:<br />
* Added links to page displaying MJPEG stream in canvas<br />
* Added more controls (FPS, Manual Exposure and Auto Exposure Limit)<br />
* Added quick switch to 1080p@30fps (MT9P006)<br />
* Updated JPEG/JP4 decoding javascript plugin - less time (-10ms) spent on EXIF reading.<br />
* Created utils.php, currenty helps to GET-request:<br />
* ports configuration<br />
* set/get system time<br />
* Fixed snapshot button for cameras with unused ports in multicam/ UI.<br />
'''==20200508=='''<br />
(rocko build)<br />
* updated camogm<br />
* added FLIR Lepton driver to kernel<br />
* added FLIR Lepton record to device tree<br />
'''==20190321=='''<br />
* overall minor changes<br />
* fixed photofinish demo<br />
'''==20180511=='''<br />
* added cron program<br />
* multi cameras control interface<br />
* multi camera system info reporting<br />
* fixed rtc<br />
'''==20180416=='''<br />
* 20180419 - mt9f002: fixed changing window size<br />
* mt9f002: added triggered mode<br />
* mt9f002: added vertical and horizontal flips (mirror)<br />
'''==20180406=='''<br />
* added initial support for MT9F002 sensor: no triggered mode, no binning/decimation<br />
* display serial number in http://camera-ip:port/meta<br />
* decode jp4s on the index page (http://camera-ip)<br />
* turn off auto wb button for all ports on the index page<br />
'''==20180130=='''<br />
* added photo finish demo<br />
* fixed fps limit calcs for triggered mode<br />
'''==20180118=='''<br />
* raw.py & raw.php, see wiki.elphel.com<br />
* added python3 and python3-opencv<br />
'''==20180116=='''<br />
* raw pixel data downloading through membridge<br />
* added gcc,make<br />
'''==20180109=='''<br />
* fixed autoexposure<br />
'''==20171228=='''<br />
* + strace, ltrace, dmsetup<br />
* added to drivers: register devs to sysfs - nodes then created by udev<br />
'''==20171226=='''<br />
* kernel updated to 4.9 (from 4.0)<br />
* lots of drivers is updated to newer versions<br />
* +dm-crypt and cryptsetup<br />
'''==20171120=='''<br />
* bugfix - incorrect displaying of TRIG_PERIOD at init<br />
'''==20171115=='''<br />
* Fixed autocampars to let 10393 work with the mux board - 10359, see wiki.elphel.com for<br />
docs<br />
'''==20170823=='''<br />
* Fixed autocampars for multiple sensors getting desynced at init<br />
* Fixed Garmin GPS 18x USB driver<br />
'''==20170802=='''<br />
* fixed a page for taking snapshots - works in chrome and firefox for bigger images (>2MB)<br />
* enabled "Access-Control-Expose-Headers: Content-Disposition" and CORS<br />
'''==20170627=='''<br />
* viewing decoded jp4 format in camvc<br />
'''==20170623=='''<br />
* fixed incorrect default setting of the master channel<br />
</font><br />
<br />
==<font color="blue">Development</font>==<br />
Usage of [[Poky_manual|SDK]], which is Eclipse and project tree cloned from git.elphel.com, simplifies the development.<br />
At the same time lots of things can be done using Python, PHP, JavaScript or C/C++ (if compiled on hardware) and do not require SDK.<br />
<br />
==<font color="blue">Other info</font>==<br />
===Change default ip address===<br />
Modify '''''/etc/network/interfaces''''', sync the changes to the file system and reboot (or rerun init scripts).<br />
<br />
For firmware 20180511 or older, follow [[Fix_network_configuration|these instructions]] to fix network configuration (= disable setting ip address via '''/etc/elphel393/init_elphel393.py''').<br />
<br />
===Add a program or a shell command to autostart on boot===<br />
There's a way to do this using [https://unix.stackexchange.com/questions/56957/how-to-start-an-application-automatically-on-boot cron or init.d] but it might run before the sensors are initialized by init_elphel393.py. The recommended way is the following:<br />
* '''nano''' or '''vi'''<br />
<font size='2'><br />
ssh root@192.168.0.9<br />
''pass''<br />
root@elphel393:~# nano /etc/elphel393/init_elphel393.py<br />
''edit - save''<br />
''example: to launch the rtsp streamer - add '''shout("/usr/bin/str")''' to the end of the file''. shout() function is just a wrapper for '''subprocess.call(cmd,shell=True)'''<br />
</font><br />
Then:<br />
<font size='2'><br />
#boot from NAND flash?<br />
root@elphel393:~# overlay_sync 1 <br />
root@elphel393:~# shutdown -hP now<br />
#powercycle<br />
<br />
#boot from card?<br />
root@elphel393:~# sync<br />
root@elphel393:~# reboot -f<br />
</font><br />
<br />
===Set up histogram window and autoexposure parameters===<br />
[[Autoexposure|Read article]]<br />
===Tools for calibrated systems===<br />
* [[Elphel_Software_Kit_for_Ubuntu#ImageJ_and_Elphel_plugins_for_imageJ|Install ImageJ plugins]]<br />
** decode jp4 raw format<br />
** aberrations correction<br />
** distortion correction (pixel mapping)<br />
** rectification and projection<br />
** '''JP46 Reader camera''' - decode JP4/JP46<br />
** '''Eyesis correction''' - post-process JP4s using calibration data<br />
<br />
===Switch between ERS and GRR modes in MT9P006===<br />
* [[Electronic_Rolling_Shutter#ERS_and_GRR_in_MT9P001_on_10393|Read article]]<br />
===External/internal synchronization & triggering and FPS control for single/multi-camera systems===<br />
* [[Trigger_393]]<br />
<br />
===SSD/MMC/USB formatting===<br />
* [[Format_SSD_MMC]]<br />
===Boot modes===<br />
* [[Boot_options_393|Boot options]]<br />
===Pointers monitor===<br />
* Displays sensor, compressor and buffer states per 10393 port:<br />
<font size='2'><br />
http://192.168.0.9/pointers/<br />
</font><br />
<br />
===Powering from batteries (12V or 48V)===<br />
[[10393_power#Powering_from_batteries| 12V and 48V power options]]<br />
===Accessing raw pixel values===<br />
[[Working_with_raw_image_data|Working with raw pixel data (how to capture raw images)]]<br />
<br />
===Photo finish (linescan mode)===<br />
[[Photo-finish|Photo Finish]] (works for JP4 image format)<br />
<br />
===Controlling multiple cameras from single GUI===<br />
* [[Multi_camera_system_operation|Recording]]<br />
<br />
===Developers version's half enclosure===<br />
{|<br />
|valign='top'|[[File:10393 half enclosure 1.jpeg|thumb|200px]]<br />
|valign='top'|[[File:10393 half enclosure 2.jpeg|thumb|200px]]<br />
|}<br />
<br />
===Available lengths for cables for connecting sensors in custom setups===<br />
* [[FPC_cables|FPC cables]] - click for available lengths.<br />
* The cables are <font color='red'>asymmetrical</font> - for correct connecting a sensor to a system board see the figure below. As a rule of thumb, the cable's back side (no contacts) will be on the same side with the connector's cover.<br />
{|<br />
|[[Image:Fpc_cable_conn_10393.jpeg|300px|thumb|Connecting sensors to the system board]]<br />
|}<br />
<br />
==<font color="blue">Known problems</font>==<br />
* <font color='green'>'''[SOLVED]'''</font> Vertical artifacts in jpegs. Images are ok at 100% quality. Fixed, testing.<br />
* <font color='green'>'''[SOLVED]'''</font> http://192.168.0.9:232x/noexif/mimg - multipart jpeg displays corrupted frames from time to time. Reason: network bandwidth?<br />
* <font color='green'>'''[SOLVED]'''</font> Sometimes on power-on (NAND flash boot) cannot mount the card's rootfs partition. Kernel Panics. Power off/on. Soft "reboot -f" works ok.<br />
<font size='2'><br />
...<br />
<b>Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,2)</b><br />
...<br />
</font><br />
[[VFS:_Unable_to_mount_root_fs_on_unknown-block(179,2)|More info]]<br />
* <font color='green'>'''[SOLVED]'''</font> Changing exposure/quality/gains - can corrupt images - needs testing.<br />
<br />
* <font color='green'>'''[SOLVED]'''</font> After rewriting rootfs to &mu;SD card - some of the cards get a corrupted partition - re-partitioning (reformatting?) solves the problem.<br />
<font size='2'><br />
On the camera the rootfs is mounted as RW and some of the files are changed (also links created) -<br />
most of the changes are now moved to tmpfs but something might have been missed.<br />
</font><br />
<br />
==<font color="blue">Notes</font>==<br />
* <font color='green'>'''[SOLVED]'''</font> In case rootfs is on flash, it might make sense (or maybe not as the history is updated only once on session exit) to disable bash sessions command history - [http://stackoverflow.com/questions/18663078/disable-history-in-linux disable bash history]<br />
<br />
* <font color='green'>'''[SOLVED]'''</font> When using '''overlays''', deleting, existing in the lower layer, dirs can cause errors (hopefully it gets fixed someday), example: <br />
** /mnt/sda1 exists in lower layer: /tmp/rootfs.ro/tmp<br />
** upper layer is mounted to "/"<br />
<font size='2'><br />
# rmdir /mnt/sda1<br />
# mkdir /mnt/sda1<br />
mkdir: cannot create directory '/mnt/sda1': Operation not supported<br />
</font><br />
[[Category:393]]</div>Andrey.filippovhttps://wiki.elphel.com/index.php?title=10393_manual&diff=1355810393 manual2022-04-12T17:48:11Z<p>Andrey.filippov: /* Changelog */</p>
<hr />
<div><!-- not anymore!<br />
==<font color="blue">Important Notes</font>==<br />
* As of 2016/12/15, the software ported from 10353 supports only 5MPix sensors, for 14MPix, please see:<br />
**[http://wiki.elphel.com/index.php?title=Tmp_manual&oldid=14676 older version of this manual with links to older software images]--><br />
<br />
<br />
<br />
==<font color="blue">In the package</font>==<br />
* 10393 camera system ([[Elphel_camera_assemblies|these 3D models]] might be helpful).<br />
{|<br />
|valign='top'|[[File:NC393-CS marked ports.jpeg|thumb|200px|Fig.1a 10393 interfaces]]<br />
|valign='top'|[[File:10393_boards_assembly.png|thumb|265px|Fig.1b Boards connections (NC393-F-CS)]]<br />
|valign='top'|[[File:10393 dev mmc.jpeg|thumb|150px|Fig.1c Micro SD card for development]]<br />
|}<br />
* Power supply options ([[10393_power|more information]]):<br />
{| class='wikitable'<br />
!Range<br />
!Power supply<br />
|-<br />
|align='left'|'''36-72V''' (default)<br />
| wall adapter (48V)<br />
|-<br />
|align='left'|'''18-75V'''<br />
| wall adapter (48V)<br />
|-<br />
|align='left'|'''12-36V'''<br />
| wall adapter, battery (12V)<br />
|-<br />
|align='left'|'''3.3V'''<br />
| direct, custom<br />
|}<br />
* CAT6 network cable<br />
* &mu;USB-to-USB cable<br />
* Recovery &mu;SD card<br />
* If the camera is calibrated the calibration data will be on a separate storage media or on the internal SSD (likely /mnt/sda1)<br />
<br />
==<font color="blue">Interfaces</font>==<br />
See Fig.1:<br />
{| class="wikitable"<br />
|-<br />
! GigE<br />
| gigabit network<br />
|-<br />
! &mu;SD <br />
| micro SD card slot - boot or storage<br />
|-<br />
! console<br />
| serial console port, use &mu;USB-to-USB cable<br />
|-<br />
! eSATA+USB<br />
| 2-in-1. Connect USB or eSATA device. USB2.0 host<br />
|-<br />
! &mu;USB<br />
| USB2.0 host<br />
|-<br />
! sync<br />
| sync multiple cameras or other devices - input/output trigger signal through a 4-conductor 2.5mm audio plug with cable (example: [http://www.digikey.com/products/en?keywords=839-1029-ND digikey])<br />
|}<br />
<br />
<br />
<br />
==<font color="blue">Power on</font>==<br />
* Plug in the power supply<br />
* Connect to LAN using the network cable<br />
<br />
====Notes====<br />
* Boot time: ~30s<br />
* No extra drivers are required on the host PC to operate the camera system. Can be operated from any network device with a browser.<br />
* The default boot is from the on-board NAND flash. [[Boot_options_393|More information]] on available boot options and recovery boot.<br />
* For a <font color='red'>'''production system'''</font> with rare changes to the file system it is recommended to boot from NAND flash. Changes to the file system require running an extra sync command (overlay_sync) followed by a proper reboot.<br />
* For <font color='red'>'''development'''</font>, one can boot from the &mu;SD recovery card and use it - saving changes does not require extra sync actions.<br />
* Camera's software includes gcc compiler - relatively small projects can be compiled on the camera.<br />
<br />
==<font color="blue">Defaults</font>==<br />
{| class="wikitable"<br />
|-<br />
! IP Address<br />
| 192.168.0.9<br />
|-<br />
! User <br />
| root<br />
|-<br />
! Password<br />
| pass<br />
|}<br />
<br />
* The default IP address is set in the ''/etc/elphel393/init_elphel393.py''.<br />
* If present the internal SSD will be formatted into 2 partitions:<br />
** /dev/sda1 - ext4 (~64-100GB)<br />
** /dev/sda2 - raw partition (no file system) for fast recording<br />
<br />
==<font color="blue">Command line access</font>==<br />
* ssh from PC's terminal:<br />
<font size='2em'><br />
user@hostname:~$ ssh root@192.168.0.9<br />
</font><br />
<br />
==<font color="blue">Serial console access</font>==<br />
* Use a ''microUSB-USB cable'' to connect '''console &mu;USB port''' (see Fig.1) to PC - the cable's end should be thin enough otherwise interferes with an inserted mmc ('''m'''ulti '''m'''edia '''c'''ard = &mu;SD card).<br />
<br />
* In Linux the '''minicom''' program can be used<br />
<font size='2em'><br />
$ minicom -c on<br />
</font><br />
Most likely the device will be <b>/dev/ttyUSB0</b>. Settings:<br />
* <b>115200 8N1, no</b> for hardware/software flow control<br />
Refer to the following article for more details on using '''minicom''': [http://wiki.elphel.com/index.php?title=Using_minicom_to_connect_to_Elphel393_camera Using minicom to connect to Elphel393 camera]<br />
<br />
==<font color="blue">Web user interface (camvc)</font>==<br />
'''http://192.168.0.9/'''<br />
* The page contains links to camvc user interface for each individual camera port.<br />
* camvc was ported from the 10353 camera series:<br />
** change parameters like image format, resolution, auto exposure, auto white balance and more. Alternative way to change parameters is described [[Tmp_manual#Change_parameters|below]].<br />
** pause compressor and search within buffered images<br />
** help tips available - see Fig.3 - select then mouse over a control element of interest<br />
{|<br />
| valign='top'|[[File:10393 starting page.png|thumb|600px|Fig.2 http://192.168.0.9]]<br />
| valign='top'|[[image:Help tips.jpeg|250px|thumb|Fig.3 enable camvc help tips]]<br />
| valign='top'|[[File:Controls with blank.jpeg|300px|thumb|Fig.4 camvc controls]]<br />
|}<br />
<br />
==<font color="blue">Download live images</font>==<br />
====camvc====<br />
* For a currently opened port (displayed in the window title and as "...sensor_port=0..." in the URL):<br />
{|<br />
|[[image:Camvc image capture.jpeg|250px|thumb|Fig.5 Acquire an image from the Camera Control Interface]]<br />
|}<br />
<br />
====browser====<br />
<font size='2'><br />
port 0: http://192.168.0.9:2323/img<br />
port 1: http://192.168.0.9:2324/img<br />
port 2: http://192.168.0.9:2325/img<br />
port 3: http://192.168.0.9:2326/img<br />
</font><br />
====command line====<br />
<font size='2'><br />
wget http://192.168.0.9:2323/img -O filename.jpeg<br />
wget http://192.168.0.9:2324/img -O filename.jpeg<br />
wget http://192.168.0.9:2325/img -O filename.jpeg<br />
wget http://192.168.0.9:2326/img -O filename.jpeg<br />
</font><br />
<br />
==<font color="blue">Video</font>==<br />
===Display===<br />
====Multipart JPEG stream====<br />
<font size='2'><br />
http://192.168.0.9:2323/mimg<br />
http://192.168.0.9:2324/mimg<br />
http://192.168.0.9:2325/mimg<br />
http://192.168.0.9:2326/mimg<br />
</font><br />
====RTSP====<br />
* Streams with either '''w''' or '''h''' >2040 might not get played - not supported by live555 often used by various media players. But there's a [https://git.elphel.com/Elphel/live555_patch live555_patch].<br />
* turn on:<br />
<font size='2'><br />
root@elphel393:~# /usr/bin/str<br />
</font><br />
* url:<br />
<font size='2'><br />
rtsp://192.168.0.9:554<br />
rtsp://192.168.0.9:556<br />
rtsp://192.168.0.9:558<br />
rtsp://192.168.0.9:560<br />
</font><br />
<br />
====GStreamer====<br />
<font size='2'><br />
gst-launch-1.0 -v playbin uri=rtsp://192.168.0.9:554 uridecodebin0::source::latency=0<br />
or<br />
gst-launch-1.0 souphttpsrc is-live=true location=http://192.168.0.9:2323/mimg ! jpegdec ! xvimagesink <br />
</font><br />
* mjpeg and rtsp<br />
* More examples at [[Using_gstreamer#Display|Using GStreamer]]<br />
<br />
====VLC====<br />
<font size='2'><br />
vlc rtsp://192.168.0.9:554 --network-caching=0<br />
</font><br />
<br />
===Record===<br />
* Recording is done by the [[Camogm|'''camogm''']] program<br />
* If recording to internal or external SSD, please, read about [[Tmp_manual#eSATA_port_switching|eSATA port switching]]<br />
* <font color='red'>important:</font> Event logger (GPS, IMU, IMG, EXT) recording is started/stopped separately. See [[Tmp_manual#Record_the_Event_Logger_data_.28GPS.2CIMU.2CIMG_.26_EXT.29|instructions]] below.<br />
* For SATA devices camogm supports:<br />
** recording to a partition with a file system - up to 80MB/s<br />
** (default) faster recording to a partition without a file system (raw partition) avoiding OS calls - up to 220MB/s<br />
* To extract data from a raw partition use '''dd''' or [https://github.com/Elphel/elphel-tools-x393 these scripts] to get the data and split it into images. Follow [[Extracting_images_from_raw_partition | this link]] for details.<br />
* Can record to an mmc partiton or usb.<br />
* <b><font size='3' color='red'>[[Using_camogm_with_Elphel393_camera|More info]]</font></b><br />
* If the ''prefix'' parameter, which is ''absolute path + prefix'', for a channel is not set the file will be written somewhere to rootfs. <br />
** if prefix is empty then the ''absolute path'' must end with a slash.<br />
<br />
====browser====<br />
Example 1: (provide a correct media mount point - /mnt/sda1/)<br />
<font size='2'><br />
* http://192.168.0.9/camogmgui.php<br />
</font><br />
Follow [[Camogmgui|this link]] for GUI description.<br />
<br />
====command line====<br />
Example:<br />
<font size='2'><br />
* '''/home/root''', file prefix='''test_''', '''1GB''' or '''10min''' files whichever occurs first<br />
** setup and start (in one line):<br />
echo "format=mov;status=/var/tmp/camogm.status;prefix=/home/root/test_;duration=600;length=1073741824;start" > /var/volatile/camogm_cmd<br />
** stop recording:<br />
echo "stop" > /var/volatile/camogm_cmd<br />
sync<br />
</font><br />
<br />
===Convert to a web cam stream===<br />
See this [https://blog.elphel.com/2020/06/convert-ip-cam-to-web-cam-in-linux-for-jitsi-zoom-etc/ tutorial].<br />
<br />
==<font color="blue">Store/restore configuration</font>==<br />
* http://192.168.0.9/autocampars.php - save/restore/initialize camera/sensor parameters per port. To (re)store parameters access the pages below:<br />
<font size='2'><br />
http://192.168.0.9/autocampars.php?sensor_port=0 (stores to /etc/elphel393/autocampars0.xml)<br />
http://192.168.0.9/autocampars.php?sensor_port=1 (stores to /etc/elphel393/autocampars1.xml)<br />
http://192.168.0.9/autocampars.php?sensor_port=2 (stores to /etc/elphel393/autocampars2.xml)<br />
http://192.168.0.9/autocampars.php?sensor_port=3 (stores to /etc/elphel393/autocampars3.xml)<br />
</font><br />
[[Autocampars 393|'''More information''']]<br />
* All stored parameters are automatically restored at boot<br />
<br />
==<font color="blue">Available programmable parameters</font>==<br />
To inspect all available reprogrammable parameters:<br />
1. http://192.168.0.9 -> Parameter Editor<br />
2. Follow a link for a particular port, e.g. http://192.168.0.9/autocampars.php?sensor_port=0<br />
3. Select groups of interest in the top table -> View/Edit Current<br />
<br />
==<font color="blue">Change parameters</font>==<br />
* http://192.168.0.9/parsedit.php - read/write parameters:<br />
** POST request<br />
<font size='2'><br />
Read: http://192.168.0.9/parsedit.php?sensor_port=0&PAR1&PAR2<br />
Change: http://192.168.0.9/parsedit.php?sensor_port=0&PAR1&PAR2 - update values - submit form<br />
</font><br />
** GET request - XML response<br />
<font size='2'><br />
Read: <br />
http://192.168.0.9/parsedit.php?immediate&sensor_port=0&PAR1&PAR2<br />
Change: <br />
http://192.168.0.9/parsedit.php?immediate&sensor_port=0&PAR1=VAL1&PAR2=VAL2<br />
Change for multiple ports at once:<br />
http://192.168.0.9/parsedit.php?immediate&sensor_port=0&PAR1=VAL1&*PAR1=MASK1&PAR2=VAL2&*PAR2=MASK2<br />
<br />
# A port bit mask is set by adding a '''*''' to a parameter name, like '''*PAR1''' - it is individual for each parameter.<br />
# The mask is 4 bits - 1 bit per port, bit[0] = port 0,... bit[3] = port 3, where 1 - enabled, 0 - disabled:<br />
# 0xf - the parameter's new value will be applied to all ports.<br />
# [[Parsedit.php#change_multiple_ports|'''More information''']]<br />
</font><br />
<br />
Note 1: if the parameter's value is specified in URL it will be applied. The call can have mixed specified and unspecified parameters.<br />
<br />
Note 2: The new value is read on the next call.<br />
<br />
Example:<br />
* set 10 fps and enable output trigger signal<br />
<font size='2'><br />
http://192.168.0.9/parsedit.php?sensor_port=0&immediate&TRIG_CONDITION=0&TRIG_OUT=0x66555&TRIG_PERIOD=10000000&TRIG=4<br />
</font><br />
[[Parsedit.php|'''More information''']]<br />
<br />
<br />
'''Notes:'''<br />
* parsedit.php and autocampars.php were ported from 353 camera series. There are a few changes from the originals related to 4x sensor ports:<br />
** parameters are individual for each sensor port - writing parameters to multiple port at once is controlled with a (bit-)'''mask''' input box<br />
** if opened w/o sensor_port specified the page will show links to available ports<br />
** '''sensor_port=x''', where x=0..3 - in the address string - for a single sensor camera it is normally 0<br />
<br />
==<font color="blue">Image formats</font>==<br />
====JPEG====<br />
* ''color'': YCbCr 4:2:0, 3x3 pixels<br />
* ''mono6'': monochrome - color YCbCr 4:2:0 with zeroed out color components<br />
* ''mono'' : monochrome - color YCbCr 4:0:0 with omitted color components<br />
<br />
Note: JPEG is not the best for processing since some information gets lost when demosaicing is applied.<br />
====JP4====<br />
* provides a quality of RAW with compression, no demosaicing<br />
* [[JP4|'''More information''']]<br />
<br />
==<font color="blue">Proper shutdown</font>==<br />
* if not properly shutdown - in a rare case the &mu;SD card can get corrupted (it's always safer to run '''sync''')<br />
<font size='2'><br />
~# sync<br />
~# shutdown -hP now<br />
</font><br />
Same effect:<br />
<font size='2'><br />
http://192.168.0.9/autocampars.php?reboot<br />
</font><br />
<br />
==<font color="blue">Temperature monitor</font>==<br />
* http://192.168.0.9/hwmon.html:<br />
** T<sub>shutdown</sub> - automatic shutdown temperature level (default is 90&deg;C)<br />
{|<br />
|[[File:10393_hwmon.jpeg|thumb|200px]]<br />
|}<br />
<br />
==<font color="blue">Event Logger (GPS, IMU, IMG & EXT)</font>==<br />
<br />
The FPGA-based Event Logger uses local clock for time-stamping data from Image Acquisition, External (Trigger) Input, GPS and IMU.<br />
<br />
* [[Event_logger|'''More information''']]<br />
===Record===<br />
====web====<br />
* Start: <br />
http://192.168.0.9/logger_launcher.php?cmd=start&file=/mnt/sda1/test.log&index=1&n=10000000<br />
* Stop:<br />
http://192.168.0.9/logger_launcher.php?cmd=stop<br />
* Help:<br />
http://192.168.0.9/logger_launcher.php<br />
<br />
====command line====<br />
* start:<br />
<font size='2'><br />
root@elphel393:~# cat /dev/imu > /path/filename.log<br />
</font><br />
* stop - CTRL-C or kill the process<br />
<br />
===Read===<br />
* http://192.168.0.9/read_imu_log.php (will display help)<br />
** on the first access creates /www/pages/logs/ (http://192.168.0.9/logs/)<br />
** link the recorded logs to /www/pages/logs/<br />
** refresh http://192.168.0.9/read_imu_log.php<br />
<br />
==<font color="blue">Set system time</font>==<br />
<br />
===Command line from PC===<br />
<font size='2'># Compare PC and camera clocks<br />
~$ ssh root@192.168.0.9 date;date -u<br />
# Write PC time into camera clock<br />
~$ ssh root@192.168.0.9 "date -s @`( date -u +"%s" )` && hwclock -w"<br />
<br />
===PHP===<br />
If in the current firmware includes '''http://192.168.0.9/utils.php''' then the clock is checked every time the index page is opened ('''http://192.168.0.9'''). The clock is then updated if the browser time differs from the camera time by more than 24h.<br />
<br />
It's also possible to force apply time using the following GET request:<br />
<nowiki>http://192.168.0.9/utils.php?cmd=time&apply&ts=<timestamp_in_ms></nowiki><br />
#example:<br />
<nowiki>http://192.168.0.9/utils.php?cmd=time&apply&ts=1589913066650</nowiki><br />
<br />
==<font color="blue">eSATA port switching</font>==<br />
* requres [[10389]]<br />
* available connections:<br />
** camera <=> internal SSD (default)<br />
** camera <=> external drive (external drive requires a separate power source)<br />
** PC <=> internal SSD<br />
* [[Sata_multiplexer_10389|'''More information''']]<br />
<br />
==<font color="blue">Firmware/software update</font>==<br />
[[Poky_2.0_manual#Write_files_to_media_and_boot|'''More information''']]<br />
<br />
==<font color="blue">Firmware images</font>==<br />
* [https://community.elphel.com/files/393/20210628/ '''20210628''']<br />
* [https://community.elphel.com/files/393/20200903/ 20200903]<br />
* [https://community.elphel.com/files/393/20200520/ 20200520]<br />
* [https://community.elphel.com/files/393/20200508/ 20200508]<br />
<br />
===Changelog===<br />
<font size='1'>'''==20220412=='''<br />
* Added websockets test<br />
* More options in format_disk (single partition, reformat already formatted disk,...)<br />
* Bug fixes<br />
<font size='1'>'''==20210628=='''<br />
* Added support for FLIR Boson sensors<br />
* Added decimation to external synchronization (triggering on each N-th incoming pulse). That was needed to run slower RGB sensors @12 Hz with Boson as a master at 60Hz<br />
* Enhanced inter-camera synchronization, added related kernel and PHP extension functionality.<br />
<font size='1'>'''==20200903=='''<br />
* switched to warrior branch for build<br />
* updated to kernel 4.19. This build was being under test for a while.<br />
'''==20200520=='''<br />
(rocko build)<br />
* Set time on main page access - taking browser time and writing to 10393 if times differ by 24h+.<br />
* Added script for sensor testing (switch to test pattern, check md5sum).<br />
Supporting MT9P006. Linked to main page.<br />
* Main page:<br />
* Added links to page displaying MJPEG stream in canvas<br />
* Added more controls (FPS, Manual Exposure and Auto Exposure Limit)<br />
* Added quick switch to 1080p@30fps (MT9P006)<br />
* Updated JPEG/JP4 decoding javascript plugin - less time (-10ms) spent on EXIF reading.<br />
* Created utils.php, currenty helps to GET-request:<br />
* ports configuration<br />
* set/get system time<br />
* Fixed snapshot button for cameras with unused ports in multicam/ UI.<br />
'''==20200508=='''<br />
(rocko build)<br />
* updated camogm<br />
* added FLIR Lepton driver to kernel<br />
* added FLIR Lepton record to device tree<br />
'''==20190321=='''<br />
* overall minor changes<br />
* fixed photofinish demo<br />
'''==20180511=='''<br />
* added cron program<br />
* multi cameras control interface<br />
* multi camera system info reporting<br />
* fixed rtc<br />
'''==20180416=='''<br />
* 20180419 - mt9f002: fixed changing window size<br />
* mt9f002: added triggered mode<br />
* mt9f002: added vertical and horizontal flips (mirror)<br />
'''==20180406=='''<br />
* added initial support for MT9F002 sensor: no triggered mode, no binning/decimation<br />
* display serial number in http://camera-ip:port/meta<br />
* decode jp4s on the index page (http://camera-ip)<br />
* turn off auto wb button for all ports on the index page<br />
'''==20180130=='''<br />
* added photo finish demo<br />
* fixed fps limit calcs for triggered mode<br />
'''==20180118=='''<br />
* raw.py & raw.php, see wiki.elphel.com<br />
* added python3 and python3-opencv<br />
'''==20180116=='''<br />
* raw pixel data downloading through membridge<br />
* added gcc,make<br />
'''==20180109=='''<br />
* fixed autoexposure<br />
'''==20171228=='''<br />
* + strace, ltrace, dmsetup<br />
* added to drivers: register devs to sysfs - nodes then created by udev<br />
'''==20171226=='''<br />
* kernel updated to 4.9 (from 4.0)<br />
* lots of drivers is updated to newer versions<br />
* +dm-crypt and cryptsetup<br />
'''==20171120=='''<br />
* bugfix - incorrect displaying of TRIG_PERIOD at init<br />
'''==20171115=='''<br />
* Fixed autocampars to let 10393 work with the mux board - 10359, see wiki.elphel.com for<br />
docs<br />
'''==20170823=='''<br />
* Fixed autocampars for multiple sensors getting desynced at init<br />
* Fixed Garmin GPS 18x USB driver<br />
'''==20170802=='''<br />
* fixed a page for taking snapshots - works in chrome and firefox for bigger images (>2MB)<br />
* enabled "Access-Control-Expose-Headers: Content-Disposition" and CORS<br />
'''==20170627=='''<br />
* viewing decoded jp4 format in camvc<br />
'''==20170623=='''<br />
* fixed incorrect default setting of the master channel<br />
</font><br />
<br />
==<font color="blue">Development</font>==<br />
Usage of [[Poky_manual|SDK]], which is Eclipse and project tree cloned from git.elphel.com, simplifies the development.<br />
At the same time lots of things can be done using Python, PHP, JavaScript or C/C++ (if compiled on hardware) and do not require SDK.<br />
<br />
==<font color="blue">Other info</font>==<br />
===Change default ip address===<br />
Modify '''''/etc/network/interfaces''''', sync the changes to the file system and reboot (or rerun init scripts).<br />
<br />
For firmware 20180511 or older, follow [[Fix_network_configuration|these instructions]] to fix network configuration (= disable setting ip address via '''/etc/elphel393/init_elphel393.py''').<br />
<br />
===Add a program or a shell command to autostart on boot===<br />
There's a way to do this using [https://unix.stackexchange.com/questions/56957/how-to-start-an-application-automatically-on-boot cron or init.d] but it might run before the sensors are initialized by init_elphel393.py. The recommended way is the following:<br />
* '''nano''' or '''vi'''<br />
<font size='2'><br />
ssh root@192.168.0.9<br />
''pass''<br />
root@elphel393:~# nano /etc/elphel393/init_elphel393.py<br />
''edit - save''<br />
''example: to launch the rtsp streamer - add '''shout("/usr/bin/str")''' to the end of the file''. shout() function is just a wrapper for '''subprocess.call(cmd,shell=True)'''<br />
</font><br />
Then:<br />
<font size='2'><br />
#boot from NAND flash?<br />
root@elphel393:~# overlay_sync 1 <br />
root@elphel393:~# shutdown -hP now<br />
#powercycle<br />
<br />
#boot from card?<br />
root@elphel393:~# sync<br />
root@elphel393:~# reboot -f<br />
</font><br />
<br />
===Set up histogram window and autoexposure parameters===<br />
[[Autoexposure|Read article]]<br />
===Tools for calibrated systems===<br />
* [[Elphel_Software_Kit_for_Ubuntu#ImageJ_and_Elphel_plugins_for_imageJ|Install ImageJ plugins]]<br />
** decode jp4 raw format<br />
** aberrations correction<br />
** distortion correction (pixel mapping)<br />
** rectification and projection<br />
** '''JP46 Reader camera''' - decode JP4/JP46<br />
** '''Eyesis correction''' - post-process JP4s using calibration data<br />
<br />
===Switch between ERS and GRR modes in MT9P006===<br />
* [[Electronic_Rolling_Shutter#ERS_and_GRR_in_MT9P001_on_10393|Read article]]<br />
===External/internal synchronization & triggering and FPS control for single/multi-camera systems===<br />
* [[Trigger_393]]<br />
<br />
===SSD/MMC/USB formatting===<br />
* [[Format_SSD_MMC]]<br />
===Boot modes===<br />
* [[Boot_options_393|Boot options]]<br />
===Pointers monitor===<br />
* Displays sensor, compressor and buffer states per 10393 port:<br />
<font size='2'><br />
http://192.168.0.9/pointers/<br />
</font><br />
<br />
===Powering from batteries (12V or 48V)===<br />
[[10393_power#Powering_from_batteries| 12V and 48V power options]]<br />
===Accessing raw pixel values===<br />
[[Working_with_raw_image_data|Working with raw pixel data (how to capture raw images)]]<br />
<br />
===Photo finish (linescan mode)===<br />
[[Photo-finish|Photo Finish]] (works for JP4 image format)<br />
<br />
===Controlling multiple cameras from single GUI===<br />
* [[Multi_camera_system_operation|Recording]]<br />
<br />
===Developers version's half enclosure===<br />
{|<br />
|valign='top'|[[File:10393 half enclosure 1.jpeg|thumb|200px]]<br />
|valign='top'|[[File:10393 half enclosure 2.jpeg|thumb|200px]]<br />
|}<br />
<br />
===Available lengths for cables for connecting sensors in custom setups===<br />
* [[FPC_cables|FPC cables]] - click for available lengths.<br />
* The cables are <font color='red'>asymmetrical</font> - for correct connecting a sensor to a system board see the figure below. As a rule of thumb, the cable's back side (no contacts) will be on the same side with the connector's cover.<br />
{|<br />
|[[Image:Fpc_cable_conn_10393.jpeg|300px|thumb|Connecting sensors to the system board]]<br />
|}<br />
<br />
==<font color="blue">Known problems</font>==<br />
* <font color='green'>'''[SOLVED]'''</font> Vertical artifacts in jpegs. Images are ok at 100% quality. Fixed, testing.<br />
* <font color='green'>'''[SOLVED]'''</font> http://192.168.0.9:232x/noexif/mimg - multipart jpeg displays corrupted frames from time to time. Reason: network bandwidth?<br />
* <font color='green'>'''[SOLVED]'''</font> Sometimes on power-on (NAND flash boot) cannot mount the card's rootfs partition. Kernel Panics. Power off/on. Soft "reboot -f" works ok.<br />
<font size='2'><br />
...<br />
<b>Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,2)</b><br />
...<br />
</font><br />
[[VFS:_Unable_to_mount_root_fs_on_unknown-block(179,2)|More info]]<br />
* <font color='green'>'''[SOLVED]'''</font> Changing exposure/quality/gains - can corrupt images - needs testing.<br />
<br />
* <font color='green'>'''[SOLVED]'''</font> After rewriting rootfs to &mu;SD card - some of the cards get a corrupted partition - re-partitioning (reformatting?) solves the problem.<br />
<font size='2'><br />
On the camera the rootfs is mounted as RW and some of the files are changed (also links created) -<br />
most of the changes are now moved to tmpfs but something might have been missed.<br />
</font><br />
<br />
==<font color="blue">Notes</font>==<br />
* <font color='green'>'''[SOLVED]'''</font> In case rootfs is on flash, it might make sense (or maybe not as the history is updated only once on session exit) to disable bash sessions command history - [http://stackoverflow.com/questions/18663078/disable-history-in-linux disable bash history]<br />
<br />
* <font color='green'>'''[SOLVED]'''</font> When using '''overlays''', deleting, existing in the lower layer, dirs can cause errors (hopefully it gets fixed someday), example: <br />
** /mnt/sda1 exists in lower layer: /tmp/rootfs.ro/tmp<br />
** upper layer is mounted to "/"<br />
<font size='2'><br />
# rmdir /mnt/sda1<br />
# mkdir /mnt/sda1<br />
mkdir: cannot create directory '/mnt/sda1': Operation not supported<br />
</font><br />
[[Category:393]]</div>Andrey.filippovhttps://wiki.elphel.com/index.php?title=Trigger_393&diff=13851Trigger 3932022-04-10T18:45:04Z<p>Andrey.filippov: /* External connector */</p>
<hr />
<div>==<font color="blue">Description</font>==<br />
[[10389]] board is required (and possibly [[103891]]).<br />
<br />
Use cases:<br />
* Trigger a single camera from external source<br />
* Synchronize multiple cameras to a master camera or external trigger source<br />
* Program frame rate<br />
<br />
The conditions of the trigger can be generated either internally or externally:<br />
* for external triggering a [[103891]] board and a 4-conductor 2.5mm audio plug with cable (example: [http://www.digikey.com/products/en?keywords=839-1029-ND digikey]) is required.<br />
* for internal triggering use J4-J6 connectors with a 4-pin flex cable: J4 - internal trigger source (also transmits timestamps that can be decoded by other cameras), J5-6 - receive trigger<br />
<br />
To program trigger go to: '''http://192.168.0.9/parsedit.php => External Trigger Controls'''<br />
<br />
'''NOTE: Be careful with changing parameters when TRIG=4. Camera drivers are driven by the frame sync interrupts from the sensor, so if the sensor is not triggered - everything can get stuck. The Program Ahead value sets the number of frame sync interrupts the camera will wait wait for until a parameter is reprogrammed.'''<br />
<br />
[[File:Parsedit screenshot 3.png|thumb|750px|External Trigger Controls page]]<br />
<br />
==<font color="blue">Parameters</font>==<br />
<br />
{| border="1"<br />
|-<br />
| ''parameter'' <br />
| ''description''<br />
|-<br />
| TRIG <br />
| Trigger mode. '''0x0''' - free running, '''0x4''' - triggered by external signal or FPGA timing generator, '''0x14''' - triggered in GRR mode<br />
|-<br />
| TRIG_MASTER<br />
| Master sensor_port (0..3) for triggering setup, other ports will have settings duplicated<br />
|-<br />
| TRIG_CONDITION <br />
| FPGA trigger sequencer trigger condition, 0 - internal, else dibits: 00 - do not use, 01 - keep, 10 - active low, 11 - active high for each GPIO[9:0] pin). 10389 board inverts signals, so 0x80000 - input from external connector, 0x08000 - input from internal flex cable (as in Eyesis)<br />
|-<br />
| TRIG_DELAY <br />
| FPGA trigger sequencer trigger delay, 32 bits in pixel clocks (100MHz or 10ns)<br />
|-<br />
| TRIG_OUT <br />
| FPGA trigger sequencer trigger output to GPIO, dibits: 00 - do not use, 01 - keep, 10 - active low GPIO output, 11 - active high GPIO output. 10389 board inverts signals, so 0x02000 - output to external connector (active high), 0x20000 - output to internal flex connector<br />
|-<br />
| TRIG_PERIOD <br />
| FPGA trigger sequencer output sync period (32 bits, in pixel clocks (100MHz or 10ns)). 0- stop. 1 - single, >=256 repetitive with specified period<br />
|-<br />
| TRIG_BITLENGTH <br />
| Bit length minus 1 (in pixel clock cycles) when transmitting/receiving timestamps, without timestamps the output pulse width is 8*(TRIG_BITLENGTH+1). Legal values 2..255<br />
|-<br />
| EXTERN_TIMESTAMP <br />
| When 1 camera will use external timestamp (received over inter-camera synchronization cable) if it is available (no action when external syncronization is not connected), when 0 - local timestamp will be used<br />
|-<br />
| XMIT_TIMESTAMP <br />
| Specify output signal sent through internal/external connector (defined by TRIG_OUT). 0 - transmit just sync pulse (8*(TRIG_BITLENGTH+1) pixel clock periods long), 1 - pulse+timestamp 64*(TRIG_BITLENGTH+1) pixel clock periods long<br />
|}<br />
<br />
==<font color="blue">Examples</font>==<br />
===Internal periodic trigger (10 fps, from fpga generator)===<br />
* http://192.168.0.9/parsedit.php?sensor_port=0&immediate&TRIG_CONDITION=0&TRIG_PERIOD=10000000&TRIG=4<br />
<br />
===Internal periodic trigger (4 fps, from fpga generator) + output the signal to external port===<br />
* http://192.168.0.9/parsedit.php?sensor_port=0&immediate&TRIG_CONDITION=0&TRIG_OUT=0x66555&TRIG_PERIOD=25000000&TRIG=4<br />
<br />
===External trigger receive (with possible self-triggering loop)===<br />
Here, internal generator is routed to sync the cable output wires.<br />
'''If the output wires are connected to the input wires (red+black and white+green) the camera will be self-triggering. '''<br />
If the wires are not connected - use external source - apply "plus" to black, "minus" to green ([[103891|check colors and pinout]]):<br />
<br />
http://192.168.0.9/parsedit.php?sensor_port=0&immediate&TRIG_CONDITION=0x95555&TRIG_OUT=0x66555&TRIG_PERIOD=100000000&TRIG=4<br />
* at the same time the fpga generator outputs a 1 fps signal - if the sync cable wires are properly connected the camera can be triggered from this 'external' signal<br />
<br />
===External trigger receive (external source only)===<br />
The sync cable wires can be looped or not - does not matter.<br />
http://192.168.0.9/parsedit.php?sensor_port=0&immediate&TRIG_CONDITION=0x95555&TRIG_OUT=0x66555&TRIG_PERIOD=100000000&TRIG=4<br />
* at the same time the fpga generator outputs a 1 fps signal - if the sync cable wires are properly connected the camera can be triggered from this 'external' signal<br />
<br />
===Recover from missing external trigger signal to internal trigger===<br />
* http://192.168.0.9/parsedit.php?sensor_port=0&immediate&TRIG_CONDITION=0*-2<br />
** '''*-2''' - apply value parameter in the current frame (if not specified, the default is 3)<br />
<br />
===Manual triggering from PC===<br />
====Enable====<br />
<font size='2'><br />
http://192.168.0.9:2323/trig/pointers<br />
<br />
* TRIG=4 should be set in advance<br />
* The command automatically sets a single-shot trigger mode with TRIG_PERIOD=0x1, but it writes the register directly into the FPGA, <br />
not updating the TRIG_PERIOD in the PHP interface:<br />
http://192.168.0.9/parsedit.php?TRIG&TRIG_CONDITION&TRIG_DELAY&TRIG_OUT&TRIG_PERIOD&TRIG_BITLENGTH&EXTERN_TIMESTAMP&XMIT_TIMESTAMP&refresh<br />
</font><br />
<br />
====Trigger/Refresh====<br />
<font size='2'><br />
http://192.168.0.9:8081/trig/pointers<br />
<br />
====Check status====<br />
http://192.168.0.9/parsedit.php?immediate&TRIG&TRIG_PERIOD&SENS_AVAIL&FRAME<br />
<br />
====Disable====<br />
=====Update the TRIG_PERIOD in the current frame=====<br />
* http://192.168.0.9/parsedit.php?sensor_port=0&immediate&TRIG_PERIOD=10000000*-2<br />
<br />
=====Update the TRIG_PERIOD from the user interface=====<br />
* http://192.168.0.9/parsedit.php?TRIG&TRIG_CONDITION&TRIG_DELAY&TRIG_OUT&TRIG_PERIOD&TRIG_BITLENGTH&EXTERN_TIMESTAMP&XMIT_TIMESTAMP&refresh<br />
* Refresh until the changes are applied (with Program Ahead = 3 it's 3 times):<br />
http://192.168.0.9:8081/trig/pointers<br />
<br />
<br />
==<font color="blue">Links</font>==<br />
* [[10389]] extension board<br />
* [[103891]] adapter board for external trigger connection<br />
<br />
==<font color="blue">10389 trigger testing</font>==<br />
<br />
===External connector===<br />
In this test the camera triggers itself via audio cable. For cable wiring see [[103891]]. <br />
* To test:<br />
- connect a sensor to port 0<br />
- http://192.168.0.9/parsedit.php?sensor_port=0&immediate&TRIG_CONDITION=0&TRIG_OUT=0x66555&TRIG_PERIOD=25000000&TRIG=4<br />
visual: LED is blinking<br />
software: frame counter is running<br />
<br />
* It's easy to modify the cable to trigger itself and other multiple cameras by connecting together red and black wires (+) and white with green (-). For self-testing (external trigger loop back) it is sufficient, for LED - connect anode to "+" (red+black), cathode - to "-" (white+green).<br />
<br />
{|<br />
|[[File:10389 extsync selftest.jpeg|thumb|400px]]<br />
|}<br />
<br />
Turn on external trigger loop back (cable should be inserted):<br />
http://192.168.0.9/parsedit.php?sensor_port=0&immediate&TRIG_CONDITION=0x80000&TRIG_OUT=0x66555&TRIG_PERIOD=25000000&TRIG=4<br />
<br />
Or use interactive page:<br />
http://192.168.0.9/parsedit.php?sensor_port=0&embed=0.25&title=Parameters+for+groups:+trigger+&TRIG&TRIG_MASTER&TRIG_CONDITION=0x80000&TRIG_DELAY&TRIG_OUT=0x66555&TRIG_PERIOD=25000000&TRIG_BITLENGTH&EXTERN_TIMESTAMP&XMIT_TIMESTAMP&TRIG_DECIMATE&THIS_FRAME&refresh<br />
<br />
And then click "Apply" button.<br />
<br />
Both variants should turn camera into external loop back mode with 0.25s period (4 fps). If the page (and the camera) hangs, the loop is not working. For troubleshooting you may restart the camera, open<br />
http://192.168.0.9/parsedit.php?sensor_port=0&embed=0.25&title=Parameters+for+groups:+trigger+&TRIG&TRIG_MASTER&TRIG_CONDITION=0&TRIG_DELAY&TRIG_OUT=0x66555&TRIG_PERIOD=25000000&TRIG_BITLENGTH&EXTERN_TIMESTAMP&XMIT_TIMESTAMP&TRIG_DECIMATE&THIS_FRAME&refresh<br />
<br />
and press "apply". The camera will continue using internal trigger (TRIG_CONDITION=0) but still generate trigger output (TRIG_OUT=0x66555). This output can be controlled by either the LED soldered to the cable or the oscilloscope (ground to the green+white, signal - red+black - it should show not just a pulse but a encoded timestamp some 22us long. Changing TRIG_CONDITION to 0x80000 (enter 80000 into "New value/Hex" field without "0x" and press "Apply") should activate loop back, and if it works then "Refresh" button should cause new "THIS_FRAME" field value. If it does not work - trigger input does not reach camera - bad cable or connector.<br />
<br />
===Internal connectors===<br />
In this test the camera triggers itself via 4-pin flex cable. <br />
* Connect as displayed on the pictures below.<br />
** J4 - trigger output (master port)<br />
** J5-J6 - trigger input (slave ports)<br />
* To test:<br />
- connect a sensor to port 0<br />
- http://192.168.0.9/parsedit.php?sensor_port=0&immediate&TRIG_CONDITION=0x8000&TRIG_OUT=0x66555&TRIG_PERIOD=25000000&TRIG=4<br />
software: frame counter is running<br />
* To sync multiple camera, example:<br />
cable 1: camera1 (J4) -> camera2 (J6)<br />
cable 2: camera2 (J5) -> camera3 (J6)<br />
cable 3: camera3 (J5) -> camera4 (J6)<br />
etc.<br />
{|<br />
|valign='top'|[[File:10389 intsync selftest.jpeg|thumb|400px]]<br />
|valign='top'|[[File:10389 intsync selftest closeup.jpeg|thumb|400px]]<br />
|}<br />
<br />
===Sync example: from external to internal (chaining)===<br />
* The simplest synchronization would be making a custom audio cable to sync all cameras in the system<br />
* In case there are multiple cameras in the same enclosure it might make sense to sync them by chaining using 4-pin flex cables<br />
{|<br />
|valign='top'|[[File:10389 sync example 1.jpeg|thumb|400px]]<br />
|}<br />
<br />
<br />
[[Category:393]]</div>Andrey.filippovhttps://wiki.elphel.com/index.php?title=Poky_manual&diff=13108Poky manual2022-01-27T21:00:42Z<p>Andrey.filippov: /* Setup */</p>
<hr />
<div>==<font color="blue">Description</font>==<br />
Build the firmware for Elphel 10393 series camera systems from scratch.<br />
<br />
Prebuilt releases can be found [https://community.elphel.com/files/393/ here].<br />
<br />
==<font color="blue">Use cases</font>==<br />
* Update Linux Kernel when developing a driver<br />
* Include application to the default firmware package<br />
* Update Elphel's PHP extension<br />
* C/C++ applications if developed on PC require a cross-compiler and require Yocto installation or some other alternative.<br />
<br />
Other projects written in Python, PHP, Javascript, HTML, C/C++ (gcc is installed on the system board) can be developed on the camera. Installing the framework is not required but it can simplify the development process.<br />
<br />
==<font color="blue">Description</font>==<br />
<br />
* Building embedded Linux image for Zynq ARMv7 platform - Elphel 10393 board<br />
* Yocto Poky revision = 2.7.1 (Warrior) - <font color="green">builds in Kubuntu 20.04.</font> <font color="red">Older OSes are not supported. Roll back to get built in 16.04.</font><br />
* <s>Yocto Poky revision = 2.4 (Rocko) - <font color="green">builds in Kubuntu 16.04.</font> <font color="red">Won't build in 18.04 or 20.04.</font></s><br />
* <s>Yocto Poky revision = 2.0 (Jethro)</s><br />
<br />
==<font color="blue">Features</font>==<br />
* Environment is set up with a single script<br />
* All Elphel projects are configured for Eclipse IDE:<br />
** fpga projects (verilog)<br />
** kernel<br />
** applications projects<br />
* All steps for fpga projects are run from Eclipse IDE<br />
** Read about [http://blog.elphel.com/2016/05/tutorial-02-eclipse-based-fpga-development-environment-for-elphel-cameras/ setting up Eclipse based FPGA development]<br />
** [https://git.elphel.com/Elphel/vdt-plugin VDT Plugin repository]<br />
<br />
* Once everything is built it supports updating software projects (files and binaries) on the target system<br />
** access is set up in yocto's ''local.conf'' (see ''setup.py'' output) + ''ssh-copy-id''<br />
** ''bitbake some-app -c target_scp'' from the command line or Eclipse IDE - see examples in '''elphel-apps-...''' at [https://git.elphel.com/Elphel Git]<br />
<br />
==<font color="blue">Requirements</font>==<br />
* Kubuntu 20.04 x64<br />
* <s>Kubuntu 18.04 x64 (as of Dec 2018) - Poky: 2.7.1 Warrior (not tested but might build w/o problems)</s><br />
* <s>Kubuntu 16.04 x64 (as of Dec 2018) - Poky: 2.4 Rocko, 2.7.1 Warrior</s><br />
<br />
==<font color="blue">Output files</font>==<br />
The names are listed as they appear in the u-boot configuration header file - actual output files have different names:<br />
{| class="wikitable"<br />
|-<br />
! File(s)<br />
! Build Command<br />
! Description<br />
|-<br />
| <font color='darkblue'>'''boot.bin'''</font><br />
| ''bitbake u-boot''<br />
| u-boot as the first stage bootloader = Secondary Program Loader (SPL) that boots '''u-boot-dtb.img'''<br />
|-<br />
| <font color='darkblue'>'''u-boot-dtb.img'''</font><br />
| ''bitbake u-boot''<br />
| full size u-boot with a stripped device tree (''cat u-boot.img some_stripped_devicetree.dtb > u-boot-dtb.img'')<br />
|-<br />
|valign='top'| <font color='darkblue'>'''devicetree.dtb'''</font><br />
| bitbake device-tree<br />
| device tree with listed interfaces, zynq registers, interrupts and drivers<br />
* ''elphel393/bootable-images/mmc/devicetree.dtb'' - mount rootfs from mmc partition<br />
* ''elphel393/bootable-images/nand/devicetree.dtb'' - mount rootfs from NAND flash<br />
|-<br />
| <font color='darkblue'>'''uImage'''</font><br />
| ''bitbake linux-xlnx''<br />
| kernel, drivers<br />
|-<br />
| <font color='darkblue'>'''rootfs.ubifs''', '''rootfs.ubi''', '''rootfs.tar.gz'''</font><br />
| ''bitbake core-image-elphel393''<br />
| rootfs in different formats - *.ubi* for NAND, *.tar.gz for mmc<br />
|}<br />
<br />
The file are located at '''elphel393/bootable-images/''', which is a link to poky's deploy directory '''elphel393/poky/build/tmp/deploy/images/elphel393/'''<br />
<br />
* complete set of files for rootfs in NAND Flash: ''elphel393/bootable-images/nand/''<br />
* complete set of files for rootfs on MMC (micro SD card): ''elphel393/bootable-images/mmc/''<br />
<br />
==<font color="blue">Write files to media and boot</font>==<br />
===Boot from micro SD card===<br />
* Use recovery or regular &mu;SD card<br />
* EXT4 partition mounted as '''/'''<br />
[[Sd_boot_rootfs|Detailed instructions]]<br />
<br />
===Boot from NAND flash===<br />
* The default boot option - power on.<br />
* A UBIFS image is written to /dev/mtd4 - is mounted as '''/'''<br />
[[NAND_flash_boot_rootfs|Detailed instructions]]<br />
<br />
===Notes===<br />
* [[Boot_options_393|'''Read more''']] about boot options.<br />
<br />
==<font color="blue">Setup</font>==<br />
* Before building<br />
Installing some dependencies:<br />
sudo apt install git build-essential chrpath diffstat gawk makeinfo zlib1g-dev python3-numpy<br />
Installing old python2.7 (bitbake snapshot that we used has problem with python3.8):<br />
sudo apt install python2.7<br />
sudo ln -s python2.7 python2<br />
sudo ln -s python2.7 python<br />
<br />
* Poky 2.7.1 Warrior (Kubuntu 20.04)<br />
<font size='2'><br />
git clone -b '''warrior''' https://git.elphel.com/Elphel/elphel393.git<br />
<br />
If you are a developer and plan to commit changes you should use ssh access instead: git clone -b warrior git@git.elphel.com:Elphel/elphel393.git<br />
<br />
<br />
cd elphel393<br />
./setup.py<br />
cd poky<br />
. ./oe-init-build-env<br />
bitbake u-boot device-tree linux-xlnx core-image-elphel393<br />
</font><br />
<br />
* <s>Poky 2.4 Rocko (Kubuntu 16.04)<br />
<font size='2'><br />
git clone -b '''rocko''' https://git.elphel.com/Elphel/elphel393.git<br />
cd elphel393<br />
./setup.py<br />
cd poky<br />
. ./oe-init-build-env<br />
bitbake u-boot device-tree linux-xlnx core-image-elphel393<br />
<!--''Temporary: linux-xlnx in Rocko depends on branch 'lwir' for x393. Change in projects.json line 42 from 'master' to 'lwir'.''--><br />
</font></s><br />
<br />
* Notes (required actions are already listed above): When trying to run bitbake on a new install got problems with older bitbake version (current build uses specific snapshot) and python3.8. So I install old python2.7 and linked it:<br />
sudo apt install python2.7<br />
sudo ln -s python2.7 python2<br />
sudo ln -s python2.7 python<br />
<br />
After this bitbake just complained about missing tools (git, build-essential were already installed):<br />
<br />
sudo apt install chrpath diffstat gawk makeinfo<br />
<br />
Program test_mcntrl.py that builds x393.h header files from FPGA code that runs during ./setup.py requires numpy and results in error output if missing Still setup.py continues, you need to look through its output few lines after<br />
* x393<br />
git host: git.elphel.com<br />
Clone and checkout: x393<br />
<br />
You may install numpy with<br />
sudo apt install python3-numpy<br />
<br />
If you did not notice missing numpy, then during bitbake you will get error "build No rule to make target 'drivers/elphel/x393.o', needed by 'drivers/elphel/built-in.a'. Stop." in that case you need to install numpy, re-run setup.py (make sure numpy error is gone) then re-create linux kernel links during next build by erasing old ones:<br />
bitbake linux-xlnx -c clean<br />
and re-running<br />
bitbake linux-xlnx device-tree core-image-elphel393<br />
<br />
When building php: configure: error: zip support requires ZLIB. Use --with-zlib-dir=<DIR> to specify prefix where ZLIB include and library are located<br />
sudo apt install zlib1g-dev<br />
<br />
==<font color="blue">Compare '''built''' vs '''deployed''' software versions</font>==<br />
<font size='2'><br />
cd elphel393<br />
./check_versions.py root@192.168.0.9<br />
</font><br />
<br />
{|<br />
|[[File:Check versions.png|thumb|400px|check_versions.py output in terminal (web-393 revision on PC is ahead of the one installed on the camera)]]<br />
|}<br />
<br />
==<font color="blue">Details for development</font>==<br />
[[Development_for_10393|'''Development for 10393''']]</div>Andrey.filippovhttps://wiki.elphel.com/index.php?title=Using_minicom_to_connect_to_Elphel393_camera&diff=13586Using minicom to connect to Elphel393 camera2022-01-27T19:05:41Z<p>Andrey.filippov: </p>
<hr />
<div>Elphel393 series cameras have built-in USB to serial converter which allows users to get access to serial console. You need microUSB-USB cable to connect a camera to your PC and a terminal software installed on the PC. We use minicom on Kubuntu for this purpose so this short note will describe how to connect to a camera using minicom.<br />
<br />
First, you need to install minicom on the PC if have not done it before. Open a terminal on your PC and use the following command on Debian based systems like Ubuntu or Kubuntu:<br />
<br />
~$sudo apt-get install minicom<br />
<br />
or do the same with your preferred package manager.<br />
minicom connects to a camera via /dev/ttyUSB0 device which is in ''dialout'' group by default:<br />
<br />
~$ ls -l /dev/ttyUSB0 <br />
crw-rw---- 1 root dialout 188, 0 May 14 14:26 /dev/ttyUSB0<br />
<br />
You should add your user to ''dialout'' group to make it easier to connect to camera without root permissions:<br />
<br />
~$ sudo adduser elphel dialout<br />
[sudo] password for elphel: <br />
Adding user `elphel' to group `dialout' ...<br />
Adding user elphel to group dialout<br />
Done.<br />
<br />
Now user ''elphel'' is in group ''dialout'',<br />
<br />
$ cat /etc/group | grep dialout<br />
dialout:x:20:elphel<br />
<br />
but new settings have not been applyed yet:<br />
<br />
~$ groups<br />
elphel adm sudo lpadmin sambashare libvirtd<br />
<br />
You need to logout from the system and login again. Now your user is added to the group and new settings are applied:<br />
<br />
~$ groups<br />
elphel adm dialout sudo lpadmin sambashare libvirtd<br />
<br />
The last step is minicom configuration. minicom tries to connect to a device which is specified in its configuration file /etc/minicom/minrc.dfl and this device is not what we are trying to connect to. If you start minicom with its default config file you will get an error:<br />
<br />
~$ minicom -c on<br />
minicom: cannot open /dev/tty8: Permission denied<br />
<br />
It should be started in setup mode with root permissions:<br />
<br />
~$ sudo minicom -s<br />
<br />
Go to 'Serial port setup',<br />
change 'Serial Device'(A) to /dev/ttyUSB0,<br />
turn off 'Hardware Flow Control'(F), <br />
leave default 'Bps/Par/Bits' (E) at 115200 8N1<br />
and 'Save setup as dfl' in the higher menu.<br />
Now you can start minicom<br />
<br />
~$ minicom -c on<br />
<br />
and it will connect to a camera.</div>Andrey.filippovhttps://wiki.elphel.com/index.php?title=Poky_manual&diff=13107Poky manual2022-01-26T22:26:08Z<p>Andrey.filippov: /* Setup */</p>
<hr />
<div>==<font color="blue">Description</font>==<br />
Build the firmware for Elphel 10393 series camera systems from scratch.<br />
<br />
Prebuilt releases can be found [https://community.elphel.com/files/393/ here].<br />
<br />
==<font color="blue">Use cases</font>==<br />
* Update Linux Kernel when developing a driver<br />
* Include application to the default firmware package<br />
* Update Elphel's PHP extension<br />
* C/C++ applications if developed on PC require a cross-compiler and require Yocto installation or some other alternative.<br />
<br />
Other projects written in Python, PHP, Javascript, HTML, C/C++ (gcc is installed on the system board) can be developed on the camera. Installing the framework is not required but it can simplify the development process.<br />
<br />
==<font color="blue">Description</font>==<br />
<br />
* Building embedded Linux image for Zynq ARMv7 platform - Elphel 10393 board<br />
* Yocto Poky revision = 2.7.1 (Warrior) - <font color="green">builds in Kubuntu 20.04.</font> <font color="red">Older OSes are not supported. Roll back to get built in 16.04.</font><br />
* <s>Yocto Poky revision = 2.4 (Rocko) - <font color="green">builds in Kubuntu 16.04.</font> <font color="red">Won't build in 18.04 or 20.04.</font></s><br />
* <s>Yocto Poky revision = 2.0 (Jethro)</s><br />
<br />
==<font color="blue">Features</font>==<br />
* Environment is set up with a single script<br />
* All Elphel projects are configured for Eclipse IDE:<br />
** fpga projects (verilog)<br />
** kernel<br />
** applications projects<br />
* All steps for fpga projects are run from Eclipse IDE<br />
** Read about [http://blog.elphel.com/2016/05/tutorial-02-eclipse-based-fpga-development-environment-for-elphel-cameras/ setting up Eclipse based FPGA development]<br />
** [https://git.elphel.com/Elphel/vdt-plugin VDT Plugin repository]<br />
<br />
* Once everything is built it supports updating software projects (files and binaries) on the target system<br />
** access is set up in yocto's ''local.conf'' (see ''setup.py'' output) + ''ssh-copy-id''<br />
** ''bitbake some-app -c target_scp'' from the command line or Eclipse IDE - see examples in '''elphel-apps-...''' at [https://git.elphel.com/Elphel Git]<br />
<br />
==<font color="blue">Requirements</font>==<br />
* Kubuntu 20.04 x64<br />
* <s>Kubuntu 18.04 x64 (as of Dec 2018) - Poky: 2.7.1 Warrior (not tested but might build w/o problems)</s><br />
* <s>Kubuntu 16.04 x64 (as of Dec 2018) - Poky: 2.4 Rocko, 2.7.1 Warrior</s><br />
<br />
==<font color="blue">Output files</font>==<br />
The names are listed as they appear in the u-boot configuration header file - actual output files have different names:<br />
{| class="wikitable"<br />
|-<br />
! File(s)<br />
! Build Command<br />
! Description<br />
|-<br />
| <font color='darkblue'>'''boot.bin'''</font><br />
| ''bitbake u-boot''<br />
| u-boot as the first stage bootloader = Secondary Program Loader (SPL) that boots '''u-boot-dtb.img'''<br />
|-<br />
| <font color='darkblue'>'''u-boot-dtb.img'''</font><br />
| ''bitbake u-boot''<br />
| full size u-boot with a stripped device tree (''cat u-boot.img some_stripped_devicetree.dtb > u-boot-dtb.img'')<br />
|-<br />
|valign='top'| <font color='darkblue'>'''devicetree.dtb'''</font><br />
| bitbake device-tree<br />
| device tree with listed interfaces, zynq registers, interrupts and drivers<br />
* ''elphel393/bootable-images/mmc/devicetree.dtb'' - mount rootfs from mmc partition<br />
* ''elphel393/bootable-images/nand/devicetree.dtb'' - mount rootfs from NAND flash<br />
|-<br />
| <font color='darkblue'>'''uImage'''</font><br />
| ''bitbake linux-xlnx''<br />
| kernel, drivers<br />
|-<br />
| <font color='darkblue'>'''rootfs.ubifs''', '''rootfs.ubi''', '''rootfs.tar.gz'''</font><br />
| ''bitbake core-image-elphel393''<br />
| rootfs in different formats - *.ubi* for NAND, *.tar.gz for mmc<br />
|}<br />
<br />
The file are located at '''elphel393/bootable-images/''', which is a link to poky's deploy directory '''elphel393/poky/build/tmp/deploy/images/elphel393/'''<br />
<br />
* complete set of files for rootfs in NAND Flash: ''elphel393/bootable-images/nand/''<br />
* complete set of files for rootfs on MMC (micro SD card): ''elphel393/bootable-images/mmc/''<br />
<br />
==<font color="blue">Write files to media and boot</font>==<br />
===Boot from micro SD card===<br />
* Use recovery or regular &mu;SD card<br />
* EXT4 partition mounted as '''/'''<br />
[[Sd_boot_rootfs|Detailed instructions]]<br />
<br />
===Boot from NAND flash===<br />
* The default boot option - power on.<br />
* A UBIFS image is written to /dev/mtd4 - is mounted as '''/'''<br />
[[NAND_flash_boot_rootfs|Detailed instructions]]<br />
<br />
===Notes===<br />
* [[Boot_options_393|'''Read more''']] about boot options.<br />
<br />
==<font color="blue">Setup</font>==<br />
* Before building<br />
Installing some dependencies:<br />
sudo apt install git build-essential chrpath diffstat gawk makeinfo zlib1g-dev python3-numpy<br />
Installing old python2.7 (bitbake snapshot that we used has problem with python3.8):<br />
sudo apt install python2.7<br />
sudo ln -s python2.7 python2<br />
sudo ln -s python2.7 python<br />
<br />
* Poky 2.7.1 Warrior (Kubuntu 20.04)<br />
<font size='2'><br />
git clone -b '''warrior''' https://git.elphel.com/Elphel/elphel393.git<br />
cd elphel393<br />
./setup.py<br />
cd poky<br />
. ./oe-init-build-env<br />
bitbake u-boot device-tree linux-xlnx core-image-elphel393<br />
</font><br />
<br />
* <s>Poky 2.4 Rocko (Kubuntu 16.04)<br />
<font size='2'><br />
git clone -b '''rocko''' https://git.elphel.com/Elphel/elphel393.git<br />
cd elphel393<br />
./setup.py<br />
cd poky<br />
. ./oe-init-build-env<br />
bitbake u-boot device-tree linux-xlnx core-image-elphel393<br />
<!--''Temporary: linux-xlnx in Rocko depends on branch 'lwir' for x393. Change in projects.json line 42 from 'master' to 'lwir'.''--><br />
</font></s><br />
<br />
* Notes (required actions are already listed above): When trying to run bitbake on a new install got problems with older bitbake version (current build uses specific snapshot) and python3.8. So I install old python2.7 and linked it:<br />
sudo apt install python2.7<br />
sudo ln -s python2.7 python2<br />
sudo ln -s python2.7 python<br />
<br />
After this bitbake just complained about missing tools (git, build-essential were already installed):<br />
<br />
sudo apt install chrpath diffstat gawk makeinfo<br />
<br />
Program test_mcntrl.py that builds x393.h header files from FPGA code that runs during ./setup.py requires numpy and results in error output if missing Still setup.py continues, you need to look through its output few lines after<br />
* x393<br />
git host: git.elphel.com<br />
Clone and checkout: x393<br />
<br />
You may install numpy with<br />
sudo apt install python3-numpy<br />
<br />
If you did not notice missing numpy, then during bitbake you will get error "build No rule to make target 'drivers/elphel/x393.o', needed by 'drivers/elphel/built-in.a'. Stop." in that case you need to install numpy, re-run setup.py (make sure numpy error is gone) then re-create linux kernel links during next build by erasing old ones:<br />
bitbake linux-xlnx -c clean<br />
and re-running<br />
bitbake linux-xlnx device-tree core-image-elphel393<br />
<br />
When building php: configure: error: zip support requires ZLIB. Use --with-zlib-dir=<DIR> to specify prefix where ZLIB include and library are located<br />
sudo apt install zlib1g-dev<br />
<br />
==<font color="blue">Compare '''built''' vs '''deployed''' software versions</font>==<br />
<font size='2'><br />
cd elphel393<br />
./check_versions.py root@192.168.0.9<br />
</font><br />
<br />
{|<br />
|[[File:Check versions.png|thumb|400px|check_versions.py output in terminal (web-393 revision on PC is ahead of the one installed on the camera)]]<br />
|}<br />
<br />
==<font color="blue">Details for development</font>==<br />
[[Development_for_10393|'''Development for 10393''']]</div>Andrey.filippovhttps://wiki.elphel.com/index.php?title=Poky_manual&diff=13106Poky manual2022-01-26T22:25:00Z<p>Andrey.filippov: /* Setup */</p>
<hr />
<div>==<font color="blue">Description</font>==<br />
Build the firmware for Elphel 10393 series camera systems from scratch.<br />
<br />
Prebuilt releases can be found [https://community.elphel.com/files/393/ here].<br />
<br />
==<font color="blue">Use cases</font>==<br />
* Update Linux Kernel when developing a driver<br />
* Include application to the default firmware package<br />
* Update Elphel's PHP extension<br />
* C/C++ applications if developed on PC require a cross-compiler and require Yocto installation or some other alternative.<br />
<br />
Other projects written in Python, PHP, Javascript, HTML, C/C++ (gcc is installed on the system board) can be developed on the camera. Installing the framework is not required but it can simplify the development process.<br />
<br />
==<font color="blue">Description</font>==<br />
<br />
* Building embedded Linux image for Zynq ARMv7 platform - Elphel 10393 board<br />
* Yocto Poky revision = 2.7.1 (Warrior) - <font color="green">builds in Kubuntu 20.04.</font> <font color="red">Older OSes are not supported. Roll back to get built in 16.04.</font><br />
* <s>Yocto Poky revision = 2.4 (Rocko) - <font color="green">builds in Kubuntu 16.04.</font> <font color="red">Won't build in 18.04 or 20.04.</font></s><br />
* <s>Yocto Poky revision = 2.0 (Jethro)</s><br />
<br />
==<font color="blue">Features</font>==<br />
* Environment is set up with a single script<br />
* All Elphel projects are configured for Eclipse IDE:<br />
** fpga projects (verilog)<br />
** kernel<br />
** applications projects<br />
* All steps for fpga projects are run from Eclipse IDE<br />
** Read about [http://blog.elphel.com/2016/05/tutorial-02-eclipse-based-fpga-development-environment-for-elphel-cameras/ setting up Eclipse based FPGA development]<br />
** [https://git.elphel.com/Elphel/vdt-plugin VDT Plugin repository]<br />
<br />
* Once everything is built it supports updating software projects (files and binaries) on the target system<br />
** access is set up in yocto's ''local.conf'' (see ''setup.py'' output) + ''ssh-copy-id''<br />
** ''bitbake some-app -c target_scp'' from the command line or Eclipse IDE - see examples in '''elphel-apps-...''' at [https://git.elphel.com/Elphel Git]<br />
<br />
==<font color="blue">Requirements</font>==<br />
* Kubuntu 20.04 x64<br />
* <s>Kubuntu 18.04 x64 (as of Dec 2018) - Poky: 2.7.1 Warrior (not tested but might build w/o problems)</s><br />
* <s>Kubuntu 16.04 x64 (as of Dec 2018) - Poky: 2.4 Rocko, 2.7.1 Warrior</s><br />
<br />
==<font color="blue">Output files</font>==<br />
The names are listed as they appear in the u-boot configuration header file - actual output files have different names:<br />
{| class="wikitable"<br />
|-<br />
! File(s)<br />
! Build Command<br />
! Description<br />
|-<br />
| <font color='darkblue'>'''boot.bin'''</font><br />
| ''bitbake u-boot''<br />
| u-boot as the first stage bootloader = Secondary Program Loader (SPL) that boots '''u-boot-dtb.img'''<br />
|-<br />
| <font color='darkblue'>'''u-boot-dtb.img'''</font><br />
| ''bitbake u-boot''<br />
| full size u-boot with a stripped device tree (''cat u-boot.img some_stripped_devicetree.dtb > u-boot-dtb.img'')<br />
|-<br />
|valign='top'| <font color='darkblue'>'''devicetree.dtb'''</font><br />
| bitbake device-tree<br />
| device tree with listed interfaces, zynq registers, interrupts and drivers<br />
* ''elphel393/bootable-images/mmc/devicetree.dtb'' - mount rootfs from mmc partition<br />
* ''elphel393/bootable-images/nand/devicetree.dtb'' - mount rootfs from NAND flash<br />
|-<br />
| <font color='darkblue'>'''uImage'''</font><br />
| ''bitbake linux-xlnx''<br />
| kernel, drivers<br />
|-<br />
| <font color='darkblue'>'''rootfs.ubifs''', '''rootfs.ubi''', '''rootfs.tar.gz'''</font><br />
| ''bitbake core-image-elphel393''<br />
| rootfs in different formats - *.ubi* for NAND, *.tar.gz for mmc<br />
|}<br />
<br />
The file are located at '''elphel393/bootable-images/''', which is a link to poky's deploy directory '''elphel393/poky/build/tmp/deploy/images/elphel393/'''<br />
<br />
* complete set of files for rootfs in NAND Flash: ''elphel393/bootable-images/nand/''<br />
* complete set of files for rootfs on MMC (micro SD card): ''elphel393/bootable-images/mmc/''<br />
<br />
==<font color="blue">Write files to media and boot</font>==<br />
===Boot from micro SD card===<br />
* Use recovery or regular &mu;SD card<br />
* EXT4 partition mounted as '''/'''<br />
[[Sd_boot_rootfs|Detailed instructions]]<br />
<br />
===Boot from NAND flash===<br />
* The default boot option - power on.<br />
* A UBIFS image is written to /dev/mtd4 - is mounted as '''/'''<br />
[[NAND_flash_boot_rootfs|Detailed instructions]]<br />
<br />
===Notes===<br />
* [[Boot_options_393|'''Read more''']] about boot options.<br />
<br />
==<font color="blue">Setup</font>==<br />
* Before building<br />
Installing some dependencies:<br />
sudo apt install git build-essential chrpath diffstat gawk makeinfo zlib1g-dev python3-numpy<br />
Installing old python2.7 (bitbake snapshot that we used has problem with python3.8):<br />
sudo apt install python2.7<br />
sudo ln -s python2.7 python2<br />
sudo ln -s python2.7 python<br />
<br />
* Poky 2.7.1 Warrior (Kubuntu 20.04)<br />
<font size='2'><br />
git clone -b '''warrior''' https://git.elphel.com/Elphel/elphel393.git<br />
cd elphel393<br />
./setup.py<br />
cd poky<br />
. ./oe-init-build-env<br />
bitbake u-boot device-tree linux-xlnx core-image-elphel393<br />
</font><br />
<br />
* <s>Poky 2.4 Rocko (Kubuntu 16.04)<br />
<font size='2'><br />
git clone -b '''rocko''' https://git.elphel.com/Elphel/elphel393.git<br />
cd elphel393<br />
./setup.py<br />
cd poky<br />
. ./oe-init-build-env<br />
bitbake u-boot device-tree linux-xlnx core-image-elphel393<br />
<!--''Temporary: linux-xlnx in Rocko depends on branch 'lwir' for x393. Change in projects.json line 42 from 'master' to 'lwir'.''--><br />
</font></s><br />
<br />
* Notes (required actions already listed above): When trying to run bitbake on a new install got problems with older bitbake version (current build uses specific snapshot) and python3.8. So I install old python2.7 and linked it:<br />
sudo apt install python2.7<br />
sudo ln -s python2.7 python2<br />
sudo ln -s python2.7 python<br />
<br />
After this bitbake just complained about missing tools (git, build-essential were already installed):<br />
<br />
sudo apt install chrpath diffstat gawk makeinfo<br />
<br />
Program test_mcntrl.py that builds x393.h header files from FPGA code that runs during ./setup.py requires numpy and results in error output if missing Still setup.py continues, you need to look through its output few lines after<br />
* x393<br />
git host: git.elphel.com<br />
Clone and checkout: x393<br />
<br />
You may install numpy with<br />
sudo apt install python3-numpy<br />
<br />
If you did not notice missing numpy, then during bitbake you will get error "build No rule to make target 'drivers/elphel/x393.o', needed by 'drivers/elphel/built-in.a'. Stop." in that case you need to install numpy, re-run setup.py (make sure numpy error is gone) then re-create linux kernel links during next build by erasing old ones:<br />
bitbake linux-xlnx -c clean<br />
and re-running<br />
bitbake linux-xlnx device-tree core-image-elphel393<br />
<br />
When building php: configure: error: zip support requires ZLIB. Use --with-zlib-dir=<DIR> to specify prefix where ZLIB include and library are located<br />
sudo apt install zlib1g-dev<br />
<br />
==<font color="blue">Compare '''built''' vs '''deployed''' software versions</font>==<br />
<font size='2'><br />
cd elphel393<br />
./check_versions.py root@192.168.0.9<br />
</font><br />
<br />
{|<br />
|[[File:Check versions.png|thumb|400px|check_versions.py output in terminal (web-393 revision on PC is ahead of the one installed on the camera)]]<br />
|}<br />
<br />
==<font color="blue">Details for development</font>==<br />
[[Development_for_10393|'''Development for 10393''']]</div>Andrey.filippovhttps://wiki.elphel.com/index.php?title=Poky_manual&diff=13105Poky manual2022-01-26T22:12:53Z<p>Andrey.filippov: /* Setup */</p>
<hr />
<div>==<font color="blue">Description</font>==<br />
Build the firmware for Elphel 10393 series camera systems from scratch.<br />
<br />
Prebuilt releases can be found [https://community.elphel.com/files/393/ here].<br />
<br />
==<font color="blue">Use cases</font>==<br />
* Update Linux Kernel when developing a driver<br />
* Include application to the default firmware package<br />
* Update Elphel's PHP extension<br />
* C/C++ applications if developed on PC require a cross-compiler and require Yocto installation or some other alternative.<br />
<br />
Other projects written in Python, PHP, Javascript, HTML, C/C++ (gcc is installed on the system board) can be developed on the camera. Installing the framework is not required but it can simplify the development process.<br />
<br />
==<font color="blue">Description</font>==<br />
<br />
* Building embedded Linux image for Zynq ARMv7 platform - Elphel 10393 board<br />
* Yocto Poky revision = 2.7.1 (Warrior) - <font color="green">builds in Kubuntu 20.04.</font> <font color="red">Older OSes are not supported. Roll back to get built in 16.04.</font><br />
* <s>Yocto Poky revision = 2.4 (Rocko) - <font color="green">builds in Kubuntu 16.04.</font> <font color="red">Won't build in 18.04 or 20.04.</font></s><br />
* <s>Yocto Poky revision = 2.0 (Jethro)</s><br />
<br />
==<font color="blue">Features</font>==<br />
* Environment is set up with a single script<br />
* All Elphel projects are configured for Eclipse IDE:<br />
** fpga projects (verilog)<br />
** kernel<br />
** applications projects<br />
* All steps for fpga projects are run from Eclipse IDE<br />
** Read about [http://blog.elphel.com/2016/05/tutorial-02-eclipse-based-fpga-development-environment-for-elphel-cameras/ setting up Eclipse based FPGA development]<br />
** [https://git.elphel.com/Elphel/vdt-plugin VDT Plugin repository]<br />
<br />
* Once everything is built it supports updating software projects (files and binaries) on the target system<br />
** access is set up in yocto's ''local.conf'' (see ''setup.py'' output) + ''ssh-copy-id''<br />
** ''bitbake some-app -c target_scp'' from the command line or Eclipse IDE - see examples in '''elphel-apps-...''' at [https://git.elphel.com/Elphel Git]<br />
<br />
==<font color="blue">Requirements</font>==<br />
* Kubuntu 20.04 x64<br />
* <s>Kubuntu 18.04 x64 (as of Dec 2018) - Poky: 2.7.1 Warrior (not tested but might build w/o problems)</s><br />
* <s>Kubuntu 16.04 x64 (as of Dec 2018) - Poky: 2.4 Rocko, 2.7.1 Warrior</s><br />
<br />
==<font color="blue">Output files</font>==<br />
The names are listed as they appear in the u-boot configuration header file - actual output files have different names:<br />
{| class="wikitable"<br />
|-<br />
! File(s)<br />
! Build Command<br />
! Description<br />
|-<br />
| <font color='darkblue'>'''boot.bin'''</font><br />
| ''bitbake u-boot''<br />
| u-boot as the first stage bootloader = Secondary Program Loader (SPL) that boots '''u-boot-dtb.img'''<br />
|-<br />
| <font color='darkblue'>'''u-boot-dtb.img'''</font><br />
| ''bitbake u-boot''<br />
| full size u-boot with a stripped device tree (''cat u-boot.img some_stripped_devicetree.dtb > u-boot-dtb.img'')<br />
|-<br />
|valign='top'| <font color='darkblue'>'''devicetree.dtb'''</font><br />
| bitbake device-tree<br />
| device tree with listed interfaces, zynq registers, interrupts and drivers<br />
* ''elphel393/bootable-images/mmc/devicetree.dtb'' - mount rootfs from mmc partition<br />
* ''elphel393/bootable-images/nand/devicetree.dtb'' - mount rootfs from NAND flash<br />
|-<br />
| <font color='darkblue'>'''uImage'''</font><br />
| ''bitbake linux-xlnx''<br />
| kernel, drivers<br />
|-<br />
| <font color='darkblue'>'''rootfs.ubifs''', '''rootfs.ubi''', '''rootfs.tar.gz'''</font><br />
| ''bitbake core-image-elphel393''<br />
| rootfs in different formats - *.ubi* for NAND, *.tar.gz for mmc<br />
|}<br />
<br />
The file are located at '''elphel393/bootable-images/''', which is a link to poky's deploy directory '''elphel393/poky/build/tmp/deploy/images/elphel393/'''<br />
<br />
* complete set of files for rootfs in NAND Flash: ''elphel393/bootable-images/nand/''<br />
* complete set of files for rootfs on MMC (micro SD card): ''elphel393/bootable-images/mmc/''<br />
<br />
==<font color="blue">Write files to media and boot</font>==<br />
===Boot from micro SD card===<br />
* Use recovery or regular &mu;SD card<br />
* EXT4 partition mounted as '''/'''<br />
[[Sd_boot_rootfs|Detailed instructions]]<br />
<br />
===Boot from NAND flash===<br />
* The default boot option - power on.<br />
* A UBIFS image is written to /dev/mtd4 - is mounted as '''/'''<br />
[[NAND_flash_boot_rootfs|Detailed instructions]]<br />
<br />
===Notes===<br />
* [[Boot_options_393|'''Read more''']] about boot options.<br />
<br />
==<font color="blue">Setup</font>==<br />
<br />
* Poky 2.7.1 Warrior (Kubuntu 20.04)<br />
<font size='2'><br />
git clone -b '''warrior''' https://git.elphel.com/Elphel/elphel393.git<br />
cd elphel393<br />
./setup.py<br />
cd poky<br />
. ./oe-init-build-env<br />
bitbake u-boot device-tree linux-xlnx core-image-elphel393<br />
</font><br />
<br />
* <s>Poky 2.4 Rocko (Kubuntu 16.04)<br />
<font size='2'><br />
git clone -b '''rocko''' https://git.elphel.com/Elphel/elphel393.git<br />
cd elphel393<br />
./setup.py<br />
cd poky<br />
. ./oe-init-build-env<br />
bitbake u-boot device-tree linux-xlnx core-image-elphel393<br />
<!--''Temporary: linux-xlnx in Rocko depends on branch 'lwir' for x393. Change in projects.json line 42 from 'master' to 'lwir'.''--><br />
</font></s><br />
<br />
* Notes: When trying to run bitbake on a new install got problems with older bitbake version (current build uses specific snapshot) and python3.8. So I install old python2.7 and linked it:<br />
sudo apt install python2.7<br />
sudo ln -s python2.7 python2<br />
sudo ln -s python2.7 python<br />
<br />
After this bitbake just complained about missing tools (git, build-essential were already installed):<br />
<br />
sudo apt install chrpath diffstat gawk makeinfo<br />
<br />
Program test_mcntrl.py that builds x393.h header files from FPGA code that runs during ./setup.py requires numpy and results in error output if missing Still setup.py continues, you need to look through its output few lines after<br />
* x393<br />
git host: git.elphel.com<br />
Clone and checkout: x393<br />
<br />
You may install numpy with<br />
sudo apt install python3-numpy<br />
<br />
If you did not notice missing numpy, then during bitbake you will get error "build No rule to make target 'drivers/elphel/x393.o', needed by 'drivers/elphel/built-in.a'. Stop." in that case you need to install numpy, re-run setup.py (make sure numpy error is gone) then re-create linux kernel links during next build by erasing old ones:<br />
bitbake linux-xlnx -c clean<br />
and re-running<br />
bitbake linux-xlnx device-tree core-image-elphel393<br />
<br />
When building php: configure: error: zip support requires ZLIB. Use --with-zlib-dir=<DIR> to specify prefix where ZLIB include and library are located<br />
sudo apt install zlib1g-dev<br />
<br />
==<font color="blue">Compare '''built''' vs '''deployed''' software versions</font>==<br />
<font size='2'><br />
cd elphel393<br />
./check_versions.py root@192.168.0.9<br />
</font><br />
<br />
{|<br />
|[[File:Check versions.png|thumb|400px|check_versions.py output in terminal (web-393 revision on PC is ahead of the one installed on the camera)]]<br />
|}<br />
<br />
==<font color="blue">Details for development</font>==<br />
[[Development_for_10393|'''Development for 10393''']]</div>Andrey.filippovhttps://wiki.elphel.com/index.php?title=Poky_manual&diff=13104Poky manual2022-01-26T21:48:43Z<p>Andrey.filippov: /* Setup */</p>
<hr />
<div>==<font color="blue">Description</font>==<br />
Build the firmware for Elphel 10393 series camera systems from scratch.<br />
<br />
Prebuilt releases can be found [https://community.elphel.com/files/393/ here].<br />
<br />
==<font color="blue">Use cases</font>==<br />
* Update Linux Kernel when developing a driver<br />
* Include application to the default firmware package<br />
* Update Elphel's PHP extension<br />
* C/C++ applications if developed on PC require a cross-compiler and require Yocto installation or some other alternative.<br />
<br />
Other projects written in Python, PHP, Javascript, HTML, C/C++ (gcc is installed on the system board) can be developed on the camera. Installing the framework is not required but it can simplify the development process.<br />
<br />
==<font color="blue">Description</font>==<br />
<br />
* Building embedded Linux image for Zynq ARMv7 platform - Elphel 10393 board<br />
* Yocto Poky revision = 2.7.1 (Warrior) - <font color="green">builds in Kubuntu 20.04.</font> <font color="red">Older OSes are not supported. Roll back to get built in 16.04.</font><br />
* <s>Yocto Poky revision = 2.4 (Rocko) - <font color="green">builds in Kubuntu 16.04.</font> <font color="red">Won't build in 18.04 or 20.04.</font></s><br />
* <s>Yocto Poky revision = 2.0 (Jethro)</s><br />
<br />
==<font color="blue">Features</font>==<br />
* Environment is set up with a single script<br />
* All Elphel projects are configured for Eclipse IDE:<br />
** fpga projects (verilog)<br />
** kernel<br />
** applications projects<br />
* All steps for fpga projects are run from Eclipse IDE<br />
** Read about [http://blog.elphel.com/2016/05/tutorial-02-eclipse-based-fpga-development-environment-for-elphel-cameras/ setting up Eclipse based FPGA development]<br />
** [https://git.elphel.com/Elphel/vdt-plugin VDT Plugin repository]<br />
<br />
* Once everything is built it supports updating software projects (files and binaries) on the target system<br />
** access is set up in yocto's ''local.conf'' (see ''setup.py'' output) + ''ssh-copy-id''<br />
** ''bitbake some-app -c target_scp'' from the command line or Eclipse IDE - see examples in '''elphel-apps-...''' at [https://git.elphel.com/Elphel Git]<br />
<br />
==<font color="blue">Requirements</font>==<br />
* Kubuntu 20.04 x64<br />
* <s>Kubuntu 18.04 x64 (as of Dec 2018) - Poky: 2.7.1 Warrior (not tested but might build w/o problems)</s><br />
* <s>Kubuntu 16.04 x64 (as of Dec 2018) - Poky: 2.4 Rocko, 2.7.1 Warrior</s><br />
<br />
==<font color="blue">Output files</font>==<br />
The names are listed as they appear in the u-boot configuration header file - actual output files have different names:<br />
{| class="wikitable"<br />
|-<br />
! File(s)<br />
! Build Command<br />
! Description<br />
|-<br />
| <font color='darkblue'>'''boot.bin'''</font><br />
| ''bitbake u-boot''<br />
| u-boot as the first stage bootloader = Secondary Program Loader (SPL) that boots '''u-boot-dtb.img'''<br />
|-<br />
| <font color='darkblue'>'''u-boot-dtb.img'''</font><br />
| ''bitbake u-boot''<br />
| full size u-boot with a stripped device tree (''cat u-boot.img some_stripped_devicetree.dtb > u-boot-dtb.img'')<br />
|-<br />
|valign='top'| <font color='darkblue'>'''devicetree.dtb'''</font><br />
| bitbake device-tree<br />
| device tree with listed interfaces, zynq registers, interrupts and drivers<br />
* ''elphel393/bootable-images/mmc/devicetree.dtb'' - mount rootfs from mmc partition<br />
* ''elphel393/bootable-images/nand/devicetree.dtb'' - mount rootfs from NAND flash<br />
|-<br />
| <font color='darkblue'>'''uImage'''</font><br />
| ''bitbake linux-xlnx''<br />
| kernel, drivers<br />
|-<br />
| <font color='darkblue'>'''rootfs.ubifs''', '''rootfs.ubi''', '''rootfs.tar.gz'''</font><br />
| ''bitbake core-image-elphel393''<br />
| rootfs in different formats - *.ubi* for NAND, *.tar.gz for mmc<br />
|}<br />
<br />
The file are located at '''elphel393/bootable-images/''', which is a link to poky's deploy directory '''elphel393/poky/build/tmp/deploy/images/elphel393/'''<br />
<br />
* complete set of files for rootfs in NAND Flash: ''elphel393/bootable-images/nand/''<br />
* complete set of files for rootfs on MMC (micro SD card): ''elphel393/bootable-images/mmc/''<br />
<br />
==<font color="blue">Write files to media and boot</font>==<br />
===Boot from micro SD card===<br />
* Use recovery or regular &mu;SD card<br />
* EXT4 partition mounted as '''/'''<br />
[[Sd_boot_rootfs|Detailed instructions]]<br />
<br />
===Boot from NAND flash===<br />
* The default boot option - power on.<br />
* A UBIFS image is written to /dev/mtd4 - is mounted as '''/'''<br />
[[NAND_flash_boot_rootfs|Detailed instructions]]<br />
<br />
===Notes===<br />
* [[Boot_options_393|'''Read more''']] about boot options.<br />
<br />
==<font color="blue">Setup</font>==<br />
<br />
* Poky 2.7.1 Warrior (Kubuntu 20.04)<br />
<font size='2'><br />
git clone -b '''warrior''' https://git.elphel.com/Elphel/elphel393.git<br />
cd elphel393<br />
./setup.py<br />
cd poky<br />
. ./oe-init-build-env<br />
bitbake u-boot device-tree linux-xlnx core-image-elphel393<br />
</font><br />
<br />
* <s>Poky 2.4 Rocko (Kubuntu 16.04)<br />
<font size='2'><br />
git clone -b '''rocko''' https://git.elphel.com/Elphel/elphel393.git<br />
cd elphel393<br />
./setup.py<br />
cd poky<br />
. ./oe-init-build-env<br />
bitbake u-boot device-tree linux-xlnx core-image-elphel393<br />
<!--''Temporary: linux-xlnx in Rocko depends on branch 'lwir' for x393. Change in projects.json line 42 from 'master' to 'lwir'.''--><br />
</font></s><br />
<br />
* Notes: When trying to run bitbake on a new install got problems with older bitbake version (current build uses specific snapshot) and python3.8. So I install old python2.7 and linked it:<br />
sudo apt install python2.7<br />
sudo ln -s python2.7 python2<br />
sudo ln -s python2.7 python<br />
<br />
After this bitbake just complained about missing tools (git, build-essential were already installed):<br />
<br />
sudo apt install chrpath diffstat gawk makeinfo<br />
<br />
Program test_mcntrl.py that builds x393.h header files from FPGA code that runs during ./setup.py requires numpy and results in error output if missing Still setup.py continues, you need to look through its output few lines after<br />
* x393<br />
git host: git.elphel.com<br />
Clone and checkout: x393<br />
<br />
You may install numpy with<br />
sudo apt install python3-numpy<br />
<br />
If you did not notice missing numpy, then during bitbake you will get error "build No rule to make target 'drivers/elphel/x393.o', needed by 'drivers/elphel/built-in.a'. Stop." in that case you need to install numpy, re-run setup.py (make sure numpy error is gone) then re-create linux kernel links during next build by erasing old ones:<br />
bitbake linux-xlnx -c clean<br />
and re-running<br />
bitbake linux-xlnx device-tree core-image-elphel393<br />
<br />
==<font color="blue">Compare '''built''' vs '''deployed''' software versions</font>==<br />
<font size='2'><br />
cd elphel393<br />
./check_versions.py root@192.168.0.9<br />
</font><br />
<br />
{|<br />
|[[File:Check versions.png|thumb|400px|check_versions.py output in terminal (web-393 revision on PC is ahead of the one installed on the camera)]]<br />
|}<br />
<br />
==<font color="blue">Details for development</font>==<br />
[[Development_for_10393|'''Development for 10393''']]</div>Andrey.filippovhttps://wiki.elphel.com/index.php?title=Poky_manual&diff=13103Poky manual2022-01-26T21:32:55Z<p>Andrey.filippov: /* Setup */</p>
<hr />
<div>==<font color="blue">Description</font>==<br />
Build the firmware for Elphel 10393 series camera systems from scratch.<br />
<br />
Prebuilt releases can be found [https://community.elphel.com/files/393/ here].<br />
<br />
==<font color="blue">Use cases</font>==<br />
* Update Linux Kernel when developing a driver<br />
* Include application to the default firmware package<br />
* Update Elphel's PHP extension<br />
* C/C++ applications if developed on PC require a cross-compiler and require Yocto installation or some other alternative.<br />
<br />
Other projects written in Python, PHP, Javascript, HTML, C/C++ (gcc is installed on the system board) can be developed on the camera. Installing the framework is not required but it can simplify the development process.<br />
<br />
==<font color="blue">Description</font>==<br />
<br />
* Building embedded Linux image for Zynq ARMv7 platform - Elphel 10393 board<br />
* Yocto Poky revision = 2.7.1 (Warrior) - <font color="green">builds in Kubuntu 20.04.</font> <font color="red">Older OSes are not supported. Roll back to get built in 16.04.</font><br />
* <s>Yocto Poky revision = 2.4 (Rocko) - <font color="green">builds in Kubuntu 16.04.</font> <font color="red">Won't build in 18.04 or 20.04.</font></s><br />
* <s>Yocto Poky revision = 2.0 (Jethro)</s><br />
<br />
==<font color="blue">Features</font>==<br />
* Environment is set up with a single script<br />
* All Elphel projects are configured for Eclipse IDE:<br />
** fpga projects (verilog)<br />
** kernel<br />
** applications projects<br />
* All steps for fpga projects are run from Eclipse IDE<br />
** Read about [http://blog.elphel.com/2016/05/tutorial-02-eclipse-based-fpga-development-environment-for-elphel-cameras/ setting up Eclipse based FPGA development]<br />
** [https://git.elphel.com/Elphel/vdt-plugin VDT Plugin repository]<br />
<br />
* Once everything is built it supports updating software projects (files and binaries) on the target system<br />
** access is set up in yocto's ''local.conf'' (see ''setup.py'' output) + ''ssh-copy-id''<br />
** ''bitbake some-app -c target_scp'' from the command line or Eclipse IDE - see examples in '''elphel-apps-...''' at [https://git.elphel.com/Elphel Git]<br />
<br />
==<font color="blue">Requirements</font>==<br />
* Kubuntu 20.04 x64<br />
* <s>Kubuntu 18.04 x64 (as of Dec 2018) - Poky: 2.7.1 Warrior (not tested but might build w/o problems)</s><br />
* <s>Kubuntu 16.04 x64 (as of Dec 2018) - Poky: 2.4 Rocko, 2.7.1 Warrior</s><br />
<br />
==<font color="blue">Output files</font>==<br />
The names are listed as they appear in the u-boot configuration header file - actual output files have different names:<br />
{| class="wikitable"<br />
|-<br />
! File(s)<br />
! Build Command<br />
! Description<br />
|-<br />
| <font color='darkblue'>'''boot.bin'''</font><br />
| ''bitbake u-boot''<br />
| u-boot as the first stage bootloader = Secondary Program Loader (SPL) that boots '''u-boot-dtb.img'''<br />
|-<br />
| <font color='darkblue'>'''u-boot-dtb.img'''</font><br />
| ''bitbake u-boot''<br />
| full size u-boot with a stripped device tree (''cat u-boot.img some_stripped_devicetree.dtb > u-boot-dtb.img'')<br />
|-<br />
|valign='top'| <font color='darkblue'>'''devicetree.dtb'''</font><br />
| bitbake device-tree<br />
| device tree with listed interfaces, zynq registers, interrupts and drivers<br />
* ''elphel393/bootable-images/mmc/devicetree.dtb'' - mount rootfs from mmc partition<br />
* ''elphel393/bootable-images/nand/devicetree.dtb'' - mount rootfs from NAND flash<br />
|-<br />
| <font color='darkblue'>'''uImage'''</font><br />
| ''bitbake linux-xlnx''<br />
| kernel, drivers<br />
|-<br />
| <font color='darkblue'>'''rootfs.ubifs''', '''rootfs.ubi''', '''rootfs.tar.gz'''</font><br />
| ''bitbake core-image-elphel393''<br />
| rootfs in different formats - *.ubi* for NAND, *.tar.gz for mmc<br />
|}<br />
<br />
The file are located at '''elphel393/bootable-images/''', which is a link to poky's deploy directory '''elphel393/poky/build/tmp/deploy/images/elphel393/'''<br />
<br />
* complete set of files for rootfs in NAND Flash: ''elphel393/bootable-images/nand/''<br />
* complete set of files for rootfs on MMC (micro SD card): ''elphel393/bootable-images/mmc/''<br />
<br />
==<font color="blue">Write files to media and boot</font>==<br />
===Boot from micro SD card===<br />
* Use recovery or regular &mu;SD card<br />
* EXT4 partition mounted as '''/'''<br />
[[Sd_boot_rootfs|Detailed instructions]]<br />
<br />
===Boot from NAND flash===<br />
* The default boot option - power on.<br />
* A UBIFS image is written to /dev/mtd4 - is mounted as '''/'''<br />
[[NAND_flash_boot_rootfs|Detailed instructions]]<br />
<br />
===Notes===<br />
* [[Boot_options_393|'''Read more''']] about boot options.<br />
<br />
==<font color="blue">Setup</font>==<br />
<br />
* Poky 2.7.1 Warrior (Kubuntu 20.04)<br />
<font size='2'><br />
git clone -b '''warrior''' https://git.elphel.com/Elphel/elphel393.git<br />
cd elphel393<br />
./setup.py<br />
cd poky<br />
. ./oe-init-build-env<br />
bitbake u-boot device-tree linux-xlnx core-image-elphel393<br />
</font><br />
<br />
* <s>Poky 2.4 Rocko (Kubuntu 16.04)<br />
<font size='2'><br />
git clone -b '''rocko''' https://git.elphel.com/Elphel/elphel393.git<br />
cd elphel393<br />
./setup.py<br />
cd poky<br />
. ./oe-init-build-env<br />
bitbake u-boot device-tree linux-xlnx core-image-elphel393<br />
<!--''Temporary: linux-xlnx in Rocko depends on branch 'lwir' for x393. Change in projects.json line 42 from 'master' to 'lwir'.''--><br />
</font></s><br />
<br />
* Notes: When trying to run bitbake on a new install got problems with older bitbake version (current build uses specific snapshot) and python3.8. So I install old python2.7 and linked it:<br />
sudo apt install python2.7<br />
sudo ln -s python2.7 python2<br />
sudo ln -s python2.7 python<br />
<br />
After this bitbake just complained about missing tools (git, build-essential were already installed):<br />
<br />
sudo apt install chrpath diffstat gawk makeinfo<br />
<br />
Program test_mcntrl.py that builds x393.h header files from FPGA code that runs during ./setup.py requires numpy and results in error output if missing Still setup.py continues, you need to look through its output few lines after<br />
* x393<br />
git host: git.elphel.com<br />
Clone and checkout: x393<br />
<br />
You may install numpy with<br />
sudo apt install python3-numpy<br />
<br />
==<font color="blue">Compare '''built''' vs '''deployed''' software versions</font>==<br />
<font size='2'><br />
cd elphel393<br />
./check_versions.py root@192.168.0.9<br />
</font><br />
<br />
{|<br />
|[[File:Check versions.png|thumb|400px|check_versions.py output in terminal (web-393 revision on PC is ahead of the one installed on the camera)]]<br />
|}<br />
<br />
==<font color="blue">Details for development</font>==<br />
[[Development_for_10393|'''Development for 10393''']]</div>Andrey.filippovhttps://wiki.elphel.com/index.php?title=Poky_manual&diff=13102Poky manual2022-01-26T20:19:27Z<p>Andrey.filippov: /* Setup */</p>
<hr />
<div>==<font color="blue">Description</font>==<br />
Build the firmware for Elphel 10393 series camera systems from scratch.<br />
<br />
Prebuilt releases can be found [https://community.elphel.com/files/393/ here].<br />
<br />
==<font color="blue">Use cases</font>==<br />
* Update Linux Kernel when developing a driver<br />
* Include application to the default firmware package<br />
* Update Elphel's PHP extension<br />
* C/C++ applications if developed on PC require a cross-compiler and require Yocto installation or some other alternative.<br />
<br />
Other projects written in Python, PHP, Javascript, HTML, C/C++ (gcc is installed on the system board) can be developed on the camera. Installing the framework is not required but it can simplify the development process.<br />
<br />
==<font color="blue">Description</font>==<br />
<br />
* Building embedded Linux image for Zynq ARMv7 platform - Elphel 10393 board<br />
* Yocto Poky revision = 2.7.1 (Warrior) - <font color="green">builds in Kubuntu 20.04.</font> <font color="red">Older OSes are not supported. Roll back to get built in 16.04.</font><br />
* <s>Yocto Poky revision = 2.4 (Rocko) - <font color="green">builds in Kubuntu 16.04.</font> <font color="red">Won't build in 18.04 or 20.04.</font></s><br />
* <s>Yocto Poky revision = 2.0 (Jethro)</s><br />
<br />
==<font color="blue">Features</font>==<br />
* Environment is set up with a single script<br />
* All Elphel projects are configured for Eclipse IDE:<br />
** fpga projects (verilog)<br />
** kernel<br />
** applications projects<br />
* All steps for fpga projects are run from Eclipse IDE<br />
** Read about [http://blog.elphel.com/2016/05/tutorial-02-eclipse-based-fpga-development-environment-for-elphel-cameras/ setting up Eclipse based FPGA development]<br />
** [https://git.elphel.com/Elphel/vdt-plugin VDT Plugin repository]<br />
<br />
* Once everything is built it supports updating software projects (files and binaries) on the target system<br />
** access is set up in yocto's ''local.conf'' (see ''setup.py'' output) + ''ssh-copy-id''<br />
** ''bitbake some-app -c target_scp'' from the command line or Eclipse IDE - see examples in '''elphel-apps-...''' at [https://git.elphel.com/Elphel Git]<br />
<br />
==<font color="blue">Requirements</font>==<br />
* Kubuntu 20.04 x64<br />
* <s>Kubuntu 18.04 x64 (as of Dec 2018) - Poky: 2.7.1 Warrior (not tested but might build w/o problems)</s><br />
* <s>Kubuntu 16.04 x64 (as of Dec 2018) - Poky: 2.4 Rocko, 2.7.1 Warrior</s><br />
<br />
==<font color="blue">Output files</font>==<br />
The names are listed as they appear in the u-boot configuration header file - actual output files have different names:<br />
{| class="wikitable"<br />
|-<br />
! File(s)<br />
! Build Command<br />
! Description<br />
|-<br />
| <font color='darkblue'>'''boot.bin'''</font><br />
| ''bitbake u-boot''<br />
| u-boot as the first stage bootloader = Secondary Program Loader (SPL) that boots '''u-boot-dtb.img'''<br />
|-<br />
| <font color='darkblue'>'''u-boot-dtb.img'''</font><br />
| ''bitbake u-boot''<br />
| full size u-boot with a stripped device tree (''cat u-boot.img some_stripped_devicetree.dtb > u-boot-dtb.img'')<br />
|-<br />
|valign='top'| <font color='darkblue'>'''devicetree.dtb'''</font><br />
| bitbake device-tree<br />
| device tree with listed interfaces, zynq registers, interrupts and drivers<br />
* ''elphel393/bootable-images/mmc/devicetree.dtb'' - mount rootfs from mmc partition<br />
* ''elphel393/bootable-images/nand/devicetree.dtb'' - mount rootfs from NAND flash<br />
|-<br />
| <font color='darkblue'>'''uImage'''</font><br />
| ''bitbake linux-xlnx''<br />
| kernel, drivers<br />
|-<br />
| <font color='darkblue'>'''rootfs.ubifs''', '''rootfs.ubi''', '''rootfs.tar.gz'''</font><br />
| ''bitbake core-image-elphel393''<br />
| rootfs in different formats - *.ubi* for NAND, *.tar.gz for mmc<br />
|}<br />
<br />
The file are located at '''elphel393/bootable-images/''', which is a link to poky's deploy directory '''elphel393/poky/build/tmp/deploy/images/elphel393/'''<br />
<br />
* complete set of files for rootfs in NAND Flash: ''elphel393/bootable-images/nand/''<br />
* complete set of files for rootfs on MMC (micro SD card): ''elphel393/bootable-images/mmc/''<br />
<br />
==<font color="blue">Write files to media and boot</font>==<br />
===Boot from micro SD card===<br />
* Use recovery or regular &mu;SD card<br />
* EXT4 partition mounted as '''/'''<br />
[[Sd_boot_rootfs|Detailed instructions]]<br />
<br />
===Boot from NAND flash===<br />
* The default boot option - power on.<br />
* A UBIFS image is written to /dev/mtd4 - is mounted as '''/'''<br />
[[NAND_flash_boot_rootfs|Detailed instructions]]<br />
<br />
===Notes===<br />
* [[Boot_options_393|'''Read more''']] about boot options.<br />
<br />
==<font color="blue">Setup</font>==<br />
<br />
* Poky 2.7.1 Warrior (Kubuntu 20.04)<br />
<font size='2'><br />
git clone -b '''warrior''' https://git.elphel.com/Elphel/elphel393.git<br />
cd elphel393<br />
./setup.py<br />
cd poky<br />
. ./oe-init-build-env<br />
bitbake u-boot device-tree linux-xlnx core-image-elphel393<br />
</font><br />
<br />
* <s>Poky 2.4 Rocko (Kubuntu 16.04)<br />
<font size='2'><br />
git clone -b '''rocko''' https://git.elphel.com/Elphel/elphel393.git<br />
cd elphel393<br />
./setup.py<br />
cd poky<br />
. ./oe-init-build-env<br />
bitbake u-boot device-tree linux-xlnx core-image-elphel393<br />
<!--''Temporary: linux-xlnx in Rocko depends on branch 'lwir' for x393. Change in projects.json line 42 from 'master' to 'lwir'.''--><br />
</font></s><br />
<br />
* Notes: When trying to run bitbake on a new install got problems with older bitbake version (current build uses specific snapshot) and python3.8. So I install old python2.7 and linked it:<br />
sudo apt install python2.7<br />
sudo ln -s python2.7 python2<br />
sudo ln -s python2.7 python<br />
<br />
After this bitbake just complained about missing tools (git, build-essential were already installed):<br />
<br />
sudo apt install chrpath diffstat gawk makeinfo<br />
<br />
==<font color="blue">Compare '''built''' vs '''deployed''' software versions</font>==<br />
<font size='2'><br />
cd elphel393<br />
./check_versions.py root@192.168.0.9<br />
</font><br />
<br />
{|<br />
|[[File:Check versions.png|thumb|400px|check_versions.py output in terminal (web-393 revision on PC is ahead of the one installed on the camera)]]<br />
|}<br />
<br />
==<font color="blue">Details for development</font>==<br />
[[Development_for_10393|'''Development for 10393''']]</div>Andrey.filippovhttps://wiki.elphel.com/index.php?title=Elphel_camera_assemblies&diff=12884Elphel camera assemblies2021-08-30T23:15:32Z<p>Andrey.filippov: </p>
<hr />
<div>[[Elphel_camera_parts_0393]]<br />
<br />
[[Elphel_camera_parts | Elphel_camera_parts_0353]]<br />
<br />
[https://blog.elphel.com/2015/12/x3d-assemblies-from-any-cad/ Blog post about the software used to create these models]<br />
==Camera assemblies ==<br />
=== LWIR16 prototype ===<br />
{{Cad4c_assembly|lwir16-37-flat}}<br />
----<br />
<br />
=== MNC393-XCAM camera ===<br />
{{Cad4c_assembly|MNC393-XCAM}}<br />
----<br />
<br />
=== EYESIS4PI-26-393 camera ===<br />
{{Cad4c_assembly|EYESIS4PI-26-393}}<br />
----<br />
<br />
=== NC393-M2242-CS camera ===<br />
{{Cad4c_assembly|NC393-M2242-CS}}<br />
----<br />
=== NC393-M2260-CS camera ===<br />
{{Cad4c_assembly|NC393-M2260-CS}}<br />
----<br />
=== NC393-M2260-F-CS camera ===<br />
{{Cad4c_assembly|NC393-M2260-F-CS}}<br />
----<br />
<br />
=== NC393-M2260-F-CS-IMU camera ===<br />
{{Cad4c_assembly|NC393-M2260-F-CS-IMU}}<br />
----<br />
=== NC393-M2260-F-CS-IMU-GPS camera ===<br />
{{Cad4c_assembly|NC393-M2260-F-CS-IMU-GPS}}<br />
----<br />
<br />
=== MC393F21 camera ===<br />
{{Cad4c_assembly|MC393F21}}<br />
----<br />
=== NC393-4PI4 camera ===<br />
{{Cad4c_assembly|NC393-4PI4}}<br />
----<br />
=== NC393-4PI4-IMU-GPS camera with IMU and GPS modules ===<br />
{{Cad4c_assembly|NC393-4PI4-IMU-GPS}}<br />
----<br />
<br />
=== EYESIS4PI-26 camera ===<br />
{{Cad4c_assembly|EYESIS4PI-26}}<br />
----<br />
=== NC353L camera ===<br />
{{Cad4c_assembly|NC353L}}<br />
----<br />
=== NC353L-369 camera ===<br />
{{Cad4c_assembly|NC353L-369}}<br />
----<br />
=== MNC354-2-STEREO camera ===<br />
{{Cad4c_assembly|MNC354-2-STEREO}}<br />
----<br />
=== NC353L-PHG camera ===<br />
{{Cad4c_assembly|NC353L-PHG}}<br />
----<br />
=== NC353L-PHG3 camera ===<br />
{{Cad4c_assembly|NC353L-PHG3}}<br />
----<br />
=== MNC354-2B camera ===<br />
{{Cad4c_assembly|MNC354-2B}}<br />
----</div>Andrey.filippovhttps://wiki.elphel.com/index.php?title=Elphel_camera_assemblies&diff=12883Elphel camera assemblies2021-08-30T22:58:15Z<p>Andrey.filippov: /* LWIR16 prototype */</p>
<hr />
<div>[[Elphel_camera_parts_0393]]<br />
<br />
[[Elphel_camera_parts | Elphel_camera_parts_0353]]<br />
<br />
[https://blog.elphel.com/2015/12/x3d-assemblies-from-any-cad/ Blog post about the software used to create these models]<br />
==Camera assemblies ==<br />
=== MNC393-XCAM camera ===<br />
{{Cad4c_assembly|MNC393-XCAM}}<br />
----<br />
<br />
=== EYESIS4PI-26-393 camera ===<br />
{{Cad4c_assembly|EYESIS4PI-26-393}}<br />
----<br />
<br />
=== NC393-M2242-CS camera ===<br />
{{Cad4c_assembly|NC393-M2242-CS}}<br />
----<br />
=== NC393-M2260-CS camera ===<br />
{{Cad4c_assembly|NC393-M2260-CS}}<br />
----<br />
=== NC393-M2260-F-CS camera ===<br />
{{Cad4c_assembly|NC393-M2260-F-CS}}<br />
----<br />
<br />
=== NC393-M2260-F-CS-IMU camera ===<br />
{{Cad4c_assembly|NC393-M2260-F-CS-IMU}}<br />
----<br />
=== NC393-M2260-F-CS-IMU-GPS camera ===<br />
{{Cad4c_assembly|NC393-M2260-F-CS-IMU-GPS}}<br />
----<br />
<br />
=== MC393F21 camera ===<br />
{{Cad4c_assembly|MC393F21}}<br />
----<br />
=== NC393-4PI4 camera ===<br />
{{Cad4c_assembly|NC393-4PI4}}<br />
----<br />
=== NC393-4PI4-IMU-GPS camera with IMU and GPS modules ===<br />
{{Cad4c_assembly|NC393-4PI4-IMU-GPS}}<br />
----<br />
<br />
=== EYESIS4PI-26 camera ===<br />
{{Cad4c_assembly|EYESIS4PI-26}}<br />
----<br />
=== NC353L camera ===<br />
{{Cad4c_assembly|NC353L}}<br />
----<br />
=== NC353L-369 camera ===<br />
{{Cad4c_assembly|NC353L-369}}<br />
----<br />
=== MNC354-2-STEREO camera ===<br />
{{Cad4c_assembly|MNC354-2-STEREO}}<br />
----<br />
=== NC353L-PHG camera ===<br />
{{Cad4c_assembly|NC353L-PHG}}<br />
----<br />
=== NC353L-PHG3 camera ===<br />
{{Cad4c_assembly|NC353L-PHG3}}<br />
----<br />
=== MNC354-2B camera ===<br />
{{Cad4c_assembly|MNC354-2B}}<br />
----<br />
=== LWIR16 prototype ===<br />
{{Cad4c_assembly|lwir16-37-flat}}</div>Andrey.filippovhttps://wiki.elphel.com/index.php?title=Elphel_camera_assemblies&diff=12882Elphel camera assemblies2021-08-30T22:50:54Z<p>Andrey.filippov: </p>
<hr />
<div>[[Elphel_camera_parts_0393]]<br />
<br />
[[Elphel_camera_parts | Elphel_camera_parts_0353]]<br />
<br />
[https://blog.elphel.com/2015/12/x3d-assemblies-from-any-cad/ Blog post about the software used to create these models]<br />
==Camera assemblies ==<br />
=== MNC393-XCAM camera ===<br />
{{Cad4c_assembly|MNC393-XCAM}}<br />
----<br />
<br />
=== EYESIS4PI-26-393 camera ===<br />
{{Cad4c_assembly|EYESIS4PI-26-393}}<br />
----<br />
<br />
=== NC393-M2242-CS camera ===<br />
{{Cad4c_assembly|NC393-M2242-CS}}<br />
----<br />
=== NC393-M2260-CS camera ===<br />
{{Cad4c_assembly|NC393-M2260-CS}}<br />
----<br />
=== NC393-M2260-F-CS camera ===<br />
{{Cad4c_assembly|NC393-M2260-F-CS}}<br />
----<br />
<br />
=== NC393-M2260-F-CS-IMU camera ===<br />
{{Cad4c_assembly|NC393-M2260-F-CS-IMU}}<br />
----<br />
=== NC393-M2260-F-CS-IMU-GPS camera ===<br />
{{Cad4c_assembly|NC393-M2260-F-CS-IMU-GPS}}<br />
----<br />
<br />
=== MC393F21 camera ===<br />
{{Cad4c_assembly|MC393F21}}<br />
----<br />
=== NC393-4PI4 camera ===<br />
{{Cad4c_assembly|NC393-4PI4}}<br />
----<br />
=== NC393-4PI4-IMU-GPS camera with IMU and GPS modules ===<br />
{{Cad4c_assembly|NC393-4PI4-IMU-GPS}}<br />
----<br />
<br />
=== EYESIS4PI-26 camera ===<br />
{{Cad4c_assembly|EYESIS4PI-26}}<br />
----<br />
=== NC353L camera ===<br />
{{Cad4c_assembly|NC353L}}<br />
----<br />
=== NC353L-369 camera ===<br />
{{Cad4c_assembly|NC353L-369}}<br />
----<br />
=== MNC354-2-STEREO camera ===<br />
{{Cad4c_assembly|MNC354-2-STEREO}}<br />
----<br />
=== NC353L-PHG camera ===<br />
{{Cad4c_assembly|NC353L-PHG}}<br />
----<br />
=== NC353L-PHG3 camera ===<br />
{{Cad4c_assembly|NC353L-PHG3}}<br />
----<br />
=== MNC354-2B camera ===<br />
{{Cad4c_assembly|MNC354-2B}}<br />
----<br />
=== LWIR16 prototype ===<br />
{{Cad4c_assembly|LWIR16}}</div>Andrey.filippovhttps://wiki.elphel.com/index.php?title=Camogm&diff=3258Camogm2021-07-11T21:39:58Z<p>Andrey.filippov: /* Starting camogm */</p>
<hr />
<div>== Description ==<br />
This program allows recording of the video/images acquired by Elphel 353/363 series cameras to the storage media. It is developed to use such media as hard disk drives, compact flash cards or USB storage devices (with reduced data rate as ETRAX FS processor currently supports only USB 1.1, not the fast USB 2). But it might work over the NFS and be useful even for the basic model 353 cameras that do not have any additional storage devices attached.<br />
<br />
camogm is designed to run in the background and accept commands through a named pipe. It writes JPEG-encoded frames from the camera [[Circbuf|circbuf]]-circular video buffer in any of the 3 formats:<br />
*'''ogm''' - MJPEG video in Xiph Ogg container<br />
*'''jpeg''' - series of the individual JPEG files (1 file per frame)<br />
*'''mov''' - MJPEG video in Apple QuickTime(R) container<br />
As of today the last one (mov) is probably the fastest one in the camera as it uses the minimum of computational resources. Ogg is optimized for streaming and requires additional memory copying and checksum calculation for all of the recorded data, individual JPEG files grow large directories that can use system resources, while recording mov format simply merges FPGA-encoded frames (with JPEG and optional Exif headers added by the software) and the file header (with frame index) is calculated only once per file.<br />
<br />
This program makes use of the [[Circbuf|circbuf]] that can hold several seconds of even high resolution/high frame rate video, so switching from file to file and/or waiting for the search operations on the HDD will not cause the frame loss - that can be verified if the Exif headers are enabled - regardless of the format selected each frame will have the exact timestamp (with 1 microsecond resolution).<br />
<br />
== Usage ==<br />
=== Starting camogm ===<br />
<br />
Eventually camogm will be started (and restarted if needed) automatically at boot time, now it is started manually with the command<br />
<br />
camogm <named_pipe_name><br />
<br />
Where <named_pipe_name> is the filename that will be used to pass commands to the camogm. A good choice is "/var/state/camogm_cmd" and it is used in a [http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/apps/camogm/camogmstate.php?view=markup camogmstate.php] - a demo PHP script that can read the current status of the camogm recorder. Running camogm without any parameters or with "--help" will just output the short version of this page. So this is the example of the command that starts camogm as a background process from the shell prompt (i.e. telnet or [[Phpshell]]):<br />
<br />
camogm /var/state/camogm_cmd &<br />
camogm -n /var/state/camogm_cmd -p 1234 -s /mnt/sda1/test4<br />
<br />
=== Sending Commands to camogm ===<br />
<br />
When the camogm is running you may verify that with the command:<br />
ps | grep "camogm"<br />
It is waiting for the commands to be sent to the pipe (/var/state/camogm_cmd above) as text strings. Commands are separated with the new lines ("\n") and/or semicolons (";"), command names are separated from the optional parameters by spaces " " and/or equal signs "=". The following is an example of such command sent from the shell prompt using command "echo" and output redirection ">" to th camogm command pipe<br />
<br />
echo "status; exif 1; format=jpeg;status=/var/tmp/camogm.status" > /var/state/camogm_cmd<br />
<br />
That command will:<br />
# print current status information sending it to the standard output (may not be visible if the program was not started from the same session),<br />
# set exif mode ON (each frame will have the full Exif header including a precise time stamp),<br />
# set output format to a series of individual JPEG files, and then<br />
# send status information to a file /var/tmp/camogm.status in the camera file system. <br />
The [http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/apps/camogm/camogmstate.php?view=markup camogmstate.php] script shows how to use a named pipe for the status information so the caller will wait until camogm returns that status info (the "echo" command by itself will not wait for the status, there can (and will) be a delay between finishing of echo (or equivalent) and the appearance of the status info in the output file. ''With the current state of the software that status info may never come if the camera frame capture process is stopped while camogm was recording video as it checks for the new commands once per frame if it is in the "running" state (in "stopped" state in checks for the incoming commands twice a second)''<br />
<br />
== camogm Commands ==<br />
===start===<br />
No parameters - just start recording video/images. At least two frames in the buffer are needed to start recording (they will not be lost) - the time stamp difference is used to calculate the frame rate. In the case there are not enough frames in the buffer (i.e. video acquisition is not started) the state of the camogm (reported by ''status'' and ''xstatus'') will be "starting" before it will become "running". The video will be recorded to the same file (may be a directory for .jpeg format) until explicitly stopped, or until the specified file size/duration/number of frames is exceeded or some critical parameters (like frame dimensions) are changed. In those cases (not explicitly stopped) camogm will restart recording into a new file (filenames are composed from the specified prefix and the timestamp) so that no frames will be lost (if it is not overwhelmed by the incoming frame rate) and the first frame of a new file segment will be the next one acquired after the last one in the previous file.<br />
===stop===<br />
Just stop the recording. If the video acquisition is on and camogm is started again before the [[Circbuf|circbuf]] is overrun, there will be no gaps in the recording. But if the pause will be too long some frames will be lost and there will be a gap between the next file and the previous one.<br />
<br />
===exit===<br />
Terminate camogm program (it will execute implied "stop" command first to finish recording if any).<br />
===duration===<br />
duration=<time_in_seconds><br />
Specify the maximal duration of each individual file segment. The new file will be started if this time limit will be exceeded. The default duration is 60 seconds, current value is reported by status/xstatus commands.<br />
===length===<br />
length=<file_size_in_bytes><br />
Specify the maximal size of each individual file segment in bytes. The new file will be started if this limit will be exceeded. The limit is 2.147.483.647 bytes (~2 GB), current value is reported by status/xstatus commands.<br />
<br />
===max_frames===<br />
max_frames=<number_of_frames><br />
Specify the maximal number of frames of each individual file segment. The new file will be started if this limit is exceeded. The default value is 16384.<br />
<br />
===frames_per_chunk===<br />
frames_per_chunk=<number_of_frames_per_chunk> (default 10)<br />
Sets the number of chunk entries in the *.mov header (10 means there's 1 chunk entry with an absolute offset in the header for each 10 frames).<br />
<br />
===start_after_timestamp===<br />
start_after_timestamp=SS.UU # double (0123456789.012345)<br />
Delays recording start until a specific time-stamp has been reached.<br />
This command alone does not start a recording you need to run the "start" command as well after setting start_after_timestamp.<br />
<br />
===prefix===<br />
prefix=<file_name_prefix><br />
prefix value is used by the camogm to generate file names/paths to store video content. Full paths will be generated from the specified prefix, timestamps of the first frame in the segment and appropriate extension (".ogm",".jpeg" or ".mov"). The prefix consists of directory path (everything before the last slash "/") and the file name prefix (what remains after the last "/"). In the case of video formats (".ogm",".mov") the directory prefix should point to an existent directory on the mounted writeable media - camogm will not try to create missing directories and will just fail to start recording. In the case of individual JPEG files camogm will try to create the last level in directory structure if it does not exist and place all the frame files there.<br />
<br />
===exif===<br />
Controls generation and output of [[Exif]] headers for each JPEG-encoded frame. These headers slightly (for the large frames) increase the file sizes and add a little of computation to the CPU, but they are very useful for later processing as they provide precise timing information that does not depend on particular file format and timing calculations that involve frame rate and frame numbers.<br />
exif=0<br />
turns it off, while<br />
exif=1<br />
turns it on. Current default value is off, but that may change in the future so it is better to specify the desired value.<br />
===timescale===<br />
Currently only works for "mov" format (will add to "ogm" later). Values >1.0 make the video play back slower than recorded ('slow motion'), the values less than 1.0 make the playback faster (time lapse video).<br />
===frameskip===<br />
frameskip=<number_of_frames_to_skip><br />
Skip specified number of frames after each frame stored (default 0 - no skip)<br />
===timelapse===<br />
timelapse=<number_seconds_between_frames><br />
Alternative way to reduce frame rate of the recorded images - specify required image period (integer value, in seconds). All intermediate images will be skipped, only first after each multiple of the specified interval will be stored. That means, that the time interval between subsequent images maybe slightly different, but the rounding error will not accumulate during long recordings.<br />
<br />
''timelapse'' and ''frameskip'' are mutually exclusive (they even use the same variable with positive values for frame skip (in frames) and negative - timelapse (in seconds).<br />
===format===<br />
format=[ogm|jpeg|mov]<br />
*ogm - record video as Ogg Media Stream<br />
*jpeg - record video as a series of JPEG files<br />
*mov - record video as Apple Quicktime (R) files<br />
===reset===<br />
Mostly a debug feature. Force camogm to start next file from the two most recent images in the circbuf, discarding all the older ones. It is the same action camogm does when the buffer is overrun and frames are lost.<br />
<br />
===debug===<br />
debug<br />
debug=<file><br />
The first command form (with to file specified) turns the debug output off, the second - directs it somewhere. camogm recognizes several special names like "stdout" and "stderr", it also treats file name "none", "null" and "/dev/null" as empty and turns the debug feature off.<br />
===debuglev===<br />
debuglev=<integer_value><br />
Allows to specify debug verbosity level, the higher the level the more information is output (it may slow down camogm and cause it to drop frames even if it could handle it with no/low debug output).<br />
===save_gp===<br />
save_gp=[0|1]<br />
As a debug feature camogm can set the camera global circbuf read pointer to the current value of camogm's read pointer. In that case it is possible to watch the camogm progress by other programs, such as [[Imgsrv|imgsrv]]<br />
===status===<br />
status<br />
status=<status_output_file><br />
This command provides the current camogm state information and sends it to standard output (maybe invisible if camogm was started from different shell session or by other means) or to the specified output file in plain text format. The same information is available in XML format - see xstatus command below. The following is a commented sample output generated by the status command:<br />
<br />
state running // may be '''stopped''', '''running''' and '''starting'''. Usually the last<br />
// one can be only visible if there are no images coming to the buffer.<br />
file /tmp/z/qvid1195433980_662716.mov // full path toi the current file being recorded<br />
frame 293 // current frame number (starts from 0)<br />
file duration 14.616060 sec // current duration of the video in this file segment<br />
file length 13167561 B // current video file size<br />
frame period 50055 (0xc387) // frame period in microseconds (this one is approximately 1/20 sec)<br />
frames to skip 100 (left 37) // number of frames to skip after the frame is acquired. Shown only if frame skip mode is enabled.<br />
timelapse period 10 sec (remaining 10 sec) // frame period for time lapse mode (time till next frame will be stored). Shown only if time lapse mode enabled<br />
width 1024 (0x400) // frame width in pixels<br />
height 768 (0x300) // frame height in pixels<br />
// - blank line<br />
output format mov // output file format - one of "ogm", "jpeg" and "mov"<br />
using exif yes // frames are generated with Exif headers that include time stamps<br />
path prefix: /tmp/z/qvid // file prefix as specified in '''prefix''' command<br />
max file duration: 60 sec // maximal file duration as specified in '''duration''' command<br />
max file length: 100000000 B // maximal file length as specified in '''length''' command<br />
max frames 16384 // maximal number of frames as specified in ... none yet, uses default<br />
timescale 1.000000 // time scale as specified in '''timescale''' command<br />
frames per chunk 10 // "frames per chunk" used in "mov" format<br />
// - blank line<br />
buffer overruns 0 // number of buffer overruns while recording since last status/xstatus<br />
// (these commands zero the buffer overruns counter). If no overruns <br />
// are reported, no frames are lost, including between file segments.<br />
buffer minimal 19748288 // Minimal level of the buffer memory since last status/xstatus command.<br />
buffer free 19748192 // Current amount of free memory in the video buffer (actual value might<br />
// be one frame less as the FPGA write pointer is reported only after<br />
// the whole frame is stored<br />
buffer used 43680 // Amount of memory currently used in the video buffer.<br />
circbuf_rp 10933536 (0xa6d520) // Current location of the read pointer in the video buffer<br />
// - blank line<br />
debug output to stderr // where the debug messages are sent to (as specified in '''debug''' command)<br />
debug level 1 // Debug verbosity level, the higher - the more "noisier". Set in<br />
// '''debuglev''' command.<br />
use global pointer no // see '''save_gp''' command.<br />
<br />
"-1" values that status/xstatus commands may return for some parameters mean "undefined", they are calculated only during video recording.<br />
<br />
===xstatus===<br />
status<br />
status=<status_output_file><br />
Same information as described for '''status''' command above, but presented in XML format more suitable to be processed by other software while '''status''' is easier to read by humans. See [http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/apps/camogm/camogmstate.php?view=markup camogmstate.php] PHP script that returns this XML data to the HTTP GET requests.<br />
<br />
<?xml version="1.0"?><br />
<camogm_state><br />
<state>"running"</state><br />
<file_name>"/tmp/z/qvid1195440137_027276.mov"</file_name><br />
<frame_number>281</frame_number><br />
<file_duration>14.015400</file_duration><br />
<file_length>12731197</file_length><br />
<frame_period>50055</frame_period><br />
<frames_skip>0</frames_skip><br />
<seconds_skip>10</seconds_skip><br />
<frames_skip_left>0</frames_skip_left><br />
<seconds_skip_left>7</seconds_skip_left><br />
<frame_width>1024</frame_width><br />
<frame_height>768</frame_height><br />
<format>"mov"</format><br />
<exif>"yes"</exif><br />
<prefix>"/tmp/z/qvid"</prefix><br />
<max_duration>60</max_duration><br />
<max_length>100000000</max_length><br />
<max_frames>16384</max_frames><br />
<timescale>1.000000</timescale><br />
<frames_per_chunk>10</frames_per_chunk><br />
<buffer_overruns>0</buffer_overruns><br />
<buffer_minimal>19747712</buffer_minimal><br />
<buffer_free>19747808</buffer_free><br />
<buffer_used>44064</buffer_used><br />
<circbuf_rp>16275392</circbuf_rp><br />
<debug_output>"stderr"</debug_output><br />
<debug_level>1</debug_level><br />
<use_global_rp>"no"</use_global_rp><br />
</camogm_state><br />
<br />
'''This program does not control the process of acquisition of the video/images to the camera internal buffer, it only retrieves that data from the buffer (waiting when needed), packages it to selected format and stores the result files.'''<br />
<br />
==Geo Tagging Specific Commands==<br />
<br />
===kml===<br />
kml=1 # turn on geotagging<br />
<br />
kml=0 # turn off geotagging<br />
<br />
Enable / Disable KML output (geotagging).<br />
<br />
===kml_period===<br />
kml_period=<number_seconds_between_kml_entries><br />
Set the amount of seconds between KML entries. (default: 2)<br />
<br />
===kml_hhf===<br />
kml_hhf=45 # set horizontal half FOV to 45° so the full horizontal FOV is 90°<br />
Set horizontal half FOV in degrees. (default: 20.0)<br />
<br />
===kml_vhf===<br />
kml_vhf=30 # set half vertical FOV to 30° so the full vertical FOV is 60°<br />
Set vertical half FOV in degrees. (default: 15.0)<br />
<br />
===kml_near===<br />
???Set "near" distance to PhotoOverlay in metres (Don't use "0") (default: 40)???<br />
<br />
===kml_alt===<br />
kml_alt=[gps|ground]<br />
Set altitude/height mode.<br />
* gps - absolute GPS altitude<br />
* ground - relative to ground (default)<br />
<br />
===kml_height===<br />
kml_height=100<br />
Set height offset (added to GPS altitude) in metres. (default: 10)<br />
<br />
== Camogm2 ==<br />
This is modified version of camogm to support audio recording (from the firmware 7.1.7.28 or later). It support recording of audio 16bit mono/stereo, from 11025 to 44100 Hz to QuickTime(MOV) and OGG(OGM) file formats. Source of the audio is the sound card (can be connected to camera over USB), and file storage can be USB-flash, HDD (connected to camera directly) or NFS-mounted disk. Preferred method is HDD drive, connected to camera directly, because NFS-mounted disk have a non-uniform system load what can cause broken files.<br />
<br />
The recorded movie have the same duration of the video and sound, but when play it's depend on how player work with file - for example, QuickTime player play movie like the sound is shorter than video, MPlayer will repeat the last sound piece at the end of movie etc. - so it's better to merge movie from the chunks to single movie.<br />
<br />
P.S. First check the sound hardware: set volume to maximum by command<br />
amixer set PCM 100<br />
and try to play test sound file:<br />
aplay /share/sounds/alsa/Front_Center.wav<br />
- if you can't hear any sound, probably you have an old USB card on the camera - this new [http://wiki.elphel.com/images/0/00/10349RevC.jpg 10349 RevC] will work correctly with sound card.<br />
<br />
== camogm2 Commands ==<br />
===audio===<br />
audio=<on|off><br />
command to enable or disable audio recording. When audio support is disabled, camogm work in the same way as original camogm. By default audio is disabled.<br />
<br />
===audio_format===<br />
audio_format=<[rate][/channels]><br />
command to set audio format - frame rate and number of channels. Frame rate can be from 11025 to 44100 Hz; number of channels - 1 for mono sound, or 2 - for stereo. By default 44100/2<br />
<br />
===allow_sync===<br />
allow_sync=<enable|disable><br />
This option is to force writing to storage after each recorded frame. Using a filesystem the OS will write data to buffer before writing to a real device.<br />
This is not a problem with a HDD or other storage media mounted directly on the camera, but with NFS mounted folder this causes trouble as the NFS driver will fill up the buffer and only send data over the network once the buffer is full - this causes a short hang on the camera and frames might be lost. (default: disabled)<br />
===audio_volume===<br />
audio_volume=<volume><br />
Set recording audio volume in percent.<br />
<br />
== camogmgui ==<br />
<br />
'''G'''raphical '''U'''ser '''I'''nterface for camogm.<br />
<br />
Please see [[Camogmgui]]<br />
<br />
== Elphel393 series cameras ==<br />
The functionality of ''camogm'' has been updated in Elphel393 series of cameras. The new version of the program can write data to a raw disk (disk without file system) and send the data over web sockets. The new version of ''camogm'' should be started with two command line arguments:<br />
camogm -n <named_pipe_name> -p <port_number><br />
Where <named_pipe_name> is the file name that will be used to pass commands to ''camogm'' and <port_number> is a port number used for web interface. The existing command set has been extended with several new commands addressing new functions.<br />
<br />
=== port_enable ===<br />
port_enable=<port_number><br />
Enable sensor port <port_number>. All sensor ports are enabled by default.<br />
<br />
=== port_disable ===<br />
port_disable=<port_number><br />
Disable sensor port <port_number>. ''camogm'' does not read data from disabled ports.<br />
<br />
=== rawdev_path ===<br />
Use<br />
rawdev_path=<path_to_disk><br />
or<br />
rawdev_path<br />
commands to set or reset path to raw device buffer. Setting path to raw device buffer along with jpeg format set switches ''camogm'' to raw device buffer operation. All subsequent writes and reads will be performed to or from raw disk. ''camogm'' saves write pointer while the program is running and sequential starts and stops will not lead to data overwrite. ''camogm'' will reject the 'start' command if the path to raw device buffer is set and current image format is not jpeg. You should either reset the path with 'rawdev_path' command without parameters or set format to jpeg with 'format=jpeg' to continue operation. Note, that ''camogm'' does not check the disk in any way and if the path is mistakenly set to a device with file system, the file system and the data on it will be destroyed.<br />
<br />
<br />
''camogm'' can process commands sent over a web socket. A command can be sent as HTTP GET request or as a simple string prefixed with 'cmd/', e.g.:<br />
cmd/next_file<br />
''camogm'' can process the following commands:<br />
<br />
=== find_file ===<br />
find_file:2016:07:12_17:14:00<br />
Find a file with a time stamp which is within one minute time frame from the time stamp given. If such a file was found, ''camogm'' saves the position of the file and 'next_file' command can be used to advance to the next file on disk. If file was not found, ''camogm'' silently resets connection without any data sent.<br />
<br />
=== next_file ===<br />
Get next file from disk. This command should only be used after 'find_file' command successfully finished and returned a file. If file pointer was not set or file was not found, ''camogm'' silently resets connection without any data sent.<br />
<br />
=== read_disk ===<br />
Read disk dump and send it over socket. The dump is split into several pieces and ''camogm'' returns the number of files to be sent in response to the command:<br />
Number of files: <number><br />
The socket is closed right after this string is sent. ''camogm'' opens a socket for each file to be send, waits for connection, sends a file and closes connection after a file was sent.<br />
<br />
=== build_index ===<br />
Read raw device buffer and create disk index directory. This directory contains the offsets of all files found on disk and can be used to retrieve files from disk. This command is a prerequisite for get_index, read_file and read_all_files commands. Note that reading disks of several dozens or hundreds of Gib in size can take much time.<br />
<br />
=== get_index ===<br />
Get disk index directory. Each record in the directory corresponds to a single file and has the following format:<br />
port_number=<port_number>;unix_time=<unix_time>;usec_time=<usec_time>;offset=<disk_offset>;file_size=<size_in_bytes><br />
<unix_time> here is time in Unix format, it represents the number of seconds elapsed since 1970-01-01 00:00:00 +0000 (UTC).<br />
<br />
=== read_file ===<br />
read_file:port_number=<port_number>;unix_time=<unix_time>;usec_time=<usec_time>;offset=<disk_offset>;file_size=<size_in_bytes><br />
Read a file from raw disk buffer and send it over socket. The disk index directory should be built prior this command. If a file was not found in disk index directory (for example, because of a mistake in the command string), ''camogm'' silently resets connection without any data sent.<br />
<br />
=== read_all_files ===<br />
Retrieve all files from disk. Disk index directory should be built before this command can be executed. When this command is received, ''camogm'' sends back the number of files in the disk index directory:<br />
Number of files: <number><br />
The socket is closed right after this string is sent. ''camogm'' opens a socket for each file to be send, waits for connection, sends a file and closes connection after a file is sent.</div>Andrey.filippovhttps://wiki.elphel.com/index.php?title=Trigger_393&diff=13850Trigger 3932021-07-07T14:45:19Z<p>Andrey.filippov: /* External trigger receive (with possible self-triggering loop) */</p>
<hr />
<div>==<font color="blue">Description</font>==<br />
[[10389]] board is required (and possibly [[103891]]).<br />
<br />
Use cases:<br />
* Trigger a single camera from external source<br />
* Synchronize multiple cameras to a master camera or external trigger source<br />
* Program frame rate<br />
<br />
The conditions of the trigger can be generated either internally or externally:<br />
* for external triggering a [[103891]] board and a 4-conductor 2.5mm audio plug with cable (example: [http://www.digikey.com/products/en?keywords=839-1029-ND digikey]) is required.<br />
* for internal triggering use J4-J6 connectors with a 4-pin flex cable: J4 - internal trigger source (also transmits timestamps that can be decoded by other cameras), J5-6 - receive trigger<br />
<br />
To program trigger go to: '''http://192.168.0.9/parsedit.php => External Trigger Controls'''<br />
<br />
'''NOTE: Be careful with changing parameters when TRIG=4. Camera drivers are driven by the frame sync interrupts from the sensor, so if the sensor is not triggered - everything can get stuck. The Program Ahead value sets the number of frame sync interrupts the camera will wait wait for until a parameter is reprogrammed.'''<br />
<br />
[[File:Parsedit screenshot 3.png|thumb|750px|External Trigger Controls page]]<br />
<br />
==<font color="blue">Parameters</font>==<br />
<br />
{| border="1"<br />
|-<br />
| ''parameter'' <br />
| ''description''<br />
|-<br />
| TRIG <br />
| Trigger mode. '''0x0''' - free running, '''0x4''' - triggered by external signal or FPGA timing generator, '''0x14''' - triggered in GRR mode<br />
|-<br />
| TRIG_MASTER<br />
| Master sensor_port (0..3) for triggering setup, other ports will have settings duplicated<br />
|-<br />
| TRIG_CONDITION <br />
| FPGA trigger sequencer trigger condition, 0 - internal, else dibits: 00 - do not use, 01 - keep, 10 - active low, 11 - active high for each GPIO[9:0] pin). 10389 board inverts signals, so 0x80000 - input from external connector, 0x08000 - input from internal flex cable (as in Eyesis)<br />
|-<br />
| TRIG_DELAY <br />
| FPGA trigger sequencer trigger delay, 32 bits in pixel clocks (100MHz or 10ns)<br />
|-<br />
| TRIG_OUT <br />
| FPGA trigger sequencer trigger output to GPIO, dibits: 00 - do not use, 01 - keep, 10 - active low GPIO output, 11 - active high GPIO output. 10389 board inverts signals, so 0x02000 - output to external connector (active high), 0x20000 - output to internal flex connector<br />
|-<br />
| TRIG_PERIOD <br />
| FPGA trigger sequencer output sync period (32 bits, in pixel clocks (100MHz or 10ns)). 0- stop. 1 - single, >=256 repetitive with specified period<br />
|-<br />
| TRIG_BITLENGTH <br />
| Bit length minus 1 (in pixel clock cycles) when transmitting/receiving timestamps, without timestamps the output pulse width is 8*(TRIG_BITLENGTH+1). Legal values 2..255<br />
|-<br />
| EXTERN_TIMESTAMP <br />
| When 1 camera will use external timestamp (received over inter-camera synchronization cable) if it is available (no action when external syncronization is not connected), when 0 - local timestamp will be used<br />
|-<br />
| XMIT_TIMESTAMP <br />
| Specify output signal sent through internal/external connector (defined by TRIG_OUT). 0 - transmit just sync pulse (8*(TRIG_BITLENGTH+1) pixel clock periods long), 1 - pulse+timestamp 64*(TRIG_BITLENGTH+1) pixel clock periods long<br />
|}<br />
<br />
==<font color="blue">Examples</font>==<br />
===Internal periodic trigger (10 fps, from fpga generator)===<br />
* http://192.168.0.9/parsedit.php?sensor_port=0&immediate&TRIG_CONDITION=0&TRIG_PERIOD=10000000&TRIG=4<br />
<br />
===Internal periodic trigger (4 fps, from fpga generator) + output the signal to external port===<br />
* http://192.168.0.9/parsedit.php?sensor_port=0&immediate&TRIG_CONDITION=0&TRIG_OUT=0x66555&TRIG_PERIOD=25000000&TRIG=4<br />
<br />
===External trigger receive (with possible self-triggering loop)===<br />
Here, internal generator is routed to sync the cable output wires.<br />
'''If the output wires are connected to the input wires (red+black and white+green) the camera will be self-triggering. '''<br />
If the wires are not connected - use external source - apply "plus" to black, "minus" to green ([[103891|check colors and pinout]]):<br />
<br />
http://192.168.0.9/parsedit.php?sensor_port=0&immediate&TRIG_CONDITION=0x95555&TRIG_OUT=0x66555&TRIG_PERIOD=100000000&TRIG=4<br />
* at the same time the fpga generator outputs a 1 fps signal - if the sync cable wires are properly connected the camera can be triggered from this 'external' signal<br />
<br />
===External trigger receive (external source only)===<br />
The sync cable wires can be looped or not - does not matter.<br />
http://192.168.0.9/parsedit.php?sensor_port=0&immediate&TRIG_CONDITION=0x95555&TRIG_OUT=0x66555&TRIG_PERIOD=100000000&TRIG=4<br />
* at the same time the fpga generator outputs a 1 fps signal - if the sync cable wires are properly connected the camera can be triggered from this 'external' signal<br />
<br />
===Recover from missing external trigger signal to internal trigger===<br />
* http://192.168.0.9/parsedit.php?sensor_port=0&immediate&TRIG_CONDITION=0*-2<br />
** '''*-2''' - apply value parameter in the current frame (if not specified, the default is 3)<br />
<br />
===Manual triggering from PC===<br />
====Enable====<br />
<font size='2'><br />
http://192.168.0.9:2323/trig/pointers<br />
<br />
* TRIG=4 should be set in advance<br />
* The command automatically sets a single-shot trigger mode with TRIG_PERIOD=0x1, but it writes the register directly into the FPGA, <br />
not updating the TRIG_PERIOD in the PHP interface:<br />
http://192.168.0.9/parsedit.php?TRIG&TRIG_CONDITION&TRIG_DELAY&TRIG_OUT&TRIG_PERIOD&TRIG_BITLENGTH&EXTERN_TIMESTAMP&XMIT_TIMESTAMP&refresh<br />
</font><br />
<br />
====Trigger/Refresh====<br />
<font size='2'><br />
http://192.168.0.9:8081/trig/pointers<br />
<br />
====Check status====<br />
http://192.168.0.9/parsedit.php?immediate&TRIG&TRIG_PERIOD&SENS_AVAIL&FRAME<br />
<br />
====Disable====<br />
=====Update the TRIG_PERIOD in the current frame=====<br />
* http://192.168.0.9/parsedit.php?sensor_port=0&immediate&TRIG_PERIOD=10000000*-2<br />
<br />
=====Update the TRIG_PERIOD from the user interface=====<br />
* http://192.168.0.9/parsedit.php?TRIG&TRIG_CONDITION&TRIG_DELAY&TRIG_OUT&TRIG_PERIOD&TRIG_BITLENGTH&EXTERN_TIMESTAMP&XMIT_TIMESTAMP&refresh<br />
* Refresh until the changes are applied (with Program Ahead = 3 it's 3 times):<br />
http://192.168.0.9:8081/trig/pointers<br />
<br />
<br />
==<font color="blue">Links</font>==<br />
* [[10389]] extension board<br />
* [[103891]] adapter board for external trigger connection<br />
<br />
==<font color="blue">10389 trigger testing</font>==<br />
<br />
===External connector===<br />
In this test the camera triggers itself via audio cable. For cable wiring see [[103891]]. <br />
* To test:<br />
- connect a sensor to port 0<br />
- http://192.168.0.9/parsedit.php?sensor_port=0&immediate&TRIG_CONDITION=0&TRIG_OUT=0x66555&TRIG_PERIOD=25000000&TRIG=4<br />
visual: LED is blinking<br />
software: frame counter is running<br />
<br />
* It's easy to modify the cable to trigger itself and other multiple cameras.<br />
<br />
{|<br />
|[[File:10389 extsync selftest.jpeg|thumb|400px]]<br />
|}<br />
<br />
===Internal connectors===<br />
In this test the camera triggers itself via 4-pin flex cable. <br />
* Connect as displayed on the pictures below.<br />
** J4 - trigger output (master port)<br />
** J5-J6 - trigger input (slave ports)<br />
* To test:<br />
- connect a sensor to port 0<br />
- http://192.168.0.9/parsedit.php?sensor_port=0&immediate&TRIG_CONDITION=0x8000&TRIG_OUT=0x66555&TRIG_PERIOD=25000000&TRIG=4<br />
software: frame counter is running<br />
* To sync multiple camera, example:<br />
cable 1: camera1 (J4) -> camera2 (J6)<br />
cable 2: camera2 (J5) -> camera3 (J6)<br />
cable 3: camera3 (J5) -> camera4 (J6)<br />
etc.<br />
{|<br />
|valign='top'|[[File:10389 intsync selftest.jpeg|thumb|400px]]<br />
|valign='top'|[[File:10389 intsync selftest closeup.jpeg|thumb|400px]]<br />
|}<br />
<br />
===Sync example: from external to internal (chaining)===<br />
* The simplest synchronization would be making a custom audio cable to sync all cameras in the system<br />
* In case there are multiple cameras in the same enclosure it might make sense to sync them by chaining using 4-pin flex cables<br />
{|<br />
|valign='top'|[[File:10389 sync example 1.jpeg|thumb|400px]]<br />
|}<br />
<br />
<br />
[[Category:393]]</div>Andrey.filippovhttps://wiki.elphel.com/index.php?title=10393_manual&diff=1355710393 manual2021-07-01T19:49:47Z<p>Andrey.filippov: /* Firmware images */</p>
<hr />
<div><!-- not anymore!<br />
==<font color="blue">Important Notes</font>==<br />
* As of 2016/12/15, the software ported from 10353 supports only 5MPix sensors, for 14MPix, please see:<br />
**[http://wiki.elphel.com/index.php?title=Tmp_manual&oldid=14676 older version of this manual with links to older software images]--><br />
<br />
<br />
<br />
==<font color="blue">In the package</font>==<br />
* 10393 camera system ([[Elphel_camera_assemblies|these 3D models]] might be helpful).<br />
{|<br />
|valign='top'|[[File:NC393-CS marked ports.jpeg|thumb|200px|Fig.1a 10393 interfaces]]<br />
|valign='top'|[[File:10393_boards_assembly.png|thumb|265px|Fig.1b Boards connections (NC393-F-CS)]]<br />
|valign='top'|[[File:10393 dev mmc.jpeg|thumb|150px|Fig.1c Micro SD card for development]]<br />
|}<br />
* Power supply options ([[10393_power|more information]]):<br />
{| class='wikitable'<br />
!Range<br />
!Power supply<br />
|-<br />
|align='left'|'''36-72V''' (default)<br />
| wall adapter (48V)<br />
|-<br />
|align='left'|'''18-75V'''<br />
| wall adapter (48V)<br />
|-<br />
|align='left'|'''12-36V'''<br />
| wall adapter, battery (12V)<br />
|-<br />
|align='left'|'''3.3V'''<br />
| direct, custom<br />
|}<br />
* CAT6 network cable<br />
* &mu;USB-to-USB cable<br />
* Recovery &mu;SD card<br />
* If the camera is calibrated the calibration data will be on a separate storage media or on the internal SSD (likely /mnt/sda1)<br />
<br />
==<font color="blue">Interfaces</font>==<br />
See Fig.1:<br />
{| class="wikitable"<br />
|-<br />
! GigE<br />
| gigabit network<br />
|-<br />
! &mu;SD <br />
| micro SD card slot - boot or storage<br />
|-<br />
! console<br />
| serial console port, use &mu;USB-to-USB cable<br />
|-<br />
! eSATA+USB<br />
| 2-in-1. Connect USB or eSATA device. USB2.0 host<br />
|-<br />
! &mu;USB<br />
| USB2.0 host<br />
|-<br />
! sync<br />
| sync multiple cameras or other devices - input/output trigger signal through a 4-conductor 2.5mm audio plug with cable (example: [http://www.digikey.com/products/en?keywords=839-1029-ND digikey])<br />
|}<br />
<br />
<br />
<br />
==<font color="blue">Power on</font>==<br />
* Plug in the power supply<br />
* Connect to LAN using the network cable<br />
<br />
====Notes====<br />
* Boot time: ~30s<br />
* No extra drivers are required on the host PC to operate the camera system. Can be operated from any network device with a browser.<br />
* The default boot is from the on-board NAND flash. [[Boot_options_393|More information]] on available boot options and recovery boot.<br />
* For a <font color='red'>'''production system'''</font> with rare changes to the file system it is recommended to boot from NAND flash. Changes to the file system require running an extra sync command (overlay_sync) followed by a proper reboot.<br />
* For <font color='red'>'''development'''</font>, one can boot from the &mu;SD recovery card and use it - saving changes does not require extra sync actions.<br />
* Camera's software includes gcc compiler - relatively small projects can be compiled on the camera.<br />
<br />
==<font color="blue">Defaults</font>==<br />
{| class="wikitable"<br />
|-<br />
! IP Address<br />
| 192.168.0.9<br />
|-<br />
! User <br />
| root<br />
|-<br />
! Password<br />
| pass<br />
|}<br />
<br />
* The default IP address is set in the ''/etc/elphel393/init_elphel393.py''.<br />
* If present the internal SSD will be formatted into 2 partitions:<br />
** /dev/sda1 - ext4 (~64-100GB)<br />
** /dev/sda2 - raw partition (no file system) for fast recording<br />
<br />
==<font color="blue">Command line access</font>==<br />
* ssh from PC's terminal:<br />
<font size='2em'><br />
user@hostname:~$ ssh root@192.168.0.9<br />
</font><br />
<br />
==<font color="blue">Serial console access</font>==<br />
* Use a ''microUSB-USB cable'' to connect '''console &mu;USB port''' (see Fig.1) to PC - the cable's end should be thin enough otherwise interferes with an inserted mmc ('''m'''ulti '''m'''edia '''c'''ard = &mu;SD card).<br />
<br />
* In Linux the '''minicom''' program can be used<br />
<font size='2em'><br />
$ minicom -c on<br />
</font><br />
Most likely the device will be <b>/dev/ttyUSB0</b>. Settings:<br />
* <b>115200 8N1, no</b> for hardware/software flow control<br />
Refer to the following article for more details on using '''minicom''': [http://wiki.elphel.com/index.php?title=Using_minicom_to_connect_to_Elphel393_camera Using minicom to connect to Elphel393 camera]<br />
<br />
==<font color="blue">Web user interface (camvc)</font>==<br />
'''http://192.168.0.9/'''<br />
* The page contains links to camvc user interface for each individual camera port.<br />
* camvc was ported from the 10353 camera series:<br />
** change parameters like image format, resolution, auto exposure, auto white balance and more. Alternative way to change parameters is described [[Tmp_manual#Change_parameters|below]].<br />
** pause compressor and search within buffered images<br />
** help tips available - see Fig.3 - select then mouse over a control element of interest<br />
{|<br />
| valign='top'|[[File:10393 starting page.png|thumb|600px|Fig.2 http://192.168.0.9]]<br />
| valign='top'|[[image:Help tips.jpeg|250px|thumb|Fig.3 enable camvc help tips]]<br />
| valign='top'|[[File:Controls with blank.jpeg|300px|thumb|Fig.4 camvc controls]]<br />
|}<br />
<br />
==<font color="blue">Download live images</font>==<br />
====camvc====<br />
* For a currently opened port (displayed in the window title and as "...sensor_port=0..." in the URL):<br />
{|<br />
|[[image:Camvc image capture.jpeg|250px|thumb|Fig.5 Acquire an image from the Camera Control Interface]]<br />
|}<br />
<br />
====browser====<br />
<font size='2'><br />
port 0: http://192.168.0.9:2323/img<br />
port 1: http://192.168.0.9:2324/img<br />
port 2: http://192.168.0.9:2325/img<br />
port 3: http://192.168.0.9:2326/img<br />
</font><br />
====command line====<br />
<font size='2'><br />
wget http://192.168.0.9:2323/img -O filename.jpeg<br />
wget http://192.168.0.9:2324/img -O filename.jpeg<br />
wget http://192.168.0.9:2325/img -O filename.jpeg<br />
wget http://192.168.0.9:2326/img -O filename.jpeg<br />
</font><br />
<br />
==<font color="blue">Video</font>==<br />
===Display===<br />
====Multipart JPEG stream====<br />
<font size='2'><br />
http://192.168.0.9:2323/mimg<br />
http://192.168.0.9:2324/mimg<br />
http://192.168.0.9:2325/mimg<br />
http://192.168.0.9:2326/mimg<br />
</font><br />
====RTSP====<br />
* Streams with either '''w''' or '''h''' >2040 might not get played - not supported by live555 often used by various media players. But there's a [https://git.elphel.com/Elphel/live555_patch live555_patch].<br />
* turn on:<br />
<font size='2'><br />
root@elphel393:~# /usr/bin/str<br />
</font><br />
* url:<br />
<font size='2'><br />
rtsp://192.168.0.9:554<br />
rtsp://192.168.0.9:556<br />
rtsp://192.168.0.9:558<br />
rtsp://192.168.0.9:560<br />
</font><br />
<br />
====GStreamer====<br />
<font size='2'><br />
gst-launch-1.0 -v playbin uri=rtsp://192.168.0.9:554 uridecodebin0::source::latency=0<br />
or<br />
gst-launch-1.0 souphttpsrc is-live=true location=http://192.168.0.9:2323/mimg ! jpegdec ! xvimagesink <br />
</font><br />
* mjpeg and rtsp<br />
* More examples at [[Using_gstreamer#Display|Using GStreamer]]<br />
<br />
====VLC====<br />
<font size='2'><br />
vlc rtsp://192.168.0.9:554 --network-caching=0<br />
</font><br />
<br />
===Record===<br />
* Recording is done by the [[Camogm|'''camogm''']] program<br />
* If recording to internal or external SSD, please, read about [[Tmp_manual#eSATA_port_switching|eSATA port switching]]<br />
* <font color='red'>important:</font> Event logger (GPS, IMU, IMG, EXT) recording is started/stopped separately. See [[Tmp_manual#Record_the_Event_Logger_data_.28GPS.2CIMU.2CIMG_.26_EXT.29|instructions]] below.<br />
* For SATA devices camogm supports:<br />
** recording to a partition with a file system - up to 80MB/s<br />
** (default) faster recording to a partition without a file system (raw partition) avoiding OS calls - up to 220MB/s<br />
* To extract data from a raw partition use '''dd''' or [https://github.com/Elphel/elphel-tools-x393 these scripts] to get the data and split it into images. Follow [[Extracting_images_from_raw_partition | this link]] for details.<br />
* Can record to an mmc partiton or usb.<br />
* <b><font size='3' color='red'>[[Using_camogm_with_Elphel393_camera|More info]]</font></b><br />
* If the ''prefix'' parameter, which is ''absolute path + prefix'', for a channel is not set the file will be written somewhere to rootfs. <br />
** if prefix is empty then the ''absolute path'' must end with a slash.<br />
<br />
====browser====<br />
Example 1: (provide a correct media mount point - /mnt/sda1/)<br />
<font size='2'><br />
* http://192.168.0.9/camogmgui.php<br />
</font><br />
Follow [[Camogmgui|this link]] for GUI description.<br />
<br />
====command line====<br />
Example:<br />
<font size='2'><br />
* '''/home/root''', file prefix='''test_''', '''1GB''' or '''10min''' files whichever occurs first<br />
** setup and start (in one line):<br />
echo "format=mov;status=/var/tmp/camogm.status;prefix=/home/root/test_;duration=600;length=1073741824;start" > /var/volatile/camogm_cmd<br />
** stop recording:<br />
echo "stop" > /var/volatile/camogm_cmd<br />
sync<br />
</font><br />
<br />
===Convert to a web cam stream===<br />
See this [https://blog.elphel.com/2020/06/convert-ip-cam-to-web-cam-in-linux-for-jitsi-zoom-etc/ tutorial].<br />
<br />
==<font color="blue">Store/restore configuration</font>==<br />
* http://192.168.0.9/autocampars.php - save/restore/initialize camera/sensor parameters per port. To (re)store parameters access the pages below:<br />
<font size='2'><br />
http://192.168.0.9/autocampars.php?sensor_port=0 (stores to /etc/elphel393/autocampars0.xml)<br />
http://192.168.0.9/autocampars.php?sensor_port=1 (stores to /etc/elphel393/autocampars1.xml)<br />
http://192.168.0.9/autocampars.php?sensor_port=2 (stores to /etc/elphel393/autocampars2.xml)<br />
http://192.168.0.9/autocampars.php?sensor_port=3 (stores to /etc/elphel393/autocampars3.xml)<br />
</font><br />
[[Autocampars 393|'''More information''']]<br />
* All stored parameters are automatically restored at boot<br />
<br />
==<font color="blue">Available programmable parameters</font>==<br />
To inspect all available reprogrammable parameters:<br />
1. http://192.168.0.9 -> Parameter Editor<br />
2. Follow a link for a particular port, e.g. http://192.168.0.9/autocampars.php?sensor_port=0<br />
3. Select groups of interest in the top table -> View/Edit Current<br />
<br />
==<font color="blue">Change parameters</font>==<br />
* http://192.168.0.9/parsedit.php - read/write parameters:<br />
** POST request<br />
<font size='2'><br />
Read: http://192.168.0.9/parsedit.php?sensor_port=0&PAR1&PAR2<br />
Change: http://192.168.0.9/parsedit.php?sensor_port=0&PAR1&PAR2 - update values - submit form<br />
</font><br />
** GET request - XML response<br />
<font size='2'><br />
Read: <br />
http://192.168.0.9/parsedit.php?immediate&sensor_port=0&PAR1&PAR2<br />
Change: <br />
http://192.168.0.9/parsedit.php?immediate&sensor_port=0&PAR1=VAL1&PAR2=VAL2<br />
Change for multiple ports at once:<br />
http://192.168.0.9/parsedit.php?immediate&sensor_port=0&PAR1=VAL1&*PAR1=MASK1&PAR2=VAL2&*PAR2=MASK2<br />
<br />
# A port bit mask is set by adding a '''*''' to a parameter name, like '''*PAR1''' - it is individual for each parameter.<br />
# The mask is 4 bits - 1 bit per port, bit[0] = port 0,... bit[3] = port 3, where 1 - enabled, 0 - disabled:<br />
# 0xf - the parameter's new value will be applied to all ports.<br />
# [[Parsedit.php#change_multiple_ports|'''More information''']]<br />
</font><br />
<br />
Note 1: if the parameter's value is specified in URL it will be applied. The call can have mixed specified and unspecified parameters.<br />
<br />
Note 2: The new value is read on the next call.<br />
<br />
Example:<br />
* set 10 fps and enable output trigger signal<br />
<font size='2'><br />
http://192.168.0.9/parsedit.php?sensor_port=0&immediate&TRIG_CONDITION=0&TRIG_OUT=0x66555&TRIG_PERIOD=10000000&TRIG=4<br />
</font><br />
[[Parsedit.php|'''More information''']]<br />
<br />
<br />
'''Notes:'''<br />
* parsedit.php and autocampars.php were ported from 353 camera series. There are a few changes from the originals related to 4x sensor ports:<br />
** parameters are individual for each sensor port - writing parameters to multiple port at once is controlled with a (bit-)'''mask''' input box<br />
** if opened w/o sensor_port specified the page will show links to available ports<br />
** '''sensor_port=x''', where x=0..3 - in the address string - for a single sensor camera it is normally 0<br />
<br />
==<font color="blue">Image formats</font>==<br />
====JPEG====<br />
* ''color'': YCbCr 4:2:0, 3x3 pixels<br />
* ''mono6'': monochrome - color YCbCr 4:2:0 with zeroed out color components<br />
* ''mono'' : monochrome - color YCbCr 4:0:0 with omitted color components<br />
<br />
Note: JPEG is not the best for processing since some information gets lost when demosaicing is applied.<br />
====JP4====<br />
* provides a quality of RAW with compression, no demosaicing<br />
* [[JP4|'''More information''']]<br />
<br />
==<font color="blue">Proper shutdown</font>==<br />
* if not properly shutdown - in a rare case the &mu;SD card can get corrupted (it's always safer to run '''sync''')<br />
<font size='2'><br />
~# sync<br />
~# shutdown -hP now<br />
</font><br />
Same effect:<br />
<font size='2'><br />
http://192.168.0.9/autocampars.php?reboot<br />
</font><br />
<br />
==<font color="blue">Temperature monitor</font>==<br />
* http://192.168.0.9/hwmon.html:<br />
** T<sub>shutdown</sub> - automatic shutdown temperature level (default is 90&deg;C)<br />
{|<br />
|[[File:10393_hwmon.jpeg|thumb|200px]]<br />
|}<br />
<br />
==<font color="blue">Event Logger (GPS, IMU, IMG & EXT)</font>==<br />
<br />
The FPGA-based Event Logger uses local clock for time-stamping data from Image Acquisition, External (Trigger) Input, GPS and IMU.<br />
<br />
* [[Event_logger|'''More information''']]<br />
===Record===<br />
====web====<br />
* Start: <br />
http://192.168.0.9/logger_launcher.php?cmd=start&file=/mnt/sda1/test.log&index=1&n=10000000<br />
* Stop:<br />
http://192.168.0.9/logger_launcher.php?cmd=stop<br />
* Help:<br />
http://192.168.0.9/logger_launcher.php<br />
<br />
====command line====<br />
* start:<br />
<font size='2'><br />
root@elphel393:~# cat /dev/imu > /path/filename.log<br />
</font><br />
* stop - CTRL-C or kill the process<br />
<br />
===Read===<br />
* http://192.168.0.9/read_imu_log.php (will display help)<br />
** on the first access creates /www/pages/logs/ (http://192.168.0.9/logs/)<br />
** link the recorded logs to /www/pages/logs/<br />
** refresh http://192.168.0.9/read_imu_log.php<br />
<br />
==<font color="blue">Set system time</font>==<br />
<br />
===Command line from PC===<br />
<font size='2'># Compare PC and camera clocks<br />
~$ ssh root@192.168.0.9 date;date -u<br />
# Write PC time into camera clock<br />
~$ ssh root@192.168.0.9 "date -s @`( date -u +"%s" )` && hwclock -w"<br />
<br />
===PHP===<br />
If in the current firmware includes '''http://192.168.0.9/utils.php''' then the clock is checked every time the index page is opened ('''http://192.168.0.9'''). The clock is then updated if the browser time differs from the camera time by more than 24h.<br />
<br />
It's also possible to force apply time using the following GET request:<br />
<nowiki>http://192.168.0.9/utils.php?cmd=time&apply&ts=<timestamp_in_ms></nowiki><br />
#example:<br />
<nowiki>http://192.168.0.9/utils.php?cmd=time&apply&ts=1589913066650</nowiki><br />
<br />
==<font color="blue">eSATA port switching</font>==<br />
* requres [[10389]]<br />
* available connections:<br />
** camera <=> internal SSD (default)<br />
** camera <=> external drive (external drive requires a separate power source)<br />
** PC <=> internal SSD<br />
* [[Sata_multiplexer_10389|'''More information''']]<br />
<br />
==<font color="blue">Firmware/software update</font>==<br />
[[Poky_2.0_manual#Write_files_to_media_and_boot|'''More information''']]<br />
<br />
==<font color="blue">Firmware images</font>==<br />
* [https://community.elphel.com/files/393/20210628/ '''20210628''']<br />
* [https://community.elphel.com/files/393/20200903/ 20200903]<br />
* [https://community.elphel.com/files/393/20200520/ 20200520]<br />
* [https://community.elphel.com/files/393/20200508/ 20200508]<br />
<br />
===Changelog===<br />
<font size='1'>'''==20210628=='''<br />
* Added support for FLIR Boson sensors<br />
* Added decimation to external synchronization (triggering on each N-th incoming pulse). That was needed to run slower RGB sensors @12 Hz with Boson as a master at 60Hz<br />
* Enhanced inter-camera synchronization, added related kernel and PHP extension functionality.<br />
<font size='1'>'''==20200903=='''<br />
* switched to warrior branch for build<br />
* updated to kernel 4.19. This build was being under test for a while.<br />
'''==20200520=='''<br />
(rocko build)<br />
* Set time on main page access - taking browser time and writing to 10393 if times differ by 24h+.<br />
* Added script for sensor testing (switch to test pattern, check md5sum).<br />
Supporting MT9P006. Linked to main page.<br />
* Main page:<br />
* Added links to page displaying MJPEG stream in canvas<br />
* Added more controls (FPS, Manual Exposure and Auto Exposure Limit)<br />
* Added quick switch to 1080p@30fps (MT9P006)<br />
* Updated JPEG/JP4 decoding javascript plugin - less time (-10ms) spent on EXIF reading.<br />
* Created utils.php, currenty helps to GET-request:<br />
* ports configuration<br />
* set/get system time<br />
* Fixed snapshot button for cameras with unused ports in multicam/ UI.<br />
'''==20200508=='''<br />
(rocko build)<br />
* updated camogm<br />
* added FLIR Lepton driver to kernel<br />
* added FLIR Lepton record to device tree<br />
'''==20190321=='''<br />
* overall minor changes<br />
* fixed photofinish demo<br />
'''==20180511=='''<br />
* added cron program<br />
* multi cameras control interface<br />
* multi camera system info reporting<br />
* fixed rtc<br />
'''==20180416=='''<br />
* 20180419 - mt9f002: fixed changing window size<br />
* mt9f002: added triggered mode<br />
* mt9f002: added vertical and horizontal flips (mirror)<br />
'''==20180406=='''<br />
* added initial support for MT9F002 sensor: no triggered mode, no binning/decimation<br />
* display serial number in http://camera-ip:port/meta<br />
* decode jp4s on the index page (http://camera-ip)<br />
* turn off auto wb button for all ports on the index page<br />
'''==20180130=='''<br />
* added photo finish demo<br />
* fixed fps limit calcs for triggered mode<br />
'''==20180118=='''<br />
* raw.py & raw.php, see wiki.elphel.com<br />
* added python3 and python3-opencv<br />
'''==20180116=='''<br />
* raw pixel data downloading through membridge<br />
* added gcc,make<br />
'''==20180109=='''<br />
* fixed autoexposure<br />
'''==20171228=='''<br />
* + strace, ltrace, dmsetup<br />
* added to drivers: register devs to sysfs - nodes then created by udev<br />
'''==20171226=='''<br />
* kernel updated to 4.9 (from 4.0)<br />
* lots of drivers is updated to newer versions<br />
* +dm-crypt and cryptsetup<br />
'''==20171120=='''<br />
* bugfix - incorrect displaying of TRIG_PERIOD at init<br />
'''==20171115=='''<br />
* Fixed autocampars to let 10393 work with the mux board - 10359, see wiki.elphel.com for<br />
docs<br />
'''==20170823=='''<br />
* Fixed autocampars for multiple sensors getting desynced at init<br />
* Fixed Garmin GPS 18x USB driver<br />
'''==20170802=='''<br />
* fixed a page for taking snapshots - works in chrome and firefox for bigger images (>2MB)<br />
* enabled "Access-Control-Expose-Headers: Content-Disposition" and CORS<br />
'''==20170627=='''<br />
* viewing decoded jp4 format in camvc<br />
'''==20170623=='''<br />
* fixed incorrect default setting of the master channel<br />
</font><br />
<br />
==<font color="blue">Development</font>==<br />
Usage of [[Poky_manual|SDK]], which is Eclipse and project tree cloned from git.elphel.com, simplifies the development.<br />
At the same time lots of things can be done using Python, PHP, JavaScript or C/C++ (if compiled on hardware) and do not require SDK.<br />
<br />
==<font color="blue">Other info</font>==<br />
===Change default ip address===<br />
Modify '''''/etc/network/interfaces''''', sync the changes to the file system and reboot (or rerun init scripts).<br />
<br />
For firmware 20180511 or older, follow [[Fix_network_configuration|these instructions]] to fix network configuration (= disable setting ip address via '''/etc/elphel393/init_elphel393.py''').<br />
<br />
===Add a program or a shell command to autostart on boot===<br />
There's a way to do this using [https://unix.stackexchange.com/questions/56957/how-to-start-an-application-automatically-on-boot cron or init.d] but it might run before the sensors are initialized by init_elphel393.py. The recommended way is the following:<br />
* '''nano''' or '''vi'''<br />
<font size='2'><br />
ssh root@192.168.0.9<br />
''pass''<br />
root@elphel393:~# nano /etc/elphel393/init_elphel393.py<br />
''edit - save''<br />
''example: to launch the rtsp streamer - add '''shout("/usr/bin/str")''' to the end of the file''. shout() function is just a wrapper for '''subprocess.call(cmd,shell=True)'''<br />
</font><br />
Then:<br />
<font size='2'><br />
#boot from NAND flash?<br />
root@elphel393:~# overlay_sync 1 <br />
root@elphel393:~# shutdown -hP now<br />
#powercycle<br />
<br />
#boot from card?<br />
root@elphel393:~# sync<br />
root@elphel393:~# reboot -f<br />
</font><br />
<br />
===Set up histogram window and autoexposure parameters===<br />
[[Autoexposure|Read article]]<br />
===Tools for calibrated systems===<br />
* [[Elphel_Software_Kit_for_Ubuntu#ImageJ_and_Elphel_plugins_for_imageJ|Install ImageJ plugins]]<br />
** decode jp4 raw format<br />
** aberrations correction<br />
** distortion correction (pixel mapping)<br />
** rectification and projection<br />
** '''JP46 Reader camera''' - decode JP4/JP46<br />
** '''Eyesis correction''' - post-process JP4s using calibration data<br />
<br />
===Switch between ERS and GRR modes in MT9P006===<br />
* [[Electronic_Rolling_Shutter#ERS_and_GRR_in_MT9P001_on_10393|Read article]]<br />
===External/internal synchronization & triggering and FPS control for single/multi-camera systems===<br />
* [[Trigger_393]]<br />
<br />
===SSD/MMC/USB formatting===<br />
* [[Format_SSD_MMC]]<br />
===Boot modes===<br />
* [[Boot_options_393|Boot options]]<br />
===Pointers monitor===<br />
* Displays sensor, compressor and buffer states per 10393 port:<br />
<font size='2'><br />
http://192.168.0.9/pointers/<br />
</font><br />
<br />
===Powering from batteries (12V or 48V)===<br />
[[10393_power#Powering_from_batteries| 12V and 48V power options]]<br />
===Accessing raw pixel values===<br />
[[Working_with_raw_image_data|Working with raw pixel data (how to capture raw images)]]<br />
<br />
===Photo finish (linescan mode)===<br />
[[Photo-finish|Photo Finish]] (works for JP4 image format)<br />
<br />
===Controlling multiple cameras from single GUI===<br />
* [[Multi_camera_system_operation|Recording]]<br />
<br />
===Developers version's half enclosure===<br />
{|<br />
|valign='top'|[[File:10393 half enclosure 1.jpeg|thumb|200px]]<br />
|valign='top'|[[File:10393 half enclosure 2.jpeg|thumb|200px]]<br />
|}<br />
<br />
===Available lengths for cables for connecting sensors in custom setups===<br />
* [[FPC_cables|FPC cables]] - click for available lengths.<br />
* The cables are <font color='red'>asymmetrical</font> - for correct connecting a sensor to a system board see the figure below. As a rule of thumb, the cable's back side (no contacts) will be on the same side with the connector's cover.<br />
{|<br />
|[[Image:Fpc_cable_conn_10393.jpeg|300px|thumb|Connecting sensors to the system board]]<br />
|}<br />
<br />
==<font color="blue">Known problems</font>==<br />
* <font color='green'>'''[SOLVED]'''</font> Vertical artifacts in jpegs. Images are ok at 100% quality. Fixed, testing.<br />
* <font color='green'>'''[SOLVED]'''</font> http://192.168.0.9:232x/noexif/mimg - multipart jpeg displays corrupted frames from time to time. Reason: network bandwidth?<br />
* <font color='green'>'''[SOLVED]'''</font> Sometimes on power-on (NAND flash boot) cannot mount the card's rootfs partition. Kernel Panics. Power off/on. Soft "reboot -f" works ok.<br />
<font size='2'><br />
...<br />
<b>Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,2)</b><br />
...<br />
</font><br />
[[VFS:_Unable_to_mount_root_fs_on_unknown-block(179,2)|More info]]<br />
* <font color='green'>'''[SOLVED]'''</font> Changing exposure/quality/gains - can corrupt images - needs testing.<br />
<br />
* <font color='green'>'''[SOLVED]'''</font> After rewriting rootfs to &mu;SD card - some of the cards get a corrupted partition - re-partitioning (reformatting?) solves the problem.<br />
<font size='2'><br />
On the camera the rootfs is mounted as RW and some of the files are changed (also links created) -<br />
most of the changes are now moved to tmpfs but something might have been missed.<br />
</font><br />
<br />
==<font color="blue">Notes</font>==<br />
* <font color='green'>'''[SOLVED]'''</font> In case rootfs is on flash, it might make sense (or maybe not as the history is updated only once on session exit) to disable bash sessions command history - [http://stackoverflow.com/questions/18663078/disable-history-in-linux disable bash history]<br />
<br />
* <font color='green'>'''[SOLVED]'''</font> When using '''overlays''', deleting, existing in the lower layer, dirs can cause errors (hopefully it gets fixed someday), example: <br />
** /mnt/sda1 exists in lower layer: /tmp/rootfs.ro/tmp<br />
** upper layer is mounted to "/"<br />
<font size='2'><br />
# rmdir /mnt/sda1<br />
# mkdir /mnt/sda1<br />
mkdir: cannot create directory '/mnt/sda1': Operation not supported<br />
</font><br />
[[Category:393]]</div>Andrey.filippovhttps://wiki.elphel.com/index.php?title=Elphel_camera_parts_0353-94&diff=6295Elphel camera parts 0353-942021-04-14T22:03:52Z<p>Andrey.filippov: /* 0353-94-22 - Lock Washer for M1.6, stainless steel 18-8 */</p>
<hr />
<div>[[Elphel_camera_parts]]<br />
== 0353-94 - washers for other than M2 and M2.5 ==<br />
<br />
=== 0353-94-01 - Washer for M1.6, stainless steel 18-8 ===<br />
McMaster p/n 93475A190<br />
{{Cad4|0353-94-01}}<br />
<br />
<br />
----<br />
<br />
=== 0353-94-02 - Washer for 1/4", stainless steel 18-8 ===<br />
McMaster p/n 90107A029<br />
{{Cad4|0353-94-02}}<br />
<br />
<br />
<br />
----<br />
<br />
=== 0353-94-11 - Washer for M3 ===<br />
t=0.7mm, OD=9mm, ID=3.2mm<br />
<br />
McMaster p/n 91116A120<br />
{{Cad4|0353-94-11}}<br />
<br />
----<br />
=== 0353-94-12 - Washer for M3, OD=7mm, stainless steel 18-8 ===<br />
<br />
McMaster p/n 93475A210<br />
<br />
----<br />
=== 0353-94-13 - Lock Washer for M3, stainless steel 18-8 ===<br />
<br />
McMaster p/n 92148A150<br />
<br />
----<br />
<br />
=== 0353-94-22 - Belleville Spring Lock Washer for M1.6 ===<br />
<br />
McMaster p/n 90895A222<br />
{{Cad4a|0353-94-22}}<br />
----<br />
<br />
=== 0353-94-41 - Washer for M4, plastic ===<br />
OD=9mm, ID=4.3mm, t=0.67mm<br />
<br />
McMaster p/n 95610A350<br />
{{Cad4|0353-94-41}}<br />
<br />
----<br />
<br />
=== 0353-94-42 - Washer for M4 ===<br />
OD=9mm, ID=4.3mm, t=0.7mm<br />
<br />
McMaster p/n 93475A230<br />
{{Cad4|0353-94-42}}<br />
<br />
----<br />
=== 0353-94-43 - Lock Washer for M4, stainless steel 18-8 ===<br />
<br />
McMaster p/n 92148A160<br />
<br />
----<br />
<br />
=== 0353-94-44 - Lock Washer for M4, OD=7mm, stainless steel 18-8 ===<br />
McMaster p/n 91111A121<br />
{{Cad4|0353-94-44}}<br />
<br />
----<br />
<br />
=== 0353-94-51 - Washer for M5 ===<br />
McMaster p/n 93475A240<br />
{{Cad4a|0353-94-51}}<br />
----<br />
<br />
=== 0353-94-52 - Lock Washer for M5 ===<br />
McMaster p/n 92148A170<br />
{{Cad4a|0353-94-52}}<br />
----<br />
<br />
=== 0353-94-53 Shim washer ===<br />
ID=5.0mm, OD=10.0mm t=1.0mm <br />
McMaster p/n 98089A375<br />
{{Cad4a|0353-94-53}}<br />
----<br />
<br />
=== 0353-94-61 - Washer, plastic ===<br />
ID=0.25", OD=0.38", t=0.03+/-0.1"<br />
<br />
McMaster p/n 95606A120<br />
{{Cad4|0353-94-61}}<br />
<br />
----<br />
<br />
=== 0353-94-62 - Washer, OD14.0, ID=8.0, t=1.0 ===<br />
{{Cad4|0353-94-62}}<br />
<br />
----<br />
<br />
=== 0353-94-63 - Washer, shim ID=8mm . OD=14, t=0.3===<br />
{{Cad4|0353-94-63}}<br />
<br />
----<br />
<br />
=== 0353-94-64 - Lock washer M8, high collar ===<br />
{{Cad4|0353-94-64}}<br />
<br />
----<br />
<br />
=== 0353-94-65 - Washer for M10, OD=20mm ===<br />
{{Cad4|0353-94-65}}<br />
<br />
----<br />
<br />
=== 0353-94-66 - Lock washer, M10 ===<br />
{{Cad4|0353-94-66}}<br />
<br />
----<br />
<br />
=== 0353-94-67 - Lock washer M10, high collar ===<br />
{{Cad4|0353-94-67}}<br />
<br />
----<br />
<br />
=== 0353-94-71 - Washer for M6, OD=12mm, stainless steel 18-8 ===<br />
<br />
McMaster p/n 93475A250<br />
<br />
----<br />
=== 0353-94-72 - Lock Washer for M6, stainless steel 18-8 ===<br />
<br />
McMaster p/n 92148A180<br />
<br />
----<br />
<br />
=== 0353-94-75 - Washer for 1/4" ===<br />
ID=.281", OD=.625", t=.04"-.06"<br />
McMaster p/n 96765A140<br />
{{Cad4a|0353-94-75}}<br />
----<br />
<br />
=== 0353-94-81 - Washer for M8, OD=16mm, stainless steel 18-8 ===<br />
McMaster p/n 93475A270<br />
<br />
{{Cad4|0353-94-81}}<br />
<br />
----<br />
<br />
=== 0353-94-82 - Lock Washer for M8, stainless steel 18-8 ===<br />
<br />
McMaster p/n 92148A200<br />
<br />
----<br />
<br />
=== 0353-94-90 - Washer, shim. OD=18mm, ID=12mm,t=0.5 ===<br />
{{Cad4|0353-94-90}}<br />
<br />
----<br />
=== 0353-94-92 - Compensating washer, OD=6mm, t=0.8 ===<br />
Part of hardware included to Digi-Key p/n 609-1420-ND<br />
{{Cad4a|0353-94-92}}<br />
<br />
----<br />
<br />
== 0353-95 - washers for M2.5 ==<br />
<br />
=== 0353-95-01 Washer for M2.5 ===<br />
OD=6mm,stainless steel 18-8<br />
McMaster p/n 90965A110<br />
{{Cad4a|0353-95-01}}<br />
----<br />
<br />
=== 0353-95-02 - Lock Washer for M2.5, stainless steel 18-8 ===<br />
McMaster p/n 92148A070<br />
----<br />
<br />
<br />
=== 0353-95-03 - Rubber Washer ID=3mm ===<br />
EPDM<br />
McMaster p/n 90130A007<br />
{{Cad4a|0353-94-53}}<br />
----<br />
<br />
== 0353-96 - washers for M2 ==<br />
=== 0353-96-01 - Washer for M2, Stainless Steel 316, OD=5mm, ID=2.2mm, t=-0.3mm ===<br />
McMaster p/n 90965A110<br />
{{Cad4|0353-96-01}}<br />
<br />
----<br />
=== 0353-96-02 - M2 washer, stainless steel 18-8 ===<br />
McMaster p/n 93475A195<br />
<br />
----<br />
=== 0353-96-03 - Lock Washer for M2, stainless steel 18-8 ===<br />
<br />
McMaster p/n 92148A050<br />
<br />
{{Cad4|0353-96-03}}<br />
<br />
<br />
----</div>Andrey.filippovhttps://wiki.elphel.com/index.php?title=Elphel_camera_parts_0353-94&diff=6294Elphel camera parts 0353-942021-04-14T21:49:40Z<p>Andrey.filippov: /* 0353-94-13 - Lock Washer for M3, stainless steel 18-8 */</p>
<hr />
<div>[[Elphel_camera_parts]]<br />
== 0353-94 - washers for other than M2 and M2.5 ==<br />
<br />
=== 0353-94-01 - Washer for M1.6, stainless steel 18-8 ===<br />
McMaster p/n 93475A190<br />
{{Cad4|0353-94-01}}<br />
<br />
<br />
----<br />
<br />
=== 0353-94-02 - Washer for 1/4", stainless steel 18-8 ===<br />
McMaster p/n 90107A029<br />
{{Cad4|0353-94-02}}<br />
<br />
<br />
<br />
----<br />
<br />
=== 0353-94-11 - Washer for M3 ===<br />
t=0.7mm, OD=9mm, ID=3.2mm<br />
<br />
McMaster p/n 91116A120<br />
{{Cad4|0353-94-11}}<br />
<br />
----<br />
=== 0353-94-12 - Washer for M3, OD=7mm, stainless steel 18-8 ===<br />
<br />
McMaster p/n 93475A210<br />
<br />
----<br />
=== 0353-94-13 - Lock Washer for M3, stainless steel 18-8 ===<br />
<br />
McMaster p/n 92148A150<br />
<br />
----<br />
<br />
=== 0353-94-22 - Lock Washer for M1.6, stainless steel 18-8 ===<br />
<br />
McMaster p/n 92148A150<br />
{{Cad4a|0353-94-22}}<br />
----<br />
<br />
=== 0353-94-41 - Washer for M4, plastic ===<br />
OD=9mm, ID=4.3mm, t=0.67mm<br />
<br />
McMaster p/n 95610A350<br />
{{Cad4|0353-94-41}}<br />
<br />
----<br />
<br />
=== 0353-94-42 - Washer for M4 ===<br />
OD=9mm, ID=4.3mm, t=0.7mm<br />
<br />
McMaster p/n 93475A230<br />
{{Cad4|0353-94-42}}<br />
<br />
----<br />
=== 0353-94-43 - Lock Washer for M4, stainless steel 18-8 ===<br />
<br />
McMaster p/n 92148A160<br />
<br />
----<br />
<br />
=== 0353-94-44 - Lock Washer for M4, OD=7mm, stainless steel 18-8 ===<br />
McMaster p/n 91111A121<br />
{{Cad4|0353-94-44}}<br />
<br />
----<br />
<br />
=== 0353-94-51 - Washer for M5 ===<br />
McMaster p/n 93475A240<br />
{{Cad4a|0353-94-51}}<br />
----<br />
<br />
=== 0353-94-52 - Lock Washer for M5 ===<br />
McMaster p/n 92148A170<br />
{{Cad4a|0353-94-52}}<br />
----<br />
<br />
=== 0353-94-53 Shim washer ===<br />
ID=5.0mm, OD=10.0mm t=1.0mm <br />
McMaster p/n 98089A375<br />
{{Cad4a|0353-94-53}}<br />
----<br />
<br />
=== 0353-94-61 - Washer, plastic ===<br />
ID=0.25", OD=0.38", t=0.03+/-0.1"<br />
<br />
McMaster p/n 95606A120<br />
{{Cad4|0353-94-61}}<br />
<br />
----<br />
<br />
=== 0353-94-62 - Washer, OD14.0, ID=8.0, t=1.0 ===<br />
{{Cad4|0353-94-62}}<br />
<br />
----<br />
<br />
=== 0353-94-63 - Washer, shim ID=8mm . OD=14, t=0.3===<br />
{{Cad4|0353-94-63}}<br />
<br />
----<br />
<br />
=== 0353-94-64 - Lock washer M8, high collar ===<br />
{{Cad4|0353-94-64}}<br />
<br />
----<br />
<br />
=== 0353-94-65 - Washer for M10, OD=20mm ===<br />
{{Cad4|0353-94-65}}<br />
<br />
----<br />
<br />
=== 0353-94-66 - Lock washer, M10 ===<br />
{{Cad4|0353-94-66}}<br />
<br />
----<br />
<br />
=== 0353-94-67 - Lock washer M10, high collar ===<br />
{{Cad4|0353-94-67}}<br />
<br />
----<br />
<br />
=== 0353-94-71 - Washer for M6, OD=12mm, stainless steel 18-8 ===<br />
<br />
McMaster p/n 93475A250<br />
<br />
----<br />
=== 0353-94-72 - Lock Washer for M6, stainless steel 18-8 ===<br />
<br />
McMaster p/n 92148A180<br />
<br />
----<br />
<br />
=== 0353-94-75 - Washer for 1/4" ===<br />
ID=.281", OD=.625", t=.04"-.06"<br />
McMaster p/n 96765A140<br />
{{Cad4a|0353-94-75}}<br />
----<br />
<br />
=== 0353-94-81 - Washer for M8, OD=16mm, stainless steel 18-8 ===<br />
McMaster p/n 93475A270<br />
<br />
{{Cad4|0353-94-81}}<br />
<br />
----<br />
<br />
=== 0353-94-82 - Lock Washer for M8, stainless steel 18-8 ===<br />
<br />
McMaster p/n 92148A200<br />
<br />
----<br />
<br />
=== 0353-94-90 - Washer, shim. OD=18mm, ID=12mm,t=0.5 ===<br />
{{Cad4|0353-94-90}}<br />
<br />
----<br />
=== 0353-94-92 - Compensating washer, OD=6mm, t=0.8 ===<br />
Part of hardware included to Digi-Key p/n 609-1420-ND<br />
{{Cad4a|0353-94-92}}<br />
<br />
----<br />
<br />
== 0353-95 - washers for M2.5 ==<br />
<br />
=== 0353-95-01 Washer for M2.5 ===<br />
OD=6mm,stainless steel 18-8<br />
McMaster p/n 90965A110<br />
{{Cad4a|0353-95-01}}<br />
----<br />
<br />
=== 0353-95-02 - Lock Washer for M2.5, stainless steel 18-8 ===<br />
McMaster p/n 92148A070<br />
----<br />
<br />
<br />
=== 0353-95-03 - Rubber Washer ID=3mm ===<br />
EPDM<br />
McMaster p/n 90130A007<br />
{{Cad4a|0353-94-53}}<br />
----<br />
<br />
== 0353-96 - washers for M2 ==<br />
=== 0353-96-01 - Washer for M2, Stainless Steel 316, OD=5mm, ID=2.2mm, t=-0.3mm ===<br />
McMaster p/n 90965A110<br />
{{Cad4|0353-96-01}}<br />
<br />
----<br />
=== 0353-96-02 - M2 washer, stainless steel 18-8 ===<br />
McMaster p/n 93475A195<br />
<br />
----<br />
=== 0353-96-03 - Lock Washer for M2, stainless steel 18-8 ===<br />
<br />
McMaster p/n 92148A050<br />
<br />
{{Cad4|0353-96-03}}<br />
<br />
<br />
----</div>Andrey.filippovhttps://wiki.elphel.com/index.php?title=Elphel_camera_parts_0393-13&diff=12803Elphel camera parts 0393-132021-04-14T21:47:19Z<p>Andrey.filippov: /* 0393-13-14 - Half-plate for SFE mount */</p>
<hr />
<div>[[Elphel_camera_parts_0393|Elphel NC393 series camera parts]]<br />
=== 0393-13 - Camera back panels ===<br />
----<br />
==== 0393-13-01 - Back panel for NC393, connector openings for 10393A and 10389B connectors ====<br />
{{Cad4a|0393-13-01}}<br />
----<br />
==== 0393-13-01A - Back panel for NC393, Rev. "A", connector openings for 10393A and 10389B connectors ====<br />
{{Cad4a|0393-13-01a}}<br />
----<br />
<br />
==== 0393-13-02 - Back panel for NC393, connector openings for 10393 board only ====<br />
{{Cad4a|0393-13-02}}<br />
----<br />
<br />
==== 0393-13-03 - Camera back connection plate ====<br />
{{Cad4a|0393-13-03}}<br />
----<br />
<br />
==== 0393-13-14 - Half-plate for SFE mount ====<br />
{{Cad4a|0393-13-14}}<br />
----<br />
<br />
==== 0393-13-14A - Half-plate for SFE mount, Rev A ====<br />
{{Cad4a|0393-13-14A}}<br />
----<br />
<br />
==== 0393-13-15 - Sensor Assembly Cover ====<br />
{{Cad4a|0393-13-15}}<br />
----<br />
<br />
==== 0393-13-15B - Sensor Assembly Cover, rev B ====<br />
{{Cad4a|0393-13-15B}}<br />
----<br />
<br />
==== 0393-13-15C - Sensor Assembly Cover, rev CB ====<br />
{{Cad4a|0393-13-15C}}<br />
----<br />
<br />
==== 0393-13-16 - Flex Cables Cover, Side ====<br />
{{Cad4a|0393-13-16}}<br />
----<br />
<br />
==== 0393-13-17 - Flex Cables Cover, Bottom ====<br />
{{Cad4a|0393-13-17}}<br />
----<br />
<br />
==== 0393-13-18 - Flex Cable Cover Spacer, Corner ====<br />
{{Cad4a|0393-13-18}}<br />
----<br />
<br />
==== 0393-13-19 - Flex Cables Cover Spacer, Middle ====<br />
{{Cad4a|0393-13-19}}<br />
----<br />
<br />
==== 0393-13-20 - Back Mount Plate ====<br />
{{Cad4a|0393-13-20}}<br />
----<br />
<br />
==== 0393-13-21 - Camera Mount Plate, Upper ====<br />
{{Cad4a|0393-13-21}}<br />
----<br />
<br />
==== 0393-13-22 - Camera Support ====<br />
{{Cad4a|0393-13-22}}<br />
----<br />
<br />
==== 0393-13-23 - Camera Mount Plate, Bottom ====<br />
{{Cad4a|0393-13-23}}<br />
----</div>Andrey.filippovhttps://wiki.elphel.com/index.php?title=Elphel_camera_parts_0353-99&diff=6165Elphel camera parts 0353-992021-04-14T21:45:49Z<p>Andrey.filippov: /* 0353-99-161 - Screw, M2, Hex Socket Cap, Stainless Steel 18-8, l=4mm */</p>
<hr />
<div>[[Elphel_camera_parts]]<br />
== 0353-99 - Screws, metric, M2 ==<br />
=== 0353-99-01 - Screw, M2, Socket cap, Black anodized, l=6mm ===<br />
McMaster p/n 91239A704<br />
----<br />
=== 0353-99-02 - Screw, M2, Socket cap, Stainless steel 316, l=10mm ===<br />
McMaster p/n 92290A017<br />
{{Cad4|0353-99-02}}<br />
<br />
----<br />
=== 0353-99-03 - Screw, M2, Socket cap, Stainless steel 316, l=12mm ===<br />
McMaster p/n 92290A019<br />
{{Cad4|0353-99-03}}<br />
<br />
----<br />
=== 0353-99-04 - Screw, M2, Flat Socket Cap, Stainless steel 18-8, l=4mm ===<br />
McMaster p/n 92125A050<br />
{{Cad4|0353-99-04}}<br />
<br />
----<br />
=== 0353-99-05 - Screw, M2, Flat Socket Cap, Stainless steel 18-8, l=8mm ===<br />
McMaster p/n 92125A054<br />
{{Cad4|0353-99-05}}<br />
<br />
<br />
----<br />
=== 0353-99-06 - Screw, M2, Flat Socket Cap, Steel, Black, l=4mm ===<br />
McMaster p/n 91294A002<br />
{{Cad4|0353-99-06}}<br />
<br />
<br />
----<br />
<!-- ???=== 0353-99-10 - Set screw, M2, Socket Cap, Steel, Black, l=3mm === <br />
McMaster p/n 91390A090--><br />
<!-- === 0353-99-10 - Screw, M2, Button Head Socket Cap, Steel, Black, l=3mm ===<br />
McMaster p/n 91239A700--><br />
<br />
=== 0353-99-07 - Screw, M2, Flat Socket Cap, Black 18-8, l=8mm ===<br />
McMaster p/n 91294A005<br />
{{Cad4|0353-99-05}}<br />
<br />
----<br />
<br />
=== 0353-99-10 - Screw Socket Head M2, l=3mm ===<br />
McMaster p/n 91292A003 <br />
<br />
----<br />
<br />
=== 0353-99-101 - Screw Button Head M2, Black Oxide, l=3mm ===<br />
McMaster p/n 91239A700 <br />
{{Cad4|0353-99-101}}<br />
<br />
<br />
----<br />
<br />
=== 0353-99-102 - Screw Button Head M2, Black Oxide, l=12mm ===<br />
McMaster p/n 91239A707 <br />
{{Cad4|0353-99-102}}<br />
<br />
<br />
----<br />
<br />
=== 0353-99-11 - Set Screw, M2, Socket Cap, Stainless Steel 18-8, l=4mm ===<br />
McMaster p/n 92015A091<br />
{{Cad4|0353-99-11}}<br />
<br />
----<br />
<br />
=== 0353-99-111 - Set Screw, M2, Socket Cap, Stainless Steel 18-8, l=3mm ===<br />
McMaster p/n 92015A090<br />
{{Cad4|0353-99-111}}<br />
<br />
----<br />
<br />
=== 0353-99-12 - Set Screw, M2, Socket Cap, Stainless Steel 18-8, l=6mm ===<br />
McMaster p/n 92015A093<br />
{{Cad4|0353-99-12}}<br />
<br />
----<br />
=== 0353-99-13 - Set Screw, M2, Socket Cap, Stainless Steel 18-8, l=12mm ===<br />
McMaster p/n 92015A198<br />
{{Cad4|0353-99-13}}<br />
<br />
----<br />
<br />
=== 0353-99-15 - Screw, M2, Button Head Socket Cap, Steel, Black, l=4mm ===<br />
McMaster p/n 91239A703<br />
{{Cad4a|0353-99-15}}<br />
<br />
----<br />
<br />
=== 0353-99-16 - Screw, M2, Hex Socket Cap, Steel, Black, l=4mm ===<br />
McMaster p/n 91290A011<br />
{{Cad4a|0353-99-16}}<br />
----<br />
<br />
=== 0353-99-161 - Screw, M2, Hex Socket Cap, Stainless Steel 18-8, l=4mm ===<br />
McMaster p/n 91292A004<br />
{{Cad4a|0353-99-161}}<br />
----<br />
<br />
=== 0353-99-17 - Screw M2, Flat, Socket, Stainless steel 18-8, l=10mm ===<br />
McMaster p/n 92125A056<br />
{{Cad4|0353-99-17}}<br />
<br />
----<br />
=== 0353-99-18 - Screw, M2, Socket Head, Stainless steel 18-8, l=16mm ===<br />
McMaster p/n 91292A002<br />
{{Cad4|0353-99-18}}<br />
<br />
----<br />
=== 0353-99-19 - Screw, M2, Socket Head, Stainless steel 18-8, l=14mm ===<br />
McMaster p/n 91292A001<br />
{{Cad4|0353-99-19}}<br />
<br />
----<br />
=== 0353-99-20 - Screw, M2, Socket Head, Stainless steel 18-8, l=6mm ===<br />
McMaster <!--p/n 91292A006--> 91292A831<br />
{{Cad4|0353-99-20}}<br />
<br />
----<br />
<br />
=== 0353-99-21 - Screw, M2, Socket Head, Stainless steel 18-8, l=25mm ===<br />
[http://www.microfasteners.com/catalog/products/METSCM.cfm SCM2025]<br />
(slotted - McMaster p/n 91800A023)<br />
{{Cad4|0353-99-21}}<br />
<br />
----<br />
<br />
=== 0353-99-22 - Screw, M2, Socket Head, Stainless steel 18-8, l=20mm ===<br />
McMaster p/n 91292A013<br />
{{Cad4|0353-99-22}}<br />
<br />
----<br />
<br />
=== 0353-99-25 - Screw, M2, Socket Head, Stainless steel 18-8, l=8mm ===<br />
McMaster p/n 91292A008, new p/n 91292A832<br />
{{Cad4|0353-99-25}}<br />
<br />
----</div>Andrey.filippovhttps://wiki.elphel.com/index.php?title=Elphel_camera_parts_0353-99&diff=6164Elphel camera parts 0353-992021-04-14T21:45:23Z<p>Andrey.filippov: /* 0353-99-16 - Screw, M2, Hex Socket Cap, Steel, Black, l=4mm */</p>
<hr />
<div>[[Elphel_camera_parts]]<br />
== 0353-99 - Screws, metric, M2 ==<br />
=== 0353-99-01 - Screw, M2, Socket cap, Black anodized, l=6mm ===<br />
McMaster p/n 91239A704<br />
----<br />
=== 0353-99-02 - Screw, M2, Socket cap, Stainless steel 316, l=10mm ===<br />
McMaster p/n 92290A017<br />
{{Cad4|0353-99-02}}<br />
<br />
----<br />
=== 0353-99-03 - Screw, M2, Socket cap, Stainless steel 316, l=12mm ===<br />
McMaster p/n 92290A019<br />
{{Cad4|0353-99-03}}<br />
<br />
----<br />
=== 0353-99-04 - Screw, M2, Flat Socket Cap, Stainless steel 18-8, l=4mm ===<br />
McMaster p/n 92125A050<br />
{{Cad4|0353-99-04}}<br />
<br />
----<br />
=== 0353-99-05 - Screw, M2, Flat Socket Cap, Stainless steel 18-8, l=8mm ===<br />
McMaster p/n 92125A054<br />
{{Cad4|0353-99-05}}<br />
<br />
<br />
----<br />
=== 0353-99-06 - Screw, M2, Flat Socket Cap, Steel, Black, l=4mm ===<br />
McMaster p/n 91294A002<br />
{{Cad4|0353-99-06}}<br />
<br />
<br />
----<br />
<!-- ???=== 0353-99-10 - Set screw, M2, Socket Cap, Steel, Black, l=3mm === <br />
McMaster p/n 91390A090--><br />
<!-- === 0353-99-10 - Screw, M2, Button Head Socket Cap, Steel, Black, l=3mm ===<br />
McMaster p/n 91239A700--><br />
<br />
=== 0353-99-07 - Screw, M2, Flat Socket Cap, Black 18-8, l=8mm ===<br />
McMaster p/n 91294A005<br />
{{Cad4|0353-99-05}}<br />
<br />
----<br />
<br />
=== 0353-99-10 - Screw Socket Head M2, l=3mm ===<br />
McMaster p/n 91292A003 <br />
<br />
----<br />
<br />
=== 0353-99-101 - Screw Button Head M2, Black Oxide, l=3mm ===<br />
McMaster p/n 91239A700 <br />
{{Cad4|0353-99-101}}<br />
<br />
<br />
----<br />
<br />
=== 0353-99-102 - Screw Button Head M2, Black Oxide, l=12mm ===<br />
McMaster p/n 91239A707 <br />
{{Cad4|0353-99-102}}<br />
<br />
<br />
----<br />
<br />
=== 0353-99-11 - Set Screw, M2, Socket Cap, Stainless Steel 18-8, l=4mm ===<br />
McMaster p/n 92015A091<br />
{{Cad4|0353-99-11}}<br />
<br />
----<br />
<br />
=== 0353-99-111 - Set Screw, M2, Socket Cap, Stainless Steel 18-8, l=3mm ===<br />
McMaster p/n 92015A090<br />
{{Cad4|0353-99-111}}<br />
<br />
----<br />
<br />
=== 0353-99-12 - Set Screw, M2, Socket Cap, Stainless Steel 18-8, l=6mm ===<br />
McMaster p/n 92015A093<br />
{{Cad4|0353-99-12}}<br />
<br />
----<br />
=== 0353-99-13 - Set Screw, M2, Socket Cap, Stainless Steel 18-8, l=12mm ===<br />
McMaster p/n 92015A198<br />
{{Cad4|0353-99-13}}<br />
<br />
----<br />
<br />
=== 0353-99-15 - Screw, M2, Button Head Socket Cap, Steel, Black, l=4mm ===<br />
McMaster p/n 91239A703<br />
{{Cad4a|0353-99-15}}<br />
<br />
----<br />
<br />
=== 0353-99-16 - Screw, M2, Hex Socket Cap, Steel, Black, l=4mm ===<br />
McMaster p/n 91290A011<br />
{{Cad4a|0353-99-16}}<br />
----<br />
<br />
=== 0353-99-161 - Screw, M2, Hex Socket Cap, Stainless Steel 18-8, l=4mm ===<br />
McMaster p/n 91292A004<br />
<br />
----<br />
<br />
=== 0353-99-17 - Screw M2, Flat, Socket, Stainless steel 18-8, l=10mm ===<br />
McMaster p/n 92125A056<br />
{{Cad4|0353-99-17}}<br />
<br />
----<br />
=== 0353-99-18 - Screw, M2, Socket Head, Stainless steel 18-8, l=16mm ===<br />
McMaster p/n 91292A002<br />
{{Cad4|0353-99-18}}<br />
<br />
----<br />
=== 0353-99-19 - Screw, M2, Socket Head, Stainless steel 18-8, l=14mm ===<br />
McMaster p/n 91292A001<br />
{{Cad4|0353-99-19}}<br />
<br />
----<br />
=== 0353-99-20 - Screw, M2, Socket Head, Stainless steel 18-8, l=6mm ===<br />
McMaster <!--p/n 91292A006--> 91292A831<br />
{{Cad4|0353-99-20}}<br />
<br />
----<br />
<br />
=== 0353-99-21 - Screw, M2, Socket Head, Stainless steel 18-8, l=25mm ===<br />
[http://www.microfasteners.com/catalog/products/METSCM.cfm SCM2025]<br />
(slotted - McMaster p/n 91800A023)<br />
{{Cad4|0353-99-21}}<br />
<br />
----<br />
<br />
=== 0353-99-22 - Screw, M2, Socket Head, Stainless steel 18-8, l=20mm ===<br />
McMaster p/n 91292A013<br />
{{Cad4|0353-99-22}}<br />
<br />
----<br />
<br />
=== 0353-99-25 - Screw, M2, Socket Head, Stainless steel 18-8, l=8mm ===<br />
McMaster p/n 91292A008, new p/n 91292A832<br />
{{Cad4|0353-99-25}}<br />
<br />
----</div>Andrey.filippovhttps://wiki.elphel.com/index.php?title=Elphel_camera_parts_0353-99&diff=6163Elphel camera parts 0353-992021-04-14T21:44:32Z<p>Andrey.filippov: /* 0353-99-16 - Screw, M2, Hex Socket Cap, Steel, Black, l=4mm */</p>
<hr />
<div>[[Elphel_camera_parts]]<br />
== 0353-99 - Screws, metric, M2 ==<br />
=== 0353-99-01 - Screw, M2, Socket cap, Black anodized, l=6mm ===<br />
McMaster p/n 91239A704<br />
----<br />
=== 0353-99-02 - Screw, M2, Socket cap, Stainless steel 316, l=10mm ===<br />
McMaster p/n 92290A017<br />
{{Cad4|0353-99-02}}<br />
<br />
----<br />
=== 0353-99-03 - Screw, M2, Socket cap, Stainless steel 316, l=12mm ===<br />
McMaster p/n 92290A019<br />
{{Cad4|0353-99-03}}<br />
<br />
----<br />
=== 0353-99-04 - Screw, M2, Flat Socket Cap, Stainless steel 18-8, l=4mm ===<br />
McMaster p/n 92125A050<br />
{{Cad4|0353-99-04}}<br />
<br />
----<br />
=== 0353-99-05 - Screw, M2, Flat Socket Cap, Stainless steel 18-8, l=8mm ===<br />
McMaster p/n 92125A054<br />
{{Cad4|0353-99-05}}<br />
<br />
<br />
----<br />
=== 0353-99-06 - Screw, M2, Flat Socket Cap, Steel, Black, l=4mm ===<br />
McMaster p/n 91294A002<br />
{{Cad4|0353-99-06}}<br />
<br />
<br />
----<br />
<!-- ???=== 0353-99-10 - Set screw, M2, Socket Cap, Steel, Black, l=3mm === <br />
McMaster p/n 91390A090--><br />
<!-- === 0353-99-10 - Screw, M2, Button Head Socket Cap, Steel, Black, l=3mm ===<br />
McMaster p/n 91239A700--><br />
<br />
=== 0353-99-07 - Screw, M2, Flat Socket Cap, Black 18-8, l=8mm ===<br />
McMaster p/n 91294A005<br />
{{Cad4|0353-99-05}}<br />
<br />
----<br />
<br />
=== 0353-99-10 - Screw Socket Head M2, l=3mm ===<br />
McMaster p/n 91292A003 <br />
<br />
----<br />
<br />
=== 0353-99-101 - Screw Button Head M2, Black Oxide, l=3mm ===<br />
McMaster p/n 91239A700 <br />
{{Cad4|0353-99-101}}<br />
<br />
<br />
----<br />
<br />
=== 0353-99-102 - Screw Button Head M2, Black Oxide, l=12mm ===<br />
McMaster p/n 91239A707 <br />
{{Cad4|0353-99-102}}<br />
<br />
<br />
----<br />
<br />
=== 0353-99-11 - Set Screw, M2, Socket Cap, Stainless Steel 18-8, l=4mm ===<br />
McMaster p/n 92015A091<br />
{{Cad4|0353-99-11}}<br />
<br />
----<br />
<br />
=== 0353-99-111 - Set Screw, M2, Socket Cap, Stainless Steel 18-8, l=3mm ===<br />
McMaster p/n 92015A090<br />
{{Cad4|0353-99-111}}<br />
<br />
----<br />
<br />
=== 0353-99-12 - Set Screw, M2, Socket Cap, Stainless Steel 18-8, l=6mm ===<br />
McMaster p/n 92015A093<br />
{{Cad4|0353-99-12}}<br />
<br />
----<br />
=== 0353-99-13 - Set Screw, M2, Socket Cap, Stainless Steel 18-8, l=12mm ===<br />
McMaster p/n 92015A198<br />
{{Cad4|0353-99-13}}<br />
<br />
----<br />
<br />
=== 0353-99-15 - Screw, M2, Button Head Socket Cap, Steel, Black, l=4mm ===<br />
McMaster p/n 91239A703<br />
{{Cad4a|0353-99-15}}<br />
<br />
----<br />
<br />
=== 0353-99-16 - Screw, M2, Hex Socket Cap, Steel, Black, l=4mm ===<br />
McMaster p/n 91290A011<br />
{{Cad4a|0393-99-16}}<br />
----<br />
<br />
=== 0353-99-161 - Screw, M2, Hex Socket Cap, Stainless Steel 18-8, l=4mm ===<br />
McMaster p/n 91292A004<br />
<br />
----<br />
<br />
=== 0353-99-17 - Screw M2, Flat, Socket, Stainless steel 18-8, l=10mm ===<br />
McMaster p/n 92125A056<br />
{{Cad4|0353-99-17}}<br />
<br />
----<br />
=== 0353-99-18 - Screw, M2, Socket Head, Stainless steel 18-8, l=16mm ===<br />
McMaster p/n 91292A002<br />
{{Cad4|0353-99-18}}<br />
<br />
----<br />
=== 0353-99-19 - Screw, M2, Socket Head, Stainless steel 18-8, l=14mm ===<br />
McMaster p/n 91292A001<br />
{{Cad4|0353-99-19}}<br />
<br />
----<br />
=== 0353-99-20 - Screw, M2, Socket Head, Stainless steel 18-8, l=6mm ===<br />
McMaster <!--p/n 91292A006--> 91292A831<br />
{{Cad4|0353-99-20}}<br />
<br />
----<br />
<br />
=== 0353-99-21 - Screw, M2, Socket Head, Stainless steel 18-8, l=25mm ===<br />
[http://www.microfasteners.com/catalog/products/METSCM.cfm SCM2025]<br />
(slotted - McMaster p/n 91800A023)<br />
{{Cad4|0353-99-21}}<br />
<br />
----<br />
<br />
=== 0353-99-22 - Screw, M2, Socket Head, Stainless steel 18-8, l=20mm ===<br />
McMaster p/n 91292A013<br />
{{Cad4|0353-99-22}}<br />
<br />
----<br />
<br />
=== 0353-99-25 - Screw, M2, Socket Head, Stainless steel 18-8, l=8mm ===<br />
McMaster p/n 91292A008, new p/n 91292A832<br />
{{Cad4|0353-99-25}}<br />
<br />
----</div>Andrey.filippovhttps://wiki.elphel.com/index.php?title=Elphel_camera_parts_0353-99&diff=6162Elphel camera parts 0353-992021-04-14T21:43:57Z<p>Andrey.filippov: /* 0353-99-15 - Screw, M2, Button Head Socket Cap, Steel, Black, l=4mm */</p>
<hr />
<div>[[Elphel_camera_parts]]<br />
== 0353-99 - Screws, metric, M2 ==<br />
=== 0353-99-01 - Screw, M2, Socket cap, Black anodized, l=6mm ===<br />
McMaster p/n 91239A704<br />
----<br />
=== 0353-99-02 - Screw, M2, Socket cap, Stainless steel 316, l=10mm ===<br />
McMaster p/n 92290A017<br />
{{Cad4|0353-99-02}}<br />
<br />
----<br />
=== 0353-99-03 - Screw, M2, Socket cap, Stainless steel 316, l=12mm ===<br />
McMaster p/n 92290A019<br />
{{Cad4|0353-99-03}}<br />
<br />
----<br />
=== 0353-99-04 - Screw, M2, Flat Socket Cap, Stainless steel 18-8, l=4mm ===<br />
McMaster p/n 92125A050<br />
{{Cad4|0353-99-04}}<br />
<br />
----<br />
=== 0353-99-05 - Screw, M2, Flat Socket Cap, Stainless steel 18-8, l=8mm ===<br />
McMaster p/n 92125A054<br />
{{Cad4|0353-99-05}}<br />
<br />
<br />
----<br />
=== 0353-99-06 - Screw, M2, Flat Socket Cap, Steel, Black, l=4mm ===<br />
McMaster p/n 91294A002<br />
{{Cad4|0353-99-06}}<br />
<br />
<br />
----<br />
<!-- ???=== 0353-99-10 - Set screw, M2, Socket Cap, Steel, Black, l=3mm === <br />
McMaster p/n 91390A090--><br />
<!-- === 0353-99-10 - Screw, M2, Button Head Socket Cap, Steel, Black, l=3mm ===<br />
McMaster p/n 91239A700--><br />
<br />
=== 0353-99-07 - Screw, M2, Flat Socket Cap, Black 18-8, l=8mm ===<br />
McMaster p/n 91294A005<br />
{{Cad4|0353-99-05}}<br />
<br />
----<br />
<br />
=== 0353-99-10 - Screw Socket Head M2, l=3mm ===<br />
McMaster p/n 91292A003 <br />
<br />
----<br />
<br />
=== 0353-99-101 - Screw Button Head M2, Black Oxide, l=3mm ===<br />
McMaster p/n 91239A700 <br />
{{Cad4|0353-99-101}}<br />
<br />
<br />
----<br />
<br />
=== 0353-99-102 - Screw Button Head M2, Black Oxide, l=12mm ===<br />
McMaster p/n 91239A707 <br />
{{Cad4|0353-99-102}}<br />
<br />
<br />
----<br />
<br />
=== 0353-99-11 - Set Screw, M2, Socket Cap, Stainless Steel 18-8, l=4mm ===<br />
McMaster p/n 92015A091<br />
{{Cad4|0353-99-11}}<br />
<br />
----<br />
<br />
=== 0353-99-111 - Set Screw, M2, Socket Cap, Stainless Steel 18-8, l=3mm ===<br />
McMaster p/n 92015A090<br />
{{Cad4|0353-99-111}}<br />
<br />
----<br />
<br />
=== 0353-99-12 - Set Screw, M2, Socket Cap, Stainless Steel 18-8, l=6mm ===<br />
McMaster p/n 92015A093<br />
{{Cad4|0353-99-12}}<br />
<br />
----<br />
=== 0353-99-13 - Set Screw, M2, Socket Cap, Stainless Steel 18-8, l=12mm ===<br />
McMaster p/n 92015A198<br />
{{Cad4|0353-99-13}}<br />
<br />
----<br />
<br />
=== 0353-99-15 - Screw, M2, Button Head Socket Cap, Steel, Black, l=4mm ===<br />
McMaster p/n 91239A703<br />
{{Cad4a|0353-99-15}}<br />
<br />
----<br />
<br />
=== 0353-99-16 - Screw, M2, Hex Socket Cap, Steel, Black, l=4mm ===<br />
McMaster p/n 91290A011<br />
<br />
----<br />
<br />
=== 0353-99-161 - Screw, M2, Hex Socket Cap, Stainless Steel 18-8, l=4mm ===<br />
McMaster p/n 91292A004<br />
<br />
----<br />
<br />
=== 0353-99-17 - Screw M2, Flat, Socket, Stainless steel 18-8, l=10mm ===<br />
McMaster p/n 92125A056<br />
{{Cad4|0353-99-17}}<br />
<br />
----<br />
=== 0353-99-18 - Screw, M2, Socket Head, Stainless steel 18-8, l=16mm ===<br />
McMaster p/n 91292A002<br />
{{Cad4|0353-99-18}}<br />
<br />
----<br />
=== 0353-99-19 - Screw, M2, Socket Head, Stainless steel 18-8, l=14mm ===<br />
McMaster p/n 91292A001<br />
{{Cad4|0353-99-19}}<br />
<br />
----<br />
=== 0353-99-20 - Screw, M2, Socket Head, Stainless steel 18-8, l=6mm ===<br />
McMaster <!--p/n 91292A006--> 91292A831<br />
{{Cad4|0353-99-20}}<br />
<br />
----<br />
<br />
=== 0353-99-21 - Screw, M2, Socket Head, Stainless steel 18-8, l=25mm ===<br />
[http://www.microfasteners.com/catalog/products/METSCM.cfm SCM2025]<br />
(slotted - McMaster p/n 91800A023)<br />
{{Cad4|0353-99-21}}<br />
<br />
----<br />
<br />
=== 0353-99-22 - Screw, M2, Socket Head, Stainless steel 18-8, l=20mm ===<br />
McMaster p/n 91292A013<br />
{{Cad4|0353-99-22}}<br />
<br />
----<br />
<br />
=== 0353-99-25 - Screw, M2, Socket Head, Stainless steel 18-8, l=8mm ===<br />
McMaster p/n 91292A008, new p/n 91292A832<br />
{{Cad4|0353-99-25}}<br />
<br />
----</div>Andrey.filippovhttps://wiki.elphel.com/index.php?title=Elphel_camera_parts_0393-19&diff=12898Elphel camera parts 0393-192021-04-14T21:41:50Z<p>Andrey.filippov: /* 0393-19-44 - Guide Tube */</p>
<hr />
<div>[[Elphel_camera_parts_0393|Elphel NC393 series camera parts]]<br />
=== 0393-19-01 - Heat Transfer Bracket ===<br />
{{Cad4a|0393-19-01}}<br />
----<br />
<br />
=== 0393-19-01A - Heat Transfer Bracket, Rev "A" ===<br />
{{Cad4a|0393-19-01A}}<br />
----<br />
<br />
=== 0393-19-02 - Heatsink for DC-DC Converter ===<br />
{{Cad4a|0393-19-02}}<br />
----<br />
<br />
=== 0393-19-03 - Heatsink Spacer ===<br />
{{Cad4a|0393-19-03}}<br />
----<br />
<br />
=== 0393-19-04 - Heatsink Spacer, Alternative ===<br />
{{Cad4a|0393-19-04}}<br />
----<br />
<br />
=== 0393-19-05 - Adjustble Rod Thrust ===<br />
{{Cad4a|0393-19-05}}<br />
----<br />
<br />
=== 0393-19-05A - Adjustble Rod Thrust, REV "A" ===<br />
{{Cad4a|0393-19-05A}}<br />
----<br />
<br />
=== 0393-19-06 - Thrust Coupler ===<br />
{{Cad4a|0393-19-06}}<br />
----<br />
<br />
=== 0393-19-07 - Guide Tube ===<br />
{{Cad4a|0393-19-07}}<br />
----<br />
<br />
=== 0393-19-08 - Hex Key Extender ===<br />
{{Cad4a|0393-19-08}}<br />
----<br />
<br />
=== 0393-19-09 - Hex Key Tip ===<br />
{{Cad4a|0393-19-09}}<br />
----<br />
<br />
=== 0393-19-10 - Hex Key Entry Port ===<br />
{{Cad4a|0393-19-10}}<br />
----<br />
<br />
=== 0393-19-11 - Modified M8 Washer ===<br />
{{Cad4a|0393-19-11}}<br />
----<br />
<br />
=== 0393-19-12 - GPS CTRL Bracket ===<br />
Mount for 0353-00-25 / 103696<br />
{{Cad4a|0393-19-12}}<br />
----<br />
<br />
=== 0393-19-13 - Hex Key Handle ===<br />
{{Cad4a|0393-19-13}}<br />
<br />
----<br />
<br />
=== 0393-19-14 - Clamp Frame ===<br />
{{Cad4a|0393-19-14}}<br />
<br />
----<br />
<br />
=== 0393-19-20 - Spacer ===<br />
{{Cad4a|0393-19-20}}<br />
<br />
----<br />
<br />
=== 0393-19-21 - Disk spring shaft ===<br />
{{Cad4a|0393-19-21}}<br />
<br />
----<br />
<br />
=== 0393-19-22 -Disk spring shaft ===<br />
{{Cad4a|0393-19-22}}<br />
<br />
----<br />
<br />
=== 0393-19-43 - Fan Mount Panel ===<br />
{{Cad4a|0393-19-43}}<br />
<br />
----<br />
<br />
=== 0393-19-44 - Guide Tube ===<br />
{{Cad4a|0393-19-44}}<br />
<br />
----<br />
<br />
=== 0393-19-45 - Guide Tube ===<br />
{{Cad4a|0393-19-45}}<br />
<br />
----<br />
<br />
=== 0393-19-46 - Guide Tube ===<br />
{{Cad4a|0393-19-46}}<br />
<br />
----<br />
<br />
=== 0393-19-81 - Tube body bottom ===<br />
{{Cad4a|0393-19-81}}<br />
<br />
----<br />
<br />
=== 0393-19-841 - Tube Rail, OD=0.25", ID=0.152" ===<br />
Made of McMaster p/n 9056K622 or equiv.<br />
{{Cad4a|0393-19-841}}<br />
<br />
----<br />
<br />
=== 0393-19-100 - Antenna plate ===<br />
{{Cad4a|0393-19-100}}<br />
----<br />
<br />
=== 0393-19-85 - Heat plate mount ===<br />
{{Cad4a|0393-19-85}}<br />
----</div>Andrey.filippovhttps://wiki.elphel.com/index.php?title=103993&diff=152761039932021-04-14T05:51:44Z<p>Andrey.filippov: /* 103993 */</p>
<hr />
<div>==103993==<br />
Adapter for FLIR Boson 640x512 LWIR sensor module<br />
[[Image:103993_pcb-layout.png|thumb|400px|<br />
[[Media:103993_sch.pdf|103993 circuit diagram]] <br/><br />
[[Media:103993_gerber.tar.gz|103993 Gerber files]] <br/><br />
[[Media:103993_assy.tar.gz|103993 placement files]] <br/><br />
[[Media:103993a.pdf|103993 Rev A circuit diagram and parts list]] <br/><br />
[[Media:103993a_gerber.tar.gz|103993 Rev A Gerber files]] <br/><br />
[[Media:103993a_assy.tar.gz|103993 Rev A placement files]]<br />
]]<br />
<br />
Mechanical CAD files and 3D model (rev 0): [[Elphel_camera_parts_0393-00#0393-00-993_-_103993_rev_0_Adapter_for_FLIR_Boson_640x512_LWIR_camera_core_103993 | 0393-00-993]]<br />
<br />
Mechanical CAD files and 3D model (rev A): [[Elphel_camera_parts_0393-00#0393-00-993_-_103993_rev_A_Adapter_for_FLIR_Boson_640x512_LWIR_camera_core_103993 | 0393-00-993A]]</div>Andrey.filippovhttps://wiki.elphel.com/index.php?title=103993&diff=152751039932021-04-14T05:51:22Z<p>Andrey.filippov: </p>
<hr />
<div>==103993==<br />
Adapter for FLIR Boson 640x512 LWIR sensor module<br />
[[Image:103993_pcb-layout.png|thumb|400px|<br />
[[Media:103993_sch.pdf|103993 circuit diagram]] <br/><br />
[[Media:103993_gerber.tar.gz|103993 Gerber files]] <br/><br />
[[Media:103993_assy.tar.gz|103993 placement files]] <br/><br />
[[Media:103993a.pdf|103993 Rev A circuit diagram and parts list]] <br/><br />
[[Media:103993a_gerber.tar.gz|103993 Rev A Gerber files]] <br/><br />
[[Media:103993a_assy.tar.gz|103993 Rev A placement files]]<br />
]]<br />
<br />
Mechanical CAD files and 3D model (rev 0): [[Elphel_camera_parts_0393-00#0393-00-993_-_103993_rev_0_Adapter_for_FLIR_Boson_640x512_LWIR_camera_core_103993 | 0393-00-993]]<br />
Mechanical CAD files and 3D model (rev A): [[Elphel_camera_parts_0393-00#0393-00-993_-_103993_rev_A_Adapter_for_FLIR_Boson_640x512_LWIR_camera_core_103993 | 0393-00-993A]]</div>Andrey.filippovhttps://wiki.elphel.com/index.php?title=File:103993a_assy.tar.gz&diff=15304File:103993a assy.tar.gz2021-04-14T05:48:19Z<p>Andrey.filippov: </p>
<hr />
<div>== Licensing ==<br />
{{CERN OHLv1.1 }}</div>Andrey.filippovhttps://wiki.elphel.com/index.php?title=File:103993a_gerber.tar.gz&diff=15303File:103993a gerber.tar.gz2021-04-14T05:47:54Z<p>Andrey.filippov: </p>
<hr />
<div>== Licensing ==<br />
{{CERN OHLv1.1 }}</div>Andrey.filippovhttps://wiki.elphel.com/index.php?title=File:103993a.pdf&diff=15302File:103993a.pdf2021-04-14T05:47:02Z<p>Andrey.filippov: </p>
<hr />
<div>== Licensing ==<br />
{{GNU FDLv1.3 }}</div>Andrey.filippovhttps://wiki.elphel.com/index.php?title=103993&diff=152741039932021-04-14T05:46:11Z<p>Andrey.filippov: </p>
<hr />
<div>==103993==<br />
Adapter for FLIR Boson 640x512 LWIR sensor module<br />
[[Image:103993_pcb-layout.png|thumb|400px|<br />
[[Media:103993_sch.pdf|103993 circuit diagram]] <br/><br />
[[Media:103993_gerber.tar.gz|103993 Gerber files]] <br/><br />
[[Media:103993_assy.tar.gz|103993 placement files]] <br/><br />
[[Media:103993a.pdf|103993 Rev A circuit diagram and parts list]] <br/><br />
[[Media:103993a_gerber.tar.gz|103993 Rev A Gerber files]] <br/><br />
[[Media:103993a_assy.tar.gz|103993 Rev A placement files]]<br />
]]<br />
<br />
Mechanical CAD files and 3D model: [[Elphel_camera_parts_0393-00#0393-00-993_-_103993_rev_0_Adapter_for_FLIR_Boson_640x512_LWIR_camera_core_103993 | 0393-00-993]]</div>Andrey.filippovhttps://wiki.elphel.com/index.php?title=103993&diff=152731039932021-04-14T05:45:47Z<p>Andrey.filippov: </p>
<hr />
<div>==103993==<br />
Adapter for FLIR Boson 640x512 LWIR sensor module<br />
[[Image:103993_pcb-layout.png|thumb|400px|<br />
[[Media:103993_sch.pdf|103993 circuit diagram]] <br/><br />
[[Media:103993_gerber.tar.gz|103993 Gerber files]] <br/><br />
[[Media:103993a_assy.tar.gz|103993 placement files]] <br/><br />
[[Media:103993a.pdf|103993 Rev A circuit diagram and parts list]] <br/><br />
[[Media:103993a_gerber.tar.gz|103993 Rev A Gerber files]] <br/><br />
[[Media:103993a_assy.tar.gz|103993 Rev A placement files]]<br />
]]<br />
<br />
Mechanical CAD files and 3D model: [[Elphel_camera_parts_0393-00#0393-00-993_-_103993_rev_0_Adapter_for_FLIR_Boson_640x512_LWIR_camera_core_103993 | 0393-00-993]]</div>Andrey.filippovhttps://wiki.elphel.com/index.php?title=Elphel_camera_parts_0393-30&diff=12831Elphel camera parts 0393-302021-04-14T05:37:59Z<p>Andrey.filippov: /* 0393-30-32 - Thermal Pad for m.2 2260 SSD, 6W/m-K, 0.5mm, adhesive one one side */</p>
<hr />
<div>[[Elphel_camera_parts_0393|Elphel NC393 series camera parts]]<br />
== 0393-30 - insulator tubing, spacers, tapes, pads ==<br />
=== 0393-30-18 - O-Ring OD=6mm, ID=4mm ===<br />
{{Cad4a|0393-30-18}}<br />
----<br />
=== 0393-30-20 - Sensor board spacer, 5 mil ===<br />
Mylar, 5 mil<br />
{{Cad4a|0393-30-20}}<br />
----<br />
<br />
=== 0393-30-21 - SFE rotation gasket ===<br />
PTFE 10 mil<br />
{{Cad4a|0393-30-21}}<br />
----<br />
<br />
=== 0393-30-30 - Thermal pad, 6W/m-K ===<br />
Made of Digi-Key p/n H48-6G-300-300-0.3-1A<br />
{{Cad4a|0393-30-30}}<br />
----<br />
<br />
=== 0393-30-31 - Thermal Pad for DCDC, 6W/m-K, 0.5mm, adhesive one one side ===<br />
Cut from H48-6G-150-150-0.5-1A (t-Global Technology), Digi-Key p/n 1168-1289-ND <br />
{{Cad4a|0393-30-31}}<br />
----<br />
<br />
=== 0393-30-32 - Thermal Pad for m.2 2260 SSD, 6W/m-K, 0.5mm, adhesive one one side ===<br />
Cut from H48-6G-150-150-0.5-1A (t-Global Technology), Digi-Key p/n 1168-1289-ND <br />
{{Cad4a|0393-30-32}}<br />
----<br />
<br />
=== 0393-30-33 - Thermal Pad for 103993B PCBA ===<br />
Cut from H48-6G-150-150-0.5-1A (t-Global Technology), Digi-Key p/n 1168-1289-ND <br />
{{Cad4a|0393-30-33}}<br />
----<br />
<br />
=== 0393-30-62 - O-ring, OD=24mm, ID=20mm ===<br />
Viton, McMaster p/n 1295N247 <br />
{{Cad4a|0393-30-62}}<br />
----<br />
<br />
=== 0393-30-63 - O-ring, OD=28mm, ID=24mm ===<br />
Viton, McMaster p/n 9263K503 <br />
{{Cad4a|0393-30-63}}<br />
----<br />
<br />
=== 0393-30-64 - O-ring, OD=36mm, ID=32mm ===<br />
Viton, McMaster p/n 9263K523 <br />
{{Cad4a|0393-30-64}}<br />
----<br />
<br />
=== 0393-30-65 - O-ring, OD=47mm, ID=45mm ===<br />
Viton, McMaster p/n 1295N436 <br />
{{Cad4a|0393-30-65}}<br />
----</div>Andrey.filippovhttps://wiki.elphel.com/index.php?title=Elphel_camera_parts_0393-19&diff=12897Elphel camera parts 0393-192021-04-14T05:36:38Z<p>Andrey.filippov: /* 0393-19-43 - Fan Mount Panel */</p>
<hr />
<div>[[Elphel_camera_parts_0393|Elphel NC393 series camera parts]]<br />
=== 0393-19-01 - Heat Transfer Bracket ===<br />
{{Cad4a|0393-19-01}}<br />
----<br />
<br />
=== 0393-19-01A - Heat Transfer Bracket, Rev "A" ===<br />
{{Cad4a|0393-19-01A}}<br />
----<br />
<br />
=== 0393-19-02 - Heatsink for DC-DC Converter ===<br />
{{Cad4a|0393-19-02}}<br />
----<br />
<br />
=== 0393-19-03 - Heatsink Spacer ===<br />
{{Cad4a|0393-19-03}}<br />
----<br />
<br />
=== 0393-19-04 - Heatsink Spacer, Alternative ===<br />
{{Cad4a|0393-19-04}}<br />
----<br />
<br />
=== 0393-19-05 - Adjustble Rod Thrust ===<br />
{{Cad4a|0393-19-05}}<br />
----<br />
<br />
=== 0393-19-05A - Adjustble Rod Thrust, REV "A" ===<br />
{{Cad4a|0393-19-05A}}<br />
----<br />
<br />
=== 0393-19-06 - Thrust Coupler ===<br />
{{Cad4a|0393-19-06}}<br />
----<br />
<br />
=== 0393-19-07 - Guide Tube ===<br />
{{Cad4a|0393-19-07}}<br />
----<br />
<br />
=== 0393-19-08 - Hex Key Extender ===<br />
{{Cad4a|0393-19-08}}<br />
----<br />
<br />
=== 0393-19-09 - Hex Key Tip ===<br />
{{Cad4a|0393-19-09}}<br />
----<br />
<br />
=== 0393-19-10 - Hex Key Entry Port ===<br />
{{Cad4a|0393-19-10}}<br />
----<br />
<br />
=== 0393-19-11 - Modified M8 Washer ===<br />
{{Cad4a|0393-19-11}}<br />
----<br />
<br />
=== 0393-19-12 - GPS CTRL Bracket ===<br />
Mount for 0353-00-25 / 103696<br />
{{Cad4a|0393-19-12}}<br />
----<br />
<br />
=== 0393-19-13 - Hex Key Handle ===<br />
{{Cad4a|0393-19-13}}<br />
<br />
----<br />
<br />
=== 0393-19-14 - Clamp Frame ===<br />
{{Cad4a|0393-19-14}}<br />
<br />
----<br />
<br />
=== 0393-19-20 - Spacer ===<br />
{{Cad4a|0393-19-20}}<br />
<br />
----<br />
<br />
=== 0393-19-21 - Disk spring shaft ===<br />
{{Cad4a|0393-19-21}}<br />
<br />
----<br />
<br />
=== 0393-19-22 -Disk spring shaft ===<br />
{{Cad4a|0393-19-22}}<br />
<br />
----<br />
<br />
=== 0393-19-43 - Fan Mount Panel ===<br />
{{Cad4a|0393-19-43}}<br />
<br />
----<br />
<br />
=== 0393-19-44 - Guide Tube ===<br />
{{Cad4a|0393-19-44}}<br />
<br />
----<br />
<br />
=== 0393-19-81 - Tube body bottom ===<br />
{{Cad4a|0393-19-81}}<br />
<br />
----<br />
<br />
=== 0393-19-841 - Tube Rail, OD=0.25", ID=0.152" ===<br />
Made of McMaster p/n 9056K622 or equiv.<br />
{{Cad4a|0393-19-841}}<br />
<br />
----<br />
<br />
=== 0393-19-100 - Antenna plate ===<br />
{{Cad4a|0393-19-100}}<br />
----<br />
<br />
=== 0393-19-85 - Heat plate mount ===<br />
{{Cad4a|0393-19-85}}<br />
----</div>Andrey.filippovhttps://wiki.elphel.com/index.php?title=Elphel_camera_parts_0393-18&diff=12822Elphel camera parts 0393-182021-04-14T05:35:13Z<p>Andrey.filippov: /* 0393-18-73A - Adjustment Spherical Mount Inner, Rev A */</p>
<hr />
<div>[[Elphel_camera_parts_0393|Elphel NC393 series camera parts]]<br />
== 0393-18 - parts external other ==<br />
----<br />
=== 0353-18-01 - Vertical arm for H-camera ===<br />
{{Cad4a|0393-18-01}}<br />
----<br />
<br />
=== 0353-18-02 - Horizontal arm for H-camera ===<br />
{{Cad4a|0393-18-02}}<br />
----<br />
<br />
=== 0353-18-30 - tripod mount nut, 1/4-20 thread ===<br />
{{Cad4a|0393-18-30}}<br />
----<br />
<br />
=== 0353-18-31 - tripod mount plate ===<br />
{{Cad4a|0393-18-31}}<br />
----<br />
=== 0353-18-31A - tripod mount plate, Rev "A" ===<br />
{{Cad4a|0393-18-31A}}<br />
----<br />
<br />
=== 0393-18-50 - IMU enclosure ===<br />
{{Cad4a|0393-18-50}}<br />
----<br />
=== 0393-18-51 - Camera top with GPS ===<br />
{{Cad4a|0393-18-51}}<br />
----<br />
=== 0393-18-52 - Camera top without GPS ===<br />
{{Cad4a|0393-18-52}}<br />
----<br />
=== 0393-18-53 - GPS cap ===<br />
{{Cad4a|0393-18-53}}<br />
----<br />
=== 0393-18-53 - Fisheye lens shade ===<br />
{{Cad4a|0393-18-54}}<br />
----<br />
<br />
=== 0393-18-67 - 103993 PCBA Body ===<br />
{{Cad4a|0393-18-67}}<br />
----<br />
<br />
=== 0393-18-67A - 103993 PCBA Body, Rev A ===<br />
{{Cad4a|0393-18-67a}}<br />
----<br />
<br />
<br />
<br />
<!--=== 0393-18-695 - Adjustment Mount Cross Drilled ===<br />
{{Cad4a|0393-18-69}}<br />
---- --><br />
<br />
=== 0393-18-69A Adjustment Mount Cross Drilled, rev A ===<br />
{{Cad4a|0393-18-69A}}<br />
<br />
----<br />
<br />
=== 0393-18-69B Adjustment Mount Cross Drilled, Rev B ===<br />
{{Cad4a|0393-18-69B}}<br />
<br />
----<br />
<br />
=== 0393-18-70 - Adjustable Mount Base for Back Access ===<br />
{{Cad4a|0393-18-70}}<br />
----<br />
<br />
=== 0393-18-70B - Adjustable Mount Base for Back Access, Rev B ===<br />
{{Cad4a|0393-18-70B}}<br />
----<br />
<br />
=== 0393-18-70C - Adjustable Mount Base for Back Access, Rev C ===<br />
{{Cad4a|0393-18-70C}}<br />
----<br />
<br />
=== 0393-18-71 - Adjustment Mount Cross Threaded ===<br />
{{Cad4a|0393-18-71}}<br />
----<br />
<br />
=== 0393-18-72 - Adjustable Mount Base for Helmet ===<br />
{{Cad4a|0393-18-72}}<br />
----<br />
<br />
<!--=== 0393-18-73 - Adjustment Spherical Mount Inner ===<br />
{{Cad4a|0393-18-73}}<br />
------><br />
<br />
=== 0393-18-73A - Adjustment Spherical Mount Inner, Rev A ===<br />
{{Cad4a|0393-18-73A}}<br />
----<br />
<br />
=== 0393-18-73C - Adjustment Spherical Mount Inner, Rev C ===<br />
{{Cad4a|0393-18-73C}}<br />
----</div>Andrey.filippovhttps://wiki.elphel.com/index.php?title=Elphel_camera_parts_0393-18&diff=12821Elphel camera parts 0393-182021-04-14T05:34:31Z<p>Andrey.filippov: </p>
<hr />
<div>[[Elphel_camera_parts_0393|Elphel NC393 series camera parts]]<br />
== 0393-18 - parts external other ==<br />
----<br />
=== 0353-18-01 - Vertical arm for H-camera ===<br />
{{Cad4a|0393-18-01}}<br />
----<br />
<br />
=== 0353-18-02 - Horizontal arm for H-camera ===<br />
{{Cad4a|0393-18-02}}<br />
----<br />
<br />
=== 0353-18-30 - tripod mount nut, 1/4-20 thread ===<br />
{{Cad4a|0393-18-30}}<br />
----<br />
<br />
=== 0353-18-31 - tripod mount plate ===<br />
{{Cad4a|0393-18-31}}<br />
----<br />
=== 0353-18-31A - tripod mount plate, Rev "A" ===<br />
{{Cad4a|0393-18-31A}}<br />
----<br />
<br />
=== 0393-18-50 - IMU enclosure ===<br />
{{Cad4a|0393-18-50}}<br />
----<br />
=== 0393-18-51 - Camera top with GPS ===<br />
{{Cad4a|0393-18-51}}<br />
----<br />
=== 0393-18-52 - Camera top without GPS ===<br />
{{Cad4a|0393-18-52}}<br />
----<br />
=== 0393-18-53 - GPS cap ===<br />
{{Cad4a|0393-18-53}}<br />
----<br />
=== 0393-18-53 - Fisheye lens shade ===<br />
{{Cad4a|0393-18-54}}<br />
----<br />
<br />
=== 0393-18-67 - 103993 PCBA Body ===<br />
{{Cad4a|0393-18-67}}<br />
----<br />
<br />
=== 0393-18-67A - 103993 PCBA Body, Rev A ===<br />
{{Cad4a|0393-18-67a}}<br />
----<br />
<br />
<br />
<br />
<!--=== 0393-18-695 - Adjustment Mount Cross Drilled ===<br />
{{Cad4a|0393-18-69}}<br />
---- --><br />
<br />
=== 0393-18-69A Adjustment Mount Cross Drilled, rev A ===<br />
{{Cad4a|0393-18-69A}}<br />
<br />
----<br />
<br />
=== 0393-18-69B Adjustment Mount Cross Drilled, Rev B ===<br />
{{Cad4a|0393-18-69B}}<br />
<br />
----<br />
<br />
=== 0393-18-70 - Adjustable Mount Base for Back Access ===<br />
{{Cad4a|0393-18-70}}<br />
----<br />
<br />
=== 0393-18-70B - Adjustable Mount Base for Back Access, Rev B ===<br />
{{Cad4a|0393-18-70B}}<br />
----<br />
<br />
=== 0393-18-70C - Adjustable Mount Base for Back Access, Rev C ===<br />
{{Cad4a|0393-18-70C}}<br />
----<br />
<br />
=== 0393-18-71 - Adjustment Mount Cross Threaded ===<br />
{{Cad4a|0393-18-71}}<br />
----<br />
<br />
=== 0393-18-72 - Adjustable Mount Base for Helmet ===<br />
{{Cad4a|0393-18-72}}<br />
----<br />
<br />
<!--=== 0393-18-73 - Adjustment Spherical Mount Inner ===<br />
{{Cad4a|0393-18-73}}<br />
------><br />
<br />
=== 0393-18-73A - Adjustment Spherical Mount Inner, Rev A ===<br />
{{Cad4a|0393-18-73A}}<br />
----</div>Andrey.filippov