29.01.2015 Views

STM32F101xx, STM32F102xx, STM32F103xx, STM32F105xx and ...

STM32F101xx, STM32F102xx, STM32F103xx, STM32F105xx and ...

STM32F101xx, STM32F102xx, STM32F103xx, STM32F105xx and ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Ethernet (ETH): media access control (MAC) with DMA controller<br />

RM0008<br />

6. Turn-off the application <strong>and</strong> transmit clock inputs to the core (<strong>and</strong> other relevant clocks<br />

in the system) to reduce power <strong>and</strong> enter Sleep mode.<br />

7. On receiving a valid wakeup frame, the Ethernet peripheral exits Power-down mode.<br />

8. On receiving the interrupt, the system must enable the application <strong>and</strong> transmit clock<br />

inputs to the Ethernet.<br />

9. Read the ETH_MACPMTCSR register to clear the interrupt, then enable the MAC <strong>and</strong><br />

resume normal operation.<br />

27.5.9 Precision time protocol (IEEE1588 PTP)<br />

The IEEE 1588 st<strong>and</strong>ard defines a protocol that allows precise clock synchronization in<br />

measurement <strong>and</strong> control systems implemented with technologies such as network<br />

communication, local computing <strong>and</strong> distributed objects. The protocol applies to systems<br />

that communicate by local area networks supporting multicast messaging, including (but not<br />

limited to) Ethernet. This protocol is used to synchronize heterogeneous systems that<br />

include clocks of varying inherent precision, resolution <strong>and</strong> stability. The protocol supports<br />

system-wide synchronization accuracy in the submicrosecond range with minimum network<br />

<strong>and</strong> local clock computing resources. The message-based protocol, known as the precision<br />

time protocol (PTP), is transported over UDP/IP. The system or network is classified into<br />

Master <strong>and</strong> Slave nodes for distributing the timing/clock information. The protocol’s<br />

technique for synchronizing a slave node to a master node by exchanging PTP messages is<br />

described in Figure 306.<br />

Figure 306. Networked time synchronization<br />

Master clock time<br />

Slave clock time<br />

t 1<br />

Sync message<br />

Data at<br />

slave clock<br />

t 2m<br />

Follow_up message<br />

containing value of t1<br />

t 2<br />

t 2<br />

t 1 , t 2 , t 3<br />

ai15669<br />

t 1 , t 2<br />

t 3m<br />

t 4<br />

t 1 , t 2 , t 3 , t 4<br />

Delay_Req message<br />

t 3<br />

Delay_Resp message<br />

containing value of t4<br />

time<br />

1. The master broadcasts PTP Sync messages to all its nodes. The Sync message<br />

contains the master’s reference time information. The time at which this message<br />

leaves the master’s system is t 1 . For Ethernet ports, this time has to be captured at the<br />

MII.<br />

2. A slave receives the Sync message <strong>and</strong> also captures the exact time, t 2 , using its<br />

timing reference.<br />

872/995 Doc ID 13902 Rev 9

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!