This topic provides board-specific information about for NXP's i.MX RT1060 Evaluation Kit. Assuming that you have set up the development environment as per the intructions in getting started.

Board features

• MIMXRT1062DVL6A MCU featuring 600MHz ARM® Cortex®-M7 core, 4-MBytes Flash, 1024-kbytes RAM
• 4.3" 480x272 16-bit RGB565 Touch Display
• 256-Mbit SDRAM memory
• 512-Mbit Hyper Flash
• 64-Mbit QSPI Flash
• Socket for SD card

Prebuilt demos and examples

The package for NXP i.MX RT1060 Eval Kit board comes with the following prebuilt demos and examples

• BareMetal
  • thermo

You can find it in the demos_images directory.

See the Flashing Instructions for NXP boards section on how to flash the binaries to the board.

Reading debug messages

By default, the output of printf calls are redirected to a virtual serial port, which is exposed on the host machine via USB.

Debugging

• For convenience, you can set an environment variable that points to the Redlink tool, which is part of the MCUXpresso IDE.

  Linux host:

  export REDLINK=$MCUXpressoIDE_PATH/ide/binaries/crt_emu_cm_redlink

  Windows host:

  set REDLINK=%MCUXpressoIDE_PATH%\ide\binaries\crt_emu_cm_redlink

  Where, MCUXpressoIDE_PATH is an environment variable pointing to the MCUXpresso IDE installation directory.

• Open a terminal window and run the following command:

  Linux host:

  $REDLINK --server :50032 --mi -2 -vc -p MIMXRT1062xxxxA --ConnectScript RT1060_connect.scp --flash-driver= -x $Qul_DIR/platform/boards/nxp/mimxrt1060-evk-baremetal/cmake

  Windows host:

  %REDLINK% --server :50032 --mi -2 -vc -p MIMXRT1062xxxxA --ConnectScript RT1060_connect.scp --flash-driver= -x %Qul_DIR%\platform\boards\nxp\mimxrt1060-evk-baremetal\cmake

  GDB Server is now listening for TCP connections on port, 50032.

  Note: To change TCP port used by redlink_server, change --server :50032 to different value.

• Run arm-none-eabi-gdb in a separate console

  Linux host:

  $ARMGCC_DIR/bin/arm-none-eabi-gdb.exe <PATH_TO>/your_app.elf

  Windows host:

  %ARMGCC_DIR%\bin\arm-none-eabi-gdb.exe <PATH_TO>\your_app.elf

• Connect to the target via the gdbserver in the arm-none-eabi-gdb console using

  (gdb) target remote :50032

• Alternatively, flash the target device from the arm-none-eabi-gdb console using the following command:

  (gdb) load

Known issues

• The interrupted program does not resume its execution while debugging. It must be restarted using the mon reset halt command.