Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feature: ContikiClock provides clock drift simulate and control #51

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Commits on May 7, 2020

  1. ContikiClock enhance API controling etimerPeriod. Just for etimer cod…

    …e clarify
    
    * temporary need for compatibily with other patched.
    alexrayne committed May 7, 2020
    Configuration menu
    Copy the full SHA
    27ae693 View commit details
    Browse the repository at this point in the history

Commits on Oct 5, 2020

  1. +ContikiClock:clockDrift simulation - now can simulate clock drifting…

    … for specified [ppm]
    
    +     rtcTime() - now rTimer value not equals to simulation time, but takes to acount clockDrift
    +     setClockDrift - provide random clockDrift from specified range
    +     provided UI - there shows time and drifts, and allow setup drift value.
    alexrayne committed Oct 5, 2020
    Configuration menu
    Copy the full SHA
    992127a View commit details
    Browse the repository at this point in the history
  2. ! ContikiClock:clockDrift simulation now protect simRtimerNextExpirat…

    …ionTime vs
    
            rTime values decimated by clock drift.
    
            if drift go rtc faster, then appears jumps in rtc sequence, to realise speedup rtc sv simulation time.
            if mote waits value exact in jumped gap, then it's firmware may loose awake.
            To prevent it, do correct simRtimerNextExpirationTime, so that go after jumped gap, if need.
    alexrayne committed Oct 5, 2020
    Configuration menu
    Copy the full SHA
    2a6f7d8 View commit details
    Browse the repository at this point in the history