• State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 21 subscribers
  • Views 2987 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

Error 22

Art Haynes

We are using the Analog Devices ADuC812. The board was modified per the Keil App Note 151. We are getting the following error messages
ERROR 22 (NO CODE MEMORY AT ADDRESS (0707)
ERROR 22 (NO CODE MEMORY AT ADDRESS (C3C3)
ERROR 22 (NO CODE MEMORY AT ADDRESS (F5F5)

The board is not set up to have writable code space at these addresses, so we would expect these errors if the tool is trying use them as writable code space. Any ideas on what is happening and how to solve it ?

Parents
  • 0


    We are using the Analog Devices ADuC812. The board was modified per the Keil App Note 151. We are getting the following error messages:

    ERROR 22 (NO CODE MEMORY AT ADDRESS (0707)
ERROR 22 (NO CODE MEMORY AT ADDRESS (C3C3)
ERROR 22 (NO CODE MEMORY AT ADDRESS (F5F5)
    The board is not set up to have writable code space at these addresses, so we would expect these errors if the tool is trying use them as writable code space. Any ideas on what is happening and how to solve it ?

    Here are two ideas...

    1. Note that the MSB and LSB are repeated. Is it possible that there is some kind of weird decoding problem or that P0 and P2 got writed up incorrectly?

    2. Are you getting these errors from the uVision2 Debugger when you try to download your program code? If so, then you need to look at the M51 file for your program to see if there's anything at these addresses.

    Keil Support

Reply
  • 0


    We are using the Analog Devices ADuC812. The board was modified per the Keil App Note 151. We are getting the following error messages:

    ERROR 22 (NO CODE MEMORY AT ADDRESS (0707)
ERROR 22 (NO CODE MEMORY AT ADDRESS (C3C3)
ERROR 22 (NO CODE MEMORY AT ADDRESS (F5F5)
    The board is not set up to have writable code space at these addresses, so we would expect these errors if the tool is trying use them as writable code space. Any ideas on what is happening and how to solve it ?

    Here are two ideas...

    1. Note that the MSB and LSB are repeated. Is it possible that there is some kind of weird decoding problem or that P0 and P2 got writed up incorrectly?

    2. Are you getting these errors from the uVision2 Debugger when you try to download your program code? If so, then you need to look at the M51 file for your program to see if there's anything at these addresses.

    Keil Support

Children
  • 0 in reply to Keil Support

    In response to your comments:

    1. Note that the MSB and LSB are repeated. Is it possible that there is some kind of weird decoding problem or that P0 and P2 got writed up incorrectly?

    We did not make any other mods to the board. And we are not using the P0 and P2 ports.

    2. Are you getting these errors from the uVision2 Debugger when you try to download your program code? If so, then you need to look at the M51 file for your program to see if there's anything at these addresses.

    We are getting the errors during download, but we do not see any reference to the addresses in question. Here is part of the M51 file listing showing the Code space. Maybe there is something there that we are not seeing.

    CODE 0000H 0003H ABSOLUTE
    CODE 0003H 0005H UNIT
    0008H 0003H
    CODE 000BH 0003H ABSOLUTE
    CODE 000EH 0390H UNIT
    CODE 039EH 036CH UNIT
    CODE 070AH 035CH UNIT
    CODE 0A66H 0310H UNIT
    CODE 0D76H 02BCH UNIT
    CODE 1032H 011AH UNIT
    CODE 114CH 008CH UNIT
    CODE 11D8H 008CH UNIT
    CODE 1264H 008AH UNIT
    CODE 12EEH 007FH UNIT
    CODE 136DH 0065H UNIT
    CODE 13D2H 005BH UNIT
    CODE 142DH 0040H UNIT
    CODE 146DH 0034H UNIT
    CODE 14A1H 0033H UNIT
    CODE 14D4H 0026H UNIT
    CODE 14FAH 0025H UNIT
    CODE 151FH 001DH UNIT
    CODE 153CH 0018H UNIT
    CODE 1554H 0017H UNIT
    CODE 156BH 0015H UNIT
    CODE 1580H 0013H UNIT
    CODE 1593H 0013H UNIT
    CODE 15A6H 0011H UNIT
    CODE 15B7H 000EH UNIT
    CODE 15C5H 000EH UNIT
    15D3H 0A50H
    CODE 2023H 0003H ABSOLUTE

  • 0 in reply to Art Haynes

    Hmmmm...

    That error indicates that there is no code address at a specific address.

    When I configure the monitor for a new target, I always test the memory to be sure that I can write the XDATA and it appears in CODE. That's where I usually find the problems.

    The XDATA memory that's reserved for the monitor MUST BE vonNeumann memory. Is it? Also, if anything writes over this memroy, you may see these kinds of errors.

    Keil Support