This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM572x GP EVM Camera not detected

Other Parts Discussed in Thread: AM5728, TMDSCM572X

Hi all,

I'm experiencing an issue that for me it's more likely a hardware issue, camera sensor is just not visible on the I2C bus as if it wasn't connected when the AM5728 EVM board is cold, so communication can't be done and the device can't get probed and registered successfully. I'm using TI's image and the output log is the following:

#) mt9t11x 4-003c: input-clock-freq: 32000000
#) mt9t11x 4-003c: pixel-clock-freq: 96000000
#) vip 48990000.vip: loading firmware vpdma-1b8.bin
#) vip 48990000.vip: VPDMA firmware loaded
#) mt9t11x 4-003c: Product ID error ffffff87

After heating the board externally with air at 140°F for around 30 minutes or more if no luck the camera starts being visible on the I2C bus and the device driver gets probed and registered successfully as shown in the following output log:

#) mt9t11x 4-003c: input-clock-freq: 32000000
#) mt9t11x 4-003c: pixel-clock-freq: 96000000
#) mt9t11x 4-003c: mt9t111 chip ID 2680
#) vip2-s0: Port A: Using subdev mt9t11x for capture
#) vip2-s0: device registered as video1
#) mt9t11x 4-003c: mt9t11x sensor driver registered !!

I have seen the same behavior with different combinations of three AM5728 EVM boards and two AM57xx EVM Camera boards. It seems that some strange physical phenomenon is occurring on the I2C lines that makes communication successful only when those lines are heated.

Has anyone experienced something similar? I would like to get this issue solved.

Regards,

Carlos Gomez

  • Hi,

    I will forward this to the factory team.
  • Hello,

    Please check this thread:

    e2e.ti.com/.../1932846

    BR
    Margarita
  • Hi,

    Thanks for your answers! Hope the factory team can provide a solution for this issue. The camera sensor should be detected on the I2C bus the first time that I turn on the  AM5728 EVM. I'll be waiting for a response.

    Thanks again,

    Carlos

  • hi Carlos,
    I use the same evm board, and get the same erro info (mt9t11x 4-003c: Product ID error ffffff87) ,but I did not get right I2C info anytime,

    have you fixed this problem?

    thanks.
  • Hi Panxi,

    No, I haven't fixed this problem. The way I found to get it working is to heat the board externally with air at 140°F or by running applications with high CPU or GPU load for several minutes or even hours and rebooting the board during that process until get the I2C bus detecting the camera sensor.

    Regards,

    Carlos
  • Hi Carlos,

    I got the same issue with the video capture device on AM5728 EVM. I tested it deeply and finally I conclude that the error is caused by something wrong with the TMDSCM572x camera module itself. I test the issue with 3 cameras, one camera works fine with no errors each time I tested it. The other two cameras fails 16 times of 20 tries in average. The test consist in boot the board 20 times with each camera and look if the device is recognized by the system, I repeat the test with other EVM to discard another possible source of error. The error is completely aleatory, with a big tendency to failure. 

    I think that maybe this camera modules have a production error or low quality control, because from 3 new brand cameras, only one works fine (This can´t be only bad luck). 

    I hope that helps you, because I spend a lot of time figuring out this issue.

    Best regards,

    Eng. Daniel Garbanzo Hidalgo

    Embedded Software Developer Engineer
    RidgeRun Engineering Limitada
    www.ridgerun.com
  • Deas our customer meet the same problem
  • Hello,
    I am using AM57x SDK 3.02.00.05 on GP EVM. I cannot get the camera to work? I did some cursory searching and it looks like it is registered during boot but i'm not sure if i need to run 'insmod'. I am still looking for 'vip driver users guide for this SK'.

    I am using 'AM57xx EVM Camera Board Revision A1'.

    Thanks for any guidance.
    Marc

    ####################################################################################

    Bootlog shows successful register:
    Check LOG :
    [ 7.313656] mt9t11x 4-003c: input-clock-freq: 32000000
    [ 7.319051] mt9t11x 4-003c: pixel-clock-freq: 96000000
    [ 7.380175] mt9t11x 4-003c: mt9t111 chip ID 2680
    [ 7.387363] mt9t11x 4-003c: mt9t11x sensor driver registered !!
    [ 7.501189] vpe 489d0000.vpe: loading firmware vpdma-1b8.bin
    [ 7.509590] input: pixcir_tangoc as /devices/platform/44000000.ocp/4807c000.i2c/i2c-4/4-005c/input/input1
    [ 7.548609] vpe 489d0000.vpe: Device registered as /dev/video0

    /dev/ has videoxx
    look into /dev/
    * video0
    * video1
    * video10
    * video11

    root@am57xx-evm:/# v4l2-ctl -D
    ---------------------------------------------------------------------
    Driver Info (not using libv4l2):
    Driver name : vpe
    Card type : vpe
    Bus info : platform:vpe
    Driver version: 4.4.32
    Capabilities : 0x84204000
    Video Memory-to-Memory Multiplanar
    Streaming
    Extended Pix Format
    Device Capabilities
    Device Caps : 0x04204000
    Video Memory-to-Memory Multiplanar
    Streaming
    Extended Pix Format



    lsmod shows mt9t11x, ti_vpe, _sc, _cs, _vpdma, vip
    root@am57xx-evm:/dev# lsmod
    =================================================
    Module Size Used by
    -----------------------------------------------------
    bc_example 7186 0
    xhci_plat_hcd 5247 0
    xhci_hcd 109138 1 xhci_plat_hcd
    usbcore 194665 2 xhci_plat_hcd,xhci_hcd
    cbc 2324 0
    drbg 13425 1
    rpmsg_pru 4962 0
    rpmsg_rpc 19668 0
    rpmsg_proto 7597 0
    xfrm_user 23228 2
    xfrm4_tunnel 2040 0
    ipcomp 2473 0
    xfrm_ipcomp 4695 1 ipcomp
    esp4 6465 0
    ah4 5665 0
    af_key 27563 0
    xfrm_algo 6970 5 ah4,esp4,af_key,xfrm_user,xfrm_ipcomp
    dwc3 64055 0
    bluetooth 325678 2
    virtio_rpmsg_bus 13080 3 rpmsg_pru,rpmsg_rpc,rpmsg_proto
    udc_core 12063 1 dwc3
    snd_soc_simple_card 7760 0
    pru_rproc 11732 4
    pruss_intc 7227 5 pru_rproc
    snd_soc_omap_hdmi_audio 4737 0
    ti_vip 35302 0
    ecb 1909 0
    sha512_generic 9903 0
    sha512_arm 12079 0
    sha256_generic 9503 1
    hmac 2735 1
    md5 1897 0
    ahci_platform 3218 0
    libahci_platform 8821 1 ahci_platform
    libahci 27891 2 libahci_platform,ahci_platform
    sha1_generic 2621 0
    pvrsrvkm 412436 5 bc_example
    sha1_arm_neon 6261 0
    libata 196388 3 libahci,libahci_platform,ahci_platform
    pruss 11186 1 pru_rproc
    sha1_arm 3862 1 sha1_arm_neon
    omap_aes_driver 19230 0
    omap_sham 21089 0
    omap_wdt 4570 0
    scsi_mod 129717 1 libata
    ti_vpe 19292 0
    ti_sc 24714 2 ti_vip,ti_vpe
    ti_csc 2313 2 ti_vip,ti_vpe
    ti_vpdma 15166 2 ti_vip,ti_vpe
    extcon_palmas 6261 0
    pixcir_i2c_ts 6570 0
    dwc3_omap 5054 0
    extcon 13943 3 dwc3,extcon_palmas,dwc3_omap
    mt9t11x 14769 1
    rtc_omap 8272 0
    rtc_palmas 5187 0
    snd_soc_tlv320aic3x 48260 1
    omap_rng 4835 0
    rtc_ds1307 11278 0
    rng_core 8011 1 omap_rng
    omap_des 11446 0
    debugss_kmodule 6848 0
    omap_remoteproc 12389 4
    remoteproc 27121 5 omap_remoteproc,pruss,pru_rproc,rpmsg_rpc,rpmsg_proto
    virtio 7580 2 remoteproc,virtio_rpmsg_bus
    virtio_ring 12291 2 remoteproc,virtio_rpmsg_bus
    sch_fq_codel 8251 3
    uio_module_drv 7353 0
    uio 9329 1 uio_module_drv
    gdbserverproxy 4671 0
    cryptodev 37405 2
    cmemk 31462 0
    root@am57xx-evm:/dev#

    It is not in the /lib/modules/4.4.32-gadde2ca9f8/kernel/drivers# ls -l
    root@am57xx-evm:/lib/modules/4.4.32-gadde2ca9f8/kernel/drivers# ls -l
    drwxr-xr-x 2 root root 4096 Dec 15 2016 ata
    drwxr-xr-x 2 root root 4096 Dec 15 2016 bluetooth
    drwxr-xr-x 2 root root 4096 Dec 15 2016 cdrom
    drwxr-xr-x 3 root root 4096 Dec 15 2016 char
    drwxr-xr-x 2 root root 4096 Dec 15 2016 crypto
    drwxr-xr-x 2 root root 4096 Dec 15 2016 extcon
    drwxr-xr-x 2 root root 4096 Dec 15 2016 gpio
    drwxr-xr-x 3 root root 4096 Dec 15 2016 hid
    drwxr-xr-x 2 root root 4096 Dec 15 2016 hwmon
    drwxr-xr-x 4 root root 4096 Dec 15 2016 iio
    drwxr-xr-x 6 root root 4096 Dec 15 2016 input
    drwxr-xr-x 6 root root 4096 Dec 15 2016 media
    drwxr-xr-x 2 root root 4096 Dec 15 2016 mfd
    drwxr-xr-x 3 root root 4096 Dec 15 2016 mtd
    drwxr-xr-x 6 root root 4096 Dec 15 2016 net
    drwxr-xr-x 2 root root 4096 Dec 15 2016 power
    drwxr-xr-x 2 root root 4096 Dec 15 2016 remoteproc
    drwxr-xr-x 2 root root 4096 Dec 15 2016 rpmsg
    drwxr-xr-x 2 root root 4096 Dec 15 2016 rtc
    drwxr-xr-x 2 root root 4096 Dec 15 2016 scsi
    drwxr-xr-x 2 root root 4096 Dec 15 2016 uio
    drwxr-xr-x 13 root root 4096 Dec 15 2016 usb
    drwxr-xr-x 2 root root 4096 Dec 15 2016 virtio
    drwxr-xr-x 3 root root 4096 Dec 15 2016 w1
    drwxr-xr-x 2 root root 4096 Dec 15 2016 watchdog

    ** check /proc/ to see what MODULES are installed.
    =============================================================================================
    =============================================================================================
    root@am57xx-evm:/proc# ls
    1 1963 28 479 64 820 cmem key-users scsi
    10 198 285 48 65 823 config.gz keys self
    1002 1991 29 49 66 824 consoles kmsg softirqs
    1007 1993 298 495 67 825 cpu kpagecgroup stat
    11 1996 3 496 68 826 cpuinfo kpagecount swaps
    114 1997 30 5 69 89 crypto kpageflags sys
    1169 2 31 50 691 9 device-tree loadavg sysrq-trigger
    12 20 32 51 7 944 devices locks sysvipc
    125 2004 345 549 70 946 diskstats meminfo thread-self
    14 2018 346 55 72 948 driver misc timer_list
    15 2019 371 56 722 961 execdomains modules tty
    16 2065 384 562 73 963 fb mounts uptime
    17 21 41 57 74 992 filesystems mtd version
    179 22 42 58 744 994 fs net vmallocinfo
    1872 23 43 59 762 asound interrupts pagetypeinfo vmstat
    1876 24 44 6 764 buddyinfo iomem partitions zoneinfo
    1877 25 45 61 773 bus ioports pvr
    1878 26 46 62 786 cgroups irq sched_debug
    19 27 47 63 8 cmdline kallsyms schedstat

    root@am57xx-evm:/# find /lib/modules/$(uname -r)/kernel/ -name '*.ko' | grep 'ti_*'
    =============================================================================================
    =============================================================================================
    /lib/modules/4.4.32-gadde2ca9f8/kernel/drivers/rpmsg/virtio_rpmsg_bus.ko
    /lib/modules/4.4.32-gadde2ca9f8/kernel/drivers/input/touchscreen/ti_am335x_tsc.ko
    /lib/modules/4.4.32-gadde2ca9f8/kernel/drivers/mfd/ti_am335x_tscadc.ko
    /lib/modules/4.4.32-gadde2ca9f8/kernel/drivers/media/platform/ti-vpe/ti-sc.ko
    /lib/modules/4.4.32-gadde2ca9f8/kernel/drivers/media/platform/ti-vpe/ti-csc.ko
    /lib/modules/4.4.32-gadde2ca9f8/kernel/drivers/media/platform/ti-vpe/ti-vpe.ko
    /lib/modules/4.4.32-gadde2ca9f8/kernel/drivers/media/platform/ti-vpe/ti-cal.ko
    /lib/modules/4.4.32-gadde2ca9f8/kernel/drivers/media/platform/ti-vpe/ti-vip.ko
    /lib/modules/4.4.32-gadde2ca9f8/kernel/drivers/media/platform/ti-vpe/ti-vpdma.ko
    /lib/modules/4.4.32-gadde2ca9f8/kernel/drivers/virtio/virtio.ko
    /lib/modules/4.4.32-gadde2ca9f8/kernel/drivers/virtio/virtio_ring.ko
    /lib/modules/4.4.32-gadde2ca9f8/kernel/drivers/net/wireless/ti/wlcore/wlcore_spi.ko
    /lib/modules/4.4.32-gadde2ca9f8/kernel/drivers/net/wireless/ti/wlcore/wlcore_sdio.ko
    /lib/modules/4.4.32-gadde2ca9f8/kernel/drivers/net/wireless/ti/wlcore/wlcore.ko
    /lib/modules/4.4.32-gadde2ca9f8/kernel/drivers/net/wireless/ti/wl18xx/wl18xx.ko
    /lib/modules/4.4.32-gadde2ca9f8/kernel/drivers/net/wireless/brcm80211/brcmutil/brcmutil.ko
    /lib/modules/4.4.32-gadde2ca9f8/kernel/drivers/net/ethernet/ti/prueth.ko
    /lib/modules/4.4.32-gadde2ca9f8/kernel/drivers/iio/adc/ti_am335x_adc.ko
    /lib/modules/4.4.32-gadde2ca9f8/kernel/drivers/usb/gadget/function/usb_f_uac2.ko
    /lib/modules/4.4.32-gadde2ca9f8/kernel/drivers/usb/gadget/function/usb_f_fs.ko
    /lib/modules/4.4.32-gadde2ca9f8/kernel/drivers/usb/gadget/function/usb_f_rndis.ko
    /lib/modules/4.4.32-gadde2ca9f8/kernel/drivers/usb/gadget/function/usb_f_ss_lb.ko
    /lib/modules/4.4.32-gadde2ca9f8/kernel/drivers/usb/gadget/function/usb_f_printer.ko
    /lib/modules/4.4.32-gadde2ca9f8/kernel/drivers/usb/gadget/function/usb_f_mass_storage.ko
    /lib/modules/4.4.32-gadde2ca9f8/kernel/drivers/usb/gadget/function/usb_f_hid.ko
    /lib/modules/4.4.32-gadde2ca9f8/kernel/drivers/usb/gadget/function/usb_f_uvc.ko
    /lib/modules/4.4.32-gadde2ca9f8/kernel/drivers/usb/gadget/function/usb_f_serial.ko
    /lib/modules/4.4.32-gadde2ca9f8/kernel/drivers/usb/gadget/function/usb_f_ecm.ko
    /lib/modules/4.4.32-gadde2ca9f8/kernel/drivers/usb/gadget/function/usb_f_midi.ko
    /lib/modules/4.4.32-gadde2ca9f8/kernel/drivers/usb/gadget/function/usb_f_acm.ko
    /lib/modules/4.4.32-gadde2ca9f8/kernel/drivers/usb/gadget/function/usb_f_ecm_subset.ko
    /lib/modules/4.4.32-gadde2ca9f8/kernel/drivers/usb/gadget/function/u_serial.ko
    /lib/modules/4.4.32-gadde2ca9f8/kernel/drivers/usb/gadget/function/u_ether.ko
    /lib/modules/4.4.32-gadde2ca9f8/kernel/drivers/usb/gadget/function/usb_f_obex.ko
    /lib/modules/4.4.32-gadde2ca9f8/kernel/drivers/usb/gadget/function/usb_f_ncm.ko
    /lib/modules/4.4.32-gadde2ca9f8/kernel/drivers/usb/gadget/legacy/g_multi.ko
    /lib/modules/4.4.32-gadde2ca9f8/kernel/net/sched/sch_multiq.ko
    /lib/modules/4.4.32-gadde2ca9f8/kernel/net/netfilter/xt_multiport.ko
    root@am57xx-evm:/#
  • Mark,
    did you checked this post? It may help...

    e2e.ti.com/.../530582