Skip to main content
michaelkotthaus9132
Associate
April 3, 2013
Question

*** error 65: access violation at 0x40023800 : no 'read' permission

  • April 3, 2013
  • 3 replies
  • 1696 views
Posted on April 03, 2013 at 14:15

I have successfully run some of the simple demos on the STM32F4Dsicovery board but when I try a couple of the usart examples I get this message in debug mode:

*** error 65: access violation at 0x40023800 : no 'read' permission

the location is this line:

  /* Reset the RCC clock configuration to the default reset state ------------*/

  /* Set HSION bit */

  RCC->CR |= (uint32_t)0x00000001;

I have the same debug setting sas before ie. ST-Link Debugger, Port=SW,SWDIO = 0x2BA01477 ARM Coresight SW-DP and on the Utilities the Programming Algorithm is:

STM32F4xx Flash On-chip Flash 1M 0800000H - 080FFFFFH

I now also get the same debug message when I go back to the previous working Flash LED examples.

Thanks in advance

#keil-debugger #usart-stm32f407 #keil-simulator
This topic has been closed for replies.

3 replies

Tesla DeLorean
Guru
April 3, 2013
Posted on April 03, 2013 at 18:38

Keil? Sure you're not trying to run the code in the simulator?

Tips, Buy me a coffee, or three.. PayPal VenmoUp vote any posts that you find helpful, it shows what's working..
michaelkotthaus9132
Associate
April 5, 2013
Posted on April 05, 2013 at 12:42

Yes using Keil, uVision4 and I don't think I'm using the simulator, I'll check and get back to you ...

Thanks for the reply.

Andrew Neil
Super User
April 17, 2013
Posted on April 17, 2013 at 10:54

*** error 65: access violation at 0x40023800 : no 'read' permission

So give it some 'read' permission, then!

http://www.keil.com/forum/22889/

A complex system that works is invariably found to have evolved from a simple system that worked.A complex system designed from scratch never works and cannot be patched up to make it work.