Another EZServe bricked by 2.01 upgrade 2009-07-03T06:40:31+00:00

HOME Forums Gateways EZSrve Another EZServe bricked by 2.01 upgrade

Viewing 15 posts - 1 through 15 (of 20 total)
  • Author
    Posts
  • Anonymous
    Post count: 84
    #40184 |

    Set unit to DHCP
    Reset device (via web interface)
    Verifed I could still talk to unit – web interface worked but now empty of devices
    Used JAVA discovery tool to do upgrade from 1.59 to 2.01
    This appeared to work but after 15 mins no access. Both yellow / green status lights solid
    Used TFTP and reset approach to reload image.bin file for 2.01
    TFTP server status window showed file was uploaded
    Still no access to EZServe


    Used TFTP to upload older image (1.59) – SUCCESS


    Used JAVA tool to ugrade to 2.01 – FAILED


    Used TFTP to upload 1.59 again – SUCCESS

    Any ideas or is my EZServe (bought Jan 2008) – is it possible that my unit is actually not compatible with version 2.01 – it’s close to the Dec 2008 cut off.

    Thanks

    Peter

    Anonymous
    Post count: 1001

    Did you download the latest 1.1 version (not the withdrawn v2 version) of the Java Discovery Tool? Did you try using TFTP server to upload 2.1 image.bin?

    Anonymous
    Post count: 84

    Downloaded JAVA tool direct from download page so yes

    Did I try V2.01 via TFTP – Yes – didn’t work either

    Anonymous
    Post count: 1001

    The same TFTP server that loaded 1.59 successfully did not load the 2.01 image or did load the image but EZSrve was not functional. If the TFTP image load 0f 2.01 was successful does the router eventually assign a DHCP IP address to it.

    Anonymous
    Post count: 84

    The TFTP service uploaded V2.01 however the EZServe was non functional afterwards (green and yellow lights solid on).

    Anonymous
    Post count: 7

    ….And we have yet another brick.

    I followed the same procedures as vaughanp and produced the same “Easy-brick” result but with two differences.
    1. In each attempt to recover using TFTP, after ~15 seconds, my yellow and green leds behaved normally. i.e. They were not solid ON. (I still could not communicate with the EZServe web page)
    2. In my first attempt to TFTP back to Ver. 1.6, I was successful but now, the TFTP download appears to complete normally but I can’t get to the web page and the java tool cannot find the EZserve. Again, my green and yellow leds are behaving normally after the image load.

    The unit worked prior to my upgrade attempts and I downloaded the image and java tools from the SHN site this morning so I think these are the correct versions.
    My unit was purchased ~ Jan 2008. There is no version indication on the case of the unit.

    Is there anything else I can do to try and recover this unit?

    Thanks

    Anonymous
    Post count: 1001

    The fact that you cannot get back to 1.60 using TFTP makes me think there is something else that we do not understand as yet. You have turned off all the firewalls, you are using SolarWinds TFTP and the log window says the upload of the image started and was complete successfully. I could not connect to my EZBridge after doing the process but my router had assigned .125 as the DHCP assigned IP address rather than the one it had always been assigning to the EZBridge. Yet to understand why that is but I have a running 2.0 (now 2.1) using .125.

    I can confirm that the 1.1 version of the Discovery tool does find 1.60, 2.0 and 2.1 successfully so I’m thinking something is not right with the upload process or the DHCP IP assignment process or you would be able to go back to 1.60. Try going through the process again, being sure all firewalls are off, you are using SolarWinds TFTP and that the upload start and complete messages are displayed in the SolarWinds window. Also that the router is handing out IP addresses to devices in DHCP mode.

    Anonymous
    Post count: 55

    Can you see the device on the network after the TFTP (ie does ARP -a from a command window show the EZServe?). If yes, can you successfully ping the IP address?

    You might try a hard reset AFTER the 1.60 TFTP recover. I had a similar but not identical problem where the FLASH0/data directory contained both 1.60 and 2.01 xml files. A hard reset solved that problem.

    Anonymous
    Post count: 7

    Success! Thank You for your help and suggestions!

    I followed SCSweet’s advice and performed a “hard reset” and this was all that it took to again be able to connect to my V2.01 EZServe. I thought that a reset was part of the image file installation. Apparently, the system sometimes needs this extra “hard reset” to get going after a software change.

    Regards,

    Greg

    Anonymous
    Post count: 1001

    Great news that 2.1 is running. Will one of you please document what you are doing to “hard reset” EZSrve. I think it would be useful information for others who follow.

    EDIT: also where in the sequence of steps was the Hard Reset done. Thanks

    Anonymous
    Post count: 55

    @grif091 wrote:

    Great news that 2.1 is running. Will one of you please document what you are doing to “hard reset” EZSrve. I think it would be useful information for others who follow.

    EDIT: also where in the sequence of steps was the Hard Reset done. Thanks

    Glad my experience proved useful for someone else. What I meant by “hard reset” is the step described in the TFTP instrucions without the power cycle: “using a blunt, narrow tip (a thick paper clip will do), depress the recessed reset button on the EZSrve”

    So the sequence of events (for me) was:
    1) EZServe became non-responsive at 2.01, attempts to recover via TFTP to 1.60 then upgrade to 2.01 fail, noted that FLASH0/data contains both sets of xml files.
    2) TFTP recovery using 1.60 image.bin, network functionality recovered (i.e. amber LED on / green LED intermittenly flashes, web interface works)
    3) Hard reset as described above (I’ve tended to leave the reset button depressed until the amber LED goes out, but that doesn’t always happen). NOTE: reset via the web interface doesn’t clear the 2.01 xml files.
    4) Using the web interface, verify that only the default 1.60 xml files are present (I’ve found that if I’ve loaded xml files with data and don’t do a reset, upgrade to 2.01 consistently bricks the EZSrve)
    5) Upgrade to 2.01 using Discovery tool v1.1

    Hope that helps.

    Anonymous
    Post count: 84

    Can you tell me how to tell if my XML files are correct. I tried the hard reset method but same problem – both LEDs on after V2.01 but 1.60 works fine.

    Thanks

    Peter

    Anonymous
    Post count: 55

    The files in 1.60 are:
    devices3.xml
    scenes.xml
    timers3.xml
    zone.xml
    macros3.xml

    The files in 2.01 are:
    devices.xml
    holidays.xml
    actions.xml
    areas.xml
    devclusters.xml

    Anonymous
    Post count: 84

    Thanks – I’m running 1.6 and only 1.6 files are showing. I’ll try hard reset followed by TFTP upgrade to 2.01 tonite and post results – if no joy then I’m sticking with V1.60 until I get a call back from Al at Simplehomenet.

    Anonymous
    Post count: 55

    @vaughanp wrote:

    Thanks – I’m running 1.6 and only 1.6 files are showing. I’ll try hard reset followed by TFTP upgrade to 2.01 tonite and post results – if no joy then I’m sticking with V1.60 until I get a call back from Al at Simplehomenet.

    If you have the EZSrve running at 1.60 with only the default 1.60 files showing in the file list (i.e. no devices or anything else added), you should be able to upgrade to 2.01 using the Discovery 1.1 utility. IIRC, TFTP doesn’t load devclusters.xml so you would need to do that manually if you go the TFTP route.

    Good luck.

Viewing 15 posts - 1 through 15 (of 20 total)
  • You must be logged in to reply to this topic.