• State Not Answered
  • Locked Locked
  • Replies 6 replies
  • Subscribers 22 subscribers
  • Views 5670 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

Access violation at 0xFFFFFFF4

Dear Martinmohsen Gholami

Hi,
I am new in ARM programming using keil.I tried to debug a sample code in the keil compiler but I have this error when i pressed f7:
Error 65: access violation at 0xFFFFFFF4.I saw the thread to solve this issue. some body said I should add following line to my ini file:
MAP 0x40000000, 0x40001FFF Read Write

I have done it but the Error 65: access violation at 0xFFFFFFF4 is appeared again.
which place i should be add above code to my ini file ?
my ini code is like this:
BREAKPOINTS]
ShowInfoWin = 1
EnableFlashBP = 2
BPDuringExecution = 0
[CFI]
CFISize = 0x00
CFIAddr = 0x00
[CPU]
OverrideMemMap = 0
AllowSimulation = 1
ScriptFile=""
MAP 0x40000000, 0x40001FFF Read Write
[FLASH]
MinNumBytesFlashDL = 0
SkipProgOnCRCMatch = 1
VerifyDownload = 1
AllowCaching = 1
EnableFlashDL = 2
Override = 0
Device="AD7160"
[GENERAL]
WorkRAMSize = 0x00
WorkRAMAddr = 0x00
[SWO]
SWOLogFile=""
[MEM]
MAP 0x40000000, 0x40001FFF Read Write EXEC
RdOverrideOrMask = 0x00
RdOverrideAndMask = 0xFFFFFFFF
RdOverrideAddr = 0xFFFFFFFF
WrOverrideOrMask = 0x00
WrOverrideAndMask = 0xFFFFFFFF
WrOverrideAddr = 0xFFFFFFFF

What should i do to solve this problem .I would like to debug lines of my code step by step.

I would be grateful if you can answer this question

thanks
Mohsen

Parents
  • 0 Arm Employee Badge in reply to Dear Martinmohsen Gholami

    Hello mohsen Gholami,

    it is not so clear to me what you want to do.
    Trying to run your application in uVision simulator or trying to debug your application with JLink on a real HW.

    I am assuming that you want to run your application in uVision debugger.
    You can not use a JLink INI file as an INI file for uVision debugger. uVision expects uVision commands in the INI file and not 'JLink syntax/commands'.

    If you are using a LPC1768 and you configured yor uVision project correct than no '-REMAP' is required. LPC1768 and most of its peripherals are simulated.

    Please tak a look at Blinky project in folder .\Keil\ARM\Boards\Keil\MCB1700\Blinky.
    Target 'Simulator' shows what needs to be done to run this application in uVision simulator.

    Best Regards,
    Martin Guenther

Reply
  • 0 Arm Employee Badge in reply to Dear Martinmohsen Gholami

    Hello mohsen Gholami,

    it is not so clear to me what you want to do.
    Trying to run your application in uVision simulator or trying to debug your application with JLink on a real HW.

    I am assuming that you want to run your application in uVision debugger.
    You can not use a JLink INI file as an INI file for uVision debugger. uVision expects uVision commands in the INI file and not 'JLink syntax/commands'.

    If you are using a LPC1768 and you configured yor uVision project correct than no '-REMAP' is required. LPC1768 and most of its peripherals are simulated.

    Please tak a look at Blinky project in folder .\Keil\ARM\Boards\Keil\MCB1700\Blinky.
    Target 'Simulator' shows what needs to be done to run this application in uVision simulator.

    Best Regards,
    Martin Guenther

Children
  • 0 in reply to Martin Günther

    Dear Martin,
    I found out the mistake.I had changed IROM1 to 0x2000 -0x8000 in order to prevent from deleting my usb boot loader code in flash boot loader segment.So when i was going to debug ,Error 65 was appeared on command window.therefore i changed the IROM1 to 0x0-0x8000 and now every thing is ok and i can debug the code in simulator mode.
    Thank you for your all kindly reply.