NXP MIMXRT1020-EVK
Overview
The i.MX RT1020 expands the i.MX RT crossover processor families by providing high-performance feature set in low-cost LQFP packages, further simplifying board design and layout for customers. The i.MX RT1020 runs on the Arm® Cortex®-M7 core at 500 MHz.
Hardware
MIMXRT1021DAG5A MCU
Memory
256 Mbit SDRAM
64 Mbit QSPI Flash
TF socket for SD card
Connectivity
10/100 Mbit/s Ethernet PHY
Micro USB host and OTG connectors
CAN transceivers
Arduino interface
Audio
Audio Codec
4-pole audio headphone jack
Microphone
External speaker connection
Power
5 V DC jack
Debug
JTAG 20-pin connector
OpenSDA with DAPLink
For more information about the MIMXRT1020 SoC and MIMXRT1020-EVK board, see these references:
External Memory
This platform has the following external memories:
Device |
Controller |
Status |
|---|---|---|
MT48LC16M16A2P |
SEMC |
Enabled via device configuration data block, which sets up SEMC at boot time |
IS25LP064A |
FLEXSPI |
Enabled via flash configurationn block, which sets up FLEXSPI at boot time |
Supported Features
The mimxrt1020_evk board configuration supports the hardware features listed below. For additional features not yet supported, please also refer to the NXP 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 mimxrt1020_evk board:
Interface |
Controller |
Driver/Component |
|---|---|---|
NVIC |
on-chip |
nested vector interrupt controller |
SYSTICK |
on-chip |
systick |
FLASH |
on-chip |
QSPI flash |
GPIO |
on-chip |
gpio |
SPI |
on-chip |
spi |
I2C |
on-chip |
i2c |
SDHC |
on-chip |
disk access |
UART |
on-chip |
serial port-polling; serial port-interrupt |
ENET |
on-chip |
ethernet |
USB |
on-chip |
USB device |
ADC |
on-chip |
adc |
GPT |
on-chip |
gpt |
TRNG |
on-chip |
entropy |
FLEXSPI |
on-chip |
flash programming |
The default configuration can be found in boards/nxp/mimxrt1020_evk/mimxrt1020_evk_defconfig
Other hardware features are not currently supported by the port.
Connections and I/Os
The MIMXRT1020 SoC has five pairs of pinmux/gpio controllers.
Name |
Function |
Usage |
|---|---|---|
GPIO_AD_B0_05 |
GPIO |
LED |
GPIO_AD_B0_06 |
LPUART1_TX |
UART Console |
GPIO_AD_B0_07 |
LPUART1_RX |
UART Console |
GPIO_AD_B1_08 |
LPUART2_TX |
UART BT HCI |
GPIO_AD_B1_09 |
LPUART2_RX |
UART BT HCI |
GPIO_AD_B1_14 |
LPI2C1_SCL |
I2C |
GPIO_AD_B1_15 |
LPI2C1_SDA |
I2C |
GPIO_SD_B1_02 |
LPI2C4_SCL |
I2C |
GPIO_SD_B1_03 |
LPI2C4_SDA |
I2C |
WAKEUP |
GPIO |
SW0 |
GPIO_AD_B0_04 |
ENET_RST |
Ethernet |
GPIO_AD_B0_08 |
ENET_REF_CLK |
Ethernet |
GPIO_AD_B0_09 |
ENET_RX_DATA01 |
Ethernet |
GPIO_AD_B0_10 |
ENET_RX_DATA00/LPSPI1_SCK | Ethernet/SPI |
|
GPIO_AD_B0_11 |
ENET_RX_EN/LPSPI1_PCS0 | Ethernet/SPI |
|
GPIO_AD_B0_12 |
ENET_RX_ER/LPSPI1_SDO | Ethernet/SPI |
|
GPIO_AD_B0_13 |
ENET_TX_EN/LPSPI1_SDI | Ethernet/SPI |
|
GPIO_AD_B0_14 |
ENET_TX_DATA00 |
Ethernet |
GPIO_AD_B0_15 |
ENET_TX_DATA01 |
Ethernet |
GPIO_AD_B1_06 |
ENET_INT |
Ethernet |
GPIO_EMC_41 |
ENET_MDC |
Ethernet |
GPIO_EMC_40 |
ENET_MDIO |
Ethernet |
GPIO_AD_B1_07 |
USDHC1_VSELECT |
SD Card |
GPIO_SD_B0_02 |
USDHC1_CMD |
SD Card |
GPIO_SD_B0_03 |
USDHC1_CLK |
SD Card |
GPIO_SD_B0_04 |
USDHC1_DATA0 |
SD Card |
GPIO_SD_B0_05 |
USDHC1_DATA1 |
SD Card |
GPIO_SD_B0_00 |
USDHC1_DATA2 |
SD Card |
GPIO_SD_B0_01 |
USDHC1_DATA3 |
SD Card |
GPIO_SD_B0_06 |
USDHC1_CD_B |
SD Card |
GPIO_AD_B1_10 |
ADC |
ADC1 Channel 10 |
GPIO_AD_B1_11 |
ADC |
ADC1 Channel 11 |
System Clock
The MIMXRT1020 SoC is configured to use SysTick as the system clock source, running at 500MHz.
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 MIMXRT1020 SoC has eight UARTs. LPUART1 is configured for the console,
LPUART2 for the Bluetooth Host Controller Interface (BT HCI), and the
remaining are not used.
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.
LinkServer Debug Host Tools (Default, Supported by NXP)
J-Link 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 RT1020, J47/J48 are the SWD isolation jumpers, J42 is the DFU mode jumper, and J16 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:
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
Follow the instructions provided at LPC-LINK2 CMSIS DAP Onboard Debug Probe to reprogram the default debug probe firmware on this board.
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:
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.
Follow the instructions provided at LPC-Link2 J-Link Onboard Debug Probe to reprogram the default debug probe firmware on this board.
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 J25 and J26 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 J23.
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 mimxrt1020_evk samples/hello_world
west flash
Open a serial terminal, reset the board (press the SW5 button), and you should see the following message in the terminal:
***** Booting Zephyr OS v1.14.0-rc1 *****
Hello World! mimxrt1020_evk
Debugging
Here is an example for the Hello World application.
# From the root of the zephyr repository
west build -b mimxrt1020_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 v1.14.0-rc1 *****
Hello World! mimxrt1020_evk