Compulab Mediawiki - User contributions [en]

CL-SOM-iMX8Plus: Yocto Linux: Known Issues

2023-07-17T07:12:07Z

Benjamin:

'''Kernel'''
* MIPI Display backlight does not work. A solution will be provided in the next release.
* LVDS Display backlight does not work. A solution will be provided in the next release.

[[Category:Yocto]]
[[Category:CL-SOM-iMX8Plus]]

CL-SOM-iMX8Plus: Yocto Linux: How-To Guide

2023-07-16T10:35:46Z

Benjamin:

=Device Tree=
The current release comes with these dtb files:
{| class="wikitable" style="text-align:left;"
|-
| align="" | '''DTB'''
| align="" | '''HW Feature'''
| align="" | '''Jumpers'/Interface Settings'''
|-
| align="" |som-imx8m-plus.dtb
| align="" |default hardware configuration; mipi dsi, lvds and hdmi enabled
|-
| align="" |som-imx8m-plus_mipi-csi1.dtb
| align="" |default hardware configuration + mipi csi1 enabled + ar1335_af sensor on the P48;
| align="" |E18 is on
|-
| align="" |som-imx8m-plus_mipi-csi2.dtb
| align="" |default hardware configuration + mipi csi2 enabled + ar1335_af sensor on the P47;
| align="" |E23 is on
|-
| align="" |som-imx8m-plus-usbdev.dtb
| align="" |default hardware configuration + USB1 as a peripheral;
| align="" |J5 is in use
|-
| align="" |som-imx8m-plus-hdmi.dtb
| align="" |default hardware configuration w/out lvds and mipi dsi; hdmi display only;
| align="" |P14 is in use
|-
| align="" |som-imx8m-plus-lvds.dtb
| align="" |default hardware configuration w/out hdmi and mipi dsi; lvds display only;
| align="" |P11/P5 lvds iface/touch is in use
|-
| align="" |som-imx8m-plus-mipi.dtb
| align="" |default hardware configuration w/out hdmi and lvds; mipi dsi display only;
| align="" |P22/P45 mipi iface/touch is in use
|-
| align="" |som-imx8m-plus_mipi-csi1-imx219.dtb
| align="" |default hardware configuration + mipi csi1 enabled + imx219 sensor on the P49;
| align="" |E18 is off
|-
|}

==Set a device tree==
The current release provides two methods to switch between dtb files:
* U-Boot environment
The U-boot '''fdtfile''' variable contains the device tree name that will be loaded into the RAM.
This variable can be changed by:
{| class="wikitable" style="text-align:left;"
|-
| align="" | '''Environment'''
| align="" | '''Command'''
|-
| align="" |U-Boot
| align="" |setenv fdtfile <fdt_file_name>; saveenv;
|-
| align="" |Linux
| align="" |cl_setenv fdtfile <fdt_file_name>
|-
|}
* GRUB environment (if the image was created with the meta-compulab-uefi layer)
{| class="wikitable" style="text-align:left;"
|-
| align="" | '''Environment'''
| align="" | '''Command/Procedure'''
|-
| align="" |GRUB Boot Menu
| align="" |Goto "Advanced Boot Options" and choose a device tree from the provided dtb list.
|-
| align="" |Linux
| align="" |grub-editenv /boot/EFI/BOOT/grubenv set fdtfile=<fdt_file_name>
|-
|}

=Controller–area network (CAN)=
CL-SOM-iMX8Plus features two Flexible Controller Area Network (FLEXCAN) modules.
The FlexCAN module is a full implementation of the CAN protocol specification, the
CAN with Flexible Data rate (CAN FD) protocol, and the CAN 2.0 version B protocol,
which supports both standard and extended message frames and long payloads up to 64
bytes, transferred at faster rates (up to 8 Mb/s).

==CAN interface configuration==
It is recommended to configure the CAN interface, with the {{filename|iproute2}} utilities.

* To make sure the right '''ip''' utility is used, run:
<pre>
ip -V
ip utility, iproute2-v5.7.0-77-gb687d1067169
</pre>
* Configure both CAN interface bit-rate to 1 Mbit/sec:
<pre>
ip link set can0 type can bitrate 1000000
ip link set can1 type can bitrate 1000000
</pre>
* Enable the CAN interface:
<pre>
ip link set can0 up
ip link set can1 up
</pre>

==Send/Receive packets==
Use {{filename|cansend}} and {{filename|candump}} utilities to send and receive packets via CAN interface.

* Send standard CAN frame (on the first device):
<pre>
cansend can0 111#1122334455667788
</pre>

* Send extended CAN frame (on the first device):
<pre>
cansend can0 11111111#1122334455667788
</pre>

* CAN frames (extended mode) generator, random payload, the interval between two successive flames 50 msec:
<pre>
cangen -g 50 -e -D r -v can0

can: raw protocol (rev 20170425)
...
can0 03FF0983#D7.61.FF.03.C1.F7.C1.34
can0 19C34D32#F7.5A.C2.73.AD.0E.3F.0B
can0 0675E391#2B.2D.D3.49
can0 13091C55#99.32.EC.77.27.81.49.0B
can0 098D67CF#22.50.AB.48.AD.7F.F4.26
can0 05263FEC#1B.4C.02.45.6E
can0 12B30E20#
can0 1F193DF9#C5
can0 1EB0B18F#3E.3F.DA.57.C2.FE.73.58
can0 1E5C64D9#6F.0D.B3.63.6A
can0 1E1DE3F9#96.48.AC.79.4E.00.27.71
can0 0E1A11B7#75.81.70.7C.86.79.A7.77
can0 05F8FD8B#33.F9.9B.1E.77.3D.1F
can0 1E155FCD#E6.BA.F8.58.ED.6D.C8.10
can0 1D91DF9E#5D.29.82.7B.97.1D.AB.5C
can0 11FB3CDA#14.65.C3
can0 091352C0#2C.ED
...
</pre>

* Dump all received data frames as well as error frames (on the second device):
<pre>
candump any,0:0,#FFFFFFFF

can0 111 [8] 11 22 33 44 55 66 77 88
can0 11111111 [8] 11 22 33 44 55 66 77 88
...
can0 03FF0983 [8] D7 61 FF 03 C1 F7 C1 34
can0 19C34D32 [8] F7 5A C2 73 AD 0E 3F 0B
can0 0675E391 [4] 2B 2D D3 49
can0 13091C55 [8] 99 32 EC 77 27 81 49 0B
can0 098D67CF [8] 22 50 AB 48 AD 7F F4 26
can0 05263FEC [5] 1B 4C 02 45 6E
can0 12B30E20 [0]
can0 1F193DF9 [1] C5
can0 1EB0B18F [8] 3E 3F DA 57 C2 FE 73 58
can0 1E5C64D9 [5] 6F 0D B3 63 6A
can0 1E1DE3F9 [8] 96 48 AC 79 4E 00 27 71
can0 0E1A11B7 [8] 75 81 70 7C 86 79 A7 77
can0 05F8FD8B [7] 33 F9 9B 1E 77 3D 1F
can0 1E155FCD [8] E6 BA F8 58 ED 6D C8 10
can0 1D91DF9E [8] 5D 29 82 7B 97 1D AB 5C
can0 11FB3CDA [3] 14 65 C3
can0 091352C0 [2] 2C ED
...
</pre>

= WiFi =

CL-SOM-iMX8Plus features 802.11ac wireless connectivity solution implemented with an NXP 88W8997 module.

== WiFi Initialization ==
WiFi requires no user interaction for being configured.
* The driver gets loaded automatically. Use this command to show the loaded drivers:
'''lsmod | grep mwifiex'''
<pre>
mwifiex_sdio 40960 0
mwifiex 274432 1 mwifiex_sdio
</pre>
* The WiFi driver can be loaded manually:
'''modprobe mwifiex'''
'''modprobe mwifiex_sdio'''
<pre>
mwifiex_sdio mmc0:0001:1: info: FW download over, size 623240 bytes
mwifiex_sdio mmc0:0001:1: WLAN FW is active
mwifiex_sdio mmc0:0001:1: info: MWIFIEX VERSION: mwifiex 1.0 (16.68.1.p197)
mwifiex_sdio mmc0:0001:1: driver_version = mwifiex 1.0 (16.68.1.p197)
</pre>
* Browse the WiFi module configuration:
'''iwconfig mlan0'''
<pre>
mlan0 IEEE 802.11 ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm
Retry short limit:9 RTS thr=2347 B Fragment thr=2346 B
Encryption key:off
Power Management:on
</pre>
* Activate the interface:
'''ifconfig mlan0 up'''
* Sample WiFi scanning:
'''iw mlan0 scan'''
The output will show the list of Access Points and Ad-Hoc cells in range.
For more information about connecting to wireless networks and tuning WiFi interfaces refer to “wpa_supplicant” and “wireless-tools” man pages.

== wpa_supplicant ==
* Create a {{cmd|wpa_supplicant}} configuration file:
<pre>
cat << eof > /etc/wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
update_config=1
eof
</pre>
* Issue {{cmd|wpa_supplicant}}:
'''ifconfig mlan0 up'''
'''wpa_supplicant -B -Dnl80211 -c /etc/wpa_supplicant.conf -i mlan0'''
* Configuring WiFi connection with {{cmd|wpa_cli}}:
'''wpa_cli'''
<pre>
Selected interface 'mlan0'

Interactive mode

> scan
> scan_results
bssid / frequency / signal level / flags / ssid
b8:08:cf:a0:7e:f4 5240 -83 [WPA2-PSK-CCMP][ESS] MYSSID
> add_network
0
> set_network 0 ssid "MYSSID"
> set_network 0 psk "passphrase"
> enable_network 0
> save_config
> quit
</pre>
* Browse the '''''/etc/wpa_supplicant.conf''''':
'''cat /etc/wpa_supplicant.conf'''
<pre>
ctrl_interface=/var/run/wpa_supplicant
update_config=1

network={
ssid="MYSSID"
psk="passphrase"
}
</pre>
* Get an ip-address:
'''udhcpc -i mlan0'''
<pre>
udhcpc: started, v1.33.1
udhcpc: sending discover
udhcpc: sending select for 172.16.11.28
udhcpc: lease of 172.16.11.28 obtained, lease time 7181
/etc/udhcpc.d/50default: Adding DNS 172.16.11.1
</pre>
* Get the connection status:
'''wpa_cli status'''
<pre>
Selected interface 'mlan0'
bssid=b8:08:cf:a0:7e:f4
freq=5240
ssid=MYSSID
id=0
mode=station
pairwise_cipher=CCMP
group_cipher=CCMP
key_mgmt=WPA2-PSK
wpa_state=COMPLETED
ip_address=172.16.11.28
p2p_device_address=ec:2e:98:d1:03:f7
address=ec:2e:98:d1:03:f7
uuid=3cb04c02-017b-5df7-af29-69f15c7449ed
</pre>

= Bluetooth =
CL-SOM-iMX8Plus features bluetooth connectivity solution implemented with an NXP 88W8997 module. 

{{Note|Before working with Bluetooth, please ensure that Bluetooth antenna is connected to the SOM.}}

To start '''bluetoothctl''' use the following command:
<pre>
bluetoothctl
</pre>

To start the scan process use the following commands:
<pre>
[bluetooth]# default-agent
[bluetooth]# power on
[bluetooth]# scan on
</pre>

Bluetooth device should be turned on and visible. Its MAC-adress and name should appear in '''bluetoothctl''' in following format:
<pre>
[CHG] Device AA:BB:CC:DD:EE:FF Name: Device_Name
</pre>

To pair with the Bluetooth device use the following command:
<pre>
pair AA:BB:CC:DD:EE:FF
</pre>

Where '''AA:BB:CC:DD:EE:FF''' is MAC-adress of the Bluetooth device.

To quit '''bluetoothctl''' use the following command:
<pre>
[Device_Name]# quit
</pre>

=Gstreamer=
Yocto Linux uses Gstreamer as a default multimedia framework. Here are some useful Gstreamer features:

Execute the following command to check all the source options:
gst-inspect-1.0 | grep source

Execute the following command to check all the sink options:
gst-inspect-1.0 | grep sink

==Analog Audio==
===List of available sound cards===
* aplay
<pre>
aplay -l

**** List of PLAYBACK Hardware Devices ****
card 0: imxaudioxcvr [imx-audio-xcvr], device 0: XCVR PCM snd-soc-dummy-dai-0 []
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: audiohdmi [audio-hdmi], device 0: imx8 hdmi i2s-hifi-0 []
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: somimx8mplus [som-imx8m-plus], device 0: 30c30000.sai-wm8731-hifi wm8731-hifi-0 []
Subdevices: 1/1
Subdevice #0: subdevice #0
</pre>
* procfs
<pre>
cat /proc/asound/cards

0 [imxaudioxcvr ]: imx-audio-xcvr - imx-audio-xcvr
compulab-som_imx8m_plus-
1 [audiohdmi ]: audio-hdmi - audio-hdmi
compulab-som_imx8m_plus-
2 [somimx8mplus ]: som-imx8m-plus - som-imx8m-plus
compulab-som_imx8m_plus-
</pre>

===Switch between the available output===
* cl-oselect allows select an output device:
<pre>
cl-oselect

1) alsa_output.platform-sound-hdmi.stereo-fallback
2) alsa_output.platform-sound-xcvr.iec958-stereo
3) alsa_output.platform-sound.analog-stereo
4) <<
Sound sink [ alsa_output.platform-sound.analog-stereo ] > 3
</pre>

===Audio playback===
* gplay-1.0 allows playing back media files:
<pre>
gplay-1.0 /path/to/media.file
</pre>

==Video Playback==
{{note|The operation below requires '''root''' access.}}

CL-SOM-iMX8Plus features 1080p60 H.264, VP8 video decoding capabilities. Before starting video playback, please, ensure that the display is connected to the board.

The following commands can be used to start video playback ('''1.mov''' is a media file):
* gst-play
<pre>
gst-play /path/to/1.mov
</pre>

* gplay-1.0
<pre>
gplay-1.0 /path/to/1.mov
</pre>

* gst-launch
This method is for advanced users. Please study this document before the start: [https://raw.githubusercontent.com/compulab-yokneam/Documentation/master/pdfs/i.MX8GStreamerUserGuide.pdf i.MX8GStreamerUserGuide.pdf]
<pre>
gst-launch-1.0 -v filesrc location=/path/to/1.mov ! qtdemux name=d.video_0 ! h264parse ! avdec_h264 ! autovideosink
</pre>

==Video Capturing==
{{note|The operation below requires '''root''' access.}}

===Requirements===
* hw: an sensor is connected to either P47 (MIPI_CSI2) or P48+E18 (MIPI_CSI1) port
* sw: a correct device tree is in use:
{| class="wikitable" style="text-align:left;"
|-
| align="" | '''Sensor'''
| align="" | '''CSI1 device tree'''
| align="" | '''CSI2 device tree'''
| align="" | '''Capture Driver'''
| align="" | '''Device Name'''
|-
| align="" |'''ar1335_af'''
| align="" |som-imx8m-plus_mipi-csi1.dtb
| align="" |som-imx8m-plus_mipi-csi2.dtb
| align="" |ISI
| align="" |/dev/video0
|-
| align="" |'''ar1335'''
| align="" |som-imx8m-plus_mipi-csi1-ar1335-mcu.dtb
| align="" |-
| align="" |ISI
| align="" |/dev/video0
|-
| align="" |'''ar0234'''
| align="" |som-imx8m-plus_mipi-csi1-ar0234.dtb
| align="" |som-imx8m-plus_mipi-csi2-ar0234.dtb
| align="" |ISI
| align="" |/dev/video0
|-
| align="" |'''imx219'''
| align="" |som-imx8m-plus_mipi-csi1-imx219.dtb
| align="" |-
| align="" |ISP
| align="" |/dev/video2
|-
|}
* sw: the '''mxc-isi-cap''' is registered:

===Discovery a capture device===
* ISI
<pre>
v4l2-ctl --list-devices

():
/dev/v4l-subdev0

mxc-isi-cap (platform:32e00000.isi:cap_devic):
/dev/video0

FSL Capture Media Device (platform:mxc-md):
/dev/media0
</pre>
* ISP
<pre>
v4l2-ctl --list-devices
():
/dev/v4l-subdev0
/dev/v4l-subdev2
/dev/v4l-subdev3

(csi0):
/dev/v4l-subdev1

FSL Capture Media Device (platform:mxc-md):
/dev/media0

VIV (platform:viv0):
/dev/video2

vsi_v4l2dec (platform:vsi_v4l2dec):
/dev/video1

vsi_v4l2enc (platform:vsi_v4l2enc):
/dev/video0

viv_media (platform:vvcam-video):
/dev/media1

</pre>

For hardware setup and camera connection instructions please refer to CL-SOM-iMX8Plus Hardware Guide.

===Examples===

Please set a correct '''capture_device''' environment variable.
{| class="wikitable" style="text-align:left;"
|-
| align="" | '''Capture Driver'''
| align="" | '''Device Name Environment Variable'''
|-
| align="" |ISI
| align="" |export capture_device=/dev/video0
|-
| align="" |ISP
| align="" |export capture_device=/dev/video2
|-
|}

The following commands should be used to start video capturing:

* filesink
Write stream to a file. In this example the encoded output gets saved in the '''1.mov''' media file.
<pre>
gst-launch-1.0 v4l2src device=${capture_device} ! 'video/x-raw,width=1280,height=720,format=NV12' ! vpuenc_h264 ! filesink location=/path/to/1.mov
</pre>

* waylandsink
Output to wayland surface.
<pre>
gst-launch-1.0 v4l2src device=${capture_device} ! 'video/x-raw,width=1280,height=720,format=NV12' ! waylandsink window-width=1280 window-height=720
</pre>
* autovideosink
Wrapper video sink for automatically detected video sink.
<pre>
gst-launch-1.0 v4l2src device=${capture_device} ! 'video/x-raw,width=1280,height=720,format=NV12' ! autovideosink
</pre>

* Single Image Capturing
<pre>
gst-launch v4l2src device=${capture_device} num-buffers=1 ! jpegenc ! filesink location=single_buffer.jpg
</pre>

==Video streaming==
{{note|The operation below requires '''root''' access.}}
The following command should be executed on CL-SOM-iMX8Plus to start video streaming:
gst-launch-1.0 v4l2src device=${capture_device} ! video/x-raw, width=640, height=480 ! jpegenc ! udpsink host='''127.0.0.1''' port='''1234'''
'''127.0.0.1''' is the IP address of the host PC, and '''1234''' is the host PC port.

The following command should be executed on host PC (Linux) to receive the video stream:
gst-launch-1.0 udpsrc port='''1234''' ! jpegdec ! autovideosink
'''1234''' is the host PC port.

=Suspend / Resume=
{{note|The operation below requires '''root''' access.}}

CL-SOM-iMX8Plus features suspend mode, which allows to minimize power consumption.

The following command should be used to enter suspend mode:
<pre>
echo mem >/sys/power/state
</pre>

To resume normal operation press shortly the '''Power On''' button '''SW5'''.

=CPU frequency=
{{note|The operation below requires '''root''' access.}}
==CPU frequency current settings==
Execute the following command to get the current settings:
<pre>
grep -ir . /sys/devices/system/cpu/cpufreq/policy0/ 2>/dev/null

/sys/devices/system/cpu/cpufreq/policy0/scaling_min_freq:1200000
/sys/devices/system/cpu/cpufreq/policy0/scaling_available_governors:conservative ondemand userspace powersave performance schedutil
/sys/devices/system/cpu/cpufreq/policy0/cpuinfo_cur_freq:1200000
/sys/devices/system/cpu/cpufreq/policy0/scaling_governor:ondemand
/sys/devices/system/cpu/cpufreq/policy0/cpuinfo_max_freq:1600000
/sys/devices/system/cpu/cpufreq/policy0/scaling_available_frequencies:1200000 1600000
/sys/devices/system/cpu/cpufreq/policy0/related_cpus:0 1 2 3
/sys/devices/system/cpu/cpufreq/policy0/scaling_cur_freq:1200000
/sys/devices/system/cpu/cpufreq/policy0/scaling_setspeed:<unsupported>
/sys/devices/system/cpu/cpufreq/policy0/stats/trans_table: From : To
/sys/devices/system/cpu/cpufreq/policy0/stats/trans_table: : 1200000 1600000
/sys/devices/system/cpu/cpufreq/policy0/stats/trans_table: 1200000: 0 65
/sys/devices/system/cpu/cpufreq/policy0/stats/trans_table: 1600000: 65 0
/sys/devices/system/cpu/cpufreq/policy0/stats/total_trans:130
/sys/devices/system/cpu/cpufreq/policy0/stats/time_in_state:1200000 643
/sys/devices/system/cpu/cpufreq/policy0/stats/time_in_state:1600000 474
/sys/devices/system/cpu/cpufreq/policy0/affected_cpus:0 1 2 3
/sys/devices/system/cpu/cpufreq/policy0/scaling_max_freq:1600000
/sys/devices/system/cpu/cpufreq/policy0/cpuinfo_transition_latency:182000
/sys/devices/system/cpu/cpufreq/policy0/scaling_driver:cpufreq-dt
/sys/devices/system/cpu/cpufreq/policy0/cpuinfo_min_freq:1200000
</pre>

==Changing the scaling governor==
Execute the following command to change the scaling governor:
<pre>
echo performance > /sys/devices/system/cpu/cpufreq/policy0/scaling_governor
</pre>

Where '''perfomance''' is name of the scaling governor.

Execute the following command to see available scaling governors:
<pre>
cat /sys/devices/system/cpu/cpufreq/policy0/scaling_available_governors
</pre>

Execute the following command to see current scaling governor:
<pre>
cat /sys/devices/system/cpu/cpufreq/policy0/scaling_governor
</pre>

==Changing CPU frequency==
{{note|CPU frequency can be changed only when the scaling governoris set to '''userspace'''.}}
Execute the following command to set CPU frequency:
<pre>
echo 1200000 > /sys/devices/system/cpu/cpufreq/policy0/scaling_setspeed
</pre>

'''1200000''' is one of the available CPU frequencies.

Execute the following command to see available CPU frequencies:
<pre>
cat /sys/devices/system/cpu/cpufreq/policy0/scaling_available_frequencies
</pre>

Execute the following command to see current CPU frequency:
<pre>
cat /sys/devices/system/cpu/cpufreq/policy0/cpuinfo_cur_freq
</pre>

=CPU temperature=
i.MX8M-Plus SoC features an internal temperature sensor which allows to measure the SoC temperature.
Execute the following command to read the current CPU temperature:
<pre>
cat /sys/class/thermal/thermal_zone0/temp
</pre>

=RTC=
There two rtc on the device:

==rtc0 (snvs-rtc-lp)==
* System information
<pre>
udevadm info -p /sys/class/rtc/rtc0

P: /devices/platform/soc@0/30000000.bus/30370000.snvs/30370000.snvs:snvs-rtc-lp/rtc/rtc0
N: rtc0
L: -100
S: rtc
E: DEVPATH=/devices/platform/soc@0/30000000.bus/30370000.snvs/30370000.snvs:snvs-rtc-lp/rtc/rtc0
E: DEVNAME=/dev/rtc0
E: MAJOR=251
E: MINOR=0
E: SUBSYSTEM=rtc
E: USEC_INITIALIZED=8188223
E: DEVLINKS=/dev/rtc
</pre>

* Wake up:
This rtc can be used as a wake up source, as a result an '''rtcwakeup''' can be used with this device:
<pre>
rtcwake --device /dev/rtc0 -s 5 -m mem
</pre>

==rtc1 (ab1805)==
* System information
<pre>
udevadm info -p /sys/class/rtc/rtc1

P: /devices/platform/soc@0/30800000.bus/30a30000.i2c/i2c-1/1-0069/rtc/rtc1
N: rtc1
L: 0
E: DEVPATH=/devices/platform/soc@0/30800000.bus/30a30000.i2c/i2c-1/1-0069/rtc/rtc1
E: DEVNAME=/dev/rtc1
E: MAJOR=251
E: MINOR=1
E: SUBSYSTEM=rtc
</pre>

* Set the date and write it into the RTC:
<pre>
date -s "12 SEP 2019 10:00:00"

Thu Sep 12 10:00:00 UTC 2019
hwclock --systohc --rtc /dev/rtc1
</pre>

* Read the RTC time and date:
<pre>
hwclock --show --rtc /dev/rtc1

Thu Sep 12 10:00:48 2019 0.000000 seconds
</pre>

= Device Serial Number and Configuration =
Product information is stored in on-board EEPROM. 
* To read the product serial number, issue the folowing command:
<pre>
compulab@som-imx8plus:~$ cat /proc/device-tree/product-sn
</pre>
* To read the product configuration part number, issue the following command:
<pre>
compulab@som-imx8plus:~$ cat /proc/device-tree/product-options
</pre>

=See Also=
*[[CL-SOM-iMX8Plus: Evaluation Kit: Getting Started | Getting started with CL-SOM-iMX8Plus Evaluation Kit]] 
* [[CL-SOM-iMX8Plus: Evaluation Kit: Hardware Guide|CL-SOM-iMX8Plus eval-kit hardware guide]]
[[Category:Yocto]]
[[Category:CL-SOM-iMX8Plus]]

CL-SOM-iMX8Plus NXP iMX8M-Plus Linux Resources

2023-07-16T08:37:39Z

Benjamin:

{{summary|
This page contains links to information about Yocto Linux distribution for the CompuLab CL-SOM-iMX8Plus System-on-Module.
Yocto Project is an open-source collaboration focused on embedded Linux development.

|CL-SOM-iMX8Plus System-on-Module.jpg|thumb}}
{{Resources Linux with app notes
|* [[CL-SOM-iMX8Plus: Evaluation Kit: Getting Started|Getting started with CL-SOM-iMX8Plus Evaluation Kit]]
* [[CL-SOM-iMX8Plus: Yocto Linux: Manual Installation: SD card|Installing Yocto on SD card]]
* [[CL-SOM-iMX8Plus: Yocto Linux: Installing Yocto images onto eMMC| Installing Yocto onto on-board eMMC]]
* [[CL-SOM-iMX8Plus: Yocto Linux: How-To Guide|Yocto Linux how-to guide]]
* [[CL-SOM-iMX8Plus: Yocto Linux: Package contents|Yocto Linux package contents]]
* [[CL-SOM-iMX8Plus: Yocto Linux: Known Issues|Known Issues]]
* [https://we.tl/t-R81S6cv3zm Latest Yocto package]
|* [[CL-SOM-iMX8Plus: Yocto Linux: Building CL-SOM-iMX8Plus Yocto images|Building CL-SOM-iMX8Plus Yocto Linux images]]
*[https://github.com/compulab-yokneam/meta-bsp-imx8mp/blob/som-imx8m-plus-r2.0/Documentation/linux_kernel_build.md Building CL-SOM-iMX8Plus Linux Kernel]
*[https://github.com/compulab-yokneam/meta-bsp-imx8mp/blob/som-imx8m-plus-r2.0/Documentation/imx_boot_image_build.md Building CL-SOM-iMX8Plus boot firmware]
*[[Application Notes: Introduction to Yocto development|Introduction to Yocto development]]
*[[Application Notes: Making Changes to Yocto Meta-Layers|Making Changes to Yocto Meta-Layers]]
|*[[Application Notes: Developing with Qt on CompuLab platforms|Developing with Qt on CompuLab platforms]]
*[[Application Notes: eMMC lifetime optimization|Optimizing eMMC lifetime and reliability]]
*[https://github.com/compulab-yokneam/meta-mender-compulab/blob/kirkstone-nxp/README.md Creating OTA update enabled images with Mender]
*[https://github.com/compulab-yokneam/meta-compulab-hab/blob/imx8/README.md Enabling secure boot (HAB) in Yocto]
}}

__NOTOC__

{{ChangelogReleaseNotesRss| content=
===== 16-Jul-2023, CL-SOM-iMX8MPlus Yocto Linux release 2.0 =====
: Release of Yocto 4.0 (Kirkstone)
: - Based on NXP release Kirkstone-5.15.71-2.0.0
: - Kernel 5.15.71 based on NXP lf-5.15.y
: - U-Boot 2021.04 based on NXP lf_v2021.04
: Supported HW features:
: - Enabled Bluetooth (NXP 88W8997)
: SW Features:
: - Enabled imx219 sensor support with imx8-isp
: Documentation:
: - Updated multiple articles to comply with the new release

===== 31-Mar-2022, CL-SOM-iMX8Plus Yocto Linux release 1.0 =====
: Release of Yocto 3.3 (Hadrknott) for CL-SOM-iMX8Plus
: - Based on NXP release 5.10.72-2.2.0
: - Kernel 5.10.72
: - U-Boot 2021.04
: Supported HW features:
: - Basic support for CL-SOM-iMX8Plus
: - USB2.0 OTG Host/Device
: - USB3.0 Host
: - PCIe, I2C, SPI
: - Storage: eMMC, uSD, EEPROM
: - Ethernet: ENET_QOS and ENET_FEC
: - FlexCAN: can0, can1
: - HDMI display interface
: - LVDS display interface
: - MIPI-DSI display interface
: - Touch screen support
: - CSI video camera interface
: - Wireless: WiFi (NXP 88W8997)
: - SNVS RTC
: - External RTC
: - Heartbeat LED
: SW Features:
: - CompuLab Deployment Tool
: - CompuLab U-Boot Tool
: - fw_printenv/fw_setenv/cl_setenv utilities provide R/W assess to U-Boot environment from Linux CLI
: - Chromium browser
: - Qt support
: Boot-loader features:
: - Supported memory configurations: 2GB, 4GB
: - Supported boot-loader devices: SD, eMMC
: - Supported linux/rootfs devices: SD, eMMC, USB, NFS
: Documentation:
: - Initial Yocto Linux documentation for CL-SOM-iMX8Plus
}}

[[Category:Linux]]
[[Category:Yocto]]
[[Category:CL-SOM-iMX8Plus]]

CL-SOM-iMX8Plus: Yocto Linux: Package contents

2023-07-16T08:22:04Z

Benjamin:

== Package contents ==

__NOTOC__

=== Layout ===
<pre>
som-imx8m-plus_yocto-linux
├── bootloader
│ ├── imx-boot_som-imx8m-plus_d1d8
│ └── imx-boot_som-imx8m-plus_d2d4
├── development
│ └── README.html
├── images
│ ├── imx-image-full-som-imx8m-plus.manifest
│ └── imx-image-full-som-imx8m-plus.rootfs.wic.zst
├── kernel
│ ├── dtb
│ │ ├── som-imx8m-plus.dtb
│ │ ├── som-imx8m-plus-hdmi.dtb
│ │ ├── som-imx8m-plus-hdmi-overlay.dtbo
│ │ ├── som-imx8m-plus-headless.dtb
│ │ ├── som-imx8m-plus-lvds.dtb
│ │ ├── som-imx8m-plus-lvds-overlay.dtbo
│ │ ├── som-imx8m-plus_mipi-csi1-ar0234.dtb
│ │ ├── som-imx8m-plus_mipi-csi1-ar1335-mcu.dtb
│ │ ├── som-imx8m-plus_mipi-csi1.dtb
│ │ ├── som-imx8m-plus_mipi-csi1-imx219.dtb
│ │ ├── som-imx8m-plus_mipi-csi2-ar0234.dtb
│ │ ├── som-imx8m-plus_mipi-csi2.dtb
│ │ ├── som-imx8m-plus-mipi.dtb
│ │ ├── som-imx8m-plus-mipi-overlay.dtbo
│ │ ├── som-imx8m-plus-rpmsg.dtb
│ │ ├── som-imx8m-plus-thermal.dtb
│ │ └── som-imx8m-plus-usbdev.dtb
│ ├── Image-som-imx8m-plus
│ └── modules-som-imx8m-plus.tgz
└── version.txt
</pre>

=== development ===
Development documentation

=== bootloader ===
* {{filename|imx-boot_som-imx8m-plus_d2d4}} - NXP imx-boot bootloader; created as a part of the Yocto image with D2D4 configuration; provided as and example (optional).
* {{filename|imx-boot_som-imx8m-plus_d1d8}} - NXP imx-boot bootloader; created as a part of the Yocto image with D1D8 configuration; provided as and example (optional).

=== images ===
* {{filename|mx-image-full-som-imx8m-plus.rootfs.wic.zst}} - SD card image that provides the full system to boot with U-Boot D2D4, Linux kernel and Yocto file-system
* {{filename|imx-image-full-som-imx8m-plus.rootfs.manifest}} - rootfs image manifest

=== kernel ===
* {{filename|Image-som-imx8m-plus}} - ready to run Linux kernel for SOM-iMX8M-Plus
* {{filename|modules-som-imx8m-plus.tgz}} - a modules archive, that match the Linux kernel
* {{filename|dtb}} - Device tree blobs folder
** {{filename|som-imx8m-plus.dtb}} - default device tree blob for SOM-iMX8M-Plus evaluation board kit
** {{filename|som-imx8m-plus-csi1.dtb}} - device tree blob for SOM-iMX8M-Plus evaluation board kit with mipi_csi1=on ; mipi_csi2=off
** {{filename|som-imx8m-plus-csi2.dtb}} - device tree blob for SOM-iMX8M-Plus evaluation board kit with mipi_csi1=off ; mipi_csi2=on
** {{filename|som-imx8m-plus-hdmi.dtb}} - device tree blob for SOM-iMX8M-Plus evaluation board kit with the HDMI interface on only
** {{filename|som-imx8m-plus-mipi.dtb}} - device tree blob for SOM-iMX8M-Plus evaluation board kit with the MIPI interface on only
** {{filename|som-imx8m-plus-lvds.dtb}} - device tree blob for SOM-iMX8M-Plus evaluation board kit with the LVDS interface on only
** {{filename|som-imx8m-plus-usbdev.dtb}} - device tree blob for SOM-iMX8M-Plus evaluation board kit with peripheral device support on J5 USB1
** {{filename|som-imx8m-plus-rpmsg.dtb}} - device tree blob for SOM-iMX8M-Plus evaluation board kit with rpmsg settings enabled
** {{filename|som-imx8m-plus_mipi-csi1-ar0234.dtb}} - device tree blob for SOM-iMX8M-Plus evaluation board kit with mipi_csi1=on ; mipi_csi2=off ; sensor ar0234
** {{filename|som-imx8m-plus_mipi-csi1-ar1335-mcu.dtb}} - device tree blob for SOM-iMX8M-Plus evaluation board kit with mipi_csi1=on ; mipi_csi2=off ; sensor ar1335
** {{filename|som-imx8m-plus_mipi-csi1-imx219.dtb}} - device tree blob for SOM-iMX8M-Plus evaluation board kit with mipi_csi1=on ; mipi_csi2=off ; sensor imx219
** {{filename|som-imx8m-plus_mipi-csi2-ar0234.dtb}} - device tree blob for SOM-iMX8M-Plus evaluation board kit with mipi_csi1=off ; mipi_csi2=on ; sensor ar0234
** {{filename|som-imx8m-plus-headless.dtb}} - device tree blob for SOM-iMX8M-Plus evaluation board kit for a headless configuration
** {{filename|som-imx8m-plus-hdmi-overlay.dtbo}} - device tree hdmi overlay
** {{filename|som-imx8m-plus-lvds-overlay.dtbo}} - device tree lvds overlay
** {{filename|som-imx8m-plus-mipi-overlay.dtbo}} - device tree mipi overlay

[[Category:Linux]]
[[Category:Yocto]]
[[Category:CL-SOM-iMX8Plus]]

CL-SOM-iMX8Plus: Yocto Linux: Building CL-SOM-iMX8Plus Yocto images

2023-07-16T08:18:36Z

Benjamin: Created page with "= Overview = The Yocto Project is an open-source collaboration focused on embedded Linux development. The purpose of this article is to show how to build a Yocto image for..."

= Overview =
The Yocto Project is an open-source collaboration focused on embedded Linux development. 
The purpose of this article is to show how to build a Yocto image for the CL-SOM-iMX8Plus System-on-Module.

= Host System Requirements =
To ensure optimal Yocto build speed and performance, it is recommended to use a host system with at least 4 CPU cores, 64GB RAM, and 500GB of free disk space. 
In addition, the system should have the option to open a large number of files simultaneously, preferably up to 4096 or higher. 

[https://www.yoctoproject.org/docs/ Learn more about Yocto]

= Docker Host for Yocto Build Environment =
There are often compatibility issues between different Linux distributions and the dependencies required for Yocto compilation. 
In order to avoid such issues and simplify the host machine configuration process, Compulab recommends using a pre-configured Docker environment. 
Please follow the instructions below

[https://github.com/compulab-yokneam/yocker Setting up Yocto Build Docker Environment].

= Building Yocto Images =

Set up the Yocto build environment and build the image:

[https://github.com/compulab-yokneam/meta-bsp-imx8mp/blob/som-imx8m-plus-r2.0/README.md Building CL-SOM-iMX8Plus Yocto Linux images].

 

[[Category:Linux]]
[[Category:Yocto]]
[[Category:CL-SOM-iMX8Plus]]

CL-SOM-iMX8Plus NXP iMX8M-Plus Linux Resources

2023-07-16T08:16:56Z

Benjamin:

{{summary|
This page contains links to information about Yocto Linux distribution for the CompuLab CL-SOM-iMX8Plus System-on-Module.
Yocto Project is an open-source collaboration focused on embedded Linux development.

|CL-SOM-iMX8Plus System-on-Module.jpg|thumb}}
{{Resources Linux with app notes
|* [[CL-SOM-iMX8Plus: Evaluation Kit: Getting Started|Getting started with CL-SOM-iMX8Plus Evaluation Kit]]
* [[CL-SOM-iMX8Plus: Yocto Linux: Manual Installation: SD card|Installing Yocto on SD card]]
* [[CL-SOM-iMX8Plus: Yocto Linux: Installing Yocto images onto eMMC| Installing Yocto onto on-board eMMC]]
* [[CL-SOM-iMX8Plus: Yocto Linux: How-To Guide|Yocto Linux how-to guide]]
* [[CL-SOM-iMX8Plus: Yocto Linux: Package contents|Yocto Linux package contents]]
* [[CL-SOM-iMX8Plus: Yocto Linux: Known Issues|Known Issues]]
|* [[CL-SOM-iMX8Plus: Yocto Linux: Building CL-SOM-iMX8Plus Yocto images|Building CL-SOM-iMX8Plus Yocto Linux images]]
*[https://github.com/compulab-yokneam/meta-bsp-imx8mp/blob/som-imx8m-plus-r2.0/Documentation/linux_kernel_build.md Building CL-SOM-iMX8Plus Linux Kernel]
*[https://github.com/compulab-yokneam/meta-bsp-imx8mp/blob/som-imx8m-plus-r2.0/Documentation/imx_boot_image_build.md Building CL-SOM-iMX8Plus boot firmware]
*[[Application Notes: Introduction to Yocto development|Introduction to Yocto development]]
*[[Application Notes: Making Changes to Yocto Meta-Layers|Making Changes to Yocto Meta-Layers]]
|*[[Application Notes: Developing with Qt on CompuLab platforms|Developing with Qt on CompuLab platforms]]
*[[Application Notes: eMMC lifetime optimization|Optimizing eMMC lifetime and reliability]]
*[https://github.com/compulab-yokneam/meta-mender-compulab/blob/kirkstone-nxp/README.md Creating OTA update enabled images with Mender]
*[https://github.com/compulab-yokneam/meta-compulab-hab/blob/imx8/README.md Enabling secure boot (HAB) in Yocto]
}}

__NOTOC__

{{ChangelogReleaseNotesRss| content=
===== 16-Jul-2023, CL-SOM-iMX8MPlus Yocto Linux release 2.0 =====
: Release of Yocto 4.0 (Kirkstone)
: - Based on NXP release Kirkstone-5.15.71-2.0.0
: - Kernel 5.15.71 based on NXP lf-5.15.y
: - U-Boot 2021.04 based on NXP lf_v2021.04
: Supported HW features:
: - Enabled Bluetooth (NXP 88W8997)
: SW Features:
: - Enabled imx219 sensor support with imx8-isp
: Documentation:
: - Updated multiple articles to comply with the new release

===== 31-Mar-2022, CL-SOM-iMX8Plus Yocto Linux release 1.0 =====
: Release of Yocto 3.3 (Hadrknott) for CL-SOM-iMX8Plus
: - Based on NXP release 5.10.72-2.2.0
: - Kernel 5.10.72
: - U-Boot 2021.04
: Supported HW features:
: - Basic support for CL-SOM-iMX8Plus
: - USB2.0 OTG Host/Device
: - USB3.0 Host
: - PCIe, I2C, SPI
: - Storage: eMMC, uSD, EEPROM
: - Ethernet: ENET_QOS and ENET_FEC
: - FlexCAN: can0, can1
: - HDMI display interface
: - LVDS display interface
: - MIPI-DSI display interface
: - Touch screen support
: - CSI video camera interface
: - Wireless: WiFi (NXP 88W8997)
: - SNVS RTC
: - External RTC
: - Heartbeat LED
: SW Features:
: - CompuLab Deployment Tool
: - CompuLab U-Boot Tool
: - fw_printenv/fw_setenv/cl_setenv utilities provide R/W assess to U-Boot environment from Linux CLI
: - Chromium browser
: - Qt support
: Boot-loader features:
: - Supported memory configurations: 2GB, 4GB
: - Supported boot-loader devices: SD, eMMC
: - Supported linux/rootfs devices: SD, eMMC, USB, NFS
: Documentation:
: - Initial Yocto Linux documentation for CL-SOM-iMX8Plus
}}

[[Category:Linux]]
[[Category:Yocto]]
[[Category:CL-SOM-iMX8Plus]]

CL-SOM-iMX8Plus NXP iMX8M-Plus SW Resources

2023-07-16T08:13:07Z

Benjamin:

{{summary|
CL-SOM-iMX8Plus is a miniature system-on-module board, designed for integration into industrial embedded applications.

CL-SOM-iMX8Plus is built around the NXP i.MX8M Plus application processor featuring a highly scalable dual/quad core Cortex-A53 1.8GHz CPU, coupled with powerful graphics and video processing units.
CL-SOM-iMX8Plus features extensive connectivity with a wide range of industry standard interfaces – GbE, USB 3.0, PCIe, SDIO, CAN, 802.11ac WiFi and Bluetooth 5.0.
CL-SOM-iMX8Plus is provided with comprehensive documentation and full ready-to-run SW support for Linux operating system.
|CL-SOM-iMX8Plus System-on-Module.jpg|thumb}}

<div style="background: white; border: 1px solid black; padding: 1em;">
{| border="0" cellpadding="2" width="100%" align="center"
|-
! style="font-size: 125%; background-color: #eeeeee;" align="center" width="25%" | [[CL-SOM-iMX8Plus NXP iMX8M-Plus Yocto Linux|Yocto Linux]]
|-

| align="center" | [[Image:Yocto-Logo1.png|200px|link=CL-SOM-iMX8Plus NXP iMX8M-Plus Yocto Linux]]
|}
</div>

__NOTOC__

{{note|1=From time to time CompuLab releases new software versions for CL-SOM-iMX8Plus in order to fix bugs, address component changes and add functionality. It is highly recommended to subscribe to the [[Image:Feed-icon.png|16px]] [{{fullurl:{{FULLPAGENAME}}|action=feed}} '''CL-SOM-iMX8Plus RSS Feed'''] in order to receive automatic notifications about software updates.}}

{{ChangelogReleaseNotesRss| content=
===== 16-Jul-2023, CL-SOM-iMX8MPlus Yocto Linux release 2.0 =====
: Release of Yocto 4.0 (Kirkstone)
: - Based on NXP release Kirkstone-5.15.71-2.0.0
: - Kernel 5.15.71 based on NXP lf-5.15.y
: - U-Boot 2021.04 based on NXP lf_v2021.04
: Supported HW features:
: - Enabled Bluetooth (NXP 88W8997)
: SW Features:
: - Enabled imx219 sensor support with imx8-isp
: Documentation:
: - Updated multiple articles to comply with the new release

===== 31-Mar-2022, CL-SOM-iMX8Plus Yocto Linux release 1.0 =====
: Release of Yocto 3.3 (Hadrknott) for CL-SOM-iMX8Plus
: - Based on NXP release 5.10.72-2.2.0
: - Kernel 5.10.72
: - U-Boot 2021.04
: Supported HW features:
: - Basic support for CL-SOM-iMX8Plus
: - USB2.0 OTG Host/Device
: - USB3.0 Host
: - PCIe, I2C, SPI
: - Storage: eMMC, uSD, EEPROM
: - Ethernet: ENET_QOS and ENET_FEC
: - FlexCAN: can0, can1
: - HDMI display interface
: - LVDS display interface
: - MIPI-DSI display interface
: - Touch screen support
: - CSI video camera interface
: - Wireless: WiFi (NXP 88W8997)
: - SNVS RTC
: - External RTC
: - Heartbeat LED
: SW Features:
: - CompuLab Deployment Tool
: - CompuLab U-Boot Tool
: - fw_printenv/fw_setenv/cl_setenv utilities provide R/W assess to U-Boot environment from Linux CLI
: - Chromium browser
: - Qt support
: Boot-loader features:
: - Supported memory configurations: 2GB, 4GB
: - Supported boot-loader devices: SD, eMMC
: - Supported linux/rootfs devices: SD, eMMC, USB, NFS
: Documentation:
: - Initial Yocto Linux documentation for CL-SOM-iMX8Plus
}}

[[Category:CL-SOM-iMX8Plus]]

UCM-iMX8M-Mini: Yocto Linux: How-To Guide

2023-07-05T10:51:04Z

Benjamin: /* Changing CPU frequency */

=Wi-Fi=
{{note|The operations below requires '''root''' access.}}

UCM-iMX8M-Mini features certified 802.11ac Wi-Fi interface (Broadcom BCM43353 chipset). Before working with Wi-Fi, please, ensure that Wi-Fi antenna is connected.

For hardware setup and Wi-Fi antenna connection instructions please refer to [[UCM-iMX8M-Mini: Evaluation Kit: Hardware Guide#WiFi.2FBluetooth | evaluation kit hardware guide]].

To start using Wi-Fi add your network credentials into the following file:
<pre>
/etc/wpa_supplicant.conf
</pre>

Add the network name into '''ssid''' field, password into '''psk''' field and key into the '''key_mgmt''' field (if your network uses key management). 
The file should have the following content:
<pre>
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
update_config=1
network={
ssid="<the name of your internet acces point>"
key_mgmt=WPA-PSK
psk="<the password of your internet access point>"
}
</pre>

Execute the following commands to connect to the network:
<pre>
wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant.conf -D nl80211
udhcpc -i wlan0
</pre>

=Gstreamer=
Yocto Linux uses Gstreamer as a default multimedia framework. Here are some useful Gstreamer features:

Execute the following command to check all the source options:
gst-inspect-1.0 | grep source

Execute the following command to check all the sink options:
gst-inspect-1.0 | grep sink

==Video Playback==
{{note|The operation below requires '''root''' access.}}

UCM-iMX8M-Mini features 1080p60 H.264, VP8 video decoding capabilities. Before starting video playback, please, ensure that the display is connected to the board.

For hardware setup and display connection instructions please refer to [[UCM-iMX8M-Mini: Evaluation Kit: Hardware Guide#LCD | evaluation kit hardware guide]].

The following command should be used to start video playback:
<pre>
gst-launch-1.0 -v filesrc location=1.mov ! h264parse ! avdec_h264 ! autovideosink
</pre>

Where '''1.mov''' is name and extension of the video file.

==Video Capturing==
{{note|The operation below requires '''root''' access.}}

UCM-iMX8M-Mini features 1080p60 H.264, VP8 video encoding. Before starting video capturing, please, ensure that camera is connected to the board.

For hardware setup and camera connection instructions please refer to [[UCM-iMX8M-Mini: Evaluation Kit: Hardware Guide#Camera | evaluation kit hardware guide]].

The following command should be used to start video capturing:
<pre>
gst-launch-1.0 -v v4l2src ! vpuenc_h264 ! filesink location=1.mov
</pre>

Where '''1.mov''' is name and extension of the file.

==Video streaming==
{{note|The operation below requires '''root''' access.}}
The following command should be executed on UCM-iMX8M-Mini to start video streaming:
gst-launch-1.0 v4l2src device=/dev/video0 ! video/x-raw, width=640, height=480 ! jpegenc ! udpsink host='''127.0.0.1''' port='''1234'''
'''127.0.0.1''' is the IP address of the host PC, and '''1234''' is the host PC port.

The following command should be executed on host PC (Linux) to receive the video stream:
gst-launch-1.0 udpsrc port='''1234''' ! jpegdec ! autovideosink
'''1234''' is the host PC port.

=Suspend / Resume=
{{note|The operation below requires '''root''' access.}}

UCM-iMX8M-Mini features suspend mode, which allows to minimize power consumption.

The following command should be used to enter suspend mode:
<pre>
echo mem >/sys/power/state
</pre>

To resume normal operation press shortly the '''Power On''' button '''SW5'''.

=CPU frequency=
{{note|The operation below requires '''root''' access.}}

CPU frequency can be changed by using one of the following methods:

==Changing the scaling governor==
Execute the following command to change the scaling governor:
<pre>
echo performance > /sys/devices/system/cpu/cpufreq/policy0/scaling_governor
</pre>

Where '''perfomance''' is name of the scaling governor.

Execute the following command to see available scaling governors:
<pre>
cat /sys/devices/system/cpu/cpufreq/policy0/scaling_available_governors
</pre>

Execute the following command to see current scaling governor:
<pre>
cat /sys/devices/system/cpu/cpufreq/policy0/scaling_governor
</pre>

==Changing CPU frequency==
{{note|CPU frequency can be changed only when the scaling governor is set to '''userspace'''.}}
<pre>
sudo echo userspace > /sys/devices/system/cpu/cpufreq/policy0/scaling_governor
</pre>

Execute the following command to set CPU frequency:
<pre>
echo 1200000 > /sys/devices/system/cpu/cpufreq/policy0/scaling_setspeed
</pre>

'''1200000''' is one of the available CPU frequencies.

Execute the following command to see available CPU frequencies:
<pre>
cat /sys/devices/system/cpu/cpufreq/policy0/scaling_available_frequencies
</pre>

Execute the following command to see current CPU frequency:
<pre>
cat /sys/devices/system/cpu/cpufreq/policy0/cpuinfo_cur_freq
</pre>

=CPU temperature=
i.MX8M-Mini SoC features an internal temperature sensor which allows to measure the SoC temperature.
Execute the following command to read the current CPU temperature:
<pre>
cat /sys/class/thermal/thermal_zone0/temp
</pre>

=RTC=
Execute the following command to set the date and write it into the RTC:
<pre>
root@ucm-imx8m-mini:~# date -s "12 SEP 2019 10:00:00"
Thu Sep 12 10:00:00 UTC 2019
root@ucm-imx8m-mini:~# /sbin/hwclock --systohc
root@ucm-imx8m-mini:~# hwclock –w
</pre>

Execute the following command to read the RTC time and date:
<pre>
root@ucm-imx8m-mini:~# hwclock
Thu Sep 12 10:00:48 2019 0.000000 seconds
</pre>

= Device Serial Number and Configuration =
Product information is stored in on-board EEPROM. 
* To read the product serial number, issue the folowing command:
<pre>
root@ucm-imx8m-mini:~# cat /proc/device-tree/product-sn
</pre>
* To read the product configuration part number, issue the following command:
<pre>
root@ucm-imx8m-mini:~# cat /proc/device-tree/product-options
</pre>

=See Also=
*[[UCM-iMX8M-Mini: Evaluation Kit: Getting Started | UCM-iMX8M-Mini:Evaluation Kit: Getting Started]] 
*[[UCM-iMX8M-Mini: Evaluation Kit: Hardware Guide | UCM-iMX8M-Mini: Evaluation Kit: Hardware Guide]] 

[[Category:Yocto]]
[[Category:UCM-iMX8M-Mini]]

Transclusion: CL-SOM-iMX7: U-Boot: Building Images

2023-06-28T15:09:32Z

Benjamin:

==== Git clone ====
* Install [http://git-scm.com/ git] version control system.
* Create a clone of U-Boot tree
<pre>
cd /home/development/cl-som-imx7/u-boot
git clone https://github.com/compulab/u-boot.git -b v2017.07-cl-som-imx7-1.9 u-boot-cl-som-imx7
cd u-boot-cl-som-imx7
</pre>
* Create a branch for CL-SOM-iMX7 development
<pre>git checkout -b cl-som-imx7-1.9-devel</pre>

=== Building the firmware images ===
* First, compile U-Boot. The following commands create the {{filename|u-boot.imx}} binary (along with other image types):
<pre>
export ARCH=arm
export CROSS_COMPILE=arm-none-linux-eabi-
make mrproper
make cl-som-imx7_defconfig && make
</pre>
* Merge the SPL and U-Boot images into one firmware image:
<pre>
dd if=/dev/zero count=640 bs=1K | tr '\000' '\377' > cl-som-imx7-firmware
dd if=SPL of=cl-som-imx7-firmware bs=1K seek=1 conv=notrunc
dd if=u-boot.img of=cl-som-imx7-firmware bs=1K seek=64 conv=notrunc
</pre>

CL-SOM-iMX7: U-Boot: Building Images

2023-06-28T15:07:52Z

Benjamin:

== Overview ==
The CompuLab CL-SOM-iMX7 System-on-Module / Computer-on-Module firmware consists of two components: Secondary Program Loader (SPL) and U-Boot.
Both components are based on [http://www.denx.de/wiki/U-Boot/WebHome U-Boot] source code. 
SPL is the bootstrap utility invoked by the CPU internal boot ROM code of the i.MX7 SoC.
U-Boot initializes hardware modules necessary for system boot and loads the operating system. 
The latest U-Boot package is available at the [http://www.compulab.com/products/computer-on-modules/cl-som-imx7-freescale-i-mx-7-system-on-module/#devres CL-SOM-iMX7 Resources] web page.

== Building Firmware images for CL-SOM-iMX7 ==
=== Getting U-Boot sources ===
We assume that you have created {{filename|/home/development/cl-som-imx7/u-boot}} directory for the the CL-SOM-iMX7 U-Boot development.

{{:Transclusion: CL-SOM-iMX7: U-Boot: Building Images}}
* You can now install the {{filename|cl-som-imx7-firmware}} file into an SD card or CL-SOM-iMX7 SPI flash.

== See also ==

* [[CL-SOM-iMX7: U-Boot: Firmware Update|Firmware Update]]
* [[CL-SOM-iMX7: U-Boot: Creating a bootable SD card|Creating a bootable SD card]]
* [[U-Boot: Quick reference]]
* [[U-Boot images]]
* [http://www.denx.de/wiki/U-Boot/Documentation U-Boot documentation]

[[Category:U-Boot]]
[[Category:CL-SOM-iMX7]]

IOT-GATE-iMX8 and SBC-IOT-iMX8 NXP iMX8M-Mini Yocto Linux

2023-06-28T14:34:18Z

Benjamin:

{{summary|
This page contains links to information about Yocto Linux distribution for the CompuLab IOT-GATE-iMX8 Internet of Things Gateway and SBC-IOT-iMX8 Single Board Computer.

The Yocto Project is an open-source collaboration focused on embedded Linux development.

|iot-gate-imx8.png|thumb}}
{{Resources Linux with app notes
|* [[IOT-GATE-iMX8: Getting Started|Getting started with IOT-GATE-iMX8]]
* [[IOT-GATE-iMX8 and SBC-IOT-iMX8: Yocto Linux: Installation|Installing Yocto on IOT-GATE-iMX8 / SBC-IOT-iMX8]]
* [[IOT-GATE-iMX8 and SBC-IOT-iMX8: Yocto Linux: How-To Guide|Yocto Linux how-to guide for IOT-GATE-iMX8 / SBC-IOT-iMX8]]
|* [[IOT-GATE-IMX8: Yocto Linux: Building Yocto image|Building IOT-GATE-iMX8 / SBC-IOT-iMX8 Yocto Linux images]]
*[https://github.com/compulab-yokneam/meta-bsp-imx8mm/blob/iot-gate-imx8-r3.2.1/Documentation/linux_kernel_build.md Building IOT-GATE-iMX8 / SBC-IOT-iMX8 Linux Kernel]
*[https://github.com/compulab-yokneam/meta-bsp-imx8mm/blob/iot-gate-imx8-r3.2.1/Documentation/imx_boot_image_build.md Building IOT-GATE-iMX8 / SBC-IOT-iMX8 U-boot image]
*[[Application Notes: Introduction to Yocto development|Introduction to Yocto development]]
*[[Application Notes: Making Changes to Yocto Meta-Layers|Making Changes to Yocto Meta-Layers]]
*[[IOT-GATE-iMX8 and SBC-IOT-iMX8: U-Boot: Recovery|U-Boot Recovery]]
|*[[Application Notes: eMMC lifetime optimization|Optimizing eMMC lifetime and reliability]]
*[https://github.com/compulab-yokneam/meta-mender-compulab/ Creating OTA update enabled images with Mender]
*[https://github.com/compulab-yokneam/meta-compulab-hab/blob/imx8/README.md Enabling secure boot (HAB) in Yocto]
}}

__NOTOC__

{{ChangelogReleaseNotesRss| content=

===== 15-Jun-2023, IOT-GATE-iMX8 / SBC-IOT-iMX8 Yocto Linux release 3.2.1 =====
: Release of Yocto 4.0 (Kirkstone) for IOT-GATE-iMX8 / SBC-IOT-iMX8
: - Fixed the Docker issue

===== 21-May-2023, IOT-GATE-iMX8 / SBC-IOT-iMX8 Yocto Linux release 3.2 =====
: Release of Yocto 4.0 (Kirkstone) for IOT-GATE-iMX8 / SBC-IOT-iMX8
: - Kirkstone Long-Term Support
: - Kernel 5.15.32 [[IOT-GATE-iMX8 and SBC-IOT-iMX8: U-Boot: Update | (Requires U-Boot version 3.2 or higher) ]]
: - U-Boot 2021.04
: - Add support for Intel AX210 WiFi/BT card

===== 09-May-2023, IOT-GATE-iMX8 / SBC-IOT-iMX8 Yocto Linux release 3.1.5 =====
: Release of Yocto 3.3 (Hardknott) for IOT-GATE-iMX8 / SBC-IOT-iMX8
: - Kernel 5.10.72
: - U-Boot 2021.04
: - Fixed USB power supply reset issue
: - Enabled root FS journaling
: - Fixed cpufreq driver issue
: - Disabled Ethernet PHY clock 125 MHz
: - Added support for simultaneous operation of two IE-CL420 modules
: Image build improvement:
: - Added Linux headers to the image
: - Migrated from CodeAurora to GitHub
: Documentation updated

===== 19-Jul-2022, IOT-GATE-iMX8 / SBC-IOT-iMX8 Yocto Linux release 3.1 =====
: Release of Yocto 3.3 (Hardknott) for IOT-GATE-iMX8 / SBC-IOT-iMX8
: - Kernel 5.10.72
: - U-Boot 2021.04
: - Fix signal configuration of Digital I/O add-on GPIOs
: - Fix WiFi driver for 4GB RAM configuration
: - Enable support for FTDI USB to serial driver
: - Add support for mbpoll ModBus utility
: - Reduce RTC battery usage when the power supply is disconnected
: - Store manufacturing details in the device tree
: - Update the CAN bus driver
: - Add support to the POE add-on module
: - Add support for the M4 core
: - Add support for the IE-CL420 module
: - Add support for the IE-TPM module
: - Enable the net filter tables feature
: - Enable setting the RTC time based on NTP
: - Enable broadcast manager CAN Protocol
: - Add the digital I/O add-on input GPIOs as wake-up sources
: - Add support for the Realtek RTL8211 PHY
: Documentation:
: - Initial Yocto Linux documentation for IOT-GATE-iMX8 / SBC-IOT-iMX8

===== 21-Sep-2020, IOT-GATE-iMX8 / SBC-IOT-iMX8 Yocto Linux release 2.0 =====
: Release of Yocto 3.0 (Zeus) for IOT-GATE-iMX8 / SBC-IOT-iMX8
: - Kernel 5.4.24
: - U-Boot 2020.04
: HW-supported features:
: - eMMC storage
: - USB2.0 Host
: - Ethernet
: - WiFi (Intel AX200)
: - Bluetooth
: - LTE modem (SIM7600G)
: - CAN-FD
: - RS485
: - RS232 with flow control
: - Industrial I/O add-ons
: - RTC
: - Industrial I/O extension boards
: SW Features:
: - CompuLab Deployment Tool
: - Linux CLI utilities for access to the U-Boot environment
: Documentation:
: - Initial Yocto Linux documentation for IOT-GATE-iMX8 / SBC-IOT-iMX8
}}

[[Category:Linux]]
[[Category:Yocto]]
[[Category:IOT-GATE-iMX8]]
[[Category:SBC-IOT-iMX8]]

IOT-GATE-IMX8: Yocto Linux: Building Yocto image

2023-06-28T14:32:25Z

Benjamin:

= Overview =
The Yocto Project is an open-source collaboration focused on embedded Linux development. 
The purpose of this article is to show how to build a Yocto image for the IOT-GATE-IMX8 Internet of Things Gateway.

= Host System Requirements =
To ensure optimal Yocto build speed and performance, it is recommended to use a host system with at least 4 CPU cores, 16GB RAM, and 500GB of free disk space. 
In addition, the system should have the option to open a large number of files simultaneously, preferably up to 4096 or higher. 
[https://www.yoctoproject.org/docs/ Learn more about Yocto]

= Docker Host for Yocto Build Environment =
There are often compatibility issues between different Linux distributions and the dependencies required for Yocto compilation. 
In order to avoid such issues and simplify the host machine configuration process, Compulab recommends using a pre-configured Docker environment. 
Please follow the instructions outlined in [https://github.com/compulab-yokneam/yocker Setting up Yocto Build Docker Environment].

= Building Yocto Images =
Set up the Yocto build environment and build the image as detailed in the [https://github.com/compulab-yokneam/meta-bsp-imx8mm/blob/iot-gate-imx8-r3.2.1/README.md Building IOT-GATE-IMX8 Yocto Linux image] guide.
 
 

[[Category:Linux]]
[[Category:Yocto]]
[[Category:IOT-GATE-iMX8]]
[[Category:SBC-IOT-iMX8]]

IOT-GATE-iMX8 and SBC-IOT-iMX8: Yocto Linux: Installation

2023-06-28T14:24:24Z

Benjamin:

== Introduction ==
This article provides instructions to install the Yocto Linux live image on the IOT-GATE-iMX8 / SBC-IOT-iMX8 device, using a Linux Host workstation and a USB flash drive.
The image includes the Linux kernel, device driver modules, and Yocto root filesystem.

{{Important|This installation process requires U-Boot version '''3.2''' or above. 
Before proceeding [[IOT-GATE-iMX8 and SBC-IOT-iMX8: U-Boot: Update|check the U-Boot version on your device and update as needed.]]
}}

== Preparation steps ==
* Obtain a Linux PC workstation.
* Obtain a USB flash drive. Any commercially available USB flash drive of 1GB (or larger) may be used for the installation.
* The Yocto Linux live image file, mentioned below, is generated during the [[IOT-GATE-IMX8: Yocto Linux: Building Yocto image|Yocto build process]].
* Plug the USB flash drive into the host PC. The following instructions assume that the flash drive device name on your Linux PC is {{filename|/dev/sdX}}.

== Preparing the installation flash drive ==
* Flash the image file to the USB flash drive:
<pre>
bzcat ~/path/to/core-image-full-cmdline-iot-gate-imx8.wic.bz2 | sudo dd of=/dev/sdX bs=1M
</pre>

== Run the Yocto live-disk image ==
{{:Transclusion: IOT-GATE-iMX8: Run Linux image}}

== Installing Yocto images onto the internal storage ==
Use the `CompuLab Deployment Tool` to install the IOT-GATE-iMX8 / SBC-IOT-iMX8 Yocto Linux onto on-board eMMC storage. 
{{:Transclusion: IOT-GATE-iMX8: cl-deply}}

==Post Installation==
{{:Transclusion: IOT-GATE-iMX8: Post Installation}}

[[Category:Linux]]
[[Category:Yocto]]
[[Category:IOT-GATE-iMX8]]
[[Category:SBC-IOT-iMX8]]

IOT-GATE-iMX8 and SBC-IOT-iMX8 NXP iMX8M-Mini Yocto Linux

2023-06-28T07:29:23Z

Benjamin:

{{summary|
This page contains links to information about Yocto Linux distribution for the CompuLab IOT-GATE-iMX8 Internet of Things Gateway and SBC-IOT-iMX8 Single Board Computer.

The Yocto Project is an open-source collaboration focused on embedded Linux development.

|iot-gate-imx8.png|thumb}}
{{Resources Linux with app notes
|* [[IOT-GATE-iMX8: Getting Started|Getting started with IOT-GATE-iMX8]]
* [[IOT-GATE-iMX8 and SBC-IOT-iMX8: Yocto Linux: Installation|Installing Yocto on IOT-GATE-iMX8 / SBC-IOT-iMX8]]
* [[IOT-GATE-iMX8 and SBC-IOT-iMX8: Yocto Linux: How-To Guide|Yocto Linux how-to guide for IOT-GATE-iMX8 / SBC-IOT-iMX8]]
|* [[IOT-GATE-IMX8: Yocto Linux: Building Yocto image|Building IOT-GATE-iMX8 / SBC-IOT-iMX8 Yocto Linux images]]
*[https://github.com/compulab-yokneam/meta-bsp-imx8mm/blob/iot-gate-imx8-r3.2.1/Documentation/linux_kernel_build.md Building IOT-GATE-iMX8 / SBC-IOT-iMX8 Linux Kernel]
*[https://github.com/compulab-yokneam/meta-bsp-imx8mm/blob/iot-gate-imx8-r3.2.1/Documentation/imx_boot_image_build.md Building IOT-GATE-iMX8 / SBC-IOT-iMX8 U-boot image]
*[[Application Notes: Introduction to Yocto development|Introduction to Yocto development]]
*[[Application Notes: Making Changes to Yocto Meta-Layers|Making Changes to Yocto Meta-Layers]]
*[[IOT-GATE-iMX8 and SBC-IOT-iMX8: U-Boot: Recovery|U-Boot Recovery]]
|*[[Application Notes: eMMC lifetime optimization|Optimizing eMMC lifetime and reliability]]
*[https://github.com/compulab-yokneam/meta-mender-compulab/ Creating OTA update enabled images with Mender]
*[https://github.com/compulab-yokneam/meta-compulab-hab/blob/imx8/README.md Enabling secure boot (HAB) in Yocto]
}}

__NOTOC__

{{ChangelogReleaseNotesRss| content=

===== 15-Jun-2023, IOT-GATE-iMX8 / SBC-IOT-iMX8 Yocto Linux release 3.2.1 =====
: Release of Yocto 4.0 (Kirkstone) for IOT-GATE-iMX8 / SBC-IOT-iMX8
: - Fixed the Docker issue

===== 21-May-2023, IOT-GATE-iMX8 / SBC-IOT-iMX8 Yocto Linux release 3.2 =====
: Release of Yocto 4.0 (Kirkstone) for IOT-GATE-iMX8 / SBC-IOT-iMX8
: - Kirkstone Long-Term Support
: - Kernel 5.15.32
: - U-Boot 2021.04
: - Add support for Intel AX210 WiFi/BT card

===== 09-May-2023, IOT-GATE-iMX8 / SBC-IOT-iMX8 Yocto Linux release 3.1.5 =====
: Release of Yocto 3.3 (Hardknott) for IOT-GATE-iMX8 / SBC-IOT-iMX8
: - Kernel 5.10.72
: - U-Boot 2021.04
: - Fixed USB power supply reset issue
: - Enabled root FS journaling
: - Fixed cpufreq driver issue
: - Disabled Ethernet PHY clock 125 MHz
: - Added support for simultaneous operation of two IE-CL420 modules
: Image build improvement:
: - Added Linux headers to the image
: - Migrated from CodeAurora to GitHub
: Documentation updated

===== 19-Jul-2022, IOT-GATE-iMX8 / SBC-IOT-iMX8 Yocto Linux release 3.1 =====
: Release of Yocto 3.3 (Hardknott) for IOT-GATE-iMX8 / SBC-IOT-iMX8
: - Kernel 5.10.72
: - U-Boot 2021.04
: - Fix signal configuration of Digital I/O add-on GPIOs
: - Fix WiFi driver for 4GB RAM configuration
: - Enable support for FTDI USB to serial driver
: - Add support for mbpoll ModBus utility
: - Reduce RTC battery usage when the power supply is disconnected
: - Store manufacturing details in the device tree
: - Update the CAN bus driver
: - Add support to the POE add-on module
: - Add support for the M4 core
: - Add support for the IE-CL420 module
: - Add support for the IE-TPM module
: - Enable the net filter tables feature
: - Enable setting the RTC time based on NTP
: - Enable broadcast manager CAN Protocol
: - Add the digital I/O add-on input GPIOs as wake-up sources
: - Add support for the Realtek RTL8211 PHY
: Documentation:
: - Initial Yocto Linux documentation for IOT-GATE-iMX8 / SBC-IOT-iMX8

===== 21-Sep-2020, IOT-GATE-iMX8 / SBC-IOT-iMX8 Yocto Linux release 2.0 =====
: Release of Yocto 3.0 (Zeus) for IOT-GATE-iMX8 / SBC-IOT-iMX8
: - Kernel 5.4.24
: - U-Boot 2020.04
: HW-supported features:
: - eMMC storage
: - USB2.0 Host
: - Ethernet
: - WiFi (Intel AX200)
: - Bluetooth
: - LTE modem (SIM7600G)
: - CAN-FD
: - RS485
: - RS232 with flow control
: - Industrial I/O add-ons
: - RTC
: - Industrial I/O extension boards
: SW Features:
: - CompuLab Deployment Tool
: - Linux CLI utilities for access to the U-Boot environment
: Documentation:
: - Initial Yocto Linux documentation for IOT-GATE-iMX8 / SBC-IOT-iMX8
}}

[[Category:Linux]]
[[Category:Yocto]]
[[Category:IOT-GATE-iMX8]]
[[Category:SBC-IOT-iMX8]]

IOT-GATE-iMX8 and SBC-IOT-iMX8 NXP iMX8M-Mini Debian Linux

2023-06-28T07:24:44Z

Benjamin:

{{summary|
This page contains links to information about Linux kernels, packages and software development for the Compulab IOT-GATE-iMX8 Internet of Things Gateway and SBC-IOT-iMX8 Single Board Computer.

CompuLab Linux support for IOT-GATE-iMX8 and SBC-IOT-iMX8 includes Linux kernel and Debian file-system image based on [http://www.debian.org/ports/arm/ ARM Debian Linux]. The [https://www.debian.org/intro/about Debian Project] is an association of individuals who have made a common cause to create a free operating system. This operating system is called Debian.
It is also possible to use other embedded Linux distributions and environments with IOT-GATE-iMX8 and SBC-IOT-iMX8.
|iot-gate-imx8.png|thumb
}}

{{Resources Linux with app notes
|*[[IOT-GATE-iMX8: Getting Started|Getting started with IOT-GATE-iMX8]]
*[[IOT-GATE-iMX8 and SBC-IOT-iMX8: Debian Linux: Installation|Installing Debian on IOT-GATE-iMX8 / SBC-IOT-iMX8]]
*[[IOT-GATE-iMX8 and SBC-IOT-iMX8: Debian Linux: How-To Guide|Debian Linux how-to guide for IOT-GATE-iMX8 / SBC-IOT-iMX8]]
*[[IOT-GATE-iMX8 and SBC-IOT-iMX8: Debian Linux: Package contents|Debian Linux package contents]]
|*
*[https://github.com/compulab-yokneam/meta-bsp-imx8mm/blob/iot-gate-imx8-r3.2.1/Documentation/linux_kernel_build.md Building IOT-GATE-iMX8 / SBC-IOT-iMX8 Linux Kernel]
*[https://github.com/compulab-yokneam/meta-bsp-imx8mm/blob/iot-gate-imx8-r3.2.1/Documentation/imx_boot_image_build.md Building IOT-GATE-iMX8 / SBC-IOT-iMX8 U-boot image]
*[[IOT-GATE-iMX8 and SBC-IOT-iMX8: U-Boot: Recovery|U-Boot Recovery]]
|*[[IOT-GATE-iMX8 and SBC-IOT-iMX8: Linux: Production Deployment|Production Image Deployment]]
*[[Application Notes: eMMC lifetime optimization|Optimizing eMMC lifetime and reliability]]
}}

__NOTOC__

{{ChangelogRss| content=
===== 15-Jun-2023, IOT-GATE-iMX8 / SBC-IOT-iMX8 Debian Linux release 3.2.1 =====
: Release of Debian (Bullseye) for IOT-GATE-iMX8 / SBC-IOT-iMX8
: - Fixed the Docker issue

===== 21-May-2023, IOT-GATE-iMX8 / SBC-IOT-iMX8 Debian Linux release 3.2 =====
: Release of Debian (Bullseye) for IOT-GATE-iMX8 / SBC-IOT-iMX8
: - Kernel 5.15.32 [[IOT-GATE-iMX8 and SBC-IOT-iMX8: U-Boot: Update | (Requires U-Boot version 3.2 or higher) ]]
: - U-Boot 2021.04
: - Add support for Intel AX210 WiFi/BT card
: - Added support for simultaneous operation of two IE-CL420 modules
: - Fixed USB power supply reset issue
: - Fixed cpufreq driver issue

===== 30-Jan-2023, IOT-GATE-iMX8 / SBC-IOT-iMX8 Debian Linux release 3.1.1 =====
: Release of Debian (Bullseye) for IOT-GATE-iMX8 / SBC-IOT-iMX8
: - Fix file-system journaling issue

===== 03-Aug-2022, IOT-GATE-iMX8 / SBC-IOT-iMX8 Debian Linux release 3.1 =====
: Release of Debian (Bullseye) for IOT-GATE-iMX8 / SBC-IOT-iMX8
: - Adjust the M4 core support to NXP release lf-5.10.72-2.2.0
: - Add OPP-TEE support to the U-Boot
: - Optimize file-system to improve eMMC lifetime

===== 24-Mar-2022, IOT-GATE-iMX8 / SBC-IOT-iMX8 Debian Linux release 3.0 =====
: Release of Debian (Bullseye) for IOT-GATE-iMX8 / SBC-IOT-iMX8
: - Based on NXP release lf-5.10.72-2.2.0
: - Kernel 5.10.72
: - U-Boot 2021.04
: - Add support for the Realtek RTL8211 PHY
: - Add support for Alliance 1GB DDR
: Documentation:
: - Updated multiple articles to comply with the new Debian package

===== 05-Dec-2021, IOT-GATE-iMX8 / SBC-IOT-iMX8 Debian Linux release 2.5 =====
: Release of Debian (Bullseye) for IOT-GATE-iMX8 / SBC-IOT-iMX8
: - Update the driver of the IE-CL420 module.
: - Add support for Samsung 4GB DDR.
: - Upgrade to Debian 11 (Bullseye).
: - Enable support for Microsoft Azure IoT Edge.
: Documentation:
: - Updated multiple articles to comply with the new Debian package

===== 20-Jun-2021, IOT-GATE-iMX8 / SBC-IOT-iMX8 Debian Linux release 2.4 =====
: Release of Debian (Buster) for IOT-GATE-iMX8 / SBC-IOT-iMX8
: - Add support for the POEv2 extension module.
: - Enable the net filter tables feature.
: - Enable setting the RTC time based on NTP.
: - Enable broadcast manager CAN Protocol.
: - Add the digital I/O add-on input GPIOs as a wakeup sources.
: Documentation:
: - Updated multiple articles to comply with the new Debian package

===== 16-Mar-2021, IOT-GATE-iMX8 / SBC-IOT-iMX8 Debian Linux release 2.3 =====
: Release of Debian (Buster) for IOT-GATE-iMX8 / SBC-IOT-iMX8
: - Add support for the M4 core.
: - Add support for the IE-CL420 module.
: - Add support for the IE-TPM module.
: - Update the CAN bus driver.
: Documentation:
: - Updated multiple articles to comply with the new Debian package

===== 17-Jan-2021, IOT-GATE-iMX8 / SBC-IOT-iMX8 Debian Linux release 2.2 =====
: Release of Debian (Buster) for IOT-GATE-iMX8 / SBC-IOT-iMX8
: - Reduce RTC battery usage when the power supply is disconnected.
: - Store manufacturing details in the device tree.
: - Update the CAN bus driver.
: - Add support to the POE extension module.
: Documentation:
: - Updated multiple articles to comply with the new Debian package

===== 10-Dec-2020, IOT-GATE-iMX8 / SBC-IOT-iMX8 Debian Linux release 2.1 =====
: Release of Debian (Buster) for IOT-GATE-iMX8 / SBC-IOT-iMX8
: - Upgrade to 64-bit Debian.
: - Fix signal configuration of Digital I/O add-on GPIOs.
: - Fix WiFi driver for 4GB RAM configuration.
: - Enable support for FTDI USB to serial driver.
: - Add support for mbpoll ModBus utility.
: Documentation:
: - Updated multiple articles to comply with the new Debian package

===== 18-Sep-2020, IOT-GATE-iMX8 / SBC-IOT-iMX8 Debian Linux release 2.0 =====
: Release of Debian (Buster) for IOT-GATE-iMX8 / SBC-IOT-iMX8
: - Kernel 5.4.24
: - U-Boot 2020.04
: HW supported features:
: - Industrial I/O extension boards
: Documentation:
: - Updated multiple articles to comply with the new Debian package

===== 5-May-2020, IOT-GATE-iMX8 / SBC-IOT-iMX8 Debian Linux release 1.0 =====
: Release of Debian (Buster) for IOT-GATE-iMX8 / SBC-IOT-iMX8
: - Based on NXP release L4.14.98-2.0.0_ga
: - Kernel 4.14.98
: HW Features:
: - eMMC storage
: - USB2.0 Host
: - Ethernet
: - WiFi (Intel AX200)
: - Bluetooth
: - LTE modem (SIM7600G)
: - CAN-FD
: - RS485
: - RTC
: SW Features:
: - CompuLab Deployment Tool
: - Linux CLI utilities for access to U-Boot environment
: - Docker
: Documentation:
: - Initial Debian Linux documentation for IOT-GATE-iMX8 / SBC-IOT-iMX8
}}

[[Category:Linux]]
[[Category:Debian]]
[[Category:IOT-GATE-iMX8]]
[[Category:SBC-IOT-iMX8]]

IOT-GATE-iMX8 and SBC-IOT-iMX8 NXP iMX8M-Mini Debian Linux

2023-06-28T07:14:03Z

Benjamin:

{{summary|
This page contains links to information about Linux kernels, packages and software development for the Compulab IOT-GATE-iMX8 Internet of Things Gateway and SBC-IOT-iMX8 Single Board Computer.

CompuLab Linux support for IOT-GATE-iMX8 and SBC-IOT-iMX8 includes Linux kernel and Debian file-system image based on [http://www.debian.org/ports/arm/ ARM Debian Linux]. The [https://www.debian.org/intro/about Debian Project] is an association of individuals who have made a common cause to create a free operating system. This operating system is called Debian.
It is also possible to use other embedded Linux distributions and environments with IOT-GATE-iMX8 and SBC-IOT-iMX8.
|iot-gate-imx8.png|thumb
}}

{{Resources Linux with app notes
|*[[IOT-GATE-iMX8: Getting Started|Getting started with IOT-GATE-iMX8]]
*[[IOT-GATE-iMX8 and SBC-IOT-iMX8: Debian Linux: Installation|Installing Debian on IOT-GATE-iMX8 / SBC-IOT-iMX8]]
*[[IOT-GATE-iMX8 and SBC-IOT-iMX8: Debian Linux: How-To Guide|Debian Linux how-to guide for IOT-GATE-iMX8 / SBC-IOT-iMX8]]
*[[IOT-GATE-iMX8 and SBC-IOT-iMX8: Debian Linux: Package contents|Debian Linux package contents]]
|*
*[https://github.com/compulab-yokneam/meta-bsp-imx8mm/blob/iot-gate-imx8-r3.2.1/Documentation/linux_kernel_build.md Building IOT-GATE-iMX8 / SBC-IOT-iMX8 Linux Kernel]
*[https://github.com/compulab-yokneam/meta-bsp-imx8mm/blob/iot-gate-imx8-r3.2.1/Documentation/imx_boot_image_build.md Building IOT-GATE-iMX8 / SBC-IOT-iMX8 U-boot image]
*[[IOT-GATE-iMX8 and SBC-IOT-iMX8: U-Boot: Recovery|U-Boot Recovery]]
|*[[IOT-GATE-iMX8 and SBC-IOT-iMX8: Linux: Production Deployment|Production Image Deployment]]
*[[Application Notes: eMMC lifetime optimization|Optimizing eMMC lifetime and reliability]]
}}

__NOTOC__

{{ChangelogRss| content=
===== 15-Jun-2023, IOT-GATE-iMX8 / SBC-IOT-iMX8 Debian Linux release 3.2.1 =====
: Release of Debian (Bullseye) for IOT-GATE-iMX8 / SBC-IOT-iMX8
: - Fixed the Docker issue

===== 21-May-2023, IOT-GATE-iMX8 / SBC-IOT-iMX8 Debian Linux release 3.2 =====
: Release of Debian (Bullseye) for IOT-GATE-iMX8 / SBC-IOT-iMX8
: - Kernel 5.15.32 (Requires bootloader upgrade to version 3.2)
: - U-Boot 2021.04
: - Add support for Intel AX210 WiFi/BT card
: - Added support for simultaneous operation of two IE-CL420 modules
: - Fixed USB power supply reset issue
: - Fixed cpufreq driver issue

===== 30-Jan-2023, IOT-GATE-iMX8 / SBC-IOT-iMX8 Debian Linux release 3.1.1 =====
: Release of Debian (Bullseye) for IOT-GATE-iMX8 / SBC-IOT-iMX8
: - Fix file-system journaling issue

===== 03-Aug-2022, IOT-GATE-iMX8 / SBC-IOT-iMX8 Debian Linux release 3.1 =====
: Release of Debian (Bullseye) for IOT-GATE-iMX8 / SBC-IOT-iMX8
: - Adjust the M4 core support to NXP release lf-5.10.72-2.2.0
: - Add OPP-TEE support to the U-Boot
: - Optimize file-system to improve eMMC lifetime

===== 24-Mar-2022, IOT-GATE-iMX8 / SBC-IOT-iMX8 Debian Linux release 3.0 =====
: Release of Debian (Bullseye) for IOT-GATE-iMX8 / SBC-IOT-iMX8
: - Based on NXP release lf-5.10.72-2.2.0
: - Kernel 5.10.72
: - U-Boot 2021.04
: - Add support for the Realtek RTL8211 PHY
: - Add support for Alliance 1GB DDR
: Documentation:
: - Updated multiple articles to comply with the new Debian package

===== 05-Dec-2021, IOT-GATE-iMX8 / SBC-IOT-iMX8 Debian Linux release 2.5 =====
: Release of Debian (Bullseye) for IOT-GATE-iMX8 / SBC-IOT-iMX8
: - Update the driver of the IE-CL420 module.
: - Add support for Samsung 4GB DDR.
: - Upgrade to Debian 11 (Bullseye).
: - Enable support for Microsoft Azure IoT Edge.
: Documentation:
: - Updated multiple articles to comply with the new Debian package

===== 20-Jun-2021, IOT-GATE-iMX8 / SBC-IOT-iMX8 Debian Linux release 2.4 =====
: Release of Debian (Buster) for IOT-GATE-iMX8 / SBC-IOT-iMX8
: - Add support for the POEv2 extension module.
: - Enable the net filter tables feature.
: - Enable setting the RTC time based on NTP.
: - Enable broadcast manager CAN Protocol.
: - Add the digital I/O add-on input GPIOs as a wakeup sources.
: Documentation:
: - Updated multiple articles to comply with the new Debian package

===== 16-Mar-2021, IOT-GATE-iMX8 / SBC-IOT-iMX8 Debian Linux release 2.3 =====
: Release of Debian (Buster) for IOT-GATE-iMX8 / SBC-IOT-iMX8
: - Add support for the M4 core.
: - Add support for the IE-CL420 module.
: - Add support for the IE-TPM module.
: - Update the CAN bus driver.
: Documentation:
: - Updated multiple articles to comply with the new Debian package

===== 17-Jan-2021, IOT-GATE-iMX8 / SBC-IOT-iMX8 Debian Linux release 2.2 =====
: Release of Debian (Buster) for IOT-GATE-iMX8 / SBC-IOT-iMX8
: - Reduce RTC battery usage when the power supply is disconnected.
: - Store manufacturing details in the device tree.
: - Update the CAN bus driver.
: - Add support to the POE extension module.
: Documentation:
: - Updated multiple articles to comply with the new Debian package

===== 10-Dec-2020, IOT-GATE-iMX8 / SBC-IOT-iMX8 Debian Linux release 2.1 =====
: Release of Debian (Buster) for IOT-GATE-iMX8 / SBC-IOT-iMX8
: - Upgrade to 64-bit Debian.
: - Fix signal configuration of Digital I/O add-on GPIOs.
: - Fix WiFi driver for 4GB RAM configuration.
: - Enable support for FTDI USB to serial driver.
: - Add support for mbpoll ModBus utility.
: Documentation:
: - Updated multiple articles to comply with the new Debian package

===== 18-Sep-2020, IOT-GATE-iMX8 / SBC-IOT-iMX8 Debian Linux release 2.0 =====
: Release of Debian (Buster) for IOT-GATE-iMX8 / SBC-IOT-iMX8
: - Kernel 5.4.24
: - U-Boot 2020.04
: HW supported features:
: - Industrial I/O extension boards
: Documentation:
: - Updated multiple articles to comply with the new Debian package

===== 5-May-2020, IOT-GATE-iMX8 / SBC-IOT-iMX8 Debian Linux release 1.0 =====
: Release of Debian (Buster) for IOT-GATE-iMX8 / SBC-IOT-iMX8
: - Based on NXP release L4.14.98-2.0.0_ga
: - Kernel 4.14.98
: HW Features:
: - eMMC storage
: - USB2.0 Host
: - Ethernet
: - WiFi (Intel AX200)
: - Bluetooth
: - LTE modem (SIM7600G)
: - CAN-FD
: - RS485
: - RTC
: SW Features:
: - CompuLab Deployment Tool
: - Linux CLI utilities for access to U-Boot environment
: - Docker
: Documentation:
: - Initial Debian Linux documentation for IOT-GATE-iMX8 / SBC-IOT-iMX8
}}

[[Category:Linux]]
[[Category:Debian]]
[[Category:IOT-GATE-iMX8]]
[[Category:SBC-IOT-iMX8]]

IOT-GATE-IMX8PLUS and SBC-IOT-IMX8PLUS SW Resources

2023-06-26T08:45:04Z

Benjamin:

{{summary2|content=
IOT-GATE-IMX8PLUS is an Internet of Things Gateway built around the NXP i.MX8M-Plus System-on-Chip. CompuLab IoT Gateways are highly customizable and cost effective industrial system designed for Internet of Things connectivity and remote control and monitoring applications. 
For projects that require custom housing with simple integration, IOT-GATE-IMX8PLUS is also offered without the enclosure – as SBC-IOT-IMX8PLUS. 
|image1=Iot-gate-imx8plus.png
|image2=Sbc-iot-imx8plus.png
}}
 

<div style="background: white; border: 1px solid black; padding: 1em;">
{| border="0" cellpadding="3" width="100%" align="center"
|-
! style="font-size: 125%; background-color: #eeeeee;" align="center" width="25%" | [[IOT-GATE-IMX8PLUS and SBC-IOT-IMX8PLUS Debian Linux|Debian Linux]]
! style="font-size: 125%; background-color: #eeeeee;" align="center" width="25%" | [[IOT-GATE-IMX8PLUS and SBC-IOT-IMX8PLUS Yocto Linux|Yocto Linux]]
|-

| align="center" | [[Image:Debian_logo.png|200px|link=IOT-GATE-IMX8PLUS and SBC-IOT-IMX8PLUS Debian Linux]]
| align="center" | [[Image:Yocto-Logo1.png|200px|link=IOT-GATE-IMX8PLUS and SBC-IOT-IMX8PLUS Yocto Linux]]

|}
</div>
__NOTOC__

{{note|1=From time to time CompuLab releases new software versions for IOT-GATE-IMX8PLUS and SBC-IOT-IMX8PLUS in order to fix bugs, address component changes and add functionality. It is highly recommended to subscribe to the [[Image:Feed-icon.png|16px]] [{{fullurl:{{FULLPAGENAME}}|action=feed}} '''IOT-GATE-IMX8PLUS and SBC-IOT-IMX8PLUS RSS Feed'''] in order to receive automatic notifications about software updates.}}

{{ChangelogRss| content=
===== 26-Jun-2023, IOT-GATE-IMX8PLUS / SBC-IOT-IMX8PLUS Yocto Linux release 2.0 =====
: Release of Yocto 4.0 (kirkstone) for IOT-GATE-IMX8PLUS / SBC-IOT-IMX8PLUS
: - U-Boot 2021.04 based on NXP lf-5.15.32-2.0.0
: - Kernel 5.15.32 based on NXP lf-5.15.32-2.0.0
: HW Features:
: - Added support for SB-IOTGIMX8PLUS EEPROM
: - Added support for LED Green_1
: - Added support for FCCAN I/O module
: - Added support for FXTPM add-on board
: - Added support for break-out add-on board
: Documentation:
: - Updated multiple articles to comply with the new release

===== 20-Mar-2023, IOT-GATE-IMX8PLUS / SBC-IOT-IMX8PLUS Debian Linux release 2.0 =====
: Release of Debian (Bullseye) for IOT-GATE-IMX8PLUS / SBC-IOT-IMX8PLUS
: - U-Boot 2021.04 based on NXP lf-5.10.35-2.0.0
: - Kernel 5.15.32 based on NXP lf-5.15.32-2.0.0
: - Added support for SB-IOTGIMX8PLUS EEPROM
: - Added support for LED Green_1
: - Added support for FCCAN I/O module
: - Added support for FXTPM add-on board
: - Added support for break-out add-on board
: - Linux startup - added initrd as a default startup scheme
: - Linux startup - added recovery mode based on initrd
: - Fixed file-system journaling issue
: Documentation:
: - Updated multiple articles to comply with the new release

===== 10-Oct-2022, IOT-GATE-IMX8PLUS / SBC-IOT-IMX8PLUS Yocto Linux release 1.0 =====
: Release of Yocto 4.0 (kirkstone) for IOT-GATE-IMX8PLUS / SBC-IOT-IMX8PLUS
: - U-Boot 2021.04 based on NXP lf_v2021.04
: - Kernel 5.15.32 based on NXP lf-5.15.y
: HW Features:
: - eMMC storage
: - USB3.0 Host port
: - 2x USB2.0 Host ports
: - 2x Ethernet
: - WiFi (Intel AX210)
: - Bluetooth
: - 4G/LTE modem (Quectel EC25E/EC25A)
: - 1x CAN 2.0B
: - Display output
: - Industrial I/O extension modules:
:: - Up to 3x RS485 / RS232
:: - Digital I/O( 4x DI, 4x DO)
: - RTC
: - Watchdog
: - 2x dual color user LEDs
: - 1x serial console (micro-USB connector)
: - USB programming interface for NXP SDP/UUU (micro-USB connector)
: SW Features:
: - CompuLab Deployment Tool
: - Linux CLI utilities for access to U-Boot environment
: Documentation:
: - Initial Yocto Linux documentation for IOT-GATE-IMX8PLUS / SBC-IOT-IMX8PLUS

===== 05-Aug-2022, IOT-GATE-IMX8PLUS / SBC-IOT-IMX8PLUS Debian Linux release 1.1 =====
: Release of Debian (Bullseye) for IOT-GATE-IMX8PLUS / SBC-IOT-IMX8PLUS
: - U-Boot 2021.04 based on NXP lf-5.10.35-2.0.0
: - Kernel 5.15.5 based on NXP lf-5.15.5-1.0.0
: HW Features:
: - eMMC storage
: - USB3.0 Host port
: - 2x USB2.0 Host ports
: - 2x Ethernet
: - WiFi (Intel AX210)
: - Bluetooth
: - 4G/LTE modem (Quectel EC25E/EC25A)
: - 1x CAN 2.0B
: - Display output
: - Industrial I/O extension modules:
:: - Up to 3x RS485 / RS232
:: - Digital I/O( 4x DI, 4x DO)
: - RTC
: - Watchdog
: - 2x dual color user LEDs
: - 1x serial console (micro-USB connector)
: - USB programming interface for NXP SDP/UUU (micro-USB connector)
: SW Features:
: - CompuLab Deployment Tool
: - Linux CLI utilities for access to U-Boot environment
: - Docker
: Documentation:
: - Initial Debian Linux documentation for IOT-GATE-IMX8PLUS / SBC-IOT-IMX8PLUS
}}

[[Category:IOT-GATE-IMX8PLUS]]
[[Category:SBC-IOT-IMX8PLUS]]

IOT-GATE-IMX8PLUS and SBC-IOT-IMX8PLUS Yocto Linux

2023-06-26T08:43:37Z

Benjamin:

{{summary2|content=
This page contains links to information about Yocto Linux distribution for the Compulab IOT-GATE-IMX8PLUS Internet of Things Gateway and SBC-IOT-IMX8PLUS Single Board Computer.
The Yocto Project is an open-source collaboration focused on embedded Linux development.

|image1=Iot-gate-imx8plus.png
|image2=Sbc-iot-imx8plus.png
}}
 

{{Resources Linux with app notes
|*[[IOT-GATE-IMX8PLUS: Getting Started|Getting started with IOT-GATE-IMX8PLUS]]
*[[SBC-IOT-IMX8PLUS: Getting Started|Getting started with SBC-IOT-IMX8PLUS]]
* [[IOT-GATE-IMX8PLUS and SBC-IOT-IMX8PLUS: Yocto Linux: Installation|Installing Yocto on IOT-GATE-IMX8PLUS / SBC-IOT-IMX8PLUS]]
* [[IOT-GATE-IMX8PLUS and SBC-IOT-IMX8PLUS: Yocto Linux: How-To Guide|Yocto Linux how-to guide for IOT-GATE-IMX8PLUS / SBC-IOT-IMX8PLUS]]
|* [[IOT-GATE-IMX8PLUS and SBC-IOT-IMX8PLUS: Yocto Linux: Building Yocto images |Building IOT-GATE-IMX8PLUS / SBC-IOT-IMX8PLUS Yocto Linux images ]]

*[https://github.com/compulab-yokneam/linux-compulab/blob/linux-compulab_v5.15.32/README.md Building IOT-GATE-IMX8PLUS / SBC-IOT-IMX8PLUS Linux Kernel]
*[[IOT-GATE-IMX8PLUS and SBC-IOT-IMX8PLUS: U-Boot: Recovery|U-Boot Recovery]]
|*[[Application Notes: eMMC lifetime optimization|Optimizing eMMC lifetime and reliability]]
}}

__NOTOC__

{{ChangelogRss| content=
===== 26-Jun-2023, IOT-GATE-IMX8PLUS / SBC-IOT-IMX8PLUS Yocto Linux release 2.0 =====
: Release of Yocto 4.0 (kirkstone) for IOT-GATE-IMX8PLUS / SBC-IOT-IMX8PLUS
: - U-Boot 2021.04 based on NXP lf-5.15.32-2.0.0
: - Kernel 5.15.32 based on NXP lf-5.15.32-2.0.0
: HW Features:
: - Added support for SB-IOTGIMX8PLUS EEPROM
: - Added support for LED Green_1
: - Added support for FCCAN I/O module
: - Added support for FXTPM add-on board
: - Added support for break-out add-on board
: Documentation:
: - Updated multiple articles to comply with the new release

===== 10-Oct-2022, IOT-GATE-IMX8PLUS / SBC-IOT-IMX8PLUS Yocto Linux release 1.0 =====
: Release of Yocto 4.0 (kirkstone) for IOT-GATE-IMX8PLUS / SBC-IOT-IMX8PLUS
: - U-Boot 2021.04 based on NXP lf_v2021.04
: - Kernel 5.15.32 based on NXP lf-5.15.y
: HW Features:
: - eMMC storage
: - USB3.0 Host port
: - 2x USB2.0 Host ports
: - 2x Ethernet
: - WiFi (Intel AX210)
: - Bluetooth
: - 4G/LTE modem (Quectel EC25E/EC25A)
: - 1x CAN 2.0B
: - Display output
: - Industrial I/O extension modules:
:: - Up to 3x RS485 / RS232
:: - Digital I/O( 4x DI, 4x DO)
: - RTC
: - Watchdog
: - 2x dual color user LEDs
: - 1x serial console (micro-USB connector)
: - USB programming interface for NXP SDP/UUU (micro-USB connector)
: SW Features:
: - CompuLab Deployment Tool
: - Linux CLI utilities for access to U-Boot environment
: Documentation:
: - Initial Yocto Linux documentation for IOT-GATE-IMX8PLUS / SBC-IOT-IMX8PLUS
}}

[[Category:Linux]]
[[Category:Yocto]]
[[Category:IOT-GATE-IMX8PLUS]]
[[Category:SBC-IOT-IMX8PLUS]]

IOT-GATE-IMX8PLUS and SBC-IOT-IMX8PLUS: Yocto Linux: How-To Guide

2023-06-26T08:38:52Z

Benjamin:

= Overview =
The example run-time Yocto Linux image for the CompuLab IOT-GATE-IMX8PLUS and SBC-IOT-IMX8PLUS was generated with Kirkstone Yocto build.
The image includes the needed drivers and utilities to operate the hardware components of the IOT-GATE-IMX8PLUS/SBC-IOT-IMX8PLUS.

The default Kirkstone Yocto image includes many software packages. Among them:

* Core system
* SSH server and client
* ConnMan
* ModemManager
* Bluez5 Bluetooth tools and daemons
* SocketCAN
* Minicom

= Connection and Login =
This Yocto rootfs comes with an empty root password.
No password is required for login.

To login into the Linux system, you may use a terminal emulator as described [[IOT-GATE-IMX8PLUS and SBC-IOT-IMX8PLUS Yocto Linux|here]], or connect through the network (ssh).
{{Important|The following examples assume '''root''' user.}}

= Connectivity =
IOT-GATE-IMX8PLUS / SBC-IOT-IMX8PLUS Yocto Linux Image includes [https://wiki.archlinux.org/title/ConnMan ConnMan] is a command-line network manager designed for use with embedded devices and fast resolve times. It can be used for managing all type of network interfaces:
# Wired
# Wireless
# Cellular

* Start '''ConnMan''' service prior to accessing network interfaces
<pre>root@iot-gate-imx8plus:~# systemctl start connman</pre>

* Display supported technologies
<pre>
root@iot-gate-imx8plus:~# connmanctl technologies
/net/connman/technology/cellular
Name = Cellular
Type = cellular
Powered = True
Connected = True
Tethering = False
TetheringFreq = 2412
/net/connman/technology/ethernet
Name = Wired
Type = ethernet
Powered = False
Connected = False
Tethering = False
TetheringFreq = 2412
/net/connman/technology/wifi
Name = WiFi
Type = wifi
Powered = True
Connected = False
Tethering = False
TetheringFreq = 2412
/net/connman/technology/bluetooth
Name = Bluetooth
Type = bluetooth
Powered = False
Connected = False
Tethering = False
TetheringFreq = 0
</pre>

== Ethernet ==
=== Enable/Disable Ethernet Interfaces ===
* To enable Ethernet interfaces:
:<pre>root@iot-gate-imx8plus:~# connmanctl enable ethernet</pre>
* To disable Ethernet interfaces:
:<pre>root@iot-gate-imx8plus:~# connmanctl disable ethernet</pre>

=== Enable/Disable Ethernet Connections ===
* To display Ethernet Connections:
:<pre>root@iot-gate-imx8plus:~# connmanctl services | grep ethernet</pre>
:Example (both Ethernet ports are connected to a LAN):
:<pre>root@iot-gate-imx8plus:~# connmanctl services | grep ethernet</pre>
:<pre>*AR Wired ethernet_0001c030d7c3_cable</pre>
:<pre>*AR Wired ethernet_0001c031ffe2_cable</pre>

* To enable Ethernet interfaces:
:<pre>root@iot-gate-imx8plus:~# connmanctl connect <ethernet service name></pre>
* To disable Ethernet interfaces:
:<pre>root@iot-gate-imx8plus:~# connmanctl disconnect <ethernet service name></pre>
:Example:
:<pre>root@iot-gate-imx8plus:~# connmanctl disconnect ethernet_0001c031ffe2_cable</pre>
:<pre>Disconnected ethernet_0001c031ffe2_cable</pre>
:<pre>root@iot-gate-imx8plus:~# connmanctl services | grep ethernet</pre>
:<pre>*AR Wired ethernet_0001c030d7c3_cable</pre>
:<pre>*A Wired ethernet_0001c031ffe2_cable</pre>
:<pre>root@iot-gate-imx8plus:~# connmanctl connect ethernet_0001c031ffe2_cable</pre>
:<pre>Connected ethernet_0001c031ffe2_cable</pre>

== Cellular Modem ==
=== Wvdial ===
{{Note| Recommended method}}
[https://wiki.debian.org/Wvdial WvDial] is a Point-to-Point Protocol dialer that automatically detects modem, and can log into almost any Internet Service Provider without a complicated configuration.

==== Loading kernel modules ====
Load Point-to-Point protocol (PPP) driver modules prior to dialing:
<pre>
root@cl-som-imx7-sid:~# modprobe ppp_generic
root@cl-som-imx7-sid:~# modprobe ppp_async
root@cl-som-imx7-sid:~# modprobe ppp_synctty
root@cl-som-imx7-sid:~# modprobe bsd_comp
root@cl-som-imx7-sid:~# modprobe ppp_deflate
</pre>

==== Dialing ====
* Example configuration file {{filename|/etc/wvdial.conf}}:
<pre>
cat << eof > /etc/wvdial.conf
[Dialer cellular]
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
Modem Type = Analog Modem
ISDN = 0
Phone = *99#
Modem = /dev/ttyUSB3
Username = dummy
Password = dummy
Baud = 9600
eof
</pre>
* Connect cellular network
:<pre>wvdial cellular &</pre>
* Verify the connection by pinging to google:
:<pre>sudo ping -c 5 dns.google</pre>
* Expected result:
:<pre>5 packets transmitted, 5 received, 0% packet loss, time 10ms</pre>
* Disconnect cellular network
:<pre>killall wvdial</pre>

=== ConnMan ===
==== Enable/Disable Cellular Interface ====
* To enable Cellular interfaces:
:<pre>root@iot-gate-imx8plus:~# connmanctl enable cellular</pre>
* To disable Cellular interfaces:
:<pre>root@iot-gate-imx8plus:~# connmanctl disable cellular</pre>

==== Enable/Disable Cellular Connections ====
* To display Cellular Connections:
:<pre>root@iot-gate-imx8plus:~# connmanctl services | grep cellular</pre>
:Example:
:<pre>root@iot-gate-imx8plus:~# connmanctl services | grep cellular</pre>
:<pre>*AR 425007 cellular_425071043611161_context1</pre>

* To connect Cellular network:
:<pre>root@iot-gate-imx8plus:~# connmanctl connect <cellular service name></pre>
* To disconnect the Cellular network:
:<pre>root@iot-gate-imx8plus:~# connmanctl disconnect <cellular service name></pre>

== WiFi ==
=== Enable/Disable WiFi Interface ===
* To enable WiFi interface:
:<pre>root@iot-gate-imx8plus:~# connmanctl enable wifi</pre>
* To disable WiFi interface:
:<pre>root@iot-gate-imx8plus:~# connmanctl disable wifi</pre>

=== Network Scanning ===
* Sample WiFi scanning:
:<pre>root@iot-gate-imx8plus:~# connmanctl scan wifi</pre>
* Display list of Access Points and Ad-Hoc cells in the range
:<pre>root@iot-gate-imx8plus:~# connmanctl services | grep wifi</pre>
:Example:
:<pre> Compulab-Guest wifi_8c1d96f18740_436f6d70756c61622d4775657374_managed_psk</pre>
:<pre> ...</pre>
:<pre> AP-Free wifi_8c1d96f18740_6b77696b2d6d6f62_managed_none</pre>
:Where a service name pattern is as shown below:
:<pre>wifi_<hashlocal>_<hashremote>_managed_<encrption></pre>

=== Connecting to Open Access Point ===
In the following example replace ''<hashlocal>'' and ''<hashremote>'' with the actual service parameters.
* Connect wireless network:
:<pre>root@iot-gate-imx8plus:~# connmanctl connect wifi_<hashlocal>_<hashremote>_managed_none</pre>
* Disconnect wireless network:
:<pre>root@iot-gate-imx8plus:~# connmanctl disconnect wifi_<hashlocal>_<hashremote>_managed_none</pre>

=== Connecting to Protected Access Point ===
For protected access points some information (like password) has to be provided to the ConnMan daemon.

The commands in this section show how to run '''connmanctl''' in interactive mode, it is required for running the agent command.
* Start interactive mode:
:<pre>root@iot-gate-imx8plus:~# connmanctl</pre>
* Sample WiFi scanning (wait for scan completed):
:<pre>connmanctl> scan wifi</pre>
* Display a list of services:
:<pre>connmanctl> services</pre>
:<pre> Compulab-Guest wifi_8c1d96f18740_436f6d70756c61622d4775657374_managed_psk</pre>
:<pre> ...</pre>
:<pre> AP-Free wifi_8c1d96f18740_6b77696b2d6d6f62_managed_none</pre>
* Register the agent to handle user requests:
:<pre>connmanctl> agent on</pre>
* Connect to one of the protected services. Replace ''<hashlocal>'' and ''<hashremote>'' with the actual service parameters:
:<pre>connmanctl> connect wifi_<hashlocal>_<hashremote>_managed_psk</pre>
:<pre>Agent RequestInput wifi_<hashlocal>_<hashremote>_managed_psk</pre>
:<pre> Passphrase = [ Type=psk, Requirement=mandatory ]</pre>
:<pre>Passphrase? </pre>
: Provide any information required by the daemon to complete the connection. The information requested may vary depending on the type of network.
* Quit:
:<pre>connmanctl> quit</pre>
* Disconnect wireless network:
:<pre>root@iot-gate-imx8plus:~# connmanctl disconnect wifi_<hashlocal>_<hashremote>_managed_psk</pre>
* Connect wireless network again:
:<pre>root@iot-gate-imx8plus:~# connmanctl connect wifi_<hashlocal>_<hashremote>_managed_psk</pre>

= CAN =
IOT-GATE-IMX8PLUS / SBC-IOT-IMX8PLUS features one CAN 2.0B port implemented with i.MX8M Plus CAN controller. 
CAN bus signals are routed to industrial I/O connector P8.

== CAN interface configuration ==
* Configure the CAN interface bit-rate to 1 Mbits/sec:
<pre>
root@iot-gate-imx8plus:~# ip link set can0 type can bitrate 1000000
</pre>
* Enable the CAN interface:
<pre>
root@iot-gate-imx8plus:~# ip link set can0 up
</pre>

== Send/Receive packets ==
Use ''cansend'' and ''candump'' utilities to send and receive packets via CAN interface.
* Send standard CAN frame (on the first device):
<pre>
root@iot-gate-imx8plus:~# cansend can0 111#1122334455667788
</pre>

* Send extended CAN frame (on the first device):
<pre>
root@iot-gate-imx8plus:~# cansend can0 11111111#1122334455667788
</pre>

* CAN frames (extended mode) generator, random payload, interval between two successive flames 50 msec:
<pre>
root@iot-gate-imx8plus:~# cangen -g 50 -e -D r -v can0
...
...
</pre>

* Dump all received data frames as well as error frames:
<pre>
root@iot-gate-imx8plus:~# candump any,0:0,#FFFFFFFF
...
...
</pre>

= Industrial Interfaces =
IOT-GATE-IMX8PLUS / SBC-IOT-IMX8PLUS implements industrial interfaces with four I/O slots (IE) that can be fitted with up-to four different I/O modules.
Slots are referred to as '''A''', '''B''', '''C''' and '''D'''.

Available I/O modules types:
* RS232 (2-wire)
* RS485 (half duplex)
* Digital I/O (4x DI + 4x DO)

{{Note|IOT-GATE-IMX8PLUS / SBC-IOT-IMX8PLUS industrial I/O signals are routed to Industrial I/O Connector (P8)}}
Please refer to Industrial I/O Connector pin-out for more details.

So far industrial I/O modules do not require any special configuration.

== RS232 ==
RS232 function is implemented with MAX3221 (or compatible) transceiver interfaced with i.MX8M Plus UART ports.

RS232 modules can be installed into I/O slots A, B and C. Up to three RS232 modules can be installed simultaneously.

=== Configuration and Access ===
Once properly installed on a specific I/O slot, RS232 interface can be accessed in Linux via '''ttyRS232_X''' tty device, where '''X''' is a slot name: A, B, C.

== RS485 ==
RS485 function is implemented with MAX13488 (or compatible) transceiver interfaced with i.MX8M Plus UART ports.

RS485 modules can be installed in I/O slots A, B and C. Up to three RS485 modules can be installed simultaneously.

=== Configuration and Access ===
Once properly installed on a specific I/O slot, RS485 interface can be accessed in Linux via '''ttyRS485_X''' tty device, where '''X''' is a slot name: A, B, C.

=== Modbus RS485 ===
The following example demonstrates how to use RS485 module installed into industrial I/O slot A in a Modbus RS485 Network.
IOTG-IMX8PLUS performs as a Master device and queries XY-MD02 temperature and humidity sensor.

==== Software installation ====
Download and install ''modpoll'' - a command line based Modbus master simulator and test utility.
<pre>
root@iot-gate-imx8plus:~# wget https://www.modbusdriver.com/downloads/modpoll.tgz -P /tmp/
...
root@iot-gate-imx8plus:~# tar -xvf /tmp/modpoll.tgz -C /opt/
...
</pre>

==== Device connection ====
* Connect XY-MD02 sensor to appropriate Industrial I/O connector pins as below:
:* '''A+''': XY-MD02 A+ to IOT-GATE-iMX8PLUS / SBC-IOT-IMX8PLUS P8-01
:* '''B-''': XY-MD02 B- to IOT-GATE-iMX8PLUS / SBC-IOT-IMX8PLUS P8-03
<pre>
-------------------- -------------------------
| | | |
| *--(+)---< <------------- 5V-30V | IOTG-IMX8PLUS |
| | | (SBC-IOT-IMX8PLUS) |
| *--(-)---< <-------------- GND |------ ------------ |
| XY-MD02 (RS485) | | |==| IE-RS485 | |
| *--(A+)--< <---...---> >---(1)---*-| | ------------ |
| | | P8 | Slot A |
| *--(B-)--< <---...---> >---(3)---*-| | |
| | |------ |
-------------------- -------------------------
</pre>

==== Read data ====

* Read temperature once:
<pre>
root@iot-gate-imx8plus:~# /opt/modpoll/arm-linux-gnueabihf/modpoll -b 9600 -p none -t 3 -c 1 -r 2 -1 /dev/ttyRS485_A
modpoll 3.10 - FieldTalk(tm) Modbus(R) Master Simulator
Copyright (c) 2002-2021 proconX Pty Ltd
Visit https://www.modbusdriver.com for Modbus libraries and tools.

Protocol configuration: Modbus RTU, FC4
Slave configuration...: address = 1, start reference = 2, count = 1
Communication.........: /dev/ttyRS485_A, 9600, 8, 1, none, t/o 1.00 s, poll rate 1000 ms
Data type.............: 16-bit register, input register table

-- Polling slave...
[2]: 250
</pre>

* Poll temperature:
<pre>
root@iot-gate-imx8plus:~# /opt/modpoll/arm-linux-gnueabihf/modpoll -b 9600 -p none -t 3 -c 1 -r 2 /dev/ttyRS485_A
modpoll 3.10 - FieldTalk(tm) Modbus(R) Master Simulator
Copyright (c) 2002-2021 proconX Pty Ltd
Visit https://www.modbusdriver.com for Modbus libraries and tools.

Protocol configuration: Modbus RTU, FC4
Slave configuration...: address = 1, start reference = 2, count = 1
Communication.........: /dev/ttyRS485_A, 9600, 8, 1, none, t/o 1.00 s, poll rate 1000 ms
Data type.............: 16-bit register, input register table

-- Polling slave... (Ctrl-C to stop)
[2]: 254
-- Polling slave... (Ctrl-C to stop)
[2]: 254
-- Polling slave... (Ctrl-C to stop)
[2]: 254
...
</pre>

* Read humidity once:
<pre>
root@iot-gate-imx8plus:~# /opt/modpoll/arm-linux-gnueabihf/modpoll -b 9600 -p none -t 3 -c 1 -r 3 -1 /dev/ttyRS485_A
modpoll 3.10 - FieldTalk(tm) Modbus(R) Master Simulator
Copyright (c) 2002-2021 proconX Pty Ltd
Visit https://www.modbusdriver.com for Modbus libraries and tools.

Protocol configuration: Modbus RTU, FC4
Slave configuration...: address = 1, start reference = 3, count = 1
Communication.........: /dev/ttyRS485_A, 9600, 8, 1, none, t/o 1.00 s, poll rate 1000 ms
Data type.............: 16-bit register, input register table

-- Polling slave...
[3]: 515
</pre>

* Poll humidity:
<pre>
root@iot-gate-imx8plus:~# /opt/modpoll/arm-linux-gnueabihf/modpoll -b 9600 -p none -t 3 -c 1 -r 3 /dev/ttyRS485_A
modpoll 3.10 - FieldTalk(tm) Modbus(R) Master Simulator
Copyright (c) 2002-2021 proconX Pty Ltd
Visit https://www.modbusdriver.com for Modbus libraries and tools.

Protocol configuration: Modbus RTU, FC4
Slave configuration...: address = 1, start reference = 3, count = 1
Communication.........: /dev/ttyRS485_A, 9600, 8, 1, none, t/o 1.00 s, poll rate 1000 ms
Data type.............: 16-bit register, input register table

-- Polling slave... (Ctrl-C to stop)
[3]: 894
-- Polling slave... (Ctrl-C to stop)
[3]: 895
-- Polling slave... (Ctrl-C to stop)
[3]: 896
...
</pre>

* Read temperature & humidity once:
<pre>
root@iot-gate-imx8plus:~# /opt/modpoll/arm-linux-gnueabihf/modpoll -b 9600 -p none -t 3 -c 2 -r 2 -1 /dev/ttyRS485_A
modpoll 3.10 - FieldTalk(tm) Modbus(R) Master Simulator
Copyright (c) 2002-2021 proconX Pty Ltd
Visit https://www.modbusdriver.com for Modbus libraries and tools.

Protocol configuration: Modbus RTU, FC4
Slave configuration...: address = 1, start reference = 2, count = 2
Communication.........: /dev/ttyRS485_A, 9600, 8, 1, none, t/o 1.00 s, poll rate 1000 ms
Data type.............: 16-bit register, input register table

-- Polling slave...
[2]: 263
[3]: 606
</pre>

* Poll temperature & humidity:
<pre>
root@iot-gate-imx8plus:~# /opt/modpoll/arm-linux-gnueabihf/modpoll -b 9600 -p none -t 3 -c 2 -r 2 /dev/ttyRS485_A
modpoll 3.10 - FieldTalk(tm) Modbus(R) Master Simulator
Copyright (c) 2002-2021 proconX Pty Ltd
Visit https://www.modbusdriver.com for Modbus libraries and tools.

Protocol configuration: Modbus RTU, FC4
Slave configuration...: address = 1, start reference = 2, count = 2
Communication.........: /dev/ttyRS485_A, 9600, 8, 1, none, t/o 1.00 s, poll rate 1000 ms
Data type.............: 16-bit register, input register table

-- Polling slave... (Ctrl-C to stop)
[2]: 263
[3]: 545
-- Polling slave... (Ctrl-C to stop)
[2]: 263
[3]: 543
-- Polling slave... (Ctrl-C to stop)
[2]: 263
[3]: 542
...
</pre>

* Read slave address, baudrate, temperature & humidity corrections:
<pre>
root@iot-gate-imx8plus:~# /opt/modpoll/arm-linux-gnueabihf/modpoll -b 9600 -p none -t 4 -c 4 -r 258 -1 /dev/ttyRS485_A
modpoll 3.10 - FieldTalk(tm) Modbus(R) Master Simulator
Copyright (c) 2002-2021 proconX Pty Ltd
Visit https://www.modbusdriver.com for Modbus libraries and tools.

Protocol configuration: Modbus RTU, FC3
Slave configuration...: address = 1, start reference = 258, count = 4
Communication.........: /dev/ttyRS485_A, 9600, 8, 1, none, t/o 1.00 s, poll rate 1000 ms
Data type.............: 16-bit register, output (holding) register table

-- Polling slave...
[258]: 1
[259]: 9600
[260]: 0
[261]: 0
</pre>

== Digital I/O ==
Digital I/O module features 4 digital inputs and 4 digital outputs and can be installed into slot D.
Four digital inputs are implemented with the CLT3-4B digital termination following EN 61131-2.
Four digital outputs are implemented with the VNI4140K solid-state relay following EN 61131-2. 
{{Note|Digital I/O module requires an external voltage supply up to 24V to be properly connected. Please refer to Industrial I/O Connector pin-out for more details.}}

=== Configuration and Access ===
Use ''iotg-imx8plus-dio'' utility to access digital inputs and outputs.

The example below shows how to access Digital inputs and outputs.
* Drive OUT2 pin HI:
<pre>
root@iot-gate-imx8plus:~# iotg-imx8plus-dio -o 2 1
</pre>

* Read IN3 pin state (LO):
<pre>
root@iot-gate-imx8plus:~# iotg-imx8plus-dio -i 3
0
</pre>

= LEDs =
IOT-GATE-IMX8PLUS / SBC-IOT-IMX8PLUS features two user Bi-Color (Red + Green) LEDs found on [[IOT-GATE-IMX8PLUS: Getting Started#Front panel|front panel]]. 
LEDs are controlled via GPIO pins and can be accessed via [https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-led sysfs] interface.

* LEDs are referred to as ''Green_1'', ''Red_1'', ''Green_2'' and ''Red_2''
* Choose a LED (LED2 Red in this example):
:<pre>root@iot-gate-imx8plus:~# LED=Red_2</pre>
* Turn the LED ON
:<pre>root@iot-gate-imx8plus:~# echo "1" | tee -a /sys/class/leds/${LED}/brightness</pre>
* Turn the LED OFF
:<pre>root@iot-gate-imx8plus:~# echo "0" | tee -a /sys/class/leds/${LED}/brightness</pre>
* Set LED's trigger
:<pre>root@iot-gate-imx8plus:~# echo "heartbeat" | tee -a /sys/class/leds/${LED}/trigger</pre>

= Video Playback=
{{note|The operation below requires '''root''' access.}}

IOT-GATE-IMX8PLUS and SBC-IOT-IMX8PLUS are built around UCM-iMX8M-Plus SoC that features 1080p60 H.264, VP8 video decoding capabilities. Before starting video playback, please, ensure that the display is connected to the board.

The following commands can be used to start video playback ('''1.mov''' is a media file):
* gst-play
:<pre>root@iot-gate-imx8plus:~# gst-play /path/to/1.mov</pre>

* gplay-1.0
:<pre>root@iot-gate-imx8plus:~# gplay-1.0 /path/to/1.mov</pre>

* gst-launch
This method is for advanced users. Please study this document before the start: [https://raw.githubusercontent.com/compulab-yokneam/Documentation/master/pdfs/i.MX8GStreamerUserGuide.pdf i.MX8GStreamerUserGuide.pdf]
:<pre>root@iot-gate-imx8plus:~# gst-launch-1.0 -v filesrc location=/path/to/1.mov ! qtdemux name=d.video_0 ! h264parse ! avdec_h264 ! autovideosink</pre>

IOT-GATE-IMX8PLUS and SBC-IOT-IMX8PLUS: Yocto Linux: How-To Guide

2023-06-26T08:36:47Z

Benjamin:

= Overview =
The example run-time Yocto Linux image for the CompuLab IOT-GATE-IMX8PLUS and SBC-IOT-IMX8PLUS was generated with Kirkstone Yocto build.
The image includes the needed drivers and utilities to operate the hardware components of the IOT-GATE-IMX8PLUS/SBC-IOT-IMX8PLUS.

The default Kirkstone Yocto image includes many software packages. Among them:

* Core system
* SSH server and client
* ConnMan
* ModemManager
* Bluez5 Bluetooth tools and daemons
* SocketCAN
* Minicom

= Connection and Login =
This Yocto rootfs comes with an empty root password.
No password is required for login.

To login into the Linux system, you may use a terminal emulator as described [[IOT-GATE-IMX8PLUS and SBC-IOT-IMX8PLUS Yocto Linux|here]], or connect through the network (ssh).
{{Important|The following examples assume '''root''' user.}}

= Connectivity =
IOT-GATE-IMX8PLUS / SBC-IOT-IMX8PLUS Yocto Linux Image includes [https://wiki.archlinux.org/title/ConnMan ConnMan] is a command-line network manager designed for use with embedded devices and fast resolve times. It can be used for managing all type of network interfaces:
# Wired
# Wireless
# Cellular

* Start '''ConnMan''' service prior to accessing network interfaces
<pre>root@iot-gate-imx8plus:~# systemctl start connman</pre>

* Display supported technologies
<pre>
root@iot-gate-imx8plus:~# connmanctl technologies
/net/connman/technology/cellular
Name = Cellular
Type = cellular
Powered = True
Connected = True
Tethering = False
TetheringFreq = 2412
/net/connman/technology/ethernet
Name = Wired
Type = ethernet
Powered = False
Connected = False
Tethering = False
TetheringFreq = 2412
/net/connman/technology/wifi
Name = WiFi
Type = wifi
Powered = True
Connected = False
Tethering = False
TetheringFreq = 2412
/net/connman/technology/bluetooth
Name = Bluetooth
Type = bluetooth
Powered = False
Connected = False
Tethering = False
TetheringFreq = 0
</pre>

== Ethernet ==
=== Enable/Disable Ethernet Interfaces ===
* To enable Ethernet interfaces:
:<pre>root@iot-gate-imx8plus:~# connmanctl enable ethernet</pre>
* To disable Ethernet interfaces:
:<pre>root@iot-gate-imx8plus:~# connmanctl disable ethernet</pre>

=== Enable/Disable Ethernet Connections ===
* To display Ethernet Connections:
:<pre>root@iot-gate-imx8plus:~# connmanctl services | grep ethernet</pre>
:Example (both Ethernet ports are connected to a LAN):
:<pre>root@iot-gate-imx8plus:~# connmanctl services | grep ethernet</pre>
:<pre>*AR Wired ethernet_0001c030d7c3_cable</pre>
:<pre>*AR Wired ethernet_0001c031ffe2_cable</pre>

* To enable Ethernet interfaces:
:<pre>root@iot-gate-imx8plus:~# connmanctl connect <ethernet service name></pre>
* To disable Ethernet interfaces:
:<pre>root@iot-gate-imx8plus:~# connmanctl disconnect <ethernet service name></pre>
:Example:
:<pre>root@iot-gate-imx8plus:~# connmanctl disconnect ethernet_0001c031ffe2_cable</pre>
:<pre>Disconnected ethernet_0001c031ffe2_cable</pre>
:<pre>root@iot-gate-imx8plus:~# connmanctl services | grep ethernet</pre>
:<pre>*AR Wired ethernet_0001c030d7c3_cable</pre>
:<pre>*A Wired ethernet_0001c031ffe2_cable</pre>
:<pre>root@iot-gate-imx8plus:~# connmanctl connect ethernet_0001c031ffe2_cable</pre>
:<pre>Connected ethernet_0001c031ffe2_cable</pre>

== Cellular Modem ==
=== Wvdial ===
{{Note| Recommended method}}
[https://wiki.debian.org/Wvdial WvDial] is a Point-to-Point Protocol dialer that automatically detects modem, and can log into almost any Internet Service Provider without a complicated configuration.

==== Loading kernel modules ====
Load Point-to-Point protocol (PPP) driver modules prior to dialing:
<pre>
root@cl-som-imx7-sid:~# modprobe ppp_generic
root@cl-som-imx7-sid:~# modprobe ppp_async
root@cl-som-imx7-sid:~# modprobe ppp_synctty
root@cl-som-imx7-sid:~# modprobe bsd_comp
root@cl-som-imx7-sid:~# modprobe ppp_deflate
</pre>

==== Dialing ====
* Example configuration file {{filename|/etc/wvdial.conf}}:
<pre>
cat << eof > /etc/wvdial.conf
[Dialer cellular]
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
Modem Type = Analog Modem
ISDN = 0
Phone = *99#
Modem = /dev/ttyUSB3
Username = dummy
Password = dummy
Baud = 9600
eof
</pre>
* Connect cellular network
:<pre>wvdial cellular &</pre>
* Verify the connection by pinging to google:
:<pre>sudo ping -c 5 dns.google</pre>
* Expected result:
:<pre>5 packets transmitted, 5 received, 0% packet loss, time 10ms</pre>
* Disconnect cellular network
:<pre>killall wvdial</pre>

=== ConnMan ===
==== Enable/Disable Cellular Interface ====
* To enable Ethernet interfaces:
:<pre>root@iot-gate-imx8plus:~# connmanctl enable cellular</pre>
* To disable Ethernet interfaces:
:<pre>root@iot-gate-imx8plus:~# connmanctl disable cellular</pre>

==== Enable/Disable Cellular Connections ====
* To display Cellular Connections:
:<pre>root@iot-gate-imx8plus:~# connmanctl services | grep cellular</pre>
:Example:
:<pre>root@iot-gate-imx8plus:~# connmanctl services | grep cellular</pre>
:<pre>*AR 425007 cellular_425071043611161_context1</pre>

* To connect Cellular network:
:<pre>root@iot-gate-imx8plus:~# connmanctl connect <cellular service name></pre>
* To disconnect Cellular network:
:<pre>root@iot-gate-imx8plus:~# connmanctl disconnect <cellular service name></pre>

== WiFi ==
=== Enable/Disable WiFi Interface ===
* To enable WiFi interface:
:<pre>root@iot-gate-imx8plus:~# connmanctl enable wifi</pre>
* To disable WiFi interface:
:<pre>root@iot-gate-imx8plus:~# connmanctl disable wifi</pre>

=== Network Scanning ===
* Sample WiFi scanning:
:<pre>root@iot-gate-imx8plus:~# connmanctl scan wifi</pre>
* Display list of Access Points and Ad-Hoc cells in range
:<pre>root@iot-gate-imx8plus:~# connmanctl services | grep wifi</pre>
:Example:
:<pre> Compulab-Guest wifi_8c1d96f18740_436f6d70756c61622d4775657374_managed_psk</pre>
:<pre> ...</pre>
:<pre> AP-Free wifi_8c1d96f18740_6b77696b2d6d6f62_managed_none</pre>
:Where a service name pattern is as shown below:
:<pre>wifi_<hashlocal>_<hashremote>_managed_<encrption></pre>

=== Connecting to Open Access Point ===
In the following example replace ''<hashlocal>'' and ''<hashremote>'' with the actual service parameters.
* Connect wireless network:
:<pre>root@iot-gate-imx8plus:~# connmanctl connect wifi_<hashlocal>_<hashremote>_managed_none</pre>
* Disconnect wireless network:
:<pre>root@iot-gate-imx8plus:~# connmanctl disconnect wifi_<hashlocal>_<hashremote>_managed_none</pre>

=== Connecting to Protected Access Point ===
For protected access points some information (like password) has to be provided to the ConnMan daemon.

The commands in this section show how to run '''connmanctl''' in interactive mode, it is required for running the agent command.
* Start interactive mode:
:<pre>root@iot-gate-imx8plus:~# connmanctl</pre>
* Sample WiFi scanning (wait for scan completed):
:<pre>connmanctl> scan wifi</pre>
* Display a list of services:
:<pre>connmanctl> services</pre>
:<pre> Compulab-Guest wifi_8c1d96f18740_436f6d70756c61622d4775657374_managed_psk</pre>
:<pre> ...</pre>
:<pre> AP-Free wifi_8c1d96f18740_6b77696b2d6d6f62_managed_none</pre>
* Register the agent to handle user requests:
:<pre>connmanctl> agent on</pre>
* Connect to one of the protected services. Replace ''<hashlocal>'' and ''<hashremote>'' with the actual service parameters:
:<pre>connmanctl> connect wifi_<hashlocal>_<hashremote>_managed_psk</pre>
:<pre>Agent RequestInput wifi_<hashlocal>_<hashremote>_managed_psk</pre>
:<pre> Passphrase = [ Type=psk, Requirement=mandatory ]</pre>
:<pre>Passphrase? </pre>
: Provide any information required by the daemon to complete the connection. The information requested may vary depending on the type of network.
* Quit:
:<pre>connmanctl> quit</pre>
* Disconnect wireless network:
:<pre>root@iot-gate-imx8plus:~# connmanctl disconnect wifi_<hashlocal>_<hashremote>_managed_psk</pre>
* Connect wireless network again:
:<pre>root@iot-gate-imx8plus:~# connmanctl connect wifi_<hashlocal>_<hashremote>_managed_psk</pre>

= CAN =
IOT-GATE-IMX8PLUS / SBC-IOT-IMX8PLUS features one CAN 2.0B port implemented with i.MX8M Plus CAN controller. 
CAN bus signals are routed to industrial I/O connector P8.

== CAN interface configuration ==
* Configure the CAN interface bit-rate to 1 Mbits/sec:
<pre>
root@iot-gate-imx8plus:~# ip link set can0 type can bitrate 1000000
</pre>
* Enable the CAN interface:
<pre>
root@iot-gate-imx8plus:~# ip link set can0 up
</pre>

== Send/Receive packets ==
Use ''cansend'' and ''candump'' utilities to send and receive packets via CAN interface.
* Send standard CAN frame (on the first device):
<pre>
root@iot-gate-imx8plus:~# cansend can0 111#1122334455667788
</pre>

* Send extended CAN frame (on the first device):
<pre>
root@iot-gate-imx8plus:~# cansend can0 11111111#1122334455667788
</pre>

* CAN frames (extended mode) generator, random payload, interval between two successive flames 50 msec:
<pre>
root@iot-gate-imx8plus:~# cangen -g 50 -e -D r -v can0
...
...
</pre>

* Dump all received data frames as well as error frames:
<pre>
root@iot-gate-imx8plus:~# candump any,0:0,#FFFFFFFF
...
...
</pre>

= Industrial Interfaces =
IOT-GATE-IMX8PLUS / SBC-IOT-IMX8PLUS implements industrial interfaces with four I/O slots (IE) that can be fitted with up-to four different I/O modules.
Slots are referred to as '''A''', '''B''', '''C''' and '''D'''.

Available I/O modules types:
* RS232 (2-wire)
* RS485 (half duplex)
* Digital I/O (4x DI + 4x DO)

{{Note|IOT-GATE-IMX8PLUS / SBC-IOT-IMX8PLUS industrial I/O signals are routed to Industrial I/O Connector (P8)}}
Please refer to Industrial I/O Connector pin-out for more details.

So far industrial I/O modules do not require any special configuration.

== RS232 ==
RS232 function is implemented with MAX3221 (or compatible) transceiver interfaced with i.MX8M Plus UART ports.

RS232 modules can be installed into I/O slots A, B and C. Up to three RS232 modules can be installed simultaneously.

=== Configuration and Access ===
Once properly installed on a specific I/O slot, RS232 interface can be accessed in Linux via '''ttyRS232_X''' tty device, where '''X''' is a slot name: A, B, C.

== RS485 ==
RS485 function is implemented with MAX13488 (or compatible) transceiver interfaced with i.MX8M Plus UART ports.

RS485 modules can be installed in I/O slots A, B and C. Up to three RS485 modules can be installed simultaneously.

=== Configuration and Access ===
Once properly installed on a specific I/O slot, RS485 interface can be accessed in Linux via '''ttyRS485_X''' tty device, where '''X''' is a slot name: A, B, C.

=== Modbus RS485 ===
The following example demonstrates how to use RS485 module installed into industrial I/O slot A in a Modbus RS485 Network.
IOTG-IMX8PLUS performs as a Master device and queries XY-MD02 temperature and humidity sensor.

==== Software installation ====
Download and install ''modpoll'' - a command line based Modbus master simulator and test utility.
<pre>
root@iot-gate-imx8plus:~# wget https://www.modbusdriver.com/downloads/modpoll.tgz -P /tmp/
...
root@iot-gate-imx8plus:~# tar -xvf /tmp/modpoll.tgz -C /opt/
...
</pre>

==== Device connection ====
* Connect XY-MD02 sensor to appropriate Industrial I/O connector pins as below:
:* '''A+''': XY-MD02 A+ to IOT-GATE-iMX8PLUS / SBC-IOT-IMX8PLUS P8-01
:* '''B-''': XY-MD02 B- to IOT-GATE-iMX8PLUS / SBC-IOT-IMX8PLUS P8-03
<pre>
-------------------- -------------------------
| | | |
| *--(+)---< <------------- 5V-30V | IOTG-IMX8PLUS |
| | | (SBC-IOT-IMX8PLUS) |
| *--(-)---< <-------------- GND |------ ------------ |
| XY-MD02 (RS485) | | |==| IE-RS485 | |
| *--(A+)--< <---...---> >---(1)---*-| | ------------ |
| | | P8 | Slot A |
| *--(B-)--< <---...---> >---(3)---*-| | |
| | |------ |
-------------------- -------------------------
</pre>

==== Read data ====

* Read temperature once:
<pre>
root@iot-gate-imx8plus:~# /opt/modpoll/arm-linux-gnueabihf/modpoll -b 9600 -p none -t 3 -c 1 -r 2 -1 /dev/ttyRS485_A
modpoll 3.10 - FieldTalk(tm) Modbus(R) Master Simulator
Copyright (c) 2002-2021 proconX Pty Ltd
Visit https://www.modbusdriver.com for Modbus libraries and tools.

Protocol configuration: Modbus RTU, FC4
Slave configuration...: address = 1, start reference = 2, count = 1
Communication.........: /dev/ttyRS485_A, 9600, 8, 1, none, t/o 1.00 s, poll rate 1000 ms
Data type.............: 16-bit register, input register table

-- Polling slave...
[2]: 250
</pre>

* Poll temperature:
<pre>
root@iot-gate-imx8plus:~# /opt/modpoll/arm-linux-gnueabihf/modpoll -b 9600 -p none -t 3 -c 1 -r 2 /dev/ttyRS485_A
modpoll 3.10 - FieldTalk(tm) Modbus(R) Master Simulator
Copyright (c) 2002-2021 proconX Pty Ltd
Visit https://www.modbusdriver.com for Modbus libraries and tools.

Protocol configuration: Modbus RTU, FC4
Slave configuration...: address = 1, start reference = 2, count = 1
Communication.........: /dev/ttyRS485_A, 9600, 8, 1, none, t/o 1.00 s, poll rate 1000 ms
Data type.............: 16-bit register, input register table

-- Polling slave... (Ctrl-C to stop)
[2]: 254
-- Polling slave... (Ctrl-C to stop)
[2]: 254
-- Polling slave... (Ctrl-C to stop)
[2]: 254
...
</pre>

* Read humidity once:
<pre>
root@iot-gate-imx8plus:~# /opt/modpoll/arm-linux-gnueabihf/modpoll -b 9600 -p none -t 3 -c 1 -r 3 -1 /dev/ttyRS485_A
modpoll 3.10 - FieldTalk(tm) Modbus(R) Master Simulator
Copyright (c) 2002-2021 proconX Pty Ltd
Visit https://www.modbusdriver.com for Modbus libraries and tools.

Protocol configuration: Modbus RTU, FC4
Slave configuration...: address = 1, start reference = 3, count = 1
Communication.........: /dev/ttyRS485_A, 9600, 8, 1, none, t/o 1.00 s, poll rate 1000 ms
Data type.............: 16-bit register, input register table

-- Polling slave...
[3]: 515
</pre>

* Poll humidity:
<pre>
root@iot-gate-imx8plus:~# /opt/modpoll/arm-linux-gnueabihf/modpoll -b 9600 -p none -t 3 -c 1 -r 3 /dev/ttyRS485_A
modpoll 3.10 - FieldTalk(tm) Modbus(R) Master Simulator
Copyright (c) 2002-2021 proconX Pty Ltd
Visit https://www.modbusdriver.com for Modbus libraries and tools.

Protocol configuration: Modbus RTU, FC4
Slave configuration...: address = 1, start reference = 3, count = 1
Communication.........: /dev/ttyRS485_A, 9600, 8, 1, none, t/o 1.00 s, poll rate 1000 ms
Data type.............: 16-bit register, input register table

-- Polling slave... (Ctrl-C to stop)
[3]: 894
-- Polling slave... (Ctrl-C to stop)
[3]: 895
-- Polling slave... (Ctrl-C to stop)
[3]: 896
...
</pre>

* Read temperature & humidity once:
<pre>
root@iot-gate-imx8plus:~# /opt/modpoll/arm-linux-gnueabihf/modpoll -b 9600 -p none -t 3 -c 2 -r 2 -1 /dev/ttyRS485_A
modpoll 3.10 - FieldTalk(tm) Modbus(R) Master Simulator
Copyright (c) 2002-2021 proconX Pty Ltd
Visit https://www.modbusdriver.com for Modbus libraries and tools.

Protocol configuration: Modbus RTU, FC4
Slave configuration...: address = 1, start reference = 2, count = 2
Communication.........: /dev/ttyRS485_A, 9600, 8, 1, none, t/o 1.00 s, poll rate 1000 ms
Data type.............: 16-bit register, input register table

-- Polling slave...
[2]: 263
[3]: 606
</pre>

* Poll temperature & humidity:
<pre>
root@iot-gate-imx8plus:~# /opt/modpoll/arm-linux-gnueabihf/modpoll -b 9600 -p none -t 3 -c 2 -r 2 /dev/ttyRS485_A
modpoll 3.10 - FieldTalk(tm) Modbus(R) Master Simulator
Copyright (c) 2002-2021 proconX Pty Ltd
Visit https://www.modbusdriver.com for Modbus libraries and tools.

Protocol configuration: Modbus RTU, FC4
Slave configuration...: address = 1, start reference = 2, count = 2
Communication.........: /dev/ttyRS485_A, 9600, 8, 1, none, t/o 1.00 s, poll rate 1000 ms
Data type.............: 16-bit register, input register table

-- Polling slave... (Ctrl-C to stop)
[2]: 263
[3]: 545
-- Polling slave... (Ctrl-C to stop)
[2]: 263
[3]: 543
-- Polling slave... (Ctrl-C to stop)
[2]: 263
[3]: 542
...
</pre>

* Read slave address, baudrate, temperature & humidity corrections:
<pre>
root@iot-gate-imx8plus:~# /opt/modpoll/arm-linux-gnueabihf/modpoll -b 9600 -p none -t 4 -c 4 -r 258 -1 /dev/ttyRS485_A
modpoll 3.10 - FieldTalk(tm) Modbus(R) Master Simulator
Copyright (c) 2002-2021 proconX Pty Ltd
Visit https://www.modbusdriver.com for Modbus libraries and tools.

Protocol configuration: Modbus RTU, FC3
Slave configuration...: address = 1, start reference = 258, count = 4
Communication.........: /dev/ttyRS485_A, 9600, 8, 1, none, t/o 1.00 s, poll rate 1000 ms
Data type.............: 16-bit register, output (holding) register table

-- Polling slave...
[258]: 1
[259]: 9600
[260]: 0
[261]: 0
</pre>

== Digital I/O ==
Digital I/O module features 4 digital inputs and 4 digital outputs and can be installed into slot D.
Four digital inputs are implemented with the CLT3-4B digital termination following EN 61131-2.
Four digital outputs are implemented with the VNI4140K solid-state relay following EN 61131-2. 
{{Note|Digital I/O module requires an external voltage supply up to 24V to be properly connected. Please refer to Industrial I/O Connector pin-out for more details.}}

=== Configuration and Access ===
Use ''iotg-imx8plus-dio'' utility to access digital inputs and outputs.

The example below shows how to access Digital inputs and outputs.
* Drive OUT2 pin HI:
<pre>
root@iot-gate-imx8plus:~# iotg-imx8plus-dio -o 2 1
</pre>

* Read IN3 pin state (LO):
<pre>
root@iot-gate-imx8plus:~# iotg-imx8plus-dio -i 3
0
</pre>

= LEDs =
IOT-GATE-IMX8PLUS / SBC-IOT-IMX8PLUS features two user Bi-Color (Red + Green) LEDs found on [[IOT-GATE-IMX8PLUS: Getting Started#Front panel|front panel]]. 
LEDs are controlled via GPIO pins and can be accessed via [https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-led sysfs] interface.

* LEDs are referred to as ''Green_1'', ''Red_1'', ''Green_2'' and ''Red_2''
* Choose a LED (LED2 Red in this example):
:<pre>root@iot-gate-imx8plus:~# LED=Red_2</pre>
* Turn the LED ON
:<pre>root@iot-gate-imx8plus:~# echo "1" | tee -a /sys/class/leds/${LED}/brightness</pre>
* Turn the LED OFF
:<pre>root@iot-gate-imx8plus:~# echo "0" | tee -a /sys/class/leds/${LED}/brightness</pre>
* Set LED's trigger
:<pre>root@iot-gate-imx8plus:~# echo "heartbeat" | tee -a /sys/class/leds/${LED}/trigger</pre>

= Video Playback=
{{note|The operation below requires '''root''' access.}}

IOT-GATE-IMX8PLUS and SBC-IOT-IMX8PLUS are built around UCM-iMX8M-Plus SoC that features 1080p60 H.264, VP8 video decoding capabilities. Before starting video playback, please, ensure that the display is connected to the board.

The following commands can be used to start video playback ('''1.mov''' is a media file):
* gst-play
:<pre>root@iot-gate-imx8plus:~# gst-play /path/to/1.mov</pre>

* gplay-1.0
:<pre>root@iot-gate-imx8plus:~# gplay-1.0 /path/to/1.mov</pre>

* gst-launch
This method is for advanced users. Please study this document before the start: [https://raw.githubusercontent.com/compulab-yokneam/Documentation/master/pdfs/i.MX8GStreamerUserGuide.pdf i.MX8GStreamerUserGuide.pdf]
:<pre>root@iot-gate-imx8plus:~# gst-launch-1.0 -v filesrc location=/path/to/1.mov ! qtdemux name=d.video_0 ! h264parse ! avdec_h264 ! autovideosink</pre>

IOT-GATE-IMX8PLUS and SBC-IOT-IMX8PLUS: Yocto Linux: Building Yocto images

2023-06-26T08:32:08Z

Benjamin:

= Overview =
The Yocto Project is an open-source collaboration focused on embedded Linux development. 
The purpose of this article is to show how to build a Yocto image for the IOT-GATE-IMX8PLUS Internet of Things Gateway and SBC-IOT-IMX8PLUS Single Board Computer.

= Host System Requirements =
To ensure optimal Yocto build speed and performance, it is recommended to use a host system with at least 4 CPU cores, 16GB RAM, and 500GB of free disk space. 
In addition, the system should have the option to open a large number of files simultaneously, preferably up to 4096 or higher. 
[https://www.yoctoproject.org/docs/ Learn more about Yocto]

= Docker Host for Yocto Build Environment =
There are often compatibility issues between different Linux distributions and the dependencies required for Yocto compilation. 
In order to avoid such issues and simplify the host machine configuration process, Compulab recommends using a pre-configured Docker environment. 
Please follow the instructions outlined in [https://github.com/compulab-yokneam/yocker Setting up Yocto Build Docker Environment].

= Building Yocto Images =
Set up the Yocto build environment and build the image as detailed in the [https://github.com/compulab-yokneam/meta-bsp-imx8mp/blob/iot-gate-imx8plus_r2.0/README.md Building IOT-GATE-IMX8PLUS / SBC-IOT-IMX8PLUS Yocto Linux images] guide.
 
 

[[Category:Linux]]
[[Category:Yocto]]
[[Category:IOT-GATE-IMX8PLUS]]
[[Category:SBC-IOT-IMX8PLUS]]

Transclusion: CL-SOM-iMX7: U-Boot: Building Images

2023-06-26T08:08:27Z

Benjamin:

==== Snapshot download ====
* Download [https://github.com/u-boot/u-boot/archive/refs/tags/v2017.07.tar.gz v2017.07] snapshot with your web browser.
* Extract the downloaded archive {{filename|u-boot-2017.07.tar.gz}}
<pre>
cd /home/development/cl-som-imx7/u-boot
tar xvf /path/to/downloaded/u-boot-2017.07.tar.gz
mv u-boot* u-boot-cl-som-imx7
</pre>
: This will create {{filename|/home/development/cl-som-imx7/u-boot/u-boot-cl-som-imx7}} directory containing U-Boot source code tree.
* Apply the CL-SOM-iMX7 patch
<pre>
cd /home/development/cl-som-imx7/u-boot/u-boot-cl-som-imx7
patch -p1 < /path/to/cl-som-imx7-u-boot-package/u-boot/u-boot-*.patch
</pre>

==== Git clone ====
* Install [http://git-scm.com/ git] version control system.
* Create a clone of U-Boot tree
<pre>
cd /home/development/cl-som-imx7/u-boot
git clone git://git.denx.de/u-boot.git u-boot-cl-som-imx7
cd /home/development/cl-som-imx7/u-boot/u-boot-cl-som-imx7
</pre>
* Create a branch for CL-SOM-iMX7 development. The CL-SOM-iMX7 patches are generated vs. v2017.07 tag (d85ca029f257b53a96da6c2fb421e78a003a9943 commit) in the U-Boot tree. It is recommended to use exactly the same baseline to avoid merge conflicts.
<pre>
git checkout -b cl-som-imx7-dev v2017.07
</pre>
* Apply CL-SOM-iMX7 patch
<pre>
git am /path/to/cl-som-imx7-u-boot-package/u-boot/patches/*.patch
</pre>

=== Building the firmware images ===
* First, compile U-Boot. The following commands create the {{filename|u-boot.imx}} binary (along with other image types):
<pre>
export ARCH=arm
export CROSS_COMPILE=arm-none-linux-eabi-
make mrproper
make cl-som-imx7_defconfig && make
</pre>
* Merge the SPL and U-Boot images into one firmware image:
<pre>
dd if=/dev/zero count=640 bs=1K | tr '\000' '\377' > cl-som-imx7-firmware
dd if=SPL of=cl-som-imx7-firmware bs=1K seek=1 conv=notrunc
dd if=u-boot.img of=cl-som-imx7-firmware bs=1K seek=64 conv=notrunc
</pre>

UCM-iMX93: Yocto Linux: Installing Yocto images onto UCM-iMX93 eMMC

2023-06-19T14:59:18Z

Benjamin:

Please use the `CompuLab Deployment Tool` to install UCM-iMX93 Yocto Linux onto on-board eMMC storage.

The `CompuLab Deployment Tool` is a shell script that allows to deploy a working OS image from micro-SD card to UCM-iMX93 on-board storage (eMMC).

Follow the step-by-step procedure for a selected image:

==Installing Yocto images onto UCM-iMX93 eMMC==
* Prepare a bootable SD card and use it to boot the system [[UCM-iMX93:_Yocto_Linux:_Manual_Installation:_SD_card|as described here]].
* [[UCM-iMX93:_Yocto_Linux:_Manual_Installation:_SD_card#Run%20Yocto%20Linux%20image|Run the Yocto Linux image]] that you intend to deploy.
* In the terminal window issue: <pre>cl-deploy</pre>
* Follow the steps below:

{| width="60%" cellspacing="1" cellpadding="1" border="1"
|-
| align="center" | '''Action'''
| align="center" | '''Screenshot'''
|-
|
:Select installation target storage: on UCM-iMX93 on-board eMMC device is called '''mmcblk0'''
| align="center" | [[File:wayland_cl-deploy_dst_choice.png|400px]]
|-
|
:Be aware of the fact that all the data on the target storage will be erased
| align="center" | [[File:wayland_cl-deploy_last_warning.png|400px]]
|-
|
:While installation process is running the output screen shows the log and progress
| align="center" | [[File:wayland_cl-deploy_process.png|400px]]
|-
|
:When installation is complete, the following message will show up
| align="center" | [[File:wayland_cl-deploy_finish.png|400px]]
|}

==Post installation==
* Reboot the module to boot the newly deployed system.

[[Category:Linux]]
[[Category:Yocto]]
[[Category:UCM-iMX93]]

File:Ucm-imx93 system-on-module.png

2023-06-19T12:35:29Z

Benjamin: Benjamin uploaded a new version of File:Ucm-imx93 system-on-module.png

UCM-iMX93: Yocto Linux: Building UCM-iMX93 Yocto images

2023-06-19T11:58:48Z

= Overview =
The Yocto Project is an open-source collaboration focused on embedded Linux development. 
The purpose of this article is to show how to build a Yocto image for the UCM-iMX93 System-on-Module.

= Host System Requirements =
To ensure optimal Yocto build speed and performance, it is recommended to use a host system with at least 4 CPU cores, 16GB RAM, and 500GB of free disk space. 
In addition, the system should have the option to open a large number of files simultaneously, preferably up to 4096 or higher. 

[https://www.yoctoproject.org/docs/ Learn more about Yocto]

= Docker Host for Yocto Build Environment =
There are often compatibility issues between different Linux distributions and the dependencies required for Yocto compilation. 
In order to avoid such issues and simplify the host machine configuration process, Compulab recommends using a pre-configured Docker environment. 
Please follow the instructions below

[https://github.com/compulab-yokneam/yocker Setting up Yocto Build Docker Environment].

= Building Yocto Images =

Set up the Yocto build environment and build the image:

[https://github.com/compulab-yokneam/meta-bsp-imx9/blob/kirkstone-2.2.0/README.md Building UCM-iMX93 Yocto Linux images].

 

[[Category:Linux]]
[[Category:Yocto]]
[[Category:UCM-iMX93]]

UCM-iMX93: Yocto Linux: Known Issues

2023-06-19T11:54:10Z

Benjamin: Created page with "{{IssueCategory|Suspend/Resume| '''Description:''' :* SDIO bus driver prevents the system from going into suspend ''' Status:''' :* To be fixed in future software releases '''..."

{{IssueCategory|Suspend/Resume|
'''Description:'''
:* SDIO bus driver prevents the system from going into suspend
''' Status:'''
:* To be fixed in future software releases
'''Workaround:'''
:* Remove SDIO WiFi and BT driver manually before suspending
}}

{{IssueCategory|LCD backlight on SB-UCMIMX93|
'''Description:'''
:* Backlight brightness intensity cannot be controlled
''' Status:'''
:* To be fixed in future software releases
'''Workaround:'''
:* None
}}

UCM-iMX93: Yocto Linux: Package contents

2023-06-19T11:52:23Z

Benjamin: Created page with "== Package contents == __NOTOC__ <pre> ucm-imx93_yocto-linux ├── bootloader │ └── imx-boot-tagged ├── development │ └── README.html ├─..."

== Package contents ==

__NOTOC__
<pre>
ucm-imx93_yocto-linux
├── bootloader
│ └── imx-boot-tagged
├── development
│ └── README.html
├── images
│ ├── imx-image-full-ucm-imx93.rootfs.wic.zst
│ └── imx-image-full-ucm-imx93.manifest
├── kernel
│ ├── dtb
│ │ ├── ucm-imx93.dtb
│ │ ├── ucm-imx93-headless.dtb
│ │ └── ucm-imx93-lvds.dtb
│ ├── Image-ucm-imx93
│ └── modules-ucm-imx93.tgz
└── version.txt
</pre>
=== development ===
Development documentation

=== bootloader ===
* {{filename|imx-boot-tagged}} - NXP imx-boot bootloader; created as a part of the Yocto image; provided as and example (optional).

=== images ===
* {{filename|imx-image-full-ucm-imx93.rootfs.wic.zst}} - SD card image that provides the full system to boot with U-Boot, Linux kernel, and Yocto file-system
* {{filename|imx-image-full-ucm-imx93.manifest}} - rootfs image manifest

=== kernel ===
* {{filename|Image-ucm-imx93}} - ready to run Linux kernel for UCM-iMX93
* {{filename|modules-ucm-imx93.tgz}} - a modules archive, that matches the Linux kernel
* {{filename|dtb}} - Device tree blobs folder
** {{filename|ucm-imx93.dtb}} - default device tree blob for UCM-iMX93 evaluation board kit
** {{filename|ucm-imx93-lvds.dtb}} - device tree blob for UCM-iMX93 evaluation board kit with LVDS display support
** {{filename|ucm-imx93-headless.dtb}} - device tree blob for UCM-iMX93 evaluation board kit without display support

[[Category:Linux]]
[[Category:Yocto]]
[[Category:UCM-iMX93]]

UCM-iMX93: Yocto Linux: How-To Guide

2023-06-19T11:50:35Z

Benjamin: Created page with "=Device Tree= == Available Device Tree Files == The current release includes the following '''dtb''' files: {| class="wikitable" style="text-align:left;" |- | align="center" |..."

=Device Tree=
== Available Device Tree Files ==
The current release includes the following '''dtb''' files:
{| class="wikitable" style="text-align:left;"
|-
| align="center" | '''DTB'''
| align="center" | '''Hardware Configuration and Features'''
| align="center" | '''Jumpers/Connectors Settings'''
|-
| align="" |ucm-imx93.dtb
| align="" |default hardware configuration + mipi dsi display
| align="" |P11/P12 mipi iface/touch is in use
|-
| align="" |ucm-imx93-lvds.dtb
| align="" |default hardware configuration + lvds display
| align="" |P7/P8 lvds iface/touch is in use
|-
| align="" |ucm-imx93-headless.dtb
| align="" |default hardware configuration w/out any display
| align="" |
|-
|}

==Set device tree==
The current release provides two methods to switch between dtb files:
* U-Boot environment
The U-boot '''fdtfile''' variable contains the device tree name that will be loaded into the RAM.
This variable can be changed by:
{| class="wikitable" style="text-align:left;"
|-
| align="" | '''Environment'''
| align="" | '''Command'''
|-
| align="" |U-Boot
| align="" |setenv fdtfile <fdt_file_name>; saveenv;
|-
| align="" |Linux
| align="" |fw_setenv fdtfile <fdt_file_name>
|-
|}
* GRUB environment (if the image was created with the meta-compulab-uefi layer)
{| class="wikitable" style="text-align:left;"
|-
| align="" | '''Environment'''
| align="" | '''Command/Procedure'''
|-
| align="" |GRUB Boot Menu
| align="" |Goto "Advanced Boot Options" and choose a device tree from the provided dtb list.
|-
| align="" |Linux
| align="" |grub-editenv /boot/grub/grubenv set fdtfile=<fdt_file_name>
|-
|}

= USB =
UCM-IMX93 features two USB2.0 ports that are derived from the i.MX93 USB sub-system. 
On SB-UCMIMX93 evaluation carrier-board USB ports are available on the following connectors:

{| class="wikitable" style="text-align:left;"
|-
| align="center" | '''USB port#'''
| align="center" | '''HW setting'''
| align="center" | '''Connector'''
| align="center" | '''Mode'''
|-
| align="center" |1
| align="" |'''P21''' is not used
| align="" |type-A '''J5'''
| align="center" |host
|-
| align="center" |1
| align="" |'''P21''' connected to USB host
| align="" |micro-USB '''P21'''
| align="center" |device
|-
| align="center" |2
| align="" |jumper '''E11''' is open
| align="" |type-A '''J6'''
| align="center" |host
|-
| align="center" |2
| align="" |jumper '''E11''' is closed
| align="" |mini-PCIe '''P18'''
| align="center" |host
|}

== USB #1 in device mode ==
USB #1 port can be operated in device mode when connected to a host machine using connector '''P21'''.
Available gadgets for the UBS #1 in device mode:
{| class="wikitable" style="text-align:left;"
|-
|align=""|'''USB gadget'''
|align=""|'''SOM command'''
|-
|align=""|usb serial device
|align=""|modprobe g_serial
|-
|align=""|usb network device
|align=""|modprobe g_ether
|-
| align="" |usb mass storage device
| align="" |modprobe g_mass_storage file=/dev/sdX
|-
|}

=Controller–area network (CAN)=
UCM-iMX93 features two Flexible Controller Area Network (FLEXCAN) modules.
SB-UCMIMX93 evaluation carrier-board exposes one CAN bus interface on connector '''J21'''.

==CAN interface configuration==
It is recommended configure the CAN interface, with the {{filename|iproute2}} utilities.

* To make sure the right '''ip''' utility is used, run:
<pre>
ip -V
ip utility, iproute2-v5.7.0-77-gb687d1067169
</pre>
* Configure both CAN interface bit-rate to 1 Mbit/sec:
<pre>
ip link set can0 type can bitrate 1000000
</pre>
* Enable the CAN interface:
<pre>
ip link set can0 up
</pre>

==Send/Receive packets==
Use {{filename|cansend}} and {{filename|candump}} utilities to send and receive packets via CAN interface.

* Send standard CAN frame (on the first device):
<pre>
cansend can0 111#1122334455667788
</pre>

* Send extended CAN frame (on the first device):
<pre>
cansend can0 11111111#1122334455667788
</pre>

* CAN frames (extended mode) generator, random payload, interval between two successive flames 50 msec:
<pre>
cangen -g 50 -e -D r -v can0

can: raw protocol (rev 20170425)
...
can0 03FF0983#D7.61.FF.03.C1.F7.C1.34
can0 19C34D32#F7.5A.C2.73.AD.0E.3F.0B
can0 0675E391#2B.2D.D3.49
can0 13091C55#99.32.EC.77.27.81.49.0B
can0 098D67CF#22.50.AB.48.AD.7F.F4.26
can0 05263FEC#1B.4C.02.45.6E
can0 12B30E20#
can0 1F193DF9#C5
can0 1EB0B18F#3E.3F.DA.57.C2.FE.73.58
can0 1E5C64D9#6F.0D.B3.63.6A
can0 1E1DE3F9#96.48.AC.79.4E.00.27.71
can0 0E1A11B7#75.81.70.7C.86.79.A7.77
can0 05F8FD8B#33.F9.9B.1E.77.3D.1F
can0 1E155FCD#E6.BA.F8.58.ED.6D.C8.10
can0 1D91DF9E#5D.29.82.7B.97.1D.AB.5C
can0 11FB3CDA#14.65.C3
can0 091352C0#2C.ED
...
</pre>

* Dump all received data frames as well as error frames (on the second device):
<pre>
candump any,0:0,#FFFFFFFF

can0 111 [8] 11 22 33 44 55 66 77 88
can0 11111111 [8] 11 22 33 44 55 66 77 88
...
can0 03FF0983 [8] D7 61 FF 03 C1 F7 C1 34
can0 19C34D32 [8] F7 5A C2 73 AD 0E 3F 0B
can0 0675E391 [4] 2B 2D D3 49
can0 13091C55 [8] 99 32 EC 77 27 81 49 0B
can0 098D67CF [8] 22 50 AB 48 AD 7F F4 26
can0 05263FEC [5] 1B 4C 02 45 6E
can0 12B30E20 [0]
can0 1F193DF9 [1] C5
can0 1EB0B18F [8] 3E 3F DA 57 C2 FE 73 58
can0 1E5C64D9 [5] 6F 0D B3 63 6A
can0 1E1DE3F9 [8] 96 48 AC 79 4E 00 27 71
can0 0E1A11B7 [8] 75 81 70 7C 86 79 A7 77
can0 05F8FD8B [7] 33 F9 9B 1E 77 3D 1F
can0 1E155FCD [8] E6 BA F8 58 ED 6D C8 10
can0 1D91DF9E [8] 5D 29 82 7B 97 1D AB 5C
can0 11FB3CDA [3] 14 65 C3
can0 091352C0 [2] 2C ED
...
</pre>

= WiFi =
UCM-iMX93 features 802.11ac wireless connectivity solution implemented with an NXP 88W8997 module. 
The [https://manpages.debian.org/stretch/network-manager/nmcli.1.en.html NetworkManager] can be used to manage WiFi interface.
{{Note|Before working with WiFi, please ensure that WiFi antenna is connected to the SOM.}}

== Enable/Disable WiFi Interface ==
* To enable WiFi interface:
:<pre>nmcli radio wifi on</pre>
* To disable WiFi interface:
:<pre>nmcli radio wifi off</pre>

== Network Scanning ==
* Sample WiFi scanning:
:<pre>nmcli dev wifi list</pre>
:The output will show the list of Access Points and Ad-Hoc cells in range.

== Connecting to Access Point ==
In the following example:
* Replace <SSID> and <PASSWORD> with the actual access point parameters:
:<pre>nmcli device wifi connect <SSID> password <PASSWORD> name WifiCon</pre>
* Disconnect wireless network:
:<pre>nmcli connection down WifiCon</pre>
* Connect wireless network again:
:<pre>nmcli connection up WifiCon</pre>

== Creating Access Point ==
In the following example:
* Replace <SSID> and <PASSWORD> with desired access point parameters:
:<pre>nmcli device wifi hotspot ssid <SSID> password <PASSWORD> con-name HotspotCon</pre>
* Disable wireless AP:
:<pre>nmcli connection down HotspotCon</pre>
* Enable wireless AP again:
:<pre>nmcli connection up HotspotCon</pre>

= Bluetooth =
UCM-iMX93 features bluetooth connectivity solution implemented with an NXP 88W8997 module. 

{{Note|Before working with Bluetooth, please ensure that Bluetooth antenna is connected to the SOM.}}

To start '''bluetoothctl''' use the following command:
<pre>
bluetoothctl
</pre>

To start the scan process use the following commands:
<pre>
[bluetooth]# default-agent
[bluetooth]# power on
[bluetooth]# scan on
</pre>

Bluetooth device should be turned on and visible. Its MAC-adress and name should appear in '''bluetoothctl''' in following format:
<pre>
[CHG] Device AA:BB:CC:DD:EE:FF Name: Device_Name
</pre>

To pair with the Bluetooth device use the following command:
<pre>
pair AA:BB:CC:DD:EE:FF
</pre>

Where '''AA:BB:CC:DD:EE:FF''' is MAC-adress of the Bluetooth device.

To quit '''bluetoothctl''' use the following command:
<pre>
[Device_Name]# quit
</pre>



=Suspend / Resume=
{{note|The operation below requires '''root''' access.}}

UCM-iMX93 features suspend mode, which allows to minimize power consumption.

The following command should be used to enter suspend mode:
<pre>
echo mem >/sys/power/state
</pre>

To resume normal operation press shortly the '''Power On''' button '''SW5'''.

=CPU temperature=
i.MX93 SoC features an internal temperature sensor which allows to measure the SoC temperature.
Execute the following command to read the current CPU temperature:
<pre>
cat /sys/class/thermal/thermal_zone0/temp
</pre>

= RTC =
UCM-iMX93 features two RTC devices:
* i.MX93 internal RTC ('''rtc0''') - can be used as wake-up source
* AB1805 external RTC ('''rtc1''') - can be used for low current battery powered time keeping

== Internal RTC - rtc0 ==
* System information
<pre>
udevadm info -p /sys/class/rtc/rtc0

P: /devices/platform/soc@0/44000000.bus/44440000.bbnsm/44440000.bbnsm:rtc/rtc/rtc0
N: rtc0
L: -100
S: rtc
E: DEVPATH=/devices/platform/soc@0/44000000.bus/44440000.bbnsm/44440000.bbnsm:rtc/rtc/rtc0
E: DEVNAME=/dev/rtc0
E: MAJOR=251
E: MINOR=0
E: SUBSYSTEM=rtc
E: USEC_INITIALIZED=14959708
E: DEVLINKS=/dev/rtc
</pre>

* Wake up:
rtc0 can be used as a wake up source, as a result an '''rtcwakeup''' can be used with this device:
<pre>
rtcwake --device /dev/rtc0 -s 5 -m mem
</pre>

== External RTC - rtc1 ==
* System information
<pre>
udevadm info -p /sys/class/rtc/rtc1

N: rtc1
L: 0
E: DEVPATH=/devices/platform/soc@0/44000000.bus/44340000.i2c/i2c-0/0-0069/rtc/rtc1
E: DEVNAME=/dev/rtc1
E: MAJOR=251
E: MINOR=1
E: SUBSYSTEM=rtc
</pre>

* Set the date and write it into the RTC:
<pre>
date -s "16 Jun 2023 12:00:00"

Fri 16 Jun 2023 12:00:00
hwclock --systohc --rtc /dev/rtc1
</pre>

* Read the RTC time and date:
<pre>
hwclock --show --rtc /dev/rtc1

2023-06-16 12:01:37.935876+00:00
</pre>

=See Also=
*[[UCM-iMX93: Evaluation Kit: Getting Started | UCM-iMX93:Evaluation Kit: Getting Started]] 

[[Category:Yocto]]
[[Category:UCM-iMX93]]

UCM-iMX93: Yocto Linux: Installing Yocto images onto UCM-iMX93 eMMC

2023-06-19T11:49:36Z

Benjamin: Created page with "Please use the `CompuLab Deployment Tool` to install UCM-iMX93 Yocto Linux onto on-board eMMC storage. The `CompuLab Deployment Tool` is a shell script that allows to deploy..."

Please use the `CompuLab Deployment Tool` to install UCM-iMX93 Yocto Linux onto on-board eMMC storage.

The `CompuLab Deployment Tool` is a shell script that allows to deploy a working OS image from micro-SD card to UCM-iMX93 on-board storage (eMMC).

Follow the step-by-step procedure for a selected image:

==Installing Yocto images onto UCM-iMX93 eMMC==
* Prepare a bootable SD card and use it to boot the system [[UCM-iMX93:_Yocto_Linux:_Manual_Installation:_SD_card|as described here]].
* [[UCM-iMX93:_Yocto_Linux:_Manual_Installation:_SD_card#Run%20Yocto%20Linux%20image|Run the Yocto Linux image]] that you intend to deploy.
* In the terminal window issue: <pre>cl-deploy</pre>
* Follow the steps below:

{| width="60%" cellspacing="1" cellpadding="1" border="1"
|-
| align="center" | '''Action'''
| align="center" | '''Screenshot'''
|-
|
:Select installation target storage: on UCM-iMX93 on-board eMMC device is called '''mmcblk2'''
| align="center" | [[File:wayland_cl-deploy_dst_choice.png|400px]]
|-
|
:Be aware of the fact that all the data on the target storage will be erased
| align="center" | [[File:wayland_cl-deploy_last_warning.png|400px]]
|-
|
:While installation process is running the output screen shows the log and progress
| align="center" | [[File:wayland_cl-deploy_process.png|400px]]
|-
|
:When installation is complete, the following message will show up
| align="center" | [[File:wayland_cl-deploy_finish.png|400px]]
|}

==Post installation==
* Reboot the module to boot the newly deployed system.

[[Category:Linux]]
[[Category:Yocto]]
[[Category:UCM-iMX93]]

UCM-iMX93: Yocto Linux: Manual Installation: SD card

2023-06-19T11:48:47Z

Benjamin: Created page with "== Introduction == This article provides instructions needed to install the Yocto Linux SD-card image on SD card using a Linux Host workstation. The image provides full boot..."

== Introduction ==
This article provides instructions needed to install the Yocto Linux SD-card image on SD card using a Linux Host workstation.
The image provides full boot system including U-Boot, Linux kernel, device driver modules and example root filesystem.

== Preparation steps ==
* Obtain a Linux PC workstation.
* Obtain a USB Card reader and an micro-SD Card. Any commercially available micro-SD card of 4GB (or larger) may be used for the installation.
* Download the UCM-iMX93 Yocto Linux package from [https://www.compulab.com/products/computer-on-modules/ucm-imx93-nxp-i-mx9-som-system-on-module-computer/#devres CompuLab website].
* Unzip the package to a directory on the host workstation. From now we assume the device name is {{filename|pakage_dir}}.
* The Yocto Linux SD-card image file, mentioned below, can be found in the {{filename|images}} subdirectory.
* Plug the USB SD Card reader into the host PC. Insert the micro-SD Card into the USB Card reader. From now we assume the device name of the MMC/SD card on your Linux PC is {{filename|/dev/sdX}}.

== Installation ==
* Flash the image file to the micro-SD card:
<pre>zstd -dc imx-image-full-ucm-imx93.wic.zst | sudo dd of=/dev/sdX bs=1M
</pre>

== Run Yocto Linux image ==
* Insert the micro-SD card into SD socket '''P15''' [[:File:UCM-iMX93-eval-kit-quick-setup.png|(see drawing)]]
* Connect a standard USB cable (included in the kit) between your host PC and the evaluation kit micro-USB2.0 connector '''P16''' [[:File:UCM-iMX93-eval-kit-quick-setup.png|(see drawing)]]
*: Use a terminal emulator as described [[UCM-iMX93:_Evaluation_Kit:_Getting_Started#System setup|here]]
* Press and hold the ALT_BOOT button ('''SW3''') and then reset / power-on the system to force boot from SD card [[:File:UCM-iMX93-eval-kit-quick-setup.png|(see drawing)]]. Release ALT_BOOT button after 2-3 seconds
* The system boots into Linux

[[Category:Linux]]
[[Category:Yocto]]
[[Category:UCM-iMX93]]

UCM-iMX93 NXP iMX93 Linux Resources

2023-06-19T11:47:26Z

Benjamin: Created page with "{{summary| This page contains links to information about Yocto Linux distribution for the CompuLab UCM-iMX93 ultra-compact System-on-Module / Computer-on-Module...."

{{summary|
This page contains links to information about Yocto Linux distribution for the CompuLab UCM-iMX93 ultra-compact System-on-Module / Computer-on-Module.
The Yocto Project is an open-source collaboration focused on embedded Linux development.

|Ucm-imx93 system-on-module.png|thumb}}
{{Resources Linux with app notes
|* [[UCM-iMX93: Evaluation Kit: Getting Started|Getting started with UCM-iMX93 Evaluation Kit]]
* [[UCM-iMX93: Evaluation Kit: Hardware Guide|Evaluation Kit hardware guide]]
* [[UCM-iMX93: Yocto Linux: Manual Installation: SD card|Installing Yocto on SD card]]
* [[UCM-iMX93: Yocto Linux: Installing Yocto images onto UCM-iMX93 eMMC| Installing Yocto onto UCM-iMX93 eMMC]]
* [[UCM-iMX93: Yocto Linux: How-To Guide|UCM-iMX93 Linux how-to guide]]
* [[UCM-iMX93: Yocto Linux: Package contents|Yocto Linux package contents]]
* [[UCM-iMX93: Yocto Linux: Known Issues|Known Issues]]
|* [[UCM-iMX93: Yocto Linux: Building UCM-iMX93 Yocto images|Building UCM-iMX93 Yocto Linux images]]
*[https://github.com/compulab-yokneam/meta-bsp-imx9/blob/kirkstone-2.2.0/Documentation/linux_kernel_build.md Building UCM-iMX93 Linux Kernel]
*[https://github.com/compulab-yokneam/meta-bsp-imx9/blob/kirkstone-2.2.0/Documentation/imx_boot_image_build.md Building UCM-iMX93 boot firmware]
*[[Application Notes: Introduction to Yocto development|Introduction to Yocto development]]
*[[Application Notes: Making Changes to Yocto Meta-Layers|Making Changes to Yocto Meta-Layers]]

|*[[Application Notes: Developing with Qt on CompuLab platforms|Developing with Qt on CompuLab platforms]]
*[[Application Notes: eMMC lifetime optimization|Optimizing eMMC lifetime and reliability]]
*[https://github.com/compulab-yokneam/meta-mender-compulab/blob/kirkstone-nxp/README.md Creating OTA update enabled images with Mender]

}}

__NOTOC__

{{ChangelogReleaseNotesRss| content=
===== 19-June-2023, UCM-iMX93 Yocto Linux release 1.0 =====
: Release of Yocto 4.2 (Kirkstone) for UCM-iMX93
: - Based on NXP release lf-5.15
: - Kernel 6.1.1
: - U-Boot 2022.04
: Supported HW features:
: - Basic support for UCM-iMX93
: - USB2.0 OTG Host/Device
: - Storage: eMMC, uSD, EEPROM
: - Ethernet (ENET_QOS)
: - WiFi (NXP 88W8997)
: - Bluetooth (NXP 88W8997)
: - CAN bus
: - LVDS display interface
: - MIPI-DSI display interface
: - Touch screen support
: - I2C, SPI
: - BBNSM RTC
: - RTC
: SW Features:
: - CompuLab Deployment Tool
: - CompuLab U-Boot Tool
: - fw_printenv/fw_setenv utilities
: - Chromium browser
: - Qt support
: Boot-loader features:
: - Supported boot-loader devices: SD, eMMC
: - Supported linux/rootfs devices: SD, eMMC, USB, NFS
: Documentation:
: - Initial Yocto Linux documentation for UCM-iMX93
}}

[[Category:Linux]]
[[Category:Yocto]]
[[Category:UCM-iMX93]]

UCM-iMX93 NXP iMX93 SW Resources

2023-06-19T11:46:01Z

Benjamin:

{{summary|
UCM-iMX93 is an ultracompact computer-on-module (CoM) / system-on-module (SoM) board, designed for integration into embedded applications.

UCM-iMX93 is based on the NXP i.MX93 application processor featuring a highly scalable dual core Cortex-A55 CPU running at up to 1.7GHz coupled with an integrated AI/ML neural processing unit.

UCM-iMX93 is provided with comprehensive documentation and full ready-to-run SW support for Linux operating system. 
|Ucm-imx93 system-on-module.png|thumb}}

<div style="background: white; border: 1px solid black; padding: 1em;">
{| border="0" cellpadding="2" width="100%" align="center"
|-
! style="font-size: 125%; background-color: #eeeeee;" align="center" width="25%" | [[UCM-iMX93 NXP iMX93 Yocto Linux|Yocto Linux]]
|-

| align="center" | [[Image:Yocto-Logo1.png|200px|link=UCM-iMX93 NXP iMX93 Yocto Linux]]
|}
</div>

__NOTOC__

{{note|1=From time to time CompuLab releases new software versions for UCM-iMX93 in order to fix bugs, address component changes and add functionality. It is highly recommended to subscribe to the [[Image:Feed-icon.png|16px]] [{{fullurl:{{FULLPAGENAME}}|action=feed}} '''UCM-iMX93 RSS Feed'''] in order to receive automatic notifications about software updates.}}

{{ChangelogReleaseNotesRss| content=
===== 19-June-2023, UCM-iMX93 Yocto Linux release 1.0 =====
: Release of Yocto 4.2 (Kirkstone) for UCM-iMX93
: - Based on NXP release lf-5.15
: - Kernel 6.1.1
: - U-Boot 2022.04
: Supported HW features:
: - Basic support for UCM-iMX93
: - USB2.0 OTG Host/Device
: - Storage: eMMC, uSD, EEPROM
: - Ethernet (ENET_QOS)
: - WiFi (NXP 88W8997)
: - Bluetooth (NXP 88W8997)
: - CAN bus
: - LVDS display interface
: - MIPI-DSI display interface
: - Touch screen support
: - I2C, SPI
: - BBNSM RTC
: - RTC
: SW Features:
: - CompuLab Deployment Tool
: - CompuLab U-Boot Tool
: - fw_printenv/fw_setenv utilities
: - Chromium browser
: - Qt support
: Boot-loader features:
: - Supported boot-loader devices: SD, eMMC
: - Supported linux/rootfs devices: SD, eMMC, USB, NFS
: Documentation:
: - Initial Yocto Linux documentation for UCM-iMX93
}}

[[Category:UCM-iMX93]]

File:Ucm-imx93 system-on-module.png

2023-06-19T11:44:09Z

Benjamin:

Main Page

2023-06-19T11:43:53Z

Benjamin:

__NOTOC__

== CompuLab System-on-Modules ==

{| width="100%" align="center" cellspacing="3" cellpadding="10"
|- style="line-height: 120%; border-bottom: 1px solid #aaaaaa; font-size: 120%; background-color: #34467F;"
| align="center" | [[UCM-iMX93 NXP iMX93 SW Resources|UCM-iMX93]]
| align="center" | [[CL-SOM-iMX8Plus NXP iMX8M-Plus SW Resources|CL-SOM-iMX8Plus]]
| align="center" | [[UCM-iMX8M-Plus NXP iMX8M-Plus SW Resources|UCM-iMX8M-Plus]]
|- style="font-size: 110%; background-color: #eeeeee;"

| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 50%;" |
* NXP i.MX93, 1.7GHz
* 2x Cortex-A55
* Linux
| align="center" | [[Image:Ucm-imx93 system-on-module.png|150px|link=UCM-iMX93 NXP iMX93 SW Resources]]
|}

| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 50%;" |
* NXP i.MX8M Plus, 1.8GHz
* 4x Cortex-A53
* Linux
| align="center" | [[Image:CL-SOM-iMX8Plus System-on-Module.jpg|150px|link=CL-SOM-iMX8Plus NXP iMX8M-Plus SW Resources]]
|}
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 50%;" |
* NXP i.MX8M Plus, 1.8GHz
* 4x Cortex-A53
* Linux
| align="center" | [[Image:UCM-iMX8M-Plus System-on-Module.png|150px|link=UCM-iMX8M-Plus NXP iMX8M-Plus SW Resources]]
|}

|- style="line-height: 120%; border-bottom: 1px solid #aaaaaa; font-size: 120%; background-color: #34467F;"
| align="center" | [[MCM-iMX8M-Mini NXP iMX8M-Mini SW Resources|MCM-iMX8M-Mini]]
| align="center" | [[UCM-iMX8M-Mini NXP iMX8M-Mini SW Resources|UCM-iMX8M-Mini]]
| align="center" | [[CL-SOM-iMX8 NXP i.MX8M SW Resources|CL-SOM-iMX8]]
|- style="font-size: 110%; background-color: #eeeeee;"

| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 50%;" |
* NXP i.MX8M-Mini 1.8GHz
* Quad-core ARM Cortex-A53
* Linux, Android
| align="center" | [[Image:MCM-iMX8M-Mini SMD system-on-module.png|150px|link=MCM-iMX8M-Mini NXP iMX8M-Mini SW Resources]]
|}

| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 50%;" |
* NXP i.MX8M-Mini 1.8GHz
* Quad-core ARM Cortex-A53
* Linux, Android
| align="center" | [[Image:UCM-iMX8M-Mini System-on-Module.png|150px|link=UCM-iMX8M-Mini NXP iMX8M-Mini SW Resources]]
|}
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 50%;" |
* NXP i.MX8M 1.5GHz
* Quad-core ARM Cortex-A53
* Linux, Android
| align="center" | [[Image:Cl-som-imx8_system-on-module.jpg|150px|link=CL-SOM-iMX8 NXP i.MX8M SW Resources]]
|}

|- style="line-height: 120%; border-bottom: 1px solid #aaaaaa; font-size: 120%; background-color: #34467F;"
| align="center" | [[CL-SOM-iMX8X NXP iMX 8X SW Resources|CL-SOM-iMX8X]]
| align="center" | [[CL-SOM-iMX7 Freescale i.MX7 SW Resources| CL-SOM-iMX7]]
|- style="font-size: 110%; background-color: #eeeeee;"

| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 50%;" |
* NXP i.MX 8X, 1.2GHz
* Quad-core ARM Cortex-A35
* Linux
| align="center" | [[Image:cl-som-imx8x_system-on-module.jpg|150px|link=CL-SOM-iMX8X NXP iMX 8X SW Resources]]
|}
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 50%;" |
* NXP i.MX7 1GHz
* Dual-core ARM Cortex-A7
* Linux
| align="center" | [[Image:Cl-som-imx7-top.jpg|150px|link=CL-SOM-iMX7 Freescale i.MX7 SW Resources]]
|}
|}
 

== CompuLab IoT Gateways ==

{| width="100%" align="center" cellspacing="3" cellpadding="10"
|- style="line-height: 120%; border-bottom: 1px solid #aaaaaa; font-size: 120%; background-color: #34467F;"
| align="center" | [[IOT-GATE-IMX8PLUS and SBC-IOT-IMX8PLUS SW Resources|IOT-GATE-IMX8PLUS]]
| align="center" | [[IOT-GATE-RPI4 SW Resources|IOT-GATE-RPI4]]
| align="center" | [[IOT-GATE-iMX8 and SBC-IOT-iMX8 NXP iMX8M-Mini SW Resources|IOT-GATE-iMX8]]
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 50%;" |
* NXP i.MX8M-Plus 1.8GHz
* Quad-core ARM Cortex-A53
* Linux
| align="center" | [[Image:Iot-gate-imx8plus.png|150px|link=IOT-GATE-IMX8PLUS and SBC-IOT-IMX8PLUS SW Resources]]
|}
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 50%;" |
* Broadcom BCM2711 1.5GHz
* Quad-core ARM Cortex-A72
* Linux
| align="center" | [[Image:Iot-gate-rpi4.png|150px|link=IOT-GATE-RPI4 SW Resources]]
|}
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 50%;" |
* NXP i.MX8M-Mini 1.8GHz
* Quad-core ARM Cortex-A53
* Linux
| align="center" | [[Image:iot-gate-imx8.png|150px|link=IOT-GATE-iMX8 and SBC-IOT-iMX8 NXP iMX8M-Mini SW Resources]]
|}

|- style="line-height: 120%; border-bottom: 1px solid #aaaaaa; font-size: 120%; background-color: #34467F;"
| align="center" | [[IOT-GATE-iMX7 and SBC-IOT-iMX7 NXP i.MX7 SW Resources|IOT-GATE-iMX7]]
| align="center" | [[IOT-GATE-RPi SW Resources|IOT-GATE-RPi]]
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 50%;" |
* NXP i.MX7 1GHz
* Dual-core ARM Cortex-A7
* Linux
| align="center" | [[Image:Iot-gate-imx7.png|150px|link=IOT-GATE-iMX7 and SBC-IOT-iMX7 NXP i.MX7 SW Resources]]
|}
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 50%;" |
* Broadcom BCM2837 1.2GHz
* Quad-core ARM Cortex-A53
* Linux
| align="center" | [[Image:Iot-gate-rpi.png|150px|link=IOT-GATE-RPi SW Resources]]
|}
|}
 

== CompuLab Single Board Computers ==

{| width="100%" align="center" cellspacing="3" cellpadding="10"
|- style="line-height: 120%; border-bottom: 1px solid #aaaaaa; font-size: 120%; background-color: #34467F;"
| align="center" | [[IOT-GATE-IMX8PLUS and SBC-IOT-IMX8PLUS SW Resources|SBC-IOT-IMX8PLUS]]
| align="center" | [[IOT-GATE-iMX8 and SBC-IOT-iMX8 NXP iMX8M-Mini SW Resources|SBC-IOT-iMX8]]
| align="center" | [[IOT-GATE-iMX7 and SBC-IOT-iMX7 NXP i.MX7 SW Resources|SBC-IOT-iMX7]]
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 50%;" |
* NXP i.MX8M-Plus 1.8GHz
* Quad-core ARM Cortex-A53
* Linux
| align="center" | [[Image:Sbc-iot-imx8plus.png|150px|link=IOT-GATE-IMX8PLUS and SBC-IOT-IMX8PLUS SW Resources]]
|}

| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 50%;" |
* NXP i.MX8M-Mini 1.8GHz
* Quad-core ARM Cortex-A53
* Linux
| align="center" | [[Image:Sbc-iot-imx8 single-board-computer.png|150px|link=IOT-GATE-iMX8 and SBC-IOT-iMX8 NXP iMX8M-Mini SW Resources]]
|}
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 50%;" |
* NXP i.MX7 1GHz
* Dual-core ARM Cortex-A7
* Linux
| align="center" | [[Image:Sbc-iot-imx7 single board computer.png|150px|link=IOT-GATE-iMX7 and SBC-IOT-iMX7 NXP i.MX7 SW Resources]]
|}
|}
 

== CompuLab COM Express Modules ==

{| width="100%" align="center" cellspacing="3" cellpadding="10"
|- style="line-height: 120%; border-bottom: 1px solid #aaaaaa; font-size: 120%; background-color: #34467F;"
| align="center" | [[COMEX-IC60U Intel Kaby Lake COM Express SW Resources|COMEX-IC60U]]
| align="center" | [[COMEX-IE38M Intel BayTrail COM Express SW Resources|COMEX-IE38M]]
| align="center" | [[COMEX-IE38 Intel BayTrail COM Express SW Resources|COMEX-IE38]]
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 50%;" |
* Intel 7th Gen. Core i7/i5/i3, up-to 2.8GHz
* COM Express Compact Type 6
* Windows, Linux
| align="center" | [[Image:Comex-ic60u-top.jpg|150px|link=COMEX-IC60U Intel Kaby Lake COM Express SW Resources]]
|}
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 50%;" |
* Intel Atom E3800, 2GHz
* COM Express Mini Type 10
* Windows, Linux
| align="center" | [[Image:Comex-ie38m-top.jpg|150px|link=COMEX-IE38M Intel BayTrail COM Express SW Resources]]
|}
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 50%;" |
* Intel Atom E3800, 2GHz
* COM Express Mini Type 10
* Windows, Linux
| align="center" | [[Image:Comex-ie38-top.jpg|150px|link=COMEX-IE38 Intel BayTrail COM Express SW Resources]]
|}
|- style="line-height: 120%; border-bottom: 1px solid #aaaaaa; font-size: 120%; background-color: #34467F;"
| align="center" | [[COMEX-IC50L Intel Broadwell COM Express SW Resources|COMEX-IC50L]]
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 50%;" |
* Intel 5th Gen. Core i7/i5/i3
* COM Express Compact Type 6
* Windows, Linux
| align="center" | [[Image:Comex-ic50l-top.jpg|150px|link=COMEX-IC50L Intel Broadwell COM Express SW Resources]]
|}

|}
 

== CompuLab Legacy Products ==

{| width="100%" align="center" cellspacing="3" cellpadding="10"
|- style="line-height: 120%; border-bottom: 1px solid #aaaaaa; font-size: 120%; background-color: #34467F;"
| align="center" | [[CL-SOM-iMX6 NXP i.MX6 SW Resources|CL-SOM-iMX6]]
| align="center" | [[CL-SOM-iMX6UL Freescale i.MX6UL SW Resources| CL-SOM-iMX6UL]]
| align="center" | [[CL-SOM-AM57x TI AM57x SW Resources| CL-SOM-AM57x]]
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 50%;" |
* NXP i.MX6 Plus 1.2GHz
* Quad-core ARM Cortex-A9
* Linux
| align="center" | [[Image:Cl-som-imx6-top.jpg|150px|link=CL-SOM-iMX6 NXP i.MX6 SW Resources]]
|}
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 50%;" |
* NXP i.MX6 UltraLite 528MHz
* ARM Cortex-A7
* Linux
| align="center" | [[Image:Som-imx6ul-top.jpg|150px|link=CL-SOM-iMX6UL Freescale i.MX6UL SW Resources]]
|}
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 50%;" |
* TI AM57x 1.5GHz
* Dual-core ARM Cortex-A15
* Linux
| align="center" | [[Image:Cl-som-am57x-top.png|150px|link=CL-SOM-AM57x TI AM57x SW Resources]]
|}

|- style="line-height: 120%; border-bottom: 1px solid #aaaaaa; font-size: 120%; background-color: #34467F;"
| align="center" | [[CM-T43 TI AM437x SW Resources| CM-T43]]
| align="center" | [[CM-T335 SW Resources| CM-T335]]
| align="center" | [[CM-FX6 SW Resources| CM-FX6]]
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 50%;" |
* TI AM437x 1GHz
* ARM Cortex-A9
* Linux
| align="center" | [[Image:Cm-t43-top.jpg|150px|link=CM-T43 TI AM437x SW Resources]]
|}
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 50%;" |
* TI AM335x 600MHz
* ARM Cortex-A8
* Linux, Android, WinCE
| align="center" | [[Image:cm-t335-top.jpg|150px|link=CM-T335 TI AM335x SW Resources]]
|}
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 50%;" |
* NXP i.MX6 1.2GHz
* Quad-core ARM Cortex-A9
* Linux, Android, WinCE
| align="center" | [[Image:Cm-fx6-top.jpg|150px|link=CM-FX6 Freescale i.MX6 SW Resources]]
|}

|- style="line-height: 120%; border-bottom: 1px solid #aaaaaa; font-size: 120%; background-color: #34467F;"
| align="center" | [[CM-T3730 SW Resources| CM-T3730]]
| align="center" | [[CM-T3517 SW Resources| CM-T3517]]
| align="center" | [[CM-T3530 SW Resources| CM-T3530]]
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 50%;" |
* TI DM3730 1GHz
* ARM Cortex-A8
* Linux, Android, WinCE
| align="center" | [[Image:T3730-cm-top-m.jpg|150px|link=CM-T3730 SW Resources]]
|}
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 50%;" |
* TI AM3517 600MHz
* ARM Cortex-A8
* Linux, WinCE
| align="center" | [[Image:cm-t3517.jpg|150px|link=CM-T3517 SW Resources]]
|}
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 50%;" |
* TI OMAP3530 720MHz
* ARM Cortex-A8
* Linux, WinCE
| align="center" | [[Image:T35_CM_top.JPG|150px|link=CM-T3530 SW Resources]]
|}
|- style="line-height: 120%; border-bottom: 1px solid #aaaaaa; font-size: 120%; background-color: #34467F;"
| align="center" | [[SBC-iBT Intel BayTrail SW Resources|SBC-iBT]]
| align="center" | [[COMEX-A420 AMD G-Series COM Express SW Resources|COMEX-A420]]
| align="center" | [[COMEX-IC40D Intel Haswell COM Express SW Resources|COMEX-IC40D]]
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 50%;" |
* Intel Atom E3800, 2GHz
* Quad-core x86
* Windows, Linux
| align="center" | [[Image:Sbc-ibt single board computer.png|150px|link=SBC-iBT Intel BayTrail SW Resources]]
|}
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 50%;" |
* AMD G-Series, 1.2GHz
* COM Express Mini Type 10
* Windows, Linux
| align="center" | [[Image:Comex-a420-top.jpg|150px|link=COMEX-A420 AMD G-Series COM Express SW Resources]]
|}
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 50%;" |
* Intel 4th Gen. Core i7/i5/i3
* COM Express Basic Type 6
* Windows, Linux
| align="center" | [[Image:Comex-ic40d-top.jpg|150px|link=COMEX-IC40D Intel Haswell COM Express SW Resources]]
|}

|- style="line-height: 120%; border-bottom: 1px solid #aaaaaa; font-size: 120%; background-color: #34467F;"
| align="center" | [[CM-QS600 SW Resources| CM-QS600]]
| align="center" | [[CM-T54 SW Resources| CM-T54]]
| align="center" | [[CM-iGT SW Resources| CM-iGT]]
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 50%;" |
* Qualcomm APQ8064, 1.7GHz
* Quad-core Krait 300
* Linux, Android
| align="center" | [[Image:Cm-qs600-top.jpg|150px|link=CM-QS600 Qualcomm Snapdragon 600 APQ8064 SW Resources]]
|}
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 50%;" |
* TI OMAP5432 1.5GHz
* Dual-core ARM Cortex-A15
* Linux
| align="center" | [[Image:Cm-t54-top.jpg|150px|link=CM-T54 SW Resources]]
|}
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 50%;" |
* AMD G-Series 1.65GHz
* Dual-core x86
* Linux, Windows
| align="center" | [[Image:Cm-igt-top-m.jpg|150px|link=CM-iGT SW Resources]]
|}
|- style="line-height: 120%; border-bottom: 1px solid #aaaaaa; font-size: 120%; background-color: #34467F;"
| align="center" | [[CM-iTC SW Resources| CM-iTC]]
| align="center" | [[CM-A510 SW Resources| CM-A510]]
| align="center" | [[CM-X300 SW Resources| CM-X300]]
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 50%;" |
* Intel Atom E680 1.6GHz
* Single-core x86
* Linux, Windows
| align="center" | [[Image:itc-cm-top-m.jpg|150px|link=CM-iTC SW Resources]]
|}
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 50%;" |
* Marvell Armada 510 800MHz
* ARM Cortex-A8
* Linux
| align="center" | [[Image:A510_CM_top_hq.JPG|150px|link=CM-A510 SW Resources]]
|}
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 50%;" |
* Marvell PXA310 624MHz
* ARM XScale
* Linux, WinCE
| align="center" | [[Image:X300-cm-top-m.jpg|150px|link=CM-X300 SW Resources]]
|}
|- style="line-height: 120%; border-bottom: 1px solid #aaaaaa; font-size: 120%; background-color: #34467F;"
| align="center" | [[CM-iAM SW Resources| CM-iAM]]
| align="center" | [[EM-T3530 SW Resources| EM-T3530]]
| align="center" | [[CM-iGLX SW Resources| CM-iGLX]]
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 50%;" |
* Intel Atom Z530, 1.6GHz
* Single-core x86
* Linux, Windows
| align="center" | [[Image:Cm-iam-top.jpg|150px|link=CM-iAM_SW Resources]]
|}
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 50%;" |
* TI OMAP3530, 720MHz
* ARM Cortex-A8
* Linux, WinCE
| align="center" | [[Image:EM-T3530.png|200px|link=EM-T3530 SW Resources]]
|}
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 50%;" |
* AMD Geode LX800, 500MHz
* Single-core x86
* Linux, Windows, WinCE
| align="center" | [[Image:Iglx-cm-top-m.jpg|150px|link=CM-iGLX SW Resources]]
|}
|- style="line-height: 120%; border-bottom: 1px solid #aaaaaa; font-size: 120%; background-color: #34467F;"
| align="center" | [[EM-X270 SW Resources| EM-X270]]
| align="center" | [[CM-X270 SW Resources| CM-X270]]
| align="center" | [[SBC-FITPC2 SW Resources| SBC-FITPC2]]
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 50%;" |
* Marvell PXA270, 520MHz
* ARM XScale
* Linux, WinCE
| align="center" | [[Image:EM-X270-bottom.png|200px|link=EM-X270 SW Resources]]
|}
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 50%;" |
* Marvell PXA270, 520MHz
* ARM XScale
* Linux, WinCE
| align="center" | [[Image:X270-cm-l-top-m.jpg|150px|link=CM-X270 SW Resources]]
|}
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 50%;" |
* Intel Atom Z530
* Single-core x86
* Linux, Windows
| align="center" | [[Image:SBC-FITPC2.png|200px|link=SBC-FITPC2 SW Resources]]
|}
|}

UCM-iMX93: Evaluation Kit: Getting Started

2023-06-19T10:26:22Z

Benjamin:

[[Image:UCM-iMX93-eval-kit-quick-setup.png|frameless|top|1500px|link=]]

== Package content ==

[https://www.compulab.com/wp-content/uploads/2023/06/ucm-imx93_eval-kit-content.pdf Package content list]

== System setup ==
UCM-iMX93 evaluation kit is preloaded with the UCM-iMX93 Yocto Linux image.
# Make sure jumper '''E9''' is populated (default state).
# Make sure jumpers '''E2''' and '''E7''' are not populated (default state).
# Connect the LCD panel (included in the kit) to connectors '''P11''' and '''P12'''. Ensure that the flat cables are fully inserted.
# Connect a standard USB cable (included in the kit) between your host PC and the evaluation kit micro-USB2.0 connector '''P16'''.
# On your computer, start a terminal emulation program (such as Tera Term or PuTTy) with the following serial port settings:
<blockquote>
{{:SB-SOM: serial port parameters table}}
</blockquote>

== Starting the system ==
# Connect the DC 12V power supply adapter (included) to main DC power connector '''J4'''.
# Follow the messages in your terminal emulator program until you see the linux shell command line prompt.
{{note|In case no messages appear in your terminal emulation program, please refer to the detailed [[SB-UCM-iMX8: HOWTO: USB Console|USB console]] guide.}}

== What's Next? ==
* [https://www.compulab.com/products/computer-on-modules/ucm-imx93-nxp-i-mx9-som-system-on-module-computer/#devres UCM-iMX93 development resources]

[[Category:UCM-iMX93]]