-
Notifications
You must be signed in to change notification settings - Fork 13.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
noTone() does not release timer1 #7364
Comments
That's why I'm doing ESP. restart () between tests as I'm looking at the two PRs - don't want invalid test conditions left over from a previous test. ;-) |
@dok-net thanks for the find about duplicate with #4598. Is this the problem and workaround? From here, thanks to @AlfonsMittelmeyer: // ETS_FRC_TIMER1_NMI_INTR_ATTACH(NULL); // doesn't work, bug in sdk for core version 2.4.0 and 2.4.1
ETS_FRC_TIMER1_INTR_ATTACH(shared_timer_isr,NULL); |
Once attached as NMI, can only do NMI thereafter. The chatty stuff by AlfonsMittelmyer is OT and TL;DR
|
@devyte More precisely: This:
is not reverted by
Because, as we well know, startWaveform works, re-attaching the ISR as NMI handler, but one cannot ETS_FRC_TIMER1_INTR_ATTACH() , any non-NMI handler never gets called.
In
In
and
|
@dok-net thanks, that is the explanation I was looking for. |
Still not fixed?) Tested today - use tone(..) and you need to power off chip for releasing timer1 |
Issue:
After issuing a “tone(D1,1550); delay(500); noTone(D1);” sequence, you can no longer use timer1 (I suspect as something to do with the tone-interrupt still using it)?
I note that the below 2 issues/commits do not appear to have effected/fixed this:
Below is an example sketch:
The text was updated successfully, but these errors were encountered: