From Texas Instruments Embedded Processors Wiki

Jump to: navigation, search

Translate this page to

Many people wonder why using memory mapping in Code Composer Studio when working with target hardware is so important. There are a number of reasons why it is desirable to use a memory map.

First, the memory map is the only truly reliable means that the user has to determine which memory locations are allowed to be touched by emulation and which are to be avoided. In many cases, touching locations where no memory is implemented does not cause a problem. However, there have been cases where trying to read a memory location that doesn’t exist hangs the memory bus. (usually these are design issues) In these types of cases, memory mapping can keep the user functioning. Without memory mapping turned on, once the memory bus is hung, the user has no recourse but to reset the target, a frustrating exercise.

When you first invoke Code Composer Studio, the memory map is turned off. You can access any memory location; the memory map does not interfere. When memory mapping is enabled, the debugger checks each of its memory accesses against the memory map provided. If you try to access an undefined or protected area, the debugger will prevent the access from occurring and the debugger will display the value as a series of dashes (-). Select->CCS->Option->Memory map->enable memory mapping.

Additionally, the memory map can serve as a double check of the linker command file and help find code or data that might be linked to non-existent memory. If code is linked to memory that is not in the memory map, Code Composer Studio will report it during the COFF load.

For more information on memory map, refer CCS contextual help. You can also refer SPRU186

Q: C6000: Memory Map of CPU registers

On the C2000 devices, the IMR and IFR are visible in Data memory, and their addresses are stated in the CPU User Guide SPRU430. On the C6000 architecture, the CPU registers and control registers are not memory mapped. The IFR and IER registers, for example, are in the control register file and are accessible via the MVC instruction into the CPU register file. More information can be found in the C6000 CPU and Instruction Set Guide SPRU189.