AM572x GP EVM Gstreamer and camera support in Linux SDK 3.0

AnBer

Other Parts Discussed in Thread: AM5728

Team,

I am trying to use the camera add-on on the AM5728 EVM with the SDK 03.00.00.04.

I would like to run the Gstreamer pipeline for capture and display:
http://processors.wiki.ti.com/index.php/DRA7xx_GLSDK_Software_Developers_Guide#Running_a_gstreamer_pipeline but does not seem that the camera is functional after boot.

This is what I got so far from dmesg:

[    5.840762] input: pixcir_tangoc as /devices/platform/44000000.ocp/4807c000.i2c/i2c-4/4-005c/input/input1
[    5.868167] mt9t11x 4-003c: input-clock-freq: 32000000
[    5.874594] mt9t11x 4-003c: pixel-clock-freq: 96000000
[    5.893940] vpe 489d0000.vpe: loading firmware vpdma-1b8.bin
         Starting Synchronize System and HW clocks...
[    5.918514] mt9t11x 4-003c: Product ID error ffffff87
[ OK ] Reached target System Time Synchronized.
[ OK ] Started Update UTMP about System Boot/Shutdown.
[    6.024445] omap_wdt: OMAP Watchdog Timer Rev 0x01: initial timeout 60 sec
[    6.037345] ti-pruss 4b200000.pruss: creating PRU cores and other child platform devices
[    6.053094] ti-pruss 4b280000.pruss: creating PRU cores and other child platform devices
[    6.092296] omap-sham 4b101000.sham: hw accel on OMAP rev 4.3
[    6.103105] remoteproc4: 4b234000.pru0 is available
[    6.108266] remoteproc4: Note: remoteproc is still under development and considered experimental.
[    6.113727] [drm] Initialized pvr 1.14.3699939 20110701 on minor 1
[    6.125294] omap-aes 4b500000.aes: OMAP AES hw accel rev: 3.3
[    6.130738] remoteproc4: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.
[    6.146521] remoteproc4: registered virtio2 (type 7)
[    6.150603] omap-aes 4b700000.aes: OMAP AES hw accel rev: 3.3
[    6.159553] vpe 489d0000.vpe: Device registered as /dev/video0
[    6.168364] vip 48990000.vip: loading firmware vpdma-1b8.bin
[    6.176533] pru-rproc 4b234000.pru0: PRU rproc node /ocp/pruss@4b200000/pru0@4b234000 probed successfully
[    6.191890] remoteproc5: 4b238000.pru1 is available

On /dev I can see:
     /dev/video0
    /dev/video10
but /dev/video1 is not registred at boot.
/dev/video0 and video10 do not seem to be the camera. For /dev/video0 and video10 Gsteamer returns "device '/dev/video0' is not a capture device"

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.12
        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

root@am57xx-evm:~# lsmod | grep vip
ti_vip                 31776 0
ti_sc                  24714 2 ti_vip,ti_vpe
ti_vpdma               14910 2 ti_vip,ti_vpe
root@am57xx-evm:~# lsmod | grep mt9*
mt9t11x                14769 0

Also there is no demo for the camera in the matrix/multimedia.

What are the steps to enable the camera?
Is there a built-in demo using the camera?

Thanks!

Anthony

over 9 years ago

0 Biser Gatchev-XID over 9 years ago

TI__Guru**** 393215 points

I will forward this to the software team.

0 Margarita Gashova over 9 years ago in reply to Biser Gatchev-XID

TI__Guru* 80190 points

Hello,

Could you check with ls /dev/video* when your camera is connect and when is not ?

BR
Margarita

0 AnBer over 9 years ago in reply to Margarita Gashova

TI__Mastermind 30160 points

Margarita,

I will try to remove the camera to see if there are differences.

Up to now the camera was always connected to the EVM (AM5728 EVM rev A3). The red led on the camera module is on.
I used the pre-build image and target file system from the SDK 3.0 to generate the SD card.

The dev entry for video only shows:
/dev/video0
/dev/video10

The camera support seems to be enabled in the kernel.
In .Config I have the below:
#
# Multimedia core support
#
CONFIG_MEDIA_CAMERA_SUPPORT=y
# CONFIG_MEDIA_ANALOG_TV_SUPPORT is not set

# CONFIG_MEDIA_DIGITAL_TV_SUPPORT is not set

# CONFIG_MEDIA_RADIO_SUPPORT is not set

# CONFIG_MEDIA_SDR_SUPPORT is not set

# CONFIG_MEDIA_RC_SUPPORT is not set

CONFIG_MEDIA_CONTROLLER=y

CONFIG_VIDEO_DEV=y

CONFIG_VIDEO_V4L2_SUBDEV_API=y

CONFIG_VIDEO_V4L2=y

# CONFIG_VIDEO_ADV_DEBUG is not set

# CONFIG_VIDEO_FIXED_MINOR_RANGES is not set

CONFIG_V4L2_MEM2MEM_DEV=y

CONFIG_VIDEOBUF_GEN=m

CONFIG_VIDEOBUF2_CORE=y

CONFIG_VIDEOBUF2_MEMOPS=y

CONFIG_VIDEOBUF2_DMA_CONTIG=y

CONFIG_VIDEOBUF2_VMALLOC=m

# CONFIG_TTPCI_EEPROM is not set

The different multimedia modules seems to be built:
CC      drivers/media/i2c/adv7180.mod.o
LD [M] drivers/media/i2c/adv7180.ko
CC      drivers/media/i2c/ml86v7667.mod.o
LD [M] drivers/media/i2c/ml86v7667.ko
CC      drivers/media/i2c/mt9t11x.mod.o
LD [M] drivers/media/i2c/mt9t11x.ko
CC      drivers/media/i2c/ov1063x.mod.o
LD [M] drivers/media/i2c/ov1063x.ko
CC      drivers/media/i2c/ov2659.mod.o
LD [M] drivers/media/i2c/ov2659.ko
CC      drivers/media/i2c/ov490.mod.o
LD [M] drivers/media/i2c/ov490.ko
CC      drivers/media/platform/soc_camera/soc_camera.mod.o
LD [M] drivers/media/platform/soc_camera/soc_camera.ko
CC      drivers/media/platform/soc_camera/soc_camera_platform.mod.o
LD [M] drivers/media/platform/soc_camera/soc_camera_platform.ko
CC      drivers/media/platform/soc_camera/soc_mediabus.mod.o
LD [M] drivers/media/platform/soc_camera/soc_mediabus.ko
CC      drivers/media/platform/ti-vpe/ti-cal.mod.o
LD [M] drivers/media/platform/ti-vpe/ti-cal.ko
CC      drivers/media/platform/ti-vpe/ti-sc.mod.o
LD [M] drivers/media/platform/ti-vpe/ti-sc.ko
CC      drivers/media/platform/ti-vpe/ti-vip.mod.o
LD [M] drivers/media/platform/ti-vpe/ti-vip.ko
CC      drivers/media/platform/ti-vpe/ti-vpdma.mod.o
LD [M] drivers/media/platform/ti-vpe/ti-vpdma.ko
CC      drivers/media/platform/ti-vpe/ti-vpe.mod.o
LD [M] drivers/media/platform/ti-vpe/ti-vpe.ko
CC      drivers/media/v4l2-core/videobuf-core.mod.o
LD [M] drivers/media/v4l2-core/videobuf-core.ko
CC      drivers/media/v4l2-core/videobuf2-vmalloc.mod.o
LD [M] drivers/media/v4l2-core/videobuf2-vmalloc.ko

and present in the sd card in:
/lib/modules/4.4.12-g3639bea54a/kernel/drivers/media/plaform

Is there something missing to start the camera drivers and have the /dev/video1 entry?

0 AnBer over 9 years ago in reply to AnBer

TI__Mastermind 30160 points

I disconnected the camera and there was no differences in the /dev/video entries.

I re-connected it and now the /dev/video1 is appearing.

I will do further tests to see if the camera is functionnal.

0 Carlos Gomez V. over 9 years ago

Prodigy 160 points

Hi Anthony,

I posted the same issue here:

https://e2e.ti.com/support/arm/sitara_arm/f/791/t/532440

Do you still have the same issue? I saw that once you re-connected the camera sensor you could get it registered and probed in /dev/video1, but I'm wondering if then you had the same issue the first time you turned on the EVM after one day (for example) with the EVM board turned off.

Please let me know if you found a real solution,

Regards,

Carlos

0 AnBer over 9 years ago in reply to Carlos Gomez V.

TI__Mastermind 30160 points

Hi Carlos,

I guess that issue was a bad interfacing (as I did not use the screws to fix the camera module at the beginning).
Now the /dev/video1 is appearing at every boot.

A.

0 jack pan over 9 years ago in reply to AnBer

Prodigy 180 points

Hi Anthony

I get the same error,How do you fix this problem ?

0 AnBer over 9 years ago in reply to jack pan

TI__Mastermind 30160 points

Hi Panxi,

I just remove the camera module and connect it again (with screw this time). On the next boot the issue was gone.

A.

Processors

Processors forum

AM572x GP EVM Gstreamer and camera support in Linux SDK 3.0