Embedded Memory explorer uncorrect memory name visualization

Sysprogs forums Forums VisualGDB Embedded Memory explorer uncorrect memory name visualization

This topic contains 1 reply, has 2 voices, and was last updated by  support 4 days, 17 hours ago.

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
  • #25795

    Good morning

    I’m using a board with stm32f429 MPU with an external 16M RAM memory placed at 0xc0000000.
    For application purposes, I have to use the external memory as main memory.
    By appropriately modifying the startup files and the  linker script , the program is compiled
    and executed correctly .

    the memory section(inside linker script) is described in this way
    FLASH (RX): ORIGIN = 0x08000000, LENGTH = 2M
    RAM2 (RWX): ORIGIN = 0x20000000, LENGTH = 192K
    CCMRAM (RWX): ORIGIN = 0x10000000, LENGTH = 64K
    / * — begin generated external memories – * /
    SRAM (RWX): ORIGIN = 0xc0000000, LENGTH = 16M
    / * — end generated external memories – * /

    However, the Embedded Memory window does not display the memory Names  and sizes as they were
    configured in the script linker; but keeps the NAME and dimension as default (eg. SRAM 192k at 0x20000000 instead 16384k at 0xc0000000) (see attached file)

    Is it a wrong configuration /usage ?

    How can these descriptions be modified/correct?

    Thanks for your help


    You must be logged in to view attached files.



    Please ensure you are using the VisualGDB Project Properties -> External Memories page for defining the external memories. This mechanism automatically updates the memory layout definition used by the Embedded Memory Explorer.

    We are also working on experimental support for parsing the linker scripts and detecting custom modifications to the memory list, however it will take a few weeks before we release a preview build with this functionality.

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.