cancel
Showing results for 
Search instead for 
Did you mean: 

Request for .ioc File of Fx_NoR_Write_Read_FileExample for STM32U5G9J-DK2

Gowri_M
Associate II

Hello ST Community,

I’m currently developing a project on the STM32U5G9J-DK2 board and working to implement a FileX + LevelX-based file system on the external NOR flash via XSPI.

I found the example project Fx_NoR_Write_Read_File in the STM32Cube firmware package, and while it’s functionally suitable, it does not include the .ioc file. This has made it challenging to fully understand and replicate the setup, especially regarding the XSPI (OctoSPI) peripheral configuration and the use of the lx_stm32_xspi_driver_glue.c for flash communication.

Why This Is Important:

  • The CubeIDE (latest version) does not provide this driver (lx_stm32_xspi_driver_glue.c) and configuration by default, making manual recreation risky and error-prone.
  • Without the .ioc or clear documentation, it’s difficult to ensure correct XSPI timings, GPIO assignments, and memory-mapped mode settings.
  • My current development progress is blocked until I can correctly mirror the peripheral and middleware configuration from this example.

What I’m Requesting:

  • The original .ioc file used to generate the Fx_NoR_Write_Read_File project for STM32U5G9J-DK2, OR
  • A newer, CubeMX-compatible example demonstrating XSPI + LevelX + FileX integration for external NOR flash, OR
  • Official documentation or screenshots detailing the XSPI + FileX + LevelX configuration used in the example.

Any help or direction from the ST team or community members would be highly appreciated, as it would unblock critical development efforts and ensure alignment with best practices.

Thank you very much for your time and support!

Warm regards,

Gowri M

3 REPLIES 3
MOBEJ
ST Employee

Hello @Gowri_M 

Thank you for your question about the .ioc file for the Fx_NoR_Write_Read_FileExample on the STM32U5G9J-DK2.

As noted in the Release Notes under Known Limitations, this application is currently provided without an .ioc file. This limitation will be fixed soon in the next release of STM32CubeU5.

Thank you for your understanding

BR

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
Andrew Neil
Super User

Note that not all examples have .ioc files:

https://community.st.com/t5/stm32-mcus-products/some-example-projects-don-t-use-ioc-file/m-p/698338/highlight/true#M255312

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.

Hello @MOBEJ 

Thank you for the clarification and for pointing me to the release notes.

While I understand that the .ioc file is not yet available, I would really appreciate it if you could share some of the essential configuration details related to the FileX/LevelX setup used in the Fx_NoR_Write_Read_File example.

In particular, it would be very helpful to know:

  • Any specific buffer or memory alignment requirements
  • Stack size or heap considerations for FileX
  • The parameters used for fx_media_format() (sector size, cluster size, number of FATs, etc.)

Thank you again for your support!

Best regards,
Gowri