[Bug]: Middleware 8.0.0 STM32 SDCard Keil uVision

[FerdinandEn]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

I have port an existing SDCard application STM32F746-Disco to the newest version.

FS_Config_MC_0.h

Entries:

• Connect to hardware via Driver_MCI#
• Connect to hardware via Driver_SPI#

can not be edited in Configuration Wizard. Doing the same in Keil Studio Preview it is possible

Replace <y> by <o> solves the problem

Drive Cache Size

I have therefore set the drive cache size to 4 kB.

When I set the area to 4 kB in the scatter file, the area was too small. The requested size is 5 kB. Even more if FAT Journal is activated (+128*4 b). Maybe you could add a hint.

Expected Behavior

No response

Steps To Reproduce

No response

Affected components

• Filesystem
• Network
• USB_Device
• USB_Host

Version

Middleware 8.0.0

Blocker

• blocker

[FerdinandEn]

To open the help, the following link to an HTML_page is inserted. Due to #mc_usage I cannot open the HTML page in VSC to display it.

[ReinhardKeil]

@FerdinandEn the open documentation feature is coming in the next VS Code extension release 1.42 - schedule for mid November.

[andbararm]

We would still prefer to have one topic per issue report.

1. Config Wizard issue
   Unfortunately, this feature is not (yet) fully supported in uVision. As you can see in the uVision documentation: https://developer.arm.com/documentation/101407/0541/Utilities/Configuration-Wizard, 'y' is not listed there. But it is in the new Open CMSIS Pack documentation: https://open-cmsis-pack.github.io/Open-CMSIS-Pack-Spec/main/html/configWizard.html
   We have already an internal request to extend uVision to fully support it also there. But not sure, when this will happen. But as it is related to uVision, this topic is basically out of scope here.
2. actual memory requirement for drive cache
   Will see, if we can add this info somewhere.

[VladimirUmek]

Memory requirements for buffers that are passed to the drivers and go into special sections should go into documentation. Each config file already contains an option to place those buffers into dedicated section and there is also an default section defined that serves the same purpose, but I think this is not properly documented. We will add this.