5 Commits (a699ff34068214a9e829c584401769c2ee22a319)

Author	SHA1	Message	Date
Kevin Bracey	8e3e19837a	More Chrono test fixes ... * Timer test - handle removal of Timer(ticker_data_t *) * Timer test - use Chrono, don't test deprecated methods * Kernel tick count test - TEST_ASSERT_WITHIN -> TEST_ASSERT_INT_WITHIN * Mutex test - fix up Chrono changes * SysTimer test - adapt to SysTimer Chrono changes * Thread test - use Chrono * SysTimer - devirtualize destructor	2020-04-27 10:19:08 +03:00
Kevin Bracey	f4e0ea2c75	Add Chrono support to Kernel and SysTimer	2020-04-27 10:19:08 +03:00
Kevin Bracey	de915a034b	Correct SysTimer absolute time calculations ... `SysTimer::set_wake_time` incorrectly assumed that the `SysTimer`s tick count and the underlying HAL timer had the same zero base. This normally holds, at least approximately, in RTOS builds where the HAL timer starts from zero at the same time the SysTimer is initialised. But in bare metal builds, the HAL timer could be started some time before the SysTimer, giving a significant discrepancy. Beyond that, there's no requirement for HAL timers to start from zero in the spec. Record the HAL timer start time to get the conversion right.	2020-01-29 15:28:20 +02:00
Kevin Bracey	a1bbbb8845	SysTimer: Suppress implicit virtual warning	2019-12-05 15:48:36 +02:00
George Psimenos	bd95c53a4c	Move source files and add Doxygen labels	2019-09-10 14:31:24 +01:00