# ExtInt Problems

**URL:** <https://forum.sierrawireless.com/t/extint-problems/1115>\
**Category:** Open AT\
**Created:** [February 21, 2007, 7:22am UTC](https://forum.sierrawireless.com/t/extint-problems/1115 "2007-02-21T07:22:18Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![gsalter](https://avatars.discourse-cdn.com/v4/letter/g/2bfe46/32.png) [@gsalter](https://forum.sierrawireless.com/u/gsalter)\
**Post date:** [February 21, 2007, 7:22am UTC](https://forum.sierrawireless.com/t/extint-problems/1115/1 "2007-02-21T07:22:18Z")

</div>

I am trying to use the IRQ and ExtInt services on a Q2686 to monitor when an interrupt (20ms high to low pulse) occurs on INT1 . I do have the Real-Time feature enabled but I am experiencing problems: I have taken two approaches, each with it’s own problems:

1: I didn’t subscribe to the IRQ and ExtInt services, but rather subcribe to the unsolicited response of “+WIND: 12,1”. This works well, but every once in a while the CPU resets (Power up reset, not an Exception error). Can anyone tell me why and how do I solve this problem.

Approach 2: I subscribe to the IRQ and ExtInt services. I have followed the code in the sample application and the ADL user guide. The problem is every time I get an interrupt pulse the CPU resets with an Exception error. Any ideas?

Thank you,

Geoff

---

<div class="post-metadata">

**Author:** ![rajanardhan](https://avatars.discourse-cdn.com/v4/letter/r/aca169/32.png) [@rajanardhan](https://forum.sierrawireless.com/u/rajanardhan)\
**Post date:** [December 5, 2008, 6:47am UTC](https://forum.sierrawireless.com/t/extint-problems/1115/2 "2008-12-05T06:47:29Z")

</div>

Mr. Geoff,

Could you solve this problem?

Janardhan

---

<div class="post-metadata">

**Author:** ![trthaithong](https://avatars.discourse-cdn.com/v4/letter/t/22d042/32.png) [@trthaithong](https://forum.sierrawireless.com/u/trthaithong)\
**Post date:** [December 9, 2008, 7:16am UTC](https://forum.sierrawireless.com/t/extint-problems/1115/3 "2008-12-09T07:16:05Z")

</div>

Hi,  
You can check the signal connect to the EXTINT pin is too fast? So it does not finish the interrupt handler yet, another interrupt has occured. Maybe it is the reason for the reset happen.  
ttt

---

<div class="post-metadata">

**Author:** ![Kaare](https://avatars.discourse-cdn.com/v4/letter/k/8dc957/32.png) [@Kaare](https://forum.sierrawireless.com/u/Kaare)\
**Post date:** [December 11, 2008, 12:09pm UTC](https://forum.sierrawireless.com/t/extint-problems/1115/4 "2008-12-11T12:09:40Z")

</div>

How do get the interrupt system to run?

I don’t even receive the +WIND 12 event, even if i have all indications enabled with +WIND=32767