I have not had issues since then (it has been about 1 hour and 30 minutes since the issue occured, and they are both running properly now). This may be annecdotal, but after this output I restarted both pipelines and Device 1 stayed working after that, while for Device 2 I had to restart nvargus-daemon and restart the pipeline an additional time (2 total restarts) before it stayed working. Notice that Device 2 has a lot more errors in /var/log/syslog than does Device 1. Here are log files ( /var/log/syslog and output from my DeepStream program) from two different devices that have the same error. Please let me know if there is anything you can do to help me. Note that I am running the exact same DeepStream pipeline on 4 different nano devices and at least 2 of them have this error (while the others have it, but far less frequently, for some reason) The device shows up when running v4l2-ctl -list-devices without fail, but I consistently get this error. The proposed “solution” is no solution at all. If you really want me to start a new post instead of resolving this one, I can do that. I have the exact same issue as those who posted above. dvs/git/dirty/git-master_linux/multimedia/nvgstreamer/gst-nvarguscamera/gstnvarguscamerasrc.cpp, execute:551 Failed to create CameraProvider (Argus) Error Timeout: Cannot create camera provider (in src/rpc/socket/client/SocketClientDispatch.cpp, function createCameraProvider(), line 102)Įrror generated. ![]() ![]() (Argus) Error Timeout: (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function openSocketConnection(), line 215) Pipeline is live and does not need PREROLL … Vi-output, imx477 6-001a gst-launch-1.0 nvarguscamerasrc sensor-id=$SENSOR_ID ! “video/x-raw(memory:NVMM),width=1920,height=1080,framerate=$FRAMERATE/1” ! nvvidconv ! nvoverlaysink ![]() This my second camera and i still cant view v4l2-ctl -list-devices
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |