• RELEVANCY SCORE 3.72

    DB:3.72:Ov5640 And Ov5642 Cameras On Imx6 9x






    Hi all,

    We are trying to use OV5640 (MIPI interface) and OV5642 in our custom iMX6 based board as rear camera and as a front camera respectively. Are these two cameras capable of coexisting on a single board based on iMX6 processor?

    Thanks for your inputs,

    Vasan

    DB:3.72:Ov5640 And Ov5642 Cameras On Imx6 9x


    Hi All,

    I had a go at modifying as per Konstantyn suggestion the the icu_csi_enc.c file from my LTIB BSP and managed to get a version that can now run both cameras concurrently. Did not attempt to midify any other files.

    I have attached the patch that shows the mods.

    I am using gstreamer to capture the data.

    There seems to be a slight issue though. I am using two LVDS screens with resolution 768x1024 and when I capture with both camera I am getting some sort of flicker. I wonder if this is a performance related issue. I am using SabreSD board with imx6Q processor, two on board camera (MIPI and CSI)

    Makis

  • RELEVANCY SCORE 3.40

    DB:3.40:I.Mx6 Camera Interface Hardware zj






    Hi guys

    we develop a board with imx6 solo with camera interface.

    1. Should I use MIPI or parallel interface

    2. Should I need external components (logic level converters, etc ) to connect imx6 camera sensor interface to cameras like below

    2PCS LOT Phone camera module OV5640+free shipping-in Integrated Circuits from Electronic Components Supplies on Aliexp

    OV5640 low cost 5M pixel long golden finger flex micro camera module 24pin auto focus function-in Other Electronic Comp

    Af ov5640 automatic webcam module 500 pixels mobile phone webcam module-inOther Electronic Components from Electronic Co

    DB:3.40:I.Mx6 Camera Interface Hardware zj


    Hi erdem

    please look at Freescale reference board schematic, it shows connections

    for both MIPI and parallel interfaces

    i.MX6_SABRE_SDP_DESIGNFILES

    Best regards

    chip

    -----------------------------------------------------------------------------------------------------------------------

    Note: If this post answers your question, please click the Correct Answer button. Thank you!

    -----------------------------------------------------------------------------------------------------------------------

  • RELEVANCY SCORE 3.37

    DB:3.37:Connect Ov5640 Camera Module To Sabre Board. kd






    Hi all,

    I want to connect an OV5640 Camera Module to the Sabre Board. The current camera module in Sabre is OV4642. It is similar to OV5640. there are both ov5640.c and ov5642.c in the kernel_imx/drivers/media/video/mxc/capture folder.

    Can anyone tell me how to config the Sabre board and make OV5640 work, instead of OV5640.

    Thanks all.

    DB:3.37:Connect Ov5640 Camera Module To Sabre Board. kd


    Please contact your support window and see whether he can help you to find camera sensors.

  • RELEVANCY SCORE 3.25

    DB:3.25:Imx6 Gstreamer Mfw_V4lsrc From Ov5640 Camera Fails When Matroskamux Debug At Level 5 jz



    I have a running gstreamer pipeline running on Wandboard iMx6 solo below

    gst-launch --gst-debug=2 mfw_v4lsrc capture-mode=4 ! queue max-size-buffers=1 ! vpuenc codec=6 bitrate= 2097152 ! queue ! mux. alsasrc ! mfw_mp3encoder bitrate=64 optmod=0 channels=1 ! queue ! mux. matroskamux name=mux ! filesink location=test.mkv

    When I turn up the traces for matroskamux to 4, it fails. It seems to fail at init or not getting any data from the sensor.

    gst-launch --gst-debug=*:2,matroskamux:4 mfw_v4lsrc capture-mode=4 ! queue max-size-buffers=1 ! vpuenc codec=6 bitrate= 2097152 ! queue ! mux. alsasrc ! mfw_mp3encoder bitrate=64 optmod=0 channels=1 ! queue ! mux. matroskamux name=mux ! filesink location=dtest.mkv

    [ 5790.920024] ERROR: v4l2 capture: mxc_v4l_dqueue timeout enc_counter 0

    0:00:11.831708335 2094 0x1473b0 ERROR mfw_v4lsrc mfw_gst_v4lsrc.c:1215:mfw_gst_v4lsrc_buffer_new: V4L_SRC: VIDIOC_DQBUF failed.

    0:00:11.832200335 2094 0x1473b0 WARN basesrc /home/norman/dev_branch_sep16/fsl-community-bsp/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/gstreamer/0.10.36-r2/gstreamer-0.10.36/libs/gst/base/gstbasesrc.c:2625:gst_base_src_loop:video_src error: Internal data flow error.

    0:00:11.832366001 2094 0x1473b0 WARN basesrc /home/norman/dev_branch_sep16/fsl-community-bsp/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/gstreamer/0.10.36-r2/gstreamer-0.10.36/libs/gst/base/gstbasesrc.c:2625:gst_base_src_loop:video_src error: streaming task paused, reason error (-5)

    This seems to be some timing issue that is troubling. I appreciate any help ideas to explain this.

    Thanks,

    Norman

    DB:3.25:Imx6 Gstreamer Mfw_V4lsrc From Ov5640 Camera Fails When Matroskamux Debug At Level 5 jz


    I have a running gstreamer pipeline running on Wandboard iMx6 solo below

    gst-launch --gst-debug=2 mfw_v4lsrc capture-mode=4 ! queue max-size-buffers=1 ! vpuenc codec=6 bitrate= 2097152 ! queue ! mux. alsasrc ! mfw_mp3encoder bitrate=64 optmod=0 channels=1 ! queue ! mux. matroskamux name=mux ! filesink location=test.mkv

    When I turn up the traces for matroskamux to 4, it fails. It seems to fail at init or not getting any data from the sensor.

    gst-launch --gst-debug=*:2,matroskamux:4 mfw_v4lsrc capture-mode=4 ! queue max-size-buffers=1 ! vpuenc codec=6 bitrate= 2097152 ! queue ! mux. alsasrc ! mfw_mp3encoder bitrate=64 optmod=0 channels=1 ! queue ! mux. matroskamux name=mux ! filesink location=dtest.mkv

    [ 5790.920024] ERROR: v4l2 capture: mxc_v4l_dqueue timeout enc_counter 0

    0:00:11.831708335 2094 0x1473b0 ERROR mfw_v4lsrc mfw_gst_v4lsrc.c:1215:mfw_gst_v4lsrc_buffer_new: V4L_SRC: VIDIOC_DQBUF failed.

    0:00:11.832200335 2094 0x1473b0 WARN basesrc /home/norman/dev_branch_sep16/fsl-community-bsp/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/gstreamer/0.10.36-r2/gstreamer-0.10.36/libs/gst/base/gstbasesrc.c:2625:gst_base_src_loop:video_src error: Internal data flow error.

    0:00:11.832366001 2094 0x1473b0 WARN basesrc /home/norman/dev_branch_sep16/fsl-community-bsp/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/gstreamer/0.10.36-r2/gstreamer-0.10.36/libs/gst/base/gstbasesrc.c:2625:gst_base_src_loop:video_src error: streaming task paused, reason error (-5)

    This seems to be some timing issue that is troubling. I appreciate any help ideas to explain this.

    Thanks,

    Norman

  • RELEVANCY SCORE 3.25

    DB:3.25:Ethernet Link Issue In Imx6 Based Design 91



    Hi Guys,

    I have iMX6 based Board in which Whenever i power on the board and plug in ethernet cable, the ethernet link is not getting detected.

    Every time i plug in the ethernet cable i need to reset the board and then ethernet starts working. Can any one help to solve this problem?

    DB:3.25:Ethernet Link Issue In Imx6 Based Design 91


    Hi Guys,

    I have iMX6 based Board in which Whenever i power on the board and plug in ethernet cable, the ethernet link is not getting detected.

    Every time i plug in the ethernet cable i need to reset the board and then ethernet starts working. Can any one help to solve this problem?

  • RELEVANCY SCORE 3.15

    DB:3.15:Camera On Jellybean 7d



    Hi,

    I want to connect the USB camera to Jellybean release on freescale iMX6 SABRE SD hardware.

    I could not locate the Camera application on for jellybean..

    How to enable the default camera application on freescale jellybean version?

    -John

    DB:3.15:Camera On Jellybean 7d


    Hi,

    I want to connect the USB camera to Jellybean release on freescale iMX6 SABRE SD hardware.

    I could not locate the Camera application on for jellybean..

    How to enable the default camera application on freescale jellybean version?

    -John

  • RELEVANCY SCORE 3.13

    DB:3.13:Add Ov2659 Camera Support In Mx53_Smd Tablet sz



    SABRE tablet uses ov5642 camera module. In kernel configuration support for ov2640, ov3640, ov5640 and ov5642 are present.

    I need ov2659 support in my sabre tablet. How it can be accomplished?

    Rgds,

    Mathews

    DB:3.13:Add Ov2659 Camera Support In Mx53_Smd Tablet sz


    Hello,Mats1z,

    Yes, in linux drivers path, there is no ov2659 driver, you should get it from OV company or manufactrue that supply vo2659 module to you , or you will have to program one according to datasheet and by refering to other ov sensor's driver.

    Regards,

    Weidong

  • RELEVANCY SCORE 3.12

    DB:3.12:I.Mx535 Qsb Jpeg Image Errors 7f



    hi all,

    I am working in i.mx535qsb board, in that i want to capture the jpeg image format, when i captured the image the header of the image is not coming, for your convenience, i have attached the sample image also, can any one help me,

    NOTE:

    Camera sensor = ov5640

    Board = i.mx535 qsb

    Resolution = 1280x720

    thanks,

    shan

    DB:3.12:I.Mx535 Qsb Jpeg Image Errors 7f


    I have posted as new discussion below is the link

    Jpeg image decoding using VPU on iMX53 running Android 2.3

    Thank you,

  • RELEVANCY SCORE 3.09

    DB:3.09:Only One Camera For Android 4.4.2 Bsp Using Ov5640 Module 1p



    As title, my customer board has refer to sabresd mother board, and I use only one ov5640 module as rear camera via mipi and i2c,

    my i2c bus has move to i2c0, so I only modify sabresd board file as follow:

    static struct i2c_board_info mxc_i2c0_board_info[] __initdata = {

    {

    I2C_BOARD_INFO("wm89**", 0x1a),

    },

    /* {

    I2C_BOARD_INFO("ov564x", 0x3c),

    .platform_data = (void *)camera_data,

    },*/

    {

    I2C_BOARD_INFO("mma8x5x", 0x1c),

    .irq = gpio_to_irq(SABRESD_ACCL_INT),

    .platform_data = (void *)mma8x5x_position,

    },

    {

    I2C_BOARD_INFO("ov5640_mipi", 0x3c),

    .platform_data = (void *)mipi_csi2_data,

    },

    };

    static struct i2c_board_info mxc_i2c1_board_info[] __initdata = {

    {

    I2C_BOARD_INFO("mxc_hdmi_i2c", 0x50),

    },

    /* {

    I2C_BOARD_INFO("ov5640_mipi", 0x3c),

    .platform_data = (void *)mipi_csi2_data,

    },

    {

    I2C_BOARD_INFO("egalax_ts", 0x4),

    .irq = gpio_to_irq(SABRESD_CAP_TCH_INT0),

    },*/

    /* {

    I2C_BOARD_INFO("max11801", 0x48),

    .platform_data = (void *)max11801_mode,

    .irq = gpio_to_irq(SABRESD_TS_INT),

    },*/

    };

    but I still can't connect this camera, I can dump ov5640 registers in rootfs using i2ctools, then I cat /dev/video1,

    it still shows read csi2 info fail.

    I miss something else that it must be modified?? please help me, thanks!

    DB:3.09:Only One Camera For Android 4.4.2 Bsp Using Ov5640 Module 1p


    Hi,

    As you can see in this discussion

    https://community.freescale.com/message/493807#493807

    the customer was able to mount the camera device with no problems. Please make sure you have the same modifications.

    Best Regards,

    Alejandro

  • RELEVANCY SCORE 3.03

    DB:3.03:Camera Ov5640 Could Not Preview On Android 4.3 a1



    hi, all

    i encountered a problem about camera ov5640.

    i checked the boot log. i found the following message.

    ------------------------------------------------------------------

    camera ov5640 is found

    mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video16

    mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video17

    ------------------------------------------------------------------

    it seems that the driver is OK.

    but when I open the camera APP in android, it display nothing on LVDS panel and it can't preview.

    i found the following message in logcat

    ------------------------------------------------------------------

    E/FslCameraHAL( 2208): VIDIOC_STREAMON failed: Operation not permitted

    E/FslCameraHAL( 2208): Couldn't start preview for DeviceAdapter

    E/FslCameraHAL( 2208): error start stream -1

    ---------------------------------------------------------------------

    and I have checked the following waveform
    1)the MCLK pin outputs 24M waveform
    2)the HSYNC, VSYNC output square wave
    3) CSI0_DAT12~CSI0_DAT19 output waveform

    by the way , my resolution of lvds panel is 1024*600, and there is not 1024*600 mode in ov5640_mode_info_data of ov5640 driver

    is this a root cause?

    DB:3.03:Camera Ov5640 Could Not Preview On Android 4.3 a1


    hi SerchMX

    i have not added the other resolution in camera driver.

    And i checked the logcat again, i found configuration for ov5640 camera is 640*480 and

    it is recommended that media_profiles_480p.xml be used for any board's configuration which defines the that media_profiles_480p.xml be used for any board's configuration which defines the in Android_Frequently_Asked_Questions.pdf .

    so as you said, the resolution is not the problem.

  • RELEVANCY SCORE 3.02

    DB:3.02:Hi Guys , How Best I.Mx6 Variants Can Handle 4 Hd Ip Camera Videos Streaming ? 33



    Hello ,

    How best IMX6 variants can handle 4 high definition IP cameras Video streaming which will be connected through 4 port Ethernet switch to Ethernet port of IMX6 ?

    Thanks

    Anand

    DB:3.02:Hi Guys , How Best I.Mx6 Variants Can Handle 4 Hd Ip Camera Videos Streaming ? 33


    Hi

    Check following link for VPU performance.

    QA: MX6 VPU H.264 Dual Stream Encode Limits

    Thanks

    Saurabh

  • RELEVANCY SCORE 3.00

    DB:3.00:Ov5640 Camera Hal V2 Stability Issue On Imx6 Android4.2 And Android4.3 Bsp 3f



    We use OV sensor in Freescale IMX6D for camera application.

    It seems the BSP may be out of memory when we run any OpenCV camera application.

    We have 1G memory and the same OpenCV application runs OK on other Android 4.2/4.3 platforms.

    For Freescale BSP Android4,2/4.3, it will not say out of memory until 2~3 hours.

    If we change the BSP to HAL camera API version1, everything is OK.

    I am wondering if Freescale BSP camera API version2/HAP implementation has bug.

    Though BSP says out of memory, the GUI operation is still OK.

    Attach the whole log and test APKs.

    Thank

    Part of log for memory issue. (Whole log, please refer to the zip file attached).

    D/CameraBridge( 3083): mStretch value: 1.0

    D/JavaCameraView( 3083): Preview Frame received. Frame size: 460800

    I/OCVSample::Activity( 3083): onCameraFrame callback

    D/JavaCameraView( 3083): Preview Frame received. Frame size: 460800

    D/OBJECT_DETECTOR( 3083): DetectionBasedTracker::SeparateDetectionWork::workcycleObjectDetector() --- end handling imageSeparateDetecting

    I/OBJECT_DETECTOR( 3083): DetectionBasedTracker::SeparateDetectionWork::workcycleObjectDetector() --- objects num==0, t_ms=150.5023

    D/OBJECT_DETECTOR( 3083): DetectionBasedTracker::SeparateDetectionWork::workcycleObjectDetector() --- next step

    D/OBJECT_DETECTOR( 3083): DetectionBasedTracker::SeparateDetectionWork::workcycleObjectDetector() --- before waiting

    D/JavaCameraView( 3083): Preview Frame received. Frame size: 460800

    D/JavaCameraView( 3083): Preview Frame received. Frame size: 460800

    D/OBJECT_DETECTOR( 3083): DetectionBasedTracker::process: time from the previous call is 294.618333 ms

    D/OBJECT_DETECTOR( 3083): DetectionBasedTracker::SeparateDetectionWork::communicateWithDetectingThread: shouldCommunicateWithDetectingThread=1

    D/OBJECT_DETECTOR( 3083): DetectionBasedTracker::SeparateDetectionWork::communicateWithDetectingThread: lastBigDetectionDuration=294.090334 ms

    D/OBJECT_DETECTOR( 3083): DetectionBasedTracker::SeparateDetectionWork::communicateWithDetectingThread: shouldSendNewDataToWorkThread was 1, now it is 1, since time_from_previous_launch_in_ms=294.18, minDetectionPeriod=0

    D/OBJECT_DETECTOR( 3083): DetectionBasedTracker::SeparateDetectionWork::workcycleObjectDetector() --- after waiting

    D/OBJECT_DETECTOR( 3083): DetectionBasedTracker::SeparateDetectionWork::workcycleObjectDetector() --- start handling imageSeparateDetecting, img.size=640x480, img.data=0x0x631ef010

    D/OBJECT_DETECTOR( 3083): DetectionBasedTracker::SeparateDetectionWork::communicateWithDetectingThread: result: shouldHandleResult=1

    D/OBJECT_DETECTOR( 3083): DetectionBasedTracker::process: get _rectsWhereRegions were got from resultDetect

    I/OBJECT_DETECTOR( 3083): DetectionBasedTracker::process: tracked objects num==0

    D/OBJECT_DETECTOR( 3083): DetectionBasedTracker::process: rectsWhereRegions.size()=0

    D/OBJECT_DETECTOR( 3083): DetectionBasedTracker::process: detectedObjectsInRegions.size()=0

    D/OBJECT_DETECTOR( 3083): DetectionBasedTracker::updateTrackedObjects: N1=0, N2=0

    D/OBJECT_DETECTOR( 3083): DetectionBasedTracker::updateTrackedObjects: start second cycle

    D/CameraBridge( 3083): mStretch value: 1.0

    D/JavaCameraView( 3083): Preview Frame received. Frame size: 460800

    E/Camera2-Device( 2218): setStreamSlot: Unable to clone metadata buffer!

    I/OCVSample::Activity( 3083): onCameraFrame callback

    E/Camera2-StreamingProcessor( 2218): startStream: Camera 0: Unable to set preview request to start preview: Out of memory (-12)

    E/Camera2 ( 2218): startPreviewL: Camera 0: Unable to start streaming preview: Out of memory (-12)

    E/Camera2 ( 2218): setPreviewCallbackFlagL: Camera 0: Unable to refresh request in state STOPPED

    E/FslCameraHAL2( 2218): handleRequest: dequeue_frame failed

    D/OBJECT_DETECTOR( 3083): DetectionBasedTracker::SeparateDetectionWork::workcycleObjectDetector() --- end handling imageSeparateDetecting

    I/OBJECT_DETECTOR( 3083): DetectionBasedTracker::SeparateDetectionWork::workcycleObjectDetector() --- objects num==0, t_ms=135.7310

    D/OBJECT_DETECTOR( 3083): DetectionBasedTracker::SeparateDetectionWork::workcycleObjectDetector() --- next step

    D/OBJECT_DETECTOR( 3083): DetectionBasedTracker::SeparateDetectionWork::workcycleObjectDetector() --- before waiting

    E/FslCameraHAL2( 2218): handleRequest: dequeue_frame failed

    D/OBJECT_DETECTOR( 3083): DetectionBasedTracker::process: time from the previous call is 207.972667 ms

    D/OBJECT_DETECTOR( 3083): DetectionBasedTracker::SeparateDetectionWork::communicateWithDetectingThread: shouldCommunicateWithDetectingThread=1

    D/OBJECT_DETECTOR( 3083): DetectionBasedTracker::SeparateDetectionWork::communicateWithDetectingThread: lastBigDetectionDuration=207.215334 ms

    D/OBJECT_DETECTOR( 3083): DetectionBasedTracker::SeparateDetectionWork::communicateWithDetectingThread: shouldSendNewDataToWorkThread was 1, now it is 1, since time_from_previous_launch_in_ms=207.23, minDetectionPeriod=0

    D/OBJECT_DETECTOR( 3083): DetectionBasedTracker::SeparateDetectionWork::workcycleObjectDetector() --- after waiting

    D/OBJECT_DETECTOR( 3083): DetectionBasedTracker::SeparateDetectionWork::workcycleObjectDetector() --- start handling imageSeparateDetecting, img.size=640x480, img.data=0x0x631ef010

    E/FslCameraHAL2( 2218): handleRequest: dequeue_frame failed

    D/OBJECT_DETECTOR( 3083): DetectionBasedTracker::SeparateDetectionWork::communicateWithDetectingThread: result: shouldHandleResult=1

    D/OBJECT_DETECTOR( 3083): DetectionBasedTracker::process: get _rectsWhereRegions were got from resultDetect

    I/OBJECT_DETECTOR( 3083): DetectionBasedTracker::process: tracked objects num==0

    D/OBJECT_DETECTOR( 3083): DetectionBasedTracker::process: rectsWhereRegions.size()=0

    D/OBJECT_DETECTOR( 3083): DetectionBasedTracker::process: detectedObjectsInRegions.size()=0

    D/OBJECT_DETECTOR( 3083): DetectionBasedTracker::updateTrackedObjects: N1=0, N2=0

    D/OBJECT_DETECTOR( 3083): DetectionBasedTracker::updateTrackedObjects: start second cycle

    D/CameraBridge( 3083): mStretch value: 1.0

    E/FslCameraHAL2( 2218): handleRequest: dequeue_frame failed

    D/OBJECT_DETECTOR( 3083): DetectionBasedTracker::SeparateDetectionWork::workcycleObjectDetector() --- end handling imageSeparateDetecting

    I/OBJECT_DETECTOR( 3083): DetectionBasedTracker::SeparateDetectionWork::workcycleObjectDetector() --- objects num==0, t_ms=86.7770

    D/OBJECT_DETECTOR( 3083): DetectionBasedTracker::SeparateDetectionWork::workcycleObjectDetector() --- next step

    D/OBJECT_DETECTOR( 3083): DetectionBasedTracker::SeparateDetectionWork::workcycleObjectDetector() --- before waiting

    E/FslCameraHAL2( 2218): handleRequest: dequeue_frame failed

    E/FslCameraHAL2( 2218): handleRequest: dequeue_frame failed

    E/FslCameraHAL2( 2218): handleRequest: dequeue_frame failed

    E/FslCameraHAL2( 2218): handleRequest: dequeue_frame failed

    E/FslCameraHAL2( 2218): handleRequest: dequeue_frame failed

    E/FslCameraHAL2( 2218): handleRequest: dequeue_frame failed

    E/FslCameraHAL2( 2218): handleRequest: dequeue_frame failed

    E/FslCameraHAL2( 2218): handleRequest: dequeue_frame failed

    E/FslCameraHAL2( 2218): handleRequest: dequeue_frame failed

    E/FslCameraHAL2( 2218): handleRequest: dequeue_frame failed

    E/FslCameraHAL2( 2218): handleRequest: dequeue_frame failed

    E/FslCameraHAL2( 2218): handleRequest: dequeue_frame failed

    E/FslCameraHAL2( 2218): handleRequest: dequeue_frame failed

    E/FslCameraHAL2( 2218): handleRequest: dequeue_frame failed

    E/FslCameraHAL2( 2218): handleRequest: dequeue_frame failed

    E/FslCameraHAL2( 2218): handleRequest: dequeue_frame failed

  • RELEVANCY SCORE 3.00

    DB:3.00:Camera Modules For Sololite Evk 9a



    hi,

    Want to know the OV5642 Camera module tested by Freescale for MCIMX6SLEVK , and the OV5640 camera module for the SABRE board.

    Thanks

    --Pankaj Rana

    DB:3.00:Camera Modules For Sololite Evk 9a


    SergioSolis , please update on the previous query.

  • RELEVANCY SCORE 2.97

    DB:2.97:Imx6 Power Supply d1



    Hi, I want to check the status of the power supply for an IMX6 board. I am using the latest yocto dora version (as described http://variwiki.com/index.php?title=VAR-SOM-MX6_Yocto_GS_R4) and I want to use the power_supply class, which must be locaated in /sys/class/power_supply/AC. In my case the power_supply folder is empty. Do you have any hint for this issue? Thanks in advance.

    DB:2.97:Imx6 Power Supply d1


    Hi, I want to check the status of the power supply for an IMX6 board. I am using the latest yocto dora version (as described http://variwiki.com/index.php?title=VAR-SOM-MX6_Yocto_GS_R4) and I want to use the power_supply class, which must be locaated in /sys/class/power_supply/AC. In my case the power_supply folder is empty. Do you have any hint for this issue? Thanks in advance.

  • RELEVANCY SCORE 2.85

    DB:2.85:Ov5640 Not Working With Imx53 jp



    I working on a IMX53 board based on the IMX53-QSB HW and linaro-bsp(linux-2.6.35.3). I've connected OV5640 camera module on the CSI0 interface. The camera is not getting detected.

    Looking at the kernel boot log. I can see that the I2C transfer is not successful.

    I made a few modifications to the mx53_loco.c file and added a few lines(taken from mx53_smd.c) as shown below.

    static struct mxc_camera_platform_data camera_data = {

    //.analog_regulator = "DA9052_LDO7",

    //.core_regulator = "DA9052_LDO9",

    .mclk = 24000000,

    .csi = 0,

    };

    static struct i2c_board_info mxc_i2c0_board_info[] __initdata = {

    {

    .type = "mma8450",

    .addr = 0x1C,

    },

    {

    .type = "ov5640",

    .addr = 0x3C,

    .platform_data = (void *)camera_data,

    },

    };

    I don't know what is missing. I've attached my interface diagram and the kernel boot logs. Added extra I2C debug messages to the log.

    Can someone help me on this?

    DB:2.85:Ov5640 Not Working With Imx53 jp


    Hello,Varma,

    I2C3 on MX53QSB is pulled up to 3.3V High, I remember VDDIO of OV5640 should be 1.8V or 2.8V, if it's VDDIO=1.8v, CPU I2C3 can't communicate with ov5640 module. If it's VDDIO=2..8v, i2c2 should normally transmit data between CPU and OV5640 even if you don't use I2C level shifter.

    So please check VDDIO's voltage of OV5640 module.

    regards,

    Weidong

  • RELEVANCY SCORE 2.85

    DB:2.85:Ov5640 And Ov5642 Camera Modules For Sabre-Sdb Platform xk



    Hi All,

    Does anyone know where it is possible to buy OV5640 and OV5642 camera modules that plug in to the SABRE-SDB platform (modules that plug in to the FX12B-40P-0.4SV sockets on the board)?

    Many thanks and best regards

    DB:2.85:Ov5640 And Ov5642 Camera Modules For Sabre-Sdb Platform xk


    Hi Craig,

    I have buy OV5642 and OV5640 samples Through the module manufacturer.

    BR

    wod

  • RELEVANCY SCORE 2.82

    DB:2.82:Camera Images Rotated 90 Degrees 7x



    hello all,

    would like to ask some advice regarding an issue on ov5640_mipi rear camera.

    problem is that hw mounting is incorrect so i get pictures rotated 90 degrees.

    After reading imx6 cpu manual, i found out that IPU lib can do image rotation.

    My question is, can I use this library from camera hal to do the image rotation?

    Or do I just need to configure some setting in camera hal to do the job?

    Any advice are highly appreciated.

    thanks,

    john

    DB:2.82:Camera Images Rotated 90 Degrees 7x


    hello all,

    would like to ask some advice regarding an issue on ov5640_mipi rear camera.

    problem is that hw mounting is incorrect so i get pictures rotated 90 degrees.

    After reading imx6 cpu manual, i found out that IPU lib can do image rotation.

    My question is, can I use this library from camera hal to do the image rotation?

    Or do I just need to configure some setting in camera hal to do the job?

    Any advice are highly appreciated.

    thanks,

    john

  • RELEVANCY SCORE 2.81

    DB:2.81:Adv7180 On Imx6 Quad cz



    Hi everybody. I am trying to get the ADV7180 board to work with the imx6 quad board.

    However, when trying to capture data using mxc_v4l2_capture app I get some error:

    v4l2 capture: mxc_v4l_dqueue timeout enc_counter 0

    Looks like it does not get to see any data on the parallel data bus. I am not using HSYNC and VSYNC, just the 8 data pins for parallel video camera capture. I've been looking for related posts about my error and I see quite a few people experiencing this timeout issue that I get. Closest related issue to my problem seems to be at: https://community.freescale.com/docs/DOC-97981 but still I see that thread as closed and not much progress. Any pointers if this is somewhat related to EAV/SAV setup since I am not using HSYNC and VSYNC? Any pointers would be much appreciated.

    Thank you.

    DB:2.81:Adv7180 On Imx6 Quad cz


    Hi Rogerio,

    thanks for the input. I'll give it a try when I have the hardware fixed and get back with a response here.

    Thank you all for your support.

  • RELEVANCY SCORE 2.80

    DB:2.80:Mipi d9



    hi

    I connected my eCAM50IMX6 to Nitrogen6x board but I cant see its frames on the screen...

    I get the following errors:

    ***************

    mxc_v4l_open: Mxc Camera no sensor ipu0/csi0

    mxc_v4l_open: Mxc Camera no sensor ipu0/csi1

    mxc_v4l_open: Mxc Camera no sensor ipu1/csi1

    DISP3 BG ():mxc_v4l_open: Mxc Camera no sensor ipu0/csi0

    /dev/video16

    /dev/video17

    Failed to open /dev/video0: Resource temporarily unavailable

    *****************

    during the boot it also written that the ov5640 is not found

    but I also get the following lines during boot:

    mxc_mipi_csi2 21dc000.mipi_csi: i.MX MIPI CSI2 driver probed

    mxc_mipi_csi2 21dc000.mipi_csi: i.MX MIPI CSI2 dphy version is 0x3130302a

    MIPI CSI2 driver module loaded

    MIPI DSI driver module loaded

    can anyone please explain me what is the problem.. I mean I have the hardware plugged in and also the kernel loaded the driver so what else I need?

    Regards

    DB:2.80:Mipi d9


    Hi,

    There is a function called ov5640_read_reg in ov5640_mipi.c file.

    Due to some timing issues, this function returns an error when it tries to read some registers in the camera. The problem that you are facing is similar to the one that we had and we changed the function to do the following (by replacing the existing loop):

    retval = i2c_master_send(ov5640_data.i2c_client, au8RegBuf, 2);

    while (2 != retval) {

    // pr_err("%s:write reg error:reg=%x **********************************************\n", __func__, reg);

    // pr_err("Retrying...\n");

    msleep(200);

    retval = i2c_master_send(ov5640_data.i2c_client, au8RegBuf, 2);

    //return -1;

    }

    retval = i2c_master_recv(ov5640_data.i2c_client, u8RdVal, 1);

    while (1 != retval) {

    // pr_err("%s:read reg error:reg=%x,val=%x **********************************************\n", __func__, reg, u8RdVal);

    // pr_err("Retrying...\n");

    msleep(200);

    retval = i2c_master_recv(ov5640_data.i2c_client, u8RdVal, 1);

    //return -1;

    }

    The main change as compared to the existing loop is the introduction of msleep and putting this read/write into a while loop till it is successful.

    You may try the same change and see if it is useful for you to overcome the error.

    Best Wishes

  • RELEVANCY SCORE 2.73

    DB:2.73:Debugging Two Prallel Camera Operation On Custom Board Based On Sabresd Imx6q Evaluation cm



    I have a custom build board based on imx6q SabreSD evaluation kit where I connected two parallel cameras ov5640. The cameras are connected to IPU1 and IPU2. The IPU1 CSI1 connection is same as SabreSD setup and works, however the IPU2 CSI2 connection is not working correctly. I done all the mods to the driver to allow two parallel cameras to work. I can talk to the camera and the driver finds the camera. The camera can be programmed too, and all the clock signals generated by the camera are working same as the camera that is working. However, when I display the camera the output does not look synced, but seems to be data coming from the camera. I am looking from some tips on to how to debug my setup.

    DB:2.73:Debugging Two Prallel Camera Operation On Custom Board Based On Sabresd Imx6q Evaluation cm


    Hi,

    I finally found the problem. The problem in this case was a hardware one. Being a custom board the PCB layout for the second camera had longer links. After some checking realised that the 56mhz pixel clock signal was not going to the imx6 cleanly so when putting the scope probe to look at the signal the out of sync capture became good. Soldering a small 20pf cap across the pin an the ground near the imx6 fixed the issue.

    This is quite good result for me.

    There is good advantage from my design as it uses both imx6 ipu's which are not used in the reference SabreSD board which uses one ipu to run two cameras. For me this helps as the IPU_prt_enc driver can be duplicated without BSP code change and can support two cameras concurrently. When one IPU is used this can be achieved with the official BSP only by using IPU_CSI_enc for the second driver. However this driver has less features then IPU_prp_enc driver.

    Makis

  • RELEVANCY SCORE 2.71

    DB:2.71:Getting Frex Frames On Ov5640 In I.Mx6 17



    Hi everyone,

    I am currently running a i.MX6 Wandboard with Arch Linux ARM v3.10.17-5. I have a OV5640 camera sensor. I have a sample driver file for the sensor, that I have modified slightly. I inserted into the I2C probe function and the I2C write register function. I followed the OV5640 datasheet (http://www.topeetboard.com/dwon/OV5640_CSP3_DS_1.0_xin_jin_hui.pdf) to configure the sensor to enable FREX mode and the STROBE functionality. The streaming functionality seems to work fine still. I can send a FREX request in the driver, and view the STROBE pulse on the scope. I do not know what happens to these frames or how to identify them through the V4L2 layer. Any ideas?

    Thanks

    darsnack

    DB:2.71:Getting Frex Frames On Ov5640 In I.Mx6 17


    Hi everyone,

    I am currently running a i.MX6 Wandboard with Arch Linux ARM v3.10.17-5. I have a OV5640 camera sensor. I have a sample driver file for the sensor, that I have modified slightly. I inserted into the I2C probe function and the I2C write register function. I followed the OV5640 datasheet (http://www.topeetboard.com/dwon/OV5640_CSP3_DS_1.0_xin_jin_hui.pdf) to configure the sensor to enable FREX mode and the STROBE functionality. The streaming functionality seems to work fine still. I can send a FREX request in the driver, and view the STROBE pulse on the scope. I do not know what happens to these frames or how to identify them through the V4L2 layer. Any ideas?

    Thanks

    darsnack

  • RELEVANCY SCORE 2.66

    DB:2.66:Image Sensor Supported By Imx6 d1



    In the current release kernel 3.0, there are only the following image sensors supported:

    MT9V111

    OV2640

    OV3640

    OV5640

    OV8820

    However, these sensors are quite old and spec are not competitive.

    Anyone knows if there are any other newer sensors can be supported by iMX6?

    DB:2.66:Image Sensor Supported By Imx6 d1


    Yes, I mean support out of box by imx6. Currently we are using the OV5642 camera module from Boundary device.

    For out-of-box support those are the supported modules

    Another question is, if I integrate other module driver to the kernel, can it be supported by the gstreamer?

    I believe so.

    Any new camera will be a /dev/videoX device, and in case you need to change some source code for gstreamer, it will be only use /dev/video10 instead of /dev/video0.

  • RELEVANCY SCORE 2.64

    DB:2.64:Cpu Load When Streaming Full Hd Camera Input To Full Hd Hdmi Display f3



    Hi all,

    Now i am trying to stream a full HD resolution (1920x1080, 30fps) camera input from OV5640 MIPI camera to display it on a full HD HDMI display.

    I manage to do so by:

    gst-launch mfw_v4lsrc device=/dev/video1 capture-mode=5 ! mfw_v4lsink

    However, when i see the CPU load using the 'top' command, the CPU load is near to 100%. Why is the CPU load so high? Isn't it the IPU should kick in in such situation and free the CPU from doing other task?

    I am using i.mx6SabreSD board, trying to simulate performance of i.mx6 SOLO by limiting the cpu to 1 core in u-boot boot arguement.

    Thank you.

    Regards,

    Zhen Cong Tee

    DB:2.64:Cpu Load When Streaming Full Hd Camera Input To Full Hd Hdmi Display f3


    As for IPU performance - it depends on system load (mainly - DRAM throughput), since other (system throughput consuming) modules may influence here.

  • RELEVANCY SCORE 2.64

    DB:2.64:Two Ov5640 Sensors On The Imx6 Csi-2 Interface 83



    I'm quite new to the MIPI standards and have started working with camera sensors using the i.MX6 CSI-2 interface. Is it possible to connect two OV5640 sensors to the chip's CSI-2 interface? I understand the need for unique I2C addresses for control. I would like to capture simultaneous as well as individual stills/video from the two sensors. I appreciate your insights and advice.

    DB:2.64:Two Ov5640 Sensors On The Imx6 Csi-2 Interface 83


    Hi R

    you can connect up to 4 cameras to the MIPI CSI-2 interface.

    For this you have to either use a MIPI CSI-2 hub (if anything

    like this already exists) or multiplex the four streams in an FPGA.

    Each camera in this case should use a different stream

    identifier (stream 0-3). See attached file.

    Best regards

    chip

    -----------------------------------------------------------------------------------------------------------------------

    Note: If this post answers your question, please click the Correct Answer button. Thank you!

    -----------------------------------------------------------------------------------------------------------------------

  • RELEVANCY SCORE 2.64

    DB:2.64:Ov5640 Mipi Camera Not Work For Imx6 Android 4.4.2 Bsp z3



    BSP: Android 4.4.2 kernel: 3.0

    Hello:

    Our customer board init rear camera using ov5640 mipi camera, the HW modify as follow:

    static iomux_v3_cfg_t mx6q_sabresd_mipi_sensor_pads[] = {

    MX6Q_PAD_GPIO_0__CCM_CLKO, /* camera clk */

    MX6Q_PAD_CSI0_DAT11__GPIO_5_29, /* camera PWDN */

    MX6Q_PAD_CSI0_DAT10__GPIO_5_28, /* camera RESET */

    //MX6Q_PAD_SD1_DAT2__GPIO_1_19, /* camera PWDN */

    //MX6Q_PAD_SD1_CLK__GPIO_1_20, /* camera RESET */

    };

    then move I2C bus from I2C2 to I2C1, so I modify the source code as follow:

    static struct i2c_board_info mxc_i2c0_board_info[] __initdata = {

    {

    I2C_BOARD_INFO("wm89**", 0x1a),

    },

    /* {

    I2C_BOARD_INFO("ov564x", 0x3c),

    .platform_data = (void *)camera_data,

    },*/

    {

    I2C_BOARD_INFO("mma8x5x", 0x1c),

    .irq = gpio_to_irq(SABRESD_ACCL_INT),

    .platform_data = (void *)mma8x5x_position,

    },

    {

    I2C_BOARD_INFO("ov5640_mipi", 0x3c),

    .platform_data = (void *)mipi_csi2_data,

    },

    };

    But when boot OS, I can't open Camera APP, it show "Connect Camera failed",

    But kernel message was boot success as follow:

    camera ov5640_mipi is found

    mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video16

    mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video17

    mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video18

    mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video19

    mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video20

    i2c can read/write using i2c tools command!

    By the way, we not have front camera now, we must be use USB camera as front camera in the future.

    How to fix this issue?

    In addition, I wonder why SABRESD_MIPICSI_PWN default was high, this pin initial low as default refer to

    datasheet, right?

    logcat file in the attachment, thanks!

    https://dl.dropboxusercontent.com/u/70208644/ov5640_logcat.txt

    DB:2.64:Ov5640 Mipi Camera Not Work For Imx6 Android 4.4.2 Bsp z3


    Hi,

    Please share the init.freescale.rc configuration you have. You have to make sure that this file contains the correct configuration.

    Please download the Android FAQ.pdf.

    http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=IMX6_SW

    Under "Documentation"--"Android"

    There you can find in the "18 How do I configure rear and front camera?"

    Best Regards,

    Alejandro

  • RELEVANCY SCORE 2.64

    DB:2.64:Camera Modules For Imx6 Sabre Board For Smart Devices ss



    Hi,

    I am looking for mipi and parallel camera modules that can be interfaced to the imx6 sabre board for smart devices.

    Thank you

    Gopal

    DB:2.64:Camera Modules For Imx6 Sabre Board For Smart Devices ss


    The i.MX6 Sabre SDP board already comes with both a parallel and a mipi camera: OV5642, please take a look at the design files for more info.

  • RELEVANCY SCORE 2.60

    DB:2.60:Armhf Kernel And Library Support For Imx6 a3



    Hi all,

    We are developing a IMX6DL board, and we have to run a detection algorithm over a camera image stream.

    In order to improve the performance of execution, we are now trying to switch from the current armel build to a armhf build,

    but we have not yet managed to achieve this.

    We have found out this discussion armhf libraries for imx6 and we have not yet figured out if, nowadays, support for armhf

    architecture exists or not for the imx6 platform...Can anyone help us to find out?

    I thank you in advice for any help,

    Best Regards

    Daniele

    DB:2.60:Armhf Kernel And Library Support For Imx6 a3


    I'm currently using a Debian Wheezy armhf, kernel 3.10.17 on a Udoo Dual Board, which is based on the imx.6DL. You can find some armhf Ubuntu or Debian rootfs on their website. They even have a Yocto to build your own rootfs, I guess you can adapt it to your board with a bit of tweaking.

    So yes, it exists. I'm doing some image processing with openCV and some NEON code to speed up things a bit, and gained a little more than 30% in performance compared to a softfp test ! This is quite nice !

  • RELEVANCY SCORE 2.56

    DB:2.56:I.Mx6q : Parallel Csi#2 Not Working 1f



    We have made a custom board based on i.MX6Q able to manage camera connected either to :
    Parallel CSI#1 : camera module OV5642Parallel CSI#2 : camera module OV5642MIPI CSI : camera module OV5640
    Parallel CSI#1 and MIPI CSI are well supported, but parallel CSI#2 isnt working

    We have checked and re-checked the IOMUX and believe the problem cant be there.

    We havent found compiling option (in Linux .config) related to parallel CSI#2 support.

    Freescale document fix about CSI numbering : The latest Rev 1 or i.MX6 RM for DQ says the second parallel camera is connected to CSI1 whereas previous version of the same document said it was connected to CSI0. Was it purely a document issue or is it linked to a silicium revision of i.MX6Q ?

    Strange observation #1 : Cant make IPU#2 working

    This could fully explain our problem. Parallel CSI#2 camera can only work on IPU#2 but MIPI CSI camera can run either on IPU#1 or IPU#2 and we didnt succeed in making it work on IPU#2.

    In the code, IPU#2 seems initialized by imx6q_add_ipuv3(1, ipu_data[1]);

    Strange observation #2 : First parallel CSI camera requires MIPI CSI support

    Using a single camera connected on the first parallel CSI port, we cant make it work without MIPI CSI support If the following 2 lines are removed, it doesnt work :

    imx6q_add_v4l2_capture(1, capture_data[1]);

    imx6q_add_mipi_csi2(mipi_csi2_pdata);

    So it seems there is a global initialisation done by one of the above lines that is required to support the first CSI camera.

    Has anybody succeeded in making the second parallel CSI camera work ? Does it require a particular patch ?

    Regards.

    DB:2.56:I.Mx6q : Parallel Csi#2 Not Working 1f


    How to let kernel support adv7180 's driver select ipu and csi channel ?   I'm sure, causes the registration failure is IPU and CSI channel selection error , Following patch is someone else's adv7180 channel selection, I hope can get detailed patches

    mx6_nitrogen6x: add adv7180 tv input camera 73898f3 boundarydevices/linux-imx6 GitHub

  • RELEVANCY SCORE 2.55

    DB:2.55:How To Deal With 8bits Raw-Rgb From Mipi Camrea Sensor To Preview sz



    Hi Sir/Madam,

    I'm working for a new MIPI camera on iMx6 quad.

    After checking many information on community, I still have no idea about how to deal with raw data.

    Since ov5642 and ov5640 MIPI can output YUV data, IPU can handle it and we can preview the images with V4l by gstreamer via HDMI.

    Now our hardware use ov2710 that can only output 8/10 bits RAW RGB with MIPI interface.

    According to the information on community, I think I should use generic mode to capture raw data and use software for conversion.

    So there are some problems.

    1. How to set CSI/IDMAC/CPMEM to capture 8bits raw data that are from MIPI interface ?

    2. How to deal with these raw data to convert it to YUV or RGB? Can gstreamer bayer plugins do this job?

    3. If we capture raw data and convert it to YUV by software and then output it to HDMI for preview simultaneously. Is this idea workable? or Does any one has such experience ?

    Thanks

    Best Regards,

    Jason

    DB:2.55:How To Deal With 8bits Raw-Rgb From Mipi Camrea Sensor To Preview sz


    Hi Sir/Madam,

    I'm working for a new MIPI camera on iMx6 quad.

    After checking many information on community, I still have no idea about how to deal with raw data.

    Since ov5642 and ov5640 MIPI can output YUV data, IPU can handle it and we can preview the images with V4l by gstreamer via HDMI.

    Now our hardware use ov2710 that can only output 8/10 bits RAW RGB with MIPI interface.

    According to the information on community, I think I should use generic mode to capture raw data and use software for conversion.

    So there are some problems.

    1. How to set CSI/IDMAC/CPMEM to capture 8bits raw data that are from MIPI interface ?

    2. How to deal with these raw data to convert it to YUV or RGB? Can gstreamer bayer plugins do this job?

    3. If we capture raw data and convert it to YUV by software and then output it to HDMI for preview simultaneously. Is this idea workable? or Does any one has such experience ?

    Thanks

    Best Regards,

    Jason

  • RELEVANCY SCORE 2.53

    DB:2.53:How To Debug Vivante Start-Up Problems In Kitkat? sp



    I'm trying to boot the Android kitkat ga release, but I get stuck when trying to initialise the Vivante GPU.

    Apparently I hit an error in one of the binary modules.

    The kernel log does not show anything suspicios, but from the android log I get the following:

    D/libEGL ( 2215): loaded /system/lib/egl/libEGL_VIVANTE.so

    D/libEGL ( 2215): loaded /system/lib/egl/libGLESv1_CM_VIVANTE.so

    D/libEGL ( 2215): loaded /system/lib/egl/libGLESv2_VIVANTE.so

    W/imx6.gralloc( 2215): 32bpp setting of Framebuffer catched!

    W/imx6.gralloc( 2215): using (fd=16)

    W/imx6.gralloc( 2215): id = DISP3 BG

    W/imx6.gralloc( 2215): xres = 320 px

    W/imx6.gralloc( 2215): yres = 480 px

    W/imx6.gralloc( 2215): xres_virtual = 320 px

    W/imx6.gralloc( 2215): yres_virtual = 1536 px

    W/imx6.gralloc( 2215): bpp = 32

    W/imx6.gralloc( 2215): r = 0:8

    W/imx6.gralloc( 2215): g = 8:8

    W/imx6.gralloc( 2215): b = 16:8

    W/imx6.gralloc( 2215): width = 51 mm (159.372543 dpi)

    W/imx6.gralloc( 2215): height = 76 mm (160.421051 dpi)

    W/imx6.gralloc( 2215): refresh rate = 73.62 Hz

    I/v_hwc ( 2215): Default primary display

    I/v_hwc ( 2215): xres = 320 px

    I/v_hwc ( 2215): yres = 480 px

    I/v_hwc ( 2215): xdpi = 159.4 dpi

    I/v_hwc ( 2215): ydpi = 160.4 dpi

    I/v_hwc ( 2215): refresh rate = 73.6 Hz

    D/v_gal ( 2215): [tid=2215] Process got signal (8). To further debug the issue, you should run in debug mode

    Sadly, I can't find any documenetation anywhere telling me how to run in debug mode, so I am rather stuck.

    Please advise.

    DB:2.53:How To Debug Vivante Start-Up Problems In Kitkat? sp


    Hi Robert,

    In general you can debug your kernel by enabling debug output or adding printk's Did you turn on DEBUG flag in GPU driver kernel side? It may help.

    Links that might help:

    http://jas-hacks.blogspot.co.uk/2013/10/imx6-ubuntu-1304-debugging-gpu.html

    Hope this helps

  • RELEVANCY SCORE 2.51

    DB:2.51:Ov5640 Not Work For Imx6 Android 4.4.2 Bsp d8



    BSP: Android 4.4.2 kernel: 3.0

    Hello:

    Our customer board init rear camera using ov5640 mipi camera, the HW modify as follow:

    static iomux_v3_cfg_t mx6q_sabresd_mipi_sensor_pads[] = {

    MX6Q_PAD_GPIO_0__CCM_CLKO, /* camera clk */

    MX6Q_PAD_CSI0_DAT11__GPIO_5_29, /* camera PWDN */

    MX6Q_PAD_CSI0_DAT10__GPIO_5_28, /* camera RESET */

    //MX6Q_PAD_SD1_DAT2__GPIO_1_19, /* camera PWDN */

    //MX6Q_PAD_SD1_CLK__GPIO_1_20, /* camera RESET */

    };

    then move I2C bus from I2C2 to I2C1, so I modify the source code as follow:

    static struct i2c_board_info mxc_i2c0_board_info[] __initdata = {

    {

    I2C_BOARD_INFO("wm89**", 0x1a),

    },

    /* {

    I2C_BOARD_INFO("ov564x", 0x3c),

    .platform_data = (void *)camera_data,

    },*/

    {

    I2C_BOARD_INFO("mma8x5x", 0x1c),

    .irq = gpio_to_irq(SABRESD_ACCL_INT),

    .platform_data = (void *)mma8x5x_position,

    },

    {

    I2C_BOARD_INFO("ov5640_mipi", 0x3c),

    .platform_data = (void *)mipi_csi2_data,

    },

    };

    But when boot OS, I can't open Camera APP, it show "Connect Camera failed",

    But kernel message was boot success as follow:

    camera ov5640_mipi is found

    mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video16

    mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video17

    mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video18

    mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video19

    mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video20

    i2c can read/write using i2c tools command!

    By the way, we not have front camera now, we must be use USB camera as front camera in the future.

    How to fix this issue?

    In addition, I wonder why SABRESD_MIPICSI_PWN default was high, this pin initial low as default refer to

    datasheet, right?

    logcat file in the attachment, thanks!

    https://dl.dropboxusercontent.com/u/70208644/ov5640_logcat.txt

    DB:2.51:Ov5640 Not Work For Imx6 Android 4.4.2 Bsp d8


    BSP: Android 4.4.2 kernel: 3.0

    Hello:

    Our customer board init rear camera using ov5640 mipi camera, the HW modify as follow:

    static iomux_v3_cfg_t mx6q_sabresd_mipi_sensor_pads[] = {

    MX6Q_PAD_GPIO_0__CCM_CLKO, /* camera clk */

    MX6Q_PAD_CSI0_DAT11__GPIO_5_29, /* camera PWDN */

    MX6Q_PAD_CSI0_DAT10__GPIO_5_28, /* camera RESET */

    //MX6Q_PAD_SD1_DAT2__GPIO_1_19, /* camera PWDN */

    //MX6Q_PAD_SD1_CLK__GPIO_1_20, /* camera RESET */

    };

    then move I2C bus from I2C2 to I2C1, so I modify the source code as follow:

    static struct i2c_board_info mxc_i2c0_board_info[] __initdata = {

    {

    I2C_BOARD_INFO("wm89**", 0x1a),

    },

    /* {

    I2C_BOARD_INFO("ov564x", 0x3c),

    .platform_data = (void *)camera_data,

    },*/

    {

    I2C_BOARD_INFO("mma8x5x", 0x1c),

    .irq = gpio_to_irq(SABRESD_ACCL_INT),

    .platform_data = (void *)mma8x5x_position,

    },

    {

    I2C_BOARD_INFO("ov5640_mipi", 0x3c),

    .platform_data = (void *)mipi_csi2_data,

    },

    };

    But when boot OS, I can't open Camera APP, it show "Connect Camera failed",

    But kernel message was boot success as follow:

    camera ov5640_mipi is found

    mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video16

    mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video17

    mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video18

    mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video19

    mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video20

    i2c can read/write using i2c tools command!

    By the way, we not have front camera now, we must be use USB camera as front camera in the future.

    How to fix this issue?

    In addition, I wonder why SABRESD_MIPICSI_PWN default was high, this pin initial low as default refer to

    datasheet, right?

    logcat file in the attachment, thanks!

    https://dl.dropboxusercontent.com/u/70208644/ov5640_logcat.txt

  • RELEVANCY SCORE 2.50

    DB:2.50:Does Imx6 Android Support Two Camera Run At The Same Time xk



    dear all

    I use the saberd imx6q,i want two camera run at the same time ,now the driver and hardware can support two camera run at same time ,but i don not know if android can show two camera at the same

    DB:2.50:Does Imx6 Android Support Two Camera Run At The Same Time xk


    https://community.freescale.com/docs/DOC-94798

    http://boundarydevices.com/jellybean-max/

  • RELEVANCY SCORE 2.49

    DB:2.49:Imx6 With Ov5640 Mipi Camera cf



    Hi all

    When we use iMX6Q with OV5640 MIPI camera, we find that the camera device seems to be getting released as soon as it is opened. Here is the debug log that we are getting after enabling DEBUG:

    In MVC: mxc_v4l_open device name is Mxc Camera End of mxc_v4l_open: v2f pix widthxheight 288 x 352 End of mxc_v4l_open: crop_bounds widthxheight 640 x 480 End of mxc_v4l_open: crop_defrect widthxheight 640 x 480 End of mxc_v4l_open: crop_current widthxheight 640 x 480 On Open: Input to ipu size is 640 x 480 In MVC:mxc_v4l_ioctl In MVC: mxc_v4l_do_ioctl 80685600 case VIDIOC_QUERYCAP In MVC:mxc_v4l_ioctl In MVC: mxc_v4l_do_ioctl c02c5651 In MVC:mxc_v4l_close mxc_v4l_close: release resource MVC: In mxc_free_frame_buf
    In MVC:mxc_free_frames

    The following are the changes made by us in the Android 4 code base:

    - Changed .csi field in ov5640_mipi_data structure from 0 to 1 in mx6q_sabrelite.c

    static struct fsl_mxc_camera_platform_data ov5640_mipi_data = {

    .mclk = 22000000,

    .csi = 1,

    .io_init = mx6_mipi_sensor_io_init,

    .pwdn = ov5640_mipi_camera_powerdown,

    };

    - Changed csi_id in mipi_csi2_pdata from 0 to 1

    static struct mipi_csi2_platform_data mipi_csi2_pdata = {

    .ipu_id = 0,

    .csi_id = 1,

    .v_channel = 0,

    .lanes = 2,

    .dphy_clk = "mipi_pllref_clk",

    .pixel_clk = "emi_clk",

    };

    - Commented the first capture interface in board_init (Since we are using only one camera - MIPI Camera - alone)

    static struct fsl_mxc_capture_platform_data capture_data[] = {

    {

    .csi = 0,

    .ipu = 0,

    .mclk_source = 0,

    .is_mipi = 0,

    }, {

    .csi = 1,

    .ipu = 0,

    .mclk_source = 0,

    .is_mipi = 1,

    },

    };

    imx6q_add_v4l2_output(0);

    //imx6q_add_v4l2_capture(0, capture_data[0]);

    imx6q_add_v4l2_capture(1, capture_data[1]);

    - In mxc_v4l2_capture.c, changed CAPTURE_NUM_INPUTS to 1 from 2 since we have only one capture interface now.

    Can someone throw some inputs on why the camera seems to be stopping and not working as expected?

    Thanks in advance for your inputs and help.

    DB:2.49:Imx6 With Ov5640 Mipi Camera cf


    Hi all

    When we use iMX6Q with OV5640 MIPI camera, we find that the camera device seems to be getting released as soon as it is opened. Here is the debug log that we are getting after enabling DEBUG:

    In MVC: mxc_v4l_open device name is Mxc Camera End of mxc_v4l_open: v2f pix widthxheight 288 x 352 End of mxc_v4l_open: crop_bounds widthxheight 640 x 480 End of mxc_v4l_open: crop_defrect widthxheight 640 x 480 End of mxc_v4l_open: crop_current widthxheight 640 x 480 On Open: Input to ipu size is 640 x 480 In MVC:mxc_v4l_ioctl In MVC: mxc_v4l_do_ioctl 80685600 case VIDIOC_QUERYCAP In MVC:mxc_v4l_ioctl In MVC: mxc_v4l_do_ioctl c02c5651 In MVC:mxc_v4l_close mxc_v4l_close: release resource MVC: In mxc_free_frame_buf
    In MVC:mxc_free_frames

    The following are the changes made by us in the Android 4 code base:

    - Changed .csi field in ov5640_mipi_data structure from 0 to 1 in mx6q_sabrelite.c

    static struct fsl_mxc_camera_platform_data ov5640_mipi_data = {

    .mclk = 22000000,

    .csi = 1,

    .io_init = mx6_mipi_sensor_io_init,

    .pwdn = ov5640_mipi_camera_powerdown,

    };

    - Changed csi_id in mipi_csi2_pdata from 0 to 1

    static struct mipi_csi2_platform_data mipi_csi2_pdata = {

    .ipu_id = 0,

    .csi_id = 1,

    .v_channel = 0,

    .lanes = 2,

    .dphy_clk = "mipi_pllref_clk",

    .pixel_clk = "emi_clk",

    };

    - Commented the first capture interface in board_init (Since we are using only one camera - MIPI Camera - alone)

    static struct fsl_mxc_capture_platform_data capture_data[] = {

    {

    .csi = 0,

    .ipu = 0,

    .mclk_source = 0,

    .is_mipi = 0,

    }, {

    .csi = 1,

    .ipu = 0,

    .mclk_source = 0,

    .is_mipi = 1,

    },

    };

    imx6q_add_v4l2_output(0);

    //imx6q_add_v4l2_capture(0, capture_data[0]);

    imx6q_add_v4l2_capture(1, capture_data[1]);

    - In mxc_v4l2_capture.c, changed CAPTURE_NUM_INPUTS to 1 from 2 since we have only one capture interface now.

    Can someone throw some inputs on why the camera seems to be stopping and not working as expected?

    Thanks in advance for your inputs and help.

  • RELEVANCY SCORE 2.47

    DB:2.47:[I.Mx6q Sabre ] Questions About Video Encoding Form A Camera With Gstreamer 0.10 a7


    Hello Mr./Mrs.

    [Develop Environment]
    H.W. : Freescale i.MX6q SABRE board / ov5640_camera
    S.W. : L3.0.35_4.0.0_130424_Source / gstreamer-0.10.35 / gst-fsl-plugins-3.0.7

    [Issue Description]
    After studied disscusion on this community ; GStreamer i.MX6 Pipelines , Re: How to do video encoding (h264 .mp4) file using gstreamer in IMX6Q?
    We still encounter two problems during encode video from ov5640.

    Q1. Does freescale gst-plugins support mp4mux ?
    It works fine if we encode video with matroskamux but we can't play video after we replaced matroskamux to mp4mux. The command as bellow:

    root@freescale /$ gst-launch -v --gst-debug=2 mfw_v4lsrc fps-n=30 capture-mode=4 ! queue ! vpuenc ! mp4mux ! filesink location=output.mp4 sync=false

    Q2. When we set "vpuenc codec=6" for H.264 encoding it will interrupt after half minutes. How to fix this error ?

    [Error Log]
    0:00:35.031735337 2906 0xd17d0 WARN mfw_v4lsrc mfw_gst_v4lsrc.c:1210:mfw_gst_v4lsrc_buffer_new: no buffer available in pool 0:00:35.032118671 2906 0xd17d0 WARN basesrc gstbasesrc.c:2582:gst_base_src_loop:mfwgstv4lsrc0 error: Internal data flow error. 0:00:35.032296337 2906 0xd17d0 WARN basesrc gstbasesrc.c:2582:gst_base_src_loop:mfwgstv4lsrc0 error: streaming task paused, reason error (-5) ERROR: from element /GstPipeline:pipeline0/MFWGstV4LSrc:mfwgstv4lsrc0: Internal data flow error.

    If you need detail log or more info. please feel free to let me know.

    Thanks for your time,

    Jimmy Su

    DB:2.47:[I.Mx6q Sabre ] Questions About Video Encoding Form A Camera With Gstreamer 0.10 a7


    For Q1, try the recommendation on the link you posted Re: How to do video encoding (h264 .mp4) file using gstreamer in IMX6Q?

    For Q2, you may try adding this property to the queue element: max-size-buffers=1. By the way, I was not able to reproduce Q2 issue.

  • RELEVANCY SCORE 2.47

    DB:2.47:Interfacing Ov5640 Mipi Camera With Imx6 Sabresd dj



    Hi Everyone,

    While trying to interface 5MP MIPI (ov5640) with my custom sabresd board running on Android JB, encountered the following problem. The changes which I made in my init.freescale.rc didnt get reflected in the operation.

    I added the following commands to my init.freescale.rc file,

    setprop back_camera_name ov8825_mipi,ov5640_mipi,ov5640_camera,uvc

    setprop back_camera_orient 0

    insmod /system/lib/modules/ov5640_mipi.ko

    But my logcat shows,

    I/FslCameraHAL( 2301): Face Back Camera is 0, orient is 0

    I/FslCameraHAL( 2301): Face Front Camera is 0, orient is 0

    I tried all combinations of above commands within my init.freescale.rc but it didn work, Do I need to add these commands somewhere else?.

    The above problem seems to be with ov5640 mipi only whereas ov8825 mipi and ov5640 paralled worked out well with the above combination.

    DB:2.47:Interfacing Ov5640 Mipi Camera With Imx6 Sabresd dj


    Please download the Android FAQ.pdf.

    http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=IMX6_SW

    Under "Documentation"--"Android"

    The information you can find in the "22 How do I configure rear and front camera?"

    Hope this can help you.

  • RELEVANCY SCORE 2.46

    DB:2.46:How To Add New Devices To Linux Kernel 3.18 sa



    Hi all,

    I am using imx6 SoloLite processor Eval board. Because of few other constraints (i.e. no support for few modules that we used in earlier version) I'm forced to use Linux kernel 3.18.

    I wanted to add a camera (OV5640) with CSI interface to kernel 3.18. Can any one help me with the steps that I need to follow to add this module in .dts and dtsi files and also how to patch the driver. As I am completely new to the linux kernel.

    I have seen the camera driver for ov5640 is available for the kernel 2.6 which I attached hear. how to use the same.

    Thanks Regards,

    Satya.

    DB:2.46:How To Add New Devices To Linux Kernel 3.18 sa


    You can find the BSP and documents from here:

    i.MX 6 Series Software and Development Tool R|Freescale

  • RELEVANCY SCORE 2.46

    DB:2.46:Asus M4a89gtd Pro 2 Kits Of Cmx4gx3m2a1600c7 : Stability Issue fm


    Hi,

  • RELEVANCY SCORE 2.46

    DB:2.46:Change Camera Parameters On The Fly (I2c) kj



    Hi, we are using board based on QSB with camera ov5640, but I think this applies globally.

    I would like to change specific camera parameters on the fly, without stopping video camera. For example, I have changed default i2c configuration values in ov5640.c driver, so that it goes into night mode (after reading datasheet on how to do it) when initialized. But now I would like to change one value in one of camera's i2c registers on the fly, but it doesn't work.

    I have tried to add a character device interface for camera driver and then from there call the internal ov5640_write_reg() function, but it doesn't work this way. The i2c_master_send() returns -5. Does the driver somehow closes connection after it has sent initial parameters or is it blocking i2c?

    Can someone help me please?

    Thank you.

    DB:2.46:Change Camera Parameters On The Fly (I2c) kj


    The problem is that when starting video capture, then i2c clock is turned on and off in different driver module (not in camera module), that's why it isn't possible later to change these parameters.

    .....
    ipu_csi_enable_mclk_if(CSI_MCLK_I2C, cam-csi, true, true);
    err = vidioc_int_s_parm(cam-sensor, parm);

    ipu_csi_enable_mclk_if(CSI_MCLK_I2C, cam-csi, false, false);

    ......

    To overcome this, we had to turn on/off i2c clock manually.

  • RELEVANCY SCORE 2.45

    DB:2.45:Full Hd Camera Input Using Gstreamer kx



    Hi all,

    I am trying to input the camera input in full HD format using gstreamer, and i come across the below thread:

    How to set imx6 camera resolution with gstreamer

    I tried to set the capture mode to 5 (1920x1080), but gstreamer returns me error below:

    root@imx6qsabresd:~# gst-launch mfw_v4lsrc capture-mode=5 ! mfw_v4lsink

    MFW_GST_V4LSRC_PLUGIN 3.0.11 build on Jun 17 2014 15:53:58.

    ov5640 initial set to VGA 30fps

    ERROR: v4l2 capture: slave not found!

    MFW_GST_V4LSINK_PLUGIN 3.0.11 build on Jun 17 2014 15:53:52.

    Setting pipeline to PAUSED ...

    ov5640 initial set to VGA 30fps

    Set ov5640 mode to 1080P

    ov5640 frame rate is 30fps

    mxc_v4l2_s_param: vidioc_int_s_parm returned an error -22

    ERROR: Pipeline doesn't want to pause.

    Setting pipeline to NULL ...

    Total rendered:0

    Freeing pipeline ...

    [---FINALIZE v4l_sink

    Some of the print out above about the video resolution setting to the camera is done by me into the ov5640 camera driver so that i can make sure what resolution setting is used by the camera.

    Is it gstreamer really cannot take in full HD camera input? or is there anything i missed out that need to be done so that gstreamer can take in full HD camera input?

    Thank you.

    Regards,

    Zhen Cong Tee

  • RELEVANCY SCORE 2.44

    DB:2.44:[Stability Issue] Cm3x2g1333c9 + Intel Dp45sg fp


    Hello,

    DB:2.44:[Stability Issue] Cm3x2g1333c9 + Intel Dp45sg fp

    I think you missed the first part of my suggestion:

  • RELEVANCY SCORE 2.43

    DB:2.43:Store Images In Pc Through Usb Cable x8



    hi all,

    I am using i.MX535 qsb in that i interfaced a camera application, i am using ov5640 camera sensor for recording, streaming and capturing the video and images, now i need to send the images and video through the USB cable to PC whether it is windows or Linux, can anyone help me, i am new to linux.

    NOTE :

    I want to use the board like a webcam does any one have idea about this

    Thanks,

    shan

    DB:2.43:Store Images In Pc Through Usb Cable x8


    yes, installing this code is the hard part

    Try using LTIB to compile this repo. Look at the .spec files located on ltib/dist/lfs-5.1/fsl-mm. before creating a new spec, run your commands under the ltib's shell (./ltib -m shell) and see if GST is found.

  • RELEVANCY SCORE 2.43

    DB:2.43:Imx53 Qsb Interface With Ov5640 1c



    IMX53 QSB board interfaced with the OV5640 Sensor interface, I configured boundary_camera and ov5640 driver and Boot Sequence for ov560 are configured. But OV5640 is not responding any of the I2C commands. Any one Faced this issue, kindly response.

    DB:2.43:Imx53 Qsb Interface With Ov5640 1c


    How did you capture jpeg image?! With gstreamer + v4l2src?

    I'm having some trouble with this too.

  • RELEVANCY SCORE 2.43

    DB:2.43:Description Of Undocumented Imx6 Mipi Registers zc



    Hello, I'm using freescale imx6q sabresd board, Android 4.0.0. I'm trying to bring up omnivisio ov9740 mipi camera connected to the same port as ov5640 on the demo board.

    Can somebody from the Freescale side please provide details on the following MIPI registers:

    CSI2_PHY_TST_CTRL0

    CSI2_PHY_TST_CTRL1

    DB:2.43:Description Of Undocumented Imx6 Mipi Registers zc


    These two registers are command and data like registers.

    In MIPI CSI PHY internal, there are some pre-defined MIPI serial clock. From the MIPI_CSI_PHY_TST_CTRL registers, it can tell the PHY to use which one for target clocks.

    For example: 0x14, it is for 849MHz MIPI serial clock, from MIPI CSI_PHY_TST_CTRL1 register, the software just send this index data to the PHY, then the PHY will use pre-set parameters to generate the 849MHz serial clock.

    For how to enable the MIPI camera, please reference to: https://community.freescale.com/message/328301

  • RELEVANCY SCORE 2.43

    DB:2.43:Error Using Gstreamer With Adv7180 With Qt 33



    Hello,

    I came accross this blog,

    iMx6 ,adv7180 and gstreamer

    I have a similar issue, but regarding QT.

    I followed the instructions in the blog, and i was able to view the display using ADV7180 using gst-launch.

    But when i run the "Declarative-Camera" code from the QT library in multimediawidgets, the code executes and GUI appears but the display does not work. the screen goes blank where it should play the video which is input to ADV7180.

    Is this a known issue? Is there a solution to it?

    thank you for your time,

    Nishad

    DB:2.43:Error Using Gstreamer With Adv7180 With Qt 33


    Hello,

    I came accross this blog,

    iMx6 ,adv7180 and gstreamer

    I have a similar issue, but regarding QT.

    I followed the instructions in the blog, and i was able to view the display using ADV7180 using gst-launch.

    But when i run the "Declarative-Camera" code from the QT library in multimediawidgets, the code executes and GUI appears but the display does not work. the screen goes blank where it should play the video which is input to ADV7180.

    Is this a known issue? Is there a solution to it?

    thank you for your time,

    Nishad

  • RELEVANCY SCORE 2.43

    DB:2.43:I.Mx6 Gstreamer Dual Record Fail c3



    1) We use Use L3.0.35_4.1.0_130816_images_MX6.tar.gz on i.MX6Q-SDP with below commands to do dual record but fail.

    2) Have to submit SR, but he suggest post here.

    3) Also try the apply unoffical patch from OV5640 and OV5642 cameras on iMX6 | Freescale Community, and it can do dual record. But will encounter performance issue while playing movie.

    ------------------------------------------------------------------

    1)

    modprobe ov5640_camera_mipi

    modprobe ov5642_camera

    modprobe mxc_v4l2_capture

    gst-launch -e mfw_v4lsrc device=/dev/video0 ! mfw_ipucsc ! vpuenc codec=6 ! matroskamux ! filesink location=video0.mkv

    gst-launch -e mfw_v4lsrc device=/dev/video1 ! mfw_ipucsc ! vpuenc codec=6 ! matroskamux ! filesink location=video1.mkv

    ERROR message

    root@freescale ~$ gst-launch -e mfw_v4lsrc device=/dev/video1 ! mfw_ipucsc ! vpu

    enc codec=6 ! matroskamux ! filesink location=video1.mkv

    root@freescale ~$ MFW_GST_V4LSRC_PLUGIN 3.0.7 build on Aug 16 2013 20:15:40.

    IPU_CSC_CORE_LIBRARY_VERSION_INFOR_01.00.

    MFW_GST_IPU_CSC_PLUGIN 3.0.7 build on Aug 16 2013 20:16:04.

    Setting pipeline to PAUSED ...

    [INFO] Product Info: i.MX6Q/D/S

    vpuenc versions

    plugin: 3.0.7

    wrapper: 1.0.35(VPUWRAPPER_ARM_LINUX Build on Aug 16 2013 20:14:38)

    vpulib: 5.4.16

    firmware: 2.3.10.40778

    imx-ipuv3 imx-ipuv3.0: handler already installed on irq 0

    Error registering rot irq

    ERROR: Pipeline doesn't want to pause.

    Setting pipeline to NULL ...

    Freeing pipeline ...

    ------------------------------------------------------------------

    2) SR 1-1226100721

    The latest mxc V4L2 capture driver supports 2 cameras simultaneously.

    The below v4l2 capture unit test command lines may verify this feature on MX6 SabreSD platform:

    root@freescale /unit_tests$ ./mxc_v4l2_capture.out -iw 1024 -ih 768 -ow 1024 -oh 768 -m 8 -fr 15 -d /dev/video0 -i 1 -c 100 /test1.yuv root@freescale /unit_tests$ ./mxc_v4l2_capture.out -iw 1024 -ih 768 -ow 1024 -oh 768 -m 8 -fr 15 -d /dev/video1 -i 0 -c 100 /test2.yuv in_width = 1024, in_height = 768 out_width = 1024, out_height = 768 top = 0, left = 0 in_width = 1024, in_height = 768 out_width = 1024, out_height = 768 top = 0, left = 0

    If this will not help, please post issue on Community, our multimedia experts will try to help You there.

    ------------------------------------------------------------------

    3)

    gst-launch -e mfw_v4lsrc device=/dev/video0 ! mfw_ipucsc ! vpuenc codec=6 ! mpegtsmux ! filesink location=video0.ts

    gst-launch -e mfw_v4lsrc device=/dev/video1 ! mfw_ipucsc ! vpuenc codec=6 ! mpegtsmux ! filesink location=video1.ts

    gst-launch playbin2 uri=file:///Wife.mp4

    ERROR message

    WARNING: from element /GstPlayBin2:playbin20/GstPlaySink:playsink0/GstBin:vbin/GstAutoVideoSink:videosink/MFW_GST_V4LSINK_INFO_T:videosink-actual-sink-mfw_v4l: A lot of buffers are being dropped.

    Additional debug info:

    gstbasesink.c(2866): gst_base_sink_is_too_late (): /GstPlayBin2:playbin20/GstPlaySink:playsink0/GstBin:vbin/GstAutoVideoSink:videosink/MFW_GST_V4LSINK_INFO_T:videosink-actual-sink-mfw_v4l:

    There may be a timestamping problem, or this computer is too slow.

    ------------------------------------------------------------------

    DB:2.43:I.Mx6 Gstreamer Dual Record Fail c3


    m.C. do you have further questions? If yes plese keep working with our enginer, otherwise we will close the DI in 3 days.

    Thanks,

    Yixing

  • RELEVANCY SCORE 2.43

    DB:2.43:Windows Embedded Compact 2013 Gpu Source Code 1p



    I am facing issue with IMX6 solo with 512 MB RAM, when I run GPU sample application with 512 MB ram it crashes after ~5-10secs. But the same crash doesn't happen for 1GB RAM. I suspect the memory range used for GPU is hard coded in the driver may cause the crash issue. To debug this i need source code for GPU driver(IMX6) Windows Embedded Compact 2013.

    Can I get the source code for GPU driver (IMX6) Windows Embedded compact 2013?

    DB:2.43:Windows Embedded Compact 2013 Gpu Source Code 1p


    Hi Adeneo Embedded

    Can you help me on this issue?

  • RELEVANCY SCORE 2.42

    DB:2.42:Mipi Ov5640 Camera Interface md



    I have a imx6 Boundry saberlite board with a mipi ov5640 camera as said I enabled the ov5640 in the kernel and also did modprobe of the module but I still find in my dmesg

    ov5642_read_reg:write reg error:reg=300a camera ov5642 is not found
    ERROR: v4l2 capture: slave not found!

    ERROR: v4l2 capture: slave not found!

    I don't know why I didn't get the 0v5640 module up ...... can anyone help me.

    How can I check that the mipi camera is live and working and i donot find any thing to indicate that it is on.

    Thanks and Regards,

    Sarah Blessie

    DB:2.42:Mipi Ov5640 Camera Interface md


    I have a imx6 Boundry saberlite board with a mipi ov5640 camera as said I enabled the ov5640 in the kernel and also did modprobe of the module but I still find in my dmesg

    ov5642_read_reg:write reg error:reg=300a camera ov5642 is not found
    ERROR: v4l2 capture: slave not found!

    ERROR: v4l2 capture: slave not found!

    I don't know why I didn't get the 0v5640 module up ...... can anyone help me.

    How can I check that the mipi camera is live and working and i donot find any thing to indicate that it is on.

    Thanks and Regards,

    Sarah Blessie

  • RELEVANCY SCORE 2.42

    DB:2.42:Two Camera Interface For Imx6 7f



    hi,

    being new to this, we are looking for a microcontroller/microprocessor with the following requirements:

    1) we need to interface 2 cameras (VGA 8 bit gray scale) for stereo vision (if not simultaneously through multiplexing is it possible?).

    2) 4 PWM outputs. 3) Flash interface of 128 MB RAM 128 MB

    4) availability of evaluation board.

    5) should support Linux.

    6) I2C

    7) used for image processing. we have chosen IMx6 (freescale processor) : it seems to have 4 parallel camera interfaces will this help our purpose of stereo vision?

    it would be helpful if you could suggest some parts.

    thanks.

    DB:2.42:Two Camera Interface For Imx6 7f


    Hi,

    Mayur

    You can refer iMX6q schematics for the parts detail.

    Regards

    Saurabh

  • RELEVANCY SCORE 2.42

    DB:2.42:Stability Issue With 2 Pairs Of Twin2x2048-6400c5 And Asus P5q Se2 1f


    Hello!

    DB:2.42:Stability Issue With 2 Pairs Of Twin2x2048-6400c5 And Asus P5q Se2 1f

    Try 2.0v, but it sounds more like a motherboard issue than anything else.

  • RELEVANCY SCORE 2.42

    DB:2.42:Mjpeg Format In Uvcdevice.Cpp(I.Mx6 Android Camera Hal) 77



    iMX6 Android camera HAL from freescale does support UVC USB camera, but it just supports few V4L2 formats. We want to use USB camera which supports 720P video stream with MJPEG format. Does anyone patch UvcDevice.cpp to support MJPEG video stream?


    DB:2.42:Mjpeg Format In Uvcdevice.Cpp(I.Mx6 Android Camera Hal) 77


    Hi Fang,

    Yes, I do. But instead I wrote a simple app to access camera through Android Camera API.

    Now the camera app can work successfully under several resolutions, such as 640x480, 800x608, 1280x720, and 1600x896(all@30fps).

    (Thanks for your tip on preview issue !!)

    However, when it comes to 1920x1088@30 fps, the camera will fail.

    I kept seeing error message as below:

    E/FslCameraHAL( 2291): VPU can't output one frame after feed stream, cap and feed again, capLoop 1

    E/FslCameraHAL( 2291): VPU can't output one frame after feed stream, cap and feed again, capLoop 2

    ......

    E/FslCameraHAL( 2291): VPU can't output one frame after feed stream, cap and feed again, capLoop 100

    E/FslCameraHAL( 2291): device thread exit with frame = null, 5 buffers still in v4l

    E/FslCameraHAL( 2291): handleError handle error:2

    E/Camera2 ( 2291): Error condition 2 reported by HAL, arguments 0, 0

    Seems it failed to acquire frame at 1920x1088, do you have any thoughts or advise about this issue?

  • RELEVANCY SCORE 2.41

    DB:2.41:Ov5640 Mipi Interface Camera On A Imx6 Processor sp



    Hi,

    We are trying to interface OV5640 camera using the MIPI interface on to a iMX6 processor.

    We find that the camera is getting correctly detected in i2C with the correct I2C id (as 0x3c). We found this out by running the i2c detect command and it reports the 3C device on the i2C bus it has been connected.

    However, when booting the image (We are using the standard OV5640 device driver that is coming with Linux kernel 3.x), we get the following error message:

    ov5640_read_reg: write reg error:reg=300a

    ov5640_probe: cannot find camera

    On inspecting the code, we find that this error message is coming because of the fact either the i2c read was not successful or the value in the register address 300a was not 0x56. Since we are able to detect this device successfully in i2c detect, can we safely assume that there is no problem in reading on i2c bus?

    If this is a correct assumption, what could be the issue for this failure? Any inputs on this will be much appreciated.

    Thanks in advance

    DB:2.41:Ov5640 Mipi Interface Camera On A Imx6 Processor sp


    Hi Vasan,

    Register 0x3635 is available with OV5640 sensor. Check whether you have configured your I2C bus with proper speed, mode and time out. Default I2C speed used is 100KHz or 400KHz. Also, make sure your I2C driver is loaded before loading camera driver.

    Regards,

    Sathya Kumar P

  • RELEVANCY SCORE 2.41

    DB:2.41:Imx6 Quad Unable To Decode 720p 60fps Video Streaming Using Vpu 18



    I'm unable get picture without artifact for RTSP video streaming with H264 codec in 720p 60 fps using VPU.

    My test device is imx6 quad (CuBox-i4Pro) and have the same issue on Android 4.3, latest GeexBox(XBMC) and Debian Jessi. In all cases CPU load is about 10% and this problem exist only with RTSP stream, local video file playback is perfect.

    Does anyone have experience with network stream and imx6 decoding capability?

    DB:2.41:Imx6 Quad Unable To Decode 720p 60fps Video Streaming Using Vpu 18


    I'm unable get picture without artifact for RTSP video streaming with H264 codec in 720p 60 fps using VPU.

    My test device is imx6 quad (CuBox-i4Pro) and have the same issue on Android 4.3, latest GeexBox(XBMC) and Debian Jessi. In all cases CPU load is about 10% and this problem exist only with RTSP stream, local video file playback is perfect.

    Does anyone have experience with network stream and imx6 decoding capability?

  • RELEVANCY SCORE 2.40

    DB:2.40:Imx6 Camera Interface I/O Voltage Levels c3



    hi guys

    does imx6 camera interface I/O s are 2.8V ? or 1.8V ?

    DB:2.40:Imx6 Camera Interface I/O Voltage Levels c3


    Hi erdem

    NVCC_CSI can be from 1.65 to 3.6V

    please check Table 6 "Operating Ranges'

    IMX6DQCEC i.MX 6Dual/6Quad Applications Processors for Consumer Products - Data Sheet

    One can also check sect.4.6.2 "General Purpose I/O (GPIO) DC Parameters",

    Table 100 "21 x 21 mm Functional Contact Assignments".

    Best regards

    chip

    -----------------------------------------------------------------------------------------------------------------------

    Note: If this post answers your question, please click the Correct Answer button. Thank you!

    -----------------------------------------------------------------------------------------------------------------------

  • RELEVANCY SCORE 2.40

    DB:2.40:Stability Studies Issue 9x



    Hi,

    I am working on stability studies..When I am assigning the Inspection Plan to Physical Samples of stability studies I am getting the below error.

    How to resolve this..

    Thanks

    Kumar

    DB:2.40:Stability Studies Issue 9x


    As suggest by Kim, use CWBQM to assign strategy QSTABI to the Inspection Plan. For this select 'Q_TSK_000000000010' for the current work area. The assign Maintenance Packages for this Inspection Plan. For this select 'Q_OPR_000000000010' as the work area.

    Best Regards,

    Rahul

  • RELEVANCY SCORE 2.39

    DB:2.39:Regulators For Imx6 Ov5640 Mipi Camera On Nitrogen6x Board zf



    There are calls in the OV5640 MIPI driver to set a few regulators (io, core, and analog), and I am not sure what these are for. Looking at the Nitrogen6x schematics I don't see any programmable regulator that feeds the MIPI connector.

    #define OV5640_VOLTAGE_ANALOG 2800000#define OV5640_VOLTAGE_DIGITAL_CORE 1500000#define OV5640_VOLTAGE_DIGITAL_IO 1800000

    The calls in questions are:

    regulator_enable()

    regulator_disable()

    regulator_get()

    regulator_set_voltage()

    Could you tell me which regulators are being controlled by these calls?

    Thanks,

    DB:2.39:Regulators For Imx6 Ov5640 Mipi Camera On Nitrogen6x Board zf


    There are calls in the OV5640 MIPI driver to set a few regulators (io, core, and analog), and I am not sure what these are for. Looking at the Nitrogen6x schematics I don't see any programmable regulator that feeds the MIPI connector.

    #define OV5640_VOLTAGE_ANALOG 2800000#define OV5640_VOLTAGE_DIGITAL_CORE 1500000#define OV5640_VOLTAGE_DIGITAL_IO 1800000

    The calls in questions are:

    regulator_enable()

    regulator_disable()

    regulator_get()

    regulator_set_voltage()

    Could you tell me which regulators are being controlled by these calls?

    Thanks,

  • RELEVANCY SCORE 2.39

    DB:2.39:Qt5 Wayland Plugin On Imx6 3d



    I was trying to configure the Qtwayland plugin using qt5 on imx6 board but since the GPU of imx6 uses wayland 1.0.3 and the qtwayland plugin doesnt support wayland versions versions older than 1.1.0, i was not able to compile the plugin. Need help in resolving the issue.

    DB:2.39:Qt5 Wayland Plugin On Imx6 3d


    I was trying to configure the Qtwayland plugin using qt5 on imx6 board but since the GPU of imx6 uses wayland 1.0.3 and the qtwayland plugin doesnt support wayland versions versions older than 1.1.0, i was not able to compile the plugin. Need help in resolving the issue.

  • RELEVANCY SCORE 2.38

    DB:2.38:Stability Of Imx6 Ethernet kk



    Hi,

    We use iMX6 ethernet RMII mode, and found there's many packets lost, and ping time is very long.

    After check this article and use "enable_wait_time=off", we get the perfect short ping time.

    imx6 solo +PHY KSZ9031 ping issue

    But still many packets lost when transferring TCP data.

    ifconfig shows many RX packets errors and dropped.

    root@android:/sdcard # busybox ifconfig

    eth0 Link encap:Ethernet HWaddr 1E:ED:19:27:1A:B3

    inet addr:192.168.1.233 Bcast:192.168.1.255 Mask:255.255.255.0

    inet6 addr: fe80::1ced:19ff:fe27:1ab3/64 Scope:Link

    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

    RX packets:4890 errors:463 dropped:11 overruns:0 frame:463

    TX packets:3785 errors:0 dropped:0 overruns:0 carrier:0

    collisions:0 txqueuelen:1000

    RX bytes:6803348 (6.4 MiB) TX bytes:266483 (260.2 KiB)

    Any suggestion about the problem? Thank you!

    Below is fec configuration code --

    static struct fec_platform_data fec_data __initdata = {
    .init = mx6q_sabresd_fec_phy_init,
    .phy = PHY_INTERFACE_MODE_RMII,
    .gpio_irq = 0,
    };

    static int mx6q_sabresd_fec_phy_init(struct phy_device *phydev)
    {
    unsigned short val;
    /* Ar8031 phy SmartEEE feature cause link status generates glitch,
    * which cause ethernet link down/up issue, so disable SmartEEE
    */
    phy_write(phydev, 0xd, 0x3);
    phy_write(phydev, 0xe, 0x805d);
    phy_write(phydev, 0xd, 0x4003);
    val = phy_read(phydev, 0xe);
    val = ~(0x1 8);
    phy_write(phydev, 0xe, val);

    /* To enable AR8031 ouput a 125MHz clk from CLK_25M */
    phy_write(phydev, 0xd, 0x7);
    phy_write(phydev, 0xe, 0x8016);
    phy_write(phydev, 0xd, 0x4007);
    val = phy_read(phydev, 0xe);

    val = 0xffe3;
    val |= 0x18;
    phy_write(phydev, 0xe, val);

    /* Introduce tx clock delay */
    phy_write(phydev, 0x1d, 0x5);
    val = phy_read(phydev, 0x1e);
    val |= 0x0100;
    phy_write(phydev, 0x1e, val);

    /*check phy power*/
    val = phy_read(phydev, 0x0);

    if (val BMCR_PDOWN)
    phy_write(phydev, 0x0, (val ~BMCR_PDOWN));

    return 0;
    }

    DB:2.38:Stability Of Imx6 Ethernet kk


    Hi,

    We use iMX6 ethernet RMII mode, and found there's many packets lost, and ping time is very long.

    After check this article and use "enable_wait_time=off", we get the perfect short ping time.

    imx6 solo +PHY KSZ9031 ping issue

    But still many packets lost when transferring TCP data.

    ifconfig shows many RX packets errors and dropped.

    root@android:/sdcard # busybox ifconfig

    eth0 Link encap:Ethernet HWaddr 1E:ED:19:27:1A:B3

    inet addr:192.168.1.233 Bcast:192.168.1.255 Mask:255.255.255.0

    inet6 addr: fe80::1ced:19ff:fe27:1ab3/64 Scope:Link

    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

    RX packets:4890 errors:463 dropped:11 overruns:0 frame:463

    TX packets:3785 errors:0 dropped:0 overruns:0 carrier:0

    collisions:0 txqueuelen:1000

    RX bytes:6803348 (6.4 MiB) TX bytes:266483 (260.2 KiB)

    Any suggestion about the problem? Thank you!

    Below is fec configuration code --

    static struct fec_platform_data fec_data __initdata = {
    .init = mx6q_sabresd_fec_phy_init,
    .phy = PHY_INTERFACE_MODE_RMII,
    .gpio_irq = 0,
    };

    static int mx6q_sabresd_fec_phy_init(struct phy_device *phydev)
    {
    unsigned short val;
    /* Ar8031 phy SmartEEE feature cause link status generates glitch,
    * which cause ethernet link down/up issue, so disable SmartEEE
    */
    phy_write(phydev, 0xd, 0x3);
    phy_write(phydev, 0xe, 0x805d);
    phy_write(phydev, 0xd, 0x4003);
    val = phy_read(phydev, 0xe);
    val = ~(0x1 8);
    phy_write(phydev, 0xe, val);

    /* To enable AR8031 ouput a 125MHz clk from CLK_25M */
    phy_write(phydev, 0xd, 0x7);
    phy_write(phydev, 0xe, 0x8016);
    phy_write(phydev, 0xd, 0x4007);
    val = phy_read(phydev, 0xe);

    val = 0xffe3;
    val |= 0x18;
    phy_write(phydev, 0xe, val);

    /* Introduce tx clock delay */
    phy_write(phydev, 0x1d, 0x5);
    val = phy_read(phydev, 0x1e);
    val |= 0x0100;
    phy_write(phydev, 0x1e, val);

    /*check phy power*/
    val = phy_read(phydev, 0x0);

    if (val BMCR_PDOWN)
    phy_write(phydev, 0x0, (val ~BMCR_PDOWN));

    return 0;
    }

  • RELEVANCY SCORE 2.37

    DB:2.37:Use Two Csi The Same Time ss



    I want to use two CSI the same time on sabre-lite(OV5642[Prallel] and OV5640[MIPI]).

    Now only use a camera (OV5642 or OV5640) to capture video is OK.

    I think it could use to each IPU.

    So I modify

    static struct fsl_mxc_capture_platform_data capture_data[] = {

    {

    .csi = 0,

    .ipu = 0,

    .mclk_source = 0,

    .is_mipi = 0,

    },

    {

    .csi = 0,

    .ipu = 1,

    .mclk_source = 1,

    .is_mipi = 1,

    }

    };

    but it not useful.

    How should I go to put the camera on each IPU??? It can will work the same time.

    DB:2.37:Use Two Csi The Same Time ss


    I want to use two CSI the same time on sabre-lite(OV5642[Prallel] and OV5640[MIPI]).

    Now only use a camera (OV5642 or OV5640) to capture video is OK.

    I think it could use to each IPU.

    So I modify

    static struct fsl_mxc_capture_platform_data capture_data[] = {

    {

    .csi = 0,

    .ipu = 0,

    .mclk_source = 0,

    .is_mipi = 0,

    },

    {

    .csi = 0,

    .ipu = 1,

    .mclk_source = 1,

    .is_mipi = 1,

    }

    };

    but it not useful.

    How should I go to put the camera on each IPU??? It can will work the same time.

  • RELEVANCY SCORE 2.37

    DB:2.37:How To Let Kernel (3.0.35) Support Parallel 2 (Adv7180) +Mipi Csi(Ov5640) sz



    Hi:

    all

    My os :android 4.2.2

    IPU(1 , 2) csi (0 , 1)

     parallel 2 (adv7180)  : ipu 2 - csi1

    mipi csi(ov5640) : ipu 1 - csi1 v_channel = 1

    I want to Connect parallel 2 (adv7180) +mipi csi(ov5640) , But how to configure the kernel ?

  • RELEVANCY SCORE 2.36

    DB:2.36:Ov5642 Camera Not Working With Ltib aa



    Hi community,

    I am using ov5642 camera with imx6q(sabrelite Board.). I have been using ov5642 camera with ltib file system. It was working fine some months back. But now It is not camera is not working with ltib root file system. Same hardware I have tried with fsl-image-gui image builded by yocto. Camera works fine over there. As per I know this problem is related to kernel it's respective modules so I do two experiments.

    1) I have cross-compile linux-imx6-boundary-imx_3.0.35_1.1.1 kernel with camera modules explicitly tested on ltib file system. camera still does not work.

    2) I have copied yocto's kernel modules in ltib file system. camera works perfectly.

    does any one face this issue earlier ?

    any suggestion will help me alot.

    Thanks ,

    Pratik

    DB:2.36:Ov5642 Camera Not Working With Ltib aa


    Hi community,

    I am using ov5642 camera with imx6q(sabrelite Board.). I have been using ov5642 camera with ltib file system. It was working fine some months back. But now It is not camera is not working with ltib root file system. Same hardware I have tried with fsl-image-gui image builded by yocto. Camera works fine over there. As per I know this problem is related to kernel it's respective modules so I do two experiments.

    1) I have cross-compile linux-imx6-boundary-imx_3.0.35_1.1.1 kernel with camera modules explicitly tested on ltib file system. camera still does not work.

    2) I have copied yocto's kernel modules in ltib file system. camera works perfectly.

    does any one face this issue earlier ?

    any suggestion will help me alot.

    Thanks ,

    Pratik

  • RELEVANCY SCORE 2.36

    DB:2.36:Imx6 Otg Port Is Not Functioning After Some Time js



    We are operating iMX6 USB OTG port in device mode. We are able to connect the host device and start the transfer.

    But after few seconds of working, imx6 USB OTG port is not responding to IN packet sent by Host device.

    Based on our understanding, USB device controller should send atleast the NAK packet for the IN token from the Host?

    Are there any known issues in imx6? Could you please advise on how to debug this issue further?

    Are there any test daemons available to check the USB transfer between PC and imx6 USB device?

    DB:2.36:Imx6 Otg Port Is Not Functioning After Some Time js


    We are operating iMX6 USB OTG port in device mode. We are able to connect the host device and start the transfer.

    But after few seconds of working, imx6 USB OTG port is not responding to IN packet sent by Host device.

    Based on our understanding, USB device controller should send atleast the NAK packet for the IN token from the Host?

    Are there any known issues in imx6? Could you please advise on how to debug this issue further?

    Are there any test daemons available to check the USB transfer between PC and imx6 USB device?

  • RELEVANCY SCORE 2.36

    DB:2.36:Enable Mipi Interface In Imx6 Wand Board pa



    hi all,

    I am using the i.MX6 solo wandboard, in that i need to enable the mipi interface for sensor ov5640, can any one guide me on how to enable the mipi in wand board, i am new to this MIPI

    BOARD: i.MX6 SOLO Wand board

    SENSOR: OV5640 [omnivision]

    Thanks,

    shan

    DB:2.36:Enable Mipi Interface In Imx6 Wand Board pa


    hi all,

    I configured the i2c for mipi interface in imx6 board, but i cant able to configure the MCLK for mipi can any one tell me how to configure the mclk, i am new to this mipi interface , any suggestions will be more helpfull to me

    Thanks,

    shan

  • RELEVANCY SCORE 2.36

    DB:2.36:Ov5640_Mipi On Bd-Sl-I.Mx6 c8



    Hi,

    I'm testing ov5640 mipi camera module on a BoundaryDevices BD-SL-i.MX6 board with BSP 3.0.35 builded by Yocto for nitrogen6x MACHINE. Standing at camera format and frame rate specifics I should obtain 30fps with 1920x1080 format or 45fps with 1280x960 format but I check a very slower fps (10fps). I'm checking it with a user level application interfacing with v4l2 and getting captured frame with VIDIOC_DQBUF ioctl (V4L2_MEMORY_MMAP). I have built kernel without apply any change to ov5640_mipi.c driver; have I to modify something to increase fps?

    Could someone give me any hints to verify that issue?thank you for the attention,

    best regards

    Andrea

    DB:2.36:Ov5640_Mipi On Bd-Sl-I.Mx6 c8


    Hi,

    I'm testing ov5640 mipi camera module on a BoundaryDevices BD-SL-i.MX6 board with BSP 3.0.35 builded by Yocto for nitrogen6x MACHINE. Standing at camera format and frame rate specifics I should obtain 30fps with 1920x1080 format or 45fps with 1280x960 format but I check a very slower fps (10fps). I'm checking it with a user level application interfacing with v4l2 and getting captured frame with VIDIOC_DQBUF ioctl (V4L2_MEMORY_MMAP). I have built kernel without apply any change to ov5640_mipi.c driver; have I to modify something to increase fps?

    Could someone give me any hints to verify that issue?thank you for the attention,

    best regards

    Andrea

  • RELEVANCY SCORE 2.35

    DB:2.35:Imx53 Encode 720p And Display 320x200 Problem a8



    Hi All,

    Available setup with me: IMX53 QSB + ov5640 sensor board in parallel interface.

    Is there any limitation from imx53 side that encoding camera frames from ov5640 at 720p@30fps and display the resolutions at 320x200 ?

    With my setup, i get a frame Hsync issues while encoding 720p format. But if i encode and display 480p works good in my setup.

    I have slightly modified imx-test-11.09.01/test/mxc_vpu_test code to suite for my requirement. And Following config file is used

    operation=1

    input=

    format=2

    chromaInterleave=

    rotation=

    count=1000

    deblock=

    dering=

    mirror=

    width=1280

    height=720

    bitrate=0

    gop=0

    end

    DB:2.35:Imx53 Encode 720p And Display 320x200 Problem a8


    Hi All,

    Available setup with me: IMX53 QSB + ov5640 sensor board in parallel interface.

    Is there any limitation from imx53 side that encoding camera frames from ov5640 at 720p@30fps and display the resolutions at 320x200 ?

    With my setup, i get a frame Hsync issues while encoding 720p format. But if i encode and display 480p works good in my setup.

    I have slightly modified imx-test-11.09.01/test/mxc_vpu_test code to suite for my requirement. And Following config file is used

    operation=1

    input=

    format=2

    chromaInterleave=

    rotation=

    count=1000

    deblock=

    dering=

    mirror=

    width=1280

    height=720

    bitrate=0

    gop=0

    end

  • RELEVANCY SCORE 2.35

    DB:2.35:Camera Preview Not Working On Imx6 Sololite Android 4.04 p8



    Hi i am working on imx6 solo lite custom board which contains a monochrome parallel interface camera sensor. i am using android 4.04 bsp for this.

    When trying to enable camera preview i am able to get the frame from the driver but i am not able to get camera preview through camera app. i am using standard camera hal provided with android 4.04 with Anativewindow concept. While debuging i found i am able to get the buffer in camera hal but when i am trying to enqueue the buffer to display adapter i am getting this error E/SurfaceTexture( 2102): [SurfaceView] error creating EGLImage: 0x300c please help me out, i am totally clueless about the issue. i am attaching the detail log.

    DB:2.35:Camera Preview Not Working On Imx6 Sololite Android 4.04 p8


    Hi i am working on imx6 solo lite custom board which contains a monochrome parallel interface camera sensor. i am using android 4.04 bsp for this.

    When trying to enable camera preview i am able to get the frame from the driver but i am not able to get camera preview through camera app. i am using standard camera hal provided with android 4.04 with Anativewindow concept. While debuging i found i am able to get the buffer in camera hal but when i am trying to enqueue the buffer to display adapter i am getting this error E/SurfaceTexture( 2102): [SurfaceView] error creating EGLImage: 0x300c please help me out, i am totally clueless about the issue. i am attaching the detail log.

  • RELEVANCY SCORE 2.35

    DB:2.35:Ov5640 Mipi I2c Access Error With 3.10.53 Kernel d3


    Hi all,
    Yesterday I upgraded my kernel from 3.10.17_1.0.0_ga (boundary devices github) to 3.10.53_1.1.0_ga-pass1 (always boundary devices github).
    But unfortunately I can't use my OV5640 mipi camera with the newest kernel (it works with the 3.10.17) : I've got an i2c access error :
    ov5642_read_reg:write reg error:reg=300a

    I made some logs in the imx i2c driver (driver/i2c/busses/i2c-imx.c), and the problem is with the i2c_imx_acked() function, in the beginning of the i2c_imx_write() function.

    Is anyone know what is the problem ? With the same board and 3.10.17 kernel it works !
    Thank you for your help !
    Jerome

    DB:2.35:Ov5640 Mipi I2c Access Error With 3.10.53 Kernel d3

    Hi all,
    Yesterday I upgraded my kernel from 3.10.17_1.0.0_ga (boundary devices github) to 3.10.53_1.1.0_ga-pass1 (always boundary devices github).
    But unfortunately I can't use my OV5640 mipi camera with the newest kernel (it works with the 3.10.17) : I've got an i2c access error :
    ov5642_read_reg:write reg error:reg=300a

    I made some logs in the imx i2c driver (driver/i2c/busses/i2c-imx.c), and the problem is with the i2c_imx_acked() function, in the beginning of the i2c_imx_write() function.

    Is anyone know what is the problem ? With the same board and 3.10.17 kernel it works !
    Thank you for your help !
    Jerome

  • RELEVANCY SCORE 2.35

    DB:2.35:V4l2 Camera Capture On Imx6 Cannot Capture Rgb24 Correctly ss



    Using SabreSD imx6q evaluation board and trying to capture data with V4L2_PIX_FMT_RGB24, and it does seem to work when I use the ipu_prp_enc.c. driver, however when I use the ipu_csi_enc.c driver the colours are quite wrong?

    I seem to be able to get correct colour if I use the V4L2_PIX_FMT_YUYV pixel format when using both drivers.

    Is this a known issue. I using kernel L3.0.35.

    DB:2.35:V4l2 Camera Capture On Imx6 Cannot Capture Rgb24 Correctly ss


    I have now build the latest Yocto based BSP with Linux 3.10.17 and the problem is still present.

    It does seem to me that the ipu_csi_enc.c driver although it accepts V4L2_PIX_FMT_RGB24 capture format it does not seem able to support it properly. The only format that seems to work is V4L2_PIX_FMT_YUYV.

  • RELEVANCY SCORE 2.34

    DB:2.34:Android Camera Mipi Driver For Gc2035 Galaxycore dd



    Hello,

    I'm developing on a board imx6 Dual Lite with Android 4.2. I would like to integrate the driver of a new camera and I was wondering if any of you had never integrated in Android this type of camera: "GalaxyCore gc2035 sensor" ?

    Thank you in advance!

    DB:2.34:Android Camera Mipi Driver For Gc2035 Galaxycore dd


    Hello,

    thanks for reply.

    I would ask you if there is a guide to integrate generic Camera mipi sensor into imx with Android ?

    Thank you in advance!

  • RELEVANCY SCORE 2.34

    DB:2.34:Linphone 3.7.0 On Imx6q: Black Screen On The Self View. s1



    So, I am trying to use this linphone 3.7.0 on my Sabre platform for smart devices with OV5640 mipi camera.

    I have done these steps:

    1. Compile Linux BSP 4.0.1 3.0.35 from freescale

    2. Compile linphone, ortp, mediastreamer2 for imx6q

    3. Launch linphone, using "linphonec -V -d 3"

    The problem is that I can see nothing on a self view (only a black screen). It seems like issue in Xv library which I have taken from freescale Ubuntu image (Linux BSP has not this library)

    This phrase I see in linphone debug:

    "ortp-error-Could not find suitable format or Xv port to work with."

    I have attached the linphone log.

    So, from this point I need some help to understand a causes of this problem. And I will appreciate for any advices!

    Thanks...

    DB:2.34:Linphone 3.7.0 On Imx6q: Black Screen On The Self View. s1


    OK, thanks.

    "If you think you understand computers, you're clearly not an expert"

    [Murphy's laws]

  • RELEVANCY SCORE 2.34

    DB:2.34:Hdmi On Imx6 Dual Lite mx



    Hi,

    We are working on imx6 DL with chip version 1.1 and in HDMI.

    We need stand alone code for testing the HDMI in imx6 dual lite.

    We have another imx6q reference platforms and our code works on that platforms.

    So we need the Difference between imx6q and imx6 DL with respect to HDMI.

    or Provide us the Standalone code HDMI Code works on imx6 DL for reference.

    We will use that code for our development..

    We are testing 1080p on hdmi and the same code works on imx6q and if use it in imx6dl and clock is different we got then we modifed the clock

    source now we got the clock 148mhz so clock also proper now but we HDMI is not working still.

    Please guide us how to fix this issue.

    Thanks.

    DB:2.34:Hdmi On Imx6 Dual Lite mx

    Xindong Yu Jun 16, 2013 11:35 PM (in response to imxcommunityscout)
    Suppose MX6DL no board level issue and the HDMI setting is same as MX6Q,
    the HDMI failed work should cause by IPU setting or some board specific setting.
    Please check with followed process:
    1. Please check DI setting in GPR3, MX6DL only have one IPU.
    2. Pixel clock, for 1080p60 the pixel clock is 148.5MHz,
    and the pixel clock should enabled before HDMI PHY configuration.
    3. Make sure clock hdmi_isfr and hdmi_iahb is enabled.
    4. Please check other display such as LVDS panel can work in MX6DL platform.

    If all above setting is right, please double check HDMI setting, dump the MX6DL and MXQ HDMI register and compare it one by one.

  • RELEVANCY SCORE 2.34

    DB:2.34:Find Luminance Value - Imx6 Ov5640 7s



    Hello Friends,

    I have Sabrelite BD-SL-i.MX6 board from boundary devices.

    I have ov5640 camera (Image Sensor).

    Now I want to know the luminance value from the sensor in my application.

    What is the way to go ahead on this.? How should i get luminance value.

    Please suggest me a way to this.

    DB:2.34:Find Luminance Value - Imx6 Ov5640 7s


    Hello Friends,

    I have Sabrelite BD-SL-i.MX6 board from boundary devices.

    I have ov5640 camera (Image Sensor).

    Now I want to know the luminance value from the sensor in my application.

    What is the way to go ahead on this.? How should i get luminance value.

    Please suggest me a way to this.

  • RELEVANCY SCORE 2.34

    DB:2.34:Imx6 Development Board xk



    Hello All,

    Please suggest iMX6 development board having 16 bit parallel port for camera interface.

    Thanks Regards,

    Pankaj

    DB:2.34:Imx6 Development Board xk


    Hello All,

    Please suggest iMX6 development board having 16 bit parallel port for camera interface.

    Thanks Regards,

    Pankaj

  • RELEVANCY SCORE 2.34

    DB:2.34:Imx6 Linux Sdio Detection Issue ak



    We are using Sabre-Lite imx6 boards from boundary devices. As we insert SDIO module in MMC/SD slot, the Linux kernel 3.10 tries to initialize the card by negotiating frequency-voltage but it eventually times out (-110 error). But the same SDIO card is successfully initialized on PC host running Ubuntu kernel 3.8. Please find the command-sequence log after enabling MMC debug in kernel for both Ubuntu PC and imx6 board.

    In the logs, i see that Ubuntu PC kernel is able to initialize the SDIO card at frequency 128.906 kHz and all higher frequency values results in command timeout. However, in case of imx6 Linux kernel, some commands seem to generate CRC errors (-84) and other commands results in timeout (-110). Also, in imx6 log i see that, CMD0 and CMD5 seem to succeed at 400KHz but further commands timeout. This behavior is not observed in case of Ubuntu PC kernel where all commands timeout until operating frequency 128.906 kHz. The imx6 kernel does not appear to support 128.906 kHz and instead seems to use 100 kHz.

    Can anyone please suggest ways to successfully initialize the device.

    The kernel source for the board i am using is boundarydevices/linux-imx6 at boundary-imx_3.10.17_1.0.0_ga GitHub

    DB:2.34:Imx6 Linux Sdio Detection Issue ak


    We are using Sabre-Lite imx6 boards from boundary devices. As we insert SDIO module in MMC/SD slot, the Linux kernel 3.10 tries to initialize the card by negotiating frequency-voltage but it eventually times out (-110 error). But the same SDIO card is successfully initialized on PC host running Ubuntu kernel 3.8. Please find the command-sequence log after enabling MMC debug in kernel for both Ubuntu PC and imx6 board.

    In the logs, i see that Ubuntu PC kernel is able to initialize the SDIO card at frequency 128.906 kHz and all higher frequency values results in command timeout. However, in case of imx6 Linux kernel, some commands seem to generate CRC errors (-84) and other commands results in timeout (-110). Also, in imx6 log i see that, CMD0 and CMD5 seem to succeed at 400KHz but further commands timeout. This behavior is not observed in case of Ubuntu PC kernel where all commands timeout until operating frequency 128.906 kHz. The imx6 kernel does not appear to support 128.906 kHz and instead seems to use 100 kHz.

    Can anyone please suggest ways to successfully initialize the device.

    The kernel source for the board i am using is boundarydevices/linux-imx6 at boundary-imx_3.10.17_1.0.0_ga GitHub

  • RELEVANCY SCORE 2.34

    DB:2.34:How To Use Gstreamer With Opencv dc



    Hi all,

    I'm working with Sabre Lite board and the OV5640 camera module, both from Boundary Devices, and I need to process video using OpenCV.

    But I was informed that this camera can't work with OpenCV because its driver works with a Freescale version of V4L2 and not with the standard one.

    I found some discussions about use GStreamer with OpenCV (with Qt and OpenGL too) in others cases.

    I would like to know if it's possible to use GStreamer's library to capture video from this camera and transfer the frames to OpenCV for a video processing.

    Thanks,

    Bruno

    DB:2.34:How To Use Gstreamer With Opencv dc


    Hi Andr,

    Sorry for being late, but I was busy and I had to use a USB camera for my project.

    I had seen this code on your blog and I got some errors when I tried to compile it.

    Now I have time to read better your code and I will test it on Sabre Lite.

    Thank you for your work,

    Bruno

  • RELEVANCY SCORE 2.34

    DB:2.34:Does Imx6 Mipi Csi-2 Support Camera Sensors With "Non-Continuous" Clock Mode? 7j



    Hi everybody,

    I'm going to start my custom mipi camera sensor.

    My transmitter supports "non-continuous" clock mode (clock lane goes in LP11 during H and V blanking).

    I made a test with SabreLite and ov5640 mipi: connecting oscilloscope on sensor output clock, it looks continuous every time (exept when it leaves power down state).

    Do you know if iMX6 MIPI CSI-2 supports "non-continuous" clock mode?

    Looking on "MIPI Alliance Specification for Camera Serial Interface 2 (CSI-2)", I found the following sentence:

    "All CSI-2 transmitter and receivers shall support continuous clock behaviour on the Clock Lane, and optionally may support non-continuous clock behaviour".

    many thanks.

    DB:2.34:Does Imx6 Mipi Csi-2 Support Camera Sensors With "Non-Continuous" Clock Mode? 7j

    Hello Sergio,

    thank you anyway. I worked with the engineer that manage the source (as I say you before, I'm not an expert in FPGA) and we are able now to produce a mipi stream with continuous clock. I saw the first image!!
    I didn't fix all my issues but, right now, the most important thing is that the low level is ok. Now, I have some problems on data path MIPI_PHY -- gasket -- CSI -- SMFC -- IDMAC and I get an image with wrong sizes. The image should be a 1280x960pix but I captured four 640x480. I think there is something wrong in the BPP,NPB setting. I'm going to read some post. If I'll not be able to find a solution, probably I'll need to post a new thread.
    Thank you.

  • RELEVANCY SCORE 2.33

    DB:2.33:Imx6 Video Capture Driver Not Using V4l2 Subdev 1f



    I noticed neither BSP4.1.0 nor Yocto Dora is using v4l2_subdev for i2c camera sensors. am I missing something?

    DB:2.33:Imx6 Video Capture Driver Not Using V4l2 Subdev 1f


    We dont support the v4l2subdev in our current kernel.

    We should update the drivers to use the v4l2-subdev, but there is no a timeline for that yet.

  • RELEVANCY SCORE 2.33

    DB:2.33:Whether I.Mx6 Solo Supports Ov9712 Camera Sensor With Doesn't Have Isp Support. 3k



    Hello,

    I am using I.MX6 solo processor for parallel camera interface with OV9712 sensor.

    As per the sensor data sheet i understood that sensor doesn't have ISP. In this case how can i use this sensor with i.mx6 solo.

    Previously we worked with OV5640 which has ISP support.

    When we don't have ISP support in OV9712, how to configure ISP in processor side.

    Attached function block diagram of OV9712.

    Thanks and Regards,

    Vishwanath

    DB:2.33:Whether I.Mx6 Solo Supports Ov9712 Camera Sensor With Doesn't Have Isp Support. 3k


    Hello,

    Thank you for your post, however please consider moving it to the right community place (e.g. i.MX Community ) to get it visible for active members.

    For details please see general advice Where to post a Discussion?

    Thank you for using Freescale Community.

  • RELEVANCY SCORE 2.33

    DB:2.33:Yocto Build Problem With Nitrogen6x Configured To Include Mipi Camera x8



    I am trying to build Yocto for BoundaryDevices nitrogen6x. I was able to build and test this a couple of months ago. This week I checked out a fresh copy and tried to build fsl-image-gui, and I am getting this error:

    ERROR: csi_dmareq_rff_enable [drivers/media/video/mxc/capture/csi_v4l2_capture.ko] undefined!

    | ERROR: csi_dmareq_rff_disable [drivers/media/video/mxc/capture/csi_v4l2_capture.ko] undefined!

    | ERROR: csi_regbase [drivers/media/video/mxc/capture/csi_v4l2_capture.ko] undefined!

    | make[1]: *** [__modpost] Error 1

    | make: *** [modules] Error 2

    I have enabled CSI camera support because I am configuring the build to include a MIPI camera (ov5640).

    Any idea what the problem might be?

    Thanks,

    DB:2.33:Yocto Build Problem With Nitrogen6x Configured To Include Mipi Camera x8


    I resolved the issue by removing CSI camera support (Device Drivers-Multimedia support-Video capture adapters-MXC Camera/V4L2 PRP Features support). I had enabled it thinking it was needed for MIPI input.

    Why CSI camera support is not needed? I thought both CSI2/MIPI and parallel cameras go through CSI input.

  • RELEVANCY SCORE 2.32

    DB:2.32:Response On Imx6 Solo Board Is Deadly Slow 88



    Hi,

    I got wandboard with IMX6 solo processor on it, it had Ubuntu 11.04 version OS image built on it.

    MY IMX6 board is responding very slowly and cannot open GUI at all.

    Sometimes I see mmcqd/0 process is consuming too much of CPU.

    Can anybody suggest me in resolving this issue.

    Thanks,

    Swaraj

    DB:2.32:Response On Imx6 Solo Board Is Deadly Slow 88


    I'm not familiar with the wandboard but probably the BSP is not enabled for graphics acceleration, since the CPU is working at full it could be that it is doing all the graphics processing by software rather than hardware.

    Have you checked on the wandboard forums to check if their BSP has an update?

  • RELEVANCY SCORE 2.32

    DB:2.32:Imx6 Dual Processor Issue 1x



    I am using IMX6 Dual processor in my current project.

    My PCB Size is 1mm thick,When i power up the system processor heats too much within 5-10 minutes.

    Is this normal issue or something to worry about.Please guide me.

    DB:2.32:Imx6 Dual Processor Issue 1x


    Hi Ronak

    you can measure current in both cases and compare.

    Best regards

    igor

  • RELEVANCY SCORE 2.32

    DB:2.32:Extra Voltage For Imx6 Sabresd - Will It Cause Issue For Derivative Boards? dk



    Looking over the android BSP provided by freescale for the imx6q sabresd board, I find that the VGEN3 output is increased from 2.5 to 2.8v and VGEN5 output increased from 2.8 to 3.0v in uboot. This file;

    board/freescale/mx6q_sabresd/mx6q_sabresd.c { funciton "static int setup_pmic_voltages(void)" }

    The comments in code provide the following explanation;

    /*For camera streaks issue,swap VGEN5 and VGEN3 to power camera.
    *sperate VDDHIGH_IN and camera 2.8V power supply, after switch:
    *VGEN5 for VDDHIGH_IN and increase to 3V to align with datasheet
    *VGEN3 for camera 2.8V power supply
    */
    /*increase VGEN3 from 2.5 to 2.8V*/
    if (i2c_read(0x8, 0x6e, 1, value, 1)) {
    printf("Read VGEN3 error!\n");
    return -1;
    }
    value = ~0xf;
    value |= 0xa;
    if (i2c_write(0x8, 0x6e, 1, value, 1)) {
    printf("Set VGEN3 error!\n");
    return -1;
    }
    /*increase VGEN5 from 2.8 to 3V*/
    if (i2c_read(0x8, 0x70, 1, value, 1)) {
    printf("Read VGEN5 error!\n");
    return -1;
    }
    value = ~0xf;
    value |= 0xc;
    if (i2c_write(0x8, 0x70, 1, value, 1)) {
    printf("Set VGEN5 error!\n");
    return -1;
    }

    DB:2.32:Extra Voltage For Imx6 Sabresd - Will It Cause Issue For Derivative Boards? dk


    On the SDP design VGEN3 (from PF0100) may be selected (via R85) to provide supply voltage GEN_2V5 for i.MX6 SATA, HDMI, MIPI, PCIe, LVDS modules.

    Strictly speaking, according to the i.MX6 Datasheet, corresponding voltages should be in range 2.25 (2.325) - 2.75 V. Therefore 2.8V is out of specified range.

    But resistor R85 is not populated by default, therefore such option (VGEN3 - GEN_2V5) really is not used.

    For customers designs it may be recommended to double check if VDDHIGH_CAP feeds GEN_2V5, as on the SDP.

  • RELEVANCY SCORE 2.32

    DB:2.32:Can't Connect To The Camera mz



    Hi,

    I am working on MCIMX6DL-SDP board which has android 4.0.4 running on it. The Android O.S. came pre - installed along with the board in the NOR flash and I am using NAND boot. The OS build number is R13.4-beta. When I connect a logitech usb camera to the board, I can see the following messages getting displayed on my minicom console:

    uvcvideo: Found UVC 1.00 device unnamed (046d:0825)
    input: UVC Camera (046d:0825) as /devices/platform/fsl-ehci.0/usb1/1-1/1-1:1.0/8

    3:3:1: cannot get freq at ep 0x86

    Also, I do see a video node appearing in the 'dev' directory, every time I connect the camera to the board, displayed as "video2". Hence, I assume that the external camera is getting detected. However, When I try to launch the built in Camera app, it says "Can't connect to camera". Also, I can see the following error on my minicom console:

    ERROR: v4l2 capture: slave not found!

    The logcat -v time messages which I receive at the time of launching the camera app are as follows:

    01-01 00:00:03.300 I/imx6.gralloc( 2203): disp_mode is D:1024x768p-60

    01-01 00:00:03.300 I/AudioFlinger( 2206): Loaded primary audio interface from LEGACY Audio HW HAL (audio)

    01-01 00:00:03.300 I/AudioFlinger( 2206): Using 'LEGACY Audio HW HAL' (audio.primary) as the primary audio interface

    01-01 00:00:03.300 I/CameraService( 2206): CameraService started (pid=2206)

    01-01 00:00:03.310 I/FslCameraHAL( 2206): Face Back Camera is ov5640_mipi, orient is 0

    01-01 00:00:03.310 I/FslCameraHAL( 2206): Face Front Camera is ov5642, orient is 0

    01-01 00:00:03.320 W/audio_hw_primary( 2206): open output stream devices 2, format 0, channels 0, sample_rate 0

    01-01 00:00:03.320 I/AudioFlinger( 2206): AudioFlinger's thread 0xc9488 ready to run

    01-01 00:00:03.320 W/AudioFlinger( 2206): Thread AudioOut_1 cannot connect to the power manager service

    01-01 00:00:03.320 W/AudioFlinger( 2206): Thread AudioOut_1 cannot connect to the power manager service

    01-01 00:00:03.320 W/audio_hw_primary( 2206): out_set_parameters routing=2, ret 1

    01-01 00:00:03.320 I/AudioPolicyService( 2206): Loaded audio policy from LEGACY Audio Policy HAL (audio_policy)

    01-01 00:00:03.330 W/imx6.gralloc( 2203): 32bpp setting of Framebuffer catched!

    01-01 00:00:03.380 W/imx6.gralloc( 2203): using (fd=12)

    01-01 00:00:03.380 W/imx6.gralloc( 2203): id = DISP3 BG - DI1

    01-01 00:00:03.380 W/imx6.gralloc( 2203): xres = 1024 px

    01-01 00:00:03.380 W/imx6.gralloc( 2203): yres = 768 px

    01-01 00:00:03.380 W/imx6.gralloc( 2203): xres_virtual = 1024 px

    01-01 00:00:03.380 W/imx6.gralloc( 2203): yres_virtual = 2304 px

    01-01 00:00:03.380 W/imx6.gralloc( 2203): bpp = 32

    01-01 00:00:03.380 W/imx6.gralloc( 2203): r = 16:8

    01-01 00:00:03.380 W/imx6.gralloc( 2203): g = 8:8

    01-01 00:00:03.380 W/imx6.gralloc( 2203): b = 0:8

    01-01 00:00:03.380 W/imx6.gralloc( 2203): width = 163 mm (159.568100 dpi)

    01-01 00:00:03.380 W/imx6.gralloc( 2203): height = 122 mm (159.895081 dpi)

    01-01 00:00:03.380 W/imx6.gralloc( 2203): refresh rate = 60.00 Hz

    01-01 00:00:03.440 D/libEGL ( 2203): loaded /system/lib/egl/libGLES_android.so

    01-01 00:00:03.450 D/libEGL ( 2203): loaded /system/lib/egl/libEGL_VIVANTE.so

    01-01 00:00:03.480 D/libEGL ( 2203): loaded /system/lib/egl/libGLESv1_CM_VIVANTE.so

    01-01 00:00:03.510 D/libEGL ( 2203): loaded /system/lib/egl/libGLESv2_VIVANTE.so

    01-01 00:00:03.520 W/SurfaceFlinger( 2203): ro.sf.lcd_density not defined, using 160 dpi by default.

    01-01 00:00:03.530 I/SurfaceFlinger( 2203): EGL informations:

    01-01 00:00:03.530 I/SurfaceFlinger( 2203): # of configs : 45

    01-01 00:00:03.530 I/SurfaceFlinger( 2203): vendor : Vivante Corporation

    01-01 00:00:03.530 I/SurfaceFlinger( 2203): version : 1.4

    01-01 00:00:03.530 I/SurfaceFlinger( 2203): extensions: EGL_KHR_reusable_sync EGL_KHR_fence_sync EGL_KHR_image_base EGL_KHR_image_pixmap EGL_KHR_image EGL_KHR_gl_textue

    01-01 00:00:03.530 I/SurfaceFlinger( 2203): Client API: OpenGL_ES OpenVG

    01-01 00:00:03.530 I/SurfaceFlinger( 2203): EGLSurface: 8-8-8-8, config=0xd

    01-01 00:00:03.530 I/SurfaceFlinger( 2203): OpenGL informations:

    01-01 00:00:03.530 I/SurfaceFlinger( 2203): vendor : Vivante Corporation

    01-01 00:00:03.530 I/SurfaceFlinger( 2203): renderer : GC880 Graphics Engine

    01-01 00:00:03.530 I/SurfaceFlinger( 2203): version : OpenGL ES-CM 1.1

    01-01 00:00:03.530 I/SurfaceFlinger( 2203): extensions: GL_OES_blend_equation_separate GL_OES_blend_func_separate GL_OES_blend_subtract GL_OES_byte_coordinates GL_OES_!

    GL_OES_packed_depth_stencil GL_EERROR: v4l2 capture: slave not found!

    XT_texture_format_BGRA8888 GL_IMG_read_format GL_IMG_user_clip_plane GL_APPLE_texture_2D_limited_npot GL_EXT_texture_lod_bias GL_EXT_blend_minmax GL_EXT_read_format_bg8

    01-01 00:00:03.530 I/SurfaceFlinger( 2203): GL_MAX_TEXTURE_SIZE = 8192

    01-01 00:00:03.530 I/SurfaceFlinger( 2203): GL_MAX_VIEWPORT_DIMS = 2048 x 2048

    01-01 00:00:03.530 I/SurfaceFlinger( 2203): flags = 00090000

    01-01 00:00:03.560 I/v_hwc ( 2203): Vivante HWComposer v2.2

    01-01 00:00:03.560 I/v_hwc ( 2203): Device: 0x1b4fb90

    01-01 00:00:03.560 I/v_hwc ( 2203): Separated 2D: YES

    01-01 00:00:03.560 I/v_hwc ( 2203): 2D PE20: YES

    01-01 00:00:03.560 I/v_hwc ( 2203): Filter-stretch blit: YES

    01-01 00:00:03.560 I/v_hwc ( 2203): 2D dither enabled : YES

    01-01 00:00:03.560 I/v_hwc ( 2203): Multi-source blit: NO

    01-01 00:00:03.560 I/v_hwc ( 2203): Multi-source blit Ex: NO

    01-01 00:00:03.560 I/v_hwc ( 2203): OPF/YUV blit/Tiling : NO

    01-01 00:00:03.650 D/libEGL ( 2286): loaded /system/lib/egl/libGLES_android.so

    Do I need to apply some patch and rebuild the android kernel in order to get the external camera working..?

    Can anybody help me getting this issue resolved. I am working on an android video calling application and hence, need the usb camera to work on the development platform.

    Best regards,

    Sumit

    DB:2.32:Can't Connect To The Camera mz


    Hi Saurabh,

    Thanks for the reply.

    Yes, you are correct. I did go through the Android Advanced User Guide which came with the android release package and found that it has a separate section for USB Camera support which talks about the modifications you suggested and plus few others as well.

    I will update the status once I have tried it out.

    Best regards,

    Sumit

  • RELEVANCY SCORE 2.32

    DB:2.32:Ipu_Csi_Mipi dp



    Hi, All!

    I'm new developer of iMX6 system. I have few questions related to IPU CSI interface connection.

    In the IMX6DQRM manual, chapter 37, says iMX6 has two CSI(Camera Sensor Interface) ports and in section 37.1.2.1.1, it mentions that the interface types of each Camera port can be Parallel or High-speed serial interface - MIPI CSI-2.

    I can find one set of MIPI-CSI2 Camera port from Chapter 40, but cannot find the MIPI-CSI2 pins for the second port.

    Is there any one can help me to identify them?

    Thanks in advance!

    Best Regards,

    Andy Guo

    DB:2.32:Ipu_Csi_Mipi dp


    In reverse, Is the image data received from MIPI-CSI2 port(describe at chapter 40) be pass to one of CSI module of IPU?

    Thanks in advance!

    Andy Guo

  • RELEVANCY SCORE 2.32

    DB:2.32:Hauppauge 950q Usb Tv Tuner Is Not Functioning Correctly With Gstreamer On Imx6 fp



    Hi,

    I'm working on an iMX6 project that inputs HDTV via USB or mini PCIe TV tuner card. The first TV tuner I got is Hauppauge 950Q. I followed the instruction from our Freescale FAE.

    ==
    The instructions on how he enabled the device are below for your reference but wanted to share a couple other comments
    used the I.MX6 Quad version only because that is what comes on the Freescale Sabre boardthe CPU load was high when starting up the device and loading the firmware but very low once the device was up and running, playing back TV. I also asked him if he thinks there would be any performance concern with using an MX6 Dual and he had no concern.performance using the tuner tied to the I.MX6 Sabre board seemed the same as when plugged into his linux PC. He was pulling in TV with over the air antenna
    Here are the implementation details.
    I had to enable 3 drivers: Xceive XC5000, Auvitek AU8522, Auvitek AU0828.

    I used a barebones Linux: no need for a full Ubuntu distribution.

    Here are the steps:
    1) Build latest LTIB Linux BSP (L3.0.35_4.1.0) with all of gstreamer packages and support
    2) Force LTIB to Configure the Kernel
    3) Within the Kernel Sub-Menu, select:
    Device Drivers Multimedia support * DVB for Linux Device Drivers Multimedia support Video capture adapters * Auvitek AU0828 support Device Drivers Multimedia support Video capture adapters V4L USB devices * Hauppauge WinTV-PVR USB2 support Device Drivers Multimedia support Video capture adapters V4L USB devices * Hauppauge HD PVR support Device Drivers Multimedia support DVB/ATSC adapters Customise DVB Frontends * Auvitek AU8522 based
    This is the gstreamer pipeline I used to play the TV stream on my MX6Q SDP:

    gst-launch -v dvbsrc frequency=551000000 modulation=7 ! mpegtsdemux program-number=3 ! mpegvideoparse ! queue ! vpudec ! mfw_v4lsink sync=false

    ==

    I could build new kernel with DVB support and load the 950Q driver/firmware dvb-fe-xc5000-1.6.114.fw without any problem. However, I couldn't get any channel information when I ran w-scan. Nor could I run the gst-launch above to get any output on display.

    I moved the TV tuner to my Ubuntu box and found it's a newer version which only works with dvb-fe-xc5000c-4.1.30.7.fw. Unfortunately, the 3.0.35_4.1.0 kernel doesn't support this firmware. I tried to port the driver from LinuxTV back to 3.0.35 but the videobuf-core is not compatible. Then, I moved to kernel 3.10.17_1.0.0_beta. I could load the driver/firmware dvb-fe-xc5000c-4.1.30.7.fw and finish channel scan via w-scan but the gst-launch didn't output anything. I attached the w-scan output and the gst-launch messages. Does anyone know how to resolve this issue? Thanks.

    Below are the gst-inspect results.

    root@debian-imx6:~# gst-inspect | grep mfw
    audiopeq.imx: mfw_audio_pp: audio post equalizeripucsc.imx: mfw_ipucsc: IPU-based video converterv4lsink.imx: mfw_v4lsink: v4l2 video sink
    isink.imx: mfw_isink: IPU-based video sinkv4lsrc.imx: mfw_v4lsrc: v4l2 based camera src

    root@debian-imx6:~# grep mfw_mpeg2decoder /usr/lib/* -nr
    Binary file /usr/lib/gstreamer-0.10/libmfw_gst_mpeg2dec.so matches
    Binary file /usr/lib/gstreamer-0.10/libmfw_gst_mpeg2dec.a matches

    root@debian-imx6:/mnt# grep mpeg2dec.imx /usr/lib/* -nR
    grep: /usr/lib/arm-linux-gnueabihf/libGLESv2.so: No such file or directory
    Binary file /usr/lib/gstreamer-0.10/libmfw_gst_mpeg2dec.so matches
    Binary file /usr/lib/gstreamer-0.10/libmfw_gst_mpeg2dec.a matches

    root@debian-imx6:~# gst-inspect | grep mpeg2
    mpeg2dec: mpeg2dec: mpeg1 and mpeg2 video decoder

    Frood

    DB:2.32:Hauppauge 950q Usb Tv Tuner Is Not Functioning Correctly With Gstreamer On Imx6 fp


    Hi Frodo,

    Can you try to build and Rootfs based on YoctoProject Dora version,

    As you are mixing different kernel version with Gstreamer Freescale plugins and

    multimedia codec libs; fslcodec libs have dependencies on the kernel version

    so I will suggest to build a root file system based on YoctoProject dora release.

    Follow the instructions from Freescale/fsl-community-bsp-platform GitHub

    to build a Yocto based rootfs; and build fsl-image-gui which will include all FSL

    test app and demos.

    Regards

    Adrian

  • RELEVANCY SCORE 2.31

    DB:2.31:Imx6 Solo Vpu Firmware Binary File Not Found 3d



    I am trying to use the VPU to encode the camera input using gstreamer, and I am getting the following error:

    root@nitrogen6x:~# gst-launch mfw_v4lsrc ! queue ! vpuenc codec=6 ! matroskamux ! filesink location=./test.avi

    MFW_GST_V4LSRC_PLUGIN 3.0.9 build on Apr 16 2014 09:57:53.

    [ERR] Error in opening firmware binary file

    [ERR] Please put bin file to /lib/firmware/vpu folder or export VPU_FW_PATH env

    Setting pipeline to PAUSED ...

    ERROR: Pipeline doesn't want to pause.

    Setting pipeline to NULL ...

    Freeing pipeline ...

    root@nitrogen6x:~#

    If I look in /lib/firmware/vpu folder, I see the following binary file:

    root@nitrogen6x:~# ls /lib/firmware/vpu/

    vpu_fw_imx6q.bin

    On my build computer I can see both vpu_fw_imx6q.bin and vpu_fw_im6dl.bin. From the naming I am guessing these are for Quad and Dual cores. If so, how do I get/generate a bin file for the Solo CPU?

    Am I really missing a vpu binary file, or is this error pointing to something different?

    My environment:

    Boundarydevices Nitrogen6x with iMX6 Solo CPU (with VPU), Silicon rev 1.1

    Yocto Dora image with MIPI camera

    Kernel: Linux-3.0.35-02991-g3338700 (Kernel was replaced with a version from Boundarydevices that fixes a MIPI clock issue when HDMI is not enabled)

    Thanks,

  • RELEVANCY SCORE 2.30

    DB:2.30:Csi Driver For 3.12 Kernel a8



    Dear Freescale,

    We are using IM6SoloLite processor as it has only CSI interface to interface the camera, and trying to interface the camera (OV5640) I could not able to find the driver with CSI. No way I can go for the other version of the kernels because of the other modules we are using. so kindly help on this.

    Thanks Regards,

    Satya.

    DB:2.30:Csi Driver For 3.12 Kernel a8


    You can get 3.10.53GA kernel from here:

    http://git.freescale.com/git/cgit.cgi/imx/linux-2.6-imx.git/log/?h=imx_3.10.53_1.1.0_ga

  • RELEVANCY SCORE 2.30

    DB:2.30:Imx6 Solo/Dl Based Processor Simultaniously Is Not Working With Live Vga 640x480 Video Capture (Ov5640) And Audio Loop Back(Wm8960 Codec) 99



    Hi ,

    ISSUE:I have faced the issue based on video capture parallel and audio loop back/simultaneous.

    Both audio and videos was working parallely with QVGA (320x240) 15 fps QCIF (176x144) 15/30 fps .\

    Working both audio and video for following resolution :

    QVGA (320x240) 15 fps

    QCIF (176x144) 15 fps

    QCIF (176x144) 30 fps

    Tested Commands:

    --------------------------------

    ./mxc_v4l2_capture.out -iw 320 -ih 240 -ow 320 -oh 240 -m 1 -fr 15-d /dev/video0 -i 1 -c 1000 /v5640_320_240_30fps.yuv

    arecord -D hw:0,0 -c 2 -f S16_LE -r 8000 -t raw | aplay -D hw:0,0 -c 2 -f S16_LE -r 8000 -v

    ./mxc_v4l2_capture.out -iw 176 -ih 144 -ow 176 -oh 144 -m 7 -fr 15 -d /dev/video0 -i 1 -c 1000 /CAM/vv176_144_i1_15.yuv

    arecord -D hw:0,0 -c 2 -f S16_LE -r 8000 -t raw | aplay -D hw:0,0 -c 2 -f S16_LE -r 8000 -v

    ./mxc_v4l2_capture.out -iw 176 -ih 144 -ow 176 -oh 144 -m 7 -fr 30 -d /dev/video0 -i 1 -c 1000 /CAM/vv176_144_i1_30.yuv

    arecord -D hw:0,0 -c 2 -f S16_LE -r 8000 -t raw | aplay -D hw:0,0 -c 2 -f S16_LE -r 8000 -v

    --------------------------------

    Both audio and video is not working for following resolution :

    QVGA (320x240) 30 fps

    QVGA (640x480) 30 fps

    QVGA (640x480) 15 fps

    Tested Commands:

    --------------------------------

    ./mxc_v4l2_capture.out -iw 640 -ih 480 -ow 640 -oh 480 -m 0 -fr 30 -d /dev/video0 -i 1 -c 1000 /CAM/v5640_640_480p_30fps.yuv

    arecord -D hw:0,0 -c 2 -f S16_LE -r 8000 -t raw | aplay -D hw:0,0 -c 2 -f S16_LE -r 8000 -v

    ./mxc_v4l2_capture.out -iw 640 -ih 480 -ow 640 -oh 480 -m 0 -fr 10 -d /dev/video0 -i 1 -c 1000 /CAM/v5640_640_480p_10fps.yuv

    arecord -D hw:0,0 -c 2 -f S16_LE -r 8000 -t raw | aplay -D hw:0,0 -c 2 -f S16_LE -r 8000 -v

    ./mxc_v4l2_capture.out -iw 320 -ih 240 -ow 320 -oh 240 -m 1 -fr 15 -d /dev/video0 -i 1 -c 1000 /v5640_320_240_15fps.yuv

    arecord -D hw:0,0 -c 2 -f S16_LE -r 8000 -t raw | aplay -D hw:0,0 -c 2 -f S16_LE -r 8000 -v

    --------------------------------

    Any memory related issue happening in the driver side for both camera capture and audio working time?

    How to solve this issue?

    Following things are the memory allocation in kernel drive(linux-3.0.35)

    Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)

    Memory: 256MB = 256MB total

    Memory: 248016k/248016k available, 276272k reserved, 0K highmem

    Virtual kernel memory layout:

    vector : 0xffff0000 - 0xffff1000 ( 4 kB)

    fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)

    DMA : 0xf4600000 - 0xffe00000 ( 184 MB)

    vmalloc : 0xa0800000 - 0xf2000000 (1304 MB)

    lowmem : 0x80000000 - 0xa0000000 ( 512 MB)

    pkmap : 0x7fe00000 - 0x80000000 ( 2 MB)

    modules : 0x7f000000 - 0x7fe00000 ( 14 MB)

    .init : 0x80008000 - 0x80032000 ( 168 kB)

    .text : 0x80032000 - 0x808f6bf0 (8979 kB)

    .data : 0x808f8000 - 0x80947240 ( 317 kB)

    Audio and camera clock settings:

    Audio clock settings:

    MX6DL_PAD_GPIO_0__CCM_CLKO,---Audio MCLK clock

    static int wm8960_clk_enable(int enable){
    if (enable) clk_enable(clko); else clk_disable(clko);
    printk(" %s HELLO old wm8960\n\n\n",__func__); return 0;
    }

    static int mxc_wm8960_init(void)

    {
    int rate;printk(" %s HELLO old wm8960\n\n\n",__func__); clko = clk_get(NULL, "clko_clk"); if (IS_ERR(clko)) { pr_err("can't get CLKO clock.\n"); return PTR_ERR(clko); } /* both audio codec and comera use CLKO clk*/ rate = clk_round_rate(clko, 24000000);rate = clk_round_rate(clko, 12000000); clk_set_rate(clko, rate);
    wm8960_data.sysclk = rate;
    printk(" %s End rate=%d\n\n\n",__func__,rate); return 0;
    }

    static int __init imx6q_init_audio(void){

    platform_device_register(sabresd_vwm8960_reg_devices); mxc_register_device(mx6_sabresd_audio_wm8960_device, wm8960_data); imx6q_add_imx_ssi(1, mx6_sabresd_ssi_pdata); mxc_wm8960_init(); printk("HELLO old wm8960\n\n\n"); return 0;}

    static struct mxc_audio_platform_data wm8960_data = { .ssi_num = 1, .src_port = 2, .ext_port = 3, .hp_active_low = 1, .mic_active_low = 1, .init = mxc_wm8960_init, .clock_enable = wm8960_clk_enable,};

    Camera clock settings:

    MX6DL_PAD_GPIO_6__CCM_CCM_OUT_0 --GPIO_6 CAmera clock

    static struct imx_ipuv3_platform_data ipu_data[] = { { .rev = 4, .csi_clk[0] = "clko2_clk", .bypass_reset = false, },#ifndef OV9712_CAM_CONFIG#if 1 { .rev = 4, .csi_clk[0] = "clko2_clk", .bypass_reset = false,#endif#endif};

    static struct fsl_mxc_capture_platform_data capture_data[] = { { .csi = 0, .ipu = 0, .mclk_source = 0, .is_mipi = 0, },#if 1 { .csi = 1, .ipu = 0, .mclk_source = 0, .is_mipi = 1, },

    static struct mipi_csi2_platform_data mipi_csi2_pdata = { .ipu_id = 0, .csi_id = 0, .csi_id = 1, .lanes = 2, .dphy_clk = "mipi_pllref_clk", .pixel_clk = "emi_clk",};

    --------- mx6_sabresd_board_init(void)(){ clko2 = clk_get(NULL, "clko2_clk"); if (IS_ERR(clko2)) { pr_err("can't get CLKO2 clock.\n"); printk(" %s clko2 error \n\n\n",__func__); } new_parent = clk_get(NULL, "osc_clk"); if (!IS_ERR(new_parent)) { clk_set_parent(clko2, new_parent); clk_put(new_parent); printk(" %s clko2 parent error \n\n\n",__func__); } rate = clk_round_rate(clko2, 24000000); clk_set_rate(clko2, rate); clk_enable(clko2); printk(" %s 2 clko2 set rate=%d\n\n\n",__func__,rate);}----------

    Please let me know whats happening inside the kernel while accessing the caera capture above QVGA resolution with audio,

    Without camera capture audio playback and capture working properly,if once camera capture enabled that time audio is not working .

    Audio using CLKO(GPIO_0) and video using the clk CLKO2(GPIO_6).

    How to solve this simultaneous memory related issue in inx6 solo/dl processor.

    Thanks by,

    Venkat

    DB:2.30:Imx6 Solo/Dl Based Processor Simultaniously Is Not Working With Live Vga 640x480 Video Capture (Ov5640) And Audio Loop Back(Wm8960 Codec) 99


    Hi Venkatesh

    internal bandwidth limitations is difficult to predict

    or calculate. Usually this is just experimentation.

    For example check that you used Freescale optimized

    codecs.

    L3.0.35_4.1.0_MM_CODECS

    and installed all latest patches, check patches tab below

    http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=i.MX6QnodeId=018rH3ZrDRB24Afpsp=1tab=Design_Tools_Tab

    Very useful would be test this use case without OS, just with bare-metal

    SDK (to exclude OS overheads)

    i.MX 6Series Platform SDK

    Best regards

    chip

  • RELEVANCY SCORE 2.29

    DB:2.29:Rear-In Camera Capture And Display On Fb On Imx6 Sabrelite. sp



    Hi,

    I am using ov5642 rear-in camera on imx6 sabrelite, I am looking for sample app which will capture camera image and display on FB. Is there any sample app available in unit_test (ltib) or any doc, guideline / suggestion to do so.

    appreciate quick response.

    Thanks.

    Santosh

    DB:2.29:Rear-In Camera Capture And Display On Fb On Imx6 Sabrelite. sp


    You can try unit_test: mxc_v4l2_overlay.out or some gstreamer command line.

    For overlay, it should be something like:

    ./mxc_v4l2_overlay.out -iw 640 -ih 480 -ow 176 -ih 144 -ol 10 -ot 10 -r

    0 -fg -t 5

    And for gstreamer, it should be something like:

    gst-launch mfw_v4lsrc ! mfw_v4lsink

    Im not sure if this command line will work without changes, because you need to take care of any codec mismatch may exists between your camera and your display

  • RELEVANCY SCORE 2.29

    DB:2.29:Cameras On Sabresd Imx6q Board Stop Working With Strange Behaviour 1p



    I have SabreSD IMX6Q board with two cameras one CSI (ov5642) and one mipi (ov5640).

    I am using Linux (GNOME profile) and usually first load the drivers like this:

    modprobe mxc_v4l2_capturemodprobe ov5642_cameramodprobe ov5640_camera_mipi

    before I can use the cameras.

    At this moment none of the drivers load and I get following output:

    camera ov5642 is not foundcamera ov5640_mipi is not found

    However, If I load the CSI driver for ov5640 instead the driver probe succeeds, i.e running

    modprobe mxc_v4l2_capture

    modprobe ov5640_camera

    modprobe ov5640_camera_mipi

    I get

    camera ov5640 is found

    camera ov5640_mipi is not found

    and I can then use the CSI camera as before as the ov5640 and ov5642 are very similar cameras.

    As there is no mipi driver for ov5642 I cannot test the same work around.

    It appears to me that part of the problem is that the cameras on the board report the wrong Chip ID.

    They report ov5640 instead of ov5642 for the CSI camera and ov5642 instead of ov5640 for the mipi camera.

    My question is:

    Did this symptom happen to anybody here too.

    What could be the reason for this, and is there a solution.

    Also can I buy the board cameras individually from somewhere, in case I somehow damage them?

    Also original Android SD card cannot see any cameras on my board anymore.

    DB:2.29:Cameras On Sabresd Imx6q Board Stop Working With Strange Behaviour 1p


    This problem is now solved.

    I have looked at the problem and as I could talk to the cameras via the I2C interface I decided to believe what the software is telling me, i.e. that the camera in the parallel camera PCB was an ov5640 and the camera in the mipi camera PCB was an ov5642. I decided to swap the cameras from the little camera boards and now the system is up and running.

  • RELEVANCY SCORE 2.29

    DB:2.29:Mipi Csi Virtual Channel 3 Support 3.10.17 Kernel x3



    Hi,

    I am trying to enable MIPI CSI Virtual channel 3 support on 3.10.17 kernel.

    I have followed the Sample code for iMX6 SabreSD to use MIPI CSI camera with virtual channel 3.

    Still I am getting " mipi csi2 can not receive sensor clk1'

    How to solve this issue?

    Thanks

    Saurabh

  • RELEVANCY SCORE 2.28

    DB:2.28:Using Same Uimage For Different Resolution 8m



    hi all,

    I am using i.mx535 board in that we interface a camera application and we done the capturing of all resolution videos and images for that we are using seperate uImage for capturing the different resolution

    CAMERA SENSOR: ov5640

    For Eg:-

    for 640x480 jpeg image we are using a seperate uImage1

    for 720p jpeg image Uimage 2

    for 1080p uImage 3 like these

    can any one help me how to capture all the resolution jpeg Images in a single uImage how can i change the ioctl functions

    NOTE:

    There is a seperate jpeg register settings for seperate resolutions

    Thanks,

    shan

    DB:2.28:Using Same Uimage For Different Resolution 8m


    The unit test code allows capturing from the camera by passing the width and height as parameters.

  • RELEVANCY SCORE 2.28

    DB:2.28:Mx6q Android Kk4.4.2 Hdmi Issue. "W/Imx6.Gralloc( 2415): Fbiopan_Display Failed: Invalid Argument" zd



    Hello Community,

    I have HDMI hot plug issue with android 4.4.2 on MX6Q platform. (android_kk4.4.2_1.0.0-ga) Following is my fb settings :

    video=mxcfb0:dev=ldb,LDB-WXGA,bpp=32 video=mxcfb1:dev=lcd,LCD-XGA,bpp=32 video=mxcfb2:dev=hdmi,1920x1080M@60,if=RGB24,bpp=32 fbmem=20M,20M,28M

    When system bootup, the lvds and lcd displayed correctly. When HDMI plugin. It reported "W/imx6.gralloc( 2415): FBIOPAN_DISPLAY failed: Invalid argument", and blank screen on HDMI. Android desktop keep showing on lvds and lcd . Following are the logs.

    --------- beginning of /dev/log/main

    I/FslHwcomposer( 2415): HDMI Plugin detected

    I/FslHwcomposer( 2415): HDMI Gralloc Framebuffer opening.

    W/imx6.gralloc( 2415): 32bpp setting of Framebuffer catched!

    W/imx6.gralloc( 2415): using (fd=52)

    W/imx6.gralloc( 2415): id = DISP4 BG - DI1

    W/imx6.gralloc( 2415): xres = 1920 px

    W/imx6.gralloc( 2415): yres = 1080 px

    W/imx6.gralloc( 2415): xres_virtual = 1920 px

    W/imx6.gralloc( 2415): yres_virtual = 3456 px

    W/imx6.gralloc( 2415): bpp = 32

    W/imx6.gralloc( 2415): r = 0:8

    W/imx6.gralloc( 2415): g = 8:8

    W/imx6.gralloc( 2415): b = 16:8

    W/imx6.gralloc( 2415): width = 305 mm (159.895081 dpi)

    W/imx6.gralloc( 2415): height = 171 mm (160.421051 dpi)

    W/imx6.gralloc( 2415): refresh rate = 60.00 Hz

    W/audio_hw_primary( 2418): open output stream devices 1024, format 1, channels 0, sample_rate 0, flag 1

    W/audio_hw_primary( 2418): adev_open_output_stream() HDMI multichannel

    W/audio_hw_primary( 2418): out_read_hdmi_channel_masks() card 0 got 2 sup channels

    W/audio_hw_primary( 2418): out_read_hdmi_rates() card 0 got 32000 sup rates

    W/audio_hw_primary( 2418): out_read_hdmi_rates() card 0 got 44100 sup rates

    W/audio_hw_primary( 2418): out_read_hdmi_rates() card 0 got 48000 sup rates

    W/audio_hw_primary( 2418): opened out stream...1105940824

    I/AudioFlinger( 2418): HAL output buffer size 192 frames, normal mix buffer size 192 frames

    I/AudioFlinger( 2418): AudioFlinger's thread 0x41fb2378 ready to run

    W/audio_hw_primary( 2418): out get parameters query sup_sampling_rates=, reply sup_sampling_rates=32000|44100|48000

    W/audio_hw_primary( 2418): out get parameters query sup_channels=, reply sup_channels=AUDIO_CHANNEL_OUT_STEREO

    W/audio_hw_primary( 2418): out_set_parameters closing=true, ret -2, out 1105940824

    W/audio_hw_primary( 2418): out_set_parameters exiting=1, ret -2, out 1105940824

    --------- beginning of /dev/log/system

    V/WiredAccessoryManager( 2824): Headset UEVENT: {SUBSYSTEM=switch, SWITCH_STATE=1, DEVPATH=/devices/virtual/switch/hdmi_audio, SEQNUM=2357, ACTION=change, SWITCH_NAME=hdmi_audio, SWITCH_TIME=639830310746}

    V/WiredAccessoryManager( 2824): newName=hdmi_audio newState=16 headsetState=16 prev headsetState=0

    V/WiredAccessoryManager( 2824): device hdmi_audio connected

    W/audio_hw_primary( 2418): adev_close_output_stream...1105940824

    W/audio_hw_primary( 2418): out_set_parameters routing=0, ret 1, out 1074919656

    I/DisplayManagerService( 2824): Display device added: DisplayDeviceInfo{"HDMI Screen": 1024 x 768, 60.000004 fps, density 227, 227.0 x 227.0 dpi, touch EXTERNAL, rotation 0, type HDMI, FLAG_SECURE, FLAG_SUPPORTS_PROTECTED_BUFFERS, FLAG_PRESENTATION}

    W/imx6.gralloc( 2415): FBIOPAN_DISPLAY failed: Invalid argument

    D/SurfaceFlinger( 2415): Screen acquired, type=1 flinger=0x413c8450

    W/imx6.gralloc( 2415): FBIOPAN_DISPLAY failed: Invalid argument

    I/InputReader( 2824): Reconfiguring input devices. changes=0x00000004

    W/imx6.gralloc( 2415): FBIOPAN_DISPLAY failed: Invalid argument

    DB:2.28:Mx6q Android Kk4.4.2 Hdmi Issue. "W/Imx6.Gralloc( 2415): Fbiopan_Display Failed: Invalid Argument" zd


    Hello Community,

    I have HDMI hot plug issue with android 4.4.2 on MX6Q platform. (android_kk4.4.2_1.0.0-ga) Following is my fb settings :

    video=mxcfb0:dev=ldb,LDB-WXGA,bpp=32 video=mxcfb1:dev=lcd,LCD-XGA,bpp=32 video=mxcfb2:dev=hdmi,1920x1080M@60,if=RGB24,bpp=32 fbmem=20M,20M,28M

    When system bootup, the lvds and lcd displayed correctly. When HDMI plugin. It reported "W/imx6.gralloc( 2415): FBIOPAN_DISPLAY failed: Invalid argument", and blank screen on HDMI. Android desktop keep showing on lvds and lcd . Following are the logs.

    --------- beginning of /dev/log/main

    I/FslHwcomposer( 2415): HDMI Plugin detected

    I/FslHwcomposer( 2415): HDMI Gralloc Framebuffer opening.

    W/imx6.gralloc( 2415): 32bpp setting of Framebuffer catched!

    W/imx6.gralloc( 2415): using (fd=52)

    W/imx6.gralloc( 2415): id = DISP4 BG - DI1

    W/imx6.gralloc( 2415): xres = 1920 px

    W/imx6.gralloc( 2415): yres = 1080 px

    W/imx6.gralloc( 2415): xres_virtual = 1920 px

    W/imx6.gralloc( 2415): yres_virtual = 3456 px

    W/imx6.gralloc( 2415): bpp = 32

    W/imx6.gralloc( 2415): r = 0:8

    W/imx6.gralloc( 2415): g = 8:8

    W/imx6.gralloc( 2415): b = 16:8

    W/imx6.gralloc( 2415): width = 305 mm (159.895081 dpi)

    W/imx6.gralloc( 2415): height = 171 mm (160.421051 dpi)

    W/imx6.gralloc( 2415): refresh rate = 60.00 Hz

    W/audio_hw_primary( 2418): open output stream devices 1024, format 1, channels 0, sample_rate 0, flag 1

    W/audio_hw_primary( 2418): adev_open_output_stream() HDMI multichannel

    W/audio_hw_primary( 2418): out_read_hdmi_channel_masks() card 0 got 2 sup channels

    W/audio_hw_primary( 2418): out_read_hdmi_rates() card 0 got 32000 sup rates

    W/audio_hw_primary( 2418): out_read_hdmi_rates() card 0 got 44100 sup rates

    W/audio_hw_primary( 2418): out_read_hdmi_rates() card 0 got 48000 sup rates

    W/audio_hw_primary( 2418): opened out stream...1105940824

    I/AudioFlinger( 2418): HAL output buffer size 192 frames, normal mix buffer size 192 frames

    I/AudioFlinger( 2418): AudioFlinger's thread 0x41fb2378 ready to run

    W/audio_hw_primary( 2418): out get parameters query sup_sampling_rates=, reply sup_sampling_rates=32000|44100|48000

    W/audio_hw_primary( 2418): out get parameters query sup_channels=, reply sup_channels=AUDIO_CHANNEL_OUT_STEREO

    W/audio_hw_primary( 2418): out_set_parameters closing=true, ret -2, out 1105940824

    W/audio_hw_primary( 2418): out_set_parameters exiting=1, ret -2, out 1105940824

    --------- beginning of /dev/log/system

    V/WiredAccessoryManager( 2824): Headset UEVENT: {SUBSYSTEM=switch, SWITCH_STATE=1, DEVPATH=/devices/virtual/switch/hdmi_audio, SEQNUM=2357, ACTION=change, SWITCH_NAME=hdmi_audio, SWITCH_TIME=639830310746}

    V/WiredAccessoryManager( 2824): newName=hdmi_audio newState=16 headsetState=16 prev headsetState=0

    V/WiredAccessoryManager( 2824): device hdmi_audio connected

    W/audio_hw_primary( 2418): adev_close_output_stream...1105940824

    W/audio_hw_primary( 2418): out_set_parameters routing=0, ret 1, out 1074919656

    I/DisplayManagerService( 2824): Display device added: DisplayDeviceInfo{"HDMI Screen": 1024 x 768, 60.000004 fps, density 227, 227.0 x 227.0 dpi, touch EXTERNAL, rotation 0, type HDMI, FLAG_SECURE, FLAG_SUPPORTS_PROTECTED_BUFFERS, FLAG_PRESENTATION}

    W/imx6.gralloc( 2415): FBIOPAN_DISPLAY failed: Invalid argument

    D/SurfaceFlinger( 2415): Screen acquired, type=1 flinger=0x413c8450

    W/imx6.gralloc( 2415): FBIOPAN_DISPLAY failed: Invalid argument

    I/InputReader( 2824): Reconfiguring input devices. changes=0x00000004

    W/imx6.gralloc( 2415): FBIOPAN_DISPLAY failed: Invalid argument

  • RELEVANCY SCORE 2.28

    DB:2.28:Possible Issue With Imx6 Platform Sdk Stack Alignment At Startup. c1



    I've been wrestling with stability issues as I am trying to reuse portions of the iMX6 Platform SDK in my boot loader. What I've found is that the memory map setup and the way stack is initialized, its possible that the stack pointer will not be double-word aligned. Apparently it is important to start off with this double-word alignment, because I've found that when I build my boot loader and the "top_of_stack" location is NOT double-word aligned (divisible by 8), then my system doesn't boot; however, if I adjust the memory map to force that to a double-word aligned address it does boot.

    While I don't fully understand the need for this double-word alignment, there is some information here...

    http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.faqs/ka4127.html

    Anyway, the easy fix for this is to simply force this alignment in the linker file...

    .stacks (NOLOAD) :

    {

    . = ALIGN (8); Add this line

    __stacks_start = .;

    . += 48K;

    __stacks_end = .;

    top_of_stacks = .;

    } DDR

    This apparently is not a problem for folks using the SDK (perhaps something else in the build is forcing this alignment that I'm not aware of), so I'd like to get feedback on this post to see if folks agree or disagree with this suggested change.

    DB:2.28:Possible Issue With Imx6 Platform Sdk Stack Alignment At Startup. c1


    Right!

    The quick fix is to do the ALIGN(8) that I show at the top.

    The better fix is to apply the BIC instruction to all assignments of SP in that startup.S code...

    @ set stacks for all other modes

    msr CPSR_c, #MODE_FIQ | I_BIT | F_BIT

    bic r0, r0, #15

    mov sp, r0

    sub r0, r0, r1

    msr CPSR_c, #MODE_IRQ | I_BIT | F_BIT

    bic r0, r0, #15

    mov sp, r0

    sub r0, r0, r1

    msr CPSR_c, #MODE_ABT | I_BIT | F_BIT

    bic r0, r0, #15

    mov sp, r0

    sub r0, r0, r1

    msr CPSR_c, #MODE_UND | I_BIT | F_BIT

    bic r0, r0, #15

    mov sp, r0

    sub r0, r0, r1

    msr CPSR_c, #MODE_SYS | I_BIT | F_BIT

    bic r0, r0, #15

    mov sp, r0

    sub r0, r0, r1

    @ Set SVC mode stack with interrupts disabled

    msr CPSR_c, #MODE_SVC | I_BIT | F_BIT

    bic r0, r0, #15

    mov sp, r0

    sub r0, r0, r1

  • RELEVANCY SCORE 2.28

    DB:2.28:5mp Camera Ov5640 Interface With I.Mx233 z3



    Hi,

    We have designed a i.MX233 board with OV5640 camera on LINUX OS. We need driver to interface this camera. If anybody have exposure to interface camera with any board, please help me to interface this camera.

    Regards,

    Pramod Kumar

    DB:2.28:5mp Camera Ov5640 Interface With I.Mx233 z3


    You could try to connect a USB camera instead.

  • RELEVANCY SCORE 2.28

    DB:2.28:Video Processing Latency 18



    Hello All,

    System Overview:

    Processor: iMX6 DualLite

    Take the Video input from the camera, process the data and output it at ethernet or wifi.

    Which camera interface (MIPI CSI2 or Parallel camera interface) of iMX6 I shall use to get the minimum latency in the output video data.

    DB:2.28:Video Processing Latency 18


    Hello Pankaj,

    Saurabh is correct, a dual buffer approach is a good idea. If I had to make a recommendation, I would go with a MIPI camera.

  • RELEVANCY SCORE 2.27

    DB:2.27:Imx6 Board Startup Issue kx



    Hi

    I am having an issue getting the IMX6 Q7 Board up and running with Linux. My goal is to get it up and running before making modifications.

    The micro sd card correctly works excepted in some case where hangs at changing runlevel .

    Error : init cannot execute /etc/rc.d/rc_mxc_S

    DB:2.27:Imx6 Board Startup Issue kx


    Hi

    I am having an issue getting the IMX6 Q7 Board up and running with Linux. My goal is to get it up and running before making modifications.

    The micro sd card correctly works excepted in some case where hangs at changing runlevel .

    Error : init cannot execute /etc/rc.d/rc_mxc_S

  • RELEVANCY SCORE 2.27

    DB:2.27:Conversion From Bayer Raw Rgb To Yuv In Imx6 Solo jm



    Hi,

    We need to understand how RAW Bayer 8 bit format from Camera sensor can be converted into YUV422 or anyother format supported by IMX6 solo. There is no YUV output from Camera sensor so this has to be taken care in the IMX6 Solo IPU block. Can anyone advise us on this.

    Yogee

    DB:2.27:Conversion From Bayer Raw Rgb To Yuv In Imx6 Solo jm


    Hi Yogee

    one can use IPU CSC (color space/format convertion), examples

    can be found in

    IMX51_IPU_LIB_UG

    i.MX51 IPU V3 Library User's Guide

    Also please check some useful Bayer links below

    https://community.freescale.com/message/331888

    https://community.freescale.com/message/309833

    https://community.freescale.com/message/309069

    Best regards

    chip

    -----------------------------------------------------------------------------------------------------------------------

    Note: If this post answers your question, please click the Correct Answer button. Thank you!

    -----------------------------------------------------------------------------------------------------------------------

  • RELEVANCY SCORE 2.27

    DB:2.27:Enable Mipi For I.Mx6 Solo Board fp



    Hi all,

    I am working in a imx6 solo wandboard, in that i need to integrate the camera ov5640 with mipi interface, for that i want to done the mux pad settings for camera data, clock, reset and pwdn, can any one tell me how to do that, i am new to this camera and linux drivers

    Thanks,

    dhana

    DB:2.27:Enable Mipi For I.Mx6 Solo Board fp


    Hi Dave

    Thank you very much.

    Best

    Andy

    发件人: Dave McMordie

    发送时间: 2013年8月28日 20:58

    收件人: imx6 zeng

    主题: Re: - ENABLE MIPI FOR I.MX6 SOLO BOARD

    https://community.freescale.com/ Freescale Community

    ENABLE MIPI FOR I.MX6 SOLO BOARD

    reply from Dave https://community.freescale.com/people/davemcmordie?et=watches.email.thread McMordie in i.MX Community - View https://community.freescale.com/message/347182?et=watches.email.thread#347182 the full discussion

  • RELEVANCY SCORE 2.27

    DB:2.27:Mipi fm



    hi

    i am using imx6q on nitrogen6x. i am trying to operate my MIPI ov5640 cam but unfortunately without any success.

    the camera / sensor doesnt give out data ( and than i get time-out error )

    streaming task paused, reason error (-5)

    Execution ended after 9996617334 ns.

    regards

    DB:2.27:Mipi fm


    no... still not working

    any case it is driver's registers issue?

  • RELEVANCY SCORE 2.27

    DB:2.27:Driver For Ov5640 Camera 7f



    Hi all,

    In our design we are using OV5640 camera module chip with sololite processor. if any driver is available for OV5640 through online please let me know.

    Thanks,

    Sivakumar

    DB:2.27:Driver For Ov5640 Camera 7f


    Hello Sivakumar,

    Our sabre sdp board uses the OV5640 camera, you can find the driver in the following path:

    kernel_imx/drivers/media/video/mxc/capture/

    Have a great day,Sergio

    -----------------------------------------------------------------------------------------------------------------------Note: If this post answers your question, please click the Correct Answer button. Thank you!-----------------------------------------------------------------------------------------------------------------------

  • RELEVANCY SCORE 2.27

    DB:2.27:Imx6 Bootup Issue, Endless Loop a8



    Hi all,

    We boot up our custom imx6 board with linux well.

    But when we move to android, it failed at an endless loop.

    We could find some i2c errors from the kernel log and camera/audio crash at android period.

    It's so strange that we just used same kernel version between linux and android.

    Anybody have tips for me?

    Many thanks.

    ===============

    Chip: imx6dl

    Android: 4.3 jb1.1.0

    Kernel version: 3.0.35

    and the log as attachment.

    DB:2.27:Imx6 Bootup Issue, Endless Loop a8


    Hello Blurence,

    Its seems to be some dummy I2C device type related.

    See some below links, may it help you

    http://linux-i2c.vger.kernel.narkive.com/e0hiIeXZ/patch-i2c-match-dummy-devices-by-type

    http://www.avrfreaks.net/forum/linux-2618-crash-i2c-twi-driver

    common from above links and other search, may be you need to be patch driver, may be.

    Thanks and Regards

    JAYMIN D