Template:C792-Software: Difference between revisions

For kernel driver usage, ensure your system is updated. As the 5.4 kernel included key changes, these guidelines are valid for kernel 5.4 and newer releases. Verify your kernel version with <code>uname -a</code>; if it is below 5.4, fix this before continuing.

pi@raspberrypi:~ $ uname -a

Linux raspberrypi 5.10.63-v7l+ #1459 SMP Wed Oct 6 16:41:57 BST 2021 armv7l GNU/Linux

<mark>1.</mark> Update and upgrade your Raspberry Pi system (time required varies by country/region).

sudo apt-get update

sudo apt-get upgrade

<mark>2.</mark> Enable the camera module (enabled by default on Raspberry Pi Bullseye OS).

sudo raspi-config

sudo reboot

*Edit the <code>/boot/firmware/config.txt</code> file (sudo privileges required):

sudo nano /boot/firmware/config.txt

</pre>

*Add the line:

dtoverlay=tc358743

</pre>

*Add the line if your shield support audio like C790 or C792：

dtoverlay=tc358743-audio

</pre>

*Add the line '''only if''': your device (e.g., C790/C792) supports a 22-pin connector with all 4 lanes connected, and the compute module has the '''CAM1 interface''' with all 4 lanes connected:

dtoverlay=tc358743,4lane=1

</pre>

*Use the following command to check the amount of memory allocated to the CMA heap:

dmesg | grep cma

</pre>

*The first line should look like:

pi@raspberrypi:~ $ dmesg | grep cma

[0.000000] cma: Reserved 256 MiB at 0x000000001ec00000

*If the reported CMA allocated memory is less than 96MB, edit the <code>/boot/cmdline.txt</code> file and add the following at the start of the line <span class="tb_red">(do not add a newline character)</span>:

cma=96M

</pre>

*Reboot the device. If everything works properly, you should see the <code>/dev/video0</code> device, and running the following command will show it is provided by Unicam:

v4l2-ctl --list-devices

</pre>

*After connecting all cables, power on the Raspberry Pi and enter the commands below：

pi@raspberrypi:~ $ ls /dev/video0

/dev/video0

*Several EDID editors are available on the market. You need to first create an edid.txt file (you can use the <code>command nano edid.txt</code> to create and edit the file), then copy the content below into the edid.txt file:

00ffffffffffff005262888800888888

1c150103800000780aEE91A3544C9926

*After the edid.txt file is created, execute the command <code>v4l2-ctl --set-edid=file=edid.txt --fix-edid-checksums</code> in the terminal, and you will see output similar to the following:

     pi@raspberrypi:~ $ v4l2-ctl --set-edid=file=edid.txt --fix-edid-checksums

*Detect the presence of HDMI signal input at present via command：

     pi@raspberrypi:~ $ v4l2-ctl --query-dv-timings

     Active width: 1280

*Use the following command to select UYVY (however, your application may override this setting):

v4l2-ctl -v pixelformat=UYVY

</pre>

*Check if the audio driver/sound card is available for ALSA:

     pi@raspberrypi:~ $ arecord -l.  

     **** List of CAPTURE Hardware Devices ****.  

*Install the GStreamer tools:

sudo apt install gstreamer1.0-tools

</pre>

*Check the GStreamer tool version:

pi@raspberrypi:~ $ gst-launch-1.0 --version

gst-launch-1.0 version 1.18.4

<mark>'''[Application Example — Using GStreamer to Record Video and Audio]'''</mark>  

# GStreamer v1.14 Command

gst-launch-1.0 v4l2src io-mode=5 ! video/x-raw, format=UYVY, framerate=25/1 ! v4l2h264enc output-io-mode=4 ! video/x-h264,profile=high ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv alsasrc device=hw:1 ! audio/x-raw,rate=48000,channels=2 ! audioconvert ! avenc_aac bitrate=48000 ! aacparse ! queue ! mux.

<code>foo.mkv</code> is the output file.

If your GStreamer version is 1.8 or higher, you can try the following test command. Additionally, <code>alsasrc device=hw:1</code> refers to the sound card for TC358743; you can check this with the command <code>arecord -l</code>.

# Command to record video with audio（GStreamer 1.18.4）

gst-launch-1.0 -vvv v4l2src ! "video/x-raw,framerate=30/1,format=UYVY" ! v4l2h264enc extra-controls="controls,h264_profile=4,h264_level=13,video_bitrate=256000;" ! "video/x-h264,profile=high, level=(string)4.2" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv alsasrc device=hw:1 ! audio/x-raw,rate=48000,channels=2 ! audioconvert ! avenc_aac bitrate=48000 ! aacparse ! queue ! mux.

*Record video only:

gst-launch-1.0 -vvv v4l2src ! "video/x-raw,framerate=60/1,format=UYVY" ! v4l2h264enc extra-controls="controls,h264_profile=4,h264_level=13,video_bitrate=256000;" ! "video/x-h264,profile=high, level=(string)4.2" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv

</pre>

*Record video and audio (if your module supports audio):

gst-launch-1.0 -vvv v4l2src ! "video/x-raw,framerate=60/1,format=UYVY" ! v4l2h264enc extra-controls="controls,h264_profile=4,h264_level=13,video_bitrate=256000;" ! "video/x-h264,profile=high, level=(string)4.2" ! h264parse ! queue ! matroskamux name=mux ! filesink location=foo.mkv alsasrc device=hw:1 ! audio/x-raw,rate=48000,channels=2 ! audioconvert ! avenc_aac bitrate=48000 ! aacparse ! queue ! mux.

</pre>

Add the following two lines to the <code>/boot/firmware/config.txt</code> file:

dtoverlay=tc358743,4lane=1

dtoverlay=tc358743-audio

After adding the driver configuration, restart the Raspberry Pi for the changes to take effect. If the configuration is correct, execute the following command in the terminal: <code>ls /dev/video*</code>. The configuration is successful if video devices appear in the output:

</pre>

First, execute the command <code>nano 1080p60edid</code> in the terminal to create an EDID file for 1080p60Hz. The content of this file is as follows:

</pre>

Execute <code>nano testC7xx.sh</code> in the same directory to create a test script. The content of this file is as follows:

#!/bin/bash

MEDIADEVICE=-1

Execute <code>bash testC7xx.sh</code> directly in the terminal; the output is as follows:

pi@raspberrypi:~/Desktop $ bash testC7xx.sh  

Active width: 1920

:If you have installed the Raspberry Pi Desktop version, you can use ffplay to play YUV files directly.

ffplay -f rawvideo -video_size 1920x1080 -pixel_format bgr24 test.yuv  

</pre>