I am using your tftpd.exe under Win XP.
IP of the Win XP machine is 192.168.1.111
Have allowed the XP firewall when asked.
And have put the POST file in the same directory as the tftpd.
Same thing, just keeps Loop resetting after reboot.
.-.-.
#> boot load=192.168.1.111:82000684_U3.bin
Downloading 82000684_U3.bin
D+
Using Factory FEP as backup.
Erasing Flash.
Storing into Flash.
Download complete.
+
Verifying image in flash.
User FEP will be used next reboot.
Firmware appears valid and will be run on next boot.
One of the “F” Hardware models had a new enough POST firmware to flash the EOS Firmware with out updating the POST first. So I thought I would give this a go!.
And it worked.
SO I now suspect the 82000685_G POST firmware from the Digi site to have a bug in it with regards to these earlier revisions in hardware (“F”&“G”).
I then also updated the POST firmware via the WEB interface to the current “G” post and the device recovered after reboot.
If someone can supply me the “F” version POST I should be able to recover the other two TS-8’s to the latest firmware revisions using the same technique.
However I suggest that the “G” POST firmware definitely needs looking into.
#> show version
PortServer TS 8(55000944-01):
Component Part-Number Release-Tag
Boot/Post 82000685 release_82000685_F
Running EOS 82000684 release_82000684_E
#>
#>
#>
#> boot load=192.168.1.111:82000684_U3.bin
Downloading 82000684_U3.bin
+
Using Factory FEP as backup.
Erasing Flash.
Storing into Flash.
Download complete.
+
Verifying image in flash.
User FEP will be used next reboot.
Firmware appears valid and will be run on next boot.
#> boot action=reset
rebooting…
>>> Then Updated EOS Firmware Via the WEB interface <<
#> show version
PortServer TS 8:
Component Part-Number Release-Tag
Boot/Post 82000685 release_82000685_G
Running EOS 82000684 release_82000684_U3
I found the Digi FTP was open and I could access all previous firmware releases.
After pulling an all nighter I have managed to flash upgrade all but one of the “F” hardware model TS8’s.
The last “F” model will only flash up to.
Firmware: Version 82000684_H 10/09/2003
POST: 82000685_G 02/02/2006
After this point trying to flash any higher EOS file into the unit only causes it to loop power cycle.
Is there a CLI command for wiping the Flash memory clean, and or possibly checking the flash as well?
I have never come across these sorts of issues with any of the TS3/4’s in the past.
TS8 “F” & “G” hardware revisions have been very dodgie with regards to flashing firmware updates.
I really doubt their reliability as I had to flash with backdated POST firmwares to get the latest EOS firmware to take before then upgrading the POST firmware to the latest.
OK, Thanks for the firmware link. But as mentioned in previous posts, I have already found this and have tried older firmware.
I have also now tried the suggested procedure of logging in via the 1st serial port using a null modem cable to effect the flash upgrades.
As I suspected this made no difference.
The issue is with flashing these two units. Not the method used to flash them.
Both units have had their POST firmware updated to release_82000685_G
Both units contain release_82000684_E EOS firmware in their internal ROM when hard reset.
When trying to upgrade the EOS firmware to 82000684_U3
The “G” hardware revision says “Not enough room in Flash.”
The “F” hardware revision accepts the flash, reboots, but then stays in a never ending reboot cycle until a hard reset is done at which point it reverts back to the the original 82000684_E ROM stored firmware.
I myself believe the flash memory needs an erase fill and or possibly a software test procedure done.
Does anyone know what the commands or procedures are for this?
Also is there any way to get a these units to log to the screen while booting so we can see what’s going on? Or perhaps put the error reporting into a more verbose mode.
