evertz 2430GDAC, Инструкция по эксплуатации

Страница: 14 / 15

2430GDAC GLink D to A Converter
2430GDAC - 8
Revision 1.3
6. UPGRADING THE FIRMWARE
The 2430GDAC module contains firmware that is contained in a FLASH EPROM device. From time to
time firmware updates will be provided to add additional features to the unit. The 2430GDAC module is
fitted with a COM port connector that can be connected to a PC with a straight through cable. The
following procedure will allow you to upload new firmware from your computer.
6.1. REQUIREMENTS
You will need the following equipment in order to update the 2430GDAC Firmware
•
PC with available communications port. The communication speed is 115200 baud, therefore a 486
PC or better with a 16550 UART based communications port is recommended.
•
“Straight-thru” serial extension cable (DB9 female to DB9 male).
•
Terminal program that is capable of Xmodem file transfer protocol (such as HyperTerminal).
•
New firmware supplied by Evertz.
6.2. UPDATE PROCEDURE
6.2.1. Part 1 – Configuring the Unit for Firmware Upgrades
1. Connect the 9 pin male connector on the straight through serial extension cable to the COM port on
the end of the 2430GDAC. Connect the 9 pin female connector to the PCs’ RS-232 communications
port.
6.2.2. Part 2 – Terminal Program Setup
2. Start the terminal program.
3. Configure the port settings of the terminal program as follows:
Baud 115200
Parity no
Data bits
8
Stop bits 2
Flow Control None
4. Apply power to the 2430GDAC. After the unit powers up, a banner with the boot code version
information should appear in the terminal window. The cursor to the right of the word “BOOT>” should
be spinning for about 5 seconds then the unit will continue to boot.
For example:
EVERTZ MCF5272 MONITOR 2.3 BUILD 3 (66 MHZ)
COPYRIGHT 1997, 1998, 1999, 2000, 2001, 2002 EVERTZ MICROSYSTEMS LTD.
28F160C3B FLASH DETECTED
PROD=2430GDAC
MCF5272 COLD BOOT> |
5. The following is a list of possible reasons for failed communications:
•
Defective serial cable.
•
Wrong communications port selected in the terminal program.
•
Improper port settings in the terminal program (Refer to step 3 for settings).