.. zephyr:board:: mimxrt1040_evk

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:

Supported Features

.. zephyr:board-supported-hw::

.. note::

For additional features not yet supported, please also refer to the :zephyr:board: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.

Shields for Supported Features

Some features in the table above are tested with Zephyr shields. These shields are tested on this board:

:ref:rk043fn02h_ct and :ref:rk043fn66hs_ctg - support the Display interface.
:ref:nxp_m2_wifi_bt - Rev C version is tested with this shield to attach any M.2 module with BT HCI UART interface and Wi-Fi SDIO interface. The shield binds the required NXP HCI driver or SDIO driver to perform firmware-load and other setup configurations for NXP SoC IW416/IW612/IW610.

For the :ref:nxp_m2_wifi_bt shield, 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.

Connections and IOs

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

.. 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:

.. code-block:: console

west blobs fetch hal_nxp

.. note:: Only Bluetooth functionality is currently supported.

Programming and Debugging

.. zephyr:board-supported-runners::

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.

:ref:jlink-debug-host-tools (Default, Supported by NXP)
:ref:linkserver-debug-host-tools (Supported by NXP)
:ref:pyocd-debug-host-tools (Not supported by NXP)

Once the host tool and board are configured, build and flash applications as usual (see :ref:build_an_application and :ref:application_run 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.

.. include:: ../../common/rt1xxx-lpclink2-debug.rst.inc

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 :zephyr:code-sample:hello_world application.

.. zephyr-app-commands:: :zephyr-app: samples/hello_world :board: mimxrt1040_evk :goals: flash

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

.. code-block:: console

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

Debugging

Here is an example for the :zephyr:code-sample:hello_world application.

.. zephyr-app-commands:: :zephyr-app: samples/hello_world :board: mimxrt1040_evk :goals: debug

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

.. code-block:: console

***** 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 :kconfig:option:CONFIG_NXP_IMXRT_BOOT_HEADER.

.. code-block:: console

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:

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

#. Reset by pressing SW1

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

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

#. Reset by pressing SW1

Bluetooth Module

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

.. code-block:: console

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

.. include:: ../../common/board-footer.rst.inc

.. _MIMXRT1040-EVK Website: https://www.nxp.com/design/development-boards/i-mx-evaluation-and-development-boards/i-mx-rt1040-evaluation-kit:MIMXRT1040-EVK

.. _MIMXRT1040-EVK User Guide: https://www.nxp.com/webapp/Download?colCode=MIMXRT1040-EVKUM

.. _MIMXRT1040-EVK Design Files: https://www.nxp.com/webapp/Download?colCode=MIMXRT1040-EVK-DESIGNFILES

.. _i.MX RT1040 Website: https://www.nxp.com/products/processors-and-microcontrollers/arm-microcontrollers/i-mx-rt-crossover-mcus/i-mx-rt1040-crossover-mcu-with-arm-cortex-m7-core:i.MX-RT1040

.. _i.MX RT1040 Datasheet: https://www.nxp.com/docs/en/data-sheet/IMXRT1040CEC.pdf

.. _i.MX RT1040 Reference Manual: https://www.nxp.com/webapp/Download?colCode=IMXRT1040RM

.. _NXP AN13206: https://www.nxp.com/docs/en/application-note/AN13206.pdf