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

Debugging code in Ext ROM

We are having trouble producing code that will run out of external code memory in an ADuC812.
It seems that when we use a printf the program hangs, although a puts seems to work.
It is my understanding that the Keil tools will not allow for debugging code residing in external ROM, and we do not seem to have this problem if we use external RAM and MON51 to execute the program.

Does anyone have any ideas on how to solve this problem ?
Does anyone know of a way that we can look at the assmbly code listing of the printf function ?

Parents
  • "Keil tools will not allow for debugging code residing in external ROM"

    It's not Keil that doesn't "allow" it - it depends on what kit you have:
    Without the aid of an ICE, breakpoints work by replacing your code with a special instruction - which is obviously impossible if the code's in ROM!

    To disassemble printf, just look up its address in the mapfile and use the UNASSEMBLE command!

    Could it be that your printf is trying to write something (eg, locals) to ROM?

Reply
  • "Keil tools will not allow for debugging code residing in external ROM"

    It's not Keil that doesn't "allow" it - it depends on what kit you have:
    Without the aid of an ICE, breakpoints work by replacing your code with a special instruction - which is obviously impossible if the code's in ROM!

    To disassemble printf, just look up its address in the mapfile and use the UNASSEMBLE command!

    Could it be that your printf is trying to write something (eg, locals) to ROM?

Children
No data