wrong XSPI memory size in — Memory utilization report —

Sysprogs forums Forums VisualGDB wrong XSPI memory size in — Memory utilization report —

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #36375
    intector
    Participant

    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

     

    I’ve attached a screenshot for your information

    Attachments:
    You must be logged in to view attached files.
    #36377
    support
    Keymaster

    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.

    #36378
    intector
    Participant

    Hey,

    Thank you very much for the fast answer. This is what I already thought. I’ve found the entry in the CSP.XML, but I wasn’t sure if that was the correct location.

     

    thank you

    Kai

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.