• State Not Answered
  • Locked Locked
  • Replies 7 replies
  • Subscribers 21 subscribers
  • Views 1550 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

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

Deepak Thomas

I'm relatively new to Keil and C167. I got an error: "error 65: access violation" while debugging an assembly program using simulator. I tried these 2 sets of assembly code

1) Using EXTS

EXTS #4, #3
mov r1, #0x0A
mov r2, #0x1000
mov [r2], r1

2) Using DPP
mov DPP2, #0x0010
mov r1, #0x0A
mov DPP2:0x1000, r1

But both gives me the error: "error 65: access violation: addr=0x00041000".

In the project settings, I had mentioned 40000 to 90000 as External RAM.

Would be grateful if you can correct me and provide me some guidance.

Thanx in advance...!!!

Parents
  • 0 in reply to Deepak Thomas

    To be honest, I didn't have to do anything like that before because I let the C compiler and the linker do all those things. I think Keil\C166\hlp\A166.PDF contains all the details about sections, classes and so on. The file Keil\C166\LIB\START167.A66 defines sections like system stack and user stack, so you can take the correct syntax from there.
    As for the assembler code, I would change only one thing.
    You wrote:

    EXTS #4, #3
mov r1, #0x0A
mov r2, #0x1000
mov [r2], r1
    The EXTS instruction locks interrupts, PEC, and hardware traps. If interrupt latency is an issue, this code is better:
    mov r1, #0x0A
mov r2, #0x1000
EXTS #4, #1
mov [r2], r1
    - Mike

Reply
  • 0 in reply to Deepak Thomas

    To be honest, I didn't have to do anything like that before because I let the C compiler and the linker do all those things. I think Keil\C166\hlp\A166.PDF contains all the details about sections, classes and so on. The file Keil\C166\LIB\START167.A66 defines sections like system stack and user stack, so you can take the correct syntax from there.
    As for the assembler code, I would change only one thing.
    You wrote:

    EXTS #4, #3
mov r1, #0x0A
mov r2, #0x1000
mov [r2], r1
    The EXTS instruction locks interrupts, PEC, and hardware traps. If interrupt latency is an issue, this code is better:
    mov r1, #0x0A
mov r2, #0x1000
EXTS #4, #1
mov [r2], r1
    - Mike

Children
No data