Wiki

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
resources:eval:user-guides:adin1300-and-adin1200:phy_faq [11 Aug 2021 19:02] – [Longer cable length?] Catherine Redmondresources:eval:user-guides:adin1300-and-adin1200:phy_faq [16 Jan 2023 10:37] (current) – Added section for MDI pins in Unpowered device Mark Bolger
Line 44: Line 44:
  
  
 +===== Timing / Latency Maximum Receive Time =====
 +The Receive latency numbers quoted in Table 1 from the Datasheet are measured from start of data at MDI to the positive edge from RGMII.RXCLK. These are following the MDI to MII/GMII delay constraint definitions in Table 24-2/3 in IEEE Std 802.3 for 100BASE-TX and Table 40-14 for 1000BASE-T, extended to 10BASE-T and RMII/RGMII using the same reference points, i.e.
 +
 +  * TX_EN/TX_CTL sampled with the rising edge of TX_CLK/TXC/REF_CLK to 1st bit/symbol on MDI
 +
 +  * 1st bit/symbol on MDI to RX_DV sampled with the rising edge of RX_CLK/RXC/REF_CLK
 +
 +----
  
 ===== Resistor Values for Hardware pin config ===== ===== Resistor Values for Hardware pin config =====
Line 151: Line 159:
 The ADIN1200 supports cable lengths as long as 180m. Limited additional experimental data with the ADIN1200 suggests it can operate out to 210 meters (at 100 Mbps) over CAT5 cable with the default configuration settings.  The ADIN1200 supports cable lengths as long as 180m. Limited additional experimental data with the ADIN1200 suggests it can operate out to 210 meters (at 100 Mbps) over CAT5 cable with the default configuration settings. 
  
- +----
  
 ===== 1588 Start of Packet Programmable Delays ===== ===== 1588 Start of Packet Programmable Delays =====
Line 175: Line 182:
 The SopRxDel delay does not make so much sense in general for ADIN1200/1300. Given that the RX SOP on the MDI pins will happen before the RX_SOP signal on the chip pin, to align both signals (as done in the TX side), it would be required to advance the RX_SOP signal rather than delay it, but that is obviously not possible. Therefore, the SopRxDel delay was intended for a different purpose, it is provided for cases where there may be a very long latency in the MAC interface (for example if the PHY had an SGMII interface) to ensure that the RX_SOP signal is received at the MAC side during the corresponding frame, as if that was not the case it might cause problems. The SopRxDel delay does not make so much sense in general for ADIN1200/1300. Given that the RX SOP on the MDI pins will happen before the RX_SOP signal on the chip pin, to align both signals (as done in the TX side), it would be required to advance the RX_SOP signal rather than delay it, but that is obviously not possible. Therefore, the SopRxDel delay was intended for a different purpose, it is provided for cases where there may be a very long latency in the MAC interface (for example if the PHY had an SGMII interface) to ensure that the RX_SOP signal is received at the MAC side during the corresponding frame, as if that was not the case it might cause problems.
 {{ :resources:eval:user-guides:adin1300-and-adin1200:soprx.png?nolink&600 |}} {{ :resources:eval:user-guides:adin1300-and-adin1200:soprx.png?nolink&600 |}}
 +
 +----
 +
 +===== Voltage Mode Line Drive =====
 +
 +The ADIN1200 & ADIN1300 are voltage mode with on chip terminations. Therefore, there is no need for external termination resistors from the center tap of the transformer to the supply as required in current mode line drivers. 
 +In addition to reducing components, Voltage mode driver also manifests a significant reduction in power consumption versus current mode. 
 +
 +When comparing PHY devices, ensure to check whether the output stage is voltage mode or current mode and also review whether the power consumption figures for current mode include the current dissipated in the transformer as a result of termination resistors. 
 +
 +----
 +
 +===== Connecting a Cable to an Unpowered Device =====
 +
 +The ADIN1300 and ADIN1200 have internal protection circuitry on the MDI pins that will protect them from damage when standard ethernet traffic is sent into an unpowered device from a remote active device.
 +
 +----
 +
 +===== Do the Exposed Pad and Bus Bars have to be soldered down? =====
 +
 +The LFCSP has an exposed pad underneath the package that must be soldered to the PCB ground for electrical, mechanical and thermal reasons. For thermal impedance performance and to maximize heat removal, use of a 4 × 4 array of thermal vias beneath the exposed ground pad is recommended. 
 +
 +There are also two bus bars on either side of the exposed pad, these bus bars are connected to internal voltage rails and are **not** intended to, and should **not** be soldered to the board. The PCB land pattern must incorporate the exposed ground paddle with vias and two keep out areas around the bus bars in the footprint. No PCB traces or vias can be used in either of the keep out areas. The EVAL-ADIN1300FMCZ uses an array of 4 × 4 vias on a 0.75 mm grid arrangement, as shown in the figure below. The via pad diameter dimension is 0.02 in. (0.5015 mm) and the finished drill hole diameter is 0.01 in. (0.2489 mm). This also applies to the exposed pad and bus bars for the ADIN1200. See the ADIN1200 Datasheet for the equivalent figure relating to the different package size.
 +
 +{{ :resources:eval:user-guides:adin1300-and-adin1200:adin1300_paddle_and_keep_out_areas.png |}}
  
resources/eval/user-guides/adin1300-and-adin1200/phy_faq.1628701375.txt.gz · Last modified: 11 Aug 2021 19:02 by Catherine Redmond