- 30 Aug, 2022 1 commit
-
-
Omar Gabella authored
-
- 26 Aug, 2022 2 commits
-
-
Omar Gabella authored
-
Omar Gabella authored
-
- 24 Aug, 2022 1 commit
-
-
Omar Gabella authored
concern DOMs (or other nodes) not concern the Bases. New additions will come for Bases with BROADCAST_BASE statements.
-
- 23 Aug, 2022 1 commit
-
-
Vincent van Beveren authored
-
- 10 May, 2022 2 commits
-
-
Omar Gabella authored
-
Omar Gabella authored
-
- 22 Feb, 2022 1 commit
-
-
Omar Gabella authored
KM3NET BROADCAST : - locking_enable in wr_link_on -> After unplug/plug or disable/enable the WR master port, the CLB stay locked in Uninitialized servo state because the spll stays locked. - New WR state WRS_BROADCAST -> added for km3net monitoring via net.wr_st_gen variable. - wr_servo_reset if errcount > 5 -> to play in a safe way.
-
- 09 Feb, 2022 1 commit
-
-
Omar Gabella authored
-
- 08 Feb, 2022 1 commit
-
-
Omar Gabella authored
-
- 27 Dec, 2021 1 commit
-
-
Omar Gabella authored
-
- 22 Dec, 2021 1 commit
-
-
Omar Gabella authored
-
- 20 Dec, 2021 1 commit
-
-
Omar Gabella authored
KM3NET BROADCAST: We don't apply the HAS_FAULTS option with the broadcast configuration. We can enable the CONFIG_WRPC_FAULTS in parallel.
-
- 07 Apr, 2021 3 commits
-
-
Omar Gabella authored
If errcount > 5 set wrModeOn to False. This modifications are needed because each time we reach an errcount > 5 (t1 timestamp flagged as incorrect 5 consecutive times), we get stucked on uninitialized servo state.
-
Omar Gabella authored
KM3NET BROADCAST : Reset the timeout PP_TO_FAULT after receiving a follow-up message. Normally this is done after a response message, but we don't handle it.
-
Omar Gabella authored
KM3NET BROADCAST : set wrMode equal to WR_SLAVE in wr_handle_announce instead of wr_handshake_init (because in broadcast mode we never start the handshake). + clear pp_lib_handle_announce.
-
- 26 Feb, 2021 1 commit
-
-
Omar Gabella authored
KM3NET BROADCAST : Force the WRS_WR_LINK_ON after recive ANNOUNCE message in wr_handle_announce instead of pp_lib_handle_announce.
-
- 22 Feb, 2021 2 commits
-
-
Omar Gabella authored
KM3NET BROADCAST : Reset the wr_servo if the TRACK_PHASE is not reached after a configurable number of iterations.
-
Omar Gabella authored
-
- 04 Dec, 2020 5 commits
-
-
Omar Gabella authored
-
Omar Gabella authored
times t1 and t2 are used to compute the offset between the master and the slave cf wr_e2e_offset_downlink().
-
Omar Gabella authored
-
Omar Gabella authored
-
Omar Gabella authored
doing handshake.
-
- 02 Aug, 2018 2 commits
-
-
Adam Wujek authored
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>
-
Alessandro Rubini authored
Signed-off-by: Alessandro Rubini <rubini@gnudd.com> abscal: simplify code related to CONFIG_ABSCAL Signed-off-by: Adam Wujek <adam.wujek@cern.ch>
-
- 04 Sep, 2017 1 commit
-
-
Adam Wujek authored
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>
-
- 07 Aug, 2017 1 commit
-
-
Adam Wujek authored
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>
-
- 01 Aug, 2017 2 commits
-
-
Adam Wujek authored
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>
-
Adam Wujek authored
For links longer than ~13km, a value (uint32_t) returned from a function __div64_32 shifted by 16 bits overflowed, introducing PPS offset. Bug introduced in the commit: 35eef679 time: introduce a new unified data structure Signed-off-by: Adam Wujek <adam.wujek@cern.ch>
-
- 31 Jul, 2017 1 commit
-
-
Adam Wujek authored
For whatever reason we perform a normalization on an incorrect timestamp, don't treat is as an negative value. Signed-off-by: Adam Wujek <adam.wujek@cern.ch>
-
- 06 Jul, 2017 1 commit
-
-
Grzegorz Daniluk authored
This reverts commit a72f6bdc.
-
- 03 Jul, 2017 1 commit
-
-
Adam Wujek authored
Remove warning that HAS_ABSCAL is redefined Signed-off-by: Adam Wujek <adam.wujek@cern.ch>
-
- 29 Jun, 2017 2 commits
-
-
Adam Wujek authored
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>
-
Adam Wujek authored
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>
-
- 23 Jun, 2017 3 commits
-
-
Alessandro Rubini authored
This is a port of previous work by Peter Jansweijer from nikhef. To perform absolute calibration, we need a grand-master look-alike mode that sends sync once a second (and hopefully slightly after the pps signal). Using a special gateware that sends a pulse whenever a frame is transmitted and received, users can correlate collected timestamps (T1 and T4), this special pulse and the pps pulse of the node. The procedure for absolute calibration is described in http://www.ohwr.org/attachments/4542/WhiteRabbitAbsoluteCalibrationProcedure.pdf Another commit, in wrpc-sw, adds "mode abscal" for this feature to be used. Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
-
Alessandro Rubini authored
This is used by absolute calibration, where we send sync and no f-up. We may implement two-step flag, actually, but this is an easier choice. Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
-
Alessandro Rubini authored
format is "%9d.%09d.%03d". This is not properly a flating point number, but counting 9 digits is already heavy, I'd better not have a 12-digit field (which, btw, will be wrongly converted by 32-bit parsers). This comes from a similar change by Peter Jansweijer from nikhef, for absolute-calibration work. Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
-
- 12 Jun, 2017 2 commits
-
-
Alessandro Rubini authored
The previous commit is not enough as a fix. This may happen: - we invalidate stamps after processing them - we send request - get reply, loose reply-fup - send request - loose reply, get f-up So we now invalidate when sending the request. And invalidate t4 alone as the beautifulness and symmetry of the previous commit is lost anyways. Note: there no need to invalidate stamps in e2e mode, because checking the sequence number to validate RX frames is enough. But here all replies match the sequence number, so the problem is not caught and stamps from different tuples are mixed. Example beofre this commit, with trimmed stamps (was 1497283863): diag-frames-1-wr1: SENT 54 bytes at 863.333173928 (pdelay_req) diag-frames-1-wr1: RECV 54 bytes at 863.334158796 (type 3, pdelay_resp) diag-frames-1-wr1: Drop received frame diag-frames-1-wr1: SENT 54 bytes at 864.479336104 (pdelay_req) diag-frames-1-wr1: Drop received frame diag-frames-1-wr1: RECV 54 bytes at 864.481095164 (type a, presp_follow_up) diag-servo-2-wr1: servo:t3 = 864:479336104:0 diag-servo-2-wr1: servo:t4 = 863:333174267:586 diag-servo-2-wr1: servo:t5 = 864:480295312:0 diag-servo-2-wr1: servo:t6 = 863:334158796:773 diag-servo-2-wr1: ->mdelay = -2:-292298352:359 Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
-
Alessandro Rubini authored
The code is checking the sequence number of pdelay-rep and pdelay-rep-fup, but we may miss the reply and get the f-up. The result was something like this (first tuple is ok, next is wrong): diag-servo-2-wr1: servo:t3 = 1497279009:22584224:0 diag-servo-2-wr1: servo:t4 = 1497279009:22584574:759 diag-servo-2-wr1: servo:t5 = 1497279009:23564032:0 diag-servo-2-wr1: servo:t6 = 1497279009:23564365:547 diag-servo-2-wr1: ->mdelay = 0:684:306 diag-servo-2-wr1: servo:t3 = 1497279009:663586672:0 diag-servo-2-wr1: servo:t4 = 1497279009:22584574:759 diag-servo-2-wr1: servo:t5 = 1497279009:683142000:0 diag-servo-2-wr1: servo:t6 = 1497279009:23564365:547 diag-servo-2-wr1: ->mdelay = -1:-300579732:306 Here, t4 and t6 are old. The former is the receipt of the request, send back to the "slave" in the pdelay-reply payload; the latter is the receive time of such frame. We now invalidate t4 and t5 when using the tuple. They are the two "remote" times, one sent back in the response and the other sent back in the response-fup. Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
-