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.

RM0008<br />

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

STM32F107xx buffer. The driver must scan all descriptors, from the last recorded position to<br />

the first one owned by the DMA.<br />

An interrupt is generated only once for simultaneous, multiple events. The driver must scan<br />

the ETH_DMASR register for the cause of the interrupt. The interrupt is not generated again<br />

unless a new interrupting event occurs, after the driver has cleared the appropriate bit in the<br />

ETH_DMASR register. For example, the controller generates a Receive interrupt<br />

(ETH_DMASR register[6]) <strong>and</strong> the driver begins reading the ETH_DMASR register. Next,<br />

receive buffer unavailable (ETH_DMASR register[7]) occurs. The driver clears the Receive<br />

interrupt. Even then, a new interrupt is generated, due to the active or pending Receive<br />

buffer unavailable interrupt.<br />

Figure 318. Interrupt scheme<br />

TBUS<br />

TBUIE<br />

AND<br />

TS<br />

TIE<br />

RS<br />

RIE<br />

AND<br />

AND<br />

ERS<br />

ERIE<br />

AND<br />

OR<br />

NIS<br />

NISE<br />

MMCI<br />

PMTI<br />

TSTI<br />

AND<br />

OR<br />

Interrupt<br />

TPSS<br />

AND<br />

TPSSIE<br />

TUS<br />

AND<br />

TUIE<br />

RWTS<br />

AND<br />

RWTIE<br />

FBES<br />

FBEIE<br />

ROS<br />

ROIE<br />

RBU<br />

RBUIE<br />

AND<br />

AND<br />

AND<br />

TJTS<br />

AND<br />

TJTIE<br />

RPSS<br />

AND<br />

RPSSIE<br />

OR<br />

AIS<br />

AISE<br />

AND<br />

ETS<br />

ETIE<br />

AND<br />

AI15646<br />

27.7 Ethernet interrupts<br />

The Ethernet controller has two interrupt vectors: one dedicated to normal Ethernet<br />

operations <strong>and</strong> the other, used only for the Ethernet wakeup event (with wakeup frame or<br />

Magic Packet detection) when it is mapped on EXTI lIne19.<br />

The first Ethernet vector is reserved for interrupts generated by the MAC <strong>and</strong> the DMA as<br />

listed in the MAC interrupts <strong>and</strong> DMA interrupts sections.<br />

The second vector is reserved for interrupts generated by the PMT on wakeup events. The<br />

mapping of a wakeup event on EXTI line19 causes the STM32F107xx to exit the low power<br />

mode, <strong>and</strong> generates an interrupt.<br />

Doc ID 13902 Rev 9 905/995

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

Saved successfully!

Ooh no, something went wrong!