keil调试 *** Error 65: Access violation at 0x00000004 : No 'write' permission问题解决方法
2016-11-16 11:05
801 查看
µVISION DEBUGGER: ERROR 65 (ACCESS VIOLATION)
Information in this article applies to:MDK All Versions
Cx51 All Versions
C166 All Versions
C251 All Versions
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
原文地址:http://www.keil.com/support/docs/814.htm
相关文章推荐
- Keil 调试ARM时出现的 *** error 65: access violation at xxxx : no 'write' permission
- MDK5.00中*** error 65: access violation at 0x40021000 : no 'read' permission的一种解决方法
- *** Error 65: Access violation at 0x00000004 : No 'write' permission
- 在keil 5的软件仿真中避免error 65: access violation at 0x40021000 : no 'read' permission
- MDK5.00中*** error 65: access violation at 0xFFFFFFFC : no 'write' permission的一种解决方法
- 解决 *** error 65: access violation at 0x0000000C : no 'read' permission
- keil *** error 65: access violation at 0x2007C125 : no 'write' permission
- “*** error 65: access violation at 0x0000000C : no 'read' permission”错误的解决
- *** error 65: access violation at 0x68014802 : no 'write' permission
- *** error 65: access violation at 0x40021000 : no 'read' permission
- 使用RealViewMDK时常见的问题 access violation at 0xFFFFFFFC: no “write” permission
- error 65: access violation at 0x40021000 : no 'read' permission
- *** error 65: access violation at C:0x001B : no 'execute/read' permission
- STM32 KEIL不能输入仿真引脚端口error 65: access violation at 0x40021000 : no 'read' permission
- STM32 KEIL不能输入仿真引脚端口error 65: access violation at 0x40021000 : no 'read' permission
- *** error 65: access violation at 0x40021000 : no 'read' permission
- STM32 软件仿真失败 ***** error 65: access violation at 0x40021000 : no ****'read' permission******
- error 65: access violation at 0x40021000 : no 'read' permission
- *** error 65: access violation at C:0x001B : no 'execute/read' permission
- keil软件仿真*** error 65: access violation at 0x0000000C : no 'read' permission