Voipac Wiki - User contributions [en]

iMX93 Industrial Debian

2026-02-26T10:31:58Z

Voipac-sw: /* Flashing the binaries */

[[Category:iMX93 Industrial]]
[[Category:iMX91 Industrial]]
[[Category:iMX93 Industrial Software]]
[[Category:iMX91 Industrial Software]]
[[Category:iMX93 Industrial Debian]]
[[Category:iMX91 Industrial Debian]]
[[Category:Debian]]

<div style="float:right">__TOC__</div>

This Wiki page guides through the process of downloading the Debian source files for release (bookworm) and building images for the iMX93 Industrial Development Kit.

All the source files for this customized Debian, together with the recent changes made, can be inspected and downloaded at the [https://github.com/voipac/debian-imx-voipac Voipac GitHub] repository.

== Cloning the project ==
Create a new directory for the project environment:
<syntaxhighlight lang="bash">
mkdir ~/voipac-debian
cd ~/voipac-debian
</syntaxhighlight>

Clone the iMX9x Industrial Debian Project into the host machine:
<syntaxhighlight lang="bash">
git clone https://github.com/voipac/debian-imx-voipac
</syntaxhighlight>

== Prerequisites ==

For Debian image building it is necessary to install docker [https://docs.docker.com/desktop/setup/install/linux/ubuntu/ installation] as whole procedure is done in virtualised environment.

== Building the image ==
Voipac provides quick and simple-to-use option how to build an image by using [https://github.com/voipac/debian-imx-voipac/blob/master/build_debian_voipac.sh build_debian_voipac.sh] prepared script:

This script automatically create Debian image for iMX93:
<syntaxhighlight lang="bash">
MACHINE=imx93-voipac ./build_debian_voipac.sh
</syntaxhighlight>

During the u-boot build user will be asked for RAM Size. For basic kit configuration select option (1), for lite select 1G (option 2) and for pro and max configurations choose 2G option (option 3) as shown in below image. 

[[image:Screenshot from 2025-01-29 08-48-33.png|400px]] 

== Locating output files ==
After the build process was completed, the freshly built output files are located in the root directory:
<syntaxhighlight lang="bash">
ls -la image.sdimg
</syntaxhighlight>

== Prebuild images ==
Prebuild images can be downloaded at following [https://downloads.voipac.com/index.php?p=iMX93_Industrial_Development_Kit/module/software/debian/binaries link]

== Flashing the binaries ==
At this point everything was prepared to flash the binaries. Follow the [[iMX93 Industrial Flashing Procedure|flashing procedure]] instructions to start the development kit with the compiled images.

=== eMMC Flash Memory (default) ===

==== Linux ====
<syntaxhighlight lang="bash">
sudo ./uuu -b emmc_all flash_imx93_<type>.bin debian12_<type>.sdimg
</syntaxhighlight>

==== Windows ====
<syntaxhighlight lang="bash">
uuu.exe -b emmc_all flash_imx93_<type>.bin debian12_<type>.sdimg
</syntaxhighlight>

=== SD Card ===

==== Linux ====
<syntaxhighlight lang="bash">
sudo ./uuu -b flash_imx93_<type>.bin debian12_<type>.sdimg
</syntaxhighlight>

==== Windows ====
<syntaxhighlight lang="bash">
uuu.exe -b sd_all flash_imx93_<type>.bin debian12_<type>.sdimg
</syntaxhighlight>

== Login ==
When image is flashed and board is booted default credentials can be either '''root/root''' or '''voipac/voipac'''.

iMX91 Industrial Debian

2026-02-25T09:16:51Z

Voipac-sw: /* Flashing the binaries */

[[Category:iMX91 Industrial]]
[[Category:iMX91 Industrial Software]]
[[Category:iMX91 Industrial Debian]]
[[Category:Debian]]

<div style="float:right">__TOC__</div>

This Wiki page guides through the process of downloading the Debian source files for release (bookworm) and building images for the iMX91 Industrial Development Kit.

All the source files for this customized Debian, together with the recent changes made, can be inspected and downloaded at the [https://github.com/voipac/debian-imx-voipac Voipac GitHub] repository.

== Cloning the project ==
Create a new directory for the project environment:
<syntaxhighlight lang="bash">
mkdir ~/voipac-debian
cd ~/voipac-debian
</syntaxhighlight>

Clone the iMX9x Industrial Debian Project into the host machine:
<syntaxhighlight lang="bash">
git clone https://github.com/voipac/debian-imx-voipac
</syntaxhighlight>

== Prerequisites ==

For Debian image building it is necessary to install docker [https://docs.docker.com/desktop/setup/install/linux/ubuntu/ installation] as whole procedure is done in virtualised environment.

== Building the image ==
Voipac provides quick and simple-to-use option how to build an image by using [https://github.com/voipac/debian-imx-voipac/blob/master/build_debian_voipac.sh build_debian_voipac.sh] prepared script:

This script automatically create Debian image for iMX91:
<syntaxhighlight lang="bash">
MACHINE=imx91-voipac ./build_debian_voipac.sh
</syntaxhighlight>

During the u-boot build user will be asked for RAM Size. For basic kit configuration select option (1), for lite select 1G (option 2) and for pro and max configurations choose 2G option (option 3) as shown in below image. 

[[image:Screenshot from 2025-01-29 08-48-33.png|400px]] 

== Locating output files ==
After the build process was completed, the freshly built output files are located in the root directory:
<syntaxhighlight lang="bash">
ls -la image.sdimg
</syntaxhighlight>

== Prebuild images ==
Prebuild images can be downloaded at following [https://downloads.voipac.com/index.php?p=iMX91_Industrial_Development_Kit/module/software/debian/binaries link]

== Flashing the binaries ==
At this point everything was prepared to flash the binaries. Follow the [[iMX91 Industrial Flashing Procedure|flashing procedure]] instructions to start the development kit with the compiled images.
There is a slight change for flashing compared to yocto binaries:
=== eMMC Flash Memory (default) ===

==== Linux ====
<syntaxhighlight lang="bash">
sudo ./uuu -b emmc_all flash_imx91_<type>.bin debian12_<type>.sdimg
</syntaxhighlight>

==== Windows ====
<syntaxhighlight lang="bash">
uuu.exe -b emmc_all flash_imx91_<type>.bin debian12_<type>.sdimg
</syntaxhighlight>

=== SD Card ===

==== Linux ====
<syntaxhighlight lang="bash">
sudo ./uuu -b flash_imx91_<type>.bin debian12_<type>.sdimg
</syntaxhighlight>

==== Windows ====
<syntaxhighlight lang="bash">
uuu.exe -b sd_all flash_imx91_<type>.bin debian12_<type>.sdimg
</syntaxhighlight>

== Login ==
When image is flashed and board is booted default credentials can be either '''root/root''' or '''voipac/voipac'''.

iMX91 Industrial Secure Boot

2026-01-15T10:37:56Z

Voipac-sw:

[[Category:imx91 Industrial]]
[[Category:imx91 Industrial Software]]

<div style="float:right">__TOC__</div>

This Wiki page provides a step-by-step guide to building and flashing a Yocto Project image with secure boot integration. These instructions apply to the imx91 Industrial Module.

'''''Note:''''' Please inspect all the recent changes at [https://github.com/voipac/yocto-imx-voipac/blob/imx9-secure-boot/ Voipac GitHub repository] and start the custom build with the newest updates.

'''''Note:''''' Additional information about the process could be found at [https://github.com/nxp-imx/uboot-imx/blob/lf_v2023.04/doc/imx/ahab/guides/mx8ulp_9x_secure_boot.txt NXP Github page].

This build was verified on Ubuntu 20.04.

== Prerequisites ==
* Install docker package on the operating system
* Download the CST tool from [https://www.nxp.com/webapp/sps/download/license.jsp?colCode=IMX_CST_TOOL NXP website]
* Unpack it into a machine where Yocto will be compiled:
<syntaxhighlight lang="bash">/home/user/cst</syntaxhighlight>
* Navigate to the subdirectory:
<syntaxhighlight lang="bash">/home/user/cst/keys</syntaxhighlight>
* Create a text file called '''''"serial"''''', which contains 8 digits. It will be used for the certificate serial numbers:
<syntaxhighlight lang="bash">echo 12345678 > serial</syntaxhighlight>
* Create a text file called '''''"key_pass.txt"''''', which contains two lines of a password repeated twice. This password will be used to protect the generated private keys:
<syntaxhighlight lang="bash">
echo my_secret_password > key_pass.txt
echo my_secret_password >> key_pass.txt
</syntaxhighlight>

== Generating keys ==
To generate the PKI tree, run the following command:
<syntaxhighlight lang="bash">
./ahab_pki_tree.sh
</syntaxhighlight>

Complete the interactive questions. For example:
<syntaxhighlight lang="bash">
Do you want to use an existing CA key (y/n)?: n
Key type options (confirm targeted device supports desired key type):
Select the key type (possible values: rsa, rsa-pss, ecc)?: ecc
Enter length for elliptic curve to be used for PKI tree:
Possible values p256, p384, p521: p384
Enter the digest algorithm to use: sha384
Enter PKI tree duration (years): 20
Do you want the SRK certificates to have the CA flag set? (y/n)?: n
</syntaxhighlight>

Generate Super Root Key (SRK) table:
<syntaxhighlight lang="bash">
cd ../crts
../linux64/bin/srktool -a -d sha256 -s sha384 -t SRK1234table.bin -e SRK1234fuse.bin -f 1 -c SRK1_sha384_secp384r1_v3_usr_crt.pem,SRK2_sha384_secp384r1_v3_usr_crt.pem,SRK3_sha384_secp384r1_v3_usr_crt.pem,SRK4_sha384_secp384r1_v3_usr_crt.pem
</syntaxhighlight>

'''''Note:''''' For the i.MX 93 SoC, the Message Digest algorithm (option —d) is sha256, while the Signature Digest algorithm (option -s) must match the option from the PKI generation.

Create a file in root of cst directory called '''''"cfs_ahag.cfg"''''' with the following content:
<syntaxhighlight lang="bash">
#Header
header_version=1.0
#Install SRK
srktable_file=SRK1234table.bin
srk_source=SRK1_sha384_secp384r1_v3_usr_crt.pem
srk_source_index=0
srk_source_set=OEM
srk_revocations=0x0
#Install Certificate
sgk_file=
sgk_permissions=
</syntaxhighlight>

This file will be used by Yocto to point to the proper SRK table and keys.

== Building an image ==
Build an image for imx91 Industrial Development Kit in the docker container:
<syntaxhighlight lang="bash">
build_image_container.sh pro imx91
</syntaxhighlight>

When image is ready, locate machine files in the build directory and copy them into an output directory:
<syntaxhighlight lang="bash">
cp -p signed-imx-boot-imx91-voipac-sd.bin-flash_singleboot /home/user/output
cp -p voipac-image-imx91-voipac.rootfs.wic.zst /home/user/output
</syntaxhighlight>

Use following script to flash the image into the development kit:
<syntaxhighlight lang="bash">
#!/bin/sh

sudo ./uuu -b emmc_all voipac-image-imx91-voipac.rootfs.wic.zst
# flash secure imx-boot
sudo ./uuu uuu-hab.lst
</syntaxhighlight>

Where '''''"uuu-hab.lst"''''' has following content:
<syntaxhighlight lang="bash">
uuu_version 1.2.39

SDPS: boot -f signed-imx-boot-imx91-voipac-sd.bin-flash_singleboot

FB: ucmd setenv fastboot_dev mmc
FB: ucmd setenv mmcdev ${emmc_dev}
FB: ucmd mmc dev ${emmc_dev}
FB: flash bootloader signed-imx-boot-imx91-voipac-sd.bin-flash_singleboot
FB: ucmd if env exists emmc_ack; then ; else setenv emmc_ack 0; fi;
FB: ucmd mmc partconf ${emmc_dev} ${emmc_ack} 1 0
FB: Done
</syntaxhighlight>

'''''Note:''''' The complete flashing procedure is described in detail in the [[imx91 Industrial Flashing Procedure|flashing procedure wiki page]].

== Programming fuses ==
Boot the newly built image and hit any key after startup to halt the booting.

Program the SRK (public keys) to the SOC e-fuses:
* Navigate to the directory: <syntaxhighlight lang="bash">cst/crts</syntaxhighlight>
* Run following command: <syntaxhighlight lang="bash">od -t x4 SRK1234fuse.bin</syntaxhighlight>
* Its output should be looking like this:
<syntaxhighlight lang="bash">
0000000 f43dab72 1b8eda1a 1ddd596d a1cb9682
0000020 0bf178ea 32308483 d596393c ca21a9b
</syntaxhighlight>

'''''Important:''''' This process in non-reversable. '''Incorrect fuse programming can lead to bricking the device!'''

Use these values to set up eFuses in u-boot console:

'''''Important:''''' Do not forget to replace this example with the numbers generated by your keys.
<syntaxhighlight lang="bash">
=> fuse prog 16 0 0xf43dab72
=> fuse prog 16 1 0x1b8eda1a
=> fuse prog 16 2 0x1ddd596d
=> fuse prog 16 3 0xa1cb9682
=> fuse prog 16 4 0x0bf178ea
=> fuse prog 16 5 0x32308483
=> fuse prog 16 6 0xd596393c
=> fuse prog 16 7 0xca21a9b
</syntaxhighlight>

Restart the board, press any key to stay in u-boot and run '''''"ahab_status"'''''. Output should look like this:
<syntaxhighlight lang="bash">
=> ahab_status
Lifecycle: 0x00000008, OEM Open

No Events Found!
</syntaxhighlight>

If there are any events present, please go back and double check if the keys were generated correctly and fuses flashed properly.
 
Please also verify if the board can boot to the userspace.

==Perform verification tests while the device is in Open state==

===Wrong Key Test===
Re-sign container using a different SRK set and flash it over the original.
 
Boot the device and run ahab_status.
Expected AHAB event:
 
0x0087FA00 — Container authentication failed due to SRK hash mismatch (wrong key or SRK fuses not yet programmed).

===Tamper Test===
Modify one byte inside the signed container binary (e.g., os_cntr_signed.bin) and reflash it.
Boot the device and run ahab_status.

Container authentication failed because signature verification failed (tampered content).

<syntaxhighlight lang="bash">
=> ahab_status
u-boot=> ahab_status
Lifecycle: 0x00000008, OEM Open

0x0287f0d6
IPC = MU APD (0x2)
CMD = ELE_OEM_CNTN_AUTH_REQ (0x87)
IND = ELE_BAD_SIGNATURE_FAILURE_IND (0xF0)
STA = ELE_SUCCESS_IND (0xD6)
</syntaxhighlight>

When try to boot image then we get following:
<syntaxhighlight lang="bash">
Running BSP bootcmd ...
switch to partitions #0, OK
mmc0(part 0) is current device
Failed to load 'boot.scr'
35750715 bytes read in 167 ms (204.2 MiB/s)
Booting from mmc ...
Authenticate OS container at 0x98000000
mu receive msg wait 1s
mu receive msg wait 2s
mu receive msg wait 3s
ERROR: Did not find a cmdline Flattened Device Tree
Could not find a valid device tree
</syntaxhighlight>

and board fails to boot.

==OEM board close==

Restart the board, stop the execution in uboot, and close the device:
<syntaxhighlight lang="bash">
ahab_close
</syntaxhighlight>

Restart the board and run '''''"ahab_status"''''' command again:
<syntaxhighlight lang="bash">
=> ahab_status
Lifecycle: 0x00000020, OEM Closed

No Events Found!
</syntaxhighlight>

'''After this step the device is locked and only images signed with private keys will be able to boot on this device.'''

iMX93 Industrial Secure Boot

2026-01-15T10:36:41Z

Voipac-sw:

[[Category:iMX93 Industrial]]
[[Category:iMX93 Industrial Software]]

<div style="float:right">__TOC__</div>

This Wiki page provides a step-by-step guide to building and flashing a Yocto Project image with secure boot integration. These instructions apply to the iMX93 Industrial Module.

'''''Note:''''' Please inspect all the recent changes at [https://github.com/voipac/yocto-imx-voipac/blob/imx9-secure-boot/ Voipac GitHub repository] and start the custom build with the newest updates.

'''''Note:''''' Additional information about the process could be found at [https://github.com/nxp-imx/uboot-imx/blob/lf_v2023.04/doc/imx/ahab/guides/mx8ulp_9x_secure_boot.txt NXP Github page].

This build was verified on Ubuntu 20.04.

== Prerequisites ==
* Install docker package on the operating system
* Download the CST tool from [https://www.nxp.com/webapp/sps/download/license.jsp?colCode=IMX_CST_TOOL NXP website]
* Unpack it into a machine where Yocto will be compiled:
<syntaxhighlight lang="bash">/home/user/cst</syntaxhighlight>
* Navigate to the subdirectory:
<syntaxhighlight lang="bash">/home/user/cst/keys</syntaxhighlight>
* Create a text file called '''''"serial"''''', which contains 8 digits. It will be used for the certificate serial numbers:
<syntaxhighlight lang="bash">echo 12345678 > serial</syntaxhighlight>
* Create a text file called '''''"key_pass.txt"''''', which contains two lines of a password repeated twice. This password will be used to protect the generated private keys:
<syntaxhighlight lang="bash">
echo my_secret_password > key_pass.txt
echo my_secret_password >> key_pass.txt
</syntaxhighlight>

== Generating keys ==
To generate the PKI tree, run the following command:
<syntaxhighlight lang="bash">
./ahab_pki_tree.sh
</syntaxhighlight>

Complete the interactive questions. For example:
<syntaxhighlight lang="bash">
Do you want to use an existing CA key (y/n)?: n
Key type options (confirm targeted device supports desired key type):
Select the key type (possible values: rsa, rsa-pss, ecc)?: ecc
Enter length for elliptic curve to be used for PKI tree:
Possible values p256, p384, p521: p384
Enter the digest algorithm to use: sha384
Enter PKI tree duration (years): 20
Do you want the SRK certificates to have the CA flag set? (y/n)?: n
</syntaxhighlight>

Generate Super Root Key (SRK) table:
<syntaxhighlight lang="bash">
cd ../crts
../linux64/bin/srktool -a -d sha256 -s sha384 -t SRK1234table.bin -e SRK1234fuse.bin -f 1 -c SRK1_sha384_secp384r1_v3_usr_crt.pem,SRK2_sha384_secp384r1_v3_usr_crt.pem,SRK3_sha384_secp384r1_v3_usr_crt.pem,SRK4_sha384_secp384r1_v3_usr_crt.pem
</syntaxhighlight>

'''''Note:''''' For the i.MX 93 SoC, the Message Digest algorithm (option —d) is sha256, while the Signature Digest algorithm (option -s) must match the option from the PKI generation.

Create a file in root of cst directory called '''''"cfs_ahag.cfg"''''' with the following content:
<syntaxhighlight lang="bash">
#Header
header_version=1.0
#Install SRK
srktable_file=SRK1234table.bin
srk_source=SRK1_sha384_secp384r1_v3_usr_crt.pem
srk_source_index=0
srk_source_set=OEM
srk_revocations=0x0
#Install Certificate
sgk_file=
sgk_permissions=
</syntaxhighlight>

This file will be used by Yocto to point to the proper SRK table and keys.

== Building an image ==
Build an image for iMX93 Industrial Development Kit in the docker container:
<syntaxhighlight lang="bash">
build_image_container.sh pro imx93
</syntaxhighlight>

When image is ready, locate machine files in the build directory and copy them into an output directory:
<syntaxhighlight lang="bash">
cp -p signed-imx-boot-imx93-voipac-sd.bin-flash_singleboot /home/user/output
cp -p voipac-image-imx93-voipac.rootfs.wic.zst /home/user/output
</syntaxhighlight>

Use following script to flash the image into the development kit:
<syntaxhighlight lang="bash">
#!/bin/sh

sudo ./uuu -b emmc_all voipac-image-imx93-voipac.rootfs.wic.zst
# flash secure imx-boot
sudo ./uuu uuu-hab.lst
</syntaxhighlight>

Where '''''"uuu-hab.lst"''''' has following content:
<syntaxhighlight lang="bash">
uuu_version 1.2.39

SDPS: boot -f signed-imx-boot-imx93-voipac-sd.bin-flash_singleboot

FB: ucmd setenv fastboot_dev mmc
FB: ucmd setenv mmcdev ${emmc_dev}
FB: ucmd mmc dev ${emmc_dev}
FB: flash bootloader signed-imx-boot-imx93-voipac-sd.bin-flash_singleboot
FB: ucmd if env exists emmc_ack; then ; else setenv emmc_ack 0; fi;
FB: ucmd mmc partconf ${emmc_dev} ${emmc_ack} 1 0
FB: Done
</syntaxhighlight>

'''''Note:''''' The complete flashing procedure is described in detail in the [[iMX93 Industrial Flashing Procedure|flashing procedure wiki page]].

== Programming fuses ==
Boot the newly built image and hit any key after startup to halt the booting.

Program the SRK (public keys) to the SOC e-fuses:
* Navigate to the directory: <syntaxhighlight lang="bash">cst/crts</syntaxhighlight>
* Run following command: <syntaxhighlight lang="bash">od -t x4 SRK1234fuse.bin</syntaxhighlight>
* Its output should be looking like this:
<syntaxhighlight lang="bash">
0000000 f43dab72 1b8eda1a 1ddd596d a1cb9682
0000020 0bf178ea 32308483 d596393c ca21a9b
</syntaxhighlight>

'''''Important:''''' This process in non-reversable. '''Incorrect fuse programming can lead to bricking the device!'''

Use these values to set up eFuses in u-boot console:

'''''Important:''''' Do not forget to replace this example with the numbers generated by your keys.
<syntaxhighlight lang="bash">
=> fuse prog 16 0 0xf43dab72
=> fuse prog 16 1 0x1b8eda1a
=> fuse prog 16 2 0x1ddd596d
=> fuse prog 16 3 0xa1cb9682
=> fuse prog 16 4 0x0bf178ea
=> fuse prog 16 5 0x32308483
=> fuse prog 16 6 0xd596393c
=> fuse prog 16 7 0xca21a9b
</syntaxhighlight>

Restart the board, press any key to stay in u-boot and run '''''"ahab_status"'''''. Output should look like this:
<syntaxhighlight lang="bash">
=> ahab_status
Lifecycle: 0x00000008, OEM Open

No Events Found!
</syntaxhighlight>

If there are any events present, please go back and double check if the keys were generated correctly and fuses flashed properly.
 
Please also verify if the board can boot to the userspace.

==Perform verification tests while the device is in Open state==

===Wrong Key Test===
Re-sign container using a different SRK set and flash it over the original.
 
Boot the device and run ahab_status.
Expected AHAB event:
 
0x0087FA00 — Container authentication failed due to SRK hash mismatch (wrong key or SRK fuses not yet programmed).

===Tamper Test===
Modify one byte inside the signed container binary (e.g., os_cntr_signed.bin) and reflash it.
Boot the device and run ahab_status.

Container authentication failed because signature verification failed (tampered content).

<syntaxhighlight lang="bash">
=> ahab_status
u-boot=> ahab_status
Lifecycle: 0x00000008, OEM Open

0x0287f0d6
IPC = MU APD (0x2)
CMD = ELE_OEM_CNTN_AUTH_REQ (0x87)
IND = ELE_BAD_SIGNATURE_FAILURE_IND (0xF0)
STA = ELE_SUCCESS_IND (0xD6)
</syntaxhighlight>

When try to boot image then we get following:
<syntaxhighlight lang="bash">
Running BSP bootcmd ...
switch to partitions #0, OK
mmc0(part 0) is current device
Failed to load 'boot.scr'
35750715 bytes read in 167 ms (204.2 MiB/s)
Booting from mmc ...
Authenticate OS container at 0x98000000
mu receive msg wait 1s
mu receive msg wait 2s
mu receive msg wait 3s
ERROR: Did not find a cmdline Flattened Device Tree
Could not find a valid device tree
</syntaxhighlight>

and board fails to boot.

==OEM board close==

Restart the board, stop the execution in uboot, and close the device:
<syntaxhighlight lang="bash">
ahab_close
</syntaxhighlight>

Restart the board and run '''''"ahab_status"''''' command again:
<syntaxhighlight lang="bash">
=> ahab_status
Lifecycle: 0x00000020, OEM Closed

No Events Found!
</syntaxhighlight>

'''After this step the device is locked and only images signed with private keys will be able to boot on this device.'''

iMX Development Baseboard Connectors Locations

2025-10-30T10:32:43Z

Voipac-sw:

[[Category:iMX8M Industrial Development Kit]]
[[Category:iMX93 Industrial Development Kit]]
[[Category:iMX91 Industrial Development Kit]]

== Connectors accessible from the top side ==
[[image:iMX_Development_Baseboard-Connectors-Top.png|center|800px]]

== Connectors accessible from the bottom side ==
[[image:iMX_Development_Baseboard-Connectors-Bottom.png|center|800px]]

iMX91 Industrial Module Interfaces Overview

2025-10-30T10:32:15Z

Voipac-sw:

[[Category:iMX91 Industrial Development Kit]]

== iM91 Industrial Module Interfaces Overview Top Side ==
[[image:iMX91 Industrial Module Interfaces-Overview top.png|center|800px]]
== iMX91 Industrial Module Interfaces Overview Bottom Side ==
[[image:iMX91 Industrial Module Interfaces-Overview bottom.png|center|800px]]

iMX91 Industrial Recovery

2025-10-30T10:31:53Z

Voipac-sw: /* Setting a suitable dtb file in bootloader (u-boot) */

<div style="float:right">__TOC__</div>
=Description=
The recovery procedure consists of following steps:

* Downloading binaries from Voipac download webpage
* Flashing binaries and filesystem over Baseboard USB-C connector
* Setting a suitable dtb file in bootloader (u-boot)
* Resetting and booting a module

==Recommended Software==
* Universal Update Utility (UUU)
* Windows Command Promt
* TFTP Server
* DHCP Server (Otional)

=Configuration=

==Updating Filesystem:==
===Download filesystem:===

https://downloads.voipac.com/index.php?p=iMX91_Industrial_Development_Kit/module/software/filesystem

===Download Universal Update Utility (UUU) if needed:===

https://github.com/nxp-imx/mfgtools/releases

Create a new folder e.g. C:\uuu and move all downloaded files into it.

==Flashing uboot and filesystem==
Prepare Voipac baseboard and follow the steps to flash the module as shown on this [[iMX91 Industrial Flashing Procedure|page]].

==Setting a suitable dtb file in bootloader (u-boot)==

Stop autoboot in bootloader:
<syntaxhighlight lang="bash">
U-Boot 2024.04-lf_v2024.04+g6c4545203d1+p0 (Nov 15 2024 - 04:02:13 +0000)

Reset Status: POR

CPU: NXP i.MX91(31) Rev1.0 A55 at 1400 MHz
CPU: Industrial temperature grade (-40C to 105C) at 29C

Model: Voipac i.MX91 EVK board
DRAM: 2 GiB
optee optee: OP-TEE api uid mismatch
tcpc_init: Can't find device id=0x52
setup_typec: tcpc portpd init failed, err=-19
tcpc_init: Can't find device id=0x51
setup_typec: tcpc port2 init failed, err=-19
tcpc_init: Can't find device id=0x50
setup_typec: tcpc port1 init failed, err=-19
Core: 205 devices, 31 uclasses, devicetree: separate
MMC: FSL_SDHC: 0, FSL_SDHC: 1
Loading Environment from MMC... *** Warning - bad CRC, using default environment

Fail to setup video link
In: serial
Out: serial
Err: serial

BuildInfo:
- ELE firmware version 2.0.0-64d8ef47

switch to partitions #0, OK
mmc0(part 0) is current device
UID: 0f369d90914746998806e2d559c410c7
flash target is MMC:0
Net: eth0: ethernet@42890000, eth1: ethernet@428a0000 [PRIME]
Fastboot: Normal
Normal Boot
Hit any key to stop autoboot: 0
u-boot=>
</syntaxhighlight>

Enter command fatls mmc 0:1 (filesystem in eMMC) or fatls mmc 1:1 (filesystem in SD Card) to see a list of DTB files:
<syntaxhighlight lang="bash">
u-boot=> fatls mmc 0:1
35697152 Image
48709 imx91-11x11-evk-aud-hat.dtb
45805 imx91-11x11-evk-flexspi-m2.dtb
45801 imx91-11x11-evk-flexspi-nand-m2.dtb
46405 imx91-11x11-evk-i2c-spi-slave.dtb
44973 imx91-11x11-evk-i3c.dtb
45319 imx91-11x11-evk-ld.dtb
45403 imx91-11x11-evk-lpuart.dtb
45819 imx91-11x11-evk-mqs.dtb
48061 imx91-11x11-evk-mt9m114.dtb
47525 imx91-11x11-evk-tianma-wvga-panel.dtb
44324 imx91-voipac-evk.dtb

12 file(s), 0 dir(s)

u-boot=>
</syntaxhighlight>

Select the required DTB file and enter the command to set it up:

<syntaxhighlight lang="bash">
u-boot=> setenv fdtfile imx91-voipac-evk.dtb
u-boot=>
</syntaxhighlight>

Save:

<syntaxhighlight lang="bash">
u-boot=> saveenv
Saving Environment to MMC... Writing to MMC(0)... OK
u-boot=>
</syntaxhighlight >

Enter boot command or reset the baseboard for image loading.

iMX91 Industrial Recovery

2025-10-30T10:30:48Z

Voipac-sw: /* Download filesystem: */

<div style="float:right">__TOC__</div>
=Description=
The recovery procedure consists of following steps:

* Downloading binaries from Voipac download webpage
* Flashing binaries and filesystem over Baseboard USB-C connector
* Setting a suitable dtb file in bootloader (u-boot)
* Resetting and booting a module

==Recommended Software==
* Universal Update Utility (UUU)
* Windows Command Promt
* TFTP Server
* DHCP Server (Otional)

=Configuration=

==Updating Filesystem:==
===Download filesystem:===

https://downloads.voipac.com/index.php?p=iMX91_Industrial_Development_Kit/module/software/filesystem

===Download Universal Update Utility (UUU) if needed:===

https://github.com/nxp-imx/mfgtools/releases

Create a new folder e.g. C:\uuu and move all downloaded files into it.

==Flashing uboot and filesystem==
Prepare Voipac baseboard and follow the steps to flash the module as shown on this [[iMX91 Industrial Flashing Procedure|page]].

==Setting a suitable dtb file in bootloader (u-boot)==

Stop autoboot in bootloader:
<syntaxhighlight lang="bash">
U-Boot 2024.04-lf_v2024.04+gde16f4f1722+p0 (Sep 02 2024 - 10:44:35 +0000)

Reset Status: POR

CPU: NXP i.MX93(52) Rev1.1 A55 at 1700 MHz
CPU: Industrial temperature grade (-40C to 105C) at 36C

Model: Voipac i.MX93 EVK board
DRAM: 2 GiB
Core: 219 devices, 31 uclasses, devicetree: separate
MMC: FSL_SDHC: 0, FSL_SDHC: 1
Loading Environment from MMC... OK
[*]-Video Link 0fail to find output device
probe video device failed, ret -19

[0] lcd-controller@4ae30000, video
fail to find output device
probe video device failed, ret -19
In: serial
Out: serial
Err: serial

BuildInfo:
- ELE firmware version 1.2.0-38f309fe

switch to partitions #0, OK
mmc0(part 0) is current device
UID: ad4a5a940e804162a528d6fe1532d4d5
flash target is MMC:0
Net: eth0: ethernet@42890000, eth1: ethernet@428a0000 [PRIME]
Fastboot: Normal
Normal Boot
Hit any key to stop autoboot: 0
u-boot=>
</syntaxhighlight>

Enter command fatls mmc 0:1 (filesystem in eMMC) or fatls mmc 1:1 (filesystem in SD Card) to see a list of DTB files:
<syntaxhighlight lang="bash">
u-boot=> fatls mmc 0:1
35564032 Image
69445 imx93-11x11-evk-aud-hat.dtb
66749 imx93-11x11-evk-boe-wxga-lvds-panel.dtb
65705 imx93-11x11-evk-flexio-i2c.dtb
66009 imx93-11x11-evk-flexspi-m2.dtb
66799 imx93-11x11-evk-i2c-spi-slave.dtb
65062 imx93-11x11-evk-i3c.dtb
2725 imx93-11x11-evk-inmate.dtb
51134 imx93-11x11-evk-iw612-otbr.dtb
65362 imx93-11x11-evk-ld.dtb
65520 imx93-11x11-evk-lpuart.dtb
65983 imx93-11x11-evk-mqs.dtb
68814 imx93-11x11-evk-mt9m114.dtb
65819 imx93-11x11-evk-rm67199.dtb
65573 imx93-11x11-evk-root.dtb
66108 imx93-11x11-evk-rpmsg-lpv.dtb
66132 imx93-11x11-evk-rpmsg.dtb
130428 imx93-11x11-evk_m33_TCM_low_power_wakeword.bin
19080 imx93-11x11-evk_m33_TCM_power_mode_switch.bin
18708 imx93-11x11-evk_m33_TCM_rpmsg_lite_pingpong_rtos_linux_remote.bin
17228 imx93-11x11-evk_m33_TCM_rpmsg_lite_str_echo_rtos.bin
47472 imx93-11x11-evk_m33_TCM_sai_low_power_audio.bin
48794 imx93-voipac-evk-boe-wxga-lvds-panel.dtb
47605 imx93-voipac-evk.dtb
593744 tee.bin

25 file(s), 0 dir(s)

u-boot=>
</syntaxhighlight>

Select the required DTB file and enter the command to set it up:

<syntaxhighlight lang="bash">
u-boot=> setenv fdtfile imx91-voipac-evk.dtb
u-boot=>
</syntaxhighlight>

Save:

<syntaxhighlight lang="bash">
u-boot=> saveenv
Saving Environment to MMC... Writing to MMC(0)... OK
u-boot=>
</syntaxhighlight >

Enter boot command or reset the baseboard for image loading.

iMX91 Industrial Recovery

2025-10-30T10:30:17Z

Voipac-sw: /* Updating U-boot and Filesystem: */

<div style="float:right">__TOC__</div>
=Description=
The recovery procedure consists of following steps:

* Downloading binaries from Voipac download webpage
* Flashing binaries and filesystem over Baseboard USB-C connector
* Setting a suitable dtb file in bootloader (u-boot)
* Resetting and booting a module

==Recommended Software==
* Universal Update Utility (UUU)
* Windows Command Promt
* TFTP Server
* DHCP Server (Otional)

=Configuration=

==Updating Filesystem:==
===Download filesystem:===

https://downloads.voipac.com/index.php?p=iMX93_Industrial_Development_Kit/module/software/filesystem

===Download Universal Update Utility (UUU) if needed:===

https://github.com/nxp-imx/mfgtools/releases

Create a new folder e.g. C:\uuu and move all downloaded files into it.

==Flashing uboot and filesystem==
Prepare Voipac baseboard and follow the steps to flash the module as shown on this [[iMX91 Industrial Flashing Procedure|page]].

==Setting a suitable dtb file in bootloader (u-boot)==

Stop autoboot in bootloader:
<syntaxhighlight lang="bash">
U-Boot 2024.04-lf_v2024.04+gde16f4f1722+p0 (Sep 02 2024 - 10:44:35 +0000)

Reset Status: POR

CPU: NXP i.MX93(52) Rev1.1 A55 at 1700 MHz
CPU: Industrial temperature grade (-40C to 105C) at 36C

Model: Voipac i.MX93 EVK board
DRAM: 2 GiB
Core: 219 devices, 31 uclasses, devicetree: separate
MMC: FSL_SDHC: 0, FSL_SDHC: 1
Loading Environment from MMC... OK
[*]-Video Link 0fail to find output device
probe video device failed, ret -19

[0] lcd-controller@4ae30000, video
fail to find output device
probe video device failed, ret -19
In: serial
Out: serial
Err: serial

BuildInfo:
- ELE firmware version 1.2.0-38f309fe

switch to partitions #0, OK
mmc0(part 0) is current device
UID: ad4a5a940e804162a528d6fe1532d4d5
flash target is MMC:0
Net: eth0: ethernet@42890000, eth1: ethernet@428a0000 [PRIME]
Fastboot: Normal
Normal Boot
Hit any key to stop autoboot: 0
u-boot=>
</syntaxhighlight>

Enter command fatls mmc 0:1 (filesystem in eMMC) or fatls mmc 1:1 (filesystem in SD Card) to see a list of DTB files:
<syntaxhighlight lang="bash">
u-boot=> fatls mmc 0:1
35564032 Image
69445 imx93-11x11-evk-aud-hat.dtb
66749 imx93-11x11-evk-boe-wxga-lvds-panel.dtb
65705 imx93-11x11-evk-flexio-i2c.dtb
66009 imx93-11x11-evk-flexspi-m2.dtb
66799 imx93-11x11-evk-i2c-spi-slave.dtb
65062 imx93-11x11-evk-i3c.dtb
2725 imx93-11x11-evk-inmate.dtb
51134 imx93-11x11-evk-iw612-otbr.dtb
65362 imx93-11x11-evk-ld.dtb
65520 imx93-11x11-evk-lpuart.dtb
65983 imx93-11x11-evk-mqs.dtb
68814 imx93-11x11-evk-mt9m114.dtb
65819 imx93-11x11-evk-rm67199.dtb
65573 imx93-11x11-evk-root.dtb
66108 imx93-11x11-evk-rpmsg-lpv.dtb
66132 imx93-11x11-evk-rpmsg.dtb
130428 imx93-11x11-evk_m33_TCM_low_power_wakeword.bin
19080 imx93-11x11-evk_m33_TCM_power_mode_switch.bin
18708 imx93-11x11-evk_m33_TCM_rpmsg_lite_pingpong_rtos_linux_remote.bin
17228 imx93-11x11-evk_m33_TCM_rpmsg_lite_str_echo_rtos.bin
47472 imx93-11x11-evk_m33_TCM_sai_low_power_audio.bin
48794 imx93-voipac-evk-boe-wxga-lvds-panel.dtb
47605 imx93-voipac-evk.dtb
593744 tee.bin

25 file(s), 0 dir(s)

u-boot=>
</syntaxhighlight>

Select the required DTB file and enter the command to set it up:

<syntaxhighlight lang="bash">
u-boot=> setenv fdtfile imx91-voipac-evk.dtb
u-boot=>
</syntaxhighlight>

Save:

<syntaxhighlight lang="bash">
u-boot=> saveenv
Saving Environment to MMC... Writing to MMC(0)... OK
u-boot=>
</syntaxhighlight >

Enter boot command or reset the baseboard for image loading.

iMX91 Industrial Accessing and Testing Peripherals

2025-10-30T10:28:34Z

Voipac-sw: /* Sleep Mode */

[[Category:iMX91 Industrial]]
[[Category:iMX91 Industrial Software]]
[[Category:iMX91 Industrial Testing]]
[[Category:iMX91 Industrial Peripherals]]

<div style="float:right">__TOC__</div>

The initial operations with the iMX91 Industrial Development Kit interfaces are presented on this page. For more specific information such as display options, camera capabilities or industrial modular extensions, refer to the dedicated [[iMX91 Industrial Max#Peripherals_and_Accessories|Peripherals and Accessories section]].

== Mandatory components ==
=== Hardware ===
* iMX91 Industrial Module
* iMX Development Baseboard
* [https://www.voipac.com/power-supply-5v-20w DC power supply (5V, 4A, 20W)]

=== Peripherals and Accessories ===
* [https://wiki.voipac.com/index.php?title=NXP_Parallel_TFT_Display_Set NXP Parallel TFT Display Set]
* [https://www.voipac.com/imx9-wifi-and-bluetooth-antennas-set iMX9 Wifi and Bluetooth antenna set]
* 1x MicroSDHC card Class 10 or higher
* 1x USB Flash drive 2.0
* Headphones
* Analog external microphone

=== Cables ===
* USB Micro-B cable for serial console
* USB-C cable for module flashing
* Ethernet cable

== Audio ==
'''''Note:''''' This audio section was tested with the iMX91 Industrial Module in Max and Pro configurations. For Basic configuration, audio capabilities are not available. For more information see [[iMX91 Industrial Development Kit|the iMX91 Industrial Module comparison]]. 

'''''Input:''''' Search kernel log for wm8904 chip 
'''''Output:''''' Audio chip is detected and bound as an output and input device
<syntaxhighlight lang="bash">
root@imx91-voipac:~# dmesg | grep wm8904
[ 6.546858] wm8904 0-001a: supply DCVDD not found, using dummy regulator
[ 6.591866] wm8904 0-001a: supply DBVDD not found, using dummy regulator
[ 6.611921] wm8904 0-001a: supply AVDD not found, using dummy regulator
[ 6.637768] wm8904 0-001a: supply CPVDD not found, using dummy regulator
[ 6.670934] wm8904 0-001a: supply MICVDD not found, using dummy regulator
[ 6.683500] wm8904 0-001a: revision A
</syntaxhighlight>

'''''Input:''''' Run amixer command 
'''''Output:''''' Current audio chip settings are displayed
<syntaxhighlight lang="bash">
root@imx91-voipac:~# amixer
Simple mixer control 'Headphone',0
Capabilities: volume pswitch
Playback channels: Front Left - Front Right
Capture channels: Front Left - Front Right
Limits: 0 - 63
Front Left: 45 [71%] [-12.00dB] Playback [on]
Front Right: 45 [71%] [-12.00dB] Playback [on]
Simple mixer control 'Headphone ZC',0
Capabilities: pswitch
Playback channels: Front Left - Front Right
Mono:
Front Left: Playback [on]
Front Right: Playback [on]
Simple mixer control 'Line Output',0
Capabilities: volume pswitch
Playback channels: Front Left - Front Right
Capture channels: Front Left - Front Right
Limits: 0 - 63
Front Left: 57 [90%] [0.00dB] Playback [on]
Front Right: 57 [90%] [0.00dB] Playback [on]
...
</syntaxhighlight>

'''''Input:''''' Connect headphones into LINE OUT jack connector 
'''''Output:''''' Audio file is played and heard
<syntaxhighlight lang="bash">
root@imx8mq-voipac:~# aplay /usr/share/multimedia/sample.wav
Playing WAVE 'multimedia/sample.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
root@imx8mq-voipac:~# aplay -D sysdefault:CARD=wm8904audio /usr/share/multimedia/sample.wav
Playing WAVE 'multimedia/sample.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
</syntaxhighlight>

'''''Input:''''' Plug headphones into HEADPHONES jack connector and analog external microphone to MIC jack connector 
'''''Output:''''' Sound recorder by microphone is played in headphones
<syntaxhighlight lang="bash">
root@imx91-voipac:~# amixer set 'Capture' '31'
root@imx91-voipac:~# amixer set 'Capture Input' ADC
root@imx91-voipac:~# amixer set 'Left Capture Inverting Mux' 'IN2L'
root@imx91-voipac:~# amixer set 'Right Capture Inverting Mux' 'IN2R'
root@imx91-voipac:~# arecord -D sysdefault:CARD=wm8904audio -t wav -f cd | aplay -D sysdefault:CARD=wm8904audio
</syntaxhighlight>

'''''Note:''''' Microphone and headphones setup can also be graphically displayed and adjusted:
<syntaxhighlight lang="bash">
root@imx91-voipac:~# alsamixer
</syntaxhighlight>
[[image:iMX8M_Industrial_Development_Kit-AlsaMixer_setup.png|800px]] 

'''''Input:''''' Verify digital microphones (Mic Left, Mic Mid, Mic Right) 
'''''Output:''''' Microphone sound is played in headphones
<syntaxhighlight lang="bash">
root@imx91-voipac:~# amixer set "Capture Input" "DMIC"
root@imx91-voipac:~# arecord -D sysdefault:CARD=wm8904audio -t wav -f cd | aplay -D sysdefault:CARD=wm8904audio
</syntaxhighlight>

== WiFi ==
'''''Note:''''' This WiFi section was tested with the iMX91 Industrial Module in Max and Pro configurations. For Basic configurations, wireless connectivity is not available. For more information see [[iMX91 Industrial Development Kit|the iMX91 Industrial Module comparison]]. 

Load the device driver:
<syntaxhighlight lang="bash">
root@imx91-voipac:~# modprobe moal mod_para=nxp/wifi_mod_para.conf
[ 926.305344] mlan: loading out-of-tree module taints kernel.
[ 926.334171] wlan: Loading MWLAN driver
[ 926.339152] wlan: Register to Bus Driver...
[ 926.343686] vendor=0x02DF device=0x9159 class=0 function=1
[ 926.349765] Attach moal handle ops, card interface type: 0x108
[ 926.355633] rps set to 0 from module param
[ 926.362045] SDIW416: init module param from usr cfg
[ 926.366995] card_type: SDIW416, config block: 0
[ 926.371541] cfg80211_wext=0xf
[ 926.374515] max_vir_bss=1
[ 926.377131] cal_data_cfg=none
[ 926.380112] ps_mode = 1
[ 926.382567] auto_ds = 1
[ 926.385010] host_mlme=enable
[ 926.387895] fw_name=nxp/sdiouartiw416_combo_v0.bin
[ 926.392709] SDIO: max_segs=128 max_seg_size=65535
[ 926.397420] rx_work=1 cpu_num=2
[ 926.400569] Enable moal_recv_amsdu_packet
[ 926.404600] Attach mlan adapter operations.card_type is 0x108.
[ 926.410826] wlan: Enable TX SG mode
[ 926.414357] wlan: Enable RX SG mode
[ 926.421681] Request firmware: nxp/sdiouartiw416_combo_v0.bin
[ 926.708639] Wlan: FW download over, firmwarelen=591808 downloaded 583072
[ 928.113594] WLAN FW is active
[ 928.116573] on_time is 927947046442
[ 928.140994] VDLL image: len=8736
[ 928.144352] FW country code WW does not match with US
[ 928.150617] fw_cap_info=0x187ccf03, dev_cap_mask=0xffffffff
[ 928.156607] max_p2p_conn = 8, max_sta_conn = 8
[ 928.176236] Register NXP 802.11 Adapter mlan0
[ 928.183724] Register NXP 802.11 Adapter uap0
[ 928.194033] Register NXP 802.11 Adapter wfd0
[ 928.199986] wlan: version = SDIW416---16.92.21.p137.2-MM6X16437.p30-GPL-(FP92)
[ 928.208947] wlan: Register to Bus Driver Done
[ 928.216412] wlan: Driver loaded successfully
</syntaxhighlight>

Check if the WiFi interface is present:
<syntaxhighlight lang="bash">
root@imx91-voipac:~# ip addr show dev mlan0
3: wlp1s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 78:c4:0e:a0:32:16 brd ff:ff:ff:ff:ff:ff
</syntaxhighlight>

'''''Input:''''' Scan the available WiFi networks 
'''''Output:''''' Networks are scanned and in-depth information are displayed 
<syntaxhighlight lang="bash">
root@imx91-voipac:~# ifconfig mlan0 up && iw dev mlan0 scan
BSS 94:27:90:7f:c3:d3(on wlp1s0)
TSF: 1213185029341 usec (14d, 00:59:45)
freq: 2442
beacon interval: 100 TUs
capability: ESS Privacy ShortPreamble ShortSlotTime (0x0431)
signal: -73.00 dBm
last seen: 4056 ms ago
SSID: HH40V_C3D3
Supported rates: 1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0
DS Parameter set: channel 7
Country: SK Environment: Indoor/Outdoor
Channels [1 - 13] @ 20 dBm
ERP: <no flags>
Extended supported rates: 24.0 36.0 48.0 54.0
HT capabilities:
Capabilities: 0x1ad
RX LDPC
HT20
SM Power Save disabled
RX HT20 SGI
TX STBC
RX STBC 1-stream
Max AMSDU length: 3839 bytes
No DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 8 usec (0x06)
HT TX/RX MCS rate indexes supported: 0-15
HT operation:
* primary channel: 7
* secondary channel offset: no secondary
* STA channel width: 20 MHz
* RIFS: 1
* HT protection: no
* non-GF present: 1
* OBSS non-GF present: 0
* dual beacon: 0
* dual CTS protection: 0
* STBC beacon: 0
* L-SIG TXOP Prot: 0
* PCO active: 0
* PCO phase: 0
Overlapping BSS scan params:
* passive dwell: 20 TUs
* active dwell: 10 TUs
* channel width trigger scan interval: 300 s
* scan passive total per channel: 200 TUs
* scan active total per channel: 20 TUs
* BSS width channel transition delay factor: 5
* OBSS Scan Activity Threshold: 0.25 %
Extended capabilities:
* HT Information Exchange Supported
* Extended Channel Switching
* SSID List
* Operating Mode Notification
WMM: * Parameter version 1
* BE: CW 15-1023, AIFSN 3
* BK: CW 15-1023, AIFSN 7
* VI: CW 7-15, AIFSN 2, TXOP 3008 usec
* VO: CW 3-7, AIFSN 2, TXOP 1504 usec
RSN: * Version: 1
* Group cipher: CCMP
* Pairwise ciphers: CCMP
* Authentication suites: PSK
* Capabilities: 1-PTKSA-RC 1-GTKSA-RC (0x0000)
WPS: * Version: 1.0
* Wi-Fi Protected Setup State: 2 (Configured)
* Response Type: 3 (AP)
* UUID: 87654321-9abc-def0-1234-942790c36dc7
* Manufacturer: TCL.org
* Model: WAP
* Model Number: 123
* Serial Number: 12345
* Primary Device Type: 6-0050f204-1
* Device name: TCL AP
* Config methods:
* Unknown TLV (0x1049, 6 bytes): 00 37 2a 00 01 20
BSS 34:e8:94:5c:06:80(on wlp1s0)
TSF: 787677017722 usec (9d, 02:47:57)
freq: 2462
beacon interval: 100 TUs
capability: ESS Privacy ShortSlotTime (0x0411)
signal: -73.00 dBm
last seen: 3952 ms ago
SSID: OrangeFlybox_0680
Supported rates: 1.0* 2.0* 5.5* 11.0* 9.0 18.0 36.0 54.0
DS Parameter set: channel 11
ERP: Barker_Preamble_Mode
Extended supported rates: 6.0 12.0 24.0 48.0
HT capabilities:
Capabilities: 0x106e
HT20/HT40
SM Power Save disabled
RX HT20 SGI
RX HT40 SGI
No RX STBC
Max AMSDU length: 3839 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 4 usec (0x05)
HT RX MCS rate indexes supported: 0-15, 32
HT TX MCS rate indexes are undefined
HT operation:
* primary channel: 11
* secondary channel offset: no secondary
* STA channel width: 20 MHz
* RIFS: 0
* HT protection: 20 MHz
* non-GF present: 1
* OBSS non-GF present: 0
* dual beacon: 0
* dual CTS protection: 0
* STBC beacon: 0
* L-SIG TXOP Prot: 0
* PCO active: 0
* PCO phase: 0
WPA: * Version: 1
* Group cipher: TKIP
* Pairwise ciphers: TKIP CCMP
* Authentication suites: PSK
RSN: * Version: 1
* Group cipher: TKIP
* Pairwise ciphers: TKIP CCMP
* Authentication suites: PSK
* Capabilities: 1-PTKSA-RC 1-GTKSA-RC (0x0000)
WMM: * Parameter version 1
* BE: CW 15-1023, AIFSN 3
* BK: CW 15-1023, AIFSN 7
* VI: CW 7-15, AIFSN 2, TXOP 3008 usec
* VO: CW 3-7, AIFSN 2, TXOP 1504 usec
BSS Load:
* station count: 3
* channel utilisation: 27/255
* available admission capacity: 31250 [*32us]
Overlapping BSS scan params:
* passive dwell: 20 TUs
* active dwell: 10 TUs
* channel width trigger scan interval: 300 s
* scan passive total per channel: 200 TUs
* scan active total per channel: 20 TUs
* BSS width channel transition delay factor: 5
* OBSS Scan Activity Threshold: 0.25 %
Extended capabilities:
* HT Information Exchange Supported
WPS: * Version: 1.0
* Wi-Fi Protected Setup State: 2 (Configured)
* AP setup locked: 0x01
* Response Type: 3 (AP)
* UUID: 38833092-3092-1883-9c77-34e8945c06c4
* Manufacturer: TP-LINK
* Model: Archer MR200
* Model Number: 1.0
* Serial Number: 1.0
* Primary Device Type: 6-0050f204-1
* Device name: AC750 Wireless Dual Band 4G LTE
* Config methods: Label, Display, Keypad
* RF Bands: 0x1
* Unknown TLV (0x1049, 6 bytes): 00 37 2a 00 01 20
BSS 34:e8:94:5b:f8:04(on wlp1s0)
TSF: 1210179077454 usec (14d, 00:09:39)
freq: 2462
beacon interval: 100 TUs
capability: ESS Privacy ShortSlotTime (0x0411)
signal: -50.00 dBm
last seen: 3432 ms ago
SSID: REDARROW
Supported rates: 1.0* 2.0* 5.5* 11.0* 9.0 18.0 36.0 54.0
DS Parameter set: channel 11
Extended supported rates: 6.0 12.0 24.0 48.0
TIM: DTIM Count 0 DTIM Period 1 Bitmap Control 0x0 Bitmap[0] 0x2
WPS: * Version: 1.0
* Wi-Fi Protected Setup State: 2 (Configured)
* AP setup locked: 0x01
* UUID: 38833092-3092-1883-9c77-34e8945bf8c4
* RF Bands: 0x1
* Unknown TLV (0x1049, 6 bytes): 00 37 2a 00 01 20
ERP: Barker_Preamble_Mode
HT capabilities:
Capabilities: 0x106e
HT20/HT40
SM Power Save disabled
RX HT20 SGI
RX HT40 SGI
No RX STBC
Max AMSDU length: 3839 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 4 usec (0x05)
HT RX MCS rate indexes supported: 0-15, 32
HT TX MCS rate indexes are undefined
HT operation:
* primary channel: 11
* secondary channel offset: no secondary
* STA channel width: 20 MHz
* RIFS: 0
* HT protection: no
* non-GF present: 0
* OBSS non-GF present: 0
* dual beacon: 0
* dual CTS protection: 0
* STBC beacon: 0
* L-SIG TXOP Prot: 0
* PCO active: 0
* PCO phase: 0
Overlapping BSS scan params:
* passive dwell: 20 TUs
* active dwell: 10 TUs
* channel width trigger scan interval: 300 s
* scan passive total per channel: 200 TUs
* scan active total per channel: 20 TUs
* BSS width channel transition delay factor: 5
* OBSS Scan Activity Threshold: 0.25 %
Extended capabilities:
* HT Information Exchange Supported
WPA: * Version: 1
* Group cipher: TKIP
* Pairwise ciphers: TKIP CCMP
* Authentication suites: PSK
RSN: * Version: 1
* Group cipher: TKIP
* Pairwise ciphers: TKIP CCMP
* Authentication suites: PSK
* Capabilities: 1-PTKSA-RC 1-GTKSA-RC (0x0000)
WMM: * Parameter version 1
* BE: CW 15-1023, AIFSN 3
* BK: CW 15-1023, AIFSN 7
* VI: CW 7-15, AIFSN 2, TXOP 3008 usec
* VO: CW 3-7, AIFSN 2, TXOP 1504 usec
BSS Load:
* station count: 0
* channel utilisation: 47/255
* available admission capacity: 31250 [*32us]
</syntaxhighlight>

To set up the network login data, edit file located in /etc/wpa_supplicant.conf and update '''''ssid''''' and passphrase '''''psk''''' fields.

<syntaxhighlight lang="bash">
root@imx91-voipac:~# cat /etc/wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
update_config=1

network={
ssid="SSID_FOR_WIFI_NETWORK"
scan_ssid=1
key_mgmt=WPA-PSK
psk="WIFI_NETWORK_PASSWORD"
}

</syntaxhighlight>

To connect to the desired WiFi network, start wpa_supplicant:
<syntaxhighlight lang="bash">
root@imx91-voipac:~# wpa_supplicant -D nl80211 -i mlan0 -c /etc/wpa_supplicant.conf &
root@imx91-voipac:~# rfkill: Cannot open RFKILL control device
[ 261.722718] wlan: mlan0 START SCAN
[ 266.018892] wlan: SCAN COMPLETED: scanned AP count=1
mlan0: SME: Trying to authentica[ 266.027303] wlan: HostMlme mlan0 send auth to bssid 40:XX:XX:XX:70:62
te with 40:a5:ef:c0:70:62 (SSID='WifiPoschodie' f[ 266.037546] mlan0:
req=2437 MHz)
[ 266.037558] wlan: HostMlme Auth received from 40:XX:XX:XX:70:62
mlan0: Trying to associate with 40:a5:ef:c0:70:62 (SSID='WifiPoschodie' freq=2437 MHz)
[ 266.057956] wlan: HostMlme mlan0 Connected to bssid 40:XX:XX:XX:70:62 successfully
mlan0: Associated[ 266.067323] mlan0:
with 40:a5:ef:c0[ 266.067340] wlan: Send EAPOL pkt to 40:XX:XX:XX:70:62
</syntaxhighlight>

To obtain an IP address and other network settings, run dhcp client:
<syntaxhighlight lang="bash">
udhcpc -i mlan0
</syntaxhighlight>

At this point the bandwidth measurement can be tested, showing that WiFi connection was established and is performed very reliably.
Used program: [https://iperf.fr iPerf3.] 

'''''Configuration:''''' iMX91 Industrial Module Pro in Industrial temperature range (u-blox MAYA-W160-00B assembled):
<syntaxhighlight lang="bash">
root@imx91-voipac:~# iperf3 -c 192.168.240.200 -t 30 -i1
Connecting to host 192.168.240.200, port 5201
[ 5] local 192.168.240.111 port 39988 connected to 192.168.240.200 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 5.12 MBytes 43.0 Mbits/sec 0 223 KBytes
[ 5] 1.00-2.00 sec 5.38 MBytes 45.1 Mbits/sec 0 460 KBytes
[ 5] 2.00-3.00 sec 7.12 MBytes 59.8 Mbits/sec 0 747 KBytes
[ 5] 3.00-4.00 sec 4.25 MBytes 35.7 Mbits/sec 0 1003 KBytes
[ 5] 4.00-5.00 sec 5.38 MBytes 45.1 Mbits/sec 0 1.25 MBytes
[ 5] 5.00-6.00 sec 5.50 MBytes 46.1 Mbits/sec 0 1.52 MBytes
[ 5] 6.00-7.00 sec 5.50 MBytes 46.1 Mbits/sec 0 1.78 MBytes
[ 5] 7.00-8.00 sec 5.62 MBytes 47.2 Mbits/sec 0 2.06 MBytes
[ 5] 8.00-9.00 sec 5.50 MBytes 46.1 Mbits/sec 0 2.31 MBytes
[ 5] 9.00-10.00 sec 5.50 MBytes 46.1 Mbits/sec 0 2.64 MBytes
[ 5] 10.00-11.00 sec 6.75 MBytes 56.6 Mbits/sec 0 2.93 MBytes
[ 5] 11.00-12.00 sec 3.00 MBytes 25.2 Mbits/sec 0 3.10 MBytes
[ 5] 12.00-13.00 sec 6.75 MBytes 56.6 Mbits/sec 0 3.41 MBytes
[ 5] 13.00-14.00 sec 5.75 MBytes 48.2 Mbits/sec 0 3.61 MBytes
[ 5] 14.00-15.00 sec 4.25 MBytes 35.7 Mbits/sec 0 3.81 MBytes
[ 5] 15.00-16.00 sec 5.75 MBytes 48.2 Mbits/sec 0 3.81 MBytes
[ 5] 16.00-17.00 sec 4.38 MBytes 36.7 Mbits/sec 0 4.07 MBytes
[ 5] 17.00-18.00 sec 5.88 MBytes 49.3 Mbits/sec 0 4.07 MBytes
[ 5] 18.00-19.00 sec 2.75 MBytes 23.1 Mbits/sec 0 4.07 MBytes
[ 5] 19.00-20.00 sec 3.38 MBytes 28.3 Mbits/sec 3 2.86 MBytes
[ 5] 20.00-21.00 sec 2.88 MBytes 24.1 Mbits/sec 0 2.94 MBytes
[ 5] 21.00-22.00 sec 1.25 MBytes 10.5 Mbits/sec 0 3.10 MBytes
[ 5] 22.00-23.00 sec 5.50 MBytes 46.1 Mbits/sec 0 3.44 MBytes
[ 5] 23.00-24.00 sec 5.50 MBytes 46.1 Mbits/sec 0 3.63 MBytes
[ 5] 24.00-25.00 sec 4.50 MBytes 37.7 Mbits/sec 0 3.64 MBytes
[ 5] 25.00-26.00 sec 4.25 MBytes 35.7 Mbits/sec 0 3.64 MBytes
[ 5] 26.00-27.00 sec 5.62 MBytes 47.2 Mbits/sec 0 3.86 MBytes
[ 5] 27.00-28.00 sec 6.62 MBytes 55.6 Mbits/sec 0 3.86 MBytes
[ 5] 28.00-29.00 sec 5.50 MBytes 46.1 Mbits/sec 0 3.86 MBytes
[ 5] 29.00-30.00 sec 4.88 MBytes 40.8 Mbits/sec 0 3.86 MBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-30.00 sec 150 MBytes 41.9 Mbits/sec 3 sender
[ 5] 0.00-30.32 sec 150 MBytes 41.5 Mbits/sec receiver

iperf Done.
</syntaxhighlight>

== Bluetooth ==
'''''Note:''''' This Bluetooth section was tested with the iMX91 Industrial Module in Max and Pro configurations. For Basic configuration, bluetooth capabilities are not available. For more information see [[iMX91 Industrial Development Kit|the iMX91 Industrial Module comparison]]. 

'''''Input:''''' None 
'''''Output:''''' Remote device is recognized after scan 

'''''Note:''''' For iMX91 Industrial Module Max (u-blox MAYA-W260-00B assembled) please use instead of <syntaxhighlight lang="bash">hciattach /dev/ttyLP7 any 3000000 flow</syntaxhighlight> command <syntaxhighlight lang="bash">hciattach /dev/ttyLP7 any 115200 flow</syntaxhighlight> in below code
<syntaxhighlight lang="bash">
# attach necessary modules
root@imx91-voipac:~# modprobe moal mod_para=nxp/wifi_mod_para.conf
root@imx91-voipac:~# modprobe hci_uart
root@imx91-voipac:~# hciattach /dev/ttyLP7 any 3000000 flow
Device setup complete
root@imx91-voipac:~# [ 1207.472299] Bluetooth: MGMT ver 1.22
[ 1207.485171] NET: Registered PF_ALG protocol family

# put hci0 device up
root@imx91-voipac:~# hciconfig hci0 up

# scan for remote bluetooth devices (enable bluetooth on phone and make it discoverable)
root@imx91-voipac:~# hcitool scan
Scanning ...
Devices:
hci0 00:0D:18:01:5A:B3
</syntaxhighlight>

== Ethernet ==
'''''Note:''''' This section was tested with the iMX91 Industrial Module in Max configuration which includes dual Gigabit Ethernet PHY. The Pro configuration includes single Gigabit Ethernet PHY. For the Basic configuration, Ethernet capabilities are not available. For more information see [[iMX91 Industrial Development Kit|the iMX91 Industrial Module comparison]]. 

'''''Input:''''' None 
'''''Output:''''' Device driver is available (for Pro configuration only one ethernet is available) 
'''''Note:''''' MAC address should be identical with the address on the sticker placed on the board
<syntaxhighlight lang="bash">

root@imx91-voipac:~# ip addr show dev eth0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:0d:15:01:8c:ae brd ff:ff:ff:ff:ff:ff
inet 192.168.1.33/24 metric 10 brd 192.168.1.255 scope global dynamic eth0
valid_lft 86378sec preferred_lft 86378sec
inet6 fe80::20d:15ff:fe01:8cae/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
root@imx91-voipac:~# ip addr show dev eth1
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:0d:15:01:8c:af brd ff:ff:ff:ff:ff:ff
inet 192.168.1.34/24 metric 10 brd 192.168.1.255 scope global dynamic eth1
valid_lft 86391sec preferred_lft 86391sec
inet6 fe80::20d:15ff:fe01:8caf/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
root@imx91-voipac:~#
</syntaxhighlight>

'''''Input:''''' Plug Ethernet cable into top or bottom connector for the Max configuration. Plug Ethernet cable into bottom connector for the Pro configuration. 
'''''Output:''''' IPv4 address is assigned
<syntaxhighlight lang="bash">
[ 1599.750399] fec 42890000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[ 1630.695671] imx-dwmac 428a0000.ethernet eth1: Link is Up - 1Gbps/Full - flow control off
</syntaxhighlight>

=== Performance ===
iPerf3 was used to test the Ethernet performance. 
'''''Note:''''' The Max configuration of the iMX91 Industrial Module includes dual Gigabit Ethernet PHY. The Pro configuration includes single Gigabit Ethernet PHY. 
'''''Input:''''' Start iPerf3 on computer using command <syntaxhighlight lang="bash">iperf3 -s </syntaxhighlight>
'''''Output:''''' Verify performance on board (argument after -c is IP address of your computer) 

<syntaxhighlight lang="bash">
root@imx91-voipac:~# iperf3 -c 192.168.240.120 -t 10 -i 1
Connecting to host 192.168.240.120, port 5201
[ 5] local 192.168.240.32 port 57734 connected to 192.168.240.120 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 114 MBytes 951 Mbits/sec 0 358 KBytes
[ 5] 1.00-2.00 sec 112 MBytes 943 Mbits/sec 0 358 KBytes
[ 5] 2.00-3.00 sec 112 MBytes 938 Mbits/sec 0 358 KBytes
[ 5] 3.00-4.00 sec 113 MBytes 947 Mbits/sec 0 393 KBytes
[ 5] 4.00-5.00 sec 112 MBytes 941 Mbits/sec 0 393 KBytes
[ 5] 5.00-6.00 sec 112 MBytes 944 Mbits/sec 0 393 KBytes
[ 5] 6.00-7.00 sec 112 MBytes 940 Mbits/sec 0 516 KBytes
[ 5] 7.00-8.00 sec 112 MBytes 943 Mbits/sec 0 516 KBytes
[ 5] 8.00-9.00 sec 112 MBytes 942 Mbits/sec 0 516 KBytes
[ 5] 9.00-10.00 sec 113 MBytes 946 Mbits/sec 0 516 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 1.10 GBytes 943 Mbits/sec 0 sender
[ 5] 0.00-10.05 sec 1.10 GBytes 937 Mbits/sec receiver

iperf Done.
root@imx91-voipac:~#

</syntaxhighlight>

== USB 2.0 ==
NOTE: Perform read/write performance test 
'''''Input:''''' Plug USB flash drive into USB connector 
'''''Output:''''' Plugged USB device is listed
<syntaxhighlight lang="bash">
root@imx91-voipac:~# lsusb
Bus 001 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 125f:d31a A-DATA Technology Co., Ltd.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
</syntaxhighlight>

'''''Input:''''' Generate a dummy file and copy it into USB flash drive 
'''''Output:''''' Generated file and copied file have the same checksum
<syntaxhighlight lang="bash">
root@imx91-voipac:~# mount /dev/sda1 /media/
root@imx91-voipac:~# rm -f file.txt /media/file.txt
root@imx91-voipac:~# dd if=/dev/urandom of=file.txt count=1024 bs=1024
1024+0 records in
1024+0 records out
root@imx91-voipac:~# cp file.txt /media/
root@imx91-voipac:~# md5sum file.txt /media/file.txt
200a9fd3e9850fcedf85ed50d4c4733d file.txt
200a9fd3e9850fcedf85ed50d4c4733d /media/file.txt
root@imx91-voipac:~# rm file.txt /media/file.txt
root@imx91-voipac:~# umount /media
</syntaxhighlight>

== USB-C ==
This connector is primarily used for flashing new binaries into the iMX91 Industrial Module. More information can be found on the dedicated [[iMX91 Industrial Flashing Procedure|module flashing page]]. 

== USB Micro-B serial console ==
'''''Input:''''' Connect USB console cable into the base board connector and open serial console with baud rate 115200 8n1 
'''''Output:''''' The board is controlled and responsive to serial terminal commands
<syntaxhighlight lang="bash">
root@imx91-voipac:~# uname -a
Linux imx91-voipac 6.6.36-lts-next-g2e3e2e65d92a #1 SMP PREEMPT Wed Sep 4 08:22:45 UTC 2024 aarch64 GNU/Linux
</syntaxhighlight>

== UART serial console ==
Serial console is utilized via USB Micro-B connector by default. Alternatively, the communication can be established using UART headers and TTL-232R-3V3 - FTDI cable. 
NOTE: Describe jumpers position 
[[File:iMX91 Industrial Development Kit-Serial console via UART1.png|800px]] 

'''''Note:''''' Usage of UART2 CONSOLE to communicate by default requires changes in Yocto binaries and new compilation of image files. 
[[File:iMX91 Industrial Development Kit-Serial console via UART2.png|800px]]

== SD Card ==
NOTE: Perform detection of SD Card
<syntaxhighlight lang="bash">
root@imx91-voipac:~# fdisk -l
Disk /dev/mmcblk0: 15 GB, 15758000128 bytes, 30777344 sectors
240448 cylinders, 4 heads, 32 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type
/dev/mmcblk0p1 * 128,0,1 1023,3,32 16384 186775 170392 83.1M c Win95 FAT32 (LBA)
/dev/mmcblk0p2 1023,3,32 1023,3,32 196608 939761 743154 362M 83 Linux
Disk /dev/mmcblk0boot0: 4 MB, 4194304 bytes, 8192 sectors
128 cylinders, 4 heads, 16 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Disk /dev/mmcblk0boot1: 4 MB, 4194304 bytes, 8192 sectors
128 cylinders, 4 heads, 16 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Disk /dev/mmcblk1: 15 GB, 15931539456 bytes, 31116288 sectors
243096 cylinders, 4 heads, 32 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type
/dev/mmcblk1p1 512,0,1 1023,3,32 65536 266255 200720 98.0M 83 Linux
</syntaxhighlight>

/dev/mmcblk1 is SD card (mmcblk0 is eMMC)

== JTAG ==
[[File:iMX91 Industrial Development Kit-JTAG communication setup.png|800px]] 
To verify that i.MX93 CPU JTAG is functional, following command identifies and connects to the CPU's debug point:
<syntaxhighlight lang="bash">
J-Link> jtagid
</syntaxhighlight>

[[File:J-Link MIMX9352 A55 1.png|800px]] 
[[File:J-Link MIMX9352 M33.png|800px]]

== Real Time Clock ==
RTC chip is detected by Linux kernel after start-up:
<syntaxhighlight lang="bash">
root@imx91-voipac:~# dmesg | grep rtc
[ 0.894414] imx-drm display-subsystem: bound imx-lcdifv3-crtc.0 (ops lcdifv3_crtc_ops)
[ 0.910506] imx-drm display-subsystem: [drm] Cannot find any crtc or sizes
[ 1.209418] bbnsm_rtc 44440000.bbnsm:rtc: registered as rtc0
[ 1.215749] bbnsm_rtc 44440000.bbnsm:rtc: setting system clock to 1970-01-01T00:00:00 UTC (0)
root@imx91-voipac:~#
</syntaxhighlight>

CPU correctly recognises RTC on the I2C1 bus, the chip is under usage by the kernel:
<syntaxhighlight lang="bash">
root@imx91-voipac:~# i2cdetect -r -y 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- UU -- -- -- UU -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- 3d -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- UU -- UU -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
</syntaxhighlight>

Set up the current date and time, show the actual values

Setup date and time
<syntaxhighlight lang="bash">
date -s "2025-8-13 14:52:26"
</syntaxhighlight>

Show actual values
<syntaxhighlight lang="bash">
root@imx91-voipac:~# timedatectl
[ 134.509782] kauditd_printk_skb: 8 callbacks suppressed
[ 134.509793] audit: type=1334 audit(1732625725.140:18): prog-id=19 op=LOAD
[ 134.523935] audit: type=1334 audit(1732625725.148:19): prog-id=20 op=LOAD
[ 134.531609] audit: type=1334 audit(1732625725.152:20): prog-id=21 op=LOAD
Local time: Tue 2024-11-26 12:55:25 UTC
Universal time: Tue 2024-11-26 12:55:25 UTC
RTC time: Tue 2024-11-26 12:55:25
Time zone: UTC (UTC, +0000)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no
</syntaxhighlight>

== I2C EEPROM Memory - on module ==
'''''Input:''''' Power on board 
'''''Output:''''' Store some data to eeprom and after reboot read it back and should be same 

<syntaxhighlight lang="bash">
# store random 8bytes to eeprom
root@imx91-voipac-evk:~# dd if=/dev/urandom of=/sys/bus/i2c/devices/0-0050/eeprom bs=8 count=1
+1 records in
0+1 records out
8 bytes copied, 0.0225523 s, 0.4 kB/s
</syntaxhighlight>

After board reboot:
<syntaxhighlight lang="bash">
# store random 8bytes to eeprom
root@imx91-voipac-evk:~# hexdump -n8 /sys/bus/i2c/devices/0-0050/eeprom
0000000 c4dd 4eda d624 535e
0000008
</syntaxhighlight>

== Reset button ==
'''''Input:''''' Press the RESET button 
'''''Output:''''' The board will execute bootloader immediately with "Reset cause: POR" 
'''''Note:''''' iMX91 Industrial Development Kit should never freeze or hang after the reset button was pressed. Testing the operation 10 times gives a reliable result
<syntaxhighlight lang="bash">
U-Boot 2023.04+gf8a2983ec8+p0 (Mar 04 2024 - 07:25:04 +0000)

CPU: i.MX93(52) rev1.1 1700 MHz (running at 1692 MHz)
CPU: Industrial temperature grade (-40C to 105C) at 45C
Reset cause: POR (0x1)
Model: NXP i.MX93 Voipac EVK board
DRAM: 2 GiB
Core: 215 devices, 32 uclasses, devicetree: separate
MMC: FSL_SDHC: 0, FSL_SDHC: 1
Loading Environment from MMC... OK
[*]-Video Link 0fail to find output device

....
</syntaxhighlight>

== On/Off button ==
'''''Input:''''' Press and hold On/Off button for more then 5 seconds 
'''''Output:''''' The board will be powered off

Press shortly the On/Off button again, the board will be powered on.

== Sleep Mode ==
'''''Input:''''' Type command:
<syntaxhighlight lang="bash">
echo mem > /sys/power/state
</syntaxhighlight>

'''''Output:''''' The board will go into a frozen state and the serial console will not respond to inputs.

Shortly press the Up user button, to wake the board up again.

[[File:imx91_sleep_mode.png|740px]] 

== User buttons ==
'''''Input:''''' Press Enter/Left/Right/Up/Down buttons 
'''''Output:''''' Button events 1 and 0 are generated
<syntaxhighlight lang="bash">
root@imx91-voipac-evk:~# evtest /dev/input/by-path/platform-gpio-buttons-event
Input driver version is 1.0.1
Input device ID: bus 0x19 vendor 0x1 product 0x1 version 0x100
Input device name: "gpio-buttons"
Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
Event code 28 (KEY_ENTER)
Event code 103 (KEY_UP)
Event code 105 (KEY_LEFT)
Event code 106 (KEY_RIGHT)
Event code 108 (KEY_DOWN)
Properties:
Testing ... (interrupt to exit)
Event: time 1717485486.586413, type 1 (EV_KEY), code 103 (KEY_UP), value 1
Event: time 1717485486.586413, -------------- SYN_REPORT ------------
Event: time 1717485486.682265, type 1 (EV_KEY), code 103 (KEY_UP), value 0
Event: time 1717485486.682265, -------------- SYN_REPORT ------------
Event: time 1717485487.255120, type 1 (EV_KEY), code 108 (KEY_DOWN), value 1
Event: time 1717485487.255120, -------------- SYN_REPORT ------------
Event: time 1717485487.367126, type 1 (EV_KEY), code 108 (KEY_DOWN), value 0
Event: time 1717485487.367126, -------------- SYN_REPORT ------------
Event: time 1717485488.539564, type 1 (EV_KEY), code 106 (KEY_RIGHT), value 1
Event: time 1717485488.539564, -------------- SYN_REPORT ------------
Event: time 1717485488.677501, type 1 (EV_KEY), code 106 (KEY_RIGHT), value 0
Event: time 1717485488.677501, -------------- SYN_REPORT ------------
Event: time 1717485488.897627, type 1 (EV_KEY), code 105 (KEY_LEFT), value 1
Event: time 1717485488.897627, -------------- SYN_REPORT ------------
Event: time 1717485489.013136, type 1 (EV_KEY), code 105 (KEY_LEFT), value 0
Event: time 1717485489.013136, -------------- SYN_REPORT ------------
Event: time 1717485489.264589, type 1 (EV_KEY), code 28 (KEY_ENTER), value 1
Event: time 1717485489.264589, -------------- SYN_REPORT ------------
Event: time 1717485489.372584, type 1 (EV_KEY), code 28 (KEY_ENTER), value 0
Event: time 1717485489.372584, -------------- SYN_REPORT ------------
</syntaxhighlight>

== User LED ==
'''''Input:''''' None 
'''''Output:''''' Script switches User LED on baseboard ON and OFF in one second intervals
<syntaxhighlight lang="bash">
#!/bin/sh

LED=/sys/class/leds/user_sbc

while true; do
echo 0 > ${LED}/brightness
sleep 1
echo 1 > ${LED}/brightness
sleep 1
done
</syntaxhighlight>

'''''Input:''''' None 
'''''Output:''''' User LED on baseboard is set to heartbeat blinking sequence
<syntaxhighlight lang="bash">
root@imx91-voipac-evk:~# echo heartbeat > /sys/class/leds/user_sbc/trigger
</syntaxhighlight>

'''''Input:''''' None 
'''''Output:''''' User LED on SOM is set to heartbeat blinking sequence
<syntaxhighlight lang="bash">
root@imx91-voipac-evk:~# echo heartbeat > /sys/class/leds/user_som/trigger
</syntaxhighlight>

File:imx91 sleep mode.png

2025-10-30T10:28:25Z

Voipac-sw:

iMX91 Industrial Accessing and Testing Peripherals

2025-10-30T10:27:59Z

Voipac-sw: /* JTAG */

[[Category:iMX91 Industrial]]
[[Category:iMX91 Industrial Software]]
[[Category:iMX91 Industrial Testing]]
[[Category:iMX91 Industrial Peripherals]]

<div style="float:right">__TOC__</div>

The initial operations with the iMX91 Industrial Development Kit interfaces are presented on this page. For more specific information such as display options, camera capabilities or industrial modular extensions, refer to the dedicated [[iMX91 Industrial Max#Peripherals_and_Accessories|Peripherals and Accessories section]].

== Mandatory components ==
=== Hardware ===
* iMX91 Industrial Module
* iMX Development Baseboard
* [https://www.voipac.com/power-supply-5v-20w DC power supply (5V, 4A, 20W)]

=== Peripherals and Accessories ===
* [https://wiki.voipac.com/index.php?title=NXP_Parallel_TFT_Display_Set NXP Parallel TFT Display Set]
* [https://www.voipac.com/imx9-wifi-and-bluetooth-antennas-set iMX9 Wifi and Bluetooth antenna set]
* 1x MicroSDHC card Class 10 or higher
* 1x USB Flash drive 2.0
* Headphones
* Analog external microphone

=== Cables ===
* USB Micro-B cable for serial console
* USB-C cable for module flashing
* Ethernet cable

== Audio ==
'''''Note:''''' This audio section was tested with the iMX91 Industrial Module in Max and Pro configurations. For Basic configuration, audio capabilities are not available. For more information see [[iMX91 Industrial Development Kit|the iMX91 Industrial Module comparison]]. 

'''''Input:''''' Search kernel log for wm8904 chip 
'''''Output:''''' Audio chip is detected and bound as an output and input device
<syntaxhighlight lang="bash">
root@imx91-voipac:~# dmesg | grep wm8904
[ 6.546858] wm8904 0-001a: supply DCVDD not found, using dummy regulator
[ 6.591866] wm8904 0-001a: supply DBVDD not found, using dummy regulator
[ 6.611921] wm8904 0-001a: supply AVDD not found, using dummy regulator
[ 6.637768] wm8904 0-001a: supply CPVDD not found, using dummy regulator
[ 6.670934] wm8904 0-001a: supply MICVDD not found, using dummy regulator
[ 6.683500] wm8904 0-001a: revision A
</syntaxhighlight>

'''''Input:''''' Run amixer command 
'''''Output:''''' Current audio chip settings are displayed
<syntaxhighlight lang="bash">
root@imx91-voipac:~# amixer
Simple mixer control 'Headphone',0
Capabilities: volume pswitch
Playback channels: Front Left - Front Right
Capture channels: Front Left - Front Right
Limits: 0 - 63
Front Left: 45 [71%] [-12.00dB] Playback [on]
Front Right: 45 [71%] [-12.00dB] Playback [on]
Simple mixer control 'Headphone ZC',0
Capabilities: pswitch
Playback channels: Front Left - Front Right
Mono:
Front Left: Playback [on]
Front Right: Playback [on]
Simple mixer control 'Line Output',0
Capabilities: volume pswitch
Playback channels: Front Left - Front Right
Capture channels: Front Left - Front Right
Limits: 0 - 63
Front Left: 57 [90%] [0.00dB] Playback [on]
Front Right: 57 [90%] [0.00dB] Playback [on]
...
</syntaxhighlight>

'''''Input:''''' Connect headphones into LINE OUT jack connector 
'''''Output:''''' Audio file is played and heard
<syntaxhighlight lang="bash">
root@imx8mq-voipac:~# aplay /usr/share/multimedia/sample.wav
Playing WAVE 'multimedia/sample.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
root@imx8mq-voipac:~# aplay -D sysdefault:CARD=wm8904audio /usr/share/multimedia/sample.wav
Playing WAVE 'multimedia/sample.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
</syntaxhighlight>

'''''Input:''''' Plug headphones into HEADPHONES jack connector and analog external microphone to MIC jack connector 
'''''Output:''''' Sound recorder by microphone is played in headphones
<syntaxhighlight lang="bash">
root@imx91-voipac:~# amixer set 'Capture' '31'
root@imx91-voipac:~# amixer set 'Capture Input' ADC
root@imx91-voipac:~# amixer set 'Left Capture Inverting Mux' 'IN2L'
root@imx91-voipac:~# amixer set 'Right Capture Inverting Mux' 'IN2R'
root@imx91-voipac:~# arecord -D sysdefault:CARD=wm8904audio -t wav -f cd | aplay -D sysdefault:CARD=wm8904audio
</syntaxhighlight>

'''''Note:''''' Microphone and headphones setup can also be graphically displayed and adjusted:
<syntaxhighlight lang="bash">
root@imx91-voipac:~# alsamixer
</syntaxhighlight>
[[image:iMX8M_Industrial_Development_Kit-AlsaMixer_setup.png|800px]] 

'''''Input:''''' Verify digital microphones (Mic Left, Mic Mid, Mic Right) 
'''''Output:''''' Microphone sound is played in headphones
<syntaxhighlight lang="bash">
root@imx91-voipac:~# amixer set "Capture Input" "DMIC"
root@imx91-voipac:~# arecord -D sysdefault:CARD=wm8904audio -t wav -f cd | aplay -D sysdefault:CARD=wm8904audio
</syntaxhighlight>

== WiFi ==
'''''Note:''''' This WiFi section was tested with the iMX91 Industrial Module in Max and Pro configurations. For Basic configurations, wireless connectivity is not available. For more information see [[iMX91 Industrial Development Kit|the iMX91 Industrial Module comparison]]. 

Load the device driver:
<syntaxhighlight lang="bash">
root@imx91-voipac:~# modprobe moal mod_para=nxp/wifi_mod_para.conf
[ 926.305344] mlan: loading out-of-tree module taints kernel.
[ 926.334171] wlan: Loading MWLAN driver
[ 926.339152] wlan: Register to Bus Driver...
[ 926.343686] vendor=0x02DF device=0x9159 class=0 function=1
[ 926.349765] Attach moal handle ops, card interface type: 0x108
[ 926.355633] rps set to 0 from module param
[ 926.362045] SDIW416: init module param from usr cfg
[ 926.366995] card_type: SDIW416, config block: 0
[ 926.371541] cfg80211_wext=0xf
[ 926.374515] max_vir_bss=1
[ 926.377131] cal_data_cfg=none
[ 926.380112] ps_mode = 1
[ 926.382567] auto_ds = 1
[ 926.385010] host_mlme=enable
[ 926.387895] fw_name=nxp/sdiouartiw416_combo_v0.bin
[ 926.392709] SDIO: max_segs=128 max_seg_size=65535
[ 926.397420] rx_work=1 cpu_num=2
[ 926.400569] Enable moal_recv_amsdu_packet
[ 926.404600] Attach mlan adapter operations.card_type is 0x108.
[ 926.410826] wlan: Enable TX SG mode
[ 926.414357] wlan: Enable RX SG mode
[ 926.421681] Request firmware: nxp/sdiouartiw416_combo_v0.bin
[ 926.708639] Wlan: FW download over, firmwarelen=591808 downloaded 583072
[ 928.113594] WLAN FW is active
[ 928.116573] on_time is 927947046442
[ 928.140994] VDLL image: len=8736
[ 928.144352] FW country code WW does not match with US
[ 928.150617] fw_cap_info=0x187ccf03, dev_cap_mask=0xffffffff
[ 928.156607] max_p2p_conn = 8, max_sta_conn = 8
[ 928.176236] Register NXP 802.11 Adapter mlan0
[ 928.183724] Register NXP 802.11 Adapter uap0
[ 928.194033] Register NXP 802.11 Adapter wfd0
[ 928.199986] wlan: version = SDIW416---16.92.21.p137.2-MM6X16437.p30-GPL-(FP92)
[ 928.208947] wlan: Register to Bus Driver Done
[ 928.216412] wlan: Driver loaded successfully
</syntaxhighlight>

Check if the WiFi interface is present:
<syntaxhighlight lang="bash">
root@imx91-voipac:~# ip addr show dev mlan0
3: wlp1s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 78:c4:0e:a0:32:16 brd ff:ff:ff:ff:ff:ff
</syntaxhighlight>

'''''Input:''''' Scan the available WiFi networks 
'''''Output:''''' Networks are scanned and in-depth information are displayed 
<syntaxhighlight lang="bash">
root@imx91-voipac:~# ifconfig mlan0 up && iw dev mlan0 scan
BSS 94:27:90:7f:c3:d3(on wlp1s0)
TSF: 1213185029341 usec (14d, 00:59:45)
freq: 2442
beacon interval: 100 TUs
capability: ESS Privacy ShortPreamble ShortSlotTime (0x0431)
signal: -73.00 dBm
last seen: 4056 ms ago
SSID: HH40V_C3D3
Supported rates: 1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0
DS Parameter set: channel 7
Country: SK Environment: Indoor/Outdoor
Channels [1 - 13] @ 20 dBm
ERP: <no flags>
Extended supported rates: 24.0 36.0 48.0 54.0
HT capabilities:
Capabilities: 0x1ad
RX LDPC
HT20
SM Power Save disabled
RX HT20 SGI
TX STBC
RX STBC 1-stream
Max AMSDU length: 3839 bytes
No DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 8 usec (0x06)
HT TX/RX MCS rate indexes supported: 0-15
HT operation:
* primary channel: 7
* secondary channel offset: no secondary
* STA channel width: 20 MHz
* RIFS: 1
* HT protection: no
* non-GF present: 1
* OBSS non-GF present: 0
* dual beacon: 0
* dual CTS protection: 0
* STBC beacon: 0
* L-SIG TXOP Prot: 0
* PCO active: 0
* PCO phase: 0
Overlapping BSS scan params:
* passive dwell: 20 TUs
* active dwell: 10 TUs
* channel width trigger scan interval: 300 s
* scan passive total per channel: 200 TUs
* scan active total per channel: 20 TUs
* BSS width channel transition delay factor: 5
* OBSS Scan Activity Threshold: 0.25 %
Extended capabilities:
* HT Information Exchange Supported
* Extended Channel Switching
* SSID List
* Operating Mode Notification
WMM: * Parameter version 1
* BE: CW 15-1023, AIFSN 3
* BK: CW 15-1023, AIFSN 7
* VI: CW 7-15, AIFSN 2, TXOP 3008 usec
* VO: CW 3-7, AIFSN 2, TXOP 1504 usec
RSN: * Version: 1
* Group cipher: CCMP
* Pairwise ciphers: CCMP
* Authentication suites: PSK
* Capabilities: 1-PTKSA-RC 1-GTKSA-RC (0x0000)
WPS: * Version: 1.0
* Wi-Fi Protected Setup State: 2 (Configured)
* Response Type: 3 (AP)
* UUID: 87654321-9abc-def0-1234-942790c36dc7
* Manufacturer: TCL.org
* Model: WAP
* Model Number: 123
* Serial Number: 12345
* Primary Device Type: 6-0050f204-1
* Device name: TCL AP
* Config methods:
* Unknown TLV (0x1049, 6 bytes): 00 37 2a 00 01 20
BSS 34:e8:94:5c:06:80(on wlp1s0)
TSF: 787677017722 usec (9d, 02:47:57)
freq: 2462
beacon interval: 100 TUs
capability: ESS Privacy ShortSlotTime (0x0411)
signal: -73.00 dBm
last seen: 3952 ms ago
SSID: OrangeFlybox_0680
Supported rates: 1.0* 2.0* 5.5* 11.0* 9.0 18.0 36.0 54.0
DS Parameter set: channel 11
ERP: Barker_Preamble_Mode
Extended supported rates: 6.0 12.0 24.0 48.0
HT capabilities:
Capabilities: 0x106e
HT20/HT40
SM Power Save disabled
RX HT20 SGI
RX HT40 SGI
No RX STBC
Max AMSDU length: 3839 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 4 usec (0x05)
HT RX MCS rate indexes supported: 0-15, 32
HT TX MCS rate indexes are undefined
HT operation:
* primary channel: 11
* secondary channel offset: no secondary
* STA channel width: 20 MHz
* RIFS: 0
* HT protection: 20 MHz
* non-GF present: 1
* OBSS non-GF present: 0
* dual beacon: 0
* dual CTS protection: 0
* STBC beacon: 0
* L-SIG TXOP Prot: 0
* PCO active: 0
* PCO phase: 0
WPA: * Version: 1
* Group cipher: TKIP
* Pairwise ciphers: TKIP CCMP
* Authentication suites: PSK
RSN: * Version: 1
* Group cipher: TKIP
* Pairwise ciphers: TKIP CCMP
* Authentication suites: PSK
* Capabilities: 1-PTKSA-RC 1-GTKSA-RC (0x0000)
WMM: * Parameter version 1
* BE: CW 15-1023, AIFSN 3
* BK: CW 15-1023, AIFSN 7
* VI: CW 7-15, AIFSN 2, TXOP 3008 usec
* VO: CW 3-7, AIFSN 2, TXOP 1504 usec
BSS Load:
* station count: 3
* channel utilisation: 27/255
* available admission capacity: 31250 [*32us]
Overlapping BSS scan params:
* passive dwell: 20 TUs
* active dwell: 10 TUs
* channel width trigger scan interval: 300 s
* scan passive total per channel: 200 TUs
* scan active total per channel: 20 TUs
* BSS width channel transition delay factor: 5
* OBSS Scan Activity Threshold: 0.25 %
Extended capabilities:
* HT Information Exchange Supported
WPS: * Version: 1.0
* Wi-Fi Protected Setup State: 2 (Configured)
* AP setup locked: 0x01
* Response Type: 3 (AP)
* UUID: 38833092-3092-1883-9c77-34e8945c06c4
* Manufacturer: TP-LINK
* Model: Archer MR200
* Model Number: 1.0
* Serial Number: 1.0
* Primary Device Type: 6-0050f204-1
* Device name: AC750 Wireless Dual Band 4G LTE
* Config methods: Label, Display, Keypad
* RF Bands: 0x1
* Unknown TLV (0x1049, 6 bytes): 00 37 2a 00 01 20
BSS 34:e8:94:5b:f8:04(on wlp1s0)
TSF: 1210179077454 usec (14d, 00:09:39)
freq: 2462
beacon interval: 100 TUs
capability: ESS Privacy ShortSlotTime (0x0411)
signal: -50.00 dBm
last seen: 3432 ms ago
SSID: REDARROW
Supported rates: 1.0* 2.0* 5.5* 11.0* 9.0 18.0 36.0 54.0
DS Parameter set: channel 11
Extended supported rates: 6.0 12.0 24.0 48.0
TIM: DTIM Count 0 DTIM Period 1 Bitmap Control 0x0 Bitmap[0] 0x2
WPS: * Version: 1.0
* Wi-Fi Protected Setup State: 2 (Configured)
* AP setup locked: 0x01
* UUID: 38833092-3092-1883-9c77-34e8945bf8c4
* RF Bands: 0x1
* Unknown TLV (0x1049, 6 bytes): 00 37 2a 00 01 20
ERP: Barker_Preamble_Mode
HT capabilities:
Capabilities: 0x106e
HT20/HT40
SM Power Save disabled
RX HT20 SGI
RX HT40 SGI
No RX STBC
Max AMSDU length: 3839 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 4 usec (0x05)
HT RX MCS rate indexes supported: 0-15, 32
HT TX MCS rate indexes are undefined
HT operation:
* primary channel: 11
* secondary channel offset: no secondary
* STA channel width: 20 MHz
* RIFS: 0
* HT protection: no
* non-GF present: 0
* OBSS non-GF present: 0
* dual beacon: 0
* dual CTS protection: 0
* STBC beacon: 0
* L-SIG TXOP Prot: 0
* PCO active: 0
* PCO phase: 0
Overlapping BSS scan params:
* passive dwell: 20 TUs
* active dwell: 10 TUs
* channel width trigger scan interval: 300 s
* scan passive total per channel: 200 TUs
* scan active total per channel: 20 TUs
* BSS width channel transition delay factor: 5
* OBSS Scan Activity Threshold: 0.25 %
Extended capabilities:
* HT Information Exchange Supported
WPA: * Version: 1
* Group cipher: TKIP
* Pairwise ciphers: TKIP CCMP
* Authentication suites: PSK
RSN: * Version: 1
* Group cipher: TKIP
* Pairwise ciphers: TKIP CCMP
* Authentication suites: PSK
* Capabilities: 1-PTKSA-RC 1-GTKSA-RC (0x0000)
WMM: * Parameter version 1
* BE: CW 15-1023, AIFSN 3
* BK: CW 15-1023, AIFSN 7
* VI: CW 7-15, AIFSN 2, TXOP 3008 usec
* VO: CW 3-7, AIFSN 2, TXOP 1504 usec
BSS Load:
* station count: 0
* channel utilisation: 47/255
* available admission capacity: 31250 [*32us]
</syntaxhighlight>

To set up the network login data, edit file located in /etc/wpa_supplicant.conf and update '''''ssid''''' and passphrase '''''psk''''' fields.

<syntaxhighlight lang="bash">
root@imx91-voipac:~# cat /etc/wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
update_config=1

network={
ssid="SSID_FOR_WIFI_NETWORK"
scan_ssid=1
key_mgmt=WPA-PSK
psk="WIFI_NETWORK_PASSWORD"
}

</syntaxhighlight>

To connect to the desired WiFi network, start wpa_supplicant:
<syntaxhighlight lang="bash">
root@imx91-voipac:~# wpa_supplicant -D nl80211 -i mlan0 -c /etc/wpa_supplicant.conf &
root@imx91-voipac:~# rfkill: Cannot open RFKILL control device
[ 261.722718] wlan: mlan0 START SCAN
[ 266.018892] wlan: SCAN COMPLETED: scanned AP count=1
mlan0: SME: Trying to authentica[ 266.027303] wlan: HostMlme mlan0 send auth to bssid 40:XX:XX:XX:70:62
te with 40:a5:ef:c0:70:62 (SSID='WifiPoschodie' f[ 266.037546] mlan0:
req=2437 MHz)
[ 266.037558] wlan: HostMlme Auth received from 40:XX:XX:XX:70:62
mlan0: Trying to associate with 40:a5:ef:c0:70:62 (SSID='WifiPoschodie' freq=2437 MHz)
[ 266.057956] wlan: HostMlme mlan0 Connected to bssid 40:XX:XX:XX:70:62 successfully
mlan0: Associated[ 266.067323] mlan0:
with 40:a5:ef:c0[ 266.067340] wlan: Send EAPOL pkt to 40:XX:XX:XX:70:62
</syntaxhighlight>

To obtain an IP address and other network settings, run dhcp client:
<syntaxhighlight lang="bash">
udhcpc -i mlan0
</syntaxhighlight>

At this point the bandwidth measurement can be tested, showing that WiFi connection was established and is performed very reliably.
Used program: [https://iperf.fr iPerf3.] 

'''''Configuration:''''' iMX91 Industrial Module Pro in Industrial temperature range (u-blox MAYA-W160-00B assembled):
<syntaxhighlight lang="bash">
root@imx91-voipac:~# iperf3 -c 192.168.240.200 -t 30 -i1
Connecting to host 192.168.240.200, port 5201
[ 5] local 192.168.240.111 port 39988 connected to 192.168.240.200 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 5.12 MBytes 43.0 Mbits/sec 0 223 KBytes
[ 5] 1.00-2.00 sec 5.38 MBytes 45.1 Mbits/sec 0 460 KBytes
[ 5] 2.00-3.00 sec 7.12 MBytes 59.8 Mbits/sec 0 747 KBytes
[ 5] 3.00-4.00 sec 4.25 MBytes 35.7 Mbits/sec 0 1003 KBytes
[ 5] 4.00-5.00 sec 5.38 MBytes 45.1 Mbits/sec 0 1.25 MBytes
[ 5] 5.00-6.00 sec 5.50 MBytes 46.1 Mbits/sec 0 1.52 MBytes
[ 5] 6.00-7.00 sec 5.50 MBytes 46.1 Mbits/sec 0 1.78 MBytes
[ 5] 7.00-8.00 sec 5.62 MBytes 47.2 Mbits/sec 0 2.06 MBytes
[ 5] 8.00-9.00 sec 5.50 MBytes 46.1 Mbits/sec 0 2.31 MBytes
[ 5] 9.00-10.00 sec 5.50 MBytes 46.1 Mbits/sec 0 2.64 MBytes
[ 5] 10.00-11.00 sec 6.75 MBytes 56.6 Mbits/sec 0 2.93 MBytes
[ 5] 11.00-12.00 sec 3.00 MBytes 25.2 Mbits/sec 0 3.10 MBytes
[ 5] 12.00-13.00 sec 6.75 MBytes 56.6 Mbits/sec 0 3.41 MBytes
[ 5] 13.00-14.00 sec 5.75 MBytes 48.2 Mbits/sec 0 3.61 MBytes
[ 5] 14.00-15.00 sec 4.25 MBytes 35.7 Mbits/sec 0 3.81 MBytes
[ 5] 15.00-16.00 sec 5.75 MBytes 48.2 Mbits/sec 0 3.81 MBytes
[ 5] 16.00-17.00 sec 4.38 MBytes 36.7 Mbits/sec 0 4.07 MBytes
[ 5] 17.00-18.00 sec 5.88 MBytes 49.3 Mbits/sec 0 4.07 MBytes
[ 5] 18.00-19.00 sec 2.75 MBytes 23.1 Mbits/sec 0 4.07 MBytes
[ 5] 19.00-20.00 sec 3.38 MBytes 28.3 Mbits/sec 3 2.86 MBytes
[ 5] 20.00-21.00 sec 2.88 MBytes 24.1 Mbits/sec 0 2.94 MBytes
[ 5] 21.00-22.00 sec 1.25 MBytes 10.5 Mbits/sec 0 3.10 MBytes
[ 5] 22.00-23.00 sec 5.50 MBytes 46.1 Mbits/sec 0 3.44 MBytes
[ 5] 23.00-24.00 sec 5.50 MBytes 46.1 Mbits/sec 0 3.63 MBytes
[ 5] 24.00-25.00 sec 4.50 MBytes 37.7 Mbits/sec 0 3.64 MBytes
[ 5] 25.00-26.00 sec 4.25 MBytes 35.7 Mbits/sec 0 3.64 MBytes
[ 5] 26.00-27.00 sec 5.62 MBytes 47.2 Mbits/sec 0 3.86 MBytes
[ 5] 27.00-28.00 sec 6.62 MBytes 55.6 Mbits/sec 0 3.86 MBytes
[ 5] 28.00-29.00 sec 5.50 MBytes 46.1 Mbits/sec 0 3.86 MBytes
[ 5] 29.00-30.00 sec 4.88 MBytes 40.8 Mbits/sec 0 3.86 MBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-30.00 sec 150 MBytes 41.9 Mbits/sec 3 sender
[ 5] 0.00-30.32 sec 150 MBytes 41.5 Mbits/sec receiver

iperf Done.
</syntaxhighlight>

== Bluetooth ==
'''''Note:''''' This Bluetooth section was tested with the iMX91 Industrial Module in Max and Pro configurations. For Basic configuration, bluetooth capabilities are not available. For more information see [[iMX91 Industrial Development Kit|the iMX91 Industrial Module comparison]]. 

'''''Input:''''' None 
'''''Output:''''' Remote device is recognized after scan 

'''''Note:''''' For iMX91 Industrial Module Max (u-blox MAYA-W260-00B assembled) please use instead of <syntaxhighlight lang="bash">hciattach /dev/ttyLP7 any 3000000 flow</syntaxhighlight> command <syntaxhighlight lang="bash">hciattach /dev/ttyLP7 any 115200 flow</syntaxhighlight> in below code
<syntaxhighlight lang="bash">
# attach necessary modules
root@imx91-voipac:~# modprobe moal mod_para=nxp/wifi_mod_para.conf
root@imx91-voipac:~# modprobe hci_uart
root@imx91-voipac:~# hciattach /dev/ttyLP7 any 3000000 flow
Device setup complete
root@imx91-voipac:~# [ 1207.472299] Bluetooth: MGMT ver 1.22
[ 1207.485171] NET: Registered PF_ALG protocol family

# put hci0 device up
root@imx91-voipac:~# hciconfig hci0 up

# scan for remote bluetooth devices (enable bluetooth on phone and make it discoverable)
root@imx91-voipac:~# hcitool scan
Scanning ...
Devices:
hci0 00:0D:18:01:5A:B3
</syntaxhighlight>

== Ethernet ==
'''''Note:''''' This section was tested with the iMX91 Industrial Module in Max configuration which includes dual Gigabit Ethernet PHY. The Pro configuration includes single Gigabit Ethernet PHY. For the Basic configuration, Ethernet capabilities are not available. For more information see [[iMX91 Industrial Development Kit|the iMX91 Industrial Module comparison]]. 

'''''Input:''''' None 
'''''Output:''''' Device driver is available (for Pro configuration only one ethernet is available) 
'''''Note:''''' MAC address should be identical with the address on the sticker placed on the board
<syntaxhighlight lang="bash">

root@imx91-voipac:~# ip addr show dev eth0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:0d:15:01:8c:ae brd ff:ff:ff:ff:ff:ff
inet 192.168.1.33/24 metric 10 brd 192.168.1.255 scope global dynamic eth0
valid_lft 86378sec preferred_lft 86378sec
inet6 fe80::20d:15ff:fe01:8cae/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
root@imx91-voipac:~# ip addr show dev eth1
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:0d:15:01:8c:af brd ff:ff:ff:ff:ff:ff
inet 192.168.1.34/24 metric 10 brd 192.168.1.255 scope global dynamic eth1
valid_lft 86391sec preferred_lft 86391sec
inet6 fe80::20d:15ff:fe01:8caf/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
root@imx91-voipac:~#
</syntaxhighlight>

'''''Input:''''' Plug Ethernet cable into top or bottom connector for the Max configuration. Plug Ethernet cable into bottom connector for the Pro configuration. 
'''''Output:''''' IPv4 address is assigned
<syntaxhighlight lang="bash">
[ 1599.750399] fec 42890000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[ 1630.695671] imx-dwmac 428a0000.ethernet eth1: Link is Up - 1Gbps/Full - flow control off
</syntaxhighlight>

=== Performance ===
iPerf3 was used to test the Ethernet performance. 
'''''Note:''''' The Max configuration of the iMX91 Industrial Module includes dual Gigabit Ethernet PHY. The Pro configuration includes single Gigabit Ethernet PHY. 
'''''Input:''''' Start iPerf3 on computer using command <syntaxhighlight lang="bash">iperf3 -s </syntaxhighlight>
'''''Output:''''' Verify performance on board (argument after -c is IP address of your computer) 

<syntaxhighlight lang="bash">
root@imx91-voipac:~# iperf3 -c 192.168.240.120 -t 10 -i 1
Connecting to host 192.168.240.120, port 5201
[ 5] local 192.168.240.32 port 57734 connected to 192.168.240.120 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 114 MBytes 951 Mbits/sec 0 358 KBytes
[ 5] 1.00-2.00 sec 112 MBytes 943 Mbits/sec 0 358 KBytes
[ 5] 2.00-3.00 sec 112 MBytes 938 Mbits/sec 0 358 KBytes
[ 5] 3.00-4.00 sec 113 MBytes 947 Mbits/sec 0 393 KBytes
[ 5] 4.00-5.00 sec 112 MBytes 941 Mbits/sec 0 393 KBytes
[ 5] 5.00-6.00 sec 112 MBytes 944 Mbits/sec 0 393 KBytes
[ 5] 6.00-7.00 sec 112 MBytes 940 Mbits/sec 0 516 KBytes
[ 5] 7.00-8.00 sec 112 MBytes 943 Mbits/sec 0 516 KBytes
[ 5] 8.00-9.00 sec 112 MBytes 942 Mbits/sec 0 516 KBytes
[ 5] 9.00-10.00 sec 113 MBytes 946 Mbits/sec 0 516 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 1.10 GBytes 943 Mbits/sec 0 sender
[ 5] 0.00-10.05 sec 1.10 GBytes 937 Mbits/sec receiver

iperf Done.
root@imx91-voipac:~#

</syntaxhighlight>

== USB 2.0 ==
NOTE: Perform read/write performance test 
'''''Input:''''' Plug USB flash drive into USB connector 
'''''Output:''''' Plugged USB device is listed
<syntaxhighlight lang="bash">
root@imx91-voipac:~# lsusb
Bus 001 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 125f:d31a A-DATA Technology Co., Ltd.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
</syntaxhighlight>

'''''Input:''''' Generate a dummy file and copy it into USB flash drive 
'''''Output:''''' Generated file and copied file have the same checksum
<syntaxhighlight lang="bash">
root@imx91-voipac:~# mount /dev/sda1 /media/
root@imx91-voipac:~# rm -f file.txt /media/file.txt
root@imx91-voipac:~# dd if=/dev/urandom of=file.txt count=1024 bs=1024
1024+0 records in
1024+0 records out
root@imx91-voipac:~# cp file.txt /media/
root@imx91-voipac:~# md5sum file.txt /media/file.txt
200a9fd3e9850fcedf85ed50d4c4733d file.txt
200a9fd3e9850fcedf85ed50d4c4733d /media/file.txt
root@imx91-voipac:~# rm file.txt /media/file.txt
root@imx91-voipac:~# umount /media
</syntaxhighlight>

== USB-C ==
This connector is primarily used for flashing new binaries into the iMX91 Industrial Module. More information can be found on the dedicated [[iMX91 Industrial Flashing Procedure|module flashing page]]. 

== USB Micro-B serial console ==
'''''Input:''''' Connect USB console cable into the base board connector and open serial console with baud rate 115200 8n1 
'''''Output:''''' The board is controlled and responsive to serial terminal commands
<syntaxhighlight lang="bash">
root@imx91-voipac:~# uname -a
Linux imx91-voipac 6.6.36-lts-next-g2e3e2e65d92a #1 SMP PREEMPT Wed Sep 4 08:22:45 UTC 2024 aarch64 GNU/Linux
</syntaxhighlight>

== UART serial console ==
Serial console is utilized via USB Micro-B connector by default. Alternatively, the communication can be established using UART headers and TTL-232R-3V3 - FTDI cable. 
NOTE: Describe jumpers position 
[[File:iMX91 Industrial Development Kit-Serial console via UART1.png|800px]] 

'''''Note:''''' Usage of UART2 CONSOLE to communicate by default requires changes in Yocto binaries and new compilation of image files. 
[[File:iMX91 Industrial Development Kit-Serial console via UART2.png|800px]]

== SD Card ==
NOTE: Perform detection of SD Card
<syntaxhighlight lang="bash">
root@imx91-voipac:~# fdisk -l
Disk /dev/mmcblk0: 15 GB, 15758000128 bytes, 30777344 sectors
240448 cylinders, 4 heads, 32 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type
/dev/mmcblk0p1 * 128,0,1 1023,3,32 16384 186775 170392 83.1M c Win95 FAT32 (LBA)
/dev/mmcblk0p2 1023,3,32 1023,3,32 196608 939761 743154 362M 83 Linux
Disk /dev/mmcblk0boot0: 4 MB, 4194304 bytes, 8192 sectors
128 cylinders, 4 heads, 16 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Disk /dev/mmcblk0boot1: 4 MB, 4194304 bytes, 8192 sectors
128 cylinders, 4 heads, 16 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Disk /dev/mmcblk1: 15 GB, 15931539456 bytes, 31116288 sectors
243096 cylinders, 4 heads, 32 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type
/dev/mmcblk1p1 512,0,1 1023,3,32 65536 266255 200720 98.0M 83 Linux
</syntaxhighlight>

/dev/mmcblk1 is SD card (mmcblk0 is eMMC)

== JTAG ==
[[File:iMX91 Industrial Development Kit-JTAG communication setup.png|800px]] 
To verify that i.MX93 CPU JTAG is functional, following command identifies and connects to the CPU's debug point:
<syntaxhighlight lang="bash">
J-Link> jtagid
</syntaxhighlight>

[[File:J-Link MIMX9352 A55 1.png|800px]] 
[[File:J-Link MIMX9352 M33.png|800px]]

== Real Time Clock ==
RTC chip is detected by Linux kernel after start-up:
<syntaxhighlight lang="bash">
root@imx91-voipac:~# dmesg | grep rtc
[ 0.894414] imx-drm display-subsystem: bound imx-lcdifv3-crtc.0 (ops lcdifv3_crtc_ops)
[ 0.910506] imx-drm display-subsystem: [drm] Cannot find any crtc or sizes
[ 1.209418] bbnsm_rtc 44440000.bbnsm:rtc: registered as rtc0
[ 1.215749] bbnsm_rtc 44440000.bbnsm:rtc: setting system clock to 1970-01-01T00:00:00 UTC (0)
root@imx91-voipac:~#
</syntaxhighlight>

CPU correctly recognises RTC on the I2C1 bus, the chip is under usage by the kernel:
<syntaxhighlight lang="bash">
root@imx91-voipac:~# i2cdetect -r -y 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- UU -- -- -- UU -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- 3d -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- UU -- UU -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
</syntaxhighlight>

Set up the current date and time, show the actual values

Setup date and time
<syntaxhighlight lang="bash">
date -s "2025-8-13 14:52:26"
</syntaxhighlight>

Show actual values
<syntaxhighlight lang="bash">
root@imx91-voipac:~# timedatectl
[ 134.509782] kauditd_printk_skb: 8 callbacks suppressed
[ 134.509793] audit: type=1334 audit(1732625725.140:18): prog-id=19 op=LOAD
[ 134.523935] audit: type=1334 audit(1732625725.148:19): prog-id=20 op=LOAD
[ 134.531609] audit: type=1334 audit(1732625725.152:20): prog-id=21 op=LOAD
Local time: Tue 2024-11-26 12:55:25 UTC
Universal time: Tue 2024-11-26 12:55:25 UTC
RTC time: Tue 2024-11-26 12:55:25
Time zone: UTC (UTC, +0000)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no
</syntaxhighlight>

== I2C EEPROM Memory - on module ==
'''''Input:''''' Power on board 
'''''Output:''''' Store some data to eeprom and after reboot read it back and should be same 

<syntaxhighlight lang="bash">
# store random 8bytes to eeprom
root@imx91-voipac-evk:~# dd if=/dev/urandom of=/sys/bus/i2c/devices/0-0050/eeprom bs=8 count=1
+1 records in
0+1 records out
8 bytes copied, 0.0225523 s, 0.4 kB/s
</syntaxhighlight>

After board reboot:
<syntaxhighlight lang="bash">
# store random 8bytes to eeprom
root@imx91-voipac-evk:~# hexdump -n8 /sys/bus/i2c/devices/0-0050/eeprom
0000000 c4dd 4eda d624 535e
0000008
</syntaxhighlight>

== Reset button ==
'''''Input:''''' Press the RESET button 
'''''Output:''''' The board will execute bootloader immediately with "Reset cause: POR" 
'''''Note:''''' iMX91 Industrial Development Kit should never freeze or hang after the reset button was pressed. Testing the operation 10 times gives a reliable result
<syntaxhighlight lang="bash">
U-Boot 2023.04+gf8a2983ec8+p0 (Mar 04 2024 - 07:25:04 +0000)

CPU: i.MX93(52) rev1.1 1700 MHz (running at 1692 MHz)
CPU: Industrial temperature grade (-40C to 105C) at 45C
Reset cause: POR (0x1)
Model: NXP i.MX93 Voipac EVK board
DRAM: 2 GiB
Core: 215 devices, 32 uclasses, devicetree: separate
MMC: FSL_SDHC: 0, FSL_SDHC: 1
Loading Environment from MMC... OK
[*]-Video Link 0fail to find output device

....
</syntaxhighlight>

== On/Off button ==
'''''Input:''''' Press and hold On/Off button for more then 5 seconds 
'''''Output:''''' The board will be powered off

Press shortly the On/Off button again, the board will be powered on.

== Sleep Mode ==
'''''Input:''''' Type command:
<syntaxhighlight lang="bash">
echo mem > /sys/power/state
</syntaxhighlight>

'''''Output:''''' The board will go into a frozen state and the serial console will not respond to inputs.

Shortly press the Up user button, to wake the board up again.

[[File:imx93_sleep_mode.png|740px]] 

== User buttons ==
'''''Input:''''' Press Enter/Left/Right/Up/Down buttons 
'''''Output:''''' Button events 1 and 0 are generated
<syntaxhighlight lang="bash">
root@imx91-voipac-evk:~# evtest /dev/input/by-path/platform-gpio-buttons-event
Input driver version is 1.0.1
Input device ID: bus 0x19 vendor 0x1 product 0x1 version 0x100
Input device name: "gpio-buttons"
Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
Event code 28 (KEY_ENTER)
Event code 103 (KEY_UP)
Event code 105 (KEY_LEFT)
Event code 106 (KEY_RIGHT)
Event code 108 (KEY_DOWN)
Properties:
Testing ... (interrupt to exit)
Event: time 1717485486.586413, type 1 (EV_KEY), code 103 (KEY_UP), value 1
Event: time 1717485486.586413, -------------- SYN_REPORT ------------
Event: time 1717485486.682265, type 1 (EV_KEY), code 103 (KEY_UP), value 0
Event: time 1717485486.682265, -------------- SYN_REPORT ------------
Event: time 1717485487.255120, type 1 (EV_KEY), code 108 (KEY_DOWN), value 1
Event: time 1717485487.255120, -------------- SYN_REPORT ------------
Event: time 1717485487.367126, type 1 (EV_KEY), code 108 (KEY_DOWN), value 0
Event: time 1717485487.367126, -------------- SYN_REPORT ------------
Event: time 1717485488.539564, type 1 (EV_KEY), code 106 (KEY_RIGHT), value 1
Event: time 1717485488.539564, -------------- SYN_REPORT ------------
Event: time 1717485488.677501, type 1 (EV_KEY), code 106 (KEY_RIGHT), value 0
Event: time 1717485488.677501, -------------- SYN_REPORT ------------
Event: time 1717485488.897627, type 1 (EV_KEY), code 105 (KEY_LEFT), value 1
Event: time 1717485488.897627, -------------- SYN_REPORT ------------
Event: time 1717485489.013136, type 1 (EV_KEY), code 105 (KEY_LEFT), value 0
Event: time 1717485489.013136, -------------- SYN_REPORT ------------
Event: time 1717485489.264589, type 1 (EV_KEY), code 28 (KEY_ENTER), value 1
Event: time 1717485489.264589, -------------- SYN_REPORT ------------
Event: time 1717485489.372584, type 1 (EV_KEY), code 28 (KEY_ENTER), value 0
Event: time 1717485489.372584, -------------- SYN_REPORT ------------
</syntaxhighlight>

== User LED ==
'''''Input:''''' None 
'''''Output:''''' Script switches User LED on baseboard ON and OFF in one second intervals
<syntaxhighlight lang="bash">
#!/bin/sh

LED=/sys/class/leds/user_sbc

while true; do
echo 0 > ${LED}/brightness
sleep 1
echo 1 > ${LED}/brightness
sleep 1
done
</syntaxhighlight>

'''''Input:''''' None 
'''''Output:''''' User LED on baseboard is set to heartbeat blinking sequence
<syntaxhighlight lang="bash">
root@imx91-voipac-evk:~# echo heartbeat > /sys/class/leds/user_sbc/trigger
</syntaxhighlight>

'''''Input:''''' None 
'''''Output:''''' User LED on SOM is set to heartbeat blinking sequence
<syntaxhighlight lang="bash">
root@imx91-voipac-evk:~# echo heartbeat > /sys/class/leds/user_som/trigger
</syntaxhighlight>

File:iMX91 Industrial Development Kit-JTAG communication setup.png

2025-10-30T10:27:33Z

Voipac-sw:

File:iMX91 Industrial Development Kit-Serial console via UART2.png

2025-10-30T10:26:39Z

Voipac-sw:

iMX91 Industrial Accessing and Testing Peripherals

2025-10-30T10:26:20Z

Voipac-sw: /* UART serial console */

[[Category:iMX91 Industrial]]
[[Category:iMX91 Industrial Software]]
[[Category:iMX91 Industrial Testing]]
[[Category:iMX91 Industrial Peripherals]]

<div style="float:right">__TOC__</div>

The initial operations with the iMX91 Industrial Development Kit interfaces are presented on this page. For more specific information such as display options, camera capabilities or industrial modular extensions, refer to the dedicated [[iMX91 Industrial Max#Peripherals_and_Accessories|Peripherals and Accessories section]].

== Mandatory components ==
=== Hardware ===
* iMX91 Industrial Module
* iMX Development Baseboard
* [https://www.voipac.com/power-supply-5v-20w DC power supply (5V, 4A, 20W)]

=== Peripherals and Accessories ===
* [https://wiki.voipac.com/index.php?title=NXP_Parallel_TFT_Display_Set NXP Parallel TFT Display Set]
* [https://www.voipac.com/imx9-wifi-and-bluetooth-antennas-set iMX9 Wifi and Bluetooth antenna set]
* 1x MicroSDHC card Class 10 or higher
* 1x USB Flash drive 2.0
* Headphones
* Analog external microphone

=== Cables ===
* USB Micro-B cable for serial console
* USB-C cable for module flashing
* Ethernet cable

== Audio ==
'''''Note:''''' This audio section was tested with the iMX91 Industrial Module in Max and Pro configurations. For Basic configuration, audio capabilities are not available. For more information see [[iMX91 Industrial Development Kit|the iMX91 Industrial Module comparison]]. 

'''''Input:''''' Search kernel log for wm8904 chip 
'''''Output:''''' Audio chip is detected and bound as an output and input device
<syntaxhighlight lang="bash">
root@imx91-voipac:~# dmesg | grep wm8904
[ 6.546858] wm8904 0-001a: supply DCVDD not found, using dummy regulator
[ 6.591866] wm8904 0-001a: supply DBVDD not found, using dummy regulator
[ 6.611921] wm8904 0-001a: supply AVDD not found, using dummy regulator
[ 6.637768] wm8904 0-001a: supply CPVDD not found, using dummy regulator
[ 6.670934] wm8904 0-001a: supply MICVDD not found, using dummy regulator
[ 6.683500] wm8904 0-001a: revision A
</syntaxhighlight>

'''''Input:''''' Run amixer command 
'''''Output:''''' Current audio chip settings are displayed
<syntaxhighlight lang="bash">
root@imx91-voipac:~# amixer
Simple mixer control 'Headphone',0
Capabilities: volume pswitch
Playback channels: Front Left - Front Right
Capture channels: Front Left - Front Right
Limits: 0 - 63
Front Left: 45 [71%] [-12.00dB] Playback [on]
Front Right: 45 [71%] [-12.00dB] Playback [on]
Simple mixer control 'Headphone ZC',0
Capabilities: pswitch
Playback channels: Front Left - Front Right
Mono:
Front Left: Playback [on]
Front Right: Playback [on]
Simple mixer control 'Line Output',0
Capabilities: volume pswitch
Playback channels: Front Left - Front Right
Capture channels: Front Left - Front Right
Limits: 0 - 63
Front Left: 57 [90%] [0.00dB] Playback [on]
Front Right: 57 [90%] [0.00dB] Playback [on]
...
</syntaxhighlight>

'''''Input:''''' Connect headphones into LINE OUT jack connector 
'''''Output:''''' Audio file is played and heard
<syntaxhighlight lang="bash">
root@imx8mq-voipac:~# aplay /usr/share/multimedia/sample.wav
Playing WAVE 'multimedia/sample.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
root@imx8mq-voipac:~# aplay -D sysdefault:CARD=wm8904audio /usr/share/multimedia/sample.wav
Playing WAVE 'multimedia/sample.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
</syntaxhighlight>

'''''Input:''''' Plug headphones into HEADPHONES jack connector and analog external microphone to MIC jack connector 
'''''Output:''''' Sound recorder by microphone is played in headphones
<syntaxhighlight lang="bash">
root@imx91-voipac:~# amixer set 'Capture' '31'
root@imx91-voipac:~# amixer set 'Capture Input' ADC
root@imx91-voipac:~# amixer set 'Left Capture Inverting Mux' 'IN2L'
root@imx91-voipac:~# amixer set 'Right Capture Inverting Mux' 'IN2R'
root@imx91-voipac:~# arecord -D sysdefault:CARD=wm8904audio -t wav -f cd | aplay -D sysdefault:CARD=wm8904audio
</syntaxhighlight>

'''''Note:''''' Microphone and headphones setup can also be graphically displayed and adjusted:
<syntaxhighlight lang="bash">
root@imx91-voipac:~# alsamixer
</syntaxhighlight>
[[image:iMX8M_Industrial_Development_Kit-AlsaMixer_setup.png|800px]] 

'''''Input:''''' Verify digital microphones (Mic Left, Mic Mid, Mic Right) 
'''''Output:''''' Microphone sound is played in headphones
<syntaxhighlight lang="bash">
root@imx91-voipac:~# amixer set "Capture Input" "DMIC"
root@imx91-voipac:~# arecord -D sysdefault:CARD=wm8904audio -t wav -f cd | aplay -D sysdefault:CARD=wm8904audio
</syntaxhighlight>

== WiFi ==
'''''Note:''''' This WiFi section was tested with the iMX91 Industrial Module in Max and Pro configurations. For Basic configurations, wireless connectivity is not available. For more information see [[iMX91 Industrial Development Kit|the iMX91 Industrial Module comparison]]. 

Load the device driver:
<syntaxhighlight lang="bash">
root@imx91-voipac:~# modprobe moal mod_para=nxp/wifi_mod_para.conf
[ 926.305344] mlan: loading out-of-tree module taints kernel.
[ 926.334171] wlan: Loading MWLAN driver
[ 926.339152] wlan: Register to Bus Driver...
[ 926.343686] vendor=0x02DF device=0x9159 class=0 function=1
[ 926.349765] Attach moal handle ops, card interface type: 0x108
[ 926.355633] rps set to 0 from module param
[ 926.362045] SDIW416: init module param from usr cfg
[ 926.366995] card_type: SDIW416, config block: 0
[ 926.371541] cfg80211_wext=0xf
[ 926.374515] max_vir_bss=1
[ 926.377131] cal_data_cfg=none
[ 926.380112] ps_mode = 1
[ 926.382567] auto_ds = 1
[ 926.385010] host_mlme=enable
[ 926.387895] fw_name=nxp/sdiouartiw416_combo_v0.bin
[ 926.392709] SDIO: max_segs=128 max_seg_size=65535
[ 926.397420] rx_work=1 cpu_num=2
[ 926.400569] Enable moal_recv_amsdu_packet
[ 926.404600] Attach mlan adapter operations.card_type is 0x108.
[ 926.410826] wlan: Enable TX SG mode
[ 926.414357] wlan: Enable RX SG mode
[ 926.421681] Request firmware: nxp/sdiouartiw416_combo_v0.bin
[ 926.708639] Wlan: FW download over, firmwarelen=591808 downloaded 583072
[ 928.113594] WLAN FW is active
[ 928.116573] on_time is 927947046442
[ 928.140994] VDLL image: len=8736
[ 928.144352] FW country code WW does not match with US
[ 928.150617] fw_cap_info=0x187ccf03, dev_cap_mask=0xffffffff
[ 928.156607] max_p2p_conn = 8, max_sta_conn = 8
[ 928.176236] Register NXP 802.11 Adapter mlan0
[ 928.183724] Register NXP 802.11 Adapter uap0
[ 928.194033] Register NXP 802.11 Adapter wfd0
[ 928.199986] wlan: version = SDIW416---16.92.21.p137.2-MM6X16437.p30-GPL-(FP92)
[ 928.208947] wlan: Register to Bus Driver Done
[ 928.216412] wlan: Driver loaded successfully
</syntaxhighlight>

Check if the WiFi interface is present:
<syntaxhighlight lang="bash">
root@imx91-voipac:~# ip addr show dev mlan0
3: wlp1s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 78:c4:0e:a0:32:16 brd ff:ff:ff:ff:ff:ff
</syntaxhighlight>

'''''Input:''''' Scan the available WiFi networks 
'''''Output:''''' Networks are scanned and in-depth information are displayed 
<syntaxhighlight lang="bash">
root@imx91-voipac:~# ifconfig mlan0 up && iw dev mlan0 scan
BSS 94:27:90:7f:c3:d3(on wlp1s0)
TSF: 1213185029341 usec (14d, 00:59:45)
freq: 2442
beacon interval: 100 TUs
capability: ESS Privacy ShortPreamble ShortSlotTime (0x0431)
signal: -73.00 dBm
last seen: 4056 ms ago
SSID: HH40V_C3D3
Supported rates: 1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0
DS Parameter set: channel 7
Country: SK Environment: Indoor/Outdoor
Channels [1 - 13] @ 20 dBm
ERP: <no flags>
Extended supported rates: 24.0 36.0 48.0 54.0
HT capabilities:
Capabilities: 0x1ad
RX LDPC
HT20
SM Power Save disabled
RX HT20 SGI
TX STBC
RX STBC 1-stream
Max AMSDU length: 3839 bytes
No DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 8 usec (0x06)
HT TX/RX MCS rate indexes supported: 0-15
HT operation:
* primary channel: 7
* secondary channel offset: no secondary
* STA channel width: 20 MHz
* RIFS: 1
* HT protection: no
* non-GF present: 1
* OBSS non-GF present: 0
* dual beacon: 0
* dual CTS protection: 0
* STBC beacon: 0
* L-SIG TXOP Prot: 0
* PCO active: 0
* PCO phase: 0
Overlapping BSS scan params:
* passive dwell: 20 TUs
* active dwell: 10 TUs
* channel width trigger scan interval: 300 s
* scan passive total per channel: 200 TUs
* scan active total per channel: 20 TUs
* BSS width channel transition delay factor: 5
* OBSS Scan Activity Threshold: 0.25 %
Extended capabilities:
* HT Information Exchange Supported
* Extended Channel Switching
* SSID List
* Operating Mode Notification
WMM: * Parameter version 1
* BE: CW 15-1023, AIFSN 3
* BK: CW 15-1023, AIFSN 7
* VI: CW 7-15, AIFSN 2, TXOP 3008 usec
* VO: CW 3-7, AIFSN 2, TXOP 1504 usec
RSN: * Version: 1
* Group cipher: CCMP
* Pairwise ciphers: CCMP
* Authentication suites: PSK
* Capabilities: 1-PTKSA-RC 1-GTKSA-RC (0x0000)
WPS: * Version: 1.0
* Wi-Fi Protected Setup State: 2 (Configured)
* Response Type: 3 (AP)
* UUID: 87654321-9abc-def0-1234-942790c36dc7
* Manufacturer: TCL.org
* Model: WAP
* Model Number: 123
* Serial Number: 12345
* Primary Device Type: 6-0050f204-1
* Device name: TCL AP
* Config methods:
* Unknown TLV (0x1049, 6 bytes): 00 37 2a 00 01 20
BSS 34:e8:94:5c:06:80(on wlp1s0)
TSF: 787677017722 usec (9d, 02:47:57)
freq: 2462
beacon interval: 100 TUs
capability: ESS Privacy ShortSlotTime (0x0411)
signal: -73.00 dBm
last seen: 3952 ms ago
SSID: OrangeFlybox_0680
Supported rates: 1.0* 2.0* 5.5* 11.0* 9.0 18.0 36.0 54.0
DS Parameter set: channel 11
ERP: Barker_Preamble_Mode
Extended supported rates: 6.0 12.0 24.0 48.0
HT capabilities:
Capabilities: 0x106e
HT20/HT40
SM Power Save disabled
RX HT20 SGI
RX HT40 SGI
No RX STBC
Max AMSDU length: 3839 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 4 usec (0x05)
HT RX MCS rate indexes supported: 0-15, 32
HT TX MCS rate indexes are undefined
HT operation:
* primary channel: 11
* secondary channel offset: no secondary
* STA channel width: 20 MHz
* RIFS: 0
* HT protection: 20 MHz
* non-GF present: 1
* OBSS non-GF present: 0
* dual beacon: 0
* dual CTS protection: 0
* STBC beacon: 0
* L-SIG TXOP Prot: 0
* PCO active: 0
* PCO phase: 0
WPA: * Version: 1
* Group cipher: TKIP
* Pairwise ciphers: TKIP CCMP
* Authentication suites: PSK
RSN: * Version: 1
* Group cipher: TKIP
* Pairwise ciphers: TKIP CCMP
* Authentication suites: PSK
* Capabilities: 1-PTKSA-RC 1-GTKSA-RC (0x0000)
WMM: * Parameter version 1
* BE: CW 15-1023, AIFSN 3
* BK: CW 15-1023, AIFSN 7
* VI: CW 7-15, AIFSN 2, TXOP 3008 usec
* VO: CW 3-7, AIFSN 2, TXOP 1504 usec
BSS Load:
* station count: 3
* channel utilisation: 27/255
* available admission capacity: 31250 [*32us]
Overlapping BSS scan params:
* passive dwell: 20 TUs
* active dwell: 10 TUs
* channel width trigger scan interval: 300 s
* scan passive total per channel: 200 TUs
* scan active total per channel: 20 TUs
* BSS width channel transition delay factor: 5
* OBSS Scan Activity Threshold: 0.25 %
Extended capabilities:
* HT Information Exchange Supported
WPS: * Version: 1.0
* Wi-Fi Protected Setup State: 2 (Configured)
* AP setup locked: 0x01
* Response Type: 3 (AP)
* UUID: 38833092-3092-1883-9c77-34e8945c06c4
* Manufacturer: TP-LINK
* Model: Archer MR200
* Model Number: 1.0
* Serial Number: 1.0
* Primary Device Type: 6-0050f204-1
* Device name: AC750 Wireless Dual Band 4G LTE
* Config methods: Label, Display, Keypad
* RF Bands: 0x1
* Unknown TLV (0x1049, 6 bytes): 00 37 2a 00 01 20
BSS 34:e8:94:5b:f8:04(on wlp1s0)
TSF: 1210179077454 usec (14d, 00:09:39)
freq: 2462
beacon interval: 100 TUs
capability: ESS Privacy ShortSlotTime (0x0411)
signal: -50.00 dBm
last seen: 3432 ms ago
SSID: REDARROW
Supported rates: 1.0* 2.0* 5.5* 11.0* 9.0 18.0 36.0 54.0
DS Parameter set: channel 11
Extended supported rates: 6.0 12.0 24.0 48.0
TIM: DTIM Count 0 DTIM Period 1 Bitmap Control 0x0 Bitmap[0] 0x2
WPS: * Version: 1.0
* Wi-Fi Protected Setup State: 2 (Configured)
* AP setup locked: 0x01
* UUID: 38833092-3092-1883-9c77-34e8945bf8c4
* RF Bands: 0x1
* Unknown TLV (0x1049, 6 bytes): 00 37 2a 00 01 20
ERP: Barker_Preamble_Mode
HT capabilities:
Capabilities: 0x106e
HT20/HT40
SM Power Save disabled
RX HT20 SGI
RX HT40 SGI
No RX STBC
Max AMSDU length: 3839 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 4 usec (0x05)
HT RX MCS rate indexes supported: 0-15, 32
HT TX MCS rate indexes are undefined
HT operation:
* primary channel: 11
* secondary channel offset: no secondary
* STA channel width: 20 MHz
* RIFS: 0
* HT protection: no
* non-GF present: 0
* OBSS non-GF present: 0
* dual beacon: 0
* dual CTS protection: 0
* STBC beacon: 0
* L-SIG TXOP Prot: 0
* PCO active: 0
* PCO phase: 0
Overlapping BSS scan params:
* passive dwell: 20 TUs
* active dwell: 10 TUs
* channel width trigger scan interval: 300 s
* scan passive total per channel: 200 TUs
* scan active total per channel: 20 TUs
* BSS width channel transition delay factor: 5
* OBSS Scan Activity Threshold: 0.25 %
Extended capabilities:
* HT Information Exchange Supported
WPA: * Version: 1
* Group cipher: TKIP
* Pairwise ciphers: TKIP CCMP
* Authentication suites: PSK
RSN: * Version: 1
* Group cipher: TKIP
* Pairwise ciphers: TKIP CCMP
* Authentication suites: PSK
* Capabilities: 1-PTKSA-RC 1-GTKSA-RC (0x0000)
WMM: * Parameter version 1
* BE: CW 15-1023, AIFSN 3
* BK: CW 15-1023, AIFSN 7
* VI: CW 7-15, AIFSN 2, TXOP 3008 usec
* VO: CW 3-7, AIFSN 2, TXOP 1504 usec
BSS Load:
* station count: 0
* channel utilisation: 47/255
* available admission capacity: 31250 [*32us]
</syntaxhighlight>

To set up the network login data, edit file located in /etc/wpa_supplicant.conf and update '''''ssid''''' and passphrase '''''psk''''' fields.

<syntaxhighlight lang="bash">
root@imx91-voipac:~# cat /etc/wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
update_config=1

network={
ssid="SSID_FOR_WIFI_NETWORK"
scan_ssid=1
key_mgmt=WPA-PSK
psk="WIFI_NETWORK_PASSWORD"
}

</syntaxhighlight>

To connect to the desired WiFi network, start wpa_supplicant:
<syntaxhighlight lang="bash">
root@imx91-voipac:~# wpa_supplicant -D nl80211 -i mlan0 -c /etc/wpa_supplicant.conf &
root@imx91-voipac:~# rfkill: Cannot open RFKILL control device
[ 261.722718] wlan: mlan0 START SCAN
[ 266.018892] wlan: SCAN COMPLETED: scanned AP count=1
mlan0: SME: Trying to authentica[ 266.027303] wlan: HostMlme mlan0 send auth to bssid 40:XX:XX:XX:70:62
te with 40:a5:ef:c0:70:62 (SSID='WifiPoschodie' f[ 266.037546] mlan0:
req=2437 MHz)
[ 266.037558] wlan: HostMlme Auth received from 40:XX:XX:XX:70:62
mlan0: Trying to associate with 40:a5:ef:c0:70:62 (SSID='WifiPoschodie' freq=2437 MHz)
[ 266.057956] wlan: HostMlme mlan0 Connected to bssid 40:XX:XX:XX:70:62 successfully
mlan0: Associated[ 266.067323] mlan0:
with 40:a5:ef:c0[ 266.067340] wlan: Send EAPOL pkt to 40:XX:XX:XX:70:62
</syntaxhighlight>

To obtain an IP address and other network settings, run dhcp client:
<syntaxhighlight lang="bash">
udhcpc -i mlan0
</syntaxhighlight>

At this point the bandwidth measurement can be tested, showing that WiFi connection was established and is performed very reliably.
Used program: [https://iperf.fr iPerf3.] 

'''''Configuration:''''' iMX91 Industrial Module Pro in Industrial temperature range (u-blox MAYA-W160-00B assembled):
<syntaxhighlight lang="bash">
root@imx91-voipac:~# iperf3 -c 192.168.240.200 -t 30 -i1
Connecting to host 192.168.240.200, port 5201
[ 5] local 192.168.240.111 port 39988 connected to 192.168.240.200 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 5.12 MBytes 43.0 Mbits/sec 0 223 KBytes
[ 5] 1.00-2.00 sec 5.38 MBytes 45.1 Mbits/sec 0 460 KBytes
[ 5] 2.00-3.00 sec 7.12 MBytes 59.8 Mbits/sec 0 747 KBytes
[ 5] 3.00-4.00 sec 4.25 MBytes 35.7 Mbits/sec 0 1003 KBytes
[ 5] 4.00-5.00 sec 5.38 MBytes 45.1 Mbits/sec 0 1.25 MBytes
[ 5] 5.00-6.00 sec 5.50 MBytes 46.1 Mbits/sec 0 1.52 MBytes
[ 5] 6.00-7.00 sec 5.50 MBytes 46.1 Mbits/sec 0 1.78 MBytes
[ 5] 7.00-8.00 sec 5.62 MBytes 47.2 Mbits/sec 0 2.06 MBytes
[ 5] 8.00-9.00 sec 5.50 MBytes 46.1 Mbits/sec 0 2.31 MBytes
[ 5] 9.00-10.00 sec 5.50 MBytes 46.1 Mbits/sec 0 2.64 MBytes
[ 5] 10.00-11.00 sec 6.75 MBytes 56.6 Mbits/sec 0 2.93 MBytes
[ 5] 11.00-12.00 sec 3.00 MBytes 25.2 Mbits/sec 0 3.10 MBytes
[ 5] 12.00-13.00 sec 6.75 MBytes 56.6 Mbits/sec 0 3.41 MBytes
[ 5] 13.00-14.00 sec 5.75 MBytes 48.2 Mbits/sec 0 3.61 MBytes
[ 5] 14.00-15.00 sec 4.25 MBytes 35.7 Mbits/sec 0 3.81 MBytes
[ 5] 15.00-16.00 sec 5.75 MBytes 48.2 Mbits/sec 0 3.81 MBytes
[ 5] 16.00-17.00 sec 4.38 MBytes 36.7 Mbits/sec 0 4.07 MBytes
[ 5] 17.00-18.00 sec 5.88 MBytes 49.3 Mbits/sec 0 4.07 MBytes
[ 5] 18.00-19.00 sec 2.75 MBytes 23.1 Mbits/sec 0 4.07 MBytes
[ 5] 19.00-20.00 sec 3.38 MBytes 28.3 Mbits/sec 3 2.86 MBytes
[ 5] 20.00-21.00 sec 2.88 MBytes 24.1 Mbits/sec 0 2.94 MBytes
[ 5] 21.00-22.00 sec 1.25 MBytes 10.5 Mbits/sec 0 3.10 MBytes
[ 5] 22.00-23.00 sec 5.50 MBytes 46.1 Mbits/sec 0 3.44 MBytes
[ 5] 23.00-24.00 sec 5.50 MBytes 46.1 Mbits/sec 0 3.63 MBytes
[ 5] 24.00-25.00 sec 4.50 MBytes 37.7 Mbits/sec 0 3.64 MBytes
[ 5] 25.00-26.00 sec 4.25 MBytes 35.7 Mbits/sec 0 3.64 MBytes
[ 5] 26.00-27.00 sec 5.62 MBytes 47.2 Mbits/sec 0 3.86 MBytes
[ 5] 27.00-28.00 sec 6.62 MBytes 55.6 Mbits/sec 0 3.86 MBytes
[ 5] 28.00-29.00 sec 5.50 MBytes 46.1 Mbits/sec 0 3.86 MBytes
[ 5] 29.00-30.00 sec 4.88 MBytes 40.8 Mbits/sec 0 3.86 MBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-30.00 sec 150 MBytes 41.9 Mbits/sec 3 sender
[ 5] 0.00-30.32 sec 150 MBytes 41.5 Mbits/sec receiver

iperf Done.
</syntaxhighlight>

== Bluetooth ==
'''''Note:''''' This Bluetooth section was tested with the iMX91 Industrial Module in Max and Pro configurations. For Basic configuration, bluetooth capabilities are not available. For more information see [[iMX91 Industrial Development Kit|the iMX91 Industrial Module comparison]]. 

'''''Input:''''' None 
'''''Output:''''' Remote device is recognized after scan 

'''''Note:''''' For iMX91 Industrial Module Max (u-blox MAYA-W260-00B assembled) please use instead of <syntaxhighlight lang="bash">hciattach /dev/ttyLP7 any 3000000 flow</syntaxhighlight> command <syntaxhighlight lang="bash">hciattach /dev/ttyLP7 any 115200 flow</syntaxhighlight> in below code
<syntaxhighlight lang="bash">
# attach necessary modules
root@imx91-voipac:~# modprobe moal mod_para=nxp/wifi_mod_para.conf
root@imx91-voipac:~# modprobe hci_uart
root@imx91-voipac:~# hciattach /dev/ttyLP7 any 3000000 flow
Device setup complete
root@imx91-voipac:~# [ 1207.472299] Bluetooth: MGMT ver 1.22
[ 1207.485171] NET: Registered PF_ALG protocol family

# put hci0 device up
root@imx91-voipac:~# hciconfig hci0 up

# scan for remote bluetooth devices (enable bluetooth on phone and make it discoverable)
root@imx91-voipac:~# hcitool scan
Scanning ...
Devices:
hci0 00:0D:18:01:5A:B3
</syntaxhighlight>

== Ethernet ==
'''''Note:''''' This section was tested with the iMX91 Industrial Module in Max configuration which includes dual Gigabit Ethernet PHY. The Pro configuration includes single Gigabit Ethernet PHY. For the Basic configuration, Ethernet capabilities are not available. For more information see [[iMX91 Industrial Development Kit|the iMX91 Industrial Module comparison]]. 

'''''Input:''''' None 
'''''Output:''''' Device driver is available (for Pro configuration only one ethernet is available) 
'''''Note:''''' MAC address should be identical with the address on the sticker placed on the board
<syntaxhighlight lang="bash">

root@imx91-voipac:~# ip addr show dev eth0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:0d:15:01:8c:ae brd ff:ff:ff:ff:ff:ff
inet 192.168.1.33/24 metric 10 brd 192.168.1.255 scope global dynamic eth0
valid_lft 86378sec preferred_lft 86378sec
inet6 fe80::20d:15ff:fe01:8cae/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
root@imx91-voipac:~# ip addr show dev eth1
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:0d:15:01:8c:af brd ff:ff:ff:ff:ff:ff
inet 192.168.1.34/24 metric 10 brd 192.168.1.255 scope global dynamic eth1
valid_lft 86391sec preferred_lft 86391sec
inet6 fe80::20d:15ff:fe01:8caf/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
root@imx91-voipac:~#
</syntaxhighlight>

'''''Input:''''' Plug Ethernet cable into top or bottom connector for the Max configuration. Plug Ethernet cable into bottom connector for the Pro configuration. 
'''''Output:''''' IPv4 address is assigned
<syntaxhighlight lang="bash">
[ 1599.750399] fec 42890000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[ 1630.695671] imx-dwmac 428a0000.ethernet eth1: Link is Up - 1Gbps/Full - flow control off
</syntaxhighlight>

=== Performance ===
iPerf3 was used to test the Ethernet performance. 
'''''Note:''''' The Max configuration of the iMX91 Industrial Module includes dual Gigabit Ethernet PHY. The Pro configuration includes single Gigabit Ethernet PHY. 
'''''Input:''''' Start iPerf3 on computer using command <syntaxhighlight lang="bash">iperf3 -s </syntaxhighlight>
'''''Output:''''' Verify performance on board (argument after -c is IP address of your computer) 

<syntaxhighlight lang="bash">
root@imx91-voipac:~# iperf3 -c 192.168.240.120 -t 10 -i 1
Connecting to host 192.168.240.120, port 5201
[ 5] local 192.168.240.32 port 57734 connected to 192.168.240.120 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 114 MBytes 951 Mbits/sec 0 358 KBytes
[ 5] 1.00-2.00 sec 112 MBytes 943 Mbits/sec 0 358 KBytes
[ 5] 2.00-3.00 sec 112 MBytes 938 Mbits/sec 0 358 KBytes
[ 5] 3.00-4.00 sec 113 MBytes 947 Mbits/sec 0 393 KBytes
[ 5] 4.00-5.00 sec 112 MBytes 941 Mbits/sec 0 393 KBytes
[ 5] 5.00-6.00 sec 112 MBytes 944 Mbits/sec 0 393 KBytes
[ 5] 6.00-7.00 sec 112 MBytes 940 Mbits/sec 0 516 KBytes
[ 5] 7.00-8.00 sec 112 MBytes 943 Mbits/sec 0 516 KBytes
[ 5] 8.00-9.00 sec 112 MBytes 942 Mbits/sec 0 516 KBytes
[ 5] 9.00-10.00 sec 113 MBytes 946 Mbits/sec 0 516 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 1.10 GBytes 943 Mbits/sec 0 sender
[ 5] 0.00-10.05 sec 1.10 GBytes 937 Mbits/sec receiver

iperf Done.
root@imx91-voipac:~#

</syntaxhighlight>

== USB 2.0 ==
NOTE: Perform read/write performance test 
'''''Input:''''' Plug USB flash drive into USB connector 
'''''Output:''''' Plugged USB device is listed
<syntaxhighlight lang="bash">
root@imx91-voipac:~# lsusb
Bus 001 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 125f:d31a A-DATA Technology Co., Ltd.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
</syntaxhighlight>

'''''Input:''''' Generate a dummy file and copy it into USB flash drive 
'''''Output:''''' Generated file and copied file have the same checksum
<syntaxhighlight lang="bash">
root@imx91-voipac:~# mount /dev/sda1 /media/
root@imx91-voipac:~# rm -f file.txt /media/file.txt
root@imx91-voipac:~# dd if=/dev/urandom of=file.txt count=1024 bs=1024
1024+0 records in
1024+0 records out
root@imx91-voipac:~# cp file.txt /media/
root@imx91-voipac:~# md5sum file.txt /media/file.txt
200a9fd3e9850fcedf85ed50d4c4733d file.txt
200a9fd3e9850fcedf85ed50d4c4733d /media/file.txt
root@imx91-voipac:~# rm file.txt /media/file.txt
root@imx91-voipac:~# umount /media
</syntaxhighlight>

== USB-C ==
This connector is primarily used for flashing new binaries into the iMX91 Industrial Module. More information can be found on the dedicated [[iMX91 Industrial Flashing Procedure|module flashing page]]. 

== USB Micro-B serial console ==
'''''Input:''''' Connect USB console cable into the base board connector and open serial console with baud rate 115200 8n1 
'''''Output:''''' The board is controlled and responsive to serial terminal commands
<syntaxhighlight lang="bash">
root@imx91-voipac:~# uname -a
Linux imx91-voipac 6.6.36-lts-next-g2e3e2e65d92a #1 SMP PREEMPT Wed Sep 4 08:22:45 UTC 2024 aarch64 GNU/Linux
</syntaxhighlight>

== UART serial console ==
Serial console is utilized via USB Micro-B connector by default. Alternatively, the communication can be established using UART headers and TTL-232R-3V3 - FTDI cable. 
NOTE: Describe jumpers position 
[[File:iMX91 Industrial Development Kit-Serial console via UART1.png|800px]] 

'''''Note:''''' Usage of UART2 CONSOLE to communicate by default requires changes in Yocto binaries and new compilation of image files. 
[[File:iMX91 Industrial Development Kit-Serial console via UART2.png|800px]]

== SD Card ==
NOTE: Perform detection of SD Card
<syntaxhighlight lang="bash">
root@imx91-voipac:~# fdisk -l
Disk /dev/mmcblk0: 15 GB, 15758000128 bytes, 30777344 sectors
240448 cylinders, 4 heads, 32 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type
/dev/mmcblk0p1 * 128,0,1 1023,3,32 16384 186775 170392 83.1M c Win95 FAT32 (LBA)
/dev/mmcblk0p2 1023,3,32 1023,3,32 196608 939761 743154 362M 83 Linux
Disk /dev/mmcblk0boot0: 4 MB, 4194304 bytes, 8192 sectors
128 cylinders, 4 heads, 16 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Disk /dev/mmcblk0boot1: 4 MB, 4194304 bytes, 8192 sectors
128 cylinders, 4 heads, 16 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Disk /dev/mmcblk1: 15 GB, 15931539456 bytes, 31116288 sectors
243096 cylinders, 4 heads, 32 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type
/dev/mmcblk1p1 512,0,1 1023,3,32 65536 266255 200720 98.0M 83 Linux
</syntaxhighlight>

/dev/mmcblk1 is SD card (mmcblk0 is eMMC)

== JTAG ==
[[File:iMX93 Industrial Development Kit-JTAG communication setup.png|800px]] 
To verify that i.MX93 CPU JTAG is functional, following command identifies and connects to the CPU's debug point:
<syntaxhighlight lang="bash">
J-Link> jtagid
</syntaxhighlight>

[[File:J-Link MIMX9352 A55 1.png|800px]] 
[[File:J-Link MIMX9352 M33.png|800px]]

== Real Time Clock ==
RTC chip is detected by Linux kernel after start-up:
<syntaxhighlight lang="bash">
root@imx91-voipac:~# dmesg | grep rtc
[ 0.894414] imx-drm display-subsystem: bound imx-lcdifv3-crtc.0 (ops lcdifv3_crtc_ops)
[ 0.910506] imx-drm display-subsystem: [drm] Cannot find any crtc or sizes
[ 1.209418] bbnsm_rtc 44440000.bbnsm:rtc: registered as rtc0
[ 1.215749] bbnsm_rtc 44440000.bbnsm:rtc: setting system clock to 1970-01-01T00:00:00 UTC (0)
root@imx91-voipac:~#
</syntaxhighlight>

CPU correctly recognises RTC on the I2C1 bus, the chip is under usage by the kernel:
<syntaxhighlight lang="bash">
root@imx91-voipac:~# i2cdetect -r -y 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- UU -- -- -- UU -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- 3d -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- UU -- UU -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
</syntaxhighlight>

Set up the current date and time, show the actual values

Setup date and time
<syntaxhighlight lang="bash">
date -s "2025-8-13 14:52:26"
</syntaxhighlight>

Show actual values
<syntaxhighlight lang="bash">
root@imx91-voipac:~# timedatectl
[ 134.509782] kauditd_printk_skb: 8 callbacks suppressed
[ 134.509793] audit: type=1334 audit(1732625725.140:18): prog-id=19 op=LOAD
[ 134.523935] audit: type=1334 audit(1732625725.148:19): prog-id=20 op=LOAD
[ 134.531609] audit: type=1334 audit(1732625725.152:20): prog-id=21 op=LOAD
Local time: Tue 2024-11-26 12:55:25 UTC
Universal time: Tue 2024-11-26 12:55:25 UTC
RTC time: Tue 2024-11-26 12:55:25
Time zone: UTC (UTC, +0000)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no
</syntaxhighlight>

== I2C EEPROM Memory - on module ==
'''''Input:''''' Power on board 
'''''Output:''''' Store some data to eeprom and after reboot read it back and should be same 

<syntaxhighlight lang="bash">
# store random 8bytes to eeprom
root@imx91-voipac-evk:~# dd if=/dev/urandom of=/sys/bus/i2c/devices/0-0050/eeprom bs=8 count=1
+1 records in
0+1 records out
8 bytes copied, 0.0225523 s, 0.4 kB/s
</syntaxhighlight>

After board reboot:
<syntaxhighlight lang="bash">
# store random 8bytes to eeprom
root@imx91-voipac-evk:~# hexdump -n8 /sys/bus/i2c/devices/0-0050/eeprom
0000000 c4dd 4eda d624 535e
0000008
</syntaxhighlight>

== Reset button ==
'''''Input:''''' Press the RESET button 
'''''Output:''''' The board will execute bootloader immediately with "Reset cause: POR" 
'''''Note:''''' iMX91 Industrial Development Kit should never freeze or hang after the reset button was pressed. Testing the operation 10 times gives a reliable result
<syntaxhighlight lang="bash">
U-Boot 2023.04+gf8a2983ec8+p0 (Mar 04 2024 - 07:25:04 +0000)

CPU: i.MX93(52) rev1.1 1700 MHz (running at 1692 MHz)
CPU: Industrial temperature grade (-40C to 105C) at 45C
Reset cause: POR (0x1)
Model: NXP i.MX93 Voipac EVK board
DRAM: 2 GiB
Core: 215 devices, 32 uclasses, devicetree: separate
MMC: FSL_SDHC: 0, FSL_SDHC: 1
Loading Environment from MMC... OK
[*]-Video Link 0fail to find output device

....
</syntaxhighlight>

== On/Off button ==
'''''Input:''''' Press and hold On/Off button for more then 5 seconds 
'''''Output:''''' The board will be powered off

Press shortly the On/Off button again, the board will be powered on.

== Sleep Mode ==
'''''Input:''''' Type command:
<syntaxhighlight lang="bash">
echo mem > /sys/power/state
</syntaxhighlight>

'''''Output:''''' The board will go into a frozen state and the serial console will not respond to inputs.

Shortly press the Up user button, to wake the board up again.

[[File:imx93_sleep_mode.png|740px]] 

== User buttons ==
'''''Input:''''' Press Enter/Left/Right/Up/Down buttons 
'''''Output:''''' Button events 1 and 0 are generated
<syntaxhighlight lang="bash">
root@imx91-voipac-evk:~# evtest /dev/input/by-path/platform-gpio-buttons-event
Input driver version is 1.0.1
Input device ID: bus 0x19 vendor 0x1 product 0x1 version 0x100
Input device name: "gpio-buttons"
Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
Event code 28 (KEY_ENTER)
Event code 103 (KEY_UP)
Event code 105 (KEY_LEFT)
Event code 106 (KEY_RIGHT)
Event code 108 (KEY_DOWN)
Properties:
Testing ... (interrupt to exit)
Event: time 1717485486.586413, type 1 (EV_KEY), code 103 (KEY_UP), value 1
Event: time 1717485486.586413, -------------- SYN_REPORT ------------
Event: time 1717485486.682265, type 1 (EV_KEY), code 103 (KEY_UP), value 0
Event: time 1717485486.682265, -------------- SYN_REPORT ------------
Event: time 1717485487.255120, type 1 (EV_KEY), code 108 (KEY_DOWN), value 1
Event: time 1717485487.255120, -------------- SYN_REPORT ------------
Event: time 1717485487.367126, type 1 (EV_KEY), code 108 (KEY_DOWN), value 0
Event: time 1717485487.367126, -------------- SYN_REPORT ------------
Event: time 1717485488.539564, type 1 (EV_KEY), code 106 (KEY_RIGHT), value 1
Event: time 1717485488.539564, -------------- SYN_REPORT ------------
Event: time 1717485488.677501, type 1 (EV_KEY), code 106 (KEY_RIGHT), value 0
Event: time 1717485488.677501, -------------- SYN_REPORT ------------
Event: time 1717485488.897627, type 1 (EV_KEY), code 105 (KEY_LEFT), value 1
Event: time 1717485488.897627, -------------- SYN_REPORT ------------
Event: time 1717485489.013136, type 1 (EV_KEY), code 105 (KEY_LEFT), value 0
Event: time 1717485489.013136, -------------- SYN_REPORT ------------
Event: time 1717485489.264589, type 1 (EV_KEY), code 28 (KEY_ENTER), value 1
Event: time 1717485489.264589, -------------- SYN_REPORT ------------
Event: time 1717485489.372584, type 1 (EV_KEY), code 28 (KEY_ENTER), value 0
Event: time 1717485489.372584, -------------- SYN_REPORT ------------
</syntaxhighlight>

== User LED ==
'''''Input:''''' None 
'''''Output:''''' Script switches User LED on baseboard ON and OFF in one second intervals
<syntaxhighlight lang="bash">
#!/bin/sh

LED=/sys/class/leds/user_sbc

while true; do
echo 0 > ${LED}/brightness
sleep 1
echo 1 > ${LED}/brightness
sleep 1
done
</syntaxhighlight>

'''''Input:''''' None 
'''''Output:''''' User LED on baseboard is set to heartbeat blinking sequence
<syntaxhighlight lang="bash">
root@imx91-voipac-evk:~# echo heartbeat > /sys/class/leds/user_sbc/trigger
</syntaxhighlight>

'''''Input:''''' None 
'''''Output:''''' User LED on SOM is set to heartbeat blinking sequence
<syntaxhighlight lang="bash">
root@imx91-voipac-evk:~# echo heartbeat > /sys/class/leds/user_som/trigger
</syntaxhighlight>

File:iMX91 Industrial Development Kit-Serial console via UART1.png

2025-10-30T10:25:48Z

Voipac-sw:

iMX91 Industrial Accessing and Testing Peripherals

2025-10-30T10:25:02Z

Voipac-sw: /* USB-C */

[[Category:iMX91 Industrial]]
[[Category:iMX91 Industrial Software]]
[[Category:iMX91 Industrial Testing]]
[[Category:iMX91 Industrial Peripherals]]

<div style="float:right">__TOC__</div>

The initial operations with the iMX91 Industrial Development Kit interfaces are presented on this page. For more specific information such as display options, camera capabilities or industrial modular extensions, refer to the dedicated [[iMX91 Industrial Max#Peripherals_and_Accessories|Peripherals and Accessories section]].

== Mandatory components ==
=== Hardware ===
* iMX91 Industrial Module
* iMX Development Baseboard
* [https://www.voipac.com/power-supply-5v-20w DC power supply (5V, 4A, 20W)]

=== Peripherals and Accessories ===
* [https://wiki.voipac.com/index.php?title=NXP_Parallel_TFT_Display_Set NXP Parallel TFT Display Set]
* [https://www.voipac.com/imx9-wifi-and-bluetooth-antennas-set iMX9 Wifi and Bluetooth antenna set]
* 1x MicroSDHC card Class 10 or higher
* 1x USB Flash drive 2.0
* Headphones
* Analog external microphone

=== Cables ===
* USB Micro-B cable for serial console
* USB-C cable for module flashing
* Ethernet cable

== Audio ==
'''''Note:''''' This audio section was tested with the iMX91 Industrial Module in Max and Pro configurations. For Basic configuration, audio capabilities are not available. For more information see [[iMX91 Industrial Development Kit|the iMX91 Industrial Module comparison]]. 

'''''Input:''''' Search kernel log for wm8904 chip 
'''''Output:''''' Audio chip is detected and bound as an output and input device
<syntaxhighlight lang="bash">
root@imx91-voipac:~# dmesg | grep wm8904
[ 6.546858] wm8904 0-001a: supply DCVDD not found, using dummy regulator
[ 6.591866] wm8904 0-001a: supply DBVDD not found, using dummy regulator
[ 6.611921] wm8904 0-001a: supply AVDD not found, using dummy regulator
[ 6.637768] wm8904 0-001a: supply CPVDD not found, using dummy regulator
[ 6.670934] wm8904 0-001a: supply MICVDD not found, using dummy regulator
[ 6.683500] wm8904 0-001a: revision A
</syntaxhighlight>

'''''Input:''''' Run amixer command 
'''''Output:''''' Current audio chip settings are displayed
<syntaxhighlight lang="bash">
root@imx91-voipac:~# amixer
Simple mixer control 'Headphone',0
Capabilities: volume pswitch
Playback channels: Front Left - Front Right
Capture channels: Front Left - Front Right
Limits: 0 - 63
Front Left: 45 [71%] [-12.00dB] Playback [on]
Front Right: 45 [71%] [-12.00dB] Playback [on]
Simple mixer control 'Headphone ZC',0
Capabilities: pswitch
Playback channels: Front Left - Front Right
Mono:
Front Left: Playback [on]
Front Right: Playback [on]
Simple mixer control 'Line Output',0
Capabilities: volume pswitch
Playback channels: Front Left - Front Right
Capture channels: Front Left - Front Right
Limits: 0 - 63
Front Left: 57 [90%] [0.00dB] Playback [on]
Front Right: 57 [90%] [0.00dB] Playback [on]
...
</syntaxhighlight>

'''''Input:''''' Connect headphones into LINE OUT jack connector 
'''''Output:''''' Audio file is played and heard
<syntaxhighlight lang="bash">
root@imx8mq-voipac:~# aplay /usr/share/multimedia/sample.wav
Playing WAVE 'multimedia/sample.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
root@imx8mq-voipac:~# aplay -D sysdefault:CARD=wm8904audio /usr/share/multimedia/sample.wav
Playing WAVE 'multimedia/sample.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
</syntaxhighlight>

'''''Input:''''' Plug headphones into HEADPHONES jack connector and analog external microphone to MIC jack connector 
'''''Output:''''' Sound recorder by microphone is played in headphones
<syntaxhighlight lang="bash">
root@imx91-voipac:~# amixer set 'Capture' '31'
root@imx91-voipac:~# amixer set 'Capture Input' ADC
root@imx91-voipac:~# amixer set 'Left Capture Inverting Mux' 'IN2L'
root@imx91-voipac:~# amixer set 'Right Capture Inverting Mux' 'IN2R'
root@imx91-voipac:~# arecord -D sysdefault:CARD=wm8904audio -t wav -f cd | aplay -D sysdefault:CARD=wm8904audio
</syntaxhighlight>

'''''Note:''''' Microphone and headphones setup can also be graphically displayed and adjusted:
<syntaxhighlight lang="bash">
root@imx91-voipac:~# alsamixer
</syntaxhighlight>
[[image:iMX8M_Industrial_Development_Kit-AlsaMixer_setup.png|800px]] 

'''''Input:''''' Verify digital microphones (Mic Left, Mic Mid, Mic Right) 
'''''Output:''''' Microphone sound is played in headphones
<syntaxhighlight lang="bash">
root@imx91-voipac:~# amixer set "Capture Input" "DMIC"
root@imx91-voipac:~# arecord -D sysdefault:CARD=wm8904audio -t wav -f cd | aplay -D sysdefault:CARD=wm8904audio
</syntaxhighlight>

== WiFi ==
'''''Note:''''' This WiFi section was tested with the iMX91 Industrial Module in Max and Pro configurations. For Basic configurations, wireless connectivity is not available. For more information see [[iMX91 Industrial Development Kit|the iMX91 Industrial Module comparison]]. 

Load the device driver:
<syntaxhighlight lang="bash">
root@imx91-voipac:~# modprobe moal mod_para=nxp/wifi_mod_para.conf
[ 926.305344] mlan: loading out-of-tree module taints kernel.
[ 926.334171] wlan: Loading MWLAN driver
[ 926.339152] wlan: Register to Bus Driver...
[ 926.343686] vendor=0x02DF device=0x9159 class=0 function=1
[ 926.349765] Attach moal handle ops, card interface type: 0x108
[ 926.355633] rps set to 0 from module param
[ 926.362045] SDIW416: init module param from usr cfg
[ 926.366995] card_type: SDIW416, config block: 0
[ 926.371541] cfg80211_wext=0xf
[ 926.374515] max_vir_bss=1
[ 926.377131] cal_data_cfg=none
[ 926.380112] ps_mode = 1
[ 926.382567] auto_ds = 1
[ 926.385010] host_mlme=enable
[ 926.387895] fw_name=nxp/sdiouartiw416_combo_v0.bin
[ 926.392709] SDIO: max_segs=128 max_seg_size=65535
[ 926.397420] rx_work=1 cpu_num=2
[ 926.400569] Enable moal_recv_amsdu_packet
[ 926.404600] Attach mlan adapter operations.card_type is 0x108.
[ 926.410826] wlan: Enable TX SG mode
[ 926.414357] wlan: Enable RX SG mode
[ 926.421681] Request firmware: nxp/sdiouartiw416_combo_v0.bin
[ 926.708639] Wlan: FW download over, firmwarelen=591808 downloaded 583072
[ 928.113594] WLAN FW is active
[ 928.116573] on_time is 927947046442
[ 928.140994] VDLL image: len=8736
[ 928.144352] FW country code WW does not match with US
[ 928.150617] fw_cap_info=0x187ccf03, dev_cap_mask=0xffffffff
[ 928.156607] max_p2p_conn = 8, max_sta_conn = 8
[ 928.176236] Register NXP 802.11 Adapter mlan0
[ 928.183724] Register NXP 802.11 Adapter uap0
[ 928.194033] Register NXP 802.11 Adapter wfd0
[ 928.199986] wlan: version = SDIW416---16.92.21.p137.2-MM6X16437.p30-GPL-(FP92)
[ 928.208947] wlan: Register to Bus Driver Done
[ 928.216412] wlan: Driver loaded successfully
</syntaxhighlight>

Check if the WiFi interface is present:
<syntaxhighlight lang="bash">
root@imx91-voipac:~# ip addr show dev mlan0
3: wlp1s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 78:c4:0e:a0:32:16 brd ff:ff:ff:ff:ff:ff
</syntaxhighlight>

'''''Input:''''' Scan the available WiFi networks 
'''''Output:''''' Networks are scanned and in-depth information are displayed 
<syntaxhighlight lang="bash">
root@imx91-voipac:~# ifconfig mlan0 up && iw dev mlan0 scan
BSS 94:27:90:7f:c3:d3(on wlp1s0)
TSF: 1213185029341 usec (14d, 00:59:45)
freq: 2442
beacon interval: 100 TUs
capability: ESS Privacy ShortPreamble ShortSlotTime (0x0431)
signal: -73.00 dBm
last seen: 4056 ms ago
SSID: HH40V_C3D3
Supported rates: 1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0
DS Parameter set: channel 7
Country: SK Environment: Indoor/Outdoor
Channels [1 - 13] @ 20 dBm
ERP: <no flags>
Extended supported rates: 24.0 36.0 48.0 54.0
HT capabilities:
Capabilities: 0x1ad
RX LDPC
HT20
SM Power Save disabled
RX HT20 SGI
TX STBC
RX STBC 1-stream
Max AMSDU length: 3839 bytes
No DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 8 usec (0x06)
HT TX/RX MCS rate indexes supported: 0-15
HT operation:
* primary channel: 7
* secondary channel offset: no secondary
* STA channel width: 20 MHz
* RIFS: 1
* HT protection: no
* non-GF present: 1
* OBSS non-GF present: 0
* dual beacon: 0
* dual CTS protection: 0
* STBC beacon: 0
* L-SIG TXOP Prot: 0
* PCO active: 0
* PCO phase: 0
Overlapping BSS scan params:
* passive dwell: 20 TUs
* active dwell: 10 TUs
* channel width trigger scan interval: 300 s
* scan passive total per channel: 200 TUs
* scan active total per channel: 20 TUs
* BSS width channel transition delay factor: 5
* OBSS Scan Activity Threshold: 0.25 %
Extended capabilities:
* HT Information Exchange Supported
* Extended Channel Switching
* SSID List
* Operating Mode Notification
WMM: * Parameter version 1
* BE: CW 15-1023, AIFSN 3
* BK: CW 15-1023, AIFSN 7
* VI: CW 7-15, AIFSN 2, TXOP 3008 usec
* VO: CW 3-7, AIFSN 2, TXOP 1504 usec
RSN: * Version: 1
* Group cipher: CCMP
* Pairwise ciphers: CCMP
* Authentication suites: PSK
* Capabilities: 1-PTKSA-RC 1-GTKSA-RC (0x0000)
WPS: * Version: 1.0
* Wi-Fi Protected Setup State: 2 (Configured)
* Response Type: 3 (AP)
* UUID: 87654321-9abc-def0-1234-942790c36dc7
* Manufacturer: TCL.org
* Model: WAP
* Model Number: 123
* Serial Number: 12345
* Primary Device Type: 6-0050f204-1
* Device name: TCL AP
* Config methods:
* Unknown TLV (0x1049, 6 bytes): 00 37 2a 00 01 20
BSS 34:e8:94:5c:06:80(on wlp1s0)
TSF: 787677017722 usec (9d, 02:47:57)
freq: 2462
beacon interval: 100 TUs
capability: ESS Privacy ShortSlotTime (0x0411)
signal: -73.00 dBm
last seen: 3952 ms ago
SSID: OrangeFlybox_0680
Supported rates: 1.0* 2.0* 5.5* 11.0* 9.0 18.0 36.0 54.0
DS Parameter set: channel 11
ERP: Barker_Preamble_Mode
Extended supported rates: 6.0 12.0 24.0 48.0
HT capabilities:
Capabilities: 0x106e
HT20/HT40
SM Power Save disabled
RX HT20 SGI
RX HT40 SGI
No RX STBC
Max AMSDU length: 3839 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 4 usec (0x05)
HT RX MCS rate indexes supported: 0-15, 32
HT TX MCS rate indexes are undefined
HT operation:
* primary channel: 11
* secondary channel offset: no secondary
* STA channel width: 20 MHz
* RIFS: 0
* HT protection: 20 MHz
* non-GF present: 1
* OBSS non-GF present: 0
* dual beacon: 0
* dual CTS protection: 0
* STBC beacon: 0
* L-SIG TXOP Prot: 0
* PCO active: 0
* PCO phase: 0
WPA: * Version: 1
* Group cipher: TKIP
* Pairwise ciphers: TKIP CCMP
* Authentication suites: PSK
RSN: * Version: 1
* Group cipher: TKIP
* Pairwise ciphers: TKIP CCMP
* Authentication suites: PSK
* Capabilities: 1-PTKSA-RC 1-GTKSA-RC (0x0000)
WMM: * Parameter version 1
* BE: CW 15-1023, AIFSN 3
* BK: CW 15-1023, AIFSN 7
* VI: CW 7-15, AIFSN 2, TXOP 3008 usec
* VO: CW 3-7, AIFSN 2, TXOP 1504 usec
BSS Load:
* station count: 3
* channel utilisation: 27/255
* available admission capacity: 31250 [*32us]
Overlapping BSS scan params:
* passive dwell: 20 TUs
* active dwell: 10 TUs
* channel width trigger scan interval: 300 s
* scan passive total per channel: 200 TUs
* scan active total per channel: 20 TUs
* BSS width channel transition delay factor: 5
* OBSS Scan Activity Threshold: 0.25 %
Extended capabilities:
* HT Information Exchange Supported
WPS: * Version: 1.0
* Wi-Fi Protected Setup State: 2 (Configured)
* AP setup locked: 0x01
* Response Type: 3 (AP)
* UUID: 38833092-3092-1883-9c77-34e8945c06c4
* Manufacturer: TP-LINK
* Model: Archer MR200
* Model Number: 1.0
* Serial Number: 1.0
* Primary Device Type: 6-0050f204-1
* Device name: AC750 Wireless Dual Band 4G LTE
* Config methods: Label, Display, Keypad
* RF Bands: 0x1
* Unknown TLV (0x1049, 6 bytes): 00 37 2a 00 01 20
BSS 34:e8:94:5b:f8:04(on wlp1s0)
TSF: 1210179077454 usec (14d, 00:09:39)
freq: 2462
beacon interval: 100 TUs
capability: ESS Privacy ShortSlotTime (0x0411)
signal: -50.00 dBm
last seen: 3432 ms ago
SSID: REDARROW
Supported rates: 1.0* 2.0* 5.5* 11.0* 9.0 18.0 36.0 54.0
DS Parameter set: channel 11
Extended supported rates: 6.0 12.0 24.0 48.0
TIM: DTIM Count 0 DTIM Period 1 Bitmap Control 0x0 Bitmap[0] 0x2
WPS: * Version: 1.0
* Wi-Fi Protected Setup State: 2 (Configured)
* AP setup locked: 0x01
* UUID: 38833092-3092-1883-9c77-34e8945bf8c4
* RF Bands: 0x1
* Unknown TLV (0x1049, 6 bytes): 00 37 2a 00 01 20
ERP: Barker_Preamble_Mode
HT capabilities:
Capabilities: 0x106e
HT20/HT40
SM Power Save disabled
RX HT20 SGI
RX HT40 SGI
No RX STBC
Max AMSDU length: 3839 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 4 usec (0x05)
HT RX MCS rate indexes supported: 0-15, 32
HT TX MCS rate indexes are undefined
HT operation:
* primary channel: 11
* secondary channel offset: no secondary
* STA channel width: 20 MHz
* RIFS: 0
* HT protection: no
* non-GF present: 0
* OBSS non-GF present: 0
* dual beacon: 0
* dual CTS protection: 0
* STBC beacon: 0
* L-SIG TXOP Prot: 0
* PCO active: 0
* PCO phase: 0
Overlapping BSS scan params:
* passive dwell: 20 TUs
* active dwell: 10 TUs
* channel width trigger scan interval: 300 s
* scan passive total per channel: 200 TUs
* scan active total per channel: 20 TUs
* BSS width channel transition delay factor: 5
* OBSS Scan Activity Threshold: 0.25 %
Extended capabilities:
* HT Information Exchange Supported
WPA: * Version: 1
* Group cipher: TKIP
* Pairwise ciphers: TKIP CCMP
* Authentication suites: PSK
RSN: * Version: 1
* Group cipher: TKIP
* Pairwise ciphers: TKIP CCMP
* Authentication suites: PSK
* Capabilities: 1-PTKSA-RC 1-GTKSA-RC (0x0000)
WMM: * Parameter version 1
* BE: CW 15-1023, AIFSN 3
* BK: CW 15-1023, AIFSN 7
* VI: CW 7-15, AIFSN 2, TXOP 3008 usec
* VO: CW 3-7, AIFSN 2, TXOP 1504 usec
BSS Load:
* station count: 0
* channel utilisation: 47/255
* available admission capacity: 31250 [*32us]
</syntaxhighlight>

To set up the network login data, edit file located in /etc/wpa_supplicant.conf and update '''''ssid''''' and passphrase '''''psk''''' fields.

<syntaxhighlight lang="bash">
root@imx91-voipac:~# cat /etc/wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
update_config=1

network={
ssid="SSID_FOR_WIFI_NETWORK"
scan_ssid=1
key_mgmt=WPA-PSK
psk="WIFI_NETWORK_PASSWORD"
}

</syntaxhighlight>

To connect to the desired WiFi network, start wpa_supplicant:
<syntaxhighlight lang="bash">
root@imx91-voipac:~# wpa_supplicant -D nl80211 -i mlan0 -c /etc/wpa_supplicant.conf &
root@imx91-voipac:~# rfkill: Cannot open RFKILL control device
[ 261.722718] wlan: mlan0 START SCAN
[ 266.018892] wlan: SCAN COMPLETED: scanned AP count=1
mlan0: SME: Trying to authentica[ 266.027303] wlan: HostMlme mlan0 send auth to bssid 40:XX:XX:XX:70:62
te with 40:a5:ef:c0:70:62 (SSID='WifiPoschodie' f[ 266.037546] mlan0:
req=2437 MHz)
[ 266.037558] wlan: HostMlme Auth received from 40:XX:XX:XX:70:62
mlan0: Trying to associate with 40:a5:ef:c0:70:62 (SSID='WifiPoschodie' freq=2437 MHz)
[ 266.057956] wlan: HostMlme mlan0 Connected to bssid 40:XX:XX:XX:70:62 successfully
mlan0: Associated[ 266.067323] mlan0:
with 40:a5:ef:c0[ 266.067340] wlan: Send EAPOL pkt to 40:XX:XX:XX:70:62
</syntaxhighlight>

To obtain an IP address and other network settings, run dhcp client:
<syntaxhighlight lang="bash">
udhcpc -i mlan0
</syntaxhighlight>

At this point the bandwidth measurement can be tested, showing that WiFi connection was established and is performed very reliably.
Used program: [https://iperf.fr iPerf3.] 

'''''Configuration:''''' iMX91 Industrial Module Pro in Industrial temperature range (u-blox MAYA-W160-00B assembled):
<syntaxhighlight lang="bash">
root@imx91-voipac:~# iperf3 -c 192.168.240.200 -t 30 -i1
Connecting to host 192.168.240.200, port 5201
[ 5] local 192.168.240.111 port 39988 connected to 192.168.240.200 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 5.12 MBytes 43.0 Mbits/sec 0 223 KBytes
[ 5] 1.00-2.00 sec 5.38 MBytes 45.1 Mbits/sec 0 460 KBytes
[ 5] 2.00-3.00 sec 7.12 MBytes 59.8 Mbits/sec 0 747 KBytes
[ 5] 3.00-4.00 sec 4.25 MBytes 35.7 Mbits/sec 0 1003 KBytes
[ 5] 4.00-5.00 sec 5.38 MBytes 45.1 Mbits/sec 0 1.25 MBytes
[ 5] 5.00-6.00 sec 5.50 MBytes 46.1 Mbits/sec 0 1.52 MBytes
[ 5] 6.00-7.00 sec 5.50 MBytes 46.1 Mbits/sec 0 1.78 MBytes
[ 5] 7.00-8.00 sec 5.62 MBytes 47.2 Mbits/sec 0 2.06 MBytes
[ 5] 8.00-9.00 sec 5.50 MBytes 46.1 Mbits/sec 0 2.31 MBytes
[ 5] 9.00-10.00 sec 5.50 MBytes 46.1 Mbits/sec 0 2.64 MBytes
[ 5] 10.00-11.00 sec 6.75 MBytes 56.6 Mbits/sec 0 2.93 MBytes
[ 5] 11.00-12.00 sec 3.00 MBytes 25.2 Mbits/sec 0 3.10 MBytes
[ 5] 12.00-13.00 sec 6.75 MBytes 56.6 Mbits/sec 0 3.41 MBytes
[ 5] 13.00-14.00 sec 5.75 MBytes 48.2 Mbits/sec 0 3.61 MBytes
[ 5] 14.00-15.00 sec 4.25 MBytes 35.7 Mbits/sec 0 3.81 MBytes
[ 5] 15.00-16.00 sec 5.75 MBytes 48.2 Mbits/sec 0 3.81 MBytes
[ 5] 16.00-17.00 sec 4.38 MBytes 36.7 Mbits/sec 0 4.07 MBytes
[ 5] 17.00-18.00 sec 5.88 MBytes 49.3 Mbits/sec 0 4.07 MBytes
[ 5] 18.00-19.00 sec 2.75 MBytes 23.1 Mbits/sec 0 4.07 MBytes
[ 5] 19.00-20.00 sec 3.38 MBytes 28.3 Mbits/sec 3 2.86 MBytes
[ 5] 20.00-21.00 sec 2.88 MBytes 24.1 Mbits/sec 0 2.94 MBytes
[ 5] 21.00-22.00 sec 1.25 MBytes 10.5 Mbits/sec 0 3.10 MBytes
[ 5] 22.00-23.00 sec 5.50 MBytes 46.1 Mbits/sec 0 3.44 MBytes
[ 5] 23.00-24.00 sec 5.50 MBytes 46.1 Mbits/sec 0 3.63 MBytes
[ 5] 24.00-25.00 sec 4.50 MBytes 37.7 Mbits/sec 0 3.64 MBytes
[ 5] 25.00-26.00 sec 4.25 MBytes 35.7 Mbits/sec 0 3.64 MBytes
[ 5] 26.00-27.00 sec 5.62 MBytes 47.2 Mbits/sec 0 3.86 MBytes
[ 5] 27.00-28.00 sec 6.62 MBytes 55.6 Mbits/sec 0 3.86 MBytes
[ 5] 28.00-29.00 sec 5.50 MBytes 46.1 Mbits/sec 0 3.86 MBytes
[ 5] 29.00-30.00 sec 4.88 MBytes 40.8 Mbits/sec 0 3.86 MBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-30.00 sec 150 MBytes 41.9 Mbits/sec 3 sender
[ 5] 0.00-30.32 sec 150 MBytes 41.5 Mbits/sec receiver

iperf Done.
</syntaxhighlight>

== Bluetooth ==
'''''Note:''''' This Bluetooth section was tested with the iMX91 Industrial Module in Max and Pro configurations. For Basic configuration, bluetooth capabilities are not available. For more information see [[iMX91 Industrial Development Kit|the iMX91 Industrial Module comparison]]. 

'''''Input:''''' None 
'''''Output:''''' Remote device is recognized after scan 

'''''Note:''''' For iMX91 Industrial Module Max (u-blox MAYA-W260-00B assembled) please use instead of <syntaxhighlight lang="bash">hciattach /dev/ttyLP7 any 3000000 flow</syntaxhighlight> command <syntaxhighlight lang="bash">hciattach /dev/ttyLP7 any 115200 flow</syntaxhighlight> in below code
<syntaxhighlight lang="bash">
# attach necessary modules
root@imx91-voipac:~# modprobe moal mod_para=nxp/wifi_mod_para.conf
root@imx91-voipac:~# modprobe hci_uart
root@imx91-voipac:~# hciattach /dev/ttyLP7 any 3000000 flow
Device setup complete
root@imx91-voipac:~# [ 1207.472299] Bluetooth: MGMT ver 1.22
[ 1207.485171] NET: Registered PF_ALG protocol family

# put hci0 device up
root@imx91-voipac:~# hciconfig hci0 up

# scan for remote bluetooth devices (enable bluetooth on phone and make it discoverable)
root@imx91-voipac:~# hcitool scan
Scanning ...
Devices:
hci0 00:0D:18:01:5A:B3
</syntaxhighlight>

== Ethernet ==
'''''Note:''''' This section was tested with the iMX91 Industrial Module in Max configuration which includes dual Gigabit Ethernet PHY. The Pro configuration includes single Gigabit Ethernet PHY. For the Basic configuration, Ethernet capabilities are not available. For more information see [[iMX91 Industrial Development Kit|the iMX91 Industrial Module comparison]]. 

'''''Input:''''' None 
'''''Output:''''' Device driver is available (for Pro configuration only one ethernet is available) 
'''''Note:''''' MAC address should be identical with the address on the sticker placed on the board
<syntaxhighlight lang="bash">

root@imx91-voipac:~# ip addr show dev eth0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:0d:15:01:8c:ae brd ff:ff:ff:ff:ff:ff
inet 192.168.1.33/24 metric 10 brd 192.168.1.255 scope global dynamic eth0
valid_lft 86378sec preferred_lft 86378sec
inet6 fe80::20d:15ff:fe01:8cae/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
root@imx91-voipac:~# ip addr show dev eth1
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:0d:15:01:8c:af brd ff:ff:ff:ff:ff:ff
inet 192.168.1.34/24 metric 10 brd 192.168.1.255 scope global dynamic eth1
valid_lft 86391sec preferred_lft 86391sec
inet6 fe80::20d:15ff:fe01:8caf/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
root@imx91-voipac:~#
</syntaxhighlight>

'''''Input:''''' Plug Ethernet cable into top or bottom connector for the Max configuration. Plug Ethernet cable into bottom connector for the Pro configuration. 
'''''Output:''''' IPv4 address is assigned
<syntaxhighlight lang="bash">
[ 1599.750399] fec 42890000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[ 1630.695671] imx-dwmac 428a0000.ethernet eth1: Link is Up - 1Gbps/Full - flow control off
</syntaxhighlight>

=== Performance ===
iPerf3 was used to test the Ethernet performance. 
'''''Note:''''' The Max configuration of the iMX91 Industrial Module includes dual Gigabit Ethernet PHY. The Pro configuration includes single Gigabit Ethernet PHY. 
'''''Input:''''' Start iPerf3 on computer using command <syntaxhighlight lang="bash">iperf3 -s </syntaxhighlight>
'''''Output:''''' Verify performance on board (argument after -c is IP address of your computer) 

<syntaxhighlight lang="bash">
root@imx91-voipac:~# iperf3 -c 192.168.240.120 -t 10 -i 1
Connecting to host 192.168.240.120, port 5201
[ 5] local 192.168.240.32 port 57734 connected to 192.168.240.120 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 114 MBytes 951 Mbits/sec 0 358 KBytes
[ 5] 1.00-2.00 sec 112 MBytes 943 Mbits/sec 0 358 KBytes
[ 5] 2.00-3.00 sec 112 MBytes 938 Mbits/sec 0 358 KBytes
[ 5] 3.00-4.00 sec 113 MBytes 947 Mbits/sec 0 393 KBytes
[ 5] 4.00-5.00 sec 112 MBytes 941 Mbits/sec 0 393 KBytes
[ 5] 5.00-6.00 sec 112 MBytes 944 Mbits/sec 0 393 KBytes
[ 5] 6.00-7.00 sec 112 MBytes 940 Mbits/sec 0 516 KBytes
[ 5] 7.00-8.00 sec 112 MBytes 943 Mbits/sec 0 516 KBytes
[ 5] 8.00-9.00 sec 112 MBytes 942 Mbits/sec 0 516 KBytes
[ 5] 9.00-10.00 sec 113 MBytes 946 Mbits/sec 0 516 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 1.10 GBytes 943 Mbits/sec 0 sender
[ 5] 0.00-10.05 sec 1.10 GBytes 937 Mbits/sec receiver

iperf Done.
root@imx91-voipac:~#

</syntaxhighlight>

== USB 2.0 ==
NOTE: Perform read/write performance test 
'''''Input:''''' Plug USB flash drive into USB connector 
'''''Output:''''' Plugged USB device is listed
<syntaxhighlight lang="bash">
root@imx91-voipac:~# lsusb
Bus 001 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 125f:d31a A-DATA Technology Co., Ltd.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
</syntaxhighlight>

'''''Input:''''' Generate a dummy file and copy it into USB flash drive 
'''''Output:''''' Generated file and copied file have the same checksum
<syntaxhighlight lang="bash">
root@imx91-voipac:~# mount /dev/sda1 /media/
root@imx91-voipac:~# rm -f file.txt /media/file.txt
root@imx91-voipac:~# dd if=/dev/urandom of=file.txt count=1024 bs=1024
1024+0 records in
1024+0 records out
root@imx91-voipac:~# cp file.txt /media/
root@imx91-voipac:~# md5sum file.txt /media/file.txt
200a9fd3e9850fcedf85ed50d4c4733d file.txt
200a9fd3e9850fcedf85ed50d4c4733d /media/file.txt
root@imx91-voipac:~# rm file.txt /media/file.txt
root@imx91-voipac:~# umount /media
</syntaxhighlight>

== USB-C ==
This connector is primarily used for flashing new binaries into the iMX91 Industrial Module. More information can be found on the dedicated [[iMX91 Industrial Flashing Procedure|module flashing page]]. 

== USB Micro-B serial console ==
'''''Input:''''' Connect USB console cable into the base board connector and open serial console with baud rate 115200 8n1 
'''''Output:''''' The board is controlled and responsive to serial terminal commands
<syntaxhighlight lang="bash">
root@imx91-voipac:~# uname -a
Linux imx91-voipac 6.6.36-lts-next-g2e3e2e65d92a #1 SMP PREEMPT Wed Sep 4 08:22:45 UTC 2024 aarch64 GNU/Linux
</syntaxhighlight>

== UART serial console ==
Serial console is utilized via USB Micro-B connector by default. Alternatively, the communication can be established using UART headers and TTL-232R-3V3 - FTDI cable. 
NOTE: Describe jumpers position 
[[File:iMX93 Industrial Development Kit-Serial console via UART1.png|800px]] 

'''''Note:''''' Usage of UART2 CONSOLE to communicate by default requires changes in Yocto binaries and new compilation of image files. 
[[File:iMX93 Industrial Development Kit-Serial console via UART2.png|800px]]

== SD Card ==
NOTE: Perform detection of SD Card
<syntaxhighlight lang="bash">
root@imx91-voipac:~# fdisk -l
Disk /dev/mmcblk0: 15 GB, 15758000128 bytes, 30777344 sectors
240448 cylinders, 4 heads, 32 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type
/dev/mmcblk0p1 * 128,0,1 1023,3,32 16384 186775 170392 83.1M c Win95 FAT32 (LBA)
/dev/mmcblk0p2 1023,3,32 1023,3,32 196608 939761 743154 362M 83 Linux
Disk /dev/mmcblk0boot0: 4 MB, 4194304 bytes, 8192 sectors
128 cylinders, 4 heads, 16 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Disk /dev/mmcblk0boot1: 4 MB, 4194304 bytes, 8192 sectors
128 cylinders, 4 heads, 16 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Disk /dev/mmcblk1: 15 GB, 15931539456 bytes, 31116288 sectors
243096 cylinders, 4 heads, 32 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type
/dev/mmcblk1p1 512,0,1 1023,3,32 65536 266255 200720 98.0M 83 Linux
</syntaxhighlight>

/dev/mmcblk1 is SD card (mmcblk0 is eMMC)

== JTAG ==
[[File:iMX93 Industrial Development Kit-JTAG communication setup.png|800px]] 
To verify that i.MX93 CPU JTAG is functional, following command identifies and connects to the CPU's debug point:
<syntaxhighlight lang="bash">
J-Link> jtagid
</syntaxhighlight>

[[File:J-Link MIMX9352 A55 1.png|800px]] 
[[File:J-Link MIMX9352 M33.png|800px]]

== Real Time Clock ==
RTC chip is detected by Linux kernel after start-up:
<syntaxhighlight lang="bash">
root@imx91-voipac:~# dmesg | grep rtc
[ 0.894414] imx-drm display-subsystem: bound imx-lcdifv3-crtc.0 (ops lcdifv3_crtc_ops)
[ 0.910506] imx-drm display-subsystem: [drm] Cannot find any crtc or sizes
[ 1.209418] bbnsm_rtc 44440000.bbnsm:rtc: registered as rtc0
[ 1.215749] bbnsm_rtc 44440000.bbnsm:rtc: setting system clock to 1970-01-01T00:00:00 UTC (0)
root@imx91-voipac:~#
</syntaxhighlight>

CPU correctly recognises RTC on the I2C1 bus, the chip is under usage by the kernel:
<syntaxhighlight lang="bash">
root@imx91-voipac:~# i2cdetect -r -y 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- UU -- -- -- UU -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- 3d -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- UU -- UU -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
</syntaxhighlight>

Set up the current date and time, show the actual values

Setup date and time
<syntaxhighlight lang="bash">
date -s "2025-8-13 14:52:26"
</syntaxhighlight>

Show actual values
<syntaxhighlight lang="bash">
root@imx91-voipac:~# timedatectl
[ 134.509782] kauditd_printk_skb: 8 callbacks suppressed
[ 134.509793] audit: type=1334 audit(1732625725.140:18): prog-id=19 op=LOAD
[ 134.523935] audit: type=1334 audit(1732625725.148:19): prog-id=20 op=LOAD
[ 134.531609] audit: type=1334 audit(1732625725.152:20): prog-id=21 op=LOAD
Local time: Tue 2024-11-26 12:55:25 UTC
Universal time: Tue 2024-11-26 12:55:25 UTC
RTC time: Tue 2024-11-26 12:55:25
Time zone: UTC (UTC, +0000)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no
</syntaxhighlight>

== I2C EEPROM Memory - on module ==
'''''Input:''''' Power on board 
'''''Output:''''' Store some data to eeprom and after reboot read it back and should be same 

<syntaxhighlight lang="bash">
# store random 8bytes to eeprom
root@imx91-voipac-evk:~# dd if=/dev/urandom of=/sys/bus/i2c/devices/0-0050/eeprom bs=8 count=1
+1 records in
0+1 records out
8 bytes copied, 0.0225523 s, 0.4 kB/s
</syntaxhighlight>

After board reboot:
<syntaxhighlight lang="bash">
# store random 8bytes to eeprom
root@imx91-voipac-evk:~# hexdump -n8 /sys/bus/i2c/devices/0-0050/eeprom
0000000 c4dd 4eda d624 535e
0000008
</syntaxhighlight>

== Reset button ==
'''''Input:''''' Press the RESET button 
'''''Output:''''' The board will execute bootloader immediately with "Reset cause: POR" 
'''''Note:''''' iMX91 Industrial Development Kit should never freeze or hang after the reset button was pressed. Testing the operation 10 times gives a reliable result
<syntaxhighlight lang="bash">
U-Boot 2023.04+gf8a2983ec8+p0 (Mar 04 2024 - 07:25:04 +0000)

CPU: i.MX93(52) rev1.1 1700 MHz (running at 1692 MHz)
CPU: Industrial temperature grade (-40C to 105C) at 45C
Reset cause: POR (0x1)
Model: NXP i.MX93 Voipac EVK board
DRAM: 2 GiB
Core: 215 devices, 32 uclasses, devicetree: separate
MMC: FSL_SDHC: 0, FSL_SDHC: 1
Loading Environment from MMC... OK
[*]-Video Link 0fail to find output device

....
</syntaxhighlight>

== On/Off button ==
'''''Input:''''' Press and hold On/Off button for more then 5 seconds 
'''''Output:''''' The board will be powered off

Press shortly the On/Off button again, the board will be powered on.

== Sleep Mode ==
'''''Input:''''' Type command:
<syntaxhighlight lang="bash">
echo mem > /sys/power/state
</syntaxhighlight>

'''''Output:''''' The board will go into a frozen state and the serial console will not respond to inputs.

Shortly press the Up user button, to wake the board up again.

[[File:imx93_sleep_mode.png|740px]] 

== User buttons ==
'''''Input:''''' Press Enter/Left/Right/Up/Down buttons 
'''''Output:''''' Button events 1 and 0 are generated
<syntaxhighlight lang="bash">
root@imx91-voipac-evk:~# evtest /dev/input/by-path/platform-gpio-buttons-event
Input driver version is 1.0.1
Input device ID: bus 0x19 vendor 0x1 product 0x1 version 0x100
Input device name: "gpio-buttons"
Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
Event code 28 (KEY_ENTER)
Event code 103 (KEY_UP)
Event code 105 (KEY_LEFT)
Event code 106 (KEY_RIGHT)
Event code 108 (KEY_DOWN)
Properties:
Testing ... (interrupt to exit)
Event: time 1717485486.586413, type 1 (EV_KEY), code 103 (KEY_UP), value 1
Event: time 1717485486.586413, -------------- SYN_REPORT ------------
Event: time 1717485486.682265, type 1 (EV_KEY), code 103 (KEY_UP), value 0
Event: time 1717485486.682265, -------------- SYN_REPORT ------------
Event: time 1717485487.255120, type 1 (EV_KEY), code 108 (KEY_DOWN), value 1
Event: time 1717485487.255120, -------------- SYN_REPORT ------------
Event: time 1717485487.367126, type 1 (EV_KEY), code 108 (KEY_DOWN), value 0
Event: time 1717485487.367126, -------------- SYN_REPORT ------------
Event: time 1717485488.539564, type 1 (EV_KEY), code 106 (KEY_RIGHT), value 1
Event: time 1717485488.539564, -------------- SYN_REPORT ------------
Event: time 1717485488.677501, type 1 (EV_KEY), code 106 (KEY_RIGHT), value 0
Event: time 1717485488.677501, -------------- SYN_REPORT ------------
Event: time 1717485488.897627, type 1 (EV_KEY), code 105 (KEY_LEFT), value 1
Event: time 1717485488.897627, -------------- SYN_REPORT ------------
Event: time 1717485489.013136, type 1 (EV_KEY), code 105 (KEY_LEFT), value 0
Event: time 1717485489.013136, -------------- SYN_REPORT ------------
Event: time 1717485489.264589, type 1 (EV_KEY), code 28 (KEY_ENTER), value 1
Event: time 1717485489.264589, -------------- SYN_REPORT ------------
Event: time 1717485489.372584, type 1 (EV_KEY), code 28 (KEY_ENTER), value 0
Event: time 1717485489.372584, -------------- SYN_REPORT ------------
</syntaxhighlight>

== User LED ==
'''''Input:''''' None 
'''''Output:''''' Script switches User LED on baseboard ON and OFF in one second intervals
<syntaxhighlight lang="bash">
#!/bin/sh

LED=/sys/class/leds/user_sbc

while true; do
echo 0 > ${LED}/brightness
sleep 1
echo 1 > ${LED}/brightness
sleep 1
done
</syntaxhighlight>

'''''Input:''''' None 
'''''Output:''''' User LED on baseboard is set to heartbeat blinking sequence
<syntaxhighlight lang="bash">
root@imx91-voipac-evk:~# echo heartbeat > /sys/class/leds/user_sbc/trigger
</syntaxhighlight>

'''''Input:''''' None 
'''''Output:''''' User LED on SOM is set to heartbeat blinking sequence
<syntaxhighlight lang="bash">
root@imx91-voipac-evk:~# echo heartbeat > /sys/class/leds/user_som/trigger
</syntaxhighlight>

iMX91 Industrial Accessing and Testing Peripherals

2025-10-30T10:24:17Z

Voipac-sw:

[[Category:iMX91 Industrial]]
[[Category:iMX91 Industrial Software]]
[[Category:iMX91 Industrial Testing]]
[[Category:iMX91 Industrial Peripherals]]

<div style="float:right">__TOC__</div>

The initial operations with the iMX91 Industrial Development Kit interfaces are presented on this page. For more specific information such as display options, camera capabilities or industrial modular extensions, refer to the dedicated [[iMX91 Industrial Max#Peripherals_and_Accessories|Peripherals and Accessories section]].

== Mandatory components ==
=== Hardware ===
* iMX91 Industrial Module
* iMX Development Baseboard
* [https://www.voipac.com/power-supply-5v-20w DC power supply (5V, 4A, 20W)]

=== Peripherals and Accessories ===
* [https://wiki.voipac.com/index.php?title=NXP_Parallel_TFT_Display_Set NXP Parallel TFT Display Set]
* [https://www.voipac.com/imx9-wifi-and-bluetooth-antennas-set iMX9 Wifi and Bluetooth antenna set]
* 1x MicroSDHC card Class 10 or higher
* 1x USB Flash drive 2.0
* Headphones
* Analog external microphone

=== Cables ===
* USB Micro-B cable for serial console
* USB-C cable for module flashing
* Ethernet cable

== Audio ==
'''''Note:''''' This audio section was tested with the iMX91 Industrial Module in Max and Pro configurations. For Basic configuration, audio capabilities are not available. For more information see [[iMX91 Industrial Development Kit|the iMX91 Industrial Module comparison]]. 

'''''Input:''''' Search kernel log for wm8904 chip 
'''''Output:''''' Audio chip is detected and bound as an output and input device
<syntaxhighlight lang="bash">
root@imx91-voipac:~# dmesg | grep wm8904
[ 6.546858] wm8904 0-001a: supply DCVDD not found, using dummy regulator
[ 6.591866] wm8904 0-001a: supply DBVDD not found, using dummy regulator
[ 6.611921] wm8904 0-001a: supply AVDD not found, using dummy regulator
[ 6.637768] wm8904 0-001a: supply CPVDD not found, using dummy regulator
[ 6.670934] wm8904 0-001a: supply MICVDD not found, using dummy regulator
[ 6.683500] wm8904 0-001a: revision A
</syntaxhighlight>

'''''Input:''''' Run amixer command 
'''''Output:''''' Current audio chip settings are displayed
<syntaxhighlight lang="bash">
root@imx91-voipac:~# amixer
Simple mixer control 'Headphone',0
Capabilities: volume pswitch
Playback channels: Front Left - Front Right
Capture channels: Front Left - Front Right
Limits: 0 - 63
Front Left: 45 [71%] [-12.00dB] Playback [on]
Front Right: 45 [71%] [-12.00dB] Playback [on]
Simple mixer control 'Headphone ZC',0
Capabilities: pswitch
Playback channels: Front Left - Front Right
Mono:
Front Left: Playback [on]
Front Right: Playback [on]
Simple mixer control 'Line Output',0
Capabilities: volume pswitch
Playback channels: Front Left - Front Right
Capture channels: Front Left - Front Right
Limits: 0 - 63
Front Left: 57 [90%] [0.00dB] Playback [on]
Front Right: 57 [90%] [0.00dB] Playback [on]
...
</syntaxhighlight>

'''''Input:''''' Connect headphones into LINE OUT jack connector 
'''''Output:''''' Audio file is played and heard
<syntaxhighlight lang="bash">
root@imx8mq-voipac:~# aplay /usr/share/multimedia/sample.wav
Playing WAVE 'multimedia/sample.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
root@imx8mq-voipac:~# aplay -D sysdefault:CARD=wm8904audio /usr/share/multimedia/sample.wav
Playing WAVE 'multimedia/sample.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
</syntaxhighlight>

'''''Input:''''' Plug headphones into HEADPHONES jack connector and analog external microphone to MIC jack connector 
'''''Output:''''' Sound recorder by microphone is played in headphones
<syntaxhighlight lang="bash">
root@imx91-voipac:~# amixer set 'Capture' '31'
root@imx91-voipac:~# amixer set 'Capture Input' ADC
root@imx91-voipac:~# amixer set 'Left Capture Inverting Mux' 'IN2L'
root@imx91-voipac:~# amixer set 'Right Capture Inverting Mux' 'IN2R'
root@imx91-voipac:~# arecord -D sysdefault:CARD=wm8904audio -t wav -f cd | aplay -D sysdefault:CARD=wm8904audio
</syntaxhighlight>

'''''Note:''''' Microphone and headphones setup can also be graphically displayed and adjusted:
<syntaxhighlight lang="bash">
root@imx91-voipac:~# alsamixer
</syntaxhighlight>
[[image:iMX8M_Industrial_Development_Kit-AlsaMixer_setup.png|800px]] 

'''''Input:''''' Verify digital microphones (Mic Left, Mic Mid, Mic Right) 
'''''Output:''''' Microphone sound is played in headphones
<syntaxhighlight lang="bash">
root@imx91-voipac:~# amixer set "Capture Input" "DMIC"
root@imx91-voipac:~# arecord -D sysdefault:CARD=wm8904audio -t wav -f cd | aplay -D sysdefault:CARD=wm8904audio
</syntaxhighlight>

== WiFi ==
'''''Note:''''' This WiFi section was tested with the iMX91 Industrial Module in Max and Pro configurations. For Basic configurations, wireless connectivity is not available. For more information see [[iMX91 Industrial Development Kit|the iMX91 Industrial Module comparison]]. 

Load the device driver:
<syntaxhighlight lang="bash">
root@imx91-voipac:~# modprobe moal mod_para=nxp/wifi_mod_para.conf
[ 926.305344] mlan: loading out-of-tree module taints kernel.
[ 926.334171] wlan: Loading MWLAN driver
[ 926.339152] wlan: Register to Bus Driver...
[ 926.343686] vendor=0x02DF device=0x9159 class=0 function=1
[ 926.349765] Attach moal handle ops, card interface type: 0x108
[ 926.355633] rps set to 0 from module param
[ 926.362045] SDIW416: init module param from usr cfg
[ 926.366995] card_type: SDIW416, config block: 0
[ 926.371541] cfg80211_wext=0xf
[ 926.374515] max_vir_bss=1
[ 926.377131] cal_data_cfg=none
[ 926.380112] ps_mode = 1
[ 926.382567] auto_ds = 1
[ 926.385010] host_mlme=enable
[ 926.387895] fw_name=nxp/sdiouartiw416_combo_v0.bin
[ 926.392709] SDIO: max_segs=128 max_seg_size=65535
[ 926.397420] rx_work=1 cpu_num=2
[ 926.400569] Enable moal_recv_amsdu_packet
[ 926.404600] Attach mlan adapter operations.card_type is 0x108.
[ 926.410826] wlan: Enable TX SG mode
[ 926.414357] wlan: Enable RX SG mode
[ 926.421681] Request firmware: nxp/sdiouartiw416_combo_v0.bin
[ 926.708639] Wlan: FW download over, firmwarelen=591808 downloaded 583072
[ 928.113594] WLAN FW is active
[ 928.116573] on_time is 927947046442
[ 928.140994] VDLL image: len=8736
[ 928.144352] FW country code WW does not match with US
[ 928.150617] fw_cap_info=0x187ccf03, dev_cap_mask=0xffffffff
[ 928.156607] max_p2p_conn = 8, max_sta_conn = 8
[ 928.176236] Register NXP 802.11 Adapter mlan0
[ 928.183724] Register NXP 802.11 Adapter uap0
[ 928.194033] Register NXP 802.11 Adapter wfd0
[ 928.199986] wlan: version = SDIW416---16.92.21.p137.2-MM6X16437.p30-GPL-(FP92)
[ 928.208947] wlan: Register to Bus Driver Done
[ 928.216412] wlan: Driver loaded successfully
</syntaxhighlight>

Check if the WiFi interface is present:
<syntaxhighlight lang="bash">
root@imx91-voipac:~# ip addr show dev mlan0
3: wlp1s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 78:c4:0e:a0:32:16 brd ff:ff:ff:ff:ff:ff
</syntaxhighlight>

'''''Input:''''' Scan the available WiFi networks 
'''''Output:''''' Networks are scanned and in-depth information are displayed 
<syntaxhighlight lang="bash">
root@imx91-voipac:~# ifconfig mlan0 up && iw dev mlan0 scan
BSS 94:27:90:7f:c3:d3(on wlp1s0)
TSF: 1213185029341 usec (14d, 00:59:45)
freq: 2442
beacon interval: 100 TUs
capability: ESS Privacy ShortPreamble ShortSlotTime (0x0431)
signal: -73.00 dBm
last seen: 4056 ms ago
SSID: HH40V_C3D3
Supported rates: 1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0
DS Parameter set: channel 7
Country: SK Environment: Indoor/Outdoor
Channels [1 - 13] @ 20 dBm
ERP: <no flags>
Extended supported rates: 24.0 36.0 48.0 54.0
HT capabilities:
Capabilities: 0x1ad
RX LDPC
HT20
SM Power Save disabled
RX HT20 SGI
TX STBC
RX STBC 1-stream
Max AMSDU length: 3839 bytes
No DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 8 usec (0x06)
HT TX/RX MCS rate indexes supported: 0-15
HT operation:
* primary channel: 7
* secondary channel offset: no secondary
* STA channel width: 20 MHz
* RIFS: 1
* HT protection: no
* non-GF present: 1
* OBSS non-GF present: 0
* dual beacon: 0
* dual CTS protection: 0
* STBC beacon: 0
* L-SIG TXOP Prot: 0
* PCO active: 0
* PCO phase: 0
Overlapping BSS scan params:
* passive dwell: 20 TUs
* active dwell: 10 TUs
* channel width trigger scan interval: 300 s
* scan passive total per channel: 200 TUs
* scan active total per channel: 20 TUs
* BSS width channel transition delay factor: 5
* OBSS Scan Activity Threshold: 0.25 %
Extended capabilities:
* HT Information Exchange Supported
* Extended Channel Switching
* SSID List
* Operating Mode Notification
WMM: * Parameter version 1
* BE: CW 15-1023, AIFSN 3
* BK: CW 15-1023, AIFSN 7
* VI: CW 7-15, AIFSN 2, TXOP 3008 usec
* VO: CW 3-7, AIFSN 2, TXOP 1504 usec
RSN: * Version: 1
* Group cipher: CCMP
* Pairwise ciphers: CCMP
* Authentication suites: PSK
* Capabilities: 1-PTKSA-RC 1-GTKSA-RC (0x0000)
WPS: * Version: 1.0
* Wi-Fi Protected Setup State: 2 (Configured)
* Response Type: 3 (AP)
* UUID: 87654321-9abc-def0-1234-942790c36dc7
* Manufacturer: TCL.org
* Model: WAP
* Model Number: 123
* Serial Number: 12345
* Primary Device Type: 6-0050f204-1
* Device name: TCL AP
* Config methods:
* Unknown TLV (0x1049, 6 bytes): 00 37 2a 00 01 20
BSS 34:e8:94:5c:06:80(on wlp1s0)
TSF: 787677017722 usec (9d, 02:47:57)
freq: 2462
beacon interval: 100 TUs
capability: ESS Privacy ShortSlotTime (0x0411)
signal: -73.00 dBm
last seen: 3952 ms ago
SSID: OrangeFlybox_0680
Supported rates: 1.0* 2.0* 5.5* 11.0* 9.0 18.0 36.0 54.0
DS Parameter set: channel 11
ERP: Barker_Preamble_Mode
Extended supported rates: 6.0 12.0 24.0 48.0
HT capabilities:
Capabilities: 0x106e
HT20/HT40
SM Power Save disabled
RX HT20 SGI
RX HT40 SGI
No RX STBC
Max AMSDU length: 3839 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 4 usec (0x05)
HT RX MCS rate indexes supported: 0-15, 32
HT TX MCS rate indexes are undefined
HT operation:
* primary channel: 11
* secondary channel offset: no secondary
* STA channel width: 20 MHz
* RIFS: 0
* HT protection: 20 MHz
* non-GF present: 1
* OBSS non-GF present: 0
* dual beacon: 0
* dual CTS protection: 0
* STBC beacon: 0
* L-SIG TXOP Prot: 0
* PCO active: 0
* PCO phase: 0
WPA: * Version: 1
* Group cipher: TKIP
* Pairwise ciphers: TKIP CCMP
* Authentication suites: PSK
RSN: * Version: 1
* Group cipher: TKIP
* Pairwise ciphers: TKIP CCMP
* Authentication suites: PSK
* Capabilities: 1-PTKSA-RC 1-GTKSA-RC (0x0000)
WMM: * Parameter version 1
* BE: CW 15-1023, AIFSN 3
* BK: CW 15-1023, AIFSN 7
* VI: CW 7-15, AIFSN 2, TXOP 3008 usec
* VO: CW 3-7, AIFSN 2, TXOP 1504 usec
BSS Load:
* station count: 3
* channel utilisation: 27/255
* available admission capacity: 31250 [*32us]
Overlapping BSS scan params:
* passive dwell: 20 TUs
* active dwell: 10 TUs
* channel width trigger scan interval: 300 s
* scan passive total per channel: 200 TUs
* scan active total per channel: 20 TUs
* BSS width channel transition delay factor: 5
* OBSS Scan Activity Threshold: 0.25 %
Extended capabilities:
* HT Information Exchange Supported
WPS: * Version: 1.0
* Wi-Fi Protected Setup State: 2 (Configured)
* AP setup locked: 0x01
* Response Type: 3 (AP)
* UUID: 38833092-3092-1883-9c77-34e8945c06c4
* Manufacturer: TP-LINK
* Model: Archer MR200
* Model Number: 1.0
* Serial Number: 1.0
* Primary Device Type: 6-0050f204-1
* Device name: AC750 Wireless Dual Band 4G LTE
* Config methods: Label, Display, Keypad
* RF Bands: 0x1
* Unknown TLV (0x1049, 6 bytes): 00 37 2a 00 01 20
BSS 34:e8:94:5b:f8:04(on wlp1s0)
TSF: 1210179077454 usec (14d, 00:09:39)
freq: 2462
beacon interval: 100 TUs
capability: ESS Privacy ShortSlotTime (0x0411)
signal: -50.00 dBm
last seen: 3432 ms ago
SSID: REDARROW
Supported rates: 1.0* 2.0* 5.5* 11.0* 9.0 18.0 36.0 54.0
DS Parameter set: channel 11
Extended supported rates: 6.0 12.0 24.0 48.0
TIM: DTIM Count 0 DTIM Period 1 Bitmap Control 0x0 Bitmap[0] 0x2
WPS: * Version: 1.0
* Wi-Fi Protected Setup State: 2 (Configured)
* AP setup locked: 0x01
* UUID: 38833092-3092-1883-9c77-34e8945bf8c4
* RF Bands: 0x1
* Unknown TLV (0x1049, 6 bytes): 00 37 2a 00 01 20
ERP: Barker_Preamble_Mode
HT capabilities:
Capabilities: 0x106e
HT20/HT40
SM Power Save disabled
RX HT20 SGI
RX HT40 SGI
No RX STBC
Max AMSDU length: 3839 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 4 usec (0x05)
HT RX MCS rate indexes supported: 0-15, 32
HT TX MCS rate indexes are undefined
HT operation:
* primary channel: 11
* secondary channel offset: no secondary
* STA channel width: 20 MHz
* RIFS: 0
* HT protection: no
* non-GF present: 0
* OBSS non-GF present: 0
* dual beacon: 0
* dual CTS protection: 0
* STBC beacon: 0
* L-SIG TXOP Prot: 0
* PCO active: 0
* PCO phase: 0
Overlapping BSS scan params:
* passive dwell: 20 TUs
* active dwell: 10 TUs
* channel width trigger scan interval: 300 s
* scan passive total per channel: 200 TUs
* scan active total per channel: 20 TUs
* BSS width channel transition delay factor: 5
* OBSS Scan Activity Threshold: 0.25 %
Extended capabilities:
* HT Information Exchange Supported
WPA: * Version: 1
* Group cipher: TKIP
* Pairwise ciphers: TKIP CCMP
* Authentication suites: PSK
RSN: * Version: 1
* Group cipher: TKIP
* Pairwise ciphers: TKIP CCMP
* Authentication suites: PSK
* Capabilities: 1-PTKSA-RC 1-GTKSA-RC (0x0000)
WMM: * Parameter version 1
* BE: CW 15-1023, AIFSN 3
* BK: CW 15-1023, AIFSN 7
* VI: CW 7-15, AIFSN 2, TXOP 3008 usec
* VO: CW 3-7, AIFSN 2, TXOP 1504 usec
BSS Load:
* station count: 0
* channel utilisation: 47/255
* available admission capacity: 31250 [*32us]
</syntaxhighlight>

To set up the network login data, edit file located in /etc/wpa_supplicant.conf and update '''''ssid''''' and passphrase '''''psk''''' fields.

<syntaxhighlight lang="bash">
root@imx91-voipac:~# cat /etc/wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
update_config=1

network={
ssid="SSID_FOR_WIFI_NETWORK"
scan_ssid=1
key_mgmt=WPA-PSK
psk="WIFI_NETWORK_PASSWORD"
}

</syntaxhighlight>

To connect to the desired WiFi network, start wpa_supplicant:
<syntaxhighlight lang="bash">
root@imx91-voipac:~# wpa_supplicant -D nl80211 -i mlan0 -c /etc/wpa_supplicant.conf &
root@imx91-voipac:~# rfkill: Cannot open RFKILL control device
[ 261.722718] wlan: mlan0 START SCAN
[ 266.018892] wlan: SCAN COMPLETED: scanned AP count=1
mlan0: SME: Trying to authentica[ 266.027303] wlan: HostMlme mlan0 send auth to bssid 40:XX:XX:XX:70:62
te with 40:a5:ef:c0:70:62 (SSID='WifiPoschodie' f[ 266.037546] mlan0:
req=2437 MHz)
[ 266.037558] wlan: HostMlme Auth received from 40:XX:XX:XX:70:62
mlan0: Trying to associate with 40:a5:ef:c0:70:62 (SSID='WifiPoschodie' freq=2437 MHz)
[ 266.057956] wlan: HostMlme mlan0 Connected to bssid 40:XX:XX:XX:70:62 successfully
mlan0: Associated[ 266.067323] mlan0:
with 40:a5:ef:c0[ 266.067340] wlan: Send EAPOL pkt to 40:XX:XX:XX:70:62
</syntaxhighlight>

To obtain an IP address and other network settings, run dhcp client:
<syntaxhighlight lang="bash">
udhcpc -i mlan0
</syntaxhighlight>

At this point the bandwidth measurement can be tested, showing that WiFi connection was established and is performed very reliably.
Used program: [https://iperf.fr iPerf3.] 

'''''Configuration:''''' iMX91 Industrial Module Pro in Industrial temperature range (u-blox MAYA-W160-00B assembled):
<syntaxhighlight lang="bash">
root@imx91-voipac:~# iperf3 -c 192.168.240.200 -t 30 -i1
Connecting to host 192.168.240.200, port 5201
[ 5] local 192.168.240.111 port 39988 connected to 192.168.240.200 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 5.12 MBytes 43.0 Mbits/sec 0 223 KBytes
[ 5] 1.00-2.00 sec 5.38 MBytes 45.1 Mbits/sec 0 460 KBytes
[ 5] 2.00-3.00 sec 7.12 MBytes 59.8 Mbits/sec 0 747 KBytes
[ 5] 3.00-4.00 sec 4.25 MBytes 35.7 Mbits/sec 0 1003 KBytes
[ 5] 4.00-5.00 sec 5.38 MBytes 45.1 Mbits/sec 0 1.25 MBytes
[ 5] 5.00-6.00 sec 5.50 MBytes 46.1 Mbits/sec 0 1.52 MBytes
[ 5] 6.00-7.00 sec 5.50 MBytes 46.1 Mbits/sec 0 1.78 MBytes
[ 5] 7.00-8.00 sec 5.62 MBytes 47.2 Mbits/sec 0 2.06 MBytes
[ 5] 8.00-9.00 sec 5.50 MBytes 46.1 Mbits/sec 0 2.31 MBytes
[ 5] 9.00-10.00 sec 5.50 MBytes 46.1 Mbits/sec 0 2.64 MBytes
[ 5] 10.00-11.00 sec 6.75 MBytes 56.6 Mbits/sec 0 2.93 MBytes
[ 5] 11.00-12.00 sec 3.00 MBytes 25.2 Mbits/sec 0 3.10 MBytes
[ 5] 12.00-13.00 sec 6.75 MBytes 56.6 Mbits/sec 0 3.41 MBytes
[ 5] 13.00-14.00 sec 5.75 MBytes 48.2 Mbits/sec 0 3.61 MBytes
[ 5] 14.00-15.00 sec 4.25 MBytes 35.7 Mbits/sec 0 3.81 MBytes
[ 5] 15.00-16.00 sec 5.75 MBytes 48.2 Mbits/sec 0 3.81 MBytes
[ 5] 16.00-17.00 sec 4.38 MBytes 36.7 Mbits/sec 0 4.07 MBytes
[ 5] 17.00-18.00 sec 5.88 MBytes 49.3 Mbits/sec 0 4.07 MBytes
[ 5] 18.00-19.00 sec 2.75 MBytes 23.1 Mbits/sec 0 4.07 MBytes
[ 5] 19.00-20.00 sec 3.38 MBytes 28.3 Mbits/sec 3 2.86 MBytes
[ 5] 20.00-21.00 sec 2.88 MBytes 24.1 Mbits/sec 0 2.94 MBytes
[ 5] 21.00-22.00 sec 1.25 MBytes 10.5 Mbits/sec 0 3.10 MBytes
[ 5] 22.00-23.00 sec 5.50 MBytes 46.1 Mbits/sec 0 3.44 MBytes
[ 5] 23.00-24.00 sec 5.50 MBytes 46.1 Mbits/sec 0 3.63 MBytes
[ 5] 24.00-25.00 sec 4.50 MBytes 37.7 Mbits/sec 0 3.64 MBytes
[ 5] 25.00-26.00 sec 4.25 MBytes 35.7 Mbits/sec 0 3.64 MBytes
[ 5] 26.00-27.00 sec 5.62 MBytes 47.2 Mbits/sec 0 3.86 MBytes
[ 5] 27.00-28.00 sec 6.62 MBytes 55.6 Mbits/sec 0 3.86 MBytes
[ 5] 28.00-29.00 sec 5.50 MBytes 46.1 Mbits/sec 0 3.86 MBytes
[ 5] 29.00-30.00 sec 4.88 MBytes 40.8 Mbits/sec 0 3.86 MBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-30.00 sec 150 MBytes 41.9 Mbits/sec 3 sender
[ 5] 0.00-30.32 sec 150 MBytes 41.5 Mbits/sec receiver

iperf Done.
</syntaxhighlight>

== Bluetooth ==
'''''Note:''''' This Bluetooth section was tested with the iMX91 Industrial Module in Max and Pro configurations. For Basic configuration, bluetooth capabilities are not available. For more information see [[iMX91 Industrial Development Kit|the iMX91 Industrial Module comparison]]. 

'''''Input:''''' None 
'''''Output:''''' Remote device is recognized after scan 

'''''Note:''''' For iMX91 Industrial Module Max (u-blox MAYA-W260-00B assembled) please use instead of <syntaxhighlight lang="bash">hciattach /dev/ttyLP7 any 3000000 flow</syntaxhighlight> command <syntaxhighlight lang="bash">hciattach /dev/ttyLP7 any 115200 flow</syntaxhighlight> in below code
<syntaxhighlight lang="bash">
# attach necessary modules
root@imx91-voipac:~# modprobe moal mod_para=nxp/wifi_mod_para.conf
root@imx91-voipac:~# modprobe hci_uart
root@imx91-voipac:~# hciattach /dev/ttyLP7 any 3000000 flow
Device setup complete
root@imx91-voipac:~# [ 1207.472299] Bluetooth: MGMT ver 1.22
[ 1207.485171] NET: Registered PF_ALG protocol family

# put hci0 device up
root@imx91-voipac:~# hciconfig hci0 up

# scan for remote bluetooth devices (enable bluetooth on phone and make it discoverable)
root@imx91-voipac:~# hcitool scan
Scanning ...
Devices:
hci0 00:0D:18:01:5A:B3
</syntaxhighlight>

== Ethernet ==
'''''Note:''''' This section was tested with the iMX91 Industrial Module in Max configuration which includes dual Gigabit Ethernet PHY. The Pro configuration includes single Gigabit Ethernet PHY. For the Basic configuration, Ethernet capabilities are not available. For more information see [[iMX91 Industrial Development Kit|the iMX91 Industrial Module comparison]]. 

'''''Input:''''' None 
'''''Output:''''' Device driver is available (for Pro configuration only one ethernet is available) 
'''''Note:''''' MAC address should be identical with the address on the sticker placed on the board
<syntaxhighlight lang="bash">

root@imx91-voipac:~# ip addr show dev eth0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:0d:15:01:8c:ae brd ff:ff:ff:ff:ff:ff
inet 192.168.1.33/24 metric 10 brd 192.168.1.255 scope global dynamic eth0
valid_lft 86378sec preferred_lft 86378sec
inet6 fe80::20d:15ff:fe01:8cae/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
root@imx91-voipac:~# ip addr show dev eth1
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:0d:15:01:8c:af brd ff:ff:ff:ff:ff:ff
inet 192.168.1.34/24 metric 10 brd 192.168.1.255 scope global dynamic eth1
valid_lft 86391sec preferred_lft 86391sec
inet6 fe80::20d:15ff:fe01:8caf/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
root@imx91-voipac:~#
</syntaxhighlight>

'''''Input:''''' Plug Ethernet cable into top or bottom connector for the Max configuration. Plug Ethernet cable into bottom connector for the Pro configuration. 
'''''Output:''''' IPv4 address is assigned
<syntaxhighlight lang="bash">
[ 1599.750399] fec 42890000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[ 1630.695671] imx-dwmac 428a0000.ethernet eth1: Link is Up - 1Gbps/Full - flow control off
</syntaxhighlight>

=== Performance ===
iPerf3 was used to test the Ethernet performance. 
'''''Note:''''' The Max configuration of the iMX91 Industrial Module includes dual Gigabit Ethernet PHY. The Pro configuration includes single Gigabit Ethernet PHY. 
'''''Input:''''' Start iPerf3 on computer using command <syntaxhighlight lang="bash">iperf3 -s </syntaxhighlight>
'''''Output:''''' Verify performance on board (argument after -c is IP address of your computer) 

<syntaxhighlight lang="bash">
root@imx91-voipac:~# iperf3 -c 192.168.240.120 -t 10 -i 1
Connecting to host 192.168.240.120, port 5201
[ 5] local 192.168.240.32 port 57734 connected to 192.168.240.120 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 114 MBytes 951 Mbits/sec 0 358 KBytes
[ 5] 1.00-2.00 sec 112 MBytes 943 Mbits/sec 0 358 KBytes
[ 5] 2.00-3.00 sec 112 MBytes 938 Mbits/sec 0 358 KBytes
[ 5] 3.00-4.00 sec 113 MBytes 947 Mbits/sec 0 393 KBytes
[ 5] 4.00-5.00 sec 112 MBytes 941 Mbits/sec 0 393 KBytes
[ 5] 5.00-6.00 sec 112 MBytes 944 Mbits/sec 0 393 KBytes
[ 5] 6.00-7.00 sec 112 MBytes 940 Mbits/sec 0 516 KBytes
[ 5] 7.00-8.00 sec 112 MBytes 943 Mbits/sec 0 516 KBytes
[ 5] 8.00-9.00 sec 112 MBytes 942 Mbits/sec 0 516 KBytes
[ 5] 9.00-10.00 sec 113 MBytes 946 Mbits/sec 0 516 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 1.10 GBytes 943 Mbits/sec 0 sender
[ 5] 0.00-10.05 sec 1.10 GBytes 937 Mbits/sec receiver

iperf Done.
root@imx91-voipac:~#

</syntaxhighlight>

== USB 2.0 ==
NOTE: Perform read/write performance test 
'''''Input:''''' Plug USB flash drive into USB connector 
'''''Output:''''' Plugged USB device is listed
<syntaxhighlight lang="bash">
root@imx91-voipac:~# lsusb
Bus 001 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 125f:d31a A-DATA Technology Co., Ltd.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
</syntaxhighlight>

'''''Input:''''' Generate a dummy file and copy it into USB flash drive 
'''''Output:''''' Generated file and copied file have the same checksum
<syntaxhighlight lang="bash">
root@imx91-voipac:~# mount /dev/sda1 /media/
root@imx91-voipac:~# rm -f file.txt /media/file.txt
root@imx91-voipac:~# dd if=/dev/urandom of=file.txt count=1024 bs=1024
1024+0 records in
1024+0 records out
root@imx91-voipac:~# cp file.txt /media/
root@imx91-voipac:~# md5sum file.txt /media/file.txt
200a9fd3e9850fcedf85ed50d4c4733d file.txt
200a9fd3e9850fcedf85ed50d4c4733d /media/file.txt
root@imx91-voipac:~# rm file.txt /media/file.txt
root@imx91-voipac:~# umount /media
</syntaxhighlight>

== USB-C ==
This connector is primarily used for flashing new binaries into the iMX91 Industrial Module. More information can be found on the dedicated [[iMX8M Industrial Flashing Procedure|module flashing page]]. 

== USB Micro-B serial console ==
'''''Input:''''' Connect USB console cable into the base board connector and open serial console with baud rate 115200 8n1 
'''''Output:''''' The board is controlled and responsive to serial terminal commands
<syntaxhighlight lang="bash">
root@imx91-voipac:~# uname -a
Linux imx91-voipac 6.6.36-lts-next-g2e3e2e65d92a #1 SMP PREEMPT Wed Sep 4 08:22:45 UTC 2024 aarch64 GNU/Linux
</syntaxhighlight>

== UART serial console ==
Serial console is utilized via USB Micro-B connector by default. Alternatively, the communication can be established using UART headers and TTL-232R-3V3 - FTDI cable. 
NOTE: Describe jumpers position 
[[File:iMX93 Industrial Development Kit-Serial console via UART1.png|800px]] 

'''''Note:''''' Usage of UART2 CONSOLE to communicate by default requires changes in Yocto binaries and new compilation of image files. 
[[File:iMX93 Industrial Development Kit-Serial console via UART2.png|800px]]

== SD Card ==
NOTE: Perform detection of SD Card
<syntaxhighlight lang="bash">
root@imx91-voipac:~# fdisk -l
Disk /dev/mmcblk0: 15 GB, 15758000128 bytes, 30777344 sectors
240448 cylinders, 4 heads, 32 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type
/dev/mmcblk0p1 * 128,0,1 1023,3,32 16384 186775 170392 83.1M c Win95 FAT32 (LBA)
/dev/mmcblk0p2 1023,3,32 1023,3,32 196608 939761 743154 362M 83 Linux
Disk /dev/mmcblk0boot0: 4 MB, 4194304 bytes, 8192 sectors
128 cylinders, 4 heads, 16 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Disk /dev/mmcblk0boot1: 4 MB, 4194304 bytes, 8192 sectors
128 cylinders, 4 heads, 16 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Disk /dev/mmcblk1: 15 GB, 15931539456 bytes, 31116288 sectors
243096 cylinders, 4 heads, 32 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type
/dev/mmcblk1p1 512,0,1 1023,3,32 65536 266255 200720 98.0M 83 Linux
</syntaxhighlight>

/dev/mmcblk1 is SD card (mmcblk0 is eMMC)

== JTAG ==
[[File:iMX93 Industrial Development Kit-JTAG communication setup.png|800px]] 
To verify that i.MX93 CPU JTAG is functional, following command identifies and connects to the CPU's debug point:
<syntaxhighlight lang="bash">
J-Link> jtagid
</syntaxhighlight>

[[File:J-Link MIMX9352 A55 1.png|800px]] 
[[File:J-Link MIMX9352 M33.png|800px]]

== Real Time Clock ==
RTC chip is detected by Linux kernel after start-up:
<syntaxhighlight lang="bash">
root@imx91-voipac:~# dmesg | grep rtc
[ 0.894414] imx-drm display-subsystem: bound imx-lcdifv3-crtc.0 (ops lcdifv3_crtc_ops)
[ 0.910506] imx-drm display-subsystem: [drm] Cannot find any crtc or sizes
[ 1.209418] bbnsm_rtc 44440000.bbnsm:rtc: registered as rtc0
[ 1.215749] bbnsm_rtc 44440000.bbnsm:rtc: setting system clock to 1970-01-01T00:00:00 UTC (0)
root@imx91-voipac:~#
</syntaxhighlight>

CPU correctly recognises RTC on the I2C1 bus, the chip is under usage by the kernel:
<syntaxhighlight lang="bash">
root@imx91-voipac:~# i2cdetect -r -y 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- UU -- -- -- UU -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- 3d -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- UU -- UU -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
</syntaxhighlight>

Set up the current date and time, show the actual values

Setup date and time
<syntaxhighlight lang="bash">
date -s "2025-8-13 14:52:26"
</syntaxhighlight>

Show actual values
<syntaxhighlight lang="bash">
root@imx91-voipac:~# timedatectl
[ 134.509782] kauditd_printk_skb: 8 callbacks suppressed
[ 134.509793] audit: type=1334 audit(1732625725.140:18): prog-id=19 op=LOAD
[ 134.523935] audit: type=1334 audit(1732625725.148:19): prog-id=20 op=LOAD
[ 134.531609] audit: type=1334 audit(1732625725.152:20): prog-id=21 op=LOAD
Local time: Tue 2024-11-26 12:55:25 UTC
Universal time: Tue 2024-11-26 12:55:25 UTC
RTC time: Tue 2024-11-26 12:55:25
Time zone: UTC (UTC, +0000)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no
</syntaxhighlight>

== I2C EEPROM Memory - on module ==
'''''Input:''''' Power on board 
'''''Output:''''' Store some data to eeprom and after reboot read it back and should be same 

<syntaxhighlight lang="bash">
# store random 8bytes to eeprom
root@imx91-voipac-evk:~# dd if=/dev/urandom of=/sys/bus/i2c/devices/0-0050/eeprom bs=8 count=1
+1 records in
0+1 records out
8 bytes copied, 0.0225523 s, 0.4 kB/s
</syntaxhighlight>

After board reboot:
<syntaxhighlight lang="bash">
# store random 8bytes to eeprom
root@imx91-voipac-evk:~# hexdump -n8 /sys/bus/i2c/devices/0-0050/eeprom
0000000 c4dd 4eda d624 535e
0000008
</syntaxhighlight>

== Reset button ==
'''''Input:''''' Press the RESET button 
'''''Output:''''' The board will execute bootloader immediately with "Reset cause: POR" 
'''''Note:''''' iMX91 Industrial Development Kit should never freeze or hang after the reset button was pressed. Testing the operation 10 times gives a reliable result
<syntaxhighlight lang="bash">
U-Boot 2023.04+gf8a2983ec8+p0 (Mar 04 2024 - 07:25:04 +0000)

CPU: i.MX93(52) rev1.1 1700 MHz (running at 1692 MHz)
CPU: Industrial temperature grade (-40C to 105C) at 45C
Reset cause: POR (0x1)
Model: NXP i.MX93 Voipac EVK board
DRAM: 2 GiB
Core: 215 devices, 32 uclasses, devicetree: separate
MMC: FSL_SDHC: 0, FSL_SDHC: 1
Loading Environment from MMC... OK
[*]-Video Link 0fail to find output device

....
</syntaxhighlight>

== On/Off button ==
'''''Input:''''' Press and hold On/Off button for more then 5 seconds 
'''''Output:''''' The board will be powered off

Press shortly the On/Off button again, the board will be powered on.

== Sleep Mode ==
'''''Input:''''' Type command:
<syntaxhighlight lang="bash">
echo mem > /sys/power/state
</syntaxhighlight>

'''''Output:''''' The board will go into a frozen state and the serial console will not respond to inputs.

Shortly press the Up user button, to wake the board up again.

[[File:imx93_sleep_mode.png|740px]] 

== User buttons ==
'''''Input:''''' Press Enter/Left/Right/Up/Down buttons 
'''''Output:''''' Button events 1 and 0 are generated
<syntaxhighlight lang="bash">
root@imx91-voipac-evk:~# evtest /dev/input/by-path/platform-gpio-buttons-event
Input driver version is 1.0.1
Input device ID: bus 0x19 vendor 0x1 product 0x1 version 0x100
Input device name: "gpio-buttons"
Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
Event code 28 (KEY_ENTER)
Event code 103 (KEY_UP)
Event code 105 (KEY_LEFT)
Event code 106 (KEY_RIGHT)
Event code 108 (KEY_DOWN)
Properties:
Testing ... (interrupt to exit)
Event: time 1717485486.586413, type 1 (EV_KEY), code 103 (KEY_UP), value 1
Event: time 1717485486.586413, -------------- SYN_REPORT ------------
Event: time 1717485486.682265, type 1 (EV_KEY), code 103 (KEY_UP), value 0
Event: time 1717485486.682265, -------------- SYN_REPORT ------------
Event: time 1717485487.255120, type 1 (EV_KEY), code 108 (KEY_DOWN), value 1
Event: time 1717485487.255120, -------------- SYN_REPORT ------------
Event: time 1717485487.367126, type 1 (EV_KEY), code 108 (KEY_DOWN), value 0
Event: time 1717485487.367126, -------------- SYN_REPORT ------------
Event: time 1717485488.539564, type 1 (EV_KEY), code 106 (KEY_RIGHT), value 1
Event: time 1717485488.539564, -------------- SYN_REPORT ------------
Event: time 1717485488.677501, type 1 (EV_KEY), code 106 (KEY_RIGHT), value 0
Event: time 1717485488.677501, -------------- SYN_REPORT ------------
Event: time 1717485488.897627, type 1 (EV_KEY), code 105 (KEY_LEFT), value 1
Event: time 1717485488.897627, -------------- SYN_REPORT ------------
Event: time 1717485489.013136, type 1 (EV_KEY), code 105 (KEY_LEFT), value 0
Event: time 1717485489.013136, -------------- SYN_REPORT ------------
Event: time 1717485489.264589, type 1 (EV_KEY), code 28 (KEY_ENTER), value 1
Event: time 1717485489.264589, -------------- SYN_REPORT ------------
Event: time 1717485489.372584, type 1 (EV_KEY), code 28 (KEY_ENTER), value 0
Event: time 1717485489.372584, -------------- SYN_REPORT ------------
</syntaxhighlight>

== User LED ==
'''''Input:''''' None 
'''''Output:''''' Script switches User LED on baseboard ON and OFF in one second intervals
<syntaxhighlight lang="bash">
#!/bin/sh

LED=/sys/class/leds/user_sbc

while true; do
echo 0 > ${LED}/brightness
sleep 1
echo 1 > ${LED}/brightness
sleep 1
done
</syntaxhighlight>

'''''Input:''''' None 
'''''Output:''''' User LED on baseboard is set to heartbeat blinking sequence
<syntaxhighlight lang="bash">
root@imx91-voipac-evk:~# echo heartbeat > /sys/class/leds/user_sbc/trigger
</syntaxhighlight>

'''''Input:''''' None 
'''''Output:''''' User LED on SOM is set to heartbeat blinking sequence
<syntaxhighlight lang="bash">
root@imx91-voipac-evk:~# echo heartbeat > /sys/class/leds/user_som/trigger
</syntaxhighlight>

File:iMX91 Industrial Module Interfaces-Overview top.png

2025-10-30T10:13:42Z

Voipac-sw: Voipac-sw uploaded a new version of File:iMX91 Industrial Module Interfaces-Overview top.png

iMX91 Industrial Flashing Procedure

2025-10-30T10:11:25Z

Voipac-sw:

[[Category:iMX91 Industrial Development Kit]]
[[Category:iMX91 Industrial Software]]

<div style="float:right">__TOC__</div>
This page describes how to flash [https://downloads.voipac.com/index.php?p=iMX91_Industrial_Development_Kit/module/software/filesystem binaries] into iMX91 Industrial Module's eMMC Flash memory or into SD card that is located on the iMX Development Baseboard. 

'''''Note: All of the steps listed below are NOT REQUIRED for standard configuration modules and development kits.'''''

== Installing Universal Upload Utility (UUU) ==
=== Linux ===
<syntaxhighlight lang="bash">
git clone https://github.com/NXPmicro/mfgtools.git
cd mfgtools
mkdir .build && cd .build && cmake .. && make -j`nproc`
</syntaxhighlight>

The binary called '''''uuu''''', which is used for flashing, is located in .build/uuu directory.

=== Windows ===
* Go to: https://github.com/NXPmicro/mfgtools/releases
* Select the latest stable release. Example: '''''Releases/uuu_1.5.233''''': https://github.com/nxp-imx/mfgtools/releases/tag/uuu_1.5.233
* Download: [https://github.com/nxp-imx/mfgtools/releases/download/uuu_1.5.233/uuu.exe uuu.exe]
* Save the file into: C:\uuu

== Preparing the binaries ==
* Download the default WIC filesystem image e.g. for pro configuration: [https://downloads.voipac.com/files/iMX91_Industrial_Development_Kit/module/software/filesystem/voipac-image-imx91-pro.rootfs.wic voipac-image-imx91-pro.rootfs.wic]

== Flashing procedure ==
* Set serial downloader mode by sliding DIP switch S1 BOOT positions to: 1-OFF, 2-ON
[[File:iMX8M_Industrial_Development_Kit-Serial_donwloader_mode.png|400px]] 

* Plug USB Micro-B cable to baseboard CONSOLE connector and PC '''''Note:''''' Make sure that UART1 and UART2 jumpers are in CP2105 positions (USB/UART bridge). 
[[image:iMX Development Baseboard-Serial console jumpers-iMX91 COM.png|594px]] 

* Plug USB-C cable to baseboard USB-C connector and PC '''''Note:''''' Powering of the development kit is not required during the flashing procedure. '''''Note:''''' After connecting 2 development board cables, 2 serial ports named ''Silicon Labs CP210x USB to UART Bridge'' should appear in the controlling PC. 
[[image:iMX8M Industrial Development Kit-Serial-consoles-recognized.png|594px]] 
* Default Serial Port Settings
[[File:Serial Port Setup.png]] 

* Download and copy imx-boot and *.wic files into ''uuu\'' directory
* Choose one of the following commands to start the flashing process:
=== eMMC Flash Memory (default) ===

==== Linux ====
<syntaxhighlight lang="bash">
sudo ./uuu -b emmc_all voipac-image-imx91-max.rootfs.wic
</syntaxhighlight>

==== Windows ====
<syntaxhighlight lang="bash">
uuu.exe -b emmc_all voipac-image-imx91-max.rootfs.wic
</syntaxhighlight>

=== SD Card ===

==== Linux ====
<syntaxhighlight lang="bash">
sudo ./uuu -b sd_all voipac-image-imx91-max.rootfs.wic
</syntaxhighlight>

==== Windows ====
<syntaxhighlight lang="bash">
uuu.exe -b sd_all voipac-image-imx91-max.rootfs.wic
</syntaxhighlight>

=== Flashing logs ===
==== UUU ====
<syntaxhighlight lang="bash">
Microsoft Windows [Version 10.0.19045.2486]
(c) Microsoft Corporation. All rights reserved.

C:\Users\voipac>cd c:\uuu

c:\uuu>uuu.exe -b emmc_all voipac-image-imx91-pro.rootfs.wic
uuu (Universal Update Utility) for nxp imx chips -- libuuu_1.5.233-0-g79ce7d2

Success 1 Failure 0

2:43 8/ 8 [Done ] FB: done

c:\uuu>
</syntaxhighlight>

[[image:iMX91_Industrial_Development_Kit-Flashing_binaries.png|750px]]

==== Serial console ====
<syntaxhighlight lang="bash">
.....................................................
downloading of 16776244 bytes finished
writing to partition 'all'
sparse flash target is mmc:0
writing to partition 'all' for sparse, buffer size 16776244
Flashing sparse image at offset 0
Flashing Sparse Image
........ wrote 16776192 bytes to 'all'
Starting download of 16776244 bytes
..........................................................................
.....................................................
downloading of 16776244 bytes finished
writing to partition 'all'
sparse flash target is mmc:0
writing to partition 'all' for sparse, buffer size 16776244
Flashing sparse image at offset 0
Flashing Sparse Image
........ wrote 16776192 bytes to 'all'
Starting download of 14886964 bytes
..........................................................................
.......................................
downloading of 14886964 bytes finished
writing to partition 'all'
sparse flash target is mmc:0
writing to partition 'all' for sparse, buffer size 14886964
Flashing sparse image at offset 0
Flashing Sparse Image
........ wrote 14886912 bytes to 'all'
Starting download of 1470464 bytes
...........
downloading of 1470464 bytes finished
writing to partition 'bootloader'
Initializing 'bootloader'
switch to partitions #1, OK
mmc0(part 1) is current device
Writing 'bootloader'

MMC write: dev # 0, block # 0, count 2872 ... 2872 blocks written: OK
Writing 'bootloader' DONE!
Detect USB boot. Will enter fastboot mode!
Detect USB boot. Will enter fastboot mode!
</syntaxhighlight>

== Running the newly flashed binaries ==
After completing the above steps, eMMC Flash memory or SD Card is flashed and the following steps are to be performed to boot the new image:

* Unplug USB-C cable from PC
* Set Boot mode by sliding DIP switch S1 BOOT positions to: 1-ON, 2-OFF
[[File:iMX8M_Industrial_Development_Kit-Boot_mode.png|400px]] 

* In case of SD card boot set DIP switch S1 BOOT positions to 1-ON, 2-ON
[[File:SD Card booting.png|400px]] 

* Make sure that S2 BOOT and S3 BOOT DIP switches are in correct positions in order to boot from the selected storage media (eMMC Flash memory or SD Card):
==== eMMC Flash Memory boot (default) ====
[[File:boot eMMC iMX91.png|400px]] 

==== SD Card boot ====
[[File:boot SD Card iMX91.png|400px]] 
* Connect USB Micro-B debug cable, switch on the power and the development kit starts booting with the new binaries 

== Setting DTB file ==
* To set a correct DTB file, stop autoboot.

* Use these commands to set a DTB file for the image loaded in eMMC:
<syntaxhighlight lang="bash">
u-boot=>fatls mmc 0:1
u-boot=>setenv fdtfile imx91-voipac-evk.dtb
u-boot=>saveenv
</syntaxhighlight>

* Use these commands to set a DTB file for the image loaded in SD Card (example for Tianma Display):
<syntaxhighlight lang="bash">
u-boot=>fatls mmc 1:1
u-boot=>setenv fdtfile imx91-11x11-evk-tianma-wvga-panel.dtb
u-boot=>saveenv
</syntaxhighlight>

[[File:imx91_dtb_setting.png|740px]] 

* To boot the image, reset the board or type the boot command:

<syntaxhighlight lang="bash">
u-boot=>boot
</syntaxhighlight>

File:imx91 dtb setting.png

2025-10-30T10:11:15Z

Voipac-sw:

File:boot eMMC iMX91.png

2025-10-30T10:09:27Z

Voipac-sw:

File:boot SD Card iMX91.png

2025-10-30T10:09:13Z

Voipac-sw:

File:iMX91 Industrial Development Kit-Flashing binaries.png

2025-10-30T10:07:02Z

Voipac-sw:

File:iMX Development Baseboard-Serial console jumpers-iMX91 COM.png

2025-10-30T09:59:45Z

Voipac-sw:

iMX91 Industrial Controlling the Development Kit

2025-10-30T09:57:23Z

Voipac-sw:

<div style="float:right">__TOC__</div>
This page guides though the first steps of controlling and operating the development kit. To prepare the working setup connect and plug in cables first.

=Controlling the Development Kit over Serial Line=
==Recommended HW:==

* PC with USB port
* Voipac iMX91 Industrial Development Kit
* Micro USB Cable: iMX Baseboard USB Micro-B Console (Default)
* TTL-232R-3V3-FTDI: iMX Baseboard UART1 Serial Console (Optional)

==Recommended SW:==

Serial line terminal (PUTTY, Minicom, Ckermit, Hyperterminal, TeraTerm, ...)

===Default serial port settings:===

* Speed (baud): 115200
* Data bits: 8
* Stop bits: 1
* Parity: None
* Flow control: None

===Controlling the development kit using TeraTerm and PuTTY:===

[[File:iMX91 TeraTerm log.png]] 
[[File:iMX91 PuTTY Serial log.png]] 

'''''NOTE:''''' If you use the UART1 Console cable, it is necessary to switch the UART1 and UART 2 jumpers to the UART-CPU position as shown in the picture below.

[[File:iMX91 UART Serial Console.png|800px]] 

=Controlling the Development Kit over Ethernet=
===Recommended HW:===

* PC with Ethernet
* Voipac iMX91 Industrial Development Kit
* Ethernet Cable

===Recommended SW:===

* SFTP client (Filezilla, PUTTY, WinSCP, …)
* Telnet client (Telnet, PUTTY, …)
* SSH client (SSH,PUTTY, …)
* FTP client (FTP, Filezilla, BareFTP, …)

===Important notes:===

iMX91 Industrial Development Kit is shipped with empty password. The default login is: "root"

The default IP address is dynamic and setup by your DHCP server upon boot.

SSH, SFTP services require root password to be set up (“passwd” command)

FTP, SFTP are recommended only for data transfers (binary mode is recommended)

===Controlling the development kit using WinSCP:===

[[File:iMX91 WinSCP.png|800px]] 
[[File:iMX91 WinSCP commander.png|800px]]

File:iMX91 WinSCP commander.png

2025-10-30T09:57:07Z

Voipac-sw:

File:iMX91 WinSCP.png

2025-10-30T09:56:46Z

Voipac-sw:

File:iMX91 UART Serial Console.png

2025-10-30T09:55:57Z

Voipac-sw:

File:iMX91 PuTTY Serial log.png

2025-10-30T09:55:07Z

Voipac-sw:

File:iMX91 TeraTerm log.png

2025-10-30T09:54:49Z

Voipac-sw:

iMX91 Industrial Connecting the Components and Cables

2025-10-30T09:54:03Z

Voipac-sw:

[[Category:iMX91 Industrial Development Kit]]


This page is intended to show the necessary connections and steps to successfully boot and operate the development kit.

==Connecting the board==
Prepare iMX Development Baseboard and plug in Micro USB Cable, Ethernet cable and other devices or interfaces you need. Plug the power supply connector in.
 
[[File:iMX91 Components Cables.png|800px]]

==Connecting the Ethernet cable==
Connect the Ethernet cable to bottom connector (preset as default) of the Ethernet port.
 
[[File:iMX93 Components Cables Ethernet.png|800px]] 

==Connecting the microSD Card (OPTIONAL)==
Insert the micro SD card into the micro SD Slot in case that booting is set from the micro SD card.

'''''NOTE:''''' The Development Kit, which have default setting to boot from SD Card, already contains an inserted SD Card.
 
[[File:Components Cables microSD.png|800px]] 

'''''NOTE:''''' Before Turn On, make sure that S1, S2 and S3 BOOT DIP switches are in correct positions in order to boot from the selected storage media (eMMC Flash memory or SD Card). For more details visit: [[iMX91_Industrial_Flashing_Procedure#Running_the_newly_flashed_binaries]]

iMX91 Industrial Connecting the Components and Cables

2025-10-30T09:53:38Z

Voipac-sw:

[[Category:iMX93 Industrial Development Kit]]


This page is intended to show the necessary connections and steps to successfully boot and operate the development kit.

==Connecting the board==
Prepare iMX Development Baseboard and plug in Micro USB Cable, Ethernet cable and other devices or interfaces you need. Plug the power supply connector in.
 
[[File:iMX91 Components Cables.png|800px]]

==Connecting the Ethernet cable==
Connect the Ethernet cable to bottom connector (preset as default) of the Ethernet port.
 
[[File:iMX93 Components Cables Ethernet.png|800px]] 

==Connecting the microSD Card (OPTIONAL)==
Insert the micro SD card into the micro SD Slot in case that booting is set from the micro SD card.

'''''NOTE:''''' The Development Kit, which have default setting to boot from SD Card, already contains an inserted SD Card.
 
[[File:Components Cables microSD.png|800px]] 

'''''NOTE:''''' Before Turn On, make sure that S1, S2 and S3 BOOT DIP switches are in correct positions in order to boot from the selected storage media (eMMC Flash memory or SD Card). For more details visit: [[iMX91_Industrial_Flashing_Procedure#Running_the_newly_flashed_binaries]]

File:iMX91 Components Cables.png

2025-10-30T09:51:46Z

Voipac-sw:

iMX91 Industrial Module Interfaces Overview

2025-10-30T09:48:52Z

Voipac-sw:

[[Category:iMX93 Industrial Development Kit]]

== iM91 Industrial Module Interfaces Overview Top Side ==
[[image:iMX91 Industrial Module Interfaces-Overview top.png|center|800px]]
== iMX91 Industrial Module Interfaces Overview Bottom Side ==
[[image:iMX91 Industrial Module Interfaces-Overview bottom.png|center|800px]]

File:iMX91 Industrial Module Interfaces-Overview bottom.png

2025-10-30T09:48:40Z

Voipac-sw:

File:iMX91 Industrial Module Interfaces-Overview top.png

2025-10-30T09:47:33Z

Voipac-sw:

iMX91 Industrial Power Consumption

2025-10-22T19:30:02Z

Voipac-sw:

[[Category:iMX91 Industrial]]
[[Category:iMX91 Industrial Development Kit]]

<div style="float:right">__TOC__</div>

This page contains power consumption measurements for the iMX91 Industrial Development Kits in all 4 standard webshop configurations. All of the sets used during the test procedure were running the default Linux distribution and booted up from the eMMC NAND Flash Memory.

'''''Note:''''' While measured, the development kits were placed under a very heavy load - using stress test application putting CPU, memories and Ethernet/s under challenging conditions.

== Test setup and measuring equipment ==
* power supply: BK Precision 1688B
* digital multimeter: Fluke 115 True RMS
* measured at: 20°C ambient temperature

[[image:iMX93 Industrial Development Kit-Power consumption measurement setup.jpg|800px]]

== Power consumption results ==
=== iMX91 Industrial Development Kit Basic ===
{| class="wikitable" style="text-align: center;
!Test condition !! Input voltage Vin [V] !! Measured current I [A] !! Power usage P [W]
|-
|Uboot only || 5.188 || 0.290 || 1.506
|-
|Booting-up process (maximum) || 5.190 || 0.341 || 1.770
|-
|Linux at idle || 5.192 || 0.227 || 1.179
|-
|Sleep mode || 5.198 || 0.049 || 0.257
|-
|Linux + Stresstest || 5.193 || 0.367 || 1.905
|}

=== iMX91 Industrial Development Kit Pro ===
{| class="wikitable" style="text-align: center;
!Test condition !! Input voltage Vin [V] !! Measured current I [A] !! Power usage P [W]
|-
|Uboot only || 5.183 || 0.401 || 2.081
|-
|Booting-up process (maximum) || 5.182 || 0.478 || 2.476
|-
|Linux at idle || 5.186 || 0.323 || 1.675
|-
|Sleep mode || 5.195 || 0.079 || 0.414
|-
|Linux + Stresstest || 5.181 || 0.482 || 2.498
|}

=== iMX91 Industrial Development Kit Max ===
{| class="wikitable" style="text-align: center;
!Test condition !! Input voltage Vin [V] !! Measured current I [A] !! Power usage P [W]
|-
|Uboot only || 5.183 || 0.416 || 2.159
|-
|Booting-up process (maximum) || 5.186 || 0.460 || 2.386
|-
|Linux at idle || 5.186 || 0.338 || 1.756
|-
|Sleep mode || 5.196 || 0.085 || 0.444
|-
|Linux + Stresstest || 5.183 || 0.574 || 2.977
|}

iMX91 Industrial Recovery

2025-10-22T19:28:52Z

Voipac-sw:

<div style="float:right">__TOC__</div>
=Description=
The recovery procedure consists of following steps:

* Downloading binaries from Voipac download webpage
* Flashing binaries and filesystem over Baseboard USB-C connector
* Setting a suitable dtb file in bootloader (u-boot)
* Resetting and booting a module

==Recommended Software==
* Universal Update Utility (UUU)
* Windows Command Promt
* TFTP Server
* DHCP Server (Otional)

=Configuration=

==Updating U-boot and Filesystem:==
===Download u-boot file:===

https://downloads.voipac.com/index.php?p=iMX93_Industrial_Development_Kit/module/software/yocto/binaries

===Download filesystem:===

https://downloads.voipac.com/index.php?p=iMX93_Industrial_Development_Kit/module/software/filesystem

===Download Universal Update Utility (UUU) if needed:===

https://github.com/nxp-imx/mfgtools/releases

Create a new folder e.g. C:\uuu and move all downloaded files into it.

==Flashing uboot and filesystem==
Prepare Voipac baseboard and follow the steps to flash the module as shown on this [[iMX91 Industrial Flashing Procedure|page]].

==Setting a suitable dtb file in bootloader (u-boot)==

Stop autoboot in bootloader:
<syntaxhighlight lang="bash">
U-Boot 2024.04-lf_v2024.04+gde16f4f1722+p0 (Sep 02 2024 - 10:44:35 +0000)

Reset Status: POR

CPU: NXP i.MX93(52) Rev1.1 A55 at 1700 MHz
CPU: Industrial temperature grade (-40C to 105C) at 36C

Model: Voipac i.MX93 EVK board
DRAM: 2 GiB
Core: 219 devices, 31 uclasses, devicetree: separate
MMC: FSL_SDHC: 0, FSL_SDHC: 1
Loading Environment from MMC... OK
[*]-Video Link 0fail to find output device
probe video device failed, ret -19

[0] lcd-controller@4ae30000, video
fail to find output device
probe video device failed, ret -19
In: serial
Out: serial
Err: serial

BuildInfo:
- ELE firmware version 1.2.0-38f309fe

switch to partitions #0, OK
mmc0(part 0) is current device
UID: ad4a5a940e804162a528d6fe1532d4d5
flash target is MMC:0
Net: eth0: ethernet@42890000, eth1: ethernet@428a0000 [PRIME]
Fastboot: Normal
Normal Boot
Hit any key to stop autoboot: 0
u-boot=>
</syntaxhighlight>

Enter command fatls mmc 0:1 (filesystem in eMMC) or fatls mmc 1:1 (filesystem in SD Card) to see a list of DTB files:
<syntaxhighlight lang="bash">
u-boot=> fatls mmc 0:1
35564032 Image
69445 imx93-11x11-evk-aud-hat.dtb
66749 imx93-11x11-evk-boe-wxga-lvds-panel.dtb
65705 imx93-11x11-evk-flexio-i2c.dtb
66009 imx93-11x11-evk-flexspi-m2.dtb
66799 imx93-11x11-evk-i2c-spi-slave.dtb
65062 imx93-11x11-evk-i3c.dtb
2725 imx93-11x11-evk-inmate.dtb
51134 imx93-11x11-evk-iw612-otbr.dtb
65362 imx93-11x11-evk-ld.dtb
65520 imx93-11x11-evk-lpuart.dtb
65983 imx93-11x11-evk-mqs.dtb
68814 imx93-11x11-evk-mt9m114.dtb
65819 imx93-11x11-evk-rm67199.dtb
65573 imx93-11x11-evk-root.dtb
66108 imx93-11x11-evk-rpmsg-lpv.dtb
66132 imx93-11x11-evk-rpmsg.dtb
130428 imx93-11x11-evk_m33_TCM_low_power_wakeword.bin
19080 imx93-11x11-evk_m33_TCM_power_mode_switch.bin
18708 imx93-11x11-evk_m33_TCM_rpmsg_lite_pingpong_rtos_linux_remote.bin
17228 imx93-11x11-evk_m33_TCM_rpmsg_lite_str_echo_rtos.bin
47472 imx93-11x11-evk_m33_TCM_sai_low_power_audio.bin
48794 imx93-voipac-evk-boe-wxga-lvds-panel.dtb
47605 imx93-voipac-evk.dtb
593744 tee.bin

25 file(s), 0 dir(s)

u-boot=>
</syntaxhighlight>

Select the required DTB file and enter the command to set it up:

<syntaxhighlight lang="bash">
u-boot=> setenv fdtfile imx91-voipac-evk.dtb
u-boot=>
</syntaxhighlight>

Save:

<syntaxhighlight lang="bash">
u-boot=> saveenv
Saving Environment to MMC... Writing to MMC(0)... OK
u-boot=>
</syntaxhighlight >

Enter boot command or reset the baseboard for image loading.

iMX91 Industrial Debian

2025-10-22T19:28:12Z

Voipac-sw:

[[Category:iMX91 Industrial]]
[[Category:iMX91 Industrial Software]]
[[Category:iMX91 Industrial Debian]]
[[Category:Debian]]

<div style="float:right">__TOC__</div>

This Wiki page guides through the process of downloading the Debian source files for release (bookworm) and building images for the iMX91 Industrial Development Kit.

All the source files for this customized Debian, together with the recent changes made, can be inspected and downloaded at the [https://github.com/voipac/debian-imx-voipac Voipac GitHub] repository.

== Cloning the project ==
Create a new directory for the project environment:
<syntaxhighlight lang="bash">
mkdir ~/voipac-debian
cd ~/voipac-debian
</syntaxhighlight>

Clone the iMX9x Industrial Debian Project into the host machine:
<syntaxhighlight lang="bash">
git clone https://github.com/voipac/debian-imx-voipac
</syntaxhighlight>

== Prerequisites ==

For Debian image building it is necessary to install docker [https://docs.docker.com/desktop/setup/install/linux/ubuntu/ installation] as whole procedure is done in virtualised environment.

== Building the image ==
Voipac provides quick and simple-to-use option how to build an image by using [https://github.com/voipac/debian-imx-voipac/blob/master/build_debian_voipac.sh build_debian_voipac.sh] prepared script:

This script automatically create Debian image for iMX91:
<syntaxhighlight lang="bash">
MACHINE=imx91-voipac ./build_debian_voipac.sh
</syntaxhighlight>

During the u-boot build user will be asked for RAM Size. For basic kit configuration select option (1), for lite select 1G (option 2) and for pro and max configurations choose 2G option (option 3) as shown in below image. 

[[image:Screenshot from 2025-01-29 08-48-33.png|400px]] 

== Locating output files ==
After the build process was completed, the freshly built output files are located in the root directory:
<syntaxhighlight lang="bash">
ls -la image.sdimg
</syntaxhighlight>

== Prebuild images ==
Prebuild images can be downloaded at following [https://downloads.voipac.com/index.php?p=iMX91_Industrial_Development_Kit/module/software/debian/binaries link]

== Flashing the binaries ==
At this point everything was prepared to flash the binaries. Follow the [[iMX91 Industrial Flashing Procedure|flashing procedure]] instructions to start the development kit with the compiled images.

== Login ==
When image is flashed and board is booted default credentials can be either '''root/root''' or '''voipac/voipac'''.

iMX91 Industrial Mender

2025-10-22T19:27:41Z

Voipac-sw:

[[Category:iMX91 Industrial]]
[[Category:iMX91 Industrial Software]]
[[Category:iMX91 Industrial Yocto]]
[[Category:Yocto]]

<div style="float:right">__TOC__</div>

This Wiki page describes [https://hub.mender.io/t/voipac-imx91-industrial-development-kit/7316 Mender OTA updater integration] into the Yocto Project for the iMX91 Industrial Development Kit. Mender is a secure, robust and industry leading software update system capable to handle a large number of devices.

Mender supports several extensions enabling features like Remote Terminal, Port Forward, File Transfer, and Device Configuration, together with the ability to monitor and alert.

The steps described on this Wiki page are primarily focused on complying Mender updater into the Yocto Project. The well written [https://docs.mender.io/ official Mender documentation] covers all the other important aspects of this utility.

== Prerequisites ==
In-depth information about the machine requirements can be found in the [https://docs.yoctoproject.org/5.0/mega-manual/mega-manual.html Yocto mega manual]

Because the Mender utility will be integrated into the Yocto Project Release 5.0 (scarthgap), the Mender layer share the same steps for host machine setup as the Yocto Project.

To prepare the machine, follow the [[iMX91 Industrial Yocto Prerequisites|Yocto Project Prerequisites]] Wiki page.

== Configuring the build ==
=== Setup Yocto environment ===
Clone repo:
<syntaxhighlight lang="bash">
git clone https://github.com/voipac/yocto-imx-voipac.git
</syntaxhighlight>

Checkout mender branch:
<syntaxhighlight lang="bash">
cd yocto-imx-voipac
git checkout origin/imx91-mender
</syntaxhighlight>

== Configure Mender server URL (optional) ==
This section is not required for a successful build but images that are generated by default are only suitable for usage with the Mender client in [https://docs.mender.io/artifact-creation/standalone-deployment?target=_blank Standalone deployments], due to lack of server configuration.

Edit the ''conf/local.conf'' file to provide the Mender server configuration, ensuring that the generated images and Mender Artifacts are connecting to the Mender server. There should already be a commented section in the generated ''conf/local.conf'' file. A simple uncommenting the relevant configuration and assigning appropriate values sets up the server sufficiently.

Build for Hosted Mender:
<syntaxhighlight lang="bash">
# To get your tenant token:
# - log in to https://hosted.mender.io
# - click your email at the top right and then "My organization"
# - press the "COPY TO CLIPBOARD"
# - assign content of clipboard to MENDER_TENANT_TOKEN
#
MENDER_SERVER_URL = "https://hosted.mender.io"
MENDER_TENANT_TOKEN = "<copy token here>"
</syntaxhighlight>

== Building the image ==
You can now proceed with building an image:
<syntaxhighlight lang="bash">
build_image.sh
</syntaxhighlight>

or if you want to use docker container for building run:
<syntaxhighlight lang="bash">
build_image_container.sh
</syntaxhighlight>

== Using the build output ==
After a successful build, the images and build artifacts are placed in ''tmp/deploy/images/imx91-voipac/'' directory.

The disk image (with ''.sdimg.zst'' suffix) is used to provision the storage for devices without Mender already running. Please proceed to the [https://docs.mender.io/system-updates-yocto-project/provisioning-a-new-device?target=_blank official documentation on provisioning a new device] for steps to do so.

On the other hand, if Mender has already been running on the device and want to deploy a rootfs update using this build, the [https://docs.mender.io/overview/artifact?target=_blank Mender Artifact] files, with ''.mender'' suffix, can be used instead. This Artifact can either be deployed in managed mode with the Mender server (upload it under Releases in the server UI) or by using the Mender client [https://docs.mender.io/artifact-creation/standalone-deployment standalone mode].

== Flashing instructions ==

For flashing to eMMC we need to use uuu utility which must be installed on your host computer (mfgtools. Also due issue with emmc boot we split flashing to 2 parts. First we use imx-boot without mender integration and the we replace imx-boot in eMMC with one with mender integration. All is prepared in convenient script imx91 mender flashing

Copy image + imx-boot to custom directory

<syntaxhighlight lang="bash">
cp yocto-imx-voipac/build/tmp/deploy/images/imx91-voipac/voipac-image-imx91-voipac.sdimg.zst yocto-imx-voipac/flashing
cp yocto-imx-voipac/build/tmp/deploy/images/imx91-voipac/imx-boot yocto-imx-voipac/flashing
</syntaxhighlight>

# make copy of mender imx-boot
<syntaxhighlight lang="bash">
cd yocto-imx-voipac/flashing
cp -f imx-boot imx-boot-flash-mender
</syntaxhighlight>

Prepare board to serial download mode
Setup S1 pin to Serial download mode and connect imx91 board to you PC using USB-C cable.

Run flashing script:
<syntaxhighlight lang="bash">
./flash-mender.sh
</syntaxhighlight>

After all is done you can unplugged USB-C and power on your board with mender integrated.

iMX91 Industrial Yocto Image Building

2025-10-22T19:26:55Z

Voipac-sw:

[[Category:iMX91 Industrial]]
[[Category:iMX91 Industrial Software]]
[[Category:iMX91 Industrial Yocto]]
[[Category:Yocto]]

<div style="float:right">__TOC__</div>

This Wiki page guides through the process of downloading the Yocto Project source files for release 5.0 (scarthgap), their synchronization and building images for the iMX91 Industrial Development Kit.

Before images can be built, [[iMX91 Industrial Yocto Prerequisites|necessary steps need to be performed]] to setup the host machine.

All the source files for this customized Yocto Project, together with the recent changes made, can be inspected and downloaded at the [https://github.com/voipac Voipac GitHub] repository.

== Cloning the project ==
Create a new directory for the project environment:
<syntaxhighlight lang="bash">
mkdir ~/voipac-yocto
cd ~/voipac-yocto
</syntaxhighlight>

Clone the iMX91 Industrial Yocto Project into the host machine:
<syntaxhighlight lang="bash">
git clone https://github.com/voipac/yocto-imx-voipac.git
git checkout -b imx91 origin/imx9x-scarthgap

</syntaxhighlight>

== Building the image ==
Voipac provides quick and simple-to-use option how to build an image by using [https://github.com/voipac/yocto-imx-voipac/blob/imx9x-scarthgap/build_image.sh prepared script]:

This script automatically updates the latest meta layers. These layers include config files describing where all the sources are located. Afterwards all the directories are synchronized.

The script can be run to fetch and build the Yocto images by simply calling its filename:
<syntaxhighlight lang="bash">
./build_image.sh [lite|basic|pro|max] imx91
</syntaxhighlight>

'''''Note:''''' The first successful build can take several hours (depending on multiple factors affecting the host machine like CPU, internet bandwidth, allocated disk space, etc.).

== Locating output files ==
After the compiling process was completed, the freshly built output files are located in the directory:
<syntaxhighlight lang="bash">
cd ~/voipac-yocto/yocto-imx-voipac/build/tmp/deploy/images/imx91-voipac
</syntaxhighlight>

This directory also include binaries to be flashed into the development kit. To make them more accessible, the files can be copied and unpacked:
<syntaxhighlight lang="bash">
cp -prv voipac-image-imx91-voipac.rootfs-20250110131518.wic.zst ~/voipac-image-imx91-voipac.wic.zst
</syntaxhighlight>
'''''Note:''''' The number string (e.g. ''20250110131518'') in the filename differs between every build as it displays the timestamp of the compilation.

== Flashing the binaries ==
At this point everything was prepared to flash the binaries. Follow the [[iMX91 Industrial Flashing Procedure|flashing procedure]] instructions to start the development kit with the compiled images.

iMX91 Industrial Yocto Prerequisites

2025-10-22T19:26:09Z

Voipac-sw:

[[Category:iMX91 Industrial]]
[[Category:iMX91 Industrial Software]]
[[Category:iMX91 Industrial Yocto]]
[[Category:Yocto]]

<div style="float:right">__TOC__</div>

This Wiki page describes the necessary steps to prepare the host machine for successful compilation of the Yocto BSP release 5.0 (scarthgap) for the iMX91 Industrial Development Kit.

If the host setup has been completed, follow [[iMX91 Industrial Yocto Image Building|Yocto Image Build Wiki page]], which summarizes the process of compiling Yocto images and binaries.

All the source files for this customized Yocto Project, together with the recent changes made, can be inspected and downloaded at the [https://github.com/voipac Voipac GitHub] repository.

== Host machine setup ==
This image build was tested and verified on [https://releases.ubuntu.com/focal/ubuntu-20.04.6-desktop-amd64.iso Ubuntu 20.04 LTS (Focal Fossa)] operating systems.

Follow the standard Ubuntu desktop installation, in case of difficulties head to the [https://ubuntu.com/tutorials/install-ubuntu-desktop Ubuntu installation guide].

'''''Note:''''' It is advisable to install the operating system into the virtual machine as this allows the working environment to be more flexible, adjustable and shareable.

== Host packages ==
After the successful operating system installation, following packages, essential for image building, need to be added to the build machine:
<syntaxhighlight lang="bash">
sudo apt install build-essential chrpath cpio debianutils diffstat file gawk gcc git iputils-ping libacl1 liblz4-tool locales python3 python3-git python3-jinja2 python3-pexpect python3-pip python3-subunit socat texinfo unzip wget xz-utils zstd

</syntaxhighlight>

== kas tool install ==
To ease the usage of Git repositories kas tool needs to be installed. This enables kas config files usage and its advantages.
<syntaxhighlight lang="bash">
pip3 install kas

</syntaxhighlight>

== Git identity setup ==
Git uses a username with connected email address to associate commits with an identity. To set up a Git username and email, following commands (with own credentials) should be used:
<syntaxhighlight lang="bash">
git config --global user.name "Your Name"
git config --global user.email "Your Email"
</syntaxhighlight>

At this point the host machine has been successfully setup and ready to start the [[iMX91 Industrial Yocto Image Building|image building]].

iMX91 Industrial EMC testing

2025-10-22T19:25:40Z

Voipac-sw:

'''''EMC testing of iMX91 Industrial Development Kit is successfully finished.''''' 
'''''Content of this page will be updated soon.'''''

[[File:iMX93 Industrial Development Kit-EMC testing-in progress.jpg|800px]]

[[Category:iMX8M Industrial Development Kit]]
[[Category:iMX8M Industrial Development Kit Testing]]

<div style="float:right">__TOC__</div>

Electromagnetic compatibility results for iMX8M Industrial Development Kit are presented on this page. Test setup and scripts are described in details. 

These tests were performed with setups using the standard hardware and software configurations of the web shop development kits, with multiple accessories actively used, to simulate a real-world operation.

The certificate measurements were carried out on the iMX8M Industrial Development Kit in Pro version as this configuration delivers the best price-performance ratio and is the most popular amongst the customers. Other configurations - Max and Basic were also tested both passing the EMC radiated and conducted emmissions Class B norm. As the differences in the results were negligible, this web page focuses on the certificated measurements of the [https://www.voipac.com/imx8m-industrial-development-kit-pro Pro configuration] of the development kit.

The certificate document contains numerous different measurement as described in the ETSI EMC standards. This wiki page highlights and discuses only the most important results. All the details can be found in the EMC certificate and [https://downloads.voipac.com/index.php?p=iMX8M_Industrial_Development_Kit/module/documents/EMC_certification dedicated downloads folder].

The measurements were performed in an accredited test laboratory. After passing all the requirements described in the harmonised standard ETSI EN 301 489-17, the [https://downloads.voipac.com/files/iMX8M_Industrial_Development_Kit/module/documents/EMC_certification/iMX8M_Industrial_Development_Kit-EMC_certificate_with_conformity_assessment_and_test_reports.pdf EMC certificate with conformity assessment and test reports] was issued for the iMX8M Industrial Development Kit.

== Connected cables/devices ==
* '''Power source:''' [https://www.voipac.com/power-supply-5v-40w +5V 40W power supply] used for input voltage
* '''Storage device:''' eMMC Flash memory soldered on module used for booting, filesystem operation and script storage
* '''Ethernet:''' 1m long CAT Ethernet [https://supportportal.juniper.net/s/article/EX-How-to-link-up-Juniper-Ethernet-switching-GbE-copper-port-by-RJ45-loopback-connector?language=en_US loopback cable] connected. Forced to 100Mbps and used for ping test
* one of these '''video output''' options was used at a time:
** '''DisplayPort (M) interface used with LCD monitor connected:''' Full-HD output video stream generated and sent to LCD monitor via 1.5m long DisplayPort cable, with ferrite beads added (Würth Elektronik P/N: 742 711 32). The output signal forced to be continuously generated, contributing to EMC spectrum, monitor was plugged into mains, turned on, and laid flat on the floor to minimise its impact on results. Used LCD monitor: 24" LG LG24BK550Y 1920×1080 px
** '''HDMI interface used with LCD monitor connected:''' Full-HD output video stream generated and sent to LCD monitor via 1.5m long HDMI cable, with ferrite beads added (Würth Elektronik P/N: 742 758 15). The output signal forced to be continuously generated, contributing to EMC spectrum, monitor was plugged into mains, turned on, and laid flat on the floor to minimise its impact on results. Used LCD monitor: 24" LG LG24BK550Y 1920×1080 px
** '''LCD Display:''' [https://www.voipac.com/newhaven-lvds-capacitive-display-set Newhaven LVDS Capacitive Display Set] with 1024x600 px resolution. The display was mounted on top of the development kit with metal standoffs, active and displaying continued video stream coming from the camera thus contributing to EMC spectrum. LCD P/N: NHD-10.1-1024600MB-LSXV-CTP
* '''2x USB 3.0:''' SanDisk Ultra Flair 16GB USB 3.2 Gen 1, each connected through a 1m long USB 3.2 Gen 1 extension cable (Molex P/N: 0687890035). Both used during read/write test
* '''USB-C:''' Kingston DataTraveler 80 32GB USB 3.2 Gen 1, connected through USB-C extension cable (Cable P/N: FCR72003)
* '''Camera:''' [https://www.voipac.com/digilent-mipi-csi-camera-set Digilent MIPI-CSI Camera Set] plugged to the baseboard, recognised by the kernel, active and capturing video stream. Ferrite bead added on the ribbon cable connecting the kit and the camera module (Würth Elektronik P/N: 742 721 1)
* '''CAN:''' [https://www.voipac.com/can-bus-module CANbus Module] inserted, not actively used during testing. CAN cable not connected
* '''WiFi and Bluetooth:''' Soldered directly on COM, placed in active scanning and discoverable mode, contributing to EMC spectrum. Depending on the temperature range, the default CM-276NF or alternative SPB228-D-3 module was populated. [https://www.voipac.com/wifi-and-bluetooth-antennas-set Two antennas] plugged in and connected
* '''Console cable:''' Micro USB extension cable used only to setup the development kit, not plugged in during the measurements
* '''SD card:''' SD card (SanDisk) plugged in and used during read/write test
* '''Microphone:''' Microphone connected via 1.5m long cable, not actively used
* '''Headphones:''' Headphones connected via 2m long cable, not actively used
* '''Speakers:''' Line Out connected via 2m long cable, plugged into the mains and not actively used
 

[[image:iMX8M Industrial Development Kit-EMC overview.jpg|800px]]

== Testing conditions and results ==
All the results were measured in compliance with the emission limits for FCC / ETSI Class B (EMC standards EN 55032B and EN 61000). Class B devices are suitable for both residential and industrial applications as the norm standards use more restrictive limits.

=== iMX8M Industrial Development Kit Pro - Testing peripherals and external LCD display – PASSED ===
'''''Test description:'''''
* development kit in standard webshop Pro configuration:
** iMX8M Industrial Module Pro in Commercial temperature range
** iMX Development Baseboard in Extended temperature range
* CPU heavy testing threads using stressapptest
* DDR4 memory heavy testing threads using stressapptest
* Ethernet loopback cable used for network testing
* running heavy read/write testing for USB devices and SD card
* [https://www.voipac.com/digilent-mipi-csi-camera-set Digilent MIPI-CSI Camera Set] capturing video stream
* [https://www.voipac.com/newhaven-lvds-capacitive-display-set LCD Newhaven LVDS Capacitive Display Set] actively used
* [https://www.voipac.com/wifi-and-bluetooth-antennas-set two antennas with cables] actively used
* cables and devices plugged in but not actively used:
** USB-C
** Audio jacks
* [[#Peripherals heavy testing script|peripherals heavy testing script]] used 
[[image:iMX8M Industrial Development Kit-EMC RE-LCD display Digilent camera.jpg|800px]]

==== Radiated Emissions ====
The measurement starts with peak detection by scanning the whole frequency spectrum. This initial detection is plotted with the red curve. Afterwards the highest peaks were pointed and measured more thoroughly by quasi-peak method. These real measured values of the radiation are displayed with the red crosses. The graph shows the setup passed the strict residential 55032-B limit represented by the red highlighted line. 

These results prove that iMX8M Industrial Development Kit, even under heavy load, meets the stricter limits even if no enclosure is used.

==== Radiated emissions in lower band 30MHz - 1GHz ====
'''''Antenna used:''''' ETS Lindgren 3143B BiConiLog Antenna 30 MHz to 1GHz 
{|style="text-align:center;"
| style="width: 49%; width:396px; border:1px solid black;" | [[image:iMX8M_Industrial_Development_Kit-EMC_RE-HorPol_30MHz_1GHz-LCD_display.jpg|370px]] 
| style="width: 2%;" | 
| style="width: 49%;width:396px; border:1px solid black;" | [[image:iMX8M_Industrial_Development_Kit-EMC_RE-VerPol_30MHz_1GHz-LCD_display.jpg|370px]] 
|-
|[https://downloads.voipac.com/files/iMX8M_Industrial_Development_Kit/module/documents/EMC_certification/iMX8M_Industrial_Development_Kit-EMC-RE_30MHz-1GHz_Hor_Pol-Heavy_CPU_memory_stress_test%2BAudio%2BUSB-C%2BNHD_display%2BUSB3%2BMIPI_camera.pdf Horizontal polarisation]
| 
|[https://downloads.voipac.com/files/iMX8M_Industrial_Development_Kit/module/documents/EMC_certification/iMX8M_Industrial_Development_Kit-EMC-RE_30MHz-1GHz_Ver_Pol-Heavy_CPU_memory_stress_test%2BAudio%2BUSB-C%2BNHD_display%2BUSB3%2BMIPI_camera.pdf Vertical polarisation]
|} 

==== Radiated emissions in higher band 1GHz - 6GHz ====
Two plots displaying the power density are used to show results in higher bands. Similar to lower frequencies red curve represents quasi-peak values. Class B limits applied for quasi-peak measurements are plotted as the higher placed red line ''55032,RF,1-6GHZ,PK,B.LIN''. 
Green curve depicts average-power values. Threshold for average-power measurement is shown with the lower placed limit line called ''55032,RF,1-6GHZ,AV,B.LIN''. 

'''''Antenna used:''''' ETS Lindgren 3119 Horn Antenna 400MHz to 6GHz 
'''''Note:''''' Emissions in the 2.4 and 5 GHz band are part of the working frequency band, they will be disregarded from the evaluation of results. 

{|style="text-align:center;"
| style="width: 49%; width:396px; border:1px solid black;" | [[image:iMX8M_Industrial_Development_Kit-EMC_RE-HorPol_1GHz_6GHz-LCD_display.jpg|370px]] 
| style="width: 2%;" | 
| style="width: 49%;width:396px; border:1px solid black;" | [[image:iMX8M_Industrial_Development_Kit-EMC_RE-VerPol_1GHz_6GHz-LCD_display.jpg|370px]] 
|-
|[https://downloads.voipac.com/files/iMX8M_Industrial_Development_Kit/module/documents/EMC_certification/iMX8M_Industrial_Development_Kit-EMC-RE_1GHz-6GHz_Hor_Pol-Heavy_CPU_memory_stress_test%2BAudio%2BUSB-C%2BNHD_display%2BUSB3%2BMIPI_camera.pdf Horizontal polarisation]
| 
|[https://downloads.voipac.com/files/iMX8M_Industrial_Development_Kit/module/documents/EMC_certification/iMX8M_Industrial_Development_Kit-EMC-RE_1GHz-6GHz_Ver_Pol-Heavy_CPU_memory_stress_test%2BAudio%2BUSB-C%2BNHD_display%2BUSB3%2BMIPI_camera.pdf Vertical polarisation]
|} 

==== Conducted Emissions ====
The measurement was performed by a clamp indirect method. 
Enhanced input power protection on the iMX Development Baseboard does not allow direct line impedance stabilisation network (LISN) method to be used. 
[[image:iMX8M_Industrial_Development_Kit-EMC_CE.jpg|800px]] 

=== iMX8M Industrial Development Kit Pro - Testing module and DisplayPort output - PASSED ===
'''''Test description:'''''
* development kit in standard webshop Pro configuration:
** iMX8M Industrial Module Pro in Commercial temperature range
** iMX Development Baseboard in Extended temperature range
* CPU heavy testing threads using stressapptest
* DDR4 memory heavy testing threads using stressapptest
* Ethernet loopback cable used for network testing
* running heavy read/write testing for USB devices and SD card
* [https://www.voipac.com/digilent-mipi-csi-camera-set Digilent MIPI-CSI Camera Set] capturing video stream
* DisplayPort output tested in Full-HD 1920x1080 resolution
* [https://www.voipac.com/wifi-and-bluetooth-antennas-set two antennas with cables] actively used
* cables and devices plugged in but not actively used:
** [https://www.voipac.com/can-bus-module CANbus Module]
** USB-C
** Audio jacks
** JTAG programmer
* [[#Module heavy testing script|module heavy testing script]] used 

[[image:iMX8M_Industrial_Development_Kit-EMC_RE-DisplayPort.jpg|800px]]

==== Radiated Emissions ====
The measurement starts with peak detection by scanning the whole frequency spectrum. This initial detection is plotted with the red curve. Afterwards the highest peaks were pointed and measured more thoroughly by quasi-peak method. These real measured values of the radiation are displayed with the red crosses. The graph shows the setup passed the strict residential 55032-B limit represented by the red highlighted line. 

These results prove that iMX8M Industrial Development Kit, even under heavy load, meets the stricter limits even if no enclosure is used.

==== Radiated emissions in lower band 30MHz - 1GHz ====
'''''Antenna used:''''' ETS Lindgren 3143B BiConiLog Antenna 30 MHz to 1GHz 
'''''Note:''''' Results in higher band 1GHz - 6GHz were very similar to the measurements performed on the [[#Radiated emissions in higher band 1GHz - 6GHz|previous]] testing setup
{|style="text-align:center;"
| style="width: 49%; width:396px; border:1px solid black;" | [[image:iMX8M_Industrial_Development_Kit-EMC_RE-HorPol_30MHz_1GHz-DisplayPort.jpg|370px]] 
| style="width: 2%;" | 
| style="width: 49%;width:396px; border:1px solid black;" | [[image:iMX8M_Industrial_Development_Kit-EMC_RE-VerPol_30MHz_1GHz-DisplayPort.jpg|370px]] 
|-
|[https://downloads.voipac.com/files/iMX8M_Industrial_Development_Kit/module/documents/EMC_certification/iMX8M_Industrial_Development_Kit-EMC-RE_30MHz-1GHz_Hor_Pol-Heavy_CPU_memory_stress_test%2BAudio%2BUSB-C%2BDisplayPort_with_ferrite_beads%2BUSB3%2BMIPI_camera%2BCAN%2BJTAG.pdf Horizontal polarisation]
| 
|[https://downloads.voipac.com/files/iMX8M_Industrial_Development_Kit/module/documents/EMC_certification/iMX8M_Industrial_Development_Kit-EMC-RE_30MHz-1GHz_Ver_Pol-Heavy_CPU_memory_stress_test%2BAudio%2BUSB-C%2BDisplayPort_with_ferrite_beads%2BUSB3%2BMIPI_camera%2BCAN%2BJTAG.pdf Vertical polarisation]
|} 

=== iMX8M Industrial Development Kit Pro - Testing module and HDMI output - PASSED ===
'''''Test description:'''''
* development kit in standard webshop Pro configuration:
** iMX8M Industrial Module Pro in Commercial temperature range
** iMX Development Baseboard in Extended temperature range
* CPU heavy testing threads using stressapptest
* DDR4 memory heavy testing threads using stressapptest
* Ethernet loopback cable used for network testing
* running heavy read/write testing for USB devices and SD card
* [https://www.voipac.com/digilent-mipi-csi-camera-set Digilent MIPI-CSI Camera Set] capturing video stream
* HDMI output tested in Full-HD 1920x1080 resolution
* [https://www.voipac.com/wifi-and-bluetooth-antennas-set two antennas with cables] actively used
* cables and devices plugged in but not actively used:
** USB-C
** Audio jacks
* [[#Module heavy testing script|module heavy testing script]] used 

==== Radiated Emissions ====
The measurement starts with peak detection by scanning the whole frequency spectrum. This initial detection is plotted with the red curve. Afterwards the highest peaks were pointed and measured more thoroughly by quasi-peak method. These real measured values of the radiation are displayed with the red crosses. The graph shows the setup passed the strict residential 55032-B limit represented by the red highlighted line. 

These results prove that iMX8M Industrial Development Kit, even under heavy load, meets the stricter limits even if no enclosure is used.

==== Radiated emissions in lower band 30MHz - 1GHz ====
'''''Antenna used:''''' ETS Lindgren 3143B BiConiLog Antenna 30 MHz to 1GHz 
'''''Note:''''' Results in higher band 1GHz - 6GHz were very similar to the measurements performed on the [[#Radiated emissions in higher band 1GHz - 6GHz|previous]] testing setup
{|style="text-align:center;"
| style="width: 49%; width:396px; border:1px solid black;" | [[image:iMX8M_Industrial_Development_Kit-EMC_RE-HorPol_30MHz_1GHz-HDMI.jpg|370px]] 
| style="width: 2%;" | 
| style="width: 49%;width:396px; border:1px solid black;" | [[image:iMX8M_Industrial_Development_Kit-EMC_RE-VerPol_30MHz_1GHz-HDMI.jpg|370px]] 
|-
|[https://downloads.voipac.com/files/iMX8M_Industrial_Development_Kit/module/documents/EMC_certification/iMX8M_Industrial_Development_Kit-EMC-RE_30MHz-1GHz_Hor_Pol-Heavy_CPU_memory_stress_test%2BAudio%2BUSB-C%2BHDMI_with_ferrite_beads%2BUSB3.pdf Horizontal polarisation]
| 
|[https://downloads.voipac.com/files/iMX8M_Industrial_Development_Kit/module/documents/EMC_certification/iMX8M_Industrial_Development_Kit-EMC-RE_30MHz-1GHz_Ver_Pol-Heavy_CPU_memory_stress_test%2BAudio%2BUSB-C%2BHDMI_with_ferrite_beads%2BUSB3.pdf Vertical polarisation]
|} 

=== Immunity - Radio frequency electromagnetic field 80MHz - 6GHz ===
[[image:iMX8M_Industrial_Development_Kit-EMC_Immunity-RF_EM_Field.jpg|800px]]

{| class="wikitable" style="text-align:center;"
!colspan="2"| !! colspan="4" style="text-align:right;"|Test results / EUT side exposure results
|-
!Frequency range (MHz) !! Antenna polarization !! Front !! Back !! Left !! Right
|-
|80 – 1000 || V || PASS || PASS || PASS || PASS
|-
|1000 – 6000 (*) || V || PASS || PASS || PASS || PASS
|-
|80 – 1000 || H || PASS || PASS || PASS || PASS
|-
|1000 – 6000 (*) || H || PASS || PASS || PASS || PASS
|}

'''''Note (*):''''' The exclusion bands are applicable in this frequency range.

=== Conducted emission - wired network ports ===
[[image:iMX8M_Industrial_Development_Kit-EMC_CE-Network_wire_port.jpg|800px]]

{|style="text-align:center;"
| style="width: 49%; width:396px; border:1px solid black;" | [[image:iMX8M_Industrial_Development_Kit-EMC_CE-Network_wire_port-Results.jpg|370px]] 
| style="width: 51%;" | 
|} 

=== Immunity - Electrostatic discharge ===
[[image:iMX8M_Industrial_Development_Kit-EMC_Immunity-ESD.jpg|800px]]

{| class="wikitable" style="text-align:center;"
!Discharge type !! Discharge level (kV) !! Discharge location !! Number of discharges per location for each polarity (number of locations) !! Performance criterion !! Test result
|-
| Direct air discharge || ±8 || Non metallic parts || 10 (17) || B || PASS
|-
| Direct contact discharge || ±4 || Metallic parts || 10 (9) || B || PASS
|-
| Indirect contact discharge || ±4 || HCP - Front || 10 || B || PASS
|-
| Indirect contact discharge || ±4 || HCP - Left || 10 || B || PASS
|-
| Indirect contact discharge || ±4 || HCP - Right || 10 || B || PASS
|-
| Indirect contact discharge || ±4 || HCP - Rear || 10 || B || PASS
|-
| Indirect contact discharge || ±4 || VCP - Front || 10 || B || PASS
|-
| Indirect contact discharge || ±4 || VCP - Left || 10 || B || PASS
|-
| Indirect contact discharge || ±4 || VCP - Right || 10 || B || PASS
|-
| Indirect contact discharge || ±4 || VCP - Rear || 10 || B || PASS
|}

'''''Note (*):''''' The EUT was without exposed conductive surfaces. 
'''''Abbreviation:''''' HCP - Horizontal coupling plane 
'''''Abbreviation:''''' VCP - Vertical coupling plane 

== Preparing the test ==
=== Boot device and software ===
These measurements were performed with boards using the actual hardware and software configuration of the web shop development kits. 

eMMC Flash memory was selected as a booting device for all the measurements. U-Boot settings were not adjusted as the default configuration was used.

=== Running the script ===
Plug the development kit into mains and connect it to the controlling PC via console. Before the first time usage of the script, permissions need to be granted by the following command:
<syntaxhighlight lang="bash">
chmod +x imx8m-voipac-peripheral-test.sh
</syntaxhighlight>
 
Testing scripts command consists of the following arguments:
* the first parameter - configuration of tested development kit (Max, Pro or Basic)
* the second parameter - USB drive 1 location
* the third parameter - USB drive 2 location
* the fourth parameter - SD card location
 
One of these commands can be used during EMC testing as shown below:

* iMX8M Industrial Development Kit Max:
<syntaxhighlight lang="bash">
./imx8m-voipac-peripheral-test.sh -max sda1 sdb1 mmcblk1p1 | tee -i imx8m-emc-testing.log
</syntaxhighlight>
* iMX8M Industrial Development Kit Pro:
<syntaxhighlight lang="bash">
./imx8m-voipac-peripheral-test.sh -pro sda1 sdb1 mmcblk1p1 | tee -i imx8m-emc-testing.log
</syntaxhighlight>
* iMX8M Industrial Development Kit Basic:
<syntaxhighlight lang="bash">
./imx8m-voipac-peripheral-test.sh -basic sda1 sdb1 mmcblk1p1 | tee -i imx8m-emc-testing.log
</syntaxhighlight>

== Testing scripts ==
=== Peripherals heavy testing script ===
This code was used during the measurements, focusing on peripherals influence on the emissions. The complete script can also be found in [https://downloads.voipac.com/files/iMX8M_Industrial_Development_Kit/module/documents/EMC_certification/imx8m-voipac-peripheral-test.sh the downloads section].
<syntaxhighlight lang="bash">
#!/bin/sh

# iMX8M Industrial Development Kit peripheral test

mountDevice() {
mkdir -p "/media/$2"
mount /dev/$1 /media/$2
cat /proc/mounts | grep -F "/dev/$1 /media/$2"
if [ "$?" -eq "0" ]; then
echo "$2 mounted"
else
echo "$2 not mounted"; exit 2
fi
}

# prepare files
cd ~/
mkdir -p imx8m-industrial-testing/
cd imx8m-industrial-testing/

touch imx8m-industrial-testing.log
touch cpu-temp.log

basic=0
pro=0
max=0
case $1 in
-basic) basic=1 ;;
-pro) pro=1 ;;
-max) max=1 ;;
*)
esac

# mount devices
mountDevice $2 usb0
mountDevice $3 usb1
mountDevice $4 mmc0

updateLogFiles() {
# obtain board ID from IP address - be sure addresses are allocated based on MAC
boardID=$(/sbin/ip -o -4 addr list eth0 | awk '{print $4}' | cut -d/ -f1 | cut -d'.' -f4 | cut -d'2' -f2);
# be sure time server is running on DHCP server
currentTime=`date +%Y-%m-%d.%H:%M`

mv imx8m-industrial-testing.log imx8m-industrial-$boardID-testing.log.$currentTime
mv cpu-temp.log imx8m-industrial-$boardID-cpu-temp.log.$currentTime
}

finish_test_now() {
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) Ctrl+C Detected: End of the test"
precced=0;
#kill -INT $vid_pid $str_pid $log_pid;
sleep 3;
test_status=`cat imx8m-industrial-testing.log | grep -i "error" | grep -v -e "0 errors" -e "no corrected errors"`
if [ -z "$test_status" ]
then
echo "*********TEST PASS*********"
else
echo "*********TEST FAIL*********"
echo "List of detected errors:"
cat imx8m-industrial-testing.log | grep -i "error" | grep -v -e "0 errors" -e "no corrected errors" -e "List of detected errors:"
fi
updateLogFiles
exit;
}

# kill all processes if Ctrl+C is detected
trap finish_test_now 2

# play video stream
gst-launch-1.0 -q imxv4l2src ! autovideosink &

# stressapptest - CPU threads and RAM memory threads
if [ "${basic}" -eq "1" ]; then
stress-ng --cpu 2 --vm 4 &
str_pid=$!
fi
if [ "${pro}" -eq "1" ]; then
stress-ng --cpu 4 --vm 4 &
str_pid=$!
fi
if [ "${max}" -eq "1" ]; then
stress-ng --cpu 4 --vm 4 &
str_pid=$!
fi
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) Starting stressapptest with PID: " $str_pid

proceed=1
# create test files
file1_path=`mktemp`
file2_path=`mktemp`
file1=`basename $file1_path`
file2=`basename $file2_path`

dd if=/dev/urandom of=$file1_path bs=1024 count=10000
dd if=/dev/urandom of=$file2_path bs=1024 count=10000

cp1_from="/media/mmc0/"
cp1_to="/media/usb0/"

cp2_from="/media/usb0/"
cp2_to="/media/usb1/"

#copy files in case they are missing
cp $file1_path $cp1_from
cp $file1_path $cp1_to
cp $file2_path $cp2_from
cp $file2_path $cp2_to

while [ $proceed -eq 1 ]
do
# before running script check if the ip address exist
ping -q -c1 192.168.0.2 >> imx8m-industrial-testing.log
if [ $? -ne 0 ]
then
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) ERROR: Ping failed"
else
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) Ping OK"
fi

cp1_done=`ps | grep $cp1_pid | grep cp`
if [ -z "$cp1_done" ]; then # copy finished
if cmp -s $cp1_from$file1 $cp1_to$file1; then
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) PASS: Copying file from $cp1_from to $cp1_to successful"
else
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) ERROR: Difference between files on $cp1_from and $cp1_to detected"
fi
cp1_temp=$cp1_from # swap destinations
cp1_from=$cp1_to
cp1_to=$cp1_temp

rm $cp1_to$file1 # remove destination file

cp $cp1_from$file1 $cp1_to$file1 &
cp1_pid=$!
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) Started copying file from $cp1_from to $cp1_to"
fi

cp2_done=`ps | grep $cp2_pid | grep cp`
if [ -z "$cp2_done" ]; then # copy finished
if cmp -s $cp2_from$file2 $cp2_to$file2; then
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) PASS: Copying file from $cp2_from to $cp2_to successful"
else
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) ERROR: Difference between files on $cp2_from and $cp2_to detected"
fi
cp2_temp=$cp2_from # swap destinations
cp2_from=$cp2_to
cp2_to=$cp2_temp

rm $cp2_to$file2 # remove destination file

cp $cp2_from$file2 $cp2_to$file2 &
cp2_pid=$!
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) Started copying file from $cp2_from to $cp2_to"
fi

done
</syntaxhighlight>

=== Module heavy testing script ===
This script was utilised for testing procedure where the measurement was primarily focused on the module emissions. To use this script, plug the development kit into mains, connect it to controlling PC via console and copy the code below:
<syntaxhighlight lang="bash">
for d in $(seq 1 1 999)
do
uptime
echo "Test $a Test $b Test $c $d times"
echo "Start stress-ng --iomix 1 -t 10 -v"
stress-ng --iomix 1 -t 10 -v
echo "End"
echo "Start Thermal zone information"
stress-ng --matrix 0 --tz -t 10 --log-brief -t 10
echo "End"
ping -q -c1 192.168.0.2 >> imx8m-industrial-testing.log
if [ $? -ne 0 ]
then
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) ERROR: Ping failed"
fi
echo "End"
done
</syntaxhighlight>

=== Starting camera capture ===
To initiate the Digilent camera to start the recording of video stream, following command can be used:
<syntaxhighlight lang="bash">
GST_DEBUG=GST_BUFFER:5 gst-launch-1.0 v4l2src device=/dev/video1 ! 'video/x-raw,framerate=30/1' ! autovideosink
</syntaxhighlight>

iMX91 Industrial Environmental chamber testing

2025-10-22T19:25:07Z

Voipac-sw:

'''''Environmental chamber testing of iMX91 Industrial Development Kit is successfully finished.''''' 
'''''Content of this page is currently being updated.'''''
 
 

[[Category:iMX91 Industrial Development Kit]]
[[Category:iMX91 Industrial Development Kit Testing]]

<div style="float:right">__TOC__</div>

Environmental stress testing results of iMX91 Industrial Development Kit are displayed on this page. Detailed instructions on how to setup the kits are also shown.

== Hardware configuration ==
All of the modules used standard specification except of the temperature ranges for the key components as described below:
 
* 1x iMX91 Industrial Development Kit in [[iMX91 Industrial Max|Max configuration]]
** i.MX 93 Dual 1.7GHz CPU - extended industrial temperature range (-40°C to +105°C)
** 2GB LPDDR4 Memory - extended industrial temperature range (-40°C to +105°C)
** eMMC Flash 32GB - industrial temperature range (-40°C to +85°C)
** 2x 1Gb Ethernet PHY - industrial temperature range (-40°C to +85°C)
** WiFi 6 & Bluetooth 5.3 Module - industrial temperature range (-40°C to +85°C)
 
* 1x iMX91 Industrial Development Kit in [[iMX91 Industrial Pro|Pro configuration]]
** i.MX 93 Dual 1.7GHz CPU - extended industrial temperature range (-40°C to +105°C)
** 2GB LPDDR4 Memory - extended industrial temperature range (-40°C to +105°C)
** eMMC Flash 16GB - industrial temperature range (-40°C to +85°C)
** 2x 1Gb Ethernet PHY - industrial temperature range (-40°C to +85°C)
** WiFi 4 & Bluetooth 5.2 Module - industrial temperature range (-40°C to +85°C)
 
* 1x iMX91 Industrial Development Kit in [[iMX91 Industrial Basic|Basic configuration]]
** i.MX 93 Solo 1.7GHz CPU - extended industrial temperature range (-40°C to +105°C)
** 1GB LPDDR4 Memory - extended industrial temperature range (-40°C to +105°C)
** eMMC Flash 8GB - industrial temperature range (-40°C to +85°C)
** 1Gb Ethernet PHY - industrial temperature range (-40°C to +85°C)
 
* 1x iMX91 Industrial Development Kit in [[iMX91 Industrial Lite|Lite configuration]]
** i.MX 93 Solo 900MHz CPU - extended industrial temperature range (-40°C to +105°C)
** 512MB LPDDR4 Memory - extended industrial temperature range (-40°C to +105°C)
** eMMC Flash 4GB - industrial temperature range (-40°C to +85°C)
 
All of the tested modules used standard configuration of iMX Development Baseboard with extended temperature range (-20°C to +70°C). The majority of tested kits used the standard heatsink sized 25x25x25mm, which is included in every development kit package, thus showcasing that this standardised heatsink performs even in very harsh conditions. 

The setup in the environmental chamber: 
[[image:iMX93_Industrial_Development_Kits-Enviromental_chamber_overview_with_description.jpg|800px]]

== Test description ==
Four iMX91 Industrial Development Kits (one in Max Industrial configuration, one in Pro Industrial configuration, one in Basic Industrial configuration and one in Lite Industrial configuration) were running CPU and memory tests to stress out all the most significant peripherals in the whole Industrial temperature scale, ranging from -40°C to +85°C, to check the reliability and stability of the firmware and hardware design. 

Configuration, software and testing threads in details: 

'''1x iMX91 Industrial Development Kit [setup no. 4] in [[iMX91 Industrial Max|Max configuration]] and Industrial temperature range CPU and memory stress testing'''
* 1 thread of extensive DDR4 Memory stress test
* 1 thread of CPU stress test
* all the messages were displayed on the serial console connected via Micro USB cable
* firmware running from eMMC Flash memory
* 2x Ethernet cable connected to network switch placed outside of the chamber
* 2x USB device connected and placed outside of the chamber
* WiFi and Bluetooth module active, connected to the antennas and running discovery mode
* standard 25x25x25mm heatsink
 
'''1x iMX91 Industrial Development Kit [setup no. 3] in [[iMX91 Industrial Pro|Pro configuration]] and Industrial temperature range CPU and memory stress testing'''
* 1 thread of extensive DDR4 Memory stress test
* 1 thread of CPU stress test
* all the messages were displayed on the serial console connected via Micro USB cable
* firmware running from eMMC Flash memory
* 2x Ethernet cable connected to network switch placed outside of the chamber
* 2x USB device connected and placed outside of the chamber
* WiFi and Bluetooth module active, connected to the antennas and running discovery mode
* standard 25x25x25mm heatsink
 
'''1x iMX91 Industrial Development Kit [setup no. 2] in [[iMX91 Industrial Basic|Basic configuration]] and Industrial temperature range CPU and memory stress testing'''
* 1 thread of extensive DDR4 Memory stress test
* 1 thread of CPU stress test
* all the messages were displayed on the serial console connected via Micro USB cable
* firmware running from eMMC Flash memory
* Ethernet cable connected to network switch placed outside of the chamber
* 2x USB device connected and placed outside of the chamber
* standard 25x25x25mm heatsink
 
'''1x iMX91 Industrial Development Kit [setup no. 1] in [[iMX91 Industrial Lite|Lite configuration]] and Industrial temperature range CPU and memory stress testing'''
* 1 thread of extensive DDR4 Memory stress test
* 1 thread of CPU stress test
* all the messages were displayed on the serial console connected via Micro USB cable
* firmware running from eMMC Flash memory
* 2x USB device connected and placed outside of the chamber
* standard 25x25x25mm heatsink
 
Power source, USB flash devices, network switch and controlling PC were placed outside the environmental chamber. All the scripts running during the test and the board setup instructions can be found in section [[#Preparing the test|How to prepare the test]].

== Testing Results ==
The picture below shows the temperature profile during the whole testing process. Humidity was not controlled. The temperature gradient for the environment chamber was set to 1°C/min. 
[[image:iMX8M_Industrial_Development_Kit-Env_chamber_temperature_profile.png|800px]]

=== Running the development kits at -40°C – PASS ===
Test description: CPU, Memory and peripheral stress tests were running at -40°C. All the tested kits were working without errors during the whole time. 

A closer image on the temperature chamber displaying the minimum temperature is shown below. These readouts are available on the display:
* the first number shows current temperature
* the second one set temperature
* the last two shows relative humidity. Humidity was not controlled during testing process.
[[image:iMX8M Industrial Kit-Env chamber-Boards at -40C.jpg|800px]]
 
[[image:iMX8M_Industrial_Development_Kit-Env_chamber_at_-40C.jpg|800px]]

=== Running the development kits at +85°C – PASS ===
Test description: The pre-set temperature profile was followed until the development kits gradually reached +85°C. The kits remained around this temperature for the duration of two hours and at the end of this whole cycle all the kits were running. 

When using both the iMX8M and iMX91 Industrial Modules with common baseboard, please note the difference when the CPUs are above the critically high temperature of +85°C: 
'''''i.MX 8M CPU – waiting for the temperature decline, than reboots itself''''' 
'''''i.MX 93 CPU – powers down'''''

[[image:iMX8M_Industrial_Kit-Env_chamber-Boards_at_+86C.jpg|800px]]
 
[[image:iMX8M_Industrial_Development_Kit-Env_chamber_at_+85C.jpg|800px]]

=== Switch OFF/ON test at -40°C – PASS ===
Test description: At temperature -40°C the development kits were switched OFF, left OFF for at least 15 minutes (to cool down completely) and then switched ON to see if they boot up without problems. Once booted up into Linux, the test script was launched to test RAM memory and all peripherals. The kits were turned OFF and ON again multiple times to see potential issues at the lowest temperature level. All of the tested setups booted up successfully.

 
[[image:iMX8M Industrial Kit-Env chamber-Boards snow.jpg|800px]]

== PC setup ==
The PC was used during the test to control / monitor all the kits through serial console sessions. The control computer was running Windows 10 operating system.

=== Serial console ===
To control iMX91 Industrial Development Kits, one TeraTerm serial console was opened for each setup.
 
The setup of the environmental chamber cables and out-of-chamber equipment:
 
[[image:iMX8M Industrial Development Kit-Climate chamber overview.jpg|800px]]

== Preparing the test ==
=== Boot device and software ===
The eMMC memory was selected as a booting device for all the kits. Device tree files were not adjusted as the default configuration was used. The only change compared to standard software package was running the test script. In order to flash a fresh firmware into the eMMC Memory follow [[iMX91_Industrial_Flashing_Procedure|these instructions]].

=== Downloading stress test ===
Stress-ng package was selected to check CPU and memory integrity. Placing this file into the same directory where the testing script will be stored is important:
<syntaxhighlight lang="bash">
wget https://downloads.voipac.com/files/iMX91_Industrial_Development_Kit/module/documents/Thermal_stress_resistance/iMX91q-voipac-peripheral-test.sh
</syntaxhighlight>

=== Start CPU and memory stress test ===
Navigate into the directory, where stress test feature and the testing script are stored. 

Stress sequence script:
<syntaxhighlight lang="bash">
for d in $(seq 1 1 99999)
do
uptime
echo "Test $a Test $b Test $c $d times"
echo "Start stress-ng --iomix 1 -t 10 -v"
stress-ng --iomix 1 -t 10 -v
echo "End"
echo "Start stress-ng --cpu 2 --vm 4 -t 10"
stress-ng --cpu 2 --vm 4 -t 10
echo "End"
echo "Start stress-ng --shm 0 -t 10"
stress-ng --shm 0 -t 10
echo "End"
echo "Start stress-ng --seq 0 -t 2 --tz -v"
stress-ng --seq 0 -t 2 --tz -v
echo "End"
echo "Start Thermal zone information"
stress-ng --matrix 0 --tz -t 10 --log-brief -t 10
echo "End"
done
</syntaxhighlight>

=== Start peripheral test ===
Plug the development kit into mains and connect it to the controlling PC via console. Before the first time usage of the script, permissions need to be granted by the following command:
<syntaxhighlight lang="bash">
chmod +x iMX91-voipac-peripheral-test.sh
</syntaxhighlight>
 
Testing scripts command consists of the following arguments:
* the first parameter - configuration of tested development kit (Max, Pro, Basic or Lite)
* the second parameter - USB drive 1 location
* the third parameter - USB drive 2 location
* the fourth parameter - SD card location
 
Several commands used during environmental chamber testing are shown below:

* iMX91 Industrial Development Kit Max:
<syntaxhighlight lang="bash">
./iMX91-voipac-peripheral-test.sh -max sda1 sdb1 mmcblk1p1 | tee -i iMX91-env-testing.log
</syntaxhighlight>
* iMX91 Industrial Development Kit Pro:
<syntaxhighlight lang="bash">
./iMX91-voipac-peripheral-test.sh -pro sda1 sdb1 mmcblk1p1 | tee -i iMX91-env-testing.log
</syntaxhighlight>
* iMX91 Industrial Development Kit Basic:
<syntaxhighlight lang="bash">
./iMX91-voipac-peripheral-test.sh -basic sda1 sdb1 mmcblk1p1 | tee -i iMX91-env-testing.log
</syntaxhighlight>
* iMX91 Industrial Development Kit Lite:
<syntaxhighlight lang="bash">
./iMX91-voipac-peripheral-test.sh -lite sda1 sdb1 mmcblk1p1 | tee -i iMX91-env-testing.log
</syntaxhighlight>
 
The complete script can be found in [https://downloads.voipac.com/files/iMX91_Industrial_Development_Kit/module/documents/Thermal_stress_resistance/iMX91-voipac-peripheral-test.sh the downloads section] or down below:
<syntaxhighlight lang="bash">
#!/bin/sh

# iMX91 environmental chamber peripheral test

mountDevice() {
mkdir -p "/media/$2"
mount /dev/$1 /media/$2
cat /proc/mounts | grep -F "/dev/$1 /media/$2"
if [ "$?" -eq "0" ]; then
echo "$2 mounted"
else
echo "$2 not mounted"; exit 2
fi
}

# prepare files
cd ~/
mkdir -p env-chamber-testing/
cd env-chamber-testing/

touch env-chamber-testing.log
touch cpu-temp.log

basic=0
pro=0
max=0
case $1 in
-basic) basic=1 ;;
-pro) pro=1 ;;
-max) max=1 ;;
*)
esac

# mount devices
mountDevice $2 usb0
mountDevice $3 usb1
mountDevice $4 mmc0

updateLogFiles() {
# obtain board ID from IP address - be sure addresses are allocated based on MAC
boardID=$(/sbin/ip -o -4 addr list eth0 | awk '{print $4}' | cut -d/ -f1 | cut -d'.' -f4 | cut -d'2' -f2);
# be sure time server is running on DHCP server
currentTime=`date +%Y-%m-%d.%H:%M`

mv env-chamber-testing.log trx-board-$boardID-env-chamber.log.$currentTime
mv cpu-temp.log trx-board-$boardID-env-cpu-temp.log.$currentTime
}

finish_test_now() {
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) Ctrl+C Detected: End of the test"
precced=0;
#kill -INT $vid_pid $str_pid $log_pid;
sleep 3;
test_status=`cat env-chamber-testing.log | grep -i "error" | grep -v -e "0 errors" -e "no corrected errors"`
if [ -z "$test_status" ]
then
echo "*********TEST PASS*********"
else
echo "*********TEST FAIL*********"
echo "List of detected errors:"
cat env-chamber-testing.log | grep -i "error" | grep -v -e "0 errors" -e "no corrected errors" -e "List of detected errors:"
fi
updateLogFiles
exit;
}

# kill all processes if Ctrl+C is detected
trap finish_test_now 2

# play a video stream
gst-launch-1.0 -q imxv4l2src ! autovideosink &

# stressapptest - CPU threads and RAM memory threads
if [ "${basic}" -eq "1" ]; then
stress-ng --cpu 2 --vm 4 &
str_pid=$!
fi
if [ "${pro}" -eq "1" ]; then
stress-ng --cpu 4 --vm 4 &
str_pid=$!
fi
if [ "${max}" -eq "1" ]; then
stress-ng --cpu 4 --vm 4 &
str_pid=$!
fi
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) Starting stressapptest with PID: " $str_pid

proceed=1
# create test files
file1_path=`mktemp`
file2_path=`mktemp`
file1=`basename $file1_path`
file2=`basename $file2_path`

dd if=/dev/urandom of=$file1_path bs=1024 count=10000
dd if=/dev/urandom of=$file2_path bs=1024 count=10000

cp1_from="/media/mmc0/"
cp1_to="/media/usb0/"

cp2_from="/media/usb0/"
cp2_to="/media/usb1/"

#copy files in case they are missing
cp $file1_path $cp1_from
cp $file1_path $cp1_to
cp $file2_path $cp2_from
cp $file2_path $cp2_to

while [ $proceed -eq 1 ]
do

ping -q -c1 192.168.0.2 >> env-chamber-testing.log
if [ $? -ne 0 ]
then
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) ERROR: Ping failed"
fi

cp1_done=`ps | grep $cp1_pid | grep cp`
if [ -z "$cp1_done" ]; then # copy finished
if cmp -s $cp1_from$file1 $cp1_to$file1; then
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) PASS: Copying file from $cp1_from to $cp1_to successful"
else
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) ERROR: Difference between files on $cp1_from and $cp1_to detected"
fi
cp1_temp=$cp1_from # swap destinations
cp1_from=$cp1_to
cp1_to=$cp1_temp

rm $cp1_to$file1 # remove destination file

cp $cp1_from$file1 $cp1_to$file1 &
cp1_pid=$!
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) Started copying file from $cp1_from to $cp1_to"
fi

cp2_done=`ps | grep $cp2_pid | grep cp`
if [ -z "$cp2_done" ]; then # copy finished
if cmp -s $cp2_from$file2 $cp2_to$file2; then
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) PASS: Copying file from $cp2_from to $cp2_to successful"
else
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) ERROR: Difference between files on $cp2_from and $cp2_to detected"
fi
cp2_temp=$cp2_from # swap destinations
cp2_from=$cp2_to
cp2_to=$cp2_temp

rm $cp2_to$file2 # remove destination file

cp $cp2_from$file2 $cp2_to$file2 &
cp2_pid=$!
echo "$(date +\%Y/\%m/\%d-\%T)($(date +\%Z)) Started copying file from $cp2_from to $cp2_to"
fi

done
</syntaxhighlight>

iMX91 Industrial Accessing and Testing Peripherals

2025-10-22T19:23:00Z

Voipac-sw:

[[Category:iMX91 Industrial]]
[[Category:iMX91 Industrial Software]]
[[Category:iMX91 Industrial Testing]]
[[Category:iMX91 Industrial Peripherals]]

<div style="float:right">__TOC__</div>

The initial operations with the iMX91 Industrial Development Kit interfaces are presented on this page. For more specific information such as display options, camera capabilities or industrial modular extensions, refer to the dedicated [[iMX91 Industrial Max#Peripherals_and_Accessories|Peripherals and Accessories section]].

== Mandatory components ==
=== Hardware ===
* iMX91 Industrial Module
* iMX Development Baseboard
* [https://www.voipac.com/power-supply-5v-20w DC power supply (5V, 4A, 20W)]

=== Peripherals and Accessories ===
* [https://www.voipac.com/boe-lvds-capacitive-display-set BOE LVDS Capacitive Display Set] (optional)
* [https://www.voipac.com/digilent-mipi-csi-camera-set Digilent MIPI-CSI Camera Set] (optional)
* [https://www.voipac.com/imx9-wifi-and-bluetooth-antennas-set iMX9 Wifi and Bluetooth antenna set]
* [https://www.voipac.com/voice-command-demo Voice Command demo] (optional)
* 1x MicroSDHC card Class 10 or higher
* 1x USB Flash drive 2.0
* Headphones
* Analog external microphone

=== Cables ===
* USB Micro-B cable for serial console
* USB-C cable for module flashing
* Ethernet cable

== Audio ==
'''''Note:''''' This audio section was tested with the iMX91 Industrial Module in Max and Pro configurations. For Basic and LIte configuration, audio capabilities are not available. For more information see [[iMX91 Industrial Development Kit|the iMX91 Industrial Module comparison]]. 

'''''Input:''''' Search kernel log for wm8904 chip 
'''''Output:''''' Audio chip is detected and bound as an output and input device
<syntaxhighlight lang="bash">
root@imx91-voipac:~# dmesg | grep wm8904
[ 6.546858] wm8904 0-001a: supply DCVDD not found, using dummy regulator
[ 6.591866] wm8904 0-001a: supply DBVDD not found, using dummy regulator
[ 6.611921] wm8904 0-001a: supply AVDD not found, using dummy regulator
[ 6.637768] wm8904 0-001a: supply CPVDD not found, using dummy regulator
[ 6.670934] wm8904 0-001a: supply MICVDD not found, using dummy regulator
[ 6.683500] wm8904 0-001a: revision A
</syntaxhighlight>

'''''Input:''''' Run amixer command 
'''''Output:''''' Current audio chip settings are displayed
<syntaxhighlight lang="bash">
root@imx91-voipac:~# amixer
Simple mixer control 'Headphone',0
Capabilities: volume pswitch
Playback channels: Front Left - Front Right
Capture channels: Front Left - Front Right
Limits: 0 - 63
Front Left: 45 [71%] [-12.00dB] Playback [on]
Front Right: 45 [71%] [-12.00dB] Playback [on]
Simple mixer control 'Headphone ZC',0
Capabilities: pswitch
Playback channels: Front Left - Front Right
Mono:
Front Left: Playback [on]
Front Right: Playback [on]
Simple mixer control 'Line Output',0
Capabilities: volume pswitch
Playback channels: Front Left - Front Right
Capture channels: Front Left - Front Right
Limits: 0 - 63
Front Left: 57 [90%] [0.00dB] Playback [on]
Front Right: 57 [90%] [0.00dB] Playback [on]
...
</syntaxhighlight>

'''''Input:''''' Connect headphones into LINE OUT jack connector 
'''''Output:''''' Audio file is played and heard
<syntaxhighlight lang="bash">
root@imx8mq-voipac:~# aplay /usr/share/multimedia/sample.wav
Playing WAVE 'multimedia/sample.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
root@imx8mq-voipac:~# aplay -D sysdefault:CARD=wm8904audio /usr/share/multimedia/sample.wav
Playing WAVE 'multimedia/sample.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
</syntaxhighlight>

'''''Input:''''' Plug headphones into HEADPHONES jack connector and analog external microphone to MIC jack connector 
'''''Output:''''' Sound recorder by microphone is played in headphones
<syntaxhighlight lang="bash">
root@imx91-voipac:~# amixer set 'Capture' '31'
root@imx91-voipac:~# amixer set 'Capture Input' ADC
root@imx91-voipac:~# amixer set 'Left Capture Inverting Mux' 'IN2L'
root@imx91-voipac:~# amixer set 'Right Capture Inverting Mux' 'IN2R'
root@imx91-voipac:~# arecord -D sysdefault:CARD=wm8904audio -t wav -f cd | aplay -D sysdefault:CARD=wm8904audio
</syntaxhighlight>

'''''Note:''''' Microphone and headphones setup can also be graphically displayed and adjusted:
<syntaxhighlight lang="bash">
root@imx91-voipac:~# alsamixer
</syntaxhighlight>
[[image:iMX8M_Industrial_Development_Kit-AlsaMixer_setup.png|800px]] 

'''''Input:''''' Verify digital microphones (Mic Left, Mic Mid, Mic Right) 
'''''Output:''''' Microphone sound is played in headphones
<syntaxhighlight lang="bash">
root@imx91-voipac:~# amixer set "Capture Input" "DMIC"
root@imx91-voipac:~# arecord -D sysdefault:CARD=wm8904audio -t wav -f cd | aplay -D sysdefault:CARD=wm8904audio
</syntaxhighlight>

== WiFi ==
'''''Note:''''' This WiFi section was tested with the iMX91 Industrial Module in Max and Pro configurations. For Basic and Lite configurations, wireless connectivity is not available. For more information see [[iMX91 Industrial Development Kit|the iMX91 Industrial Module comparison]]. 

Load the device driver:
<syntaxhighlight lang="bash">
root@imx91-voipac:~# modprobe moal mod_para=nxp/wifi_mod_para.conf
[ 926.305344] mlan: loading out-of-tree module taints kernel.
[ 926.334171] wlan: Loading MWLAN driver
[ 926.339152] wlan: Register to Bus Driver...
[ 926.343686] vendor=0x02DF device=0x9159 class=0 function=1
[ 926.349765] Attach moal handle ops, card interface type: 0x108
[ 926.355633] rps set to 0 from module param
[ 926.362045] SDIW416: init module param from usr cfg
[ 926.366995] card_type: SDIW416, config block: 0
[ 926.371541] cfg80211_wext=0xf
[ 926.374515] max_vir_bss=1
[ 926.377131] cal_data_cfg=none
[ 926.380112] ps_mode = 1
[ 926.382567] auto_ds = 1
[ 926.385010] host_mlme=enable
[ 926.387895] fw_name=nxp/sdiouartiw416_combo_v0.bin
[ 926.392709] SDIO: max_segs=128 max_seg_size=65535
[ 926.397420] rx_work=1 cpu_num=2
[ 926.400569] Enable moal_recv_amsdu_packet
[ 926.404600] Attach mlan adapter operations.card_type is 0x108.
[ 926.410826] wlan: Enable TX SG mode
[ 926.414357] wlan: Enable RX SG mode
[ 926.421681] Request firmware: nxp/sdiouartiw416_combo_v0.bin
[ 926.708639] Wlan: FW download over, firmwarelen=591808 downloaded 583072
[ 928.113594] WLAN FW is active
[ 928.116573] on_time is 927947046442
[ 928.140994] VDLL image: len=8736
[ 928.144352] FW country code WW does not match with US
[ 928.150617] fw_cap_info=0x187ccf03, dev_cap_mask=0xffffffff
[ 928.156607] max_p2p_conn = 8, max_sta_conn = 8
[ 928.176236] Register NXP 802.11 Adapter mlan0
[ 928.183724] Register NXP 802.11 Adapter uap0
[ 928.194033] Register NXP 802.11 Adapter wfd0
[ 928.199986] wlan: version = SDIW416---16.92.21.p137.2-MM6X16437.p30-GPL-(FP92)
[ 928.208947] wlan: Register to Bus Driver Done
[ 928.216412] wlan: Driver loaded successfully
</syntaxhighlight>

Check if the WiFi interface is present:
<syntaxhighlight lang="bash">
root@imx91-voipac:~# ip addr show dev mlan0
3: wlp1s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 78:c4:0e:a0:32:16 brd ff:ff:ff:ff:ff:ff
</syntaxhighlight>

'''''Input:''''' Scan the available WiFi networks 
'''''Output:''''' Networks are scanned and in-depth information are displayed 
<syntaxhighlight lang="bash">
root@imx91-voipac:~# ifconfig mlan0 up && iw dev mlan0 scan
BSS 94:27:90:7f:c3:d3(on wlp1s0)
TSF: 1213185029341 usec (14d, 00:59:45)
freq: 2442
beacon interval: 100 TUs
capability: ESS Privacy ShortPreamble ShortSlotTime (0x0431)
signal: -73.00 dBm
last seen: 4056 ms ago
SSID: HH40V_C3D3
Supported rates: 1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0
DS Parameter set: channel 7
Country: SK Environment: Indoor/Outdoor
Channels [1 - 13] @ 20 dBm
ERP: <no flags>
Extended supported rates: 24.0 36.0 48.0 54.0
HT capabilities:
Capabilities: 0x1ad
RX LDPC
HT20
SM Power Save disabled
RX HT20 SGI
TX STBC
RX STBC 1-stream
Max AMSDU length: 3839 bytes
No DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 8 usec (0x06)
HT TX/RX MCS rate indexes supported: 0-15
HT operation:
* primary channel: 7
* secondary channel offset: no secondary
* STA channel width: 20 MHz
* RIFS: 1
* HT protection: no
* non-GF present: 1
* OBSS non-GF present: 0
* dual beacon: 0
* dual CTS protection: 0
* STBC beacon: 0
* L-SIG TXOP Prot: 0
* PCO active: 0
* PCO phase: 0
Overlapping BSS scan params:
* passive dwell: 20 TUs
* active dwell: 10 TUs
* channel width trigger scan interval: 300 s
* scan passive total per channel: 200 TUs
* scan active total per channel: 20 TUs
* BSS width channel transition delay factor: 5
* OBSS Scan Activity Threshold: 0.25 %
Extended capabilities:
* HT Information Exchange Supported
* Extended Channel Switching
* SSID List
* Operating Mode Notification
WMM: * Parameter version 1
* BE: CW 15-1023, AIFSN 3
* BK: CW 15-1023, AIFSN 7
* VI: CW 7-15, AIFSN 2, TXOP 3008 usec
* VO: CW 3-7, AIFSN 2, TXOP 1504 usec
RSN: * Version: 1
* Group cipher: CCMP
* Pairwise ciphers: CCMP
* Authentication suites: PSK
* Capabilities: 1-PTKSA-RC 1-GTKSA-RC (0x0000)
WPS: * Version: 1.0
* Wi-Fi Protected Setup State: 2 (Configured)
* Response Type: 3 (AP)
* UUID: 87654321-9abc-def0-1234-942790c36dc7
* Manufacturer: TCL.org
* Model: WAP
* Model Number: 123
* Serial Number: 12345
* Primary Device Type: 6-0050f204-1
* Device name: TCL AP
* Config methods:
* Unknown TLV (0x1049, 6 bytes): 00 37 2a 00 01 20
BSS 34:e8:94:5c:06:80(on wlp1s0)
TSF: 787677017722 usec (9d, 02:47:57)
freq: 2462
beacon interval: 100 TUs
capability: ESS Privacy ShortSlotTime (0x0411)
signal: -73.00 dBm
last seen: 3952 ms ago
SSID: OrangeFlybox_0680
Supported rates: 1.0* 2.0* 5.5* 11.0* 9.0 18.0 36.0 54.0
DS Parameter set: channel 11
ERP: Barker_Preamble_Mode
Extended supported rates: 6.0 12.0 24.0 48.0
HT capabilities:
Capabilities: 0x106e
HT20/HT40
SM Power Save disabled
RX HT20 SGI
RX HT40 SGI
No RX STBC
Max AMSDU length: 3839 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 4 usec (0x05)
HT RX MCS rate indexes supported: 0-15, 32
HT TX MCS rate indexes are undefined
HT operation:
* primary channel: 11
* secondary channel offset: no secondary
* STA channel width: 20 MHz
* RIFS: 0
* HT protection: 20 MHz
* non-GF present: 1
* OBSS non-GF present: 0
* dual beacon: 0
* dual CTS protection: 0
* STBC beacon: 0
* L-SIG TXOP Prot: 0
* PCO active: 0
* PCO phase: 0
WPA: * Version: 1
* Group cipher: TKIP
* Pairwise ciphers: TKIP CCMP
* Authentication suites: PSK
RSN: * Version: 1
* Group cipher: TKIP
* Pairwise ciphers: TKIP CCMP
* Authentication suites: PSK
* Capabilities: 1-PTKSA-RC 1-GTKSA-RC (0x0000)
WMM: * Parameter version 1
* BE: CW 15-1023, AIFSN 3
* BK: CW 15-1023, AIFSN 7
* VI: CW 7-15, AIFSN 2, TXOP 3008 usec
* VO: CW 3-7, AIFSN 2, TXOP 1504 usec
BSS Load:
* station count: 3
* channel utilisation: 27/255
* available admission capacity: 31250 [*32us]
Overlapping BSS scan params:
* passive dwell: 20 TUs
* active dwell: 10 TUs
* channel width trigger scan interval: 300 s
* scan passive total per channel: 200 TUs
* scan active total per channel: 20 TUs
* BSS width channel transition delay factor: 5
* OBSS Scan Activity Threshold: 0.25 %
Extended capabilities:
* HT Information Exchange Supported
WPS: * Version: 1.0
* Wi-Fi Protected Setup State: 2 (Configured)
* AP setup locked: 0x01
* Response Type: 3 (AP)
* UUID: 38833092-3092-1883-9c77-34e8945c06c4
* Manufacturer: TP-LINK
* Model: Archer MR200
* Model Number: 1.0
* Serial Number: 1.0
* Primary Device Type: 6-0050f204-1
* Device name: AC750 Wireless Dual Band 4G LTE
* Config methods: Label, Display, Keypad
* RF Bands: 0x1
* Unknown TLV (0x1049, 6 bytes): 00 37 2a 00 01 20
BSS 34:e8:94:5b:f8:04(on wlp1s0)
TSF: 1210179077454 usec (14d, 00:09:39)
freq: 2462
beacon interval: 100 TUs
capability: ESS Privacy ShortSlotTime (0x0411)
signal: -50.00 dBm
last seen: 3432 ms ago
SSID: REDARROW
Supported rates: 1.0* 2.0* 5.5* 11.0* 9.0 18.0 36.0 54.0
DS Parameter set: channel 11
Extended supported rates: 6.0 12.0 24.0 48.0
TIM: DTIM Count 0 DTIM Period 1 Bitmap Control 0x0 Bitmap[0] 0x2
WPS: * Version: 1.0
* Wi-Fi Protected Setup State: 2 (Configured)
* AP setup locked: 0x01
* UUID: 38833092-3092-1883-9c77-34e8945bf8c4
* RF Bands: 0x1
* Unknown TLV (0x1049, 6 bytes): 00 37 2a 00 01 20
ERP: Barker_Preamble_Mode
HT capabilities:
Capabilities: 0x106e
HT20/HT40
SM Power Save disabled
RX HT20 SGI
RX HT40 SGI
No RX STBC
Max AMSDU length: 3839 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 4 usec (0x05)
HT RX MCS rate indexes supported: 0-15, 32
HT TX MCS rate indexes are undefined
HT operation:
* primary channel: 11
* secondary channel offset: no secondary
* STA channel width: 20 MHz
* RIFS: 0
* HT protection: no
* non-GF present: 0
* OBSS non-GF present: 0
* dual beacon: 0
* dual CTS protection: 0
* STBC beacon: 0
* L-SIG TXOP Prot: 0
* PCO active: 0
* PCO phase: 0
Overlapping BSS scan params:
* passive dwell: 20 TUs
* active dwell: 10 TUs
* channel width trigger scan interval: 300 s
* scan passive total per channel: 200 TUs
* scan active total per channel: 20 TUs
* BSS width channel transition delay factor: 5
* OBSS Scan Activity Threshold: 0.25 %
Extended capabilities:
* HT Information Exchange Supported
WPA: * Version: 1
* Group cipher: TKIP
* Pairwise ciphers: TKIP CCMP
* Authentication suites: PSK
RSN: * Version: 1
* Group cipher: TKIP
* Pairwise ciphers: TKIP CCMP
* Authentication suites: PSK
* Capabilities: 1-PTKSA-RC 1-GTKSA-RC (0x0000)
WMM: * Parameter version 1
* BE: CW 15-1023, AIFSN 3
* BK: CW 15-1023, AIFSN 7
* VI: CW 7-15, AIFSN 2, TXOP 3008 usec
* VO: CW 3-7, AIFSN 2, TXOP 1504 usec
BSS Load:
* station count: 0
* channel utilisation: 47/255
* available admission capacity: 31250 [*32us]
</syntaxhighlight>

To set up the network login data, edit file located in /etc/wpa_supplicant.conf and update '''''ssid''''' and passphrase '''''psk''''' fields.

<syntaxhighlight lang="bash">
root@imx91-voipac:~# cat /etc/wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
update_config=1

network={
ssid="SSID_FOR_WIFI_NETWORK"
scan_ssid=1
key_mgmt=WPA-PSK
psk="WIFI_NETWORK_PASSWORD"
}

</syntaxhighlight>

To connect to the desired WiFi network, start wpa_supplicant:
<syntaxhighlight lang="bash">
root@imx91-voipac:~# wpa_supplicant -D nl80211 -i mlan0 -c /etc/wpa_supplicant.conf &
root@imx91-voipac:~# rfkill: Cannot open RFKILL control device
[ 261.722718] wlan: mlan0 START SCAN
[ 266.018892] wlan: SCAN COMPLETED: scanned AP count=1
mlan0: SME: Trying to authentica[ 266.027303] wlan: HostMlme mlan0 send auth to bssid 40:XX:XX:XX:70:62
te with 40:a5:ef:c0:70:62 (SSID='WifiPoschodie' f[ 266.037546] mlan0:
req=2437 MHz)
[ 266.037558] wlan: HostMlme Auth received from 40:XX:XX:XX:70:62
mlan0: Trying to associate with 40:a5:ef:c0:70:62 (SSID='WifiPoschodie' freq=2437 MHz)
[ 266.057956] wlan: HostMlme mlan0 Connected to bssid 40:XX:XX:XX:70:62 successfully
mlan0: Associated[ 266.067323] mlan0:
with 40:a5:ef:c0[ 266.067340] wlan: Send EAPOL pkt to 40:XX:XX:XX:70:62
</syntaxhighlight>

To obtain an IP address and other network settings, run dhcp client:
<syntaxhighlight lang="bash">
udhcpc -i mlan0
</syntaxhighlight>

At this point the bandwidth measurement can be tested, showing that WiFi connection was established and is performed very reliably.
Used program: [https://iperf.fr iPerf3.] 

'''''Configuration:''''' iMX91 Industrial Module Pro in Industrial temperature range (u-blox MAYA-W160-00B assembled):
<syntaxhighlight lang="bash">
root@imx91-voipac:~# iperf3 -c 192.168.240.200 -t 30 -i1
Connecting to host 192.168.240.200, port 5201
[ 5] local 192.168.240.111 port 39988 connected to 192.168.240.200 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 5.12 MBytes 43.0 Mbits/sec 0 223 KBytes
[ 5] 1.00-2.00 sec 5.38 MBytes 45.1 Mbits/sec 0 460 KBytes
[ 5] 2.00-3.00 sec 7.12 MBytes 59.8 Mbits/sec 0 747 KBytes
[ 5] 3.00-4.00 sec 4.25 MBytes 35.7 Mbits/sec 0 1003 KBytes
[ 5] 4.00-5.00 sec 5.38 MBytes 45.1 Mbits/sec 0 1.25 MBytes
[ 5] 5.00-6.00 sec 5.50 MBytes 46.1 Mbits/sec 0 1.52 MBytes
[ 5] 6.00-7.00 sec 5.50 MBytes 46.1 Mbits/sec 0 1.78 MBytes
[ 5] 7.00-8.00 sec 5.62 MBytes 47.2 Mbits/sec 0 2.06 MBytes
[ 5] 8.00-9.00 sec 5.50 MBytes 46.1 Mbits/sec 0 2.31 MBytes
[ 5] 9.00-10.00 sec 5.50 MBytes 46.1 Mbits/sec 0 2.64 MBytes
[ 5] 10.00-11.00 sec 6.75 MBytes 56.6 Mbits/sec 0 2.93 MBytes
[ 5] 11.00-12.00 sec 3.00 MBytes 25.2 Mbits/sec 0 3.10 MBytes
[ 5] 12.00-13.00 sec 6.75 MBytes 56.6 Mbits/sec 0 3.41 MBytes
[ 5] 13.00-14.00 sec 5.75 MBytes 48.2 Mbits/sec 0 3.61 MBytes
[ 5] 14.00-15.00 sec 4.25 MBytes 35.7 Mbits/sec 0 3.81 MBytes
[ 5] 15.00-16.00 sec 5.75 MBytes 48.2 Mbits/sec 0 3.81 MBytes
[ 5] 16.00-17.00 sec 4.38 MBytes 36.7 Mbits/sec 0 4.07 MBytes
[ 5] 17.00-18.00 sec 5.88 MBytes 49.3 Mbits/sec 0 4.07 MBytes
[ 5] 18.00-19.00 sec 2.75 MBytes 23.1 Mbits/sec 0 4.07 MBytes
[ 5] 19.00-20.00 sec 3.38 MBytes 28.3 Mbits/sec 3 2.86 MBytes
[ 5] 20.00-21.00 sec 2.88 MBytes 24.1 Mbits/sec 0 2.94 MBytes
[ 5] 21.00-22.00 sec 1.25 MBytes 10.5 Mbits/sec 0 3.10 MBytes
[ 5] 22.00-23.00 sec 5.50 MBytes 46.1 Mbits/sec 0 3.44 MBytes
[ 5] 23.00-24.00 sec 5.50 MBytes 46.1 Mbits/sec 0 3.63 MBytes
[ 5] 24.00-25.00 sec 4.50 MBytes 37.7 Mbits/sec 0 3.64 MBytes
[ 5] 25.00-26.00 sec 4.25 MBytes 35.7 Mbits/sec 0 3.64 MBytes
[ 5] 26.00-27.00 sec 5.62 MBytes 47.2 Mbits/sec 0 3.86 MBytes
[ 5] 27.00-28.00 sec 6.62 MBytes 55.6 Mbits/sec 0 3.86 MBytes
[ 5] 28.00-29.00 sec 5.50 MBytes 46.1 Mbits/sec 0 3.86 MBytes
[ 5] 29.00-30.00 sec 4.88 MBytes 40.8 Mbits/sec 0 3.86 MBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-30.00 sec 150 MBytes 41.9 Mbits/sec 3 sender
[ 5] 0.00-30.32 sec 150 MBytes 41.5 Mbits/sec receiver

iperf Done.
</syntaxhighlight>

== Bluetooth ==
'''''Note:''''' This Bluetooth section was tested with the iMX91 Industrial Module in Max and Pro configurations. For Basic and Lite configurations, bluetooth capabilities are not available. For more information see [[iMX91 Industrial Development Kit|the iMX91 Industrial Module comparison]]. 

'''''Input:''''' None 
'''''Output:''''' Remote device is recognized after scan 

'''''Note:''''' For iMX91 Industrial Module Max (u-blox MAYA-W260-00B assembled) please use instead of <syntaxhighlight lang="bash">hciattach /dev/ttyLP7 any 3000000 flow</syntaxhighlight> command <syntaxhighlight lang="bash">hciattach /dev/ttyLP7 any 115200 flow</syntaxhighlight> in below code
<syntaxhighlight lang="bash">
# attach necessary modules
root@imx91-voipac:~# modprobe moal mod_para=nxp/wifi_mod_para.conf
root@imx91-voipac:~# modprobe hci_uart
root@imx91-voipac:~# hciattach /dev/ttyLP7 any 3000000 flow
Device setup complete
root@imx91-voipac:~# [ 1207.472299] Bluetooth: MGMT ver 1.22
[ 1207.485171] NET: Registered PF_ALG protocol family

# put hci0 device up
root@imx91-voipac:~# hciconfig hci0 up

# scan for remote bluetooth devices (enable bluetooth on phone and make it discoverable)
root@imx91-voipac:~# hcitool scan
Scanning ...
Devices:
hci0 00:0D:18:01:5A:B3
</syntaxhighlight>

== Ethernet ==
'''''Note:''''' This section was tested with the iMX91 Industrial Module in Max and Pro configurations, that both include dual Gigabit Ethernet PHY. The Basic configuration include single Gigabit Ethernet PHY. For the Lite configuration, Ethernet capabilities are not available. For more information see [[iMX91 Industrial Development Kit|the iMX91 Industrial Module comparison]]. 

'''''Input:''''' None 
'''''Output:''''' Device driver is available (for Lite configuration only one ethernet is available) 
'''''Note:''''' MAC address should be identical with the address on the sticker placed on the board
<syntaxhighlight lang="bash">

root@imx91-voipac:~# ip addr show dev eth0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:0d:15:01:8c:ae brd ff:ff:ff:ff:ff:ff
inet 192.168.1.33/24 metric 10 brd 192.168.1.255 scope global dynamic eth0
valid_lft 86378sec preferred_lft 86378sec
inet6 fe80::20d:15ff:fe01:8cae/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
root@imx91-voipac:~# ip addr show dev eth1
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:0d:15:01:8c:af brd ff:ff:ff:ff:ff:ff
inet 192.168.1.34/24 metric 10 brd 192.168.1.255 scope global dynamic eth1
valid_lft 86391sec preferred_lft 86391sec
inet6 fe80::20d:15ff:fe01:8caf/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
root@imx91-voipac:~#
</syntaxhighlight>

'''''Input:''''' Plug Ethernet cable into top or bottom connector 
'''''Output:''''' IPv4 address is assigned
<syntaxhighlight lang="bash">
[ 1599.750399] fec 42890000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[ 1630.695671] imx-dwmac 428a0000.ethernet eth1: Link is Up - 1Gbps/Full - flow control off
</syntaxhighlight>

=== Performance ===
iPerf3 was used to test the Ethernet performance. 
'''''Note:''''' Max and Pro configurations of the iMX91 Industrial Module include dual Gigabit Ethernet PHY. 
'''''Input:''''' Start iPerf3 on computer using command <syntaxhighlight lang="bash">iperf3 -s </syntaxhighlight>
'''''Output:''''' Verify performance on board (argument after -c is IP address of your computer) 

<syntaxhighlight lang="bash">
root@imx91-voipac:~# iperf3 -c 192.168.240.120 -t 10 -i 1
Connecting to host 192.168.240.120, port 5201
[ 5] local 192.168.240.32 port 57734 connected to 192.168.240.120 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 114 MBytes 951 Mbits/sec 0 358 KBytes
[ 5] 1.00-2.00 sec 112 MBytes 943 Mbits/sec 0 358 KBytes
[ 5] 2.00-3.00 sec 112 MBytes 938 Mbits/sec 0 358 KBytes
[ 5] 3.00-4.00 sec 113 MBytes 947 Mbits/sec 0 393 KBytes
[ 5] 4.00-5.00 sec 112 MBytes 941 Mbits/sec 0 393 KBytes
[ 5] 5.00-6.00 sec 112 MBytes 944 Mbits/sec 0 393 KBytes
[ 5] 6.00-7.00 sec 112 MBytes 940 Mbits/sec 0 516 KBytes
[ 5] 7.00-8.00 sec 112 MBytes 943 Mbits/sec 0 516 KBytes
[ 5] 8.00-9.00 sec 112 MBytes 942 Mbits/sec 0 516 KBytes
[ 5] 9.00-10.00 sec 113 MBytes 946 Mbits/sec 0 516 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 1.10 GBytes 943 Mbits/sec 0 sender
[ 5] 0.00-10.05 sec 1.10 GBytes 937 Mbits/sec receiver

iperf Done.
root@imx91-voipac:~#

</syntaxhighlight>

== USB 2.0 ==
NOTE: Perform read/write performance test 
'''''Input:''''' Plug USB flash drive into USB connector 
'''''Output:''''' Plugged USB device is listed
<syntaxhighlight lang="bash">
root@imx91-voipac:~# lsusb
Bus 001 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 125f:d31a A-DATA Technology Co., Ltd.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
</syntaxhighlight>

'''''Input:''''' Generate a dummy file and copy it into USB flash drive 
'''''Output:''''' Generated file and copied file have the same checksum
<syntaxhighlight lang="bash">
root@imx91-voipac:~# mount /dev/sda1 /media/
root@imx91-voipac:~# rm -f file.txt /media/file.txt
root@imx91-voipac:~# dd if=/dev/urandom of=file.txt count=1024 bs=1024
1024+0 records in
1024+0 records out
root@imx91-voipac:~# cp file.txt /media/
root@imx91-voipac:~# md5sum file.txt /media/file.txt
200a9fd3e9850fcedf85ed50d4c4733d file.txt
200a9fd3e9850fcedf85ed50d4c4733d /media/file.txt
root@imx91-voipac:~# rm file.txt /media/file.txt
root@imx91-voipac:~# umount /media
</syntaxhighlight>

== USB-C ==
This connector is primarily used for flashing new binaries into the iMX91 Industrial Module. More information can be found on the dedicated [[iMX8M Industrial Flashing Procedure|module flashing page]]. 

== USB Micro-B serial console ==
'''''Input:''''' Connect USB console cable into the base board connector and open serial console with baud rate 115200 8n1 
'''''Output:''''' The board is controlled and responsive to serial terminal commands
<syntaxhighlight lang="bash">
root@imx91-voipac:~# uname -a
Linux imx91-voipac 6.6.36-lts-next-g2e3e2e65d92a #1 SMP PREEMPT Wed Sep 4 08:22:45 UTC 2024 aarch64 GNU/Linux
</syntaxhighlight>

== UART serial console ==
Serial console is utilized via USB Micro-B connector by default. Alternatively, the communication can be established using UART headers and TTL-232R-3V3 - FTDI cable. 
NOTE: Describe jumpers position 
[[File:iMX93 Industrial Development Kit-Serial console via UART1.png|800px]] 

'''''Note:''''' Usage of UART2 CONSOLE to communicate by default requires changes in Yocto binaries and new compilation of image files. 
[[File:iMX93 Industrial Development Kit-Serial console via UART2.png|800px]]

== SD Card ==
NOTE: Perform detection of SD Card
<syntaxhighlight lang="bash">
root@imx91-voipac:~# fdisk -l
Disk /dev/mmcblk0: 15 GB, 15758000128 bytes, 30777344 sectors
240448 cylinders, 4 heads, 32 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type
/dev/mmcblk0p1 * 128,0,1 1023,3,32 16384 186775 170392 83.1M c Win95 FAT32 (LBA)
/dev/mmcblk0p2 1023,3,32 1023,3,32 196608 939761 743154 362M 83 Linux
Disk /dev/mmcblk0boot0: 4 MB, 4194304 bytes, 8192 sectors
128 cylinders, 4 heads, 16 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Disk /dev/mmcblk0boot1: 4 MB, 4194304 bytes, 8192 sectors
128 cylinders, 4 heads, 16 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Disk /dev/mmcblk1: 15 GB, 15931539456 bytes, 31116288 sectors
243096 cylinders, 4 heads, 32 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type
/dev/mmcblk1p1 512,0,1 1023,3,32 65536 266255 200720 98.0M 83 Linux
</syntaxhighlight>

/dev/mmcblk1 is SD card (mmcblk0 is eMMC)

== JTAG ==
[[File:iMX93 Industrial Development Kit-JTAG communication setup.png|800px]] 
To verify that i.MX93 CPU JTAG is functional, following command identifies and connects to the CPU's debug point:
<syntaxhighlight lang="bash">
J-Link> jtagid
</syntaxhighlight>

[[File:J-Link MIMX9352 A55 1.png|800px]] 
[[File:J-Link MIMX9352 M33.png|800px]]

== Real Time Clock ==
RTC chip is detected by Linux kernel after start-up:
<syntaxhighlight lang="bash">
root@imx91-voipac:~# dmesg | grep rtc
[ 0.894414] imx-drm display-subsystem: bound imx-lcdifv3-crtc.0 (ops lcdifv3_crtc_ops)
[ 0.910506] imx-drm display-subsystem: [drm] Cannot find any crtc or sizes
[ 1.209418] bbnsm_rtc 44440000.bbnsm:rtc: registered as rtc0
[ 1.215749] bbnsm_rtc 44440000.bbnsm:rtc: setting system clock to 1970-01-01T00:00:00 UTC (0)
root@imx91-voipac:~#
</syntaxhighlight>

CPU correctly recognises RTC on the I2C1 bus, the chip is under usage by the kernel:
<syntaxhighlight lang="bash">
root@imx91-voipac:~# i2cdetect -r -y 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- UU -- -- -- UU -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- 3d -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- UU -- UU -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
</syntaxhighlight>

Set up the current date and time, show the actual values

Setup date and time
<syntaxhighlight lang="bash">
date -s "2025-8-13 14:52:26"
</syntaxhighlight>

Show actual values
<syntaxhighlight lang="bash">
root@imx91-voipac:~# timedatectl
[ 134.509782] kauditd_printk_skb: 8 callbacks suppressed
[ 134.509793] audit: type=1334 audit(1732625725.140:18): prog-id=19 op=LOAD
[ 134.523935] audit: type=1334 audit(1732625725.148:19): prog-id=20 op=LOAD
[ 134.531609] audit: type=1334 audit(1732625725.152:20): prog-id=21 op=LOAD
Local time: Tue 2024-11-26 12:55:25 UTC
Universal time: Tue 2024-11-26 12:55:25 UTC
RTC time: Tue 2024-11-26 12:55:25
Time zone: UTC (UTC, +0000)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no
</syntaxhighlight>

== I2C EEPROM Memory - on module ==
'''''Input:''''' Power on board 
'''''Output:''''' Store some data to eeprom and after reboot read it back and should be same 

<syntaxhighlight lang="bash">
# store random 8bytes to eeprom
root@imx91-voipac-evk:~# dd if=/dev/urandom of=/sys/bus/i2c/devices/0-0050/eeprom bs=8 count=1
+1 records in
0+1 records out
8 bytes copied, 0.0225523 s, 0.4 kB/s
</syntaxhighlight>

After board reboot:
<syntaxhighlight lang="bash">
# store random 8bytes to eeprom
root@imx91-voipac-evk:~# hexdump -n8 /sys/bus/i2c/devices/0-0050/eeprom
0000000 c4dd 4eda d624 535e
0000008
</syntaxhighlight>

== Reset button ==
'''''Input:''''' Press the RESET button 
'''''Output:''''' The board will execute bootloader immediately with "Reset cause: POR" 
'''''Note:''''' iMX91 Industrial Development Kit should never freeze or hang after the reset button was pressed. Testing the operation 10 times gives a reliable result
<syntaxhighlight lang="bash">
U-Boot 2023.04+gf8a2983ec8+p0 (Mar 04 2024 - 07:25:04 +0000)

CPU: i.MX93(52) rev1.1 1700 MHz (running at 1692 MHz)
CPU: Industrial temperature grade (-40C to 105C) at 45C
Reset cause: POR (0x1)
Model: NXP i.MX93 Voipac EVK board
DRAM: 2 GiB
Core: 215 devices, 32 uclasses, devicetree: separate
MMC: FSL_SDHC: 0, FSL_SDHC: 1
Loading Environment from MMC... OK
[*]-Video Link 0fail to find output device

....
</syntaxhighlight>

== On/Off button ==
'''''Input:''''' Press and hold On/Off button for more then 5 seconds 
'''''Output:''''' The board will be powered off

Press shortly the On/Off button again, the board will be powered on.

== Sleep Mode ==
'''''Input:''''' Type command:
<syntaxhighlight lang="bash">
echo mem > /sys/power/state
</syntaxhighlight>

'''''Output:''''' The board will go into a frozen state and the serial console will not respond to inputs.

Shortly press the Up user button, to wake the board up again.

[[File:imx93_sleep_mode.png|740px]] 

== User buttons ==
'''''Input:''''' Press Enter/Left/Right/Up/Down buttons 
'''''Output:''''' Button events 1 and 0 are generated
<syntaxhighlight lang="bash">
root@imx91-voipac-evk:~# evtest /dev/input/by-path/platform-gpio-buttons-event
Input driver version is 1.0.1
Input device ID: bus 0x19 vendor 0x1 product 0x1 version 0x100
Input device name: "gpio-buttons"
Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
Event code 28 (KEY_ENTER)
Event code 103 (KEY_UP)
Event code 105 (KEY_LEFT)
Event code 106 (KEY_RIGHT)
Event code 108 (KEY_DOWN)
Properties:
Testing ... (interrupt to exit)
Event: time 1717485486.586413, type 1 (EV_KEY), code 103 (KEY_UP), value 1
Event: time 1717485486.586413, -------------- SYN_REPORT ------------
Event: time 1717485486.682265, type 1 (EV_KEY), code 103 (KEY_UP), value 0
Event: time 1717485486.682265, -------------- SYN_REPORT ------------
Event: time 1717485487.255120, type 1 (EV_KEY), code 108 (KEY_DOWN), value 1
Event: time 1717485487.255120, -------------- SYN_REPORT ------------
Event: time 1717485487.367126, type 1 (EV_KEY), code 108 (KEY_DOWN), value 0
Event: time 1717485487.367126, -------------- SYN_REPORT ------------
Event: time 1717485488.539564, type 1 (EV_KEY), code 106 (KEY_RIGHT), value 1
Event: time 1717485488.539564, -------------- SYN_REPORT ------------
Event: time 1717485488.677501, type 1 (EV_KEY), code 106 (KEY_RIGHT), value 0
Event: time 1717485488.677501, -------------- SYN_REPORT ------------
Event: time 1717485488.897627, type 1 (EV_KEY), code 105 (KEY_LEFT), value 1
Event: time 1717485488.897627, -------------- SYN_REPORT ------------
Event: time 1717485489.013136, type 1 (EV_KEY), code 105 (KEY_LEFT), value 0
Event: time 1717485489.013136, -------------- SYN_REPORT ------------
Event: time 1717485489.264589, type 1 (EV_KEY), code 28 (KEY_ENTER), value 1
Event: time 1717485489.264589, -------------- SYN_REPORT ------------
Event: time 1717485489.372584, type 1 (EV_KEY), code 28 (KEY_ENTER), value 0
Event: time 1717485489.372584, -------------- SYN_REPORT ------------
</syntaxhighlight>

== User LED ==
'''''Input:''''' None 
'''''Output:''''' Script switches User LED on baseboard ON and OFF in one second intervals
<syntaxhighlight lang="bash">
#!/bin/sh

LED=/sys/class/leds/user_sbc

while true; do
echo 0 > ${LED}/brightness
sleep 1
echo 1 > ${LED}/brightness
sleep 1
done
</syntaxhighlight>

'''''Input:''''' None 
'''''Output:''''' User LED on baseboard is set to heartbeat blinking sequence
<syntaxhighlight lang="bash">
root@imx91-voipac-evk:~# echo heartbeat > /sys/class/leds/user_sbc/trigger
</syntaxhighlight>

'''''Input:''''' None 
'''''Output:''''' User LED on SOM is set to heartbeat blinking sequence
<syntaxhighlight lang="bash">
root@imx91-voipac-evk:~# echo heartbeat > /sys/class/leds/user_som/trigger
</syntaxhighlight>

iMX91 Industrial Flashing Procedure

2025-10-22T19:19:36Z

Voipac-sw:

[[Category:iMX91 Industrial Development Kit]]
[[Category:iMX91 Industrial Software]]

<div style="float:right">__TOC__</div>
This page describes how to flash [https://downloads.voipac.com/index.php?p=iMX91_Industrial_Development_Kit/module/software/filesystem binaries] into iMX91 Industrial Module's eMMC Flash memory or into SD card that is located on the iMX Development Baseboard. 

'''''Note: All of the steps listed below are NOT REQUIRED for standard configuration modules and development kits.'''''

== Installing Universal Upload Utility (UUU) ==
=== Linux ===
<syntaxhighlight lang="bash">
git clone https://github.com/NXPmicro/mfgtools.git
cd mfgtools
mkdir .build && cd .build && cmake .. && make -j`nproc`
</syntaxhighlight>

The binary called '''''uuu''''', which is used for flashing, is located in .build/uuu directory.

=== Windows ===
* Go to: https://github.com/NXPmicro/mfgtools/releases
* Select the latest stable release. Example: '''''Releases/uuu_1.5.201''''': https://github.com/nxp-imx/mfgtools/releases/tag/uuu_1.5.201
* Download: [https://github.com/nxp-imx/mfgtools/releases/download/uuu_1.5.201/uuu.exe uuu.exe]
* Save the file into: C:\uuu

== Preparing the binaries ==
* Download the default WIC filesystem image e.g. for pro configuration: [https://downloads.voipac.com/files/iMX91_Industrial_Development_Kit/module/software/filesystem/voipac-image-imx93-pro.rootfs.wic voipac-image-imx93-pro.rootfs.wic]

== Flashing procedure ==
* Set serial downloader mode by sliding DIP switch S1 BOOT positions to: 1-OFF, 2-ON
[[File:iMX8M_Industrial_Development_Kit-Serial_donwloader_mode.png|400px]] 

* Plug USB Micro-B cable to baseboard CONSOLE connector and PC '''''Note:''''' Make sure that UART1 and UART2 jumpers are in CP2105 positions (USB/UART bridge). 
[[image:iMX Development Baseboard-Serial console jumpers-iMX93 COM.png|594px]] 

* Plug USB-C cable to baseboard USB-C connector and PC '''''Note:''''' Powering of the development kit is not required during the flashing procedure. '''''Note:''''' After connecting 2 development board cables, 2 serial ports named ''Silicon Labs CP210x USB to UART Bridge'' should appear in the controlling PC. 
[[image:iMX8M Industrial Development Kit-Serial-consoles-recognized.png|594px]] 
* Default Serial Port Settings
[[File:Serial Port Setup.png]] 

* Download and copy imx-boot and *.wic files into ''uuu\'' directory
* Choose one of the following commands to start the flashing process:
=== eMMC Flash Memory (default) ===

==== Linux ====
<syntaxhighlight lang="bash">
sudo ./uuu -b emmc_all voipac-image-imx93-pro.rootfs.wic
</syntaxhighlight>

==== Windows ====
<syntaxhighlight lang="bash">
uuu.exe -b emmc_all voipac-image-imx93-pro.rootfs.wic
</syntaxhighlight>

=== SD Card ===

==== Linux ====
<syntaxhighlight lang="bash">
sudo ./uuu -b sd_all voipac-image-imx93-pro.rootfs.wic
</syntaxhighlight>

==== Windows ====
<syntaxhighlight lang="bash">
uuu.exe -b sd_all voipac-image-imx93-pro.rootfs.wic
</syntaxhighlight>

=== Flashing logs ===
==== UUU ====
<syntaxhighlight lang="bash">
Microsoft Windows [Version 10.0.19045.2486]
(c) Microsoft Corporation. All rights reserved.

C:\Users\voipac>cd c:\uuu

c:\uuu>uuu.exe -b emmc_all voipac-image-imx93-pro.rootfs.wic
uuu (Universal Update Utility) for nxp imx chips -- libuuu_1.4.243-0-ged48c51

Success 1 Failure 0

2:43 8/ 8 [Done ] FB: done

c:\uuu>
</syntaxhighlight>

[[image:iMX93_Industrial_Development_Kit-Flashing_binaries.png|750px]]

==== Serial console ====
<syntaxhighlight lang="bash">
.....................................................
downloading of 16776244 bytes finished
writing to partition 'all'
sparse flash target is mmc:0
writing to partition 'all' for sparse, buffer size 16776244
Flashing sparse image at offset 0
Flashing Sparse Image
........ wrote 16776192 bytes to 'all'
Starting download of 16776244 bytes
..........................................................................
.....................................................
downloading of 16776244 bytes finished
writing to partition 'all'
sparse flash target is mmc:0
writing to partition 'all' for sparse, buffer size 16776244
Flashing sparse image at offset 0
Flashing Sparse Image
........ wrote 16776192 bytes to 'all'
Starting download of 11424820 bytes
..........................................................................
.............
downloading of 11424820 bytes finished
writing to partition 'all'
sparse flash target is mmc:0
writing to partition 'all' for sparse, buffer size 11424820
Flashing sparse image at offset 0
Flashing Sparse Image
........ wrote 11424768 bytes to 'all'
Starting download of 2126848 bytes
................
downloading of 2126848 bytes finished
writing to partition 'bootloader'
Initializing 'bootloader'
switch to partitions #1, OK
mmc0(part 1) is current device
Writing 'bootloader'

MMC write: dev # 0, block # 0, count 4154 ... 4154 blocks written: OK
Writing 'bootloader' DONE!
Detect USB boot. Will enter fastboot mode!
Detect USB boot. Will enter fastboot mode!

</syntaxhighlight>

== Running the newly flashed binaries ==
After completing the above steps, eMMC Flash memory or SD Card is flashed and the following steps are to be performed to boot the new image:

* Unplug USB-C cable from PC
* Set Boot mode by sliding DIP switch S1 BOOT positions to: 1-ON, 2-OFF
[[File:iMX8M_Industrial_Development_Kit-Boot_mode.png|400px]] 

* In case of SD card boot set DIP switch S1 BOOT positions to 1-ON, 2-ON
[[File:SD Card booting.png|400px]] 

* Make sure that S2 BOOT and S3 BOOT DIP switches are in correct positions in order to boot from the selected storage media (eMMC Flash memory or SD Card):
==== eMMC Flash Memory boot (default) ====
[[File:boot eMMC iMX93.png|400px]] 

==== SD Card boot ====
[[File:boot SD Card iMX93.png|400px]] 
* Connect USB Micro-B debug cable, switch on the power and the development kit starts booting with the new binaries 

== Setting DTB file ==
* To set a correct DTB file, stop autoboot.

* Use these commands to set a DTB file for the image loaded in eMMC:
<syntaxhighlight lang="bash">
u-boot=>fatls mmc 0:1
u-boot=>setenv fdtfile imx91-voipac-evk.dtb
u-boot=>saveenv
</syntaxhighlight>

* Use these commands to set a DTB file for the image loaded in SD Card (example for BOE Display):
<syntaxhighlight lang="bash">
u-boot=>fatls mmc 1:1
u-boot=>setenv fdtfile imx93-voipac-evk-boe-wxga-lvds-panel.dtb
u-boot=>saveenv
</syntaxhighlight>

[[File:imx93_dtb_setting.png|740px]] 

* To boot the image, reset the board or type the boot command:

<syntaxhighlight lang="bash">
u-boot=>boot
</syntaxhighlight>

iMX91 Industrial Controlling the Development Kit

2025-10-22T19:18:44Z

Voipac-sw:

<div style="float:right">__TOC__</div>
This page guides though the first steps of controlling and operating the development kit. To prepare the working setup connect and plug in cables first.

=Controlling the Development Kit over Serial Line=
==Recommended HW:==

* PC with USB port
* Voipac iMX91 Industrial Development Kit
* Micro USB Cable: iMX Baseboard USB Micro-B Console (Default)
* TTL-232R-3V3-FTDI: iMX Baseboard UART1 Serial Console (Optional)

==Recommended SW:==

Serial line terminal (PUTTY, Minicom, Ckermit, Hyperterminal, TeraTerm, ...)

===Default serial port settings:===

* Speed (baud): 115200
* Data bits: 8
* Stop bits: 1
* Parity: None
* Flow control: None

===Controlling the development kit using TeraTerm and PuTTY:===

[[File:iMX93 TeraTerm log.png]] 
[[File:iMX93 PuTTY Serial log.png]] 

'''''NOTE:''''' If you use the UART1 Console cable, it is necessary to switch the UART1 and UART 2 jumpers to the UART-CPU position as shown in the picture below.

[[File:iMX93 UART Serial Console.png|800px]] 

=Controlling the Development Kit over Ethernet=
===Recommended HW:===

* PC with Ethernet
* Voipac iMX91 Industrial Development Kit
* Ethernet Cable

===Recommended SW:===

* SFTP client (Filezilla, PUTTY, WinSCP, …)
* Telnet client (Telnet, PUTTY, …)
* SSH client (SSH,PUTTY, …)
* FTP client (FTP, Filezilla, BareFTP, …)

===Important notes:===

iMX91 Industrial Development Kit is shipped with empty password. The default login is: "root"

The default IP address is dynamic and setup by your DHCP server upon boot.

SSH, SFTP services require root password to be set up (“passwd” command)

FTP, SFTP are recommended only for data transfers (binary mode is recommended)

===Controlling the development kit using WinSCP:===

[[File:iMX93 WinSCP.png|800px]] 
[[File:iMX93 WinSCP commander.png|800px]]

iMX91 Industrial Connecting the Components and Cables

2025-10-22T19:17:52Z

Voipac-sw:

[[Category:iMX93 Industrial Development Kit]]


This page is intended to show the necessary connections and steps to successfully boot and operate the development kit.

==Connecting the board==
Prepare iMX Development Baseboard and plug in Micro USB Cable, Ethernet cable and other devices or interfaces you need. Plug the power supply connector in.
 
[[File:iMX93 Components Cables.png|800px]]

==Connecting the Ethernet cable==
Connect the Ethernet cable to bottom connector (preset as default) of the Ethernet port.
 
[[File:iMX93 Components Cables Ethernet.png|800px]] 

==Connecting the microSD Card (OPTIONAL)==
Insert the micro SD card into the micro SD Slot in case that booting is set from the micro SD card.

'''''NOTE:''''' The Development Kit, which have default setting to boot from SD Card, already contains an inserted SD Card.
 
[[File:Components Cables microSD.png|800px]] 

'''''NOTE:''''' Before Turn On, make sure that S1, S2 and S3 BOOT DIP switches are in correct positions in order to boot from the selected storage media (eMMC Flash memory or SD Card). For more details visit: [[iMX91_Industrial_Flashing_Procedure#Running_the_newly_flashed_binaries]]

iMX91 Industrial Power Consumption

2025-10-22T10:41:16Z

Voipac-sw: Created page with "Category:iMX93 Industrial Category:iMX93 Industrial Development Kit  <div style="float:right">__TOC__</div> This page contains power consumption measurements..."

[[Category:iMX93 Industrial]]
[[Category:iMX93 Industrial Development Kit]]

<div style="float:right">__TOC__</div>

This page contains power consumption measurements for the iMX93 Industrial Development Kits in all 4 standard webshop configurations. All of the sets used during the test procedure were running the default Linux distribution and booted up from the eMMC NAND Flash Memory.

'''''Note:''''' While measured, the development kits were placed under a very heavy load - using stress test application putting CPU, memories and Ethernet/s under challenging conditions.

== Test setup and measuring equipment ==
* power supply: BK Precision 1688B
* digital multimeter: Fluke 115 True RMS
* measured at: 20°C ambient temperature

[[image:iMX93 Industrial Development Kit-Power consumption measurement setup.jpg|800px]]

== Power consumption results ==
=== iMX93 Industrial Development Kit Lite ===
{| class="wikitable" style="text-align: center;
!Test condition !! Input voltage Vin [V] !! Measured current I [A] !! Power usage P [W]
|-
|Uboot only || 5.194 || 0.128 || 0.666
|-
|Booting-up process (maximum) || 5.194 || 0.138 || 0.717
|-
|Linux at idle || 5.195 || 0.101 || 0.525
|-
|Sleep mode || 5.199 || 0.026 || 0.138
|-
|Linux + Stresstest || 5.193 || 0.152 || 0.793
|}

=== iMX93 Industrial Development Kit Basic ===
{| class="wikitable" style="text-align: center;
!Test condition !! Input voltage Vin [V] !! Measured current I [A] !! Power usage P [W]
|-
|Uboot only || 5.188 || 0.290 || 1.506
|-
|Booting-up process (maximum) || 5.190 || 0.341 || 1.770
|-
|Linux at idle || 5.192 || 0.227 || 1.179
|-
|Sleep mode || 5.198 || 0.049 || 0.257
|-
|Linux + Stresstest || 5.193 || 0.367 || 1.905
|}

=== iMX93 Industrial Development Kit Pro ===
{| class="wikitable" style="text-align: center;
!Test condition !! Input voltage Vin [V] !! Measured current I [A] !! Power usage P [W]
|-
|Uboot only || 5.183 || 0.401 || 2.081
|-
|Booting-up process (maximum) || 5.182 || 0.478 || 2.476
|-
|Linux at idle || 5.186 || 0.323 || 1.675
|-
|Sleep mode || 5.195 || 0.079 || 0.414
|-
|Linux + Stresstest || 5.181 || 0.482 || 2.498
|}

=== iMX93 Industrial Development Kit Max ===
{| class="wikitable" style="text-align: center;
!Test condition !! Input voltage Vin [V] !! Measured current I [A] !! Power usage P [W]
|-
|Uboot only || 5.183 || 0.416 || 2.159
|-
|Booting-up process (maximum) || 5.186 || 0.460 || 2.386
|-
|Linux at idle || 5.186 || 0.338 || 1.756
|-
|Sleep mode || 5.196 || 0.085 || 0.444
|-
|Linux + Stresstest || 5.183 || 0.574 || 2.977
|}