Changes

Jump to navigation Jump to search
Line 49: Line 49:  
====Toolkits Overview====
 
====Toolkits Overview====
 
[[File:Rpi github overview.jpg|alt=|center|thumb|600x600px|Software Tookits on github]]
 
[[File:Rpi github overview.jpg|alt=|center|thumb|600x600px|Software Tookits on github]]
Software toolkits contains threeparts. ''veye_raspcam'' is raspcam alike Video Stream Toolkits, D_mipi_rpi is D-SDK Video Stream Toolkits, ''i2c_cmd'' is Video Control Toolkits.
+
Software toolkits contains three parts. ''veye_raspcam'' is raspcam alike Video Stream Toolkits, D_mipi_rpi is D-SDK Video Stream Toolkits, ''i2c_cmd'' is Video Control Toolkits.
    
*Video Stream Tookkits provides real-time display, capture, video recording, etc.
 
*Video Stream Tookkits provides real-time display, capture, video recording, etc.
Line 81: Line 81:     
At the same time,Dispaly real-time video to HDMI output.(use ''-n'' if you do not want preview)
 
At the same time,Dispaly real-time video to HDMI output.(use ''-n'' if you do not want preview)
 +
 +
*veye_raspivid (stream over tcp using gstreamer)
 +
 +
'''''RPI side'''''
 +
 +
<code>./veye_raspivid -b 4000000 -t 0 -o -  | gst-launch-1.0 -v fdsrc ! h264parse ! rtph264pay config-interval=1 pt=96 ! gdppay ! tcpserversink host=x.x.x.x port=5000</code>
 +
 +
H.264 encoding on bitrate 4Mbps,forever,listen on TCP port 5000.
 +
 +
'''''PC side,using gstreamer(Powershell recommended)'''''
 +
 +
<code>gst-launch-1.0 -v tcpclientsrc host=x.x.x.x port=5000 ! gdpdepay ! rtph264depay ! avdec_h264 ! autovideosink sync=false</code>
 +
 +
x.x.x.x is RPI IP address
 +
 +
'''''gstreamer''''' windows version download.
    
*veye_raspivid  (direct tcp stream with '''netcat,gstreamer''' etc..)
 
*veye_raspivid  (direct tcp stream with '''netcat,gstreamer''' etc..)
Line 160: Line 176:  
*compile:
 
*compile:
   −
<code>./build</code>
+
<code>./buildme</code>
    
*install:
 
*install:
Line 231: Line 247:  
Shows how to get yuv stream,transfer to opencv format and display it.
 
Shows how to get yuv stream,transfer to opencv format and display it.
 
===Video Control Toolkits Manual===
 
===Video Control Toolkits Manual===
On Raspberry Pi, I2C-0 is used by GPU. We use I2C-1 as control bus for VEYE Camera Module. We provide a Shell Script — camera_i2c_config— to config pin usage.
+
On Raspberry Pi, We use I2C-0 as control bus for VEYE Camera Module. We provide a Shell Script — camera_i2c_config— to config pin usage.
    
Video Control Toolkits Manual : [[VEYE-MIPI-290/327 i2c/|VEYE-MIPI-290/327 i2c]]
 
Video Control Toolkits Manual : [[VEYE-MIPI-290/327 i2c/|VEYE-MIPI-290/327 i2c]]
<br />
+
 
 
===RPI Computer Module and RPI Zero Additional Info===
 
===RPI Computer Module and RPI Zero Additional Info===
   Line 299: Line 315:  
====Video Control Toolkits====
 
====Video Control Toolkits====
 
Downloading dt-blob.bin file from link,and upload it to /root/,reboot RPI.  
 
Downloading dt-blob.bin file from link,and upload it to /root/,reboot RPI.  
 +
 +
CM3 use I2C-1 to control 2 cameras,It is time-sharing multiplexing.
    
<code>./camera_i2c_config [cameranum]</code>
 
<code>./camera_i2c_config [cameranum]</code>
Line 310: Line 328:  
|1
 
|1
 
|CAM1
 
|CAM1
|}<code>./veye_mipi_i2c.sh -b [i2c bus num]</code>
+
|}<code>./veye_mipi_i2c.sh -b 1</code>
{| class="wikitable"
+
 
!i2c bus num
+
<br />Other options see : [[VEYE-MIPI-290/327 i2c/zh|VEYE-MIPI-290/327 i2c]]
!description
  −
|-
  −
|0
  −
|CAM0
  −
|-
  −
|1
  −
|CAM1
  −
|}<br />Other options see : [[VEYE-MIPI-290/327 i2c/zh|VEYE-MIPI-290/327 i2c]]
   
===FFC Cable Remarks===
 
===FFC Cable Remarks===
  

Navigation menu