Closed ryan-summers closed 3 years ago
I suspect there is a broader issue with the Ethernet PHY. I don't know whether it's hardware or software. A few observations:
I tried poking around a bit on the v1.0 board and probing a few things but didn't see anything that caught my eye.
@gkasprow
I don't remember exactly, But once I replaced broken PHY on either Stabilizer or Thermostat. What's the status of this issue?
No news. Let's try gathering some data on this: @airwoodix @hartytp @nkuh have you seen anything like this?
@jordens this is the only somewhat relevant issue I'm aware of us having seen https://github.com/sinara-hw/Stabilizer/issues/47
Thanks for reminding me that I replaced it on Thermostat. It's the same PHY and CPU, but they are supplied from different SMPS.
No news. Let's try gathering some data on this: @airwoodix @hartytp @nkuh have you seen anything like this?
We don't use PoE.
the same PoE circuit is used in Thermostat design. I tested it with Netgear GS305P and it works fine. The Stabilizer I have has broken PoE circuit - there is an internal short circuit that is hard to locate. The other v1.1 boards may have a similar issue with shorted traces. I think we cannot do much here.
When connecting the Stabilizer v1.1 ethernet port to a Netgear GS305P PoE ethernet switch, the auto-negotiation phase of the ethernet connection never completes. This phase is entirely managed by the LAN8942A PHY, so it is assumed this failure is due to signaling issues on the ethernet pair. Indication of the failure to complete is denoted by the PHY basic status register never indicating a complete auto-negotiation as well as the LED on the RJ45 housing.
When the ethernet cable is then disconnected from GS503P and reconnected to a D-Link DGS-1005D ethernet switch (not PoE), the green and orange link LEDs on the RJ45 housing illuminate, which indicates a 100Mbps connection has been established.