2018-04-12 05:47 AM
I am using stm32f446zet6 and IDE keilv5 for a project . When debugging it shows the following error ,
*** error 65: access violation at 0x40023800 : no 'read' permission
*** error 65: access violation at 0x40023800 : no 'write' permission*** error 65: access violation at 0x40023808 : no 'write' permission*** error 65: access violation at 0x40023800 : no 'read' permission*** error 65: access violation at 0x40023800 : no 'write' permission*** error 65: access violation at 0x40023804 : no 'write' permission*** error 65: access violation at 0x40023800 : no 'read' permission*** error 65: access violation at 0x40023800 : no 'write' permission*** error 65: access violation at 0x4002380C : no 'write' permission*** error 65: access violation at 0x40023840 : no 'read' permission*** error 65: access violation at 0x40023840 : no 'write' permission*** error 65: access violation at 0x40023808 : no 'read' permission*** error 65: access violation at 0x40023808 : no 'write' permission*** error 65: access violation at 0x40007000 : no 'read' permission*** error 65: access violation at 0x40007000 : no 'write' permission and so on.................../***********************
// Clock addresses
RCC_CR 0x40023800
RCC_PLLCFGR 0x40023804
RCC_CFGR 0x40023808
RCC_CIR 0x4002380C
***********************/
As per the forum post
http://www.keil.com/support/docs/814.htm
,I have put the required MAP commands into a debugger INI file that can be entered under
Project -> Options for Target -> Debug -> Initialization file asMAP 0x40000000, 0x47FFFFFF READ WRITE // allow R/W access to IO space
Then it doesn't exist the function for making external clock to 180MHz .If I use the internal clock , the same issue persists . How could I solve these issues. Any help would be greatly appreciated .
#stm32f4 #stm32 #stm32f4-external-nor-flash2018-04-12 06:57 AM
Peripheral clock to the RTC not enabled ?
2018-04-12 07:46 AM
>>How could I solve these issues
STOP using the Simulator, all the ERROR 65 posts are from people trying to use the simulator which doesn't support their hardware. Keil has stopped supporting simulations of the 1000's, and growing, chips from everyone and their brother, NUCLEO and DISCO boards are now very cheap and have an on-board debugger. If you want to simulate the Cortex-M4 core you can probably do that, but once you start touching peripherals added by the vendor you will get this error.
Use Real Hardware
Use the Debugger, NOT the Simulator
2018-04-12 08:17 AM
Google keil initialization file. Essentially you need to mark certain memory regions read write or execute-able.
2018-04-12 10:27 AM
>>Google keil initialization file. Essentially you need to mark certain memory regions read write or execute-able.
This allows code to plough forward in the simulator but doesn't make the underlying 'memory' function like the peripherals the code is expecting.
The solution here is not to hammer harder, but to stop hammering.
2018-04-12 09:27 PM
Thank you Clive for your quick reply .