Sample code to interface Hyper Flash in our custom board with MCXN947 MCU

[Ramadurai]

We require library code for interfacing Hyper Flash with MCXN947 MCU in our custom board.

I could find the sample code “frdmmcxn947_flexspi_octal_polling_transfer_cm33_core0” for Octal Flash in SDK for EVB FRDMFRDM-MCXN947.

Please share the library code for interfacing HyperFlash through FlexSPI in ##MCXN94

[Harry_Zhang]

Hi @Ramadurai 

May I ask what model of Hyper Flash you are using？

BR

Harry

[Ramadurai]

Infineon make Hyper flash Part S26KL128SDABHI020 is used in our custom board and interfaced through FlexSPI Port A. But why the make is so important?

Irrespective of the flash make, the source code of the Hyper flash for MCXN947 should work with any compatible make Hyper Flash model?

[Harry_Zhang]

Hi @Ramadurai 

Different HyperFlash devices all use the HyperBus protocol, but their timing parameters, latency counts, voltage/clock requirements, address modes, and command sequences are not identical. Because the MCXN947 FlexSPI uses a LUT‑based command engine, these device‑specific differences require different LUT entries and FlexSPI configuration settings for each HyperFlash part. Therefore, changing to another HyperFlash device usually means updating the LUT, timing parameters, and related FlexSPI configurations to match the new device’s datasheet.

For the mcxn947, there is currently no demo related to S26KL128SDABHI020.

But you can refer to the evkbimx1060 flexspi hyperflash demo.

For  the MIMXRT1060-EVKB, it connected to the hyperflash  S26KS512SDPBHI020.

Hope this will help you.

BR

Harry

[Ramadurai]

Please inform me the high level changes and config needed when I reuse the code from #evkbimx1060 flexspi hyperflash demo for #MCXN947 custom board to interface the #Hyper Flas

[Harry_Zhang]

Hi @Ramadurai 

Although both platforms use FlexSPI and HyperBus,

Clocking and Pin mux are the most significant changes.

There are no major changes in deviceconfig , LUT and main.

BR

Harry