Hi Jiri,
Interesting behavior. Hermeslite.py does have a reboot, but it is the same as what Quisk does. This is a full warm reboot. Information such as the fixed IP, whether to use DHCP or not, and MAC etc., are stored in a separate EEPROM so are not overwritten by rewriting the gateware. The same chip which sets the bias has some free EEPROM and that is what is used. I wonder if something with the i2c interface on that chip went awry and now requires a full cold reboot.
I assume you have checked and set fixed IP, favor DHCP, and other options the way you want? For remote settings, I usually set a default fixed IP in a subnet I like, but also set favor DHCP so DHCP will be used if available.
I'd also check your DHCP server. Maybe something failed during a DHCP renewal and your DHCP server thinks an address is assigned but the HL2 does not. Maybe you can manually remove any lease.
Regarding why any programming of the gateware now also fails, perhaps that is also related to some of the serial interfaces locking up. Gateware programming also must read/write another external EEPROM. It might also be related to the private address in use, although I haven't heard of other cases of that. Maybe you just experienced a bit flip due to the more active solar weather. :)
Please let us know what you find. There have been about a dozen cases of HL2s going in to private IP mode without the user doing anything. Usually one can reboot in factory mode and clear the use fixed IP bit. I'd like to get to the bottom of this.
73,
Steve
kf7o