topic Re: Writing QSPI Flash on MCXN947 board. in MCX Microcontrollers

Writing QSPI Flash on MCXN947 board.

takagi_y — Wed, 05 Mar 2025 05:44:19 GMT

The other day I asked a question about writing flash to FRDM-MCXN947.

Thanks to your answer, I am now able to write to FRDM-MCXN947.

Thank you.

This time I would like to ask a question about writing flash to another board using MCXN947.

I tried to write to this board using the writing method for FRDM-MCXN947 as a reference, but an error occurred.

Below is the content of the console at that time.

NXP: MCXN947
DAP stride is 1024 bytes (256 words)
Inspected v.2 External Flash Device on SPI using SFDP JEDEC ID MCXN9xx_SFDP_FlexSPI.cfx
Image 'MCXN9xx_SFDP_FlexSPI Sep 19 2024 18:18:31'
Opening flash driver MCXN9xx_SFDP_FlexSPI.cfx
VECTRESET requested, but not supported on ARMv8-M CPUs. Using SOFTRESET instead.
Using SOFT reset to run the flash driver
Driver V.2 dynamic startup failed - driver Init provided no flash parameters
driver describes no sectors starting at 0x80000000
Flash Driver V.2 startup failed - rc Ef(58): Flash Driver describes no sectors at its base address
chip initialization failed - Ef(58): Flash Driver describes no sectors at its base address
failed to initialize flash driver MCXN9xx_SFDP_FlexSPI.cfx
Inspected v.2 External Flash Device on SPI using SFDP JEDEC ID MCXN9xx_SFDP_FlexSPI.cfx
Image 'MCXN9xx_SFDP_FlexSPI Sep 19 2024 18:18:31'
Opening flash driver MCXN9xx_SFDP_FlexSPI.cfx
VECTRESET requested, but not supported on ARMv8-M CPUs. Using SOFTRESET instead.
Using SOFT reset to run the flash driver
Driver V.2 dynamic startup failed - driver Init provided no flash parameters
driver describes no sectors starting at 0x80000000
Flash Driver V.2 startup failed - rc Ef(58): Flash Driver describes no sectors at its base address
chip initialization failed - Ef(58): Flash Driver describes no sectors at its base address
failed to initialize flash driver MCXN9xx_SFDP_FlexSPI.cfx

Is there any setting or anything I need to do?

I would appreciate your reply.

Re: Writing QSPI Flash on MCXN947 board.

takagi_y — Wed, 05 Mar 2025 10:20:57 GMT

As additional information, we would like to inform you of what we did to implement XIP processing from the demo project you contacted us about to the project for this board.

- Copy the following files.
source\mcxn_flexspi_nor_config.c
source\mcxn_flexspi_nor_config.h
linkscripts\rodata.ldt
linkscripts\text.ldt

- Rewrite to "bootfromflexspi.bin" using blhost.

- Change the settings of the Memory Configuration editor.

I would appreciate your reply.

Best regards

Re: Writing QSPI Flash on MCXN947 board.

Harry_Zhang — Thu, 06 Mar 2025 06:24:42 GMT

HI @takagi_y

"I tried to write to this board using the writing method for FRDM-MCXN947 as a reference, but an error occurred."

You change to another board.

Did you try the same method but not succeed？

Harry

Re: Writing QSPI Flash on MCXN947 board.

takagi_y — Thu, 06 Mar 2025 09:50:05 GMT

Thank you for your reply.

I modified the project with reference to the demo program of FRDM-MCXN947 and confirmed writing from IDE.
The procedure is as written yesterday under "As additional information...".

My board uses MX25L3233F for Flash, so I built an example of CMSIS-DAP Flash Drivers and checked it.

First, I used the one I built without any modifications and wrote it from the IDE. (CONFIG_OPTION0=0xC0000001)
As a result, the following was displayed on the console and writing was not performed.

MCUXpresso IDE RedlinkMulti Driver v24.9 (Sep 19 2024 19:34:05 - crt_emu_cm_redlink build 802)

Found chip XML file in C:/WorkSpace/MCUX/MCUXpressoIDE_24.9.25/NX-N947/frdmmcxn947_hello_world_qspi_xip/Debug\MCXN947.xml

( 5) Remote configuration complete

Reconnected to existing LinkServer process.

Probe Firmware: MCU-LINK (r0FF) CMSIS-DAP V3.153 (NXP Semiconductors)

Serial Number: VUDADS0NIE0ZM

VID:PID: 1FC9:0143

USB Path: 0001:0008:00

Using memory from core 0 after searching for a good core

processor is in secure mode

debug interface type = CoreSight DP (DAP DP ID 6BA02477) over SWD TAP 0

processor type = Cortex-M33 (CPU ID 00000D21) 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: 6BA02477. CpuID: 00000D21. Info: <None>

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

Content of CoreSight Debug ROM(s):

RBASE E00FE000: CID B105100D PID 0000095000 ROM (type 0x1)

ROM 1 E00FF000: CID B105100D PID 04000BB4C9 ROM (type 0x1)

ROM 2 E000E000: CID B105900D PID 04000BBD21 CSt ARM ARMv8-M type 0x0 Misc - Undefined

ROM 2 E0001000: CID B105900D PID 04000BBD21 CSt ARM DWTv2 type 0x0 Misc - Undefined

ROM 2 E0002000: CID B105900D PID 04000BBD21 CSt ARM FPBv2 type 0x0 Misc - Undefined

ROM 2 E0000000: CID B105900D PID 04000BBD21 CSt ARM ITMv2 type 0x43 Trace Source - Bus

ROM 2 E0041000: CID B105900D PID 04002BBD21 CSt ARM ETMv4.0 type 0x13 Trace Source - Core

ROM 2 E0042000: CID B105900D PID 04000BBD21 CSt ARM CTIv2 type 0x14 Debug Control - Trigger, e.g. ECT

ROM 1 E0040000: CID B105900D PID 04000BBD21 CSt type 0x11 Trace Sink - TPIU

ROM 1 E0044000: CID B105900D PID 04003BB908 CSt CSTF type 0x12 Trace Link - Trace funnel/router

ROM 1 E0045000: CID B105900D PID 04001BB961 CSt type 0x21 Trace Sink - ETB

NXP: MCXN947

DAP stride is 1024 bytes (256 words)

Inspected v.2 External Flash Device on SPI using SFDP JEDEC ID MCXN9xx_SFDP_FlexSPI_.cfx

Image 'MCXN9xx_SFDP_FlexSPI Mar 6 2025 17:01:24'

Opening flash driver MCXN9xx_SFDP_FlexSPI_.cfx

VECTRESET requested, but not supported on ARMv8-M CPUs. Using SOFTRESET instead.

Using SOFT reset to run the flash driver

Flash variant 'JEDEC_FlexSPI_Device' detected (0B = at 0x80000000)

driver describes no sectors starting at 0x80000000

Flash Driver V.2 startup failed - rc Ef(58): Flash Driver describes no sectors at its base address

chip initialization failed - Ef(58): Flash Driver describes no sectors at its base address

failed to initialize flash driver MCXN9xx_SFDP_FlexSPI_.cfx

Inspected v.2 External Flash Device on SPI using SFDP JEDEC ID MCXN9xx_SFDP_FlexSPI_.cfx

Image 'MCXN9xx_SFDP_FlexSPI Mar 6 2025 17:01:24'

Opening flash driver MCXN9xx_SFDP_FlexSPI_.cfx

VECTRESET requested, but not supported on ARMv8-M CPUs. Using SOFTRESET instead.

Using SOFT reset to run the flash driver

Flash variant 'JEDEC_FlexSPI_Device' detected (4MB = 64*64K at 0x80000000)

Closing flash driver MCXN9xx_SFDP_FlexSPI_.cfx

Next, I changed the setting value used in the SEC tool (CONFIG_OPTION0=0xC0000405) and checked, but writing was not performed here either.
(You can write with the SEC tool.)
The following is the console display at that time.

MCUXpresso IDE RedlinkMulti Driver v24.9 (Sep 19 2024 19:34:05 - crt_emu_cm_redlink build 802)

Found chip XML file in C:/WorkSpace/MCUX/MCUXpressoIDE_24.9.25/NX-N947/NX-N947_ledblinky/frdmmcxn947_led_blinky/Debug_NoRAM\MCXN947.xml

( 5) Remote configuration complete

Reconnected to existing LinkServer process.

Probe Firmware: MCU-LINK (r0FF) CMSIS-DAP V3.153 (NXP Semiconductors)

Serial Number: VUDADS0NIE0ZM

VID:PID: 1FC9:0143

USB Path: 0001:0008:00

Using memory from core 0 after searching for a good core

( 30) Emulator Connected