DART-MX95
Overview
The DART-MX95 is a high-performance, low-power System-on-Module based on NXP’s i.MX 95 applications processor family. It targets demanding edge and industrial applications that require AI/ML acceleration, advanced graphics, rich connectivity and functional safety.
The i.MX 95 integrates up to six Arm® Cortex®-A55 processors running at up to 2.0 GHz together with an NPU for machine learning acceleration. Two real-time Arm® cores complete the heterogeneous architecture: a Cortex®-M7 running up to 800 MHz for high-performance real-time tasks and a Cortex®-M33 for system management, safety and low-power processing.
The SoM also features dual GbE plus 10GbE, PCIe Gen 3, high-speed USB, multiple display and camera interfaces, and industrial temperature range, making it suitable for a wide variety of embedded designs.
Zephyr OS is ported to run on either the Cortex®-A55 or the Cortex®-M7.
More information about the SoM can be found at the Variscite Wiki and Variscite website.
Specs Summary
CPU
NXP i.MX 95:
Up to 6x Cortex®-A55 @ 2.0 GHz
1x Cortex®-M7 @ 800 MHz
1x Cortex®-M33 (System Manager)
Neural Processing Unit (NPU) up to 2 TOPS
Memory
Up to 16GB LPDDR5 RAM
GPU
2D/3D GPU with support for OpenGL® ES 3.2, Vulkan® 1.2 and OpenCL® 3.0
Hardware 4K video encode/decode
NPU (Neural Processing Unit)
AI/ML acceleration engine up to 2 TOPS
Optimized for 8-bit and 16-bit integer workloads
Display
1x MIPI DSI up to 4K resolution
Dual-channel LVDS up to 1920x1080p60
Additional parallel / secondary display options depending on carrier
Network
2x 10/100/1000 Mbit/s Ethernet interfaces
1x 10GbE interface
Certified Wi-Fi 802.11ax/ac/a/b/g/n
Bluetooth/BLE 5.x and 802.15.4 (on Wi-Fi/Bluetooth module variants)
Camera
Up to 2x MIPI CSI-2 camera inputs (lane configuration depends on carrier)
Audio
Headphones / line out
Digital and analog microphone interfaces
Multiple I2S(SAI), S/PDIF, PDM and MQS outputs
USB
Up to 2x USB 3.0/2.0 OTG / Dual-Role ports (SoM + carrier dependent)
Serial interfaces
Up to 7x I2C
Up to 8x LPUART
Up to 8x SPI
1x I3C
Up to 5x CAN-FD
SD/MMC, QSPI and other high-speed interfaces
Temperature range
-40°C to 85°C (industrial grade)
More information about the SoM can be found at the Variscite Wiki and Variscite website.
Supported Features
The imx95_var_dart board supports the hardware features listed below.
- on-chip / on-board
- Feature integrated in the SoC / present on the board.
- 2 / 2
-
Number of instances that are enabled / disabled.
Click on the label to see the first instance of this feature in the board/SoC DTS files. -
vnd,foo -
Compatible string for the Devicetree binding matching the feature.
Click on the link to view the binding documentation.
imx95_var_dart/mimx9596/a55 target
On-target memory for this board target: 1 MiB of RAM, N/A of Flash.
Type |
Location |
Description |
Compatible |
|---|---|---|---|
CPU |
on-chip |
||
CAN |
on-chip |
NXP FlexCAN CANFD controller5 |
|
Clock control |
on-chip |
Generic fixed-rate clock provider4 |
|
Counter |
on-chip |
NXP Timer/PWM Module (TPM) used as timer6 |
|
Ethernet |
on-chip |
NXP i.MX NETC Block Controller1 |
|
on-chip |
NXP i.MX NETC Controller1 |
||
on-chip |
NXP i.MX NETC External MDIO controller1 |
||
on-chip |
NXP i.MX NETC Physical Station Interface (PSI)3 |
||
on-chip |
NXP NETC PTP (Precision Time Protocol) Clock1 |
||
Firmware |
on-chip |
SCMI (System Control and Management Interface) SHMEM (shared memory)1 |
|
on-chip |
SCMI (System Control and Management Interface) with doorbell and SHMEM (shared memory) transport1 |
||
on-chip |
SCMI (System Control and Management Interface) power domain protocol1 |
||
on-chip |
SCMI (System Control and Management Interface) clock protocol1 |
||
on-chip |
SCMI (System Control and Management Interface) pinctrl protocol1 |
||
GPIO & Headers |
on-chip |
i.MX RGPIO5 |
|
I2C |
on-chip |
NXP LPI2C controller8 |
|
Interrupt controller |
on-chip |
ARM Generic Interrupt Controller v31 |
|
on-chip |
GIC v3 Interrupt Translation Service1 |
||
Mailbox |
on-chip |
||
Pin control |
on-chip |
The node has the ‘pinctrl’ node label set in MCUX SoC’s devicetree1 |
|
PWM |
on-chip |
MCUX Timer/PWM Module (TPM)5 |
|
Serial controller |
on-chip |
||
Timer |
on-chip |
per-core ARM architected timer1 |
|
Watchdog |
on-chip |
NXP watchdog (WDOG32)2 |
imx95_var_dart/mimx9596/m7 target
On-target memory for this board target: 256 KiB of RAM, 256 KiB of Flash.
Type |
Location |
Description |
Compatible |
|---|---|---|---|
CPU |
on-chip |
ARM Cortex-M7 CPU1 |
|
ADC |
on-chip |
NXP successive-approximation ADC (SAR ADC) controller1 |
|
ARM architecture |
on-chip |
i.MX DTCM (Data Tightly Coupled Memory)1 |
|
Audio |
on-chip |
NXP PDM Microphone Interface (MICFIL)1 |
|
CAN |
on-chip |
NXP FlexCAN CANFD controller5 |
|
Counter |
on-chip |
NXP Time Stamp Timer (TSTMR)2 |
|
on-chip |
NXP Low Power Periodic Interrupt Timer (LPIT)2 |
||
on-chip |
Child node for the Low Power Periodic Interrupt Timer node, intended for an individual timer channel8 |
||
on-chip |
|||
DAI |
on-chip |
NXP Synchronous Audio Interface (SAI)1 |
|
Display |
on-chip |
socionext DPU display controller for DSI panels1 |
|
DMA |
on-chip |
NXP MCUX EDMA controller2 |
|
Ethernet |
on-chip |
NXP i.MX NETC Block Controller1 |
|
on-chip |
NXP i.MX NETC Controller1 |
||
on-chip |
NXP i.MX NETC External MDIO controller1 |
||
on-chip |
NXP i.MX NETC Physical Station Interface (PSI)3 |
||
on-chip |
NXP NETC PTP (Precision Time Protocol) Clock1 |
||
on-chip |
NXP NETC Virtual Station Interface (VSI)6 |
||
Firmware |
on-chip |
SCMI (System Control and Management Interface) SHMEM (shared memory)1 |
|
on-chip |
SCMI (System Control and Management Interface) with doorbell and SHMEM (shared memory) transport1 |
||
on-chip |
SCMI (System Control and Management Interface) power domain protocol1 |
||
on-chip |
SCMI (System Control and Management Interface) system power protocol1 |
||
on-chip |
SCMI (System Control and Management Interface) clock protocol1 |
||
on-chip |
SCMI (System Control and Management Interface) pinctrl protocol1 |
||
on-chip |
SCMI (System Control and Management Interface) cpu domain protocol1 |
||
GPIO & Headers |
on-chip |
i.MX RGPIO5 |
|
I2C |
on-chip |
NXP LPI2C controller8 |
|
I2S |
on-chip |
NXP mcux SAI-I2S controller1 |
|
I3C |
on-chip |
NXP MCUX I3C controller2 |
|
Interrupt controller |
on-chip |
ARMv7-M NVIC (Nested Vectored Interrupt Controller)1 |
|
on-chip |
|||
on-chip |
|||
Mailbox |
on-chip |
||
MIPI-DSI |
on-chip |
NXP MCUX MIPI DSI DWC1 |
|
Miscellaneous |
on-chip |
NXP FlexIO controller2 |
|
MMU / MPU |
on-chip |
ARMv7-M Memory Protection Unit (MPU)1 |
|
Pin control |
on-chip |
The node has the ‘pinctrl’ node label set in MCUX SoC’s devicetree1 |
|
Power domain |
on-chip |
SCMI (System Control and Management Interface) power domain2 |
|
PWM |
on-chip |
MCUX Timer/PWM Module (TPM)6 |
|
Serial controller |
on-chip |
||
SPI |
on-chip |
NXP LPSPI controller8 |
|
on-chip |
NXP FlexSPI controller1 |
||
Timer |
on-chip |
ARMv7-M System Tick1 |
|
Watchdog |
on-chip |
NXP watchdog (WDOG32)1 |
Note
It is recommended to disable peripherals used by the Cortex-M7 core on the Linux host when running Zephyr on M7.
Devices
System Clock
This board configuration uses a system clock frequency of 24 MHz. Cortex-A55 cores can run up to 2.0 GHz. Cortex-M7 core can run up to 800 MHz, and the SYSTICK timer runs at the same frequency as the M7 core clock.
Serial Port
On the standard DART-MX95 + DT8MCustomBoard setup, this board configuration uses:
LPUART1 as the primary debug serial console for the Cortex-A55 core
LPUART3 as the debug serial console for the Cortex-M7 core
Programming and Debugging (A55)
Copy the compiled zephyr.bin to the boot directory of the SD card or eMMC device and plug it
into the DT8MCustomBoard. Power it up and stop the U-Boot execution at the prompt.
Use U-Boot to load and run zephyr.bin on the Cortex-A55:
load mmc $mmcdev:$mmcpart $loadaddr /boot/zephyr.bin
dcache off; icache flush; go $loadaddr
Use this configuration to run basic Zephyr applications and kernel tests, for example, with the Hello World sample:
# From the root of the zephyr repository
west build -b imx95_var_dart/mimx9596/a55 samples/hello_world
This will build an image with the hello_world sample app. When loaded and executed it will
display the following console output on the A55 serial console:
*** Booting Zephyr OS build v4.0.0-xx-gxxxxxxxxxxxx ***
Hello World! imx95_var_dart/mimx9596/a55
Programming and Debugging (M7)
The imx95_var_dart board supports the runners and associated west commands listed below.
| flash | debug | rtt | reset | attach | debugserver | |
|---|---|---|---|---|---|---|
| jlink | ✅ (default) | ✅ (default) | ✅ | ✅ | ✅ | ✅ |
Note
The System Manager (SM) is an application that runs on the Cortex-M33. By default, the SM build configuration does not support the Cortex-M7 core. Support for it must be enabled before running Zephyr and it can be done by following the instructions in the Variscite Zephyr Page .
There are two main methods to load Cortex-M7 images on DART-MX95:
Using U-Boot commands to load and start the Cortex-M7 firmware.
Using the Linux
remoteprocframework (manual sysfs control or Variscite helper scripts).
Note
Do not enable both U-Boot auto-loading and Linux remoteproc control at the same time. If
Linux is expected to load/control the M7, ensure U-Boot auto-loading is disabled.
Load and Run M7 Zephyr Image from U-Boot
Load and run Zephyr on M7 from the Cortex-A55 using U-Boot by copying the compiled zephyr.bin to
the boot directory of the SD card or eMMC device. Power it up and stop U-Boot at the prompt.
The Variscite U-Boot environment provides helper commands to load and start the Cortex-M7 firmware. First, configure the M7 support and device tree once from Linux (optional but recommended):
root@imx95-var-dart:~# fw_setenv use_m7 yes
root@imx95-var-dart:~# fw_setenv fdt_file imx95-var-dart-dt8mcustomboard-m7.dtb
Then, after copying zephyr.bin to /boot, from U-Boot you can run:
setenv m7_bin zephyr.bin
saveenv
run loadm7bin
run runm7bin
By default, the Variscite environment loads the M7 image to the alias of the M7 TCM code area (for
example 0x203c0000) and then starts it using bootaux. The Zephyr console for M7 will appear
on the M7 UART (LPUART3 on DT8MCustomBoard).
Use this configuration to run basic Zephyr applications and kernel tests, for example, with the Hello World sample:
# From the root of the zephyr repository
west build -b imx95_var_dart/mimx9596/m7 samples/hello_world
When loaded and executed it will display the following console output on the M7 serial port:
*** Booting Zephyr OS build v4.0.0-xx-gxxxxxxxxxxxx ***
Hello World! imx95_var_dart/mimx9596/m7
Load and Run M7 Zephyr Image from Linux
The Linux remoteproc framework can be used to load the Cortex-M7 firmware from Linux userspace.
This can be done either manually via sysfs, or by using Variscite helper scripts.
Note
The device index (for example remoteproc1) may vary depending on the kernel and device tree.
List available devices with:
ls /sys/class/remoteproc/
Option A: Manual remoteproc control (sysfs)
(Optional) increase kernel loglevel while debugging:
sysctl -w kernel.printk=7
If the state is running, stop the Cortex-M7:
echo stop > /sys/class/remoteproc/remoteproc1/state
Load new firmware:
echo zephyr.elf > /sys/class/remoteproc/remoteproc1/firmware
The .elf file is expected to exist in the /lib/firmware directory.
Run the new firmware:
echo start > /sys/class/remoteproc/remoteproc1/state
Option B: Variscite helper scripts (recommended)
Transfer the built binaries zephyr.bin and zephyr.elf to the SoM /boot and
/lib/firmware respectively using scp or a USB drive.
Before running Cortex-M7 binaries from Linux, it is necessary to enable the device tree variant dedicated to Cortex-M7 applications:
root@imx95-var-dart:~# fw_setenv fdt_file imx95-var-dart-dt8mcustomboard-m7.dtb
root@imx95-var-dart:~# reboot
After rebooting into Linux with the -m7 device tree, it is possible to execute Zephyr binaries using Variscite remoteproc scripts originally designed for MCUXpresso firmware:
root@imx95-var-dart:~# /etc/remoteproc/variscite-rproc-linux -f /lib/firmware/zephyr.elf -c 1
[ 233.xxx] remoteproc remoteproc1: powering up imx-rproc
[ 233.xxx] remoteproc remoteproc1: Booting fw image zephyr.elf
[ 233.xxx] remoteproc remoteproc1: header-less resource table
[ 233.xxx] remoteproc remoteproc1: remote processor imx95-cm7 is now up
The Zephyr log should then appear on the Cortex-M7 UART (LPUART3), showing output similar to:
*** Booting Zephyr OS build v4.0.0-xx-gxxxxxxxxxxxx ***
Hello World! imx95_var_dart/mimx9596/m7
Configure U-Boot to auto-load the M7 firmware (optional)
You can also configure U-Boot to automatically load the M7 firmware on boot using the Variscite helper script:
root@imx95-var-dart:~# /etc/remoteproc/variscite-rproc-u-boot -f /boot/zephyr.bin -c 1
Configuring for M7 TCM memory
+ fw_setenv m7_addr 0x203c0000
+ fw_setenv fdt_file imx95-var-dart-dt8mcustomboard-m7.dtb
+ fw_setenv use_m7 yes
+ fw_setenv m7_bin zephyr.bin
+ fw_setenv m7_addr_auxview 0x00000000
Finished: Please reboot, the M7 firmware will run during U-Boot
After this configuration, on every boot U-Boot will load the Cortex-M7 firmware from
/boot/zephyr.bin before starting Linux.
For more information about Variscite remoteproc scripts and general Cortex-M7 support, visit Variscite Wiki.