MIMXRT1040-EVK

Board Overview

MIMXRT1040-EVK

Name:

mimxrt1040_evk

Vendor:

NXP Semiconductors

Architecture:

arm

SoC:

mimxrt1042

Browse board sources

Overview

i.MX RT1040 crossover MCUs add additional flexibility with new packages and an extended temperature range up to 125° C. The i.MX RT1040 MCU has a compact 9x9 mm package, as well as the 11x11 mm package that supports implementing a 2-layer PCB design. The i.MX RT1040 MCUs run on the Arm® Cortex®-M7 core at 600 MHz.

Hardware

• MIMXRT1042XJM5B MCU (600 MHz, 512 KB TCM)

• Memory

  • 256 MBit SDRAM (Winbond W9825G6KH)

  • 64 Mbit QSPI Flash (Winbond W25Q64JVSSIQ)

• Display

  • LCD connector

  • Touch connector

• Ethernet

  • 10/100 Mbit/s Ethernet PHY

• USB

  • USB 2.0 OTG connector

• Audio

  • 3.5 mm audio stereo headphone jack

  • Board-mounted microphone

• Power

  • 5 V DC jack

• Debug

  • JTAG 20-pin connector

  • OpenSDA with DAPLink

• Expansion port

  • Arduino interface

• CAN bus connector

For more information about the MIMXRT1040 SoC and MIMXRT1040-EVK board, see these references:

• i.MX RT1040 Website

• i.MX RT1040 Datasheet

• i.MX RT1040 Reference Manual

• MIMXRT1040-EVK Website

• MIMXRT1040-EVK User Guide

• MIMXRT1040-EVK Design Files

External Memory

This platform has the following external memories:

Device	Controller	Status
W9825G6KH	SEMC	Enabled via device configuration data block, which sets up SEMC at boot time
W25Q64JVSSIQ	FLEXSPI	Enabled via flash configuration block, which sets up FLEXSPI at boot time. Supported for XIP only.

Supported Features

The mimxrt1040_evk 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.

mimxrt1040_evk

/

mimxrt1042

mimxrt1040_evk/mimxrt1042 target

Type	Location	Description	Compatible
CPU	on-chip	ARM Cortex-M7 CPU1	arm,cortex-m7
ADC	on-chip	NXP MCUA 12B1MSPS SAR ADC1 1	nxp,mcux-12b1msps-sar
ARM architecture	on-chip	MCUX XBAR (Crossbar)3	nxp,mcux-xbar
Bluetooth	on-board	Bluetooth module that uses NXP’s Bluetooth Module (e.g1	nxp,bt-hci-uart
CAN	on-chip	NXP FlexCAN controller2	nxp,flexcan
	on-chip	NXP FlexCAN CANFD controller1	nxp,flexcan-fd
Clock control	on-chip	i.MX CCM (Clock Controller Module) IP node1	nxp,imx-ccm
	on-chip	Generic fixed factor clock provider3	fixed-factor-clock
	on-chip	i.MX CCM Fractional PLL1	nxp,imx-ccm-fnpll
	on-chip	i.MX ANATOP (Analog Clock Controller Module) IP node1	nxp,imx-anatop
	on-chip	Generic fixed-rate clock provider4	fixed-clock
Counter	on-chip	NXP MCUX Quad Timer (QTMR)4	nxp,imx-qtmr
	on-chip	NXP MCUX Quad Timer Channel16	nxp,imx-tmr
	on-chip	NXP Periodic Interrupt Timer (PIT)1	nxp,pit
	on-chip	Child node for the Periodic Interrupt Timer node, intended for an individual timer channel4	nxp,pit-channel
Cryptographic accelerator	on-chip	NXP Data Co-Processor (DCP) Crypto accelerator1	nxp,mcux-dcp
Debug	on-chip	ARMv7 instrumentation trace macrocell1	arm,armv7m-itm
Display	on-chip	NXP i.MX eLCDIF (Enhanced LCD Interface) controller1	nxp,imx-elcdif
DMA	on-chip	NXP MCUX EDMA controller1	nxp,mcux-edma
	on-chip	NXP PXP 2D DMA engine1	nxp,pxp
Ethernet	on-chip	NXP ENET IP Module1	nxp,enet
	on-chip	NXP ENET MAC/L2 Device1	nxp,enet-mac
	on-chip	NXP ENET PTP (Precision Time Protocol) Clock1	nxp,enet-ptp-clock
GPIO & Headers	on-chip	i.MX GPIO9	nxp,imx-gpio
	on-board	GPIO pins exposed on NXP LCD interface1	nxp,parallel-lcd-connector
	on-board	GPIO pins exposed on NXP LCD touch controller interface1	nxp,i2c-tsc-fpc
	on-board	GPIO pins exposed on Arduino Uno (R3) headers1	arduino-header-r3
I2C	on-chip	NXP LPI2C controller2 2	nxp,lpi2c
I2S	on-chip	NXP mcux SAI-I2S controller3	nxp,mcux-i2s
Input	on-board	Group of GPIO-bound input keys1	gpio-keys
Interrupt controller	on-chip	ARMv7-M NVIC (Nested Vectored Interrupt Controller)1	arm,v7m-nvic
LED	on-board	Group of GPIO-controlled LEDs1	gpio-leds
MDIO	on-chip	NXP ENET MDIO Features1	nxp,enet-mdio
Memory controller	on-chip	NXP FlexRAM on-chip ram controller If the flexram,bank-spec property is specified, then the flexram will be dynamically reconfigured to the configuration specified at runtime1	nxp,flexram
	on-chip	NXP Smart External Memory Controller (SEMC)1	nxp,imx-semc
Miscellaneous	on-chip	NXP FlexIO controller3	nxp,flexio
MMU / MPU	on-chip	ARMv7-M Memory Protection Unit (MPU)1	arm,armv7m-mpu
MTD	on-board	NXP FlexSPI NOR1	nxp,imx-flexspi-nor
	on-board	Fixed partitions of a flash (or other non-volatile storage) memory1	fixed-partitions
Pin control	on-chip	This compatible binding should be applied to the device’s iomuxc DTS node1	nxp,imx-iomuxc
	on-chip	The node has the ‘pinctrl’ node label set in MCUX RT SoC’s devicetree1	nxp,mcux-rt-pinctrl
	on-chip	i.MX IOMUXC1	nxp,imx-gpr
PWM	on-chip	NXP eFLEX PWM module with mcux-pwm submodules4	nxp,flexpwm
	on-chip	NXP MCUX PWM1 15	nxp,imx-pwm
RNG	on-chip	Kinetis TRNG (True Random Number Generator)1	nxp,kinetis-trng
RTC	on-chip	NXP SNVS LP/HP RTC1	nxp,imx-snvs-rtc
SDHC	on-chip	NXP imx USDHC controller2	nxp,imx-usdhc
Sensors	on-board	FXLS8974 3-axis accelerometer sensor1	nxp,fxls8974
	on-chip	NXP MCUX QDEC4	nxp,mcux-qdec
	on-chip	NXP on-die temperature monitor1	nxp,tempmon
Serial controller	on-chip	NXP LPUART2 6	nxp,lpuart
SPI	on-chip	NXP FlexSPI controller1 1	nxp,imx-flexspi
	on-chip	NXP LPSPI controller1 2	nxp,lpspi
Timer	on-chip	ARMv7-M System Tick1	arm,armv7m-systick
	on-chip	NXP MCUX General-Purpose HW Timer (GPT)1	nxp,gpt-hw-timer
	on-chip	NXP MCUX General-Purpose Timer (GPT)1	nxp,imx-gpt
USB	on-chip	NXP EHCI USB device mode1	nxp,ehci
	on-chip	NXP USB high speed phy that is used on NXP RTxxxx, RTxxx, MCX, LPC and Kinetis platforms if high speed usb is supported on these platforms2	nxp,usbphy
Watchdog	on-chip	imxRT watchdog2	nxp,imx-wdog

Note

For additional features not yet supported, please also refer to the MIMXRT1064-EVK , which is the superset board in NXP’s i.MX RT10xx family. NXP prioritizes enabling the superset board with NXP’s Full Platform Support for Zephyr. Therefore, the mimxrt1064_evk board may have additional features already supported, which can also be re-used on this mimxrt1040_evk board.

Connections and IOs

The MIMXRT1040 SoC has five pairs of pinmux/gpio controllers.

Name	Function	Usage
GPIO_AD_B0_12	LPUART1_TX	UART Console
GPIO_AD_B0_13	LPUART1_RX	UART Console
WAKEUP	GPIO	SW0
GPIO_AD_B0_08	GPIO	User LD1
GPIO_AD_B0_10	FLEXPWM1 PWM3A	PWM Output
GPIO_AD_B0_14	ADC0 IN3	ADC0 Input
GPIO_AD_B0_15	ADC0 IN4	ADC0 Input
GPIO_SD_B0_02	LPSPI1_SDO	SPI Output
GPIO_SD_B0_03	LPSPI1_SDI	SPI Input
GPIO_SD_B0_00	LPSPI1_SCK	SPI Clock
GPIO_SD_B0_00	LPSPI1_SCK	SPI Clock
GPIO_AD_B1_00	LPI2C1_SCL	I2C Clock
GPIO_AD_B1_01	LPI2C1_SDA	I2C Data
GPIO_AD_B1_06	LPUART3_TX	M.2 BT HCI
GPIO_AD_B1_07	LPUART3_RX	M.2 BT HCI
GPIO_AD_B1_04	LPUART3_CTS_b	M.2 BT HCI
GPIO_AD_B1_05	LPUART3_RTS_b	M.2 BT HCI

Note

In order to use the SPI peripheral on this board, resistors R350, R346, and R360 must be populated with zero ohm resistors.

System Clock

The MIMXRT1040 SoC is configured to use SysTick as the system clock source, running at 600MHz.

When power management is enabled, the 32 KHz low frequency oscillator on the board will be used as a source for the GPT timer to generate a system clock. This clock enables lower power states, at the cost of reduced resolution

Serial Port

The MIMXRT1040 SoC has eight UARTs. LPUART1 is configured for the console, LPUART3 for the Bluetooth Host Controller Interface (BT HCI), and the remaining UARTs are not used.

Fetch Binary Blobs

The board Bluetooth/WiFi module requires fetching some binary blob files, to do that run the command:

west blobs fetch hal_nxp

Note

Only Bluetooth functionality is currently supported.

Programming and Debugging

This board supports 3 debug host tools. Please install your preferred host tool, then follow the instructions in Configuring a Debug Probe to configure the board appropriately.

• J-Link Debug Host Tools (Default, Supported by NXP)

• LinkServer Debug Host Tools (Supported by NXP)

• pyOCD Debug Host Tools (Not supported by NXP)

Once the host tool and board are configured, build and flash applications as usual (see Building an Application and Run an Application for more details).

Configuring a Debug Probe

For the RT1040, J9/J10 are the SWD isolation jumpers, J12 is the DFU mode jumper, and J2 is the 20 pin JTAG/SWD header.

A debug probe is used for both flashing and debugging the board. This board has an LPC-LINK2 Onboard Debug Probe. The default firmware present on this probe is the LPC-Link2 DAPLink Onboard Debug Probe.

Based on the host tool installed, please use the following instructions to setup your debug probe:

• J-Link Debug Host Tools: Using J-Link with LPC-Link2 Probe

• LinkServer Debug Host Tools: Using CMSIS-DAP with LPC-Link2 Probe

• pyOCD Debug Host Tools: Using CMSIS-DAP with LPC-Link2 Probe

Using CMSIS-DAP with LPC-Link2 Probe

1. Follow the instructions provided at LPC-LINK2 CMSIS DAP Onboard Debug Probe to reprogram the default debug probe firmware on this board.

2. Ensure the SWD isolation jumpers are populated

Using J-Link with LPC-Link2 Probe

There are two options: the onboard debug circuit can be updated with Segger J-Link firmware, or a J-Link External Debug Probe can be attached to the EVK.

To update the onboard debug circuit, please do the following:

1. Switch the power source for the EVK to a different source than the debug USB, as the J-Link firmware does not power the EVK via the debug USB.

2. Follow the instructions provided at LPC-Link2 J-Link Onboard Debug Probe to reprogram the default debug probe firmware on this board.

3. Ensure the SWD isolation jumpers are populated.

To attach an external J-Link probe, ensure the SWD isolation jumpers are removed, then connect the probe to the external JTAG/SWD header

Configuring a Console

Regardless of your choice in debug probe, we will use the OpenSDA microcontroller as a usb-to-serial adapter for the serial console. Check that jumpers J11 and J13 are on (they are on by default when boards ship from the factory) to connect UART signals to the OpenSDA microcontroller.

Connect a USB cable from your PC to J1.

Use the following settings with your serial terminal of choice (minicom, putty, etc.):

• Speed: 115200

• Data: 8 bits

• Parity: None

• Stop bits: 1

Flashing

Here is an example for the Hello World application.

# From the root of the zephyr repository
west build -b mimxrt1040_evk samples/hello_world
west flash

Open a serial terminal, reset the board (press the SW1 button), and you should see the following message in the terminal:

***** Booting Zephyr OS Booting Zephyr OS build v3.3.0-rc3-66 *****
Hello World! mimxrt1040_evk

Debugging

Here is an example for the Hello World application.

# From the root of the zephyr repository
west build -b mimxrt1040_evk samples/hello_world
west debug

Open a serial terminal, step through the application in your debugger, and you should see the following message in the terminal:

***** Booting Zephyr OS Booting Zephyr OS build v3.3.0-rc3-66 *****
Hello World! mimxrt1040_evk

Troubleshooting

USER_LED D8

The MIMXRT1040-EVK board ships with the wireless module in the M.2 connector, and with jumper J80 shorted. This causes a conflict with the USER_LED D8, and the LED will not turn off. Samples and applications using USER_LED D8, like blinky, require removal of J80 jumper.

Boot Header

If the debug probe fails to connect with the following error, it’s possible that the boot header in QSPI is invalid or corrupted. The boot header is configured by CONFIG_NXP_IMXRT_BOOT_HEADER.

Remote debugging using :2331
Remote communication error.  Target disconnected.: Connection reset by peer.
"monitor" command not supported by this target.
"monitor" command not supported by this target.
You can't do that when your target is `exec'
(gdb) Could not connect to target.
Please check power, connection and settings.

You can fix it by erasing and reprogramming the QSPI with the following steps:

1. Set the SW4 DIP switches to OFF-OFF-OFF-ON to boot into the ROM bootloader.

2. Reset by pressing SW1

3. Run west debug or west flash again with a known working Zephyr application.

4. Set the SW4 DIP switches to OFF-OFF-ON-OFF to boot from QSPI.

5. Reset by pressing SW1

Bluetooth Module

For Murate 2EL M.2 Mdoule, the following hardware rework needs to be applied, Solder 0 ohm resistors for R96, and R93. Remove resistors from R497, R498, R456 and R457.

And due to pin conflict issue, the PCM interface of Bluetooth module cannot be supported.

For the debugger fails to connect with the following error, please refer to the next section.

WiFi Module

If the debugger fails to connect with the following error, it’s possible the M.2 WiFi module is interfering with the debug signals

Remote debugging using :2331
Remote communication error.  Target disconnected.: Connection reset by peer.
"monitor" command not supported by this target.
"monitor" command not supported by this target.
You can't do that when your target is `exec'
(gdb) Could not connect to target.
Please check power, connection and settings.

To resolve this, you may remove the M.2 WiFi module from the board when flashing or debugging it, or remove jumper J80.

Support Resources for Zephyr

• NXP Zephyr Downstream Software Development Kit

• MCUXpresso for VS Code, wiki documentation and Zephyr lab guides

• NXP Zephyr Knowledge Hub

• NXP’s Zephyr landing page (including training resources)

• NXP Support Community forum for Zephyr