https://wiki.voipac.com/api.php?action=feedcontributions&feedformat=atom&user=Voipac-hw
Voipac Wiki - User contributions [en]
2026-05-04T13:01:04Z
User contributions
MediaWiki 1.35.0
https://wiki.voipac.com/index.php?title=iMX93_Industrial_Environmental_chamber_testing&diff=5586
iMX93 Industrial Environmental chamber testing
2025-05-14T14:27:52Z
<p>Voipac-hw: /* Test description */</p>
<hr />
<div>[[Category:iMX93 Industrial Development Kit]]<br />
[[Category:iMX93 Industrial Development Kit Testing]]<br />
<!-- --><br />
<div style="float:right">__TOC__</div><br />
<br />
On this page environmental stress testing results of iMX93 Industrial Development Kit are displayed. Detailed instructions how to setup kits are also shown.<br />
<br />
== Hardware configuration ==<br />
All of the modules used standard specification except of the temperature ranges for the key components as described below:<br />
<br /><br />
* 1x iMX93 Industrial Development Kit in [[iMX93 Industrial Max|Max configuration]]<br />
** i.MX 93 Dual 1.7GHz CPU - extended industrial temperature range (-40°C to +105°C)<br />
** 2GB LPDDR4 Memory - extended industrial temperature range (-40°C to +95°C)<br />
** eMMC Flash 32GB - industrial temperature range (-40°C to +85°C)<br />
** MAYA-W260-00B WiFi & Bluetooth Module - industrial temperature range (-40°C to +85°C)<br />
<br /><br />
* 1x iMX93 Industrial Development Kit in [[iMX93 Industrial Pro|Pro configuration]]<br />
** i.MX 93 Dual 1.7GHz CPU - extended industrial temperature range (-40°C to +105°C)<br />
** 2GB LPDDR4 Memory - automotive temperature range (-40°C to +95°C)<br />
** eMMC Flash 16GB - industrial temperature range (-40°C to +85°C)<br />
** MAYA-W160-00B WiFi & Bluetooth Module - industrial temperature range (-40°C to +85°C)<br />
<br /><br />
* 1x iMX93 Industrial Development Kit in [[iMX93 Industrial Basic|Basic configuration]]<br />
** i.MX 93 Solo 1.7GHz CPU - extended industrial temperature range (-40°C to +105°C)<br />
** 1GB LPDDR4 Memory - industrial temperature range (-40°C to +95°C)<br />
** eMMC Flash 8GB - industrial temperature range (-40°C to +85°C)<br />
<br /><br />
* 1x iMX93 Industrial Development Kit in [[iMX93 Industrial Lite|Lite configuration]]<br />
** i.MX 93 Solo 900MHz CPU - extended commercial temperature range (0°C to +95°C)<br />
** 512MB LPDDR4 Memory - industrial temperature range (-30°C to +85°C)<br />
** eMMC Flash 4GB - extended temperature range (-25°C to +85°C)<br />
<br /><br />
All of the tested modules used standard configuration of iMX Development Baseboard with extended temperature range (-20°C to +70°C). The majority of tested kits used the standard heatsink sized 25x25x25mm, which is included in every development kit package, thus showcasing that this standardised heatsink performs even in very harsh conditions.<br /><br />
<br />
The setup in the environmental chamber:<br /><br />
[[image:iMX93_Industrial_Development_Kits-Enviromental_chamber_overview_with_description.jpg|800px]]<br />
<br />
== Test description ==<br />
Four iMX93 Industrial Development Kits (one in Max Industrial configuration, one in Pro Industrial configuration, one in Basic Industrial configuration and one in Lite Industrial configuration) were running CPU and memory tests to stress out all the most significant peripherals in the whole Industrial temperature scale, ranging from -40°C to +85°C, to check the reliability and stability of the firmware and hardware design.<br /><br /><br />
<br />
Configuration, software and testing threads in details:<br /><br /><br />
<br />
'''1x iMX93 Industrial Development Kit [setup no. 4] in [[iMX93 Industrial Max|Max configuration]] and Industrial temperature range<br />CPU and memory stress testing'''<br />
* 1 thread of extensive DDR4 Memory stress test<br />
* 1 thread of CPU stress test<br />
* all the messages were displayed on the serial console connected via Micro USB cable<br />
* firmware running from eMMC Flash memory<br />
* Ethernet cable connected to network switch placed outside of the chamber<br />
* 2x USB device connected and placed outside of the chamber<br />
* WiFi and Bluetooth module active, connected to the antennas and running discovery mode<br />
* standard 25x25x25mm heatsink<br />
<br /><br />
'''1x iMX93 Industrial Development Kit [setup no. 2] in [[iMX93 Industrial Pro|Pro configuration]] and Industrial temperature range<br />CPU and memory stress testing'''<br />
* 1 thread of extensive DDR4 Memory stress test<br />
* 1 thread of CPU stress test<br />
* all the messages were displayed on the serial console connected via Micro USB cable<br />
* firmware running from eMMC Flash memory<br />
* Ethernet cable connected to network switch placed outside of the chamber<br />
* 2x USB device connected and placed outside of the chamber<br />
* WiFi and Bluetooth module active, connected to the antennas and running discovery mode<br />
* standard 25x25x25mm heatsink<br />
<br /><br />
'''1x iMX93 Industrial Development Kit [setup no. 1] in [[iMX93 Industrial Basic|Basic configuration]] and Industrial temperature range<br />CPU and memory stress testing'''<br />
* 1 thread of extensive DDR4 Memory stress test<br />
* 1 thread of CPU stress test<br />
* all the messages were displayed on the serial console connected via Micro USB cable<br />
* firmware running from eMMC Flash memory<br />
* Ethernet cable connected to network switch placed outside of the chamber<br />
* 2x USB device connected and placed outside of the chamber<br />
* standard 25x25x25mm heatsink<br />
<br /><br />
'''1x iMX93 Industrial Development Kit [setup no. 3] in [[iMX93 Industrial Lite|Lite configuration]] and Industrial temperature range<br />CPU and memory stress testing'''<br />
* 1 thread of extensive DDR4 Memory stress test<br />
* 1 thread of CPU stress test<br />
* all the messages were displayed on the serial console connected via Micro USB cable<br />
* firmware running from eMMC Flash memory<br />
* Ethernet cable connected to network switch placed outside of the chamber<br />
* 2x USB device connected and placed outside of the chamber<br />
* WiFi and Bluetooth module active, connected to the antennas and running discovery mode<br />
* standard 25x25x25mm heatsink<br />
<br /><br />
Power sources, USB flash devices, network switch and controlling PC were placed outside the environmental chamber. All the scripts running during the test and the board setup instructions can be found in section [[#Preparing the test|How to prepare the test]].<br />
<br />
== Testing Results ==<br />
The picture below shows the temperature profile during the whole testing process. Humidity was not controlled. The temperature gradient for the environment chamber was set to 1°C/min.<br /><br />
[[image:iMX8M_Industrial_Development_Kit-Env_chamber_temperature_profile.png|800px]]<br />
<br />
=== Running the development kits at -40°C – PASS ===<br />
Test description: CPU, Memory and peripheral stress tests were running at -40°C. All the tested kits were working without errors during the whole time, even if some components used for iMX93 Industrial Development Kit Max in Commercial temperature range were only rated for the temperature range between 0°C and +95°C.<br /><br /><br />
<br />
A closer image on the temperature chamber displaying the minimum temperature is shown below. These readouts are available on the display:<br />
* the first number shows current temperature<br />
* the second one set temperature<br />
* the last two shows relative humidity. Humidity was not controlled during testing process.<br />
[[image:iMX8M Industrial Kit-Env chamber-Boards at -40C.jpg|800px]]<br />
<br /><br /><br />
[[image:iMX8M_Industrial_Development_Kit-Env_chamber_at_-40C.jpg|800px]]<br />
<br />
=== Running the development kits at +85°C – PASS ===<br />
Test description: The pre-set temperature profile was followed until the development kits gradually reached +85°C. The kits remained around this temperature for the duration of two hours and at the end of this whole cycle all the kits were running.<br /><br />
[[image:iMX8M_Industrial_Kit-Env_chamber-Boards_at_+86C.jpg|800px]]<br />
<br /><br /><br />
[[image:iMX8M_Industrial_Development_Kit-Env_chamber_at_+85C.jpg|800px]]<br />
<br />
=== Switch OFF/ON test at -40°C – PASS ===<br />
Test description: At temperature -40°C the development kits were switched OFF, left OFF for at least 15 minutes (to cool down completely) and then switched ON to see if they boot up without problems. Once booted up into Linux, the test script was launched to test RAM memory and all peripherals. The kits were turned OFF and ON again multiple times to see potential issues at the lowest temperature level. All of the tested setups booted up successfully.<br />
<br />
<br /><br />
[[image:iMX8M Industrial Kit-Env chamber-Boards snow.jpg|800px]]<br />
<br />
== PC setup ==<br />
The PC was used during the test to control / monitor all the kits through serial console sessions. The control computer was running Windows 10 operating system.<br />
<br />
=== HDMI Outputs and Serial consoles ===<br />
To control iMX93 Industrial Development Kits, one TeraTerm serial console was opened for each setup. The kits were connected to the external HDMI switch to monitor HDMI outputs.<br />
<br /><br /><br />
The setup of the environmental chamber cables and out-of-chamber equipment:<br />
<br /><br />
[[image:iMX8M Industrial Development Kit-Climate chamber overview.jpg|800px]]<br />
<br />
== Preparing the test ==<br />
=== Boot device and software ===<br />
The eMMC memory was selected as a booting device for all the kits. Device tree files were not adjusted as the default configuration was used. The only change compared to standard software package was running the test script. In order to flash a fresh firmware into the eMMC Memory follow [[iMX93_Industrial_Flashing_Procedure|these instructions]].<br />
<br />
=== Downloading stress test ===<br />
Stress-ng package was selected to check CPU and memory integrity. Placing this file into the same directory where the testing script will be stored is important:<br />
<syntaxhighlight lang="bash"><br />
wget https://downloads.voipac.com/files/iMX93_Industrial_Development_Kit/module/documents/Thermal_stress_resistance/iMX93q-voipac-peripheral-test.sh<br />
</syntaxhighlight><br />
<br />
=== Start CPU and memory stress test ===<br />
Navigate into the directory, where stress test feature and the testing script are stored.<br /><br /><br />
<br />
Stress sequence script:<br />
<syntaxhighlight lang="bash"><br />
for d in $(seq 1 1 99999)<br />
do<br />
uptime<br />
echo "Test $a Test $b Test $c $d times"<br />
echo "Start stress-ng --iomix 1 -t 10 -v"<br />
stress-ng --iomix 1 -t 10 -v<br />
echo "End"<br />
echo "Start stress-ng --cpu 2 --vm 4 -t 10"<br />
stress-ng --cpu 2 --vm 4 -t 10<br />
echo "End"<br />
echo "Start stress-ng --shm 0 -t 10"<br />
stress-ng --shm 0 -t 10<br />
echo "End"<br />
echo "Start stress-ng --seq 0 -t 2 --tz -v"<br />
stress-ng --seq 0 -t 2 --tz -v<br />
echo "End"<br />
echo "Start Thermal zone information"<br />
stress-ng --matrix 0 --tz -t 10 --log-brief -t 10<br />
echo "End"<br />
done<br />
</syntaxhighlight><br />
<br />
=== Start peripheral test ===<br />
Plug the development kit into mains and connect it to the controlling PC via console. Before the first time usage of the script, permissions need to be granted by the following command: <br />
<syntaxhighlight lang="bash"><br />
chmod +x iMX93-voipac-peripheral-test.sh<br />
</syntaxhighlight><br />
<br /><br />
Testing scripts command consists of the following arguments:<br />
* the first parameter - configuration of tested development kit (Max, Pro or Basic)<br />
* the second parameter - USB drive 1 location<br />
* the third parameter - USB drive 2 location<br />
* the fourth parameter - SD card location<br />
<br /><br />
Several commands used during environmental chamber testing are shown below:<br />
<br />
* iMX93 Industrial Development Kit Max:<br />
<syntaxhighlight lang="bash"><br />
./iMX93-voipac-peripheral-test.sh -max sda1 sdb1 mmcblk1p1 | tee -i iMX93-env-testing.log<br />
</syntaxhighlight><br />
* iMX93 Industrial Development Kit Pro:<br />
<syntaxhighlight lang="bash"><br />
./iMX93-voipac-peripheral-test.sh -pro sda1 sdb1 mmcblk1p1 | tee -i iMX93-env-testing.log<br />
</syntaxhighlight><br />
* iMX93 Industrial Development Kit Basic:<br />
<syntaxhighlight lang="bash"><br />
./iMX93-voipac-peripheral-test.sh -basic sda1 sdb1 mmcblk1p1 | tee -i iMX93-env-testing.log<br />
</syntaxhighlight><br />
<br /><br />
The complete script can be found in [https://downloads.voipac.com/files/iMX93_Industrial_Development_Kit/module/documents/Thermal_stress_resistance/iMX93q-voipac-peripheral-test.sh the downloads section] or down below:<br />
<syntaxhighlight lang="bash"><br />
#!/bin/sh<br />
<br />
# iMX93Q environmental chamber peripheral test<br />
<br />
mountDevice() {<br />
mkdir -p "/media/$2"<br />
mount /dev/$1 /media/$2<br />
cat /proc/mounts | grep -F "/dev/$1 /media/$2"<br />
if [ "$?" -eq "0" ]; then<br />
echo "$2 mounted"<br />
else<br />
echo "$2 not mounted"; exit 2<br />
fi<br />
}<br />
<br />
# prepare files<br />
cd ~/<br />
mkdir -p env-chamber-testing/<br />
cd env-chamber-testing/<br />
<br />
touch env-chamber-testing.log<br />
touch cpu-temp.log<br />
<br />
basic=0<br />
pro=0<br />
max=0<br />
case $1 in<br />
-basic) basic=1 ;;<br />
-pro) pro=1 ;;<br />
-max) max=1 ;;<br />
*)<br />
esac<br />
<br />
# mount devices<br />
mountDevice $2 usb0<br />
mountDevice $3 usb1<br />
mountDevice $4 mmc0<br />
<br />
updateLogFiles() {<br />
# obtain board ID from IP address - be sure addresses are allocated based on MAC<br />
boardID=$(/sbin/ip -o -4 addr list eth0 | awk '{print $4}' | cut -d/ -f1 | cut -d'.' -f4 | cut -d'2' -f2);<br />
# be sure time server is running on DHCP server<br />
currentTime=`date +%Y-%m-%d.%H:%M`<br />
<br />
mv env-chamber-testing.log trx-board-$boardID-env-chamber.log.$currentTime<br />
mv cpu-temp.log trx-board-$boardID-env-cpu-temp.log.$currentTime<br />
}<br />
<br />
finish_test_now() {<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) Ctrl+C Detected: End of the test"<br />
precced=0;<br />
#kill -INT $vid_pid $str_pid $log_pid;<br />
sleep 3;<br />
test_status=`cat env-chamber-testing.log | grep -i "error" | grep -v -e "0 errors" -e "no corrected errors"`<br />
if [ -z "$test_status" ]<br />
then<br />
echo "*********TEST PASS*********"<br />
else<br />
echo "*********TEST FAIL*********"<br />
echo "List of detected errors:"<br />
cat env-chamber-testing.log | grep -i "error" | grep -v -e "0 errors" -e "no corrected errors" -e "List of detected errors:"<br />
fi<br />
updateLogFiles<br />
exit;<br />
}<br />
<br />
# kill all processes if Ctrl+C is detected<br />
trap finish_test_now 2<br />
<br />
# play a video stream<br />
gst-launch-1.0 -q imxv4l2src ! autovideosink &<br />
<br />
# stressapptest - CPU threads and RAM memory threads<br />
if [ "${basic}" -eq "1" ]; then<br />
stress-ng --cpu 2 --vm 4 &<br />
str_pid=$!<br />
fi<br />
if [ "${pro}" -eq "1" ]; then<br />
stress-ng --cpu 4 --vm 4 &<br />
str_pid=$!<br />
fi<br />
if [ "${max}" -eq "1" ]; then<br />
stress-ng --cpu 4 --vm 4 &<br />
str_pid=$!<br />
fi<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) Starting stressapptest with PID: " $str_pid<br />
<br />
proceed=1<br />
# create test files<br />
file1_path=`mktemp`<br />
file2_path=`mktemp`<br />
file1=`basename $file1_path`<br />
file2=`basename $file2_path`<br />
<br />
dd if=/dev/urandom of=$file1_path bs=1024 count=10000<br />
dd if=/dev/urandom of=$file2_path bs=1024 count=10000<br />
<br />
cp1_from="/media/mmc0/"<br />
cp1_to="/media/usb0/"<br />
<br />
cp2_from="/media/usb0/"<br />
cp2_to="/media/usb1/"<br />
<br />
#copy files in case they are missing<br />
cp $file1_path $cp1_from<br />
cp $file1_path $cp1_to<br />
cp $file2_path $cp2_from<br />
cp $file2_path $cp2_to<br />
<br />
while [ $proceed -eq 1 ]<br />
do<br />
<br />
ping -q -c1 192.168.0.2 >> env-chamber-testing.log<br />
if [ $? -ne 0 ]<br />
then<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) ERROR: Ping failed"<br />
fi<br />
<br />
cp1_done=`ps | grep $cp1_pid | grep cp`<br />
if [ -z "$cp1_done" ]; then # copy finished<br />
if cmp -s $cp1_from$file1 $cp1_to$file1; then<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) PASS: Copying file from $cp1_from to $cp1_to successful"<br />
else<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) ERROR: Difference between files on $cp1_from and $cp1_to detected"<br />
fi<br />
cp1_temp=$cp1_from # swap destinations<br />
cp1_from=$cp1_to<br />
cp1_to=$cp1_temp<br />
<br />
rm $cp1_to$file1 # remove destination file<br />
<br />
cp $cp1_from$file1 $cp1_to$file1 &<br />
cp1_pid=$!<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) Started copying file from $cp1_from to $cp1_to"<br />
fi<br />
<br />
cp2_done=`ps | grep $cp2_pid | grep cp`<br />
if [ -z "$cp2_done" ]; then # copy finished<br />
if cmp -s $cp2_from$file2 $cp2_to$file2; then<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) PASS: Copying file from $cp2_from to $cp2_to successful"<br />
else<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) ERROR: Difference between files on $cp2_from and $cp2_to detected"<br />
fi<br />
cp2_temp=$cp2_from # swap destinations<br />
cp2_from=$cp2_to<br />
cp2_to=$cp2_temp<br />
<br />
rm $cp2_to$file2 # remove destination file<br />
<br />
cp $cp2_from$file2 $cp2_to$file2 &<br />
cp2_pid=$!<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) Started copying file from $cp2_from to $cp2_to"<br />
fi<br />
<br />
done<br />
</syntaxhighlight></div>
Voipac-hw
https://wiki.voipac.com/index.php?title=iMX93_Industrial_Environmental_chamber_testing&diff=5585
iMX93 Industrial Environmental chamber testing
2025-05-14T14:24:50Z
<p>Voipac-hw: /* Test description */</p>
<hr />
<div>[[Category:iMX93 Industrial Development Kit]]<br />
[[Category:iMX93 Industrial Development Kit Testing]]<br />
<!-- --><br />
<div style="float:right">__TOC__</div><br />
<br />
On this page environmental stress testing results of iMX93 Industrial Development Kit are displayed. Detailed instructions how to setup kits are also shown.<br />
<br />
== Hardware configuration ==<br />
All of the modules used standard specification except of the temperature ranges for the key components as described below:<br />
<br /><br />
* 1x iMX93 Industrial Development Kit in [[iMX93 Industrial Max|Max configuration]]<br />
** i.MX 93 Dual 1.7GHz CPU - extended industrial temperature range (-40°C to +105°C)<br />
** 2GB LPDDR4 Memory - extended industrial temperature range (-40°C to +95°C)<br />
** eMMC Flash 32GB - industrial temperature range (-40°C to +85°C)<br />
** MAYA-W260-00B WiFi & Bluetooth Module - industrial temperature range (-40°C to +85°C)<br />
<br /><br />
* 1x iMX93 Industrial Development Kit in [[iMX93 Industrial Pro|Pro configuration]]<br />
** i.MX 93 Dual 1.7GHz CPU - extended industrial temperature range (-40°C to +105°C)<br />
** 2GB LPDDR4 Memory - automotive temperature range (-40°C to +95°C)<br />
** eMMC Flash 16GB - industrial temperature range (-40°C to +85°C)<br />
** MAYA-W160-00B WiFi & Bluetooth Module - industrial temperature range (-40°C to +85°C)<br />
<br /><br />
* 1x iMX93 Industrial Development Kit in [[iMX93 Industrial Basic|Basic configuration]]<br />
** i.MX 93 Solo 1.7GHz CPU - extended industrial temperature range (-40°C to +105°C)<br />
** 1GB LPDDR4 Memory - industrial temperature range (-40°C to +95°C)<br />
** eMMC Flash 8GB - industrial temperature range (-40°C to +85°C)<br />
<br /><br />
* 1x iMX93 Industrial Development Kit in [[iMX93 Industrial Lite|Lite configuration]]<br />
** i.MX 93 Solo 900MHz CPU - extended commercial temperature range (0°C to +95°C)<br />
** 512MB LPDDR4 Memory - industrial temperature range (-30°C to +85°C)<br />
** eMMC Flash 4GB - extended temperature range (-25°C to +85°C)<br />
<br /><br />
All of the tested modules used standard configuration of iMX Development Baseboard with extended temperature range (-20°C to +70°C). The majority of tested kits used the standard heatsink sized 25x25x25mm, which is included in every development kit package, thus showcasing that this standardised heatsink performs even in very harsh conditions.<br /><br />
<br />
The setup in the environmental chamber:<br /><br />
[[image:iMX93_Industrial_Development_Kits-Enviromental_chamber_overview_with_description.jpg|800px]]<br />
<br />
== Test description ==<br />
Four iMX93 Industrial Development Kits (one in Max Industrial configuration, one in Pro Industrial configuration, one in Basic Industrial configuration and one in Lite Industrial configuration) were running CPU and memory tests to stress out all the most significant peripherals in the whole Industrial temperature scale, ranging from -40°C to +85°C, to check the reliability and stability of the firmware and hardware design.<br /><br /><br />
<br />
Configuration, software and testing threads in details:<br /><br /><br />
<br />
'''1x iMX93 Industrial Development Kit [setup no. 4] in [[iMX93 Industrial Max|Max configuration]] and Industrial temperature range<br />CPU and memory stress testing'''<br />
* 1 thread of extensive DDR4 Memory stress test<br />
* 1 thread of CPU stress test<br />
* sending HDMI Output to external monitor<br />
* all the messages were displayed on the serial console connected via Micro USB cable<br />
* firmware running from eMMC Flash memory<br />
* Ethernet cable connected to network switch placed outside of the chamber<br />
* 2x USB device connected and placed outside of the chamber<br />
* WiFi and Bluetooth module active, connected to the antennas and running discovery mode<br />
* standard 25x25x25mm heatsink<br />
<br /><br />
'''1x iMX93 Industrial Development Kit [setup no. 2] in [[iMX93 Industrial Pro|Pro configuration]] and Industrial temperature range<br />CPU and memory stress testing'''<br />
* 1 thread of extensive DDR4 Memory stress test<br />
* 1 thread of CPU stress test<br />
* sending HDMI Output to external monitor<br />
* NXP MIPI-CSI camera connected and capturing video stream<br />
* all the messages were displayed on the serial console connected via Micro USB cable<br />
* firmware running from eMMC Flash memory<br />
* Ethernet cable connected to network switch placed outside of the chamber<br />
* 2x USB device connected and placed outside of the chamber<br />
* WiFi and Bluetooth module active, connected to the antennas and running discovery mode<br />
* standard 25x25x25mm heatsink<br />
<br /><br />
'''1x iMX93 Industrial Development Kit [setup no. 1] in [[iMX93 Industrial Basic|Basic configuration]] and Industrial temperature range<br />CPU and memory stress testing'''<br />
* 1 thread of extensive DDR4 Memory stress test<br />
* 1 thread of CPU stress test<br />
* sending HDMI Output to external monitor<br />
* all the messages were displayed on the serial console connected via Micro USB cable<br />
* firmware running from eMMC Flash memory<br />
* Ethernet cable connected to network switch placed outside of the chamber<br />
* 2x USB device connected and placed outside of the chamber<br />
* WiFi PCI Express card plugged in, connected to the antennas and running discovery mode<br />
* standard 25x25x25mm heatsink<br />
<br /><br />
'''1x iMX93 Industrial Development Kit [setup no. 3] in [[iMX93 Industrial Lite|Lite configuration]] and Industrial temperature range<br />CPU and memory stress testing'''<br />
* 1 thread of extensive DDR4 Memory stress test<br />
* 1 thread of CPU stress test<br />
* sending HDMI Output to external monitor<br />
* Digilent MIPI-CSI camera connected and capturing video stream<br />
* all the messages were displayed on the serial console connected via Micro USB cable<br />
* firmware running from eMMC Flash memory<br />
* Ethernet cable connected to network switch placed outside of the chamber<br />
* 2x USB device connected and placed outside of the chamber<br />
* WiFi and Bluetooth module active, connected to the antennas and running discovery mode<br />
* standard 25x25x25mm heatsink<br />
<br /><br />
Power sources, USB flash devices, network switch and controlling PC were placed outside the environmental chamber. All the scripts running during the test and the board setup instructions can be found in section [[#Preparing the test|How to prepare the test]].<br />
<br />
== Testing Results ==<br />
The picture below shows the temperature profile during the whole testing process. Humidity was not controlled. The temperature gradient for the environment chamber was set to 1°C/min.<br /><br />
[[image:iMX8M_Industrial_Development_Kit-Env_chamber_temperature_profile.png|800px]]<br />
<br />
=== Running the development kits at -40°C – PASS ===<br />
Test description: CPU, Memory and peripheral stress tests were running at -40°C. All the tested kits were working without errors during the whole time, even if some components used for iMX93 Industrial Development Kit Max in Commercial temperature range were only rated for the temperature range between 0°C and +95°C.<br /><br /><br />
<br />
A closer image on the temperature chamber displaying the minimum temperature is shown below. These readouts are available on the display:<br />
* the first number shows current temperature<br />
* the second one set temperature<br />
* the last two shows relative humidity. Humidity was not controlled during testing process.<br />
[[image:iMX8M Industrial Kit-Env chamber-Boards at -40C.jpg|800px]]<br />
<br /><br /><br />
[[image:iMX8M_Industrial_Development_Kit-Env_chamber_at_-40C.jpg|800px]]<br />
<br />
=== Running the development kits at +85°C – PASS ===<br />
Test description: The pre-set temperature profile was followed until the development kits gradually reached +85°C. The kits remained around this temperature for the duration of two hours and at the end of this whole cycle all the kits were running.<br /><br />
[[image:iMX8M_Industrial_Kit-Env_chamber-Boards_at_+86C.jpg|800px]]<br />
<br /><br /><br />
[[image:iMX8M_Industrial_Development_Kit-Env_chamber_at_+85C.jpg|800px]]<br />
<br />
=== Switch OFF/ON test at -40°C – PASS ===<br />
Test description: At temperature -40°C the development kits were switched OFF, left OFF for at least 15 minutes (to cool down completely) and then switched ON to see if they boot up without problems. Once booted up into Linux, the test script was launched to test RAM memory and all peripherals. The kits were turned OFF and ON again multiple times to see potential issues at the lowest temperature level. All of the tested setups booted up successfully.<br />
<br />
<br /><br />
[[image:iMX8M Industrial Kit-Env chamber-Boards snow.jpg|800px]]<br />
<br />
== PC setup ==<br />
The PC was used during the test to control / monitor all the kits through serial console sessions. The control computer was running Windows 10 operating system.<br />
<br />
=== HDMI Outputs and Serial consoles ===<br />
To control iMX93 Industrial Development Kits, one TeraTerm serial console was opened for each setup. The kits were connected to the external HDMI switch to monitor HDMI outputs.<br />
<br /><br /><br />
The setup of the environmental chamber cables and out-of-chamber equipment:<br />
<br /><br />
[[image:iMX8M Industrial Development Kit-Climate chamber overview.jpg|800px]]<br />
<br />
== Preparing the test ==<br />
=== Boot device and software ===<br />
The eMMC memory was selected as a booting device for all the kits. Device tree files were not adjusted as the default configuration was used. The only change compared to standard software package was running the test script. In order to flash a fresh firmware into the eMMC Memory follow [[iMX93_Industrial_Flashing_Procedure|these instructions]].<br />
<br />
=== Downloading stress test ===<br />
Stress-ng package was selected to check CPU and memory integrity. Placing this file into the same directory where the testing script will be stored is important:<br />
<syntaxhighlight lang="bash"><br />
wget https://downloads.voipac.com/files/iMX93_Industrial_Development_Kit/module/documents/Thermal_stress_resistance/iMX93q-voipac-peripheral-test.sh<br />
</syntaxhighlight><br />
<br />
=== Start CPU and memory stress test ===<br />
Navigate into the directory, where stress test feature and the testing script are stored.<br /><br /><br />
<br />
Stress sequence script:<br />
<syntaxhighlight lang="bash"><br />
for d in $(seq 1 1 99999)<br />
do<br />
uptime<br />
echo "Test $a Test $b Test $c $d times"<br />
echo "Start stress-ng --iomix 1 -t 10 -v"<br />
stress-ng --iomix 1 -t 10 -v<br />
echo "End"<br />
echo "Start stress-ng --cpu 2 --vm 4 -t 10"<br />
stress-ng --cpu 2 --vm 4 -t 10<br />
echo "End"<br />
echo "Start stress-ng --shm 0 -t 10"<br />
stress-ng --shm 0 -t 10<br />
echo "End"<br />
echo "Start stress-ng --seq 0 -t 2 --tz -v"<br />
stress-ng --seq 0 -t 2 --tz -v<br />
echo "End"<br />
echo "Start Thermal zone information"<br />
stress-ng --matrix 0 --tz -t 10 --log-brief -t 10<br />
echo "End"<br />
done<br />
</syntaxhighlight><br />
<br />
=== Start peripheral test ===<br />
Plug the development kit into mains and connect it to the controlling PC via console. Before the first time usage of the script, permissions need to be granted by the following command: <br />
<syntaxhighlight lang="bash"><br />
chmod +x iMX93-voipac-peripheral-test.sh<br />
</syntaxhighlight><br />
<br /><br />
Testing scripts command consists of the following arguments:<br />
* the first parameter - configuration of tested development kit (Max, Pro or Basic)<br />
* the second parameter - USB drive 1 location<br />
* the third parameter - USB drive 2 location<br />
* the fourth parameter - SD card location<br />
<br /><br />
Several commands used during environmental chamber testing are shown below:<br />
<br />
* iMX93 Industrial Development Kit Max:<br />
<syntaxhighlight lang="bash"><br />
./iMX93-voipac-peripheral-test.sh -max sda1 sdb1 mmcblk1p1 | tee -i iMX93-env-testing.log<br />
</syntaxhighlight><br />
* iMX93 Industrial Development Kit Pro:<br />
<syntaxhighlight lang="bash"><br />
./iMX93-voipac-peripheral-test.sh -pro sda1 sdb1 mmcblk1p1 | tee -i iMX93-env-testing.log<br />
</syntaxhighlight><br />
* iMX93 Industrial Development Kit Basic:<br />
<syntaxhighlight lang="bash"><br />
./iMX93-voipac-peripheral-test.sh -basic sda1 sdb1 mmcblk1p1 | tee -i iMX93-env-testing.log<br />
</syntaxhighlight><br />
<br /><br />
The complete script can be found in [https://downloads.voipac.com/files/iMX93_Industrial_Development_Kit/module/documents/Thermal_stress_resistance/iMX93q-voipac-peripheral-test.sh the downloads section] or down below:<br />
<syntaxhighlight lang="bash"><br />
#!/bin/sh<br />
<br />
# iMX93Q environmental chamber peripheral test<br />
<br />
mountDevice() {<br />
mkdir -p "/media/$2"<br />
mount /dev/$1 /media/$2<br />
cat /proc/mounts | grep -F "/dev/$1 /media/$2"<br />
if [ "$?" -eq "0" ]; then<br />
echo "$2 mounted"<br />
else<br />
echo "$2 not mounted"; exit 2<br />
fi<br />
}<br />
<br />
# prepare files<br />
cd ~/<br />
mkdir -p env-chamber-testing/<br />
cd env-chamber-testing/<br />
<br />
touch env-chamber-testing.log<br />
touch cpu-temp.log<br />
<br />
basic=0<br />
pro=0<br />
max=0<br />
case $1 in<br />
-basic) basic=1 ;;<br />
-pro) pro=1 ;;<br />
-max) max=1 ;;<br />
*)<br />
esac<br />
<br />
# mount devices<br />
mountDevice $2 usb0<br />
mountDevice $3 usb1<br />
mountDevice $4 mmc0<br />
<br />
updateLogFiles() {<br />
# obtain board ID from IP address - be sure addresses are allocated based on MAC<br />
boardID=$(/sbin/ip -o -4 addr list eth0 | awk '{print $4}' | cut -d/ -f1 | cut -d'.' -f4 | cut -d'2' -f2);<br />
# be sure time server is running on DHCP server<br />
currentTime=`date +%Y-%m-%d.%H:%M`<br />
<br />
mv env-chamber-testing.log trx-board-$boardID-env-chamber.log.$currentTime<br />
mv cpu-temp.log trx-board-$boardID-env-cpu-temp.log.$currentTime<br />
}<br />
<br />
finish_test_now() {<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) Ctrl+C Detected: End of the test"<br />
precced=0;<br />
#kill -INT $vid_pid $str_pid $log_pid;<br />
sleep 3;<br />
test_status=`cat env-chamber-testing.log | grep -i "error" | grep -v -e "0 errors" -e "no corrected errors"`<br />
if [ -z "$test_status" ]<br />
then<br />
echo "*********TEST PASS*********"<br />
else<br />
echo "*********TEST FAIL*********"<br />
echo "List of detected errors:"<br />
cat env-chamber-testing.log | grep -i "error" | grep -v -e "0 errors" -e "no corrected errors" -e "List of detected errors:"<br />
fi<br />
updateLogFiles<br />
exit;<br />
}<br />
<br />
# kill all processes if Ctrl+C is detected<br />
trap finish_test_now 2<br />
<br />
# play a video stream<br />
gst-launch-1.0 -q imxv4l2src ! autovideosink &<br />
<br />
# stressapptest - CPU threads and RAM memory threads<br />
if [ "${basic}" -eq "1" ]; then<br />
stress-ng --cpu 2 --vm 4 &<br />
str_pid=$!<br />
fi<br />
if [ "${pro}" -eq "1" ]; then<br />
stress-ng --cpu 4 --vm 4 &<br />
str_pid=$!<br />
fi<br />
if [ "${max}" -eq "1" ]; then<br />
stress-ng --cpu 4 --vm 4 &<br />
str_pid=$!<br />
fi<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) Starting stressapptest with PID: " $str_pid<br />
<br />
proceed=1<br />
# create test files<br />
file1_path=`mktemp`<br />
file2_path=`mktemp`<br />
file1=`basename $file1_path`<br />
file2=`basename $file2_path`<br />
<br />
dd if=/dev/urandom of=$file1_path bs=1024 count=10000<br />
dd if=/dev/urandom of=$file2_path bs=1024 count=10000<br />
<br />
cp1_from="/media/mmc0/"<br />
cp1_to="/media/usb0/"<br />
<br />
cp2_from="/media/usb0/"<br />
cp2_to="/media/usb1/"<br />
<br />
#copy files in case they are missing<br />
cp $file1_path $cp1_from<br />
cp $file1_path $cp1_to<br />
cp $file2_path $cp2_from<br />
cp $file2_path $cp2_to<br />
<br />
while [ $proceed -eq 1 ]<br />
do<br />
<br />
ping -q -c1 192.168.0.2 >> env-chamber-testing.log<br />
if [ $? -ne 0 ]<br />
then<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) ERROR: Ping failed"<br />
fi<br />
<br />
cp1_done=`ps | grep $cp1_pid | grep cp`<br />
if [ -z "$cp1_done" ]; then # copy finished<br />
if cmp -s $cp1_from$file1 $cp1_to$file1; then<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) PASS: Copying file from $cp1_from to $cp1_to successful"<br />
else<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) ERROR: Difference between files on $cp1_from and $cp1_to detected"<br />
fi<br />
cp1_temp=$cp1_from # swap destinations<br />
cp1_from=$cp1_to<br />
cp1_to=$cp1_temp<br />
<br />
rm $cp1_to$file1 # remove destination file<br />
<br />
cp $cp1_from$file1 $cp1_to$file1 &<br />
cp1_pid=$!<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) Started copying file from $cp1_from to $cp1_to"<br />
fi<br />
<br />
cp2_done=`ps | grep $cp2_pid | grep cp`<br />
if [ -z "$cp2_done" ]; then # copy finished<br />
if cmp -s $cp2_from$file2 $cp2_to$file2; then<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) PASS: Copying file from $cp2_from to $cp2_to successful"<br />
else<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) ERROR: Difference between files on $cp2_from and $cp2_to detected"<br />
fi<br />
cp2_temp=$cp2_from # swap destinations<br />
cp2_from=$cp2_to<br />
cp2_to=$cp2_temp<br />
<br />
rm $cp2_to$file2 # remove destination file<br />
<br />
cp $cp2_from$file2 $cp2_to$file2 &<br />
cp2_pid=$!<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) Started copying file from $cp2_from to $cp2_to"<br />
fi<br />
<br />
done<br />
</syntaxhighlight></div>
Voipac-hw
https://wiki.voipac.com/index.php?title=iMX93_Industrial_Environmental_chamber_testing&diff=5582
iMX93 Industrial Environmental chamber testing
2025-05-14T14:19:38Z
<p>Voipac-hw: </p>
<hr />
<div>[[Category:iMX93 Industrial Development Kit]]<br />
[[Category:iMX93 Industrial Development Kit Testing]]<br />
<!-- --><br />
<div style="float:right">__TOC__</div><br />
<br />
On this page environmental stress testing results of iMX93 Industrial Development Kit are displayed. Detailed instructions how to setup kits are also shown.<br />
<br />
== Hardware configuration ==<br />
All of the modules used standard specification except of the temperature ranges for the key components as described below:<br />
<br /><br />
* 1x iMX93 Industrial Development Kit in [[iMX93 Industrial Max|Max configuration]]<br />
** i.MX 93 Dual 1.7GHz CPU - extended industrial temperature range (-40°C to +105°C)<br />
** 2GB LPDDR4 Memory - extended industrial temperature range (-40°C to +95°C)<br />
** eMMC Flash 32GB - industrial temperature range (-40°C to +85°C)<br />
** MAYA-W260-00B WiFi & Bluetooth Module - industrial temperature range (-40°C to +85°C)<br />
<br /><br />
* 1x iMX93 Industrial Development Kit in [[iMX93 Industrial Pro|Pro configuration]]<br />
** i.MX 93 Dual 1.7GHz CPU - extended industrial temperature range (-40°C to +105°C)<br />
** 2GB LPDDR4 Memory - automotive temperature range (-40°C to +95°C)<br />
** eMMC Flash 16GB - industrial temperature range (-40°C to +85°C)<br />
** MAYA-W160-00B WiFi & Bluetooth Module - industrial temperature range (-40°C to +85°C)<br />
<br /><br />
* 1x iMX93 Industrial Development Kit in [[iMX93 Industrial Basic|Basic configuration]]<br />
** i.MX 93 Solo 1.7GHz CPU - extended industrial temperature range (-40°C to +105°C)<br />
** 1GB LPDDR4 Memory - industrial temperature range (-40°C to +95°C)<br />
** eMMC Flash 8GB - industrial temperature range (-40°C to +85°C)<br />
<br /><br />
* 1x iMX93 Industrial Development Kit in [[iMX93 Industrial Lite|Lite configuration]]<br />
** i.MX 93 Solo 900MHz CPU - extended commercial temperature range (0°C to +95°C)<br />
** 512MB LPDDR4 Memory - industrial temperature range (-30°C to +85°C)<br />
** eMMC Flash 4GB - extended temperature range (-25°C to +85°C)<br />
<br /><br />
All of the tested modules used standard configuration of iMX Development Baseboard with extended temperature range (-20°C to +70°C). The majority of tested kits used the standard heatsink sized 25x25x25mm, which is included in every development kit package, thus showcasing that this standardised heatsink performs even in very harsh conditions.<br /><br />
<br />
The setup in the environmental chamber:<br /><br />
[[image:iMX93 Industrial Development Kit-Environmental chamber testing-in progress.jpg|800px]]<br />
<br />
== Test description ==<br />
Four iMX93 Industrial Development Kits (one in Max Industrial configuration, one in Pro Industrial configuration, one in Basic Industrial configuration and one in Lite Industrial configuration) were running CPU and memory tests to stress out all the most significant peripherals in the whole Industrial temperature scale, ranging from -40°C to +85°C, to check the reliability and stability of the firmware and hardware design.<br /><br /><br />
<br />
Configuration, software and testing threads in details:<br /><br /><br />
<br />
'''1x iMX93 Industrial Development Kit [setup no. 4] in [[iMX93 Industrial Max|Max configuration]] and Industrial temperature range<br />CPU and memory stress testing'''<br />
* 1 thread of extensive DDR4 Memory stress test<br />
* 1 thread of CPU stress test<br />
* sending HDMI Output to external monitor<br />
* all the messages were displayed on the serial console connected via Micro USB cable<br />
* firmware running from eMMC Flash memory<br />
* Ethernet cable connected to network switch placed outside of the chamber<br />
* 2x USB device connected and placed outside of the chamber<br />
* WiFi and Bluetooth module active, connected to the antennas and running discovery mode<br />
* standard 25x25x25mm heatsink<br />
<br /><br />
'''1x iMX93 Industrial Development Kit [setup no. 2] in [[iMX93 Industrial Pro|Pro configuration]] and Industrial temperature range<br />CPU and memory stress testing'''<br />
* 1 thread of extensive DDR4 Memory stress test<br />
* 1 thread of CPU stress test<br />
* sending HDMI Output to external monitor<br />
* NXP MIPI-CSI camera connected and capturing video stream<br />
* all the messages were displayed on the serial console connected via Micro USB cable<br />
* firmware running from eMMC Flash memory<br />
* Ethernet cable connected to network switch placed outside of the chamber<br />
* 2x USB device connected and placed outside of the chamber<br />
* WiFi and Bluetooth module active, connected to the antennas and running discovery mode<br />
* standard 25x25x25mm heatsink<br />
<br /><br />
'''1x iMX93 Industrial Development Kit [setup no. 1] in [[iMX93 Industrial Basic|Basic configuration]] and Industrial temperature range<br />CPU and memory stress testing'''<br />
* 1 thread of extensive DDR4 Memory stress test<br />
* 1 thread of CPU stress test<br />
* sending HDMI Output to external monitor<br />
* all the messages were displayed on the serial console connected via Micro USB cable<br />
* firmware running from eMMC Flash memory<br />
* Ethernet cable connected to network switch placed outside of the chamber<br />
* 2x USB device connected and placed outside of the chamber<br />
* WiFi PCI Express card plugged in, connected to the antennas and running discovery mode<br />
* standard 25x25x25mm heatsink<br />
<br /><br />
'''1x iMX93 Industrial Development Kit [setup no. 3] in [[iMX93 Industrial Max|Max configuration]] and Commercial temperature range<br />CPU and memory stress testing'''<br />
* 1 thread of extensive DDR4 Memory stress test<br />
* 1 thread of CPU stress test<br />
* sending HDMI Output to external monitor<br />
* Digilent MIPI-CSI camera connected and capturing video stream<br />
* all the messages were displayed on the serial console connected via Micro USB cable<br />
* firmware running from eMMC Flash memory<br />
* Ethernet cable connected to network switch placed outside of the chamber<br />
* 2x USB device connected and placed outside of the chamber<br />
* WiFi and Bluetooth module active, connected to the antennas and running discovery mode<br />
* standard 25x25x25mm heatsink<br />
<br /><br />
Power sources, USB flash devices, network switch, HDMI monitor and controlling PC were placed outside the environmental chamber. All the scripts running during the test and the board setup instructions can be found in section [[#Preparing the test|How to prepare the test]].<br />
<br />
== Testing Results ==<br />
The picture below shows the temperature profile during the whole testing process. Humidity was not controlled. The temperature gradient for the environment chamber was set to 1°C/min.<br /><br />
[[image:iMX8M_Industrial_Development_Kit-Env_chamber_temperature_profile.png|800px]]<br />
<br />
=== Running the development kits at -40°C – PASS ===<br />
Test description: CPU, Memory and peripheral stress tests were running at -40°C. All the tested kits were working without errors during the whole time, even if some components used for iMX93 Industrial Development Kit Max in Commercial temperature range were only rated for the temperature range between 0°C and +95°C.<br /><br /><br />
<br />
A closer image on the temperature chamber displaying the minimum temperature is shown below. These readouts are available on the display:<br />
* the first number shows current temperature<br />
* the second one set temperature<br />
* the last two shows relative humidity. Humidity was not controlled during testing process.<br />
[[image:iMX8M Industrial Kit-Env chamber-Boards at -40C.jpg|800px]]<br />
<br /><br /><br />
[[image:iMX8M_Industrial_Development_Kit-Env_chamber_at_-40C.jpg|800px]]<br />
<br />
=== Running the development kits at +85°C – PASS ===<br />
Test description: The pre-set temperature profile was followed until the development kits gradually reached +85°C. The kits remained around this temperature for the duration of two hours and at the end of this whole cycle all the kits were running.<br /><br />
[[image:iMX8M_Industrial_Kit-Env_chamber-Boards_at_+86C.jpg|800px]]<br />
<br /><br /><br />
[[image:iMX8M_Industrial_Development_Kit-Env_chamber_at_+85C.jpg|800px]]<br />
<br />
=== Switch OFF/ON test at -40°C – PASS ===<br />
Test description: At temperature -40°C the development kits were switched OFF, left OFF for at least 15 minutes (to cool down completely) and then switched ON to see if they boot up without problems. Once booted up into Linux, the test script was launched to test RAM memory and all peripherals. The kits were turned OFF and ON again multiple times to see potential issues at the lowest temperature level. All of the tested setups booted up successfully.<br />
<br />
<br /><br />
[[image:iMX8M Industrial Kit-Env chamber-Boards snow.jpg|800px]]<br />
<br />
== PC setup ==<br />
The PC was used during the test to control / monitor all the kits through serial console sessions. The control computer was running Windows 10 operating system.<br />
<br />
=== HDMI Outputs and Serial consoles ===<br />
To control iMX93 Industrial Development Kits, one TeraTerm serial console was opened for each setup. The kits were connected to the external HDMI switch to monitor HDMI outputs.<br />
<br /><br /><br />
The setup of the environmental chamber cables and out-of-chamber equipment:<br />
<br /><br />
[[image:iMX8M Industrial Development Kit-Climate chamber overview.jpg|800px]]<br />
<br />
== Preparing the test ==<br />
=== Boot device and software ===<br />
The eMMC memory was selected as a booting device for all the kits. Device tree files were not adjusted as the default configuration was used. The only change compared to standard software package was running the test script. In order to flash a fresh firmware into the eMMC Memory follow [[iMX93_Industrial_Flashing_Procedure|these instructions]].<br />
<br />
=== Downloading stress test ===<br />
Stress-ng package was selected to check CPU and memory integrity. Placing this file into the same directory where the testing script will be stored is important:<br />
<syntaxhighlight lang="bash"><br />
wget https://downloads.voipac.com/files/iMX93_Industrial_Development_Kit/module/documents/Thermal_stress_resistance/iMX93q-voipac-peripheral-test.sh<br />
</syntaxhighlight><br />
<br />
=== Start CPU and memory stress test ===<br />
Navigate into the directory, where stress test feature and the testing script are stored.<br /><br /><br />
<br />
Stress sequence script:<br />
<syntaxhighlight lang="bash"><br />
for d in $(seq 1 1 99999)<br />
do<br />
uptime<br />
echo "Test $a Test $b Test $c $d times"<br />
echo "Start stress-ng --iomix 1 -t 10 -v"<br />
stress-ng --iomix 1 -t 10 -v<br />
echo "End"<br />
echo "Start stress-ng --cpu 2 --vm 4 -t 10"<br />
stress-ng --cpu 2 --vm 4 -t 10<br />
echo "End"<br />
echo "Start stress-ng --shm 0 -t 10"<br />
stress-ng --shm 0 -t 10<br />
echo "End"<br />
echo "Start stress-ng --seq 0 -t 2 --tz -v"<br />
stress-ng --seq 0 -t 2 --tz -v<br />
echo "End"<br />
echo "Start Thermal zone information"<br />
stress-ng --matrix 0 --tz -t 10 --log-brief -t 10<br />
echo "End"<br />
done<br />
</syntaxhighlight><br />
<br />
=== Start peripheral test ===<br />
Plug the development kit into mains and connect it to the controlling PC via console. Before the first time usage of the script, permissions need to be granted by the following command: <br />
<syntaxhighlight lang="bash"><br />
chmod +x iMX93-voipac-peripheral-test.sh<br />
</syntaxhighlight><br />
<br /><br />
Testing scripts command consists of the following arguments:<br />
* the first parameter - configuration of tested development kit (Max, Pro or Basic)<br />
* the second parameter - USB drive 1 location<br />
* the third parameter - USB drive 2 location<br />
* the fourth parameter - SD card location<br />
<br /><br />
Several commands used during environmental chamber testing are shown below:<br />
<br />
* iMX93 Industrial Development Kit Max:<br />
<syntaxhighlight lang="bash"><br />
./iMX93-voipac-peripheral-test.sh -max sda1 sdb1 mmcblk1p1 | tee -i iMX93-env-testing.log<br />
</syntaxhighlight><br />
* iMX93 Industrial Development Kit Pro:<br />
<syntaxhighlight lang="bash"><br />
./iMX93-voipac-peripheral-test.sh -pro sda1 sdb1 mmcblk1p1 | tee -i iMX93-env-testing.log<br />
</syntaxhighlight><br />
* iMX93 Industrial Development Kit Basic:<br />
<syntaxhighlight lang="bash"><br />
./iMX93-voipac-peripheral-test.sh -basic sda1 sdb1 mmcblk1p1 | tee -i iMX93-env-testing.log<br />
</syntaxhighlight><br />
<br /><br />
The complete script can be found in [https://downloads.voipac.com/files/iMX93_Industrial_Development_Kit/module/documents/Thermal_stress_resistance/iMX93q-voipac-peripheral-test.sh the downloads section] or down below:<br />
<syntaxhighlight lang="bash"><br />
#!/bin/sh<br />
<br />
# iMX93Q environmental chamber peripheral test<br />
<br />
mountDevice() {<br />
mkdir -p "/media/$2"<br />
mount /dev/$1 /media/$2<br />
cat /proc/mounts | grep -F "/dev/$1 /media/$2"<br />
if [ "$?" -eq "0" ]; then<br />
echo "$2 mounted"<br />
else<br />
echo "$2 not mounted"; exit 2<br />
fi<br />
}<br />
<br />
# prepare files<br />
cd ~/<br />
mkdir -p env-chamber-testing/<br />
cd env-chamber-testing/<br />
<br />
touch env-chamber-testing.log<br />
touch cpu-temp.log<br />
<br />
basic=0<br />
pro=0<br />
max=0<br />
case $1 in<br />
-basic) basic=1 ;;<br />
-pro) pro=1 ;;<br />
-max) max=1 ;;<br />
*)<br />
esac<br />
<br />
# mount devices<br />
mountDevice $2 usb0<br />
mountDevice $3 usb1<br />
mountDevice $4 mmc0<br />
<br />
updateLogFiles() {<br />
# obtain board ID from IP address - be sure addresses are allocated based on MAC<br />
boardID=$(/sbin/ip -o -4 addr list eth0 | awk '{print $4}' | cut -d/ -f1 | cut -d'.' -f4 | cut -d'2' -f2);<br />
# be sure time server is running on DHCP server<br />
currentTime=`date +%Y-%m-%d.%H:%M`<br />
<br />
mv env-chamber-testing.log trx-board-$boardID-env-chamber.log.$currentTime<br />
mv cpu-temp.log trx-board-$boardID-env-cpu-temp.log.$currentTime<br />
}<br />
<br />
finish_test_now() {<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) Ctrl+C Detected: End of the test"<br />
precced=0;<br />
#kill -INT $vid_pid $str_pid $log_pid;<br />
sleep 3;<br />
test_status=`cat env-chamber-testing.log | grep -i "error" | grep -v -e "0 errors" -e "no corrected errors"`<br />
if [ -z "$test_status" ]<br />
then<br />
echo "*********TEST PASS*********"<br />
else<br />
echo "*********TEST FAIL*********"<br />
echo "List of detected errors:"<br />
cat env-chamber-testing.log | grep -i "error" | grep -v -e "0 errors" -e "no corrected errors" -e "List of detected errors:"<br />
fi<br />
updateLogFiles<br />
exit;<br />
}<br />
<br />
# kill all processes if Ctrl+C is detected<br />
trap finish_test_now 2<br />
<br />
# play a video stream<br />
gst-launch-1.0 -q imxv4l2src ! autovideosink &<br />
<br />
# stressapptest - CPU threads and RAM memory threads<br />
if [ "${basic}" -eq "1" ]; then<br />
stress-ng --cpu 2 --vm 4 &<br />
str_pid=$!<br />
fi<br />
if [ "${pro}" -eq "1" ]; then<br />
stress-ng --cpu 4 --vm 4 &<br />
str_pid=$!<br />
fi<br />
if [ "${max}" -eq "1" ]; then<br />
stress-ng --cpu 4 --vm 4 &<br />
str_pid=$!<br />
fi<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) Starting stressapptest with PID: " $str_pid<br />
<br />
proceed=1<br />
# create test files<br />
file1_path=`mktemp`<br />
file2_path=`mktemp`<br />
file1=`basename $file1_path`<br />
file2=`basename $file2_path`<br />
<br />
dd if=/dev/urandom of=$file1_path bs=1024 count=10000<br />
dd if=/dev/urandom of=$file2_path bs=1024 count=10000<br />
<br />
cp1_from="/media/mmc0/"<br />
cp1_to="/media/usb0/"<br />
<br />
cp2_from="/media/usb0/"<br />
cp2_to="/media/usb1/"<br />
<br />
#copy files in case they are missing<br />
cp $file1_path $cp1_from<br />
cp $file1_path $cp1_to<br />
cp $file2_path $cp2_from<br />
cp $file2_path $cp2_to<br />
<br />
while [ $proceed -eq 1 ]<br />
do<br />
<br />
ping -q -c1 192.168.0.2 >> env-chamber-testing.log<br />
if [ $? -ne 0 ]<br />
then<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) ERROR: Ping failed"<br />
fi<br />
<br />
cp1_done=`ps | grep $cp1_pid | grep cp`<br />
if [ -z "$cp1_done" ]; then # copy finished<br />
if cmp -s $cp1_from$file1 $cp1_to$file1; then<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) PASS: Copying file from $cp1_from to $cp1_to successful"<br />
else<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) ERROR: Difference between files on $cp1_from and $cp1_to detected"<br />
fi<br />
cp1_temp=$cp1_from # swap destinations<br />
cp1_from=$cp1_to<br />
cp1_to=$cp1_temp<br />
<br />
rm $cp1_to$file1 # remove destination file<br />
<br />
cp $cp1_from$file1 $cp1_to$file1 &<br />
cp1_pid=$!<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) Started copying file from $cp1_from to $cp1_to"<br />
fi<br />
<br />
cp2_done=`ps | grep $cp2_pid | grep cp`<br />
if [ -z "$cp2_done" ]; then # copy finished<br />
if cmp -s $cp2_from$file2 $cp2_to$file2; then<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) PASS: Copying file from $cp2_from to $cp2_to successful"<br />
else<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) ERROR: Difference between files on $cp2_from and $cp2_to detected"<br />
fi<br />
cp2_temp=$cp2_from # swap destinations<br />
cp2_from=$cp2_to<br />
cp2_to=$cp2_temp<br />
<br />
rm $cp2_to$file2 # remove destination file<br />
<br />
cp $cp2_from$file2 $cp2_to$file2 &<br />
cp2_pid=$!<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) Started copying file from $cp2_from to $cp2_to"<br />
fi<br />
<br />
done<br />
</syntaxhighlight></div>
Voipac-hw
https://wiki.voipac.com/index.php?title=iMX93_Industrial_Environmental_chamber_testing&diff=5581
iMX93 Industrial Environmental chamber testing
2025-05-14T14:17:33Z
<p>Voipac-hw: </p>
<hr />
<div>[[Category:iMX93 Industrial Development Kit]]<br />
[[Category:iMX93 Industrial Development Kit Testing]]<br />
<!-- --><br />
<div style="float:right">__TOC__</div><br />
<br />
On this page environmental stress testing results of iMX93 Industrial Development Kit are displayed. Detailed instructions how to setup kits are also shown.<br />
<br />
== Hardware configuration ==<br />
All of the modules used standard specification except of the temperature ranges for the key components as described below:<br />
<br /><br />
* 1x iMX93 Industrial Development Kit in [[iMX93 Industrial Max|Max configuration]]<br />
** i.MX 93 Dual 1.7GHz CPU - extended industrial temperature range (-40°C to +105°C)<br />
** 2GB LPDDR4 Memory - extended industrial temperature range (-40°C to +95°C)<br />
** eMMC Flash 32GB - industrial temperature range (-40°C to +85°C)<br />
** MAYA-W260-00B WiFi & Bluetooth Module - industrial temperature range (-40°C to +85°C)<br />
<br /><br />
* 1x iMX93 Industrial Development Kit in [[iMX93 Industrial Pro|Pro configuration]]<br />
** i.MX 93 Dual 1.7GHz CPU - extended industrial temperature range (-40°C to +105°C)<br />
** 2GB LPDDR4 Memory - automotive temperature range (-40°C to +95°C)<br />
** eMMC Flash 16GB - industrial temperature range (-40°C to +85°C)<br />
** MAYA-W160-00B WiFi & Bluetooth Module - industrial temperature range (-40°C to +85°C)<br />
<br /><br />
* 1x iMX93 Industrial Development Kit in [[iMX93 Industrial Basic|Basic configuration]]<br />
** i.MX 93 Solo 1.7GHz CPU - extended industrial temperature range (-40°C to +105°C)<br />
** 1GB LPDDR4 Memory - industrial temperature range (-40°C to +95°C)<br />
** eMMC Flash 8GB - industrial temperature range (-40°C to +85°C)<br />
<br /><br />
* 1x iMX93 Industrial Development Kit in [[iMX93 Industrial Lite|Lite configuration]]<br />
** i.MX 93 Solo 900MHz CPU - extended commercial temperature range (0°C to +95°C)<br />
** 512MB LPDDR4 Memory - industrial temperature range (-30°C to +85°C)<br />
** eMMC Flash 4GB - extended temperature range (-25°C to +85°C)<br />
<br /><br />
All of the tested modules used standard configuration of iMX Development Baseboard with extended temperature range (-20°C to +70°C). The majority of tested kits used the standard heatsink sized 25x25x25mm, which is included in every development kit package, thus showcasing that this standardised heatsink performs even in very harsh conditions.<br /><br />
<br />
The setup in the environmental chamber:<br /><br />
[[image:iMX93 Industrial Development Kit-Environmental chamber testing-in progress.jpg|800px]]<br />
<br />
== Test description ==<br />
Four iMX93 Industrial Development Kits (one in Max Industrial configuration, one in Pro Industrial configuration, one in Basic Industrial configuration and one in Lite Industrial configuration) were running CPU and memory tests to stress out all the most significant peripherals in the whole Industrial temperature scale, ranging from -40°C to +85°C, to check the reliability and stability of the firmware and hardware design.<br /><br /><br />
<br />
Configuration, software and testing threads in details:<br /><br /><br />
<br />
'''1x iMX93 Industrial Development Kit [setup no. 4] in [[iMX93 Industrial Max|Max configuration]] and Industrial temperature range<br />CPU and memory stress testing'''<br />
* 1 thread of extensive DDR4 Memory stress test<br />
* 1 thread of CPU stress test<br />
* sending HDMI Output to external monitor<br />
* all the messages were displayed on the serial console connected via Micro USB cable<br />
* firmware running from eMMC Flash memory<br />
* Ethernet cable connected to network switch placed outside of the chamber<br />
* 2x USB device connected and placed outside of the chamber<br />
* WiFi and Bluetooth module active, connected to the antennas and running discovery mode<br />
* large 48x48x16mm heatsink<br />
<br /><br />
'''1x iMX93 Industrial Development Kit [setup no. 2] in [[iMX93 Industrial Pro|Pro configuration]] and Industrial temperature range<br />CPU and memory stress testing'''<br />
* 1 thread of extensive DDR4 Memory stress test<br />
* 1 thread of CPU stress test<br />
* sending HDMI Output to external monitor<br />
* NXP MIPI-CSI camera connected and capturing video stream<br />
* all the messages were displayed on the serial console connected via Micro USB cable<br />
* firmware running from eMMC Flash memory<br />
* Ethernet cable connected to network switch placed outside of the chamber<br />
* 2x USB device connected and placed outside of the chamber<br />
* WiFi and Bluetooth module active, connected to the antennas and running discovery mode<br />
* standard 25x25x25mm heatsink<br />
<br /><br />
'''1x iMX93 Industrial Development Kit [setup no. 1] in [[iMX93 Industrial Basic|Basic configuration]] and Industrial temperature range<br />CPU and memory stress testing'''<br />
* 1 thread of extensive DDR4 Memory stress test<br />
* 1 thread of CPU stress test<br />
* sending HDMI Output to external monitor<br />
* all the messages were displayed on the serial console connected via Micro USB cable<br />
* firmware running from eMMC Flash memory<br />
* Ethernet cable connected to network switch placed outside of the chamber<br />
* 2x USB device connected and placed outside of the chamber<br />
* WiFi PCI Express card plugged in, connected to the antennas and running discovery mode<br />
* standard 25x25x25mm heatsink<br />
<br /><br />
'''1x iMX93 Industrial Development Kit [setup no. 3] in [[iMX93 Industrial Max|Max configuration]] and Commercial temperature range<br />CPU and memory stress testing'''<br />
* 1 thread of extensive DDR4 Memory stress test<br />
* 1 thread of CPU stress test<br />
* sending HDMI Output to external monitor<br />
* Digilent MIPI-CSI camera connected and capturing video stream<br />
* all the messages were displayed on the serial console connected via Micro USB cable<br />
* firmware running from eMMC Flash memory<br />
* Ethernet cable connected to network switch placed outside of the chamber<br />
* 2x USB device connected and placed outside of the chamber<br />
* WiFi and Bluetooth module active, connected to the antennas and running discovery mode<br />
* standard 25x25x25mm heatsink including a fan<br />
<br /><br />
Power sources, USB flash devices, network switch, HDMI monitor and controlling PC were placed outside the environmental chamber. All the scripts running during the test and the board setup instructions can be found in section [[#Preparing the test|How to prepare the test]].<br />
<br />
== Testing Results ==<br />
The picture below shows the temperature profile during the whole testing process. Humidity was not controlled. The temperature gradient for the environment chamber was set to 1°C/min.<br /><br />
[[image:iMX8M_Industrial_Development_Kit-Env_chamber_temperature_profile.png|800px]]<br />
<br />
=== Running the development kits at -40°C – PASS ===<br />
Test description: CPU, Memory and peripheral stress tests were running at -40°C. All the tested kits were working without errors during the whole time, even if some components used for iMX93 Industrial Development Kit Max in Commercial temperature range were only rated for the temperature range between 0°C and +95°C.<br /><br /><br />
<br />
A closer image on the temperature chamber displaying the minimum temperature is shown below. These readouts are available on the display:<br />
* the first number shows current temperature<br />
* the second one set temperature<br />
* the last two shows relative humidity. Humidity was not controlled during testing process.<br />
[[image:iMX8M Industrial Kit-Env chamber-Boards at -40C.jpg|800px]]<br />
<br /><br /><br />
[[image:iMX8M_Industrial_Development_Kit-Env_chamber_at_-40C.jpg|800px]]<br />
<br />
=== Running the development kits at +85°C – PASS ===<br />
Test description: The pre-set temperature profile was followed until the development kits gradually reached +85°C. The kits remained around this temperature for the duration of two hours and at the end of this whole cycle all the kits were running.<br /><br />
[[image:iMX8M_Industrial_Kit-Env_chamber-Boards_at_+86C.jpg|800px]]<br />
<br /><br /><br />
[[image:iMX8M_Industrial_Development_Kit-Env_chamber_at_+85C.jpg|800px]]<br />
<br />
=== Switch OFF/ON test at -40°C – PASS ===<br />
Test description: At temperature -40°C the development kits were switched OFF, left OFF for at least 15 minutes (to cool down completely) and then switched ON to see if they boot up without problems. Once booted up into Linux, the test script was launched to test RAM memory and all peripherals. The kits were turned OFF and ON again multiple times to see potential issues at the lowest temperature level. All of the tested setups booted up successfully.<br />
<br />
<br /><br />
[[image:iMX8M Industrial Kit-Env chamber-Boards snow.jpg|800px]]<br />
<br />
== PC setup ==<br />
The PC was used during the test to control / monitor all the kits through serial console sessions. The control computer was running Windows 10 operating system.<br />
<br />
=== HDMI Outputs and Serial consoles ===<br />
To control iMX93 Industrial Development Kits, one TeraTerm serial console was opened for each setup. The kits were connected to the external HDMI switch to monitor HDMI outputs.<br />
<br /><br /><br />
The setup of the environmental chamber cables and out-of-chamber equipment:<br />
<br /><br />
[[image:iMX8M Industrial Development Kit-Climate chamber overview.jpg|800px]]<br />
<br />
== Preparing the test ==<br />
=== Boot device and software ===<br />
The eMMC memory was selected as a booting device for all the kits. Device tree files were not adjusted as the default configuration was used. The only change compared to standard software package was running the test script. In order to flash a fresh firmware into the eMMC Memory follow [[iMX93_Industrial_Flashing_Procedure|these instructions]].<br />
<br />
=== Downloading stress test ===<br />
Stress-ng package was selected to check CPU and memory integrity. Placing this file into the same directory where the testing script will be stored is important:<br />
<syntaxhighlight lang="bash"><br />
wget https://downloads.voipac.com/files/iMX93_Industrial_Development_Kit/module/documents/Thermal_stress_resistance/iMX93q-voipac-peripheral-test.sh<br />
</syntaxhighlight><br />
<br />
=== Start CPU and memory stress test ===<br />
Navigate into the directory, where stress test feature and the testing script are stored.<br /><br /><br />
<br />
Stress sequence script:<br />
<syntaxhighlight lang="bash"><br />
for d in $(seq 1 1 99999)<br />
do<br />
uptime<br />
echo "Test $a Test $b Test $c $d times"<br />
echo "Start stress-ng --iomix 1 -t 10 -v"<br />
stress-ng --iomix 1 -t 10 -v<br />
echo "End"<br />
echo "Start stress-ng --cpu 2 --vm 4 -t 10"<br />
stress-ng --cpu 2 --vm 4 -t 10<br />
echo "End"<br />
echo "Start stress-ng --shm 0 -t 10"<br />
stress-ng --shm 0 -t 10<br />
echo "End"<br />
echo "Start stress-ng --seq 0 -t 2 --tz -v"<br />
stress-ng --seq 0 -t 2 --tz -v<br />
echo "End"<br />
echo "Start Thermal zone information"<br />
stress-ng --matrix 0 --tz -t 10 --log-brief -t 10<br />
echo "End"<br />
done<br />
</syntaxhighlight><br />
<br />
=== Start peripheral test ===<br />
Plug the development kit into mains and connect it to the controlling PC via console. Before the first time usage of the script, permissions need to be granted by the following command: <br />
<syntaxhighlight lang="bash"><br />
chmod +x iMX93-voipac-peripheral-test.sh<br />
</syntaxhighlight><br />
<br /><br />
Testing scripts command consists of the following arguments:<br />
* the first parameter - configuration of tested development kit (Max, Pro or Basic)<br />
* the second parameter - USB drive 1 location<br />
* the third parameter - USB drive 2 location<br />
* the fourth parameter - SD card location<br />
<br /><br />
Several commands used during environmental chamber testing are shown below:<br />
<br />
* iMX93 Industrial Development Kit Max:<br />
<syntaxhighlight lang="bash"><br />
./iMX93-voipac-peripheral-test.sh -max sda1 sdb1 mmcblk1p1 | tee -i iMX93-env-testing.log<br />
</syntaxhighlight><br />
* iMX93 Industrial Development Kit Pro:<br />
<syntaxhighlight lang="bash"><br />
./iMX93-voipac-peripheral-test.sh -pro sda1 sdb1 mmcblk1p1 | tee -i iMX93-env-testing.log<br />
</syntaxhighlight><br />
* iMX93 Industrial Development Kit Basic:<br />
<syntaxhighlight lang="bash"><br />
./iMX93-voipac-peripheral-test.sh -basic sda1 sdb1 mmcblk1p1 | tee -i iMX93-env-testing.log<br />
</syntaxhighlight><br />
<br /><br />
The complete script can be found in [https://downloads.voipac.com/files/iMX93_Industrial_Development_Kit/module/documents/Thermal_stress_resistance/iMX93q-voipac-peripheral-test.sh the downloads section] or down below:<br />
<syntaxhighlight lang="bash"><br />
#!/bin/sh<br />
<br />
# iMX93Q environmental chamber peripheral test<br />
<br />
mountDevice() {<br />
mkdir -p "/media/$2"<br />
mount /dev/$1 /media/$2<br />
cat /proc/mounts | grep -F "/dev/$1 /media/$2"<br />
if [ "$?" -eq "0" ]; then<br />
echo "$2 mounted"<br />
else<br />
echo "$2 not mounted"; exit 2<br />
fi<br />
}<br />
<br />
# prepare files<br />
cd ~/<br />
mkdir -p env-chamber-testing/<br />
cd env-chamber-testing/<br />
<br />
touch env-chamber-testing.log<br />
touch cpu-temp.log<br />
<br />
basic=0<br />
pro=0<br />
max=0<br />
case $1 in<br />
-basic) basic=1 ;;<br />
-pro) pro=1 ;;<br />
-max) max=1 ;;<br />
*)<br />
esac<br />
<br />
# mount devices<br />
mountDevice $2 usb0<br />
mountDevice $3 usb1<br />
mountDevice $4 mmc0<br />
<br />
updateLogFiles() {<br />
# obtain board ID from IP address - be sure addresses are allocated based on MAC<br />
boardID=$(/sbin/ip -o -4 addr list eth0 | awk '{print $4}' | cut -d/ -f1 | cut -d'.' -f4 | cut -d'2' -f2);<br />
# be sure time server is running on DHCP server<br />
currentTime=`date +%Y-%m-%d.%H:%M`<br />
<br />
mv env-chamber-testing.log trx-board-$boardID-env-chamber.log.$currentTime<br />
mv cpu-temp.log trx-board-$boardID-env-cpu-temp.log.$currentTime<br />
}<br />
<br />
finish_test_now() {<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) Ctrl+C Detected: End of the test"<br />
precced=0;<br />
#kill -INT $vid_pid $str_pid $log_pid;<br />
sleep 3;<br />
test_status=`cat env-chamber-testing.log | grep -i "error" | grep -v -e "0 errors" -e "no corrected errors"`<br />
if [ -z "$test_status" ]<br />
then<br />
echo "*********TEST PASS*********"<br />
else<br />
echo "*********TEST FAIL*********"<br />
echo "List of detected errors:"<br />
cat env-chamber-testing.log | grep -i "error" | grep -v -e "0 errors" -e "no corrected errors" -e "List of detected errors:"<br />
fi<br />
updateLogFiles<br />
exit;<br />
}<br />
<br />
# kill all processes if Ctrl+C is detected<br />
trap finish_test_now 2<br />
<br />
# play a video stream<br />
gst-launch-1.0 -q imxv4l2src ! autovideosink &<br />
<br />
# stressapptest - CPU threads and RAM memory threads<br />
if [ "${basic}" -eq "1" ]; then<br />
stress-ng --cpu 2 --vm 4 &<br />
str_pid=$!<br />
fi<br />
if [ "${pro}" -eq "1" ]; then<br />
stress-ng --cpu 4 --vm 4 &<br />
str_pid=$!<br />
fi<br />
if [ "${max}" -eq "1" ]; then<br />
stress-ng --cpu 4 --vm 4 &<br />
str_pid=$!<br />
fi<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) Starting stressapptest with PID: " $str_pid<br />
<br />
proceed=1<br />
# create test files<br />
file1_path=`mktemp`<br />
file2_path=`mktemp`<br />
file1=`basename $file1_path`<br />
file2=`basename $file2_path`<br />
<br />
dd if=/dev/urandom of=$file1_path bs=1024 count=10000<br />
dd if=/dev/urandom of=$file2_path bs=1024 count=10000<br />
<br />
cp1_from="/media/mmc0/"<br />
cp1_to="/media/usb0/"<br />
<br />
cp2_from="/media/usb0/"<br />
cp2_to="/media/usb1/"<br />
<br />
#copy files in case they are missing<br />
cp $file1_path $cp1_from<br />
cp $file1_path $cp1_to<br />
cp $file2_path $cp2_from<br />
cp $file2_path $cp2_to<br />
<br />
while [ $proceed -eq 1 ]<br />
do<br />
<br />
ping -q -c1 192.168.0.2 >> env-chamber-testing.log<br />
if [ $? -ne 0 ]<br />
then<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) ERROR: Ping failed"<br />
fi<br />
<br />
cp1_done=`ps | grep $cp1_pid | grep cp`<br />
if [ -z "$cp1_done" ]; then # copy finished<br />
if cmp -s $cp1_from$file1 $cp1_to$file1; then<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) PASS: Copying file from $cp1_from to $cp1_to successful"<br />
else<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) ERROR: Difference between files on $cp1_from and $cp1_to detected"<br />
fi<br />
cp1_temp=$cp1_from # swap destinations<br />
cp1_from=$cp1_to<br />
cp1_to=$cp1_temp<br />
<br />
rm $cp1_to$file1 # remove destination file<br />
<br />
cp $cp1_from$file1 $cp1_to$file1 &<br />
cp1_pid=$!<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) Started copying file from $cp1_from to $cp1_to"<br />
fi<br />
<br />
cp2_done=`ps | grep $cp2_pid | grep cp`<br />
if [ -z "$cp2_done" ]; then # copy finished<br />
if cmp -s $cp2_from$file2 $cp2_to$file2; then<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) PASS: Copying file from $cp2_from to $cp2_to successful"<br />
else<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) ERROR: Difference between files on $cp2_from and $cp2_to detected"<br />
fi<br />
cp2_temp=$cp2_from # swap destinations<br />
cp2_from=$cp2_to<br />
cp2_to=$cp2_temp<br />
<br />
rm $cp2_to$file2 # remove destination file<br />
<br />
cp $cp2_from$file2 $cp2_to$file2 &<br />
cp2_pid=$!<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) Started copying file from $cp2_from to $cp2_to"<br />
fi<br />
<br />
done<br />
</syntaxhighlight></div>
Voipac-hw
https://wiki.voipac.com/index.php?title=iMX93_Industrial_Environmental_chamber_testing&diff=5579
iMX93 Industrial Environmental chamber testing
2025-05-14T14:11:11Z
<p>Voipac-hw: </p>
<hr />
<div>[[Category:iMX93 Industrial Development Kit]]<br />
[[Category:iMX93 Industrial Development Kit Testing]]<br />
<!-- --><br />
<div style="float:right">__TOC__</div><br />
<br />
On this page environmental stress testing results of iMX93 Industrial Development Kit are displayed. Detailed instructions how to setup kits are also shown.<br />
<br />
== Hardware configuration ==<br />
All of the modules used standard specification except of the temperature ranges for the key components as described below:<br />
<br /><br />
* 1x iMX93 Industrial Development Kit in [[iMX93 Industrial Max|Max configuration]]<br />
** i.MX 93 Dual 1.7GHz CPU - extended industrial temperature range (-40°C to +105°C)<br />
** 2GB LPDDR4 Memory - extended industrial temperature range (-40°C to +95°C)<br />
** eMMC Flash 32GB - industrial temperature range (-40°C to +85°C)<br />
** MAYA-W260-00B WiFi & Bluetooth Module - industrial temperature range (-40°C to +85°C)<br />
<br /><br />
* 1x iMX93 Industrial Development Kit in [[iMX93 Industrial Pro|Pro configuration]]<br />
** i.MX 93 Dual 1.7GHz CPU - extended industrial temperature range (-40°C to +105°C)<br />
** 2GB LPDDR4 Memory - automotive temperature range (-40°C to +95°C)<br />
** eMMC Flash 16GB - industrial temperature range (-40°C to +85°C)<br />
** MAYA-W160-00B WiFi & Bluetooth Module - industrial temperature range (-40°C to +85°C)<br />
<br /><br />
* 1x iMX93 Industrial Development Kit in [[iMX93 Industrial Basic|Basic configuration]]<br />
** i.MX 93 Solo 1.7GHz CPU - extended industrial temperature range (-40°C to +105°C)<br />
** 1GB LPDDR4 Memory - industrial temperature range (-40°C to +95°C)<br />
** eMMC Flash 8GB - industrial temperature range (-40°C to +85°C)<br />
<br /><br />
* 1x iMX93 Industrial Development Kit in [[iMX93 Industrial Lite|Lite configuration]]<br />
** i.MX 93 Solo 900MHz CPU - extended commercial temperature range (0°C to +95°C)<br />
** 512MB LPDDR4 Memory - industrial temperature range (-30°C to +85°C)<br />
** eMMC Flash 4GB - extended temperature range (-25°C to +85°C)<br />
<br /><br />
All of the tested modules used standard configuration of iMX Development Baseboard with extended temperature range (-20°C to +70°C). The majority of tested kits used the standard heatsink sized 25x25x25mm, which is included in every development kit package, thus showcasing that this standardised heatsink performs even in very harsh conditions.<br /><br />
<br />
The setup in the environmental chamber:<br /><br />
[[image:iMX8M_Industrial_Development_Kits-Enviromental_chamber_overview_with_description.jpg|800px]]<br />
<br />
== Test description ==<br />
Four iMX93 Industrial Development Kits (one in Max Industrial configuration, one in Pro Industrial configuration, one in Basic Industrial configuration and one in Max Commercial configuration) were running CPU and memory tests to stress out all the most significant peripherals in the whole Industrial temperature scale, ranging from -40°C to +85°C, to check the reliability and stability of the firmware and hardware design.<br /><br /><br />
<br />
Configuration, software and testing threads in details:<br /><br /><br />
<br />
'''1x iMX93 Industrial Development Kit [setup no. 4] in [[iMX93 Industrial Max|Max configuration]] and Industrial temperature range<br />CPU and memory stress testing'''<br />
* 1 thread of extensive DDR4 Memory stress test<br />
* 1 thread of CPU stress test<br />
* sending HDMI Output to external monitor<br />
* all the messages were displayed on the serial console connected via Micro USB cable<br />
* firmware running from eMMC Flash memory<br />
* Ethernet cable connected to network switch placed outside of the chamber<br />
* 2x USB device connected and placed outside of the chamber<br />
* WiFi and Bluetooth module active, connected to the antennas and running discovery mode<br />
* large 48x48x16mm heatsink<br />
<br /><br />
'''1x iMX93 Industrial Development Kit [setup no. 2] in [[iMX93 Industrial Pro|Pro configuration]] and Industrial temperature range<br />CPU and memory stress testing'''<br />
* 1 thread of extensive DDR4 Memory stress test<br />
* 1 thread of CPU stress test<br />
* sending HDMI Output to external monitor<br />
* NXP MIPI-CSI camera connected and capturing video stream<br />
* all the messages were displayed on the serial console connected via Micro USB cable<br />
* firmware running from eMMC Flash memory<br />
* Ethernet cable connected to network switch placed outside of the chamber<br />
* 2x USB device connected and placed outside of the chamber<br />
* WiFi and Bluetooth module active, connected to the antennas and running discovery mode<br />
* standard 25x25x25mm heatsink<br />
<br /><br />
'''1x iMX93 Industrial Development Kit [setup no. 1] in [[iMX93 Industrial Basic|Basic configuration]] and Industrial temperature range<br />CPU and memory stress testing'''<br />
* 1 thread of extensive DDR4 Memory stress test<br />
* 1 thread of CPU stress test<br />
* sending HDMI Output to external monitor<br />
* all the messages were displayed on the serial console connected via Micro USB cable<br />
* firmware running from eMMC Flash memory<br />
* Ethernet cable connected to network switch placed outside of the chamber<br />
* 2x USB device connected and placed outside of the chamber<br />
* WiFi PCI Express card plugged in, connected to the antennas and running discovery mode<br />
* standard 25x25x25mm heatsink<br />
<br /><br />
'''1x iMX93 Industrial Development Kit [setup no. 3] in [[iMX93 Industrial Max|Max configuration]] and Commercial temperature range<br />CPU and memory stress testing'''<br />
* 1 thread of extensive DDR4 Memory stress test<br />
* 1 thread of CPU stress test<br />
* sending HDMI Output to external monitor<br />
* Digilent MIPI-CSI camera connected and capturing video stream<br />
* all the messages were displayed on the serial console connected via Micro USB cable<br />
* firmware running from eMMC Flash memory<br />
* Ethernet cable connected to network switch placed outside of the chamber<br />
* 2x USB device connected and placed outside of the chamber<br />
* WiFi and Bluetooth module active, connected to the antennas and running discovery mode<br />
* standard 25x25x25mm heatsink including a fan<br />
<br /><br />
Power sources, USB flash devices, network switch, HDMI monitor and controlling PC were placed outside the environmental chamber. All the scripts running during the test and the board setup instructions can be found in section [[#Preparing the test|How to prepare the test]].<br />
<br />
== Testing Results ==<br />
The picture below shows the temperature profile during the whole testing process. Humidity was not controlled. The temperature gradient for the environment chamber was set to 1°C/min.<br /><br />
[[image:iMX8M_Industrial_Development_Kit-Env_chamber_temperature_profile.png|800px]]<br />
<br />
=== Running the development kits at -40°C – PASS ===<br />
Test description: CPU, Memory and peripheral stress tests were running at -40°C. All the tested kits were working without errors during the whole time, even if some components used for iMX93 Industrial Development Kit Max in Commercial temperature range were only rated for the temperature range between 0°C and +95°C.<br /><br /><br />
<br />
A closer image on the temperature chamber displaying the minimum temperature is shown below. These readouts are available on the display:<br />
* the first number shows current temperature<br />
* the second one set temperature<br />
* the last two shows relative humidity. Humidity was not controlled during testing process.<br />
[[image:iMX8M Industrial Kit-Env chamber-Boards at -40C.jpg|800px]]<br />
<br /><br /><br />
[[image:iMX8M_Industrial_Development_Kit-Env_chamber_at_-40C.jpg|800px]]<br />
<br />
=== Running the development kits at +85°C – PASS ===<br />
Test description: The pre-set temperature profile was followed until the development kits gradually reached +85°C. The kits remained around this temperature for the duration of two hours and at the end of this whole cycle all the kits were running.<br /><br />
[[image:iMX8M_Industrial_Kit-Env_chamber-Boards_at_+86C.jpg|800px]]<br />
<br /><br /><br />
[[image:iMX8M_Industrial_Development_Kit-Env_chamber_at_+85C.jpg|800px]]<br />
<br />
=== Switch OFF/ON test at -40°C – PASS ===<br />
Test description: At temperature -40°C the development kits were switched OFF, left OFF for at least 15 minutes (to cool down completely) and then switched ON to see if they boot up without problems. Once booted up into Linux, the test script was launched to test RAM memory and all peripherals. The kits were turned OFF and ON again multiple times to see potential issues at the lowest temperature level. All of the tested setups booted up successfully.<br />
<br />
<br /><br />
[[image:iMX8M Industrial Kit-Env chamber-Boards snow.jpg|800px]]<br />
<br />
== PC setup ==<br />
The PC was used during the test to control / monitor all the kits through serial console sessions. The control computer was running Windows 10 operating system.<br />
<br />
=== HDMI Outputs and Serial consoles ===<br />
To control iMX93 Industrial Development Kits, one TeraTerm serial console was opened for each setup. The kits were connected to the external HDMI switch to monitor HDMI outputs.<br />
<br /><br /><br />
The setup of the environmental chamber cables and out-of-chamber equipment:<br />
<br /><br />
[[image:iMX8M Industrial Development Kit-Climate chamber overview.jpg|800px]]<br />
<br />
== Preparing the test ==<br />
=== Boot device and software ===<br />
The eMMC memory was selected as a booting device for all the kits. Device tree files were not adjusted as the default configuration was used. The only change compared to standard software package was running the test script. In order to flash a fresh firmware into the eMMC Memory follow [[iMX93_Industrial_Flashing_Procedure|these instructions]].<br />
<br />
=== Downloading stress test ===<br />
Stress-ng package was selected to check CPU and memory integrity. Placing this file into the same directory where the testing script will be stored is important:<br />
<syntaxhighlight lang="bash"><br />
wget https://downloads.voipac.com/files/iMX93_Industrial_Development_Kit/module/documents/Thermal_stress_resistance/iMX93q-voipac-peripheral-test.sh<br />
</syntaxhighlight><br />
<br />
=== Start CPU and memory stress test ===<br />
Navigate into the directory, where stress test feature and the testing script are stored.<br /><br /><br />
<br />
Stress sequence script:<br />
<syntaxhighlight lang="bash"><br />
for d in $(seq 1 1 99999)<br />
do<br />
uptime<br />
echo "Test $a Test $b Test $c $d times"<br />
echo "Start stress-ng --iomix 1 -t 10 -v"<br />
stress-ng --iomix 1 -t 10 -v<br />
echo "End"<br />
echo "Start stress-ng --cpu 2 --vm 4 -t 10"<br />
stress-ng --cpu 2 --vm 4 -t 10<br />
echo "End"<br />
echo "Start stress-ng --shm 0 -t 10"<br />
stress-ng --shm 0 -t 10<br />
echo "End"<br />
echo "Start stress-ng --seq 0 -t 2 --tz -v"<br />
stress-ng --seq 0 -t 2 --tz -v<br />
echo "End"<br />
echo "Start Thermal zone information"<br />
stress-ng --matrix 0 --tz -t 10 --log-brief -t 10<br />
echo "End"<br />
done<br />
</syntaxhighlight><br />
<br />
=== Start peripheral test ===<br />
Plug the development kit into mains and connect it to the controlling PC via console. Before the first time usage of the script, permissions need to be granted by the following command: <br />
<syntaxhighlight lang="bash"><br />
chmod +x iMX93-voipac-peripheral-test.sh<br />
</syntaxhighlight><br />
<br /><br />
Testing scripts command consists of the following arguments:<br />
* the first parameter - configuration of tested development kit (Max, Pro or Basic)<br />
* the second parameter - USB drive 1 location<br />
* the third parameter - USB drive 2 location<br />
* the fourth parameter - SD card location<br />
<br /><br />
Several commands used during environmental chamber testing are shown below:<br />
<br />
* iMX93 Industrial Development Kit Max:<br />
<syntaxhighlight lang="bash"><br />
./iMX93-voipac-peripheral-test.sh -max sda1 sdb1 mmcblk1p1 | tee -i iMX93-env-testing.log<br />
</syntaxhighlight><br />
* iMX93 Industrial Development Kit Pro:<br />
<syntaxhighlight lang="bash"><br />
./iMX93-voipac-peripheral-test.sh -pro sda1 sdb1 mmcblk1p1 | tee -i iMX93-env-testing.log<br />
</syntaxhighlight><br />
* iMX93 Industrial Development Kit Basic:<br />
<syntaxhighlight lang="bash"><br />
./iMX93-voipac-peripheral-test.sh -basic sda1 sdb1 mmcblk1p1 | tee -i iMX93-env-testing.log<br />
</syntaxhighlight><br />
<br /><br />
The complete script can be found in [https://downloads.voipac.com/files/iMX93_Industrial_Development_Kit/module/documents/Thermal_stress_resistance/iMX93q-voipac-peripheral-test.sh the downloads section] or down below:<br />
<syntaxhighlight lang="bash"><br />
#!/bin/sh<br />
<br />
# iMX93Q environmental chamber peripheral test<br />
<br />
mountDevice() {<br />
mkdir -p "/media/$2"<br />
mount /dev/$1 /media/$2<br />
cat /proc/mounts | grep -F "/dev/$1 /media/$2"<br />
if [ "$?" -eq "0" ]; then<br />
echo "$2 mounted"<br />
else<br />
echo "$2 not mounted"; exit 2<br />
fi<br />
}<br />
<br />
# prepare files<br />
cd ~/<br />
mkdir -p env-chamber-testing/<br />
cd env-chamber-testing/<br />
<br />
touch env-chamber-testing.log<br />
touch cpu-temp.log<br />
<br />
basic=0<br />
pro=0<br />
max=0<br />
case $1 in<br />
-basic) basic=1 ;;<br />
-pro) pro=1 ;;<br />
-max) max=1 ;;<br />
*)<br />
esac<br />
<br />
# mount devices<br />
mountDevice $2 usb0<br />
mountDevice $3 usb1<br />
mountDevice $4 mmc0<br />
<br />
updateLogFiles() {<br />
# obtain board ID from IP address - be sure addresses are allocated based on MAC<br />
boardID=$(/sbin/ip -o -4 addr list eth0 | awk '{print $4}' | cut -d/ -f1 | cut -d'.' -f4 | cut -d'2' -f2);<br />
# be sure time server is running on DHCP server<br />
currentTime=`date +%Y-%m-%d.%H:%M`<br />
<br />
mv env-chamber-testing.log trx-board-$boardID-env-chamber.log.$currentTime<br />
mv cpu-temp.log trx-board-$boardID-env-cpu-temp.log.$currentTime<br />
}<br />
<br />
finish_test_now() {<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) Ctrl+C Detected: End of the test"<br />
precced=0;<br />
#kill -INT $vid_pid $str_pid $log_pid;<br />
sleep 3;<br />
test_status=`cat env-chamber-testing.log | grep -i "error" | grep -v -e "0 errors" -e "no corrected errors"`<br />
if [ -z "$test_status" ]<br />
then<br />
echo "*********TEST PASS*********"<br />
else<br />
echo "*********TEST FAIL*********"<br />
echo "List of detected errors:"<br />
cat env-chamber-testing.log | grep -i "error" | grep -v -e "0 errors" -e "no corrected errors" -e "List of detected errors:"<br />
fi<br />
updateLogFiles<br />
exit;<br />
}<br />
<br />
# kill all processes if Ctrl+C is detected<br />
trap finish_test_now 2<br />
<br />
# play a video stream<br />
gst-launch-1.0 -q imxv4l2src ! autovideosink &<br />
<br />
# stressapptest - CPU threads and RAM memory threads<br />
if [ "${basic}" -eq "1" ]; then<br />
stress-ng --cpu 2 --vm 4 &<br />
str_pid=$!<br />
fi<br />
if [ "${pro}" -eq "1" ]; then<br />
stress-ng --cpu 4 --vm 4 &<br />
str_pid=$!<br />
fi<br />
if [ "${max}" -eq "1" ]; then<br />
stress-ng --cpu 4 --vm 4 &<br />
str_pid=$!<br />
fi<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) Starting stressapptest with PID: " $str_pid<br />
<br />
proceed=1<br />
# create test files<br />
file1_path=`mktemp`<br />
file2_path=`mktemp`<br />
file1=`basename $file1_path`<br />
file2=`basename $file2_path`<br />
<br />
dd if=/dev/urandom of=$file1_path bs=1024 count=10000<br />
dd if=/dev/urandom of=$file2_path bs=1024 count=10000<br />
<br />
cp1_from="/media/mmc0/"<br />
cp1_to="/media/usb0/"<br />
<br />
cp2_from="/media/usb0/"<br />
cp2_to="/media/usb1/"<br />
<br />
#copy files in case they are missing<br />
cp $file1_path $cp1_from<br />
cp $file1_path $cp1_to<br />
cp $file2_path $cp2_from<br />
cp $file2_path $cp2_to<br />
<br />
while [ $proceed -eq 1 ]<br />
do<br />
<br />
ping -q -c1 192.168.0.2 >> env-chamber-testing.log<br />
if [ $? -ne 0 ]<br />
then<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) ERROR: Ping failed"<br />
fi<br />
<br />
cp1_done=`ps | grep $cp1_pid | grep cp`<br />
if [ -z "$cp1_done" ]; then # copy finished<br />
if cmp -s $cp1_from$file1 $cp1_to$file1; then<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) PASS: Copying file from $cp1_from to $cp1_to successful"<br />
else<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) ERROR: Difference between files on $cp1_from and $cp1_to detected"<br />
fi<br />
cp1_temp=$cp1_from # swap destinations<br />
cp1_from=$cp1_to<br />
cp1_to=$cp1_temp<br />
<br />
rm $cp1_to$file1 # remove destination file<br />
<br />
cp $cp1_from$file1 $cp1_to$file1 &<br />
cp1_pid=$!<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) Started copying file from $cp1_from to $cp1_to"<br />
fi<br />
<br />
cp2_done=`ps | grep $cp2_pid | grep cp`<br />
if [ -z "$cp2_done" ]; then # copy finished<br />
if cmp -s $cp2_from$file2 $cp2_to$file2; then<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) PASS: Copying file from $cp2_from to $cp2_to successful"<br />
else<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) ERROR: Difference between files on $cp2_from and $cp2_to detected"<br />
fi<br />
cp2_temp=$cp2_from # swap destinations<br />
cp2_from=$cp2_to<br />
cp2_to=$cp2_temp<br />
<br />
rm $cp2_to$file2 # remove destination file<br />
<br />
cp $cp2_from$file2 $cp2_to$file2 &<br />
cp2_pid=$!<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) Started copying file from $cp2_from to $cp2_to"<br />
fi<br />
<br />
done<br />
</syntaxhighlight></div>
Voipac-hw
https://wiki.voipac.com/index.php?title=iMX93_Industrial_Environmental_chamber_testing&diff=5575
iMX93 Industrial Environmental chamber testing
2025-05-14T13:59:33Z
<p>Voipac-hw: </p>
<hr />
<div>[[Category:iMX93 Industrial Development Kit]]<br />
[[Category:iMX93 Industrial Development Kit Testing]]<br />
<!-- --><br />
<div style="float:right">__TOC__</div><br />
<br />
On this page environmental stress testing results of iMX93 Industrial Development Kit are displayed. Detailed instructions how to setup kits are also shown.<br />
<br />
== Hardware configuration ==<br />
All of the modules used standard specification except of the temperature ranges for the key components as described below:<br />
<br /><br />
* 1x iMX93 Industrial Development Kit in [[iMX93 Industrial Max|Max configuration]]<br />
** i.MX 93 Dual 1.7GHz CPU - extended industrial temperature range (-40°C to +105°C)<br />
** 2GB LPDDR4 Memory - extended industrial temperature range (-40°C to +95°C)<br />
** eMMC Flash 32GB - industrial temperature range (-40°C to +85°C)<br />
** MAYA-W260-00B WiFi & Bluetooth Module - industrial temperature range (-40°C to +85°C)<br />
<br /><br />
* 1x iMX93 Industrial Development Kit in [[iMX93 Industrial Pro|Pro configuration]]<br />
** i.MX 93 Dual 1.7GHz CPU - extended industrial temperature range (-40°C to +105°C)<br />
** 2GB LPDDR4 Memory - automotive temperature range (-40°C to +95°C)<br />
** eMMC Flash 16GB - industrial temperature range (-40°C to +85°C)<br />
** MAYA-W160-00B WiFi & Bluetooth Module - industrial temperature range (-40°C to +85°C)<br />
<br /><br />
* 1x iMX93 Industrial Development Kit in [[iMX93 Industrial Basic|Basic configuration]]<br />
** i.MX 93 Solo 1.7GHz CPU - extended industrial temperature range (-40°C to +105°C)<br />
** 1GB LPDDR4 Memory - industrial temperature range (-40°C to +95°C)<br />
** eMMC Flash 8GB - industrial temperature range (-40°C to +85°C)<br />
<br /><br />
* 1x iMX93 Industrial Development Kit in [[iMX93 Industrial Lite|Lite configuration]]<br />
** i.MX 93 Solo 900MHz CPU - extended commercial temperature range (0°C to +95°C)<br />
** 512MB LPDDR4 Memory - industrial temperature range (-30°C to +85°C)<br />
** eMMC Flash 4GB - extended temperature range (-25°C to +85°C)<br />
<br /><br />
All of the tested modules used standard configuration of iMX Development Baseboard with extended temperature range (-20°C to +70°C). The majority of tested kits used the standard heatsink sized 25x25x25mm, which is included in every development kit package, thus showcasing that this standardised heatsink performs even in very harsh conditions.<br /><br />
<br />
The setup in the environmental chamber:<br /><br />
[[image:iMX8M_Industrial_Development_Kits-Enviromental_chamber_overview_with_description.jpg|800px]]<br />
<br />
== Test description ==<br />
Four iMX8M Industrial Development Kits (one in Max Industrial configuration, one in Pro Industrial configuration, one in Basic Industrial configuration and one in Max Commercial configuration) were running CPU and memory tests to stress out all the most significant peripherals in the whole Industrial temperature scale, ranging from -40°C to +85°C, to check the reliability and stability of the firmware and hardware design.<br /><br /><br />
<br />
Configuration, software and testing threads in details:<br /><br /><br />
<br />
'''1x iMX8M Industrial Development Kit [setup no. 4] in [[iMX8M Industrial Max|Max configuration]] and Industrial temperature range<br />CPU and memory stress testing'''<br />
* 1 thread of extensive DDR4 Memory stress test<br />
* 1 thread of CPU stress test<br />
* sending HDMI Output to external monitor<br />
* all the messages were displayed on the serial console connected via Micro USB cable<br />
* firmware running from eMMC Flash memory<br />
* Ethernet cable connected to network switch placed outside of the chamber<br />
* 2x USB device connected and placed outside of the chamber<br />
* WiFi and Bluetooth module active, connected to the antennas and running discovery mode<br />
* large 48x48x16mm heatsink<br />
<br /><br />
'''1x iMX8M Industrial Development Kit [setup no. 2] in [[iMX8M Industrial Pro|Pro configuration]] and Industrial temperature range<br />CPU and memory stress testing'''<br />
* 1 thread of extensive DDR4 Memory stress test<br />
* 1 thread of CPU stress test<br />
* sending HDMI Output to external monitor<br />
* NXP MIPI-CSI camera connected and capturing video stream<br />
* all the messages were displayed on the serial console connected via Micro USB cable<br />
* firmware running from eMMC Flash memory<br />
* Ethernet cable connected to network switch placed outside of the chamber<br />
* 2x USB device connected and placed outside of the chamber<br />
* WiFi and Bluetooth module active, connected to the antennas and running discovery mode<br />
* standard 25x25x25mm heatsink<br />
<br /><br />
'''1x iMX8M Industrial Development Kit [setup no. 1] in [[iMX8M Industrial Basic|Basic configuration]] and Industrial temperature range<br />CPU and memory stress testing'''<br />
* 1 thread of extensive DDR4 Memory stress test<br />
* 1 thread of CPU stress test<br />
* sending HDMI Output to external monitor<br />
* all the messages were displayed on the serial console connected via Micro USB cable<br />
* firmware running from eMMC Flash memory<br />
* Ethernet cable connected to network switch placed outside of the chamber<br />
* 2x USB device connected and placed outside of the chamber<br />
* WiFi PCI Express card plugged in, connected to the antennas and running discovery mode<br />
* standard 25x25x25mm heatsink<br />
<br /><br />
'''1x iMX8M Industrial Development Kit [setup no. 3] in [[iMX8M Industrial Max|Max configuration]] and Commercial temperature range<br />CPU and memory stress testing'''<br />
* 1 thread of extensive DDR4 Memory stress test<br />
* 1 thread of CPU stress test<br />
* sending HDMI Output to external monitor<br />
* Digilent MIPI-CSI camera connected and capturing video stream<br />
* all the messages were displayed on the serial console connected via Micro USB cable<br />
* firmware running from eMMC Flash memory<br />
* Ethernet cable connected to network switch placed outside of the chamber<br />
* 2x USB device connected and placed outside of the chamber<br />
* WiFi and Bluetooth module active, connected to the antennas and running discovery mode<br />
* standard 25x25x25mm heatsink including a fan<br />
<br /><br />
Power sources, USB flash devices, network switch, HDMI monitor and controlling PC were placed outside the environmental chamber. All the scripts running during the test and the board setup instructions can be found in section [[#Preparing the test|How to prepare the test]].<br />
<br />
== Testing Results ==<br />
The picture below shows the temperature profile during the whole testing process. Humidity was not controlled. The temperature gradient for the environment chamber was set to 1°C/min.<br /><br />
[[image:iMX8M_Industrial_Development_Kit-Env_chamber_temperature_profile.png|800px]]<br />
<br />
=== Running the development kits at -40°C – PASS ===<br />
Test description: CPU, Memory and peripheral stress tests were running at -40°C. All the tested kits were working without errors during the whole time, even if some components used for iMX8M Industrial Development Kit Max in Commercial temperature range were only rated for the temperature range between 0°C and +95°C.<br /><br /><br />
<br />
A closer image on the temperature chamber displaying the minimum temperature is shown below. These readouts are available on the display:<br />
* the first number shows current temperature<br />
* the second one set temperature<br />
* the last two shows relative humidity. Humidity was not controlled during testing process.<br />
[[image:iMX8M Industrial Kit-Env chamber-Boards at -40C.jpg|800px]]<br />
<br /><br /><br />
[[image:iMX8M_Industrial_Development_Kit-Env_chamber_at_-40C.jpg|800px]]<br />
<br />
=== Running the development kits at +85°C – PASS ===<br />
Test description: The pre-set temperature profile was followed until the development kits gradually reached +85°C. The kits remained around this temperature for the duration of two hours and at the end of this whole cycle all the kits were running.<br /><br />
[[image:iMX8M_Industrial_Kit-Env_chamber-Boards_at_+86C.jpg|800px]]<br />
<br /><br /><br />
[[image:iMX8M_Industrial_Development_Kit-Env_chamber_at_+85C.jpg|800px]]<br />
<br />
=== Switch OFF/ON test at -40°C – PASS ===<br />
Test description: At temperature -40°C the development kits were switched OFF, left OFF for at least 15 minutes (to cool down completely) and then switched ON to see if they boot up without problems. Once booted up into Linux, the test script was launched to test RAM memory and all peripherals. The kits were turned OFF and ON again multiple times to see potential issues at the lowest temperature level. All of the tested setups booted up successfully.<br />
<br />
<br /><br />
[[image:iMX8M Industrial Kit-Env chamber-Boards snow.jpg|800px]]<br />
<br />
== PC setup ==<br />
The PC was used during the test to control / monitor all the kits through serial console sessions. The control computer was running Windows 10 operating system.<br />
<br />
=== HDMI Outputs and Serial consoles ===<br />
To control iMX8M Industrial Development Kits, one TeraTerm serial console was opened for each setup. The kits were connected to the external HDMI switch to monitor HDMI outputs.<br />
<br /><br /><br />
The setup of the environmental chamber cables and out-of-chamber equipment:<br />
<br /><br />
[[image:iMX8M Industrial Development Kit-Climate chamber overview.jpg|800px]]<br />
<br />
== Preparing the test ==<br />
=== Boot device and software ===<br />
The eMMC memory was selected as a booting device for all the kits. Device tree files were not adjusted as the default configuration was used. The only change compared to standard software package was running the test script. In order to flash a fresh firmware into the eMMC Memory follow [[iMX8M_Industrial_Flashing_Procedure|these instructions]].<br />
<br />
=== Downloading stress test ===<br />
Stress-ng package was selected to check CPU and memory integrity. Placing this file into the same directory where the testing script will be stored is important:<br />
<syntaxhighlight lang="bash"><br />
wget https://downloads.voipac.com/files/iMX8M_Industrial_Development_Kit/module/documents/Thermal_stress_resistance/imx8mq-voipac-peripheral-test.sh<br />
</syntaxhighlight><br />
<br />
=== Start CPU and memory stress test ===<br />
Navigate into the directory, where stress test feature and the testing script are stored.<br /><br /><br />
<br />
Stress sequence script:<br />
<syntaxhighlight lang="bash"><br />
for d in $(seq 1 1 99999)<br />
do<br />
uptime<br />
echo "Test $a Test $b Test $c $d times"<br />
echo "Start stress-ng --iomix 1 -t 10 -v"<br />
stress-ng --iomix 1 -t 10 -v<br />
echo "End"<br />
echo "Start stress-ng --cpu 2 --vm 4 -t 10"<br />
stress-ng --cpu 2 --vm 4 -t 10<br />
echo "End"<br />
echo "Start stress-ng --shm 0 -t 10"<br />
stress-ng --shm 0 -t 10<br />
echo "End"<br />
echo "Start stress-ng --seq 0 -t 2 --tz -v"<br />
stress-ng --seq 0 -t 2 --tz -v<br />
echo "End"<br />
echo "Start Thermal zone information"<br />
stress-ng --matrix 0 --tz -t 10 --log-brief -t 10<br />
echo "End"<br />
done<br />
</syntaxhighlight><br />
<br />
=== Start peripheral test ===<br />
Plug the development kit into mains and connect it to the controlling PC via console. Before the first time usage of the script, permissions need to be granted by the following command: <br />
<syntaxhighlight lang="bash"><br />
chmod +x imx8m-voipac-peripheral-test.sh<br />
</syntaxhighlight><br />
<br /><br />
Testing scripts command consists of the following arguments:<br />
* the first parameter - configuration of tested development kit (Max, Pro or Basic)<br />
* the second parameter - USB drive 1 location<br />
* the third parameter - USB drive 2 location<br />
* the fourth parameter - SD card location<br />
<br /><br />
Several commands used during environmental chamber testing are shown below:<br />
<br />
* iMX8M Industrial Development Kit Max:<br />
<syntaxhighlight lang="bash"><br />
./imx8m-voipac-peripheral-test.sh -max sda1 sdb1 mmcblk1p1 | tee -i imx8m-env-testing.log<br />
</syntaxhighlight><br />
* iMX8M Industrial Development Kit Pro:<br />
<syntaxhighlight lang="bash"><br />
./imx8m-voipac-peripheral-test.sh -pro sda1 sdb1 mmcblk1p1 | tee -i imx8m-env-testing.log<br />
</syntaxhighlight><br />
* iMX8M Industrial Development Kit Basic:<br />
<syntaxhighlight lang="bash"><br />
./imx8m-voipac-peripheral-test.sh -basic sda1 sdb1 mmcblk1p1 | tee -i imx8m-env-testing.log<br />
</syntaxhighlight><br />
<br /><br />
The complete script can be found in [https://downloads.voipac.com/files/iMX8M_Industrial_Development_Kit/module/documents/Thermal_stress_resistance/imx8mq-voipac-peripheral-test.sh the downloads section] or down below:<br />
<syntaxhighlight lang="bash"><br />
#!/bin/sh<br />
<br />
# iMX8MQ environmental chamber peripheral test<br />
<br />
mountDevice() {<br />
mkdir -p "/media/$2"<br />
mount /dev/$1 /media/$2<br />
cat /proc/mounts | grep -F "/dev/$1 /media/$2"<br />
if [ "$?" -eq "0" ]; then<br />
echo "$2 mounted"<br />
else<br />
echo "$2 not mounted"; exit 2<br />
fi<br />
}<br />
<br />
# prepare files<br />
cd ~/<br />
mkdir -p env-chamber-testing/<br />
cd env-chamber-testing/<br />
<br />
touch env-chamber-testing.log<br />
touch cpu-temp.log<br />
<br />
basic=0<br />
pro=0<br />
max=0<br />
case $1 in<br />
-basic) basic=1 ;;<br />
-pro) pro=1 ;;<br />
-max) max=1 ;;<br />
*)<br />
esac<br />
<br />
# mount devices<br />
mountDevice $2 usb0<br />
mountDevice $3 usb1<br />
mountDevice $4 mmc0<br />
<br />
updateLogFiles() {<br />
# obtain board ID from IP address - be sure addresses are allocated based on MAC<br />
boardID=$(/sbin/ip -o -4 addr list eth0 | awk '{print $4}' | cut -d/ -f1 | cut -d'.' -f4 | cut -d'2' -f2);<br />
# be sure time server is running on DHCP server<br />
currentTime=`date +%Y-%m-%d.%H:%M`<br />
<br />
mv env-chamber-testing.log trx-board-$boardID-env-chamber.log.$currentTime<br />
mv cpu-temp.log trx-board-$boardID-env-cpu-temp.log.$currentTime<br />
}<br />
<br />
finish_test_now() {<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) Ctrl+C Detected: End of the test"<br />
precced=0;<br />
#kill -INT $vid_pid $str_pid $log_pid;<br />
sleep 3;<br />
test_status=`cat env-chamber-testing.log | grep -i "error" | grep -v -e "0 errors" -e "no corrected errors"`<br />
if [ -z "$test_status" ]<br />
then<br />
echo "*********TEST PASS*********"<br />
else<br />
echo "*********TEST FAIL*********"<br />
echo "List of detected errors:"<br />
cat env-chamber-testing.log | grep -i "error" | grep -v -e "0 errors" -e "no corrected errors" -e "List of detected errors:"<br />
fi<br />
updateLogFiles<br />
exit;<br />
}<br />
<br />
# kill all processes if Ctrl+C is detected<br />
trap finish_test_now 2<br />
<br />
# play a video stream<br />
gst-launch-1.0 -q imxv4l2src ! autovideosink &<br />
<br />
# stressapptest - CPU threads and RAM memory threads<br />
if [ "${basic}" -eq "1" ]; then<br />
stress-ng --cpu 2 --vm 4 &<br />
str_pid=$!<br />
fi<br />
if [ "${pro}" -eq "1" ]; then<br />
stress-ng --cpu 4 --vm 4 &<br />
str_pid=$!<br />
fi<br />
if [ "${max}" -eq "1" ]; then<br />
stress-ng --cpu 4 --vm 4 &<br />
str_pid=$!<br />
fi<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) Starting stressapptest with PID: " $str_pid<br />
<br />
proceed=1<br />
# create test files<br />
file1_path=`mktemp`<br />
file2_path=`mktemp`<br />
file1=`basename $file1_path`<br />
file2=`basename $file2_path`<br />
<br />
dd if=/dev/urandom of=$file1_path bs=1024 count=10000<br />
dd if=/dev/urandom of=$file2_path bs=1024 count=10000<br />
<br />
cp1_from="/media/mmc0/"<br />
cp1_to="/media/usb0/"<br />
<br />
cp2_from="/media/usb0/"<br />
cp2_to="/media/usb1/"<br />
<br />
#copy files in case they are missing<br />
cp $file1_path $cp1_from<br />
cp $file1_path $cp1_to<br />
cp $file2_path $cp2_from<br />
cp $file2_path $cp2_to<br />
<br />
while [ $proceed -eq 1 ]<br />
do<br />
<br />
ping -q -c1 192.168.0.2 >> env-chamber-testing.log<br />
if [ $? -ne 0 ]<br />
then<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) ERROR: Ping failed"<br />
fi<br />
<br />
cp1_done=`ps | grep $cp1_pid | grep cp`<br />
if [ -z "$cp1_done" ]; then # copy finished<br />
if cmp -s $cp1_from$file1 $cp1_to$file1; then<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) PASS: Copying file from $cp1_from to $cp1_to successful"<br />
else<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) ERROR: Difference between files on $cp1_from and $cp1_to detected"<br />
fi<br />
cp1_temp=$cp1_from # swap destinations<br />
cp1_from=$cp1_to<br />
cp1_to=$cp1_temp<br />
<br />
rm $cp1_to$file1 # remove destination file<br />
<br />
cp $cp1_from$file1 $cp1_to$file1 &<br />
cp1_pid=$!<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) Started copying file from $cp1_from to $cp1_to"<br />
fi<br />
<br />
cp2_done=`ps | grep $cp2_pid | grep cp`<br />
if [ -z "$cp2_done" ]; then # copy finished<br />
if cmp -s $cp2_from$file2 $cp2_to$file2; then<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) PASS: Copying file from $cp2_from to $cp2_to successful"<br />
else<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) ERROR: Difference between files on $cp2_from and $cp2_to detected"<br />
fi<br />
cp2_temp=$cp2_from # swap destinations<br />
cp2_from=$cp2_to<br />
cp2_to=$cp2_temp<br />
<br />
rm $cp2_to$file2 # remove destination file<br />
<br />
cp $cp2_from$file2 $cp2_to$file2 &<br />
cp2_pid=$!<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) Started copying file from $cp2_from to $cp2_to"<br />
fi<br />
<br />
done<br />
</syntaxhighlight></div>
Voipac-hw
https://wiki.voipac.com/index.php?title=iMX93_Industrial_Environmental_chamber_testing&diff=5574
iMX93 Industrial Environmental chamber testing
2025-05-14T13:58:36Z
<p>Voipac-hw: </p>
<hr />
<div>[[Category:iMX93 Industrial Development Kit]]<br />
[[Category:iMX93 Industrial Development Kit Testing]]<br />
<!-- --><br />
<div style="float:right">__TOC__</div><br />
<br />
On this page environmental stress testing results of iMX93 Industrial Development Kit are displayed. Detailed instructions how to setup kits are also shown.<br />
<br />
== Hardware configuration ==<br />
All of the modules used standard specification except of the temperature ranges for the key components as described below:<br />
<br /><br />
* 1x iMX93 Industrial Development Kit in [[iMX93 Industrial Max|Max configuration]]<br />
** i.MX 93 Dual 1.7GHz CPU - extended industrial temperature range (-40°C to +105°C)<br />
** 2GB LPDDR4 Memory - extended industrial temperature range (-40°C to +95°C)<br />
** eMMC Flash 32GB - industrial temperature range (-40°C to +85°C)<br />
** MAYA-W260-00B WiFi & Bluetooth Module - industrial temperature range (-40°C to +85°C)<br />
<br /><br />
* 1x iMX93 Industrial Development Kit in [[iMX93 Industrial Pro|Pro configuration]]<br />
** i.MX 93 Dual 1.7GHz CPU - extended industrial temperature range (-40°C to +105°C)<br />
** 2GB LPDDR4 Memory - automotive temperature range (-40°C to +95°C)<br />
** eMMC Flash 16GB - industrial temperature range (-40°C to +85°C)<br />
** MAYA-W160-00B WiFi & Bluetooth Module - industrial temperature range (-40°C to +85°C)<br />
<br /><br />
* 1x iMX93 Industrial Development Kit in [[iMX93 Industrial Basic|Basic configuration]]<br />
** i.MX 93 Solo 1.7GHz CPU - extended industrial temperature range (-40°C to +105°C)<br />
** 1GB LPDDR4 Memory - industrial temperature range (-40°C to +95°C)<br />
** eMMC Flash 8GB - industrial temperature range (-40°C to +85°C)<br />
<br /><br />
* 1x iMX93 Industrial Development Kit in [[iMX93 Industrial Lite|Lite configuration]]<br />
** i.MX 93 Solo 900MHz CPU - extended commercial temperature range (0°C to +95°C)<br />
** 512MB LPDDR4 Memory - industrial temperature range (-30°C to +85°C)<br />
** eMMC Flash 4GB - extended temperature range (-25°C to +85°C)<br />
<br /><br />
All of the tested modules used standard configuration of iMX Development Baseboard with extended temperature range (-20°C to +70°C). The majority of tested kits used the standard heatsink sized 25x25x25mm, which is included in every development kit package, thus showcasing that this standardised heatsink performs even in very harsh conditions. One of the kits was mounted with a larger heatsink and one of the standard heatsinks was mounted with an active fan to test its impact on the performance.<br /><br />
To test the performance of the video capturing capabilities of the development kits under extreme conditions, NXP MIPI-CSI and Digilent MIPI-CSI cameras were included in the tested setups.<br />
<br /><br />
<br />
The setup in the environmental chamber:<br /><br />
[[image:iMX8M_Industrial_Development_Kits-Enviromental_chamber_overview_with_description.jpg|800px]]<br />
<br />
== Test description ==<br />
Four iMX8M Industrial Development Kits (one in Max Industrial configuration, one in Pro Industrial configuration, one in Basic Industrial configuration and one in Max Commercial configuration) were running CPU and memory tests to stress out all the most significant peripherals in the whole Industrial temperature scale, ranging from -40°C to +85°C, to check the reliability and stability of the firmware and hardware design.<br /><br /><br />
<br />
Configuration, software and testing threads in details:<br /><br /><br />
<br />
'''1x iMX8M Industrial Development Kit [setup no. 4] in [[iMX8M Industrial Max|Max configuration]] and Industrial temperature range<br />CPU and memory stress testing'''<br />
* 1 thread of extensive DDR4 Memory stress test<br />
* 1 thread of CPU stress test<br />
* sending HDMI Output to external monitor<br />
* all the messages were displayed on the serial console connected via Micro USB cable<br />
* firmware running from eMMC Flash memory<br />
* Ethernet cable connected to network switch placed outside of the chamber<br />
* 2x USB device connected and placed outside of the chamber<br />
* WiFi and Bluetooth module active, connected to the antennas and running discovery mode<br />
* large 48x48x16mm heatsink<br />
<br /><br />
'''1x iMX8M Industrial Development Kit [setup no. 2] in [[iMX8M Industrial Pro|Pro configuration]] and Industrial temperature range<br />CPU and memory stress testing'''<br />
* 1 thread of extensive DDR4 Memory stress test<br />
* 1 thread of CPU stress test<br />
* sending HDMI Output to external monitor<br />
* NXP MIPI-CSI camera connected and capturing video stream<br />
* all the messages were displayed on the serial console connected via Micro USB cable<br />
* firmware running from eMMC Flash memory<br />
* Ethernet cable connected to network switch placed outside of the chamber<br />
* 2x USB device connected and placed outside of the chamber<br />
* WiFi and Bluetooth module active, connected to the antennas and running discovery mode<br />
* standard 25x25x25mm heatsink<br />
<br /><br />
'''1x iMX8M Industrial Development Kit [setup no. 1] in [[iMX8M Industrial Basic|Basic configuration]] and Industrial temperature range<br />CPU and memory stress testing'''<br />
* 1 thread of extensive DDR4 Memory stress test<br />
* 1 thread of CPU stress test<br />
* sending HDMI Output to external monitor<br />
* all the messages were displayed on the serial console connected via Micro USB cable<br />
* firmware running from eMMC Flash memory<br />
* Ethernet cable connected to network switch placed outside of the chamber<br />
* 2x USB device connected and placed outside of the chamber<br />
* WiFi PCI Express card plugged in, connected to the antennas and running discovery mode<br />
* standard 25x25x25mm heatsink<br />
<br /><br />
'''1x iMX8M Industrial Development Kit [setup no. 3] in [[iMX8M Industrial Max|Max configuration]] and Commercial temperature range<br />CPU and memory stress testing'''<br />
* 1 thread of extensive DDR4 Memory stress test<br />
* 1 thread of CPU stress test<br />
* sending HDMI Output to external monitor<br />
* Digilent MIPI-CSI camera connected and capturing video stream<br />
* all the messages were displayed on the serial console connected via Micro USB cable<br />
* firmware running from eMMC Flash memory<br />
* Ethernet cable connected to network switch placed outside of the chamber<br />
* 2x USB device connected and placed outside of the chamber<br />
* WiFi and Bluetooth module active, connected to the antennas and running discovery mode<br />
* standard 25x25x25mm heatsink including a fan<br />
<br /><br />
Power sources, USB flash devices, network switch, HDMI monitor and controlling PC were placed outside the environmental chamber. All the scripts running during the test and the board setup instructions can be found in section [[#Preparing the test|How to prepare the test]].<br />
<br />
== Testing Results ==<br />
The picture below shows the temperature profile during the whole testing process. Humidity was not controlled. The temperature gradient for the environment chamber was set to 1°C/min.<br /><br />
[[image:iMX8M_Industrial_Development_Kit-Env_chamber_temperature_profile.png|800px]]<br />
<br />
=== Running the development kits at -40°C – PASS ===<br />
Test description: CPU, Memory and peripheral stress tests were running at -40°C. All the tested kits were working without errors during the whole time, even if some components used for iMX8M Industrial Development Kit Max in Commercial temperature range were only rated for the temperature range between 0°C and +95°C.<br /><br /><br />
<br />
A closer image on the temperature chamber displaying the minimum temperature is shown below. These readouts are available on the display:<br />
* the first number shows current temperature<br />
* the second one set temperature<br />
* the last two shows relative humidity. Humidity was not controlled during testing process.<br />
[[image:iMX8M Industrial Kit-Env chamber-Boards at -40C.jpg|800px]]<br />
<br /><br /><br />
[[image:iMX8M_Industrial_Development_Kit-Env_chamber_at_-40C.jpg|800px]]<br />
<br />
=== Running the development kits at +85°C – PASS ===<br />
Test description: The pre-set temperature profile was followed until the development kits gradually reached +85°C. The kits remained around this temperature for the duration of two hours and at the end of this whole cycle all the kits were running.<br /><br />
[[image:iMX8M_Industrial_Kit-Env_chamber-Boards_at_+86C.jpg|800px]]<br />
<br /><br /><br />
[[image:iMX8M_Industrial_Development_Kit-Env_chamber_at_+85C.jpg|800px]]<br />
<br />
=== Switch OFF/ON test at -40°C – PASS ===<br />
Test description: At temperature -40°C the development kits were switched OFF, left OFF for at least 15 minutes (to cool down completely) and then switched ON to see if they boot up without problems. Once booted up into Linux, the test script was launched to test RAM memory and all peripherals. The kits were turned OFF and ON again multiple times to see potential issues at the lowest temperature level. All of the tested setups booted up successfully.<br />
<br />
<br /><br />
[[image:iMX8M Industrial Kit-Env chamber-Boards snow.jpg|800px]]<br />
<br />
== PC setup ==<br />
The PC was used during the test to control / monitor all the kits through serial console sessions. The control computer was running Windows 10 operating system.<br />
<br />
=== HDMI Outputs and Serial consoles ===<br />
To control iMX8M Industrial Development Kits, one TeraTerm serial console was opened for each setup. The kits were connected to the external HDMI switch to monitor HDMI outputs.<br />
<br /><br /><br />
The setup of the environmental chamber cables and out-of-chamber equipment:<br />
<br /><br />
[[image:iMX8M Industrial Development Kit-Climate chamber overview.jpg|800px]]<br />
<br />
== Preparing the test ==<br />
=== Boot device and software ===<br />
The eMMC memory was selected as a booting device for all the kits. Device tree files were not adjusted as the default configuration was used. The only change compared to standard software package was running the test script. In order to flash a fresh firmware into the eMMC Memory follow [[iMX8M_Industrial_Flashing_Procedure|these instructions]].<br />
<br />
=== Downloading stress test ===<br />
Stress-ng package was selected to check CPU and memory integrity. Placing this file into the same directory where the testing script will be stored is important:<br />
<syntaxhighlight lang="bash"><br />
wget https://downloads.voipac.com/files/iMX8M_Industrial_Development_Kit/module/documents/Thermal_stress_resistance/imx8mq-voipac-peripheral-test.sh<br />
</syntaxhighlight><br />
<br />
=== Start CPU and memory stress test ===<br />
Navigate into the directory, where stress test feature and the testing script are stored.<br /><br /><br />
<br />
Stress sequence script:<br />
<syntaxhighlight lang="bash"><br />
for d in $(seq 1 1 99999)<br />
do<br />
uptime<br />
echo "Test $a Test $b Test $c $d times"<br />
echo "Start stress-ng --iomix 1 -t 10 -v"<br />
stress-ng --iomix 1 -t 10 -v<br />
echo "End"<br />
echo "Start stress-ng --cpu 2 --vm 4 -t 10"<br />
stress-ng --cpu 2 --vm 4 -t 10<br />
echo "End"<br />
echo "Start stress-ng --shm 0 -t 10"<br />
stress-ng --shm 0 -t 10<br />
echo "End"<br />
echo "Start stress-ng --seq 0 -t 2 --tz -v"<br />
stress-ng --seq 0 -t 2 --tz -v<br />
echo "End"<br />
echo "Start Thermal zone information"<br />
stress-ng --matrix 0 --tz -t 10 --log-brief -t 10<br />
echo "End"<br />
done<br />
</syntaxhighlight><br />
<br />
=== Start peripheral test ===<br />
Plug the development kit into mains and connect it to the controlling PC via console. Before the first time usage of the script, permissions need to be granted by the following command: <br />
<syntaxhighlight lang="bash"><br />
chmod +x imx8m-voipac-peripheral-test.sh<br />
</syntaxhighlight><br />
<br /><br />
Testing scripts command consists of the following arguments:<br />
* the first parameter - configuration of tested development kit (Max, Pro or Basic)<br />
* the second parameter - USB drive 1 location<br />
* the third parameter - USB drive 2 location<br />
* the fourth parameter - SD card location<br />
<br /><br />
Several commands used during environmental chamber testing are shown below:<br />
<br />
* iMX8M Industrial Development Kit Max:<br />
<syntaxhighlight lang="bash"><br />
./imx8m-voipac-peripheral-test.sh -max sda1 sdb1 mmcblk1p1 | tee -i imx8m-env-testing.log<br />
</syntaxhighlight><br />
* iMX8M Industrial Development Kit Pro:<br />
<syntaxhighlight lang="bash"><br />
./imx8m-voipac-peripheral-test.sh -pro sda1 sdb1 mmcblk1p1 | tee -i imx8m-env-testing.log<br />
</syntaxhighlight><br />
* iMX8M Industrial Development Kit Basic:<br />
<syntaxhighlight lang="bash"><br />
./imx8m-voipac-peripheral-test.sh -basic sda1 sdb1 mmcblk1p1 | tee -i imx8m-env-testing.log<br />
</syntaxhighlight><br />
<br /><br />
The complete script can be found in [https://downloads.voipac.com/files/iMX8M_Industrial_Development_Kit/module/documents/Thermal_stress_resistance/imx8mq-voipac-peripheral-test.sh the downloads section] or down below:<br />
<syntaxhighlight lang="bash"><br />
#!/bin/sh<br />
<br />
# iMX8MQ environmental chamber peripheral test<br />
<br />
mountDevice() {<br />
mkdir -p "/media/$2"<br />
mount /dev/$1 /media/$2<br />
cat /proc/mounts | grep -F "/dev/$1 /media/$2"<br />
if [ "$?" -eq "0" ]; then<br />
echo "$2 mounted"<br />
else<br />
echo "$2 not mounted"; exit 2<br />
fi<br />
}<br />
<br />
# prepare files<br />
cd ~/<br />
mkdir -p env-chamber-testing/<br />
cd env-chamber-testing/<br />
<br />
touch env-chamber-testing.log<br />
touch cpu-temp.log<br />
<br />
basic=0<br />
pro=0<br />
max=0<br />
case $1 in<br />
-basic) basic=1 ;;<br />
-pro) pro=1 ;;<br />
-max) max=1 ;;<br />
*)<br />
esac<br />
<br />
# mount devices<br />
mountDevice $2 usb0<br />
mountDevice $3 usb1<br />
mountDevice $4 mmc0<br />
<br />
updateLogFiles() {<br />
# obtain board ID from IP address - be sure addresses are allocated based on MAC<br />
boardID=$(/sbin/ip -o -4 addr list eth0 | awk '{print $4}' | cut -d/ -f1 | cut -d'.' -f4 | cut -d'2' -f2);<br />
# be sure time server is running on DHCP server<br />
currentTime=`date +%Y-%m-%d.%H:%M`<br />
<br />
mv env-chamber-testing.log trx-board-$boardID-env-chamber.log.$currentTime<br />
mv cpu-temp.log trx-board-$boardID-env-cpu-temp.log.$currentTime<br />
}<br />
<br />
finish_test_now() {<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) Ctrl+C Detected: End of the test"<br />
precced=0;<br />
#kill -INT $vid_pid $str_pid $log_pid;<br />
sleep 3;<br />
test_status=`cat env-chamber-testing.log | grep -i "error" | grep -v -e "0 errors" -e "no corrected errors"`<br />
if [ -z "$test_status" ]<br />
then<br />
echo "*********TEST PASS*********"<br />
else<br />
echo "*********TEST FAIL*********"<br />
echo "List of detected errors:"<br />
cat env-chamber-testing.log | grep -i "error" | grep -v -e "0 errors" -e "no corrected errors" -e "List of detected errors:"<br />
fi<br />
updateLogFiles<br />
exit;<br />
}<br />
<br />
# kill all processes if Ctrl+C is detected<br />
trap finish_test_now 2<br />
<br />
# play a video stream<br />
gst-launch-1.0 -q imxv4l2src ! autovideosink &<br />
<br />
# stressapptest - CPU threads and RAM memory threads<br />
if [ "${basic}" -eq "1" ]; then<br />
stress-ng --cpu 2 --vm 4 &<br />
str_pid=$!<br />
fi<br />
if [ "${pro}" -eq "1" ]; then<br />
stress-ng --cpu 4 --vm 4 &<br />
str_pid=$!<br />
fi<br />
if [ "${max}" -eq "1" ]; then<br />
stress-ng --cpu 4 --vm 4 &<br />
str_pid=$!<br />
fi<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) Starting stressapptest with PID: " $str_pid<br />
<br />
proceed=1<br />
# create test files<br />
file1_path=`mktemp`<br />
file2_path=`mktemp`<br />
file1=`basename $file1_path`<br />
file2=`basename $file2_path`<br />
<br />
dd if=/dev/urandom of=$file1_path bs=1024 count=10000<br />
dd if=/dev/urandom of=$file2_path bs=1024 count=10000<br />
<br />
cp1_from="/media/mmc0/"<br />
cp1_to="/media/usb0/"<br />
<br />
cp2_from="/media/usb0/"<br />
cp2_to="/media/usb1/"<br />
<br />
#copy files in case they are missing<br />
cp $file1_path $cp1_from<br />
cp $file1_path $cp1_to<br />
cp $file2_path $cp2_from<br />
cp $file2_path $cp2_to<br />
<br />
while [ $proceed -eq 1 ]<br />
do<br />
<br />
ping -q -c1 192.168.0.2 >> env-chamber-testing.log<br />
if [ $? -ne 0 ]<br />
then<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) ERROR: Ping failed"<br />
fi<br />
<br />
cp1_done=`ps | grep $cp1_pid | grep cp`<br />
if [ -z "$cp1_done" ]; then # copy finished<br />
if cmp -s $cp1_from$file1 $cp1_to$file1; then<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) PASS: Copying file from $cp1_from to $cp1_to successful"<br />
else<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) ERROR: Difference between files on $cp1_from and $cp1_to detected"<br />
fi<br />
cp1_temp=$cp1_from # swap destinations<br />
cp1_from=$cp1_to<br />
cp1_to=$cp1_temp<br />
<br />
rm $cp1_to$file1 # remove destination file<br />
<br />
cp $cp1_from$file1 $cp1_to$file1 &<br />
cp1_pid=$!<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) Started copying file from $cp1_from to $cp1_to"<br />
fi<br />
<br />
cp2_done=`ps | grep $cp2_pid | grep cp`<br />
if [ -z "$cp2_done" ]; then # copy finished<br />
if cmp -s $cp2_from$file2 $cp2_to$file2; then<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) PASS: Copying file from $cp2_from to $cp2_to successful"<br />
else<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) ERROR: Difference between files on $cp2_from and $cp2_to detected"<br />
fi<br />
cp2_temp=$cp2_from # swap destinations<br />
cp2_from=$cp2_to<br />
cp2_to=$cp2_temp<br />
<br />
rm $cp2_to$file2 # remove destination file<br />
<br />
cp $cp2_from$file2 $cp2_to$file2 &<br />
cp2_pid=$!<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) Started copying file from $cp2_from to $cp2_to"<br />
fi<br />
<br />
done<br />
</syntaxhighlight></div>
Voipac-hw
https://wiki.voipac.com/index.php?title=iMX93_Industrial_Environmental_chamber_testing&diff=5560
iMX93 Industrial Environmental chamber testing
2025-05-14T13:27:32Z
<p>Voipac-hw: </p>
<hr />
<div>[[Category:iMX93 Industrial Development Kit]]<br />
[[Category:iMX93 Industrial Development Kit Testing]]<br />
<!-- --><br />
<div style="float:right">__TOC__</div><br />
<br />
On this page environmental stress testing results of iMX93 Industrial Development Kit are displayed. Detailed instructions how to setup kits are also shown.<br />
<br />
== Hardware configuration ==<br />
All of the modules used standard specification except of the temperature ranges for the key components as described below:<br />
<br /><br />
* 1x iMX Industrial Development Kit in [[iMX93 Industrial Max|Max configuration]]<br />
** i.MX 8M Quad 1.3GHz CPU - extended industrial temperature range (-40°C to +105°C)<br />
** 4GB LPDDR4 Memory - extended industrial temperature range (-40°C to +95°C)<br />
** eMMC 32GB - industrial temperature range (-40°C to +85°C)<br />
** SPB228-D-3 WiFi & Bluetooth Module - industrial temperature range (-40°C to +85°C)<br />
<br /><br />
* 1x iMX93 Industrial Development Kit in [[iMX93 Industrial Pro|Pro configuration]]<br />
** i.MX 8M QuadLite 1.3GHz CPU - extended industrial temperature range (-40°C to +105°C)<br />
** 2GB LPDDR4 Memory - automotive temperature range (-40°C to +95°C)<br />
** eMMC 16GB - industrial temperature range (-40°C to +85°C)<br />
** SPB228-D-3 WiFi & Bluetooth Module - industrial temperature range (-40°C to +85°C)<br />
<br /><br />
* 1x iMX93 Industrial Development Kit in [[iMX93 Industrial Basic|Basic configuration]]<br />
** i.MX 8M Dual 1.3GHz CPU - extended industrial temperature range (-40°C to +105°C)<br />
** 1GB LPDDR4 Memory - industrial temperature range (-40°C to +95°C)<br />
** eMMC 8GB - industrial temperature range (-40°C to +85°C)<br />
<br /><br />
* 1x iMX93 Industrial Development Kit in [[iMX93 Industrial Lite|Lite configuration]]<br />
** i.MX 8M Quad 1.5GHz CPU - extended commercial temperature range (0°C to +95°C)<br />
** 4GB LPDDR4 Memory - industrial temperature range (-30°C to +85°C)<br />
** eMMC 32GB - extended temperature range (-25°C to +85°C)<br />
** CM-276NF WiFi & Bluetooth Module - industrial temperature range (-30°C to +85°C)<br />
<br /><br />
All of the tested modules used standard configuration of iMX Development Baseboard with extended temperature range (-20°C to +70°C). The majority of tested kits used the standard heatsink sized 25x25x25mm, which is included in every development kit package, thus showcasing that this standardised heatsink performs even in very harsh conditions. One of the kits was mounted with a larger heatsink and one of the standard heatsinks was mounted with an active fan to test its impact on the performance.<br /><br />
To test the performance of the video capturing capabilities of the development kits under extreme conditions, NXP MIPI-CSI and Digilent MIPI-CSI cameras were included in the tested setups.<br />
<br /><br />
<br />
The setup in the environmental chamber:<br /><br />
[[image:iMX8M_Industrial_Development_Kits-Enviromental_chamber_overview_with_description.jpg|800px]]<br />
<br />
== Test description ==<br />
Four iMX8M Industrial Development Kits (one in Max Industrial configuration, one in Pro Industrial configuration, one in Basic Industrial configuration and one in Max Commercial configuration) were running CPU and memory tests to stress out all the most significant peripherals in the whole Industrial temperature scale, ranging from -40°C to +85°C, to check the reliability and stability of the firmware and hardware design.<br /><br /><br />
<br />
Configuration, software and testing threads in details:<br /><br /><br />
<br />
'''1x iMX8M Industrial Development Kit [setup no. 4] in [[iMX8M Industrial Max|Max configuration]] and Industrial temperature range<br />CPU and memory stress testing'''<br />
* 1 thread of extensive DDR4 Memory stress test<br />
* 1 thread of CPU stress test<br />
* sending HDMI Output to external monitor<br />
* all the messages were displayed on the serial console connected via Micro USB cable<br />
* firmware running from eMMC Flash memory<br />
* Ethernet cable connected to network switch placed outside of the chamber<br />
* 2x USB device connected and placed outside of the chamber<br />
* WiFi and Bluetooth module active, connected to the antennas and running discovery mode<br />
* large 48x48x16mm heatsink<br />
<br /><br />
'''1x iMX8M Industrial Development Kit [setup no. 2] in [[iMX8M Industrial Pro|Pro configuration]] and Industrial temperature range<br />CPU and memory stress testing'''<br />
* 1 thread of extensive DDR4 Memory stress test<br />
* 1 thread of CPU stress test<br />
* sending HDMI Output to external monitor<br />
* NXP MIPI-CSI camera connected and capturing video stream<br />
* all the messages were displayed on the serial console connected via Micro USB cable<br />
* firmware running from eMMC Flash memory<br />
* Ethernet cable connected to network switch placed outside of the chamber<br />
* 2x USB device connected and placed outside of the chamber<br />
* WiFi and Bluetooth module active, connected to the antennas and running discovery mode<br />
* standard 25x25x25mm heatsink<br />
<br /><br />
'''1x iMX8M Industrial Development Kit [setup no. 1] in [[iMX8M Industrial Basic|Basic configuration]] and Industrial temperature range<br />CPU and memory stress testing'''<br />
* 1 thread of extensive DDR4 Memory stress test<br />
* 1 thread of CPU stress test<br />
* sending HDMI Output to external monitor<br />
* all the messages were displayed on the serial console connected via Micro USB cable<br />
* firmware running from eMMC Flash memory<br />
* Ethernet cable connected to network switch placed outside of the chamber<br />
* 2x USB device connected and placed outside of the chamber<br />
* WiFi PCI Express card plugged in, connected to the antennas and running discovery mode<br />
* standard 25x25x25mm heatsink<br />
<br /><br />
'''1x iMX8M Industrial Development Kit [setup no. 3] in [[iMX8M Industrial Max|Max configuration]] and Commercial temperature range<br />CPU and memory stress testing'''<br />
* 1 thread of extensive DDR4 Memory stress test<br />
* 1 thread of CPU stress test<br />
* sending HDMI Output to external monitor<br />
* Digilent MIPI-CSI camera connected and capturing video stream<br />
* all the messages were displayed on the serial console connected via Micro USB cable<br />
* firmware running from eMMC Flash memory<br />
* Ethernet cable connected to network switch placed outside of the chamber<br />
* 2x USB device connected and placed outside of the chamber<br />
* WiFi and Bluetooth module active, connected to the antennas and running discovery mode<br />
* standard 25x25x25mm heatsink including a fan<br />
<br /><br />
Power sources, USB flash devices, network switch, HDMI monitor and controlling PC were placed outside the environmental chamber. All the scripts running during the test and the board setup instructions can be found in section [[#Preparing the test|How to prepare the test]].<br />
<br />
== Testing Results ==<br />
The picture below shows the temperature profile during the whole testing process. Humidity was not controlled. The temperature gradient for the environment chamber was set to 1°C/min.<br /><br />
[[image:iMX8M_Industrial_Development_Kit-Env_chamber_temperature_profile.png|800px]]<br />
<br />
=== Running the development kits at -40°C – PASS ===<br />
Test description: CPU, Memory and peripheral stress tests were running at -40°C. All the tested kits were working without errors during the whole time, even if some components used for iMX8M Industrial Development Kit Max in Commercial temperature range were only rated for the temperature range between 0°C and +95°C.<br /><br /><br />
<br />
A closer image on the temperature chamber displaying the minimum temperature is shown below. These readouts are available on the display:<br />
* the first number shows current temperature<br />
* the second one set temperature<br />
* the last two shows relative humidity. Humidity was not controlled during testing process.<br />
[[image:iMX8M Industrial Kit-Env chamber-Boards at -40C.jpg|800px]]<br />
<br /><br /><br />
[[image:iMX8M_Industrial_Development_Kit-Env_chamber_at_-40C.jpg|800px]]<br />
<br />
=== Running the development kits at +85°C – PASS ===<br />
Test description: The pre-set temperature profile was followed until the development kits gradually reached +85°C. The kits remained around this temperature for the duration of two hours and at the end of this whole cycle all the kits were running.<br /><br />
[[image:iMX8M_Industrial_Kit-Env_chamber-Boards_at_+86C.jpg|800px]]<br />
<br /><br /><br />
[[image:iMX8M_Industrial_Development_Kit-Env_chamber_at_+85C.jpg|800px]]<br />
<br />
=== Switch OFF/ON test at -40°C – PASS ===<br />
Test description: At temperature -40°C the development kits were switched OFF, left OFF for at least 15 minutes (to cool down completely) and then switched ON to see if they boot up without problems. Once booted up into Linux, the test script was launched to test RAM memory and all peripherals. The kits were turned OFF and ON again multiple times to see potential issues at the lowest temperature level. All of the tested setups booted up successfully.<br />
<br />
<br /><br />
[[image:iMX8M Industrial Kit-Env chamber-Boards snow.jpg|800px]]<br />
<br />
== PC setup ==<br />
The PC was used during the test to control / monitor all the kits through serial console sessions. The control computer was running Windows 10 operating system.<br />
<br />
=== HDMI Outputs and Serial consoles ===<br />
To control iMX8M Industrial Development Kits, one TeraTerm serial console was opened for each setup. The kits were connected to the external HDMI switch to monitor HDMI outputs.<br />
<br /><br /><br />
The setup of the environmental chamber cables and out-of-chamber equipment:<br />
<br /><br />
[[image:iMX8M Industrial Development Kit-Climate chamber overview.jpg|800px]]<br />
<br />
== Preparing the test ==<br />
=== Boot device and software ===<br />
The eMMC memory was selected as a booting device for all the kits. Device tree files were not adjusted as the default configuration was used. The only change compared to standard software package was running the test script. In order to flash a fresh firmware into the eMMC Memory follow [[iMX8M_Industrial_Flashing_Procedure|these instructions]].<br />
<br />
=== Downloading stress test ===<br />
Stress-ng package was selected to check CPU and memory integrity. Placing this file into the same directory where the testing script will be stored is important:<br />
<syntaxhighlight lang="bash"><br />
wget https://downloads.voipac.com/files/iMX8M_Industrial_Development_Kit/module/documents/Thermal_stress_resistance/imx8mq-voipac-peripheral-test.sh<br />
</syntaxhighlight><br />
<br />
=== Start CPU and memory stress test ===<br />
Navigate into the directory, where stress test feature and the testing script are stored.<br /><br /><br />
<br />
Stress sequence script:<br />
<syntaxhighlight lang="bash"><br />
for d in $(seq 1 1 99999)<br />
do<br />
uptime<br />
echo "Test $a Test $b Test $c $d times"<br />
echo "Start stress-ng --iomix 1 -t 10 -v"<br />
stress-ng --iomix 1 -t 10 -v<br />
echo "End"<br />
echo "Start stress-ng --cpu 2 --vm 4 -t 10"<br />
stress-ng --cpu 2 --vm 4 -t 10<br />
echo "End"<br />
echo "Start stress-ng --shm 0 -t 10"<br />
stress-ng --shm 0 -t 10<br />
echo "End"<br />
echo "Start stress-ng --seq 0 -t 2 --tz -v"<br />
stress-ng --seq 0 -t 2 --tz -v<br />
echo "End"<br />
echo "Start Thermal zone information"<br />
stress-ng --matrix 0 --tz -t 10 --log-brief -t 10<br />
echo "End"<br />
done<br />
</syntaxhighlight><br />
<br />
=== Start peripheral test ===<br />
Plug the development kit into mains and connect it to the controlling PC via console. Before the first time usage of the script, permissions need to be granted by the following command: <br />
<syntaxhighlight lang="bash"><br />
chmod +x imx8m-voipac-peripheral-test.sh<br />
</syntaxhighlight><br />
<br /><br />
Testing scripts command consists of the following arguments:<br />
* the first parameter - configuration of tested development kit (Max, Pro or Basic)<br />
* the second parameter - USB drive 1 location<br />
* the third parameter - USB drive 2 location<br />
* the fourth parameter - SD card location<br />
<br /><br />
Several commands used during environmental chamber testing are shown below:<br />
<br />
* iMX8M Industrial Development Kit Max:<br />
<syntaxhighlight lang="bash"><br />
./imx8m-voipac-peripheral-test.sh -max sda1 sdb1 mmcblk1p1 | tee -i imx8m-env-testing.log<br />
</syntaxhighlight><br />
* iMX8M Industrial Development Kit Pro:<br />
<syntaxhighlight lang="bash"><br />
./imx8m-voipac-peripheral-test.sh -pro sda1 sdb1 mmcblk1p1 | tee -i imx8m-env-testing.log<br />
</syntaxhighlight><br />
* iMX8M Industrial Development Kit Basic:<br />
<syntaxhighlight lang="bash"><br />
./imx8m-voipac-peripheral-test.sh -basic sda1 sdb1 mmcblk1p1 | tee -i imx8m-env-testing.log<br />
</syntaxhighlight><br />
<br /><br />
The complete script can be found in [https://downloads.voipac.com/files/iMX8M_Industrial_Development_Kit/module/documents/Thermal_stress_resistance/imx8mq-voipac-peripheral-test.sh the downloads section] or down below:<br />
<syntaxhighlight lang="bash"><br />
#!/bin/sh<br />
<br />
# iMX8MQ environmental chamber peripheral test<br />
<br />
mountDevice() {<br />
mkdir -p "/media/$2"<br />
mount /dev/$1 /media/$2<br />
cat /proc/mounts | grep -F "/dev/$1 /media/$2"<br />
if [ "$?" -eq "0" ]; then<br />
echo "$2 mounted"<br />
else<br />
echo "$2 not mounted"; exit 2<br />
fi<br />
}<br />
<br />
# prepare files<br />
cd ~/<br />
mkdir -p env-chamber-testing/<br />
cd env-chamber-testing/<br />
<br />
touch env-chamber-testing.log<br />
touch cpu-temp.log<br />
<br />
basic=0<br />
pro=0<br />
max=0<br />
case $1 in<br />
-basic) basic=1 ;;<br />
-pro) pro=1 ;;<br />
-max) max=1 ;;<br />
*)<br />
esac<br />
<br />
# mount devices<br />
mountDevice $2 usb0<br />
mountDevice $3 usb1<br />
mountDevice $4 mmc0<br />
<br />
updateLogFiles() {<br />
# obtain board ID from IP address - be sure addresses are allocated based on MAC<br />
boardID=$(/sbin/ip -o -4 addr list eth0 | awk '{print $4}' | cut -d/ -f1 | cut -d'.' -f4 | cut -d'2' -f2);<br />
# be sure time server is running on DHCP server<br />
currentTime=`date +%Y-%m-%d.%H:%M`<br />
<br />
mv env-chamber-testing.log trx-board-$boardID-env-chamber.log.$currentTime<br />
mv cpu-temp.log trx-board-$boardID-env-cpu-temp.log.$currentTime<br />
}<br />
<br />
finish_test_now() {<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) Ctrl+C Detected: End of the test"<br />
precced=0;<br />
#kill -INT $vid_pid $str_pid $log_pid;<br />
sleep 3;<br />
test_status=`cat env-chamber-testing.log | grep -i "error" | grep -v -e "0 errors" -e "no corrected errors"`<br />
if [ -z "$test_status" ]<br />
then<br />
echo "*********TEST PASS*********"<br />
else<br />
echo "*********TEST FAIL*********"<br />
echo "List of detected errors:"<br />
cat env-chamber-testing.log | grep -i "error" | grep -v -e "0 errors" -e "no corrected errors" -e "List of detected errors:"<br />
fi<br />
updateLogFiles<br />
exit;<br />
}<br />
<br />
# kill all processes if Ctrl+C is detected<br />
trap finish_test_now 2<br />
<br />
# play a video stream<br />
gst-launch-1.0 -q imxv4l2src ! autovideosink &<br />
<br />
# stressapptest - CPU threads and RAM memory threads<br />
if [ "${basic}" -eq "1" ]; then<br />
stress-ng --cpu 2 --vm 4 &<br />
str_pid=$!<br />
fi<br />
if [ "${pro}" -eq "1" ]; then<br />
stress-ng --cpu 4 --vm 4 &<br />
str_pid=$!<br />
fi<br />
if [ "${max}" -eq "1" ]; then<br />
stress-ng --cpu 4 --vm 4 &<br />
str_pid=$!<br />
fi<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) Starting stressapptest with PID: " $str_pid<br />
<br />
proceed=1<br />
# create test files<br />
file1_path=`mktemp`<br />
file2_path=`mktemp`<br />
file1=`basename $file1_path`<br />
file2=`basename $file2_path`<br />
<br />
dd if=/dev/urandom of=$file1_path bs=1024 count=10000<br />
dd if=/dev/urandom of=$file2_path bs=1024 count=10000<br />
<br />
cp1_from="/media/mmc0/"<br />
cp1_to="/media/usb0/"<br />
<br />
cp2_from="/media/usb0/"<br />
cp2_to="/media/usb1/"<br />
<br />
#copy files in case they are missing<br />
cp $file1_path $cp1_from<br />
cp $file1_path $cp1_to<br />
cp $file2_path $cp2_from<br />
cp $file2_path $cp2_to<br />
<br />
while [ $proceed -eq 1 ]<br />
do<br />
<br />
ping -q -c1 192.168.0.2 >> env-chamber-testing.log<br />
if [ $? -ne 0 ]<br />
then<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) ERROR: Ping failed"<br />
fi<br />
<br />
cp1_done=`ps | grep $cp1_pid | grep cp`<br />
if [ -z "$cp1_done" ]; then # copy finished<br />
if cmp -s $cp1_from$file1 $cp1_to$file1; then<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) PASS: Copying file from $cp1_from to $cp1_to successful"<br />
else<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) ERROR: Difference between files on $cp1_from and $cp1_to detected"<br />
fi<br />
cp1_temp=$cp1_from # swap destinations<br />
cp1_from=$cp1_to<br />
cp1_to=$cp1_temp<br />
<br />
rm $cp1_to$file1 # remove destination file<br />
<br />
cp $cp1_from$file1 $cp1_to$file1 &<br />
cp1_pid=$!<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) Started copying file from $cp1_from to $cp1_to"<br />
fi<br />
<br />
cp2_done=`ps | grep $cp2_pid | grep cp`<br />
if [ -z "$cp2_done" ]; then # copy finished<br />
if cmp -s $cp2_from$file2 $cp2_to$file2; then<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) PASS: Copying file from $cp2_from to $cp2_to successful"<br />
else<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) ERROR: Difference between files on $cp2_from and $cp2_to detected"<br />
fi<br />
cp2_temp=$cp2_from # swap destinations<br />
cp2_from=$cp2_to<br />
cp2_to=$cp2_temp<br />
<br />
rm $cp2_to$file2 # remove destination file<br />
<br />
cp $cp2_from$file2 $cp2_to$file2 &<br />
cp2_pid=$!<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) Started copying file from $cp2_from to $cp2_to"<br />
fi<br />
<br />
done<br />
</syntaxhighlight><br />
<br />
=== Starting camera capture ===<br />
==== Digilent camera ====<br />
To initiate the camera to start the capturing of video stream, following command can be used:<br />
<syntaxhighlight lang="bash"><br />
GST_DEBUG=GST_BUFFER:5 gst-launch-1.0 v4l2src device=/dev/video1 ! 'video/x-raw,framerate=30/1' ! autovideosink<br />
</syntaxhighlight><br />
<br />
==== NXP camera ====<br />
To initiate the camera to start the capturing of video stream, following command can be used:<br />
<syntaxhighlight lang="bash"><br />
GST_DEBUG=GST_BUFFER:5 gst-launch-1.0 v4l2src device=/dev/video0 ! 'video/x-raw,framerate=30/1' ! autovideosink<br />
</syntaxhighlight></div>
Voipac-hw
https://wiki.voipac.com/index.php?title=iMX93_Industrial_Environmental_chamber_testing&diff=5559
iMX93 Industrial Environmental chamber testing
2025-05-14T13:25:25Z
<p>Voipac-hw: </p>
<hr />
<div>[[Category:iMX93 Industrial Development Kit]]<br />
[[Category:iMX93 Industrial Development Kit Testing]]<br />
<!-- --><br />
<div style="float:right">__TOC__</div><br />
<br />
On this page environmental stress testing results of iMX93 Industrial Development Kit are displayed. Detailed instructions how to setup kits are also shown.<br />
<br />
== Hardware configuration ==<br />
All of the modules used standard specification except of the temperature ranges for the key components as described below:<br />
<br /><br />
* 1x iMX Industrial Development Kit in [[iMX93 Industrial Max|Max configuration]]<br />
** i.MX 8M Quad 1.3GHz CPU - extended industrial temperature range (-40°C to +105°C)<br />
** 4GB LPDDR4 Memory - extended industrial temperature range (-40°C to +95°C)<br />
** eMMC 32GB - industrial temperature range (-40°C to +85°C)<br />
** SPB228-D-3 WiFi & Bluetooth Module - industrial temperature range (-40°C to +85°C)<br />
<br /><br />
* 1x iMX93 Industrial Development Kit in [[iMX93 Industrial Pro|Pro configuration]]<br />
** i.MX 8M QuadLite 1.3GHz CPU - extended industrial temperature range (-40°C to +105°C)<br />
** 2GB LPDDR4 Memory - automotive temperature range (-40°C to +95°C)<br />
** eMMC 16GB - industrial temperature range (-40°C to +85°C)<br />
** SPB228-D-3 WiFi & Bluetooth Module - industrial temperature range (-40°C to +85°C)<br />
<br /><br />
* 1x iMX93 Industrial Development Kit in [[iMX93 Industrial Basic|Basic configuration]]<br />
** i.MX 8M Dual 1.3GHz CPU - extended industrial temperature range (-40°C to +105°C)<br />
** 1GB LPDDR4 Memory - industrial temperature range (-40°C to +95°C)<br />
** eMMC 8GB - industrial temperature range (-40°C to +85°C)<br />
<br /><br />
* 1x iMX93 Industrial Development Kit in [[iMX93 Industrial Max|Max configuration]]<br />
** i.MX 8M Quad 1.5GHz CPU - extended commercial temperature range (0°C to +95°C)<br />
** 4GB LPDDR4 Memory - industrial temperature range (-30°C to +85°C)<br />
** eMMC 32GB - extended temperature range (-25°C to +85°C)<br />
** CM-276NF WiFi & Bluetooth Module - industrial temperature range (-30°C to +85°C)<br />
<br /><br />
All of the tested modules used standard configuration of iMX Development Baseboard with extended temperature range (-20°C to +70°C). The majority of tested kits used the standard heatsink sized 25x25x25mm, which is included in every development kit package, thus showcasing that this standardised heatsink performs even in very harsh conditions. One of the kits was mounted with a larger heatsink and one of the standard heatsinks was mounted with an active fan to test its impact on the performance.<br /><br />
To test the performance of the video capturing capabilities of the development kits under extreme conditions, NXP MIPI-CSI and Digilent MIPI-CSI cameras were included in the tested setups.<br />
<br /><br />
<br />
The setup in the environmental chamber:<br /><br />
[[image:iMX8M_Industrial_Development_Kits-Enviromental_chamber_overview_with_description.jpg|800px]]<br />
<br />
== Test description ==<br />
Four iMX8M Industrial Development Kits (one in Max Industrial configuration, one in Pro Industrial configuration, one in Basic Industrial configuration and one in Max Commercial configuration) were running CPU and memory tests to stress out all the most significant peripherals in the whole Industrial temperature scale, ranging from -40°C to +85°C, to check the reliability and stability of the firmware and hardware design.<br /><br /><br />
<br />
Configuration, software and testing threads in details:<br /><br /><br />
<br />
'''1x iMX8M Industrial Development Kit [setup no. 4] in [[iMX8M Industrial Max|Max configuration]] and Industrial temperature range<br />CPU and memory stress testing'''<br />
* 1 thread of extensive DDR4 Memory stress test<br />
* 1 thread of CPU stress test<br />
* sending HDMI Output to external monitor<br />
* all the messages were displayed on the serial console connected via Micro USB cable<br />
* firmware running from eMMC Flash memory<br />
* Ethernet cable connected to network switch placed outside of the chamber<br />
* 2x USB device connected and placed outside of the chamber<br />
* WiFi and Bluetooth module active, connected to the antennas and running discovery mode<br />
* large 48x48x16mm heatsink<br />
<br /><br />
'''1x iMX8M Industrial Development Kit [setup no. 2] in [[iMX8M Industrial Pro|Pro configuration]] and Industrial temperature range<br />CPU and memory stress testing'''<br />
* 1 thread of extensive DDR4 Memory stress test<br />
* 1 thread of CPU stress test<br />
* sending HDMI Output to external monitor<br />
* NXP MIPI-CSI camera connected and capturing video stream<br />
* all the messages were displayed on the serial console connected via Micro USB cable<br />
* firmware running from eMMC Flash memory<br />
* Ethernet cable connected to network switch placed outside of the chamber<br />
* 2x USB device connected and placed outside of the chamber<br />
* WiFi and Bluetooth module active, connected to the antennas and running discovery mode<br />
* standard 25x25x25mm heatsink<br />
<br /><br />
'''1x iMX8M Industrial Development Kit [setup no. 1] in [[iMX8M Industrial Basic|Basic configuration]] and Industrial temperature range<br />CPU and memory stress testing'''<br />
* 1 thread of extensive DDR4 Memory stress test<br />
* 1 thread of CPU stress test<br />
* sending HDMI Output to external monitor<br />
* all the messages were displayed on the serial console connected via Micro USB cable<br />
* firmware running from eMMC Flash memory<br />
* Ethernet cable connected to network switch placed outside of the chamber<br />
* 2x USB device connected and placed outside of the chamber<br />
* WiFi PCI Express card plugged in, connected to the antennas and running discovery mode<br />
* standard 25x25x25mm heatsink<br />
<br /><br />
'''1x iMX8M Industrial Development Kit [setup no. 3] in [[iMX8M Industrial Max|Max configuration]] and Commercial temperature range<br />CPU and memory stress testing'''<br />
* 1 thread of extensive DDR4 Memory stress test<br />
* 1 thread of CPU stress test<br />
* sending HDMI Output to external monitor<br />
* Digilent MIPI-CSI camera connected and capturing video stream<br />
* all the messages were displayed on the serial console connected via Micro USB cable<br />
* firmware running from eMMC Flash memory<br />
* Ethernet cable connected to network switch placed outside of the chamber<br />
* 2x USB device connected and placed outside of the chamber<br />
* WiFi and Bluetooth module active, connected to the antennas and running discovery mode<br />
* standard 25x25x25mm heatsink including a fan<br />
<br /><br />
Power sources, USB flash devices, network switch, HDMI monitor and controlling PC were placed outside the environmental chamber. All the scripts running during the test and the board setup instructions can be found in section [[#Preparing the test|How to prepare the test]].<br />
<br />
== Testing Results ==<br />
The picture below shows the temperature profile during the whole testing process. Humidity was not controlled. The temperature gradient for the environment chamber was set to 1°C/min.<br /><br />
[[image:iMX8M_Industrial_Development_Kit-Env_chamber_temperature_profile.png|800px]]<br />
<br />
=== Running the development kits at -40°C – PASS ===<br />
Test description: CPU, Memory and peripheral stress tests were running at -40°C. All the tested kits were working without errors during the whole time, even if some components used for iMX8M Industrial Development Kit Max in Commercial temperature range were only rated for the temperature range between 0°C and +95°C.<br /><br /><br />
<br />
A closer image on the temperature chamber displaying the minimum temperature is shown below. These readouts are available on the display:<br />
* the first number shows current temperature<br />
* the second one set temperature<br />
* the last two shows relative humidity. Humidity was not controlled during testing process.<br />
[[image:iMX8M Industrial Kit-Env chamber-Boards at -40C.jpg|800px]]<br />
<br /><br /><br />
[[image:iMX8M_Industrial_Development_Kit-Env_chamber_at_-40C.jpg|800px]]<br />
<br />
=== Running the development kits at +85°C – PASS ===<br />
Test description: The pre-set temperature profile was followed until the development kits gradually reached +85°C. The kits remained around this temperature for the duration of two hours and at the end of this whole cycle all the kits were running.<br /><br />
[[image:iMX8M_Industrial_Kit-Env_chamber-Boards_at_+86C.jpg|800px]]<br />
<br /><br /><br />
[[image:iMX8M_Industrial_Development_Kit-Env_chamber_at_+85C.jpg|800px]]<br />
<br />
=== Switch OFF/ON test at -40°C – PASS ===<br />
Test description: At temperature -40°C the development kits were switched OFF, left OFF for at least 15 minutes (to cool down completely) and then switched ON to see if they boot up without problems. Once booted up into Linux, the test script was launched to test RAM memory and all peripherals. The kits were turned OFF and ON again multiple times to see potential issues at the lowest temperature level. All of the tested setups booted up successfully.<br />
<br />
<br /><br />
[[image:iMX8M Industrial Kit-Env chamber-Boards snow.jpg|800px]]<br />
<br />
== PC setup ==<br />
The PC was used during the test to control / monitor all the kits through serial console sessions. The control computer was running Windows 10 operating system.<br />
<br />
=== HDMI Outputs and Serial consoles ===<br />
To control iMX8M Industrial Development Kits, one TeraTerm serial console was opened for each setup. The kits were connected to the external HDMI switch to monitor HDMI outputs.<br />
<br /><br /><br />
The setup of the environmental chamber cables and out-of-chamber equipment:<br />
<br /><br />
[[image:iMX8M Industrial Development Kit-Climate chamber overview.jpg|800px]]<br />
<br />
== Preparing the test ==<br />
=== Boot device and software ===<br />
The eMMC memory was selected as a booting device for all the kits. Device tree files were not adjusted as the default configuration was used. The only change compared to standard software package was running the test script. In order to flash a fresh firmware into the eMMC Memory follow [[iMX8M_Industrial_Flashing_Procedure|these instructions]].<br />
<br />
=== Downloading stress test ===<br />
Stress-ng package was selected to check CPU and memory integrity. Placing this file into the same directory where the testing script will be stored is important:<br />
<syntaxhighlight lang="bash"><br />
wget https://downloads.voipac.com/files/iMX8M_Industrial_Development_Kit/module/documents/Thermal_stress_resistance/imx8mq-voipac-peripheral-test.sh<br />
</syntaxhighlight><br />
<br />
=== Start CPU and memory stress test ===<br />
Navigate into the directory, where stress test feature and the testing script are stored.<br /><br /><br />
<br />
Stress sequence script:<br />
<syntaxhighlight lang="bash"><br />
for d in $(seq 1 1 99999)<br />
do<br />
uptime<br />
echo "Test $a Test $b Test $c $d times"<br />
echo "Start stress-ng --iomix 1 -t 10 -v"<br />
stress-ng --iomix 1 -t 10 -v<br />
echo "End"<br />
echo "Start stress-ng --cpu 2 --vm 4 -t 10"<br />
stress-ng --cpu 2 --vm 4 -t 10<br />
echo "End"<br />
echo "Start stress-ng --shm 0 -t 10"<br />
stress-ng --shm 0 -t 10<br />
echo "End"<br />
echo "Start stress-ng --seq 0 -t 2 --tz -v"<br />
stress-ng --seq 0 -t 2 --tz -v<br />
echo "End"<br />
echo "Start Thermal zone information"<br />
stress-ng --matrix 0 --tz -t 10 --log-brief -t 10<br />
echo "End"<br />
done<br />
</syntaxhighlight><br />
<br />
=== Start peripheral test ===<br />
Plug the development kit into mains and connect it to the controlling PC via console. Before the first time usage of the script, permissions need to be granted by the following command: <br />
<syntaxhighlight lang="bash"><br />
chmod +x imx8m-voipac-peripheral-test.sh<br />
</syntaxhighlight><br />
<br /><br />
Testing scripts command consists of the following arguments:<br />
* the first parameter - configuration of tested development kit (Max, Pro or Basic)<br />
* the second parameter - USB drive 1 location<br />
* the third parameter - USB drive 2 location<br />
* the fourth parameter - SD card location<br />
<br /><br />
Several commands used during environmental chamber testing are shown below:<br />
<br />
* iMX8M Industrial Development Kit Max:<br />
<syntaxhighlight lang="bash"><br />
./imx8m-voipac-peripheral-test.sh -max sda1 sdb1 mmcblk1p1 | tee -i imx8m-env-testing.log<br />
</syntaxhighlight><br />
* iMX8M Industrial Development Kit Pro:<br />
<syntaxhighlight lang="bash"><br />
./imx8m-voipac-peripheral-test.sh -pro sda1 sdb1 mmcblk1p1 | tee -i imx8m-env-testing.log<br />
</syntaxhighlight><br />
* iMX8M Industrial Development Kit Basic:<br />
<syntaxhighlight lang="bash"><br />
./imx8m-voipac-peripheral-test.sh -basic sda1 sdb1 mmcblk1p1 | tee -i imx8m-env-testing.log<br />
</syntaxhighlight><br />
<br /><br />
The complete script can be found in [https://downloads.voipac.com/files/iMX8M_Industrial_Development_Kit/module/documents/Thermal_stress_resistance/imx8mq-voipac-peripheral-test.sh the downloads section] or down below:<br />
<syntaxhighlight lang="bash"><br />
#!/bin/sh<br />
<br />
# iMX8MQ environmental chamber peripheral test<br />
<br />
mountDevice() {<br />
mkdir -p "/media/$2"<br />
mount /dev/$1 /media/$2<br />
cat /proc/mounts | grep -F "/dev/$1 /media/$2"<br />
if [ "$?" -eq "0" ]; then<br />
echo "$2 mounted"<br />
else<br />
echo "$2 not mounted"; exit 2<br />
fi<br />
}<br />
<br />
# prepare files<br />
cd ~/<br />
mkdir -p env-chamber-testing/<br />
cd env-chamber-testing/<br />
<br />
touch env-chamber-testing.log<br />
touch cpu-temp.log<br />
<br />
basic=0<br />
pro=0<br />
max=0<br />
case $1 in<br />
-basic) basic=1 ;;<br />
-pro) pro=1 ;;<br />
-max) max=1 ;;<br />
*)<br />
esac<br />
<br />
# mount devices<br />
mountDevice $2 usb0<br />
mountDevice $3 usb1<br />
mountDevice $4 mmc0<br />
<br />
updateLogFiles() {<br />
# obtain board ID from IP address - be sure addresses are allocated based on MAC<br />
boardID=$(/sbin/ip -o -4 addr list eth0 | awk '{print $4}' | cut -d/ -f1 | cut -d'.' -f4 | cut -d'2' -f2);<br />
# be sure time server is running on DHCP server<br />
currentTime=`date +%Y-%m-%d.%H:%M`<br />
<br />
mv env-chamber-testing.log trx-board-$boardID-env-chamber.log.$currentTime<br />
mv cpu-temp.log trx-board-$boardID-env-cpu-temp.log.$currentTime<br />
}<br />
<br />
finish_test_now() {<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) Ctrl+C Detected: End of the test"<br />
precced=0;<br />
#kill -INT $vid_pid $str_pid $log_pid;<br />
sleep 3;<br />
test_status=`cat env-chamber-testing.log | grep -i "error" | grep -v -e "0 errors" -e "no corrected errors"`<br />
if [ -z "$test_status" ]<br />
then<br />
echo "*********TEST PASS*********"<br />
else<br />
echo "*********TEST FAIL*********"<br />
echo "List of detected errors:"<br />
cat env-chamber-testing.log | grep -i "error" | grep -v -e "0 errors" -e "no corrected errors" -e "List of detected errors:"<br />
fi<br />
updateLogFiles<br />
exit;<br />
}<br />
<br />
# kill all processes if Ctrl+C is detected<br />
trap finish_test_now 2<br />
<br />
# play a video stream<br />
gst-launch-1.0 -q imxv4l2src ! autovideosink &<br />
<br />
# stressapptest - CPU threads and RAM memory threads<br />
if [ "${basic}" -eq "1" ]; then<br />
stress-ng --cpu 2 --vm 4 &<br />
str_pid=$!<br />
fi<br />
if [ "${pro}" -eq "1" ]; then<br />
stress-ng --cpu 4 --vm 4 &<br />
str_pid=$!<br />
fi<br />
if [ "${max}" -eq "1" ]; then<br />
stress-ng --cpu 4 --vm 4 &<br />
str_pid=$!<br />
fi<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) Starting stressapptest with PID: " $str_pid<br />
<br />
proceed=1<br />
# create test files<br />
file1_path=`mktemp`<br />
file2_path=`mktemp`<br />
file1=`basename $file1_path`<br />
file2=`basename $file2_path`<br />
<br />
dd if=/dev/urandom of=$file1_path bs=1024 count=10000<br />
dd if=/dev/urandom of=$file2_path bs=1024 count=10000<br />
<br />
cp1_from="/media/mmc0/"<br />
cp1_to="/media/usb0/"<br />
<br />
cp2_from="/media/usb0/"<br />
cp2_to="/media/usb1/"<br />
<br />
#copy files in case they are missing<br />
cp $file1_path $cp1_from<br />
cp $file1_path $cp1_to<br />
cp $file2_path $cp2_from<br />
cp $file2_path $cp2_to<br />
<br />
while [ $proceed -eq 1 ]<br />
do<br />
<br />
ping -q -c1 192.168.0.2 >> env-chamber-testing.log<br />
if [ $? -ne 0 ]<br />
then<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) ERROR: Ping failed"<br />
fi<br />
<br />
cp1_done=`ps | grep $cp1_pid | grep cp`<br />
if [ -z "$cp1_done" ]; then # copy finished<br />
if cmp -s $cp1_from$file1 $cp1_to$file1; then<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) PASS: Copying file from $cp1_from to $cp1_to successful"<br />
else<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) ERROR: Difference between files on $cp1_from and $cp1_to detected"<br />
fi<br />
cp1_temp=$cp1_from # swap destinations<br />
cp1_from=$cp1_to<br />
cp1_to=$cp1_temp<br />
<br />
rm $cp1_to$file1 # remove destination file<br />
<br />
cp $cp1_from$file1 $cp1_to$file1 &<br />
cp1_pid=$!<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) Started copying file from $cp1_from to $cp1_to"<br />
fi<br />
<br />
cp2_done=`ps | grep $cp2_pid | grep cp`<br />
if [ -z "$cp2_done" ]; then # copy finished<br />
if cmp -s $cp2_from$file2 $cp2_to$file2; then<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) PASS: Copying file from $cp2_from to $cp2_to successful"<br />
else<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) ERROR: Difference between files on $cp2_from and $cp2_to detected"<br />
fi<br />
cp2_temp=$cp2_from # swap destinations<br />
cp2_from=$cp2_to<br />
cp2_to=$cp2_temp<br />
<br />
rm $cp2_to$file2 # remove destination file<br />
<br />
cp $cp2_from$file2 $cp2_to$file2 &<br />
cp2_pid=$!<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) Started copying file from $cp2_from to $cp2_to"<br />
fi<br />
<br />
done<br />
</syntaxhighlight><br />
<br />
=== Starting camera capture ===<br />
==== Digilent camera ====<br />
To initiate the camera to start the capturing of video stream, following command can be used:<br />
<syntaxhighlight lang="bash"><br />
GST_DEBUG=GST_BUFFER:5 gst-launch-1.0 v4l2src device=/dev/video1 ! 'video/x-raw,framerate=30/1' ! autovideosink<br />
</syntaxhighlight><br />
<br />
==== NXP camera ====<br />
To initiate the camera to start the capturing of video stream, following command can be used:<br />
<syntaxhighlight lang="bash"><br />
GST_DEBUG=GST_BUFFER:5 gst-launch-1.0 v4l2src device=/dev/video0 ! 'video/x-raw,framerate=30/1' ! autovideosink<br />
</syntaxhighlight></div>
Voipac-hw
https://wiki.voipac.com/index.php?title=iMX93_Industrial_Environmental_chamber_testing&diff=5558
iMX93 Industrial Environmental chamber testing
2025-05-14T13:20:11Z
<p>Voipac-hw: </p>
<hr />
<div>[[Category:iMX8M Industrial Development Kit]]<br />
[[Category:iMX8M Industrial Development Kit Testing]]<br />
<!-- --><br />
<div style="float:right">__TOC__</div><br />
<br />
On this page environmental stress testing results of iMX8M Industrial Development Kit are displayed. Detailed instructions how to setup kits are also shown.<br />
<br />
== Hardware configuration ==<br />
All of the modules used standard specification except of the temperature ranges for the key components as described below:<br />
<br /><br />
* 1x iMX8M Industrial Development Kit in [[iMX8M Industrial Max|Max configuration]]<br />
** i.MX 8M Quad 1.3GHz CPU - extended industrial temperature range (-40°C to +105°C)<br />
** 4GB LPDDR4 Memory - extended industrial temperature range (-40°C to +95°C)<br />
** eMMC 32GB - industrial temperature range (-40°C to +85°C)<br />
** SPB228-D-3 WiFi & Bluetooth Module - industrial temperature range (-40°C to +85°C)<br />
<br /><br />
* 1x iMX8M Industrial Development Kit in [[iMX8M Industrial Pro|Pro configuration]]<br />
** i.MX 8M QuadLite 1.3GHz CPU - extended industrial temperature range (-40°C to +105°C)<br />
** 2GB LPDDR4 Memory - automotive temperature range (-40°C to +95°C)<br />
** eMMC 16GB - industrial temperature range (-40°C to +85°C)<br />
** SPB228-D-3 WiFi & Bluetooth Module - industrial temperature range (-40°C to +85°C)<br />
<br /><br />
* 1x iMX8M Industrial Development Kit in [[iMX8M Industrial Basic|Basic configuration]]<br />
** i.MX 8M Dual 1.3GHz CPU - extended industrial temperature range (-40°C to +105°C)<br />
** 1GB LPDDR4 Memory - industrial temperature range (-40°C to +95°C)<br />
** eMMC 8GB - industrial temperature range (-40°C to +85°C)<br />
<br /><br />
* 1x iMX8M Industrial Development Kit in [[iMX8M Industrial Max|Max configuration]]<br />
** i.MX 8M Quad 1.5GHz CPU - extended commercial temperature range (0°C to +95°C)<br />
** 4GB LPDDR4 Memory - industrial temperature range (-30°C to +85°C)<br />
** eMMC 32GB - extended temperature range (-25°C to +85°C)<br />
** CM-276NF WiFi & Bluetooth Module - industrial temperature range (-30°C to +85°C)<br />
<br /><br />
All of the tested modules used standard configuration of iMX Development Baseboard with extended temperature range (-20°C to +70°C). The majority of tested kits used the standard heatsink sized 25x25x25mm, which is included in every development kit package, thus showcasing that this standardised heatsink performs even in very harsh conditions. One of the kits was mounted with a larger heatsink and one of the standard heatsinks was mounted with an active fan to test its impact on the performance.<br /><br />
To test the performance of the video capturing capabilities of the development kits under extreme conditions, NXP MIPI-CSI and Digilent MIPI-CSI cameras were included in the tested setups.<br />
<br /><br />
<br />
The setup in the environmental chamber:<br /><br />
[[image:iMX8M_Industrial_Development_Kits-Enviromental_chamber_overview_with_description.jpg|800px]]<br />
<br />
== Test description ==<br />
Four iMX8M Industrial Development Kits (one in Max Industrial configuration, one in Pro Industrial configuration, one in Basic Industrial configuration and one in Max Commercial configuration) were running CPU and memory tests to stress out all the most significant peripherals in the whole Industrial temperature scale, ranging from -40°C to +85°C, to check the reliability and stability of the firmware and hardware design.<br /><br /><br />
<br />
Configuration, software and testing threads in details:<br /><br /><br />
<br />
'''1x iMX8M Industrial Development Kit [setup no. 4] in [[iMX8M Industrial Max|Max configuration]] and Industrial temperature range<br />CPU and memory stress testing'''<br />
* 1 thread of extensive DDR4 Memory stress test<br />
* 1 thread of CPU stress test<br />
* sending HDMI Output to external monitor<br />
* all the messages were displayed on the serial console connected via Micro USB cable<br />
* firmware running from eMMC Flash memory<br />
* Ethernet cable connected to network switch placed outside of the chamber<br />
* 2x USB device connected and placed outside of the chamber<br />
* WiFi and Bluetooth module active, connected to the antennas and running discovery mode<br />
* large 48x48x16mm heatsink<br />
<br /><br />
'''1x iMX8M Industrial Development Kit [setup no. 2] in [[iMX8M Industrial Pro|Pro configuration]] and Industrial temperature range<br />CPU and memory stress testing'''<br />
* 1 thread of extensive DDR4 Memory stress test<br />
* 1 thread of CPU stress test<br />
* sending HDMI Output to external monitor<br />
* NXP MIPI-CSI camera connected and capturing video stream<br />
* all the messages were displayed on the serial console connected via Micro USB cable<br />
* firmware running from eMMC Flash memory<br />
* Ethernet cable connected to network switch placed outside of the chamber<br />
* 2x USB device connected and placed outside of the chamber<br />
* WiFi and Bluetooth module active, connected to the antennas and running discovery mode<br />
* standard 25x25x25mm heatsink<br />
<br /><br />
'''1x iMX8M Industrial Development Kit [setup no. 1] in [[iMX8M Industrial Basic|Basic configuration]] and Industrial temperature range<br />CPU and memory stress testing'''<br />
* 1 thread of extensive DDR4 Memory stress test<br />
* 1 thread of CPU stress test<br />
* sending HDMI Output to external monitor<br />
* all the messages were displayed on the serial console connected via Micro USB cable<br />
* firmware running from eMMC Flash memory<br />
* Ethernet cable connected to network switch placed outside of the chamber<br />
* 2x USB device connected and placed outside of the chamber<br />
* WiFi PCI Express card plugged in, connected to the antennas and running discovery mode<br />
* standard 25x25x25mm heatsink<br />
<br /><br />
'''1x iMX8M Industrial Development Kit [setup no. 3] in [[iMX8M Industrial Max|Max configuration]] and Commercial temperature range<br />CPU and memory stress testing'''<br />
* 1 thread of extensive DDR4 Memory stress test<br />
* 1 thread of CPU stress test<br />
* sending HDMI Output to external monitor<br />
* Digilent MIPI-CSI camera connected and capturing video stream<br />
* all the messages were displayed on the serial console connected via Micro USB cable<br />
* firmware running from eMMC Flash memory<br />
* Ethernet cable connected to network switch placed outside of the chamber<br />
* 2x USB device connected and placed outside of the chamber<br />
* WiFi and Bluetooth module active, connected to the antennas and running discovery mode<br />
* standard 25x25x25mm heatsink including a fan<br />
<br /><br />
Power sources, USB flash devices, network switch, HDMI monitor and controlling PC were placed outside the environmental chamber. All the scripts running during the test and the board setup instructions can be found in section [[#Preparing the test|How to prepare the test]].<br />
<br />
== Testing Results ==<br />
The picture below shows the temperature profile during the whole testing process. Humidity was not controlled. The temperature gradient for the environment chamber was set to 1°C/min.<br /><br />
[[image:iMX8M_Industrial_Development_Kit-Env_chamber_temperature_profile.png|800px]]<br />
<br />
=== Running the development kits at -40°C – PASS ===<br />
Test description: CPU, Memory and peripheral stress tests were running at -40°C. All the tested kits were working without errors during the whole time, even if some components used for iMX8M Industrial Development Kit Max in Commercial temperature range were only rated for the temperature range between 0°C and +95°C.<br /><br /><br />
<br />
A closer image on the temperature chamber displaying the minimum temperature is shown below. These readouts are available on the display:<br />
* the first number shows current temperature<br />
* the second one set temperature<br />
* the last two shows relative humidity. Humidity was not controlled during testing process.<br />
[[image:iMX8M Industrial Kit-Env chamber-Boards at -40C.jpg|800px]]<br />
<br /><br /><br />
[[image:iMX8M_Industrial_Development_Kit-Env_chamber_at_-40C.jpg|800px]]<br />
<br />
=== Running the development kits at +85°C – PASS ===<br />
Test description: The pre-set temperature profile was followed until the development kits gradually reached +85°C. The kits remained around this temperature for the duration of two hours and at the end of this whole cycle all the kits were running.<br /><br />
[[image:iMX8M_Industrial_Kit-Env_chamber-Boards_at_+86C.jpg|800px]]<br />
<br /><br /><br />
[[image:iMX8M_Industrial_Development_Kit-Env_chamber_at_+85C.jpg|800px]]<br />
<br />
=== Switch OFF/ON test at -40°C – PASS ===<br />
Test description: At temperature -40°C the development kits were switched OFF, left OFF for at least 15 minutes (to cool down completely) and then switched ON to see if they boot up without problems. Once booted up into Linux, the test script was launched to test RAM memory and all peripherals. The kits were turned OFF and ON again multiple times to see potential issues at the lowest temperature level. All of the tested setups booted up successfully.<br />
<br />
<br /><br />
[[image:iMX8M Industrial Kit-Env chamber-Boards snow.jpg|800px]]<br />
<br />
== PC setup ==<br />
The PC was used during the test to control / monitor all the kits through serial console sessions. The control computer was running Windows 10 operating system.<br />
<br />
=== HDMI Outputs and Serial consoles ===<br />
To control iMX8M Industrial Development Kits, one TeraTerm serial console was opened for each setup. The kits were connected to the external HDMI switch to monitor HDMI outputs.<br />
<br /><br /><br />
The setup of the environmental chamber cables and out-of-chamber equipment:<br />
<br /><br />
[[image:iMX8M Industrial Development Kit-Climate chamber overview.jpg|800px]]<br />
<br />
== Preparing the test ==<br />
=== Boot device and software ===<br />
The eMMC memory was selected as a booting device for all the kits. Device tree files were not adjusted as the default configuration was used. The only change compared to standard software package was running the test script. In order to flash a fresh firmware into the eMMC Memory follow [[iMX8M_Industrial_Flashing_Procedure|these instructions]].<br />
<br />
=== Downloading stress test ===<br />
Stress-ng package was selected to check CPU and memory integrity. Placing this file into the same directory where the testing script will be stored is important:<br />
<syntaxhighlight lang="bash"><br />
wget https://downloads.voipac.com/files/iMX8M_Industrial_Development_Kit/module/documents/Thermal_stress_resistance/imx8mq-voipac-peripheral-test.sh<br />
</syntaxhighlight><br />
<br />
=== Start CPU and memory stress test ===<br />
Navigate into the directory, where stress test feature and the testing script are stored.<br /><br /><br />
<br />
Stress sequence script:<br />
<syntaxhighlight lang="bash"><br />
for d in $(seq 1 1 99999)<br />
do<br />
uptime<br />
echo "Test $a Test $b Test $c $d times"<br />
echo "Start stress-ng --iomix 1 -t 10 -v"<br />
stress-ng --iomix 1 -t 10 -v<br />
echo "End"<br />
echo "Start stress-ng --cpu 2 --vm 4 -t 10"<br />
stress-ng --cpu 2 --vm 4 -t 10<br />
echo "End"<br />
echo "Start stress-ng --shm 0 -t 10"<br />
stress-ng --shm 0 -t 10<br />
echo "End"<br />
echo "Start stress-ng --seq 0 -t 2 --tz -v"<br />
stress-ng --seq 0 -t 2 --tz -v<br />
echo "End"<br />
echo "Start Thermal zone information"<br />
stress-ng --matrix 0 --tz -t 10 --log-brief -t 10<br />
echo "End"<br />
done<br />
</syntaxhighlight><br />
<br />
=== Start peripheral test ===<br />
Plug the development kit into mains and connect it to the controlling PC via console. Before the first time usage of the script, permissions need to be granted by the following command: <br />
<syntaxhighlight lang="bash"><br />
chmod +x imx8m-voipac-peripheral-test.sh<br />
</syntaxhighlight><br />
<br /><br />
Testing scripts command consists of the following arguments:<br />
* the first parameter - configuration of tested development kit (Max, Pro or Basic)<br />
* the second parameter - USB drive 1 location<br />
* the third parameter - USB drive 2 location<br />
* the fourth parameter - SD card location<br />
<br /><br />
Several commands used during environmental chamber testing are shown below:<br />
<br />
* iMX8M Industrial Development Kit Max:<br />
<syntaxhighlight lang="bash"><br />
./imx8m-voipac-peripheral-test.sh -max sda1 sdb1 mmcblk1p1 | tee -i imx8m-env-testing.log<br />
</syntaxhighlight><br />
* iMX8M Industrial Development Kit Pro:<br />
<syntaxhighlight lang="bash"><br />
./imx8m-voipac-peripheral-test.sh -pro sda1 sdb1 mmcblk1p1 | tee -i imx8m-env-testing.log<br />
</syntaxhighlight><br />
* iMX8M Industrial Development Kit Basic:<br />
<syntaxhighlight lang="bash"><br />
./imx8m-voipac-peripheral-test.sh -basic sda1 sdb1 mmcblk1p1 | tee -i imx8m-env-testing.log<br />
</syntaxhighlight><br />
<br /><br />
The complete script can be found in [https://downloads.voipac.com/files/iMX8M_Industrial_Development_Kit/module/documents/Thermal_stress_resistance/imx8mq-voipac-peripheral-test.sh the downloads section] or down below:<br />
<syntaxhighlight lang="bash"><br />
#!/bin/sh<br />
<br />
# iMX8MQ environmental chamber peripheral test<br />
<br />
mountDevice() {<br />
mkdir -p "/media/$2"<br />
mount /dev/$1 /media/$2<br />
cat /proc/mounts | grep -F "/dev/$1 /media/$2"<br />
if [ "$?" -eq "0" ]; then<br />
echo "$2 mounted"<br />
else<br />
echo "$2 not mounted"; exit 2<br />
fi<br />
}<br />
<br />
# prepare files<br />
cd ~/<br />
mkdir -p env-chamber-testing/<br />
cd env-chamber-testing/<br />
<br />
touch env-chamber-testing.log<br />
touch cpu-temp.log<br />
<br />
basic=0<br />
pro=0<br />
max=0<br />
case $1 in<br />
-basic) basic=1 ;;<br />
-pro) pro=1 ;;<br />
-max) max=1 ;;<br />
*)<br />
esac<br />
<br />
# mount devices<br />
mountDevice $2 usb0<br />
mountDevice $3 usb1<br />
mountDevice $4 mmc0<br />
<br />
updateLogFiles() {<br />
# obtain board ID from IP address - be sure addresses are allocated based on MAC<br />
boardID=$(/sbin/ip -o -4 addr list eth0 | awk '{print $4}' | cut -d/ -f1 | cut -d'.' -f4 | cut -d'2' -f2);<br />
# be sure time server is running on DHCP server<br />
currentTime=`date +%Y-%m-%d.%H:%M`<br />
<br />
mv env-chamber-testing.log trx-board-$boardID-env-chamber.log.$currentTime<br />
mv cpu-temp.log trx-board-$boardID-env-cpu-temp.log.$currentTime<br />
}<br />
<br />
finish_test_now() {<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) Ctrl+C Detected: End of the test"<br />
precced=0;<br />
#kill -INT $vid_pid $str_pid $log_pid;<br />
sleep 3;<br />
test_status=`cat env-chamber-testing.log | grep -i "error" | grep -v -e "0 errors" -e "no corrected errors"`<br />
if [ -z "$test_status" ]<br />
then<br />
echo "*********TEST PASS*********"<br />
else<br />
echo "*********TEST FAIL*********"<br />
echo "List of detected errors:"<br />
cat env-chamber-testing.log | grep -i "error" | grep -v -e "0 errors" -e "no corrected errors" -e "List of detected errors:"<br />
fi<br />
updateLogFiles<br />
exit;<br />
}<br />
<br />
# kill all processes if Ctrl+C is detected<br />
trap finish_test_now 2<br />
<br />
# play a video stream<br />
gst-launch-1.0 -q imxv4l2src ! autovideosink &<br />
<br />
# stressapptest - CPU threads and RAM memory threads<br />
if [ "${basic}" -eq "1" ]; then<br />
stress-ng --cpu 2 --vm 4 &<br />
str_pid=$!<br />
fi<br />
if [ "${pro}" -eq "1" ]; then<br />
stress-ng --cpu 4 --vm 4 &<br />
str_pid=$!<br />
fi<br />
if [ "${max}" -eq "1" ]; then<br />
stress-ng --cpu 4 --vm 4 &<br />
str_pid=$!<br />
fi<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) Starting stressapptest with PID: " $str_pid<br />
<br />
proceed=1<br />
# create test files<br />
file1_path=`mktemp`<br />
file2_path=`mktemp`<br />
file1=`basename $file1_path`<br />
file2=`basename $file2_path`<br />
<br />
dd if=/dev/urandom of=$file1_path bs=1024 count=10000<br />
dd if=/dev/urandom of=$file2_path bs=1024 count=10000<br />
<br />
cp1_from="/media/mmc0/"<br />
cp1_to="/media/usb0/"<br />
<br />
cp2_from="/media/usb0/"<br />
cp2_to="/media/usb1/"<br />
<br />
#copy files in case they are missing<br />
cp $file1_path $cp1_from<br />
cp $file1_path $cp1_to<br />
cp $file2_path $cp2_from<br />
cp $file2_path $cp2_to<br />
<br />
while [ $proceed -eq 1 ]<br />
do<br />
<br />
ping -q -c1 192.168.0.2 >> env-chamber-testing.log<br />
if [ $? -ne 0 ]<br />
then<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) ERROR: Ping failed"<br />
fi<br />
<br />
cp1_done=`ps | grep $cp1_pid | grep cp`<br />
if [ -z "$cp1_done" ]; then # copy finished<br />
if cmp -s $cp1_from$file1 $cp1_to$file1; then<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) PASS: Copying file from $cp1_from to $cp1_to successful"<br />
else<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) ERROR: Difference between files on $cp1_from and $cp1_to detected"<br />
fi<br />
cp1_temp=$cp1_from # swap destinations<br />
cp1_from=$cp1_to<br />
cp1_to=$cp1_temp<br />
<br />
rm $cp1_to$file1 # remove destination file<br />
<br />
cp $cp1_from$file1 $cp1_to$file1 &<br />
cp1_pid=$!<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) Started copying file from $cp1_from to $cp1_to"<br />
fi<br />
<br />
cp2_done=`ps | grep $cp2_pid | grep cp`<br />
if [ -z "$cp2_done" ]; then # copy finished<br />
if cmp -s $cp2_from$file2 $cp2_to$file2; then<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) PASS: Copying file from $cp2_from to $cp2_to successful"<br />
else<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) ERROR: Difference between files on $cp2_from and $cp2_to detected"<br />
fi<br />
cp2_temp=$cp2_from # swap destinations<br />
cp2_from=$cp2_to<br />
cp2_to=$cp2_temp<br />
<br />
rm $cp2_to$file2 # remove destination file<br />
<br />
cp $cp2_from$file2 $cp2_to$file2 &<br />
cp2_pid=$!<br />
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) Started copying file from $cp2_from to $cp2_to"<br />
fi<br />
<br />
done<br />
</syntaxhighlight><br />
<br />
=== Starting camera capture ===<br />
==== Digilent camera ====<br />
To initiate the camera to start the capturing of video stream, following command can be used:<br />
<syntaxhighlight lang="bash"><br />
GST_DEBUG=GST_BUFFER:5 gst-launch-1.0 v4l2src device=/dev/video1 ! 'video/x-raw,framerate=30/1' ! autovideosink<br />
</syntaxhighlight><br />
<br />
==== NXP camera ====<br />
To initiate the camera to start the capturing of video stream, following command can be used:<br />
<syntaxhighlight lang="bash"><br />
GST_DEBUG=GST_BUFFER:5 gst-launch-1.0 v4l2src device=/dev/video0 ! 'video/x-raw,framerate=30/1' ! autovideosink<br />
</syntaxhighlight></div>
Voipac-hw
https://wiki.voipac.com/index.php?title=DIGILENT_MIPI-CSI_Camera_Set&diff=3895
DIGILENT MIPI-CSI Camera Set
2022-10-21T15:22:37Z
<p>Voipac-hw: /* Video preview */</p>
<hr />
<div>[[Category:iMX8M Industrial Development Kit]]<br />
[[Category:iMX8M Industrial Peripherals]]<br />
<!-- --><br />
<div style="float:right">__TOC__</div><br />
<br />
This example uses Digilent Pcam 5C is a MIPI-CSI interface camera (built on OV5640 MIPI sensor) as a test device for CSI Interface. On this page OV5640 sensor integration, settings and usage on i.MX8M processors are shown.<br />
<br /><br />
[[image:Pcam-5C.png|800px]]<br /><br />
Digilent Pcam 5C is a MIPI-CSI interface, 5 MP Fixed-Focus color camera connected to iMX8M Development Baseboard <br />
<br /><br />
<br />
== Kernel detection ==<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# dmesg | grep ov56<br />
[ 2.410383] ov5640_mipi 1-003c: No pin available<br />
[ 2.415040] ov5640_mipi 1-003c: No sensor pwdn pin available<br />
[ 2.420726] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 2.426512] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.555690] ov5640_mipi 2-003c: No pin available<br />
[ 2.562074] ov5640_mipi 2-003c: No sensor reset pin available<br />
[ 2.567861] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.948998] ov5640_mipi 1-003c: No pin available<br />
[ 2.959199] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 2.970608] ov5640_mipi 1-003c: 1-003c supply DVDD not found, using dummy regulator<br />
[ 2.983356] ov5640_mipi 1-003c: 1-003c supply AVDD not found, using dummy regulator<br />
[ 4.190794] mxc-mipi-csi2_yav 30b60000.mipi_csi: Registered sensor subdevice: ov5640_mipi 1-003c<br />
[ 4.204863] ov5640_mipi 1-003c: Camera is found<br />
[ 4.209719] ov5640_mipi 2-003c: No pin available<br />
[ 4.214385] ov5640_mipi 2-003c: Failed to set power pin<br />
[ 4.219626] ov5640_mipi 2-003c: retval=-16<br />
[ 4.223747] ov5640_mipi: probe of 2-003c failed with error -16<br />
root@imx8mq-voipac:~#<br />
</syntaxhighlight><br />
<br />
== I2C detection ==<br />
DIGILENT Pcam 5C camera chip is connected via I2C2. The most important address for correct detection is 0x3c.<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# i2cdetect -y 1<br />
0 1 2 3 4 5 6 7 8 9 a b c d e f<br />
00: -- -- -- -- -- -- -- -- -- -- -- -- --<br />
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
20: -- -- -- UU -- -- -- UU -- -- -- -- -- -- -- --<br />
30: -- -- -- -- -- -- -- -- -- -- -- -- UU 3d -- --<br />
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
50: -- UU -- UU -- -- -- -- -- -- -- -- -- -- -- --<br />
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
70: -- -- -- -- -- -- -- --<br />
</syntaxhighlight><br />
<br />
== Modules listing ==<br />
=== Kernel 4.1 ???????????===<br />
<syntaxhighlight lang="bash"><br />
root@imx6-openrex:~# lsmod ????????????????<br />
Module Size Used by<br />
mxc_v4l2_capture 27624 2<br />
ipu_bg_overlay_sdc 5385 1 mxc_v4l2_capture<br />
ipu_still 2331 1 mxc_v4l2_capture<br />
ipu_prp_enc 5903 1 mxc_v4l2_capture<br />
ipu_csi_enc 3904 1 mxc_v4l2_capture<br />
ipu_fg_overlay_sdc 6130 1 mxc_v4l2_capture<br />
ov5647_camera_mipi_int 30566 0<br />
adv7610_video 6373 0<br />
v4l2_int_device 2872 4 ov5647_camera_mipi_int,adv7610_video,ipu_csi_enc,mxc_v4l2_capture<br />
mxc_dcic 6528 0<br />
<br />
<br />
<br />
root@imx8mq-voipac:~# lsmod<br />
Module Size Used by<br />
crct10dif_ce 16384 1<br />
mwifiex_pcie 45056 0<br />
mwifiex 294912 1 mwifiex_pcie<br />
galcore 610304 2<br />
<br />
</syntaxhighlight><br />
<br />
== Resolution setting ==<br />
The camera support video streaming formats 1080p (at 30 frames per second) and 720p (at 60 frames per second)<br />
=== 1280x960 ===<br />
<syntaxhighlight lang="bash"><br />
echo 0 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1280x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 1 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1920x1080 ===<br />
<syntaxhighlight lang="bash"><br />
echo 2 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 ===<br />
<syntaxhighlight lang="bash"><br />
echo 3 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1024x768 (default) ===<br />
<syntaxhighlight lang="bash"><br />
echo 4 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 960x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 5 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 (narrow angle of view) ===<br />
<syntaxhighlight lang="bash"><br />
echo 6 > /sys/bus/i2c/devices/1-0036/ov5647_mode <br />
</syntaxhighlight><br />
<br />
== Gstreamer ==<br />
=== Capture single JPEG picture ===<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# gst-launch-1.0 v4l2src num-buffers=1 ! jpegenc ! filesink location=sample_image.jp<br />
Setting pipeline to PAUSED ...<br />
Pipeline is live and does not need PREROLL ...<br />
Setting pipeline to PLAYING ...<br />
New clock: GstSystemClock<br />
ERROR: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Internal data stream error.<br />
Additional debug info:<br />
../git/libs/gst/base/gstbasesrc.c(3072): gst_base_src_loop (): /GstPipeline:pipeline0/GstV4l2Src:v4l2src0:<br />
streaming stopped, reason not-negotiated (-4)<br />
Execution ended after 0:00:00.000309960<br />
Setting pipeline to PAUSED ...<br />
Setting pipeline to READY ...<br />
Setting pipeline to NULL ...<br />
Freeing pipeline ...<br />
root@imx8mq-voipac:~# ls<br />
sample_image.jp<br />
</syntaxhighlight><br />
<br />
The image stored in local media with name sample_image.jpeg<br />
<br />
=== Video preview ===<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# GST_DEBUG=GST_BUFFER:5 gst-launch-1.0 v4l2src device=/dev/video1 ! 'video/x-raw,framerate=30/1' ! autovideosink<br />
Setting pipeline to PAUSED ...<br />
Pipeline is live and does not need PREROLL ...<br />
Setting pipeline to PLAYING ...<br />
New clock: GstSystemClock<br />
0:00:00.842776580 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc0623c0 (GstVideoMeta) of size 112<br />
0:00:00.842935198 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc062440 (GstVideoMeta) of size 112<br />
0:00:00.843278592 469 0xaaaadc001c00 DEB[ 1415.898001] ov5640_mipi 2-003c: s_stream: 1<br />
UG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc0624c0 (GstVideoMeta) of size 112<br />
0:00:00.843338584 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc062540 (GstVideoMeta) of size 112<br />
[ 1416.119964] skip frame 1<br />
</syntaxhighlight><br />
The video stream from camera can be displayed on display/monitor</div>
Voipac-hw
https://wiki.voipac.com/index.php?title=iMX8M_Industrial_Accessing_and_Testing_Peripherals&diff=3894
iMX8M Industrial Accessing and Testing Peripherals
2022-10-21T14:05:42Z
<p>Voipac-hw: /* CAN */</p>
<hr />
<div>[[Category:iMX8M Industrial]]<br />
[[Category:iMX8M Industrial Max]]<br />
[[Category:iMX8M Industrial Software]]<br />
[[Category:iMX8M Industrial Testing]]<br />
[[Category:iMX8M Industrial Peripherals]]<br />
<!-- --><br />
<div style="float:right">__TOC__</div><br />
<br />
Elemental operations of iMX8M Industrial Development Kit interfaces in Max configuration are shown on this page.<br />
<br />
== Prerequisites ==<br />
=== Hardware ===<br />
* DC power supply (5V, 8A, 40W)<br />
* iMX8M Industrial Development Kit Max<br />
<br />
=== Peripherals and Accessories ===<br />
* 1x FullHD monitor with Audio output<br />
* 1x MicroSD card<br />
* KOE LVDS capacitive display set<br />
* Newhaven LVDS capacitive display set<br />
* Digilent MIPI-CSI camera<br />
* NXP MIPI-CSI camera<br />
* CANBus module<br />
* Wifi and Bluetooth antenna set<br />
<br />
<br />
=== Cables ===<br />
* Ethernet cable<br />
* HDMI cable<br />
* Micro USB cable<br />
* USB to UART cable<br />
* Headphones<br />
<br />
== Audio ==<br />
'''''Input:''''' Search kernel log for wm8904 chip<br /><br />
'''''Output:''''' Audio chip is detected and bound as an input device<br />
<syntaxhighlight lang="bash"><br />
[ 1.864809] fsl-asoc-card sound-wm8904: failed to find codec device<br />
[ 2.155773] wm8904 0-001a: 0-001a supply DCVDD not found, using dummy regulator<br />
[ 2.163163] wm8904 0-001a: 0-001a supply DBVDD not found, using dummy regulator<br />
[ 2.170561] wm8904 0-001a: 0-001a supply AVDD not found, using dummy regulator<br />
[ 2.177846] wm8904 0-001a: 0-001a supply CPVDD not found, using dummy regulator<br />
[ 2.185209] wm8904 0-001a: 0-001a supply MICVDD not found, using dummy regulator<br />
[ 2.197860] wm8904 0-001a: revision A<br />
[ 2.699093] debugfs: Directory '308b0000.sai' with parent 'wm8904-audio' already present!<br />
[ 2.707395] fsl-asoc-card sound-wm8904: wm8904-hifi <-> 308b0000.sai mapping ok<br />
[ 2.714808] fsl-asoc-card sound-wm8904: ASoC: no DMI vendor name!<br />
[ 3.145901] #1: wm8904-audio<br />
</syntaxhighlight><br />
<br />
'''''Input:''''' Run amixer command<br /><br />
'''''Output:''''' Controls for card are available<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# amixer -c1<br />
Simple mixer control 'Headphone',0<br />
Capabilities: volume pswitch<br />
Playback channels: Front Left - Front Right<br />
Capture channels: Front Left - Front Right<br />
Limits: 0 - 63<br />
Front Left: 46 [73%] [-11.00dB] Playback [on]<br />
Front Right: 45 [71%] [-12.00dB] Playback [on]<br />
Simple mixer control 'Headphone ZC',0<br />
Capabilities: pswitch<br />
Playback channels: Front Left - Front Right<br />
Mono:<br />
Front Left: Playback [on]<br />
Front Right: Playback [on]<br />
Simple mixer control 'Line Output',0<br />
Capabilities: volume pswitch<br />
Playback channels: Front Left - Front Right<br />
Capture channels: Front Left - Front Right<br />
Limits: 0 - 63<br />
Front Left: 57 [90%] [0.00dB] Playback [on]<br />
Front Right: 57 [90%] [0.00dB] Playback [on]<br />
Simple mixer control 'Line Output ZC',0<br />
Capabilities: pswitch<br />
Playback channels: Front Left - Front Right<br />
Mono:<br />
Front Left: Playback [on]<br />
Front Right: Playback [on]<br />
...<br />
</syntaxhighlight><br />
<br />
'''''Input:''''' Boot-up the board with HDMI cable plugged in, connect headphones into HP_OUT connector and plug-in USB flash drive with wav file on it<br /><br />
'''''Output:''''' Sound is played and heard<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# aplay multimedia/sample.wav<br />
Playing WAVE 'multimedia/sample.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo<br />
</syntaxhighlight><br />
<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# #aplay -D sysdefault:CARD=wm8904audio multimedia/sample.wav <br />
root@imx8mq-voipac:~# aplay -D sysdefault:CARD=wm8904audio multimedia/sample.wav<br />
Playing WAVE 'multimedia/sample.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo<br />
</syntaxhighlight><br />
<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# aplay -D sysdefault:CARD=imxaudiohdmi multimedia/sample.wav <br />
Playing WAVE 'multimedia/sample.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo<br />
</syntaxhighlight><br />
<br />
'''''Input:''''' Plug headphones with microphone input into HP_OUT connector and microphone to MIC<br /><br />
'''''Output:''''' Microphone sound is played in headphones<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# #arecord -D sysdefault:CARD=wm8904audio -t wav -f cd | aplay -D sysdefault:CARD=wm8904audio<br />
root@imx8mq-voipac:~# arecord -D sysdefault:CARD=wm8904audio -t wav -f cd | aplay -D sysdefault:CARD=wm8904audio<br />
</syntaxhighlight><br />
<br />
'''''Input:''''' Verify Digital microphone <br /><br />
'''''Output:''''' Microphone sound is played in headphones<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# amixer -c1 sset "Capture Input" "DMIC"<br />
root@imx8mq-voipac:~# #arecord -D sysdefault:CARD=wm8904audio -t wav -f cd | aplay -D sysdefault:CARD=wm8904audio<br />
root@imx8mq-voipac:~# arecord -D sysdefault:CARD=wm8904audio -t wav -f cd | aplay -D sysdefault:CARD=wm8904audio<br />
</syntaxhighlight><br />
<br />
== User buttons ==<br />
'''''Input:''''' Press Enter/Left/Right/Up/Down buttons<br /><br />
'''''Output:''''' Button events 1 and 0 are generated<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# evtest /dev/input/by-path/platform-gpio-buttons-event <br />
Input driver version is 1.0.1<br />
Input device ID: bus 0x19 vendor 0x1 product 0x1 version 0x100<br />
Input device name: "gpio-buttons"<br />
Supported events:<br />
Event type 0 (EV_SYN)<br />
Event type 1 (EV_KEY)<br />
Event code 28 (KEY_ENTER)<br />
Event code 103 (KEY_UP)<br />
Event code 105 (KEY_LEFT)<br />
Event code 106 (KEY_RIGHT)<br />
Event code 108 (KEY_DOWN)<br />
Properties:<br />
Testing ... (interrupt to exit)<br />
</syntaxhighlight><br />
<br />
== Reset button ==<br />
'''''Input:''''' Press the RESET button<br /><br />
'''''Output:''''' The board will execute bootloader immediately with "Reset cause: POR"<br /><br />
'''''Note:''''' iMX8M Industrial Development Kit should never freeze or hang after the reset button was pressed. Testing the operation 10 times gives a reliable result<br />
<syntaxhighlight lang="bash"><br />
U-Boot 2020.04-imx_v2020.04_5.4.24_2.1.0+g4979a99482 (May 30 2020 - 06:50:01 +0000)<br />
<br />
CPU: i.MX8MQLite rev2.1 1300 MHz (running at 800 MHz)<br />
CPU: Industrial temperature grade (-40C to 105C) at 62C<br />
Reset cause: POR<br />
Model: Voipac i.MX8MQ EVK<br />
DRAM: 2 GiB<br />
MMC: FSL_SDHC: 0, FSL_SDHC: 1<br />
Loading Environment from MMC... OK<br />
[*]-Video Link 0imx8m_hdmi_probe<br />
....<br />
</syntaxhighlight><br />
<br />
== Power button ==<br />
'''''Input:''''' Press the POWER button<br /><br />
'''''Output:''''' The board will shutdown. By pressing again board should start booting."<br /><br />
<br />
<syntaxhighlight lang="bash"><br />
[ OK ] Stopped target Sound Card.<br />
[ OK ] Stopped target System Time Synchronized.<br />
[ OK ] Stopped target System Time Set.<br />
[ OK ] Stopped target Timers.<br />
[ OK ] Stopped Daily Cleanup of Temporary Directories.<br />
Stopping Save/Restore Sound Card State...<br />
Stopping Kernel Logging Service...<br />
Stopping System Logging Service...<br />
Stopping Getty on tty1...<br />
Stopping Serial Getty on ttymxc0...<br />
Stopping Hostname Service...<br />
Stopping Load/Save Random Seed...<br />
[ OK ] Stopped Kernel Logging Service.<br />
[ OK ] Stopped System Logging Service.<br />
[ OK ] Stopped Getty on tty1.<br />
[ OK ] Stopped Serial Getty on ttymxc0.<br />
[ OK ] Stopped Hostname Service.<br />
[ OK ] Stopped Save/Restore Sound Card State.<br />
[ OK ] Stopped Load/Save Random Seed.<br />
[ OK ] Stopped Session c1 of user root.<br />
[ OK ] Removed slice system-getty.slice.<br />
[ OK ] Removed slice system-serial\x2dgetty.slice.<br />
Stopping Login Service...<br />
Stopping User Manager for UID 0...<br />
[ OK ] Stopped User Manager for UID 0.<br />
Stopping User Runtime Directory /run/user/0...<br />
[ OK ] Unmounted /run/user/0.<br />
[ OK ] Stopped User Runtime Directory /run/user/0.<br />
[ OK ] Removed slice User Slice of UID 0.<br />
Stopping D-Bus System Message Bus...<br />
Stopping Permit User Sessions...<br />
[ OK ] Stopped D-Bus System Message Bus.<br />
[ OK ] Stopped Login Service.<br />
[ OK ] Stopped Permit User Sessions.<br />
[ OK ] Stopped target Basic System.<br />
[ OK ] Stopped target Network.<br />
[ OK ] Stopped target Paths. <br />
[ OK ] Stopped Dispatch Password ��…ts to Console Directory Watch. <br />
[ OK ] Stopped Forward Password R��…uests to Wall Directory Watch. <br />
[ OK ] Stopped target Remote File Systems. <br />
[ OK ] Stopped target Slices. <br />
[ OK ] Removed slice User and Session Slice.<br />
[ OK ] Stopped target Sockets.<br />
[ OK ] Closed D-Bus System Message Bus Socket.<br />
[ OK ] Closed dropbear.socket.<br />
[ OK ] Stopped target System Initialization.<br />
[ OK ] Closed Syslog Socket.<br />
Stopping Network Name Resolution...<br />
Stopping Network Time Synchronization...<br />
[ OK ] Stopped Network Name Resolution.<br />
[ OK ] Stopped Network Time Synchronization.<br />
Stopping Network Service...<br />
[ OK ] Stopped Create Volatile Files and Directories.<br />
[ OK ] Stopped target Local File Systems.<br />
Unmounting Temporary Directory (/tmp)...<br />
Unmounting /var/volatile...<br />
[ OK ] Stopped Network Service.<br />
[ OK ] Unmounted Temporary Directory (/tmp).<br />
[ OK ] Unmounted /var/volatile.<br />
[ OK ] Stopped target Local File Systems (Pre).<br />
[ OK ] Stopped target Swap.<br />
[ OK ] Reached target Unmount All Filesystems.<br />
[ OK ] Stopped Remount Root and Kernel File Systems.<br />
[ OK ] Stopped Apply Kernel Variables.<br />
[ OK ] Stopped Load Kernel Modules.<br />
[ OK ] Stopped Create Static Device Nodes in /dev.<br />
[ OK ] Reached target Shutdown.<br />
[ OK ] Reached target Final Step.<br />
[ OK ] Started Power-Off.<br />
[ OK ] Reached target Power-Off.<br />
[ 15.911216] systemd-shutdown[1]: Syncing filesystems and block devices.<br />
[ 15.920832] systemd-shutdown[1]: Sending SIGTERM to remaining processes...<br />
[ 15.936588] systemd-journald[247]: Received SIGTERM from PID 1 (systemd-shutdow).<br />
[ 15.959340] systemd-shutdown[1]: Sending SIGKILL to remaining processes...<br />
[ 15.975454] systemd-shutdown[1]: Unmounting file systems.<br />
[ 15.982656] [353]: Remounting '/' read-only in with options '(null)'.<br />
[ 16.020576] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)<br />
[ 16.031646] systemd-shutdown[1]: All filesystems unmounted.<br />
[ 16.037301] systemd-shutdown[1]: Deactivating swaps.<br />
[ 16.042421] systemd-shutdown[1]: All swaps deactivated.<br />
[ 16.047678] systemd-shutdown[1]: Detaching loop devices.<br />
[ 16.055830] systemd-shutdown[1]: All loop devices detached.<br />
[ 16.061424] systemd-shutdown[1]: Detaching DM devices.<br />
[ 16.066794] systemd-shutdown[1]: All DM devices detached.<br />
[ 16.072226] systemd-shutdown[1]: All filesystems, swaps, loop devices and DM devices detached.<br />
[ 16.086744] systemd-shutdown[1]: Syncing filesystems and block devices.<br />
[ 16.093483] systemd-shutdown[1]: Powering off.<br />
[ 16.097961] kvm: exiting hardware virtualization<br />
[ 16.097991] imx-sdma 30bd0000.sdma: external firmware not found, using ROM firmware<br />
[ 16.098546] cfg80211: failed to load regulatory.db<br />
[ 16.101341] imx-sdma 302c0000.sdma: loaded firmware 4.5<br />
[ 16.166426] mwifiex_pcie 0000:01:00.0: info: shutdown mwifiex...<br />
[ 16.173169] mwifiex_pcie 0000:01:00.0: PREP_CMD: card is removed<br />
[ 16.240963] mwifiex_pcie 0000:01:00.0: performing cancel_work_sync()...<br />
[ 16.247595] mwifiex_pcie 0000:01:00.0: cancel_work_sync() done<br />
[ 16.288309] reboot: Power down<br />
</syntaxhighlight><br />
<br />
Then pressing POWER button again:<br />
<br />
<syntaxhighlight lang="bash"><br />
U-Boot 2020.04-imx_v2020.04_5.4.24_2.1.0+g4979a99482 (May 30 2020 - 06:50:01 +0000)<br />
<br />
CPU: i.MX8MQLite rev2.1 1300 MHz (running at 800 MHz)<br />
CPU: Industrial temperature grade (-40C to 105C) at 62C<br />
Reset cause: POR<br />
Model: Voipac i.MX8MQ EVK<br />
DRAM: 2 GiB<br />
MMC: FSL_SDHC: 0, FSL_SDHC: 1<br />
Loading Environment from MMC... OK<br />
[*]-Video Link 0imx8m_hdmi_probe<br />
....<br />
</syntaxhighlight><br />
<br />
== CAN ==<br />
'''''Input:''''' None<br /><br />
'''''Output:''''' Device driver is available<br />
<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# ip addr show dev can0<br />
1: can0: <NOARP,ECHO> mtu 16 qdisc noop state DOWN group default qlen 10<br />
link/can <br />
</syntaxhighlight><br />
<br />
To setup can interface to 500kB bitrate use following command:<br />
<syntaxhighlight lang="bash"><br />
ip link set can0 up type can bitrate 500000<br />
</syntaxhighlight><br />
<br />
To test send data use following command:<br />
<syntaxhighlight lang="bash"><br />
cansend can0 365#AA.11.11<br />
</syntaxhighlight><br />
<br />
To test receiving data use following command:<br />
<syntaxhighlight lang="bash"><br />
candump can0<br />
</syntaxhighlight><br />
<br />
== Camera Input ==<br />
'''''Input:''''' Connect DIGILENT Pcam 5C camera module into CSI-2 interface and check if it is detected on I2C bus<br /><br />
'''''Output:''''' Camera is found<br /><br />
<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# dmesg | grep ov56<br />
[ 2.383324] ov5640_mipi 1-003c: No pin available<br />
[ 2.387976] ov5640_mipi 1-003c: No sensor pwdn pin available<br />
[ 2.393683] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 2.399479] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 3.018132] ov5640_mipi 1-003c: No pin available<br />
[ 3.033972] ov5640_mipi 1-003c: No sensor pwdn pin available<br />
[ 3.046488] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 3.062091] ov5640_mipi 1-003c: 1-003c supply DVDD not found, using dummy regulator<br />
[ 3.072436] ov5640_mipi 1-003c: 1-003c supply AVDD not found, using dummy regulator<br />
[ 4.325257] mxc-mipi-csi2_yav 30b60000.mipi_csi: Registered sensor subdevice: ov5640_mipi 1-003c<br />
[ 4.337288] ov5640_mipi 1-003c: Camera is found<br />
</syntaxhighlight><br />
<br />
<br />
'''''Input:''''' Connect DIGILENT Pcam 5C camera module into CSI-2 interface and capture image<br /><br />
'''''Output:''''' The image stored in local media with name sample_image.jpeg<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# gst-launch-1.0 v4l2src num-buffers=1 ! jpegenc ! filesink location=sample_image.jpeg<br />
Setting pipeline to PAUSED ...<br />
Pipeline is live and does not need PREROLL ...<br />
Setting pipeline to PLAYING ...<br />
New clock: GstSystemClock<br />
[ 59.069241] ov5640_mipi 1-003c: s_stream: 1<br />
[ 59.759767] skip frame 1<br />
Got EOS from element "pipeline0".[ 61.733964] ov5640_mipi 1-003c: s_stream: 0<br />
<br />
Execution ended after 0:00:03.186379448<br />
Setting pipeline to PAUSED ...<br />
Setting pipeline to READY ...<br />
Setting pipeline to NULL ...<br />
Freeing pipeline ...<br />
</syntaxhighlight><br />
<br />
'''''Input:''''' Connect DIGILENT Pcam 5C camera module into CSI-2 interface and capture video<br /><br />
'''''Output:''''' The image displayed on display/monitor<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# GST_DEBUG=GST_BUFFER:5 gst-launch-1.0 v4l2src ! 'video/x-raw,framerate=30/1' ! autovideosink<br />
Setting pipeline to PAUSED ...<br />
Pipeline is live and does not need PREROLL ...<br />
Setting pipeline to PLAYING ...<br />
New clock: GstSystemClock<br />
0:00:00.787577440 510 0xaaab09d54800 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadat<br />
a 0xaaab09db63c0 (GstVideoMeta) of size 112<br />
0:00:00.787728994 510 0xaaab09d54800 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadat<br />
a 0xaaab09db6440 (GstVideoMeta) of size 112<br />
0:00:00.787782512 510 0xaaab09d54800 4116.266441] ov5640_mipi 1-003c: s_stream: 1<br />
mDEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaab09db64c0 (GstVideoMeta) of siz<br />
e 112<br />
0:00:00.787833750 510 0xaaab09d54800 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadat<br />
a 0xaaab09db6540 (GstVideoMeta) of size 112<br />
[ 4116.843975] skip frame 1<br />
<br />
</syntaxhighlight><br />
<br />
Video should be displayed on video output (hdmi or lvds display)<br />
<br />
== Ethernet ==<br />
'''''Input:''''' None<br /><br />
'''''Output:''''' Device driver is available<br /><br />
'''''Note:''''' MAC address should be identical with the address on the sticker placed on the board<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# ip addr show dev eth0<br />
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000<br />
link/ether 00:0d:15:01:50:92 brd ff:ff:ff:ff:ff:ff<br />
inet 192.168.10.122/24 brd 192.168.10.255 scope global dynamic eth0<br />
valid_lft 86103sec preferred_lft 86103sec<br />
inet6 fe80::20d:15ff:fe01:5092/64 scope link <br />
valid_lft forever preferred_lft forever<br />
</syntaxhighlight><br />
<br />
'''''Input:''''' Plug Ethernet cable into connector<br /><br />
'''''Output:''''' IPv4 address is assigned<br />
<syntaxhighlight lang="bash"><br />
[ 348.300585] fec 30be0000.ethernet eth0: Link is Down<br />
[ 350.350853] fec 30be0000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off<br />
</syntaxhighlight><br />
<br />
== HDMI Output ==<br />
'''''Input:''''' Connect LCD monitor to the SBC<br /><br />
'''''Output:''''' Desktop UI is displayed correctly<br /><br />
[[image:iMX6_TinyRex_Development_Kit-HDMI_terminal.png|580px]]<br />
<br />
== User LED ==<br />
'''''Input:''''' None<br /><br />
'''''Output:''''' Script switches User LED on baseboard ON and OFF in one second intervals<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~#<br />
for LED in /sys/class/leds/user<br />
do<br />
echo Testing ${LED}<br />
echo -n "1" > ${LED}/brightness<br />
sleep 1<br />
echo -n "0" > ${LED}/brightness<br />
sleep 1<br />
done<br />
</syntaxhighlight><br />
<br />
'''''Input:''''' None<br /><br />
'''''Output:''''' User LED on baseboard is set to heartbeat blinking sequence<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# echo heartbeat > /sys/class/leds/user/trigger<br />
</syntaxhighlight><br />
<br />
'''''Input:''''' None<br /><br />
'''''Output:''''' User LED on SOM is set to heartbeat blinking sequence<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# echo heartbeat > /sys/class/leds/user-som/trigger<br />
</syntaxhighlight><br />
<br />
== Wifi ==<br />
'''''Input:''''' None<br /><br />
'''''Output:''''' Device driver is available<br /><br />
<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# dmesg | grep mwifiex<br />
[ 5.145232] mwifiex_pcie 0000:01:00.0: enabling device (0000 -> 0002)<br />
[ 5.166217] mwifiex_pcie: PCI memory map Virt0: (____ptrval____) PCI memory map Virt2: (____ptrval____)<br />
[ 6.133666] mwifiex_pcie 0000:01:00.0: info: FW download over, size 632240 bytes<br />
[ 7.004061] mwifiex_pcie 0000:01:00.0: WLAN FW is active<br />
[ 7.049670] mwifiex_pcie 0000:01:00.0: Unknown api_id: 3<br />
[ 7.055024] mwifiex_pcie 0000:01:00.0: Unknown api_id: 4<br />
[ 7.060385] mwifiex_pcie 0000:01:00.0: Unknown GET_HW_SPEC TLV type: 0x217<br />
[ 7.075700] mwifiex_pcie 0000:01:00.0: info: MWIFIEX VERSION: mwifiex 1.0 (16.68.1.p179) <br />
[ 7.080505] mwifiex_pcie 0000:01:00.0 wlp1s0: renamed from mlan0<br />
[ 7.083959] mwifiex_pcie 0000:01:00.0: driver_version = mwifiex 1.0 (16.68.1.p179) <br />
</syntaxhighlight><br />
<br />
Chek if interface is present<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# ip addr show dev wlp1s0<br />
3: wlp1s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000<br />
link/ether 78:c4:0e:a0:32:16 brd ff:ff:ff:ff:ff:ff<br />
</syntaxhighlight><br />
<br />
=== Check connection ===<br />
* edit in /etc/wpa_supplicant.conf ssid and passphrase fields<br />
<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# cat /etc/wpa_supplicant.conf <br />
ctrl_interface=/var/run/wpa_supplicant<br />
ctrl_interface_group=0<br />
update_config=1<br />
<br />
network={<br />
ssid="AAA"<br />
scan_ssid=1<br />
key_mgmt=WPA-PSK<br />
psk="BBB"<br />
}<br />
<br />
</syntaxhighlight><br />
<br />
* start wpa_supplicant<br />
<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# wpa_supplicant -i wlp1s0 -c/etc/wpa_supplicant.conf &<br />
root@imx8mq-voipac:~# Successfully initialized wpa_supplicant<br />
rfkill: Cannot open RFKILL control device<br />
wlp1s0: Trying to associate with 40:a5:ef:c0:70:62 (SSID='CPE_C0[ 188.254851] mwifiex_pcie 0000:01:00.0: info: trying <br />
to associate to 'CPE_C07061' bssid 40:a5:ef:c0:70:62<br />
7061' freq=2462 MHz)<br />
[ 188.334475] mwifiex_pcie 0000:01:00.0: info: associated to bssid 40:a5:ef:c0:70:62 successfully<br />
wlp1s0: Associated with 40:a5:ef:c0:70:62<br />
wlp1s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0<br />
[ 188.351598] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready<br />
wlp1s0: WPA: Key negotiation completed with 40:a5:ef:c0:70:62 [PTK=CCMP GTK=CCMP]<br />
wlp1s0: CTRL-EVENT-CONNECTED - Connection to 40:a5:ef:c0:70:62 completed [id=0 id_str=]<br />
</syntaxhighlight><br />
<br />
* run udhcpc <br />
<syntaxhighlight lang="bash"><br />
udhcpc -i wlp1s0<br />
</syntaxhighlight><br />
<br />
== Bluetooth ==<br />
'''''Input:''''' None<br /><br />
'''''Output:''''' Remote device is recognized after scan<br /><br />
<br />
<syntaxhighlight lang="bash"><br />
# attach module<br />
root@imx8mq-voipac:~# hciattach /dev/ttymxc2 any 115200 flow <br />
[ 63.137693] Bluetooth: HCI UART driver ver 2.3 <br />
[ 63.142196] Bluetooth: HCI UART protocol H4 registered <br />
[ 63.147407] Bluetooth: HCI UART protocol BCSP registered <br />
[ 63.153061] Bluetooth: HCI UART protocol LL registered <br />
[ 63.158263] Bluetooth: HCI UART protocol ATH3K registered <br />
[ 63.163719] Bluetooth: HCI UART protocol Three-wire (H5) registered <br />
[ 63.170309] Bluetooth: HCI UART protocol Broadcom registered <br />
[ 63.176113] Bluetooth: HCI UART protocol QCA registered <br />
Device setup complete <br />
<br />
# put hci0 device up<br />
root@imx8mq-voipac:~# hciconfig hci0 up<br />
<br />
# scan for remote bluetooth devices (enable bluetooth on phone and make it discoverable)<br />
root@imx8mq-voipac:~# hcitool scan <br />
Scanning ... <br />
Devices:<br />
hci0 00:0D:18:01:5A:B3<br />
</syntaxhighlight><br />
<br />
== SATA ==<br />
'''''Input:''''' Plug sata disk to M2 extension board and power on<br /><br />
'''''Output:''''' Sata device is recognized<br /><br />
<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# ls -la /dev/sda<br />
brw-rw---- 1 root disk 8, 0 Feb 22 07:13 /dev/sda<br />
# run speed test - write<br />
root@imx8mq-voipac:~# time dd if=/dev/urandom of=/dev/sdb bs=4096 status=progress count=200000<br />
812093440 bytes (812 MB, 774 MiB) copied, 29 s, 28.0 MB/s<br />
200000+0 records in<br />
200000+0 records out<br />
819200000 bytes (819 MB, 781 MiB) copied, 34.1491 s, 24.0 MB/s<br />
real 0m 34.15s<br />
user 0m 0.30s<br />
sys 0m 12.74s<br />
<br />
# run speed test - read<br />
root@imx8mq-voipac:~# time dd if=/dev/sdb of=/tmp/test.bin bs=4096 status=progress count=100000<br />
364503040 bytes (365 MB, 348 MiB) copied, 4 s, 91.1 MB/s<br />
100000+0 records in<br />
100000+0 records out<br />
409600000 bytes (410 MB, 391 MiB) copied, 4.5828 s, 89.4 MB/s<br />
real 0m 4.79s<br />
user 0m 0.06s<br />
sys 0m 2.15s<br />
</syntaxhighlight><br />
<br />
We achieved aw write speed ~ 24MB/s and read speed ~90MB/s</div>
Voipac-hw
https://wiki.voipac.com/index.php?title=CANbus_Module&diff=3893
CANbus Module
2022-08-03T12:54:46Z
<p>Voipac-hw: </p>
<hr />
<div>[[Category:iMX8M Industrial Development Kit]]<br />
[[Category:iMX8M Industrial Peripherals]]<br />
<!-- --><br />
<div style="float:right">__TOC__</div><br />
<br />
On this page PCIe card functionality is shown. Both Bluetooth and WiFi operations are tested using dual band Intel AC 3160 wireless card. Mini PCI Express slot must provide PCIe and USB signals to support all the features.<br />
<br />
'''''Input:''''' None<br /><br />
'''''Output:''''' Device driver is available<br />
<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# ip addr show dev can0<br />
3: can0: <NOARP,UP,LOWER_UP,ECHO> mtu 16 qdisc pfifo_fast state UP group default qlen 10<br />
link/can<br />
root@imx8mq-voipac:~# ip link set can0 type can bitrate 500000<br />
root@imx8mq-voipac:~# ip link set can0 up<br />
root@imx8mq-voipac:~# cansend can0 01a#01020304<br />
interface = can0, family = 29, ty[ 434.135862] NOHZ: local_softirq_pending 08<br />
pe = 3, proto = 1<br />
root@imx8mq-voipac:~#<br />
to receive <br />
root@imx8mq-voipac:~# candump can0<br />
</syntaxhighlight><br/><br />
<br />
'''''Input:''''' Connect a pair of iMX6 TinyRex Development boards and a couple of dedicated [https://www.ti.com/tool/TCAN332EVM CAN evaluation modules]<br /><br />
'''''Output:''''' Boards communicate between each other. Sent messages are received successfully<br /><br /><br />
<br />
Board 1 (receiver) commands and outputs:<br />
<syntaxhighlight lang="bash"><br />
root@imx6-tinyrexpro:~# ip link set can0 type can bitrate 1000000<br />
root@imx6-tinyrexpro:~# ip link set can0 up<br />
flexcan 2090000.flexcan can0: writing ctrl=0x01232054<br />
root@imx6-tinyrexpro:~# candump can0 &<br />
[1] 833<br />
root@imx6-tinyrexpro:~# can0 123 [4] DE AD BE EF<br />
</syntaxhighlight><br />
<br />
Board 2 (transmitter and receiver) commands and outputs:<br />
<syntaxhighlight lang="bash"><br />
root@imx6-tinyrexpro:~# ip link set can0 type can bitrate 1000000<br />
root@imx6-tinyrexpro:~# ip link set can0 up<br />
flexcan 2090000.flexcan can0: writing ctrl=0x01232054<br />
root@imx6-tinyrexpro:~# candump can0 &<br />
[1] 847<br />
root@imx6-tinyrexpro:~# cansend can0 123#DEADBEEF<br />
root@imx6-tinyrexpro:~# can0 123 [4] DE AD BE EF<br />
</syntaxhighlight></div>
Voipac-hw
https://wiki.voipac.com/index.php?title=NXP_MIPI-CSI_Camera_Set&diff=3892
NXP MIPI-CSI Camera Set
2022-08-03T11:31:14Z
<p>Voipac-hw: /* Video preview */</p>
<hr />
<div>[[Category:iMX8M Industrial Development Kit]]<br />
[[Category:iMX8M Industrial Peripherals]]<br />
<!-- --><br />
<div style="float:right">__TOC__</div><br />
<br />
MINISASTOCSI is a MIPI-CSI interface camera kit, based on OmniVision chipset OV5640 Detection, performance and essential commands are described here.<br />
<br /><br /><br />
[[image:hot-plug.png|400px]]<br />
<br /><br /><br />
[[image:MINISASTOCSI-Voipac-BB.png|800px]]<br /><br />
MINISASTOCSI is a MIPI-CSI interface camera connected to iMX8M Development Baseboard <br />
<br /><br />
<br />
== Kernel detection ==<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# dmesg | grep ov56<br />
[ 2.398433] ov5640_mipi 1-003c: No pin available<br />
[ 2.403090] ov5640_mipi 1-003c: No sensor pwdn pin available<br />
[ 2.408777] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 2.414571] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.539603] ov5640_mipi 2-003c: No pin available<br />
[ 2.549079] ov5640_mipi 2-003c: No sensor reset pin available<br />
[ 2.554887] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.999855] ov5640_mipi 1-003c: No pin available<br />
[ 3.005558] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 3.012003] ov5640_mipi 1-003c: 1-003c supply DVDD not found, using dummy regulator<br />
[ 3.019785] ov5640_mipi 1-003c: 1-003c supply AVDD not found, using dummy regulator<br />
[ 3.039290] ov5640_mipi 1-003c: Read reg error: reg=300a<br />
[ 3.044691] ov5640_mipi 1-003c: Camera is not found<br />
[ 3.051918] ov5640_mipi 2-003c: No pin available<br />
[ 3.062814] ov5640_mipi 2-003c: No sensor reset pin available<br />
[ 3.069209] ov5640_mipi 2-003c: 2-003c supply DVDD not found, using dummy regulator<br />
[ 3.076945] ov5640_mipi 2-003c: 2-003c supply AVDD not found, using dummy regulator<br />
[ 4.291092] mxc-mipi-csi2_yav 30a70000.mipi_csi: Registered sensor subdevice: ov5640_mipi 2-003c<br />
[ 4.304334] ov5640_mipi 2-003c: Camera is found<br />
</syntaxhighlight><br />
<br />
== I2C detection ==<br />
MINISASTOCSI camera chip is connected via I2C3. The most important address for correct detection is 0x3c.<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# i2cdetect -y 2<br />
0 1 2 3 4 5 6 7 8 9 a b c d e f<br />
00: -- -- -- -- -- -- -- -- -- -- -- -- --<br />
10: UU UU UU UU -- -- -- -- -- -- -- -- -- -- -- --<br />
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
30: -- -- -- -- -- -- -- -- -- -- -- -- UU -- -- --<br />
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
70: -- -- -- -- -- -- -- --<br />
</syntaxhighlight><br />
<br /><br />
MINISASTOCSI camera can be also connected to I2C2 interface by moving 0R resistors. However second camera connected on CSI-2 interface have same address 0x3c as MINISASTOCSI camera connected on CSI-1 interface. <br /><br />
[[image:CSI1-I2C2 and I2C3.png|800px]]<br /><br />
<br />
== Modules listing ==<br />
=== Kernel 4.1 ===<br />
<syntaxhighlight lang="bash"><br />
root@imx6-openrex:~# lsmod<br />
Module Size Used by<br />
mxc_v4l2_capture 27624 2<br />
ipu_bg_overlay_sdc 5385 1 mxc_v4l2_capture<br />
ipu_still 2331 1 mxc_v4l2_capture<br />
ipu_prp_enc 5903 1 mxc_v4l2_capture<br />
ipu_csi_enc 3904 1 mxc_v4l2_capture<br />
ipu_fg_overlay_sdc 6130 1 mxc_v4l2_capture<br />
ov5647_camera_mipi_int 30566 0<br />
adv7610_video 6373 0<br />
v4l2_int_device 2872 4 ov5647_camera_mipi_int,adv7610_video,ipu_csi_enc,mxc_v4l2_capture<br />
mxc_dcic 6528 0<br />
<br />
<br />
<br />
root@imx8mq-voipac:~# lsmod<br />
Module Size Used by<br />
crct10dif_ce 16384 1<br />
mwifiex_pcie 45056 0<br />
mwifiex 294912 1 mwifiex_pcie<br />
galcore 610304 2<br />
<br />
</syntaxhighlight><br />
<br />
== Resolution setting ==<br />
=== 1280x960 ===<br />
<syntaxhighlight lang="bash"><br />
echo 0 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1280x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 1 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1920x1080 ===<br />
<syntaxhighlight lang="bash"><br />
echo 2 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 ===<br />
<syntaxhighlight lang="bash"><br />
echo 3 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1024x768 (default) ===<br />
<syntaxhighlight lang="bash"><br />
echo 4 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 960x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 5 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 (narrow angle of view) ===<br />
<syntaxhighlight lang="bash"><br />
echo 6 > /sys/bus/i2c/devices/1-0036/ov5647_mode <br />
</syntaxhighlight><br />
<br />
== Gstreamer ==<br />
=== Capture single JPEG picture ===<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# gst-launch-1.0 v4l2src num-buffers=1 ! jpegenc ! filesink location=sample_image.jpeg<br />
Setting pipeline to PAUSED ...<br />
Pipeline is live and does not need PREROLL ...<br />
Setting pipeline to PLAYING ...<br />
New clock: GstSystemClock<br />
[ 1301.273334] ov5640_mipi 2-003c: s_stream: 1<br />
Got EOS from element "pipeline0".[ 1303.353181] ov5640_mipi 2-003c: s_stream: 0<br />
<br />
Execution ended after 0:00:02.649996154<br />
Setting pipeline to PAUSED ...<br />
Setting pipeline to READY ...<br />
Setting pipeline to NULL ...<br />
Freeing pipeline ...<br />
root@imx8mq-voipac:~# ls<br />
sample_image.jpeg<br />
root@imx8mq-voipac:~#<br />
</syntaxhighlight><br />
<br />
The image stored in local media with name sample_image.jpeg<br />
<br />
=== Video preview ===<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# GST_DEBUG=GST_BUFFER:5 gst-launch-1.0 v4l2src ! 'video/x-raw,framerate=30/1' ! autovideosink<br />
Setting pipeline to PAUSED ...<br />
Pipeline is live and does not need PREROLL ...<br />
Setting pipeline to PLAYING ...<br />
New clock: GstSystemClock<br />
0:00:00.842776580 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc0623c0 (GstVideoMeta) of size 112<br />
0:00:00.842935198 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc062440 (GstVideoMeta) of size 112<br />
0:00:00.843278592 469 0xaaaadc001c00 DEB[ 1415.898001] ov5640_mipi 2-003c: s_stream: 1<br />
UG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc0624c0 (GstVideoMeta) of size 112<br />
0:00:00.843338584 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc062540 (GstVideoMeta) of size 112<br />
[ 1416.119964] skip frame 1<br />
</syntaxhighlight><br />
The video stream from camera can be displayed on display/monitor</div>
Voipac-hw
https://wiki.voipac.com/index.php?title=NXP_MIPI-CSI_Camera_Set&diff=3891
NXP MIPI-CSI Camera Set
2022-08-03T08:08:43Z
<p>Voipac-hw: /* Capture single JPEG picture */</p>
<hr />
<div>[[Category:iMX8M Industrial Development Kit]]<br />
[[Category:iMX8M Industrial Peripherals]]<br />
<!-- --><br />
<div style="float:right">__TOC__</div><br />
<br />
MINISASTOCSI is a MIPI-CSI interface camera kit, based on OmniVision chipset OV5640 Detection, performance and essential commands are described here.<br />
<br /><br /><br />
[[image:hot-plug.png|400px]]<br />
<br /><br /><br />
[[image:MINISASTOCSI-Voipac-BB.png|800px]]<br /><br />
MINISASTOCSI is a MIPI-CSI interface camera connected to iMX8M Development Baseboard <br />
<br /><br />
<br />
== Kernel detection ==<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# dmesg | grep ov56<br />
[ 2.398433] ov5640_mipi 1-003c: No pin available<br />
[ 2.403090] ov5640_mipi 1-003c: No sensor pwdn pin available<br />
[ 2.408777] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 2.414571] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.539603] ov5640_mipi 2-003c: No pin available<br />
[ 2.549079] ov5640_mipi 2-003c: No sensor reset pin available<br />
[ 2.554887] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.999855] ov5640_mipi 1-003c: No pin available<br />
[ 3.005558] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 3.012003] ov5640_mipi 1-003c: 1-003c supply DVDD not found, using dummy regulator<br />
[ 3.019785] ov5640_mipi 1-003c: 1-003c supply AVDD not found, using dummy regulator<br />
[ 3.039290] ov5640_mipi 1-003c: Read reg error: reg=300a<br />
[ 3.044691] ov5640_mipi 1-003c: Camera is not found<br />
[ 3.051918] ov5640_mipi 2-003c: No pin available<br />
[ 3.062814] ov5640_mipi 2-003c: No sensor reset pin available<br />
[ 3.069209] ov5640_mipi 2-003c: 2-003c supply DVDD not found, using dummy regulator<br />
[ 3.076945] ov5640_mipi 2-003c: 2-003c supply AVDD not found, using dummy regulator<br />
[ 4.291092] mxc-mipi-csi2_yav 30a70000.mipi_csi: Registered sensor subdevice: ov5640_mipi 2-003c<br />
[ 4.304334] ov5640_mipi 2-003c: Camera is found<br />
</syntaxhighlight><br />
<br />
== I2C detection ==<br />
MINISASTOCSI camera chip is connected via I2C3. The most important address for correct detection is 0x3c.<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# i2cdetect -y 2<br />
0 1 2 3 4 5 6 7 8 9 a b c d e f<br />
00: -- -- -- -- -- -- -- -- -- -- -- -- --<br />
10: UU UU UU UU -- -- -- -- -- -- -- -- -- -- -- --<br />
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
30: -- -- -- -- -- -- -- -- -- -- -- -- UU -- -- --<br />
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
70: -- -- -- -- -- -- -- --<br />
</syntaxhighlight><br />
<br /><br />
MINISASTOCSI camera can be also connected to I2C2 interface by moving 0R resistors. However second camera connected on CSI-2 interface have same address 0x3c as MINISASTOCSI camera connected on CSI-1 interface. <br /><br />
[[image:CSI1-I2C2 and I2C3.png|800px]]<br /><br />
<br />
== Modules listing ==<br />
=== Kernel 4.1 ===<br />
<syntaxhighlight lang="bash"><br />
root@imx6-openrex:~# lsmod<br />
Module Size Used by<br />
mxc_v4l2_capture 27624 2<br />
ipu_bg_overlay_sdc 5385 1 mxc_v4l2_capture<br />
ipu_still 2331 1 mxc_v4l2_capture<br />
ipu_prp_enc 5903 1 mxc_v4l2_capture<br />
ipu_csi_enc 3904 1 mxc_v4l2_capture<br />
ipu_fg_overlay_sdc 6130 1 mxc_v4l2_capture<br />
ov5647_camera_mipi_int 30566 0<br />
adv7610_video 6373 0<br />
v4l2_int_device 2872 4 ov5647_camera_mipi_int,adv7610_video,ipu_csi_enc,mxc_v4l2_capture<br />
mxc_dcic 6528 0<br />
<br />
<br />
<br />
root@imx8mq-voipac:~# lsmod<br />
Module Size Used by<br />
crct10dif_ce 16384 1<br />
mwifiex_pcie 45056 0<br />
mwifiex 294912 1 mwifiex_pcie<br />
galcore 610304 2<br />
<br />
</syntaxhighlight><br />
<br />
== Resolution setting ==<br />
=== 1280x960 ===<br />
<syntaxhighlight lang="bash"><br />
echo 0 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1280x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 1 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1920x1080 ===<br />
<syntaxhighlight lang="bash"><br />
echo 2 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 ===<br />
<syntaxhighlight lang="bash"><br />
echo 3 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1024x768 (default) ===<br />
<syntaxhighlight lang="bash"><br />
echo 4 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 960x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 5 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 (narrow angle of view) ===<br />
<syntaxhighlight lang="bash"><br />
echo 6 > /sys/bus/i2c/devices/1-0036/ov5647_mode <br />
</syntaxhighlight><br />
<br />
== Gstreamer ==<br />
=== Capture single JPEG picture ===<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# gst-launch-1.0 v4l2src num-buffers=1 ! jpegenc ! filesink location=sample_image.jpeg<br />
Setting pipeline to PAUSED ...<br />
Pipeline is live and does not need PREROLL ...<br />
Setting pipeline to PLAYING ...<br />
New clock: GstSystemClock<br />
[ 1301.273334] ov5640_mipi 2-003c: s_stream: 1<br />
Got EOS from element "pipeline0".[ 1303.353181] ov5640_mipi 2-003c: s_stream: 0<br />
<br />
Execution ended after 0:00:02.649996154<br />
Setting pipeline to PAUSED ...<br />
Setting pipeline to READY ...<br />
Setting pipeline to NULL ...<br />
Freeing pipeline ...<br />
root@imx8mq-voipac:~# ls<br />
sample_image.jpeg<br />
root@imx8mq-voipac:~#<br />
</syntaxhighlight><br />
<br />
The image stored in local media with name sample_image.jpeg<br />
<br />
=== Video preview ===<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# GST_DEBUG=GST_BUFFER:5 gst-launch-1.0 v4l2src ! 'video/x-raw,framerate=30/1' ! aut<br />
ovideosink<br />
Setting pipeline to PAUSED ...<br />
Pipeline is live and does not need PREROLL ...<br />
Setting pipeline to PLAYING ...<br />
New clock: GstSystemClock<br />
0:00:00.842776580 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc0623c0 (GstVideoMeta) of size 112<br />
0:00:00.842935198 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc062440 (GstVideoMeta) of size 112<br />
0:00:00.843278592 469 0xaaaadc001c00 DEB[ 1415.898001] ov5640_mipi 2-003c: s_stream: 1<br />
UG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc0624c0 (GstVideoMeta) of size 112<br />
0:00:00.843338584 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc062540 (GstVideoMeta) of size 112<br />
[ 1416.119964] skip frame 1<br />
</syntaxhighlight><br />
The video stream from camera can be displayed on display/monitor</div>
Voipac-hw
https://wiki.voipac.com/index.php?title=File:LVDS0_NH_jumpers.png&diff=3890
File:LVDS0 NH jumpers.png
2022-07-26T16:18:50Z
<p>Voipac-hw: Voipac-hw uploaded a new version of File:LVDS0 NH jumpers.png</p>
<hr />
<div>LVDS0 NH jumpers</div>
Voipac-hw
https://wiki.voipac.com/index.php?title=File:LVDS0_KOE_jumpers.png&diff=3889
File:LVDS0 KOE jumpers.png
2022-07-26T16:13:12Z
<p>Voipac-hw: </p>
<hr />
<div>LVDS0 KOE jumpers</div>
Voipac-hw
https://wiki.voipac.com/index.php?title=KOE_LVDS_Capacitive_Display_Set&diff=3888
KOE LVDS Capacitive Display Set
2022-07-26T16:09:20Z
<p>Voipac-hw: /* Hardware jumpers Newhaven LVDS */</p>
<hr />
<div>[[Category:iMX8M Industial Development Kit]]<br />
[[Category:iMX8M Industial Peripherals]]<br />
<!-- --><br />
<div style="float:right">__TOC__</div><br />
<br />
This section shows information about the KOE LVDS Capacitive Display Set. The iMX8M Industrial Development Kit in this configuration is equipped with Yocto dunfell, kernel 5.4 to support LVDS display with a touchscreen layer. In this case the display is installed on the top of the iMX8M Development Baseboard.<br /><br />
[[image:iMX8M Industrial Dev Kit KOE LCD.jpg|800px]]<br />
<br />
== Mechanical connection ==<br />
When combined with the complete iMX8M Industrial Kit, the Display Set creates a compact, ready-to-use solution. To assemble them together, the following mechanical and electrical accessories were designed and selected to be part of the Display set: <br />
* TFT LCD 1920 x 1080 Pixels display (TX18D200VM0EAA) with LVDS interface and Capacitive Touch with SIS9509 controller<br />
* 4x Hex Standoff Threaded M3 35.00mm long [Manufacturer PN: 971350321]<br />
* custom 20-pins LVDS cable, 180mm long. The cable is supply with LCD as set<br />
* custom 2-pins cable for LCD back light, 150mm long. The cable is supply with LCD as set<br />
* necessary spacers<br />
[[image:iMX8M Industrial Dev Kit KOE LCD Side view.jpg|800px]]<br />
<br />
== Hardware connection ==<br />
<br />
To enable smooth communication between the board and the display, connect the 20 Position LVDS cable for LCD and 6 pin touchscreen FFC cable. To implement the display capabilities, following connections need to be made:<br />
* connection between LVDS Display and iMX8M Development Baseboard connector LVDS0 KOE (J14) using a 20 Position LVDS cable<br />
* 2 position back light cable connect to connector J15<br />
* touchscreen connection between iMX8M Development Baseboard connector KOE Touch (J40) and Touchscreen 6 pin FFC cable<br />
<br />
=== LVDS and Touchscreen cable ===<br />
[[image:imx8m LVDS with touchscreen cable for KOE.jpg|800px]]<br />
<br />
=== Hardware jumpers KOE LVDS ===<br />
Make sure that configurable 0R resistor are moved to KOE LVDS0 interface <br /><br />
[[image:LVDS0 KOE jumpers.png|800px]]<br /><br />
<br />
== Software instructions ==<br />
iMX8M Industrial kit is preinstalled with Yocto dunfell operation system enabling LVDS and touchscreen capabilities by default. Manual configuration is necessary, Devicetree in U-Boot have to by set to KOE LVDS0 LCD. <br />
=== LVDS0 KOE Devicetree in U-Boot ===<br />
Manually booting with LVDS interface as a primary source for video output:<br />
<syntaxhighlight lang="bash"><br />
Fastboot: Normal<br />
Normal Boot<br />
Hit any key to stop autoboot: 0<br />
u-boot=><br />
u-boot=><br />
u-boot=><br />
u-boot=><br />
u-boot=><br />
u-boot=> fatls mmc 0:1<br />
27787776 Image<br />
48586 imx8mq-evk-voipac-dp.dtb<br />
48793 imx8mq-evk-voipac-hdmi.dtb<br />
49194 imx8mq-evk-voipac-lvds-koe.dtb<br />
49198 imx8mq-evk-voipac-lvds-newhaven.dtb<br />
<br />
5 file(s), 0 dir(s)<br />
<br />
u-boot=> setenv fdt_file imx8mq-evk-voipac-lvds-koe.dtb<br />
u-boot=> saveenv<br />
Saving Environment to MMC... Writing to MMC(0)... OK<br />
u-boot=><br />
u-boot=> boot<br />
</syntaxhighlight><br />
<br />
=== Touchscreen test ===<br />
Default Voipac iMX8M Image contain evtest utility to catch touchscreen events. Make sure SiS9509 controller is detected and bound as input device: <br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# dmesg | grep -i SiS9509 <br />
input: ----------<br />
evbug: ----------<br />
</syntaxhighlight><br />
<br />
ouchscreen events are generated after touching capacitive touch screen. <br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# evtest /dev/input/by-path/platform-21a4000.i2c-event <br />
-<br />
-<br />
--<br />
---<br />
---<br />
--<br />
-<br />
-<br />
</syntaxhighlight></div>
Voipac-hw
https://wiki.voipac.com/index.php?title=Newhaven_LVDS_Capacitive_Display_Set&diff=3887
Newhaven LVDS Capacitive Display Set
2022-07-26T16:06:02Z
<p>Voipac-hw: /* Touchscreen test */</p>
<hr />
<div>[[Category:iMX8M Industial Development Kit]]<br />
[[Category:iMX8M Industial Peripherals]]<br />
<!-- --><br />
<div style="float:right">__TOC__</div><br />
<br />
This section shows information about the Newhaven LVDS Capacitive Display Set. The iMX8M Industrial Development Kit in this configuration is equipped with Yocto dunfell, kernel 5.4 to support LVDS display with a touchscreen layer. In this case the display is installed on the top of the iMX8M Development Baseboard.<br /><br />
[[image:Voipac NHD LCD Assembly.png|800px]]<br />
<br />
== Mechanical connection ==<br />
When combined with the complete iMX8M Industrial Kit, the Display Set creates a compact, ready-to-use solution. To assemble them together, the following mechanical and electrical accessories were designed and selected to be part of the Display set:<br />
* TFT LCD 1024x600 Pixels display with LVDS interface and Capacitive Touch with SiS9509 controller <br />
* 4x Hex Standoff Threaded M3 30.00mm long [Manufacturer PN: 971300321]<br />
* 40 Position flat flex cable 50.80mm long [Manufacturer PN: 0150200427]<br />
* 6 pin touchscreen flat flex cable<br />
* necessary spacers<br />
[[image:Voipac NHD LCD Fastener.png|800px]]<br />
<br />
== Hardware connection ==<br />
To enable smooth communication between the board and the display, connect the 40 Position FFC cable for LCD and 6 pin touchscreen FFC cable. To implement the display capabilities, following connections need to be made:<br />
* connection between LVDS Display and iMX8M Development Baseboard connector LVDS0 NHD (J12) using a 40 Position FFC cable<br />
* touchscreen connection between iMX8M Development Baseboard connector NHD Touch (J13) and Touchscreen 6 pin FFC cable<br />
=== LVDS and Touchscreen cable ===<br />
[[image:imx8m_LVDS_with_touchscreen_cable_for_NHD.jpg|800px]]<br />
=== Hardware jumpers Newhaven LVDS ===<br />
Make sure that configurable 0R resistor are moved to Newhaven LVDS0 interface <br /><br />
[[image:LVDS0 NH jumpers.png|800px]]<br />
<br /><br />
<br />
== Software instructions ==<br />
iMX8M Industrial kit is preinstalled with Yocto dunfell operation system enabling LVDS and touchscreen capabilities by default. Manual configuration is necessary, Devicetree in U-Boot have to by set to NHD LVDS0 LCD. <br />
=== LVDS0 NHD Devicetree in U-Boot ===<br />
Manually booting with LVDS interface as a primary source for video output:<br />
<syntaxhighlight lang="bash"><br />
Fastboot: Normal<br />
Normal Boot<br />
Hit any key to stop autoboot: 0<br />
u-boot=><br />
u-boot=><br />
u-boot=><br />
u-boot=><br />
u-boot=><br />
u-boot=> fatls mmc 0:1<br />
27787776 Image<br />
48586 imx8mq-evk-voipac-dp.dtb<br />
48793 imx8mq-evk-voipac-hdmi.dtb<br />
49194 imx8mq-evk-voipac-lvds-koe.dtb<br />
49198 imx8mq-evk-voipac-lvds-newhaven.dtb<br />
<br />
5 file(s), 0 dir(s)<br />
<br />
u-boot=> setenv fdt_file imx8mq-evk-voipac-lvds-newhaven.dtb<br />
u-boot=> saveenv<br />
Saving Environment to MMC... Writing to MMC(0)... OK<br />
u-boot=><br />
u-boot=> boot<br />
<br />
.<br />
</syntaxhighlight><br />
<br />
=== Touchscreen test ===<br />
Default Voipac iMX8M Image contain evtest utility to catch touchscreen events. Make sure SiS9509 controller is detected and bound as input device. Select the device event number 1 (generic ft5x06 (79)):<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# evtest<br />
No device specified, trying to scan all of /dev/input/event*<br />
Available devices:<br />
/dev/input/event0: 30370000.snvs:snvs-powerkey<br />
/dev/input/event1: generic ft5x06 (79)<br />
/dev/input/event2: gpio-buttons<br />
/dev/input/event3: bd718xx-pwrkey<br />
/dev/input/event4: Logitech USB Receiver<br />
/dev/input/event5: Logitech USB Receiver Mouse<br />
/dev/input/event6: Logitech USB Receiver Consumer Control<br />
/dev/input/event7: Logitech USB Receiver System Control<br />
Select the device event number [0-7]: 1<br />
Input driver version is 1.0.1<br />
Input device ID: bus 0x18 vendor 0x0 product 0x0 version 0x0<br />
Input device name: "generic ft5x06 (79)"<br />
Supported events:<br />
Event type 0 (EV_SYN)<br />
Event type 1 (EV_KEY)<br />
Event code 330 (BTN_TOUCH)<br />
Event type 3 (EV_ABS)<br />
Event code 0 (ABS_X)<br />
Value 308<br />
Min 0<br />
Max 1023<br />
Event code 1 (ABS_Y)<br />
Value 211<br />
Min 0<br />
Max 799<br />
Event code 47 (ABS_MT_SLOT)<br />
Value 0<br />
Min 0<br />
Max 4<br />
Event code 53 (ABS_MT_POSITION_X)<br />
Value 0<br />
Min 0<br />
Max 1023<br />
Event code 54 (ABS_MT_POSITION_Y)<br />
Value 0<br />
Min 0<br />
Max 799<br />
Event code 57 (ABS_MT_TRACKING_ID)<br />
Value 0<br />
Min 0<br />
Max 65535<br />
Properties:<br />
Property type 1 (INPUT_PROP_DIRECT)<br />
<br />
<br />
</syntaxhighlight><br />
<br />
Touchscreen events are generated after touching capacitive touch screen.<br />
<syntaxhighlight lang="bash"><br />
Testing ... (interrupt to exit)<br />
Event: time 1658851286.1658851286, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 40<br />
Event: time 1658851286.1658851286, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 506<br />
Event: time 1658851286.1658851286, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 478<br />
Event: time 1658851286.1658851286, -------------- SYN_REPORT ------------<br />
Event: time 1658851286.1658851286, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value -1<br />
Event: time 1658851286.1658851286, -------------- SYN_REPORT ------------<br />
Event: time 1658851532.1658851532, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 41<br />
Event: time 1658851532.1658851532, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 453<br />
Event: time 1658851532.1658851532, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 447<br />
Event: time 1658851532.1658851532, -------------- SYN_REPORT ------------<br />
Event: time 1658851532.1658851532, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 456<br />
Event: time 1658851532.1658851532, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 449<br />
Event: time 1658851532.1658851532, -------------- SYN_REPORT ------------<br />
Event: time 1658851533.1658851533, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 460<br />
Event: time 1658851533.1658851533, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 451<br />
Event: time 1658851533.1658851533, -------------- SYN_REPORT ------------<br />
Event: time 1658851533.1658851533, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 468<br />
Event: time 1658851533.1658851533, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 456<br />
Event: time 1658851533.1658851533, -------------- SYN_REPORT ------------<br />
Event: time 1658851533.1658851533, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 471<br />
Event: time 1658851533.1658851533, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 458<br />
Event: time 1658851533.1658851533, -------------- SYN_REPORT ------------<br />
Event: time 1658851533.1658851533, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 482<br />
Event: time 1658851533.1658851533, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 461<br />
Event: time 1658851533.1658851533, -------------- SYN_REPORT ------------<br />
Event: time 1658851533.1658851533, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 489<br />
Event: time 1658851533.1658851533, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 463<br />
Event: time 1658851533.1658851533, -------------- SYN_REPORT ------------<br />
Event: time 1658851533.1658851533, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 492<br />
Event: time 1658851533.1658851533, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 464<br />
Event: time 1658851533.1658851533, -------------- SYN_REPORT ------------<br />
Event: time 1658851533.1658851533, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 495<br />
Event: time 1658851533.1658851533, -------------- SYN_REPORT ------------<br />
Event: time 1658851533.1658851533, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 497<br />
Event: time 1658851533.1658851533, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 467<br />
Event: time 1658851533.1658851533, -------------- SYN_REPORT ------------<br />
Event: time 1658851533.1658851533, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 499<br />
Event: time 1658851533.1658851533, -------------- SYN_REPORT ------------<br />
Event: time 1658851533.1658851533, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 506<br />
Event: time 1658851533.1658851533, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 468<br />
Event: time 1658851533.1658851533, -------------- SYN_REPORT ------------<br />
Event: time 1658851533.1658851533, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 512<br />
Event: time 1658851533.1658851533, -------------- SYN_REPORT ------------<br />
Event: time 1658851533.1658851533, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 520<br />
Event: time 1658851533.1658851533, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 466<br />
Event: time 1658851533.1658851533, -------------- SYN_REPORT ------------<br />
Event: time 1658851533.1658851533, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 528<br />
Event: time 1658851533.1658851533, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 465<br />
</syntaxhighlight></div>
Voipac-hw
https://wiki.voipac.com/index.php?title=Newhaven_LVDS_Capacitive_Display_Set&diff=3886
Newhaven LVDS Capacitive Display Set
2022-07-26T16:04:52Z
<p>Voipac-hw: /* Touchscreen test */</p>
<hr />
<div>[[Category:iMX8M Industial Development Kit]]<br />
[[Category:iMX8M Industial Peripherals]]<br />
<!-- --><br />
<div style="float:right">__TOC__</div><br />
<br />
This section shows information about the Newhaven LVDS Capacitive Display Set. The iMX8M Industrial Development Kit in this configuration is equipped with Yocto dunfell, kernel 5.4 to support LVDS display with a touchscreen layer. In this case the display is installed on the top of the iMX8M Development Baseboard.<br /><br />
[[image:Voipac NHD LCD Assembly.png|800px]]<br />
<br />
== Mechanical connection ==<br />
When combined with the complete iMX8M Industrial Kit, the Display Set creates a compact, ready-to-use solution. To assemble them together, the following mechanical and electrical accessories were designed and selected to be part of the Display set:<br />
* TFT LCD 1024x600 Pixels display with LVDS interface and Capacitive Touch with SiS9509 controller <br />
* 4x Hex Standoff Threaded M3 30.00mm long [Manufacturer PN: 971300321]<br />
* 40 Position flat flex cable 50.80mm long [Manufacturer PN: 0150200427]<br />
* 6 pin touchscreen flat flex cable<br />
* necessary spacers<br />
[[image:Voipac NHD LCD Fastener.png|800px]]<br />
<br />
== Hardware connection ==<br />
To enable smooth communication between the board and the display, connect the 40 Position FFC cable for LCD and 6 pin touchscreen FFC cable. To implement the display capabilities, following connections need to be made:<br />
* connection between LVDS Display and iMX8M Development Baseboard connector LVDS0 NHD (J12) using a 40 Position FFC cable<br />
* touchscreen connection between iMX8M Development Baseboard connector NHD Touch (J13) and Touchscreen 6 pin FFC cable<br />
=== LVDS and Touchscreen cable ===<br />
[[image:imx8m_LVDS_with_touchscreen_cable_for_NHD.jpg|800px]]<br />
=== Hardware jumpers Newhaven LVDS ===<br />
Make sure that configurable 0R resistor are moved to Newhaven LVDS0 interface <br /><br />
[[image:LVDS0 NH jumpers.png|800px]]<br />
<br /><br />
<br />
== Software instructions ==<br />
iMX8M Industrial kit is preinstalled with Yocto dunfell operation system enabling LVDS and touchscreen capabilities by default. Manual configuration is necessary, Devicetree in U-Boot have to by set to NHD LVDS0 LCD. <br />
=== LVDS0 NHD Devicetree in U-Boot ===<br />
Manually booting with LVDS interface as a primary source for video output:<br />
<syntaxhighlight lang="bash"><br />
Fastboot: Normal<br />
Normal Boot<br />
Hit any key to stop autoboot: 0<br />
u-boot=><br />
u-boot=><br />
u-boot=><br />
u-boot=><br />
u-boot=><br />
u-boot=> fatls mmc 0:1<br />
27787776 Image<br />
48586 imx8mq-evk-voipac-dp.dtb<br />
48793 imx8mq-evk-voipac-hdmi.dtb<br />
49194 imx8mq-evk-voipac-lvds-koe.dtb<br />
49198 imx8mq-evk-voipac-lvds-newhaven.dtb<br />
<br />
5 file(s), 0 dir(s)<br />
<br />
u-boot=> setenv fdt_file imx8mq-evk-voipac-lvds-newhaven.dtb<br />
u-boot=> saveenv<br />
Saving Environment to MMC... Writing to MMC(0)... OK<br />
u-boot=><br />
u-boot=> boot<br />
<br />
.<br />
</syntaxhighlight><br />
<br />
=== Touchscreen test ===<br />
Default Voipac iMX8M Image contain evtest utility to catch touchscreen events. Make sure SiS9509 controller is detected and bound as input device. Select the device event number 1 (generic ft5x06 (79)):<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# evtest<br />
No device specified, trying to scan all of /dev/input/event*<br />
Available devices:<br />
/dev/input/event0: 30370000.snvs:snvs-powerkey<br />
/dev/input/event1: generic ft5x06 (79)<br />
/dev/input/event2: gpio-buttons<br />
/dev/input/event3: bd718xx-pwrkey<br />
/dev/input/event4: Logitech USB Receiver<br />
/dev/input/event5: Logitech USB Receiver Mouse<br />
/dev/input/event6: Logitech USB Receiver Consumer Control<br />
/dev/input/event7: Logitech USB Receiver System Control<br />
Select the device event number [0-7]: 1<br />
Input driver version is 1.0.1<br />
Input device ID: bus 0x18 vendor 0x0 product 0x0 version 0x0<br />
Input device name: "generic ft5x06 (79)"<br />
Supported events:<br />
Event type 0 (EV_SYN)<br />
Event type 1 (EV_KEY)<br />
Event code 330 (BTN_TOUCH)<br />
Event type 3 (EV_ABS)<br />
Event code 0 (ABS_X)<br />
Value 308<br />
Min 0<br />
Max 1023<br />
Event code 1 (ABS_Y)<br />
Value 211<br />
Min 0<br />
Max 799<br />
Event code 47 (ABS_MT_SLOT)<br />
Value 0<br />
Min 0<br />
Max 4<br />
Event code 53 (ABS_MT_POSITION_X)<br />
Value 0<br />
Min 0<br />
Max 1023<br />
Event code 54 (ABS_MT_POSITION_Y)<br />
Value 0<br />
Min 0<br />
Max 799<br />
Event code 57 (ABS_MT_TRACKING_ID)<br />
Value 0<br />
Min 0<br />
Max 65535<br />
Properties:<br />
Property type 1 (INPUT_PROP_DIRECT)<br />
<br />
<br />
</syntaxhighlight><br />
<br />
Touchscreen events are generated after touching capacitive touch screen.<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# evtest /dev/input/by-path/platform-21a4000.i2c-event <br />
Testing ... (interrupt to exit)<br />
Event: time 1658851286.1658851286, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 40<br />
Event: time 1658851286.1658851286, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 506<br />
Event: time 1658851286.1658851286, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 478<br />
Event: time 1658851286.1658851286, -------------- SYN_REPORT ------------<br />
Event: time 1658851286.1658851286, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value -1<br />
Event: time 1658851286.1658851286, -------------- SYN_REPORT ------------<br />
</syntaxhighlight></div>
Voipac-hw
https://wiki.voipac.com/index.php?title=NXP_MIPI-CSI_Camera_Set&diff=3885
NXP MIPI-CSI Camera Set
2022-07-25T14:54:21Z
<p>Voipac-hw: </p>
<hr />
<div>[[Category:iMX8M Industrial Development Kit]]<br />
[[Category:iMX8M Industrial Peripherals]]<br />
<!-- --><br />
<div style="float:right">__TOC__</div><br />
<br />
MINISASTOCSI is a MIPI-CSI interface camera kit, based on OmniVision chipset OV5640 Detection, performance and essential commands are described here.<br />
<br /><br /><br />
[[image:hot-plug.png|400px]]<br />
<br /><br /><br />
[[image:MINISASTOCSI-Voipac-BB.png|800px]]<br /><br />
MINISASTOCSI is a MIPI-CSI interface camera connected to iMX8M Development Baseboard <br />
<br /><br />
<br />
== Kernel detection ==<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# dmesg | grep ov56<br />
[ 2.398433] ov5640_mipi 1-003c: No pin available<br />
[ 2.403090] ov5640_mipi 1-003c: No sensor pwdn pin available<br />
[ 2.408777] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 2.414571] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.539603] ov5640_mipi 2-003c: No pin available<br />
[ 2.549079] ov5640_mipi 2-003c: No sensor reset pin available<br />
[ 2.554887] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.999855] ov5640_mipi 1-003c: No pin available<br />
[ 3.005558] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 3.012003] ov5640_mipi 1-003c: 1-003c supply DVDD not found, using dummy regulator<br />
[ 3.019785] ov5640_mipi 1-003c: 1-003c supply AVDD not found, using dummy regulator<br />
[ 3.039290] ov5640_mipi 1-003c: Read reg error: reg=300a<br />
[ 3.044691] ov5640_mipi 1-003c: Camera is not found<br />
[ 3.051918] ov5640_mipi 2-003c: No pin available<br />
[ 3.062814] ov5640_mipi 2-003c: No sensor reset pin available<br />
[ 3.069209] ov5640_mipi 2-003c: 2-003c supply DVDD not found, using dummy regulator<br />
[ 3.076945] ov5640_mipi 2-003c: 2-003c supply AVDD not found, using dummy regulator<br />
[ 4.291092] mxc-mipi-csi2_yav 30a70000.mipi_csi: Registered sensor subdevice: ov5640_mipi 2-003c<br />
[ 4.304334] ov5640_mipi 2-003c: Camera is found<br />
</syntaxhighlight><br />
<br />
== I2C detection ==<br />
MINISASTOCSI camera chip is connected via I2C3. The most important address for correct detection is 0x3c.<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# i2cdetect -y 2<br />
0 1 2 3 4 5 6 7 8 9 a b c d e f<br />
00: -- -- -- -- -- -- -- -- -- -- -- -- --<br />
10: UU UU UU UU -- -- -- -- -- -- -- -- -- -- -- --<br />
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
30: -- -- -- -- -- -- -- -- -- -- -- -- UU -- -- --<br />
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
70: -- -- -- -- -- -- -- --<br />
</syntaxhighlight><br />
<br /><br />
MINISASTOCSI camera can be also connected to I2C2 interface by moving 0R resistors. However second camera connected on CSI-2 interface have same address 0x3c as MINISASTOCSI camera connected on CSI-1 interface. <br /><br />
[[image:CSI1-I2C2 and I2C3.png|800px]]<br /><br />
<br />
== Modules listing ==<br />
=== Kernel 4.1 ===<br />
<syntaxhighlight lang="bash"><br />
root@imx6-openrex:~# lsmod<br />
Module Size Used by<br />
mxc_v4l2_capture 27624 2<br />
ipu_bg_overlay_sdc 5385 1 mxc_v4l2_capture<br />
ipu_still 2331 1 mxc_v4l2_capture<br />
ipu_prp_enc 5903 1 mxc_v4l2_capture<br />
ipu_csi_enc 3904 1 mxc_v4l2_capture<br />
ipu_fg_overlay_sdc 6130 1 mxc_v4l2_capture<br />
ov5647_camera_mipi_int 30566 0<br />
adv7610_video 6373 0<br />
v4l2_int_device 2872 4 ov5647_camera_mipi_int,adv7610_video,ipu_csi_enc,mxc_v4l2_capture<br />
mxc_dcic 6528 0<br />
<br />
<br />
<br />
root@imx8mq-voipac:~# lsmod<br />
Module Size Used by<br />
crct10dif_ce 16384 1<br />
mwifiex_pcie 45056 0<br />
mwifiex 294912 1 mwifiex_pcie<br />
galcore 610304 2<br />
<br />
</syntaxhighlight><br />
<br />
== Resolution setting ==<br />
=== 1280x960 ===<br />
<syntaxhighlight lang="bash"><br />
echo 0 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1280x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 1 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1920x1080 ===<br />
<syntaxhighlight lang="bash"><br />
echo 2 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 ===<br />
<syntaxhighlight lang="bash"><br />
echo 3 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1024x768 (default) ===<br />
<syntaxhighlight lang="bash"><br />
echo 4 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 960x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 5 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 (narrow angle of view) ===<br />
<syntaxhighlight lang="bash"><br />
echo 6 > /sys/bus/i2c/devices/1-0036/ov5647_mode <br />
</syntaxhighlight><br />
<br />
== Gstreamer ==<br />
=== Capture single JPEG picture ===<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# gst-launch-1.0 v4l2src num-buffers=1 ! jpegenc ! filesink location=sample_image.jp<br />
eg<br />
Setting pipeline to PAUSED ...<br />
Pipeline is live and does not need PREROLL ...<br />
Setting pipeline to PLAYING ...<br />
New clock: GstSystemClock<br />
[ 1301.273334] ov5640_mipi 2-003c: s_stream: 1<br />
Got EOS from element "pipeline0".[ 1303.353181] ov5640_mipi 2-003c: s_stream: 0<br />
<br />
Execution ended after 0:00:02.649996154<br />
Setting pipeline to PAUSED ...<br />
Setting pipeline to READY ...<br />
Setting pipeline to NULL ...<br />
Freeing pipeline ...<br />
root@imx8mq-voipac:~# ls<br />
sample_image.jpeg<br />
root@imx8mq-voipac:~#<br />
</syntaxhighlight><br />
<br />
The image stored in local media with name sample_image.jpeg<br />
<br />
=== Video preview ===<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# GST_DEBUG=GST_BUFFER:5 gst-launch-1.0 v4l2src ! 'video/x-raw,framerate=30/1' ! aut<br />
ovideosink<br />
Setting pipeline to PAUSED ...<br />
Pipeline is live and does not need PREROLL ...<br />
Setting pipeline to PLAYING ...<br />
New clock: GstSystemClock<br />
0:00:00.842776580 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc0623c0 (GstVideoMeta) of size 112<br />
0:00:00.842935198 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc062440 (GstVideoMeta) of size 112<br />
0:00:00.843278592 469 0xaaaadc001c00 DEB[ 1415.898001] ov5640_mipi 2-003c: s_stream: 1<br />
UG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc0624c0 (GstVideoMeta) of size 112<br />
0:00:00.843338584 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc062540 (GstVideoMeta) of size 112<br />
[ 1416.119964] skip frame 1<br />
</syntaxhighlight><br />
The video stream from camera can be displayed on display/monitor</div>
Voipac-hw
https://wiki.voipac.com/index.php?title=DIGILENT_MIPI-CSI_Camera_Set&diff=3884
DIGILENT MIPI-CSI Camera Set
2022-07-23T12:32:26Z
<p>Voipac-hw: /* Capture single JPEG picture */</p>
<hr />
<div>[[Category:iMX8M Industrial Development Kit]]<br />
[[Category:iMX8M Industrial Peripherals]]<br />
<!-- --><br />
<div style="float:right">__TOC__</div><br />
<br />
This example uses Digilent Pcam 5C is a MIPI-CSI interface camera (built on OV5640 MIPI sensor) as a test device for CSI Interface. On this page OV5640 sensor integration, settings and usage on i.MX8M processors are shown.<br />
<br /><br />
[[image:Pcam-5C.png|800px]]<br /><br />
Digilent Pcam 5C is a MIPI-CSI interface, 5 MP Fixed-Focus color camera connected to iMX8M Development Baseboard <br />
<br /><br />
<br />
== Kernel detection ==<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# dmesg | grep ov56<br />
[ 2.410383] ov5640_mipi 1-003c: No pin available<br />
[ 2.415040] ov5640_mipi 1-003c: No sensor pwdn pin available<br />
[ 2.420726] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 2.426512] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.555690] ov5640_mipi 2-003c: No pin available<br />
[ 2.562074] ov5640_mipi 2-003c: No sensor reset pin available<br />
[ 2.567861] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.948998] ov5640_mipi 1-003c: No pin available<br />
[ 2.959199] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 2.970608] ov5640_mipi 1-003c: 1-003c supply DVDD not found, using dummy regulator<br />
[ 2.983356] ov5640_mipi 1-003c: 1-003c supply AVDD not found, using dummy regulator<br />
[ 4.190794] mxc-mipi-csi2_yav 30b60000.mipi_csi: Registered sensor subdevice: ov5640_mipi 1-003c<br />
[ 4.204863] ov5640_mipi 1-003c: Camera is found<br />
[ 4.209719] ov5640_mipi 2-003c: No pin available<br />
[ 4.214385] ov5640_mipi 2-003c: Failed to set power pin<br />
[ 4.219626] ov5640_mipi 2-003c: retval=-16<br />
[ 4.223747] ov5640_mipi: probe of 2-003c failed with error -16<br />
root@imx8mq-voipac:~#<br />
</syntaxhighlight><br />
<br />
== I2C detection ==<br />
DIGILENT Pcam 5C camera chip is connected via I2C2. The most important address for correct detection is 0x3c.<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# i2cdetect -y 1<br />
0 1 2 3 4 5 6 7 8 9 a b c d e f<br />
00: -- -- -- -- -- -- -- -- -- -- -- -- --<br />
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
20: -- -- -- UU -- -- -- UU -- -- -- -- -- -- -- --<br />
30: -- -- -- -- -- -- -- -- -- -- -- -- UU 3d -- --<br />
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
50: -- UU -- UU -- -- -- -- -- -- -- -- -- -- -- --<br />
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
70: -- -- -- -- -- -- -- --<br />
</syntaxhighlight><br />
<br />
== Modules listing ==<br />
=== Kernel 4.1 ???????????===<br />
<syntaxhighlight lang="bash"><br />
root@imx6-openrex:~# lsmod ????????????????<br />
Module Size Used by<br />
mxc_v4l2_capture 27624 2<br />
ipu_bg_overlay_sdc 5385 1 mxc_v4l2_capture<br />
ipu_still 2331 1 mxc_v4l2_capture<br />
ipu_prp_enc 5903 1 mxc_v4l2_capture<br />
ipu_csi_enc 3904 1 mxc_v4l2_capture<br />
ipu_fg_overlay_sdc 6130 1 mxc_v4l2_capture<br />
ov5647_camera_mipi_int 30566 0<br />
adv7610_video 6373 0<br />
v4l2_int_device 2872 4 ov5647_camera_mipi_int,adv7610_video,ipu_csi_enc,mxc_v4l2_capture<br />
mxc_dcic 6528 0<br />
<br />
<br />
<br />
root@imx8mq-voipac:~# lsmod<br />
Module Size Used by<br />
crct10dif_ce 16384 1<br />
mwifiex_pcie 45056 0<br />
mwifiex 294912 1 mwifiex_pcie<br />
galcore 610304 2<br />
<br />
</syntaxhighlight><br />
<br />
== Resolution setting ==<br />
The camera support video streaming formats 1080p (at 30 frames per second) and 720p (at 60 frames per second)<br />
=== 1280x960 ===<br />
<syntaxhighlight lang="bash"><br />
echo 0 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1280x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 1 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1920x1080 ===<br />
<syntaxhighlight lang="bash"><br />
echo 2 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 ===<br />
<syntaxhighlight lang="bash"><br />
echo 3 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1024x768 (default) ===<br />
<syntaxhighlight lang="bash"><br />
echo 4 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 960x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 5 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 (narrow angle of view) ===<br />
<syntaxhighlight lang="bash"><br />
echo 6 > /sys/bus/i2c/devices/1-0036/ov5647_mode <br />
</syntaxhighlight><br />
<br />
== Gstreamer ==<br />
=== Capture single JPEG picture ===<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# gst-launch-1.0 v4l2src num-buffers=1 ! jpegenc ! filesink location=sample_image.jp<br />
Setting pipeline to PAUSED ...<br />
Pipeline is live and does not need PREROLL ...<br />
Setting pipeline to PLAYING ...<br />
New clock: GstSystemClock<br />
ERROR: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Internal data stream error.<br />
Additional debug info:<br />
../git/libs/gst/base/gstbasesrc.c(3072): gst_base_src_loop (): /GstPipeline:pipeline0/GstV4l2Src:v4l2src0:<br />
streaming stopped, reason not-negotiated (-4)<br />
Execution ended after 0:00:00.000309960<br />
Setting pipeline to PAUSED ...<br />
Setting pipeline to READY ...<br />
Setting pipeline to NULL ...<br />
Freeing pipeline ...<br />
root@imx8mq-voipac:~# ls<br />
sample_image.jp<br />
</syntaxhighlight><br />
<br />
The image stored in local media with name sample_image.jpeg<br />
<br />
=== Video preview ===<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# GST_DEBUG=GST_BUFFER:5 gst-launch-1.0 v4l2src ! 'video/x-raw,framerate=30/1' ! aut<br />
ovideosink<br />
Setting pipeline to PAUSED ...<br />
Pipeline is live and does not need PREROLL ...<br />
Setting pipeline to PLAYING ...<br />
New clock: GstSystemClock<br />
0:00:00.842776580 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc0623c0 (GstVideoMeta) of size 112<br />
0:00:00.842935198 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc062440 (GstVideoMeta) of size 112<br />
0:00:00.843278592 469 0xaaaadc001c00 DEB[ 1415.898001] ov5640_mipi 2-003c: s_stream: 1<br />
UG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc0624c0 (GstVideoMeta) of size 112<br />
0:00:00.843338584 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc062540 (GstVideoMeta) of size 112<br />
[ 1416.119964] skip frame 1<br />
</syntaxhighlight><br />
The video stream from camera can be displayed on display/monitor</div>
Voipac-hw
https://wiki.voipac.com/index.php?title=DIGILENT_MIPI-CSI_Camera_Set&diff=3883
DIGILENT MIPI-CSI Camera Set
2022-07-23T12:28:48Z
<p>Voipac-hw: /* Kernel 4.1 */</p>
<hr />
<div>[[Category:iMX8M Industrial Development Kit]]<br />
[[Category:iMX8M Industrial Peripherals]]<br />
<!-- --><br />
<div style="float:right">__TOC__</div><br />
<br />
This example uses Digilent Pcam 5C is a MIPI-CSI interface camera (built on OV5640 MIPI sensor) as a test device for CSI Interface. On this page OV5640 sensor integration, settings and usage on i.MX8M processors are shown.<br />
<br /><br />
[[image:Pcam-5C.png|800px]]<br /><br />
Digilent Pcam 5C is a MIPI-CSI interface, 5 MP Fixed-Focus color camera connected to iMX8M Development Baseboard <br />
<br /><br />
<br />
== Kernel detection ==<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# dmesg | grep ov56<br />
[ 2.410383] ov5640_mipi 1-003c: No pin available<br />
[ 2.415040] ov5640_mipi 1-003c: No sensor pwdn pin available<br />
[ 2.420726] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 2.426512] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.555690] ov5640_mipi 2-003c: No pin available<br />
[ 2.562074] ov5640_mipi 2-003c: No sensor reset pin available<br />
[ 2.567861] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.948998] ov5640_mipi 1-003c: No pin available<br />
[ 2.959199] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 2.970608] ov5640_mipi 1-003c: 1-003c supply DVDD not found, using dummy regulator<br />
[ 2.983356] ov5640_mipi 1-003c: 1-003c supply AVDD not found, using dummy regulator<br />
[ 4.190794] mxc-mipi-csi2_yav 30b60000.mipi_csi: Registered sensor subdevice: ov5640_mipi 1-003c<br />
[ 4.204863] ov5640_mipi 1-003c: Camera is found<br />
[ 4.209719] ov5640_mipi 2-003c: No pin available<br />
[ 4.214385] ov5640_mipi 2-003c: Failed to set power pin<br />
[ 4.219626] ov5640_mipi 2-003c: retval=-16<br />
[ 4.223747] ov5640_mipi: probe of 2-003c failed with error -16<br />
root@imx8mq-voipac:~#<br />
</syntaxhighlight><br />
<br />
== I2C detection ==<br />
DIGILENT Pcam 5C camera chip is connected via I2C2. The most important address for correct detection is 0x3c.<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# i2cdetect -y 1<br />
0 1 2 3 4 5 6 7 8 9 a b c d e f<br />
00: -- -- -- -- -- -- -- -- -- -- -- -- --<br />
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
20: -- -- -- UU -- -- -- UU -- -- -- -- -- -- -- --<br />
30: -- -- -- -- -- -- -- -- -- -- -- -- UU 3d -- --<br />
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
50: -- UU -- UU -- -- -- -- -- -- -- -- -- -- -- --<br />
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
70: -- -- -- -- -- -- -- --<br />
</syntaxhighlight><br />
<br />
== Modules listing ==<br />
=== Kernel 4.1 ???????????===<br />
<syntaxhighlight lang="bash"><br />
root@imx6-openrex:~# lsmod ????????????????<br />
Module Size Used by<br />
mxc_v4l2_capture 27624 2<br />
ipu_bg_overlay_sdc 5385 1 mxc_v4l2_capture<br />
ipu_still 2331 1 mxc_v4l2_capture<br />
ipu_prp_enc 5903 1 mxc_v4l2_capture<br />
ipu_csi_enc 3904 1 mxc_v4l2_capture<br />
ipu_fg_overlay_sdc 6130 1 mxc_v4l2_capture<br />
ov5647_camera_mipi_int 30566 0<br />
adv7610_video 6373 0<br />
v4l2_int_device 2872 4 ov5647_camera_mipi_int,adv7610_video,ipu_csi_enc,mxc_v4l2_capture<br />
mxc_dcic 6528 0<br />
<br />
<br />
<br />
root@imx8mq-voipac:~# lsmod<br />
Module Size Used by<br />
crct10dif_ce 16384 1<br />
mwifiex_pcie 45056 0<br />
mwifiex 294912 1 mwifiex_pcie<br />
galcore 610304 2<br />
<br />
</syntaxhighlight><br />
<br />
== Resolution setting ==<br />
The camera support video streaming formats 1080p (at 30 frames per second) and 720p (at 60 frames per second)<br />
=== 1280x960 ===<br />
<syntaxhighlight lang="bash"><br />
echo 0 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1280x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 1 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1920x1080 ===<br />
<syntaxhighlight lang="bash"><br />
echo 2 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 ===<br />
<syntaxhighlight lang="bash"><br />
echo 3 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1024x768 (default) ===<br />
<syntaxhighlight lang="bash"><br />
echo 4 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 960x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 5 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 (narrow angle of view) ===<br />
<syntaxhighlight lang="bash"><br />
echo 6 > /sys/bus/i2c/devices/1-0036/ov5647_mode <br />
</syntaxhighlight><br />
<br />
== Gstreamer ==<br />
=== Capture single JPEG picture ===<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# gst-launch-1.0 v4l2src num-buffers=1 ! jpegenc ! filesink location=sample_image.jp<br />
eg<br />
Setting pipeline to PAUSED ...<br />
Pipeline is live and does not need PREROLL ...<br />
Setting pipeline to PLAYING ...<br />
New clock: GstSystemClock<br />
[ 1301.273334] ov5640_mipi 2-003c: s_stream: 1<br />
Got EOS from element "pipeline0".[ 1303.353181] ov5640_mipi 2-003c: s_stream: 0<br />
<br />
Execution ended after 0:00:02.649996154<br />
Setting pipeline to PAUSED ...<br />
Setting pipeline to READY ...<br />
Setting pipeline to NULL ...<br />
Freeing pipeline ...<br />
root@imx8mq-voipac:~# ls<br />
sample_image.jpeg<br />
root@imx8mq-voipac:~#<br />
</syntaxhighlight><br />
<br />
The image stored in local media with name sample_image.jpeg<br />
<br />
=== Video preview ===<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# GST_DEBUG=GST_BUFFER:5 gst-launch-1.0 v4l2src ! 'video/x-raw,framerate=30/1' ! aut<br />
ovideosink<br />
Setting pipeline to PAUSED ...<br />
Pipeline is live and does not need PREROLL ...<br />
Setting pipeline to PLAYING ...<br />
New clock: GstSystemClock<br />
0:00:00.842776580 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc0623c0 (GstVideoMeta) of size 112<br />
0:00:00.842935198 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc062440 (GstVideoMeta) of size 112<br />
0:00:00.843278592 469 0xaaaadc001c00 DEB[ 1415.898001] ov5640_mipi 2-003c: s_stream: 1<br />
UG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc0624c0 (GstVideoMeta) of size 112<br />
0:00:00.843338584 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc062540 (GstVideoMeta) of size 112<br />
[ 1416.119964] skip frame 1<br />
</syntaxhighlight><br />
The video stream from camera can be displayed on display/monitor</div>
Voipac-hw
https://wiki.voipac.com/index.php?title=DIGILENT_MIPI-CSI_Camera_Set&diff=3882
DIGILENT MIPI-CSI Camera Set
2022-07-23T12:28:06Z
<p>Voipac-hw: /* I2C detection */</p>
<hr />
<div>[[Category:iMX8M Industrial Development Kit]]<br />
[[Category:iMX8M Industrial Peripherals]]<br />
<!-- --><br />
<div style="float:right">__TOC__</div><br />
<br />
This example uses Digilent Pcam 5C is a MIPI-CSI interface camera (built on OV5640 MIPI sensor) as a test device for CSI Interface. On this page OV5640 sensor integration, settings and usage on i.MX8M processors are shown.<br />
<br /><br />
[[image:Pcam-5C.png|800px]]<br /><br />
Digilent Pcam 5C is a MIPI-CSI interface, 5 MP Fixed-Focus color camera connected to iMX8M Development Baseboard <br />
<br /><br />
<br />
== Kernel detection ==<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# dmesg | grep ov56<br />
[ 2.410383] ov5640_mipi 1-003c: No pin available<br />
[ 2.415040] ov5640_mipi 1-003c: No sensor pwdn pin available<br />
[ 2.420726] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 2.426512] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.555690] ov5640_mipi 2-003c: No pin available<br />
[ 2.562074] ov5640_mipi 2-003c: No sensor reset pin available<br />
[ 2.567861] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.948998] ov5640_mipi 1-003c: No pin available<br />
[ 2.959199] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 2.970608] ov5640_mipi 1-003c: 1-003c supply DVDD not found, using dummy regulator<br />
[ 2.983356] ov5640_mipi 1-003c: 1-003c supply AVDD not found, using dummy regulator<br />
[ 4.190794] mxc-mipi-csi2_yav 30b60000.mipi_csi: Registered sensor subdevice: ov5640_mipi 1-003c<br />
[ 4.204863] ov5640_mipi 1-003c: Camera is found<br />
[ 4.209719] ov5640_mipi 2-003c: No pin available<br />
[ 4.214385] ov5640_mipi 2-003c: Failed to set power pin<br />
[ 4.219626] ov5640_mipi 2-003c: retval=-16<br />
[ 4.223747] ov5640_mipi: probe of 2-003c failed with error -16<br />
root@imx8mq-voipac:~#<br />
</syntaxhighlight><br />
<br />
== I2C detection ==<br />
DIGILENT Pcam 5C camera chip is connected via I2C2. The most important address for correct detection is 0x3c.<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# i2cdetect -y 1<br />
0 1 2 3 4 5 6 7 8 9 a b c d e f<br />
00: -- -- -- -- -- -- -- -- -- -- -- -- --<br />
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
20: -- -- -- UU -- -- -- UU -- -- -- -- -- -- -- --<br />
30: -- -- -- -- -- -- -- -- -- -- -- -- UU 3d -- --<br />
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
50: -- UU -- UU -- -- -- -- -- -- -- -- -- -- -- --<br />
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
70: -- -- -- -- -- -- -- --<br />
</syntaxhighlight><br />
<br />
== Modules listing ==<br />
=== Kernel 4.1 ===<br />
<syntaxhighlight lang="bash"><br />
root@imx6-openrex:~# lsmod<br />
Module Size Used by<br />
mxc_v4l2_capture 27624 2<br />
ipu_bg_overlay_sdc 5385 1 mxc_v4l2_capture<br />
ipu_still 2331 1 mxc_v4l2_capture<br />
ipu_prp_enc 5903 1 mxc_v4l2_capture<br />
ipu_csi_enc 3904 1 mxc_v4l2_capture<br />
ipu_fg_overlay_sdc 6130 1 mxc_v4l2_capture<br />
ov5647_camera_mipi_int 30566 0<br />
adv7610_video 6373 0<br />
v4l2_int_device 2872 4 ov5647_camera_mipi_int,adv7610_video,ipu_csi_enc,mxc_v4l2_capture<br />
mxc_dcic 6528 0<br />
<br />
<br />
<br />
root@imx8mq-voipac:~# lsmod<br />
Module Size Used by<br />
crct10dif_ce 16384 1<br />
mwifiex_pcie 45056 0<br />
mwifiex 294912 1 mwifiex_pcie<br />
galcore 610304 2<br />
<br />
</syntaxhighlight><br />
<br />
== Resolution setting ==<br />
The camera support video streaming formats 1080p (at 30 frames per second) and 720p (at 60 frames per second)<br />
=== 1280x960 ===<br />
<syntaxhighlight lang="bash"><br />
echo 0 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1280x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 1 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1920x1080 ===<br />
<syntaxhighlight lang="bash"><br />
echo 2 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 ===<br />
<syntaxhighlight lang="bash"><br />
echo 3 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1024x768 (default) ===<br />
<syntaxhighlight lang="bash"><br />
echo 4 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 960x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 5 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 (narrow angle of view) ===<br />
<syntaxhighlight lang="bash"><br />
echo 6 > /sys/bus/i2c/devices/1-0036/ov5647_mode <br />
</syntaxhighlight><br />
<br />
== Gstreamer ==<br />
=== Capture single JPEG picture ===<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# gst-launch-1.0 v4l2src num-buffers=1 ! jpegenc ! filesink location=sample_image.jp<br />
eg<br />
Setting pipeline to PAUSED ...<br />
Pipeline is live and does not need PREROLL ...<br />
Setting pipeline to PLAYING ...<br />
New clock: GstSystemClock<br />
[ 1301.273334] ov5640_mipi 2-003c: s_stream: 1<br />
Got EOS from element "pipeline0".[ 1303.353181] ov5640_mipi 2-003c: s_stream: 0<br />
<br />
Execution ended after 0:00:02.649996154<br />
Setting pipeline to PAUSED ...<br />
Setting pipeline to READY ...<br />
Setting pipeline to NULL ...<br />
Freeing pipeline ...<br />
root@imx8mq-voipac:~# ls<br />
sample_image.jpeg<br />
root@imx8mq-voipac:~#<br />
</syntaxhighlight><br />
<br />
The image stored in local media with name sample_image.jpeg<br />
<br />
=== Video preview ===<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# GST_DEBUG=GST_BUFFER:5 gst-launch-1.0 v4l2src ! 'video/x-raw,framerate=30/1' ! aut<br />
ovideosink<br />
Setting pipeline to PAUSED ...<br />
Pipeline is live and does not need PREROLL ...<br />
Setting pipeline to PLAYING ...<br />
New clock: GstSystemClock<br />
0:00:00.842776580 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc0623c0 (GstVideoMeta) of size 112<br />
0:00:00.842935198 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc062440 (GstVideoMeta) of size 112<br />
0:00:00.843278592 469 0xaaaadc001c00 DEB[ 1415.898001] ov5640_mipi 2-003c: s_stream: 1<br />
UG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc0624c0 (GstVideoMeta) of size 112<br />
0:00:00.843338584 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc062540 (GstVideoMeta) of size 112<br />
[ 1416.119964] skip frame 1<br />
</syntaxhighlight><br />
The video stream from camera can be displayed on display/monitor</div>
Voipac-hw
https://wiki.voipac.com/index.php?title=DIGILENT_MIPI-CSI_Camera_Set&diff=3881
DIGILENT MIPI-CSI Camera Set
2022-07-23T12:24:40Z
<p>Voipac-hw: /* Kernel detection */</p>
<hr />
<div>[[Category:iMX8M Industrial Development Kit]]<br />
[[Category:iMX8M Industrial Peripherals]]<br />
<!-- --><br />
<div style="float:right">__TOC__</div><br />
<br />
This example uses Digilent Pcam 5C is a MIPI-CSI interface camera (built on OV5640 MIPI sensor) as a test device for CSI Interface. On this page OV5640 sensor integration, settings and usage on i.MX8M processors are shown.<br />
<br /><br />
[[image:Pcam-5C.png|800px]]<br /><br />
Digilent Pcam 5C is a MIPI-CSI interface, 5 MP Fixed-Focus color camera connected to iMX8M Development Baseboard <br />
<br /><br />
<br />
== Kernel detection ==<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# dmesg | grep ov56<br />
[ 2.410383] ov5640_mipi 1-003c: No pin available<br />
[ 2.415040] ov5640_mipi 1-003c: No sensor pwdn pin available<br />
[ 2.420726] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 2.426512] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.555690] ov5640_mipi 2-003c: No pin available<br />
[ 2.562074] ov5640_mipi 2-003c: No sensor reset pin available<br />
[ 2.567861] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.948998] ov5640_mipi 1-003c: No pin available<br />
[ 2.959199] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 2.970608] ov5640_mipi 1-003c: 1-003c supply DVDD not found, using dummy regulator<br />
[ 2.983356] ov5640_mipi 1-003c: 1-003c supply AVDD not found, using dummy regulator<br />
[ 4.190794] mxc-mipi-csi2_yav 30b60000.mipi_csi: Registered sensor subdevice: ov5640_mipi 1-003c<br />
[ 4.204863] ov5640_mipi 1-003c: Camera is found<br />
[ 4.209719] ov5640_mipi 2-003c: No pin available<br />
[ 4.214385] ov5640_mipi 2-003c: Failed to set power pin<br />
[ 4.219626] ov5640_mipi 2-003c: retval=-16<br />
[ 4.223747] ov5640_mipi: probe of 2-003c failed with error -16<br />
root@imx8mq-voipac:~#<br />
</syntaxhighlight><br />
<br />
== I2C detection ==<br />
MINISASTOCSI camera chip is connected via I2C3. The most important address for correct detection is 0x3c.<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# i2cdetect -y 2<br />
0 1 2 3 4 5 6 7 8 9 a b c d e f<br />
00: -- -- -- -- -- -- -- -- -- -- -- -- --<br />
10: UU UU UU UU -- -- -- -- -- -- -- -- -- -- -- --<br />
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
30: -- -- -- -- -- -- -- -- -- -- -- -- UU -- -- --<br />
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
70: -- -- -- -- -- -- -- --<br />
</syntaxhighlight><br />
<br />
MINISASTOCSI camera can be also connected to I2C2 interface by moving 0R resistors. However second camera connected on CSI-2 interface have same address 0x3c as MINISASTOCSI camera connected on CSI-1 interface. <br />
[[image:CSI1-I2C2 and I2C3.png|800px]]<br />
<br />
== Modules listing ==<br />
=== Kernel 4.1 ===<br />
<syntaxhighlight lang="bash"><br />
root@imx6-openrex:~# lsmod<br />
Module Size Used by<br />
mxc_v4l2_capture 27624 2<br />
ipu_bg_overlay_sdc 5385 1 mxc_v4l2_capture<br />
ipu_still 2331 1 mxc_v4l2_capture<br />
ipu_prp_enc 5903 1 mxc_v4l2_capture<br />
ipu_csi_enc 3904 1 mxc_v4l2_capture<br />
ipu_fg_overlay_sdc 6130 1 mxc_v4l2_capture<br />
ov5647_camera_mipi_int 30566 0<br />
adv7610_video 6373 0<br />
v4l2_int_device 2872 4 ov5647_camera_mipi_int,adv7610_video,ipu_csi_enc,mxc_v4l2_capture<br />
mxc_dcic 6528 0<br />
<br />
<br />
<br />
root@imx8mq-voipac:~# lsmod<br />
Module Size Used by<br />
crct10dif_ce 16384 1<br />
mwifiex_pcie 45056 0<br />
mwifiex 294912 1 mwifiex_pcie<br />
galcore 610304 2<br />
<br />
</syntaxhighlight><br />
<br />
== Resolution setting ==<br />
The camera support video streaming formats 1080p (at 30 frames per second) and 720p (at 60 frames per second)<br />
=== 1280x960 ===<br />
<syntaxhighlight lang="bash"><br />
echo 0 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1280x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 1 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1920x1080 ===<br />
<syntaxhighlight lang="bash"><br />
echo 2 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 ===<br />
<syntaxhighlight lang="bash"><br />
echo 3 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1024x768 (default) ===<br />
<syntaxhighlight lang="bash"><br />
echo 4 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 960x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 5 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 (narrow angle of view) ===<br />
<syntaxhighlight lang="bash"><br />
echo 6 > /sys/bus/i2c/devices/1-0036/ov5647_mode <br />
</syntaxhighlight><br />
<br />
== Gstreamer ==<br />
=== Capture single JPEG picture ===<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# gst-launch-1.0 v4l2src num-buffers=1 ! jpegenc ! filesink location=sample_image.jp<br />
eg<br />
Setting pipeline to PAUSED ...<br />
Pipeline is live and does not need PREROLL ...<br />
Setting pipeline to PLAYING ...<br />
New clock: GstSystemClock<br />
[ 1301.273334] ov5640_mipi 2-003c: s_stream: 1<br />
Got EOS from element "pipeline0".[ 1303.353181] ov5640_mipi 2-003c: s_stream: 0<br />
<br />
Execution ended after 0:00:02.649996154<br />
Setting pipeline to PAUSED ...<br />
Setting pipeline to READY ...<br />
Setting pipeline to NULL ...<br />
Freeing pipeline ...<br />
root@imx8mq-voipac:~# ls<br />
sample_image.jpeg<br />
root@imx8mq-voipac:~#<br />
</syntaxhighlight><br />
<br />
The image stored in local media with name sample_image.jpeg<br />
<br />
=== Video preview ===<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# GST_DEBUG=GST_BUFFER:5 gst-launch-1.0 v4l2src ! 'video/x-raw,framerate=30/1' ! aut<br />
ovideosink<br />
Setting pipeline to PAUSED ...<br />
Pipeline is live and does not need PREROLL ...<br />
Setting pipeline to PLAYING ...<br />
New clock: GstSystemClock<br />
0:00:00.842776580 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc0623c0 (GstVideoMeta) of size 112<br />
0:00:00.842935198 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc062440 (GstVideoMeta) of size 112<br />
0:00:00.843278592 469 0xaaaadc001c00 DEB[ 1415.898001] ov5640_mipi 2-003c: s_stream: 1<br />
UG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc0624c0 (GstVideoMeta) of size 112<br />
0:00:00.843338584 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc062540 (GstVideoMeta) of size 112<br />
[ 1416.119964] skip frame 1<br />
</syntaxhighlight><br />
The video stream from camera can be displayed on display/monitor</div>
Voipac-hw
https://wiki.voipac.com/index.php?title=Newhaven_LVDS_Capacitive_Display_Set&diff=3880
Newhaven LVDS Capacitive Display Set
2022-07-23T12:17:26Z
<p>Voipac-hw: </p>
<hr />
<div>[[Category:iMX8M Industial Development Kit]]<br />
[[Category:iMX8M Industial Peripherals]]<br />
<!-- --><br />
<div style="float:right">__TOC__</div><br />
<br />
This section shows information about the Newhaven LVDS Capacitive Display Set. The iMX8M Industrial Development Kit in this configuration is equipped with Yocto dunfell, kernel 5.4 to support LVDS display with a touchscreen layer. In this case the display is installed on the top of the iMX8M Development Baseboard.<br /><br />
[[image:Voipac NHD LCD Assembly.png|800px]]<br />
<br />
== Mechanical connection ==<br />
When combined with the complete iMX8M Industrial Kit, the Display Set creates a compact, ready-to-use solution. To assemble them together, the following mechanical and electrical accessories were designed and selected to be part of the Display set:<br />
* TFT LCD 1024x600 Pixels display with LVDS interface and Capacitive Touch with SiS9509 controller <br />
* 4x Hex Standoff Threaded M3 30.00mm long [Manufacturer PN: 971300321]<br />
* 40 Position flat flex cable 50.80mm long [Manufacturer PN: 0150200427]<br />
* 6 pin touchscreen flat flex cable<br />
* necessary spacers<br />
[[image:Voipac NHD LCD Fastener.png|800px]]<br />
<br />
== Hardware connection ==<br />
To enable smooth communication between the board and the display, connect the 40 Position FFC cable for LCD and 6 pin touchscreen FFC cable. To implement the display capabilities, following connections need to be made:<br />
* connection between LVDS Display and iMX8M Development Baseboard connector LVDS0 NHD (J12) using a 40 Position FFC cable<br />
* touchscreen connection between iMX8M Development Baseboard connector NHD Touch (J13) and Touchscreen 6 pin FFC cable<br />
=== LVDS and Touchscreen cable ===<br />
[[image:imx8m_LVDS_with_touchscreen_cable_for_NHD.jpg|800px]]<br />
=== Hardware jumpers Newhaven LVDS ===<br />
Make sure that configurable 0R resistor are moved to Newhaven LVDS0 interface <br /><br />
[[image:LVDS0 NH jumpers.png|800px]]<br />
<br /><br />
<br />
== Software instructions ==<br />
iMX8M Industrial kit is preinstalled with Yocto dunfell operation system enabling LVDS and touchscreen capabilities by default. Manual configuration is necessary, Devicetree in U-Boot have to by set to NHD LVDS0 LCD. <br />
=== LVDS0 NHD Devicetree in U-Boot ===<br />
Manually booting with LVDS interface as a primary source for video output:<br />
<syntaxhighlight lang="bash"><br />
Fastboot: Normal<br />
Normal Boot<br />
Hit any key to stop autoboot: 0<br />
u-boot=><br />
u-boot=><br />
u-boot=><br />
u-boot=><br />
u-boot=><br />
u-boot=> fatls mmc 0:1<br />
27787776 Image<br />
48586 imx8mq-evk-voipac-dp.dtb<br />
48793 imx8mq-evk-voipac-hdmi.dtb<br />
49194 imx8mq-evk-voipac-lvds-koe.dtb<br />
49198 imx8mq-evk-voipac-lvds-newhaven.dtb<br />
<br />
5 file(s), 0 dir(s)<br />
<br />
u-boot=> setenv fdt_file imx8mq-evk-voipac-lvds-newhaven.dtb<br />
u-boot=> saveenv<br />
Saving Environment to MMC... Writing to MMC(0)... OK<br />
u-boot=><br />
u-boot=> boot<br />
<br />
.<br />
</syntaxhighlight><br />
<br />
=== Touchscreen test ===<br />
Default Voipac iMX8M Image contain evtest utility to catch touchscreen events. Make sure SiS9509 controller is detected and bound as input device:<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# dmesg | grep -i SiS9509 <br />
input: ----------<br />
evbug: ----------<br />
</syntaxhighlight><br />
<br />
Touchscreen events are generated after touching capacitive touch screen.<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# evtest /dev/input/by-path/platform-21a4000.i2c-event <br />
-<br />
-<br />
--<br />
---<br />
---<br />
--<br />
-<br />
-<br />
</syntaxhighlight></div>
Voipac-hw
https://wiki.voipac.com/index.php?title=File:Voipac_NHD_LCD_Fastener.png&diff=3879
File:Voipac NHD LCD Fastener.png
2022-07-23T12:17:02Z
<p>Voipac-hw: </p>
<hr />
<div>Voipac NHD LCD Fastener</div>
Voipac-hw
https://wiki.voipac.com/index.php?title=File:Voipac_NHD_LCD_Assembly.png&diff=3878
File:Voipac NHD LCD Assembly.png
2022-07-23T12:15:56Z
<p>Voipac-hw: </p>
<hr />
<div>Voipac NHD LCD Assembly</div>
Voipac-hw
https://wiki.voipac.com/index.php?title=DIGILENT_MIPI-CSI_Camera_Set&diff=3877
DIGILENT MIPI-CSI Camera Set
2022-07-23T10:17:46Z
<p>Voipac-hw: </p>
<hr />
<div>[[Category:iMX8M Industrial Development Kit]]<br />
[[Category:iMX8M Industrial Peripherals]]<br />
<!-- --><br />
<div style="float:right">__TOC__</div><br />
<br />
This example uses Digilent Pcam 5C is a MIPI-CSI interface camera (built on OV5640 MIPI sensor) as a test device for CSI Interface. On this page OV5640 sensor integration, settings and usage on i.MX8M processors are shown.<br />
<br /><br />
[[image:Pcam-5C.png|800px]]<br /><br />
Digilent Pcam 5C is a MIPI-CSI interface, 5 MP Fixed-Focus color camera connected to iMX8M Development Baseboard <br />
<br /><br />
<br />
== Kernel detection ==<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# dmesg | grep ov56<br />
[ 2.398433] ov5640_mipi 1-003c: No pin available<br />
[ 2.403090] ov5640_mipi 1-003c: No sensor pwdn pin available<br />
[ 2.408777] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 2.414571] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.539603] ov5640_mipi 2-003c: No pin available<br />
[ 2.549079] ov5640_mipi 2-003c: No sensor reset pin available<br />
[ 2.554887] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.999855] ov5640_mipi 1-003c: No pin available<br />
[ 3.005558] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 3.012003] ov5640_mipi 1-003c: 1-003c supply DVDD not found, using dummy regulator<br />
[ 3.019785] ov5640_mipi 1-003c: 1-003c supply AVDD not found, using dummy regulator<br />
[ 3.039290] ov5640_mipi 1-003c: Read reg error: reg=300a<br />
[ 3.044691] ov5640_mipi 1-003c: Camera is not found<br />
[ 3.051918] ov5640_mipi 2-003c: No pin available<br />
[ 3.062814] ov5640_mipi 2-003c: No sensor reset pin available<br />
[ 3.069209] ov5640_mipi 2-003c: 2-003c supply DVDD not found, using dummy regulator<br />
[ 3.076945] ov5640_mipi 2-003c: 2-003c supply AVDD not found, using dummy regulator<br />
[ 4.291092] mxc-mipi-csi2_yav 30a70000.mipi_csi: Registered sensor subdevice: ov5640_mipi 2-003c<br />
[ 4.304334] ov5640_mipi 2-003c: Camera is found<br />
</syntaxhighlight><br />
<br />
== I2C detection ==<br />
MINISASTOCSI camera chip is connected via I2C3. The most important address for correct detection is 0x3c.<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# i2cdetect -y 2<br />
0 1 2 3 4 5 6 7 8 9 a b c d e f<br />
00: -- -- -- -- -- -- -- -- -- -- -- -- --<br />
10: UU UU UU UU -- -- -- -- -- -- -- -- -- -- -- --<br />
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
30: -- -- -- -- -- -- -- -- -- -- -- -- UU -- -- --<br />
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
70: -- -- -- -- -- -- -- --<br />
</syntaxhighlight><br />
<br />
MINISASTOCSI camera can be also connected to I2C2 interface by moving 0R resistors. However second camera connected on CSI-2 interface have same address 0x3c as MINISASTOCSI camera connected on CSI-1 interface. <br />
[[image:CSI1-I2C2 and I2C3.png|800px]]<br />
<br />
== Modules listing ==<br />
=== Kernel 4.1 ===<br />
<syntaxhighlight lang="bash"><br />
root@imx6-openrex:~# lsmod<br />
Module Size Used by<br />
mxc_v4l2_capture 27624 2<br />
ipu_bg_overlay_sdc 5385 1 mxc_v4l2_capture<br />
ipu_still 2331 1 mxc_v4l2_capture<br />
ipu_prp_enc 5903 1 mxc_v4l2_capture<br />
ipu_csi_enc 3904 1 mxc_v4l2_capture<br />
ipu_fg_overlay_sdc 6130 1 mxc_v4l2_capture<br />
ov5647_camera_mipi_int 30566 0<br />
adv7610_video 6373 0<br />
v4l2_int_device 2872 4 ov5647_camera_mipi_int,adv7610_video,ipu_csi_enc,mxc_v4l2_capture<br />
mxc_dcic 6528 0<br />
<br />
<br />
<br />
root@imx8mq-voipac:~# lsmod<br />
Module Size Used by<br />
crct10dif_ce 16384 1<br />
mwifiex_pcie 45056 0<br />
mwifiex 294912 1 mwifiex_pcie<br />
galcore 610304 2<br />
<br />
</syntaxhighlight><br />
<br />
== Resolution setting ==<br />
The camera support video streaming formats 1080p (at 30 frames per second) and 720p (at 60 frames per second)<br />
=== 1280x960 ===<br />
<syntaxhighlight lang="bash"><br />
echo 0 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1280x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 1 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1920x1080 ===<br />
<syntaxhighlight lang="bash"><br />
echo 2 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 ===<br />
<syntaxhighlight lang="bash"><br />
echo 3 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1024x768 (default) ===<br />
<syntaxhighlight lang="bash"><br />
echo 4 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 960x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 5 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 (narrow angle of view) ===<br />
<syntaxhighlight lang="bash"><br />
echo 6 > /sys/bus/i2c/devices/1-0036/ov5647_mode <br />
</syntaxhighlight><br />
<br />
== Gstreamer ==<br />
=== Capture single JPEG picture ===<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# gst-launch-1.0 v4l2src num-buffers=1 ! jpegenc ! filesink location=sample_image.jp<br />
eg<br />
Setting pipeline to PAUSED ...<br />
Pipeline is live and does not need PREROLL ...<br />
Setting pipeline to PLAYING ...<br />
New clock: GstSystemClock<br />
[ 1301.273334] ov5640_mipi 2-003c: s_stream: 1<br />
Got EOS from element "pipeline0".[ 1303.353181] ov5640_mipi 2-003c: s_stream: 0<br />
<br />
Execution ended after 0:00:02.649996154<br />
Setting pipeline to PAUSED ...<br />
Setting pipeline to READY ...<br />
Setting pipeline to NULL ...<br />
Freeing pipeline ...<br />
root@imx8mq-voipac:~# ls<br />
sample_image.jpeg<br />
root@imx8mq-voipac:~#<br />
</syntaxhighlight><br />
<br />
The image stored in local media with name sample_image.jpeg<br />
<br />
=== Video preview ===<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# GST_DEBUG=GST_BUFFER:5 gst-launch-1.0 v4l2src ! 'video/x-raw,framerate=30/1' ! aut<br />
ovideosink<br />
Setting pipeline to PAUSED ...<br />
Pipeline is live and does not need PREROLL ...<br />
Setting pipeline to PLAYING ...<br />
New clock: GstSystemClock<br />
0:00:00.842776580 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc0623c0 (GstVideoMeta) of size 112<br />
0:00:00.842935198 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc062440 (GstVideoMeta) of size 112<br />
0:00:00.843278592 469 0xaaaadc001c00 DEB[ 1415.898001] ov5640_mipi 2-003c: s_stream: 1<br />
UG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc0624c0 (GstVideoMeta) of size 112<br />
0:00:00.843338584 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc062540 (GstVideoMeta) of size 112<br />
[ 1416.119964] skip frame 1<br />
</syntaxhighlight><br />
The video stream from camera can be displayed on display/monitor</div>
Voipac-hw
https://wiki.voipac.com/index.php?title=File:Pcam-5C.png&diff=3876
File:Pcam-5C.png
2022-07-23T10:17:24Z
<p>Voipac-hw: </p>
<hr />
<div>Pcam 5C</div>
Voipac-hw
https://wiki.voipac.com/index.php?title=DIGILENT_MIPI-CSI_Camera_Set&diff=3875
DIGILENT MIPI-CSI Camera Set
2022-07-23T09:41:05Z
<p>Voipac-hw: </p>
<hr />
<div>[[Category:iMX8M Industrial Development Kit]]<br />
[[Category:iMX8M Industrial Peripherals]]<br />
<!-- --><br />
<div style="float:right">__TOC__</div><br />
<br />
This example uses Digilent Pcam 5C is a MIPI-CSI interface camera (built on OV5640 MIPI sensor) as a test device for CSI Interface. On this page OV5640 sensor integration, settings and usage on i.MX8M processors are shown.<br />
<br /><br />
[[image:MINISASTOCSI-Voipac-BB.png|800px]]<br /><br />
Digilent Pcam 5C is a MIPI-CSI interface, 5 MP Fixed-Focus color camera connected to iMX8M Development Baseboard <br />
<br /><br />
<br />
== Kernel detection ==<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# dmesg | grep ov56<br />
[ 2.398433] ov5640_mipi 1-003c: No pin available<br />
[ 2.403090] ov5640_mipi 1-003c: No sensor pwdn pin available<br />
[ 2.408777] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 2.414571] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.539603] ov5640_mipi 2-003c: No pin available<br />
[ 2.549079] ov5640_mipi 2-003c: No sensor reset pin available<br />
[ 2.554887] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.999855] ov5640_mipi 1-003c: No pin available<br />
[ 3.005558] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 3.012003] ov5640_mipi 1-003c: 1-003c supply DVDD not found, using dummy regulator<br />
[ 3.019785] ov5640_mipi 1-003c: 1-003c supply AVDD not found, using dummy regulator<br />
[ 3.039290] ov5640_mipi 1-003c: Read reg error: reg=300a<br />
[ 3.044691] ov5640_mipi 1-003c: Camera is not found<br />
[ 3.051918] ov5640_mipi 2-003c: No pin available<br />
[ 3.062814] ov5640_mipi 2-003c: No sensor reset pin available<br />
[ 3.069209] ov5640_mipi 2-003c: 2-003c supply DVDD not found, using dummy regulator<br />
[ 3.076945] ov5640_mipi 2-003c: 2-003c supply AVDD not found, using dummy regulator<br />
[ 4.291092] mxc-mipi-csi2_yav 30a70000.mipi_csi: Registered sensor subdevice: ov5640_mipi 2-003c<br />
[ 4.304334] ov5640_mipi 2-003c: Camera is found<br />
</syntaxhighlight><br />
<br />
== I2C detection ==<br />
MINISASTOCSI camera chip is connected via I2C3. The most important address for correct detection is 0x3c.<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# i2cdetect -y 2<br />
0 1 2 3 4 5 6 7 8 9 a b c d e f<br />
00: -- -- -- -- -- -- -- -- -- -- -- -- --<br />
10: UU UU UU UU -- -- -- -- -- -- -- -- -- -- -- --<br />
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
30: -- -- -- -- -- -- -- -- -- -- -- -- UU -- -- --<br />
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
70: -- -- -- -- -- -- -- --<br />
</syntaxhighlight><br />
<br />
MINISASTOCSI camera can be also connected to I2C2 interface by moving 0R resistors. However second camera connected on CSI-2 interface have same address 0x3c as MINISASTOCSI camera connected on CSI-1 interface. <br />
[[image:CSI1-I2C2 and I2C3.png|800px]]<br />
<br />
== Modules listing ==<br />
=== Kernel 4.1 ===<br />
<syntaxhighlight lang="bash"><br />
root@imx6-openrex:~# lsmod<br />
Module Size Used by<br />
mxc_v4l2_capture 27624 2<br />
ipu_bg_overlay_sdc 5385 1 mxc_v4l2_capture<br />
ipu_still 2331 1 mxc_v4l2_capture<br />
ipu_prp_enc 5903 1 mxc_v4l2_capture<br />
ipu_csi_enc 3904 1 mxc_v4l2_capture<br />
ipu_fg_overlay_sdc 6130 1 mxc_v4l2_capture<br />
ov5647_camera_mipi_int 30566 0<br />
adv7610_video 6373 0<br />
v4l2_int_device 2872 4 ov5647_camera_mipi_int,adv7610_video,ipu_csi_enc,mxc_v4l2_capture<br />
mxc_dcic 6528 0<br />
<br />
<br />
<br />
root@imx8mq-voipac:~# lsmod<br />
Module Size Used by<br />
crct10dif_ce 16384 1<br />
mwifiex_pcie 45056 0<br />
mwifiex 294912 1 mwifiex_pcie<br />
galcore 610304 2<br />
<br />
</syntaxhighlight><br />
<br />
== Resolution setting ==<br />
The camera support video streaming formats 1080p (at 30 frames per second) and 720p (at 60 frames per second)<br />
=== 1280x960 ===<br />
<syntaxhighlight lang="bash"><br />
echo 0 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1280x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 1 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1920x1080 ===<br />
<syntaxhighlight lang="bash"><br />
echo 2 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 ===<br />
<syntaxhighlight lang="bash"><br />
echo 3 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1024x768 (default) ===<br />
<syntaxhighlight lang="bash"><br />
echo 4 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 960x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 5 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 (narrow angle of view) ===<br />
<syntaxhighlight lang="bash"><br />
echo 6 > /sys/bus/i2c/devices/1-0036/ov5647_mode <br />
</syntaxhighlight><br />
<br />
== Gstreamer ==<br />
=== Capture single JPEG picture ===<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# gst-launch-1.0 v4l2src num-buffers=1 ! jpegenc ! filesink location=sample_image.jp<br />
eg<br />
Setting pipeline to PAUSED ...<br />
Pipeline is live and does not need PREROLL ...<br />
Setting pipeline to PLAYING ...<br />
New clock: GstSystemClock<br />
[ 1301.273334] ov5640_mipi 2-003c: s_stream: 1<br />
Got EOS from element "pipeline0".[ 1303.353181] ov5640_mipi 2-003c: s_stream: 0<br />
<br />
Execution ended after 0:00:02.649996154<br />
Setting pipeline to PAUSED ...<br />
Setting pipeline to READY ...<br />
Setting pipeline to NULL ...<br />
Freeing pipeline ...<br />
root@imx8mq-voipac:~# ls<br />
sample_image.jpeg<br />
root@imx8mq-voipac:~#<br />
</syntaxhighlight><br />
<br />
The image stored in local media with name sample_image.jpeg<br />
<br />
=== Video preview ===<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# GST_DEBUG=GST_BUFFER:5 gst-launch-1.0 v4l2src ! 'video/x-raw,framerate=30/1' ! aut<br />
ovideosink<br />
Setting pipeline to PAUSED ...<br />
Pipeline is live and does not need PREROLL ...<br />
Setting pipeline to PLAYING ...<br />
New clock: GstSystemClock<br />
0:00:00.842776580 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc0623c0 (GstVideoMeta) of size 112<br />
0:00:00.842935198 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc062440 (GstVideoMeta) of size 112<br />
0:00:00.843278592 469 0xaaaadc001c00 DEB[ 1415.898001] ov5640_mipi 2-003c: s_stream: 1<br />
UG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc0624c0 (GstVideoMeta) of size 112<br />
0:00:00.843338584 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc062540 (GstVideoMeta) of size 112<br />
[ 1416.119964] skip frame 1<br />
</syntaxhighlight><br />
The video stream from camera can be displayed on display/monitor</div>
Voipac-hw
https://wiki.voipac.com/index.php?title=DIGILENT_MIPI-CSI_Camera_Set&diff=3874
DIGILENT MIPI-CSI Camera Set
2022-07-23T09:14:00Z
<p>Voipac-hw: </p>
<hr />
<div>[[Category:iMX8M Industrial Development Kit]]<br />
[[Category:iMX8M Industrial Peripherals]]<br />
<!-- --><br />
<div style="float:right">__TOC__</div><br />
<br />
This example uses RDigilent Pcam 5C is a MIPI-CSI interface camera (built on OV5640 MIPI sensor) as a test device for CSI Interface. On this page OV5640 sensor integration, settings and usage on i.MX8M processors are shown.<br />
<br /><br />
[[image:MINISASTOCSI-Voipac-BB.png|800px]]<br /><br />
Digilent Pcam 5C is a MIPI-CSI interface, 5 MP Fixed-Focus color camera connected to iMX8M Development Baseboard <br />
<br /><br />
<br />
== Kernel detection ==<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# dmesg | grep ov56<br />
[ 2.398433] ov5640_mipi 1-003c: No pin available<br />
[ 2.403090] ov5640_mipi 1-003c: No sensor pwdn pin available<br />
[ 2.408777] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 2.414571] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.539603] ov5640_mipi 2-003c: No pin available<br />
[ 2.549079] ov5640_mipi 2-003c: No sensor reset pin available<br />
[ 2.554887] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.999855] ov5640_mipi 1-003c: No pin available<br />
[ 3.005558] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 3.012003] ov5640_mipi 1-003c: 1-003c supply DVDD not found, using dummy regulator<br />
[ 3.019785] ov5640_mipi 1-003c: 1-003c supply AVDD not found, using dummy regulator<br />
[ 3.039290] ov5640_mipi 1-003c: Read reg error: reg=300a<br />
[ 3.044691] ov5640_mipi 1-003c: Camera is not found<br />
[ 3.051918] ov5640_mipi 2-003c: No pin available<br />
[ 3.062814] ov5640_mipi 2-003c: No sensor reset pin available<br />
[ 3.069209] ov5640_mipi 2-003c: 2-003c supply DVDD not found, using dummy regulator<br />
[ 3.076945] ov5640_mipi 2-003c: 2-003c supply AVDD not found, using dummy regulator<br />
[ 4.291092] mxc-mipi-csi2_yav 30a70000.mipi_csi: Registered sensor subdevice: ov5640_mipi 2-003c<br />
[ 4.304334] ov5640_mipi 2-003c: Camera is found<br />
</syntaxhighlight><br />
<br />
== I2C detection ==<br />
MINISASTOCSI camera chip is connected via I2C3. The most important address for correct detection is 0x3c.<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# i2cdetect -y 2<br />
0 1 2 3 4 5 6 7 8 9 a b c d e f<br />
00: -- -- -- -- -- -- -- -- -- -- -- -- --<br />
10: UU UU UU UU -- -- -- -- -- -- -- -- -- -- -- --<br />
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
30: -- -- -- -- -- -- -- -- -- -- -- -- UU -- -- --<br />
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
70: -- -- -- -- -- -- -- --<br />
</syntaxhighlight><br />
<br />
MINISASTOCSI camera can be also connected to I2C2 interface by moving 0R resistors. However second camera connected on CSI-2 interface have same address 0x3c as MINISASTOCSI camera connected on CSI-1 interface. <br />
[[image:CSI1-I2C2 and I2C3.png|800px]]<br />
<br />
== Modules listing ==<br />
=== Kernel 4.1 ===<br />
<syntaxhighlight lang="bash"><br />
root@imx6-openrex:~# lsmod<br />
Module Size Used by<br />
mxc_v4l2_capture 27624 2<br />
ipu_bg_overlay_sdc 5385 1 mxc_v4l2_capture<br />
ipu_still 2331 1 mxc_v4l2_capture<br />
ipu_prp_enc 5903 1 mxc_v4l2_capture<br />
ipu_csi_enc 3904 1 mxc_v4l2_capture<br />
ipu_fg_overlay_sdc 6130 1 mxc_v4l2_capture<br />
ov5647_camera_mipi_int 30566 0<br />
adv7610_video 6373 0<br />
v4l2_int_device 2872 4 ov5647_camera_mipi_int,adv7610_video,ipu_csi_enc,mxc_v4l2_capture<br />
mxc_dcic 6528 0<br />
<br />
<br />
<br />
root@imx8mq-voipac:~# lsmod<br />
Module Size Used by<br />
crct10dif_ce 16384 1<br />
mwifiex_pcie 45056 0<br />
mwifiex 294912 1 mwifiex_pcie<br />
galcore 610304 2<br />
<br />
</syntaxhighlight><br />
<br />
== Resolution setting ==<br />
The camera support video streaming formats 1080p (at 30 frames per second) and 720p (at 60 frames per second)<br />
=== 1280x960 ===<br />
<syntaxhighlight lang="bash"><br />
echo 0 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1280x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 1 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1920x1080 ===<br />
<syntaxhighlight lang="bash"><br />
echo 2 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 ===<br />
<syntaxhighlight lang="bash"><br />
echo 3 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1024x768 (default) ===<br />
<syntaxhighlight lang="bash"><br />
echo 4 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 960x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 5 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 (narrow angle of view) ===<br />
<syntaxhighlight lang="bash"><br />
echo 6 > /sys/bus/i2c/devices/1-0036/ov5647_mode <br />
</syntaxhighlight><br />
<br />
== Gstreamer ==<br />
=== Capture single JPEG picture ===<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# gst-launch-1.0 v4l2src num-buffers=1 ! jpegenc ! filesink location=sample_image.jp<br />
eg<br />
Setting pipeline to PAUSED ...<br />
Pipeline is live and does not need PREROLL ...<br />
Setting pipeline to PLAYING ...<br />
New clock: GstSystemClock<br />
[ 1301.273334] ov5640_mipi 2-003c: s_stream: 1<br />
Got EOS from element "pipeline0".[ 1303.353181] ov5640_mipi 2-003c: s_stream: 0<br />
<br />
Execution ended after 0:00:02.649996154<br />
Setting pipeline to PAUSED ...<br />
Setting pipeline to READY ...<br />
Setting pipeline to NULL ...<br />
Freeing pipeline ...<br />
root@imx8mq-voipac:~# ls<br />
sample_image.jpeg<br />
root@imx8mq-voipac:~#<br />
</syntaxhighlight><br />
<br />
The image stored in local media with name sample_image.jpeg<br />
<br />
=== Video preview ===<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# GST_DEBUG=GST_BUFFER:5 gst-launch-1.0 v4l2src ! 'video/x-raw,framerate=30/1' ! aut<br />
ovideosink<br />
Setting pipeline to PAUSED ...<br />
Pipeline is live and does not need PREROLL ...<br />
Setting pipeline to PLAYING ...<br />
New clock: GstSystemClock<br />
0:00:00.842776580 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc0623c0 (GstVideoMeta) of size 112<br />
0:00:00.842935198 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc062440 (GstVideoMeta) of size 112<br />
0:00:00.843278592 469 0xaaaadc001c00 DEB[ 1415.898001] ov5640_mipi 2-003c: s_stream: 1<br />
UG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc0624c0 (GstVideoMeta) of size 112<br />
0:00:00.843338584 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc062540 (GstVideoMeta) of size 112<br />
[ 1416.119964] skip frame 1<br />
</syntaxhighlight><br />
The video stream from camera can be displayed on display/monitor</div>
Voipac-hw
https://wiki.voipac.com/index.php?title=DIGILENT_MIPI-CSI_Camera_Set&diff=3873
DIGILENT MIPI-CSI Camera Set
2022-07-23T09:13:37Z
<p>Voipac-hw: </p>
<hr />
<div>[[Category:iMX8M Industrial Development Kit]]<br />
[[Category:iMX8M Industrial Peripherals]]<br />
<!-- --><br />
<div style="float:right">__TOC__</div><br />
<br />
This example uses RDigilent Pcam 5C is a MIPI-CSI interface camera (built on OV5640 MIPI sensor) as a test device for CSI Interface. On this page OV5640 sensor integration, settings and usage on i.MX8M processors are shown.<br /><br /><br />
<br />
<br />
<br /><br />
[[image:MINISASTOCSI-Voipac-BB.png|800px]]<br /><br />
Digilent Pcam 5C is a MIPI-CSI interface, 5 MP Fixed-Focus color camera connected to iMX8M Development Baseboard <br />
<br /><br />
<br />
== Kernel detection ==<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# dmesg | grep ov56<br />
[ 2.398433] ov5640_mipi 1-003c: No pin available<br />
[ 2.403090] ov5640_mipi 1-003c: No sensor pwdn pin available<br />
[ 2.408777] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 2.414571] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.539603] ov5640_mipi 2-003c: No pin available<br />
[ 2.549079] ov5640_mipi 2-003c: No sensor reset pin available<br />
[ 2.554887] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.999855] ov5640_mipi 1-003c: No pin available<br />
[ 3.005558] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 3.012003] ov5640_mipi 1-003c: 1-003c supply DVDD not found, using dummy regulator<br />
[ 3.019785] ov5640_mipi 1-003c: 1-003c supply AVDD not found, using dummy regulator<br />
[ 3.039290] ov5640_mipi 1-003c: Read reg error: reg=300a<br />
[ 3.044691] ov5640_mipi 1-003c: Camera is not found<br />
[ 3.051918] ov5640_mipi 2-003c: No pin available<br />
[ 3.062814] ov5640_mipi 2-003c: No sensor reset pin available<br />
[ 3.069209] ov5640_mipi 2-003c: 2-003c supply DVDD not found, using dummy regulator<br />
[ 3.076945] ov5640_mipi 2-003c: 2-003c supply AVDD not found, using dummy regulator<br />
[ 4.291092] mxc-mipi-csi2_yav 30a70000.mipi_csi: Registered sensor subdevice: ov5640_mipi 2-003c<br />
[ 4.304334] ov5640_mipi 2-003c: Camera is found<br />
</syntaxhighlight><br />
<br />
== I2C detection ==<br />
MINISASTOCSI camera chip is connected via I2C3. The most important address for correct detection is 0x3c.<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# i2cdetect -y 2<br />
0 1 2 3 4 5 6 7 8 9 a b c d e f<br />
00: -- -- -- -- -- -- -- -- -- -- -- -- --<br />
10: UU UU UU UU -- -- -- -- -- -- -- -- -- -- -- --<br />
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
30: -- -- -- -- -- -- -- -- -- -- -- -- UU -- -- --<br />
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
70: -- -- -- -- -- -- -- --<br />
</syntaxhighlight><br />
<br />
MINISASTOCSI camera can be also connected to I2C2 interface by moving 0R resistors. However second camera connected on CSI-2 interface have same address 0x3c as MINISASTOCSI camera connected on CSI-1 interface. <br />
[[image:CSI1-I2C2 and I2C3.png|800px]]<br />
<br />
== Modules listing ==<br />
=== Kernel 4.1 ===<br />
<syntaxhighlight lang="bash"><br />
root@imx6-openrex:~# lsmod<br />
Module Size Used by<br />
mxc_v4l2_capture 27624 2<br />
ipu_bg_overlay_sdc 5385 1 mxc_v4l2_capture<br />
ipu_still 2331 1 mxc_v4l2_capture<br />
ipu_prp_enc 5903 1 mxc_v4l2_capture<br />
ipu_csi_enc 3904 1 mxc_v4l2_capture<br />
ipu_fg_overlay_sdc 6130 1 mxc_v4l2_capture<br />
ov5647_camera_mipi_int 30566 0<br />
adv7610_video 6373 0<br />
v4l2_int_device 2872 4 ov5647_camera_mipi_int,adv7610_video,ipu_csi_enc,mxc_v4l2_capture<br />
mxc_dcic 6528 0<br />
<br />
<br />
<br />
root@imx8mq-voipac:~# lsmod<br />
Module Size Used by<br />
crct10dif_ce 16384 1<br />
mwifiex_pcie 45056 0<br />
mwifiex 294912 1 mwifiex_pcie<br />
galcore 610304 2<br />
<br />
</syntaxhighlight><br />
<br />
== Resolution setting ==<br />
The camera support video streaming formats 1080p (at 30 frames per second) and 720p (at 60 frames per second)<br />
=== 1280x960 ===<br />
<syntaxhighlight lang="bash"><br />
echo 0 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1280x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 1 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1920x1080 ===<br />
<syntaxhighlight lang="bash"><br />
echo 2 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 ===<br />
<syntaxhighlight lang="bash"><br />
echo 3 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1024x768 (default) ===<br />
<syntaxhighlight lang="bash"><br />
echo 4 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 960x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 5 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 (narrow angle of view) ===<br />
<syntaxhighlight lang="bash"><br />
echo 6 > /sys/bus/i2c/devices/1-0036/ov5647_mode <br />
</syntaxhighlight><br />
<br />
== Gstreamer ==<br />
=== Capture single JPEG picture ===<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# gst-launch-1.0 v4l2src num-buffers=1 ! jpegenc ! filesink location=sample_image.jp<br />
eg<br />
Setting pipeline to PAUSED ...<br />
Pipeline is live and does not need PREROLL ...<br />
Setting pipeline to PLAYING ...<br />
New clock: GstSystemClock<br />
[ 1301.273334] ov5640_mipi 2-003c: s_stream: 1<br />
Got EOS from element "pipeline0".[ 1303.353181] ov5640_mipi 2-003c: s_stream: 0<br />
<br />
Execution ended after 0:00:02.649996154<br />
Setting pipeline to PAUSED ...<br />
Setting pipeline to READY ...<br />
Setting pipeline to NULL ...<br />
Freeing pipeline ...<br />
root@imx8mq-voipac:~# ls<br />
sample_image.jpeg<br />
root@imx8mq-voipac:~#<br />
</syntaxhighlight><br />
<br />
The image stored in local media with name sample_image.jpeg<br />
<br />
=== Video preview ===<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# GST_DEBUG=GST_BUFFER:5 gst-launch-1.0 v4l2src ! 'video/x-raw,framerate=30/1' ! aut<br />
ovideosink<br />
Setting pipeline to PAUSED ...<br />
Pipeline is live and does not need PREROLL ...<br />
Setting pipeline to PLAYING ...<br />
New clock: GstSystemClock<br />
0:00:00.842776580 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc0623c0 (GstVideoMeta) of size 112<br />
0:00:00.842935198 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc062440 (GstVideoMeta) of size 112<br />
0:00:00.843278592 469 0xaaaadc001c00 DEB[ 1415.898001] ov5640_mipi 2-003c: s_stream: 1<br />
UG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc0624c0 (GstVideoMeta) of size 112<br />
0:00:00.843338584 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc062540 (GstVideoMeta) of size 112<br />
[ 1416.119964] skip frame 1<br />
</syntaxhighlight><br />
The video stream from camera can be displayed on display/monitor</div>
Voipac-hw
https://wiki.voipac.com/index.php?title=DIGILENT_MIPI-CSI_Camera_Set&diff=3872
DIGILENT MIPI-CSI Camera Set
2022-07-23T09:13:10Z
<p>Voipac-hw: </p>
<hr />
<div>[[Category:iMX8M Industrial Development Kit]]<br />
[[Category:iMX8M Industrial Peripherals]]<br />
<!-- --><br />
<div style="float:right">__TOC__</div><br />
<br />
This example uses RDigilent Pcam 5C is a MIPI-CSI interface camera (built on OV5640 MIPI sensor) as a test device for CSI Interface. On this page OV5640 sensor integration, settings and usage on i.MX8M processors are shown.<br /><br /><br />
<br />
'''''Note:''''' There is an issue concerning Raspberry Pi 1.3 cameras and its I2C detected. There might be some camera models that does not get identified.<br />
<br />
<br /><br />
[[image:MINISASTOCSI-Voipac-BB.png|800px]]<br /><br />
Digilent Pcam 5C is a MIPI-CSI interface, 5 MP Fixed-Focus color camera connected to iMX8M Development Baseboard <br />
<br /><br />
<br />
== Kernel detection ==<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# dmesg | grep ov56<br />
[ 2.398433] ov5640_mipi 1-003c: No pin available<br />
[ 2.403090] ov5640_mipi 1-003c: No sensor pwdn pin available<br />
[ 2.408777] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 2.414571] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.539603] ov5640_mipi 2-003c: No pin available<br />
[ 2.549079] ov5640_mipi 2-003c: No sensor reset pin available<br />
[ 2.554887] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.999855] ov5640_mipi 1-003c: No pin available<br />
[ 3.005558] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 3.012003] ov5640_mipi 1-003c: 1-003c supply DVDD not found, using dummy regulator<br />
[ 3.019785] ov5640_mipi 1-003c: 1-003c supply AVDD not found, using dummy regulator<br />
[ 3.039290] ov5640_mipi 1-003c: Read reg error: reg=300a<br />
[ 3.044691] ov5640_mipi 1-003c: Camera is not found<br />
[ 3.051918] ov5640_mipi 2-003c: No pin available<br />
[ 3.062814] ov5640_mipi 2-003c: No sensor reset pin available<br />
[ 3.069209] ov5640_mipi 2-003c: 2-003c supply DVDD not found, using dummy regulator<br />
[ 3.076945] ov5640_mipi 2-003c: 2-003c supply AVDD not found, using dummy regulator<br />
[ 4.291092] mxc-mipi-csi2_yav 30a70000.mipi_csi: Registered sensor subdevice: ov5640_mipi 2-003c<br />
[ 4.304334] ov5640_mipi 2-003c: Camera is found<br />
</syntaxhighlight><br />
<br />
== I2C detection ==<br />
MINISASTOCSI camera chip is connected via I2C3. The most important address for correct detection is 0x3c.<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# i2cdetect -y 2<br />
0 1 2 3 4 5 6 7 8 9 a b c d e f<br />
00: -- -- -- -- -- -- -- -- -- -- -- -- --<br />
10: UU UU UU UU -- -- -- -- -- -- -- -- -- -- -- --<br />
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
30: -- -- -- -- -- -- -- -- -- -- -- -- UU -- -- --<br />
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
70: -- -- -- -- -- -- -- --<br />
</syntaxhighlight><br />
<br />
MINISASTOCSI camera can be also connected to I2C2 interface by moving 0R resistors. However second camera connected on CSI-2 interface have same address 0x3c as MINISASTOCSI camera connected on CSI-1 interface. <br />
[[image:CSI1-I2C2 and I2C3.png|800px]]<br />
<br />
== Modules listing ==<br />
=== Kernel 4.1 ===<br />
<syntaxhighlight lang="bash"><br />
root@imx6-openrex:~# lsmod<br />
Module Size Used by<br />
mxc_v4l2_capture 27624 2<br />
ipu_bg_overlay_sdc 5385 1 mxc_v4l2_capture<br />
ipu_still 2331 1 mxc_v4l2_capture<br />
ipu_prp_enc 5903 1 mxc_v4l2_capture<br />
ipu_csi_enc 3904 1 mxc_v4l2_capture<br />
ipu_fg_overlay_sdc 6130 1 mxc_v4l2_capture<br />
ov5647_camera_mipi_int 30566 0<br />
adv7610_video 6373 0<br />
v4l2_int_device 2872 4 ov5647_camera_mipi_int,adv7610_video,ipu_csi_enc,mxc_v4l2_capture<br />
mxc_dcic 6528 0<br />
<br />
<br />
<br />
root@imx8mq-voipac:~# lsmod<br />
Module Size Used by<br />
crct10dif_ce 16384 1<br />
mwifiex_pcie 45056 0<br />
mwifiex 294912 1 mwifiex_pcie<br />
galcore 610304 2<br />
<br />
</syntaxhighlight><br />
<br />
== Resolution setting ==<br />
The camera support video streaming formats 1080p (at 30 frames per second) and 720p (at 60 frames per second)<br />
=== 1280x960 ===<br />
<syntaxhighlight lang="bash"><br />
echo 0 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1280x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 1 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1920x1080 ===<br />
<syntaxhighlight lang="bash"><br />
echo 2 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 ===<br />
<syntaxhighlight lang="bash"><br />
echo 3 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1024x768 (default) ===<br />
<syntaxhighlight lang="bash"><br />
echo 4 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 960x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 5 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 (narrow angle of view) ===<br />
<syntaxhighlight lang="bash"><br />
echo 6 > /sys/bus/i2c/devices/1-0036/ov5647_mode <br />
</syntaxhighlight><br />
<br />
== Gstreamer ==<br />
=== Capture single JPEG picture ===<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# gst-launch-1.0 v4l2src num-buffers=1 ! jpegenc ! filesink location=sample_image.jp<br />
eg<br />
Setting pipeline to PAUSED ...<br />
Pipeline is live and does not need PREROLL ...<br />
Setting pipeline to PLAYING ...<br />
New clock: GstSystemClock<br />
[ 1301.273334] ov5640_mipi 2-003c: s_stream: 1<br />
Got EOS from element "pipeline0".[ 1303.353181] ov5640_mipi 2-003c: s_stream: 0<br />
<br />
Execution ended after 0:00:02.649996154<br />
Setting pipeline to PAUSED ...<br />
Setting pipeline to READY ...<br />
Setting pipeline to NULL ...<br />
Freeing pipeline ...<br />
root@imx8mq-voipac:~# ls<br />
sample_image.jpeg<br />
root@imx8mq-voipac:~#<br />
</syntaxhighlight><br />
<br />
The image stored in local media with name sample_image.jpeg<br />
<br />
=== Video preview ===<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# GST_DEBUG=GST_BUFFER:5 gst-launch-1.0 v4l2src ! 'video/x-raw,framerate=30/1' ! aut<br />
ovideosink<br />
Setting pipeline to PAUSED ...<br />
Pipeline is live and does not need PREROLL ...<br />
Setting pipeline to PLAYING ...<br />
New clock: GstSystemClock<br />
0:00:00.842776580 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc0623c0 (GstVideoMeta) of size 112<br />
0:00:00.842935198 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc062440 (GstVideoMeta) of size 112<br />
0:00:00.843278592 469 0xaaaadc001c00 DEB[ 1415.898001] ov5640_mipi 2-003c: s_stream: 1<br />
UG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc0624c0 (GstVideoMeta) of size 112<br />
0:00:00.843338584 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc062540 (GstVideoMeta) of size 112<br />
[ 1416.119964] skip frame 1<br />
</syntaxhighlight><br />
The video stream from camera can be displayed on display/monitor</div>
Voipac-hw
https://wiki.voipac.com/index.php?title=DIGILENT_MIPI-CSI_Camera_Set&diff=3871
DIGILENT MIPI-CSI Camera Set
2022-07-23T09:11:17Z
<p>Voipac-hw: </p>
<hr />
<div>[[Category:iMX8M Industrial Development Kit]]<br />
[[Category:iMX8M Industrial Peripherals]]<br />
<!-- --><br />
<div style="float:right">__TOC__</div><br />
<br />
This example uses Raspberry Pi Camera Rev 1.3 (built on OV5647 MIPI sensor) as a test device for CSI Interface. On this page OV5647 sensor integration, settings and usage on i.MX8M processors are shown.<br /><br /><br />
<br />
'''''Note:''''' There is an issue concerning Raspberry Pi 1.3 cameras and its I2C detected. There might be some camera models that does not get identified.<br />
<br />
<br /><br />
[[image:MINISASTOCSI-Voipac-BB.png|800px]]<br /><br />
Digilent Pcam 5C is a MIPI-CSI interface, 5 MP Fixed-Focus color camera connected to iMX8M Development Baseboard <br />
<br /><br />
<br />
== Kernel detection ==<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# dmesg | grep ov56<br />
[ 2.398433] ov5640_mipi 1-003c: No pin available<br />
[ 2.403090] ov5640_mipi 1-003c: No sensor pwdn pin available<br />
[ 2.408777] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 2.414571] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.539603] ov5640_mipi 2-003c: No pin available<br />
[ 2.549079] ov5640_mipi 2-003c: No sensor reset pin available<br />
[ 2.554887] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.999855] ov5640_mipi 1-003c: No pin available<br />
[ 3.005558] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 3.012003] ov5640_mipi 1-003c: 1-003c supply DVDD not found, using dummy regulator<br />
[ 3.019785] ov5640_mipi 1-003c: 1-003c supply AVDD not found, using dummy regulator<br />
[ 3.039290] ov5640_mipi 1-003c: Read reg error: reg=300a<br />
[ 3.044691] ov5640_mipi 1-003c: Camera is not found<br />
[ 3.051918] ov5640_mipi 2-003c: No pin available<br />
[ 3.062814] ov5640_mipi 2-003c: No sensor reset pin available<br />
[ 3.069209] ov5640_mipi 2-003c: 2-003c supply DVDD not found, using dummy regulator<br />
[ 3.076945] ov5640_mipi 2-003c: 2-003c supply AVDD not found, using dummy regulator<br />
[ 4.291092] mxc-mipi-csi2_yav 30a70000.mipi_csi: Registered sensor subdevice: ov5640_mipi 2-003c<br />
[ 4.304334] ov5640_mipi 2-003c: Camera is found<br />
</syntaxhighlight><br />
<br />
== I2C detection ==<br />
MINISASTOCSI camera chip is connected via I2C3. The most important address for correct detection is 0x3c.<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# i2cdetect -y 2<br />
0 1 2 3 4 5 6 7 8 9 a b c d e f<br />
00: -- -- -- -- -- -- -- -- -- -- -- -- --<br />
10: UU UU UU UU -- -- -- -- -- -- -- -- -- -- -- --<br />
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
30: -- -- -- -- -- -- -- -- -- -- -- -- UU -- -- --<br />
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
70: -- -- -- -- -- -- -- --<br />
</syntaxhighlight><br />
<br />
MINISASTOCSI camera can be also connected to I2C2 interface by moving 0R resistors. However second camera connected on CSI-2 interface have same address 0x3c as MINISASTOCSI camera connected on CSI-1 interface. <br />
[[image:CSI1-I2C2 and I2C3.png|800px]]<br />
<br />
== Modules listing ==<br />
=== Kernel 4.1 ===<br />
<syntaxhighlight lang="bash"><br />
root@imx6-openrex:~# lsmod<br />
Module Size Used by<br />
mxc_v4l2_capture 27624 2<br />
ipu_bg_overlay_sdc 5385 1 mxc_v4l2_capture<br />
ipu_still 2331 1 mxc_v4l2_capture<br />
ipu_prp_enc 5903 1 mxc_v4l2_capture<br />
ipu_csi_enc 3904 1 mxc_v4l2_capture<br />
ipu_fg_overlay_sdc 6130 1 mxc_v4l2_capture<br />
ov5647_camera_mipi_int 30566 0<br />
adv7610_video 6373 0<br />
v4l2_int_device 2872 4 ov5647_camera_mipi_int,adv7610_video,ipu_csi_enc,mxc_v4l2_capture<br />
mxc_dcic 6528 0<br />
<br />
<br />
<br />
root@imx8mq-voipac:~# lsmod<br />
Module Size Used by<br />
crct10dif_ce 16384 1<br />
mwifiex_pcie 45056 0<br />
mwifiex 294912 1 mwifiex_pcie<br />
galcore 610304 2<br />
<br />
</syntaxhighlight><br />
<br />
== Resolution setting ==<br />
=== 1280x960 ===<br />
<syntaxhighlight lang="bash"><br />
echo 0 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1280x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 1 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1920x1080 ===<br />
<syntaxhighlight lang="bash"><br />
echo 2 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 ===<br />
<syntaxhighlight lang="bash"><br />
echo 3 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1024x768 (default) ===<br />
<syntaxhighlight lang="bash"><br />
echo 4 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 960x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 5 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 (narrow angle of view) ===<br />
<syntaxhighlight lang="bash"><br />
echo 6 > /sys/bus/i2c/devices/1-0036/ov5647_mode <br />
</syntaxhighlight><br />
<br />
== Gstreamer ==<br />
=== Capture single JPEG picture ===<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# gst-launch-1.0 v4l2src num-buffers=1 ! jpegenc ! filesink location=sample_image.jp<br />
eg<br />
Setting pipeline to PAUSED ...<br />
Pipeline is live and does not need PREROLL ...<br />
Setting pipeline to PLAYING ...<br />
New clock: GstSystemClock<br />
[ 1301.273334] ov5640_mipi 2-003c: s_stream: 1<br />
Got EOS from element "pipeline0".[ 1303.353181] ov5640_mipi 2-003c: s_stream: 0<br />
<br />
Execution ended after 0:00:02.649996154<br />
Setting pipeline to PAUSED ...<br />
Setting pipeline to READY ...<br />
Setting pipeline to NULL ...<br />
Freeing pipeline ...<br />
root@imx8mq-voipac:~# ls<br />
sample_image.jpeg<br />
root@imx8mq-voipac:~#<br />
</syntaxhighlight><br />
<br />
The image stored in local media with name sample_image.jpeg<br />
<br />
=== Video preview ===<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# GST_DEBUG=GST_BUFFER:5 gst-launch-1.0 v4l2src ! 'video/x-raw,framerate=30/1' ! aut<br />
ovideosink<br />
Setting pipeline to PAUSED ...<br />
Pipeline is live and does not need PREROLL ...<br />
Setting pipeline to PLAYING ...<br />
New clock: GstSystemClock<br />
0:00:00.842776580 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc0623c0 (GstVideoMeta) of size 112<br />
0:00:00.842935198 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc062440 (GstVideoMeta) of size 112<br />
0:00:00.843278592 469 0xaaaadc001c00 DEB[ 1415.898001] ov5640_mipi 2-003c: s_stream: 1<br />
UG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc0624c0 (GstVideoMeta) of size 112<br />
0:00:00.843338584 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc062540 (GstVideoMeta) of size 112<br />
[ 1416.119964] skip frame 1<br />
</syntaxhighlight><br />
The video stream from camera can be displayed on display/monitor</div>
Voipac-hw
https://wiki.voipac.com/index.php?title=KOE_LVDS_Capacitive_Display_Set&diff=3870
KOE LVDS Capacitive Display Set
2022-07-23T09:03:03Z
<p>Voipac-hw: /* Hardware connection */</p>
<hr />
<div>[[Category:iMX8M Industial Development Kit]]<br />
[[Category:iMX8M Industial Peripherals]]<br />
<!-- --><br />
<div style="float:right">__TOC__</div><br />
<br />
This section shows information about the KOE LVDS Capacitive Display Set. The iMX8M Industrial Development Kit in this configuration is equipped with Yocto dunfell, kernel 5.4 to support LVDS display with a touchscreen layer. In this case the display is installed on the top of the iMX8M Development Baseboard.<br /><br />
[[image:iMX8M Industrial Dev Kit KOE LCD.jpg|800px]]<br />
<br />
== Mechanical connection ==<br />
When combined with the complete iMX8M Industrial Kit, the Display Set creates a compact, ready-to-use solution. To assemble them together, the following mechanical and electrical accessories were designed and selected to be part of the Display set: <br />
* TFT LCD 1920 x 1080 Pixels display (TX18D200VM0EAA) with LVDS interface and Capacitive Touch with SIS9509 controller<br />
* 4x Hex Standoff Threaded M3 35.00mm long [Manufacturer PN: 971350321]<br />
* custom 20-pins LVDS cable, 180mm long. The cable is supply with LCD as set<br />
* custom 2-pins cable for LCD back light, 150mm long. The cable is supply with LCD as set<br />
* necessary spacers<br />
[[image:iMX8M Industrial Dev Kit KOE LCD Side view.jpg|800px]]<br />
<br />
== Hardware connection ==<br />
<br />
To enable smooth communication between the board and the display, connect the 20 Position LVDS cable for LCD and 6 pin touchscreen FFC cable. To implement the display capabilities, following connections need to be made:<br />
* connection between LVDS Display and iMX8M Development Baseboard connector LVDS0 KOE (J14) using a 20 Position LVDS cable<br />
* 2 position back light cable connect to connector J15<br />
* touchscreen connection between iMX8M Development Baseboard connector KOE Touch (J40) and Touchscreen 6 pin FFC cable<br />
<br />
=== LVDS and Touchscreen cable ===<br />
[[image:imx8m LVDS with touchscreen cable for KOE.jpg|800px]]<br />
<br />
=== Hardware jumpers Newhaven LVDS ===<br />
Make sure that configurable 0R resistor are moved to Newhaven LVDS0 interface <br /><br />
[[image:LVDS0 NH jumpers.png|800px]]<br /><br />
<br />
== Software instructions ==<br />
iMX8M Industrial kit is preinstalled with Yocto dunfell operation system enabling LVDS and touchscreen capabilities by default. Manual configuration is necessary, Devicetree in U-Boot have to by set to KOE LVDS0 LCD. <br />
=== LVDS0 KOE Devicetree in U-Boot ===<br />
Manually booting with LVDS interface as a primary source for video output:<br />
<syntaxhighlight lang="bash"><br />
Fastboot: Normal<br />
Normal Boot<br />
Hit any key to stop autoboot: 0<br />
u-boot=><br />
u-boot=><br />
u-boot=><br />
u-boot=><br />
u-boot=><br />
u-boot=> fatls mmc 0:1<br />
27787776 Image<br />
48586 imx8mq-evk-voipac-dp.dtb<br />
48793 imx8mq-evk-voipac-hdmi.dtb<br />
49194 imx8mq-evk-voipac-lvds-koe.dtb<br />
49198 imx8mq-evk-voipac-lvds-newhaven.dtb<br />
<br />
5 file(s), 0 dir(s)<br />
<br />
u-boot=> setenv fdt_file imx8mq-evk-voipac-lvds-koe.dtb<br />
u-boot=> saveenv<br />
Saving Environment to MMC... Writing to MMC(0)... OK<br />
u-boot=><br />
u-boot=> boot<br />
</syntaxhighlight><br />
<br />
=== Touchscreen test ===<br />
Default Voipac iMX8M Image contain evtest utility to catch touchscreen events. Make sure SiS9509 controller is detected and bound as input device: <br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# dmesg | grep -i SiS9509 <br />
input: ----------<br />
evbug: ----------<br />
</syntaxhighlight><br />
<br />
ouchscreen events are generated after touching capacitive touch screen. <br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# evtest /dev/input/by-path/platform-21a4000.i2c-event <br />
-<br />
-<br />
--<br />
---<br />
---<br />
--<br />
-<br />
-<br />
</syntaxhighlight></div>
Voipac-hw
https://wiki.voipac.com/index.php?title=Newhaven_LVDS_Capacitive_Display_Set&diff=3869
Newhaven LVDS Capacitive Display Set
2022-07-23T09:01:16Z
<p>Voipac-hw: /* Hardware connection */</p>
<hr />
<div>[[Category:iMX8M Industial Development Kit]]<br />
[[Category:iMX8M Industial Peripherals]]<br />
<!-- --><br />
<div style="float:right">__TOC__</div><br />
<br />
This section shows information about the Newhaven LVDS Capacitive Display Set. The iMX8M Industrial Development Kit in this configuration is equipped with Yocto dunfell, kernel 5.4 to support LVDS display with a touchscreen layer. In this case the display is installed on the top of the iMX8M Development Baseboard.<br /><br />
[[image:iMX8M_Industrial_NH_EMC.jpg|800px]]<br />
<br />
== Mechanical connection ==<br />
When combined with the complete iMX8M Industrial Kit, the Display Set creates a compact, ready-to-use solution. To assemble them together, the following mechanical and electrical accessories were designed and selected to be part of the Display set:<br />
* TFT LCD 1024x600 Pixels display with LVDS interface and Capacitive Touch with SiS9509 controller <br />
* 4x Hex Standoff Threaded M3 30.00mm long [Manufacturer PN: 971300321]<br />
* 40 Position flat flex cable 50.80mm long [Manufacturer PN: 0150200427]<br />
* 6 pin touchscreen flat flex cable<br />
* necessary spacers<br />
[[image:iMX8M_Industrial_NH_EMC.jpg|800px]]<br />
<br />
== Hardware connection ==<br />
To enable smooth communication between the board and the display, connect the 40 Position FFC cable for LCD and 6 pin touchscreen FFC cable. To implement the display capabilities, following connections need to be made:<br />
* connection between LVDS Display and iMX8M Development Baseboard connector LVDS0 NHD (J12) using a 40 Position FFC cable<br />
* touchscreen connection between iMX8M Development Baseboard connector NHD Touch (J13) and Touchscreen 6 pin FFC cable<br />
=== LVDS and Touchscreen cable ===<br />
[[image:imx8m_LVDS_with_touchscreen_cable_for_NHD.jpg|800px]]<br />
=== Hardware jumpers Newhaven LVDS ===<br />
Make sure that configurable 0R resistor are moved to Newhaven LVDS0 interface <br /><br />
[[image:LVDS0 NH jumpers.png|800px]]<br />
<br /><br />
<br />
== Software instructions ==<br />
iMX8M Industrial kit is preinstalled with Yocto dunfell operation system enabling LVDS and touchscreen capabilities by default. Manual configuration is necessary, Devicetree in U-Boot have to by set to NHD LVDS0 LCD. <br />
=== LVDS0 NHD Devicetree in U-Boot ===<br />
Manually booting with LVDS interface as a primary source for video output:<br />
<syntaxhighlight lang="bash"><br />
Fastboot: Normal<br />
Normal Boot<br />
Hit any key to stop autoboot: 0<br />
u-boot=><br />
u-boot=><br />
u-boot=><br />
u-boot=><br />
u-boot=><br />
u-boot=> fatls mmc 0:1<br />
27787776 Image<br />
48586 imx8mq-evk-voipac-dp.dtb<br />
48793 imx8mq-evk-voipac-hdmi.dtb<br />
49194 imx8mq-evk-voipac-lvds-koe.dtb<br />
49198 imx8mq-evk-voipac-lvds-newhaven.dtb<br />
<br />
5 file(s), 0 dir(s)<br />
<br />
u-boot=> setenv fdt_file imx8mq-evk-voipac-lvds-newhaven.dtb<br />
u-boot=> saveenv<br />
Saving Environment to MMC... Writing to MMC(0)... OK<br />
u-boot=><br />
u-boot=> boot<br />
<br />
.<br />
</syntaxhighlight><br />
<br />
=== Touchscreen test ===<br />
Default Voipac iMX8M Image contain evtest utility to catch touchscreen events. Make sure SiS9509 controller is detected and bound as input device:<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# dmesg | grep -i SiS9509 <br />
input: ----------<br />
evbug: ----------<br />
</syntaxhighlight><br />
<br />
Touchscreen events are generated after touching capacitive touch screen.<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# evtest /dev/input/by-path/platform-21a4000.i2c-event <br />
-<br />
-<br />
--<br />
---<br />
---<br />
--<br />
-<br />
-<br />
</syntaxhighlight></div>
Voipac-hw
https://wiki.voipac.com/index.php?title=Newhaven_LVDS_Capacitive_Display_Set&diff=3868
Newhaven LVDS Capacitive Display Set
2022-07-23T08:58:48Z
<p>Voipac-hw: /* Hardware connection */</p>
<hr />
<div>[[Category:iMX8M Industial Development Kit]]<br />
[[Category:iMX8M Industial Peripherals]]<br />
<!-- --><br />
<div style="float:right">__TOC__</div><br />
<br />
This section shows information about the Newhaven LVDS Capacitive Display Set. The iMX8M Industrial Development Kit in this configuration is equipped with Yocto dunfell, kernel 5.4 to support LVDS display with a touchscreen layer. In this case the display is installed on the top of the iMX8M Development Baseboard.<br /><br />
[[image:iMX8M_Industrial_NH_EMC.jpg|800px]]<br />
<br />
== Mechanical connection ==<br />
When combined with the complete iMX8M Industrial Kit, the Display Set creates a compact, ready-to-use solution. To assemble them together, the following mechanical and electrical accessories were designed and selected to be part of the Display set:<br />
* TFT LCD 1024x600 Pixels display with LVDS interface and Capacitive Touch with SiS9509 controller <br />
* 4x Hex Standoff Threaded M3 30.00mm long [Manufacturer PN: 971300321]<br />
* 40 Position flat flex cable 50.80mm long [Manufacturer PN: 0150200427]<br />
* 6 pin touchscreen flat flex cable<br />
* necessary spacers<br />
[[image:iMX8M_Industrial_NH_EMC.jpg|800px]]<br />
<br />
== Hardware connection ==<br />
To enable smooth communication between the board and the display, connect the 40 Position FFC cable for LCD and 6 pin touchscreen FFC cable. To implement the display capabilities, following connections need to be made:<br />
* connection between LVDS Display and iMX8M Development Baseboard connector LVDS0 NHD (J12) using a 40 Position FFC cable<br />
* touchscreen connection between iMX8M Development Baseboard connector NHD Touch (J13) and Touchscreen 6 pin FFC cable<br />
=== LVDS and Touchscreen cable ===<br />
[[image:imx8m_LVDS_with_touchscreen_cable_for_NHD.jpg|800px]]<br />
=== Hardware jumpers Newhaven LVDS ===<br />
Make sure that configurable 0R resistor are moved to Newhaven LVDS0 interface <br />
[[image:LVDS0 NH jumpers.png|800px]]<br />
<br />
== Software instructions ==<br />
iMX8M Industrial kit is preinstalled with Yocto dunfell operation system enabling LVDS and touchscreen capabilities by default. Manual configuration is necessary, Devicetree in U-Boot have to by set to NHD LVDS0 LCD. <br />
=== LVDS0 NHD Devicetree in U-Boot ===<br />
Manually booting with LVDS interface as a primary source for video output:<br />
<syntaxhighlight lang="bash"><br />
Fastboot: Normal<br />
Normal Boot<br />
Hit any key to stop autoboot: 0<br />
u-boot=><br />
u-boot=><br />
u-boot=><br />
u-boot=><br />
u-boot=><br />
u-boot=> fatls mmc 0:1<br />
27787776 Image<br />
48586 imx8mq-evk-voipac-dp.dtb<br />
48793 imx8mq-evk-voipac-hdmi.dtb<br />
49194 imx8mq-evk-voipac-lvds-koe.dtb<br />
49198 imx8mq-evk-voipac-lvds-newhaven.dtb<br />
<br />
5 file(s), 0 dir(s)<br />
<br />
u-boot=> setenv fdt_file imx8mq-evk-voipac-lvds-newhaven.dtb<br />
u-boot=> saveenv<br />
Saving Environment to MMC... Writing to MMC(0)... OK<br />
u-boot=><br />
u-boot=> boot<br />
<br />
.<br />
</syntaxhighlight><br />
<br />
=== Touchscreen test ===<br />
Default Voipac iMX8M Image contain evtest utility to catch touchscreen events. Make sure SiS9509 controller is detected and bound as input device:<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# dmesg | grep -i SiS9509 <br />
input: ----------<br />
evbug: ----------<br />
</syntaxhighlight><br />
<br />
Touchscreen events are generated after touching capacitive touch screen.<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# evtest /dev/input/by-path/platform-21a4000.i2c-event <br />
-<br />
-<br />
--<br />
---<br />
---<br />
--<br />
-<br />
-<br />
</syntaxhighlight></div>
Voipac-hw
https://wiki.voipac.com/index.php?title=File:LVDS0_NH_jumpers.png&diff=3867
File:LVDS0 NH jumpers.png
2022-07-23T08:56:33Z
<p>Voipac-hw: </p>
<hr />
<div>LVDS0 NH jumpers</div>
Voipac-hw
https://wiki.voipac.com/index.php?title=DIGILENT_MIPI-CSI_Camera_Set&diff=3866
DIGILENT MIPI-CSI Camera Set
2022-07-22T20:23:46Z
<p>Voipac-hw: </p>
<hr />
<div>[[Category:iMX8M Industrial Development Kit]]<br />
[[Category:iMX8M Industrial Peripherals]]<br />
<!-- --><br />
<div style="float:right">__TOC__</div><br />
<br />
This example uses Raspberry Pi Camera Rev 1.3 (built on OV5647 MIPI sensor) as a test device for CSI Interface. On this page OV5647 sensor integration, settings and usage on i.MX8M processors are shown.<br /><br /><br />
<br />
'''''Note:''''' There is an issue concerning Raspberry Pi 1.3 cameras and its I2C detected. There might be some camera models that does not get identified.<br />
<br />
MINISASTOCSI is a MIPI-CSI interface camera kit, based on OmniVision chipset OV5640 Detection, performance and essential commands are described here.<br />
<br /><br /><br />
[[image:hot-plug.png|400px]]<br />
<br /><br /><br />
[[image:MINISASTOCSI-Voipac-BB.png|800px]]<br /><br />
MINISASTOCSI is a MIPI-CSI interface camera connected to iMX8M Development Baseboard <br />
<br /><br />
<br />
== Kernel detection ==<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# dmesg | grep ov56<br />
[ 2.398433] ov5640_mipi 1-003c: No pin available<br />
[ 2.403090] ov5640_mipi 1-003c: No sensor pwdn pin available<br />
[ 2.408777] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 2.414571] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.539603] ov5640_mipi 2-003c: No pin available<br />
[ 2.549079] ov5640_mipi 2-003c: No sensor reset pin available<br />
[ 2.554887] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.999855] ov5640_mipi 1-003c: No pin available<br />
[ 3.005558] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 3.012003] ov5640_mipi 1-003c: 1-003c supply DVDD not found, using dummy regulator<br />
[ 3.019785] ov5640_mipi 1-003c: 1-003c supply AVDD not found, using dummy regulator<br />
[ 3.039290] ov5640_mipi 1-003c: Read reg error: reg=300a<br />
[ 3.044691] ov5640_mipi 1-003c: Camera is not found<br />
[ 3.051918] ov5640_mipi 2-003c: No pin available<br />
[ 3.062814] ov5640_mipi 2-003c: No sensor reset pin available<br />
[ 3.069209] ov5640_mipi 2-003c: 2-003c supply DVDD not found, using dummy regulator<br />
[ 3.076945] ov5640_mipi 2-003c: 2-003c supply AVDD not found, using dummy regulator<br />
[ 4.291092] mxc-mipi-csi2_yav 30a70000.mipi_csi: Registered sensor subdevice: ov5640_mipi 2-003c<br />
[ 4.304334] ov5640_mipi 2-003c: Camera is found<br />
</syntaxhighlight><br />
<br />
== I2C detection ==<br />
MINISASTOCSI camera chip is connected via I2C3. The most important address for correct detection is 0x3c.<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# i2cdetect -y 2<br />
0 1 2 3 4 5 6 7 8 9 a b c d e f<br />
00: -- -- -- -- -- -- -- -- -- -- -- -- --<br />
10: UU UU UU UU -- -- -- -- -- -- -- -- -- -- -- --<br />
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
30: -- -- -- -- -- -- -- -- -- -- -- -- UU -- -- --<br />
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
70: -- -- -- -- -- -- -- --<br />
</syntaxhighlight><br />
<br />
MINISASTOCSI camera can be also connected to I2C2 interface by moving 0R resistors. However second camera connected on CSI-2 interface have same address 0x3c as MINISASTOCSI camera connected on CSI-1 interface. <br />
[[image:CSI1-I2C2 and I2C3.png|800px]]<br />
<br />
== Modules listing ==<br />
=== Kernel 4.1 ===<br />
<syntaxhighlight lang="bash"><br />
root@imx6-openrex:~# lsmod<br />
Module Size Used by<br />
mxc_v4l2_capture 27624 2<br />
ipu_bg_overlay_sdc 5385 1 mxc_v4l2_capture<br />
ipu_still 2331 1 mxc_v4l2_capture<br />
ipu_prp_enc 5903 1 mxc_v4l2_capture<br />
ipu_csi_enc 3904 1 mxc_v4l2_capture<br />
ipu_fg_overlay_sdc 6130 1 mxc_v4l2_capture<br />
ov5647_camera_mipi_int 30566 0<br />
adv7610_video 6373 0<br />
v4l2_int_device 2872 4 ov5647_camera_mipi_int,adv7610_video,ipu_csi_enc,mxc_v4l2_capture<br />
mxc_dcic 6528 0<br />
<br />
<br />
<br />
root@imx8mq-voipac:~# lsmod<br />
Module Size Used by<br />
crct10dif_ce 16384 1<br />
mwifiex_pcie 45056 0<br />
mwifiex 294912 1 mwifiex_pcie<br />
galcore 610304 2<br />
<br />
</syntaxhighlight><br />
<br />
== Resolution setting ==<br />
=== 1280x960 ===<br />
<syntaxhighlight lang="bash"><br />
echo 0 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1280x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 1 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1920x1080 ===<br />
<syntaxhighlight lang="bash"><br />
echo 2 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 ===<br />
<syntaxhighlight lang="bash"><br />
echo 3 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1024x768 (default) ===<br />
<syntaxhighlight lang="bash"><br />
echo 4 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 960x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 5 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 (narrow angle of view) ===<br />
<syntaxhighlight lang="bash"><br />
echo 6 > /sys/bus/i2c/devices/1-0036/ov5647_mode <br />
</syntaxhighlight><br />
<br />
== Gstreamer ==<br />
=== Capture single JPEG picture ===<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# gst-launch-1.0 v4l2src num-buffers=1 ! jpegenc ! filesink location=sample_image.jp<br />
eg<br />
Setting pipeline to PAUSED ...<br />
Pipeline is live and does not need PREROLL ...<br />
Setting pipeline to PLAYING ...<br />
New clock: GstSystemClock<br />
[ 1301.273334] ov5640_mipi 2-003c: s_stream: 1<br />
Got EOS from element "pipeline0".[ 1303.353181] ov5640_mipi 2-003c: s_stream: 0<br />
<br />
Execution ended after 0:00:02.649996154<br />
Setting pipeline to PAUSED ...<br />
Setting pipeline to READY ...<br />
Setting pipeline to NULL ...<br />
Freeing pipeline ...<br />
root@imx8mq-voipac:~# ls<br />
sample_image.jpeg<br />
root@imx8mq-voipac:~#<br />
</syntaxhighlight><br />
<br />
The image stored in local media with name sample_image.jpeg<br />
<br />
=== Video preview ===<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# GST_DEBUG=GST_BUFFER:5 gst-launch-1.0 v4l2src ! 'video/x-raw,framerate=30/1' ! aut<br />
ovideosink<br />
Setting pipeline to PAUSED ...<br />
Pipeline is live and does not need PREROLL ...<br />
Setting pipeline to PLAYING ...<br />
New clock: GstSystemClock<br />
0:00:00.842776580 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc0623c0 (GstVideoMeta) of size 112<br />
0:00:00.842935198 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc062440 (GstVideoMeta) of size 112<br />
0:00:00.843278592 469 0xaaaadc001c00 DEB[ 1415.898001] ov5640_mipi 2-003c: s_stream: 1<br />
UG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc0624c0 (GstVideoMeta) of size 112<br />
0:00:00.843338584 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc062540 (GstVideoMeta) of size 112<br />
[ 1416.119964] skip frame 1<br />
</syntaxhighlight><br />
The video stream from camera can be displayed on display/monitor</div>
Voipac-hw
https://wiki.voipac.com/index.php?title=NXP_MIPI-CSI_Camera_Set&diff=3865
NXP MIPI-CSI Camera Set
2022-07-22T20:21:09Z
<p>Voipac-hw: /* Video preview */</p>
<hr />
<div>[[Category:iMX8M Industrial Development Kit]]<br />
[[Category:iMX8M Industrial Peripherals]]<br />
<!-- --><br />
<div style="float:right">__TOC__</div><br />
<br />
MINISASTOCSI is a MIPI-CSI interface camera kit, based on OmniVision chipset OV5640 Detection, performance and essential commands are described here.<br />
<br /><br /><br />
[[image:hot-plug.png|400px]]<br />
<br /><br /><br />
[[image:MINISASTOCSI-Voipac-BB.png|800px]]<br /><br />
MINISASTOCSI is a MIPI-CSI interface camera connected to iMX8M Development Baseboard <br />
<br /><br />
<br />
== Kernel detection ==<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# dmesg | grep ov56<br />
[ 2.398433] ov5640_mipi 1-003c: No pin available<br />
[ 2.403090] ov5640_mipi 1-003c: No sensor pwdn pin available<br />
[ 2.408777] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 2.414571] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.539603] ov5640_mipi 2-003c: No pin available<br />
[ 2.549079] ov5640_mipi 2-003c: No sensor reset pin available<br />
[ 2.554887] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.999855] ov5640_mipi 1-003c: No pin available<br />
[ 3.005558] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 3.012003] ov5640_mipi 1-003c: 1-003c supply DVDD not found, using dummy regulator<br />
[ 3.019785] ov5640_mipi 1-003c: 1-003c supply AVDD not found, using dummy regulator<br />
[ 3.039290] ov5640_mipi 1-003c: Read reg error: reg=300a<br />
[ 3.044691] ov5640_mipi 1-003c: Camera is not found<br />
[ 3.051918] ov5640_mipi 2-003c: No pin available<br />
[ 3.062814] ov5640_mipi 2-003c: No sensor reset pin available<br />
[ 3.069209] ov5640_mipi 2-003c: 2-003c supply DVDD not found, using dummy regulator<br />
[ 3.076945] ov5640_mipi 2-003c: 2-003c supply AVDD not found, using dummy regulator<br />
[ 4.291092] mxc-mipi-csi2_yav 30a70000.mipi_csi: Registered sensor subdevice: ov5640_mipi 2-003c<br />
[ 4.304334] ov5640_mipi 2-003c: Camera is found<br />
</syntaxhighlight><br />
<br />
== I2C detection ==<br />
MINISASTOCSI camera chip is connected via I2C3. The most important address for correct detection is 0x3c.<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# i2cdetect -y 2<br />
0 1 2 3 4 5 6 7 8 9 a b c d e f<br />
00: -- -- -- -- -- -- -- -- -- -- -- -- --<br />
10: UU UU UU UU -- -- -- -- -- -- -- -- -- -- -- --<br />
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
30: -- -- -- -- -- -- -- -- -- -- -- -- UU -- -- --<br />
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
70: -- -- -- -- -- -- -- --<br />
</syntaxhighlight><br />
<br />
MINISASTOCSI camera can be also connected to I2C2 interface by moving 0R resistors. However second camera connected on CSI-2 interface have same address 0x3c as MINISASTOCSI camera connected on CSI-1 interface. <br />
[[image:CSI1-I2C2 and I2C3.png|800px]]<br />
<br />
== Modules listing ==<br />
=== Kernel 4.1 ===<br />
<syntaxhighlight lang="bash"><br />
root@imx6-openrex:~# lsmod<br />
Module Size Used by<br />
mxc_v4l2_capture 27624 2<br />
ipu_bg_overlay_sdc 5385 1 mxc_v4l2_capture<br />
ipu_still 2331 1 mxc_v4l2_capture<br />
ipu_prp_enc 5903 1 mxc_v4l2_capture<br />
ipu_csi_enc 3904 1 mxc_v4l2_capture<br />
ipu_fg_overlay_sdc 6130 1 mxc_v4l2_capture<br />
ov5647_camera_mipi_int 30566 0<br />
adv7610_video 6373 0<br />
v4l2_int_device 2872 4 ov5647_camera_mipi_int,adv7610_video,ipu_csi_enc,mxc_v4l2_capture<br />
mxc_dcic 6528 0<br />
<br />
<br />
<br />
root@imx8mq-voipac:~# lsmod<br />
Module Size Used by<br />
crct10dif_ce 16384 1<br />
mwifiex_pcie 45056 0<br />
mwifiex 294912 1 mwifiex_pcie<br />
galcore 610304 2<br />
<br />
</syntaxhighlight><br />
<br />
== Resolution setting ==<br />
=== 1280x960 ===<br />
<syntaxhighlight lang="bash"><br />
echo 0 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1280x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 1 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1920x1080 ===<br />
<syntaxhighlight lang="bash"><br />
echo 2 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 ===<br />
<syntaxhighlight lang="bash"><br />
echo 3 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1024x768 (default) ===<br />
<syntaxhighlight lang="bash"><br />
echo 4 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 960x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 5 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 (narrow angle of view) ===<br />
<syntaxhighlight lang="bash"><br />
echo 6 > /sys/bus/i2c/devices/1-0036/ov5647_mode <br />
</syntaxhighlight><br />
<br />
== Gstreamer ==<br />
=== Capture single JPEG picture ===<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# gst-launch-1.0 v4l2src num-buffers=1 ! jpegenc ! filesink location=sample_image.jp<br />
eg<br />
Setting pipeline to PAUSED ...<br />
Pipeline is live and does not need PREROLL ...<br />
Setting pipeline to PLAYING ...<br />
New clock: GstSystemClock<br />
[ 1301.273334] ov5640_mipi 2-003c: s_stream: 1<br />
Got EOS from element "pipeline0".[ 1303.353181] ov5640_mipi 2-003c: s_stream: 0<br />
<br />
Execution ended after 0:00:02.649996154<br />
Setting pipeline to PAUSED ...<br />
Setting pipeline to READY ...<br />
Setting pipeline to NULL ...<br />
Freeing pipeline ...<br />
root@imx8mq-voipac:~# ls<br />
sample_image.jpeg<br />
root@imx8mq-voipac:~#<br />
</syntaxhighlight><br />
<br />
The image stored in local media with name sample_image.jpeg<br />
<br />
=== Video preview ===<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# GST_DEBUG=GST_BUFFER:5 gst-launch-1.0 v4l2src ! 'video/x-raw,framerate=30/1' ! aut<br />
ovideosink<br />
Setting pipeline to PAUSED ...<br />
Pipeline is live and does not need PREROLL ...<br />
Setting pipeline to PLAYING ...<br />
New clock: GstSystemClock<br />
0:00:00.842776580 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc0623c0 (GstVideoMeta) of size 112<br />
0:00:00.842935198 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc062440 (GstVideoMeta) of size 112<br />
0:00:00.843278592 469 0xaaaadc001c00 DEB[ 1415.898001] ov5640_mipi 2-003c: s_stream: 1<br />
UG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc0624c0 (GstVideoMeta) of size 112<br />
0:00:00.843338584 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc062540 (GstVideoMeta) of size 112<br />
[ 1416.119964] skip frame 1<br />
</syntaxhighlight><br />
The video stream from camera can be displayed on display/monitor</div>
Voipac-hw
https://wiki.voipac.com/index.php?title=NXP_MIPI-CSI_Camera_Set&diff=3864
NXP MIPI-CSI Camera Set
2022-07-22T20:20:31Z
<p>Voipac-hw: /* Capture single JPEG picture */</p>
<hr />
<div>[[Category:iMX8M Industrial Development Kit]]<br />
[[Category:iMX8M Industrial Peripherals]]<br />
<!-- --><br />
<div style="float:right">__TOC__</div><br />
<br />
MINISASTOCSI is a MIPI-CSI interface camera kit, based on OmniVision chipset OV5640 Detection, performance and essential commands are described here.<br />
<br /><br /><br />
[[image:hot-plug.png|400px]]<br />
<br /><br /><br />
[[image:MINISASTOCSI-Voipac-BB.png|800px]]<br /><br />
MINISASTOCSI is a MIPI-CSI interface camera connected to iMX8M Development Baseboard <br />
<br /><br />
<br />
== Kernel detection ==<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# dmesg | grep ov56<br />
[ 2.398433] ov5640_mipi 1-003c: No pin available<br />
[ 2.403090] ov5640_mipi 1-003c: No sensor pwdn pin available<br />
[ 2.408777] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 2.414571] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.539603] ov5640_mipi 2-003c: No pin available<br />
[ 2.549079] ov5640_mipi 2-003c: No sensor reset pin available<br />
[ 2.554887] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.999855] ov5640_mipi 1-003c: No pin available<br />
[ 3.005558] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 3.012003] ov5640_mipi 1-003c: 1-003c supply DVDD not found, using dummy regulator<br />
[ 3.019785] ov5640_mipi 1-003c: 1-003c supply AVDD not found, using dummy regulator<br />
[ 3.039290] ov5640_mipi 1-003c: Read reg error: reg=300a<br />
[ 3.044691] ov5640_mipi 1-003c: Camera is not found<br />
[ 3.051918] ov5640_mipi 2-003c: No pin available<br />
[ 3.062814] ov5640_mipi 2-003c: No sensor reset pin available<br />
[ 3.069209] ov5640_mipi 2-003c: 2-003c supply DVDD not found, using dummy regulator<br />
[ 3.076945] ov5640_mipi 2-003c: 2-003c supply AVDD not found, using dummy regulator<br />
[ 4.291092] mxc-mipi-csi2_yav 30a70000.mipi_csi: Registered sensor subdevice: ov5640_mipi 2-003c<br />
[ 4.304334] ov5640_mipi 2-003c: Camera is found<br />
</syntaxhighlight><br />
<br />
== I2C detection ==<br />
MINISASTOCSI camera chip is connected via I2C3. The most important address for correct detection is 0x3c.<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# i2cdetect -y 2<br />
0 1 2 3 4 5 6 7 8 9 a b c d e f<br />
00: -- -- -- -- -- -- -- -- -- -- -- -- --<br />
10: UU UU UU UU -- -- -- -- -- -- -- -- -- -- -- --<br />
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
30: -- -- -- -- -- -- -- -- -- -- -- -- UU -- -- --<br />
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
70: -- -- -- -- -- -- -- --<br />
</syntaxhighlight><br />
<br />
MINISASTOCSI camera can be also connected to I2C2 interface by moving 0R resistors. However second camera connected on CSI-2 interface have same address 0x3c as MINISASTOCSI camera connected on CSI-1 interface. <br />
[[image:CSI1-I2C2 and I2C3.png|800px]]<br />
<br />
== Modules listing ==<br />
=== Kernel 4.1 ===<br />
<syntaxhighlight lang="bash"><br />
root@imx6-openrex:~# lsmod<br />
Module Size Used by<br />
mxc_v4l2_capture 27624 2<br />
ipu_bg_overlay_sdc 5385 1 mxc_v4l2_capture<br />
ipu_still 2331 1 mxc_v4l2_capture<br />
ipu_prp_enc 5903 1 mxc_v4l2_capture<br />
ipu_csi_enc 3904 1 mxc_v4l2_capture<br />
ipu_fg_overlay_sdc 6130 1 mxc_v4l2_capture<br />
ov5647_camera_mipi_int 30566 0<br />
adv7610_video 6373 0<br />
v4l2_int_device 2872 4 ov5647_camera_mipi_int,adv7610_video,ipu_csi_enc,mxc_v4l2_capture<br />
mxc_dcic 6528 0<br />
<br />
<br />
<br />
root@imx8mq-voipac:~# lsmod<br />
Module Size Used by<br />
crct10dif_ce 16384 1<br />
mwifiex_pcie 45056 0<br />
mwifiex 294912 1 mwifiex_pcie<br />
galcore 610304 2<br />
<br />
</syntaxhighlight><br />
<br />
== Resolution setting ==<br />
=== 1280x960 ===<br />
<syntaxhighlight lang="bash"><br />
echo 0 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1280x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 1 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1920x1080 ===<br />
<syntaxhighlight lang="bash"><br />
echo 2 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 ===<br />
<syntaxhighlight lang="bash"><br />
echo 3 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1024x768 (default) ===<br />
<syntaxhighlight lang="bash"><br />
echo 4 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 960x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 5 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 (narrow angle of view) ===<br />
<syntaxhighlight lang="bash"><br />
echo 6 > /sys/bus/i2c/devices/1-0036/ov5647_mode <br />
</syntaxhighlight><br />
<br />
== Gstreamer ==<br />
=== Capture single JPEG picture ===<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# gst-launch-1.0 v4l2src num-buffers=1 ! jpegenc ! filesink location=sample_image.jp<br />
eg<br />
Setting pipeline to PAUSED ...<br />
Pipeline is live and does not need PREROLL ...<br />
Setting pipeline to PLAYING ...<br />
New clock: GstSystemClock<br />
[ 1301.273334] ov5640_mipi 2-003c: s_stream: 1<br />
Got EOS from element "pipeline0".[ 1303.353181] ov5640_mipi 2-003c: s_stream: 0<br />
<br />
Execution ended after 0:00:02.649996154<br />
Setting pipeline to PAUSED ...<br />
Setting pipeline to READY ...<br />
Setting pipeline to NULL ...<br />
Freeing pipeline ...<br />
root@imx8mq-voipac:~# ls<br />
sample_image.jpeg<br />
root@imx8mq-voipac:~#<br />
</syntaxhighlight><br />
<br />
The image stored in local media with name sample_image.jpeg<br />
<br />
=== Video preview ===<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# GST_DEBUG=GST_BUFFER:5 gst-launch-1.0 v4l2src ! 'video/x-raw,framerate=30/1' ! aut<br />
ovideosink<br />
Setting pipeline to PAUSED ...<br />
Pipeline is live and does not need PREROLL ...<br />
Setting pipeline to PLAYING ...<br />
New clock: GstSystemClock<br />
0:00:00.842776580 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc0623c0 (GstVideoMeta) of size 112<br />
0:00:00.842935198 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc062440 (GstVideoMeta) of size 112<br />
0:00:00.843278592 469 0xaaaadc001c00 DEB[ 1415.898001] ov5640_mipi 2-003c: s_stream: 1<br />
UG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc0624c0 (GstVideoMeta) of size 112<br />
0:00:00.843338584 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc062540 (GstVideoMeta) of size 112<br />
[ 1416.119964] skip frame 1<br />
</syntaxhighlight></div>
Voipac-hw
https://wiki.voipac.com/index.php?title=NXP_MIPI-CSI_Camera_Set&diff=3863
NXP MIPI-CSI Camera Set
2022-07-22T20:06:36Z
<p>Voipac-hw: /* Video preview */</p>
<hr />
<div>[[Category:iMX8M Industrial Development Kit]]<br />
[[Category:iMX8M Industrial Peripherals]]<br />
<!-- --><br />
<div style="float:right">__TOC__</div><br />
<br />
MINISASTOCSI is a MIPI-CSI interface camera kit, based on OmniVision chipset OV5640 Detection, performance and essential commands are described here.<br />
<br /><br /><br />
[[image:hot-plug.png|400px]]<br />
<br /><br /><br />
[[image:MINISASTOCSI-Voipac-BB.png|800px]]<br /><br />
MINISASTOCSI is a MIPI-CSI interface camera connected to iMX8M Development Baseboard <br />
<br /><br />
<br />
== Kernel detection ==<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# dmesg | grep ov56<br />
[ 2.398433] ov5640_mipi 1-003c: No pin available<br />
[ 2.403090] ov5640_mipi 1-003c: No sensor pwdn pin available<br />
[ 2.408777] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 2.414571] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.539603] ov5640_mipi 2-003c: No pin available<br />
[ 2.549079] ov5640_mipi 2-003c: No sensor reset pin available<br />
[ 2.554887] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.999855] ov5640_mipi 1-003c: No pin available<br />
[ 3.005558] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 3.012003] ov5640_mipi 1-003c: 1-003c supply DVDD not found, using dummy regulator<br />
[ 3.019785] ov5640_mipi 1-003c: 1-003c supply AVDD not found, using dummy regulator<br />
[ 3.039290] ov5640_mipi 1-003c: Read reg error: reg=300a<br />
[ 3.044691] ov5640_mipi 1-003c: Camera is not found<br />
[ 3.051918] ov5640_mipi 2-003c: No pin available<br />
[ 3.062814] ov5640_mipi 2-003c: No sensor reset pin available<br />
[ 3.069209] ov5640_mipi 2-003c: 2-003c supply DVDD not found, using dummy regulator<br />
[ 3.076945] ov5640_mipi 2-003c: 2-003c supply AVDD not found, using dummy regulator<br />
[ 4.291092] mxc-mipi-csi2_yav 30a70000.mipi_csi: Registered sensor subdevice: ov5640_mipi 2-003c<br />
[ 4.304334] ov5640_mipi 2-003c: Camera is found<br />
</syntaxhighlight><br />
<br />
== I2C detection ==<br />
MINISASTOCSI camera chip is connected via I2C3. The most important address for correct detection is 0x3c.<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# i2cdetect -y 2<br />
0 1 2 3 4 5 6 7 8 9 a b c d e f<br />
00: -- -- -- -- -- -- -- -- -- -- -- -- --<br />
10: UU UU UU UU -- -- -- -- -- -- -- -- -- -- -- --<br />
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
30: -- -- -- -- -- -- -- -- -- -- -- -- UU -- -- --<br />
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
70: -- -- -- -- -- -- -- --<br />
</syntaxhighlight><br />
<br />
MINISASTOCSI camera can be also connected to I2C2 interface by moving 0R resistors. However second camera connected on CSI-2 interface have same address 0x3c as MINISASTOCSI camera connected on CSI-1 interface. <br />
[[image:CSI1-I2C2 and I2C3.png|800px]]<br />
<br />
== Modules listing ==<br />
=== Kernel 4.1 ===<br />
<syntaxhighlight lang="bash"><br />
root@imx6-openrex:~# lsmod<br />
Module Size Used by<br />
mxc_v4l2_capture 27624 2<br />
ipu_bg_overlay_sdc 5385 1 mxc_v4l2_capture<br />
ipu_still 2331 1 mxc_v4l2_capture<br />
ipu_prp_enc 5903 1 mxc_v4l2_capture<br />
ipu_csi_enc 3904 1 mxc_v4l2_capture<br />
ipu_fg_overlay_sdc 6130 1 mxc_v4l2_capture<br />
ov5647_camera_mipi_int 30566 0<br />
adv7610_video 6373 0<br />
v4l2_int_device 2872 4 ov5647_camera_mipi_int,adv7610_video,ipu_csi_enc,mxc_v4l2_capture<br />
mxc_dcic 6528 0<br />
<br />
<br />
<br />
root@imx8mq-voipac:~# lsmod<br />
Module Size Used by<br />
crct10dif_ce 16384 1<br />
mwifiex_pcie 45056 0<br />
mwifiex 294912 1 mwifiex_pcie<br />
galcore 610304 2<br />
<br />
</syntaxhighlight><br />
<br />
== Resolution setting ==<br />
=== 1280x960 ===<br />
<syntaxhighlight lang="bash"><br />
echo 0 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1280x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 1 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1920x1080 ===<br />
<syntaxhighlight lang="bash"><br />
echo 2 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 ===<br />
<syntaxhighlight lang="bash"><br />
echo 3 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1024x768 (default) ===<br />
<syntaxhighlight lang="bash"><br />
echo 4 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 960x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 5 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 (narrow angle of view) ===<br />
<syntaxhighlight lang="bash"><br />
echo 6 > /sys/bus/i2c/devices/1-0036/ov5647_mode <br />
</syntaxhighlight><br />
<br />
== Gstreamer ==<br />
=== Capture single JPEG picture ===<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# gst-launch-1.0 v4l2src num-buffers=1 ! jpegenc ! filesink location=sample_image.jp<br />
eg<br />
Setting pipeline to PAUSED ...<br />
Pipeline is live and does not need PREROLL ...<br />
Setting pipeline to PLAYING ...<br />
New clock: GstSystemClock<br />
[ 1301.273334] ov5640_mipi 2-003c: s_stream: 1<br />
Got EOS from element "pipeline0".[ 1303.353181] ov5640_mipi 2-003c: s_stream: 0<br />
<br />
Execution ended after 0:00:02.649996154<br />
Setting pipeline to PAUSED ...<br />
Setting pipeline to READY ...<br />
Setting pipeline to NULL ...<br />
Freeing pipeline ...<br />
root@imx8mq-voipac:~# ls<br />
sample_image.jpeg<br />
root@imx8mq-voipac:~#<br />
</syntaxhighlight><br />
<br />
=== Video preview ===<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# GST_DEBUG=GST_BUFFER:5 gst-launch-1.0 v4l2src ! 'video/x-raw,framerate=30/1' ! aut<br />
ovideosink<br />
Setting pipeline to PAUSED ...<br />
Pipeline is live and does not need PREROLL ...<br />
Setting pipeline to PLAYING ...<br />
New clock: GstSystemClock<br />
0:00:00.842776580 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc0623c0 (GstVideoMeta) of size 112<br />
0:00:00.842935198 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc062440 (GstVideoMeta) of size 112<br />
0:00:00.843278592 469 0xaaaadc001c00 DEB[ 1415.898001] ov5640_mipi 2-003c: s_stream: 1<br />
UG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc0624c0 (GstVideoMeta) of size 112<br />
0:00:00.843338584 469 0xaaaadc001c00 DEBUG GST_BUFFER gstbuffer.c:2279:gst_buffer_add_meta: alloc metadata 0xaaaadc062540 (GstVideoMeta) of size 112<br />
[ 1416.119964] skip frame 1<br />
</syntaxhighlight></div>
Voipac-hw
https://wiki.voipac.com/index.php?title=NXP_MIPI-CSI_Camera_Set&diff=3862
NXP MIPI-CSI Camera Set
2022-07-22T20:05:19Z
<p>Voipac-hw: /* Capture single JPEG picture */</p>
<hr />
<div>[[Category:iMX8M Industrial Development Kit]]<br />
[[Category:iMX8M Industrial Peripherals]]<br />
<!-- --><br />
<div style="float:right">__TOC__</div><br />
<br />
MINISASTOCSI is a MIPI-CSI interface camera kit, based on OmniVision chipset OV5640 Detection, performance and essential commands are described here.<br />
<br /><br /><br />
[[image:hot-plug.png|400px]]<br />
<br /><br /><br />
[[image:MINISASTOCSI-Voipac-BB.png|800px]]<br /><br />
MINISASTOCSI is a MIPI-CSI interface camera connected to iMX8M Development Baseboard <br />
<br /><br />
<br />
== Kernel detection ==<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# dmesg | grep ov56<br />
[ 2.398433] ov5640_mipi 1-003c: No pin available<br />
[ 2.403090] ov5640_mipi 1-003c: No sensor pwdn pin available<br />
[ 2.408777] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 2.414571] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.539603] ov5640_mipi 2-003c: No pin available<br />
[ 2.549079] ov5640_mipi 2-003c: No sensor reset pin available<br />
[ 2.554887] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.999855] ov5640_mipi 1-003c: No pin available<br />
[ 3.005558] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 3.012003] ov5640_mipi 1-003c: 1-003c supply DVDD not found, using dummy regulator<br />
[ 3.019785] ov5640_mipi 1-003c: 1-003c supply AVDD not found, using dummy regulator<br />
[ 3.039290] ov5640_mipi 1-003c: Read reg error: reg=300a<br />
[ 3.044691] ov5640_mipi 1-003c: Camera is not found<br />
[ 3.051918] ov5640_mipi 2-003c: No pin available<br />
[ 3.062814] ov5640_mipi 2-003c: No sensor reset pin available<br />
[ 3.069209] ov5640_mipi 2-003c: 2-003c supply DVDD not found, using dummy regulator<br />
[ 3.076945] ov5640_mipi 2-003c: 2-003c supply AVDD not found, using dummy regulator<br />
[ 4.291092] mxc-mipi-csi2_yav 30a70000.mipi_csi: Registered sensor subdevice: ov5640_mipi 2-003c<br />
[ 4.304334] ov5640_mipi 2-003c: Camera is found<br />
</syntaxhighlight><br />
<br />
== I2C detection ==<br />
MINISASTOCSI camera chip is connected via I2C3. The most important address for correct detection is 0x3c.<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# i2cdetect -y 2<br />
0 1 2 3 4 5 6 7 8 9 a b c d e f<br />
00: -- -- -- -- -- -- -- -- -- -- -- -- --<br />
10: UU UU UU UU -- -- -- -- -- -- -- -- -- -- -- --<br />
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
30: -- -- -- -- -- -- -- -- -- -- -- -- UU -- -- --<br />
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
70: -- -- -- -- -- -- -- --<br />
</syntaxhighlight><br />
<br />
MINISASTOCSI camera can be also connected to I2C2 interface by moving 0R resistors. However second camera connected on CSI-2 interface have same address 0x3c as MINISASTOCSI camera connected on CSI-1 interface. <br />
[[image:CSI1-I2C2 and I2C3.png|800px]]<br />
<br />
== Modules listing ==<br />
=== Kernel 4.1 ===<br />
<syntaxhighlight lang="bash"><br />
root@imx6-openrex:~# lsmod<br />
Module Size Used by<br />
mxc_v4l2_capture 27624 2<br />
ipu_bg_overlay_sdc 5385 1 mxc_v4l2_capture<br />
ipu_still 2331 1 mxc_v4l2_capture<br />
ipu_prp_enc 5903 1 mxc_v4l2_capture<br />
ipu_csi_enc 3904 1 mxc_v4l2_capture<br />
ipu_fg_overlay_sdc 6130 1 mxc_v4l2_capture<br />
ov5647_camera_mipi_int 30566 0<br />
adv7610_video 6373 0<br />
v4l2_int_device 2872 4 ov5647_camera_mipi_int,adv7610_video,ipu_csi_enc,mxc_v4l2_capture<br />
mxc_dcic 6528 0<br />
<br />
<br />
<br />
root@imx8mq-voipac:~# lsmod<br />
Module Size Used by<br />
crct10dif_ce 16384 1<br />
mwifiex_pcie 45056 0<br />
mwifiex 294912 1 mwifiex_pcie<br />
galcore 610304 2<br />
<br />
</syntaxhighlight><br />
<br />
== Resolution setting ==<br />
=== 1280x960 ===<br />
<syntaxhighlight lang="bash"><br />
echo 0 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1280x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 1 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1920x1080 ===<br />
<syntaxhighlight lang="bash"><br />
echo 2 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 ===<br />
<syntaxhighlight lang="bash"><br />
echo 3 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1024x768 (default) ===<br />
<syntaxhighlight lang="bash"><br />
echo 4 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 960x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 5 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 (narrow angle of view) ===<br />
<syntaxhighlight lang="bash"><br />
echo 6 > /sys/bus/i2c/devices/1-0036/ov5647_mode <br />
</syntaxhighlight><br />
<br />
== Gstreamer ==<br />
=== Capture single JPEG picture ===<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# gst-launch-1.0 v4l2src num-buffers=1 ! jpegenc ! filesink location=sample_image.jp<br />
eg<br />
Setting pipeline to PAUSED ...<br />
Pipeline is live and does not need PREROLL ...<br />
Setting pipeline to PLAYING ...<br />
New clock: GstSystemClock<br />
[ 1301.273334] ov5640_mipi 2-003c: s_stream: 1<br />
Got EOS from element "pipeline0".[ 1303.353181] ov5640_mipi 2-003c: s_stream: 0<br />
<br />
Execution ended after 0:00:02.649996154<br />
Setting pipeline to PAUSED ...<br />
Setting pipeline to READY ...<br />
Setting pipeline to NULL ...<br />
Freeing pipeline ...<br />
root@imx8mq-voipac:~# ls<br />
sample_image.jpeg<br />
root@imx8mq-voipac:~#<br />
</syntaxhighlight><br />
<br />
=== Video preview ===<br />
<syntaxhighlight lang="bash"><br />
echo 2 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
gst-launch-1.0 v4l2src device="/dev/video1" ! video/x-bayer,width=1920,height=1080,framerate=30/1 ! queue ! bayer2rgb ! videoconvert ! fbdevsink<br />
</syntaxhighlight><br />
<br />
<syntaxhighlight lang="bash"><br />
echo 3 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
gst-launch-1.0 v4l2src device="/dev/video1" ! video/x-bayer,width=640,height=480,framerate=15/1 ! bayer2rgb ! videoconvert ! fbdevsink<br />
</syntaxhighlight></div>
Voipac-hw
https://wiki.voipac.com/index.php?title=NXP_MIPI-CSI_Camera_Set&diff=3861
NXP MIPI-CSI Camera Set
2022-07-22T20:04:38Z
<p>Voipac-hw: /* Capture single JPEG picture */</p>
<hr />
<div>[[Category:iMX8M Industrial Development Kit]]<br />
[[Category:iMX8M Industrial Peripherals]]<br />
<!-- --><br />
<div style="float:right">__TOC__</div><br />
<br />
MINISASTOCSI is a MIPI-CSI interface camera kit, based on OmniVision chipset OV5640 Detection, performance and essential commands are described here.<br />
<br /><br /><br />
[[image:hot-plug.png|400px]]<br />
<br /><br /><br />
[[image:MINISASTOCSI-Voipac-BB.png|800px]]<br /><br />
MINISASTOCSI is a MIPI-CSI interface camera connected to iMX8M Development Baseboard <br />
<br /><br />
<br />
== Kernel detection ==<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# dmesg | grep ov56<br />
[ 2.398433] ov5640_mipi 1-003c: No pin available<br />
[ 2.403090] ov5640_mipi 1-003c: No sensor pwdn pin available<br />
[ 2.408777] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 2.414571] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.539603] ov5640_mipi 2-003c: No pin available<br />
[ 2.549079] ov5640_mipi 2-003c: No sensor reset pin available<br />
[ 2.554887] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.999855] ov5640_mipi 1-003c: No pin available<br />
[ 3.005558] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 3.012003] ov5640_mipi 1-003c: 1-003c supply DVDD not found, using dummy regulator<br />
[ 3.019785] ov5640_mipi 1-003c: 1-003c supply AVDD not found, using dummy regulator<br />
[ 3.039290] ov5640_mipi 1-003c: Read reg error: reg=300a<br />
[ 3.044691] ov5640_mipi 1-003c: Camera is not found<br />
[ 3.051918] ov5640_mipi 2-003c: No pin available<br />
[ 3.062814] ov5640_mipi 2-003c: No sensor reset pin available<br />
[ 3.069209] ov5640_mipi 2-003c: 2-003c supply DVDD not found, using dummy regulator<br />
[ 3.076945] ov5640_mipi 2-003c: 2-003c supply AVDD not found, using dummy regulator<br />
[ 4.291092] mxc-mipi-csi2_yav 30a70000.mipi_csi: Registered sensor subdevice: ov5640_mipi 2-003c<br />
[ 4.304334] ov5640_mipi 2-003c: Camera is found<br />
</syntaxhighlight><br />
<br />
== I2C detection ==<br />
MINISASTOCSI camera chip is connected via I2C3. The most important address for correct detection is 0x3c.<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# i2cdetect -y 2<br />
0 1 2 3 4 5 6 7 8 9 a b c d e f<br />
00: -- -- -- -- -- -- -- -- -- -- -- -- --<br />
10: UU UU UU UU -- -- -- -- -- -- -- -- -- -- -- --<br />
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
30: -- -- -- -- -- -- -- -- -- -- -- -- UU -- -- --<br />
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
70: -- -- -- -- -- -- -- --<br />
</syntaxhighlight><br />
<br />
MINISASTOCSI camera can be also connected to I2C2 interface by moving 0R resistors. However second camera connected on CSI-2 interface have same address 0x3c as MINISASTOCSI camera connected on CSI-1 interface. <br />
[[image:CSI1-I2C2 and I2C3.png|800px]]<br />
<br />
== Modules listing ==<br />
=== Kernel 4.1 ===<br />
<syntaxhighlight lang="bash"><br />
root@imx6-openrex:~# lsmod<br />
Module Size Used by<br />
mxc_v4l2_capture 27624 2<br />
ipu_bg_overlay_sdc 5385 1 mxc_v4l2_capture<br />
ipu_still 2331 1 mxc_v4l2_capture<br />
ipu_prp_enc 5903 1 mxc_v4l2_capture<br />
ipu_csi_enc 3904 1 mxc_v4l2_capture<br />
ipu_fg_overlay_sdc 6130 1 mxc_v4l2_capture<br />
ov5647_camera_mipi_int 30566 0<br />
adv7610_video 6373 0<br />
v4l2_int_device 2872 4 ov5647_camera_mipi_int,adv7610_video,ipu_csi_enc,mxc_v4l2_capture<br />
mxc_dcic 6528 0<br />
<br />
<br />
<br />
root@imx8mq-voipac:~# lsmod<br />
Module Size Used by<br />
crct10dif_ce 16384 1<br />
mwifiex_pcie 45056 0<br />
mwifiex 294912 1 mwifiex_pcie<br />
galcore 610304 2<br />
<br />
</syntaxhighlight><br />
<br />
== Resolution setting ==<br />
=== 1280x960 ===<br />
<syntaxhighlight lang="bash"><br />
echo 0 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1280x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 1 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1920x1080 ===<br />
<syntaxhighlight lang="bash"><br />
echo 2 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 ===<br />
<syntaxhighlight lang="bash"><br />
echo 3 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1024x768 (default) ===<br />
<syntaxhighlight lang="bash"><br />
echo 4 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 960x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 5 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 (narrow angle of view) ===<br />
<syntaxhighlight lang="bash"><br />
echo 6 > /sys/bus/i2c/devices/1-0036/ov5647_mode <br />
</syntaxhighlight><br />
<br />
== Gstreamer ==<br />
=== Capture single JPEG picture ===<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# gst-launch-1.0 v4l2src num-buffers=1 ! jpegenc ! filesink location=sample_image.jp<br />
eg<br />
Setting pipeline to PAUSED ...<br />
Pipeline is live and does not need PREROLL ...<br />
Setting pipeline to PLAYING ...<br />
New clock: GstSystemClock<br />
[ 1301.273334] ov5640_mipi 2-003c: s_stream: 1<br />
Got EOS from element "pipeline0".[ 1303.353181] ov5640_mipi 2-003c: s_stream: 0<br />
<br />
Execution ended after 0:00:02.649996154<br />
Setting pipeline to PAUSED ...<br />
Setting pipeline to READY ...<br />
Setting pipeline to NULL ...<br />
Freeing pipeline ...<br />
root@imx8mq-voipac:~#<br />
</syntaxhighlight><br />
<br />
=== Video preview ===<br />
<syntaxhighlight lang="bash"><br />
echo 2 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
gst-launch-1.0 v4l2src device="/dev/video1" ! video/x-bayer,width=1920,height=1080,framerate=30/1 ! queue ! bayer2rgb ! videoconvert ! fbdevsink<br />
</syntaxhighlight><br />
<br />
<syntaxhighlight lang="bash"><br />
echo 3 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
gst-launch-1.0 v4l2src device="/dev/video1" ! video/x-bayer,width=640,height=480,framerate=15/1 ! bayer2rgb ! videoconvert ! fbdevsink<br />
</syntaxhighlight></div>
Voipac-hw
https://wiki.voipac.com/index.php?title=NXP_MIPI-CSI_Camera_Set&diff=3860
NXP MIPI-CSI Camera Set
2022-07-22T19:47:11Z
<p>Voipac-hw: /* Kernel 4.1 */</p>
<hr />
<div>[[Category:iMX8M Industrial Development Kit]]<br />
[[Category:iMX8M Industrial Peripherals]]<br />
<!-- --><br />
<div style="float:right">__TOC__</div><br />
<br />
MINISASTOCSI is a MIPI-CSI interface camera kit, based on OmniVision chipset OV5640 Detection, performance and essential commands are described here.<br />
<br /><br /><br />
[[image:hot-plug.png|400px]]<br />
<br /><br /><br />
[[image:MINISASTOCSI-Voipac-BB.png|800px]]<br /><br />
MINISASTOCSI is a MIPI-CSI interface camera connected to iMX8M Development Baseboard <br />
<br /><br />
<br />
== Kernel detection ==<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# dmesg | grep ov56<br />
[ 2.398433] ov5640_mipi 1-003c: No pin available<br />
[ 2.403090] ov5640_mipi 1-003c: No sensor pwdn pin available<br />
[ 2.408777] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 2.414571] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.539603] ov5640_mipi 2-003c: No pin available<br />
[ 2.549079] ov5640_mipi 2-003c: No sensor reset pin available<br />
[ 2.554887] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.999855] ov5640_mipi 1-003c: No pin available<br />
[ 3.005558] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 3.012003] ov5640_mipi 1-003c: 1-003c supply DVDD not found, using dummy regulator<br />
[ 3.019785] ov5640_mipi 1-003c: 1-003c supply AVDD not found, using dummy regulator<br />
[ 3.039290] ov5640_mipi 1-003c: Read reg error: reg=300a<br />
[ 3.044691] ov5640_mipi 1-003c: Camera is not found<br />
[ 3.051918] ov5640_mipi 2-003c: No pin available<br />
[ 3.062814] ov5640_mipi 2-003c: No sensor reset pin available<br />
[ 3.069209] ov5640_mipi 2-003c: 2-003c supply DVDD not found, using dummy regulator<br />
[ 3.076945] ov5640_mipi 2-003c: 2-003c supply AVDD not found, using dummy regulator<br />
[ 4.291092] mxc-mipi-csi2_yav 30a70000.mipi_csi: Registered sensor subdevice: ov5640_mipi 2-003c<br />
[ 4.304334] ov5640_mipi 2-003c: Camera is found<br />
</syntaxhighlight><br />
<br />
== I2C detection ==<br />
MINISASTOCSI camera chip is connected via I2C3. The most important address for correct detection is 0x3c.<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# i2cdetect -y 2<br />
0 1 2 3 4 5 6 7 8 9 a b c d e f<br />
00: -- -- -- -- -- -- -- -- -- -- -- -- --<br />
10: UU UU UU UU -- -- -- -- -- -- -- -- -- -- -- --<br />
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
30: -- -- -- -- -- -- -- -- -- -- -- -- UU -- -- --<br />
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
70: -- -- -- -- -- -- -- --<br />
</syntaxhighlight><br />
<br />
MINISASTOCSI camera can be also connected to I2C2 interface by moving 0R resistors. However second camera connected on CSI-2 interface have same address 0x3c as MINISASTOCSI camera connected on CSI-1 interface. <br />
[[image:CSI1-I2C2 and I2C3.png|800px]]<br />
<br />
== Modules listing ==<br />
=== Kernel 4.1 ===<br />
<syntaxhighlight lang="bash"><br />
root@imx6-openrex:~# lsmod<br />
Module Size Used by<br />
mxc_v4l2_capture 27624 2<br />
ipu_bg_overlay_sdc 5385 1 mxc_v4l2_capture<br />
ipu_still 2331 1 mxc_v4l2_capture<br />
ipu_prp_enc 5903 1 mxc_v4l2_capture<br />
ipu_csi_enc 3904 1 mxc_v4l2_capture<br />
ipu_fg_overlay_sdc 6130 1 mxc_v4l2_capture<br />
ov5647_camera_mipi_int 30566 0<br />
adv7610_video 6373 0<br />
v4l2_int_device 2872 4 ov5647_camera_mipi_int,adv7610_video,ipu_csi_enc,mxc_v4l2_capture<br />
mxc_dcic 6528 0<br />
<br />
<br />
<br />
root@imx8mq-voipac:~# lsmod<br />
Module Size Used by<br />
crct10dif_ce 16384 1<br />
mwifiex_pcie 45056 0<br />
mwifiex 294912 1 mwifiex_pcie<br />
galcore 610304 2<br />
<br />
</syntaxhighlight><br />
<br />
== Resolution setting ==<br />
=== 1280x960 ===<br />
<syntaxhighlight lang="bash"><br />
echo 0 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1280x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 1 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1920x1080 ===<br />
<syntaxhighlight lang="bash"><br />
echo 2 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 ===<br />
<syntaxhighlight lang="bash"><br />
echo 3 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1024x768 (default) ===<br />
<syntaxhighlight lang="bash"><br />
echo 4 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 960x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 5 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 (narrow angle of view) ===<br />
<syntaxhighlight lang="bash"><br />
echo 6 > /sys/bus/i2c/devices/1-0036/ov5647_mode <br />
</syntaxhighlight><br />
<br />
== Gstreamer ==<br />
=== Capture single JPEG picture ===<br />
<syntaxhighlight lang="bash"><br />
echo 2 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
gst-launch-1.0 v4l2src device="/dev/video1" num-buffers=1 ! video/x-bayer,width=1920,height=1080,framerate=30/1 ! bayer2rgb ! videoconvert ! jpegenc ! filesink location=sample_1920_1080.jpeg<br />
</syntaxhighlight><br />
<br />
=== Video preview ===<br />
<syntaxhighlight lang="bash"><br />
echo 2 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
gst-launch-1.0 v4l2src device="/dev/video1" ! video/x-bayer,width=1920,height=1080,framerate=30/1 ! queue ! bayer2rgb ! videoconvert ! fbdevsink<br />
</syntaxhighlight><br />
<br />
<syntaxhighlight lang="bash"><br />
echo 3 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
gst-launch-1.0 v4l2src device="/dev/video1" ! video/x-bayer,width=640,height=480,framerate=15/1 ! bayer2rgb ! videoconvert ! fbdevsink<br />
</syntaxhighlight></div>
Voipac-hw
https://wiki.voipac.com/index.php?title=NXP_MIPI-CSI_Camera_Set&diff=3859
NXP MIPI-CSI Camera Set
2022-07-22T19:46:15Z
<p>Voipac-hw: </p>
<hr />
<div>[[Category:iMX8M Industrial Development Kit]]<br />
[[Category:iMX8M Industrial Peripherals]]<br />
<!-- --><br />
<div style="float:right">__TOC__</div><br />
<br />
MINISASTOCSI is a MIPI-CSI interface camera kit, based on OmniVision chipset OV5640 Detection, performance and essential commands are described here.<br />
<br /><br /><br />
[[image:hot-plug.png|400px]]<br />
<br /><br /><br />
[[image:MINISASTOCSI-Voipac-BB.png|800px]]<br /><br />
MINISASTOCSI is a MIPI-CSI interface camera connected to iMX8M Development Baseboard <br />
<br /><br />
<br />
== Kernel detection ==<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# dmesg | grep ov56<br />
[ 2.398433] ov5640_mipi 1-003c: No pin available<br />
[ 2.403090] ov5640_mipi 1-003c: No sensor pwdn pin available<br />
[ 2.408777] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 2.414571] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.539603] ov5640_mipi 2-003c: No pin available<br />
[ 2.549079] ov5640_mipi 2-003c: No sensor reset pin available<br />
[ 2.554887] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.999855] ov5640_mipi 1-003c: No pin available<br />
[ 3.005558] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 3.012003] ov5640_mipi 1-003c: 1-003c supply DVDD not found, using dummy regulator<br />
[ 3.019785] ov5640_mipi 1-003c: 1-003c supply AVDD not found, using dummy regulator<br />
[ 3.039290] ov5640_mipi 1-003c: Read reg error: reg=300a<br />
[ 3.044691] ov5640_mipi 1-003c: Camera is not found<br />
[ 3.051918] ov5640_mipi 2-003c: No pin available<br />
[ 3.062814] ov5640_mipi 2-003c: No sensor reset pin available<br />
[ 3.069209] ov5640_mipi 2-003c: 2-003c supply DVDD not found, using dummy regulator<br />
[ 3.076945] ov5640_mipi 2-003c: 2-003c supply AVDD not found, using dummy regulator<br />
[ 4.291092] mxc-mipi-csi2_yav 30a70000.mipi_csi: Registered sensor subdevice: ov5640_mipi 2-003c<br />
[ 4.304334] ov5640_mipi 2-003c: Camera is found<br />
</syntaxhighlight><br />
<br />
== I2C detection ==<br />
MINISASTOCSI camera chip is connected via I2C3. The most important address for correct detection is 0x3c.<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# i2cdetect -y 2<br />
0 1 2 3 4 5 6 7 8 9 a b c d e f<br />
00: -- -- -- -- -- -- -- -- -- -- -- -- --<br />
10: UU UU UU UU -- -- -- -- -- -- -- -- -- -- -- --<br />
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
30: -- -- -- -- -- -- -- -- -- -- -- -- UU -- -- --<br />
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
70: -- -- -- -- -- -- -- --<br />
</syntaxhighlight><br />
<br />
MINISASTOCSI camera can be also connected to I2C2 interface by moving 0R resistors. However second camera connected on CSI-2 interface have same address 0x3c as MINISASTOCSI camera connected on CSI-1 interface. <br />
[[image:CSI1-I2C2 and I2C3.png|800px]]<br />
<br />
== Modules listing ==<br />
=== Kernel 4.1 ===<br />
<syntaxhighlight lang="bash"><br />
root@imx6-openrex:~# lsmod<br />
Module Size Used by<br />
mxc_v4l2_capture 27624 2<br />
ipu_bg_overlay_sdc 5385 1 mxc_v4l2_capture<br />
ipu_still 2331 1 mxc_v4l2_capture<br />
ipu_prp_enc 5903 1 mxc_v4l2_capture<br />
ipu_csi_enc 3904 1 mxc_v4l2_capture<br />
ipu_fg_overlay_sdc 6130 1 mxc_v4l2_capture<br />
ov5647_camera_mipi_int 30566 0<br />
adv7610_video 6373 0<br />
v4l2_int_device 2872 4 ov5647_camera_mipi_int,adv7610_video,ipu_csi_enc,mxc_v4l2_capture<br />
mxc_dcic 6528 0<br />
</syntaxhighlight><br />
<br />
== Resolution setting ==<br />
=== 1280x960 ===<br />
<syntaxhighlight lang="bash"><br />
echo 0 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1280x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 1 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1920x1080 ===<br />
<syntaxhighlight lang="bash"><br />
echo 2 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 ===<br />
<syntaxhighlight lang="bash"><br />
echo 3 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1024x768 (default) ===<br />
<syntaxhighlight lang="bash"><br />
echo 4 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 960x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 5 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 (narrow angle of view) ===<br />
<syntaxhighlight lang="bash"><br />
echo 6 > /sys/bus/i2c/devices/1-0036/ov5647_mode <br />
</syntaxhighlight><br />
<br />
== Gstreamer ==<br />
=== Capture single JPEG picture ===<br />
<syntaxhighlight lang="bash"><br />
echo 2 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
gst-launch-1.0 v4l2src device="/dev/video1" num-buffers=1 ! video/x-bayer,width=1920,height=1080,framerate=30/1 ! bayer2rgb ! videoconvert ! jpegenc ! filesink location=sample_1920_1080.jpeg<br />
</syntaxhighlight><br />
<br />
=== Video preview ===<br />
<syntaxhighlight lang="bash"><br />
echo 2 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
gst-launch-1.0 v4l2src device="/dev/video1" ! video/x-bayer,width=1920,height=1080,framerate=30/1 ! queue ! bayer2rgb ! videoconvert ! fbdevsink<br />
</syntaxhighlight><br />
<br />
<syntaxhighlight lang="bash"><br />
echo 3 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
gst-launch-1.0 v4l2src device="/dev/video1" ! video/x-bayer,width=640,height=480,framerate=15/1 ! bayer2rgb ! videoconvert ! fbdevsink<br />
</syntaxhighlight></div>
Voipac-hw
https://wiki.voipac.com/index.php?title=NXP_MIPI-CSI_Camera_Set&diff=3858
NXP MIPI-CSI Camera Set
2022-07-22T19:45:42Z
<p>Voipac-hw: /* Modules listing */</p>
<hr />
<div>[[Category:iMX8M Industrial Development Kit]]<br />
[[Category:iMX8M Industrial Peripherals]]<br />
<!-- --><br />
<div style="float:right">__TOC__</div><br />
<br />
MINISASTOCSI is a MIPI-CSI interface camera kit, based on OmniVision chipset OV5640 Detection, performance and essential commands are described here.<br />
<br /><br /><br />
[[image:hot-plug.png|400px]]<br />
<br /><br /><br />
[[image:MINISASTOCSI-Voipac-BB.png|800px]]<br /><br />
MINISASTOCSI is a MIPI-CSI interface camera connected to iMX8M Development Baseboard <br />
<br /><br />
<br />
== Kernel detection ==<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# dmesg | grep ov56<br />
[ 2.398433] ov5640_mipi 1-003c: No pin available<br />
[ 2.403090] ov5640_mipi 1-003c: No sensor pwdn pin available<br />
[ 2.408777] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 2.414571] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.539603] ov5640_mipi 2-003c: No pin available<br />
[ 2.549079] ov5640_mipi 2-003c: No sensor reset pin available<br />
[ 2.554887] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.999855] ov5640_mipi 1-003c: No pin available<br />
[ 3.005558] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 3.012003] ov5640_mipi 1-003c: 1-003c supply DVDD not found, using dummy regulator<br />
[ 3.019785] ov5640_mipi 1-003c: 1-003c supply AVDD not found, using dummy regulator<br />
[ 3.039290] ov5640_mipi 1-003c: Read reg error: reg=300a<br />
[ 3.044691] ov5640_mipi 1-003c: Camera is not found<br />
[ 3.051918] ov5640_mipi 2-003c: No pin available<br />
[ 3.062814] ov5640_mipi 2-003c: No sensor reset pin available<br />
[ 3.069209] ov5640_mipi 2-003c: 2-003c supply DVDD not found, using dummy regulator<br />
[ 3.076945] ov5640_mipi 2-003c: 2-003c supply AVDD not found, using dummy regulator<br />
[ 4.291092] mxc-mipi-csi2_yav 30a70000.mipi_csi: Registered sensor subdevice: ov5640_mipi 2-003c<br />
[ 4.304334] ov5640_mipi 2-003c: Camera is found<br />
</syntaxhighlight><br />
<br />
== I2C detection ==<br />
MINISASTOCSI camera chip is connected via I2C3. The most important address for correct detection is 0x3c.<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# i2cdetect -y 2<br />
0 1 2 3 4 5 6 7 8 9 a b c d e f<br />
00: -- -- -- -- -- -- -- -- -- -- -- -- --<br />
10: UU UU UU UU -- -- -- -- -- -- -- -- -- -- -- --<br />
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
30: -- -- -- -- -- -- -- -- -- -- -- -- UU -- -- --<br />
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
70: -- -- -- -- -- -- -- --<br />
</syntaxhighlight><br />
<br />
MINISASTOCSI camera can be also connected to I2C2 interface by moving 0R resistors. However second camera connected on CSI-2 interface have same address 0x3c as MINISASTOCSI camera connected on CSI-1 interface. <br />
[[image:CSI1-I2C2 and I2C3.png|800px]]<br />
<br />
== GPIO control ==<br />
GPIO pins are controlled by the camera driver and access to these pins is blocked. Power on signal is recognised as GPIO 198, LED GPIO has number 199.<br /><br /><br />
<br />
LED located on camera module can be tested by temporarily disabling mipi kernel module and toggling corresponding GPIO pin:<br />
<syntaxhighlight lang="bash"><br />
root@imx6s-openrex:~# modprobe -r ov5647_camera_mipi<br />
root@imx6s-openrex:~# echo 199 > /sys/class/gpio/export<br />
root@imx6s-openrex:~# echo out > /sys/class/gpio/gpio199/direction<br />
root@imx6s-openrex:~# echo 1 > /sys/class/gpio/gpio199/value<br />
root@imx6s-openrex:~# echo 0 > /sys/class/gpio/gpio199/value<br />
root@imx6s-openrex:~# echo 199 > /sys/class/gpio/unexport<br />
root@imx6s-openrex:~# modprobe ov5647_camera_mipi<br />
</syntaxhighlight><br />
<br />
== Modules listing ==<br />
=== Kernel 4.1 ===<br />
<syntaxhighlight lang="bash"><br />
root@imx6-openrex:~# lsmod<br />
Module Size Used by<br />
mxc_v4l2_capture 27624 2<br />
ipu_bg_overlay_sdc 5385 1 mxc_v4l2_capture<br />
ipu_still 2331 1 mxc_v4l2_capture<br />
ipu_prp_enc 5903 1 mxc_v4l2_capture<br />
ipu_csi_enc 3904 1 mxc_v4l2_capture<br />
ipu_fg_overlay_sdc 6130 1 mxc_v4l2_capture<br />
ov5647_camera_mipi_int 30566 0<br />
adv7610_video 6373 0<br />
v4l2_int_device 2872 4 ov5647_camera_mipi_int,adv7610_video,ipu_csi_enc,mxc_v4l2_capture<br />
mxc_dcic 6528 0<br />
</syntaxhighlight><br />
<br />
== Resolution setting ==<br />
=== 1280x960 ===<br />
<syntaxhighlight lang="bash"><br />
echo 0 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1280x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 1 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1920x1080 ===<br />
<syntaxhighlight lang="bash"><br />
echo 2 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 ===<br />
<syntaxhighlight lang="bash"><br />
echo 3 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1024x768 (default) ===<br />
<syntaxhighlight lang="bash"><br />
echo 4 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 960x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 5 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 (narrow angle of view) ===<br />
<syntaxhighlight lang="bash"><br />
echo 6 > /sys/bus/i2c/devices/1-0036/ov5647_mode <br />
</syntaxhighlight><br />
<br />
== Gstreamer ==<br />
=== Capture single JPEG picture ===<br />
<syntaxhighlight lang="bash"><br />
echo 2 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
gst-launch-1.0 v4l2src device="/dev/video1" num-buffers=1 ! video/x-bayer,width=1920,height=1080,framerate=30/1 ! bayer2rgb ! videoconvert ! jpegenc ! filesink location=sample_1920_1080.jpeg<br />
</syntaxhighlight><br />
<br />
=== Video preview ===<br />
<syntaxhighlight lang="bash"><br />
echo 2 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
gst-launch-1.0 v4l2src device="/dev/video1" ! video/x-bayer,width=1920,height=1080,framerate=30/1 ! queue ! bayer2rgb ! videoconvert ! fbdevsink<br />
</syntaxhighlight><br />
<br />
<syntaxhighlight lang="bash"><br />
echo 3 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
gst-launch-1.0 v4l2src device="/dev/video1" ! video/x-bayer,width=640,height=480,framerate=15/1 ! bayer2rgb ! videoconvert ! fbdevsink<br />
</syntaxhighlight></div>
Voipac-hw
https://wiki.voipac.com/index.php?title=NXP_MIPI-CSI_Camera_Set&diff=3857
NXP MIPI-CSI Camera Set
2022-07-22T19:44:19Z
<p>Voipac-hw: </p>
<hr />
<div>[[Category:iMX8M Industrial Development Kit]]<br />
[[Category:iMX8M Industrial Peripherals]]<br />
<!-- --><br />
<div style="float:right">__TOC__</div><br />
<br />
MINISASTOCSI is a MIPI-CSI interface camera kit, based on OmniVision chipset OV5640 Detection, performance and essential commands are described here.<br />
<br /><br /><br />
[[image:hot-plug.png|400px]]<br />
<br /><br /><br />
[[image:MINISASTOCSI-Voipac-BB.png|800px]]<br /><br />
MINISASTOCSI is a MIPI-CSI interface camera connected to iMX8M Development Baseboard <br />
<br /><br />
<br />
== Kernel detection ==<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# dmesg | grep ov56<br />
[ 2.398433] ov5640_mipi 1-003c: No pin available<br />
[ 2.403090] ov5640_mipi 1-003c: No sensor pwdn pin available<br />
[ 2.408777] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 2.414571] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.539603] ov5640_mipi 2-003c: No pin available<br />
[ 2.549079] ov5640_mipi 2-003c: No sensor reset pin available<br />
[ 2.554887] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.999855] ov5640_mipi 1-003c: No pin available<br />
[ 3.005558] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 3.012003] ov5640_mipi 1-003c: 1-003c supply DVDD not found, using dummy regulator<br />
[ 3.019785] ov5640_mipi 1-003c: 1-003c supply AVDD not found, using dummy regulator<br />
[ 3.039290] ov5640_mipi 1-003c: Read reg error: reg=300a<br />
[ 3.044691] ov5640_mipi 1-003c: Camera is not found<br />
[ 3.051918] ov5640_mipi 2-003c: No pin available<br />
[ 3.062814] ov5640_mipi 2-003c: No sensor reset pin available<br />
[ 3.069209] ov5640_mipi 2-003c: 2-003c supply DVDD not found, using dummy regulator<br />
[ 3.076945] ov5640_mipi 2-003c: 2-003c supply AVDD not found, using dummy regulator<br />
[ 4.291092] mxc-mipi-csi2_yav 30a70000.mipi_csi: Registered sensor subdevice: ov5640_mipi 2-003c<br />
[ 4.304334] ov5640_mipi 2-003c: Camera is found<br />
</syntaxhighlight><br />
<br />
== I2C detection ==<br />
MINISASTOCSI camera chip is connected via I2C3. The most important address for correct detection is 0x3c.<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# i2cdetect -y 2<br />
0 1 2 3 4 5 6 7 8 9 a b c d e f<br />
00: -- -- -- -- -- -- -- -- -- -- -- -- --<br />
10: UU UU UU UU -- -- -- -- -- -- -- -- -- -- -- --<br />
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
30: -- -- -- -- -- -- -- -- -- -- -- -- UU -- -- --<br />
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
70: -- -- -- -- -- -- -- --<br />
</syntaxhighlight><br />
<br />
MINISASTOCSI camera can be also connected to I2C2 interface by moving 0R resistors. However second camera connected on CSI-2 interface have same address 0x3c as MINISASTOCSI camera connected on CSI-1 interface. <br />
[[image:CSI1-I2C2 and I2C3.png|800px]]<br />
<br />
== GPIO control ==<br />
GPIO pins are controlled by the camera driver and access to these pins is blocked. Power on signal is recognised as GPIO 198, LED GPIO has number 199.<br /><br /><br />
<br />
LED located on camera module can be tested by temporarily disabling mipi kernel module and toggling corresponding GPIO pin:<br />
<syntaxhighlight lang="bash"><br />
root@imx6s-openrex:~# modprobe -r ov5647_camera_mipi<br />
root@imx6s-openrex:~# echo 199 > /sys/class/gpio/export<br />
root@imx6s-openrex:~# echo out > /sys/class/gpio/gpio199/direction<br />
root@imx6s-openrex:~# echo 1 > /sys/class/gpio/gpio199/value<br />
root@imx6s-openrex:~# echo 0 > /sys/class/gpio/gpio199/value<br />
root@imx6s-openrex:~# echo 199 > /sys/class/gpio/unexport<br />
root@imx6s-openrex:~# modprobe ov5647_camera_mipi<br />
</syntaxhighlight><br />
<br />
== Modules listing ==<br />
=== Kernel 4.1 ===<br />
<syntaxhighlight lang="bash"><br />
root@imx6-openrex:~# lsmod<br />
Module Size Used by<br />
mxc_v4l2_capture 27624 2<br />
ipu_bg_overlay_sdc 5385 1 mxc_v4l2_capture<br />
ipu_still 2331 1 mxc_v4l2_capture<br />
ipu_prp_enc 5903 1 mxc_v4l2_capture<br />
ipu_csi_enc 3904 1 mxc_v4l2_capture<br />
ipu_fg_overlay_sdc 6130 1 mxc_v4l2_capture<br />
ov5647_camera_mipi_int 30566 0<br />
adv7610_video 6373 0<br />
v4l2_int_device 2872 4 ov5647_camera_mipi_int,adv7610_video,ipu_csi_enc,mxc_v4l2_capture<br />
mxc_dcic 6528 0<br />
</syntaxhighlight><br />
<br />
=== Kernel 3.14 ===<br />
<syntaxhighlight lang="bash"><br />
root@imx6s-openrex:~# lsmod<br />
Module Size Used by<br />
mxc_v4l2_capture 28532 1 <br />
ipu_bg_overlay_sdc 5401 1 mxc_v4l2_capture<br />
ipu_still 2528 1 mxc_v4l2_capture<br />
ipu_prp_enc 5943 1 mxc_v4l2_capture<br />
ipu_csi_enc 3863 1 mxc_v4l2_capture<br />
ipu_fg_overlay_sdc 6217 1 mxc_v4l2_capture<br />
ov5647_camera_mipi 30906 0 <br />
v4l2_int_device 2930 2 ov5647_camera_mipi,mxc_v4l2_capture<br />
mxc_dcic 6569 0 <br />
evbug 1875 0<br />
</syntaxhighlight><br />
<br />
== Resolution setting ==<br />
=== 1280x960 ===<br />
<syntaxhighlight lang="bash"><br />
echo 0 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1280x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 1 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1920x1080 ===<br />
<syntaxhighlight lang="bash"><br />
echo 2 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 ===<br />
<syntaxhighlight lang="bash"><br />
echo 3 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1024x768 (default) ===<br />
<syntaxhighlight lang="bash"><br />
echo 4 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 960x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 5 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 (narrow angle of view) ===<br />
<syntaxhighlight lang="bash"><br />
echo 6 > /sys/bus/i2c/devices/1-0036/ov5647_mode <br />
</syntaxhighlight><br />
<br />
== Gstreamer ==<br />
=== Capture single JPEG picture ===<br />
<syntaxhighlight lang="bash"><br />
echo 2 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
gst-launch-1.0 v4l2src device="/dev/video1" num-buffers=1 ! video/x-bayer,width=1920,height=1080,framerate=30/1 ! bayer2rgb ! videoconvert ! jpegenc ! filesink location=sample_1920_1080.jpeg<br />
</syntaxhighlight><br />
<br />
=== Video preview ===<br />
<syntaxhighlight lang="bash"><br />
echo 2 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
gst-launch-1.0 v4l2src device="/dev/video1" ! video/x-bayer,width=1920,height=1080,framerate=30/1 ! queue ! bayer2rgb ! videoconvert ! fbdevsink<br />
</syntaxhighlight><br />
<br />
<syntaxhighlight lang="bash"><br />
echo 3 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
gst-launch-1.0 v4l2src device="/dev/video1" ! video/x-bayer,width=640,height=480,framerate=15/1 ! bayer2rgb ! videoconvert ! fbdevsink<br />
</syntaxhighlight></div>
Voipac-hw
https://wiki.voipac.com/index.php?title=NXP_MIPI-CSI_Camera_Set&diff=3856
NXP MIPI-CSI Camera Set
2022-07-22T19:41:43Z
<p>Voipac-hw: </p>
<hr />
<div>[[Category:iMX8M Industrial Development Kit]]<br />
[[Category:iMX8M Industrial Peripherals]]<br />
<!-- --><br />
<div style="float:right">__TOC__</div><br />
<br />
MINISASTOCSI is a MIPI-CSI interface camera kit, based on OmniVision chipset OV5640 Detection, performance and essential commands are described here.<br />
<br /><br /><br />
[[image:hot-plug.png|400px]]<br />
<br /><br /><br />
[[image:MINISASTOCSI-Voipac-BB.png|800px]]<br /><br />
MINISASTOCSI is a MIPI-CSI interface camera connected to iMX8M Development Baseboard <br />
<br /><br />
<br />
== Kernel detection ==<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# dmesg | grep ov56<br />
[ 2.398433] ov5640_mipi 1-003c: No pin available<br />
[ 2.403090] ov5640_mipi 1-003c: No sensor pwdn pin available<br />
[ 2.408777] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 2.414571] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.539603] ov5640_mipi 2-003c: No pin available<br />
[ 2.549079] ov5640_mipi 2-003c: No sensor reset pin available<br />
[ 2.554887] ov5640_regulator_enable: cannot get io voltage error - err:-517<br />
[ 2.999855] ov5640_mipi 1-003c: No pin available<br />
[ 3.005558] ov5640_mipi 1-003c: No sensor reset pin available<br />
[ 3.012003] ov5640_mipi 1-003c: 1-003c supply DVDD not found, using dummy regulator<br />
[ 3.019785] ov5640_mipi 1-003c: 1-003c supply AVDD not found, using dummy regulator<br />
[ 3.039290] ov5640_mipi 1-003c: Read reg error: reg=300a<br />
[ 3.044691] ov5640_mipi 1-003c: Camera is not found<br />
[ 3.051918] ov5640_mipi 2-003c: No pin available<br />
[ 3.062814] ov5640_mipi 2-003c: No sensor reset pin available<br />
[ 3.069209] ov5640_mipi 2-003c: 2-003c supply DVDD not found, using dummy regulator<br />
[ 3.076945] ov5640_mipi 2-003c: 2-003c supply AVDD not found, using dummy regulator<br />
[ 4.291092] mxc-mipi-csi2_yav 30a70000.mipi_csi: Registered sensor subdevice: ov5640_mipi 2-003c<br />
[ 4.304334] ov5640_mipi 2-003c: Camera is found<br />
</syntaxhighlight><br />
<br />
== I2C detection ==<br />
MINISASTOCSI camera chip is connected via I2C3. The most important address for correct detection is 0x3c.<br />
<syntaxhighlight lang="bash"><br />
root@imx8mq-voipac:~# i2cdetect -y 2<br />
0 1 2 3 4 5 6 7 8 9 a b c d e f<br />
00: -- -- -- -- -- -- -- -- -- -- -- -- --<br />
10: UU UU UU UU -- -- -- -- -- -- -- -- -- -- -- --<br />
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
30: -- -- -- -- -- -- -- -- -- -- -- -- UU -- -- --<br />
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br />
70: -- -- -- -- -- -- -- --<br />
</syntaxhighlight><br />
<br />
MINISASTOCSI camera can be also connected to I2C2 interface by moving 0R resistors. However second camera connected on CSI-2 interface have same address 0x3c as MINISASTOCSI camera connected on CSI-1 interface. <br />
[[image:CSI1-I2C2 and I2C3.png|800px]]<br />
<br />
== Resolution setting ==<br />
=== 1280x960 ===<br />
<syntaxhighlight lang="bash"><br />
echo 0 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1280x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 1 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1920x1080 ===<br />
<syntaxhighlight lang="bash"><br />
echo 2 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 ===<br />
<syntaxhighlight lang="bash"><br />
echo 3 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 1024x768 (default) ===<br />
<syntaxhighlight lang="bash"><br />
echo 4 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 960x720 ===<br />
<syntaxhighlight lang="bash"><br />
echo 5 > /sys/bus/i2c/devices/1-0036/ov5647_mode<br />
</syntaxhighlight><br />
<br />
=== 640x480 (narrow angle of view) ===<br />
<syntaxhighlight lang="bash"><br />
echo 6 > /sys/bus/i2c/devices/1-0036/ov5647_mode <br />
</syntaxhighlight></div>
Voipac-hw