Re: [Linuxptp-users] Problems with hardware time stamping with PHY DP83640 on MCP5200 powerpc platform

[Richard C. <ric...@gm...>]

On Tue, May 22, 2012 at 07:34:55PM +0200, Mario Molitor wrote:
> Hallo linuxptp members,
> 
> I have some problems to use our PTP device (PHY DP83640 on MCP5200 powerpc 
                                                             ^^^
(I think you mean MPC)

> platform).

I have never seen the combination MPC5200/DP83640. Is this a
commercial board or a custom design?

> 2.) hardware time stamping
> ===================
> ptp4l[183]: selected /dev/ptp0 as PTP clock
> 
> ptp4l[183]: port 1: INITIALIZING to LISTENING on INITIALIZE
> ptp4l[183]: received SYNC without timestamp
> ptp4l[183]: port 1: bad message
> ptp4l[183]: port 1: new foreign master 0050c2.fffe.c2dfc3-1
> ptp4l[183]: received SYNC without timestamp
> ptp4l[183]: port 1: bad message
> ptp4l[183]: received SYNC without timestamp
> ptp4l[183]: port 1: bad message

Looks like no packets are being time stamped at all.

> I used following linux version without any source changes for test of PTP:
> 
> Linux version 3.4.0-rc7-next-20120514
> with following options
> - CONFIG_EXPERIMENTAL
> - CONFIG_PPS
> - CONFIG_NETWORK_PHY_TIMESTAMPING
> - PTP_1588_CLOCKPTP
                  ^^^
(I think you mean PTP_1588_CLOCK)

Did you enable CONFIG_DP83640_PHY too?

> I have at the moment no any idea what is wrong and I need help to figure out 
> where the problem is.

Don't worry, we will figure this out...

> The other point is, I am not sure that the ptp4l support the  DP83640 PHY.

The ptp4l should work with every PHC Linux driver.
 
> Please let me know how I can debug this problem e.g. with some printks in 
> the kernel driver or adapt the ptp4l application.

This might be a driver issue with the MPC5200, since I never tested it
in combination with the DP83640. But first, make sure you have the PHY
driver compiled in your kernel.

Thanks,
Richard