MCM-iMX93: Yocto Linux: How-To Guide - Revision history

Igor at 16:17, 1 July 2026

2026-07-01T16:17:19Z

Igor at 10:04, 19 February 2025

2025-02-19T10:04:33Z

Igor at 09:59, 19 February 2025

2025-02-19T09:59:57Z

Igor at 13:05, 16 February 2025

2025-02-16T13:05:54Z

Igor at 13:58, 11 August 2024

2024-08-11T13:58:42Z

Igor at 09:06, 4 July 2024

2024-07-04T09:06:42Z

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

2024-06-30T11:24:28Z

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

New page

=Device Tree=
== Available Device Tree Files ==
The current release includes the following '''dtb''' files:
{| class="wikitable" style="text-align:left;"
|-
| '''DTB'''
| '''Hardware Configuration and Features'''
| '''Jumpers/Connectors Settings'''
|-
|sbc-mcm-imx93.dtb
|default hardware configuration + lvds display
| visit [[MCM-iMX93: Evaluation Kit: Hardware Guide#Connector_Locations | Connector Locations ]]
|-
|}

==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;"
|-
| '''Environment'''
| '''Command'''
|-
|U-Boot
|setenv fdtfile <fdt_file_name>; saveenv;
|-
|Linux
|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;"
|-
| '''Environment'''
| '''Command/Procedure'''
|-
|GRUB Boot Menu
|Goto "Advanced Boot Options" and choose a device tree from the provided dtb list.
|-
|Linux
|grub-editenv /boot/grub/grubenv set fdtfile=<fdt_file_name>
|-
|}

= Serial Console =
MCM-iMX93 provides serial console on UART1.
SBC-MCM93 carrier-board exposes the console UART via CP2104 serial-to-USB bridge on connector '''P3''' depicted [[MCM-iMX93: Evaluation Kit: Hardware Guide#Connector_Locations | here ]]
== Connecting to a host PC ==
# Use a micro-USB cable to connect the console to an USB port on your host PC.
# Make sure the CP2104 driver is available with your operating system, otherwise install CP2104 driver onto the host PC from https://www.silabs.com/documents/public/software/CP210x_Windows_Drivers_with_Serial_Enumeration.zip
# Identify the host PC interface and port number that will be used for communication with the MCM-iMX93 evaluation kit:
#* In most Linux PCs, the serial port will be denoted as one of the following (where n is a positive integer): /dev/ttyUSB0, /dev/ttyUSB1 ... /dev/ttyUSBn
#* In Windows PCs, the serial port usually will be denoted as one of the following (where n is a positive integer): COM1, COM2 ... COMn
# Start a terminal emulation program (such as [https://www.putty.org/ PuTTY] on Windows or minicom on Linux).
# In the port configuration section of the terminal emulation program select the port identified in previous step and set the following serial port parameters:
<blockquote>
{{:SB-SOM: serial port parameters table}}
</blockquote>

=Display=
==LVDS==
The MCM-iMX93 evaluation kit can be optionally supplied with the Startec KD070HDTLA020 7" LVDS LCD panel.
Use the EB-HDRLVDS adapter to connect the LCD panel (if ordered with the kit) to connectors '''P13''' and '''P14''' as depicted in [[MCM-iMX93: Evaluation Kit: Hardware Guide#Connector_Locations | Connector Locations ]].
Check the Linux device node for information about the display, such as its supported modes and its current configuration.
udevadm info -ap /sys/class/drm/card0-LVDS-1

==Display Manager==
MCM-iMX93 Yocto uses Weston as the default display manager. It can be configured in ''/etc/xdg/weston/weston.ini''.
For example the transform setting can be set to rotate-90, rotate-180, rotate-270, or commented out.
In order to apply the configuration, you need to:
systemctl restart weston



= USB =
MCM-iMX93 features two USB2.0 ports that are derived from the i.MX93 USB sub-system. 
SBC-MCM93 carrier-board multiplexes '''J2''' USB connector with mini-PCIe socket '''P8'''. To use USB connector '''J2''' make sure jumper '''E1''' is open. 
USB connector '''J3''' is multiplexed with USB SDP port as detailed [[MCM-iMX93: Evaluation Kit: Hardware Guide#Serial_Download_Programming_.28SDP.29_port| here]].

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

=CAN bus=
SBC-MCM93 evaluation board exposes one CAN bus interface on header '''P17'''.

* To test it you will need another board with CAN IF
* Configure both CAN interface bit-rate to 1 Mbit/sec:
<pre>
ip link set can0 up type can bitrate 1000000
</pre>

* On one system, dump all received data frames as well as error frames:
<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>

On second system:
* Send standard CAN frame:
<pre>
cansend can0 111#1122334455667788
</pre>

* Send extended CAN frame:
<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>

= WiFi =
SBC-MCM93 carrier-board 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 WiFi module.}}

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

== Network Scanning ==
* Sample WiFi scanning:
nmcli dev wifi list
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:
nmcli device wifi connect <SSID> password <PASSWORD> name WifiCon
* Disconnect wireless network:
nmcli connection down WifiCon
* Connect wireless network again:
nmcli connection up WifiCon

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

= Bluetooth =
SBC-MCM93 carrier-board features Bluetooth connectivity implemented with an NXP 88W8997 module. 

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

To start '''bluetoothctl''' use the following command:
bluetoothctl

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

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

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

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

To quit '''bluetoothctl''' use the following command:
[Device_Name]# quit

=Cellular Modem=
The MCM-iMX93 evaluation kit can be optionally supplied with Quectel EG25-G mini-PCIe cellular modem

* Install the modem module into the mini-PCIe socket [[MCM-iMX93: Evaluation Kit: Hardware Guide#Connector_Locations | '''P8''']]
* Close jumper [[MCM-iMX93: Evaluation Kit: Hardware Guide#Jumpers_Summary| '''E1''']]
* Connect a cellular antenna to modem's main antenna connector
* Install an active SIM card into SIM socket [[MCM-iMX93: Evaluation Kit: Hardware Guide#Connector_Locations | '''P7''']]
* Boot to linux

Run the following command to verify that the modem is detected correctly:
lsusb
Expected output:
Bus 001 Device 002: ID 2c7c:0125 Quectel Wireless Solutions Co., Ltd. EC25 LTE modem
run:
mmcli -L
Expected output:
/org/freedesktop/ModemManager1/Modem/0 [QUALCOMM INCORPORATED] QUECTEL Mobile Broadband Module
Obtain <apn> of your sim card company ,e.g. rl.internet

Establish connection:
<pre>
nmcli connection add type gsm ifname '*' con-name CellularCon apn <apn>
nmcli connection
</pre>
Expected output:
<pre>
NAME UUID TYPE DEVICE
CellularCon a1620622-8588-4349-b3fc-66be79fbbede gsm cdc-wdm0
</pre>
Allow up to a minute to connect to wireless network and make sure modem state is connected:
mmcli -m 0
To test the wireless interface run:
ping -c 5 dns.google -I wwan0

=UART=
The following table outlines default UART routing when MCM-iMX93 is used with the SBC-MCM93 carrier-board:

{| class="wikitable" style="text-align:center;"
|-
| '''MCM-iMX93 port''' || '''Linux device''' || '''on SBC-MCM93 carrier-board''' || pinout
|-
|UART3
|/dev/ttyLP2
|[[MCM-iMX93: Evaluation Kit: Hardware Guide#Connector_Locations | 100-mil header P20]]
| 2-rx, 4-tx
|-
|UART5
|/dev/ttyLP4
| [[MCM-iMX93: Evaluation Kit: Hardware Guide#Connector_Locations | 100-mil header P19]]
| 4-tx, 2-rx, 3-rts, 6-cts
|-
|}

'''Example: testing UART5'''
* Short RX and TX pins on SBC-MCM93 to create a loop-back.
* Run the following commands:
stty -F /dev/ttyLP4 1:0:1cb2:0:3:1c:7f:15:4:5:1:0:11:13:1a:0:12:f:17:16:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0
cat /dev/ttyLP4 &
echo hello > /dev/ttyLP4
The "hello" string should appear on the terminal.

=I2C=
The following I2C buses and devices are present when MCM-iMX93 is used with the SBC-MCM93 carrier-board:
{| class="wikitable" style="text-align:center;"
|-
| '''Device''' || '''I2C bus in Linux''' || '''Address''' || '''HW port in MCM-iMX93'''
|-
|user I2C on connector [[MCM-iMX93: Evaluation Kit: Hardware Guide#Connector_Locations | P16]] pins: 3-sda, 5-scl
|5
|NA
|I2C6
|-
|}

To list all mapped devices:
ls /proc/device-tree/soc@0/bus@*/i2c@*/*@* -d -w 1
Note how:
* each node is appended with its address.
* I2C buses order corresponds to the order of their addresses.

e.g. to inspect bus 0, in which we have RTC, run:
# i2cdetect -y 0
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: 50 51 52 53 -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- UU -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
In the above output numbers mark unused devices, UU marks a device that is used by a driver.

Indeed we see RTC in use at offset 0x69.

An example how to dump EEPROM contents:
hexdump -C /sys/devices/platform/soc@0/44000000.bus/44340000.i2c/i2c-0/0-0050/eeprom

=SPI=
SBC-MCM93 carrier-board exposes SPI3 port on 10-mil header [[MCM-iMX93: Evaluation Kit: Hardware Guide#Connector_Locations | P15]]. 
<pre>
ECSPI3_MOSI - pin 3
ECSPI3_SCLK - pin 5
ECSPI3_MISO - pin 2
ECSPI3_SSO - pin 4
</pre>

Loopback example:

Short MOSI and MISO pins.

Compile test tool:
${CROSS_COMPILE}gcc ./tools/spi/spidev_test.c -o ./spidev_test

Copy the spidev_test binary to the SoM.

On the module, run:
./spidev_test -v -D /dev/spidev0.0 -p "hello"

You should see RX same as TX.

=GPIO=
SBC-MCM93 carrier-board provides the following MCM-iMX93 GPIOs on 100-mil header [[MCM-iMX93: Evaluation Kit: Hardware Guide#Connector_Locations | P18]]. 

{| class="wikitable" style="text-align:center;"
|-
| '''Signal Name || '''pin''' || '''GPIO # in sysfs'''
|-
|GPIO_IO18
|2
|32+18
|-
|GPIO2_21
|3
|96+21
|-
|GPIO_IO24
|5
|32+24
|-
|GPIO_IO26
|7
|32+26
|-
|GPIO_IO22
|9
|32+22
|-
|}

==Example: controlling pin GPIO_IO18==
'''Exporting the pin in sysfs'''
<pre>
cd /sys/class/gpio/
echo $((32+18)) > export
</pre>
Now pin GPIO_IO18 is assigned to sysfs. You can view the newly created entry in line 18 by running:
<pre>gpioinfo 0</pre>

'''Writing to a pin'''
<pre>cd /sys/class/gpio/gpio$((32+18))</pre>
Set pin direction to output:
<pre>echo out > direction</pre>
Set pin value to high or low:
<pre>
echo 1 > value
echo 0 > value
</pre>
'''Reading from a pin'''
<pre>cd /sys/class/gpio/gpio$((32+18))</pre>
Set pin direction to input:
<pre>echo in > direction</pre>
Read the value of the pin from the value file:
<pre>cat value</pre>

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

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

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

To resume normal operation press shortly the power button [[MCM-iMX93: Evaluation Kit: Hardware Guide#Connector_Locations | '''SW4''']].

=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:
cat /sys/class/thermal/thermal_zone0/temp

= RTC =
MCM-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 keeper

== Internal RTC - rtc0 ==
System information:

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

== External RTC - rtc1 ==
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>

= Device Serial Number=
Product information is stored in on-board EEPROM. 
* To read the product serial number run:
cat /proc/device-tree/product-sn && echo
* To read the product configuration part number run:
cat /proc/device-tree/product-options && echo

=See Also=
* [[MCM-iMX93: Evaluation Kit: Getting Started|Eval-kit Quick Start Guide]]
* [[MCM-iMX93: Evaluation Kit: Hardware Guide|Eval-Kit Hardware Guide]]

[[Category:Yocto]]
[[Category:MCM-iMX93]]

@@ Line 104: / Line 104: @@
 USB connector '''J3''' is multiplexed with USB SDP port as detailed [[MCM-iMX93: Evaluation Kit: Hardware Guide#Serial_Download_Programming_.28SDP.29_port| here]].
-== USB in device mode ==
+== USB Device (Gadget) Mode ==
-USB port can be operated in device mode when connected to a host machine using connector '''P21'''.</br>
+*The SoM supports the mode through its USB‑OTG controller.
-Available gadgets for the UBS device mode:
+*USB port P21 can be operated in device mode when connected to a host machine
-{| class="wikitable" style="text-align:left;"
+*Linux can expose multiple USB functions (Serial, Ethernet, Mass Storage, etc.) to a host PC.
-|-
-|'''USB gadget''' ||'''SOM command'''
+=== Legacy Gadget Modules (Simple Evaluation) ===
-|-
+For quick, single‑function testing.
-|usb serial device||modprobe g_serial
 |-
-|usb network device||modprobe g_ether
+| USB Serial || modprobe g_serial
 |-
-|usb mass storage device||modprobe g_mass_storage file=/dev/sdX
+| USB Ethernet || modprobe g_ether
 |-
 |}
 =CAN bus=
@@ Line 439: / Line 471: @@
 {{note|The operation below requires '''root''' access.}}
 *Suspend mode allows minimizing the power consumption.
-*WiFi device currently doesn't support suspension so you should first run:
+*To enter suspend mode run:
   echo mem >/sys/power/state
 *To resume normal operation press shortly the power button [[MCM-iMX93: Evaluation Kit: Hardware Guide#Connector_Locations | '''SW4''']].
-*To enter temporary sleep run:
+*To enter suspend mode with RTC as wakeup source that wakes after 5 seconds run:
   rtcwake -s 5 -m mem -d /dev/rtc0
 =CPU temperature=
-i.MX93 SoC features an internal temperature sensor which allows to measure the SoC 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:
+*Execute the following command to read the current CPU temperature:
   cat /sys/class/thermal/thermal_zone0/temp

@@ Line 1: / Line 1: @@
-=user LED=
+= Device Tree =
 == Available Device Tree Files ==
 The current release includes the following '''dtb''' files:
@@ Line 23: / Line 13: @@
 |-
 |}
+== Switching the Device Tree ==
 The current release provides two methods to switch between dtb files:
 * U-Boot environment
@@ Line 497: / Line 486: @@
 </pre>
 = Device Serial Number=
 Product information is stored in on-board EEPROM.<br>

@@ Line 1: / Line 1: @@
 =Device Tree=
 == Available Device Tree Files ==
@@ Line 121: / Line 131: @@
 =CAN bus=
-SBC-MCM93 evaluation board exposes one CAN bus interface on header '''P17'''.
+CAN bus interface is available via header '''P17'''.
+CAN bus on-board termination is enabled by shorting jumper '''E6'''.
-* To test it you will need another board with CAN IF
+==Operation Example==
-* Configure both CAN interface bit-rate to 1 Mbit/sec:
+* Obtain another board with CAN interface
 <pre>
-  ip link set can0 up type can bitrate 1000000
+DUT Header P17          Device 2
 </pre>
+* Configure both CAN interface bit-rate to 1 Mbit/sec:
 <pre>
-cansend can0 11111111#1122334455667788
+ip link set can0 up type can bitrate 1000000
 </pre>
-* CAN frames (extended mode) generator, random payload, interval between two successive flames 50 msec:
+* Send data from one system and expect to receive it on the other:
-<pre>
+:* Standard frame:
-cangen -g 50 -e -D r -v can0
+ cansend can0 111#1122334455667788
+:* Extended frame:
-can: raw protocol (rev 20170425)
+ cansend can0 11111111#1122334455667788
-...
+:* Generate 50 random extended frames with 50 msec interval between each:
-  can0  03FF0983#D7.61.FF.03.C1.F7.C1.34
+ cangen -g 50 -e -D r -v can0 -n 50
-  can0  19C34D32#F7.5A.C2.73.AD.0E.3F.0B
+* Disable the interfaces:
-  can0  0675E391#2B.2D.D3.49
+  ip link set can0 down
 =Ethernet=
@@ Line 319: / Line 285: @@
 |UART3
 |/dev/ttyLP2
-|[[MCM-iMX93: Evaluation Kit: Hardware Guide#Connector_Locations | 100-mil header P20]]
+|[[MCM-iMX93: Evaluation Kit: Hardware Guide#Connector_Locations | 100-mil header P19]]
 | 2-rx, 4-tx
 |-
 |UART5
 |/dev/ttyLP4
-| [[MCM-iMX93: Evaluation Kit: Hardware Guide#Connector_Locations | 100-mil header P19]]
+| [[MCM-iMX93: Evaluation Kit: Hardware Guide#Connector_Locations | 100-mil header P20]]
 | 4-tx, 2-rx, 3-rts, 6-cts
 |-

@@ Line 99: / Line 99: @@
 aplay -D hw:0,0 -vv /path/to/media.file
 </pre>
 = USB =
@@ Line 263: / Line 233: @@
 == Creating Access Point ==
-In the following example:
+*Prepare routing:
-* Replace <SSID> and <PASSWORD> with desired access point parameters:
+<pre>
-  nmcli device wifi hotspot ssid <SSID> password <PASSWORD> con-name HotspotCon
+iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
 * Disable wireless AP:
   nmcli connection down HotspotCon
@@ Line 407: / Line 386: @@
 Short MOSI and MISO pins.
 On the module, run:
-  ./spidev_test -v -D /dev/spidev0.0 -p "hello"
+  spidev_test -v -D /dev/spidev0.0 -p "hello"
 You should see RX same as TX.
@@ Line 480: / Line 453: @@
 =ADC=
 i.MX93 SoC features integrated 12 bit analog to digital converter.<br>
 for sysfs device controls go to:
   cd /sys/bus/iio/devices/iio\:device0/
@@ Line 518: / Line 482: @@
 =Suspend / Resume=
-{{note|The following operation requires '''root''' access.}}
+{{note|The operation below requires '''root''' access.}}
+*Suspend mode allows minimizing the power consumption.
-MCM-iMX93 features suspend mode, which allows to minimize power consumption.
+*WiFi device currently doesn't support suspension so you should first run:
+<pre>
-The following command should be used to enter suspend mode:
+ip link set mlan0 down
   echo mem >/sys/power/state
+*To resume normal operation press shortly the power button [[MCM-iMX93: Evaluation Kit: Hardware Guide#Connector_Locations | '''SW4''']].
-To resume normal operation press shortly the power button [[MCM-iMX93: Evaluation Kit: Hardware Guide#Connector_Locations | '''SW4''']].
+*To enter temporary sleep run:
 =CPU temperature=

@@ Line 424: / Line 424: @@
 {| class="wikitable" style="text-align:center;"
 |-
-| '''Signal Name || '''pin''' || '''GPIO # in sysfs'''
+| '''Name in u-boot || '''pin''' || '''GPIO # in sysfs'''
 |-
-|GPIO_IO18
+|GPIO2_18
 |2
-|32+18
+|512+18
 |-
 |GPIO2_21
 |3
-|96+21
+|512+21
 |-
-|GPIO_IO24
+|GPIO2_24
 |5
-|32+24
+|512+24
 |-
-|GPIO_IO26
+|GPIO2_26
 |7
-|32+26
+|512+26
 |-
-|GPIO_IO22
+|GPIO2_22
 |9
-|32+22
+|512+22
 |-
 |}
-==Example: controlling pin GPIO_IO18==
+==Example: controlling pin GPIO2_18==
 '''Exporting the pin in sysfs'''</br>
 <pre>
 cd /sys/class/gpio/
-echo $((32+18)) > export
+echo $((512+18)) > export
 </pre>
 '''Writing to a pin'''</br>
 Set pin direction to output:
-<pre>echo out > direction</pre>
+ echo out > direction
 Set pin value to high or low:
 <pre>
@@ Line 467: / Line 473: @@
 </pre>
 '''Reading from a pin'''</br>
 Set pin direction to input:
-<pre>echo in > direction</pre>
+ echo in > direction
 Read the value of the pin from the value file:
-<pre>cat value</pre>
+ cat value
 =ADC=
 i.MX93 SoC features integrated 12 bit analog to digital converter.<br>
 To use the ADC, enable it in device tree e.g. in arch/arm64/boot/dts/compulab/sbc-mcm-imx93.dts:
 <pre>
@@ Line 482: / Line 488: @@
 };
 </pre>
-Sysfs device controls will appear in:
+-->
   cd /sys/bus/iio/devices/iio\:device0/
 SBC-MCM93 exposes ADC signals on 100-mil header '''P9'''.

@@ Line 73: / Line 73: @@
   systemctl restart weston
 <!--
 =Camera=
@@ Line 196: / Line 222: @@
 ...
 </pre>
 = WiFi =
@@ Line 432: / Line 472: @@
 Read the value of the pin from the value file:
 <pre>cat value</pre>
 =Suspend / Resume=