![]() This module implements the Ethernet Interface. R_ETHER_TxStatusGet ( ether_ctrl_t *const p_ctrl, void *const p_buffer_address)ĭriver for the Ethernet peripheral on RA MCUs. In the non zero copy mode, transmits data after being copied to the internal buffer. Transmits data from the location specified by the pointer to the transmit buffer, with the data size equal to the specified frame length. R_ETHER_Write ( ether_ctrl_t *const p_ctrl, void *const p_buffer, uint32_t const frame_length) In non zero copy mode, the received data in the internal buffer is copied to the pointer passed by the argument. In zero copy mode, the address of the receive buffer is returned. Receives data to the location specified by the pointer to the receive buffer. R_ETHER_Read ( ether_ctrl_t *const p_ctrl, void *const p_buffer, uint32_t *const length_bytes) The setting of ETHERC is changed from normal sending and receiving mode to magic packet detection mode. R_ETHER_WakeOnLANEnable ( ether_ctrl_t *const p_ctrl) ![]() The Link up processing, the Link down processing, and the magic packet detection processing are executed. R_ETHER_LinkProcess ( ether_ctrl_t *const p_ctrl) R_ETHER_RxBufferUpdate ( ether_ctrl_t *const p_ctrl, void *const p_buffer)Ĭhange the buffer pointer of the current rx buffer descriptor. Move to the next buffer in the circular receive buffer list. R_ETHER_BufferRelease ( ether_ctrl_t *const p_ctrl) Removes power and releases hardware lock. ![]() R_ETHER_Close ( ether_ctrl_t *const p_ctrl)ĭisables interrupts. Afterwards, the link signal change interrupt is permitted. The following example code shows the usage of the Ethernet interface.R_ETHER_Open ( ether_ctrl_t *const p_ctrl, ether_cfg_t const *const p_cfg)Īfter ETHERC, EDMAC and PHY-LSI are reset in software, an auto negotiation of PHY-LSI is begun. A typical setup sequence for the drivers is shown below: ARM_DRIVER_ETH_PHY : access struct for Ethernet PHY driver functions.īoth drivers are used in combination and usually the Ethernet MAC provides a media interface to the Ethernet PHY.ARM_DRIVER_ETH_MAC : access struct for Ethernet MAC driver functions.The driver functions are published in the access struct as explained in Common Driver Functions ![]() Note For parameters, the value marked with (default) is the setting after the driver initialization. The driver implementation of the Ethernet PHY is a typical part of a Network Software Pack, since PHY is typically not integrated into the microcontroller. The driver implementation of the Ethernet MAC is a typical part of a Device Family Pack (DFP) that supports the peripherals of the microcontroller family. Driver_ETH_PHY.h : API for the Ethernet PHY.Driver_ETH_MAC.h : API for the Ethernet MAC.Driver_ETH.h : Common definitions of the Ethernet PHY and MAC part.The following header files define the Application Programming Interface (API) for the Ethernet interface: The Ethernet PHY connects typically to the Ethernet MAC using an MII (Media Independent Interface) or RMII (Reduced Media Independent Interface).īlock Diagram of a typical Ethernet Interface Wikipedia offers more information about the Ethernet. Several microcontrollers integrate an Ethernet MAC (Media Access Control) data-link layer that interfaces to an Ethernet PHY (Physical Interface Transceiver). Ethernet common definitions (Driver_ETH.h)ĭriver API for Ethernet MAC Peripheral (Driver_ETH_MAC.h)ĭriver API for Ethernet PHY Peripheral (Driver_ETH_PHY.h)Įthernet is a networking technology for exchanging data packages between computer systems.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |