crashed digi, forgotten bootimage

hi

i tried to update the firmware of a DigiOne IAP.

after download the 82000770_F.bin file it was no problem to update my digi.

the digi doesent start now. (Sure after i read this:
NOTE: When upgrading the EOS firmware, you MUST upgrade to the latest POST image FIRST, then reboot before upgrading the EOS or your unit may stop functioning.)

its possible to install the bootloader additional?
when its possible… HOW???

thx
greets from switzerland

Digi tech support has a 3 page “recovery” guide - it takes a bit of dexterity since it involves hitting a key sequence in the serial port while a certain RED LED pattern blinks on boot up. This breaks into the POST/BIOS (ie: like the BIOS config on a PC). From here you can reload the older “D1” firmware & thus recover to upgrade the BIOS and then reload the “F”.

The issue is the “E” (& thus E1 & F) compressed firmware image crossed the 1MB boundary in size and the writers of the old POST didn’t handle such a size gracefully when decompressing (it overwrites the end of the image in RAM).

Best to email me (lynnl at Digi.com) and I can send the document and “D1” - or contact tech support and they can supply.

Hmm, I see I can attach files - what will this computer folks think of next, eh?

i do the steps in the pdf explained.

BUT the crashed digi wont bring the menu.

i take hyperterminal press ctrl+pause (so i think thats means with reset) i hold down the buttons and press one time the v key.

wait more than 60 seconds but the digi wont do anything.
the leds (from left to the right) Power DIAG DTR DSR DCD light always. when i press a key tx lights also… so im sure i have connection to the digi.

when i want to do this try on a fine works digi the hyperterminal shows some every second a point (…) but i never see a menu…

The pumpkin TFTP is a nice little Windows freeware TFTP client and server. No need to install, just unpack so I find it ideal to carry on my USB stick to use for PC-to-PC transfers. It only handles 32MB or 64MB (depends on how the peer reacts to 16-bit seq number roll-over). The server nicely shows access & status.

If you are comfortable with the telnet interface to DOIAP, check out the “show config” command. The DOIAP can even be setup to boot via TFTP server. I use this while testing new builds since then I just need to update the TFTP server image & reboot all DOIAP to run a new image. You’ll also find the “show boot” command far easier/faster to reflash DOIAP via TFTP than use of the Web UI.