The memory map is updated when you load an image.

A memory map can be configured in a board/chip definition (BCD) file that you associate with the connection. If you connect to a target that is configured in this way, then memory mapping is automatically enabled.

Any areas of memory that are not defined by the memory map are shown as default mapping. If target memory exists in these areas, it is treated as RAM. If any of these memory areas are not RAM (for example, ROM or Flash), then this can affect various operations you perform in RealView Debugger. For example, if you attempt to set a software breakpoint in ROM, then an error occurs. However, you can force the creation of a hardware breakpoint using the failover qualifier, depending on the remaining hardware breakpoint resources available.

If you delete any or all memory map blocks in the Memory Map tab that have been defined in a BCD file, then that memory map is no longer available for the connection. However, the definitions in the BCD file are not deleted. Therefore, to restore the memory map back to that defined in the BCD file, you must disconnect and then reconnect.