Issues debugging MIMXRT1050-EVK development board with QSPI Flash using MCUXpresso.

mike4 — Thu, 29 Nov 2018 19:25:34 GMT

We are using the MIMXRT1050-EVK (not EVKB) development board rev A1. Using MCUXpresso 10.2.1 with SDK 2.4.2 installed, we have been able to download the hello_word project (which is XIP) to the Hyperflash and boot from it successfully. We plan on using QSPI flash in our actual product so we are trying to do the same using the QSPI flash.

Following AN12183, we have removed the Hyperflash from the board and added the 0 Ohm resistors to R153 to R158. We have updated the DapLink firmware to k20dx_mimxrt1050_evk_qspi_if_crc_bin according to the directions. Question 1 – how do we know the firmware has updated correctly?

Under Project settings, we changed the Flash size to 0x800000 and the Flash driver to MIMXRT1050-EVK_IS25WP064A.cfx

Erasing the QSPI appears to work correctly as shown by the log at the end of this post:

However, when trying to program the QSPI flash by clickingg Debug in the Quickstart Menu we appear to get an error as can be seen in the programming log after the erase log. It seems to imply that the Flash programmed ok but was not able to boot. Did we need to modify the Boot Image to run from QSPI instead of the Hyperflash?

Erase Flash log:

Executing flash operation 'Erase' (Erase flash) - Tue Nov 27 16:09:16 EST 2018

Checking MCU info...

Scanning for targets...

Executing flash action...

MCUXpresso IDE RedlinkMulti Driver v10.2 (Jul 25 2018 11:25:37 - crt_emu_cm_redlink.exe build 555)

( 0) Reading remote configuration

Wc(03). No cache support.

Found chip XML file in C:/iMX1050RT/temp/evkimxrt1050_hello_world/Debug\MIMXRT1052xxxxB.xml

( 5) Remote configuration complete

Reconnected to existing link server

Connecting to probe 1 core 0:0 (using server started externally) gave 'OK'

Probe Firmware: DAPLink CMSIS-DAP (ARM)

Serial Number: 0227000032624e45003400197ece004e7e61000097969900

VID:PID: 0D28:0204

USB Path: \\?\hid#vid_0d28&pid_0204&mi_03#7&5d84601&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

Using memory from core 0:0 after searching for a good core

( 30) Emulator Connected

( 40) Debug Halt

( 50) CPU ID

debug interface type = Cortex-M7 (DAP DP ID 0BD11477) over SWD TAP 0

processor type = Cortex-M7 (CPU ID 00000C27) on DAP AP 0

number of h/w breakpoints = 8

number of flash patches = 0

number of h/w watchpoints = 4

Probe(0): Connected&Reset. DpID: 0BD11477. CpuID: 00000C27. Info: <None>

Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.

Content of CoreSight Debug ROM(s):

RBASE E00FD000: CID B105100D PID 000008E88C ROM dev (type 0x1)

ROM 1 E00FE000: CID B105100D PID 04000BB4C8 ROM dev (type 0x1)

ROM 2 E00FF000: CID B105100D PID 04000BB4C7 ROM dev (type 0x1)

ROM 3 E000E000: CID B105E00D PID 04000BB00C ChipIP dev SCS (type 0x0)

ROM 3 E0001000: CID B105E00D PID 04000BB002 ChipIP dev DWT (type 0x0)

ROM 3 E0002000: CID B105E00D PID 04000BB00E ChipIP dev (type 0x0)

ROM 3 E0000000: CID B105E00D PID 04000BB001 ChipIP dev ITM (type 0x0)

ROM 2 E0041000: CID B105900D PID 04001BB975 ARCH 23B:4A13r0 CoreSight dev type 0x13 Trace Source - core

ROM 2 E0042000: CID B105900D PID 04004BB906 CoreSight dev type 0x14 Debug Control - Trigger, e.g. ECT

ROM 1 E0040000: CID B105900D PID 04000BB9A9 CoreSight dev type 0x11 Trace Sink - TPIU

ROM 1 E0043000: CID B105F00D PID 04001BB101 System dev (type 0x0)

Inspected v.2 External Flash Device on SPI MIMXRT1050-EVK_IS25WP064A.cfx

Image 'MIMXRT1050-EVK_IS25WP064A Jul 25 2018 11:27:33'

Non-standard DAP stride detected - 1024 bytes

NXP: MIMXRT1052xxxxB

( 65) Chip Setup Complete

Connected: was_reset=false. was_stopped=false

( 70) License Check Complete

Opening flash driver MIMXRT1050-EVK_IS25WP064A.cfx

Sending VECTRESET to run flash driver

Mass Erase flash at 0x60000000

Closing flash driver MIMXRT1050-EVK_IS25WP064A.cfx

MassErase completed (in 16401ms)

Flash programming log:

Executing flash operation 'Program' (Program file into flash: evkimxrt1050_hello_world.axf) - Tue Nov 27 17:08:05 EST 2018