From: Greiner, A. <and...@iv...> - 2023-04-10 19:24:10
Hello,
we are currently trying to use ptp4l on a NVIDIA Orin to sync with a couple of sensors using layer 2 ptp.
However, we get an error when starting the master instance on the Orin.
uam@hubble:~$ sudo ptp4l -i eth0 -m -2 -l 7
ptp4l[922.980]: selected /dev/ptp0 as PTP clock
ptp4l[923.053]: driver rejected most general HWTSTAMP filter
ptp4l[923.059]: ioctl SIOCSHWTSTAMP failed: Numerical result out of range
ptp4l[923.120]: port 1 (eth0): INITIALIZING to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)
ptp4l[923.121]: port 0 (/var/run/ptp4l): INITIALIZING to LISTENING on INIT_COMPLETE
ptp4l[923.121]: port 0 (/var/run/ptp4lro): INITIALIZING to LISTENING on INIT_COMPLETE
As far as I can tell it should be supported by the hardware though, as this output of ethtool suggests:
uam@hubble:~$ ethtool -T eth0
Time stamping parameters for eth0:
Capabilities:
hardware-transmit (SOF_TIMESTAMPING_TX_HARDWARE)
software-transmit (SOF_TIMESTAMPING_TX_SOFTWARE)
hardware-receive (SOF_TIMESTAMPING_RX_HARDWARE)
software-receive (SOF_TIMESTAMPING_RX_SOFTWARE)
software-system-clock (SOF_TIMESTAMPING_SOFTWARE)
hardware-raw-clock (SOF_TIMESTAMPING_RAW_HARDWARE)
PTP Hardware Clock: 0
Hardware Transmit Timestamp Modes:
off (HWTSTAMP_TX_OFF)
on (HWTSTAMP_TX_ON)
one-step-sync (HWTSTAMP_TX_ONESTEP_SYNC)
Hardware Receive Filter Modes:
none (HWTSTAMP_FILTER_NONE)
ptpv1-l4-sync (HWTSTAMP_FILTER_PTP_V1_L4_SYNC)
ptpv1-l4-delay-req (HWTSTAMP_FILTER_PTP_V1_L4_DELAY_REQ)
ptpv2-l4-sync (HWTSTAMP_FILTER_PTP_V2_L4_SYNC)
ptpv2-l4-delay-req (HWTSTAMP_FILTER_PTP_V2_L4_DELAY_REQ)
ptpv2-l2-sync (HWTSTAMP_FILTER_PTP_V2_L2_SYNC)
ptpv2-l2-delay-req (HWTSTAMP_FILTER_PTP_V2_L2_DELAY_REQ)
ptpv2-event (HWTSTAMP_FILTER_PTP_V2_EVENT)
We are using these versions:
ptp4l: 3.1-00224-gd4adf87
kernel: 5.10.104-tegra
Are there any mistakes on our side? What else can we try?
Kind regards,
Andreas
From: Richard C. <ric...@gm...> - 2023-04-10 21:19:12
On Mon, Apr 10, 2023 at 07:09:23PM +0000, Greiner, Andreas wrote:
> We are using these versions:
>
> ptp4l: 3.1-00224-gd4adf87
> kernel: 5.10.104-tegra
>
> Are there any mistakes on our side? What else can we try?
This is likely a bug in the vendor kernel. You should ask them to fix
it for you.
Thanks,
Richard