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
sketch with 3 additional FreeRTOS tasks leads to a significant lengthening of the set poriodes of the rmt module. I was able to narrow it down to the Onewire or the Dalles temperature library. If I remove Onewire completely from the sketch, then the times are correct again.
which surprises me a bit, because the onewire library doesn't seem to use rmt. And it's just fed with data and then runs in hardware, at least that's my assumption.
can someone confirm the problem?
The text was updated successfully, but these errors were encountered:
Hallo,
I looked at the OneWire code again and saw that this library deactivates the interrupts in order to maintain the timings. It's certainly not a problem for non-RTOS applications. But it will certainly stop all hardware timers and thus halt the tasks.
I don't expect a solution to the problem, but perhaps this insight will help others if they encounter timing problems in their RTOs application when using this library.
All bus activities are performed respecting open-drain character of the 1-wire protocol.
During normal 1-wire activities, the master MCU GPIO controlling the bus is never set high
(providing direct voltage source on the bus) instead the GPIO is switched to the reading mode
causing the high state seen on the bus via the pull-up resistor.
ESP32 Wemos Lolin32
sketch with 3 additional FreeRTOS tasks leads to a significant lengthening of the set poriodes of the rmt module. I was able to narrow it down to the Onewire or the Dalles temperature library. If I remove Onewire completely from the sketch, then the times are correct again.
which surprises me a bit, because the onewire library doesn't seem to use rmt. And it's just fed with data and then runs in hardware, at least that's my assumption.
can someone confirm the problem?
The text was updated successfully, but these errors were encountered: