On the Tinker Edge T board, we get video from the camera using the command:

gst-launch-1.0 v4l2src device=/dev/video0 ! "video/x-raw,format=(string)YUY2, width=(int)1920, height=(int)1080,framerate=(fraction)30/1" ! glimagesink

But when trying to get the h264 stream using the command:

gst-launch-1.0 v4l2src device=/dev/video0 ! "video/x-raw,format=(string)YUY2, width=(int)1920, height=(int)1080,framerate=(fraction)30/1" ! videoconvert ! x264enc ! h264parse ! rtph264pay config-interval=1 pt=96 ! rtph264depay ! rtspclientsink protocols=tcp location=rtsp://0.0.0.0:8554/live/h264 latency=1000

An error is thrown:
photo_2022-02-22_14-07-48.jpg

How to get h264 stream?

@wqh
这个我也不是很懂，但是我们文档4.2.1章节的
Gstreamer 嵌入到 OpenCV 部分，肯定是一种实现方法，有很多客户都是这么做的。

@jdx-jdx
通过-b来指明不同的i2c bus.
请参考下面链接的 4.3.1部分
http://wiki.veye.cc/index.php/VEYE_CS_Camera_for_Jetson_TX2/zh#.E8.A7.86.E9.A2.91.E6.8E.A7.E5.88.B6.E8.BD.AF.E4.BB.B6.E5.8C.85.E7.9A.84.E4.BD.BF.E7.94.A8

@veye_xumm Okay. Anyway Thank you.

@meitiever
Can you provide the command you executed?

@daxue0116
正常情况下，插上两个，会probe到两个。
你可以看看/dev/video0 /dev/video1是否同时存在。
另外可以看看

dmesg | grep 307

的输出情况。

Hi, I tried the V4L2 driver with Buster which worked OK on a Pi4 4 GB then I tested Bullseye with the legacy mode and the same V4L2 driver ( veyecam2m ver 5.10.63) and that worked OK too.
I was previously testing with a Pi 3A which I would like to work but that does seem to have a problem with the v4L2 driver with both OS's.

@veye_xumm 重新插拔了下线，目前已经能正常读到，看来应该是线没有接好

@veye_xumm
We use:

veye_raspivid -b 1000000 -t 0 -n -o -

and checked:

veye_raspivid -b 1000000 -t 0 -p '0,0,1920,1080'

Using these commands results in a reboot, with the distortions shown above. veye_raspipreview displays such pictures perfectly.

@年华灬
这个模组启动比较慢，大约7-8秒，你进行sysreset之后需要等会儿才能正确读到。
会不会是i2c通信有问题，你检查检查排线插接情况，是否有接触不良？
可以循环使用
i2cdetect -y 10
查看是否有0x3b,有的话，说明摄像头的i2c还活着，在响应。

如果detect一会儿有，一会儿没有，一种可能，摄像头在不停重启。
可以尝试在detect到的时候发送sysreset

@zjutony
为防万一我这边测试了一下。用的jetson nx，jetpack4.6.
45d47986-5c26-40c3-9b9a-53113b74bd5b-image.png
图像是正常的啊。
请你检查一下我上面列出的模式相关的内容，看一下结果。

@ruimin-huang 不客气

@maponarooo
Good.
These are two different product lines with impassable solutions. From sensors, to isp, etc.

@sjchen
除了你已经修改的地方之外，
需要用
D_init_camera_ex函数代替D_init_camera，这个函数具备分辨率的定义参数。

@zjutony
你说的没错，132不支持那么大的分辨率。
http://wiki.veye.cc/index.php/CS-MIPI-SC132_Data_Sheet/zh

@anatom
please read http://wiki.veye.cc/index.php/VEYE-MIPI-290/327_for_Raspberry_Pi
part2

Hi

Oh, my mistake I only downloaded veye_mipi_i2c.sh, I didn't realise it called i2c_read, i2c_write.
Sorry I will download all files tomorrow and try again.

thanks
Nigel

@nigel-gardiner
You are welcome.

@zhangxuezhi618
你好，我们现在在bullseye系统上已经可以执行原有程序了。请参考wiki文档尝试一下。