I create in last MDK-ARM new project for STM32F207Z and can test debuuging in softrare simulator, but debugger say
*** error 65: access violation at 0x40023800 : no 'read' permission
I thing is need make initialisation file with MAP directive, but I do not know how, and especially why is not it will not generate IDE. Any advice?
0x40023800 is Reset clock controller (RCC) In http://www.keil.com/dd/chip/5121.htm say :Simulation for this device is provided by the default peripheral simulation driver."
Why it does not work?
Default != ST
Defalt = CortexM3 and CortexM3 = ST ==> simulator support all standard CM3 features. I in sumulator see all STM3 peritperals including FSMC or DCMI. I thing simulator support all CM3 standart features in STM32F2 , but I have any error in seting SARMCM3.DLL -REMAP -MPU DCM.DLL -pCM3
or MAP inini file
But never ignore that bold "Complete peripheral simulation is not available and is not planned to be implemented by ARM." for your processor.
Your view of what is M3 core and what is peripherials might not match Keil's view.
Next thing - the debugger is the same when you simulate and when you run on real hardware. And the API of the debugger is configured using XML files. So the debugger can support peripherial hardware that the simulator does not support. So your dialog boxes does not prove simulation support.
It is possible, but I make new project for STM32F103Z http://www.keil.com/dd/chip/5094.htm and The following on-chip peripherals are simulated by the Keil Software µVision Debugger.
but even so, simulator say
*** error 65: access violation at 0x40021000 : no 'read' permission
The Cortex-M3 is a FRACTIONAL portion of the STM32F2 die, so everything OUTSIDE the CPU core is ST unique, and consequently not supported. This would be everything on the AHB and APB buses, and anything in the 0x40000000 address space.
This is a USER forum, and I could argue with you all day, if you want Keil support to walk you through this I'd suggest you call them or email them. http://www.keil.com/support/contact.asp
The chip info pages primarily deal with uv4, a smaller subset of features are supported by uv5 in my experience.
OK Her is solution.
For STM32F103Z Replace dialog.dll from DCM.DLL -pCM3 to DARMSTM.DLL -pSTM32F103ZC
For STM32F2 is only DARMSTM.DLL -pSTM32F217IG