I would insert a USB stick with FW file on it into the device before uploading the bin file and issuing the 'go' command. Still I think the correct kernel should look for update file if it finds a usb flash
for me this is still strange and does not match what I have seen on these meters. Maybe I am wrong but I have many logs of different meters and none
shows up like this. I mean first it says phy not found and then it shows link detected and 100Mb/sec even though no cable is connected
this is not some internal ethernet communication. this is exactly for the LAN connection.
Phy not found
WaitForLink Start (ticks=3751)
Link Detected (ticks=3753)
GMAC Init : 100 Mbit/s FULL DUPLEX (MII)
Flushed Transmit Buffer
phyCfg->dwSpeed 0x64
<--EDeviceInitialize
it could be that dll files of the WInCE are corrupted as well. The next message you will see after the last line of your log is about loading some dll files.
of course there could be some other stuff going on in between which we are not aware of but as far as the UART messages are concerned the next message is about some dll files. If that's the case we need to force the unit to boot the wince from usb (just like in the keysight 3000A scopes) and thus take the dlls from there
i dont know how it can be done but it must be similar to keysight infiniivision scopes.
still I think a hardware issue is the more likely problem. if you got the cpu from aliexpress, be ready to exchange it again as I had to a couple of times.
also maybe probing around that LAN chip could be useful too