Re: attachInterrupt missing 1uS pulses
Posted: Sat Jun 04, 2016 3:11 amThere could be a few reasons for that.
The GPIO does not run at 80 or 160 MHz. It actually runs slower.
Since the ESP does not properly trigger edges (it triggers on falling or rising regardless) we read the GPIO to determine what is the level of the pins at the moment of interrupt and that could report wrong pin level that leads to the callback not being called.
Overall 1us pulses are really hard to catch if you are using the Arduino routines. If you do not use the Arduino methods but rather attach directly to the interrupt, you might be able to pick that 1us pulse.
The GPIO does not run at 80 or 160 MHz. It actually runs slower.
Since the ESP does not properly trigger edges (it triggers on falling or rising regardless) we read the GPIO to determine what is the level of the pins at the moment of interrupt and that could report wrong pin level that leads to the callback not being called.
Overall 1us pulses are really hard to catch if you are using the Arduino routines. If you do not use the Arduino methods but rather attach directly to the interrupt, you might be able to pick that 1us pulse.