Skip to content
Snippets Groups Projects
  1. Jun 07, 2019
  2. Jun 06, 2019
  3. Jun 05, 2019
  4. Jun 04, 2019
  5. May 29, 2019
  6. May 28, 2019
  7. May 27, 2019
    • Jean-Claude BAU's avatar
      [Issue:#196] WR time not set properly in GM mode · 36accb7e
      Jean-Claude BAU authored
      The WR time is set in GM mode as follow :
      1/ At startup the NTP time is set using wr_date script
      2/ PPSi calls the tool wr_date with parameters "set host". It will be
      called every time it detects a PLL transition from UNLOCKED to LOCKED
      state. Also PPSi provide a error counter 'gmUnlockErr' which gives the
      number of time the PLL unlocked.
      3/ Parameters "-v set host" in wr_date tool, set only the second part of
      the WR time. The time is set in a middle of two WR seconds ticks.
      36accb7e
    • Jean-Claude BAU's avatar
      WR protocol extension improvements · 4da70724
      Jean-Claude BAU authored
      - Give priority to the time-out and not the number of msg repetitions
      - Call also wr_handshake_fail() function when a time-out is detected.
      4da70724
  8. May 24, 2019
  9. May 20, 2019
    • Jean-Claude BAU's avatar
      [Feature:#128] Improve GM status · b66d61fe
      Jean-Claude BAU authored
      - Add a new state machine available for all timing modes ( Free running
      master, Grand master and boundary clock)
      - State is stored in pp_globals, field timingModeLockingState
      - The 3 main states are :
      -- Locking: Waiting for PLL locked
      -- Locked: PLL is locked
      -- Error: PLL is unlocked but was locked before
      - Changing the timing mode will reset the state to 'Locking'
      b66d61fe
  10. May 15, 2019
  11. May 14, 2019
  12. May 09, 2019
    • Jean-Claude BAU's avatar
      WR/PTP protocol detection + WR protocol improvement · 59838a0d
      Jean-Claude BAU authored
      - Simplify how an instance switch from WR to PTP protocol and vice-versa
      - Change the WR state machine: When an unexpected WR signaling message
      is received, the state is forced to IDLE. Solve handshake issue when
      instance is waiting for an answer with a long time-out and in the other
      side the PPSi process is restarted. In this use case the handshake will
      fail.
      59838a0d
  13. May 07, 2019
  14. May 03, 2019
  15. May 02, 2019
  16. Apr 30, 2019
  17. Apr 10, 2019
  18. Apr 09, 2019