Load Map
In this topic:
Load Map offers a quick insight into what was loaded to the memory. You can open it via Debug | Show Load Map.
The Load Map window displays a grid that represents the target memory. Each grid unit represents the status summary of all bytes in that range. The legend is displayed on the left, explaining the color scheme.
On a higher level, where one unit displays information for many bytes, the information on each byte is inspected and merged into a single color. If all bytes in these regions have the same status, then this color is shown on the parent unit, otherwise, the Mixed color is displayed. If a unit contains bytes with different statuses and at least one byte with overlapped data, then MixedOverlap color is displayed in order to propagate the information about the overlap to the top-most unit.
Lower and upper left addresses provide the address range that is displayed on the grid. Hovering over a unit will display the start address in the Address field. Clicking a unit will expand that memory region to the grid. Addresses that were successfully filled with data (Loaded) will display the loaded data in the Data field. The Load Map view displays the total size of the loaded memory (in bytes).
Block size - Click on the arrows to zoom in or out into the memory blocks.
Not Mapped - The memory space is not accessible in the system.
Target - Empty target memory space.
Loaded - Addresses successfully filled with data.
Overlap - Unit with overlapped data, it is possible that the desired data has not been loaded.
Mix - A region with a mix of different byte statuses.
MixOverlap - A region with a mix of different byte statuses where at least one byte has an Overlap status.
The Load Map option is enabled by default. You can disable it in Debug | Configure Session | SoC | Startup. winIDEA can also generate an XML formatted load report after download.
•Check what will be loaded to the target before actually downloading the application enable Tools | Demo Mode and perform a download. Load Map shows which memory regions are programmed.
•Check if there are any code overlaps before performing download