Keil MDK-ARM V4.14.4.0 return error 65: access violation

[RomainR.]

Posted on January 28, 2011 at 10:39

Hello,

I try to debug and simulate the discover project on MDK-ARM evaluation IDE. I have no hardware. So i just want to test debug and simulation. Here below the error message after build and start debug:

Running with Code Size Limit: 32K

Load ''C:\\USERS\\MyDev\\STM\\STM32VL-Discovery\\STM32VLDiscovery_Project\\Project\\Demo\\MDK-ARM\\Debug\\DISCOVER.AXF''

*** Restricted Version with 32768 Byte Code Size Limit

*** Currently used: 2020 Bytes (6%)

BS

file://discover/main/53

, 1 *** error 65: access violation at 0x0000000C : no 'read' permission *** error 65: access violation at 0x00000000 : no 'execute/read' permission Can you help me. Regards Romain

[xavius]

Posted on April 06, 2011 at 22:08

---

[xavius]

Posted on April 06, 2011 at 22:12

Hi

You should set the Flash Tool options.Look this reference ''UM0986 User manual'' .

[Andrew Neil]

Posted on April 07, 2011 at 09:44

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

http://www.keil.com/support/docs/814.htm

http://www.keil.com/support/man/docs/uv4/uv4_e065.htm

[guillaumefaye]

Posted on September 11, 2011 at 10:04

Hello,

I have the same probleme, I try to modifie the map , it 's don't work. I think it's a reset mystake to point to a wrong adresse. do you resolve this? thanks.

[muratterzi2]

Posted on September 11, 2011 at 21:58

value line controllers has not proper simulation capabilities in keil. let you chose the same type other than value line controller and simulate without having problems.if you want upload code to controller you must chose value line controller when debugging.

[guillaumefaye]

Posted on September 12, 2011 at 07:30

Ok thank you.

I try it.

[Andrew Neil]

Posted on September 12, 2011 at 08:39

''value line controllers has not proper simulation capabilities in keil''

What do you mean by that?

Keil uVision simulates the code execution on any Cortex-M3 CPU; the ''special'', device-specific simulation features are just about the peripherals. This looks like just a basic memory options set-up issue (see the Keil support pages linked earlier) - so peripheral support (or lack of it) should not matter?

[guillaumefaye]

Posted on September 12, 2011 at 19:01

I think the real probleme is the pc jump to 0x00000000 adress on reset with the simulator.

cause this adress isn't define in discovery start-up so it is normaly to have an ''error 65''  why simulator don't jump to 0x08000000 with discovery exemples???????

[guillaumefaye]

Posted on September 12, 2011 at 21:42

good news.

I try to simul discovery exemple after select stm32f103RB device ,it 's ok so stm32f100rb don't work in simulator.why???