You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Vincent Dupont ad0f0877cc tests,examples: sort BOARD_INSUFFICIENT_MEMORY alphabetically 5 years ago
Makefile tests,examples: sort BOARD_INSUFFICIENT_MEMORY alphabetically 5 years ago tests: add README for xtimer_drift 5 years ago
main.c tests: optimize mem size of xtimer_drift 5 years ago

xtimer_drift test application

Make note of the PC clock when starting this test. Let it run for a while, and compare the printed time against the expected time from the PC clock. The difference is the RIOT timer drift, this is likely caused by either:

  • an inaccurate hardware timer, or
  • bugs in the software (xtimer or periph/timer)

This test will run a periodic timer every TEST_INTERVAL microseconds (TEST_HZ). The current time will be printed once per second, along with the difference between the actual and expected xtimer_now value. The first output variable drift, represents the total offset since start between xtimer_now and the expected time. The second output variable jitter, represents the difference in drift from the last printout. Two other threads are also running only to cause CPU load with extra interrupts and context switches.