This is an old revision of the document!
This PHY exchange guide captures pertinent information to support migration from the Qualcomm AR8031/8033 to the Analog Devices ADIN1300 Ethernet PHY. The ADIN1300 has compelling reasons for adoption versus this competitor PHY, such as reduced power consumption, lower latency and supports MII/RMII and RGMII MAC interface modes. The ADIN1300 Ethernet PHY supports all the standard functions and pins of an Ethernet PHY and it is very straight forward to migrate an existing design to the ADIN1300. The following sections detail the modifications at the schematic level required to migrate from a AR8031/8033 device to the ADIN1300 device. Including a description of differences corresponding to each functional group of pins and differences in the hardware pin configuration of the device. A side-by-side pinout and package comparison and a feature comparison table are included for easy reference. The ADIN1300 datasheet provides a detailed description of all functions of the device and should also be consulted for reference.
The ADIN1300 requires a minimum of 2 power supply rails, where the VDDIO is connected to the same power supply voltage as the MAC or as the PHY analog supply AVDD_3P3 (AVDD33). The VDDIO supply rail powers the MAC interface and MDIO blocks, this can operate from 1.8V, 2.5V or 3.3V. The AR8031/8033 can operate off a single 3.3V supply with an internal switching regulator used to generate the 1.1V supply with an external inductor. The supply requirements are listed in Table 1.
The ADIN1300 is robust to power supply sequencing and the power can be applied in any order. Decoupling requirements for each device differ as described in Table 2.
Both devices have a RESET_N (RSTn) pin which initializes the device and latches the hardware pin configuration. To reset the ADIN1300 the RESET_N pin should be held low for >10 μs. Deglitch circuitry is included on this pin to reject pulses shorter than ~1 μs. This pin requires a 1 kΩ pull-up resistor to AVDD_3P3. The ADIN1300 includes power monitoring circuitry to monitor all of the supplies. At power-up, the ADIN1300 is held in hardware reset until each of the supplies has crossed its minimum rising threshold value. The hardware strapping pins are read and updated at the de-assertion of reset for both devices. For the ADIN1300, the RESET_N pin resides in the AVDD_3P3 voltage domain. After 5 ms from the deassertion of RESET_N, the management interface registers are accessible and the device can be programmed. In applications where the MAC interface is powered from VDDIO of 1.8V, level shifting of the RESET_N signal applied to the ADIN1300 may be required to ensure the voltage level on the RESET_N pin is in excess of the minimum input high threshold level. The AR8031/8033 requires an external pull-up resistor on RSTn. The AR8031/8033 requires external input clock that should be stable for at least 1ms before RESET can be deasserted and for chip reliability the external clock must be input after the power-on sequence. When using crystal with the AR8031/8033, the clock is generated internally after power is stable and for a reliable power on reset, reset low long enough (10ms) to ensure the clock is stable and clock-to-reset 1ms requirement is satisfied.
A 25 MHz crystal or external clock source is used to provide the reference clock for both devices. A crystal can be connected to pins XTAL_I/XTAL_O (XTLI/XTLO), with both devices using the same external circuit. Or a 25 MHz refence clock can be provided on the input clock pin CLK_IN (XI). The AR8031/8033 does not support the RMII MAC interface. The ADIN1300 does support RMII and requires an external 50 MHz REF_CLK on the XTAL_I/REF_CLK pin in RMII mode.
An external resistor is required to bias internal reference circuitry for both AR8031/8033 and ADIN1300. The ADIN1300 requires a 3.01 kΩ resistor (1% tolerance, 100 ppm/°C temperature coefficient) connected to pin 10. The AR8031/8033 uses a 2.37 kΩ (1%) on pin 9.
The ADIN1300 has voltage mode line drivers with on-chip terminations so no external termination resistors are required. Both devices use voltage mode line drive for connection from the MDI_0:3_P/N (TRXP/N0:3) pins to the magnetics and RJ-45 line using the same external circuit. The recommended external circuit for the interface to the magnetics and RJ-45 is shown in Figure 1.
Both devices support the IEEE management interface using the MDIO/MDC pins and require a pullup resistor on the MDIO pin (Management Data Open Drain Input/Output). The recommended value for ADIN1300 is a 1.5kΩ resistor connected to pin 24. The AR8031/8033 also recommends a 1.5kΩ resistor connected to pin 48. Both devices provide an interrupt pin, INT_N (¯INT). This pin requires a 1.5 kΩ pull-up resistor to VDDIO. The AR8031/8033 recommends 10kΩ pull-up resistors for their interrupt pin.
The ADIN1300 support two LED pins on LED_0 and LINK_ST. The LED_0 has programmability of LED functions, with different blinking operation possible through MDIO configuration, the default mode is ON when Link is Up, blink if activity. The LINK_ST provides static information about Link up or down status. The AR8031/8033 supports 3 LEDs pins 23, 24, 26. Both devices use these pins for strapping purposes.
The ADIN1300 LED_0 operates from the AVDD_3P3 voltage domain, therefore can support driving LEDs even when the MAC interface is running at the lower voltage of 1.8V. The default LED operation is on if the Link is up and blinks when there is activity, this operation can be reprogrammed through MDIO write. For the LED_0 of the ADIN1300, it can be configured with 4-level strapping. The strapping configuration will have an impact on how the LED function operates and needs to be considered if the LED pins are used to directly drive an LED. If the strap pin is pulled high by the strapping resistors, (MODE_3/MODE_4) the output will be configured as an active low driver and conversely if the strapping input is pulled low (MODE_0/MODE_1), the output will be configured as active high. This LED circuit should be configured accordingly.
The ADIN1300 has a dedicated LINK_ST pin to provide information to the MAC on the status of the Link. By default, the LINK_ST pin goes high indicating the link is up and low to indicate the link is down. The LINK_ST polarity is programmable by setting the bit high GE_LNK_STAT_INV_EN. The LINK_ST could be used to drive an LED, however it resides in the VDDIO voltage domain, therefore, when driving an LED in an integrated RJ45 jack where the PHY VDDIO is 1.8V, level shifting will be required. This can be done using a FET.
The ADIN1300 supports RGMII, MII and RMII MAC interface modes. The following sections describe the RGMII, MII and RMII interfaces for both devices. The AR8031/8033 only supports RGMII and does not support the MII or RMII interface.
The RGMII interface is the communication path between the PHY and MAC devices. The RGMII interface has a low pin count interface supports 10M, 100M and Gigabit operation, with a total of 12 pins for data transmission, reception and to signal errors or collision. It is the most common interface for Gigabit applications and has the lowest latency. Table 5 shows a pin overview of both devices for the RGMII MAC interface mode. Both devices support the internal delay on the clocks. By default, the ADIN1300 is configured in RGMII mode with a 2 ns delay on RXC and TXC.
The AR8031/8033 does not support the MII interface. The MII interface is the communication path between the PHY and MAC devices. The MII interface has a high pin count, with a total of 15 pins for data transmission, reception and to signal errors or collision. It is sometimes used in 100M applications as it has a lower latency than RGMII and is much lower than RMII. Table 5 shows a pin overview of both devices for the MII MAC interface mode. When using the ADIN1300 in MII mode, the multifunction pin “LED_0/COL/TX_ER” automatically becomes either COL or TX_ER. If EEE advertisement is disabled, the pin function is COL as full and half-duplex operation is supported and TX_ER is not required as an input. If EEE advertisement is enabled the pin function is TX_ER as only full duplex operation is supported with EEE and the COL pin is not required. Similarly, the “INT_N/CRS” becomes CRS. The ADIN1300 sub-system registers provide user with ability to reconfigure which pin the COL and CRS functions are provided on (option of redirecting to GP_CLK, LINK_ST or INT_N). This requires a register write over MDIO interface to reconfigure.
The AR8031/8033 does not support the RMII interface. RMII is a reduced MII interface using fewer pins as shown in Table 6. The pin count for this interface is 8 pins.
In RMII mode, the ADIN1300 requires an external 50MHz clock applied to XTAL_I. This clock could come from the MAC.
The ADIN1300 provides a 25 MHz output reference clock on the REF_CLK pin. This can be used a 25 MHz input reference clock for another PHY device. The ADIN1300 can optionally provide a number of clock signals on the GP_CLK pin. This is configured via MDIO writes and the clocks available are a 125 MHz free running clock, 25 MHz clock and 25 MHz/125 MHz recovered clock.
Both devices have a number of strapping options to enable managed or unmanaged configurations of the PHY function such as PHY address, mode of operation, Auto-Negotiation and MAC Interface. After power on, the strapping pin voltages get sensed and latched upon existing from a reset and the sensed voltages are used to set the personality of the PHY. When configuring any strapping configurations, ensure to review the default state of the MAC side, whether the pins are being driven when coming out of reset or if there are internal pulls. Understanding the behavior on the MAC side is key to ensuring there are no conflicts with the hardware strapping implemented, or to adjust the strapping resistor values if required. The ADIN1300 uses a mix of 2-level and 4-level strapping options. The AR8031/8033 just uses 2-level strapping. In general, strapping pins are multi-functional and have different operation after the device is brought out of reset. The ADIN1300 has internal pull downs on many of its strapping pins (not all), therefore it would be possible to minimize external strapping resistors.
Strapping configurations are very specific to the device, consult the respective datasheets to determine the exact configuration for required use case.
For the ADIN1300, speed configuration is done using two pins, PHY_CFG0 and PHY_CFG1. These pins do not have any internal pull resistors, therefore external strapping is required. Both pins support 4-level strapping, providing much flexibility in terms of the possible combinations, such as Auto-neg speeds shown in Table 8 or Forced modes shown in Table 9. Review the datasheet hardware configuration pin section for full detail on the possible settings using these pins.
Selection of Auto-MDIX for the ADIN1300 is done using one pin, (MDIX_MODE) with 4-level strapping.
The ADIN1300 uses two hardware pins, MACIF_SEL0 and MACIF_SEL1 to provide user ability to select different MAC interfaces. These two pins have internal weak pull downs, therefore the default operation would be RGMII with delays as shown in Table 11. To configure any other MAC interface mode, use 10kΩ pull up or pull down resistors to select accordingly.
The ADIN1300 has a default strapping providing a PHY address of 0x0000. The AR8031/8033 has a default strapping providing a PHY address of 0x0004. The ADIN1300 uses two-level strapping for the four PHY address pins, either pull high or low to configure the PHY address, with an option of 16 unique addresses possible. Two level strapping provides a very robust PHY addressing scheme. The AR8031/8033 provides two- level strapping for the PHY address pins, capable of 8 unique address. When configuring any strapping configurations, assess the default state of the MAC side, in case it conflicts with the hardware strapping implemented.
The ADIN1300 is available in a 40 lead LFCSP (6 mm x 6 mm footprint). The AR8031/8033 is available in a 48 lead QFN (6 mm x 6 mm). Note the AR8031/8033 package has a 0.4 mm pin pitch, where the ADIN1300 uses a standard 0.5 mm pin pitch. Due to the different package footprint and differing pinout, the ADIN1300 is not a drop-in replacement for the AR8031/8033 product. It will require a re-spin of schematic and board layout to achieve this exchange.
The underside of the LFCSP package for the ADIN1300 includes an exposed paddle which should be soldered directly to the board with an array of vias for thermal purposes. There are also two exposed stripes adjacent to the exposed paddle. These do not need to be soldered to the board, they should be treated as a keep out area as they are connected to supply rails in the device, therefore should not be tied to ground and there should be no routing or traces on the PCB layer directly underneath them.
Both devices include integrated termination resistors on the MDI paths. These are voltage mode PHYs, no external resistors are required for biasing and no supply voltage is required at the center tap of the transformer.
The ADIN1300 provides user with ability to adjust the RGMII drive current through the GE_RGMII_IO_CNTRL register.
The ADIN1300 supports MII MAC interface mode for 10/100M operation. The AR8031/8033 does not support the MII interface.
The ADIN1300 supports RMII MAC interface mode for 10/100M operation. The AR8031/8033 does not support the RMII interface.
The ADIN1300 and AR8031/8033 do not support the GMII interface.
The ADIN1300 and AR8031/8033 do not support the SGMII interface.
The ADIN1300 and AR8031/8033 do not support fiber protocols.
Both devices can be hardware strapped to be used in an unmanaged configuration. Alternatively, they can provide SMI/MII access over the MDIO interface. The AR8031/8033 supports Clause 22 register access, while the ADIN1300 supports both Clause 22 and Clause 45 register access using both the 802.3 Clause 22 and Clause 45 management frame structures. Registers 0x0 to 0xF are common across all PHYs.
The ADIN1300 has a Linux Driver available in the Linux mainline kernel. The ADIN1300 linux driver detail is captured here: https://wiki.analog.com/resources/tools-software/linux-drivers/net-phy/adin
The ADIN1200 has a C Non Operating System Driver available from the devices product page here: en/products/adin1200.html#product-requirement
The following is a side-by-side comparison of the package and pinouts, showing the position of the corresponding functional pins on each device.
The following example captures how to configure the ADIN1300 for an unmanaged configuration with RGMII Interface, operating in Auto Negotiation mode advertising all speeds. The PHY will power up in this state, ready to establish a link with a link partner. The MAC interface configuration pins (MACIF_SEL0/1) are pulled to ground, setting the PHY to RGMII mode with 2ns Delay on RXC & TXC. GP_CLK is pulled to VDDIO to configure an automatic MDIX operation. In addition, the PHY_CFG0 and PHY_CFG1 pins are configured for MODE_4 and MODE_1 respectively. The PHY_CFG0 pin is also shared with the LED_0 pin, it’s configuration with MODE_4 means an active low LED can be used on LED_0.
The following list summarizes an RGMII auto negotiate, 10 Mbps, 100 Mbps, or 1000 Mbps with full duplex or half duplex, with the software power-down enabled after reset: