keil下access violation at 0xFFFF0D04 : no 'read' permission问题解决

最新推荐文章于 2025-05-11 22:25:37 发布

转载最新推荐文章于 2025-05-11 22:25:37 发布 · 289 阅读

0 ·

本内容遵循CC 4.0 BY-SA版权协议

原文链接：http://www.cnblogs.com/zxj015/archive/2013/01/01/2841577.html

本文详细介绍了如何解决μVision Debugger在访问绝对内存地址时产生的错误65：访问违规，包括如何使用MAP命令或调试器内存映射对话框启用内存区域访问，以及确保设置内存范围权限以匹配实际硬件。

SYMPTOMS

My project includes a variable that I access using an absolute memory address. The µVision Debugger generates the following error whenever I try to write to the variable:

*** Error 65: Access violation at 0x00000004 : No 'write' permission

I have specified this memory area to the linker but I still receive this error.

CAUSE

When the µVision Debugger loads an executable program, it creates a memory map using the program and data segments from the program. Code segments are marked as executable while data segments are marked as read/write. All other memory is unmapped and is, therefore, not marked for any type of access.

The µVision Debugger checks that all memory accesses are made to objects that are defined in your C program. For any access that is outside of a defined C object, the µVision debugger generates an error 65: access violation message.

By default, the debugger allows only memory accesses to valid data objects. This is useful for finding uninitialized or incorrectly initialized pointers, for example. Usually, there is a programming error when you try to access unexpected locations.

RESOLUTION

Enable memory regions for absolute memory accesses using the MAP debugger command or the Debug - Memory Map dialog. Define all the memory ranges that your program is permitted to access. Ensure that you set the permissions (read, write, execute) for each range to match your actual hardware.

You may put the required MAP commands into a debugger INI file that can be entered under Project -> Options for Target -> Debug -> Initialization file. For example, the content of such a file may be:

MAP  0xF800, 0xF8FF  READ WRITE  // allow R/W access to IO space

转载于:https://www.cnblogs.com/zxj015/archive/2013/01/01/2841577.html