- This topic has 2 replies, 2 voices, and was last updated 1 month ago by
.
-
Posts
-
Hello,
I’m working on a project with an STM32H7R3L8H6H MCU, and everything looks good so far. However, after the build, I noted one thing in the Memory utilization report. The XSPI memory is listed as 128 MB, which is somewhat incorrect.
How can I understand this number?
- Is it the maximum addressable memory of the XSPI?
- This would be 256 MB for each XSPI on the STM32H7RS series
- Is it the total of the usable memory size for that project?
- That number could be extracted from the “MX_XSPIx_Init” function within the project, which is in my case:
- hxspi1.Init.MemorySize = HAL_XSPI_SIZE_256MB – 32 MByte in my project
- hxspi2.Init.MemorySize = HAL_XSPI_SIZE_256MB – 32 MByte in my project
- That number could be extracted from the “MX_XSPIx_Init” function within the project, which is in my case:
I’ve attached a screenshot for your information
Hi,
Due to historical reasons, the maximum memory size shown in the build output and in the Memory Explorer is fixed for each device type. It doesn’t affect anything other than the displayed utilization, so for the devices with variable size we usually just take the default value from the default vendor-supplied linker script.
You can always patch it on your side by editing the MemoryMap tag in BSP.XML under %LOCALAPPDATA%\VisualGDB.
Another option would be to configure VisualGDB to infer the memory map from the linker script (requires Custom edition) via VisualGDB Project Properties -> Memories.
- Is it the maximum addressable memory of the XSPI?
- You must be logged in to reply to this topic.