ESP8266 Developer Zone The Official ESP8266 Forum 2016-03-25T15:48:59+08:00 https://bbs.espressif.com:443/feed.php?f=66&t=1773 2016-03-25T15:48:59+08:00 2016-03-25T15:48:59+08:00 https://bbs.espressif.com:443/viewtopic.php?t=1773&p=6224#p6224 <![CDATA[Re: PWM duty not set correct in RTOS & NONOS SDK]]>
Again the request to reply to this issue.
this issue really hampers the use of pwm functionality.

Tested also in the NONOS version with the same results

Statistics: Posted by hreintke — Fri Mar 25, 2016 3:48 pm


]]>
2016-03-06T17:28:25+08:00 2016-03-06T17:28:25+08:00 https://bbs.espressif.com:443/viewtopic.php?t=1773&p=5988#p5988 <![CDATA[Re: PWM duty not set correct in RTOS SDK]]>
Can you react in this issue.
It showed that also the NONOS version has the same erratic behavior.

As we are using it in an framework implementation (Sming) there is no possibility to enforce the timing between the setDuty(..);pwm_start(), setDuty(..);pwm_start()

Statistics: Posted by hreintke — Sun Mar 06, 2016 5:28 pm


]]>
2016-02-15T18:13:35+08:00 2016-02-15T18:13:35+08:00 https://bbs.espressif.com:443/viewtopic.php?t=1773&p=5749#p5749 <![CDATA[PWM duty not set correct in RTOS SDK]]>
When multiple setduty(...);pwm_start() are called to fast, pwm is not correctly set.

When using :

Code:

setduty(..);pwm_start()
wait some time
setduty(..);pwm_start()


It works OK,
But when using :

Code:

setduty(..);pwm_start()
setduty(..);pwm_start()


pwm behavior is not correct.
As the setduty(..);pwm_start() can come from different threads, interrupts. There cannot be a guarantee that there is a long enough period between the two calls.

Statistics: Posted by hreintke — Mon Feb 15, 2016 6:13 pm


]]>