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
>> vs. system time
2706479 Timer1Clock is UP counter
4706622 System time elapsed: 2000000
4706654 Ticks: 0 (4294967258 - 4294967258)
4706696 Ratio: x 0.
4706839 Apparent time: 0
FAIL: abs(int(us - duration)) < 500
FAIL in `void ClockTestTemplate<Clock, TimeType>::execute() [with Clock = Timer1Clock<TIMER_CLKDIV_16>; TimeType = long unsigned int]`
!!!! Test Group 'TimeSource: Timer1Clock/5MHz/32-bit/microseconds' FAILED !!!!
Up-counters are expected to read back as zero, but this shows as 4294967258 == 0xFFFFFFDA.
The text was updated successfully, but these errors were encountered:
>> vs. system time
25457812 Timer1Clock is UP counter
27457951 System time elapsed: 2000000
27457992 Ticks: 0 (4294967255 - 4294967255)
27458038 Ratio: x 0.
27458225 Apparent time: 0
assert failed: void ClockTestTemplate<Clock, TimeType>::execute() [with Clock = Timer1Clock<TIMER_CLKDIV_16>; TimeType = long unsigned int] Clocks.cpp:74 (false)
Cause: As it's a down-counter, must initialise count value (call timer1_write) as it doesn't auto-wrap. This is just an issue with the test code; not a bug in the driver.
Current develop fails for esp32c3:
Up-counters are expected to read back as zero, but this shows as 4294967258 == 0xFFFFFFDA.
The text was updated successfully, but these errors were encountered: