.. zephyr:board:: mimxrt1060_evk

Overview

The i.MX RT1060 adds to the industry's first crossover processor series and expands the i.MX RT series to three scalable families.

The i.MX RT1060 doubles the On-Chip SRAM to 1MB while keeping pin-to-pin compatibility with i.MX RT1050. This series introduces additional features ideal for real-time applications such as High-Speed GPIO, CAN FD, and synchronous parallel NAND/NOR/PSRAM controller. The i.MX RT1060 runs on the Arm® Cortex-M7® core up to 600 MHz.

Hardware

MIMXRT1062DVL6A MCU (600 MHz, 1024 KB on-chip memory)
Memory
- 256 Mbit SDRAM
- 64 Mbit QSPI Flash
- 512 Mbit Hyper Flash
- TF socket for SD card
Display
- LCD connector
Ethernet
- 10/100 Mbit/s Ethernet PHY
USB
- USB 2.0 OTG connector
- USB 2.0 host connector
Audio
- 3.5 mm audio stereo headphone jack
- Board-mounted microphone
- Left and right speaker out connectors
Power
- 5 V DC jack
Debug
- JTAG 20-pin connector
- OpenSDA with DAPLink
Sensor
- FXOS8700CQ 6-axis e-compass
- CMOS camera sensor interface
Expansion port
- Arduino interface
CAN bus connector

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

i.MX RT1060 Website_
i.MX RT1060 Datasheet_
i.MX RT1060 Reference Manual_
MIMXRT1060-EVK Website_
MIMXRT1060-EVK User Guide_
MIMXRT1060-EVK Schematics_
MIMXRT1060-EVK Debug Firmware_

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 mimxrt1060_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: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.
:ref:rk043fn02h_ct and :ref:rk043fn66hs_ctg - support the Display interface.
:ref:dvp_fpc24_mt9m114 - supports the CSI video/camera interface.

Connections and I/Os

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

.. note:: In order to use the SPI peripheral on this board, resistors R278, R279, R280 and R281 must be populated with zero ohm resistors.

System Clock

The MIMXRT1060 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 MIMXRT1060 SoC has eight UARTs. LPUART1 is configured for the console, LPUART3 for the Bluetooth Host Controller Interface (BT HCI), and the remaining are not used.

Board Revisions and Targets

There are three revisions of this board.

Rev A:

Initial version

Rev B:

adds the M.2 connector for Wi-Fi/BLE
adds audio expansion connector J23
USER LED1 changed to GPIO1 pin 8

Rev C:

Replaces audio codec WM8960(EOL) to WM8962
Replaces 32.768 KHz oscillator from ASH7K-32.768KHz-T(EOL)to ASH7KW-32.768KHZ-L-T
Replaces motion sensor from FXOS8700CQ(EOL) to FXLS8974CFR3
Re-assigns Bluetooth Audio PCM with dedicated I2S2
Re-assigns Bluetooth interface UART_CTS, UART_RTS to hardware PIN

This board has two variants that can be targeted, depending on which flash to set as zephyr,flash:

mimxrt1060_evk/mimxrt1062/qspi is the default variant for the out of box setup of the board using the qspi flash.
mimxrt1060_evk/mimxrt1062/hyperflash is for a board that has been reworked to use the hyperflash instead of the qspi flash.
This board also has two revisions, the EVKA and EVKB. EVKA is the default target for this board. To target EVKB, the board target string would become mimxrt1060_evk@B//qspi, for example.

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

Three revisions of the RT1060 EVK exist. For all of them, to replace the debug firmware, short the DFU jumper to boot the on board debugger to ISP mode.

RT1060 EVK (Revision A)
- SWD isolation jumpers: J47/48
- 20 pin JTAG/SWD header: J21
- DFU mode jumper: J42
RT1060 EVKB
- SWD isolation jumpers: J9/10
- 20 pin JTAG/SWD header: J2
- DFU mode jumper: J12
RT1060 EVKC
- Debugger choice jumper: JP5
- DFU mode jumper: JP3

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

See Using J-Link with MIMXRT1060-EVK or MIMXRT1064-EVK_ or Using J-Link with MIMXRT1060-EVKB_ for more details.

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 J45 and J46 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 J41.

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

Speed: 115200
Data: 8 bits
Parity: None
Stop bits: 1

Using SWO

SWO can be used as a logging backend, by setting CONFIG_LOG_BACKEND_SWO=y. Your SWO viewer should be configured with a CPU frequency of 132MHz, and SWO frequency of 7500KHz.

Flashing

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

.. tabs::

.. group-tab:: i.MX RT1060 Rev A

  .. zephyr-app-commands::
     :zephyr-app: samples/hello_world
     :board: mimxrt1060_evk@A//qspi
     :goals: flash

.. group-tab:: i.MX RT1060 Rev B

  .. zephyr-app-commands::
     :zephyr-app: samples/hello_world
     :board: mimxrt1060_evk@B//qspi
     :goals: flash

.. group-tab:: i.MX RT1060 Rev C (default)

  .. zephyr-app-commands::
     :zephyr-app: samples/hello_world
     :board: mimxrt1060_evk@C//qspi
     :goals: flash

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

.. code-block:: console

***** Booting Zephyr OS v1.14.0-rc1 ***** Hello World! mimxrt1060_evk//qspi

Debugging

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

.. tabs::

.. group-tab:: i.MX RT1060 Rev A

  .. zephyr-app-commands::
     :zephyr-app: samples/hello_world
     :board: mimxrt1060_evk@A//qspi
     :goals: debug

.. group-tab:: i.MX RT1060 Rev B

  .. zephyr-app-commands::
     :zephyr-app: samples/hello_world
     :board: mimxrt1060_evk@B//qspi
     :goals: debug

.. group-tab:: i.MX RT1060 Rev C (default)

  .. zephyr-app-commands::
     :zephyr-app: samples/hello_world
     :board: mimxrt1060_evk@C//qspi
     :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 v1.14.0-rc1 ***** Hello World! mimxrt1060_evk//qspi

Troubleshooting

If the debug probe fails to connect with the following error, it's possible that the boot header in QSPI flash 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 flash with the following steps:

#. Set the SW7 DIP switches to ON-OFF-ON-OFF to prevent booting from QSPI flash.

#. Reset by pressing SW9

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

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

#. Reset by pressing SW9

If the west flash or debug commands fail, and the command hangs while executing runners.jlink, confirm the J-Link debug probe is configured, powered, and connected to the EVK properly.

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

.. _MIMXRT1060-EVK Website: https://www.nxp.com/design/development-boards/i-mx-evaluation-and-development-boards/i-mx-rt1060-evaluation-kit:MIMXRT1060-EVKB

.. _MIMXRT1060-EVK User Guide: https://www.nxp.com/webapp/Download?colCode=MIMXRT10601064EKBHUG

.. _MIMXRT1060-EVK Debug Firmware: https://www.nxp.com/docs/en/application-note/AN13206.pdf

.. _MIMXRT1060-EVK Schematics: https://www.nxp.com/webapp/Download?colCode=MIMXRT1060-EVK-DESIGNFILE-A3

.. _i.MX RT1060 Website: https://www.nxp.com/products/processors-and-microcontrollers/arm-based-processors-and-mcus/i.mx-applications-processors/i.mx-rt-series/i.mx-rt1060-crossover-processor-with-arm-cortex-m7-core:i.MX-RT1060

.. _i.MX RT1060 Datasheet: https://www.nxp.com/docs/en/nxp/data-sheets/IMXRT1060CEC.pdf

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

.. _Using J-Link with MIMXRT1060-EVK or MIMXRT1064-EVK: https://community.nxp.com/t5/i-MX-RT-Knowledge-Base/Using-J-Link-with-MIMXRT1060-EVK-or-MIMXRT1064-EVK/ta-p/1281149

.. _Using J-Link with MIMXRT1060-EVKB: https://community.nxp.com/t5/i-MX-RT-Knowledge-Base/Using-J-Link-with-MIMXRT1060-EVKB/ta-p/1452717