An IEEE 1588 Precision Time Protocol core that distributes accurate time across a network so distributed nodes share a common clock, with a variant for automotive Ethernet. Timing is one of those requirements that is invisible until it is wrong, at which point every downstream measurement is wrong with it.
IEEE 1588 defines how nodes on a packet network agree on time. A master distributes timestamps, slaves measure the delay in both directions, and each node corrects its local clock against the difference. The accuracy achievable depends almost entirely on where in the stack the timestamp is taken — software timestamping is at the mercy of scheduling jitter, hardware timestamping at the media-independent interface is not.
This core implements the protocol machinery with hardware timestamping, so the accuracy is set by the physical layer rather than by whatever the processor happened to be doing. It integrates as a block within a larger SoC or as a discrete function alongside a MAC.
The automotive Ethernet variant exists because vehicle networks have a specific problem: sensor data from cameras, radar and inertial units is only fusable if the timestamps agree. A consistent offset between two sensors becomes a consistent position error proportional to relative velocity, and a tracker learns that bias rather than correcting it.
| Parameter | Detail |
|---|---|
| Standard | IEEE 1588 Precision Time Protocol |
| Timestamping | Hardware, taken at the media-independent interface |
| Roles | Master, slave and boundary clock configurations |
| Variant | Automotive Ethernet profile |
| Interface | Configurable to the host bus and MAC in the target design |
| Delivery | Synthesisable RTL with integration documentation and verification collateral |
| Typical markets | Telecom transport, industrial control, automotive, test and measurement |
Maturity — silicon-proven, FPGA-validated or RTL stage — is confirmed at enquiry for the specific configuration you need, rather than claimed generically here.
Send the target node, the interface requirements and the integration context. If this is not the right fit, that will be said early rather than discovered at integration.
It distributes accurate time across a packet network so distributed nodes share a common clock. It is used in telecom transport, industrial control, automotive sensor networks, test and measurement, and power system automation.
Because software timestamping is subject to scheduling jitter and interrupt latency, which sets a floor on achievable accuracy that is orders of magnitude above what hardware timestamping at the media-independent interface delivers.
It targets the automotive Ethernet profile and the specific requirement that distributed sensor data carry consistent timestamps, because a timing offset between sensors becomes a position error proportional to relative velocity when their data is fused.
Tell us the specification, the constraint and the deadline. Programmes that cross silicon, radio, embedded and AI are where Faststream is strongest.