Issue Programming External NOR Flash on Custom i.MX RT1062 Board

Kesavan

Problem Description

I am working with a custom board based on the NXP i.MX RT1062, and I am facing issues while programming the external QSPI NOR flash.

I am attempting to flash the application using J-Link through JTAG, but the programming process fails. The debugger is able to connect to the target, and the core is detected correctly; however, the external flash is not being programmed.

Setup Details

MCU: NXP i.MX RT1062
External Flash: QSPI NOR Flash (part number: 25LP-WP256E or equivalent)
Debugger: SEGGER J-Link
IDE / Tools: MCUXpresso IDE / J-Link Commander
Boot Mode: FlexSPI NOR boot
Board Type: Custom hardware (not an evaluation board)

Observed Behavior

J-Link successfully connects to the RT1062.
Flash programming fails or hangs when attempting to write to external NOR flash.

mayliu1

Hi @Kesavan ,

Thank you so much for your interest in our products and for using our community.

1: Please check the hardware design, especially the DQS pin connection(for high-speed operation, DQS should float).

and also double-check the Boot Mode and Boot Config pins settings.

2: Please test that the binary is a valid FlexSPI NOR boot image, and it contains the required boot header information, including the FCB and IVT .

Please also make sure that the flexspi_nor_config_t (FCB) matches the external QSPI NOR flash device, and that the flash programming algorithm/loader is for the correct flash device.

Please refer to this application note for more detail information:

https://www.nxp.com/docs/en/nxp/application-notes/AN12183.pdf

Wish it helps you

Best Regards

May Liu

Kesavan

Hi @May_Liu and @Kesavan,

Thank you very much for your detailed response and for sharing the reference application note.

Please find our observations and follow‑up below:

Hardware Design (DQS, Boot Mode & Boot Config Pins)

The external QSPI NOR flash used on our custom board is IS25LP256E (QuadSPI NOR, 3.3 V).
For the QSPI NOR interface, DQS is not required.
However, on our board, the FlexSPI DQS pin is currently repurposed and connected for ADC functionality.
The FlexSPI signals (CLK, CS, D0–D3) are routed according to the i.MX RT1062 reference design.
BOOT_MODE[1:0] and BT_CFG[0…11] pins are correctly configured for FlexSPI1 Serial NOR boot, and this configuration is documented in the boot fuse map section of our schematic.

We would appreciate your confirmation on whether repurposing the FlexSPI DQS pin for ADC use could potentially impact FlexSPI NOR operation or flash programming on RT1062.

FlexSPI NOR Boot Image Verification

The binary being programmed is intended as a FlexSPI NOR boot image, with the following characteristics:

It includes the required Flash Configuration Block (FCB) and Image Vector Table (IVT).
The flexspi_nor_config_t (FCB) parameters are configured according to the IS25LP256E datasheet.

To ensure we are validating this correctly on our side, could you please advise on the recommended method or tool to explicitly verify that a binary is a valid FlexSPI NOR boot image, particularly with respect to correct FCB and IVT placement and format?

For example:

Is verifying the FCB at offset 0x400 and IVT at offset 0x1000 sufficient?
Is there a preferred NXP tool or method (e.g., MCUXpresso, blhost, elftosb, or ROM diagnostics) to perform this validation more formally?

Thank you again for your support and guidance.
We look forward to your clarification.

Best regards,
Kesavan

mayliu1

Hi @Kesavan ,

Thanks for your updated information.

1: your understanding about DQS pin is not correct.

Please refer to RT1060 data sheet.

If you want your Flash run at a High frequency, you need leave DQS pin float.

Please refer to this link.

【新提醒】iMX RT 系列中 FlexSPI DQS 信号引脚配置GPIO 方法 - i.MX RT - 恩智浦技术社区

2: I suggest you use SEC tool to test your Flash first.

https://www.nxp.com/design/design-center/software/development-software/mcuxpresso-software-and-tools...

a. Set your board as serial download mode.

b. Create a new workspace for RT1060, connect your board with LPUART1 or USB1 to the PC.

c. set Boot Memory Configuration, select your Flash type, then Test Connection.

Wish it helps you

Best Regards

May Liu

Kesavan

We have tried using the MCUBootUtility tool. We are able to successfully connect to the flashloader, but after that, when it is expected to switch to boot device mode, it does not proceed further and instead reports the error “failed to configure external memory.”

We have attached a screenshot of the error message for your reference.

Additionally, please note that on our custom board, we are not using the default QSPI/FlexSPI pin configuration. The FlexSPI signals are routed to different pins on our hardware. We have attached the detailed pin‑mapping information for reference.

Could you please advise whether any additional configuration or changes are required when using non‑default QSPI/FlexSPI pins, to ensure successful external flash detection during the boot utility flow?

we have attached images for your reference

mayliu1

Please try the settings shown in the image below.