Wednesday, January 26, 2005
Digi Boot Loader
The S-type Digi boot loader is not the same as the one in the NetOS source tree. Digi has not published the source but, according to Digi tech support, there are two ways to recover bad-download modules using the Digi Boot Loader:
1. Upon module power up, if the boot loader determines that the application image is missing or corrupted it attempts to retrieve a replacement image, via TFTP, using the TFTP server address of 192.168.0.128 and a filename of 82000856. I have not observed this behavior. My Ethereal shows no activity on TFTP port 69; however, there could be a problem with netmask, etc., keeping me from seeing these packets.
2. If ConnectMe pin 18 is grounded at powerup, the boot loader puts out a menu at 9600N81 on the normal serial port. The menu lets you set up IP and netmask, retrieve a file by tftp and load it to Flash. This system works, I have used it on an S-type module that I know to have had its application erased.
Notice that neither of these behaviors is described in the "The Digi CM disaster recovery procedure" which I described in my last post.
Larry Martin
www.GlueLogix.com
Copyright (c) 2005 Larry Martin. All Rights reserved.
1. Upon module power up, if the boot loader determines that the application image is missing or corrupted it attempts to retrieve a replacement image, via TFTP, using the TFTP server address of 192.168.0.128 and a filename of 82000856. I have not observed this behavior. My Ethereal shows no activity on TFTP port 69; however, there could be a problem with netmask, etc., keeping me from seeing these packets.
2. If ConnectMe pin 18 is grounded at powerup, the boot loader puts out a menu at 9600N81 on the normal serial port. The menu lets you set up IP and netmask, retrieve a file by tftp and load it to Flash. This system works, I have used it on an S-type module that I know to have had its application erased.
Notice that neither of these behaviors is described in the "The Digi CM disaster recovery procedure" which I described in my last post.
Larry Martin
www.GlueLogix.com
Copyright (c) 2005 Larry Martin. All Rights reserved.
Digi Knowledge Base
Digi has started building a ConnectMe knowledge base (KB):
http://www.digi.com/support/knowledgebase.jsp
This link:
http://www.digi.com/support/kbaseresultdetl.jsp?id=746
takes you to an article titled "The Digi CM disaster recovery procedure". I found the article by searching the KB for "boot loader", with the Product ID set for "Any". When I searched with the product ID set for "ConnectMe" the KB did not show me this article.
While I can't reprint the article here, the gist is: connect a terminal (9600N81) to the broken ConnectMe and press ESCape within 3 seconds of powerup. Then you get a recovery menu. I've heard from Digi tech support that the S-type boot loader is different from the NetOS one. So, presumably, this procedure is only for S-type ConnectMe.
Incidentally, I have tried this and it has not yet worked for me. The problem could still be me. I'll post again when I know for sure.
Larry Martin
www.GlueLogix.com
Copyright (c) 2004 Larry Martin. All Rights reserved.
http://www.digi.com/support/knowledgebase.jsp
This link:
http://www.digi.com/support/kbaseresultdetl.jsp?id=746
takes you to an article titled "The Digi CM disaster recovery procedure". I found the article by searching the KB for "boot loader", with the Product ID set for "Any". When I searched with the product ID set for "ConnectMe" the KB did not show me this article.
While I can't reprint the article here, the gist is: connect a terminal (9600N81) to the broken ConnectMe and press ESCape within 3 seconds of powerup. Then you get a recovery menu. I've heard from Digi tech support that the S-type boot loader is different from the NetOS one. So, presumably, this procedure is only for S-type ConnectMe.
Incidentally, I have tried this and it has not yet worked for me. The problem could still be me. I'll post again when I know for sure.
Larry Martin
www.GlueLogix.com
Copyright (c) 2004 Larry Martin. All Rights reserved.
