Why is a change notification interrupt run without the flag bit being set?

A PIC32 change notification (CN) interrupt will only be started when the flag bit is set. If you are in a CN interrupt you may find the flag bit is cleared (0) before you clear it.

The CN interrupt is persistent but the CN status flags are not persistent (i.e. not latched). If the first mismatch on the port pin triggers the interrupt, it may be possible that the second edge comes in during the interrupt and effectively resets or cancels the mismatch so that the status flag is reset to zero.

You may want to use the change notice EDGEDETECT function instead of the pin mismatch. This mode also sets the CNFx register bit(s). Please see the Family Reference Manual (I/O Ports section) for more detail.

  Return to Top

© 2025 Microchip Technology, Inc.
Notice: ARM and Cortex are the registered trademarks of ARM Limited in the EU and other countries.
Information contained on this site regarding device applications and the like is provided only for your convenience and may be superseded by updates. It is your responsibility to ensure that your application meets with your specifications. MICROCHIP MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WHETHER EXPRESS OR IMPLIED, WRITTEN OR ORAL, STATUTORY OR OTHERWISE, RELATED TO THE INFORMATION, INCLUDING BUT NOT LIMITED TO ITS CONDITION, QUALITY, PERFORMANCE, MERCHANTABILITY OR FITNESS FOR PURPOSE. Microchip disclaims all liability arising from this information and its use. Use of Microchip devices in life support and/or safety applications is entirely at the buyer's risk, and the buyer agrees to defend, indemnify and hold harmless Microchip from any and all damages, claims, suits, or expenses resulting from such use. No licenses are conveyed, implicitly or otherwise, under any Microchip intellectual property rights.