NXP i.MX RT1064 Eval Kit (MIMXRT1064-EVK)
This topic provides board-specific information about for NXP's i.MX RT1064 Evaluation Kit. Assuming that you have set up the development environment as per the intructions in getting started.
- MIMXRT1064DVL6A MCU featuring 600MHz ARM® Cortex®-M7 core, 4-MBytes Flash, 1024-kbytes RAM
- 4.3” 480x272 RGB Touch Display
- 256-Mbit SDRAM memory
- 512-Mbit Hyper Flash
- 64-Mbit QSPI Flash
- Socket for SD card
The reference port for this board supports 16bpp color depth. The board family supports 24bpp and 32bpp framebuffers, but the reference boards have only 16 lines physically connected to the LCD interface, so only 16 bpp is supported. See QUL_COLOR_DEPTH and Color depth for more information.
The package for
NXP i.MX RT1064 Eval Kit board comes with the following prebuilt demos and examples
You can find it in the
See Flashing Instructions for NXP boards section on how to flash the binaries to the board.
By default, the output of
printf calls are redirected to a virtual serial port, which is exposed on the host machine via USB.
- For convenience, you can set an environment variable that points to the Redlink tool, which is part of the MCUXpresso IDE.
MCUXPRESSO_IDE_PATHis an environment variable pointing to the MCUXpresso IDE installation directory.
- Open a terminal window and run the following command:
$REDLINK --server :50032 --mi -2 -vc -p MIMXRT1064xxxxA --ConnectScript RT1064_connect.scp --flash-driver= -x ./platform/boards/nxp/mimxrt1064-evk-common/cmake
%REDLINK% --server :50032 --mi -2 -vc -p MIMXRT1064xxxxA --ConnectScript RT1064_connect.scp --flash-driver= -x .\platform\boards\nxp\mimxrt1064-evk-common\cmake
GDB Server is now listening for TCP connections on port,
Note: To change TCP port used by
--server :50032to different value.
arm-none-eabi-gdbin a separate console
- Connect to the target via the gdbserver in the
(gdb) target remote :50032
- Alternatively, flash the target device from the
arm-none-eabi-gdbconsole using the following command:
- The interrupted program does not resume its execution while debugging. It must be restarted using the
mon reset haltcommand.
Available under certain Qt licenses.
Find out more.