NCR Kit Operating System Recovery Installation File



[pic]

NCR Q67 (7616-XXXX) BIOS/SPI Updating Instructions

Section 1.0 ---- Purpose of Document

Section 2.0 ---- Update Media Requirements

Section 2.1 ---- PXE Network Boot

Section 2.2 ---- USB Flash Key Boot

Section 3.0 ---- DMI Programming

Section 4.0 ---- Default BIOS Settings

Section 1.0 – Purpose of Document

The purpose of this document is to provide consistent instructions for the process by which an existing motherboard can be upgraded to the latest BIOS/SPI version. This process includes the setting of the DMI information (If necessary). This is to prevent misunderstandings concerning upper versus lower case as well as a defined set of instructions. This process is intended for use with any manufacturers of the Q67 based products. This is primarily intended for end-stage when the motherboard is actually put into a terminal. The details below indicate the process that is required when the Q67 motherboard is placed in a PSD terminal, such as the 7616-XXXX.

Section 2.0 – Update Media Requirements

NCR provides a complete BIOS/SPI update process that can be used from either PXE Network Boot, or USB Memory Key boot. The use of each of the media is similar and is documented in the sections below. The common DMI information is described later.

Section 2.1 – PXE Network Boot

The PXE network boot is provided in a series of files that are downloaded via software such as NCR FitClient or NCR RSM. The files must be uploaded via that tool and configured to be downloaded to the terminal to be updated.

The terminal to be updated must have a valid network connection. During the power-up process of the terminal, pressing the key will bring up a boot menu that allows the network option to be booted. If booted successful, a menu will be presented to the operator. The first option (a complete BIOS/SPI update that is automatic) is the default option that will take place after a period of time. It is completely automatic, unless the DMI data is not properly set. If this happens the operator will be prompted to enter the appropriate data.

Upon completion of the update process, the terminal will briefly pause and then reboot. As the terminal is booting with the new BIOS/SPI, it will power cycle itself multiple times. This is expected behavior due to the nature of the BIOS/SPI environment.

Section 2.3 – USB Flash Key Boot

The USB Flash Key Boot is provided in a series of files. The files must be placed in the root directory of the USB key to be created. The following command must be executed to make the USB key bootable. It is suggested that the current drive be switched to the USB key in order to minimize the risk of corrupting the current computer boot process.

syslinux –fma f:

or

syslinux –sfma f:

Assuming that F: is the USB Flash key drive. The second command line is for some USB keys that are not as “advanced” as others. It is suggested to try the first command line.

Once completed, the USB Flash key, may be removed and used to update other terminals. During the power-up process of the terminal, pressing the key will bring up a boot menu that allows the USB Flash key to be booted. If booted successful, a menu will be presented to the operator. The first option (a complete BIOS/SPI update that is automatic) is the default option that will take place after a period of time. It is completely automatic, unless the DMI data is not properly set. If this happens the operator will be prompted to enter the appropriate data.

Upon completion of the update process, the terminal will briefly pause and then reboot. As the terminal is booting with the new BIOS/SPI, it will power cycle itself multiple times. This is expected behavior due to the nature of the BIOS/SPI environment.

Section 3.0 – DMI Programming

Part of the BIOS/SPI update process is to ensure that the proper DMI information is present in the terminal. The utility for updating the DMI utility is AMI’s AMDDEDOS.exe utility. This utility is run as part of the standard NCR update process described above. It will not allow for wrongly formatted data to be entered. However, if the command needs to be run separately, the following information is provided. This utility takes a single command line parameter of a file that contains the DMI information.

An example of the command line for updating the DMI is:

Amidedos ncr.dms

The contents of the DMI file, ncr.dms in this example, are as follows:

[System]

Manufacturer = NCR Corporation

Product = 7616-1001-8801

Version = NCR BIOS

SerialNum = 50-11223344

UUID = 4E435220000000000000050011223344

The data in the file is case sensitive and is required to be in the following format:

• Manufacturer - NCR Corporation

• Product – XXXX-YYYY-ZZZZ

o Where XXXX is a class number (Example: 7616 or 7606) and YYYY-ZZZZ is a Model number (Example: 1001-8801)

• Version - NCR BIOS

o Note: The BIOS version is NOT to be inserted.

• SerialNum – XX-AAAAAAAA or YYY-AAAAAAAA

o Where XX or YYY is normally the Manufacturing Plant code and AAAAAAAA is the terminal serial number (Example: 50-35170890)

• UUID – 4E4352200000000000000XX0AAAAAAAA

o Where XX is normally the Manufacturing Plant code and AAAAAAAA is the terminal serial number (Example: 54-35170890). The UUID contains the serial number where any dashes are replaced by a “0”.

Section 4.0 – Default BIOS Settings

It is required that before the terminal leave manufacturing, the BIOS defaults need to be in place. This is normally done through the standard update process found on the NCR media. However, if testing has been done on the terminal which may have changed some of the CMOS settings, or additional hardware was added, the following procedure is used to perform a BIOS default.

1) Power up the terminal. As the terminal is powering up, press the key to enter BIOS setup.

2) After entering BIOS setup, press the key to load the BIOS defaults.

3) Press the key to save the values and reboot the terminal.

4) The terminal is now ready to be shipped.

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download