boards/nxp/mimxrt595_evk/doc/index.rst
.. zephyr:board:: mimxrt595_evk
Overview
i.MX RT500 crossover MCUs are part of the edge computing family and are optimized for low-power HMI applications by combining a graphics engine and a streamlined Cadence Tensilica Fusion F1 DSP core with a next-generation Arm Cortex-M33 core. These devices are designed to unlock the potential of display-based applications with a secure, power-optimized embedded processor.
i.MX RT500 MCUs provides up to 5MB of on-chip SRAM and several high-bandwidth interfaces to access off-chip flash, including an Octal/Quad SPI interface with an on-the-fly decryption engine.
Hardware
For more information about the MIMXRT595 SoC and MIMXRT595-EVK board, see these references:
i.MX RT595 Website_i.MX RT595 Datasheet_i.MX RT595 Reference Manual_MIMXRT595-EVK Website_MIMXRT595-EVK User Guide_MIMXRT595-EVK Schematics_MIMXRT595-EVK Debug Firmware_NXP considers the MIMXRT595-EVK as a superset board for the i.MX RT5xx
family of MCUs. This board is a focus for NXP's Full Platform Support for
Zephyr, to better enable the entire RT5xx family. NXP prioritizes enabling
this board with new support for Zephyr features. Another very similar
board is the :zephyr:board:mimxrt685_evk, and that board may have additional features
already supported, which can also be re-used on this mimxrt595_evk board.
.. zephyr:board-supported-hw::
Some features in the table above are tested with Zephyr shields. These shields are tested on this board:
rk055hdmipi4m, :ref:rk055hdmipi4ma0 and :ref:g1120b0mipi - support
the MIPI-DSI display interface.The MIMXRT595 SoC has IOCON registers, which can be used to configure the functionality of a pin.
+---------+-----------------+----------------------------+ | Name | Function | Usage | +=========+=================+============================+ | PIO0_2 | USART0 | USART RX | +---------+-----------------+----------------------------+ | PIO0_1 | USART0 | USART TX | +---------+-----------------+----------------------------+ | PIO0_14 | GPIO | GREEN LED | +---------+-----------------+----------------------------+ | PIO0_25 | GPIO | SW0 | +---------+-----------------+----------------------------+ | PIO0_10 | GPIO | SW1 | +---------+-----------------+----------------------------+ | PIO4_30 | USART12 | USART TX | +---------+-----------------+----------------------------+ | PIO4_31 | USART12 | USART RX | +---------+-----------------+----------------------------+ | PIO0_29 | I2C | I2C SCL | +---------+-----------------+----------------------------+ | PIO0_30 | I2C | I2C SDA | +---------+-----------------+----------------------------+ | PIO0_22 | GPIO | FXOS8700 TRIGGER | +---------+-----------------+----------------------------+ | PIO1_5 | SPI | SPI MOSI | +---------+-----------------+----------------------------+ | PIO1_4 | SPI | SPI MISO | +---------+-----------------+----------------------------+ | PIO1_3 | SPI | SPI SCK | +---------+-----------------+----------------------------+ | PIO1_6 | SPI | SPI SSEL | +---------+-----------------+----------------------------+ | PIO0_5 | SCT0 | SCT0 GPI0 | +---------+-----------------+----------------------------+ | PIO0_6 | SCT0 | SCT0 GPI1 | +---------+-----------------+----------------------------+
The MIMXRT595 EVK is configured to use the OS Event timer as a source for the system clock.
The MIMXRT595 SoC has 13 FLEXCOMM interfaces for serial communication. One is configured as USART for the console and the remaining are not used.
You can build a Zephyr application for the RT500 DSP core by targeting the F1 SOC. Xtensa toolchain supporting RT500 DSP core is included in Zephyr SDK. To build the hello_world sample for the RT500 DSP core:
.. code-block:: shell
$ west build -b mimxrt595_evk/mimxrt595s/f1 samples/hello_world
For detailed instructions on how to debug DSP firmware, please refer to
this document: Getting Started with Xplorer for EVK-MIMXRT595_
Programming and Debugging
.. zephyr:board-supported-runners::
Build and flash applications as usual (see :ref:build_an_application and
:ref:application_run for more details).
A debug probe is used for both flashing and debugging the board. This board is configured by default to use the LPC-Link2.
.. tabs::
.. group-tab:: LPCLink2 JLink Onboard
1. Install the :ref:`jlink-debug-host-tools` and make sure they are in your search path.
2. To connect the SWD signals to onboard debug circuit, install jumpers JP17, JP18 and JP19,
if not already done (these jumpers are installed by default).
3. Follow the instructions in :ref:`lpclink2-jlink-onboard-debug-probe` to program the
J-Link firmware. Please make sure you have the latest firmware for this board.
.. group-tab:: JLink External
1. Install the :ref:`jlink-debug-host-tools` and make sure they are in your search path.
2. To disconnect the SWD signals from onboard debug circuit, **remove** jumpers J17, J18,
and J19 (these are installed by default).
3. Connect the J-Link probe to J2 10-pin header.
See :ref:`jlink-external-debug-probe` for more information.
.. group-tab:: Linkserver
1. Install the :ref:`linkserver-debug-host-tools` and make sure they are in your search path.
2. To update the debug firmware, please follow the instructions on `MIMXRT595-EVK Debug Firmware`
Connect a USB cable from your PC to J40, and use the serial terminal of your choice (minicom, putty, etc.) with the following settings:
Here is an example for the :zephyr:code-sample:hello_world application. This example uses the
:ref:jlink-debug-host-tools as default.
.. zephyr-app-commands:: :zephyr-app: samples/hello_world :board: mimxrt595_evk/mimxrt595s/cm33 :goals: flash
Open a serial terminal, reset the board (press the RESET button), and you should see the following message in the terminal:
.. code-block:: console
*** Booting Zephyr OS v2.7 *** Hello World! mimxrt595_evk
Here is an example for the :zephyr:code-sample:hello_world application. This example uses the
:ref:jlink-debug-host-tools as default.
.. zephyr-app-commands:: :zephyr-app: samples/hello_world :board: mimxrt595_evk/mimxrt595s/cm33 :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 v2.7 *** Hello World! mimxrt595_evk
If the debug probe fails to connect with the following error, it's possible that the image in flash is interfering and causing this issue.
.. 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 flash with the following steps:
#. Set the SW7 DIP switches to ON-ON-ON to prevent booting from flash.
#. Reset by pressing SW3
#. Run west debug or west flash again with a known working Zephyr
application (example "Hello World").
#. Set the SW5 DIP switches to OFF-OFF-ON to boot from flash.
#. Reset by pressing SW3
.. include:: ../../common/board-footer.rst.inc
.. _MIMXRT595-EVK Website: https://www.nxp.com/design/development-boards/i-mx-evaluation-and-development-boards/i-mx-rt595-evaluation-kit:MIMXRT595-EVK
.. _MIMXRT595-EVK User Guide: https://www.nxp.com/webapp/Download?colCode=MIMXRT595EVKHUG
.. _MIMXRT595-EVK Debug Firmware: https://www.nxp.com/docs/en/application-note/AN13206.pdf
.. _MIMXRT595-EVK Schematics: https://www.nxp.com/downloads/en/schematics/MIMXRT595-EVK-DESIGN-FILES.zip
.. _i.MX RT595 Website: https://www.nxp.com/products/processors-and-microcontrollers/arm-microcontrollers/i-mx-rt-crossover-mcus/i-mx-rt500-crossover-mcu-with-arm-cortex-m33-dsp-and-gpu-cores:i.MX-RT500
.. _i.MX RT595 Datasheet: https://www.nxp.com/docs/en/data-sheet/IMXRT500EC.pdf
.. _i.MX RT595 Reference Manual: https://www.nxp.com/webapp/Download?colCode=IMXRT500RM
.. _Getting Started with Xplorer for EVK-MIMXRT595: https://www.nxp.com/docs/en/supporting-information/GSXEVKMIMXRT595.pdf