| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
This happened when the overflow counter for ticks_ms() was interrupted
by an external hard interrupt (issue #3076).
|
|
|
|
| |
So now ticks_ms can count up to the full 30 bits. Fixes issue #2412.
|
| |
|
|
|
|
| |
So ets_loop_iter is now only disabled when using machine.disable_irq.
|
|
|
|
|
|
| |
ets_loop_iter processes pending tasks, and tasks are considered lower
priority than interrupts, so tasks shouldn't be processed if interrupts
are disabled.
|
| |
|
|
|
|
|
| |
FIRST_PRIO=2 works but using 0 is hopefully safer, and can anyway be
optimised in the future.
|
|
|
|
|
| |
SDK 1.5.0 has a task with priority 3: ets_task(401001f4, 3, 3fff9808, 4).
Recognizing SDK version requires the latets esp-open-sdk build.
|
|
|
|
|
| |
Otherwise, if handler calls recursive event loop, there's infinite
recursion (because the loop calls the same handler on same event again).
|
| |
|
|
This implementation provides the same interface and uses the same
datastructures as used by BootROM, i.e. is a drop-in replacement for it.
But it offers one advantage: it allows to run single iteration of
event-pumping loop.
Original BootROM function are renamed, prefixed with underscore. There's
a switch which allows to use forward calls to them, for compatibility
testing.
The implementation also includes workarounds for hardware timer handler,
and these workarounds may be SDK version specific.
|