https://community.nxp.com/t5/i-MX-Processors/Error-when-using-hardware-timestamp-in-ptp/m-p/1445073#M189428 <P>Error occured when ptp using hardware timestamp, does anyone met the same before and how it be fixed?</P><P>root@imx8mqevk:~# ethtool -T eth0<BR />Time stamping parameters for eth0:<BR />Capabilities:<BR />hardware-transmit (SOF_TIMESTAMPING_TX_HARDWARE)<BR />software-transmit (SOF_TIMESTAMPING_TX_SOFTWARE)<BR />hardware-receive (SOF_TIMESTAMPING_RX_HARDWARE)<BR />software-receive (SOF_TIMESTAMPING_RX_SOFTWARE)<BR />software-system-clock (SOF_TIMESTAMPING_SOFTWARE)<BR />hardware-raw-clock (SOF_TIMESTAMPING_RAW_HARDWARE)<BR />PTP Hardware Clock: 0<BR />Hardware Transmit Timestamp Modes:<BR />off (HWTSTAMP_TX_OFF)<BR />on (HWTSTAMP_TX_ON)<BR />Hardware Receive Filter Modes:<BR />none (HWTSTAMP_FILTER_NONE)<BR />all (HWTSTAMP_FILTER_ALL)<BR />root@imx8mqevk:~# sudo ptp4l -i eth0 -m -H<BR />ptp4l[2861.116]: selected /dev/ptp0 as PTP clock<BR />ptp4l[2861.117]: driver changed our HWTSTAMP options<BR />ptp4l[2861.117]: tx_type 1 not 1<BR />ptp4l[2861.117]: rx_filter 1 not 12<BR />ptp4l[2861.118]: port 1: INITIALIZING to LISTENING on INITIALIZE<BR />ptp4l[2861.118]: port 0: INITIALIZING to LISTENING on INITIALIZE<BR />ptp4l[2861.118]: port 1: link up<BR />ptp4l[2868.709]: port 1: LISTENING to MASTER on ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES<BR />ptp4l[2868.709]: selected best master clock e6b036.fffe.a0450a<BR />ptp4l[2868.709]: assuming the grand master role<BR />ptp4l[2869.711]: timed out while polling for tx timestamp<BR />ptp4l[2869.711]: increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bug<BR />ptp4l[2869.711]: port 1: send sync failed<BR />ptp4l[2869.711]: port 1: MASTER to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)<BR />ptp4l[2885.713]: driver changed our HWTSTAMP options<BR />ptp4l[2885.713]: tx_type 1 not 1<BR />ptp4l[2885.713]: rx_filter 1 not 12<BR />ptp4l[2885.713]: port 1: FAULTY to LISTENING on FAULT_CLEARED<BR />ptp4l[2893.506]: port 1: LISTENING to MASTER on ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES<BR />ptp4l[2893.506]: selected best master clock e6b036.fffe.a0450a<BR />ptp4l[2893.506]: assuming the grand master role<BR />ptp4l[2895.508]: timed out while polling for tx timestamp<BR />ptp4l[2895.508]: increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bug<BR />ptp4l[2895.508]: port 1: send sync failed<BR />ptp4l[2895.508]: port 1: MASTER to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)</P> Mon, 18 Apr 2022 10:36:16 GMT shenfungping 2022-04-18T10:36:16Z https://community.nxp.com/t5/i-MX-Processors/Error-when-using-hardware-timestamp-in-ptp/m-p/1445073#M189428 <P>Error occured when ptp using hardware timestamp, does anyone met the same before and how it be fixed?</P><P>root@imx8mqevk:~# ethtool -T eth0<BR />Time stamping parameters for eth0:<BR />Capabilities:<BR />hardware-transmit (SOF_TIMESTAMPING_TX_HARDWARE)<BR />software-transmit (SOF_TIMESTAMPING_TX_SOFTWARE)<BR />hardware-receive (SOF_TIMESTAMPING_RX_HARDWARE)<BR />software-receive (SOF_TIMESTAMPING_RX_SOFTWARE)<BR />software-system-clock (SOF_TIMESTAMPING_SOFTWARE)<BR />hardware-raw-clock (SOF_TIMESTAMPING_RAW_HARDWARE)<BR />PTP Hardware Clock: 0<BR />Hardware Transmit Timestamp Modes:<BR />off (HWTSTAMP_TX_OFF)<BR />on (HWTSTAMP_TX_ON)<BR />Hardware Receive Filter Modes:<BR />none (HWTSTAMP_FILTER_NONE)<BR />all (HWTSTAMP_FILTER_ALL)<BR />root@imx8mqevk:~# sudo ptp4l -i eth0 -m -H<BR />ptp4l[2861.116]: selected /dev/ptp0 as PTP clock<BR />ptp4l[2861.117]: driver changed our HWTSTAMP options<BR />ptp4l[2861.117]: tx_type 1 not 1<BR />ptp4l[2861.117]: rx_filter 1 not 12<BR />ptp4l[2861.118]: port 1: INITIALIZING to LISTENING on INITIALIZE<BR />ptp4l[2861.118]: port 0: INITIALIZING to LISTENING on INITIALIZE<BR />ptp4l[2861.118]: port 1: link up<BR />ptp4l[2868.709]: port 1: LISTENING to MASTER on ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES<BR />ptp4l[2868.709]: selected best master clock e6b036.fffe.a0450a<BR />ptp4l[2868.709]: assuming the grand master role<BR />ptp4l[2869.711]: timed out while polling for tx timestamp<BR />ptp4l[2869.711]: increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bug<BR />ptp4l[2869.711]: port 1: send sync failed<BR />ptp4l[2869.711]: port 1: MASTER to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)<BR />ptp4l[2885.713]: driver changed our HWTSTAMP options<BR />ptp4l[2885.713]: tx_type 1 not 1<BR />ptp4l[2885.713]: rx_filter 1 not 12<BR />ptp4l[2885.713]: port 1: FAULTY to LISTENING on FAULT_CLEARED<BR />ptp4l[2893.506]: port 1: LISTENING to MASTER on ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES<BR />ptp4l[2893.506]: selected best master clock e6b036.fffe.a0450a<BR />ptp4l[2893.506]: assuming the grand master role<BR />ptp4l[2895.508]: timed out while polling for tx timestamp<BR />ptp4l[2895.508]: increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bug<BR />ptp4l[2895.508]: port 1: send sync failed<BR />ptp4l[2895.508]: port 1: MASTER to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)</P> Mon, 18 Apr 2022 10:36:16 GMT https://community.nxp.com/t5/i-MX-Processors/Error-when-using-hardware-timestamp-in-ptp/m-p/1445073#M189428 shenfungping 2022-04-18T10:36:16Z