Phytec phyCAM User Manual

=
mevqb`=jÉëëíÉÅÜåáâ=dãÄe=
=
«=mevqb`=jÉëëíÉÅÜåáâ=dãÄe=OMOM= = NQ=L=NU=
pìééçêí=eçíäáåÉ=bìêçéÉWW=HQV=ESNPNF=VOONJ ●PN==ÜííéWLLïïïKéÜóíÉÅKÇÉ=
pìééçêí=eçíäáåÉ=kçêíÜ=^ãÉêáÅ~W==NJUMMJOTUJ ●VVNP==ÜííéWLLïïïKéÜóíÉÅKÅçã=
Media controller devices expose entities to the media controller framework. Each entity has one or more source pads and one or more sink pads. You use the media
controller kernel API (ie via media-ctl) to query entities, link source pads to sink pads, and set formats of pads.
We use media-ctl to set:
- the desired resolution and color format of the camera sensor
- the fitting resolution and color format in the CSI interface (controller-camera-interface)
- the way (and/or preprocessing) through the different hardware blocks in the controller
- the resulting camera stream is made available as “/dev/videox” device
The settings are necessary:
- once after restarting the system and using the camera for the first time
- set a new resolution, color format or bit-depth
- set a new path through the hardware blocks
Following entities are present at the i.MX 8M Mini Image (check with “media-ctl –p”):
- entity 1: csi (2 pads, 2 links)
pad0: Sink
pad1: Source
- entity 4: csi capture (1 pad, 1 link)
pad0: Sink
- entity 10: imx7-mipi-csis.0 (2 pads, 2 links)
pad0: Sink
pad1: Source
- entity 13: ar0144 3-0010 (1 pad, 1 link) #(depend on selected camera)
pad0: Source
For setting the media-ctl we use in our demo script following points:
- media-ctl –r reset all links to inactive
- media-ctl –l setup the links between the hardware blocks
- media-ctl –V formats the hardware blocks
For example we will set the VM-016-COL (AR0144) with full Resolution from CSI Port to a /dev/videox device:
First we set the links:

Phytec phyCAM Specifications

General

Brand	Phytec
Model	phyCAM
Category	Control Unit
Language	English