Do I need to update the new software? Version 1.9.1?Glad to hear that.
Read the Documentation of the RTLPLayground firmware in the link I've provided, navigate to 192.168.10.247 (for this you have to change your network settings), adjust the IP to your network settiings, and just be happy.

I am a translator. Can I translate the software into Polish?RTLPlayground is an open source alternative firmware, it has nothing to do with the OEM firmware.
As I wrote before, there are multiple cases of SWGTW218AS switches which "die" after one or 2 years, because the access to the flash doesn't work reliably with OEM firmware. RTLPlayground uses a more reliable method.
I understand that I will never be able to return to the original software on this device, but must use this software?Please read the documentation. It's all there.
![]()
GitHub - logicog/RTLPlayground: A Playground for Firmware development for RTL8372/RTL8373 based 2.5GBit Switches
A Playground for Firmware development for RTL8372/RTL8373 based 2.5GBit Switches - logicog/RTLPlaygroundgithub.com
Well, you can reflash the OEM firmware again with your programmer, but if this OEM firmware doesn't work, it makes no sense.I understand that I will never be able to return to the original software on this device, but must use this software?
If the flash chip degradation is the root-cause, it will likely solve the problem (for another year or two).If I desolder the M25Q16A chip and replace it with a brand-new one of the same type, would that solve the issue?
Check also this guide:If I desolder the M25Q16A chip and replace it with a brand-new one of the same type, would that solve the issue? Would I then be able to install the original manufacturer firmware without problems?
Nope. This image kills my switchJust a remark - V200.1.10 dump is firmware to be used for update via web interface.
==========Loader start V0.2===========
Press any key to start the normal procedure.
To run SPI flash viewer, press [v]
To enforce the download of the runtime kernel, press [ESC] .....
cmd -1
Check Runtime Image.....
Chksum Correct!
RunTime Kernel Starting....
=============== Try to detect the PSE ===============
=============== PSE IC Existed Result:39 ===============
=============== PSE IC ChipSet Result:A ===============
=============== PSE IC Type: RTL8239 ===============
Ver8372N=2
Ver8373N=2
NSQ=1 RXIDLE=0 SYNC_OK Rx reset!
LINE 1462, RL6818C_pwr_on_patch_phy_v007 , patch 0xf finished!
LINE 1462, RL6818C_pwr_on_patch_phy_v007 , patch 0xf0 finished!
=============== Init PSE Starts ===============
PSE Step0: Reset the whole PSE Chip.
rtk_pse_wholechip_reset1
rtk_pse_wholechip_reset2
PSE Step1: Disable all the PSE ports.
address: 0x20 pse_init regVal=fff0000
address: 0x21 pse_init regVal=fff0000
address: 0x20 pse_init regVal=fff0000
address: 0x20 pse_init regVal=fff0000
=================================
PSE Step2: Begin to load PSE image.
load 8238B pse image
load ok...
=============== Init PSE Ends ===============
===========================Config Area pre-check Starts.=====================.
Pre-Check the config size structure is equal or not.
It seems no risk!..................
==============================Config Area pre-check ends.===================.
SalFlshCopyFlshToCache()
sal_sys_config_restore()
Restore dhcp state is: 0
Restore ip is: 192.168.11.21
...OK
sal_mirror_config_restore()...OK
sal_qos_config_restore()...OK
sal_vlan_config_restore()...OK
sal_rate_config_restore()...OK
sal_trunk_config_restore()...OK
sal_l2_config_restore()...OK
sal_loop_config_restore()...OK
sal_eee_config_restore()...OK
sal_stp_config_restore()...OK
sal_igmp_config_restore()...OK
sal_dhcp_snooping_config_restore()...OK
sal_port_config_restore()...OK
sal_poe_config_restore()...OK
NSQ=1 RXIDLE=0 SYNC_OK Rx reset!
################################################################
############Login Menu ############
### Please input uboot password below: ###
NSQ=1 RXIDLE=0 SYNC_OK Rx reset!
NSQ=1 RXIDLE=0 SYNC_OK Rx reset!
NSQ=1 RXIDLE=0 SYNC_OK Rx reset!
NSQ=1 RXIDLE=0 SYNC_OK Rx reset!
NSQ=1 RXIDLE=0 SYNC_OK Rx reset!
NSQ=1 RXIDLE=0 SYNC_OK Rx reset!
NSQ=1 RXIDLE=0 SYNC_OK Rx reset!
NSQ=1 RXIDLE=0 SYNC_OK Rx reset!
NSQ=1 RXIDLE=0 SYNC_OK Rx reset!
NSQ=1 RXIDLE=0 SYNC_OK Rx reset!
NSQ=1 RXIDLE=0 SYNC_OK Rx reset!
NSQ=1 RXIDLE=0 SYNC_OK Rx reset!
NSQ=1 RXIDLE=0 SYNC_OK Rx reset!
NSQ=1 RXIDLE=0 SYNC_OK Rx reset!
NSQ=1 RXIDLE=0 SYNC_OK Rx reset!
NSQ=1 RXIDLE=0 SYNC_OK Rx reset!
NSQ=1 RXIDLE=0 SYNC_OK Rx reset!
NSQ=1 RXIDLE=0 SYNC_OK Rx reset!
NSQ=1 RXIDLE=0 SYNC_OK Rx reset!
NSQ=1 RXIDLE=0 SYNC_OK Rx reset!
NSQ=1 RXIDLE=0 SYNC_OK Rx reset!
NSQ=1 RXIDLE=0 SYNC_OK Rx reset!
NSQ=1 RXIDLE=0 SYNC_OK Rx reset!
NSQ=1 RXIDLE=0 SYNC_OK Rx reset!
NSQ=1 RXIDLE=0 SYNC_OK Rx reset!
NSQ=1 RXIDLE=0 SYNC_OK Rx reset!
NSQ=1 RXIDLE=0 SYNC_OK Rx reset!
[/QUTE]
Devices with Firmware 1.9.x, 100.9.x and 200.x.x are all incompatible with each other.After upgrading via web from V100.9.6 up to V200.1.10
Yes, seems so. I already have some statisticsDevices with Firmware 1.9.x, 100.9.x and 200.x.x are all incompatible with each other.

