NXP MIMXRT595 User Manual
NXP Semiconductors Document identifier: MIMXRT595EVKHUG
User's Guide Rev. 0, 02/2021
MIMXRT595 EVK Board Hardware User's
Guide
NXP Semiconductors
Contents
Chapter 1 Introduction........................................................................................... 3
Chapter 2 Getting started.......................................................................................6
Chapter 3 On-board (Link2) debug probe..............................................................8
Chapter 4 Board layout and settings....................................................................10
Chapter 5 Board power........................................................................................20
Chapter 6 Clock sources......................................................................................22
Chapter 7 External memory................................................................................. 23
Chapter 8 On-board peripherals.......................................................................... 26
Chapter 9 Expansion headers............................................................................. 29
Chapter 10 Known issues/errata for revision D................................................... 33
Chapter 11 Revision history.................................................................................34
MIMXRT595 EVK Board Hardware User's Guide, Rev. 0, 02/2021
User's Guide 2 / 35
NXP Semiconductors
Chapter 1
Introduction
This document is a Hardware User’s Guide for the MIMXRT595 Evaluation Kit (EVK) based on the NXP Semiconductor i.MX
RT595 Cortex-M33 core processor with Cadence Xtensa Fusion F1 DSP and Vivante GCNanoLite-V vector graphics core. This
board is fully supported by NXP Semiconductor. This Manual includes system setup, debugging information, and provides detailed
information on the overall design and usage of the EVK board from a hardware systems perspective.
1.1 Board overview
This EVK board is a platform designed to showcase many of the most commonly used features of the i.MX RT595 processor in
a small, low-cost package. The MIMXRT595 EVK board is an entry level development board, which gives option to developer
to becoming familiar with the processor before investing a large amount or resources in more specific designs. This document
describes revision D and D1 of the board with B2 silicon (SILICONREV_ID = 0x000B0002).
Features of the MIMXRT595 EVK board are shown below:
• MIMXRT595SFFOC device in 249 FOWLP soldered directly onto the PCB
• Independent voltage domains: VDD_CORE and VDDIO_n’s (0-4)
• 1.2 V, 1.8 V, and 3.3 V support for each voltage domain
• On-board 5 V inputs NXP PCA9420UK PMIC providing 1.2 V, 1.8 V, 3.3 V.
• Multiple power-supply schemes supported
• Jumpers to allow power source selection
• Jumpers for IDD measurement on VDD_CORE and VDDIO_n’s (0-4)
• VBAT coin cell battery holder
• Li-Ion battery header support
• High frequency crystal 24 MHz with compatible footprint
• Low-frequency crystal 32.768 kHz for RTC
• Octal/Quad/pSRAM external memories via FlexSPI
• One reset push button/bootloader selection
• Two push buttons for user input, including Interrupt (SW2) and NMI_b (SW3)
• One motion sensor combo accelero-/magneto-meter NXP FXOS8700CQ
• One RGB LED for user interface
• One Green LED for target MCU power status
• One Red LED for reset status
• One Orange LED for LPC-Link status
• USB2.0 high-speed host and device with micro USB connector and external crystal
• On-board eMMC chip
• Full-size SD card slot
• On-board, high-speed USB, Link2 debug probe with CMSIS-DAP protocol (supports Cortex-M33 debug only) circuit based
on LPC4322 MCU
• Optional external debug probe connections with trace option (10 pin or 20 pin Cortex-M connectors, later required for
trace)
MIMXRT595 EVK Board Hardware User's Guide, Rev. 0, 02/2021
User's Guide 3 / 35
NXP Semiconductors
• Single row headers for ARDUINO signals
• MikroBus connector
• FlexIO connector for MikroElektronica TFT Proto 5” capacitive touch display
• Pmod/host expansion connector
• MIPI-DSI connector
• M.2 mini card connector
• Stereo audio codec with line-In/ line-Out/ and Microphone
• NXP TFA9896 audio digital amplifier
• Support for up to 8, off-board digital microphones via 12-pin header
• Two on-board digital microphones
1.2 MIMXRT595 EVK contents
The MIMXRT595 EVK contains the following items:
• MIMXRT595 EVK board
• USB cable (Micro B)
Introduction
• Quick start guide
MIMXRT595 EVK Board Hardware User's Guide, Rev. 0, 02/2021
User's Guide 4 / 35
NXP Semiconductors
Introduction
Figure 1. i.MX RT595 board
1.3 MIMXRT595 EVK board revision history
• Rev D
• Rev D1
MIMXRT595 EVK Board Hardware User's Guide, Rev. 0, 02/2021
User's Guide 5 / 35
NXP Semiconductors
Chapter 2
Getting started
This section describes how to power up the board and also how to start a first debug session using the MCUXpresso SDK. The
board is pre-programmed with a program indicating that the target MCU is running. Connect a micro USB cable from connector
J40 (LINK USB) to a host computer or supply to power up the board and run this program.
The following debug probes can be used with the board:
• On-board debug probe (LPC4322 Link2), Cortex® M33 only.
• SEGGER J-link probes (version 9 or newer).
Other debug probes may also be supported by IAR and Keil tools and by other IDEs/debug tools. See third-party websites for
further information.
2.1 Starting a debug session using on-board (Link2) Debug Probe
By default, the i.MX RT595 EVK is configured to use the on-board Debug Probe (Link2) via J40 to debug the on-board target (i.MX
RT595), using the CMSIS-DAP debug protocol pre-programmed into the Link2 Flash memory. When connecting the USB cable,
this powers the board and you see that a virtual COM port enumerates.
When using the MCUXpresso IDE, the on-board Link2 can also be booted in the DFU mode (see jumper settings). If this is
done, MCUXpresso IDE downloads CMSIS-DAP to the probe as needed. Using the DFU boot mode, ensure that the most
up-to-date/compatible firmware image is used with MCUXpresso IDE.
The IAR IDE or other development tools that support the CMSIS-DAP protocol can be used in the default configuration (once
support is released for those tools). Check with your toolchain vendor for availability of specific device support packs for the i.MX
RT595 series devices.
NOTE
If the Debug Probe is set up to boot in DFU mode, the USB bridge functions (virtual COM port) and Debug Probe
features will not be available if the board is not first initialized by the MCUXpresso IDE.
2.2 Download and install the MCUXpresso SDK
In order to download the RT500 SDK, visit the MCUXpresso SDK Builder site.
• Go to https://mcuxpresso.nxp.com
• Make sure to log in with NXP account
• Click select development board
• Type in “EVK-MIMXRT595”
• Add desired software components
• Now, download SDK
2.3 Installation steps to use with MCUXpresso IDE
1. Download and install the MCUXpresso IDE v11.3 or latest.
2. Install the RT500 SDK zip package.
3. Install JP1 to force the Link2 Debug Probe to boot in DFU mode.
MIMXRT595 EVK Board Hardware User's Guide, Rev. 0, 02/2021
User's Guide 6 / 35
NXP Semiconductors
Getting started
NOTE
If the Debug Probe is set up to boot in DFU mode, the USB bridge functions (virtual COM port) and Debug Probe
features will not be available if the board is not first initialized by the MCUXpresso IDE.
4. Ensure that:
• The jumper JP2 is fitted in position 1-2, local target powered.
• The jumper JP3 is not installed.
5. Connect the board to the USB port of your host computer, connecting a micro USB cable to connector J40 (Link USB).
6. Allow about 10 seconds for the i.MX RT595 EVK device to enumerate for the first time. The device will appear as
LPC-Link2 UCom Port.
Now you can use the MCUXpresso IDE to run the various SDK examples. If the first attempt to debug a project fails in the IDE,
cancel the debug session and repower the board. On some machines the drivers take longer to enumerate for the first time, so
these steps should correct the issue.
2.4 Installation steps to use Keil and IAR tools
1. Download and install LPCScrypt for LPCXpresso boards (http://www.nxp.com/lpcutilities). This installs required drivers
for the board.
NOTE
The Link2 (LPC4322 device) is pre-programmed with CMSIS-DAP firmware during manufacture, so you do not
need to program it.
2. Ensure that JP1 is open to force the Link2 Debug Probe to boot from internal flash.
3. Ensure that jumper JP2 is fitted in position 1-2, and JP3 is not installed. These are the default position set during board
manufacture.
4. Connect the i.MX RT595 board to the USB port of your host computer, connecting a micro USB cable to connector J40
(Link USB). Allow about 10 seconds for the Link2 devices to enumerate for the first time. It is not necessary to check the
Hardware Manager.
Your board is now ready to use with your third-party tool. Follow the instructions for those tools for using a CMSIS-DAP probe.
MCUXpresso IDE can also be used with the board after setting up the board this way.
Now, you can use the Keil/IAR IDE to run the various SDK examples.
NOTE
If using IAR, use v8.50.9 or latest. If using Keil, use v.5.33 or latest.
2.5 Starting a debug session using external Debug Probe
The i.MX RT595 target can also be programmed and debugged using an external Debug Probe that conforms to the standard
Arm® Cortex-M debug connectors (either with 10 pin or 20 pin). To use an external Debug Probe, connect the probe to one of the
SWD connectors (J2 or J19) and connect power via the micro USB connector J39.
MIMXRT595 EVK Board Hardware User's Guide, Rev. 0, 02/2021
User's Guide 7 / 35
NXP Semiconductors
Chapter 3
On-board (Link2) debug probe
This section describes the features provided by the on-board Link2 Debug Probe, including how to use this to debug an
external target.
The Link2 Debug Probe is implemented using an LPC43xx MCU, which provides a high-speed USB port interface to the
host computer that runs the development tools. This device is not intended for developer use, and should only be used with
approved firmware images from NXP. The Link2 on-chip flash memory is factory programmed with a firmware image that supports
CMSIS-DAP debug protocol, but also includes other USB end-point functions.
• Virtual COM (VCOM) port: a serial device that can be used with any host computer application design for serial port
communication (for example, Teraterm, puTTY). Set the terminal program for baud rate to 115200, no parity, 8-bit data, 1
stop bit, no flow control.
• SWO trace end point: this virtual device is used by MCUXpresso to retrieve SWO trace data. See the MCUXpresso IDE
documentation for more information.
All of these devices are independent of each other and of the CMSIS-DAP debug device that is enumerated when the board is
connected to a host computer; for example, the VCOM port can be used if the board is running an application when no debugger
is running.
In order to correctly install and use the Link2 device on the i.MX RT595 EVK (required for any debugging purpose) for Windows 7
or 8 host computers, install the drivers first. These drivers will automatically be installed when MCUXpresso IDE has already been
installed. If these IDEs are not being used, it is recommended LPCScrypt be installed as this also includes the required drivers.
All these tools and utilities are available for free download at https://www.nxp.com/lpcscrypt.
The CMSIS-DAP firmware image installed at the factory (and by LPCScrypt) will uniquely identify itself to the host computer so
that more than one board can be connected to that host computer at any time. Some toolchains cannot discern between multiple
debug devices, see your toolchain documentation for more information.
NOTE
MCUXpresso does support multiple LPCXpresso board targets.
It is strongly recommended that LPCScrypt be used to update the Debug Probe firmware in order to ensure that the latest version
is being used.
NOTE
The Link2 only boots when the board is power cycled; the reset button on the board does not reset the Link2.
When using MCUXpresso IDE, the Link2 can be automatically booted with the latest / most appropriate firmware for that IDE
version by installing JP1 DFU jumper before powering up the board. This is the recommended approach for the MCUXpresso IDE.
NOTE
If JP1 is installed when powering the board, then the VCOM port (and other devices mentioned above) device will
not appear until the MCUXpresso IDE boots the Debug Probe. The Debug Probe is booted once a debug session
is started (that is, the IDE attempts to download code to the target).
3.1 Programming the Link2 firmware
As mentioned earlier in this section, it is not normally necessary to program the Link2 firmware. However, this can easily be
accomplished using the supporting utility, LPCScrypt.
To program the Link2 flash, the Link2 device (LPC432x) must be in DFU mode. If the Link2 already has a valid image in the flash, it
needs to be forced into DFU mode by placing a jumper shunt on JP1, and power cycling (disconnecting then reconnecting power).
Link2 MCU programming is performed using the LPCScrypt utility (see http://www.nxp.com/lpcscrypt). Instructions for using the
tool are located at the same webpage. You can also check the instructions in the RT500 Get Started Guide.
MIMXRT595 EVK Board Hardware User's Guide, Rev. 0, 02/2021
User's Guide 8 / 35
NXP Semiconductors
On-board (Link2) debug probe
3.2 VCOM port
The identifier of the VCOM port varies between boards and hosts as each board enumerate with a unique identifier. On Windows
OS, to determine the COM port, open the Windows operating system Device Manager. This can be achieved by going to the
Windows operating system click on
“Ports”; the LPC-LinkII UCom Port device and its name should be visible.
This VCOM port will only appear:
• If the Debug Probe has been programmed with the CMSIS-DAP firmware and the Debug Probe DFU link (JP1)
is removed at power-up.
• If the Debug Probe has been configured for DFU boot (JP1) installed at power-up and MCUXpresso IDE has
booted it (by starting a debug session).
Start menu
and typing
Device Manager
NOTE
in the search bar. In the device manager look under
MIMXRT595 EVK Board Hardware User's Guide, Rev. 0, 02/2021
User's Guide 9 / 35
NXP Semiconductors
Chapter 4
Board layout and settings
This chapter describes the i.MXRT595-EVK layout, including a description of the jumpers and headers on the board.
Figure 2. i.MX RT595 EVK's block diagram
MIMXRT595 EVK Board Hardware User's Guide, Rev. 0, 02/2021
User's Guide 10 / 35
NXP Semiconductors
Board layout and settings
Figure 3. MIMXRT595 EVK board. Components, LEDs, and buttons
Table 1. i.MX RT595 EVK components
Index Circuit
Default Description Reference
Ref.
1 BT3 N/A Coin battery holder. Li-Ion Battery
2 D19 N/A User RGB LED. User LEDs
3 J3 N/A Audio codec line input jack Schematic
4 J4 N/A Audio codec line output jack Schematic
5 J11, J46 N/A Screw terminal connections for external
Schematic
speakers. When attaching a speaker, ensure
that the appropriate driver settings are used
in the TFA9894 devices to avoid damage to
the speaker
Table continues on the next page...
MIMXRT595 EVK Board Hardware User's Guide, Rev. 0, 02/2021
User's Guide 11 / 35
Loading...