SOLVED CS-USB-IMX307 OpenCV 連續採集影像造成 USB disconnct

veye_xumm

@coolmitch
我也是按照这个步骤做的。但是cmake阶段报错了。

coolmitch

@veye_xumm cmake 可能需要重新安裝新版。
參考這個（我有點忘記更新 cmake 的程序了)
https://stackoverflow.com/questions/49859457/how-to-reinstall-the-latest-cmake-version

----------------- BEGIN imx307_debug.py --------------------

import cv2

def run_once():

cap = cv2.VideoCapture('/dev/video0', cv2.CAP_V4L)
# cap.set(cv2.CAP_PROP_FOURCC, cv2.VideoWriter.fourcc('M','J','P','G'))
cap.set(cv2.CAP_PROP_FOURCC, cv2.VideoWriter.fourcc('h','2','6','4'))
cap.set(cv2.CAP_PROP_FRAME_WIDTH, 1920)
cap.set(cv2.CAP_PROP_FRAME_HEIGHT, 1080)
cap.set(cv2.CAP_PROP_FPS, 30)

# 讀取 10 個 frames
for i in range(10):
    ret, frame = cap.read()

cap.release()

def main():
cap_count = 0
while True:
run_once()
print('-- %d --' % cap_count)
cap_count += 1

if name == 'main':
main()

----------------- END imx307_debug.py --------------------

coolmitch

重新把程式碼排版ㄧ下...

#! /usr/bin/python3
import cv2

def run_once():

    cap = cv2.VideoCapture('/dev/video0', cv2.CAP_V4L)
    # cap.set(cv2.CAP_PROP_FOURCC, cv2.VideoWriter.fourcc('M','J','P','G'))
    cap.set(cv2.CAP_PROP_FOURCC, cv2.VideoWriter.fourcc('h','2','6','4'))
    cap.set(cv2.CAP_PROP_FRAME_WIDTH, 1920)
    cap.set(cv2.CAP_PROP_FRAME_HEIGHT, 1080)
    cap.set(cv2.CAP_PROP_FPS, 30)

    # 讀取 10 個 frames
    for i in range(10):
        ret, frame = cap.read()

    cap.release()

def main():
    cap_count = 0
    while True:
        run_once()
        print('-- %d --' % cap_count)
        cap_count += 1

if __name__ == '__main__':
    main()

veye_xumm

@coolmitch
请问你的cmake版本是？
我的是3.10.2

veye_xumm

@coolmitch
我更新了一下cmake，还是编译不过。
anyway，这事先放一放。
我现在改了一个版本的固件，用ffmpeg循环测试的方法，测试到6000+次数，还是稳定的。
请你也升级并老化测试一下：

下载链接：
https://www.mediafire.com/file/nnysng0map7jnf0/dimaging_upgrade.bin/file

升级方法：
http://wiki.veye.cc/index.php/USB升级固件方法

coolmitch

@veye_xumm
cmake --version
cmake version 3.10.2

CMake suite maintained and supported by Kitware (kitware.com/cmake).
我的也是 3.10.2
所以會不會是有什麼 dependent lib 沒有安裝完全？

coolmitch

@veye_xumm
升級後，開機看到這個
[ 48.421580] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 2: -32 (exp. 2).
[ 53.659534] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 2: -32 (exp. 2).
[ 53.672858] uvcvideo: Failed to query (GET_CUR) UVC control 11 on unit 2: -32 (exp. 1).
[ 53.681295] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 2: -32 (exp. 2).
[ 89.889940] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 2: -32 (exp. 2).
[ 410.317273] uvcvideo: Failed to resubmit video URB (-1).

不過我還是讓他去跑著測試了...
今晚先用 python3 的程式跑跑看...

veye_xumm

@coolmitch
我这边老化一夜，已经运行38000+次数，现在还是稳定的。期待你的结果。

coolmitch

@veye_xumm 我昨晚也跑了 22000+ 次，這樣應該就過了。所以是什麼原因造成的？

veye_xumm

@coolmitch
应该是我这边程序在处理close的时候，对资源的释放上有逻辑不完善的地方。希望你后面也继续测试观察吧。嵌入式端控制frequency的问题，我再研究一下。

coolmitch

@veye_xumm 瞭解。昨晚的還繼續在跑。我今天會做另一個測試站雙重測試。uvccamera 的參數看有沒有辦法讓有支援的都給出來，這樣在 linux 這邊會比較好處理（之前用 python 的那個 fourcc 的處理方式，因為沒有完整 uvc 的參數，搞了很久才找到那個怪方法...）

veye_xumm

@coolmitch
这个涉及到的改动太大了。暂时做不了所有参数都支持。现在我们只能是把摄像头默认参数调到最好。
另外就是你说的frequency hz设置的问题，需要解决一下。

coolmitch

@veye_xumm
對了，在 CS-USB-IMX307 新版韌體更新後，插入主機時會出現以下訊息，請問那些 Failed to query (GET_DEF) UVC control ... 是否就是 driver 要去讀取 uvccamera 參數時讀不到的錯誤？

[66391.767449] usb 1-2.4: new high-speed USB device number 5 using tegra-xusb
[66391.788802] usb 1-2.4: New USB device found, idVendor=12d1, idProduct=4321
[66391.788807] usb 1-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[66391.788810] usb 1-2.4: Product: CS-USB-IMX307
[66391.788813] usb 1-2.4: Manufacturer: Tianjin Zhonganyijia
[66391.788815] usb 1-2.4: SerialNumber: 2021-04-29-v1.5
[66391.790104] uvcvideo: Found UVC 1.10 device CS-USB-IMX307 (12d1:4321)
[66391.791116] uvcvideo 1-2.4:1.0: Entity type for entity Processing 2 was not initialized!
[66391.799329] uvcvideo 1-2.4:1.0: Entity type for entity Extension 10 was not initialized!
[66391.807507] uvcvideo 1-2.4:1.0: Entity type for entity Camera 1 was not initialized!
[66391.815533] input: CS-USB-IMX307 as /devices/70090000.xusb/usb1/1-2/1-2.4/1-2.4:1.0/input/input3
[66391.860569] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 2: -32 (exp. 2).
[66391.868750] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 2: -32 (exp. 2).
[66391.876889] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 2: -32 (exp. 2).
[66391.885043] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 2: -32 (exp. 2).
[66391.893245] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 2: -32 (exp. 2).
[66391.901418] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 2: -32 (exp. 2).
[66391.909611] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 2: -32 (exp. 2).
[66391.917744] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 2: -32 (exp. 2).
[66391.925863] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 2: -32 (exp. 2).
[66391.933954] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 2: -32 (exp. 2).
[66391.942076] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 2: -32 (exp. 2).
[66391.950219] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 2: -32 (exp. 2).
[66391.958366] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 2: -32 (exp. 2).
[66391.966488] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 2: -32 (exp. 2).
[66391.974603] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 2: -32 (exp. 2).
[66391.982734] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 2: -32 (exp. 2).
[66391.990897] uvcvideo: Failed to query (GET_DEF) UVC control 4 on unit 2: -32 (exp. 2).
[66391.999007] uvcvideo: Failed to query (GET_DEF) UVC control 4 on unit 2: -32 (exp. 2).
[66392.007219] uvcvideo: Failed to query (GET_DEF) UVC control 4 on unit 2: -32 (exp. 2).
[66392.015352] uvcvideo: Failed to query (GET_DEF) UVC control 4 on unit 2: -32 (exp. 2).
[66392.023488] uvcvideo: Failed to query (GET_DEF) UVC control 4 on unit 2: -32 (exp. 2).
[66392.031630] uvcvideo: Failed to query (GET_DEF) UVC control 4 on unit 2: -32 (exp. 2).
[66392.039743] uvcvideo: Failed to query (GET_DEF) UVC control 4 on unit 2: -32 (exp. 2).
[66392.047865] uvcvideo: Failed to query (GET_DEF) UVC control 4 on unit 2: -32 (exp. 2).
[66392.056021] uvcvideo: Failed to query (GET_DEF) UVC control 4 on unit 2: -32 (exp. 2).
[66392.064287] uvcvideo: Failed to query (GET_CUR) UVC control 11 on unit 2: -32 (exp. 1).
[66392.072494] uvcvideo: Failed to query (GET_CUR) UVC control 11 on unit 2: -32 (exp. 1).
[66392.080699] uvcvideo: Failed to query (GET_CUR) UVC control 11 on unit 2: -32 (exp. 1).
[66392.088904] uvcvideo: Failed to query (GET_CUR) UVC control 11 on unit 2: -32 (exp. 1).
[66392.097111] uvcvideo: Failed to query (GET_CUR) UVC control 11 on unit 2: -32 (exp. 1).
[66392.105311] uvcvideo: Failed to query (GET_CUR) UVC control 11 on unit 2: -32 (exp. 1).
[66392.113525] uvcvideo: Failed to query (GET_CUR) UVC control 11 on unit 2: -32 (exp. 1).
[66392.121728] uvcvideo: Failed to query (GET_CUR) UVC control 11 on unit 2: -32 (exp. 1).
[66392.129935] uvcvideo: Failed to query (GET_CUR) UVC control 11 on unit 2: -32 (exp. 1).
[66392.138162] uvcvideo: Failed to query (GET_CUR) UVC control 11 on unit 2: -32 (exp. 1).
[66392.146380] uvcvideo: Failed to query (GET_DEF) UVC control 8 on unit 2: -32 (exp. 2).
[66392.154495] uvcvideo: Failed to query (GET_DEF) UVC control 8 on unit 2: -32 (exp. 2).
[66392.162626] uvcvideo: Failed to query (GET_DEF) UVC control 8 on unit 2: -32 (exp. 2).
[66392.170738] uvcvideo: Failed to query (GET_DEF) UVC control 1 on unit 2: -32 (exp. 2).
[66392.178855] uvcvideo: Failed to query (GET_DEF) UVC control 1 on unit 2: -32 (exp. 2).
[66392.186981] uvcvideo: Failed to query (GET_DEF) UVC control 1 on unit 2: -32 (exp. 2).

veye_xumm

@coolmitch
这个就是对于uvc参数支持不完善所体现出来的。

veye_xumm

@coolmitch
我查了一下 powerhz 这个选项，应该是UVC control 5，这个是支持的。
至于为何v4l2-ctl报错，暂时还不清楚。

coolmitch

不好的消息
執行 29525 次之後，再度發生一樣的狀況。不過至少不是 6000 次斷。

veye_xumm

@coolmitch
(⊙﹏⊙)
建议你暂时先设计一个机制，遇到问题时，或者定时，将jetson重启一下。
我觉得jetson重启的时候，usb接口会有断电重新上电的操作（需要验证），可以将系统整个从错误状态中恢复。

coolmitch

@veye_xumm 我可以試試看每天夜間定時重啟看看。但已知的狀況是，當 disconnect 發生時，重啟 jetson nano 是無效的（不斷電）。目前的硬體機制沒辦法讓他斷電重啟。

coolmitch

@veye_xumm 已確認下 reboot 指令時 usb 不會斷電。

veye_xumm

@coolmitch
你好，不知你的jetson nano是哪个版本。
我查了一下官方的nano devkit的底板原理图，以及nvidia的论坛，这个usb的power应该是可控的。
以下帖子作为参考。
https://forums.developer.nvidia.com/t/usb-power-control/79037