On 2/14/12, Fabio Estevam <festevam@xxxxxxxxx> wrote: > Then I start the following Gstreamer pipeline: > > $ gst-launch v4l2src ! fbdevsink > Setting pipeline to PAUSED ... > mx3-camera mx3-camera.0: MX3 Camera driver attached to camera 0 > Pipeline is live and does not need PREROLL ... > WARNING: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Could not > get > parameters on device '/dev/video0' > Additional debug info: > v4l2src_calls.c(225): gst_v4l2src_set_capture (): > /GstPipeline:pipeline0/GstV4l2 > Src:v4l2src0: > system error: Invalid argument > Setting pipeline to PLAYING ... > New clock: GstSystemClock > > , and I start to see the captured image in the LCD, but after about > 10-15 seconds I get: > > > dma dma0chan7: NFB4EOF on channel 7, ready 0, 0, cur 80 Ok, looks like if I adjust the resolution and framerate properly I no longer get this error. With this pipeline I don`t get this error: gst-launch -v v4l2src device=/dev/video0 ! video/x-raw-yuv,width=320,height=240,framerate=25/1 ! ffmpegcolorspace ! fbdevsink Now this leads to a new issue: the board resets after about 3 minutes. Then I started to investigate if this issue was in the capture side or in the display side: Capture only pipeline: gst-launch -v v4l2src ! video/x-raw-yuv,width=320,height=240, framerate=25/1 ! fakesink (works fine) Display only pipeline: gst-launch videotestsrc ! fbdevsink (resets the system after ~ 3 minutes) I will start investigating this and any comments/suggestions are welcome. Thanks, Fabio Estevam -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
