Thanks Richard for reply,
I have tried this option from my side but still i have observing following
error
ptp4l_new[76369.348]: timed out while polling for tx timestamp
ptp4l_new[76369.348]: increasing tx_timestamp_timeout may correct this
issue, but it is likely caused by a driver bug
ptp4l_new[76369.348]: port 1: send delay request failed
ptp4l_new[76369.348]: port 1: UNCALIBRATED to FAULTY on FAULT_DETECTED
(FT_UNSPECIFIED)
I have done changes as below to avoid error but still time sync is not
happening. Any further pointers?
rgoyal@rgoyal-ubuntu-1:~/linuxptp$ git diff
diff --git a/port.c b/port.c
index 58fbe66..c3f1bd5 100644
--- a/port.c
+++ b/port.c
@@ -1376,14 +1376,18 @@ int port_delay_request(struct port *p)
msg->header.flagField[0] |= UNICAST;
}
- if (port_prepare_and_send(p, msg, TRANS_EVENT)) {
- pr_err("port %hu: send delay request failed", portnum(p));
- goto out;
- }
- if (msg_sots_missing(msg)) {
- pr_err("missing timestamp on transmitted delay request");
- goto out;
- }
+ if (port_prepare_and_send(p, msg, TRANS_ONESTEP)) {
+ pr_err("RG: port %hu: send delay request fAiled",
portnum(p));
+ goto out;
+ } else {
+ goto out_1;
+ }
+ if (msg_sots_missing(msg)) {
+ pr_err("RG: missing timestamp on transmitted delay
request");
+ goto out;
+ }
+
+out_1:
my PTP.cfg file as as following
[global]
#
# Default Data Set
#
twoStepFlag 0
gmCapable 1
priority1 248
priority2 248
domainNumber 0
clockClass 248
clockAccuracy 0xFE
offsetScaledLogVariance 0xFFFF
free_running 0
freq_est_interval 1
#
# Port Data Set
#
logAnnounceInterval 1
logSyncInterval -3
logMinPdelayReqInterval 0
announceReceiptTimeout 3
syncReceiptTimeout 3
delayAsymmetry 0
fault_reset_interval 4
neighborPropDelayThresh 800
min_neighbor_prop_delay -20000000
# �
# Run time options
#
assume_two_step 0
logging_level 6
path_trace_enabled 1
follow_up_info 0
hybrid_e2e 0
tx_timestamp_timeout 1
use_syslog 1
verbose 0
summary_interval 0
kernel_leap 1
check_fup_sync 0
#
# Servo options
#
pi_proportional_const 0.0
pi_integral_const 0.0
pi_proportional_scale 0.0
pi_proportional_exponent -0.3
pi_proportional_norm_max 0.7
pi_integral_scale 0.0
pi_integral_exponent 0.4
pi_integral_norm_max 0.3
step_threshold 0.0
first_step_threshold 0.00002
max_frequency 900000000
clock_servo pi
sanity_freq_limit 200000000
ntpshm_segment 0
#
# Transport options
#
transportSpecific 0x1
ptp_dst_mac 01:1B:19:00:00:00
p2p_dst_mac 01:80:C2:00:00:0E
uds_address /var/run/ptp4l
#
# Default interface options
#
network_transport L2
delay_mechanism P2P
time_stamping onestep
tsproc_mode filter
delay_filter moving_median
delay_filter_length 10
egressLatency 0
ingressLatency 0
boundary_clock_jbod 0
regards,
Rakesh G
On Wed, Feb 5, 2020 at 10:46 AM Richard Cochran <richardcoch...@gmail.com>
wrote:
> On Wed, Feb 05, 2020 at 12:09:07AM +0530, rakesh goyal wrote:
> > I am trying to set up one-step-syncing using ptp4l build from source code
> > https://github.com/richardcochran/linuxptp.git. Is it supported by
> ptp4l?
>
> Yes it is fully supported, but it does require hardware support.
> As of version 1.9, use the configuration options,
>
> time_stamping onestep
> twoStepFlag 0
>
> to enable this mode. For version 1.8 and earlier, use this;
>
> time_stamping hardware
> twoStepFlag 0
>
> > Could you please let me know which branch/tag should i use.
>
> This mode has been supported all along, iirc, and so any version will do.
>
> HTH,
> Richard
>
>
>
--
|2/-\1<|=&|-|
_______________________________________________
Linuxptp-users mailing list
Linuxptp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-users
