CubeMx does not configure FileX properly - Bugs

[matt-crc]

There are 3 bugs reported here:

Bug 1:

In the FileX parameters GUI, under SRAM Disk Driver: The range for the "SRAM Disk Size" is wrong.  The Address space allows for 256MBytes, not 256KBytes.

Workaround - After CubeMX regenerates the code, I have to change the #define manually in the code.

Seems to work on my board with 64Mb, (in the example below I have the base address set to C0200000 and using the upper 32MB)

Bug-2

Under "Software Packs", when we select "LevelX NOR custom inferface", CubeMX doesn't seem to do anything.  We are unable to select the "File System Interface" in the parameters table:

If you unselect the LevelX QuadSPI memory interface,

The majority of the configuration parameters in LevelX disappear, but is left with an unselectable option (MT25TL01G

Bug-3

Since the Custom driver option does not work in CubeMX, we tried to modify the QSPI driver with the MT25TL01G component.  The problem is there are no    " USER COMMENT" sections in the entire file, so we have to make the changes each time CubeMX runs.  We have it working, but CubeMX shouldn't be overwriting code all the time.  There needs to be a way for CubeMX to exclude certain files from updating. - OR - make sure each file has a "USER COMMENT" and the very  beginning and end of each file, so users can comment out all the CubeMX code between the comment sandwich....

 

 

[matt-crc]

Hello ST employee,

I bet you will ask me for the .ioc file... so here it is.

[Ghofrane GSOURI]

Hello @matt-crc 

First let me thank you for posting.

I'm currently investigating this, I will get back to you asap

Thx

Ghofrane

[Ghofrane GSOURI]

Hello @matt-crc 

Regarding the first bug : 

The STM32H7 series typically offers up to 1 MB of RAM, not 256 MB, which is a much larger memory size 

Clarification on RAM Size :

Actual RAM Size: The STM32H7 series includes devices with up to 1 MB of RAM, divided into different types such as 192 Kbytes of TCM RAM (inc. 64 Kbytes of ITCM RAM +128 Kbytes of DTCM RAM for time critical routines), Up to 864 Kbytes of user SRAM, and 4 Kbytes of SRAM in Backup domain

The mention of a 256 MB address space is likely incorrect for the internal SRAM of the STM32H7. This could be a mix-up with external memory configurations or a misunderstanding of how memory is allocated in the system.

External Memory: If you are using external memory like SDRAM, you might be able to configure a larger address space, but this would require specific hardware and configuration beyond the standard STM32H7 setup7.

 

Regarding the second bug :

Under "Software Packs", when we select "LevelX NOR custom inferface"
CubeMX add the following define

--> In FileX\Target\fx_stm32_levelx_nor_driver.h
#define LX_NOR_CUSTOM_DRIVER

Regarding the third bug : still under investigation

 

 

 

[matt-crc]

Hi @Ghofrane GSOURI 

First bug report

I find your first answer strange because you do not limit the size of the drive when using external FLASH, but you limit the size of  the drive when using external RAM.  The data sheet that you provided only says there is 2MB of flash in the chip, yet I can define a 128MB flash drive.  I would have assumed that ST would use the same logic for external RAM.

Second bug report

there doesn't seem to be a #define LX_NOR_CUSTOM_DRIVER in my file.