Andrey.filippov uploaded File:Gtkwave cocotb.png GTKWave viewer after cocotb simulation finished

New page

== Summary ==
GTKWave viewer after cocotb simulation finished
== Licensing ==
{{GNU FDLv1.3 }} Andrey.filippov

Andrey.filippov uploaded File:Finish cocotb.png VDT+cocotb after simulation finished

New page

== Summary ==
VDT+cocotb after simulation finished
== Licensing ==
{{GNU FDLv1.3 }} Andrey.filippov

Andrey.filippov uploaded File:Continue cocotb.png Screenshot of the running cocotb after client ran several commands

New page

== Summary ==
Screenshot of the running cocotb after client ran several commands
== Licensing ==
{{GNU FDLv1.3 }} Andrey.filippov

Andrey.filippov uploaded File:Launch cocotb.png

New page

== Licensing ==
{{GNU FDLv1.3 }} Andrey.filippov

‎Simulation with Cocotb

← Older revision Revision as of 21:25, 15 November 2017 Line 16: Line 16:  VDT plugin does not use Vivado GUI, in the case of x393 it only uses Vivado synthesis and implementation command line tools. Other projects (x353) for older FPGA devices use Xiinx ISE, it is possible to use Intel/Altera Quartus also. VDT plugin does not use Vivado GUI, in the case of x393 it only uses Vivado synthesis and implementation command line tools. Other projects (x353) for older FPGA devices use Xiinx ISE, it is possible to use Intel/Altera Quartus also.  ==Simulation with Cocotb== ==Simulation with Cocotb==  +Simulation with cocotb uses client-server model.  +  +First you launch Cocotb simulation (double-click on 'Cocotb Python Verification' menu item in the bottom-right panel of VDT perspective. This should launch simulation, and after all the initialization steps are done, simulation will be suspended, waiting for the client to communicate.  +  +Client is a Python application that may run either in the physical camera, or on a GNU/Linux computer. In that case all hardware-dependent functionality (access to the memory or FPGA registers) is replaced by the interaction with Cocotb simulation (see this blog post [https://blog.elphel.com/2016/07/i-will-not-have-to-learn-systemverilog/])  +  +Examples of the commands to launch in the client program are available like comment sin the end of the file [https://git.elphel.com/Elphel/x393/blob/master/py393/x393_jpeg.py] and can be copy-pasted from there. Program is ran from the top directory of the cloned x393 project:  + ./py393/test_mcntrl.py @py393/cocoargs  --simulated=localhost:7777  +  +Next lines are the actual commands to be executed, starting with the DDR memory initialization. The whole command block can be copy-pasted simultaneously, and they will start running - that may take a long times (from tens to hundreds of minutes with small but actual image acquisition and compression on all ports).  +As soon as the client will start, Cocotb simulation in VDT should come to life again and output commands executed  +  + measure_all "*DI" Andrey.filippov

starting page

New page

x393 is a project for the FPGA (Xilinx Zynq 7030) that powers Elphel NC393 camera.

==Code repository==
[https://git.elphel.com/Elphel/x393/]

==Installation instructions==
[https://git.elphel.com/Elphel/x393/blob/master/README.md]

==Introduction==
The project uses Verilog HDL, it is distributed as a project of [[VDT]] plugin for Eclipse IDE. When VDT plugin (and related software) is installed you may launch simulation and implementation tools from this IDE.

Simulation uses Icarus Verilog simulator and Cocotb Python co-simulator (Cocotb still uses Icarus).

Proprietary Implementations tools (x393 project uses only free for download WebPack edition of Xilinx Vivado tools) may be installed on the same computer as the development environment, or on a separate computer - in that case VDP plugin uses ssh+rsync to communicate with teh installed software. Such separation allows to comply with Xilinx WebPack license that requires that computer with Vivado WebPack installation should be connected to the Internet, and at the same time preserve security of the files on your workstation - communication between the two computers is one-way and Vivado can not reach files on the workstation.

VDT plugin does not use Vivado GUI, in the case of x393 it only uses Vivado synthesis and implementation command line tools. Other projects (x353) for older FPGA devices use Xiinx ISE, it is possible to use Intel/Altera Quartus also.
==Simulation with Cocotb== Andrey.filippov

← Older revision Revision as of 20:49, 15 November 2017 (One intermediate revision by the same user not shown)Line 78: Line 78:  [[Category:393]] [[Category:393]]    −==Comments==+==More details==  ===device tree=== ===device tree===  * decompile device tree * decompile device tree Line 89: Line 89:  * compile device tree * compile device tree    ~$ dtc -I dts -O dtb -o devicetree.dtb devicetree.dts   ~$ dtc -I dts -O dtb -o devicetree.dtb devicetree.dts  +  +===if 10389 is connected===  +Go to http://community.elphel.com/bootblock393/ and program 10389 EEPROM  +* Enter camera's IP address in the 1st block (top-left)  +* In the 2nd block:  +** Read AUX  +** Set  + '''Application''' = MT9P006  + '''Application mode''' = as described for 10389-less setup  +** Program AUX  +* Reboot Oleg

marked as legacy, added link to current page

← Older revision Revision as of 20:40, 15 November 2017 Line 1: Line 1:  +{{Legacy}}  +Current page is [[VDT]]  +  == About == == About ==  Eclipse/ExDT (and its special version for Verilog - Eclipse/VDT) is a plugin for Eclipse developed by [http://www.excelsior-usa.com Excelsior,LLC] for Elphel,Inc. Eclipse/ExDT (and its special version for Verilog - Eclipse/VDT) is a plugin for Eclipse developed by [http://www.excelsior-usa.com Excelsior,LLC] for Elphel,Inc. Andrey.filippov

Andrey.filippov moved page Vdt to VDT without leaving a redirect

Andrey.filippov

Andrey.filippov moved page Templete:legacy to Template:Legacy without leaving a redirect

Andrey.filippov

‎Phase adjustments

← Older revision Revision as of 20:35, 15 November 2017 Line 65: Line 65:  ** inspect image ** inspect image  ** TESTSENSOR=0x10008 - color bars mode, see Fig.3 ** TESTSENSOR=0x10008 - color bars mode, see Fig.3 −** MULTI_PHASE1=0x10000 (this worked for )+** MULTI_PHASE1=0x10000 (this worked for the tested setup)  ** MULTI_PHASE2=0x10000 ** MULTI_PHASE2=0x10000  ** MULTI_PHASE3=0x10050 ** MULTI_PHASE3=0x10050 Oleg

← Older revision Revision as of 20:34, 15 November 2017 Line 1: Line 1: −  <font color=red>This is a legacy page. Information may not reflect the current state of the products or code</font>+  <font color=red>This is a legacy page. Information may not reflect the current state of the products or code.</font> Andrey.filippov

general legacy template

New page

<font color=red>This is a legacy page. Information may not reflect the current state of the products or code</font> Andrey.filippov

← Older revision Revision as of 20:33, 15 November 2017 (One intermediate revision by the same user not shown)Line 2: Line 2:     ===Firmware image=== ===Firmware image=== −[https://community.elphel.com/files/393/20171115/ '''20171115'''] or apps-autocampars version at least 1.0.46+[https://community.elphel.com/files/393/20171115/ '''20171115'''] or required apps-autocampars version is at least 1.0.46    root@elphel393:~# cat /etc/elphel393/packages/apps-autocampars     root@elphel393:~# cat /etc/elphel393/packages/apps-autocampars      1.0.46   1.0.46 Line 67: Line 67:  ** MULTI_PHASE1=0x10000 (this worked for ) ** MULTI_PHASE1=0x10000 (this worked for )  ** MULTI_PHASE2=0x10000 ** MULTI_PHASE2=0x10000 −** MULTI_PHASE3=0x10000+** MULTI_PHASE3=0x10050    −[[File:Color_bars.jpeg|thumbs|200px|Fig.3 Test pattern]]+[[File:Color_bars.jpeg|thumb|200px|Fig.3 Test pattern]]  +   +Note: I had a script somewhere for auto adjustment  +   +* Save configuration (for port 0):  + http://192.168.0.9/autocampars.php?sensor_port=0     [[Category:393]] [[Category:393]] Oleg

← Older revision Revision as of 20:30, 15 November 2017 Line 1: Line 1: −  <font color=red>This is a legacy page. The information bellow is not compatible with Elphel 353/363 series cameras.</font>+  <font color=red>This is a legacy page. The information bellow is not compatible with Elphel 393 or 353/363 series cameras.</font> Andrey.filippov

← Older revision Revision as of 20:27, 15 November 2017 Line 54: Line 54:     ===Phase adjustments=== ===Phase adjustments=== −* For each port with incorrect sensor phase (just a quick link):+* For each port with incorrect sensor phase. A quick link for port 0:    http://192.168.0.9/parsedit.php?sensor_port=0&TESTSENSOR&SENSOR_PHASE&MULTI_PHASE1&MULTI_PHASE2&MULTI_PHASE3   http://192.168.0.9/parsedit.php?sensor_port=0&TESTSENSOR&SENSOR_PHASE&MULTI_PHASE1&MULTI_PHASE2&MULTI_PHASE3    Line 64: Line 64:     ** inspect image ** inspect image −** TESTSENSOR=0x10008 - color bars mode+** TESTSENSOR=0x10008 - color bars mode, see Fig.3 −**  +** MULTI_PHASE1=0x10000 (this worked for )  +** MULTI_PHASE2=0x10000  +** MULTI_PHASE3=0x10000     +[[File:Color_bars.jpeg|thumbs|200px|Fig.3 Test pattern]]     [[Category:393]] [[Category:393]] Oleg

Oleg uploaded File:Color bars.jpeg

New page

== Licensing ==
{{CC }} Oleg

created page for VDT plugin

New page

VDT plugin for Eclipse is designed to integrate different tools for Verilog-based FPGA design.
Currently it supports only GNU/Linux operating system and tool specification file support
Icarus Verilog simulator and Xilinx ISE and Vivado Webpack design suites. It also works with Altera
Quartus tools for synthesising FPGA code for Altera devices.

Code repository: [https://git.elphel.com/Elphel/vdt-plugin/]

Installation instructions are: [https://git.elphel.com/Elphel/vdt-plugin/blob/master/README.md]

Video tutorial: [https://blog.elphel.com/2016/05/tutorial-02-eclipse-based-fpga-development-environment-for-elphel-cameras] Andrey.filippov

← Older revision Revision as of 20:21, 15 November 2017 (One intermediate revision by the same user not shown)Line 10: Line 10:  [[File:10393 ports.jpeg|300px|thumb|Fig.1 10393 ports]] [[File:10393 ports.jpeg|300px|thumb|Fig.1 10393 ports]]     +* cable sides as described [[10359#Connect_10353.2C_10359_and_sensors|here]]  * a mux board can be connected to any sensor port * a mux board can be connected to any sensor port  * up to 4x mux boards at the same time (2- do not require extra power modifications) * up to 4x mux boards at the same time (2- do not require extra power modifications) Line 16: Line 17:  [[File:10359top.jpeg|thumb|200px|Fig.2 10359 mux board (older revision)]] [[File:10359top.jpeg|thumb|200px|Fig.2 10359 mux board (older revision)]]    −* if the number of connected mux boards is 3+ then:  +* if the number of connected mux boards is 3+ then extra power is needed:      quick mod: see Fig.2   quick mod: see Fig.2    lift pins 3,4 on J1, put teflon tape under them and solder a wire to those lifted pins connected. Then add a MOS transistor or a switch that will apply external 3.3 V to W2 when those J1.3, J1.4 have     lift pins 3,4 on J1, put teflon tape under them and solder a wire to those lifted pins connected. Then add a MOS transistor or a switch that will apply external 3.3 V to W2 when those J1.3, J1.4 have   Line 51: Line 52:    root@elphel393:~# sync   root@elphel393:~# sync    root@elphel393:~# reboot -f   root@elphel393:~# reboot -f  +  +===Phase adjustments===  +* For each port with incorrect sensor phase (just a quick link):  + http://192.168.0.9/parsedit.php?sensor_port=0&TESTSENSOR&SENSOR_PHASE&MULTI_PHASE1&MULTI_PHASE2&MULTI_PHASE3  +  + TESTSENSOR - test pattern mode  + SENSOR_PHASE - mux or single sensor phase  + MULTI_PHASE1 - mux port 0 (J2)  + MULTI_PHASE2 - mux port 1 (J3)  + MULTI_PHASE3 - mux port 2 (J4)  +  +** inspect image  +** TESTSENSOR=0x10008 - color bars mode  +**       Oleg

← Older revision Revision as of 20:04, 15 November 2017 Line 16: Line 16:  [[File:10359top.jpeg|thumb|200px|Fig.2 10359 mux board (older revision)]] [[File:10359top.jpeg|thumb|200px|Fig.2 10359 mux board (older revision)]]    −* if the number of connected mux boards is 3+ then:  +* if the number of connected mux boards is 3+ then extra power is needed:      quick mod: see Fig.2   quick mod: see Fig.2    lift pins 3,4 on J1, put teflon tape under them and solder a wire to those lifted pins connected. Then add a MOS transistor or a switch that will apply external 3.3 V to W2 when those J1.3, J1.4 have     lift pins 3,4 on J1, put teflon tape under them and solder a wire to those lifted pins connected. Then add a MOS transistor or a switch that will apply external 3.3 V to W2 when those J1.3, J1.4 have   Oleg