From: Hardik G. <har...@gm...> - 2017-01-17 08:25:46
|
On Mon, Jan 16, 2017 at 8:09 PM, Richard Cochran <ric...@gm...> wrote: > On Mon, Jan 16, 2017 at 04:19:15PM +0800, Hardik Gohil wrote: > > I have a message when I configure GPS to work PTP in Peer-to-Peer mode > > It is not enough to configure the master alone, you must also > configure the slave in P2P mode. > Yes I have done. ptp4l -i eth0 -m -A (The -A enables automatic selection of the delay measurement mechanism.) > > > ptp4l[18815.624]: port 1: received PDELAY_REQ without timestamp > > ptp4l[18815.624]: port 1: received PDELAY_REQ without timestamp > > ptp4l[18815.624]: port 1: received PDELAY_REQ without timestamp > > This means that the application received a PDelay_Req message, but the > driver did not provide a HW time stamp. > > This error most likely indicates a driver or HW problem. > > The fact that you have three such messages all occurring within one > millisecond of each other is suspicious. You should think about that > and find out why this is happening. > sorry for my mistake I have copied and pasted same message three times. following are real time message ptp4l[2460.587]: port 1: received PDELAY_REQ without timestamp ptp4l[2461.589]: port 1: received PDELAY_REQ without timestamp ptp4l[2462.590]: port 1: received PDELAY_REQ without timestamp ptp4l[2463.590]: port 1: received PDELAY_REQ without timestamp ptp4l[2464.592]: port 1: received PDELAY_REQ without timestamp ptp4l[2465.594]: port 1: received PDELAY_REQ without timestamp ptp4l[2466.594]: port 1: received PDELAY_REQ without timestamp once I exit from application [ 2506.471859] cpts: unable to obtain a time stamp [ 2514.487888] cpts: event pool is empty HTH, > Richard > > > |