Boot File Needs to be Upgraded

Use the following procedure to upgrade the Boot file:

NOTE: A boot file rarely needs to be upgraded. Perform this procedure only at Avaya’s request.

1. The following message displays:

2. While the hardware is being initialized, the following message displays:

3. While either the application file if there is one or the boot code is uncompressed into RAM, the following message displays:

This message counts the seconds as the application file (replboot_v3.app in this example) is being written into RAM.

4. When control is passed to the software that was just loaded, the following messages display:

This message continues while the new boot code is being written into RAM.

NOTE: Unplugging the telephone while the flash memory is being erased and the boot code rewritten can cause file corruption.

5. The telephone detects and displays the speed of the Ethernet interface in Mbps, that is, 0, 10, or 100. The message No Ethernet displays until the software determines whether the interface is 10 Mbps or 100 Mbps.

NOTE: The Ethernet speed indicated is the LAN interface speed for both the telephone and any attached PC.

6. The software determines whether sufficient IP Address information was downloaded. In this scenario, it is discovered that sufficient information has not been downloaded. The following message displays while the DHCP process is invoked:

The number of elapsed seconds is incremented once per second, until DHCP successfully completes.

7. The following message displays while the TFTP or HTTP process is invoked:

The number increments once per second, until the TFTP or HTTP server responds.

8. The following message displays while the upgrade script downloads from the TFTP or HTTP server:

where n is the number of KBs that have been downloaded.

9. The script file is processed. The software determines that the telephone’s boot code file name (BOOTNAME) is not the latest version. APPNAME is set to the name of an application file to replace the boot code. The following message displays while the application file is downloaded into RAM:

where n is the number of KBs downloaded.

10. The following message displays while the application file is stored in flash memory:

where n is the percentage of the file stored, and x is the number of elapsed seconds. This usually takes longer than the file download.

11. The following message displays while the telephone is reset so the application file can be executed:

12. While the hardware is being initialized, the following message displays:

13. While either the new application file is uncompressed into RAM, the following message displays:

This message counts the seconds as the application file (4620_031225.app in this example) is being written into RAM.

14. When control is passed to the software that was just loaded, the following message displays:

15. While the entire flash memory is erased in preparation for rewriting the code, the following message displays:

where n is the percentage of memory erased and x is the number of elapsed seconds during erasing.

16. While the boot code is rewritten, the following message displays:

where n is the percentage of boot code rewritten and x is the number of elapsed seconds during rewriting.

17. When the new boot code is successfully written into the flash memory, the application corrupts its own checksum stored in flash. The application then resets the telephone so the latest system-specific application file can be downloaded.
18. Continue with the next procedure.