Part Number: DP83826E
Hello,
We're trying to get a connection with Ethernet but we can't seem to get it to work.
We have been able to get a connection to the PHY but we aren't able to get a connection to the Ethernet port.
The PHY is working in BASIC mode, RMII Master mode & Auto Negotiation Enable.
Under here you can see the schematic.
Does anyone know what we might be doing wrong?
Hello Gerome,
We are able to read out the registers but the auto-negotiation doesn't seem to work.
Yes, we are using a mag-jack.
I changed the schematic to be up to date with some modifications we did but I see i made a mistake while doing this. I updated the schematic. Is this what you were talking about for the wrong capacitors? Or do you mean that the value is wrong?
On de ETH_MDIO net i do see a couple of signals at starting up but nothing after that. On the ETH_RXD0 and ETH_RXD1 I don't see any signals.
Hello Gerome,
The ethernet cable is plugged in. It is connected to an prosafe 24 port gigabit switch with is connected to our network.
The driver was originally meant for the DP83848 but my colleague this shouldn't matter to much because the registers from both PHY's should be the same. We are also not changing much in the registers.
We do have a clock signal.
Hello Gerome,
We've tried this but it doesn't seem to help.
We have also tried to configure the print so the ESP32 sends an clock to the PHY which also didn't seem to work but we did notice by accident that if we load the firmware for the print without a crystal onto a print witch a crystal it eventually does get an (unreliable) Ethernet connection. My ques is that the clock the ESP32 is making sometimes lines up with the clock of the PHY so it can communicate for a short while. This means there is a problem in the clock signal. The clock signal looks fine to me. Could the problem maybe be a phase change? And is there a way to shift the phase?
Best Regards,
Ramon
Hello Gerome,
Sorry, print is an other word for PCB in Dutch. This might not be something in English.
The way the PCB is set up to make it sort of work is that the PHY is using a 25MHz crystal as it's clock. It is configured an Master so it sends out a 50MHz signal to the ESP32. The ESP32 has firmware loaded on it so it is not listening to the 50MHz signal from the PHY and making its own 50MHz signal. This firmware was meant to be put on a PCB that had the PHY configured in slave mode but i loaded it on the wrong PCB. This way we were able to get an Ethernet IP response. The PCB with the PHY in slave mode also didn't work.
For the crystal we are using the ECS-250-10-37B-CTN-TR. I believe this complies with al the requirements.
Best regards,
Ramon
