Part Number: DP83867IR
Hi,
I’m currently troubleshooting an issue during the power-up sequence of the DP83867IR, specifically related to the sampling of the PHY address strapping pins. We are using the PHY in 3-supply mode, with VDDIO at 1.8 V.
We observe two different power-on behaviors:
Working Case
Full Trace 
Power Sequence

- The 1.8 V rail ramps up and settles in ~0.5 ms.
- The 2.5 V rail begins ramping ~0.1 ms after the 1.8 V rail starts ramping (i.e., before 1.8 V has settled) and settles in ~1.5 ms.
- Both rails are stable well before reset is released (~200 ms later).
- In this case, the PHY initializes correctly with the expected address (00001).
- The RX_D0 strapping pin remains high for ~60 ms after reset release before being pulled low.
Failing Case
Full Trace

Reset

- The power rails ramp in the same order and with similar timing.
- However, reset is released much later (~2.5 s after both rails are stable).
(This delay is arbitrary; the same issue occurs for reset delays ≥ ~300 ms.) - In this case, the PHY initializes but latches the incorrect address (00000).
- Notably, RX_D0 is pulled low immediately as reset is released, even before reset reaches 1.8 V.
Debugging performed (failing case):
All observations below are consistent with the working case unless noted otherwise:
- Isolated RX_D0 from the SoC by cutting the trace between the SoC and the strapping resistors. The behavior remains unchanged, indicating the DP83867 is pulling the line low.
- Verified MDIO/MDC activity: no traffic is present prior to SoC boot, confirmed via oscilloscope.
- Checked INT/PWRDN#: remains high throughout the sequence as expected.
- Checked XO and CLK_OUT: clock is present once power rails are up, even while reset is asserted, and remains stable well before reset release.
In both cases our strapping looks as follows:

Question:
Do you have any guidance on what could cause RX_D0 to be driven low at reset release in the failing case, resulting in the incorrect strap reading?
Specifically, is there any dependency on reset timing relative to power stability that could explain this behavior?












