DESK-MX9-L/pdf
History[edit | edit source]
| DESK-MX9-L History | |||
|---|---|---|---|
| Version | Issue Date | Notes | Refers to |
| 5.0.0 | Feb 2024 | DESK-MX9-L-5.0.0 release |  AURA
|
General Information[edit | edit source]
Release Notes[edit | edit source]
DAVE Embedded Systems adds to the latest Linux BSP from NXP the customization required to support the SOC platform. For this reason, most of the documentation provided by NXP remains valid for the DESK development kit.
However, some customization is required, in particular at bootloader and linux kernel levels.
The following table reports the DESK releases information.
| DESK version | |
|---|---|
| Release number | 5.0.0 |
| Release type | Major |
| Status | Released |
| Release date | Feb 2024 |
| Release notes | Ver 5.0.0 |
| Product support | AURA |
| MVM (distro version) | Ubuntu 20.04 |
| U-Boot version | 2023.04-desk-mx9-l-5.0.0 |
| Linux version | 6.1.55-desk-mx9-l-5.0.0 |
| Drivers |
NAND SD |
| Manufacturer BSP version | rel_imx_6.1.55_2.2.0 |
| Graphic libraries | Qt 6.5.0 |
| Build System | Yocto Mickledore (4.2) |
DESK-MX9-L 5.0.0[edit | edit source]
 New MVM must be installed for using |
Release notes:
- First release based on NXP BSP 6.1.55
Known Limitations[edit | edit source]
The following table reports the known limitations of this DESK release:
| Issue | Description |
|---|---|
| U-Boot | SPI NAND is not supported |
| Kernel | Camera first access after power-on fails. The following access are working correctly |
| kernel | Power management is not supported |
| UART | Only RS232 mode is supported on Evaluation Kit multiprotocol port |
Downloadable binary images[edit | edit source]
All binary images for DESK-MX9-L are hosted on DAVE Embedded System mirror server. There you can find a sub directory for each version of this development kit.
The binary file must be stored into SD card using BalenaEtcher tool, see How to create a bootable microSD card page.
A summary of images with a brief description can be found in the table below:
| Image | DESK version 5.0.0 |
|---|---|
| Platform | SBCX AURA |
| Carrier Board ConfigID | 2001 |
| LCD panel | Ampire 800 x 480 7" LVDS (AM-800480BTMQW-TG0H-C) |
| Touchscreen | capacitive |
| Linux kernel | Image-desk-mx93.bin |
| Device tree | imx93-aura-cb2001-desk-mx93.dtb |
| root file system | dave-image-devel-desk-mx93.tar.bz2 |
| wic file | dave-image-devel-desk-mx93.wic.bz2 |
Release types[edit | edit source]
DESK release type can be:
- Major, when substantial changes are applied to the BSP (eg: major kernel version upgrades) or to the development kit (eg: new features, build system updates, ..). This usually means that a new DVDK is created for the DESK release
- Maintenance, when minor updates and bug fixes are introduced. This usually means that the DVDK remains the same provided with the previous major version, and only an update of the source tree repositories (and the tftp binaries) is required
As an example, DESK 1.1.0 is a maintenance release, so it provides the DVDK released with the 1.0.0 major release; customers can easily upgrade to the 1.1.0 release by updating the software components as described in Synchronizing git repositories.
Supported platforms[edit | edit source]
The following table reports the supported platforms in this DESK release:
| Platform | Description |
|---|---|
| SBC AXEL | Single Board Computer using AURA SOM as Evaluation Kit |
Virtual Machine[edit | edit source]
DAVE' standard DVDK Virtual Machine contains all the required software and documentation to start developing Linux applications on the AURA platforms. In particular, DESK-MX9-L provides a virtual machine, called DVDK, with the following features:
- VirtualBox virtual machine (.OVA archive)
- based on Lubuntu 20.04 LTS (64-bit version)
- pre-installed VirtualBox Guest Additions
- LXDE desktop environment
- boot disk with the distro and pre-configured basic Linux services:
- TFTP: with base directory
/tftpboot/desk-mx9-l/ - NFS: configured through the
/etc/exportsfile
- TFTP: with base directory
- Disk containing source code and tools:
- bootloader (U-Boot) source tree cloned from DAVE Embedded Systems public git repository
- Linux kernel source tree cloned from DAVE Embedded Systems public git repository
- external pre-built toolchain
- Yocto BSP for AURA SOM
- pre-installed Yocto-based root file systems with setup scripts, makefiles, example applications, ...
- administrator account (dvdk) with autologin. Please note that the user account credentials are provided with the development kit (you can find them in the README file contained in the sw/dvdk folder of the kit distribution)
- user: dvdk
- password: dvdk
Please note that U-Boot and kernel source trees are derived from the official trees released by NXP/Freescale; these trees have been customized to add support for the AURA SOMs.
Host setup[edit | edit source]
As stated previously, AURA SOM host tools are based on a Managed Virtual Machine. As indicated here, microSD card delivered along with AURA Evaluation Kit includes basic version of MVM that is the default option.
Please follows the README file on the SD card to extract the *.ova archive and to install the MVM.
It is also worth remembering that access to git repositories is required to download target source code. To enable it, please refer to this page.
MVM can be downloaded here. For accessing DESK Reserved area please contact our helpdesk support channel
To install it, please refer to this page.
Installing the meta-toolchain SDK[edit | edit source]
meta toolchain is preinstalled on DESK-MX9-L-5.0.0 and it is used for building U-Boot and kernel sources. It can be found in the following path.
dvdk@vagrant:~/desk-mx-l$ls -la /opt/yocto/sdk/desk-mx9-l/desk-mx9-l-5.0.0/ total 36 drwxr-xr-x 3 root root 4096 Jan 26 11:00 . drwxr-xr-x 3 root root 4096 Jan 26 11:04 .. -rw-r--r-- 1 root root 4309 Jan 26 11:00 environment-setup-armv8a-poky-linux -rw-r--r-- 1 root root 12016 Jan 26 11:00 site-config-armv8a-poky-linux drwxr-xr-x 4 root root 4096 Jan 26 11:00 sysroots -rw-r--r-- 1 root root 141 Jan 26 11:00 version-armv8a-poky-linux dvdk@vagrant:~/desk-mx-l$
The toolchain can be re-installed, just download it from here and install it. Example commands to execute the reinstallation of toolchain.
dvdk@vagrant:~$ cd desk-mx-l/ dvdk@vagrant:~/desk-mx-l$ wget https://mirror.dave.eu/desk-mx-l/desk-mx9-l-5.0.0/fsl-imx-wayland-glibc-x86_64-meta-toolchain-armv8a-desk-mx93-toolchain-6.1-mickledore.sh -O meta_toolchain.sh --2024-01-30 15:25:34-- https://mirror.dave.eu/desk-mx-l/desk-mx9-l-5.0.0/fsl-imx-wayland-glibc-x86_64-meta-toolchain-armv8a-desk-mx93-toolchain-6.1-mickledore.sh Resolving mirror.dave.eu (mirror.dave.eu)... 84.46.251.143 Connecting to mirror.dave.eu (mirror.dave.eu)|84.46.251.143|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 139078250 (133M) [text/x-sh] Saving to: ‘meta_toolchain.sh’ meta_toolchain.sh 100%[==============================================================================================================>] 132.63M 11.3MB/s in 13s 2024-01-30 15:25:47 (10.2 MB/s) - ‘meta_toolchain.sh’ saved [139078250/139078250] dvdk@vagrant:~/desk-mx-l$ chmod +x meta_toolchain.sh dvdk@vagrant:~/desk-mx-l$ ./meta_toolchain.sh -d /opt/yocto/sdk/desk-mx9-l/desk-mx9-l-5.0.0 -y NXP i.MX Release Distro SDK installer version 6.1-mickledore ============================================================ You are about to install the SDK to "/opt/yocto/sdk/desk-mx9-l/desk-mx9-l-5.0.0". Proceed [Y/n]? Y Extracting SDK..............................................done Setting it up...done SDK has been successfully set up and is ready to be used. Each time you wish to use the SDK in a new shell session, you need to source the environment setup script e.g. $ . /opt/yocto/sdk/desk-mx9-l/desk-mx9-l-5.0.0/environment-setup-armv8a-poky-linux dvdk@vagrant:~/desk-mx-l$
Installing the application SDK[edit | edit source]
application SDK is preinstalled on DESK-MX9-L-5.0.0 and it is used for building userspace application. The SDK contains the headers and libraries for building the Qt6 application. It can be found in the following path.
dvdk@vagrant:~/desk-mx-l$ ls -la ~/desk-mx-l/sdk/desk-mx9-l-5.0.0/ total 40 drwxr-xr-x 3 root root 4096 Jan 26 10:59 . drwxr-xr-x 3 dvdk dvdk 4096 Jan 26 11:04 .. -rw-r--r-- 1 root root 1989 Jan 26 10:59 buildinfo -rw-r--r-- 1 root root 4298 Jan 26 10:59 environment-setup-armv8a-poky-linux -rw-r--r-- 1 root root 12016 Jan 26 10:59 site-config-armv8a-poky-linux drwxr-xr-x 4 root root 4096 Jan 26 10:54 sysroots -rw-r--r-- 1 root root 141 Jan 26 10:59 version-armv8a-poky-linux dvdk@vagrant:~$
The SDK can be re-installed, just download it from here and install it. Example commands to execute the reinstallation of SDK.
dvdk@vagrant:~$ cd desk-mx-l/ dvdk@vagrant:~/desk-mx-l$ wget https://mirror.dave.eu/desk-mx-l/desk-mx9-l-5.0.0/fsl-imx-wayland-glibc-x86_64-desk-image-qt6-armv8a-desk-mx93-toolchain-6.1-mickledore.sh -O sdk.sh --2024-01-30 15:33:00-- https://mirror.dave.eu/desk-mx-l/desk-mx9-l-5.0.0/fsl-imx-wayland-glibc-x86_64-desk-image-qt6-armv8a-desk-mx93-toolchain-6.1-mickledore.sh Resolving mirror.dave.eu (mirror.dave.eu)... 84.46.251.143 Connecting to mirror.dave.eu (mirror.dave.eu)|84.46.251.143|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 3614508682 (3.4G) [text/x-sh] Saving to: ‘sdk.sh’ sdk.sh 100%[==============================================================================================================>] 3.37G 5.50MB/s in 6m 23s 2024-01-30 15:39:22 (9.01 MB/s) - ‘sdk.sh’ saved [3614508682/3614508682] dvdk@vagrant:~/desk-mx-l$ chmod +x sdk.sh dvdk@vagrant:~/desk-mx-l$ ./sdk.sh -d /home/dvdk/desk-mx-l/sdk/desk-mx9-l-5.0.0 -y NXP i.MX Release Distro SDK installer version 6.1-mickledore ============================================================ The directory "/home/dvdk/desk-mx-l/sdk/desk-mx9-l-5.0.0" already contains a SDK for this architecture. If you continue, existing files will be overwritten! Proceed [y/N]? Y Extracting SDK.........................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................done Setting it up...done SDK has been successfully set up and is ready to be used. Each time you wish to use the SDK in a new shell session, you need to source the environment setup script e.g. $ . /home/dvdk/desk-mx-l/sdk/desk-mx9-l-5.0.0/environment-setup-armv8a-poky-linux dvdk@vagrant:~/desk-mx-l$
Using the SDK[edit | edit source]
Anytime it is required to compile u-boot or kernel sources, it is enough to enabling it using the script:
source ~/desk-mx-l/desk-mx9-l-5.0.0_env.sh
ConfigID and UniqueID[edit | edit source]
ConfigID[edit | edit source]
ConfigID is a new feature of DAVE Embedded Systems products. Its main purpose is providing an automatic mechanism for the identification of the product model and configuration.
With ConfigID, we aim at:
- completing the hardware configuration information that the software can't normally auto-detect (i.e. RAM chip version,...), implementing a dedicated reliable detect procedure
- when required, overriding the auto-detected hardware configuration information
When implemented, this mechanism allows for:
- initializing in the proper way the hardware platform, based on the specific features and parameters of the product, using a common software base (eg: a typical case is the SDRAM controller parameters, which must be configured by U-Boot depending on the particular memory chip, which can be different for the various SOM models)
- getting the complete hardware configuration (combining ConfigID with the information collectable at runtime) of a product deployed on the field
In simple words, model identification means the capability of reading a numerical code, stored in an available device (SOC's OTP , I2C EEPROM, 1-wire memories, protected NOR flash, etc.)
There are two ConfigIDs:
- SOM ConfigID: which reflects the characteristics of the SOM (stored on the SOM itself)
- Carrier Board (CB) ConfigID: which reflects the characteristics of the carrier board that hosts the SOM (stored on the carrier board itself and read by the SOM at boot time)
UniqueID[edit | edit source]
An additional attribute is UniqueID, which is a read-only code which univocally identifies a single product and is used for traceability.
|
It is worth remembering that ConfigID and UniqueID are independent from product serial number. |
Customer's action[edit | edit source]
DAVE Embedded Systems recommends to be up-to-date with Official SOM's BSPs for taking advantages of ConfigID/UniqueId features: this is the only required action.
- ConfigID advantage: to allow U-Boot bootloader to be executed only with the correct configuration (if the U-Boot loaded is not the proper one, it may stop execution avoiding incorrect behaviour)
- UniqueID advantage: to trace univocally each individual SOMs and, in turn, all the on-the-field equipments
ConfigID values[edit | edit source]
ConfigID is a N-bit (typically N>8) signed integer, that can have the following values:
- < 0: error
- -1: not initialized
- = 0: ConfigID legacy
- for prototypes (ConfigID not yet defined) or for products manufactured before the introduction of the ConfigID feature
- > 0: valid ConfigID
- values are reported accordingly with the specific product table
Hardware implementations of the ConfigID[edit | edit source]
The following paragraphs briefly describe the available solutions for storing the ConfigID.
OTP on the SOC[edit | edit source]
Some SOCs provides programmable OTPs (eg. for security, MAC address, boot modes, etc). Usually, some of these are general purpose registers and can be managed by the user.
This is the ideal implementation, because:
- ConfigID is stored in the most important component of the SOM
- the component that hosts the ConfigID is NOT optional
- typically, a very selective lock can be forced. In general, for reliability and/or security reasons, OTP areas used to store ConfigIDs may be locked during the manufacturing process.
OTP 1-wire memory[edit | edit source]
This implementation requires a 1-wire memory chip.
I2C Eeprom[edit | edit source]
This implementation requires connecting an EEPROM to an I2C bus of the SOC. Moreover, routing a write protect pin to the SOM connector is required.
NOR Flash SPI[edit | edit source]
This implementation requires a NOR flash connected to the SPI bus of the SOC.
DAVE Embedded Systems' hardware implementation[edit | edit source]
DAVE's SOCs implement the ConfigID feature depending on hardware Capabilities of the SOCs. The following list shows the priority used for its implementation:
- OTPs
- example: AXEL family processor (i.MX6) implements ConfigID using processor's OTP
- AXEL uses GP1 eFuse register to store ConfigID
- NOR Flash SPI
- example: DIVA family processor (AM335x) implements ConfigID using NOR SPI (if present)
- DIVA and BORA use the first 32bytes OTP block on NOR SPI to store ConfigID (and its CRC32), UniqueID (and its CRC32)
- I2C Eeprom
- example: DIVA family processor (AM335x) or BORA Lite processor (ZYNQ) implements ConfigID using I2C Eeprom when NOR SPI is not present (module boots from NAND or SD)
- DIVA and BORA Lite use the first 32bytes on I2C EPROM to store ConfigID (and its CRC32), UniqueID (and its CRC32)
- 1-wire
- example: latest AXEL Lite, AXEL ULite and BORA/BORA Xpress/BORA Lite Evaluation Kits implement CB ConfigID using the onboard 1-wire device (DS2431)
Software implementation[edit | edit source]
U-Boot[edit | edit source]
u-boot integrates the software routines for reading and displaying the ConfigID: hereunder an example of SOM ConfigID at startup:
U-Boot 2013.04-00010-gcb05b30 (Jun 26 2015 - 12:49:26)-xelk-2.1.0 CPU: Freescale i.MX6Q rev1.5 at 792 MHz CPU: Temperature 47 C, limits (-40 C, 125 C), calibration data: 0xc0 Reset cause: POR Environment: SPI Flash I2C: ready DRAM: 2 GiB Now running in RAM - U-Boot at: 8ff35000 NAND: 512 MiB MMC: FSL_SDHC: 0, FSL_SDHC: 1 SF: Detected S25FL256S with page size 64 KiB, total 32 MiB In: serial Out: serial Err: serial Power: found PFUZE100 (devid=10, revid=21) SOM ConfigID#: 00000003 SOM UniqueID#: df646299:0b0579d4
For accessing these information on Linux procfs, the device tree must be modified (using u-boot fdt command): for example:
DIVA# setenv fdtfixup 'fdt addr ${fdtaddr}; run fdtfixup_configid'
DIVA# setenv fdtfixup_configid 'fdt set / som_configid ${som_configid#}; fdt set / som_uniqueid ${som_uniqueid#}; fdt set / cb_configid ${cb_configid#}; fdt set / cb_uniqueid ${cb_uniqueid#}'
Linux[edit | edit source]
It is possible to read the ConfigID/UniqueID via procfs; for example:
root@axel-lite:~# cat /proc/device-tree/som/configid && echo 00000003 root@axel-lite:~# cat /proc/device-tree/som/uniqueid && echo df646299:0b0579d4 root@axel-lite:~#
Legacy device tree, has a sightly different procfs structure:
root@axel-lite:~# cat /proc/device-tree/som_configid && echo 00000003 root@axel-lite:~# cat /proc/device-tree/som_uniqueid && echo df646299:0b0579d4 root@axel-lite:~#
A real case example of ConfigID benefit[edit | edit source]
The ConfigID benefit is clear when:
- there is a number of products deployed on the field
- the products deployed on the field needs a SW update
The ideal scenario is that all products are equal and there are no differences on the Bill Of Material (BOM):
- All products have the same BOM with a single Config ID
ConfigID A
ConfigID A
ConfigID A
ConfigID A
ConfigID A
ConfigID A
In this case there are no problems to deploy a new SW update on the field: all products have the same HW configuration, then the same SW configuration.
Unfortunately, this is an ideal scenario. The reality is that:
- component obsolescence
- product shortage
- second source strategies
force to have an on-the-field different version of product (with same functionalities but with different HW configuration) which doesn't permit to realize what proposed in the ideal case.
|
The usage of the ConfigID technique, allows the running SW to identify the underlying HW configuration and automatically adapt the BSP (i.e. the driver layer) to properly use the HW subsystems: this, maintaining the overall product features identical to the final User point-of-view. |
- All products are similar BUT there are different Config ID between the 2 product versions
ConfigID A
ConfigID A
ConfigID B
ConfigID B
ConfigID A
ConfigID B
With a scenario, like the one described above, if you would like to update the SW you need to implement a strategy for understanding what platform version is going to be updated. The Config ID is used exactly for this goal.
The ConfigID provides to the software update routine the information on which product version is so the update can be adapted to the exact product version.
In this way, you can distribute one single version of the software update which will automatically adapt itself to the currently running platform.
How to handle After Sales with Config ID[edit | edit source]
One of the mos common questions about Config ID is how to handle the Config ID issue. Below is described with an example how to handle it.
This product is returned from the field with a problem on the display:
After Sales Dept analizes the product and decide to substitute the display. The problem is that the existing display is not available - because of is End Of Life (EOL) - and it is required to move to a different display: in the product a different Config ID will be written because of the 2 displays requires a dedicated SW version and cannot be distinguished automatically during the startup. The final result is to have the similar product:
As indicated, the new display requires a different Config ID (from A to B) so it can be updated with an easy software routine before start the SW update. This Config ID update routine can be implemented in manufacturing facility typically using a dedicated USB pen drive which modify the saved ConfigID to the new one depending on the storage memory in use
ConfigID[edit | edit source]
This article describes how the ConfigID is implemented in the products supported by the DESK-MX9-L Linux Kit.
AURA[edit | edit source]
As AURA is a system-on-module (SOM), the typical mechanism described here is used.
Moreover, a system is composed of the combination of a SOM and a carrier board. In this case, two ConfigIDs are used to identify the actual board configuration like it was a SOM+carrier board system.
For the sake of simplicity, the first ConfigID is denoted as SOM ConfigID, while the second one is denoted as CB ConfigID:
... SOM ConfigID#: 00000001 SOM UniqueID#: df646299:0b0579d4 CB ConfigID#: 00002001 CB UniqueID#: da000011:0dd2e72d ...
Generally speaking:
- SOM ConfigID is used to identify the configuration of the basic features of the SOM
- CB ConfigID is used to identify the peripherals and the I/O interfaces.
|
NXP guarantees that processors UIDs (a.k.a. SOM UniqueID# on DESK-MX9-L) to be unique over the whole MX9 family |
Booting from NFS[edit | edit source]
This configuration is very helpful during the software development (both for kernel and applications). The kernel image is downloaded via TFTP while the root file system is remotely mounted via NFS from the host. It is assumed that the development host:
- is connected with the target host board through an Ethernet LAN
- exports the directory containing the root file system for the target through the NFS server
- runs a TFTP server.
- has a proper subnet IP address
net_nfs configuration[edit | edit source]
DESK-MX9-L Virtual Machine is properly configured for the TFTP and NFS debug.
In any case, some variables has to be configured on the target and the VM itself has to be configured for respect to the network environment.
Host (Virtual Machine) configuration[edit | edit source]
The DESK-MX9-L Virtual Machine has the tftp and nfs services already running. Optionally, their configuration has to be changed according to the network configuration where the target is connected to.
Check and properly configure the items describe in VirtualBox Network Configuration
Target configuration[edit | edit source]
The IP address for server and target should be configured: an example (for a network subnet 192.168.0.x)
u-boot=> setenv serverip 192.168.0.89 u-boot=> setenv ipaddr 192.168.0.169 u-boot=> setenv gatewayip 192.168.0.254 u-boot=> setenv netmask 255.255.255.0 u-boot=> setenv netdev eth0
serveripis the IP address of the host machine running the tftp/nfs serveripaddris the IP address of the targetgatewayipis the gateway address of the targetnetmaskis the netmask address of the targetnetdevis the name of ethernet interface of the target
For using the DVDK Virtual Machine, a static IP address configuration has been selected, to the U-Boot variable ip_dyn has to be set to no:
u-boot=> setenv ip_dyn no
The kernel and device tree files have to be selected
u-boot=> setenv bootfile /tftpboot/desk-mx9-l/Image
AURA has its dtb file imx93-aura-cb2001.dtb
u-boot=> setenv fdt_file /tftpboot/desk-mx9-l/imx93-aura-cb2001.dtb
finally, the root file system directory on the Virtual Machine should be configured to let the kernel find the INIT
u-boot=> setenv rootpath /home/dvdk/desk-mx-l/rfs/desk-mx9-l/
To run this configuration just issue the net_nfs command which firstly downloads the kernel and device tree using the tftp protocol
u-boot=> setenv net_nfs 'run loadk loadfdt nfsargs addip addcons addmisc; booti ${loadaddr} - ${fdtaddr}'
Here below the complete bootlog from nfs:
u-boot=> run net_nfs
ethernet@428a0000 Waiting for PHY auto negotiation to complete........ done
Using ethernet@428a0000 device
TFTP from server 192.168.0.169; our IP address is 192.168.0.89
Filename 'desk-mx9-l/Image'.
Load address: 0x80400000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
###########
580.1 KiB/s
done
Bytes transferred = 33001984 (1f79200 hex)
Using ethernet@428a0000 device
TFTP from server 192.168.0.169; our IP address is 192.168.0.89
Filename 'desk-mx9-l/imx93-aura-cb2001.dtb'.
Load address: 0x83000000
Loading: #########
376 KiB/s
done
Bytes transferred = 45441 (b181 hex)
## Flattened Device Tree blob at 83000000
Booting using the fdt blob at 0x83000000
Working FDT set to 83000000
Using Device Tree in place at 0000000083000000, end 000000008300e180
Working FDT set to 83000000
Starting kernel ...
[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x412fd050]
[ 0.000000] Linux version 6.1.55-desk-mx9-l-5.0.0-rc2+g27df6782c46f (oe-user@oe-host) (aarch64-poky-linux-gcc (GCC) 12.3.0, GNU ld (GNU Binutils) 2.40.0.20230703) #1 SMP PREEMPT Wed Jan 24 09:29:00 UTC 2024
[ 0.000000] Machine model: DAVE i.MX93 AURA on SBCX
[ 0.000000] efi: UEFI not found.
[ 0.000000] Reserved memory: created CMA memory pool at 0x00000000b0000000, size 256 MiB
[ 0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
[ 0.000000] Reserved memory: created DMA memory pool at 0x00000000a4020000, size 1 MiB
[ 0.000000] OF: reserved mem: initialized node vdevbuffer@a4020000, compatible id shared-dma-pool
[ 0.000000] Reserved memory: created DMA memory pool at 0x00000000a4120000, size 1 MiB
[ 0.000000] OF: reserved mem: initialized node ele-reserved@a4120000, compatible id shared-dma-pool
[ 0.000000] Reserved memory: created CMA memory pool at 0x00000000c0000000, size 256 MiB
[ 0.000000] OF: reserved mem: initialized node ethosu_region@C0000000, compatible id shared-dma-pool
[ 0.000000] earlycon: lpuart32 at MMIO32 0x0000000044380000 (options '')
[ 0.000000] printk: bootconsole [lpuart32] enabled
[ 0.000000] NUMA: No NUMA configuration found
[ 0.000000] NUMA: Faking a node at [mem 0x0000000080000000-0x00000000ffffffff]
[ 0.000000] NUMA: NODE_DATA [mem 0xffbc5700-0xffbc7fff]
[ 0.000000] Zone ranges:
[ 0.000000] DMA [mem 0x0000000080000000-0x00000000ffffffff]
[ 0.000000] DMA32 empty
[ 0.000000] Normal empty
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x0000000080000000-0x00000000a3ffffff]
[ 0.000000] node 0: [mem 0x00000000a4000000-0x00000000a421ffff]
[ 0.000000] node 0: [mem 0x00000000a4220000-0x00000000ffffffff]
[ 0.000000] Initmem setup node 0 [mem 0x0000000080000000-0x00000000ffffffff]
[ 0.000000] psci: probing for conduit method from DT.
[ 0.000000] psci: PSCIv1.1 detected in firmware.
[ 0.000000] psci: Using standard PSCI v0.2 function IDs
[ 0.000000] psci: MIGRATE_INFO_TYPE not supported.
[ 0.000000] psci: SMC Calling Convention v1.2
[ 0.000000] percpu: Embedded 20 pages/cpu s44520 r8192 d29208 u81920
[ 0.000000] Detected VIPT I-cache on CPU0
[ 0.000000] CPU features: detected: GIC system register CPU interface
[ 0.000000] CPU features: detected: Virtualization Host Extensions
[ 0.000000] CPU features: detected: Qualcomm erratum 1009, or ARM erratum 1286807, 2441009
[ 0.000000] CPU features: detected: ARM errata 1165522, 1319367, or 1530923
[ 0.000000] alternatives: applying boot alternatives
[ 0.000000] Fallback order for Node 0: 0
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 516096
[ 0.000000] Policy zone: DMA
[ 0.000000] Kernel command line: root=/dev/nfs rw nfsroot=192.168.0.169:/home/dvdk/desk-mx-l/rfs/desk-mx9-l/,v3,tcp ip=192.168.0.89:192.168.0.169:192.168.0.254:255.255.255.0:desk-mx:eth0:off panic=1 console=ttyLP0,115200 earlycon ;
[ 0.000000] Unknown kernel command line parameters ";", will be passed to user space.
[ 0.000000] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes, linear)
[ 0.000000] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes, linear)
[ 0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[ 0.000000] Memory: 1497352K/2097152K available (19776K kernel code, 1636K rwdata, 7312K rodata, 3392K init, 645K bss, 75512K reserved, 524288K cma-reserved)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[ 0.000000] rcu: Preemptible hierarchical RCU implementation.
[ 0.000000] rcu: RCU event tracing is enabled.
[ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=2.
[ 0.000000] Trampoline variant of Tasks RCU enabled.
[ 0.000000] Tracing variant of Tasks RCU enabled.
[ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
[ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[ 0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[ 0.000000] GICv3: GIC: Using split EOI/Deactivate mode
[ 0.000000] GICv3: 960 SPIs implemented
[ 0.000000] GICv3: 0 Extended SPIs implemented
[ 0.000000] Root IRQ handler: gic_handle_irq
[ 0.000000] GICv3: GICv3 features: 16 PPIs
[ 0.000000] GICv3: CPU0: found redistributor 0 region 0:0x0000000048040000
[ 0.000000] rcu: srcu_init: Setting srcu_struct sizes based on contention.
[ 0.000000] arch_timer: cp15 timer(s) running at 24.00MHz (phys).
[ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns
[ 0.000000] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns
[ 0.008291] Console: colour dummy device 80x25
[ 0.012526] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=96000)
[ 0.022704] pid_max: default: 32768 minimum: 301
[ 0.027329] LSM: Security Framework initializing
[ 0.031958] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes, linear)
[ 0.039259] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes, linear)
[ 0.047730] cacheinfo: Unable to detect cache hierarchy for CPU 0
[ 0.053987] cblist_init_generic: Setting adjustable number of callback queues.
[ 0.060973] cblist_init_generic: Setting shift to 1 and lim to 1.
[ 0.067057] cblist_init_generic: Setting adjustable number of callback queues.
[ 0.074214] cblist_init_generic: Setting shift to 1 and lim to 1.
[ 0.080394] rcu: Hierarchical SRCU implementation.
[ 0.085047] rcu: Max phase no-delay instances is 1000.
[ 0.090951] EFI services will not be available.
[ 0.095385] smp: Bringing up secondary CPUs ...
[ 0.100073] Detected VIPT I-cache on CPU1
[ 0.100138] cacheinfo: Unable to detect cache hierarchy for CPU 1
[ 0.100147] GICv3: CPU1: found redistributor 100 region 0:0x0000000048060000
[ 0.100181] CPU1: Booted secondary processor 0x0000000100 [0x412fd050]
[ 0.100265] smp: Brought up 1 node, 2 CPUs
[ 0.127683] SMP: Total of 2 processors activated.
[ 0.132355] CPU features: detected: 32-bit EL0 Support
[ 0.137476] CPU features: detected: 32-bit EL1 Support
[ 0.142581] CPU features: detected: Data cache clean to the PoU not required for I/D coherence
[ 0.151157] CPU features: detected: Common not Private translations
[ 0.157396] CPU features: detected: CRC32 instructions
[ 0.162512] CPU features: detected: RCpc load-acquire (LDAPR)
[ 0.168229] CPU features: detected: LSE atomic instructions
[ 0.173776] CPU features: detected: Privileged Access Never
[ 0.179322] CPU features: detected: RAS Extension Support
[ 0.184698] CPU features: detected: Speculative Store Bypassing Safe (SSBS)
[ 0.191677] CPU: All CPU(s) started at EL2
[ 0.195705] alternatives: applying system-wide alternatives
[ 0.205417] devtmpfs: initialized
[ 0.212995] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[ 0.222488] futex hash table entries: 512 (order: 3, 32768 bytes, linear)
[ 0.237224] pinctrl core: initialized pinctrl subsystem
[ 0.243348] DMI not present or invalid.
[ 0.247343] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[ 0.253772] DMA: preallocated 256 KiB GFP_KERNEL pool for atomic allocations
[ 0.260648] DMA: preallocated 256 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
[ 0.268349] DMA: preallocated 256 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
[ 0.276214] audit: initializing netlink subsys (disabled)
[ 0.281725] audit: type=2000 audit(0.184:1): state=initialized audit_enabled=0 res=1
[ 0.282126] thermal_sys: Registered thermal governor 'step_wise'
[ 0.289252] thermal_sys: Registered thermal governor 'power_allocator'
[ 0.295365] cpuidle: using governor menu
[ 0.305821] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[ 0.312424] ASID allocator initialised with 65536 entries
[ 0.318355] Serial: AMBA PL011 UART driver
[ 0.322233] imx mu driver is registered.
[ 0.326092] imx rpmsg driver is registered.
[ 0.334623] imx93-pinctrl 443c0000.pinctrl: initialized IMX pinctrl driver
[ 0.346899] platform 4ae30000.lcd-controller: Fixed dependency cycle(s) with /soc@0/ldb@4ac10020/lvds-channel@0/port@0/endpoint
[ 0.360391] platform lvds_panel: Fixed dependency cycle(s) with /soc@0/ldb@4ac10020/lvds-channel@0/port@1/endpoint
[ 0.370992] KASLR disabled due to lack of seed
[ 0.386572] HugeTLB: registered 1.00 GiB page size, pre-allocated 0 pages
[ 0.393105] HugeTLB: 0 KiB vmemmap can be freed for a 1.00 GiB page
[ 0.399336] HugeTLB: registered 32.0 MiB page size, pre-allocated 0 pages
[ 0.406094] HugeTLB: 0 KiB vmemmap can be freed for a 32.0 MiB page
[ 0.412335] HugeTLB: registered 2.00 MiB page size, pre-allocated 0 pages
[ 0.419094] HugeTLB: 0 KiB vmemmap can be freed for a 2.00 MiB page
[ 0.425335] HugeTLB: registered 64.0 KiB page size, pre-allocated 0 pages
[ 0.432094] HugeTLB: 0 KiB vmemmap can be freed for a 64.0 KiB page
[ 0.439905] ACPI: Interpreter disabled.
[ 0.445075] iommu: Default domain type: Translated
[ 0.449697] iommu: DMA domain TLB invalidation policy: strict mode
[ 0.456145] SCSI subsystem initialized
[ 0.459977] usbcore: registered new interface driver usbfs
[ 0.465232] usbcore: registered new interface driver hub
[ 0.470498] usbcore: registered new device driver usb
[ 0.476241] mc: Linux media interface: v0.10
[ 0.480286] videodev: Linux video capture interface: v2.00
[ 0.485750] pps_core: LinuxPPS API ver. 1 registered
[ 0.490649] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 0.499754] PTP clock support registered
[ 0.503741] EDAC MC: Ver: 3.0.0
[ 0.507718] FPGA manager framework
[ 0.510935] Advanced Linux Sound Architecture Driver Initialized.
[ 0.517314] Bluetooth: Core ver 2.22
[ 0.520641] NET: Registered PF_BLUETOOTH protocol family
[ 0.525917] Bluetooth: HCI device and connection manager initialized
[ 0.532243] Bluetooth: HCI socket layer initialized
[ 0.537094] Bluetooth: L2CAP socket layer initialized
[ 0.542126] Bluetooth: SCO socket layer initialized
[ 0.547292] vgaarb: loaded
[ 0.550208] clocksource: Switched to clocksource arch_sys_counter
[ 0.556233] VFS: Disk quotas dquot_6.6.0
[ 0.559980] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 0.566923] pnp: PnP ACPI: disabled
[ 0.574948] NET: Registered PF_INET protocol family
[ 0.579733] IP idents hash table entries: 32768 (order: 6, 262144 bytes, linear)
[ 0.588086] tcp_listen_portaddr_hash hash table entries: 1024 (order: 2, 16384 bytes, linear)
[ 0.596409] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
[ 0.604075] TCP established hash table entries: 16384 (order: 5, 131072 bytes, linear)
[ 0.612019] TCP bind hash table entries: 16384 (order: 7, 524288 bytes, linear)
[ 0.619631] TCP: Hash tables configured (established 16384 bind 16384)
[ 0.625991] UDP hash table entries: 1024 (order: 3, 32768 bytes, linear)
[ 0.632595] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes, linear)
[ 0.639783] NET: Registered PF_UNIX/PF_LOCAL protocol family
[ 0.645627] RPC: Registered named UNIX socket transport module.
[ 0.651293] RPC: Registered udp transport module.
[ 0.655957] RPC: Registered tcp transport module.
[ 0.660636] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.667593] PCI: CLS 0 bytes, default 64
[ 0.671786] hw perfevents: enabled with armv8_cortex_a55 PMU driver, 7 counters available
[ 0.680201] kvm [1]: IPA Size Limit: 40 bits
[ 0.684234] kvm [1]: GICv3: no GICV resource entry
[ 0.688977] kvm [1]: disabling GICv2 emulation
[ 0.693407] kvm [1]: GIC system register CPU interface enabled
[ 0.699248] kvm [1]: vgic interrupt IRQ9
[ 0.703152] kvm [1]: VHE mode initialized successfully
[ 0.709098] Initialise system trusted keyrings
[ 0.713477] workingset: timestamp_bits=42 max_order=19 bucket_order=0
[ 0.723724] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 0.729775] NFS: Registering the id_resolver key type
[ 0.734603] Key type id_resolver registered
[ 0.738724] Key type id_legacy registered
[ 0.742758] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[ 0.749386] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering...
[ 0.756761] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[ 0.763072] 9p: Installing v9fs 9p2000 file system support
[ 0.793556] Key type asymmetric registered
[ 0.797389] Asymmetric key parser 'x509' registered
[ 0.802278] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 243)
[ 0.809611] io scheduler mq-deadline registered
[ 0.814115] io scheduler kyber registered
[ 0.822644] EINJ: ACPI disabled.
[ 0.830435] Bus freq driver module loaded
[ 0.839054] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[ 0.856405] printk: console [ttyLP0] enabled0x44380010 (irq = 18, base_baud = 1500000) is a FSL_LPUART
[ 0.856405] printk: console [ttyLP0] enabled
[ 0.864817] printk: bootconsole [lpuart32] disabled
[ 0.864817] printk: bootconsole [lpuart32] disabled
[ 0.875124] 44390000.serial: ttyLP1 at MMIO 0x44390010 (irq = 19, base_baud = 1500000) is a FSL_LPUART
[ 0.884979] 42580000.serial: ttyLP3 at MMIO 0x42580010 (irq = 20, base_baud = 1500000) is a FSL_LPUART
[ 0.894800] 42690000.serial: ttyLP2 at MMIO 0x42690010 (irq = 21, base_baud = 1500000) is a FSL_LPUART
[ 0.908653] Error: Driver 'mxsfb' is already registered, aborting...
[ 0.916480] imx-drm display-subsystem: bound imx-lcdifv3-crtc.0 (ops lcdifv3_crtc_ops)
[ 0.925463] cacheinfo: Unable to detect cache hierarchy for CPU 0
[ 0.935019] loop: module loaded
[ 0.939315] of_reserved_mem_lookup() returned NULL
[ 0.944250] megasas: 07.719.03.00-rc1
[ 0.951696] spi-nand spi0.0: Winbond SPI NAND was found.
[ 0.957035] spi-nand spi0.0: 256 MiB, block size: 128 KiB, page size: 2048, OOB size: 128
[ 0.968248] tun: Universal TUN/TAP device driver, 1.6
[ 0.973508] CAN device driver interface
[ 0.978934] thunder_xcv, ver 1.0
[ 0.982186] thunder_bgx, ver 1.0
[ 0.985437] nicpf, ver 1.0
[ 0.989548] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version
[ 0.996779] hns3: Copyright (c) 2017 Huawei Corporation.
[ 1.002220] hclge is initializing
[ 1.005541] e1000: Intel(R) PRO/1000 Network Driver
[ 1.010412] e1000: Copyright (c) 1999-2006 Intel Corporation.
[ 1.016176] e1000e: Intel(R) PRO/1000 Network Driver
[ 1.021133] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[ 1.027094] igb: Intel(R) Gigabit Ethernet Network Driver
[ 1.032488] igb: Copyright (c) 2007-2014 Intel Corporation.
[ 1.038079] igbvf: Intel(R) Gigabit Virtual Function Network Driver
[ 1.044333] igbvf: Copyright (c) 2009 - 2012 Intel Corporation.
[ 1.050456] sky2: driver version 1.30
[ 1.054600] usbcore: registered new interface driver r8152
[ 1.060367] VFIO - User Level meta-driver version: 0.3
[ 1.068262] usbcore: registered new interface driver uas
[ 1.073619] usbcore: registered new interface driver usb-storage
[ 1.079681] usbcore: registered new interface driver usbserial_generic
[ 1.086210] usbserial: USB Serial support registered for generic
[ 1.092226] usbcore: registered new interface driver ftdi_sio
[ 1.097971] usbserial: USB Serial support registered for FTDI USB Serial Device
[ 1.105288] usbcore: registered new interface driver usb_serial_simple
[ 1.111812] usbserial: USB Serial support registered for carelink
[ 1.117904] usbserial: USB Serial support registered for flashloader
[ 1.124262] usbserial: USB Serial support registered for funsoft
[ 1.130262] usbserial: USB Serial support registered for google
[ 1.136188] usbserial: USB Serial support registered for hp4x
[ 1.141932] usbserial: USB Serial support registered for kaufmann
[ 1.148021] usbserial: USB Serial support registered for libtransistor
[ 1.154546] usbserial: USB Serial support registered for moto_modem
[ 1.160812] usbserial: USB Serial support registered for motorola_tetra
[ 1.167426] usbserial: USB Serial support registered for nokia
[ 1.173257] usbserial: USB Serial support registered for novatel_gps
[ 1.179611] usbserial: USB Serial support registered for siemens_mpi
[ 1.185967] usbserial: USB Serial support registered for suunto
[ 1.191884] usbserial: USB Serial support registered for vivopay
[ 1.197889] usbserial: USB Serial support registered for zio
[ 1.203562] usbcore: registered new interface driver usb_ehset_test
[ 1.212085] bbnsm_pwrkey 44440000.bbnsm:pwrkey: KEY_POWER without setting in dts
[ 1.220294] input: 44440000.bbnsm:pwrkey as /devices/platform/soc@0/44000000.bus/44440000.bbnsm/44440000.bbnsm:pwrkey/input/input0
[ 1.234971] bbnsm_rtc 44440000.bbnsm:rtc: registered as rtc0
[ 1.241024] bbnsm_rtc 44440000.bbnsm:rtc: setting system clock to 1970-01-01T00:00:00 UTC (0)
[ 1.250264] i2c_dev: i2c /dev entries driver
[ 1.255599] Driver for 1-wire Dallas network protocol.
[ 1.262740] imx7ulp-wdt 42490000.wdog: imx93 wdt probe
[ 1.297495] Bluetooth: HCI UART driver ver 2.3
[ 1.301959] Bluetooth: HCI UART protocol H4 registered
[ 1.307097] Bluetooth: HCI UART protocol BCSP registered
[ 1.312416] Bluetooth: HCI UART protocol LL registered
[ 1.317541] Bluetooth: HCI UART protocol ATH3K registered
[ 1.322941] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 1.329322] Bluetooth: HCI UART protocol Broadcom registered
[ 1.334985] Bluetooth: HCI UART protocol QCA registered
[ 1.341469] sdhci: Secure Digital Host Controller Interface driver
[ 1.347672] sdhci: Copyright(c) Pierre Ossman
[ 1.352493] Synopsys Designware Multimedia Card Interface Driver
[ 1.358912] sdhci-pltfm: SDHCI platform and OF driver helper
[ 1.365946] ledtrig-cpu: registered to indicate activity on CPUs
[ 1.373041] fsl-ele-mu soc@0:ele-mu: ele_mu_probe: Not able to read cmd_tag
[ 1.380024] fsl-ele-mu soc@0:ele-mu: ele_mu_probe: Not able to read rsp_tag
[ 1.387426] fsl-ele-mu soc@0:ele-mu: assigned reserved memory node ele-reserved@a4120000
[ 1.395553] fsl-ele-mu soc@0:ele-mu: Failed to initialize ele fw.
[ 1.396820] mmc0: SDHCI controller on 42850000.mmc [42850000.mmc] using ADMA
[ 1.401675] fsl-ele-mu soc@0:ele-mu: registering ele-trng
[ 1.414372] fsl-ele-mu soc@0:ele-mu: Successfully registered ele-trng
[ 1.420923] random: crng init done
[ 1.421018] SMCCC: SOC_ID: ARCH_SOC_ID not implemented, skipping ....
[ 1.430807] hid: raw HID events driver (C) Jiri Kosina
[ 1.436402] usbcore: registered new interface driver usbhid
[ 1.442014] usbhid: USB HID core driver
[ 1.447245] mxc-md 42800000.bus:camera: deferring cap_device registration
[ 1.454880] ethosu ethosu: assigned reserved memory node ethosu_region@C0000000
[ 1.463707] remoteproc remoteproc0: releasing imx-rproc
[ 1.471285] cs_system_cfg: CoreSight Configuration manager initialised
[ 1.485154] NET: Registered PF_LLC protocol family
[ 1.490508] NET: Registered PF_INET6 protocol family
[ 1.496131] Segment Routing with IPv6
[ 1.499823] In-situ OAM (IOAM) with IPv6
[ 1.503789] NET: Registered PF_PACKET protocol family
[ 1.508862] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[ 1.521807] can: controller area network core
[ 1.526194] NET: Registered PF_CAN protocol family
[ 1.530992] can: raw protocol
[ 1.533956] can: broadcast manager protocol
[ 1.538138] can: netlink gateway - max_hops=1
[ 1.542748] Bluetooth: RFCOMM TTY layer initialized
[ 1.547660] Bluetooth: RFCOMM socket layer initialized
[ 1.552855] Bluetooth: RFCOMM ver 1.11
[ 1.556628] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 1.561954] Bluetooth: BNEP filters: protocol multicast
[ 1.567172] Bluetooth: BNEP socket layer initialized
[ 1.572128] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 1.578055] Bluetooth: HIDP socket layer initialized
[ 1.583246] 8021q: 802.1Q VLAN Support v1.8
[ 1.587486] lib80211: common routines for IEEE802.11 drivers
[ 1.593259] 9pnet: Installing 9P2000 support
[ 1.597621] Key type dns_resolver registered
[ 1.602328] registered taskstats version 1
[ 1.606453] Loading compiled-in X.509 certificates
[ 1.612651] mmc0: new DDR MMC card at address 0001
[ 1.618061] mmcblk0: mmc0:0001 DG4008 7.28 GiB
[ 1.624689] mmcblk0: p1 p2
[ 1.624882] usb_phy_generic soc@0:usbphynop1: supply vcc not found, using dummy regulator
[ 1.627960] mmcblk0boot0: mmc0:0001 DG4008 4.00 MiB
[ 1.635930] usb_phy_generic soc@0:usbphynop1: dummy supplies not allowed for exclusive requests
[ 1.641635] mmcblk0boot1: mmc0:0001 DG4008 4.00 MiB
[ 1.649676] usb_phy_generic soc@0:usbphynop2: supply vcc not found, using dummy regulator
[ 1.655185] mmcblk0rpmb: mmc0:0001 DG4008 4.00 MiB, chardev (234:0)
[ 1.662686] usb_phy_generic soc@0:usbphynop2: dummy supplies not allowed for exclusive requests
[ 1.686527] imx93-ldb soc@0:ldb@4ac10020: Failed to create device link (0x180) with soc@0:phy@4ac10024
[ 1.699634] imx-drm display-subsystem: bound imx-lcdifv3-crtc.0 (ops lcdifv3_crtc_ops)
[ 1.709069] imx-dwmac 428a0000.ethernet: IRQ eth_lpi not found
[ 1.715173] imx-dwmac 428a0000.ethernet: User ID: 0x10, Synopsys ID: 0x52
[ 1.721991] imx-dwmac 428a0000.ethernet: DWMAC4/5
[ 1.726777] imx-dwmac 428a0000.ethernet: DMA HW capability register supported
[ 1.733897] imx-dwmac 428a0000.ethernet: RX Checksum Offload Engine supported
[ 1.741021] imx-dwmac 428a0000.ethernet: TX Checksum insertion supported
[ 1.747710] imx-dwmac 428a0000.ethernet: Wake-Up On Lan supported
[ 1.753847] imx-dwmac 428a0000.ethernet: Enable RX Mitigation via HW Watchdog Timer
[ 1.761503] imx-dwmac 428a0000.ethernet: Enabled L3L4 Flow TC (entries=8)
[ 1.768279] imx-dwmac 428a0000.ethernet: Enabled RFS Flow TC (entries=10)
[ 1.775065] imx-dwmac 428a0000.ethernet: Enabling HW TC (entries=256, max_off=256)
[ 1.782623] imx-dwmac 428a0000.ethernet: Using 32/32 bits DMA host/device width
[ 1.800047] sdhci-esdhc-imx 42860000.mmc: Got CD GPIO
[ 1.800573] isi-capture 4ae40000.isi:cap_device: deferring 4ae40000.isi:cap_device device registration
[ 1.814561] mxc-isi 4ae40000.isi: mxc_isi.0 registered successfully
[ 1.821687] mxc-md 42800000.bus:camera: deferring cap_device registration
[ 1.829999] remoteproc remoteproc0: releasing imx-rproc
[ 1.835434] mmc1: SDHCI controller on 42860000.mmc [42860000.mmc] using ADMA
[ 1.840620] i2c i2c-0: LPI2C adapter registered
[ 1.851606] nxp-pca9450 1-0025: pca9451a probed.
[ 1.856358] i2c i2c-1: LPI2C adapter registered
[ 1.861849] i2c 2-003c: Fixed dependency cycle(s) with /soc@0/bus@42800000/camera/csi@4ae00000/port@0/endpoint
[ 1.872945] ov5640 2-003c: ov5640_write_reg: error: reg=3008, val=82
[ 1.887156] mmc1: new high speed SDHC card at address 5048
[ 1.893153] mmcblk1: mmc1:5048 SD32G 28.9 GiB
[ 1.899001] mmcblk1: p1 p2
[ 1.905587] i2c i2c-2: LPI2C adapter registered
[ 1.911853] imx-drm display-subsystem: bound imx-lcdifv3-crtc.0 (ops lcdifv3_crtc_ops)
[ 1.920053] imx-drm display-subsystem: bound soc@0:ldb@4ac10020 (ops imx93_ldb_ops)
[ 1.927980] [drm] Initialized imx-drm 1.0.0 20120507 for display-subsystem on minor 0
[ 1.967244] Console: switching to colour frame buffer device 100x30
[ 1.987808] imx-drm display-subsystem: [drm] fb0: imx-drmdrmfb frame buffer device
[ 1.999429] ci_hdrc ci_hdrc.1: EHCI Host Controller
[ 2.004353] ci_hdrc ci_hdrc.1: new USB bus registered, assigned bus number 1
[ 2.026227] ci_hdrc ci_hdrc.1: USB 2.0 started, EHCI 1.00
[ 2.032148] hub 1-0:1.0: USB hub found
[ 2.035926] hub 1-0:1.0: 1 port detected
[ 2.042163] mx8-img-md: Registered mxc_isi.0.capture as /dev/video0
[ 2.048484] mxc-md 42800000.bus:camera: deferring csi device registration
[ 2.056286] dwc-mipi-csi2-host 4ae00000.csi: lanes: 2, name: mxc-mipi-csi2.0
[ 2.064371] remoteproc remoteproc0: releasing imx-rproc
[ 2.087080] mx8-img-md: Registered mxc_isi.0.capture as /dev/video0
[ 2.093422] mx8-img-md: Registered sensor subdevice: ov5640 2-003c (1)
[ 2.099958] mx8-img-md: created link [mxc_isi.0] => [mxc_isi.0.capture]
[ 2.106564] mx8-img-md: created link [mxc-mipi-csi2.0] => [mxc_isi.0]
[ 2.112998] mx8-img-md: created link [ov5640 2-003c] => [mxc-mipi-csi2.0]
[ 2.119772] mxc-md 42800000.bus:camera: mxc_md_create_links
[ 2.126629] remoteproc remoteproc0: releasing imx-rproc
[ 2.132807] remoteproc remoteproc0: releasing imx-rproc
[ 2.139760] imx-dwmac 428a0000.ethernet eth0: Register MEM_TYPE_PAGE_POOL RxQ-0
[ 2.186924] imx-dwmac 428a0000.ethernet eth0: PHY [stmmac-1:07] driver [Microchip LAN8841 Gigabit PHY] (irq=POLL)
[ 2.207221] imx-dwmac 428a0000.ethernet eth0: No Safety Features support found
[ 2.214454] imx-dwmac 428a0000.ethernet eth0: IEEE 1588-2008 Advanced Timestamp supported
[ 2.222817] imx-dwmac 428a0000.ethernet eth0: registered PTP clock
[ 2.229376] imx-dwmac 428a0000.ethernet eth0: FPE workqueue start
[ 2.235471] imx-dwmac 428a0000.ethernet eth0: configuring for phy/rgmii-id link mode
[ 2.243626] 8021q: adding VLAN 0 to HW filter on device eth0
[ 2.634214] usb 1-1: new high-speed USB device number 2 using ci_hdrc
[ 2.796025] usb-storage 1-1:1.0: USB Mass Storage device detected
[ 2.802493] scsi host0: usb-storage 1-1:1.0
[ 2.807811] remoteproc remoteproc0: releasing imx-rproc
[ 3.815663] scsi 0:0:0:0: Direct-Access USB SanDisk 3.2Gen1 1.00 PQ: 0 ANSI: 6
[ 3.824788] sd 0:0:0:0: [sda] 60125184 512-byte logical blocks: (30.8 GB/28.7 GiB)
[ 3.833401] sd 0:0:0:0: [sda] Write Protect is off
[ 3.838908] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 3.860161] sda: sda1
[ 3.862760] sd 0:0:0:0: [sda] Attached SCSI removable disk
[ 3.869214] remoteproc remoteproc0: releasing imx-rproc
[ 6.344483] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 6.350768] imx-dwmac 428a0000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[ 6.378213] IP-Config: Complete:
[ 6.381435] device=eth0, hwaddr=1e:48:64:89:f4:51, ipaddr=192.168.0.89, mask=255.255.255.0, gw=192.168.0.254
[ 6.391693] host=desk-mx, domain=, nis-domain=(none)
[ 6.397083] bootserver=192.168.0.169, rootserver=192.168.0.169, rootpath=
[ 6.397199] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 6.413522] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[ 6.420132] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[ 6.422995] ALSA device list:
[ 6.428781] platform regulatory.0: Falling back to sysfs fallback for: regulatory.db
[ 6.431781] #0: SBCX_TLV320
[ 6.615832] VFS: Mounted root (nfs filesystem) on device 0:21.
[ 6.625250] devtmpfs: mounted
[ 6.629253] Freeing unused kernel memory: 3392K
[ 6.646249] Run /sbin/init as init process
[ 7.139417] systemd[1]: System time before build time, advancing clock.
[ 7.321889] systemd[1]: systemd 253.1^ running in system mode (+PAM -AUDIT -SELINUX -APPARMOR +IMA -SMACK +SECCOMP -GCRYPT -GNUTLS -OPENSSL +ACL +BLKID -CURL -ELFUTILS -FIDO2 -IDN2 -IDN -IPTC +KMOD -LIBCRYPTSETUP +LIBFDISK -PCRE2 -PWQUALITY -P11KIT -QRENCODE -TPM2 -BZIP2 -LZ4 -XZ -ZLIB +ZSTD -BPF_FRAMEWORK -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=hybrid)
[ 7.353674] systemd[1]: Detected architecture arm64.
Welcome to NXP i.MX Release Distro 6.1-mickledore (mickledore)!
[ 7.433863] systemd[1]: Hostname set to <desk-mx93>.
[ 7.639155] systemd-sysv-generator[182]: SysV service '/etc/init.d/single' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[ 7.679178] systemd-sysv-generator[182]: SysV service '/etc/init.d/halt' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[ 7.734562] systemd-sysv-generator[182]: SysV service '/etc/init.d/sshd' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[ 7.761399] systemd-sysv-generator[182]: SysV service '/etc/init.d/sendsigs' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[ 7.786347] systemd-sysv-generator[182]: SysV service '/etc/init.d/umountfs' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[ 7.877676] systemd-sysv-generator[182]: SysV service '/etc/init.d/rc.local' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[ 7.906297] systemd-sysv-generator[182]: SysV service '/etc/init.d/reboot' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[ 7.939008] systemd-sysv-generator[182]: SysV service '/etc/init.d/psplash.sh' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[ 7.972662] systemd-sysv-generator[182]: SysV service '/etc/init.d/trousers' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[ 8.045014] systemd-sysv-generator[182]: SysV service '/etc/init.d/fuse' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[ 8.082950] systemd-sysv-generator[182]: SysV service '/etc/init.d/umountnfs.sh' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[ 8.112726] systemd-sysv-generator[182]: SysV service '/etc/init.d/save-rtc.sh' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[ 9.153313] systemd[1]: Queued start job for default target Graphical Interface.
[ 9.201488] systemd[1]: Created slice Slice /system/getty.
[ OK ] Created slice Slice /system/getty.
[ 9.224127] systemd[1]: Created slice Slice /system/modprobe.
[ OK ] Created slice Slice /system/modprobe.
[ 9.248059] systemd[1]: Created slice Slice /system/serial-getty.
[ OK ] Created slice Slice /system/serial-getty.
[ 9.271682] systemd[1]: Created slice User and Session Slice.
[ OK ] Created slice User and Session Slice.
[ 9.294626] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[ OK ] Started Dispatch Password …ts to Console Directory Watch.
[ 9.318573] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[ OK ] Started Forward Password R…uests to Wall Directory Watch.
[ 9.342579] systemd[1]: Reached target Host and Network Name Lookups.
[ OK ] Reached target Host and Network Name Lookups.
[ 9.366375] systemd[1]: Reached target Path Units.
[ OK ] Reached target Path Units.
[ 9.386376] systemd[1]: Reached target Remote File Systems.
[ OK ] Reached target Remote File Systems.
[ 9.406388] systemd[1]: Reached target Slice Units.
[ OK ] Reached target Slice Units.
[ 9.426400] systemd[1]: Reached target Swaps.
[ OK ] Reached target Swaps.
[ 9.501961] systemd[1]: Listening on RPCbind Server Activation Socket.
[ OK ] Listening on RPCbind Server Activation Socket.
[ 9.526480] systemd[1]: Reached target RPC Port Mapper.
[ OK ] Reached target RPC Port Mapper.
[ 9.549498] systemd[1]: Listening on Syslog Socket.
[ OK ] Listening on Syslog Socket.
[ 9.570711] systemd[1]: Listening on initctl Compatibility Named Pipe.
[ OK ] Listening on initctl Compatibility Named Pipe.
[ 9.596478] systemd[1]: Listening on Journal Audit Socket.
[ OK ] Listening on Journal Audit Socket.
[ 9.618879] systemd[1]: Listening on Journal Socket (/dev/log).
[ OK ] Listening on Journal Socket (/dev/log).
[ 9.642951] systemd[1]: Listening on Journal Socket.
[ OK ] Listening on Journal Socket.
[ 9.664731] systemd[1]: Listening on Network Service Netlink Socket.
[ OK ] Listening on Network Service Netlink Socket.
[ 9.690609] systemd[1]: Listening on udev Control Socket.
[ OK ] Listening on udev Control Socket.
[ 9.710867] systemd[1]: Listening on udev Kernel Socket.
[ OK ] Listening on udev Kernel Socket.
[ 9.741382] systemd[1]: Listening on User Database Manager Socket.
[ OK ] Listening on User Database Manager Socket.
[ 9.778668] systemd[1]: Mounting Huge Pages File System...
Mounting Huge Pages File System...
[ 9.802087] systemd[1]: Mounting POSIX Message Queue File System...
Mounting POSIX Message Queue File System...
[ 9.831852] systemd[1]: Mounting Kernel Debug File System...
Mounting Kernel Debug File System...
[ 9.850776] systemd[1]: Kernel Trace File System was skipped because of an unmet condition check (ConditionPathExists=/sys/kernel/tracing).
[ 9.890744] systemd[1]: Mounting Temporary Directory /tmp...
Mounting Temporary Directory /tmp...
[ 9.915628] systemd[1]: Starting Create List of Static Device Nodes...
Starting Create List of Static Device Nodes...
[ 9.942982] systemd[1]: Starting Load Kernel Module configfs...
Starting Load Kernel Module configfs...
[ 9.966423] systemd[1]: Starting Load Kernel Module drm...
Starting Load Kernel Module drm...
[ 9.990559] systemd[1]: Starting Load Kernel Module fuse...
Starting Load Kernel Module fuse...
[ 10.046303] fuse: init (API version 7.37)
[ 10.048137] systemd[1]: Starting RPC Bind...
Starting RPC Bind...
[ 10.068295] systemd[1]: File System Check on Root Device was skipped because of an unmet condition check (ConditionPathIsReadWrite=!/).
[ 10.086529] systemd[1]: Starting Journal Service...
Starting Journal Service...
[ 10.147138] systemd[1]: Starting Load Kernel Modules...
Starting Load Kernel Modules...
[ 10.173264] systemd[1]: Starting Generate network units from Kernel command line...
Starting Generate network …ts from Kernel command line...
[ 10.220203] systemd[1]: Starting Remount Root and Kernel File Systems...
Starting Remount Root and Kernel File Systems...
[ 10.239760] systemd-journald[196]: Collecting audit messages is enabled.
[ 10.254349] systemd[1]: Starting Coldplug All udev Devices...
Starting Coldplug All udev Devices...
[ 10.273740] systemd[1]: Starting Setup Virtual Console...
Starting Setup Virtual Console...
[ 10.304388] systemd[1]: Started RPC Bind.
[ OK ] Started RPC Bind.
[ 10.333666] systemd[1]: Mounted Huge Pages File System.
[ OK ] Mounted Huge Pages File System.
[ 10.346510] systemd[1]: Mounted POSIX Message Queue File System.
[ OK ] Mounted POSIX Message Queue File System.
[ 10.373792] systemd[1]: Mounted Kernel Debug File System.
[ OK ] Mounted Kernel Debug File System.
[ 10.407875] systemd[1]: Started Journal Service.
[ OK ] Started Journal Service.
[ OK ] Mounted Temporary Directory /tmp.
[ OK ] Finished Create List of Static Device Nodes.
[ OK ] Finished Load Kernel Module configfs.
[ OK ] Finished Load Kernel Module drm.
[ OK ] Finished Load Kernel Module fuse.
[ OK ] Finished Load Kernel Modules.
[ OK ] Finished Generate network units from Kernel command line.
[ OK ] Finished Remount Root and Kernel File Systems.
[ OK ] Finished Setup Virtual Console.
Mounting FUSE Control File System...
Mounting Kernel Configuration File System...
Starting Flush Journal to Persistent Storage...
Starting Apply Kernel Variables...
Starting Create Static Device Nodes in /dev...
[ OK ] Mounted 10.807203] systemd-journald[196]: Received client request to flush runtime journal.
1;39mFUSE Control File System.
[ OK ] Mounted Kernel Configuration File System.
[ OK ] Finished Flush Journal to Persistent Storage.
[ OK ] Finished Apply Kernel Variables.
[ OK ] Finished Create Static Device Nodes in /dev.
[ OK ] Finished Coldplug All udev Devices.
[ OK ] Reached target Preparation for Local File Systems.
[ 11.100445] audit: type=1334 audit(1677836961.956:2): prog-id=5 op=LOAD
[ 11.107126] audit: type=1334 audit(1677836961.964:3): prog-id=6 op=LOAD
Starting Rule-based Manage…for Device Events and Files...
Mounting /var/volatile...
[ OK ] Mounted /var/volatile.
Starting Load/Save OS Random Seed...
[ OK ] Reached target Local File Systems.
Starting Create Volatile Files and Directories...
[ OK ] Finished Load/Save OS Random Seed.
[ OK ] Started Rule-based Manager for Device Events and Files.
Starting Start Psplash Boot Screen...
[ OK ] Started Start Psplash Boot Screen.
[ OK ] Started Start psplash-syst…progress communication helper.
[ 12.013884] mtdblock: MTD device 'spi0.0' is NAND, please consider using UBI block devices instead.
[ OK ] Finished Create Volatile Files and Directories.
Starting Network Time Synchronization...
Starting Record System Boot/Shutdown in UTMP...
[ OK ] Finished Record System Boot/Shutdown in UTMP.
[ 12.599801] systemd-journald[196]: Oldest entry in /run/log/journal/2cab78c5a4924c12b068e806c2fa7c0b/system.journal is older than the configured file retention duration (1month), suggesting rotation.
[ 12.648204] systemd-journald[196]: /run/log/journal/2cab78c5a4924c12b068e806c2fa7c0b/system.journal: Journal header limits reached or header out-of-date, rotating.
[ OK ] Started Network Time Synchronization.
[ OK ] Reached target System Initialization.
[ OK ] Started Daily Cleanup of Temporary Directories.
[ OK ] Reached target System Time Set.
[ OK ] Started Daily rotation of log files.
[ OK ] Reached target Timer Units.
[ OK ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
[ OK ] Listening on D-Bus System Message Bus Socket.
Starting sshd.socket...
Starting Weston socket...
[ OK ] Listening on sshd.socket.
[ OK ] Listening on Weston socket.
[ OK ] Reached target Socket Units.
[ OK ] Reached target Basic System.
[ OK ] Started Job spooling tools.
[ OK ] Started Periodic Command Scheduler.
Starting D-Bus System Message Bus...
[ OK ] Started Linux Firmware Loader Daemon.
Starting IPv6 Packet Filtering Framework...
Starting IPv4 Packet Filtering Framework...
Starting Telephony service...
[ OK ] Started Parsec Service.
[ OK ] Started Updates psplash to basic.
Starting LSB: Run /etc/rc.local if it exist...
[ OK ] Started System Logging Service.
[ 13.428185] audit: type=1334 audit(1706612628.332:4): prog-id=7 op=LOAD
[ 13.442554] audit: type=1334 audit(1706612628.344:5): prog-id=8 op=LOAD
Starting User Login Management...
Starting OpenSSH Key Generation...
Starting Rotate log files...
[ OK ] Finished IPv6 Packet Filtering Framework.
[ OK ] Finished IPv4 Packet Filtering Framework.
[ OK ] Started LSB: Run /etc/rc.local if it exist.
[ OK ] Finished OpenSSH Key Generation.
[ OK ] Reached target Preparation for Network.
Starting Network Configuration...
[ OK ] Started D-Bus System Message Bus.
Starting Connection service...
[ OK ] Started Telephony service.
[ OK ] Started User Login Management.
[ OK ] Finished Rotate log files.
[ OK ] Started Connection service.
Starting Avahi mDNS/DNS-SD Stack...
[ OK ] Started Network Configuration.
[ OK ] Reached target Network.
[ OK ] Started NFS status monitor for NFSv2/3 locking..
Starting Network Time Service...
[ OK ] Started Update psplash to network.
Starting Terminate Psplash Boot Screen...
Starting /etc/rc.local Compatibility...
Starting Wait for Network to be Configured...
Starting Permit User Sessions...
[ OK ] Finished Terminate Psplash Boot Scre[ 14.788597] mtdblock: MTD device 'spi0.0' is NAND, please consider using UBI block devices instead.
en.
[ OK ] Started /etc/rc.local Compatibility.
[ OK ] Started Avahi mDNS/DNS-SD Stack.
[ OK ] Finished Wait for Network to be Configured.
[ OK ] Finished Permit User Sessions.
[ 14.912114] mtdblock: MTD device 'spi0.0' is NAND, please consider using UBI block devices instead.
[ OK ] Reached target Network is Online.
[ OK ] Started Getty on tty1.
[ OK ] Started Serial Getty on ttyLP0.
[ OK ] Reached target Login Prompts.
[ 15.016578] audit: type=1334 audit(1706612629.920:6): prog-id=9 op=LOAD
[ 15.039142] audit: type=1334 audit(1706612629.944:7): prog-id=10 op=LOAD
Starting Hostname Service...
Starting LSB: starts tcsd...
Starting Weston, a Wayland…ositor, as a system service...
Starting WPA supplicant...
[ OK ] Started Network Time Service.
[ OK ] Started LSB: starts tcsd.
[ OK ] Reached target Multi-User System.
[ 15.414442] audit: type=1334 audit(1706612630.320:8): prog-id=11 op=LOAD
[ 15.429467] audit: type=1334 audit(1706612630.332:9): prog-id=12 op=LOAD
[ 15.451342] mtdblock: MTD device 'spi0.0' is NAND, please consider using UBI block devices instead.
Starting User Database Manager...
[ OK ] Started WPA supplicant.
[ OK ] Started Hostname Service.
[ 15.847610] mtdblock: MTD device 'spi0.0' is NAND, please consider using UBI block devices instead.
[ OK ] Started User Database Manager.
[ OK ] Created slice User Slice of UID 0.
Starting User Runtime Directory /run/user/0...
[ OK ] Reached target Hardware activated USB gadget.
[ 16.378097] fsl_mc_err_probe: No ECC DIMMs discovered
[ OK ] Finished User Runtime Directory /run/user/0.
Starting User Manager for UID 0...
[ 16.588828] audit: type=1006 audit(1706612631.492:10): pid=587 uid=0 old-auid=4294967295 auid=0 tty=(none) old-ses=4294967295 ses=1 res=1
[ 16.608073] audit: type=1300 audit(1706612631.492:10): arch=c00000b7 syscall=64 success=yes exit=1 a0=8 a1=fffff5b274c0 a2=1 a3=0 items=0 ppid=1 pid=587 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=1 comm="(systemd)" exe="/lib/systemd/systemd" key=(null)
[ 16.648431] audit: type=1327 audit(1706612631.492:10): proctitle="(systemd)"
[ 16.764265] audit: type=1334 audit(1706612631.668:11): prog-id=13 op=LOAD
[ 16.774326] audit: type=1300 audit(1706612631.668:11): arch=c00000b7 syscall=280 success=yes exit=8 a0=5 a1=ffffe6bfe658 a2=90 a3=0 items=0 ppid=1 pid=587 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=1 comm="systemd" exe="/lib/systemd/systemd" key=(null)
[ 16.824542] audit: type=1327 audit(1706612631.668:11): proctitle="(systemd)"
[ 16.838337] audit: type=1334 audit(1706612631.668:12): prog-id=13 op=UNLOAD
[ 16.850326] audit: type=1334 audit(1706612631.668:13): prog-id=14 op=LOAD
[ 16.868310] audit: type=1300 audit(1706612631.668:13): arch=c00000b7 syscall=280 success=yes exit=8 a0=5 a1=ffffe6bfe708 a2=90 a3=aaaae571e04a items=0 ppid=1 pid=587 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=1 comm="systemd" exe="/lib/systemd/systemd" key=(null)
[ 16.906307] audit: type=1327 audit(1706612631.668:13): proctitle="(systemd)"
[ OK ] Created slice Slice /system/systemd-fsck.
[ OK ] Found device /dev/mmcblk0p1.
[ OK ] Found device /dev/mmcblk0p2.
[ 17.466116] mtdblock: MTD device 'spi0.0' is NAND, please consider using UBI block devices instead.
Starting Save/Restore Sound Card State...
Starting File System Check on /dev/mmcblk0p1...
Starting File System Check on /dev/mmcblk0p2...
[ OK ] Finished Save/Restore Sound Card State.
[ OK ] Reached target Sound Card.
[ OK ] Started User Manager for UID 0.
[ OK ] Started Session c1 of User root.
[ OK ] Found device /dev/mmcblk1p2.
[ OK ] Finished File System Check on /dev/mmcblk0p1.
Mounting /run/media/BOOT-mmcblk0p1...
Starting File System Check on /dev/mmcblk1p2...
[ OK ] Mounted /run/media/BOOT-mmcblk0p1.
[ OK ] Found device /dev/mmcblk1p1.
Starting File System Check on /dev/mmcblk1p1...
[ OK ] Finished File System Check on /dev/mmcblk0p2.
Mounting /run/media/ROOTFS-mmcblk0p2...
[ 18.466447] EXT4-fs (mmcblk0p2): mounting ext3 file system using the ext4 subsystem
[ 18.518806] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Quota mode: none.
[ OK ] Mounted /run/media/ROOTFS-mmcblk0p2.
[ OK ] Finished File System Check on /dev/mmcblk1p1.
Mounting /run/media/boot-mmcblk1p1...
[ OK ] Found device SanDisk_3.2Gen1 CERTIFICATI.
Starting File System Check on /dev/sda1...
[ OK ] Mounted /run/media/boot-mmcblk1p1.
[ OK ] Started Weston, a Wayland …mpositor, as a system service.
[ OK ] Reached target Graphical Interface.
Starting Record Runlevel Change in UTMP...
[ OK ] Finished Record Runlevel Change in UTMP.
root: fsck 6.6% complete...
NXP i.MX Release Distro 6.1-mickledore desk-mx93 ttyLP0
[ 22.897993] EXT4-fs (mmcblk1p2): mounted filesystem with ordered data mode. Quota mode: none.
[ 26.507271] remoteproc remoteproc0: releasing imx-rproc
[ 26.512659] platform imx93-cm33: deferred probe pending
[ 45.894337] kauditd_printk_skb: 4 callbacks suppressed
[ 45.894348] audit: type=1334 audit(1706612660.800:16): prog-id=10 op=UNLOAD
[ 45.906506] audit: type=1334 audit(1706612660.800:17): prog-id=9 op=UNLOAD
root
root@desk-mx93:~#
root@desk-mx93:~# cat /etc/os-release
ID=fsl-imx-wayland
NAME="NXP i.MX Release Distro"
VERSION="6.1-mickledore (mickledore)"
VERSION_ID=6.1-mickledore
VERSION_CODENAME="mickledore"
PRETTY_NAME="NXP i.MX Release Distro 6.1-mickledore (mickledore)"
BUILD_VERSION="desk-mx9-l-5.0.0-rc2"
root@desk-mx93:~# cat /etc/buildinfo
-----------------------
Build Configuration: |
-----------------------
DISTRO = fsl-imx-wayland
DISTRO_VERSION = 6.1-mickledore
MACHINE = desk-mx93
IMAGE_BASENAME = desk-image-qt6
-----------------------
Layer Revisions: |
-----------------------
meta = HEAD:a57506c46d92bf0767060102d2139be06d46f575
meta-poky = HEAD:a57506c46d92bf0767060102d2139be06d46f575
meta-oe = HEAD:922f41b39f364e5b6be596b4b51e0fb37ffe1971
meta-multimedia = HEAD:922f41b39f364e5b6be596b4b51e0fb37ffe1971
meta-python = HEAD:922f41b39f364e5b6be596b4b51e0fb37ffe1971
meta-freescale = HEAD:7327e03c61823268a5a957fe090c4cc5e1735b34
meta-freescale-3rdparty = HEAD:bccd93f1ceece608e69799b6fc8f79e8a519f89e
meta-freescale-distro = HEAD:7956a0ab407a33c40fdc6eb4fabdcb7dc54fd359
meta-bsp = HEAD:c842613830da0a5473513cdbc2dce015b0ca9a5d
meta-sdk = HEAD:c842613830da0a5473513cdbc2dce015b0ca9a5d
meta-ml = HEAD:c842613830da0a5473513cdbc2dce015b0ca9a5d
meta-v2x = HEAD:c842613830da0a5473513cdbc2dce015b0ca9a5d
meta-nxp-demo-experience = HEAD:b8c0a9af3e3ca5400b9aff6436fbb654d3108cb4
meta-arm = HEAD:c6380674f59489b327c5047d803cc35b68642cd4
meta-arm-toolchain = HEAD:c6380674f59489b327c5047d803cc35b68642cd4
meta-chromium = HEAD:e232c2e21b96dc092d9af8bea4b3a528e7a46dd6
meta-clang = HEAD:af4dcba009ba98250315520f3003fde4ee164cce
meta-gnome = HEAD:922f41b39f364e5b6be596b4b51e0fb37ffe1971
meta-networking = HEAD:922f41b39f364e5b6be596b4b51e0fb37ffe1971
meta-filesystems = HEAD:922f41b39f364e5b6be596b4b51e0fb37ffe1971
meta-qt6 = HEAD:1406d0a85525a71fe5d7892d7f915404290a78ad
meta-parsec = HEAD:d7db0a3bd1a8639df7570483f003ce00cbe274a2
meta-tpm = HEAD:d7db0a3bd1a8639df7570483f003ce00cbe274a2
meta-virtualization = HEAD:38e6b3e2fe0219c773f4637a09221ca5d15bf6fc
meta-dave = HEAD:7ec931f7492f729281db6ec71a7492a4160f9931
meta-desk-mx = HEAD:659033ca1edf35389c685567b4523ee640049f74
root@desk-mx93:~#
The following message appears from the VM, when the rootfs is mounted:
dvdk@vagrant:~$ cat /var/log/syslog | tail -n 2 Jan 30 16:06:08 vagrant tftpd[2326386]: tftpd: serving file from /tftpboot Jan 30 16:06:15 vagrant rpc.mountd[862]: authenticated mount request from 192.168.0.89:720 for /home/dvdk/desk-mx-l/rfs/desk-mx9-l-5.0.0/mx9 (/home)
Kernel Module[edit | edit source]
The module are already present and loaded on RFS on MVM.
root@desk-mx93:~# ls -l /lib/modules/$(uname -r) total 1180 drwxr-xr-x 3 root root 4096 Mar 9 2018 extra drwxr-xr-x 11 root root 4096 Mar 9 2018 kernel -rw-r--r-- 1 root root 220476 Mar 9 2018 modules.alias -rw-r--r-- 1 root root 229732 Mar 9 2018 modules.alias.bin -rw-r--r-- 1 root root 37574 Mar 9 2018 modules.builtin -rw-r--r-- 1 root root 21202 Mar 9 2018 modules.builtin.alias.bin -rw-r--r-- 1 root root 40950 Mar 9 2018 modules.builtin.bin -rw-r--r-- 1 root root 239291 Mar 9 2018 modules.builtin.modinfo -rw-r--r-- 1 root root 52225 Mar 9 2018 modules.dep -rw-r--r-- 1 root root 91940 Mar 9 2018 modules.dep.bin -rw-r--r-- 1 root root 146 Mar 9 2018 modules.devname -rw-r--r-- 1 root root 33890 Mar 9 2018 modules.order -rw-r--r-- 1 root root 391 Mar 9 2018 modules.softdep -rw-r--r-- 1 root root 89290 Mar 9 2018 modules.symbols -rw-r--r-- 1 root root 114396 Mar 9 2018 modules.symbols.bin root@desk-mx93:~# lsmod Module Size Used by crct10dif_ce 16384 1 polyval_ce 16384 0 polyval_generic 16384 1 polyval_ce layerscape_edac_mod 16384 0 fuse 135168 1 root@desk-mx93:~#
Development[edit | edit source]
Synchronizing the repository[edit | edit source]
In DESK-MX9-L, the following source trees are clones of the correspondent DAVE Embedded Systems git repositories:
| Component | GIT Remote |
|---|---|
| U-Boot | git@git.dave.eu:dave/desk-mx-l/u-boot-imx.git
|
| Linux kernel | git@git.dave.eu:dave/desk-mx-l/linux-imx.git
|
| Yocto BSP | git@git.dave.eu:dave/desk-mx-l/desk-mx-l-bsp.git
|
For more information about the access to these repositories, please refer to this link.
Access to DAVE Embedded Systems' git repositories is granted to development kit's owners only. Please refer to this page for detailed instructions on how to get access.
Instructions[edit | edit source]
The components listed in the table above can be kept in sync and up to date with DAVE Embedded Systems' repositories.
Once the git account has been enabled, the developer can:
- clone the repository with the
git clone <git_remote_repository>command - synchronize a source tree entering the repository directory and launching the
git fetch origincommand.
Please note that git fetch doesn't merge the commits on the current branch. To do that, the developer should run the git merge command or replace the fetch-merge process with a single git pull command. Please note that the recommended method is the fetch-merge process. For further information on Git, please refer to the official Git Documentation
Building Linux[edit | edit source]
Quick reference[edit | edit source]
| Repository Information | |
|---|---|
| URL | git@git.dave.eu:desk-mx-l/linux-imx.git |
| stable branch | desk-mx9-l-5.x.x |
| stable tag | desk-mx9-l-5.0.0 |
| Build Information | ||
|---|---|---|
| defconfig | imx_v8_defconfig | |
| Kernel binary | Image | |
| Device trees | Platform | DTB |
| SBC | freescale/imx93-aura-cb2001.dtb | |
Instructions[edit | edit source]
It is assumed that the development environment has been set up properly as described here.
- start the Linux development VM and login into the system
- open a terminal window and cd into Linux kernel source code
dvdk@vagrant:~$ cd ~/desk-mx-l/linux dvdk@vagrant:~/desk-mx-l/linux$
- in case of needs you can update your local repository with the following git command
dvdk@vagrant:~/desk-mx-l/linux$ git pull
- configure the build environment
dvdk@vagrant:~/desk-mx-l/linux$ source ~/desk-mx-l/desk-mx9-l-5.0.0_env.sh
- enter the source tree directory and run the following commands:
dvdk@vagrant:~/desk-mx-l/linux$ make imx_v8_defconfig dvdk@vagrant:~/desk-mx-l/linux$ make Image modules freescale/imx93-aura-cb2001.dtb
NOTE: this is the default configuration suitable for latest target.
- The former command selects the default DESK-MX9-L configuration, while the latter builds the kernel binary image with the required u-boot header and the kernel device tree.
Default Linux kernel configuration can be changed by using the standard menuconfig, xconfig, or gconfig make target. Subsequent builds just require uImage make target to update the binary image. Once the build process is complete, the kernel binary image is stored into the arch/arm/boot/Image file. Both this file and the kernel device tree can be copied to the tftp root directory /tftpboot/desk-mx9-l/ with the following commands:
dvdk@vagrant:~/desk-mx-l/linux$ cp arch/arm64/boot/Image /tftpboot/desk-mx9-l/ dvdk@vagrant:~/desk-mx-l/linux$ cp arch/arm64/boot/dts/freescale/*.dtb /tftpboot/desk-mx9-l/
Usually, kernel modules are installed with make modules_install command, but this method installs the modules into the /lib/modules directory of your MVM, which is not what you want.
A better way to deploy kernel modules while cross-compiling is
- generate a
.tar.gzarchive - install this archive into the target root file system
User can create such an archive, for example, using the following commands:
dvdk@vagrant:~/desk-mx-l/linux$ mkdir modules-install dvdk@vagrant:~/desk-mx-l/linux$ make INSTALL_MOD_PATH=modules-install modules_install dvdk@vagrant:~/desk-mx-l/linux$ cd modules-install dvdk@vagrant:~/desk-mx-l/linux/modules-install$ tar cvzf ../modules.tar.gz . && cd .. dvdk@vagrant:~/desk-mx-l/linux$
Now copy modules.tar.gz into the target root file system and install them as root with the following command
root@desk-mx93:~# tar xvzf modules.tar.gz -C /
Building the Yocto BSP[edit | edit source]
Quick reference[edit | edit source]
| Repository Information | ||
|---|---|---|
| Repository | BSP Manifest | Yocto BSP Layer |
| URL | git@git.dave.eu:desk-mx-l/desk-mx-l-bsp.git | git@git.dave.eu:desk-mx-l/meta-desk-mx.git |
| stable branch | desk-mx9-l-5.x.x | desk-mx9-l-5.x.x |
| stable tag | desk-mx9-l-5.0.0 | desk-mx9-l-5.0.0 |
| Build targets | |
|---|---|
| Name | Description |
| dave-image-devel | This image include tools for development/debugging |
| desk-image-qt6 | This image include a Qt6 graphic backend on Wayland compositor |
Introduction[edit | edit source]
As known, in addition to a bootloader and the o.s. kernel, an embedded Linux system needs a root file system to operate. The root file system must contain everything needed to support the Linux system (applications, settings, data, etc.). The root file system is the file system that is contained on the same partition on which the root directory is located. The Linux kernel, at the end of its startup stage, mounts the root file system on the configured root device and finally launches the /sbin/init, the first user space process and "father" of all the other processes.
For more information on the Linux filesystem, please refer to http://www.thegeekstuff.com/2010/09/linux-file-system-structure/.
DESK-MX9-L provides one (or more) pre-built root file system, that can be used during the evaluation/development/deployment cycle. For instance, the root file system included in the desk-image-devel image is suited for the development phase, since it provides a relatively rich set of packages including tools and libraries used to debug the application code. The pre-built root file systems are located here: /home/dvdk/<target_name>/rfs/<kit_name>.
Besides the pre-built root file systems, DAVE also provides a rich repository containing pre-built applications and libraries. These packages can be easily installed on the target by using the apt-get tool. Please refer to this application note for more details.
To generate the supported root file systems, the build of the Yocto BSP has to be run. The output of this process is an image containing the U-Boot binary file, the Linux kernel image, and the selected root file system image. The following sections describe in detail how to execute this operation.
For more general information regarding the Yocto build system, please refer the dedicated category page.
How to build the Yocto BSP images including the U-Boot binary file, the Linux kernel image, and the target root file system image[edit | edit source]
|
The following procedure requires the access to the DAVE Embedded Systems' git repositories. The access to such repositories is granted to development kit's owners only. Please refer to this page for detailed instructions on how to get it. |
|
This process requires a lot of hardware resources in terms of disk storage, RAM, and processing power. For this reason, it also is recommended to consider the use of a physical machine. For more details on this topic, please refer to the NXP documentation on this BSP, i.e. the i.MX Yocto Project User's Guide, which talks about the host setup for the Yocto build system. |
Initialize the build environment[edit | edit source]
Before running the build, the environment must be initialized properly.
DESK-MX9-L Yocto BSP uses git-repo tool to fetch all the required git repositories. To install it, please use the following commands:
dvdk@vagrant:~$ mkdir -p ~/desk-mx-l/yocto dvdk@vagrant:~$ cd ~/desk-mx-l/yocto dvdk@vagrant:~/desk-mx-l/yocto$ curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > repo dvdk@vagrant:~/desk-mx-l/yocto$ chmod a+x repo
then, fetch the Yocto repositories with the proper branch:
dvdk@vagrant:~/desk-mx-l/yocto$ python3 ./repo init -u git@git.dave.eu:desk-mx-l/desk-mx-l-bsp.git -b refs/tags/desk-mx9-l-5.0.0 dvdk@vagrant:~/desk-mx-l/yocto$ python3 ./repo sync
Initialize DISTRO and MACHINE[edit | edit source]
Select the Weston backend (you will be asked to accept the EULA):
dvdk@vagrant:~/desk-mx-l/yocto$ DISTRO=fsl-imx-wayland MACHINE=desk-mx93 source desk-setup-release.sh -b build-wayland
...
Do you accept the EULA you just read? (y/n) y
EULA has been accepted.
Welcome to Freescale Community BSP
...
dvdk@vagrant:~/desk-mx-l/yocto/build-wayland$
Running the build[edit | edit source]
Please note that even the basic root file system requires a few hours to build on a mid/hi range desktop (4-6 cores, 8-12 GiB RAM) also depending on your Internet connection speed (all sources are fetched from the network). Nearly 50GiB of disk space is required for the build. The process may be slowed down significantly since the performances of a virtual machine are reduced if compared to the physical hardware. Thus, it's recommended to check the hardware capabilities of the host system and, when building with Yocto is required, to consider the following options:
- Migrating the build system to a physical machine
- Assuming that the host system has the required resources, extending the hardware capabilities of the default MVM (e.g. adding more cores and disk space).
Once completed the initialization phase, developers can launch the Yocto image build process with the following commands:
dvdk@vagrant:~/desk-mx-l/yocto/build$ bitbake <target-image-name>
Where <target-image-name> is one of the images listed in here.
Once the build process is completed, the resulting files (the U-Boot binaries, the Linux kernel image, the device tree blob, the .tar.gz compressed root file system image, etc.) will be available in build/tmp/deploy/images/desk-mx39.
Generating the SDKs[edit | edit source]
After creating an image as described in the previous version, the corresponding SDK can be generated by issuing the following command:
bitbake <target-image-name> -c populate-sdk
Again, replace <target-image-name> with one of the images listed in here.
Generating the Toolchain[edit | edit source]
Toolchain can be created by the following command:
bitbake meta-toolchain
Building additional packages[edit | edit source]
To build additional packages the user must select the DISTRO and source the desk-setup-release.sh script
dvdk@vagrant:~/desk-mx-l/yocto$ DISTRO=fsl-imx-wayland MACHINE=desk-mx93 source desk-setup-release.sh -b build-wayland dvdk@vagrant:~/desk-mx-l/yocto/build-wayland$
And then can run any of the bitbake command.
dvdk@vagrant:~/desk-mx-l/yocto/build$ bitbake memtester
The resulting packages (the default format is deb) can be found inside tmp/deploy/rpm/images/desk-mx93-l-5.0.0.
dvdk@vagrant:~/yocto/build-wayland$ ls -l tmp/deploy/deb/armv8a/memtester* -rw-r--r-- 2 dvdk dvdk 7548 Jan 28 13:54 tmp/deploy/deb/armv8a/memtester_4.6.0-r0_arm64.deb -rw-r--r-- 2 dvdk dvdk 21956 Jan 28 13:54 tmp/deploy/deb/armv8a/memtester-dbg_4.6.0-r0_arm64.deb -rw-r--r-- 2 dvdk dvdk 876 Jan 28 13:54 tmp/deploy/deb/armv8a/memtester-dev_4.6.0-r0_arm64.deb -rw-r--r-- 2 dvdk dvdk 3072 Jan 28 13:54 tmp/deploy/deb/armv8a/memtester-doc_4.6.0-r0_arm64.deb -rw-r--r-- 2 dvdk dvdk 6672 Jan 28 13:54 tmp/deploy/deb/armv8a/memtester-src_4.6.0-r0_arm64.deb
How to create a bootable SD card[edit | edit source]
This article shows how to (re)create the bootable SD card, from the binary images produced by the DESK-MX-L Yocto build, using a standard SD image flasher like balenaEtcher
The process is relatively straightforward: it consists of writing the WIC file of interest generated by Yocto onto the SD card. The following instruction explains how to use balenaEtcher on a Windows host. The procedure is similar when working with a Linux host.
- download the desired binary image to flash (
*.wicor*.wic.bz2) from the mirror binary server selecting the proper DESK-MX9-L release- among the binaries made available in the mirror there are several
*.wic.bz2files for the available releases. In particular, there is thedave-image-devel-desk-mx9.wic.bz2(for AURA) file. This image is the one used to program the microSD card delivered along with the evaluation kit.
- among the binaries made available in the mirror there are several
- connect the microSD card to the PC Host
- open balenaEtcher tool
- once the tool is open:
- select the binary to flash by clicking on
Flash from file - select the microSD to flash by clicking on
Select target - flash the uSD by clicking o
Flash
- select the binary to flash by clicking on
SD card structure[edit | edit source]
The created SD card has the following structure:
- raw sectors for the bootloader storage: typically this is an 8MB raw part that stores the bootloader binaries (like
imx9_flash.bin) for the bootrom startup FAT32first partition: this will be mapped to the/dev/mmcblk1p1device in Linux- usually this partition contains the Linux kernel binary and the device tree blob
- splash screen image is stored in this partition too for a splash image showing during U-Boot startup
ext4second partition: this will be mapped to the/dev/mmcblk1p2device in Linux- this partition contains the Linux root file system
Creating the SD card from binary artifacts[edit | edit source]
Even if the overall binary artifacts have been created by the Yocto build, it is highly discouraged to manually create the SD card starting from them.
The Yocto build takes care of the overall binary consistency (like kernel modules and so on) avoiding mismatching different versions.
Moreover, the SD card is intended to be used during the development process and not for the production phase (where other deployment specifications and details have to be taken into account).
Hello word example[edit | edit source]
Here below is an example on C code displaying the classic Hello World! message on the target serial console.
This example shows how to use the arm cross-compiler using the environment configured for this purpose.
Setting the cross-compiler[edit | edit source]
- start the Linux development VM and login into the system
- open a terminal window and cd into your source code directory
dvdk@vagrant:~$ mkdir myproject
dvdk@vagrant:~$ cd myproject/
dvdk@vagrant:~/myproject$ vi hello.c
dvdk@vagrant:~/myproject$ cat hello.c
#include <stdio.h>
int main(){
printf("Hello, World!\n");
return 0;
}
- configure the build environment
dvdk@vagrant:~/myproject$ source /home/dvdk/desk-mx-l/desk-mx9-l-5.0.0_env.sh
- as you can see here below, the
$CCenvironment variable has been properly configured for using the SDKsysrootparameter:
dvdk@vagrant:~/myproject$ echo $CC aarch64-poky-linux-gcc -march=armv8-a+crc+crypto -mbranch-protection=standard -fstack-protector-strong -O2 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security --sysroot=/opt/yocto/sdk/desk-mx9-l/desk-mx9-l-5.0.0/sysroots/armv8a-poky-linux dvdk@vagrant:~/myproject$
- invoke the cross-compiler for compiling your source code example: the object file obtained, is a proper ELF 64-bit for the target microprocessor
dvdk@vagrant:~/myproject$ $CC hello.c -o hello dvdk@vagrant:~/myproject$ file hello hello: ELF 64-bit LSB shared object, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-aarch64.so.1, BuildID[sha1]=c64beb8181cc5a2fe6290f8b61b217a25041b429, for GNU/Linux 3.14.0, with debug_info, not stripped dvdk@vagrant:~/myproject$
Running the example on the target[edit | edit source]
Now it is enough to copy the object file in the /home/root rfs directory and boot from nfs:
dvdk@vagrant:~/myproject$ sudo cp hello /home/dvdk/desk-mx-l/rfs/desk-mx9-l/home/root/ dvdk@vagrant:~/myproject$ sudo ls -la /home/dvdk/desk-mx-l/rfs/desk-mx9-l/home/root/ total 32 drwx------ 3 root root 4096 Jan 31 10:46 . drwxr-xr-x 4 root root 4096 Mar 9 2018 .. -rwxr-xr-x 1 root root 75624 Jan 31 10:46 hello -rw-r--r-- 1 root root 1011 Mar 9 2018 .profile dvdk@vagrant:~/myproject$
on the target:
...
[ OK ] Mounted /run/media/root-mmcblk1p2.
[ OK ] Started Weston, a Wayland …mpositor, as a system service.
[ OK ] Reached target Graphical Interface.
Starting Record Runlevel Change in UTMP...
[ OK ] Finished Record Runlevel Change in UTMP.
NXP i.MX Release Distro 6.1-mickledore desk-mx93 ttyLP0
desk-mx93 login: root
root@desk-mx93:~# ls -la
total 32
drwx------ 3 root root 4096 Jan 31 2024 .
drwxr-xr-x 4 root root 4096 Mar 9 2018 ..
-rw-r--r-- 1 root root 1011 Mar 9 2018 .profile
-rwxr-xr-x 1 root root 75624 Jan 31 2024 hello
root@desk-mx93:~# ./hello
Hello, World!
root@desk-mx93:~#
DESK-MX9-L/Development/Package management with DNF
Deployment[edit | edit source]
Boot from different storage devices[edit | edit source]
AURA SOM is designed to support different bootable storage devices.
The i.MX93 SoC supports different boot modes. DAVE Embedded Systems SOM designs simplify and provide the following boot mode options, see AURA boot modes
The usage of NOR flash memories, NAND devices and eMMC or SD devices can be chosen with regard to the reliability. This is especially true when the NAND flash is used as the boot device. Several techniques such as wear leveling and bad block management have to be implemented to achieve an acceptable reliability.
Please check the AURA P/N composition page for the storage devices available on the SOMs or contact our technical support for more information.
Storage devices support[edit | edit source]
DESK-MX9-L-5.0.0 supports boot from uSD device only.
How to configure the network interfaces[edit | edit source]
For deploying an Embedded System, one of the most important configuration is the Network Interface configuration.
Once the Embedded Device is finally configured for stand-alone bootstrap, the network interface should be configured for reaching the device remotely via network connections like ssh, telnet, ftp, http, etc.
This Application Note briefly describes how it is possible to simply configure the network interfaces on systemd
Resources[edit | edit source]
For further details on network configuration, please refer - for example - to:
Examples[edit | edit source]
The following configuration assumptions are used in the paragraphs shown below:
- IP address range of the LAN network 192.168.0.0 - 192.168.0.255
- IP address of the gateway 192.168.0.254
- IP address of the device 192.168.0.144
systemd[edit | edit source]
The network configuration for systemd are basically found in the /etc/systemd/network/ directory.
The most simply way for configuring the network interface is to create/edit the file /etc/systemd/network/1-eth0.network as per the following paragraphs. For more example and usage hints on systemd, please refer to our wiki page.
Static IP address[edit | edit source]
SBCX AURA has one network interfaces, below is shown how to configureit through a static IP.
Example:
[Match] Name=eth0 # Prevent the interface loading if the kernel boots from nfs KernelCommandLine=!nfsroot [Network] Address=192.168.0.89 Gateway=192.168.0.254 DNS=192.168.0.1
Once modified, the networkd service should be resarted:
systemctl restart systemd-networkd
Dynamic IP addres (DHCP)[edit | edit source]
[Match] Name=eth0 # Prevent the interface loading if the kernel boots from nfs KernelCommandLine=!nfsroot [Network] DHCP=yes
When systemd network starts, it tries to use a DHCP server present in the network to configure the interface.
DNS[edit | edit source]
The DNS key (in the configuration file) is used only if the systemd-resolved service is enabled and the /etc/resolv.conf has a symbolic link to /run/systemd/resolve/stub-resolv.conf
ln -sf /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf
Once modified, the resolved service should be resarted:
systemctl restart systemd-resolved
loopback network interface[edit | edit source]
systemd contains native implementations of various tasks that need to be executed as part of the boot process.
For example, it sets the hostname or configures the loopback network device.
Apply configuration changes[edit | edit source]
After editing the above files, changes are applied after reboot or by restarting systemd-networkd.service:
root@desk-mx93:~# systemctl restart systemd-networkd.service
MAC Address programming[edit | edit source]
Every network adapter has a Media Access Control address (usually shortened to MAC address). A MAC address is a six-byte identifying number permanently embedded in the firmware of the adapter, and is readable by the network and the operating system of the device on which the adapter is installed.
The address must follow the standards set by the Institute of Electrical and Electronics Engineers (IEEE), which sets computer networking standards.
The MAC address is a six-pair set of hexadecimal numbers, for example a1-c2-e3-44-5f-6d. Specifically, in Ethernet, the MAC address is known as the Ethernet Address, which is the unique ID serial number of the Ethernet device in one's computer. MAC Addresses are used in a Local Area Network (LAN) by computers to communicate with each other. Every adapter has a unique MAC address.
Platform supported[edit | edit source]
In this Application Note, we will describe how to use the i.MX93x eFuse for programming and using the MAC address(es).
|
This Application Note has been validated in the AURA SOM. The commands used have been not validated in the other platform yet. |
Obtaining a MAC address[edit | edit source]
To obtain a MAC address for your organization, please refer to our Setting the MAC address wiki page with the overall information about this topic.
Permanent storage areas[edit | edit source]
Some SOCs provide programmable OTPs for security, MAC addresses, boot modes, etc. Usually, some of these are general-purpose registers and can be managed by the user.
In other cases, an external permanent storage device can be used for storing permanent settings like the MAC address: for the i.MX93x product family, DAVE proposes to use the General Purposes eFuses (OTP blocks) on SoC itself for storing permanently the MAC address(es).
MAC address programming on i.MX93x family[edit | edit source]
MAC address configuration in u-boot[edit | edit source]
If the MAC address is not already programmed in the OTPs and the ethaddr u-boot variable is not set, u-boot assignes a random value (different at every power on cycle):
Net: Warning: ethernet@428a0000 (eth1) using random MAC address - 56:ea:aa:42:d2:0e eth1: ethernet@428a0000 [PRIME]
If the ethaddr is set and saved in the u-boot environment, its value is used as the MAC Address:
u-boot=> setenv ethaddr 00:50:c2:1e:af:a8 u-boot=> saveenv Saving Environment to MMC... Writing to MMC(1)... OK u-boot=>
eFuse bank registers[edit | edit source]
i.MX93x family uses the Bank39 Word3, Word4, and Word5 (if the SoC has two ethernet interfaces) for storing the MAC addresses. The MAC values should be properly divided into the three registers for correct programming.
|
Warning!! eFuse programming is a permanent and non-reversible action. Pay attention to the values and commands used during MAC programming. |
eth0 eFuse programming[edit | edit source]
U-Boot uses the fuse prog command for writing the MAC address into the eFuse. The MAC address should be divided into high 16 bits and low 32 bits. For example MAC address AB:CD:12:34:56:78 for eth0 is then divided into:
fuse prog -y 39 3 0x12345678 fuse prog -y 39 4 0xABCD
In the following example the MAC address 00:50:c2:1e:af:a8 is stored in the SOC:
- (in case of presence) clear the
ethaddru-boot variable
u-boot=> setenv ethaddr u-boot=> saveenv Saving Environment to MMC... Writing to MMC(1)... OK
- program the MAC address in the OPTs with the following commands:
u-boot=> fuse prog 39 3 c21eafa8
Programming bank 9 word 0x00000000 to 0xc21eafa8...
Warning: Programming fuses is an irreversible operation!
This may brick your system.
Use this command only if you are sure of what you are doing!
Really perform this fuse programming? <y/N>
y
u-boot=> fuse prog 39 4 0050
Programming bank 9 word 0x00000001 to 0x00000050...
Warning: Programming fuses is an irreversible operation!
This may brick your system.
Use this command only if you are sure of what you are doing!
Really perform this fuse programming? <y/N>
y
u-boot=>
If you want to write the eFuse value directly without confirmation, uses the -y parameter with the fuse prog command, as per the previous example:
u-boot=> fuse prog -y 39 3 c21eafa8 u-boot=> fuse prog -y 39 4 0050
At the next boot, the ethaddr value wil be read from the OPTs:
Warning: ethernet@428a0000 using MAC address from ROM eth0: ethernet@428a0000 Fastboot: Normal Normal Boot Hit any key to stop autoboot: 0 u-boot=> print ethaddr ethaddr=00:50:c2:1e:af:a8 u-boot=>
The warning message informs that the ethaddr is not present in the u-boot environment and it has been set using the value read from the OTPs. For clearing the warning, it is enough to save the environment with saveenv.
u-boot=> saveenv
eFuse locking[edit | edit source]
The OTP eFuse registers should be locked to avoid unwanted registers (and then MAC addresses) modifications. OTP lock grants that the MAC values cannot be modified anymore.
|
If not locked yet, OTP bits can be set to '1' but not reversed to '0' value, so some modifications can be applied if the eFuse registers are not locked. |
eFuse reading[edit | edit source]
The eFuse registers can be read - after programming - for checking the written values:
u-boot=> fuse read 39 3 Reading bank 39: Word 0x00000003: c21eafa8 u-boot=> fuse read 39 4 Reading bank 39: Word 0x00000004: 00000050 u-boot=> fuse read 39 5 Reading bank 39: Word 0x00000005: 0050c21e u-boot=>
Linux kernel MAC address[edit | edit source]
The MAC Address configured in u-boot is passed to the kernel which configures the eth0 and eth1 peripherals with the correct values:
root@desk-mx93:~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:50:c2:1e:af:a8
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:82 errors:0 dropped:0 overruns:0 frame:0
TX packets:82 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6220 (6.0 KiB) TX bytes:6220 (6.0 KiB)
root@desk-mx93:~#
Peripherals[edit | edit source]
Peripheral CAN[edit | edit source]
Device tree configuration[edit | edit source]
Here below is an example of device tree configuration used on standard DAVE's kit for the AURA SOM:
From imx93-aura.dtsi:
...
&flexcan2 {
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_flexcan2>;
status = "okay";
};
...
&iomuxc {
...
pinctrl_flexcan2: flexcan2grp {
fsl,pins = <
MX93_PAD_GPIO_IO25__CAN2_TX 0x139e
MX93_PAD_GPIO_IO27__CAN2_RX 0x139e
>;
};
...
};
Accessing the peripheral[edit | edit source]
Linux messages at boot time[edit | edit source]
... [ 1.527184] can: controller area network core [ 1.536411] can: raw protocol [ 1.539420] can: broadcast manager protocol [ 1.543646] can: netlink gateway - max_hops=1 ...
Enable the interface and check status[edit | edit source]
root@desk-mx93:~# ip link set can0 type can bitrate 500000
root@desk-mx93:~# ifconfig can0 up
[ 487.839975] IPv6: ADDRCONF(NETDEV_CHANGE): can0: link becomes ready
root@desk-mx93:~# ifconfig can0
can0: flags=193<UP,RUNNING,NOARP> mtu 16
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 10 (UNSPEC)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 24
root@desk-mx93:~#
Usage with can-utils[edit | edit source]
root@desk-mx93:~# ip link set can0 type can bitrate 500000 triple-sampling on loopback on RTNETLINK answers: Device or resource busy root@desk-mx93:~# ifconfig can0 up root@desk-mx93:~# candump can0 & [2] 734 interface = can0, family = 29, type = 3, proto = 1 root@desk-mx93:~# cansend can0 -i 0x255 0x0f 0x1e 0x2d 0x3c 0x4b 0x5a 0x69 0x78 interface = can0, family = 29, type = 3, proto = 1 <0x255> [8] 0f 1e 2d 3c 4b 5a 69 78 <0x000> [8] f0 e1 d2 c3 b4 a5 96 87
Additional information[edit | edit source]
Each CAN port appears like a networking interface in the form canX where X is the port number.
Information about programming the CAN socket interface is given in the kernel tree under Documentation/networking/can.rst
Peripheral Ethernet[edit | edit source]
The ethernet interface is made available through the i.MX93 eqos interface which should be initialized on the device tree.
Device tree configuration[edit | edit source]
Here below is an example of device tree configuration used on standard DAVE's kit for the AURA SOM:
From imx93-aura.dtsi :
&eqos {
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_eqos>;
phy-mode = "rgmii-id";
phy-handle = <ðphy1>;
status = "okay";
mdio {
compatible = "snps,dwmac-mdio";
#address-cells = <1>;
#size-cells = <0>;
clock-frequency = <5000000>;
ethphy1: ethernet-phy@7 {
compatible = "ethernet-phy-ieee802.3-c22";
reg = <7>;
eee-broken-1000t;
};
};
};
...
...
&iomuxc {
...
pinctrl_eqos: eqosgrp {
fsl,pins = <
MX93_PAD_ENET1_MDC__ENET_QOS_MDC 0x57e
MX93_PAD_ENET1_MDIO__ENET_QOS_MDIO 0x57e
MX93_PAD_ENET1_RD0__ENET_QOS_RGMII_RD0 0x57e
MX93_PAD_ENET1_RD1__ENET_QOS_RGMII_RD1 0x57e
MX93_PAD_ENET1_RD2__ENET_QOS_RGMII_RD2 0x57e
MX93_PAD_ENET1_RD3__ENET_QOS_RGMII_RD3 0x57e
MX93_PAD_ENET1_RXC__CCM_ENET_QOS_CLOCK_GENERATE_RX_CLK 0x5fe
MX93_PAD_ENET1_RX_CTL__ENET_QOS_RGMII_RX_CTL 0x57e
MX93_PAD_ENET1_TD0__ENET_QOS_RGMII_TD0 0x57e
MX93_PAD_ENET1_TD1__ENET_QOS_RGMII_TD1 0x57e
MX93_PAD_ENET1_TD2__ENET_QOS_RGMII_TD2 0x57e
MX93_PAD_ENET1_TD3__ENET_QOS_RGMII_TD3 0x57e
MX93_PAD_ENET1_TXC__CCM_ENET_QOS_CLOCK_GENERATE_TX_CLK 0x5fe
MX93_PAD_ENET1_TX_CTL__ENET_QOS_RGMII_TX_CTL 0x57e
>;
};
...
};
...
Accessing the peripheral[edit | edit source]
AURA SOM provides the network interface mapped as eth0.
Linux messages at boot time[edit | edit source]
[ 8.031281] imx-dwmac 428a0000.ethernet eth0: Register MEM_TYPE_PAGE_POOL RxQ-0 [ 8.105959] imx-dwmac 428a0000.ethernet eth0: PHY [stmmac-1:07] driver [Microchip LAN8841 Gigabit PHY] (irq=POLL) [ 8.114909] imx-dwmac 428a0000.ethernet eth0: No Safety Features support found [ 8.114940] imx-dwmac 428a0000.ethernet eth0: IEEE 1588-2008 Advanced Timestamp supported [ 8.115479] imx-dwmac 428a0000.ethernet eth0: registered PTP clock [ 8.144953] imx-dwmac 428a0000.ethernet eth0: FPE workqueue start [ 8.144975] imx-dwmac 428a0000.ethernet eth0: configuring for phy/rgmii-id link mode [ 8.145479] 8021q: adding VLAN 0 to HW filter on device eth0
Cable connection:
... [ 79.845148] imx-dwmac 428a0000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx [ 79.853449] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready ...
Check the interface with ifconfig[edit | edit source]
root@desk-mx93:~# ifconfig eth0
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.89 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 fe80::140a:71ff:fe2d:ce0e prefixlen 64 scopeid 0x20<link>
ether 16:0a:71:2d:ce:0e txqueuelen 1000 (Ethernet)
RX packets 1224 bytes 91175 (89.0 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 120 bytes 20793 (20.3 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 101
Test with iperf3[edit | edit source]
root@desk-mx93:~# iperf3 -t 5 -c 192.168.0.168 Connecting to host 192.168.0.168, port 5201 [ 5] local 192.168.0.89 port 42688 connected to 192.168.0.168 port 5201 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 109 MBytes 915 Mbits/sec 4 481 KBytes [ 5] 1.00-2.00 sec 109 MBytes 912 Mbits/sec 0 549 KBytes [ 5] 2.00-3.00 sec 110 MBytes 923 Mbits/sec 0 608 KBytes [ 5] 3.00-4.00 sec 111 MBytes 933 Mbits/sec 0 643 KBytes [ 5] 4.00-5.00 sec 110 MBytes 923 Mbits/sec 0 660 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 549 MBytes 921 Mbits/sec 4 sender [ 5] 0.00-5.04 sec 546 MBytes 908 Mbits/sec iperf Done. root@desk-mx93:~#
MAC Address[edit | edit source]
For the MAC Address programming, refers to the following wiki page
Peripheral LVDS[edit | edit source]
Device tree configuration[edit | edit source]
Here below an example of device tree modification on standard DAVE's kit for the AURA SOM:
...
/ {
...
regulators {
...
reg_lvds_en: regulator_lcd_3V3_en {
compatible = "regulator-fixed";
regulator-name = "lvds_enable";
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_lcd_3v3_enable>;
gpio = <&gpio1 10 GPIO_ACTIVE_HIGH>;
enable-active-high;
};
...
};
...
lvds_panel {
compatible = "panel-lvds";
power-supply = <®_lvds_en>;
width-mm = <154>;
height-mm = <87>;
label = "am800480btmqw-tg0h-c";
data-mapping = "vesa-24";
status = "okay";
panel-timing {
clock-frequency = <35000000>;
hactive = <800>;
vactive = <480>;
hback-porch = <88>;
hfront-porch = <40>;
vback-porch = <32>;
vfront-porch = <13>;
hsync-len = <48>;
vsync-len = <3>;
hsync-active = <0>;
vsync-active = <0>;
de-active = <1>;
};
port {
panel_lvds_in: endpoint {
remote-endpoint = <&lvds_out>;
};
};
};
...
};
...
&lcdif {
status = "okay";
assigned-clock-rates = <498000000>, <71142857>, <400000000>, <133333333>;
};
&ldb {
status = "okay";
lvds-channel@0 {
status = "okay";
port@1 {
reg = <1>;
lvds_out: endpoint {
remote-endpoint = <&panel_lvds_in>;
};
};
};
};
&ldb_phy {
status = "okay";
};
...
&iomuxc {
...
pinctrl_lcd_3v3_enable: lcd_3v3_en {
fsl,pins = <
MX93_PAD_PDM_BIT_STREAM1__GPIO1_IO10 0x31e
>;
};
...
};
Accessing the peripheral[edit | edit source]
Linux messages at boot time[edit | edit source]
... [ 0.917991] imx-drm display-subsystem: bound imx-lcdifv3-crtc.0 (ops lcdifv3_crtc_ops) [ 1.714036] imx-drm display-subsystem: bound imx-lcdifv3-crtc.0 (ops lcdifv3_crtc_ops) [ 1.927160] imx-drm display-subsystem: bound imx-lcdifv3-crtc.0 (ops lcdifv3_crtc_ops) [ 1.935332] imx-drm display-subsystem: bound soc@0:ldb@4ac10020 (ops imx93_ldb_ops) [ 1.943254] [drm] Initialized imx-drm 1.0.0 20120507 for display-subsystem on minor 0 [ 2.003273] imx-drm display-subsystem: [drm] fb0: imx-drmdrmfb frame buffer device [ 4.634721] systemd[1]: Starting Load Kernel Module drm... ...
DRM access[edit | edit source]
DRM framework can be accessed using the modetest DRM utility.
root@desk-mx93:~# modetest -M imx-drm
Encoders:
id crtc type possible crtcs possible clones
34 33 LVDS 0x00000001 0x00000001
Connectors:
id encoder status name size (mm) modes encoders
35 34 connected LVDS-1 154x87 1 34
modes:
index name refresh (Hz) hdisp hss hse htot vdisp vss vse vtot
#0 800x480 67.92 800 840 888 976 480 493 496 528 35000 flags: nhsync, nvsync; type: preferred, driver
props:
1 EDID:
flags: immutable blob
blobs:
value:
2 DPMS:
flags: enum
enums: On=0 Standby=1 Suspend=2 Off=3
value: 0
5 link-status:
flags: enum
enums: Good=0 Bad=1
value: 0
6 non-desktop:
flags: immutable range
values: 0 1
value: 0
4 TILE:
flags: immutable blob
blobs:
value:
CRTCs:
id fb pos size
33 39 (0,0) (800x480)
#0 800x480 67.92 800 840 888 976 480 493 496 528 35000 flags: nhsync, nvsync; type: preferred, driver
props:
24 VRR_ENABLED:
flags: range
values: 0 1
value: 0
Planes:
id crtc fb CRTC x,y x,y gamma size possible crtcs
31 33 39 0,0 0,0 0 0x00000001
formats: XR24 AR24 RG16 XB24 AB24 AR15 XR15
props:
8 type:
flags: immutable enum
enums: Overlay=0 Primary=1 Cursor=2
value: 1
32 zpos:
flags: immutable range
values: 0 0
value: 0
Frame buffers:
id size pitch
root@desk-mx93:~#
Additional information[edit | edit source]
For some information on DRM/KMS framework, see the DRM-KMS kernel documentation.
Peripheral MIPI[edit | edit source]
Device tree configuration[edit | edit source]
Here below is an example of device tree configuration used on standard DAVE's kit for the AURA SOM:
From imx93-aura-cb2001.dts:
...
/ {
...
regulators {
...
ov5640_reg_2v8: ov5640_reg_2v8 {
compatible = "regulator-fixed";
regulator-name = "ov5640_reg_2v8";
regulator-min-microvolt = <2800000>;
regulator-max-microvolt = <2800000>;
regulator-always-on;
};
ov5640_reg_1v8: ov5640_reg_1v8 {
compatible = "regulator-fixed";
regulator-name = "ov5640_reg_1v8";
regulator-min-microvolt = <1800000>;
regulator-max-microvolt = <1800000>;
regulator-always-on;
};
ov5640_reg_1v5: ov5640_reg_1v5 {
compatible = "regulator-fixed";
regulator-name = "ov5640_reg_1v5";
regulator-min-microvolt = <1500000>;
regulator-max-microvolt = <1500000>;
regulator-always-on;
};
...
};
...
};
...
&lpi2c3 {
...
ov5640_mipi: ov5640_mipi@3c {
compatible = "ovti,ov5640";
reg = <0x3c>;
clocks = <&clk IMX93_CLK_CCM_CKO3>;
assigned-clocks = <&clk IMX93_CLK_CCM_CKO3>;
assigned-clock-rates = <24000000>;
clock-names = "xclk";
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_mipi_cam>;
reset-gpios = <&gpio1 11 GPIO_ACTIVE_HIGH>;
csi_id = <0>;
mclk = <24000000>;
mclk_source = <0>;
mipi_csi;
DOVDD-supply = <&ov5640_reg_1v8>;
AVDD-supply = <&ov5640_reg_2v8>;
DVDD-supply = <&ov5640_reg_1v5>;
status = "okay";
port {
ov5640_mipi1_ep: endpoint {
remote-endpoint = <&mipi_csi_ep>;
data-lanes = <2>;
cfg-clk-range = <28>;
hs-clk-range = <0x16>;
};
};
};
...
};
...
&mipi_csi {
#address-cells = <1>;
#size-cells = <0>;
status = "okay";
port@0 {
reg = <0>;
mipi_csi_ep: endpoint {
remote-endpoint = <&ov5640_mipi1_ep>;
data-lanes = <2>;
cfg-clk-range = <28>;
hs-clk-range = <0x16>;
bus-type = <4>;
};
};
};
...
&iomuxc {
...
pinctrl_mipi_cam: mipi_cam {
fsl,pins = <
MX93_PAD_SAI1_TXFS__GPIO1_IO11 0x31e
>;
};
...
};
Accessing the peripheral[edit | edit source]
Linux messages at boot time[edit | edit source]
MIPI CSI driver initialized and if a MIPI camera is inserted, it has been recognized and its video driver is loaded:
... [ 1.877299] i2c 2-003c: Fixed dependency cycle(s) with /soc@0/bus@42800000/camera/csi@4ae00000/port@0/endpoint [ 1.888225] ov5640 2-003c: ov5640_write_reg: error: reg=3008, val=82 [ 2.064939] mxc-md 42800000.bus:camera: deferring csi device registration [ 2.072752] dwc-mipi-csi2-host 4ae00000.csi: lanes: 2, name: mxc-mipi-csi2.0 [ 2.109933] mx8-img-md: Registered sensor subdevice: ov5640 2-003c (1) [ 2.123066] mx8-img-md: created link [mxc-mipi-csi2.0] => [mxc_isi.0] [ 2.129497] mx8-img-md: created link [ov5640 2-003c] => [mxc-mipi-csi2.0] ...
Then, check if the camera is correctly recognized.
root@desk-mx93:~# ls -la /dev/video0 crw-rw---- 1 root video 81, 0 Mar 3 11:31 /dev/video0 root@desk-mx93:~#
Usage with gstreamer[edit | edit source]
Video capture and display using Pcam 5C OV5640 MIPI camera:
|
At every power-on cycle the first camera usage is not working. Run |
root@desk-mx93:~# gst-launch-1.0 v4l2src device=/dev/video0 ! video/x-raw,width=640,height=480 ! waylandsink Setting pipeline to PAUSED ... Pipeline is live and does not need PREROLL ... Pipeline is PREROLLED ... Setting pipeline to PLAYING ... New clock: GstSystemClock [ 1864.940941] mxc-mipi-csi2.0: format: 0x2008 [ 1864.950148] bypass csc [ 1864.952512] input fmt YUV4 [ 1864.955219] output fmt YUYV [ 1865.066804] dwc-mipi-csi2-host 4ae00000.csi: enter enable=1 Redistribute latency... handling interrupt.:99. Interrupt: Stopping pipeline ... Execution ended after 0:00:06.73270[ 1871.190805] dwc-mipi-csi2-host 4ae00000.csi: enter enable=0 5712 Setting pipeline to NULL ... Total showed frames (137), playing for (0:00:06.732670920), fps (20.349). Freeing pipeline ... root@desk-mx93:~#
Additional information[edit | edit source]
More information about gstreamer on its web site.
More information about i.MX gstreamer plugin on the gstreamer-imx web site
Peripheral SD[edit | edit source]
Device tree configuration[edit | edit source]
N.B. The USDHC interface is re-configured on the carrier device tree because of the Card Detect pin (which is related to the real board hardware implementation).
Here below is an example of device tree configuration used on standard DAVE's kit for the AURA SOM:
From imx93-aura-cb2001.dts:
...
&usdhc2 {
status = "okay";
};
...
From imx93-aura.dtsi:
...
&usdhc2 {
pinctrl-names = "default", "state_100mhz", "state_200mhz";
pinctrl-0 = <&pinctrl_usdhc2>, <&pinctrl_usdhc2_gpio>;
pinctrl-1 = <&pinctrl_usdhc2>, <&pinctrl_usdhc2_gpio>;
pinctrl-2 = <&pinctrl_usdhc2>, <&pinctrl_usdhc2_gpio>;
cd-gpios = <&gpio3 00 GPIO_ACTIVE_LOW>;
bus-width = <4>;
no-sdio;
no-mmc;
disable-wp;
no-1-8-v;
status = "disabled";
};
...
&iomuxc {
...
pinctrl_usdhc2_gpio: usdhc2gpiogrp {
fsl,pins = <
MX93_PAD_SD2_CD_B__GPIO3_IO00 0x31e
>;
};
pinctrl_usdhc2: usdhc2grp {
fsl,pins = <
MX93_PAD_SD2_CLK__USDHC2_CLK 0x17fe
MX93_PAD_SD2_CMD__USDHC2_CMD 0x13fe
MX93_PAD_SD2_DATA0__USDHC2_DATA0 0x13fe
MX93_PAD_SD2_DATA1__USDHC2_DATA1 0x13fe
MX93_PAD_SD2_DATA2__USDHC2_DATA2 0x13fe
MX93_PAD_SD2_DATA3__USDHC2_DATA3 0x13fe
MX93_PAD_SD2_VSELECT__USDHC2_VSELECT 0x51e
>;
};
...
};
Accessing the peripheral[edit | edit source]
Once initialized, the SD device is mapped to the standard /dev/mmcblk1pX block device, depending on how many partitions are created on the SD card.
Linux messages at boot time[edit | edit source]
If the microSD card is inserted at boot time, the kernel - once the USDHC interface has been initialized - prints the device information and the partitions detected like p1, p2, etc.:
... ... [ 1.347520] sdhci: Secure Digital Host Controller Interface driver [ 1.353715] sdhci: Copyright(c) Pierre Ossman [ 1.365042] sdhci-pltfm: SDHCI platform and OF driver helper ... [ 1.402850] mmc0: SDHCI controller on 42850000.mmc [42850000.mmc] using ADMA [ 1.525510] mmc0: new DDR MMC card at address 0001 [ 1.532646] mmcblk0: mmc0:0001 DG4008 7.28 GiB [ 1.543004] mmcblk0: p1 p2 [ 1.549076] mmcblk0boot0: mmc0:0001 DG4008 4.00 MiB [ 1.557364] mmcblk0boot1: mmc0:0001 DG4008 4.00 MiB [ 1.566409] mmcblk0rpmb: mmc0:0001 DG4008 4.00 MiB, chardev (234:0) [ 1.814684] sdhci-esdhc-imx 42860000.mmc: Got CD GPIO [ 1.851039] mmc1: SDHCI controller on 42860000.mmc [42860000.mmc] using ADMA [ 1.889752] mmc1: new high speed SDHC card at address 5048 [ 1.900514] mmcblk1: mmc1:5048 SD32G 28.9 GiB [ 1.906361] mmcblk1: p1 p2 [ 2.358195] EXT4-fs (mmcblk1p2): mounted filesystem with ordered data mode. Quota mode: none. [ 4.890543] EXT4-fs (mmcblk1p2): re-mounted. Quota mode: none. ...
Additional information[edit | edit source]
If booting from NFS, the file system configuration automatically mounts the uSD partitions.
root@desk-mx93:~# lsblk /dev/mmcblk1 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS mmcblk1 179:96 0 28.9G 0 disk |-mmcblk1p1 179:97 0 83.2M 0 part /run/media/boot-mmcblk1p1 `-mmcblk1p2 179:98 0 6.5G 0 part /run/media/root-mmcblk1p2 root@desk-mx93:~#
Peripheral UART[edit | edit source]
Device tree configuration[edit | edit source]
Here below is an example of device tree modifications to standard DAVE's kit for the AURA SOM:
From imx93-aura-cb2001.dts:
...
...
&lpuart4 {
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_uart4>;
status = "okay";
};
...
&iomuxc {
...
pinctrl_uart4: uart4grp{
fsl,pins = <
MX93_PAD_GPIO_IO14__LPUART4_TX 0x31e
MX93_PAD_GPIO_IO15__LPUART4_RX 0x31e
>;
};
...
Accessing the peripheral[edit | edit source]
Linux messages at boot time[edit | edit source]
... [ 0.847346] 44380000.serial: ttyLP0 at MMIO 0x44380010 (irq = 18, base_baud = 1500000) is a FSL_LPUART [ 0.856702] printk: console [ttyLP0] enabled [ 0.875438] 44390000.serial: ttyLP1 at MMIO 0x44390010 (irq = 19, base_baud = 1500000) is a FSL_LPUART [ 0.885307] 42580000.serial: ttyLP3 at MMIO 0x42580010 (irq = 20, base_baud = 1500000) is a FSL_LPUART [ 0.895137] 42690000.serial: ttyLP2 at MMIO 0x42690010 (irq = 21, base_baud = 1500000) is a FSL_LPUART ...
Usage with stty[edit | edit source]
N.B. UART mapping respect to ttyLPX is the following one:
LPUART1 <-> ttyLP0 LPUART2 <-> ttyLP1 LPUART3 <-> ttyLP2 LPUART4 <-> ttyLP3 ...
root@desk-mx93:~# stty -F /dev/ttyLP1 115200 -echo -raw root@desk-mx93:~# cat /dev/ttyLP1 > test_ttyLP1.log & [1] 716 root@desk-mx93:~# echo "Test loopback" > /dev/ttyLP1 root@desk-mx93:~# cat test_ttyLP1.log Test loopback root@desk-mx93:~#
Additional information[edit | edit source]
Serial ports can be used through the standard serial programming API.
For detailed information, please refer to the Serial Programming HOWTO at Serial-Programming-HOWTO
Peripheral USB1 OTG[edit | edit source]
AURA SOM supports OTG/Host/Peripheral modes: on AURA Evaluation Kit the USB1 OTG port is configured as peripheral.
Device tree configuration[edit | edit source]
Here below is an example of device tree configuration used on standard DAVE's kit for the AURA SOM:
From kernel device tree imx93-aura.dtsi:
...
&usbotg1 {
dr_mode = "peripheral";
hnp-disable;
srp-disable;
adp-disable;
disable-over-current;
samsung,picophy-pre-emp-curr-control = <3>;
samsung,picophy-dc-vol-level-adjust = <7>;
status = "disabled";
};
...
From kernel device tree imx93-aura-cb2001.dts:
/ {
...
&usbotg1 {
dr_mode = "peripheral";
status = "okay";
};
...
Accessing the peripheral[edit | edit source]
Usage with mass-storage[edit | edit source]
root@desk-mx93:~# dd if=/dev/zero of=mass_storage count=256 bs=1M 256+0 records in 256+0 records out 268435456 bytes (268 MB, 256 MiB) copied, 0.774426 s, 347 MB/s root@desk-mx93:~# mkfs.msdos mass_storage mkfs.fat 4.2 (2021-01-31) root@desk-mx93:~# mkdir loop root@desk-mx93:~# mount -o loop mass_storage loop [ 2309.051910] loop0: detected capacity change from 0 to 524288 root@desk-mx93:~# echo "Test USB OTG with mass storage device" > loop/usb.txt root@desk-mx93:~# umount loop root@desk-mx93:~#
then insert the g_mass_storage kernel module driver enabling an Windows PC to see it as a removable device
root@desk-mx93:~# modprobe g_mass_storage removable=y file=mass_storage [ 2366.224448] Mass Storage Function, version: 2009/09/11 [ 2366.229698] LUN: removable file: (no medium) [ 2366.234576] LUN: removable file: /home/root/mass_storage [ 2366.239928] Number of LUNs=1 [ 2366.242990] g_mass_storage gadget.0: Mass Storage Gadget, version: 2009/09/11 [ 2366.250151] g_mass_storage gadget.0: userspace failed to provide iSerialNumber [ 2366.257373] g_mass_storage gadget.0: g_mass_storage ready root@desk-mx93:~#
Once the USB cable is connected to the PC, the kernel prints the following messages:
[32262.935133] usb 1-1: new high-speed USB device number 2 using ehci-pci [32263.305571] usb 1-1: New USB device found, idVendor=0525, idProduct=a4a5, bcdDevice= 6.01 [32263.305574] usb 1-1: New USB device strings: Mfr=3, Product=4, SerialNumber=0 [32263.305575] usb 1-1: Product: Mass Storage Gadget [32263.305577] usb 1-1: Manufacturer: Linux 6.1.55-desk-mx9-l-5.0.0+g8942d3259e9b with 4c100000.usb [32263.337697] usb-storage 1-1:1.0: USB Mass Storage device detected [32263.337819] usb-storage 1-1:1.0: Quirks match for vid 0525 pid a4a5: 10000 [32263.337867] scsi host4: usb-storage 1-1:1.0 [32263.337968] usbcore: registered new interface driver usb-storage [32263.340492] usbcore: registered new interface driver uas [32264.367940] scsi 4:0:0:0: Direct-Access Linux File-Stor Gadget 0601 PQ: 0 ANSI: 2 [32264.368435] sd 4:0:0:0: Attached scsi generic sg2 type 0 [32264.385398] sd 4:0:0:0: Power-on or device reset occurred [32264.404893] sd 4:0:0:0: [sdb] 524288 512-byte logical blocks: (268 MB/256 MiB) [32264.519991] sd 4:0:0:0: [sdb] Write Protect is off [32264.519993] sd 4:0:0:0: [sdb] Mode Sense: 0f 00 00 00 [32264.637756] sd 4:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [32264.942269] sdb: [32265.225654] sd 4:0:0:0: [sdb] Attached SCSI removable disk
Peripheral USB2 OTG[edit | edit source]
AURA SOM supports OTG/Host/Peripheral modes: on AURA Evaluation Kit the USB2 OTG port is configured as USB Host.
Device tree configuration[edit | edit source]
Here below an example of device tree configuration used on standard DAVE's kit for the AURA SOM:
From kernel device tree imx93-aura.dtsi:
...
&usbotg2 {
dr_mode = "otg";
hnp-disable;
srp-disable;
adp-disable;
disable-over-current;
samsung,picophy-pre-emp-curr-control = <3>;
samsung,picophy-dc-vol-level-adjust = <7>;
status = "disabled";
};
...
From kernel device tree imx93-aura-cb2001.dts:
/ {
...
regulators {
...
reg_usb_pwr: usb_pwr {
compatible = "regulator-fixed";
regulator-name = "usb_pwr_en";
regulator-min-microvolt = <5000000>;
regulator-max-microvolt = <5000000>;
gpio = <&gpio1 8 GPIO_ACTIVE_HIGH>;
enable-active-high;
};
...
};
...
};
...
&usbotg2 {
dr_mode = "host";
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_usb_pwr>;
vbus-supply = <®_usb_pwr>;
status = "okay";
};
...
&iomuxc {
...
pinctrl_usb_pwr: usbpwrgrp {
fsl,pins = <
MX93_PAD_PDM_CLK__GPIO1_IO08 0x31e
>;
};
...
};
Accessing the peripheral[edit | edit source]
Linux messages at boot time[edit | edit source]
When a USB peripheral is inserted, in the following example a memory mass storage device, the kernel recognizes the device (i.e. xlass, vendor id, product id, etc.)
[ 1272.354409] usb 1-1: new high-speed USB device number 3 using ci_hdrc [ 1272.521077] usb-storage 1-1:1.0: USB Mass Storage device detected [ 1272.527735] scsi host0: usb-storage 1-1:1.0 [ 1273.539755] scsi 0:0:0:0: Direct-Access USB SanDisk 3.2Gen1 1.00 PQ: 0 ANSI: 6 [ 1273.550783] sd 0:0:0:0: [sda] 60125184 512-byte logical blocks: (30.8 GB/28.7 GiB) [ 1273.560595] sd 0:0:0:0: [sda] Write Protect is off [ 1273.567632] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 1273.592520] sda: sda1 [ 1273.601008] sd 0:0:0:0: [sda] Attached SCSI removable disk
Additional information[edit | edit source]
The root file system configuration automatically mounts the partition:
root@desk-mx93:~# lsblk /dev/sda NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 1 28.7G 0 disk `-sda1 8:1 1 28.7G 0 part /run/media/<usb-partition-name>-sda1
The mount point directory name depends on the USB partition name.
Peripheral GPIOs[edit | edit source]
i.MX93 can handle external pins in many different ways and most of them can be configured as GPIOs. When a pin is set as a GPIO, it is possible to read its value, change its direction or change output value directly from the shell.
Device tree configuration[edit | edit source]
Here below is an example of device tree configuration for using the GPIOs and enabling UART2 on standard DAVE's kit for the AURA SOM:
From imx93-aura-cb2001.dts:
leds {
compatible = "gpio-leds";
status = "okay";
uart2_en {
label = "uart2_en";
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_uart2_en>;
gpios = <&gpio2 4 GPIO_ACTIVE_HIGH>;
default-state = "on";
};
uart2_mode {
label = "uart2_mode";
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_uart2_mode>;
gpios = <&gpio3 27 GPIO_ACTIVE_HIGH>;
default-state = "off";
status = "disabled";
};
};
};
while the related pad configuration has been defined in the iomuxc section:
pinctrl_uart2_mode: uart2_mode {
fsl,pins = <
MX93_PAD_CCM_CLKO2__GPIO3_IO27 0x31e
>;
};
Accessing the peripheral[edit | edit source]
Linux messages at boot time[edit | edit source]
With the previous leds configuration for the GPIOs, it is possible to find them on sysfs under /sys/class/leds sub-directory:
root@desk-mx93:~# ls -la /sys/class/leds/uart2* total 0 lrwxrwxrwx 1 root root 0 Mar 3 2023 uart2_en -> ../../devices/platform/leds/leds/uart2_en root@desk-mx93:~#
Usage with libgpiod[edit | edit source]
Information about GPIOs library libgpiod - C library and tools - can be found on git.kernel.org
It is possible to compile libgpiod in the target (if the related Yocto package is not available for installation). Once the autoconf-archive package has been installed
dnf install autoconf-archive
it is possible to clone the libgpiod git repository and compile the related sources:
git clone https://git.kernel.org/pub/scm/libs/libgpiod/libgpiod.git cd libgpiod ./autogen.sh --enable-tools=yes --prefix=/usr/local make make install
Once installed, the gpio utilities are available in the target:
root@desk-mx93:~# gpio gpiodetect gpioget gpioinfo gpiomon gpionotify gpioset
gpiomon example[edit | edit source]
If a push button, with proper pull-up, is connected to a GPIO line available - for example using the J33.28 pin available on SBC AXEL Lite WIDE connector - the related GPIO can be used as an interrupt:
- J33.28 is connected to J10.191 SO-DIMM pin
- J33 connector is the WIDE connector in the AURA Evaluation Kit
- J10 connector is the SO-DIMM connector in the AURA Evaluation Kit
- ALT-0 alternate function for this pin is
GPIO2_IO12
- the corresponding pin number is associated to
gpiochip0line12 gpiomonutility can be used for monitor the pin status and triggering, for example, the falling-edge event:
root@desk-mx93:~# gpiomon -e falling -c 0 12 503.836012614 falling gpiochip0 12 504.229875114 falling gpiochip0 12 504.229962281 falling gpiochip0 12 504.229970823 falling gpiochip0 12 ^Croot@desk-mx93:~#
gpioset example[edit | edit source]
For changing a GPIO output status, the gpioset utility can be used:
- the following example set to High the pin
GPIO_IO00connected to J10.179 SO-DIMM pin
root@desk-mx93:~# gpioset -c 0 0=1
