• State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 22 subscribers
  • Views 1151 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

STM32L152 *** error 65: access violation at 0x0000000C : no 'read' permission in debuger

Carpenter J

Hello
I begin with STM32xxx Cortex M3 MCU. I MDK-ARM I make new project for STM32L152 MCU
program is very simple blinky with LED, compiled is OK
Program Size: Code=936 RO-data=276 RW-data=32 ZI-data=1632
"LED2.axf" - 0 Error(s), 0 Warning(s).
Problem is in Debug (software simulated debug , debuger report

*** error 65: access violation at 0x0000000C : no 'read' permission
Where is problem?

Parents
  • 0 Arm Employee Badge

    Hello Takl Berry,

    In Options for Target - Debug - 'Simulator section' CPU DLL you can add "-REMAP" to Parameter.
    This will automatically remap the code from address 0x08000000 to address 0x00000000.

    But be aware that this device is not simulated and also the address space for the peripherals are not mapped. To map the periperal address space you need an INI file which does this mapping.

    Use command MAP.

    MAP 0x40000000, 0x40001FFF Read Write  // map peripherals

    Best Regards,
    Martin Guenther

Reply
  • 0 Arm Employee Badge

    Hello Takl Berry,

    In Options for Target - Debug - 'Simulator section' CPU DLL you can add "-REMAP" to Parameter.
    This will automatically remap the code from address 0x08000000 to address 0x00000000.

    But be aware that this device is not simulated and also the address space for the peripherals are not mapped. To map the periperal address space you need an INI file which does this mapping.

    Use command MAP.

    MAP 0x40000000, 0x40001FFF Read Write  // map peripherals

    Best Regards,
    Martin Guenther

Children
No data