Thread: [Linuxptp-users] can't get linux PTP to run
PTP IEEE 1588 stack for Linux
Brought to you by:
rcochran
Menu
▾
▴
linuxptp-users
|
From: <Tim...@de...> - 2013-03-15 13:58:51
|
Hi,
I'm having trouble to get started with LinuxPPT.
I'm using a custom x86 3.2.37 Kernel with Real Time support. I'm using an "e1000e Intel 82574" with should be supported.
I activated :
<M> PPS support
[*] PPS debugging messages
[*] PPS kernel consumer support
*** PPS clients support ***
<M> Kernel timer client (Testing client, use for debug)
<M> PPS line discipline
<M> Parallel port PPS client
<M> PPS client using GPIO
*** PPS generators support ***
and
<M> PTP clock support
*** Enable PHYLIB and NETWORK_PHY_TIMESTAMPING to see the additional
After installing I've tried to get started with creating a Master using "$ ptp4l -S -i eth2 -m -q" but I get the errors:
ptp4l[14927.233]: port 1: get_ts_info not supported
ptp4l[14927.235]: port 1: INITIALIZING to LISTENING on INITIALIZE
ptp4l[14927.235]: port 0: INITIALIZING to LISTENING on INITIALIZE
ptp4l[14933.235]: port 1: LISTENING to MASTER on ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES
ptp4l[14934.242]: recvmsg tx timestamp failed: Resource temporarily unavailable
ptp4l[14934.242]: port 1: send sync failed
ptp4l[14934.242]: port 1: MASTER to FAULTY on FAULT_DETECTED
ptp4l[14950.245]: port 1: FAULTY to LISTENING on FAULT_CLEARED
ptp4l[14956.245]: port 1: LISTENING to MASTER on ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES
ptp4l[14957.252]: recvmsg tx timestamp failed: Resource temporarily unavailable
ptp4l[14957.252]: port 1: send sync failed
ptp4l[14957.252]: port 1: MASTER to FAULTY on FAULT_DETECTED
ptp4l[14973.254]: port 1: FAULTY to LISTENING on FAULT_CLEARED
ptp4l[14979.254]: port 1: LISTENING to MASTER on ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES
...
or :
$ ptp4l -i eth2 -L -m
ptp4l[314.690]: port 1: get_ts_info not supported
ptp4l[314.692]: driver rejected most general HWTSTAMP filter
ptp4l[314.692]: ioctl SIOCSHWTSTAMP failed: Operation not supported
ptp4l[314.693]: port 1: INITIALIZING to FAULTY on INITIALIZE
ptp4l[314.693]: port 0: INITIALIZING to LISTENING on INITIALIZE
And on the slave "ptp4l -S -i eth2 -s -m -q"
ptp4l[14964.111]: port 1: get_ts_info not supported
ptp4l[14964.113]: port 1: INITIALIZING to LISTENING on INITIALIZE
ptp4l[14964.113]: port 0: INITIALIZING to LISTENING on INITIALIZE
what am I doing wrong? In /dev/ there is no ptp device.
Would be nice if someone can give me a hint.
Cheers
B.Rapp
|
|
From: Richard C. <ric...@gm...> - 2013-03-15 15:37:01
|
On Fri, Mar 15, 2013 at 01:24:16PM +0000, Tim...@de... wrote: > I'm using a custom x86 3.2.37 Kernel with Real Time support. I'm > using an "e1000e Intel 82574" with should be supported. The e1000e driver will have PHC and HW timestamping in kernel 3.9, and it has SW time stamping as of kernel 3.5. So it is not supported on your kernel version. The easiest way to get going with your 3.2 kernel is to back port the SW time stamping patch. [ See the table of supported hardware at the linuxptp home page. ] HTH, Richard |
|
From: Keller, J. E <jac...@in...> - 2013-03-15 16:33:34
|
> -----Original Message----- > From: Richard Cochran [mailto:ric...@gm...] > Sent: Friday, March 15, 2013 8:37 AM > To: Tim...@de... > Cc: lin...@li... > Subject: Re: [Linuxptp-users] can't get linux PTP to run > > On Fri, Mar 15, 2013 at 01:24:16PM +0000, Tim- > Ben...@de... wrote: > > > I'm using a custom x86 3.2.37 Kernel with Real Time support. I'm > > using an "e1000e Intel 82574" with should be supported. > > The e1000e driver will have PHC and HW timestamping in kernel 3.9, > and > it has SW time stamping as of kernel 3.5. So it is not supported on > your kernel version. > > The easiest way to get going with your 3.2 kernel is to back port the > SW time stamping patch. > > [ See the table of supported hardware at the linuxptp home page. ] > > HTH, > Richard > > There may be a kernel module released on sourceforge with support if you don't need in-kernel driver, this should work with the PTP framework in 3.2 http://sourceforge.net/projects/e1000/files/e1000e%20stable/ - Jake |
|
From: <Tim...@de...> - 2013-03-19 08:42:16
|
First of all thanks for your help. >There may be a kernel module released on sourceforge with support if you don't need in-kernel driver, this should >work with the PTP framework in 3.2 >http://sourceforge.net/projects/e1000/files/e1000e%20stable/ Now I have set up this driver and compiled it with PTP support but there is nothing different than before still ptp4l[98.033]: port 1: get_ts_info not supported ptp4l[98.035]: port 1: INITIALIZING to LISTENING on INITIALIZE ptp4l[98.035]: port 0: INITIALIZING to LISTENING on INITIALIZE ptp4l[104.035]: port 1: LISTENING to MASTER on ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES ptp4l[105.041]: recvmsg tx timestamp failed: Resource temporarily unavailable ptp4l[105.041]: port 1: send sync failed ptp4l[105.041]: port 1: MASTER to FAULTY on FAULT_DETECTED ptp4l[121.043]: port 1: FAULTY to LISTENING on FAULT_CLEARED ptp4l[127.043]: port 1: LISTENING to MASTER on ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES ptp4l[128.049]: recvmsg tx timestamp failed: Resource temporarily unavailable As you can see below that the new driver is working: ~$ ethtool -i eth2 driver: e1000e version: 2.3.2-NAPI firmware-version: 2.1-2 bus-info: 0000:07:00.0 changing the kernel to 3.5 or 3.9 would take a lot of time because a lot of realtime support is bound into it. So I would prefer staying on 3.2. Is there something I still can try? Thanks, Benny -----Ursprüngliche Nachricht----- Von: Keller, Jacob E [mailto:jac...@in...] Gesendet: Freitag, 15. März 2013 17:33 An: Richard Cochran; Rapp, Tim-Benjamin Cc: lin...@li... Betreff: RE: [Linuxptp-users] can't get linux PTP to run > -----Original Message----- > From: Richard Cochran [mailto:ric...@gm...] > Sent: Friday, March 15, 2013 8:37 AM > To: Tim...@de... > Cc: lin...@li... > Subject: Re: [Linuxptp-users] can't get linux PTP to run > > On Fri, Mar 15, 2013 at 01:24:16PM +0000, Tim- > Ben...@de... wrote: > > > I'm using a custom x86 3.2.37 Kernel with Real Time support. I'm > > using an "e1000e Intel 82574" with should be supported. > > The e1000e driver will have PHC and HW timestamping in kernel 3.9, and > it has SW time stamping as of kernel 3.5. So it is not supported on > your kernel version. > > The easiest way to get going with your 3.2 kernel is to back port the > SW time stamping patch. > > [ See the table of supported hardware at the linuxptp home page. ] > > HTH, > Richard > > >There may be a kernel module released on sourceforge with support if you don't need in-kernel driver, this should >work with the PTP framework in 3.2 >http://sourceforge.net/projects/e1000/files/e1000e%20stable/ >- Jake |
|
From: Keller, J. E <jac...@in...> - 2013-03-19 20:21:13
|
Yes. You first of all need to determine which /dev/ptp device you are supposed to use. Can you show me the command you use to run ptp4l? Second, you may need to modify the config file to increase the tx_retries value in the config file (and pass that config to ptp4l's command option) Basically, the part may not be returning the tx timestamp on the socket fast enough. If you increase the tx_retries count to a fair bit higher that may resolve the particular error. - Jake > -----Original Message----- > From: Tim...@de... [mailto:Tim- > Ben...@de...] > Sent: Tuesday, March 19, 2013 1:42 AM > To: lin...@li... > Subject: Re: [Linuxptp-users] can't get linux PTP to run > > First of all thanks for your help. > > >There may be a kernel module released on sourceforge with support if > you don't need in-kernel driver, this should >work with the PTP > framework in 3.2 > > >http://sourceforge.net/projects/e1000/files/e1000e%20stable/ > > Now I have set up this driver and compiled it with PTP support but there > is nothing different than before still > > ptp4l[98.033]: port 1: get_ts_info not supported > ptp4l[98.035]: port 1: INITIALIZING to LISTENING on INITIALIZE > ptp4l[98.035]: port 0: INITIALIZING to LISTENING on INITIALIZE > ptp4l[104.035]: port 1: LISTENING to MASTER on > ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES > ptp4l[105.041]: recvmsg tx timestamp failed: Resource temporarily > unavailable > ptp4l[105.041]: port 1: send sync failed > ptp4l[105.041]: port 1: MASTER to FAULTY on FAULT_DETECTED > ptp4l[121.043]: port 1: FAULTY to LISTENING on FAULT_CLEARED > ptp4l[127.043]: port 1: LISTENING to MASTER on > ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES > ptp4l[128.049]: recvmsg tx timestamp failed: Resource temporarily > unavailable > > As you can see below that the new driver is working: > > ~$ ethtool -i eth2 > driver: e1000e > version: 2.3.2-NAPI > firmware-version: 2.1-2 > bus-info: 0000:07:00.0 > > changing the kernel to 3.5 or 3.9 would take a lot of time because a lot > of realtime support is bound into it. So I would prefer staying on 3.2. > > Is there something I still can try? > > Thanks, > Benny > > -----Ursprüngliche Nachricht----- > Von: Keller, Jacob E [mailto:jac...@in...] > Gesendet: Freitag, 15. März 2013 17:33 > An: Richard Cochran; Rapp, Tim-Benjamin > Cc: lin...@li... > Betreff: RE: [Linuxptp-users] can't get linux PTP to run > > > -----Original Message----- > > From: Richard Cochran [mailto:ric...@gm...] > > Sent: Friday, March 15, 2013 8:37 AM > > To: Tim...@de... > > Cc: lin...@li... > > Subject: Re: [Linuxptp-users] can't get linux PTP to run > > > > On Fri, Mar 15, 2013 at 01:24:16PM +0000, Tim- > > Ben...@de... wrote: > > > > > I'm using a custom x86 3.2.37 Kernel with Real Time support. I'm > > > using an "e1000e Intel 82574" with should be supported. > > > > The e1000e driver will have PHC and HW timestamping in kernel 3.9, > and > > it has SW time stamping as of kernel 3.5. So it is not supported on > > your kernel version. > > > > The easiest way to get going with your 3.2 kernel is to back port the > > SW time stamping patch. > > > > [ See the table of supported hardware at the linuxptp home page. ] > > > > HTH, > > Richard > > > > > > >There may be a kernel module released on sourceforge with support if > you don't need in-kernel driver, this should >work with the PTP > framework in 3.2 > > >http://sourceforge.net/projects/e1000/files/e1000e%20stable/ > > >- Jake > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_mar > _______________________________________________ > Linuxptp-users mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxptp-users |
|
From: <Tim...@de...> - 2013-03-25 08:11:23
|
Hi, well im using the modified driver from sourceforge (see post of Jake). Therfore I only can use software timetamping, because HW-timespamps are not supported. If i dont use HW timestamping then I dont need to pick an /dev/ptp (I dont have one). After your information I changed to using a config file. Did I do it like you ment? Adding the tx_timestamp_retries? I tried several different numbers. Always the same error. The command I use is: ptp4l -i eht2 -f /etc/ptp4l.cfg the config is: [global] # logging_level 6 tx_timestamp_retries 100 use_syslog 0 verbose 1 time_stamping software And I still get the same error than before: > ptp4l[98.033]: port 1: get_ts_info not supported > ptp4l[98.035]: port 1: INITIALIZING to LISTENING on INITIALIZE > ptp4l[98.035]: port 0: INITIALIZING to LISTENING on INITIALIZE > ptp4l[104.035]: port 1: LISTENING to MASTER on > ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES > ptp4l[105.041]: recvmsg tx timestamp failed: Resource temporarily > unavailable > ptp4l[105.041]: port 1: send sync failed > ptp4l[105.041]: port 1: MASTER to FAULTY on FAULT_DETECTED > ptp4l[121.043]: port 1: FAULTY to LISTENING on FAULT_CLEARED > ptp4l[127.043]: port 1: LISTENING to MASTER on > ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES > ptp4l[128.049]: recvmsg tx timestamp failed: Resource temporarily > unavailable Thanks, Benny -----Ursprüngliche Nachricht----- Von: Keller, Jacob E [mailto:jac...@in...] Gesendet: Dienstag, 19. März 2013 21:21 An: Rapp, Tim-Benjamin; lin...@li... Betreff: Re: [Linuxptp-users] can't get linux PTP to run Yes. You first of all need to determine which /dev/ptp device you are supposed to use. Can you show me the command you use to run ptp4l? Second, you may need to modify the config file to increase the tx_retries value in the config file (and pass that config to ptp4l's command option) Basically, the part may not be returning the tx timestamp on the socket fast enough. If you increase the tx_retries count to a fair bit higher that may resolve the particular error. - Jake > -----Original Message----- > From: Tim...@de... [mailto:Tim- > Ben...@de...] > Sent: Tuesday, March 19, 2013 1:42 AM > To: lin...@li... > Subject: Re: [Linuxptp-users] can't get linux PTP to run > > First of all thanks for your help. > > >There may be a kernel module released on sourceforge with support if > you don't need in-kernel driver, this should >work with the PTP > framework in 3.2 > > >http://sourceforge.net/projects/e1000/files/e1000e%20stable/ > > Now I have set up this driver and compiled it with PTP support but > there is nothing different than before still > > ptp4l[98.033]: port 1: get_ts_info not supported > ptp4l[98.035]: port 1: INITIALIZING to LISTENING on INITIALIZE > ptp4l[98.035]: port 0: INITIALIZING to LISTENING on INITIALIZE > ptp4l[104.035]: port 1: LISTENING to MASTER on > ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES > ptp4l[105.041]: recvmsg tx timestamp failed: Resource temporarily > unavailable > ptp4l[105.041]: port 1: send sync failed > ptp4l[105.041]: port 1: MASTER to FAULTY on FAULT_DETECTED > ptp4l[121.043]: port 1: FAULTY to LISTENING on FAULT_CLEARED > ptp4l[127.043]: port 1: LISTENING to MASTER on > ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES > ptp4l[128.049]: recvmsg tx timestamp failed: Resource temporarily > unavailable > > As you can see below that the new driver is working: > > ~$ ethtool -i eth2 > driver: e1000e > version: 2.3.2-NAPI > firmware-version: 2.1-2 > bus-info: 0000:07:00.0 > > changing the kernel to 3.5 or 3.9 would take a lot of time because a > lot of realtime support is bound into it. So I would prefer staying on 3.2. > > Is there something I still can try? > > Thanks, > Benny > > -----Ursprüngliche Nachricht----- > Von: Keller, Jacob E [mailto:jac...@in...] > Gesendet: Freitag, 15. März 2013 17:33 > An: Richard Cochran; Rapp, Tim-Benjamin > Cc: lin...@li... > Betreff: RE: [Linuxptp-users] can't get linux PTP to run > > > -----Original Message----- > > From: Richard Cochran [mailto:ric...@gm...] > > Sent: Friday, March 15, 2013 8:37 AM > > To: Tim...@de... > > Cc: lin...@li... > > Subject: Re: [Linuxptp-users] can't get linux PTP to run > > > > On Fri, Mar 15, 2013 at 01:24:16PM +0000, Tim- > > Ben...@de... wrote: > > > > > I'm using a custom x86 3.2.37 Kernel with Real Time support. I'm > > > using an "e1000e Intel 82574" with should be supported. > > > > The e1000e driver will have PHC and HW timestamping in kernel 3.9, > and > > it has SW time stamping as of kernel 3.5. So it is not supported on > > your kernel version. > > > > The easiest way to get going with your 3.2 kernel is to back port > > the SW time stamping patch. > > > > [ See the table of supported hardware at the linuxptp home page. ] > > > > HTH, > > Richard > > > > > > >There may be a kernel module released on sourceforge with support if > you don't need in-kernel driver, this should >work with the PTP > framework in 3.2 > > >http://sourceforge.net/projects/e1000/files/e1000e%20stable/ > > >- Jake > > ---------------------------------------------------------------------- > -------- Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics Download AppDynamics Lite > for free today: > http://p.sf.net/sfu/appdyn_d2d_mar > _______________________________________________ > Linuxptp-users mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxptp-users ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar _______________________________________________ Linuxptp-users mailing list Lin...@li... https://lists.sourceforge.net/lists/listinfo/linuxptp-users |
|
From: Richard C. <ric...@gm...> - 2013-03-25 18:20:51
|
On Mon, Mar 25, 2013 at 08:11:12AM +0000, Tim...@de... wrote: > Hi, > > well im using the modified driver from sourceforge (see post of Jake). > Therfore I only can use software timetamping, because HW-timespamps are not supported. If i dont use HW timestamping then I dont need to pick an /dev/ptp (I dont have one). Looking at the code, in e1000e-2.3.2.tar.gz, and in its README, HW time stamps *are* supported, but you need to add flag when building. IEEE 1588 Precision Time Protocol (PTP) Hardware Clock (PHC) ------------------------------------------------------------ Support for the IEEE 1588 Precision Time Protocol (PTP) Hardware Clock (PHC) is disabled by default in this out-of-tree driver even if it is enabled for the in-kernel driver. The feature is available only on a subset of devices supported by the driver, and can only be enabled on 3.0 and newer kernels that also have the PTP_1588_CLOCK support compiled in statically or as a module. To enable the feature when compiling the driver, add 'CFLAGS_EXTRA=-DE1000E_PTP' to the command line. > After your information I changed to using a config file. Did I do it like you ment? Adding the tx_timestamp_retries? I tried several different numbers. Always the same error. > > The command I use is: > ptp4l -i eht2 -f /etc/ptp4l.cfg > > the config is: > [global] > # > logging_level 6 > tx_timestamp_retries 100 > use_syslog 0 > verbose 1 > time_stamping software When using SW time stamping, the tx_timestamp_retries has no effect, since the time stamp is taken during the 'send' call. I can only suggest to recheck if: - you are really using the out-of-tree driver - that eth2 is really, truely serviced by the e1000e driver There is a Linux test program for time stamping in Documentation/networking/timestamping Can you test your interface with that program like so: timestamping eth2 SOF_TIMESTAMPING_TX_SOFTWARE SOF_TIMESTAMPING_RX_SOFTWARE SOF_TIMESTAMPING_SOFTWARE and post the results? Thanks, Richard |
|
From: <Tim...@de...> - 2013-03-26 14:50:53
|
Hi, ok it seems that the driver works now (down ask me what I have changed, don't know). I can now use HW stamping. But the time does not change at all. If I start the master clock it shows: ptp4l -f ptp.cfg -p /dev/ptp0 -i eth2 ptp4l[7470.955]: selected /dev/ptp0 as PTP clock ptp4l[7470.955]: failed to read out the clock frequency adjustment: Operation not supported ptp4l[7470.955]: port 1: get_ts_info not supported ptp4l[7470.958]: port 1: INITIALIZING to LISTENING on INITIALIZE ptp4l[7470.958]: port 0: INITIALIZING to LISTENING on INITIALIZE ptp4l[7476.958]: port 1: LISTENING to MASTER on ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES And if I start the slave it shows: ptp4l -f ptp.cfg -p /dev/ptp0 -i eth2 -s ptp4l[8394.096]: selected /dev/ptp0 as PTP clock ptp4l[8394.096]: failed to read out the clock frequency adjustment: Operation not supported ptp4l[8394.096]: port 1: get_ts_info not supported ptp4l[8394.098]: port 1: INITIALIZING to LISTENING on INITIALIZE ptp4l[8394.098]: port 0: INITIALIZING to LISTENING on INITIALIZE ptp4l[8395.985]: port 1: new foreign master 745798.fffe.000021-1 ptp4l[8399.987]: selected best master clock 745798.fffe.000021 ptp4l[8399.987]: port 1: LISTENING to UNCALIBRATED on RS_SLAVE ptp4l[8401.429]: negative path delay -5520 ptp4l[8401.429]: path_delay = (t2 - t3) + (t4 - t1) ptp4l[8401.429]: t2 - t3 = -427837600 ptp4l[8401.429]: t4 - t1 = +427826560 ptp4l[8401.429]: c1 0 ptp4l[8401.429]: c2 0 ptp4l[8401.429]: c3 0 ptp4l[8402.001]: master offset -1637602062061189501 s0 freq +0 path delay -5520 ptp4l[8402.750]: negative path delay -10180 ptp4l[8402.750]: path_delay = (t2 - t3) + (t4 - t1) ptp4l[8402.750]: t2 - t3 = -748785600 ptp4l[8402.750]: t4 - t1 = +748765240 ptp4l[8402.750]: c1 0 ptp4l[8402.750]: c2 0 ptp4l[8402.750]: c3 0 ptp4l[8403.002]: master offset -1637602062061158011 s1 freq +31485 path delay -7850 ptp4l[8404.002]: master offset -1637602062061128851 s2 freq -32767999 path delay -7850 ptp4l[8404.002]: port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED ptp4l[8404.216]: negative path delay -2380 ptp4l[8404.216]: path_delay = (t2 - t3) + (t4 - t1) ptp4l[8404.216]: t2 - t3 = -213503440 ptp4l[8404.216]: t4 - t1 = +213498680 ptp4l[8404.216]: c1 0 ptp4l[8404.216]: c2 0 ptp4l[8404.216]: c3 0 ptp4l[8405.003]: master offset -1637602062061101475 s2 freq -32767999 path delay -6026 ptp4l[8405.072]: negative path delay -280 ptp4l[8405.072]: path_delay = (t2 - t3) + (t4 - t1) ptp4l[8405.072]: t2 - t3 = -69388320 ptp4l[8405.072]: t4 - t1 = +69387760 ptp4l[8405.072]: c1 0 ptp4l[8405.072]: c2 0 ptp4l[8405.072]: c3 0 ptp4l[8405.778]: negative path delay -10560 ptp4l[8405.778]: path_delay = (t2 - t3) + (t4 - t1) ptp4l[8405.778]: t2 - t3 = -774949920 ptp4l[8405.778]: t4 - t1 = +774928800 ptp4l[8405.778]: c1 0 ptp4l[8405.778]: c2 0 ptp4l[8405.778]: c3 0 ptp4l[8406.003]: master offset -1637602062061072517 s2 freq -32767999 path delay -5784 ptp4l[8406.374]: negative path delay -4680 ptp4l[8406.374]: path_delay = (t2 - t3) + (t4 - t1) ptp4l[8406.374]: t2 - t3 = -370912120 ptp4l[8406.374]: t4 - t1 = +370902760 ptp4l[8406.374]: c1 0 ptp4l[8406.374]: c2 0 ptp4l[8406.374]: c3 0 ptp4l[8406.885]: negative path delay -12120 ptp4l[8406.885]: path_delay = (t2 - t3) + (t4 - t1) ptp4l[8406.885]: t2 - t3 = -881060360 ptp4l[8406.885]: t4 - t1 = +881036120 ptp4l[8406.885]: c1 0 ptp4l[8406.885]: c2 0 ptp4l[8406.885]: c3 0 ptp4l[8407.004]: master offset -1637602062061042610 s2 freq -32767999 path delay -6531 My config is: [global] # # Port Data Set # logAnnounceInterval 1 logSyncInterval 0 logMinDelayReqInterval 0 logMinPdelayReqInterval 0 announceReceiptTimeout 3 delayAsymmetry 0 fault_reset_interval 4 # # Run time options # assume_two_step 0 logging_level 6 path_trace_enabled 1 follow_up_info 0 tx_timestamp_retries 100 use_syslog 0 verbose 1 summary_interval 0 # # Servo Options # pi_proportional_const 0.0 pi_integral_const 0.0 pi_offset_const 0.0 clock_servo pi # # Default interface options # network_transport UDPv4 delay_mechanism E2E time_stamping hardware If I check the time (both date and hwclock) on both PCs, one says (for example) 10:12:11 and the other says 08:45:00. Even after an hour running ptp4l the time difference is the same. I think it got something to do with the clock frequency adjustment. I'm getting closer to success but what am I doing wrong now? Thanks, Benny -----Ursprüngliche Nachricht----- Von: Richard Cochran [mailto:ric...@gm...] Gesendet: Montag, 25. März 2013 19:20 An: Rapp, Tim-Benjamin Cc: lin...@li... Betreff: Re: [Linuxptp-users] can't get linux PTP to run On Mon, Mar 25, 2013 at 08:11:12AM +0000, Tim...@de... wrote: > Hi, > > well im using the modified driver from sourceforge (see post of Jake). > Therfore I only can use software timetamping, because HW-timespamps are not supported. If i dont use HW timestamping then I dont need to pick an /dev/ptp (I dont have one). Looking at the code, in e1000e-2.3.2.tar.gz, and in its README, HW time stamps *are* supported, but you need to add flag when building. IEEE 1588 Precision Time Protocol (PTP) Hardware Clock (PHC) ------------------------------------------------------------ Support for the IEEE 1588 Precision Time Protocol (PTP) Hardware Clock (PHC) is disabled by default in this out-of-tree driver even if it is enabled for the in-kernel driver. The feature is available only on a subset of devices supported by the driver, and can only be enabled on 3.0 and newer kernels that also have the PTP_1588_CLOCK support compiled in statically or as a module. To enable the feature when compiling the driver, add 'CFLAGS_EXTRA=-DE1000E_PTP' to the command line. > After your information I changed to using a config file. Did I do it like you ment? Adding the tx_timestamp_retries? I tried several different numbers. Always the same error. > > The command I use is: > ptp4l -i eht2 -f /etc/ptp4l.cfg > > the config is: > [global] > # > logging_level 6 > tx_timestamp_retries 100 > use_syslog 0 > verbose 1 > time_stamping software When using SW time stamping, the tx_timestamp_retries has no effect, since the time stamp is taken during the 'send' call. I can only suggest to recheck if: - you are really using the out-of-tree driver - that eth2 is really, truely serviced by the e1000e driver There is a Linux test program for time stamping in Documentation/networking/timestamping Can you test your interface with that program like so: timestamping eth2 SOF_TIMESTAMPING_TX_SOFTWARE SOF_TIMESTAMPING_RX_SOFTWARE SOF_TIMESTAMPING_SOFTWARE and post the results? Thanks, Richard |
|
From: Keller, J. E <jac...@in...> - 2013-03-26 18:34:00
|
FYI, the PTP4l does not directly modify the system (kernel) time, except in the case of Software timestamping. Each ptp device actually represents its own clock. You should use phc2sys application to modify the system time in addition. The reason for this design is because the clock on the adapter is completely disconnected from the system time in the kernel (The source is completely different). What version of the kernel are you using? If you don't have v3.5 with the get_ts_info ethtool support, you need to ensure that the /dev/ptp0 device is actually the device for the port you are using. Intel's Ethernet adapters create one ptp device per port due to being unable to represent multiple ports using the same clock. If you have a multi-port adapter that could be part of why you are seeing some issues. Do those negative adjust values go away over time? As in does it stabilize? - Jake > -----Original Message----- > From: Tim...@de... [mailto:Tim- > Ben...@de...] > Sent: Tuesday, March 26, 2013 7:51 AM > To: lin...@li... > Subject: Re: [Linuxptp-users] can't get linux PTP to run > > Hi, > > ok it seems that the driver works now (down ask me what I have > changed, don't know). I can now use HW stamping. > > But the time does not change at all. If I start the master clock it shows: > ptp4l -f ptp.cfg -p /dev/ptp0 -i eth2 > ptp4l[7470.955]: selected /dev/ptp0 as PTP clock > ptp4l[7470.955]: failed to read out the clock frequency > adjustment: Operation not supported > ptp4l[7470.955]: port 1: get_ts_info not supported > ptp4l[7470.958]: port 1: INITIALIZING to LISTENING on INITIALIZE > ptp4l[7470.958]: port 0: INITIALIZING to LISTENING on INITIALIZE > ptp4l[7476.958]: port 1: LISTENING to MASTER on > ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES > > And if I start the slave it shows: > ptp4l -f ptp.cfg -p /dev/ptp0 -i eth2 -s > ptp4l[8394.096]: selected /dev/ptp0 as PTP clock > ptp4l[8394.096]: failed to read out the clock frequency > adjustment: Operation not supported > ptp4l[8394.096]: port 1: get_ts_info not supported > ptp4l[8394.098]: port 1: INITIALIZING to LISTENING on INITIALIZE > ptp4l[8394.098]: port 0: INITIALIZING to LISTENING on INITIALIZE > ptp4l[8395.985]: port 1: new foreign master 745798.fffe.000021-1 > ptp4l[8399.987]: selected best master clock 745798.fffe.000021 > ptp4l[8399.987]: port 1: LISTENING to UNCALIBRATED on > RS_SLAVE > ptp4l[8401.429]: negative path delay -5520 > ptp4l[8401.429]: path_delay = (t2 - t3) + (t4 - t1) > ptp4l[8401.429]: t2 - t3 = -427837600 > ptp4l[8401.429]: t4 - t1 = +427826560 > ptp4l[8401.429]: c1 0 > ptp4l[8401.429]: c2 0 > ptp4l[8401.429]: c3 0 > ptp4l[8402.001]: master offset -1637602062061189501 s0 freq > +0 path delay -5520 > ptp4l[8402.750]: negative path delay -10180 > ptp4l[8402.750]: path_delay = (t2 - t3) + (t4 - t1) > ptp4l[8402.750]: t2 - t3 = -748785600 > ptp4l[8402.750]: t4 - t1 = +748765240 > ptp4l[8402.750]: c1 0 > ptp4l[8402.750]: c2 0 > ptp4l[8402.750]: c3 0 > ptp4l[8403.002]: master offset -1637602062061158011 s1 freq > +31485 path delay -7850 > ptp4l[8404.002]: master offset -1637602062061128851 s2 freq - > 32767999 path delay -7850 > ptp4l[8404.002]: port 1: UNCALIBRATED to SLAVE on > MASTER_CLOCK_SELECTED > ptp4l[8404.216]: negative path delay -2380 > ptp4l[8404.216]: path_delay = (t2 - t3) + (t4 - t1) > ptp4l[8404.216]: t2 - t3 = -213503440 > ptp4l[8404.216]: t4 - t1 = +213498680 > ptp4l[8404.216]: c1 0 > ptp4l[8404.216]: c2 0 > ptp4l[8404.216]: c3 0 > ptp4l[8405.003]: master offset -1637602062061101475 s2 freq - > 32767999 path delay -6026 > ptp4l[8405.072]: negative path delay -280 > ptp4l[8405.072]: path_delay = (t2 - t3) + (t4 - t1) > ptp4l[8405.072]: t2 - t3 = -69388320 > ptp4l[8405.072]: t4 - t1 = +69387760 > ptp4l[8405.072]: c1 0 > ptp4l[8405.072]: c2 0 > ptp4l[8405.072]: c3 0 > ptp4l[8405.778]: negative path delay -10560 > ptp4l[8405.778]: path_delay = (t2 - t3) + (t4 - t1) > ptp4l[8405.778]: t2 - t3 = -774949920 > ptp4l[8405.778]: t4 - t1 = +774928800 > ptp4l[8405.778]: c1 0 > ptp4l[8405.778]: c2 0 > ptp4l[8405.778]: c3 0 > ptp4l[8406.003]: master offset -1637602062061072517 s2 freq - > 32767999 path delay -5784 > ptp4l[8406.374]: negative path delay -4680 > ptp4l[8406.374]: path_delay = (t2 - t3) + (t4 - t1) > ptp4l[8406.374]: t2 - t3 = -370912120 > ptp4l[8406.374]: t4 - t1 = +370902760 > ptp4l[8406.374]: c1 0 > ptp4l[8406.374]: c2 0 > ptp4l[8406.374]: c3 0 > ptp4l[8406.885]: negative path delay -12120 > ptp4l[8406.885]: path_delay = (t2 - t3) + (t4 - t1) > ptp4l[8406.885]: t2 - t3 = -881060360 > ptp4l[8406.885]: t4 - t1 = +881036120 > ptp4l[8406.885]: c1 0 > ptp4l[8406.885]: c2 0 > ptp4l[8406.885]: c3 0 > ptp4l[8407.004]: master offset -1637602062061042610 s2 freq - > 32767999 path delay -6531 > > My config is: > [global] > # > # Port Data Set > # > logAnnounceInterval 1 > logSyncInterval 0 > logMinDelayReqInterval 0 > logMinPdelayReqInterval 0 > announceReceiptTimeout 3 > delayAsymmetry 0 > fault_reset_interval 4 > # > # Run time options > # > assume_two_step 0 > logging_level 6 > path_trace_enabled 1 > follow_up_info 0 > tx_timestamp_retries 100 > use_syslog 0 > verbose 1 > summary_interval 0 > # > # Servo Options > # > pi_proportional_const 0.0 > pi_integral_const 0.0 > pi_offset_const 0.0 > clock_servo pi > # > # Default interface options > # > network_transport UDPv4 > delay_mechanism E2E > time_stamping hardware > > If I check the time (both date and hwclock) on both PCs, one says (for > example) 10:12:11 and the other says 08:45:00. Even after an hour > running ptp4l the time difference is the same. > > I think it got something to do with the clock frequency adjustment. > > I'm getting closer to success but what am I doing wrong now? > > Thanks, > Benny > > > -----Ursprüngliche Nachricht----- > Von: Richard Cochran [mailto:ric...@gm...] > Gesendet: Montag, 25. März 2013 19:20 > An: Rapp, Tim-Benjamin > Cc: lin...@li... > Betreff: Re: [Linuxptp-users] can't get linux PTP to run > > On Mon, Mar 25, 2013 at 08:11:12AM +0000, Tim- > Ben...@de... wrote: > > Hi, > > > > well im using the modified driver from sourceforge (see post of Jake). > > Therfore I only can use software timetamping, because HW- > timespamps are not supported. If i dont use HW timestamping then I > dont need to pick an /dev/ptp (I dont have one). > > Looking at the code, in e1000e-2.3.2.tar.gz, and in its README, HW time > stamps *are* supported, but you need to add flag when building. > > IEEE 1588 Precision Time Protocol (PTP) Hardware Clock (PHC) > ------------------------------------------------------------ > Support for the IEEE 1588 Precision Time Protocol (PTP) Hardware Clock > (PHC) > is disabled by default in this out-of-tree driver even if it is enabled for > the in-kernel driver. > > The feature is available only on a subset of devices supported by the > driver, and can only be enabled on 3.0 and newer kernels that also > have > the PTP_1588_CLOCK support compiled in statically or as a module. To > enable > the feature when compiling the driver, add 'CFLAGS_EXTRA=- > DE1000E_PTP' to > the command line. > > > After your information I changed to using a config file. Did I do it like > you ment? Adding the tx_timestamp_retries? I tried several different > numbers. Always the same error. > > > > The command I use is: > > ptp4l -i eht2 -f /etc/ptp4l.cfg > > > > the config is: > > [global] > > # > > logging_level 6 > > tx_timestamp_retries 100 > > use_syslog 0 > > verbose 1 > > time_stamping software > > When using SW time stamping, the tx_timestamp_retries has no effect, > since the time stamp is taken during the 'send' call. > > I can only suggest to recheck if: > > - you are really using the out-of-tree driver > - that eth2 is really, truely serviced by the e1000e driver > > There is a Linux test program for time stamping in > > Documentation/networking/timestamping > > Can you test your interface with that program like so: > > timestamping eth2 SOF_TIMESTAMPING_TX_SOFTWARE > SOF_TIMESTAMPING_RX_SOFTWARE SOF_TIMESTAMPING_SOFTWARE > > and post the results? > > Thanks, > Richard > > > ------------------------------------------------------------------------------ > Own the Future-Intel® Level Up Game Demo Contest 2013 > Rise to greatness in Intel's independent game demo contest. > Compete for recognition, cash, and the chance to get your game > on Steam. $5K grand prize plus 10 genre and skill prizes. > Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d > _______________________________________________ > Linuxptp-users mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxptp-users |
|
From: Jeroen V. d. K. <jer...@gm...> - 2013-03-26 15:11:51
|
Hi, I'm not an expert, but the log seems to indicate a systematically decreasing master time offset, with a maxed out freq. adjustment. I would say the PHC is somehow unable to properly step to a new value (clock_settime/adjtime fails). You could try setting both clocks nearly equal and see if they eventually converge. You could also compile and try the testptp program (/Documentation/ptp/testptp.c) to see if your PHC clock actually works. I'm not sure if support of the get_ts_info() call is required. J. 2013/3/26 <Tim...@de...> > Hi, > > ok it seems that the driver works now (down ask me what I have changed, > don't know). I can now use HW stamping. > > But the time does not change at all. If I start the master clock it shows: > ptp4l -f ptp.cfg -p /dev/ptp0 -i eth2 > ptp4l[7470.955]: selected /dev/ptp0 as PTP clock > ptp4l[7470.955]: failed to read out the clock frequency > adjustment: Operation not supported > ptp4l[7470.955]: port 1: get_ts_info not supported > ptp4l[7470.958]: port 1: INITIALIZING to LISTENING on INITIALIZE > ptp4l[7470.958]: port 0: INITIALIZING to LISTENING on INITIALIZE > ptp4l[7476.958]: port 1: LISTENING to MASTER on > ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES > > And if I start the slave it shows: > ptp4l -f ptp.cfg -p /dev/ptp0 -i eth2 -s > ptp4l[8394.096]: selected /dev/ptp0 as PTP clock > ptp4l[8394.096]: failed to read out the clock frequency > adjustment: Operation not supported > ptp4l[8394.096]: port 1: get_ts_info not supported > ptp4l[8394.098]: port 1: INITIALIZING to LISTENING on INITIALIZE > ptp4l[8394.098]: port 0: INITIALIZING to LISTENING on INITIALIZE > ptp4l[8395.985]: port 1: new foreign master 745798.fffe.000021-1 > ptp4l[8399.987]: selected best master clock 745798.fffe.000021 > ptp4l[8399.987]: port 1: LISTENING to UNCALIBRATED on RS_SLAVE > ptp4l[8401.429]: negative path delay -5520 > ptp4l[8401.429]: path_delay = (t2 - t3) + (t4 - t1) > ptp4l[8401.429]: t2 - t3 = -427837600 > ptp4l[8401.429]: t4 - t1 = +427826560 > ptp4l[8401.429]: c1 0 > ptp4l[8401.429]: c2 0 > ptp4l[8401.429]: c3 0 > ptp4l[8402.001]: master offset -1637602062061189501 s0 freq > +0 path delay -5520 > ptp4l[8402.750]: negative path delay -10180 > ptp4l[8402.750]: path_delay = (t2 - t3) + (t4 - t1) > ptp4l[8402.750]: t2 - t3 = -748785600 > ptp4l[8402.750]: t4 - t1 = +748765240 > ptp4l[8402.750]: c1 0 > ptp4l[8402.750]: c2 0 > ptp4l[8402.750]: c3 0 > ptp4l[8403.002]: master offset -1637602062061158011 s1 freq > +31485 path delay -7850 > ptp4l[8404.002]: master offset -1637602062061128851 s2 freq > -32767999 path delay -7850 > ptp4l[8404.002]: port 1: UNCALIBRATED to SLAVE on > MASTER_CLOCK_SELECTED > ptp4l[8404.216]: negative path delay -2380 > ptp4l[8404.216]: path_delay = (t2 - t3) + (t4 - t1) > ptp4l[8404.216]: t2 - t3 = -213503440 > ptp4l[8404.216]: t4 - t1 = +213498680 > ptp4l[8404.216]: c1 0 > ptp4l[8404.216]: c2 0 > ptp4l[8404.216]: c3 0 > ptp4l[8405.003]: master offset -1637602062061101475 s2 freq > -32767999 path delay -6026 > ptp4l[8405.072]: negative path delay -280 > ptp4l[8405.072]: path_delay = (t2 - t3) + (t4 - t1) > ptp4l[8405.072]: t2 - t3 = -69388320 > ptp4l[8405.072]: t4 - t1 = +69387760 > ptp4l[8405.072]: c1 0 > ptp4l[8405.072]: c2 0 > ptp4l[8405.072]: c3 0 > ptp4l[8405.778]: negative path delay -10560 > ptp4l[8405.778]: path_delay = (t2 - t3) + (t4 - t1) > ptp4l[8405.778]: t2 - t3 = -774949920 > ptp4l[8405.778]: t4 - t1 = +774928800 > ptp4l[8405.778]: c1 0 > ptp4l[8405.778]: c2 0 > ptp4l[8405.778]: c3 0 > ptp4l[8406.003]: master offset -1637602062061072517 s2 freq > -32767999 path delay -5784 > ptp4l[8406.374]: negative path delay -4680 > ptp4l[8406.374]: path_delay = (t2 - t3) + (t4 - t1) > ptp4l[8406.374]: t2 - t3 = -370912120 > ptp4l[8406.374]: t4 - t1 = +370902760 > ptp4l[8406.374]: c1 0 > ptp4l[8406.374]: c2 0 > ptp4l[8406.374]: c3 0 > ptp4l[8406.885]: negative path delay -12120 > ptp4l[8406.885]: path_delay = (t2 - t3) + (t4 - t1) > ptp4l[8406.885]: t2 - t3 = -881060360 > ptp4l[8406.885]: t4 - t1 = +881036120 > ptp4l[8406.885]: c1 0 > ptp4l[8406.885]: c2 0 > ptp4l[8406.885]: c3 0 > ptp4l[8407.004]: master offset -1637602062061042610 s2 freq > -32767999 path delay -6531 > > My config is: > [global] > # > # Port Data Set > # > logAnnounceInterval 1 > logSyncInterval 0 > logMinDelayReqInterval 0 > logMinPdelayReqInterval 0 > announceReceiptTimeout 3 > delayAsymmetry 0 > fault_reset_interval 4 > # > # Run time options > # > assume_two_step 0 > logging_level 6 > path_trace_enabled 1 > follow_up_info 0 > tx_timestamp_retries 100 > use_syslog 0 > verbose 1 > summary_interval 0 > # > # Servo Options > # > pi_proportional_const 0.0 > pi_integral_const 0.0 > pi_offset_const 0.0 > clock_servo pi > # > # Default interface options > # > network_transport UDPv4 > delay_mechanism E2E > time_stamping hardware > > If I check the time (both date and hwclock) on both PCs, one says (for > example) 10:12:11 and the other says 08:45:00. Even after an hour running > ptp4l the time difference is the same. > > I think it got something to do with the clock frequency adjustment. > > I'm getting closer to success but what am I doing wrong now? > > Thanks, > Benny > > > -----Ursprüngliche Nachricht----- > Von: Richard Cochran [mailto:ric...@gm...] > Gesendet: Montag, 25. März 2013 19:20 > An: Rapp, Tim-Benjamin > Cc: lin...@li... > Betreff: Re: [Linuxptp-users] can't get linux PTP to run > > On Mon, Mar 25, 2013 at 08:11:12AM +0000, Tim...@de...: > > Hi, > > > > well im using the modified driver from sourceforge (see post of Jake). > > Therfore I only can use software timetamping, because HW-timespamps are > not supported. If i dont use HW timestamping then I dont need to pick an > /dev/ptp (I dont have one). > > Looking at the code, in e1000e-2.3.2.tar.gz, and in its README, HW time > stamps *are* supported, but you need to add flag when building. > > IEEE 1588 Precision Time Protocol (PTP) Hardware Clock (PHC) > ------------------------------------------------------------ > Support for the IEEE 1588 Precision Time Protocol (PTP) Hardware Clock > (PHC) > is disabled by default in this out-of-tree driver even if it is enabled > for > the in-kernel driver. > > The feature is available only on a subset of devices supported by the > driver, and can only be enabled on 3.0 and newer kernels that also have > the PTP_1588_CLOCK support compiled in statically or as a module. To > enable > the feature when compiling the driver, add 'CFLAGS_EXTRA=-DE1000E_PTP' to > the command line. > > > After your information I changed to using a config file. Did I do it > like you ment? Adding the tx_timestamp_retries? I tried several different > numbers. Always the same error. > > > > The command I use is: > > ptp4l -i eht2 -f /etc/ptp4l.cfg > > > > the config is: > > [global] > > # > > logging_level 6 > > tx_timestamp_retries 100 > > use_syslog 0 > > verbose 1 > > time_stamping software > > When using SW time stamping, the tx_timestamp_retries has no effect, since > the time stamp is taken during the 'send' call. > > I can only suggest to recheck if: > > - you are really using the out-of-tree driver > - that eth2 is really, truely serviced by the e1000e driver > > There is a Linux test program for time stamping in > > Documentation/networking/timestamping > > Can you test your interface with that program like so: > > timestamping eth2 SOF_TIMESTAMPING_TX_SOFTWARE > SOF_TIMESTAMPING_RX_SOFTWARE SOF_TIMESTAMPING_SOFTWARE > > and post the results? > > Thanks, > Richard > > > > ------------------------------------------------------------------------------ > Own the Future-Intel® Level Up Game Demo Contest 2013 > Rise to greatness in Intel's independent game demo contest. > Compete for recognition, cash, and the chance to get your game > on Steam. $5K grand prize plus 10 genre and skill prizes. > Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d > _______________________________________________ > Linuxptp-users mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxptp-users > |
|
From: <Tim...@de...> - 2013-03-26 16:00:21
|
Hi, I tested the ptp test porgramm. capabilities: 599999999 maximum frequency adjustment (ppb) 0 programmable alarms 0 external time stamp channels 0 programmable periodic signals 0 pulse per second What i can do: I can adjust the frequency, get ptp clock time set/get the ptp clock from and to system time. time shift okay What i can not do: timer_create: Operation not supported PTP_ENABLE_PPS: Operation not supported I also tested /Documentation/networking/timestamping this seems fine: SO_TIMESTAMP 0 SO_TIMESTAMPNS 0 SO_TIMESTAMPING 0 873.135483: sent 124 bytes 873.135517: select 1864483us 875.000334: select returned: 0, success 875.000423: sent 124 bytes 875.000441: select 4999559us 880.004323: select returned: 0, success 880.004497: sent 124 bytes 880.004521: select 4995479us I also set both clocks to nealy the same nothing changed. Thanks, Benny >>Hi, >> >> >>I'm not an expert, but the log seems to indicate a systematically decreasing master time offset, with a maxed out freq. adjustment. I would say the >>PHC is somehow unable to properly step to a new value (clock_settime/adjtime fails). >> >>You could try setting both clocks nearly equal and see if they eventually converge. >> >>You could also compile and try the testptp program (/Documentation/ptp/testptp.c) to see if your PHC clock actually works. >> >>I'm not sure if support of the get_ts_info() call is required. >> >> >>J. |
|
From: Richard C. <ric...@gm...> - 2013-03-26 18:53:25
|
On Tue, Mar 26, 2013 at 04:00:11PM +0000, Tim...@de... wrote: > Hi, > > > I tested the ptp test porgramm. > > capabilities: > 599999999 maximum frequency adjustment (ppb) > 0 programmable alarms > 0 external time stamp channels > 0 programmable periodic signals > 0 pulse per second > > What i can do: > I can adjust the frequency, > get ptp clock time > set/get the ptp clock from and to system time. > time shift okay > > What i can not do: > timer_create: Operation not supported > PTP_ENABLE_PPS: Operation not supported This all looks good. > I also tested /Documentation/networking/timestamping this seems fine: But here you should see some output about getting time stamps from the transmitted packets. Also, if you run a second instance of the program on another host, then you should also see time stamps on the received packets. HTH, Richard |
|
From: <Tim...@de...> - 2013-04-02 08:45:34
|
Thanks guys, with your help I got ptp4l to run an my 3.2 Kernel. The only strange thing is that I get a jitter (measured every second) of about +- 25 microseconds this should be less with hw timestamps. Maybe I have to play around with the settings a little bit. But you have been a great help to me Thanks Benny -----Ursprüngliche Nachricht----- Von: Richard Cochran [mailto:ric...@gm...] Gesendet: Dienstag, 26. März 2013 19:53 An: Rapp, Tim-Benjamin Cc: lin...@li... Betreff: Re: [Linuxptp-users] can't get linux PTP to run On Tue, Mar 26, 2013 at 04:00:11PM +0000, Tim...@de... wrote: > Hi, > > > I tested the ptp test porgramm. > > capabilities: > 599999999 maximum frequency adjustment (ppb) > 0 programmable alarms > 0 external time stamp channels > 0 programmable periodic signals > 0 pulse per second > > What i can do: > I can adjust the frequency, > get ptp clock time > set/get the ptp clock from and to system time. > time shift okay > > What i can not do: > timer_create: Operation not supported > PTP_ENABLE_PPS: Operation not supported This all looks good. > I also tested /Documentation/networking/timestamping this seems fine: But here you should see some output about getting time stamps from the transmitted packets. Also, if you run a second instance of the program on another host, then you should also see time stamps on the received packets. HTH, Richard |
|
From: Keller, J. E <jac...@in...> - 2013-04-02 20:31:36
|
> -----Original Message----- > From: Tim...@de... [mailto:Tim- > Ben...@de...] > Sent: Tuesday, April 02, 2013 1:45 AM > To: lin...@li... > Subject: Re: [Linuxptp-users] can't get linux PTP to run > > Thanks guys, > with your help I got ptp4l to run an my 3.2 Kernel. > > The only strange thing is that I get a jitter (measured every second) of > about +- 25 microseconds this should be less with hw timestamps. > Maybe I have to play around with the settings a little bit. > > But you have been a great help to me Thanks > Benny Which device are you using? It could also be your P/I servo numbers. - Jake |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X