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.
We develop an IoT gateway based on ESP32 + DP83848J as PHY for ehternet. The PHY is working properly getting the link when connected to a 100 Mbps switch. If we directly connect the Ethernet to a modem router (or some switches) it does not get the link. We already tried to fix the PHY speed and duplex mode, and disabling autonegotiation.
In this case we get the link with most of the routers (only at 10 Mbps) but then the ARP messages result corrupted and we are not able to properly get the IP from the router.
We produced 10 devices and not all of them show the same problem with the same network device (router/switches).
We made several tests and the strapping is OK, Voltages on PFB and RBIAS are OK.
Can someone give us some guidance how to proceed?
Thanks a lot
Hi Matteo,
Thank you for reposting this in a new thread. For personal reference, I will link your previous thread here: https://e2e.ti.com/support/interface-group/interface/f/interface-forum/1224989/dp83848j-not-getting-link-when-connected-to-a-router-most-times-with-a-100-mbps-switch-it-properly-works
I have a few tests for you to try:
- Could you provide a scope shot of your MDI signal? The fact that lower data rates are able to link make me wonder if the issue lies in the quality of the signal. There are instructions for how to do this in this app note in section 3.4.7: https://www.ti.com/lit/an/snla246b/snla246b.pdf?ts=1692927342776&ref_url=https%253A%252F%252Fwww.google.com%252F
- Could you also try the following test:
Additionally, what do you mean by the ARP messages are corrupted? What do the corrupted messages look like compared to the original messages?
Best regards,
Melissa
We finally found the problem in the ethernet connector, by changing this component all the devices became working.
Thanks a lot for the support
Hi Matteo,
I'm glad to hear it works now! Would you be able to elaborate on the connector issue? Was it a specific part number that does not work with our device? What is the new part number?
Best regards,
Melissa