retrieve the new image files by downloading them into the BudgeTone 200’s SRAM. During this stage, the BudgeTone 200’s LEDs will blink until the checking/downloading process is completed. Upon verification of checksum, the new code image will then be saved into the Flash. If TFTP fails for any reason (e.g., TFTP server is not responding, there are no code image files available for upgrade, or checksum test fails, etc), the BudgeTone 200 will stop the TFTP process and simply boot using the existing code image in the flash.
TFTP process may take as long as 1 to 2 minutes over the Internet, or just 20+ seconds if it is performed on a LAN. Users are recommended to conduct TFTP upgrade in a controlled LAN environment if possible. For those who do not have a local TFTP server, Grandstream provides a
NOTE:
•When BudgeTone 200 boots up, it will send TFTP or HTTP request to download configuration files, there are two configuration files, one is “cfg.txt” and the other is “cfg000b82xxxxxx”, where “000b82xxxxxx” is the MAC address of the BudgeTone 200. These two files are for initial automatically provisioning purpose only, for normal TFTP or HTTP firmware upgrade, the following error messages in a TFTP or HTTP server log can be ignored.
TFTP Error from [IP ADRESS] requesting cfg000b82023dd4 : File does not exist
TFTP Error from [IP ADRESS] requesting cfg.txt : File does not exist
46
