|ARM Technical Support Knowledge Articles|
Applies to: MON166 Target Monitor
Information in this article applies to:
Help, I have configured the MON166 monitor so that my program code lives above address 0x400000. After I load my program and attempt to single-step, the uVision2 Debugger gives me an error message and I have to restart my target hardware. Run til cursor works fine.
What could cause this problem?
This problem may be caused by an oversignt in the MON.LIB file that is used when building the C166 monitor program. The problem specifically affected the single step and procedure steps over instructions at address 40:0000 and higher. This is not a common problem because most target systems don't have that much memory available.
This problem is corrected in version 2.02 of the monitor library. The version of the monitor library may be checked by typing
LIB166 LIST MON.LIB
This problem has been fixed in C166 version 4.10. Install this update and rebuild your monitor.
Request the files attached to this knowledgebase article.
Article last edited on: 2001-04-07 00:00:00
Did you find this article helpful? Yes No
How can we improve this article?