In the Memory Access page you can specify how winIDEA is permitted to access target memory.
Debug Options dialog, Memory Access page
When CPU is running
You can allow winIDEA to access memory of the debugged system even when it is running.
•Allow real-time access - when checked winIDEA will use real-time access for reading and writing. Reading or writing a byte using this method will stall the CPU for one CPU cycle only.
•Allow monitor access - when checked winIDEA is permitted to use monitor access. Monitor access stops the CPU, performs memory access and sets the CPU running. Since this can take several hundred milliseconds (depending on the speed of the PC and CPU), use this option only if the CPU can be interrupted for such intervals.
Cache memory read accesses
Memory read accesses can be cached. This can greatly improve IDE performance. A memory that is read will not be read again until a write access is performed or program execution point is advanced. Care must be taken to exclude memory regions which can be corrupted with read access (some SFRs on some CPUs).
•None - no caching is performed (default)
•All - all memory accesses are cached
•None, except - no caching except in the regions specified in the Except list
•All, except - all memory accesses are cached, except for regions in the Except list
Multiple regions can be defined in the exception dialog.
Entering memory areas
Memory area definition
Specify the address, the memory area and the size of the memory area to include/exclude.
Don't cache SFRs
If this option is selected, the SFRs will not be cached.
Cache real-time accesses
If this option is checked, real-time memory accesses are cached in blocks of 64 bytes. This improves refresh performance if many watches located close to each other are configured, but decreases it if only a few sparse locations are monitored.