mirror of
https://github.com/logicog/RTLPlayground.git
synced 2026-10-29 17:54:14 +08:00
Victor
389dc2af76
The hongyavision HYWS-SGT0204S is sold as an unmanaged 4x2.5G + 2x10G SFP+ switch and carries the 2G5F4_10G2_V1.01 marking on the PCB. It is a sibling of the KP-9000-6XH-X2 (2M-PCB43-V1.1), so machine/2G5F4_10G2_V1_01.c is that board definition with these changes: - The two SFP+ cages (physical ports 5 and 6) are wired the other way round: physical 5 is on SDS1 with GPIO30/GPIO37, physical 6 on SDS0 with GPIO50/GPIO10. Copper ports 1-4 match the KP-9000 layout. - No reset button is fitted and the case has no opening for one, so reset_pin is GPIO_NA. GPIO54, the reset pin on the KP-9000 layout, reads as permanently pressed here. - The board definition sets flash_sio, so the flash is read with single-IO: the fitted 512 KB Bright Moon T25S40 cannot be read in DIO mode on this board, an image that leaves DIO enabled does not come up at all, while the same image with single-IO boots and runs normally (two units). - The board is added to the machine_custom_init() group that sets LED_GLB_IO_EN bit 6, otherwise the RTL837x "solid" conditions (LINK/speed) never drive the LEDs and the 2.5G LED glows faintly at 100M/1000M. flash_sio is a new field of struct machine that rtlplayground.c hands to flash_init(); only this board sets it, every other machine keeps DIO. It costs management-plane speed only, the ASIC keeps forwarding in hardware. The stock firmware runs a factory test console on the serial header at 9600 baud, whose silkscreen labels are shifted by one pin. Verified: warning-free build, `make machine_check` passes for every target, the host tests pass, and a control build of this target without the LED hook differs from the KP-9000-6XH_X2_V1_1 image in 44 bytes: all inside the machine description (including flash_sio) and the image CRC16, nothing else in the firmware moved. On the board the single-IO image boots and runs on two units; port order, SFP cages and LED behaviour come from the machine definition verified on this board earlier.
48 lines
1.9 KiB
Markdown
48 lines
1.9 KiB
Markdown
# Change Log
|
|
|
|
## [0.x] - 2026-xx-XX
|
|
|
|
## Added
|
|
|
|
- Devices
|
|
- Support the hongyavision HYWS-SGT0204S (PCB marking `2G5F4_10G2_V1.01`), an
|
|
RTL8372 based 4x2.5G + 2xSFP+ unmanaged switch with a 512 KB Bright Moon
|
|
`T25S40` flash. It is a sibling of the KP-9000-6XH-X2 (2M-PCB43-V1.1) with
|
|
the two SFP+ cages wired the other way round (physical 5 is on SDS1,
|
|
physical 6 on SDS0), no reset button fitted, wrong silkscreen labels on the
|
|
serial header, `LED_GLB_IO_EN` bit 6 has to be set for the port LEDs to
|
|
work, and the fitted T25S40 cannot be read in DIO mode on this board, so the
|
|
target selects single-IO flash reads (`flash_sio`). New machine target
|
|
`MACHINE_2G5F4_10G2_V1_01`, see `doc/devices/2G5F4_10G2_V1.01.md`.
|
|
|
|
- Web UI
|
|
- Compress the embedded assets (minify + gzip) and switch to a single-page layout. #315
|
|
- Replace the multi-page UI with a themed single-page app: light, dark and Selenized themes following the browser by default,
|
|
English, Japanese and Chinese, save to flash merges the command log into the startup config and verifies the write,
|
|
firmware images are checked in the browser before upload. #429
|
|
|
|
## Changed
|
|
|
|
## Fixed
|
|
|
|
- Config
|
|
- A startup configuration line longer than the command buffer no longer stops the replay:
|
|
the offending line is skipped and the following lines are still applied.
|
|
- The web UI and the configuration upload now refuse a line the replay cannot take,
|
|
instead of writing it to flash.
|
|
|
|
## Breaking changes
|
|
|
|
- Config
|
|
- VLAN don't accept port `u`-suffix anymore.
|
|
So `vlan 1 4u` is not valid anymore.
|
|
Replace it with `vlan 1 4`.
|
|
- Commands
|
|
- port zero/`0` is treated as the `CPU_PORT`. #326
|
|
- Many commands don't accept the CPU_PORT anymore. See #334.
|
|
When the CPU_PORT is needed, the command/service will add the CPU_PORT automaticly.
|
|
Only `isolate` accept the CPU_PORT as destination port.
|
|
|
|
## [v0.1_aplha] - 2025-11-03
|
|
|
|
First release. |