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

ARM Cortex-A55 CPU15

arm,cortex-a55

CAN

on-chip

NXP FlexCAN CANFD controller5

nxp,flexcan-fd

Clock control

on-chip

Generic fixed-rate clock provider4

fixed-clock

Counter

on-chip

NXP Timer/PWM Module (TPM) used as timer6

nxp,tpm-timer

Ethernet

on-chip

NXP i.MX NETC Block Controller1

nxp,imx-netc-blk-ctrl

on-chip

NXP i.MX NETC Controller1

nxp,imx-netc

on-chip

NXP i.MX NETC External MDIO controller1

nxp,imx-netc-emdio

on-chip

NXP i.MX NETC Physical Station Interface (PSI)3

nxp,imx-netc-psi

on-chip

NXP NETC PTP (Precision Time Protocol) Clock1

nxp,netc-ptp-clock

Firmware

on-chip

SCMI (System Control and Management Interface) SHMEM (shared memory)1

arm,scmi-shmem

on-chip

SCMI (System Control and Management Interface) with doorbell and SHMEM (shared memory) transport1

arm,scmi

on-chip

SCMI (System Control and Management Interface) power domain protocol1

arm,scmi-power

on-chip

SCMI (System Control and Management Interface) clock protocol1

arm,scmi-clock

on-chip

SCMI (System Control and Management Interface) pinctrl protocol1

arm,scmi-pinctrl

GPIO & Headers

on-chip

i.MX RGPIO5

nxp,imx-rgpio

I2C

on-chip

NXP LPI2C controller8

nxp,lpi2c

Interrupt controller

on-chip

ARM Generic Interrupt Controller v31

arm,gic-v3

on-chip

GIC v3 Interrupt Translation Service1

arm,gic-v3-its

Mailbox

on-chip

NXP i.MX Message Unit as Zephyr MBOX15

nxp,mbox-imx-mu

Pin control

on-chip

The node has the ‘pinctrl’ node label set in MCUX SoC’s devicetree1

nxp,imx93-pinctrl

PWM

on-chip

MCUX Timer/PWM Module (TPM)5

nxp,kinetis-tpm

Serial controller

on-chip

NXP LPUART17

nxp,lpuart

Timer

on-chip

per-core ARM architected timer1

arm,armv8-timer

Watchdog

on-chip

NXP watchdog (WDOG32)2

nxp,wdog32

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

arm,cortex-m7

ADC

on-chip

NXP successive-approximation ADC (SAR ADC) controller1

nxp,sar-adc

ARM architecture

on-chip

i.MX DTCM (Data Tightly Coupled Memory)1

nxp,imx-dtcm

Audio

on-chip

NXP PDM Microphone Interface (MICFIL)1

nxp,micfil

CAN

on-chip

NXP FlexCAN CANFD controller5

nxp,flexcan-fd

Counter

on-chip

NXP Time Stamp Timer (TSTMR)2

nxp,tstmr

on-chip

NXP Low Power Periodic Interrupt Timer (LPIT)2

nxp,lpit

on-chip

Child node for the Low Power Periodic Interrupt Timer node, intended for an individual timer channel8

nxp,lpit-channel

on-chip

NXP LPTMR11

nxp,lptmr

DAI

on-chip

NXP Synchronous Audio Interface (SAI)1

nxp,dai-sai

Display

on-chip

socionext DPU display controller for DSI panels1

socionext,dpu

DMA

on-chip

NXP MCUX EDMA controller2

nxp,mcux-edma

Ethernet

on-chip

NXP i.MX NETC Block Controller1

nxp,imx-netc-blk-ctrl

on-chip

NXP i.MX NETC Controller1

nxp,imx-netc

on-chip

NXP i.MX NETC External MDIO controller1

nxp,imx-netc-emdio

on-chip

NXP i.MX NETC Physical Station Interface (PSI)3

nxp,imx-netc-psi

on-chip

NXP NETC PTP (Precision Time Protocol) Clock1

nxp,netc-ptp-clock

on-chip

NXP NETC Virtual Station Interface (VSI)6

nxp,imx-netc-vsi

Firmware

on-chip

SCMI (System Control and Management Interface) SHMEM (shared memory)1

arm,scmi-shmem

on-chip

SCMI (System Control and Management Interface) with doorbell and SHMEM (shared memory) transport1

arm,scmi

on-chip

SCMI (System Control and Management Interface) power domain protocol1

arm,scmi-power

on-chip

SCMI (System Control and Management Interface) system power protocol1

arm,scmi-system

on-chip

SCMI (System Control and Management Interface) clock protocol1

arm,scmi-clock

on-chip

SCMI (System Control and Management Interface) pinctrl protocol1

arm,scmi-pinctrl

on-chip

SCMI (System Control and Management Interface) cpu domain protocol1

nxp,scmi-cpu

GPIO & Headers

on-chip

i.MX RGPIO5

nxp,imx-rgpio

I2C

on-chip

NXP LPI2C controller8

nxp,lpi2c

I2S

on-chip

NXP mcux SAI-I2S controller1

nxp,mcux-i2s

I3C

on-chip

NXP MCUX I3C controller2

nxp,mcux-i3c

Interrupt controller

on-chip

ARMv7-M NVIC (Nested Vectored Interrupt Controller)1

arm,v7m-nvic

on-chip

i.MX DSP interrupt controller11

nxp,irqsteer-intc

on-chip

i.MX IRQ_STEER master106

nxp,irqsteer-master

Mailbox

on-chip

NXP i.MX Message Unit as Zephyr MBOX11

nxp,mbox-imx-mu

MIPI-DSI

on-chip

NXP MCUX MIPI DSI DWC1

nxp,mipi-dsi-dwc

Miscellaneous

on-chip

NXP FlexIO controller2

nxp,flexio

MMU / MPU

on-chip

ARMv7-M Memory Protection Unit (MPU)1

arm,armv7m-mpu

Pin control

on-chip

The node has the ‘pinctrl’ node label set in MCUX SoC’s devicetree1

nxp,imx93-pinctrl

Power domain

on-chip

SCMI (System Control and Management Interface) power domain2

arm,scmi-power-domain

PWM

on-chip

MCUX Timer/PWM Module (TPM)6

nxp,kinetis-tpm

Serial controller

on-chip

NXP LPUART17

nxp,lpuart

SPI

on-chip

NXP LPSPI controller8

nxp,lpspi

on-chip

NXP FlexSPI controller1

nxp,imx-flexspi

Timer

on-chip

ARMv7-M System Tick1

arm,armv7m-systick

Watchdog

on-chip

NXP watchdog (WDOG32)1

nxp,wdog32

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 remoteproc framework (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

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.

References