Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Stabilizer v1.1] Ethernet auto-negotiation fails with PoE switch #76

Closed
ryan-summers opened this issue Jun 9, 2020 · 7 comments
Closed

Comments

@ryan-summers
Copy link

ryan-summers commented Jun 9, 2020

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.

@jordens
Copy link
Member

jordens commented Jul 15, 2020

I suspect there is a broader issue with the Ethernet PHY. I don't know whether it's hardware or software. A few observations:

  • On the Stabilizer v1.0 that I have here, originally the Ethernet PHY worked just fine and I could connect to my switch. Now the link initialization fails (with and without autonegotiation, with and without PoE). The CPU talks fine with the PHY but the registers indicate link link down most of the time and then intermittent flashes on the LEDs and very short intervals of a other values in the registers. Now that Stabilizer doesn't even want to accept PoE from the switch (a Cisco Catalyst). The switch doesn't see anything worth noting.
  • On a Stabilizer v1.1 from us that's currently with Technosystem for repair, the failure involving the hot CPU started suddenly. TS suspects a short between NRST and RMII TXD.
  • On the other Stabilizer v1.1 PoE works but the link with the Cisco switch doesn't come up either.

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

@gkasprow
Copy link
Member

I don't remember exactly, But once I replaced broken PHY on either Stabilizer or Thermostat. What's the status of this issue?

@jordens
Copy link
Member

jordens commented Oct 11, 2020

No news. Let's try gathering some data on this: @airwoodix @hartytp @nkuh have you seen anything like this?

@hartytp
Copy link
Collaborator

hartytp commented Oct 11, 2020

@jordens this is the only somewhat relevant issue I'm aware of us having seen #47

@gkasprow
Copy link
Member

Thanks for reminding me that I replaced it on Thermostat.
It's the same PHY and CPU, but they are supplied from different SMPS.

@nkuh
Copy link

nkuh commented Oct 12, 2020

No news. Let's try gathering some data on this: @airwoodix @hartytp @nkuh have you seen anything like this?

We don't use PoE.

@gkasprow
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants