F D C 3 3 0 2 U s e r M a n u a l
26
A P P E N D I X C
After re-connecting via Telnet, issue the
ver
command and verify that it is indeed the firmware that
you intended to upload to the distribution chassis. If it is, you have successfully upgraded the firm-
ware.
Problems with the Upgrade
In general, if you fail to upgrade the firmware successfully, you will need to use the RS-232 port
to recover. Should you have difficulties with the upload due to a corrupt file, power failure during
upload, or other accident, do not be alarmed. Even though you may have lost the existing application
program, the distribution chassis bootloader program will remain intact. On boot up, it will check to
see if a valid application program is in the FLASH memory. If there is not, it will immediately go
into the ‘waiting for download’ mode, sending the ‘C’ character every three seconds. You may then
retry the upload procedure, after you have corrected the original problem.
It is possible for the bootloader program to be fooled by a corrupted application program that has
been previously downloaded into FLASH. In this case, it will attempt to start the application pro-
gram. Generally this will result in a failure that will force a watchdog initiated reboot. This process
will be repeated indefinitely unless you intervene.
If the bootload/application launch sequence appears to be caught in a loop, then you will need to use
the serial port to correct the problem. Please see
Appendix B - Upgrading the Firmware, Recover
.
Summary of Contents for FDC3302
Page 2: ......
Page 6: ...F D C 3 3 0 2 U s e r M a n u a l...
Page 10: ...F D C 3 3 0 2 U s e r M a n u a l...
Page 13: ...3 F D C 3 3 0 2 U s e r M a n u a l...
Page 14: ...F D C 3 3 0 2 U s e r M a n u a l 4 C H A P T E R O N E...
Page 41: ...31 F D C 3 3 0 2 U s e r M a n u a l S P E C I F I C AT I O N S...
Page 42: ...F D C 3 3 0 2 U s e r M a n u a l 32 A P P E N D I X D...
Page 44: ...F D C 3 3 0 2 U s e r M a n u a l 34 S P E C I A L M O D I F I C AT I O N S...
Page 45: ......