Functions
fsp_err_t	R_ETHERCAT_PHY_Open (ether_phy_ctrl_t const p_ctrl, ether_phy_cfg_t const const p_cfg)
	Resets Ethercat PHY device. Implements ether_phy_api_t::open. More...

fsp_err_t	R_ETHERCAT_PHY_Close (ether_phy_ctrl_t *const p_ctrl)
	Close Ethercat PHY device. Implements ether_phy_api_t::close. More...

fsp_err_t	R_ETHERCAT_PHY_StartAutoNegotiate (ether_phy_ctrl_t *const p_ctrl)
	Starts auto-negotiate. Implements ether_phy_api_t::startAutoNegotiate. More...

fsp_err_t	R_ETHERCAT_PHY_LinkPartnerAbilityGet (ether_phy_ctrl_t const p_ctrl, uint32_t const p_line_speed_duplex, uint32_t const p_local_pause, uint32_t const p_partner_pause)
	Reports the other side's physical capability. Implements ether_phy_api_t::linkPartnerAbilityGet. More...

fsp_err_t	R_ETHERCAT_PHY_LinkStatusGet (ether_phy_ctrl_t *const p_ctrl)
	Returns the status of the physical link. Implements ether_phy_api_t::linkStatusGet. More...

fsp_err_t	R_ETHERCAT_PHY_ChipInit (ether_phy_ctrl_t const p_ctrl, ether_phy_cfg_t const const p_cfg)
	Initialize Ethercat PHY device. Implements ether_phy_api_t::chipInit. More...

fsp_err_t	R_ETHERCAT_PHY_Read (ether_phy_ctrl_t const p_ctrl, uint32_t reg_addr, uint32_t const p_data)
	Read data from register of PHY-LSI . Implements ether_phy_api_t::read. More...

fsp_err_t	R_ETHERCAT_PHY_Write (ether_phy_ctrl_t *const p_ctrl, uint32_t reg_addr, uint32_t data)
	Write data to register of PHY-LSI . Implements ether_phy_api_t::write. More...

Detailed Description

The Ethercat PHY module (r_ethercat_phy) provides an API for standard Ethercat PHY communications applications that use the ETHERC peripheral. It implements the Ethernet PHY Interface.

Overview

The Ethercat PHY module is used to setup and manage an external Ethercat PHY device for use with the on-chip Ethercat Slave Controller (ESC) peripheral. It performs auto-negotiation to determine the optimal connection parameters between link partners. Once initialized the connection between the external PHY and the onboard controller is automatically managed in hardware.

Features

The Ethercat PHY module supports the following features:

Auto negotiation support
Flow control support
Link status check support

Configuration

Build Time Configurations for r_ethercat_phy

The following build time configurations are defined in fsp_cfg/r_ethercat_phy_cfg.h:

Configuration	Options	Default	Description
Parameter Checking	Default (BSP) Enabled Disabled	Default (BSP)	If selected code for parameter checking is included in the build.
ICS1894 Target	Disabled Enabled	Disabled	Select whether to use ICS1894 Phy LSI or not.
User Own Target	Disabled Enabled	Disabled	Select whether to use User own Phy LSI or not.

Configurations for Networking > Ethernet (r_ethercat_phy)

This module can be added to the Stacks tab via New Stack > Networking > Ethernet (r_ethercat_phy). Non-secure callable guard functions can be generated for this module by right clicking the module in the RA Configuration tool and checking the "Non-secure Callable" box.

Configuration	Options	Default	Description
Name	Name must be a valid C symbol	g_ethercat_phy0	Module name.
Channel	0 1	0	Select the Ethernet controller channel number.
PHY-LSI Address	Specify a value between 0 and 31.	0	Specify the address of the PHY-LSI used.
PHY-LSI Reset Completion Timeout	Specify a value between 0x1 and 0xFFFFFFFF.	0x00020000	Specify the number of times to read the PHY-LSI control register while waiting for reset completion. This value should be adjusted experimentally based on the PHY-LSI used.
Select MII type	MII	module.driver.ether_phy.mii_type.rmii	Specify to use MII.
PHY-LSI Type	Kit Component DEFAULT ICS1894 User own PHY	Kit Component	Select the Phy LSI target. Selecting 'Kit Component' will automatically choose the correct option when using a Renesas development board.
Target Init Function	Name must be a valid C symbol	NULL	Set the initial function of the PHY-LSI, When using your own PHY-LSI.
Target Link Partner Ability Get Function	Name must be a valid C symbol	NULL	Set the link partner ability get function of the PHY-LSI, When using your own PHY-LSI.
MII Register Access Wait-time	Specify a value between 0x1 and 0x7FFFFFFF.	8	Specify the bit timing for MII register accesses during PHY initialization. This value should be adjusted experimentally based on the PHY-LSI used.
Flow Control	Disable Enable	Disable	Select whether to enable or disable flow control.

Usage Notes

Note: See the example below for details on how to initialize the Ethercat PHY module.

Accessing the MII and RMII Registers

Use the PIR register to access the MII and RMII registers in the PHY-LSI. Serial data in the MII and RMII management frame format is transmitted and received through the ET0_MDC and ET0_MDIO pins controlled by software.

MII and RMII management frame format

The below table lists the MII and RMII management frame formats.

Access type		MII and RMII management frame
	Item	PRE	ST	OP	PHYAD	REGAD	TA	DATA	IDLE
	Number of bits	32	2	2	5	5	2	16	1
Read		1...1	01	10	00001	RRRRR	Z0	DDDDDDDDDDDDDDDD	Z
Write		1...1	01	01	00001	RRRRR	10	DDDDDDDDDDDDDDDD	Z

Note: - PRE (preamble): Send 32 consecutive 1s.; - ST (start of frame): Send 01b.; - OP (operation code): Send 10b for read or 01b for write.; - PHYAD (PHY address): Up to 32 PHY-LSIs can be connected to one MAC. PHY-LSIs are selected with these 5 bits. When the PHY-LSI address is 1, send 00001b.; - REGAD (register address): One register is selected from up to 32 registers in the PHY-LSI. When the register address is 1, send 00001b.; - TA (turnaround): Use 2-bit turnaround time to avoid contention between the register address and data during a read operation.; Send 10b during a write operation. Release the bus for 1 bit during a read operation (Z is output).; (This is indicated as Z0 because 0 is output from the PHY-LSI on the next clock cycle.); - DATA (data): 16-bit data. Sequentially send or receive starting from the MSB.; - IDLE (IDLE condition): Wait time before inputting the next MII or RMII management format. Release the bus during a write; operation (Z is output). No control is required, because a bus was already released during a read operation.

Limitations

The r_ethercat_phy module may need to be customized for PHY devices other than the ones currently supported. Use the existing code as a starting point for creating a custom implementation. Supported PHY devices are as follows.
- ICS1894

Examples

ETHERCAT PHY Basic Example

This is a basic example of minimal use of the ETHERCAT PHY in an application.

void ethercat_phy_basic_example (void)
{
    fsp_err_t err = FSP_SUCCESS;
    g_ethercat_phy0_ctrl.open   = 0U;
    g_ethercat_phy0_cfg.channel = 0;
    /* Initializes the module. */
    err = R_ETHERCAT_PHY_Open(&g_ethercat_phy0_ctrl, &g_ethercat_phy0_cfg);
    /* Handle any errors. This function should be defined by the user. */
    assert(FSP_SUCCESS == err);
    /* Start auto negotiation. */
    err = R_ETHERCAT_PHY_StartAutoNegotiate(&g_ethercat_phy0_ctrl);
    assert(FSP_SUCCESS == err);
    /* Polling until link is established. */
    while (FSP_SUCCESS != R_ETHERCAT_PHY_LinkStatusGet(&g_ethercat_phy0_ctrl))
    {
        /* Do nothing */
    }
    /* Get link partner ability from phy interface. */
    err = R_ETHERCAT_PHY_LinkPartnerAbilityGet(&g_ethercat_phy0_ctrl,
                                               &g_ethercat_phy0_line_speed_duplex,
                                               &g_ethercat_phy0_local_pause,
                                               &g_ethercat_phy0_partner_pause);
    assert(FSP_SUCCESS == err);
    /* Check current link status. */
    err = R_ETHERCAT_PHY_LinkStatusGet(&g_ethercat_phy0_ctrl);
    assert(FSP_SUCCESS == err);
}

Data Structures
struct	ethercat_phy_instance_ctrl_t

struct	ethercat_phy_extended_cfg_t

Enumerations
enum	ethercat_phy_interface_status_t

Data Structure Documentation

◆ ethercat_phy_instance_ctrl_t

struct ethercat_phy_instance_ctrl_t

ETHER PHY control block. DO NOT INITIALIZE. Initialization occurs when ether_phy_api_t::open is called.

Data Fields
uint32_t	open	Used to determine if the channel is configured.
ether_phy_cfg_t const *	p_ether_phy_cfg	Pointer to initial configurations.
uint32_t	local_advertise	Capabilities bitmap for local advertising.
ethercat_phy_interface_status_t	interface_status	Initialized status of ETHER PHY interface.

◆ ethercat_phy_extended_cfg_t

struct ethercat_phy_extended_cfg_t

ETHERCAT PHY extended configuration.

Data Fields
void(*	p_target_init )(ethercat_phy_instance_ctrl_t *p_instance_ctrl)
	Pointer to callback that is called to initialize the target.

bool(*	p_target_link_partner_ability_get )(ethercat_phy_instance_ctrl_t *p_instance_ctrl, uint32_t line_speed_duplex)
	Pointer to callback that is called to get the link partner ability.

Enumeration Type Documentation

◆ ethercat_phy_interface_status_t

enum ethercat_phy_interface_status_t

Initialization state for read/write

Enumerator
ETHERCAT_PHY_INTERFACE_STATUS_UNINITIALIZED	ETHER PHY interface is uninitialized.
ETHERCAT_PHY_INTERFACE_STATUS_INITIALIZED	ETHER PHY interface is initialized.

Function Documentation

◆ R_ETHERCAT_PHY_Open()

fsp_err_t R_ETHERCAT_PHY_Open	(	ether_phy_ctrl_t *const	p_ctrl,
		ether_phy_cfg_t const *const	p_cfg
	)

Resets Ethercat PHY device. Implements ether_phy_api_t::open.

Return values

FSP_SUCCESS	Channel opened successfully.
FSP_ERR_ASSERTION	Pointer to ETHERCAT_PHY control block or configuration structure is NULL.
FSP_ERR_ALREADY_OPEN	Control block has already been opened or channel is being used by another instance. Call close() then open() to reconfigure.
FSP_ERR_INVALID_CHANNEL	Invalid channel number is given.
FSP_ERR_INVALID_POINTER	Pointer to p_cfg is NULL.

◆ R_ETHERCAT_PHY_Close()

fsp_err_t R_ETHERCAT_PHY_Close ( ether_phy_ctrl_t *const p_ctrl )

Close Ethercat PHY device. Implements ether_phy_api_t::close.

Return values

FSP_SUCCESS	Channel successfully closed.
FSP_ERR_ASSERTION	Pointer to ETHERCAT_PHY control block is NULL.
FSP_ERR_NOT_OPEN	The control block has not been opened

◆ R_ETHERCAT_PHY_StartAutoNegotiate()

fsp_err_t R_ETHERCAT_PHY_StartAutoNegotiate ( ether_phy_ctrl_t *const p_ctrl )

Starts auto-negotiate. Implements ether_phy_api_t::startAutoNegotiate.

Return values

FSP_SUCCESS	ETHERCAT_PHY successfully starts auto-negotiate.
FSP_ERR_ASSERTION	Pointer to ETHERCAT_PHY control block is NULL.
FSP_ERR_NOT_OPEN	The control block has not been opened
FSP_ERR_INVALID_ARGUMENT	Register address is incorrect
FSP_ERR_INVALID_MODE	Command is invalid.
FSP_ERR_INVALID_POINTER	Pointer to read buffer is NULL.
FSP_ERR_NOT_INITIALIZED	The control block has not been initialized

◆ R_ETHERCAT_PHY_LinkPartnerAbilityGet()

fsp_err_t R_ETHERCAT_PHY_LinkPartnerAbilityGet	(	ether_phy_ctrl_t *const	p_ctrl,
		uint32_t *const	p_line_speed_duplex,
		uint32_t *const	p_local_pause,
		uint32_t *const	p_partner_pause
	)

Reports the other side's physical capability. Implements ether_phy_api_t::linkPartnerAbilityGet.

Return values

FSP_SUCCESS	ETHERCAT_PHY successfully get link partner ability.
FSP_ERR_ASSERTION	Pointer to ETHERCAT_PHY control block is NULL.
FSP_ERR_INVALID_POINTER	Pointer to arguments are NULL.
FSP_ERR_NOT_OPEN	The control block has not been opened
FSP_ERR_ETHER_PHY_ERROR_LINK	PHY-LSI is not link up.
FSP_ERR_ETHER_PHY_NOT_READY	The auto-negotiation isn't completed
FSP_ERR_INVALID_ARGUMENT	Status register address is incorrect
FSP_ERR_INVALID_MODE	Command is invalid.
FSP_ERR_NOT_INITIALIZED	The control block has not been initialized

◆ R_ETHERCAT_PHY_LinkStatusGet()

fsp_err_t R_ETHERCAT_PHY_LinkStatusGet ( ether_phy_ctrl_t *const p_ctrl )

Returns the status of the physical link. Implements ether_phy_api_t::linkStatusGet.

Return values

FSP_SUCCESS	ETHERCAT_PHY successfully get link partner ability.
FSP_ERR_ASSERTION	Pointer to ETHERCAT_PHY control block is NULL.
FSP_ERR_NOT_OPEN	The control block has not been opened
FSP_ERR_ETHER_PHY_ERROR_LINK	PHY-LSI is not link up.
FSP_ERR_INVALID_ARGUMENT	Status register address is incorrect
FSP_ERR_INVALID_MODE	Command is invalid.
FSP_ERR_INVALID_POINTER	Pointer to read buffer is NULL.
FSP_ERR_NOT_INITIALIZED	The control block has not been initialized

◆ R_ETHERCAT_PHY_ChipInit()

fsp_err_t R_ETHERCAT_PHY_ChipInit	(	ether_phy_ctrl_t *const	p_ctrl,
		ether_phy_cfg_t const *const	p_cfg
	)

Initialize Ethercat PHY device. Implements ether_phy_api_t::chipInit.

Return values

FSP_SUCCESS	PHY device initialized successfully.
FSP_ERR_ASSERTION	Pointer to ETHERCAT_PHY control block or configuration structure is NULL.
FSP_ERR_INVALID_POINTER	Pointer to p_cfg is NULL.
FSP_ERR_NOT_OPEN	The control block has not been opened.
FSP_ERR_TIMEOUT	PHY-LSI Reset wait timeout.

◆ R_ETHERCAT_PHY_Read()

fsp_err_t R_ETHERCAT_PHY_Read	(	ether_phy_ctrl_t *const	p_ctrl,
		uint32_t	reg_addr,
		uint32_t *const	p_data
	)

Read data from register of PHY-LSI . Implements ether_phy_api_t::read.

Return values

FSP_SUCCESS	ETHERCAT_PHY successfully read data.
FSP_ERR_ASSERTION	Pointer to ETHERCAT_PHY control block is NULL.
FSP_ERR_INVALID_POINTER	Pointer to read buffer is NULL.
FSP_ERR_INVALID_ARGUMENT	Address is not a valid size
FSP_ERR_INVALID_MODE	Command is invalid.
FSP_ERR_NOT_INITIALIZED	The control block has not been initialized

◆ R_ETHERCAT_PHY_Write()

fsp_err_t R_ETHERCAT_PHY_Write	(	ether_phy_ctrl_t *const	p_ctrl,
		uint32_t	reg_addr,
		uint32_t	data
	)

Write data to register of PHY-LSI . Implements ether_phy_api_t::write.

Return values

FSP_SUCCESS	ETHERCAT_PHY successfully write data.
FSP_ERR_ASSERTION	Pointer to ETHERCAT_PHY control block is NULL.
FSP_ERR_INVALID_ARGUMENT	Address or data is not a valid size
FSP_ERR_INVALID_MODE	Command is invalid.
FSP_ERR_NOT_INITIALIZED	The control block has not been initialized

Functions

Detailed Description

Overview

Features

Configuration

Build Time Configurations for r_ethercat_phy

Configurations for Networking > Ethernet (r_ethercat_phy)

Usage Notes

Accessing the MII and RMII Registers

MII and RMII management frame format

Limitations

Examples

ETHERCAT PHY Basic Example

Data Structures

Enumerations

Data Structure Documentation

◆ ethercat_phy_instance_ctrl_t

◆ ethercat_phy_extended_cfg_t

Data Fields

Enumeration Type Documentation

◆ ethercat_phy_interface_status_t

Function Documentation

◆ R_ETHERCAT_PHY_Open()

◆ R_ETHERCAT_PHY_Close()

◆ R_ETHERCAT_PHY_StartAutoNegotiate()

◆ R_ETHERCAT_PHY_LinkPartnerAbilityGet()

◆ R_ETHERCAT_PHY_LinkStatusGet()

◆ R_ETHERCAT_PHY_ChipInit()

◆ R_ETHERCAT_PHY_Read()

◆ R_ETHERCAT_PHY_Write()