‎About

← Older revision Revision as of 23:48, 1 December 2017 (3 intermediate revisions by the same user not shown)Line 4: Line 4:  10393 is the system board of Elphel NC393 series camera. It is also the core part of the [[Eyesis4Pi_393|Eyesis4Pi 393]], the full-sphere multi-camera system. It has the same physical dimensions as the 10353 (previous generation) and may be used as an upgrade to the previous camera modules. 10393 is the system board of Elphel NC393 series camera. It is also the core part of the [[Eyesis4Pi_393|Eyesis4Pi 393]], the full-sphere multi-camera system. It has the same physical dimensions as the 10353 (previous generation) and may be used as an upgrade to the previous camera modules.    −More information related to NC393 series is available here [https://blog.elphel.com/category/model-393/]+More information related to NC393 series is available here [https://blog.elphel.com/category/model-393 https://blog.elphel.com/category/model-393]     ==Overview== ==Overview== Line 105: Line 105:     ==Known issues== ==Known issues== −* [http://wiki.elphel.com/index.php?title=SATA_issues SATA issues]+* [[SATA_issues|SATA issues]] (old ones, all fixed now) − +* [[PCB_Assembly_Problems#10393_rev_B|PCB assembly problems]] (manually corrected, to be considered during future production runs) −    [[Category:393]] [[Category:393]] Andrey.filippov

‎Known issues

← Older revision Revision as of 21:53, 1 December 2017 (2 intermediate revisions by the same user not shown)Line 105: Line 105:     ==Known issues== ==Known issues== −* [http://wiki.elphel.com/index.php?title=SATA_issues SATA issues]+* [[SATA_issues|SATA issues]] (old ones, all fixed now) − +* [[PCB_Assembly_Problems#10393_rev_B|PCB assembly problems]] (manually corrected, to be considered during future production runs) −    [[Category:393]] [[Category:393]] Andrey.filippov

‎10393 rev B

← Older revision Revision as of 21:47, 1 December 2017 Line 2: Line 2:     ==10393 rev B== ==10393 rev B== −<gallery widths=300 heights=400 mode=nolines caption="manufacturing flaws">+<gallery widths=300 heights=400 mode=nolines caption="10393 B">    File:10393 mflaw 1.jpg| Figure 1a. DC1 pin (closest) is bent up, not soldered   File:10393 mflaw 1.jpg| Figure 1a. DC1 pin (closest) is bent up, not soldered    File:10393 mflaw 2.jpeg| Figure 1b. micro USB connector (J4) pins are not soldered   File:10393 mflaw 2.jpeg| Figure 1b. micro USB connector (J4) pins are not soldered  </gallery> </gallery> Andrey.filippov

Created page with "Some PCB assembly problems to be considered during next production runs ==10393 rev B== <gallery widths=300 heights=400 mode=nolines caption="manufacturing flaws"> File:1039..."

New page

Some PCB assembly problems to be considered during next production runs

==10393 rev B==
<gallery widths=300 heights=400 mode=nolines caption="manufacturing flaws">
File:10393 mflaw 1.jpg| Figure 1a. DC1 pin (closest) is bent up, not soldered
File:10393 mflaw 2.jpeg| Figure 1b. micro USB connector (J4) pins are not soldered
</gallery> Andrey.filippov

← Older revision Revision as of 21:45, 1 December 2017 (2 intermediate revisions by the same user not shown)Line 2: Line 2:  [[Image:10393_top_sm.png|frame|[[Media:10393_top.jpeg|10393 board, top view]]]] [[Image:10393_top_sm.png|frame|[[Media:10393_top.jpeg|10393 board, top view]]]]  [[Image:10393_bottom_sm.png|frame|[[Media:10393_bottom.jpeg|10393 board, bottom view]]]] [[Image:10393_bottom_sm.png|frame|[[Media:10393_bottom.jpeg|10393 board, bottom view]]]] −10393 is the system board of Elphel NC393 series camera. It is the core part of the [[Eyesis4Pi_393|Eyesis4Pi 393]], the full-sphere multi-camera system. It has the same physical dimensions as the 10353 (previous generation) and may be used as an upgrade to the previous camera modules.+10393 is the system board of Elphel NC393 series camera. It is also the core part of the [[Eyesis4Pi_393|Eyesis4Pi 393]], the full-sphere multi-camera system. It has the same physical dimensions as the 10353 (previous generation) and may be used as an upgrade to the previous camera modules.  +   +More information related to NC393 series is available here [https://blog.elphel.com/category/model-393/]     ==Overview== ==Overview== Line 105: Line 107:  * [http://wiki.elphel.com/index.php?title=SATA_issues SATA issues] * [http://wiki.elphel.com/index.php?title=SATA_issues SATA issues]    −==Collection of manufacturing flaws==  −<gallery widths=300 heights=400 mode=nolines caption="manufacturing flaws">  − File:10393 mflaw 1.jpg| Figure 1a. DC1 pin (closest) is bent up, not soldered  − File:10393 mflaw 2.jpeg| Figure 1b. micro USB connector (J4) pins are not soldered  −</gallery>      [[Category:393]] [[Category:393]] Andrey.filippov

‎10338D

← Older revision Revision as of 21:37, 1 December 2017 (One intermediate revision by the same user not shown)Line 1: Line 1: −==10338D==+==10338D, 10338E==  [[Image:10338d.jpeg|frame|[[Media:10338d.jpeg|10338 board, rev D and E]]]] [[Image:10338d.jpeg|frame|[[Media:10338d.jpeg|10338 board, rev D and E]]]]  [[Image:10338bd.png|frame|[[Media:10338d.pdf|10338D Circuit Diagram, PCB layout]] <br/> [[Media:10338d_gerber.tar.gz|10338 rev D Gerber files]]]] [[Image:10338bd.png|frame|[[Media:10338d.pdf|10338D Circuit Diagram, PCB layout]] <br/> [[Media:10338d_gerber.tar.gz|10338 rev D Gerber files]]]] Line 6: Line 6:  Connectors: Connectors:  * 30-pin flex cable connector (J1) for data and power. * 30-pin flex cable connector (J1) for data and power.  +  +These boards are compatible with the [[10393]] camera system board. Andrey.filippov

legacy warning, link to the new content

← Older revision Revision as of 21:35, 1 December 2017 Line 1: Line 1:  +{{Legacy}} See similar current products here: [[10393]]  == Elphel 353/363 series cameras and camera modules == == Elphel 353/363 series cameras and camera modules ==    Andrey.filippov

links to current development

← Older revision Revision as of 21:33, 1 December 2017 Line 1: Line 1:  +{{legacy}} See current FPGA project here: [[X393]], [[VDT]]  == Introduction == == Introduction ==  Much of the performance and flexibility of the Elphel cameras are provided by the reconfigurable [http://en.wikipedia.org/wiki/Fpga FPGA] chips. FPGA is used on the main camera board (currently it is [[10353]]) and on some of the extension ones ([[10347]], [[10359]], [[10357]]). On the main board the FPGA chip complements CPU to perform video processing and compression - it does this nearly 100 times faster than the CPU alone, but generally it is significantly more difficult to implement some functionality in the FPGA than it can be done in the software. And so the camera (like many other modern devices) combines the strong features of both: FPGA performs computationally intensive but algorithmically relatively simple operations (working with the images on the pixel level, providing image compression) and the CPU is responsible for the higher level functions, interface and overall control of the camera. Much of the performance and flexibility of the Elphel cameras are provided by the reconfigurable [http://en.wikipedia.org/wiki/Fpga FPGA] chips. FPGA is used on the main camera board (currently it is [[10353]]) and on some of the extension ones ([[10347]], [[10359]], [[10357]]). On the main board the FPGA chip complements CPU to perform video processing and compression - it does this nearly 100 times faster than the CPU alone, but generally it is significantly more difficult to implement some functionality in the FPGA than it can be done in the software. And so the camera (like many other modern devices) combines the strong features of both: FPGA performs computationally intensive but algorithmically relatively simple operations (working with the images on the pixel level, providing image compression) and the CPU is responsible for the higher level functions, interface and overall control of the camera. Andrey.filippov

‎Collection of manufacturing flaws

← Older revision Revision as of 00:09, 30 November 2017 (2 intermediate revisions by the same user not shown)Line 106: Line 106:     ==Collection of manufacturing flaws== ==Collection of manufacturing flaws== −<gallery widths=400 heights=500 mode=nolines caption="manufacturing flaws">+<gallery widths=300 heights=400 mode=nolines caption="manufacturing flaws">    File:10393 mflaw 1.jpg| Figure 1a. DC1 pin (closest) is bent up, not soldered   File:10393 mflaw 1.jpg| Figure 1a. DC1 pin (closest) is bent up, not soldered  + File:10393 mflaw 2.jpeg| Figure 1b. micro USB connector (J4) pins are not soldered  </gallery> </gallery>     [[Category:393]] [[Category:393]] Oleg

Oleg uploaded File:10393 mflaw 2.jpeg

New page

== Licensing ==
{{CC }} Oleg

‎Collection of manufacturing flaws

← Older revision Revision as of 23:38, 29 November 2017 (2 intermediate revisions by the same user not shown)Line 104: Line 104:  ==Known issues== ==Known issues==  * [http://wiki.elphel.com/index.php?title=SATA_issues SATA issues] * [http://wiki.elphel.com/index.php?title=SATA_issues SATA issues]  +  +==Collection of manufacturing flaws==  +<gallery widths=400 heights=500 mode=nolines caption="manufacturing flaws">  + File:10393 mflaw 1.jpg| Figure 1a. DC1 pin (closest) is bent up, not soldered  +</gallery>     [[Category:393]] [[Category:393]] Oleg

‎Collection of manufacturing flaws

← Older revision Revision as of 21:44, 29 November 2017 (One intermediate revision by the same user not shown)Line 104: Line 104:  ==Known issues== ==Known issues==  * [http://wiki.elphel.com/index.php?title=SATA_issues SATA issues] * [http://wiki.elphel.com/index.php?title=SATA_issues SATA issues]  +  +==Collection of manufacturing flaws==  +<gallery widths=400 heights=500 mode=nolines caption="manufacturing flaws">  + File:10393 mflaw 1.jpg| Figure 1a. DC1 pin is bent up, not soldered  +</gallery>     [[Category:393]] [[Category:393]] Oleg

Oleg uploaded a new version of File:10393 mflaw 1.jpg

New page

Oleg

Oleg uploaded File:10393 mflaw 1.jpg

New page

Oleg

‎Initializing Eclipse Workspace for Existing (Cloned) Verilog Projects

← Older revision Revision as of 17:27, 29 November 2017 (One intermediate revision by the same user not shown)Line 66: Line 66:  ==Initializing Eclipse Workspace for Existing (Cloned) Projects== ==Initializing Eclipse Workspace for Existing (Cloned) Projects==  After running '''setup.py''' for the first time you may create the brand new workspace for Eclipse, that should have all necessary plugins (such as CDT and EGit at least) already installed. Workspace is created with '''setup_eclipse.py''' script, list of projects that it sets up is saved in '''setup_eclipse_paths.xml''' file. '''setup_eclipse.py''' provides usage information when launched without parameters, for normal run it requires full path to Eclipse installation - directory that contains '''eclipse''' executable and '''eclipse.ini''' configuration. Before running '''setup_eclipse.py''' Eclipse should have all the required plugins installed (at least CDT and EGit) using temporary workspace. After running '''setup.py''' for the first time you may create the brand new workspace for Eclipse, that should have all necessary plugins (such as CDT and EGit at least) already installed. Workspace is created with '''setup_eclipse.py''' script, list of projects that it sets up is saved in '''setup_eclipse_paths.xml''' file. '''setup_eclipse.py''' provides usage information when launched without parameters, for normal run it requires full path to Eclipse installation - directory that contains '''eclipse''' executable and '''eclipse.ini''' configuration. Before running '''setup_eclipse.py''' Eclipse should have all the required plugins installed (at least CDT and EGit) using temporary workspace.  +  + ./setup_eclipse.py &lt;eclipse_home&gt; &lt;workspace_path&gt;     '''setup_eclipse.py''' performs 2 actions: '''setup_eclipse.py''' performs 2 actions: Line 72: Line 74:     After creating a new workspace with '''setup_eclipse.py''' it can be opened with Eclipse, the projects you plan to use have to be indexed (right-click on the project in the Navigator ⇒ Index ⇒ Rebuild. After creating a new workspace with '''setup_eclipse.py''' it can be opened with Eclipse, the projects you plan to use have to be indexed (right-click on the project in the Navigator ⇒ Index ⇒ Rebuild.  +  +==Initializing Eclipse Workspace for Existing (Cloned) Verilog Projects==  +'''setup_eclipse.py''' can also be used to setup a separate workspace for the FPGA projects for the camera:  +  +*x393 - full camera RTL code and test benches. It has several active branches:  +** master - production camera code  +** dct - development branch for testing DCT-IV/DST-IV and CLT modules for image correction and 3d reconstruction  +** CMV300 - development for the high-speed CMOSIS sensor, will be used for other sensors with compatible interface  +*x393_sata - AHCI/SATA subsystem. The code is included in x393, this repository is for faster troubleshooting and may be used for other applications  +*x359 - FPGA code for [[10359|10359 sensor multiplexer]]  +  +These projects are now opened from the second instance of Eclipse IDE. [https://git.elphel.com/Elphel/vdt-plugin|VDT plugin] has to be installed first (imported to the workspace and set up). The Eclipse FPGA workspace is created with the following command issued from the elphel393 project directory:  + ./setup_eclipse.py &lt;eclipse_home&gt; &lt;workspace_fpga_path&gt; setup_eclipse_fpga_paths.xml  +where eclipse_home is the path to Eclipse installation and  workspace_fpga_path is a path to the new workspace (should be different from the workspace_path set earlier.  +The workspace_fpga_path should also be specified in Run Configuration -> Eclipse application of the "main" Eclipse.     ==Setting up New Project== ==Setting up New Project== Andrey.filippov

← Older revision Revision as of 00:21, 26 November 2017 Line 7: Line 7:  |} |}    −[http://www3.elphel.com Elphel 10393 series] are highly customizable high performance, network, multi-sensor (multi-) camera systems.+Elphel 393 series are highly customizable high performance, network, multi-sensor (multi-) camera systems.     To ensure the freedom of our customers and the sustainable development of the Elphel project all our developments are covered by the GNU/GPL v3 License. To ensure the freedom of our customers and the sustainable development of the Elphel project all our developments are covered by the GNU/GPL v3 License. Andrey.filippov

‎Setting up New Project

Show changes Andrey.filippov

‎Setting up New Project

Show changes Andrey.filippov

Show changes Andrey.filippov

‎Initializing Eclipse Workspace for Existing (Cloned) Projects

← Older revision Revision as of 03:16, 22 November 2017 (17 intermediate revisions by the same user not shown)Line 1: Line 1:  +==Introduction==  +Elphel camera software is based on Yocto Poky distribution, all the individual projects such as Linux kernel drivers, C/C++ applications, web applications, Python projects are organized as '''Makefile''' projects, each tied to a separate Git repository. The makefiles are not standalone, they receive defined variables provided by '''bitbake''' recipes and classes.     +The top project [https://git.elphel.com/Elphel/elphel393 elphel393] has the '''setup.py''' script that installs and synchronizes them. All projects have Eclipse IDE configuration data (in '''eclipse_project_setup''' subdirectories), and this data is copied to the project root by '''setup.py'''. As Eclipse project settings may have user-dependent settings, current configuration files (/.project, /.cproject, ...) are not version controlled, so to restore them after corruption or just to get updated versions you need either to manually copy '''eclipse_project_setup''' sub-tree, or delete /.project and re-run '''setup.py'''.    − +Eclipse IDE setting reference not only files that are in the Git repository, but also those that are generated during build process, so Eclipse should be launched with these projects only after the command-line [[Poky_2.0_manual#Setup|build process]] has finished. If Eclipse is opened after some project is cleared (such as with '''bitbake -c clean''') it will delete the non-existing directories from '''.cproject''' configuration files. If that happens, you may close Eclipse and restore '''.cproject''' from the '''eclipse_project_setup/.cproject'''. −  ├── bitbake-logs -> /home/eyesis/nc393/elphel393/poky/build/tmp/work/cortexa9-neon-poky-linux-gnueabi/apps-gps/1_0-26/temp+  −  ├── eclipse_project_setup+   +After running '''setup.py''' for the first time you may create the brand [[#Initializing_Eclipse_Workspace_for_Existing_.28Cloned.29_Projects|new workspace]] for Eclipse.  +Projects are relying on '''bitbake''' build process, so main Eclipse build command launches '''bitbake ''target-name'' -c compile -f''' instead of '''make all''' or similar. And as error processing (problem highlighting in the source code, jump to source file/line) is possible only for the main builder, it is the '''CDT Builder''' that has to be configured this way.  +   +   +==Project Files and Directories==  +   +Below is the file/directory list of a typical application ('''elphel-apps-astreamer''' is a subdirectory of '''elphel393/rootfs-elphel''', '''apps-astreamer''' - bitbake target for this project):  +   +  ├── '''bitbake-logs''' -> /home/eyesis/nc393/elphel393/poky/build/tmp/work/cortexa9-neon-poky-linux-gnueabi/apps-astreamer/1_0-23/temp  +  ├── '''eclipse_project_setup'''    │   ├── .externalToolBuilders   │   ├── .externalToolBuilders −  │   │   └── SCP apps-gps to target.launch+  │   │   └── SCP apps-astreamer to target.launch    │   ├── .cproject   │   ├── .cproject    │   └── .project   │   └── .project −  ├── .externalToolBuilders+  ├── '''.externalToolBuilders''' −  │   └── SCP apps-gps to target.launch+  │   └── SCP apps-astreamer to target.launch −  ├── image -> /home/eyesis/nc393/elphel393/poky/build/tmp/work/cortexa9-neon-poky-linux-gnueabi/apps-gps/1_0-26/image+  ├── '''.git''' −  ├── scripts -> ../../scripts/+  ... −  │   ├── run_bitbake.sh+ ├── '''image''' -> /home/eyesis/nc393/elphel393/poky/build/tmp/work/cortexa9-neon-poky-linux-gnueabi/apps-astreamer/1_0-23/image −  │   └── used_files.py+  ├── '''scripts''' -> ../../scripts/ −  ├── src+  │  ├── '''run_bitbake.sh''' − │   ├── .depend+  │  └── '''used_files.py''' −  │   ├── exifgen.c+  ├── '''.settings''' − │   ├── exifgen.h+  │   └── language.settings.xml −  │   ├── garmin.h+  ├── '''src''' −  │   ├── garminusb2exif.c+  │   ├── audio.cpp −  │   ├── garminusb2nmea.c+  │   ├── audio.h − │   ├── imu_setup.php+  ... − │   ├── logger_launcher.php+  │   ├── streamer.h − │   ├── log_imu.c+  │   ├── video.cpp −  │   ├── Makefile+  │   └── video.h − │   ├── nmea2exif+  ├── '''sysroots''' -> /home/eyesis/nc393/elphel393/poky/build/tmp/sysroots − │   ├── nmea2exif.c+  ├── '''.cproject''' − │   ├── nmeagen.c+  ├── '''.gitignore''' − │   ├── nmeagen.h+  ├── '''LICENSE''' −  │   ├── read_imu_log.php+  ├── '''Makefile''' −  │   └── start_gps_compass.php+  ├── '''.project''' −  ├── sysroots -> /home/eyesis/nc393/elphel393/poky/build/tmp/sysroots+  ├── '''README.md''' −  ├── .cproject+  └── '''VERSION''' −  ├── .gitignore+*'''bitbake-logs''' is a convenience link to the latest bitbake build logs −  ├── LICENSE+*'''eclipse_project_setup''' copy of Eclipse IDE  settings under version control. Content of the subdirectory is copied (during setup or manually) to teh project root directory (one level up). −  ├── Makefile+*'''.externalToolBuilders''' is copied from '''eclipse_project_setup''' and then maintained by Eclipse. Currently is used to launch file copying to the target (actual camera). −  ├── .project+*'''.git''' - project Git data tree −  ├── README.md+*'''image''' is a link to directory that contains deployable files, built as a result of bitbake recipes execution. −  └── VERSION+*'''scripts''' - a link to a collection of scripts needed for all projects. It contains the following files:  +**'''run_bitbake.sh''' - script to create an environment and execute bitbake recipe. Used every time Eclipse builds the project.  +**'''used_files.py''' - script to create a list of header files/directories used by bitbake to build the project. It is not needed to run to configure existing projects - all of them are provided with preconfigured '''.cproject''' files. ''TODO: add link to description''  +*'''.settings''' - project settings maintained by Eclipse IDE  +*'''src''' - a hard-coded (in '''used_files.py''') directory name for C/C++ source files. Source files should not be in the project root directory for convenience of filter generation for additional source (headers) directories  +*'''sysroots''' - a link to header files directories, available in the target system. The content is generated after the linux kernel is being built. All the applications use header files from the subdirectories of this folder. This link is generated for every project by the bitbake class.  +*'''.cproject''' - Eclipse CDT project configuration. Parts of this file are modified by the scripts, such as '''used_files.py'''. This file is copied from version-controlled '''eclipse_project_setup''' during setup or manually.  +*'''.gitignore''' - Git ignore file list  +*'''LICENSE''' - project GNU GPLv3 license  +*'''Makefile''' - top make file of the project. It is invoked when executing bitbake recipes, it receives variables defined in bitbake recipes/classes  +*'''.project''' - Eclipse general project configuration. This file is copied from version-controlled '''eclipse_project_setup''' during setup or manually.  +*'''README.md''' - README file presented by the Git repository web interface  +*'''VERSION''' - project version, used by bitbake build process to determine which dependent recipes have to be re-ran.  +==Initializing Eclipse Workspace for Existing (Cloned) Projects==  +After running '''setup.py''' for the first time you may create the brand new workspace for Eclipse, that should have all necessary plugins (such as CDT and EGit at least) already installed. Workspace is created with '''setup_eclipse.py''' script, list of projects that it sets up is saved in '''setup_eclipse_paths.xml''' file. '''setup_eclipse.py''' provides usage information when launched without parameters, for normal run it requires full path to Eclipse installation - directory that contains '''eclipse''' executable and '''eclipse.ini''' configuration. Before running '''setup_eclipse.py''' Eclipse should have all the required plugins installed (at least CDT and EGit) using temporary workspace.  +   +'''setup_eclipse.py''' performs 2 actions:  +*It first batch-imports all the listed in '''setup_eclipse_paths.xml''' projects using headless build of the CDT (org.eclipse.cdt.managedbuilder.core.headlessbuild), without actually building and indexing files - indexing should be done manually before using particular project.  +*Next it connects project Git repositories to Eclipse EGit, so the projects are immediately ready for Git operations ('team' operations). project navigator shows repository and branch for each of the projects.     +After creating a new workspace with '''setup_eclipse.py''' it can be opened with Eclipse, the projects you plan to use have to be indexed (right-click on the project in the Navigator ⇒ Index ⇒ Rebuild.     +==a==  +==b==  +==c==  [[File:Eclipse builders.png|500px|thumb|right|Figure 1. Project builders]] [[File:Eclipse builders.png|500px|thumb|right|Figure 1. Project builders]]  [[File:Eclipse scp main.png|500px|thumb|right|Figure 2. Configuring SCP to target tool for apps-astreamer project]] [[File:Eclipse scp main.png|500px|thumb|right|Figure 2. Configuring SCP to target tool for apps-astreamer project]]  [[File:Eclipse scp options.png|500px|thumb|right|Figure 3. Configuring SCP to target tool for apps-astreamer project(options)]] [[File:Eclipse scp options.png|500px|thumb|right|Figure 3. Configuring SCP to target tool for apps-astreamer project(options)]]  [[File:Eclipse ccpp build.png|500px|thumb|right|Figure 4. C/C++ Build ⇒ Builder Settings]] [[File:Eclipse ccpp build.png|500px|thumb|right|Figure 4. C/C++ Build ⇒ Builder Settings]] −[[File:Eclipse builders.png|500px|thumb|right|Figure 5. Project builders]]+[[File:Eclipse ccpp build behavior.png|500px|thumb|right|Figure 5. C/C++ Build ⇒ Behavior]] −[[File:Eclipse builders.png|500px|thumb|right|Figure 6. Project builders]]+[[File:Eclipse ccpp build refresh.png|500px|thumb|right|Figure 6. C/C++ Build ⇒ Refresh Policy]] −[[File:Eclipse builders.png|500px|thumb|right|Figure 6. Project builders]]+[[File:Eclipse source location.png|500px|thumb|right|Figure 7. C/C++ General ⇒ Paths and Symbols ⇒ Source Location]] Andrey.filippov