Forums

Integrate a 1.3 Mega-pixel Camera Board

  • Hi all,

     

    I purchased a leopardboard 355 and a 1.3 Mega-pixel Camera Board. after lot of tries, I am a little surprised regarding the integration and work of this kind of camera.

    What I think is only VGA camera is supported by the SDK, right ?

    Does anyone already use this camera, if yes how ?

    When I check the source code, what I see is the vpfe is set for MT9V113 which is the VGA model and only this model, does anyone already modify this code for integrate another kind of camera ?

     

    Thanks in advance for your replies and sorry for my non fluent english. I am french.

     

     

     
  • i think no camera is useable except VGA unless you pay 500-600 USD more for drivers... they just seem to have binary demo for videos but of course that's not useable for your own project, at least it's what i understood from the little info i could decipher from the forums. no V4L2 except for VGA.

  • Currently only VGA and 5M drivers are available.

    Other driver will be available.

    Camera driver implementation requires unique knowledges about sensor and DM3xx VPFE.

    Leopard Imaging people are the people understand them.

    They had been too busy with their own business.

    I heard they are trying to open drivers for other camera boards now.

    Some will be shown soon.

  • Nara Won

    Currently only VGA and 5M drivers are available.

    according to this: http://designsomething.org/leopardboard/f/33/t/287.aspx

     

    it didn't look like the driver was available. there's a paid package for the driver, unless paying 4-600 USD is what you mean by available of course. What i mean in my message is that it appears only the VGA driver is "freely" available (= you buy only camera and board)

  • Currently only VGA and 5M have drivers with source code, all other resolution camera boards don't have driver yet. we would like to work together with community members to have all other resolutions driver working, of course, we are working on that as well, but it takes time.

    - Bill

  • Bill, in the thread I linked, you wrote that you don't know if the camera works with UVC drivers. I'm not sure what driver the 5MP camera has then (?)

    In short, as this was unreplied, does it works with V4L2 ?

    Or even more simple, can you just run that:

    gst-launch v4l2src ! fdsink > video.mp4

    with no additional paid software on the 5MP camera and it works?

     

    thanks

  • The 5M camera has linux driver based on V4l2.  The RidgeRun SDK integrated this driver. The driver in the ECDK/EUCDK is user mode driver, which is a new written one different from the one in RR SDK.

    I wanted to bring up one special thing of the 5M camera. It is a non-SOC sensor, meaning the image from the driver is RAW data, it needs a lot of image processing to make it good quality. The MT9V034 WVGA sensor is a non-SOC sensor as well. All other camera boards are using SOC sensor. That is why the VGA give you decent image without any processing.

    I never try gstreamer, not sure if gst-launch v4l2src ! fdsink > video.mp4 will give your video stream or not. But I am sure even it outputs image, the quality won't be good since it is RAW.

  • Leon Luo

    The 5M camera has linux driver based on V4l2.  The RidgeRun SDK integrated this driver. The driver in the ECDK/EUCDK is user mode driver, which is a new written one different from the one in RR SDK.

    I wanted to bring up one special thing of the 5M camera. It is a non-SOC sensor, meaning the image from the driver is RAW data, it needs a lot of image processing to make it good quality. The MT9V034 WVGA sensor is a non-SOC sensor as well. All other camera boards are using SOC sensor. That is why the VGA give you decent image without any processing.

    I never try gstreamer, not sure if gst-launch v4l2src ! fdsink > video.mp4 will give your video stream or not. But I am sure even it outputs image, the quality won't be good since it is RAW.

     

    Ok, thanks for the reply. I put .mp4 but i just meant > file ;) it would save as yuv or something like that .. i guess i'll look in the driver code i hope they do some preprocessing of the image

    also thanks for the precision on the non-soc sensor. finally got the questions answered ! :)