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.

OMAP4 camera interface - Difference between BLAZE and Pandabord platform

Hello,

    I have BLAZE platform and a PandBoard platform. Both have OMAP4.

    On both platforms, I am able to successfully load sys and app images and start syslink_deamon.

   I am successfully able to use omx_camera on BLAZE platform to capture video from both, front and back, cameras, using gst-omx.

   On pandaboard, I installed camera on the camera connector.

   Question I have is :

       -  Can I run gst-omx pipeline that I successfully used on BLAZE platform, on Pandaboard.to capture from camera?

       -  Can I use  omx on pandabord to capture video from camera that is connected to camera interface socket.

       -  Can some send me an get-omx pipeline for recording video from camera that s connected to camera interface socket on pandaboard.

 

Thank you for helping me with this.

  • Marc,

    Let's start with the basic question: Which software release ?

    Since you are talking of syslink_daemon and gst-omx, it suggests that you are using an Ubuntu distribution (not Android), either an old GLP1.4.x release (based on maverick and kernel 2.6.35) or GLP1.5.x (based on oneiric and kernel 3.2). At that time, Panda camera was not supported.

    In any case, you should migrate to the latest GLP1.6.x based on kernel 3.4 and a new rpmsg architecture that replaces syslink. Such release do support both Blaze and Panda cameras.

    Here is an example of video record: gst-launch-0.10 -e omx_camera num-buffers=240 mode=1 name=cam cam.src ! "video/x-raw-yuv, format=(fourcc)NV12, width=1280, height=720, framerate=24/1" ! queue ! ducatih264enc ! queue ! h264parse ! avimux ! filesink location=foo.avi

    Regards,
    -- Olivier

  • Thankyou for you response.

     

        Where can I acess GLP1.6.x? The link above does not work.

        Can I get pinout description for J8 (primary camera) on blaze platform?

     

    Thank you

     

  • Marc,

    Sorry, wrong link. Let me elaborate.

    * For TI customers, GLP1.6.x can be accessed via TI CDDS portal. It includes a Ducati firmware with OMX camera.

    * For Pandaboard community, the equivalent can be accessed on Launchpad (https://launchpad.net/~tiomap-dev/+archive/release). However the public Ducati firmware does not contain OMX camera.

    Apparently you are already using an old GLP release, so you should have the necessary agreements in place and have access to CDDS. For further details, please contact your TI representative.

    Same thing for the Blaze schematics.

    Regards,
    -- Olivier

  • there are some cameras that work on pandaboard using V4L.  Why is that?  

    not all MIPI  interface cameras work using V4L? why is that?

    trying to understand. What do I need for camera with MIPI interface to work on pandaboard or blaze board?

  • "not all MIPI  interface cameras work using V4L" This is not correct.

    V4L and OMX are software frameworks. Both of them are capable of supporting all parallel and MIPI sensors. The only difference is that OMX is user space API and V4L is kernel space ioctls. In TI releases, there is support for some sensors in our proprietary source code (called Ducati) through OMX. The number of sensors supported is bery small. If you want to have a sensor other than these, you have 2 options

    1. Write your own driver in Ducati

    2. Use V4L driver available in opensource and integrate them with OMAP V4L driver

  • I needed to connect different camera to Blaze's primary camera connector. However the primary cable connector (J8) is 24 pin and other camera has 30 pin connector(some pins are probably not used). How can I connect this camera to blaze? are there any abapters available?

  • I beleive, you are saying that, propritery TI software libraries are not needed for video capture on pandaboard or blaze platform. Is this correct?

    I understand that V4L2 kernel will capture imagems from some omnivision camera, why is it that cannot capture from other cameras.

    what is the difference between blaze platform primar camera interface and pandaboard camera interface? 

    if I can capture images from blaze platforms pri and sec camera, should I not be able to capture images from any camera connected to pandaboard?

    I do not understand why I can capture images from omnivision camera on pandaboard but not from other cameras.

    Will utilizing GLP 1.6.x allow me to capture images on pandaboard as well as blaze platform ?

    thank you

  • >>I beleive, you are saying that, propritery TI software libraries are not needed for video capture on pandaboard or blaze platform. Is this correct?

    [Mayank] I am not saying this. I am saying that proprietary libraries support only a fixed set of sensors.

    >>what is the difference between blaze platform primar camera interface and pandaboard camera interface?

    [Mayank] There is a difference in how sensor is interfaced to OMAP. I2C bus, GPIOs are different. However for sensors supported, there are proprietary drivers available for both Panda and Blaze. You need to use the right software release.

     

    >>if I can capture images from blaze platforms pri and sec camera, should I not be able to capture images from any camera connected to pandaboard?

    [Mayank] Blaze primary camera is IMX060 which is not available on Panda. Blaze secondary camera is OV5650 which is available on Panda as a primary sensor through an external expansion board.

    >> I do not understand why I can capture images from omnivision camera on pandaboard but not from other cameras.

    [Mayank]  You can not assume that "any" camera will work without modifying the software. Camera sensor needs a device driver.

    >>Will utilizing GLP 1.6.x allow me to capture images on pandaboard as well as blaze platform ?

    [Mayank] It will. GLP1.6.x release is available for both boards. You need to make sure that you use the correct software for the board you are using.