Keil Logo

ULINK: Debugging Interrupts Fails From Internal Flash

Information in this article applies to:

  • C166 Version 4.27 and later
  • ULINK2 USB-JTAG Adapter


I use interrupt functions in my code and debug my project with the ULINK2. The program is loaded to on-chip Flash of the XC16x device. The debugger behaves strangely after interrupts are enabled.

What can be the reason for that?


There is a potential problem with the Startup Configuration from external circuitry. You should use the Peripherals - Interrupt dialog and check the setting of the VECSEG value. For on-chip Flash the value should be 0xC0. If this is not the case, you should take care that ALE, EA and RD configure the Standard start internal mode.

Detailed information can be found in the XC16x System User Manual in the chapter "Default Configuration in Single Chip Mode".

Last Reviewed: Friday, January 15, 2021

Did this article provide the answer you needed?
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.