Just a short update along the lines of this thread:
On top of the previous work on PPS input to i210,
I've cobbled together a simple PLL synth with a 25MHz VCXO,
good enough to take an external 10 MHz reference
and "influence" the crystal on an i210 to run in step with the PPS.
(I could as well
...due to problems with direct attachments in this list, please
download the attachments mentioned in message text from here:
http://support.fccps.cz/download/adv/frr/ptp/i210_ext_pps.zip
On 13 Feb 2018 at 17:11, frantisek.rysa...@post.cz wrote:
>
> Dear everyone (maybe Mr. Cochran especially),
Just for the record:
On 13 Feb 2018 at 8:05, Richard Cochran wrote:
>
> The reason for this is that that the i210 latches the time on both
> rising and falling edges of the input signal. You can't program it
> for rising edge only, for example.
>
I've checked the datasheet again and you're
Dear everyone (maybe Mr. Cochran especially),
my setup with external PPS has started showing basic signs of life.
Interestingly, my two i210 cards seem to be throwing an event on both
PPS edges, rising and falling :-) They're spaced 200 ms apart.
And, somehow the system converges to the "wrong"
Ohh... excellent, that answers a question from my next message :-)
In fact I don't mind if I see the falling edges as well - only I
should detect them somehow, by timing calculation if there's no other
way, and ignore them in the servo policing loop.
As my application is tcpdump timestamping
Dear Mr. Cochran,
I've finally got back to my plan (ext.PPS to 2-4 i210 chips for
tcpdump timestamping) and I'm reviewing your proggie.
Yes the code is pretty self-explanatory :-) and packed with gems.
If I understand correctly, setting up the SDP0 GPIO for external
PPS input (which takes two
On Mon, Dec 11, 2017 at 04:17:14PM +0100, Frantisek Rysanek wrote:
> ...oops... ...forgot to post this to the mailing list...
and again, my reply was:
On Mon, Dec 11, 2017 at 12:42:20PM +0100, Frantisek Rysanek wrote:
> If I provide an UTC-synchronous PPS externally (from a GPS receiver),
> to
On Mon, Dec 11, 2017 at 04:25:42PM +0100, Frantisek Rysanek wrote:
> Oh... and this one also went to Mr. Cochran directly. Apologies.
> I already got an answer from him and I'm past this stage,
> but I'm forwarding this into the mailing-list "for the record",
> to give some food to the Google
Oh... and this one also went to Mr. Cochran directly. Apologies.
I already got an answer from him and I'm past this stage,
but I'm forwarding this into the mailing-list "for the record",
to give some food to the Google spider.
FR
On 8 Dec 2017 at 15:59, Richard Cochran wrote:
> On Fri, Dec 08,
...oops... ...forgot to post this to the mailing list...
On 10 Dec 2017 at 19:20, Richard Cochran wrote:
> Just use
>
> tcpdump \
> -j adapter_unsynced \
>
>
On Fri, Dec 08, 2017 at 11:09:40PM +, Keller, Jacob E wrote:
> I'm thinking the best way is to use the external timestamp events setup, and
> then plug that in as the pps source into phc2sys?
>
> Does this make any sense, or am I paddling up the wrong creek?
So you *could* extend phc2sys,
Hey Richard and others,
I've been recently investigating a setup where two ethernet devices with
support for PHCs have hooked up one GPIO pin from one device into a GPIO of the
second device. The intent was to have the first device trigger a PPS signal on
the pin, while the second device
12 matches
Mail list logo
