You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had a problem with custom servo implementation. I am using hardware serial to parallel port extension. Needed to change servo implementation to send serial code for each servo pulse.
Code crashed in case eps is connecting to a wifi at the time when servo is active. If servo is activated after the connection, it works. If it is activated before the wifi connection (my device works with and without connection), it crashes (attached stac traces).
While debugging, I found, that the new ESP core (2.4.2) calls stopWaveForm in each call to a _digitalWrite. This new implementation (comparing to the pwm-one, the old one,
* Make stopWaveform call interrupt callable
Match the behavior of pre-2.4.2 PWM by allowing stopWaveform to be
called from an interrupt.
Fixes#5247
* Move to O2, save ~500 bytes of code
The actual runtime difference of -O2 vs -O3 is quite small, but -O3
takes ~500 more bytes of code (~300 more in IRAM, ~200 more in PMEM).
Arduino/cores/esp8266/core_esp8266_waveform.c
Line 205 in 2eb5b56
I had a problem with custom servo implementation. I am using hardware serial to parallel port extension. Needed to change servo implementation to send serial code for each servo pulse.
Code crashed in case eps is connecting to a wifi at the time when servo is active. If servo is activated after the connection, it works. If it is activated before the wifi connection (my device works with and without connection), it crashes (attached stac traces).
While debugging, I found, that the new ESP core (2.4.2) calls stopWaveForm in each call to a _digitalWrite. This new implementation (comparing to the pwm-one, the old one,
Arduino/cores/esp8266/core_esp8266_wiring_pwm.c
Line 168 in ea4720b
Suggest to evaluate this change to be included in the esp core.
stacktrace.txt
stacktrace-parsed.txt
The text was updated successfully, but these errors were encountered: