FileX / LevelX / QSPI cannot get the filesystem to startup.

[matt-crc]

Hello,

Is there any documentation or example on how to setup a STMH7(43) with QSPI and FileX and LevelX? There must be something that is not setup properly.   I looked at the Fx_Nor_Write_Read_File project for the STM32H735, but the code and CubeMX settings are completely different from the new project I started with CubeMX.

On my custom board, the system comes up. It starts by calling FX_Media_Format, which calls 'FlashErase; it thinks it successfully erased the entire flash (but I have my doubts), it then sets up the semaphores, and start the actual formatting.  lx_stm32_qspi_read() runs 3 times and then fails. I would have expect to see "FFFFFFFF"s on all the reads, but it seems to be getting different data.

I dropped the clock to 50MHz for this test, but it is unclear if the 1/2 clock shift should be enabled or not, and what should the DMA settings be in CubeMX.  It seems to be reading the Device ID and passes that test. Is it a memory cache issue?

Any help or suggestions would be helpful

thanks

Matthew

QSPI device is MT25QL256 (32Mbyte)

 

 

[matt-crc]

Hello,

I got a hold of the STM32H735-DK demo board, and tried to run the demo Fx_NoR_Write_Read_File demo, and it has the exact same issue that we are facing on our board.

1- The external flash was erased (also verified with the CubeProgrammer

2- The demo program calls fx_media_format() and it fails with error 144 (0x90).

According the AzRtos manual it means: Driver I/O error.

 

Can someone at ST validate the demo program on the discovery board, and let me know what you find?

thanks

Matthew

[matt-crc]

It seems the only way the FileX / LevelX code runs under STM32 is with the cache off.  Is there a version of FileX / LevelX that manages the memory so the cache can be enabled?