Keil Logo

MON166: ERROR (CANNOT WRITE MEMORY)


Information in this article applies to:

  • MON166 All Versions

SYMPTOMS

When I try to debug my application with Monitor-166 I receive the following error message:

CANNOT WRITE TO ROM AREA AT ADDRESS 0AEFFFFH

Why is this error message displayed and what does it mean?

CAUSE

Most likely your application is larger than the available memory and when loaded it is overwriting the monitor data area. You can check this in the linker MAP file (typically this file has the extension *.M66). This file tells you the memory areas in use by your program. Verify that the monitor data area is not also being used by your application.

RESOLUTION

If your program is using the monitor data area, you have several alternatives:

  • Reduce the memory requirements of your application.
  • Increase the amount memory available on your target system.
  • Reserve the monitor data area using the Linker RESERVE directive.
  • Reconfigure the monitor to use a different area for its data space.

MORE INFORMATION

  • µVision2 Getting Started User's Guide, Chapter 11. Using Monitor-166
  • Refer to Monitor Configuration in the MON166 User's Guide.

FORUM THREADS

The following Discussion Forum threads may provide information related to this topic.

Last Reviewed: Wednesday, August 3, 2005


Did this article provide the answer you needed?
 
Yes
No
Not Sure
 
  Arm logo
Important information

This site uses cookies to store information on your computer. By continuing to use our site, you consent to our cookies.

Change Settings

Privacy Policy Update

Arm’s Privacy Policy has been updated. By continuing to use our site, you consent to Arm’s Privacy Policy. Please review our Privacy Policy to learn more about our collection, use and transfers
of your data.