-
Notifications
You must be signed in to change notification settings - Fork 14
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
ethblue/ethblack LEDs mode #17
Comments
Are you referring to the Gnubee-PC1 or the Gnubee-PC2 ?? The network LEDs seem to be wired differently. For the PC-1: The file lists possible triggers, Choose the one you want and write that name to the file. The "system" and "status" LEDs can be controlled in a similar way. |
I should have added: for the PC2, I don't think the green LAN LEDs are wired to anything. I certainly cannot find a way to drive them. |
You're right. The PC2 schematic shows the green LEDs are not connected to anything. P3:yellow is connected to the IP1001, bizzarely, its LEDs are connected to SoC GPIO/JTAG instead of IP1001 LED pins: |
Here's what I have on the PC2:
system and status control the two green LEDs next to the power switch. (you turn them on/off by setting trigger to default-on/none, brightness does nothing). lan1 and lan2 do nothing so are superfluous. Perhaps completely new LEDs for the PC2 could be named gb-pc2:lan3-orange and green that control GPIO13/15? |
I see this was discussed in https://github.com/gnubee-git/GnuBee_Docs/issues/82 |
Only the orange LED lights with Link/Act mode, regardless of speed/duplex. Usually one LED shows speed, the other Act or some combination thereof. For example: 1G: orange=link, green=act; 100M/10M: orange=off,green=link/act (this depends on what modes the chip can be set to). Is this fixable via SW/FW or is it a HW issue?
The text was updated successfully, but these errors were encountered: