-
Notifications
You must be signed in to change notification settings - Fork 10
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
Investigate feasibility of supporting RTL8238B-based protocol #25
Comments
Anything useful to be found in the GS1900-24EP code archive? |
Thank you! I found some headers and a kernel module with no corresponding source code:
|
Fwiw, I requested GPL compliance from Engenius. |
@RussellSenior, I've started a branch to test out the new dialect: https://github.com/Hurricos/realtek-poe/commits/mrnuke-what-did-realtek-do-now Feel free to give it a try (though don't expect it to work just yet). To test individual commands, you may use
I only recommend sending commands listed in #25 (comment). The BCM dialect has some "erase firmware" commands, and we don't know if the new one does too. |
I have a bunch of GS1900 10HP v2s which appear to use this, happy to give access or test anything if we can get it working! POE delivers power, MCU info and consumption for individual ports sometimes works but otherwise nothing works including status and enabling/disabling poe:
|
@jwh , @RussellSenior, please see the artifacts in #35, and report with results. No need for complete debug output, just |
@mrnuke , I have a Zyxel GS1900-24HPv2 which probably speaks the realtek dialect as well. It has a Nuvoton microcontroller for PoE management. I'm willing to test this, but I'm unsure which snapshot or release the downloadable artifacts are built against. Currently the switch is running OpenWrt 23.05.2, but I can upgrade to SNAPSHOT for testing purposes. Getting backport packages for the 23.05 series would be nice once this is sufficiently tested.
|
I think I've seen this before. Does |
Zyxel GS1900-24HPv2 with the artifacts mentioned above.
Enabling the debug log results in:
|
Installing latest OpenWrt snapshot worked. |
During further testing on the Zyxel GS1900-24HPv2 I am unable to get PoE delivered to any port. Anything else I can try? |
Try If that doesn't work, restart realtek-poe. |
realtek-log-boot.txt Test sequence:
|
@mrnuke anything else I can try? |
@hailfinger, I pushed my latest devel code. I don't think that will change anything, as the command sequence didn't change much. If that doesn't work, I might need a serial port capture from the vendor firmware. EDIT: There's no need to run |
FWIW it seems that the same dialect is used on Zyxel GS1900 8HP (v3)
Logs seem to come in bursts (and every burst is ended with the error message above). Click for the full log!
Built on Still, being able to at least get the firmware version and mcu in
Unfortunately no devices obtained power over PoE. I am away from the device ATM and can't play with the manual plugging-in I'd be happy to help anything and provide more info if you point me in some direction. On a side note, when I initially turn on the device it powers all devices over PoE just fine (without any control from OpenWRT I presume), but after some time it randomly reboots and the PoE power gets cut off as part of that. |
To follow this ticket. |
On zyxel gs1900-10hp with OpenWrt SNAPSHOT, r28410-a85059438f2c and realtek-poe-0~c49e44d3-r2 (i.e. built from realtek-poe commit c49e44d, aka current branch mrnuke-rtl8238b-devel):
Port 4 is requesting power, but not getting it. |
Trying realtek-poe commit 12fec5d on a GS1900-10HP v2.
|
How to test toggling power to an individual port? These seem to work:
Although I still get a message: "Command failed: Parsing message data failed" |
That should be fixed by #49 |
Introduction
The first PoE solution for RTL83xx switches was based on the BCM59111 family of chips. A later solution was implemented by Realtek, using the RTL8238B. realtek-poe speaks the dialect used on the former. IT does not appear to be compatible with the latter.
Instigate the feasibility of implementing the realtek dialect in realtek-poe.
Nomenclature
Techical details
Frame format
Both dialects implement a 12-byte frame format, originally documented by @svanheule [1] :
Command IDs
The realtek dialect appears to implement completely new command IDs, simply using IDs not implemented in the briadcom dialect. Some commands map between dialects, albeit with a different ID
Example of an equivalent command:
Broadcom dialect:
Realtek dialect:
Command Equivalency tables
(1) The
consumed_power
is incorrect, and shows a sum of allocated power for all ports, not actual overall power consumption.(2) The
get port overview
command only appears to work on Engenius switches. This is true for both broadcom and realtek dialects.Command
50
(2a
in BCM) appears to be specific to eother EnGenius or 8-port switches. Other switches do not support it and return error 0x61.References
[1] https://svanheule.net/switches/software/broadcom_poe_control_protocol#serial_control_protocol
[2] https://svanheule.net/switches/gpl_source_drops
The text was updated successfully, but these errors were encountered: