Tool/software:
Hi,
May I ask what causes this log to appear.
"Failed to drain DMA. Next frame might be bogus"
regards,
cesar
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Tool/software:
Hi,
May I ask what causes this log to appear.
"Failed to drain DMA. Next frame might be bogus"
regards,
cesar
Hi Cesar,
From which CSIRX driver are you seeing this issue?
Regards,
Brijesh
Hi Brijesh,
Sometimes these logs are flashed after the system starts up
regards,
cesar
Hi cesar,
When do you see this issue and which SDK release are you using? Typically this error should not come while running the V4L2 example, so are you seeing this error when stopping the driver? Can you try on latest release?
Regards,
Brijesh
Hi Brijesh,
sdk0900;
example app cmd:
gst-launch-1.0 -v \
v4l2src device=/dev/video2 io-mode=4 do-timestamp=true ! queue max-size-buffers=240 max-size-time=0 ! \
video/x-raw,format=UYVY,width=1920,height=1080,framerate=15/1,interlace-mode=progressive,colorimetry=bt709 ! \
identity sync=true single-segment=true ! tiovxdlcolorconvert ! queue max-size-buffers=240 max-size-time=0 ! \
video/x-raw,format=NV12,width=1920,height=1080,framerate=15/1,interlace-mode=progressive,colorimetry=bt709 ! \
videorate ! video/x-raw,framerate=15/1 ! \
v4l2h264enc extra-controls="controls, frame_level_rate_control_enable=(int)1, video_bitrate=(int)5000000, video_gop_size=(int)15;" ! \
h264parse ! queue max-size-buffers=240 max-size-time=0 ! filesink sync=true location=/mnt/output/output${new_number}_2M_right.h264 &
Under what circumstances will drain dma occur.
regards,
cesar
Hi Cesar,
Could you share which camera you are using as your v4l2src device? Does this issue occur every time you run the pipeline? We highly recommend you try this on the latest SDK release.
Thank you,
Fabiana