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

[Mario M. <Mar...@we...>]

Hello Richard,

many thanks for your quick answer.

>(I think you mean MPC)



Yes, it was typo



>I have never seen the combination MPC5200/DP83640. Is this a

> commercial board or a custom design?



It is custom design. We design a module for our data acquisition systems.




>Looks like no packets are being time stamped at all.



Why the software time stamping work and only the hardware time stamping has 
this problem? This point has me irritated.



The other point we don't have connected the PTP server directly with our PTP 
slave module and it is some Ethernet switches involved in Ethernet 
connection. Could this make a problem?



>(I think you mean PTP_1588_CLOCK)

Yes, it was typo



>Did you enable CONFIG_DP83640_PHY too?

Yes we have also used this option.



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

Thanks. I appreciate your help. :)



>The ptp4l should work with every PHC Linux driver.

Ok. Fine and I am happy to hear that.





>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.



I have adapt the code of PHY driver (net/phy/dp83640.c) with printk and I 
have seen the probe function is executed. I can say the kernel driver is 
compiled and loaded.



I have a question to phy driver dp83640.c only for interest. I have seen in 
probe function that recalibrate(clock) function not always executed directly 
after registration.  What is the reason for this?

I men following code sequence:

==========================================

if (choose_this_phy(clock, phydev)) {                clock->chosen = 
dp83640;                clock->ptp_clock = ptp_clock_register(&clock->caps); 
if (IS_ERR(clock->ptp_clock)) {                        err = 
PTR_ERR(clock->ptp_clock);                        goto 
             }         } else                 list_add_tail(&dp83640->list, 
&clock->phylist);          if (clock->chosen && 
!list_empty(&clock->phylist))                 recalibrate(clock); 
========================================

 Kind regards and thanks again for your help,

Mario



----- Original Message ----- 
From: "Richard Cochran" <ric...@gm...>
To: "Mario Molitor" <Mar...@we...>
Cc: <lin...@li...>
Sent: Tuesday, May 22, 2012 8:17 PM
Subject: Re: [Linuxptp-users] Problems with hardware time stamping with PHY 
DP83640 on MCP5200 powerpc platform


> 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
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Linuxptp-users mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxptp-users