de1f1dd164
Before, both uwTick and mp_hal_ticks_ms() were used as clock source. That assumes, that these two are synchronous and start with the same value, which may be not the case for all ports. If the lag between uwTick and mp_hal_ticks_ms() is larger than the timer interval, the timer would either rush up until the times are synchronous, or not start until uwTick wraps over. As suggested by @dpgeorge, MICROPY_SOFT_TIMER_TICKS_MS is now used in softtimer.c, which has to be defined in a port's mpconfigport.h with the variable that holds the SysTick counter. Note that it's not possible to switch everything in softtimer.c to use mp_hal_ticks_ms() because the logic in SysTick_Handler that schedules soft_timer_handler() uses (eg on mimxrt) the uwTick variable directly (named systick_ms there), and mp_hal_ticks_ms() uses a different source timer. Thus it is made fully configurable. |
||
|---|---|---|
| .. | ||
| libc | ||
| memzip | ||
| netutils | ||
| readline | ||
| runtime | ||
| timeutils | ||
| tinyusb | ||
| upytesthelper | ||
| README.md | ||
This directory contains libraries, utilities and helper code developed specifically for this project. The code is intended to be portable and usable by any port.