Keil Logo

µVISION DEBUGGER: PEC REGISTERS DO NOT WORK IN THE DEBUGGER


Information in this article applies to:

  • C166 Version 4.03

QUESTION

The debugger seems to ignore PEC source and destination pointer initialization. When the code loads SRCP0 and DSTP0, the debugger PEC window shows no change. Isn't the debugger supposed to pick up the PEC info automatically from the code, or does it have to be initialized manually?

If the source and destination pointers aren't initialized properly, of course, the debugger gives an access violation error. We entered the correct pointers manually using the debugger PEC window and the code executed properly without an access violation. But do we have to enter the pointers manually every time we run the debugger?

ANSWER

The original C166 has different addresses for the PEC registers to the C167 and its derivatives. This means that currently µVision is unable to properly simulate all the features of the C166. The C167 and derivatives are fully supported however.

Debugger support for the C166 will be developed by early 2000.

Last Reviewed: Tuesday, June 29, 2004


Did this article provide the answer you needed?
 
Yes
No
Not Sure
 
  Arm logo
Important information

This site uses cookies to store information on your computer. By continuing to use our site, you consent to our cookies.

Change Settings

Privacy Policy Update

Arm’s Privacy Policy has been updated. By continuing to use our site, you consent to Arm’s Privacy Policy. Please review our Privacy Policy to learn more about our collection, use and transfers
of your data.