9.5. Setting up a temporary memory map

You can set up a memory map for your current debug session. Target memory settings defined in this way are only temporary and are lost when you disconnect from the target.

To set up a temporary map:

  1. Create a Debug Configuration that does not have a BCD file assigned to it.

  2. Connect to a target in the Debug Configuration.

  3. Enable memory mapping.

  4. Right-click in the Memory Map tab, shown in Figure 9.7, to display the context menu.

    Figure 9.7. Default memory map

    Default memory map

  5. Select Create Map Entry... from the context menu to open the Create Map Entry dialog box. Figure 9.8 shows an example:

    Figure 9.8. Create Map Entry dialog box

    Create Map Entry dialog box


    In RealView Debugger, memory mapping is defined by a start address and a block size by default, not by an end address. If you want to specify the end address, you must deselect the Size is inclusive Length (vs Addr.) check box.

  6. Specify the starting location for the new map entry in the Start Addr field.

    For this example, leave the address as 0x0.

  7. Specify the block size for the new map entry in the Size field.

    For this example, enter 0x8000.

    By default, this specifies the size of the memory block to be defined. To specify the absolute end address, rather than the size:

    1. Deselect the Size is inclusive Length (vs. Addr) check box.

    2. Enter the required address in the Size field. For example, enter 0xFFFFFFF0.

    RealView Debugger automatically sets the size you specify. If the computed size does not fall on a page boundary an error dialog box is opened and you must re-enter the block size.

    If you enter a value of 0x0, all memory from the starting address is remapped.

  8. Select the access type in the Access list.

    For this example, leave the type as RAM - Read/Write Memory.

  9. Select the memory type to be allocated from the Type list. The options listed depend on your target.

  10. If required, select the size of memory accesses in bytes from the Access Size.


    By default, memory access is set to byte-size (8 bits) for a Default Mapping entry in the Memory Map tab.

  11. If you selected Flash - FLASH/EEPROM Updateable as the Access type, then you must specify the appropriate Flash MEthod (FME) file to use for your development platform. Otherwise, skip this step.

    To specify the FME file to use for Flash programming:

    1. Click the file browser button for the FLASH Programming Method File (FLASH Only) field.

    2. Select <Select File ...> from the menu to open the Select File dialog box.

    3. Locate the required FME file.

    4. Click Open.

      The FME file and path are inserted into the FLASH Programming Method File (FLASH Only) field.

    You can optionally set the FLASH write mode to one of the following:


    Causes the Flash Memory Control dialog box to be displayed so that you can manually perform a Flash write operation.


    Causes RealView Debugger to perform Flash write operations automatically.

    Also, set the FLASH Auto-write clock frequency in Hz field to the correct speed.

    In this mode, the write operation is complete when RealView Debugger displays the Flash Memory Control dialog box. Also, messages are displayed in the Cmd tab of the Output view, depending on the feature used to perform the write operation.

  12. Enter a description for this entry in the Description field.

    For this example, enter Area before image.

  13. Click OK to confirm your changes. The memory map is updated to show the memory block you have added.

  14. Repeat these steps for other memory map entries you want to define.

    For this example, create two map entries with the settings shown in Table 9.1.

    Table 9.1. Settings for new map entries

    SettingSecond BlockThird block
    Start address0x80000x10000
    DescriptionMiddleArea after image


    If you right-click on the Default Mapping entry, and select Create Map Entry..., then the start address for the new entry is set to the next unused address.

  15. Expand each memory map entry to see the details. The memory map looks like that shown in Figure 9.9.

    Figure 9.9. Example of a memory map

    Example of a memory map

See also:

Copyright © 2002-2011 ARM. All rights reserved.ARM DUI 0153N