Other Parts Discussed in Thread: DP83869
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hi Dominik,
Please have a look at DP83869 checklist. When PHY is not coming up, is link not able to be detected via LED or link partner? If you scope out MDC/MDIO lines, is MDIO not responding once controller relinquishes control of line?
DP83869_Schematic_Design_Review_Checklist.xlsx
Sincerely,
Gerome
Hi Gerome,
We have worked through the checklist and we fulfill everything.
When PHY is not coming up, there is no link and no acknowledge from PHY.
Please answer my questions.
Sincerely,
Dominik
Hi Dominik,
Can you please share schematic? I would like to take a look at a few things.
Reg 0x3 = 0xA0F1 indicates this is previous silicon. Please see revision history relating to bug fix to understand what has been corrected in 0xA0F3 devices. In short, if you are not using fiber support, the PHY should act the same between the revisions.
Please ignore Supplymode_Sel guidance. This is typo in datasheet and we will look to correct for it in next update. There shouldn't be anything connected to pin 23 unless using JTAG functionality.
Sincerely,
Gerome
Hi Gerome,
We don't have any information about silicon revision history.
The attachment contains the Ethernet Phy schematic.
Sincerely,
Dominik
Hi Dominik,
Please give me until EoD Thursday to get back to you with my feedback. I do hope to get back sooner.
Sincerely,
Gerome
Hi Dominik,
It appears that strapping is saying that PHY may be in JTAG mode if timing may be off on FPGA. Is it possible that this is causing issue? Can you place PHY into RGMII to copper mode where GPIO_1, RX_D2, RX_D3 are all mode 0 instead of mode 1? Do you see same problem statement?
Sincerely,
Gerome