ECOM 100 failed during firmware update

[sclrick]

I was updating the firmware on a H2-ECOM100 and the update ended with an error,  I did not note the error but now I cannot access the module.  The error light is flashing 2 blinks pause 2 blinks...  I spoke with AD and their tech support recommended setting dip switch 6 and cycling power.  That did not correct the issue.  Any ideas how to get the module back online?

[BobO]

If the leds are flashing, then at the very least it is running the bootloader and isn't bricked. Need to get you talking to a support guy here at Host...

[Greg]

I was updating the firmware on a H2-ECOM100 and the update ended with an error,  I did not note the error but now I cannot access the module.  The error light is flashing 2 blinks pause 2 blinks...  I spoke with AD and their tech support recommended setting dip switch 6 and cycling power.  That did not correct the issue.  Any ideas how to get the module back online?

That particular pattern of flashing lights just means the H2-ECOM100 is "stuck in the booter" because it cannot find a valid copy of firmware to run (obviously because it failed during the update attempt).

The first thing to try is in NetEdit3 (which doesn't show your H2-ECOM100), try Network --> Adapter, and pick your PC's NIC directly instead of the default. If that doesn't work...

...then one of the easiest ways to get it back is to use a utility in DS Launch to write a new IP address to it. It is called "IPConfig" and is located under the "Utilities" folder in DS Launch. Double-clicking on this will bring it up.

1. At the bottom, select your PC's NIC (this helps set the Subnet Mask)
2. Enter your H2-ECOM100's MAC address (printed on the label)
3. Enter the IP Address you want your H2-ECOM100 to have (make sure this new IP address is on your PC's same logical network)
4. Press the <Write> button. You should get, "Cool! Found device!"

Now use NetEdit3 again, to see if you can see the module. Most of the time you can. Then simply attempt the firmware update again.

[sclrick]

I found an answer.  I used an old XP notebook and NetEdit connected through IPX.  Updated the firmware and the module is working fine now.  Thanks for the reply's.