5.243 bytes

Service Hints & Tips

Document ID: DDSE-3QNJB5

PCServer704 - System BIOS Information

Applicable to: World-Wide

System BIOS
The system BIOS is stored in nonvolatile memory (NVRAM) in a flash EPROM device. You can easily update the BIOS without replacing the device.

A BIOS update always updates Setup, the onboard Video BIOS, and the SCSI BIOS. Language files will be overwritten by a BIOS update. If a custom language file has been created for the system, you must flash in the custom file again after updating the BIOS. The user binary area is untouched by a system BIOS update.

When running FMUP in the interactive mode, you can do the following:
Save: Take a mirror image copy of a given flash area and copy it to a hard disk or diskette.
Update: Take a file or files from a hard disk or diskette and update them with the system's flash device.
Verify: Compare an existing flash area against a file or files on hard disk or diskette to verify that the versions are the same and insure that the system has the correct BIOS version.

Note
FMU must be run without the presence of a 386 control program (such as Windows or EMM386). FMUP uses the processor's flat model mode to update the flash part. If necessary, exit Windows and disable EMM386 before using FMUP.

System BIOS Normal Update Procedure
To update the system BIOS, do the following.
1. Copy the files from the BIOS Update diskette toa bootable DOS diskette.
2. Insert the bootable diskette into drive A; then, reboot the system. The update process starts automatically after the system reboots.
3. Follow the displayed prompts, includinga final reboot.

Note
Updating the BIOS does not clear CMOS. If you need to clear CMOS and reset nonvolatile memory to the factory defaults.

System BIOS Recovery Procedure
The recovery operation automatically updates the main system BIOS only. Video is not initialized, and the keyboard is disabled. Because there is not screen display, you will need to listen for the following audible status signals.
Audible Beeps Description
1 Signals beginning of recovery process; process takes 2 to 4 minutes.
2 Signals successful completion of recovery process with no errors.
4 System could not boot form the diskette. Diskette may not be bootable.

Audible Beeps Description
Continuous series Any or all of the following causes: of low beeps (like The wrong BIOS recovery files are being used a buzz)Configuration switch allowing BIOS Recovery mode is in the wrong position.
- Configuration switch allowing BIOS Write to flash memory is in the wrong position.
- One or more system BIOS FMUP files are corrupt or missing.

Note
If the BIOS of an add-in board is mapped to any part of the E0000H range, you must either map it to another area before beginning a recovery procedure or physically remove the board from the system.

To run the BIOS recovery procedure, do the following.
1. If you have not already done so, copy the BIOS Update diskette files toa bootable DOS diskette.
2. Power-off the system.
3. On the system board, move the J6A1 BIOS Recovery jumper from pins1 and2 to pins2 and 3. See 'BIOS Recovery Jumper (J6A1)— .
4. Insert the Flash Memory Update diskette (the bootable DOS diskette you copied the update files to) in drive A; then, power-on the system. You will hear a single initial beep that is part of the normal system start-up process.
5. You will hear two beeps when the process is successfully completed. If the process is not successful, you will hear a different beep pattern. Refer to the preceding table.
6. Make sure the diskette drive activity light is off. Power-off the system.
7. At J6A1, remove the BIOS Recovery jumper from pins2 and 3, and place it back on pins1 and 2.
8. Remove the FMUP diskette from drive A.
9. Power-on the system and check the BIOS version number against what you intended to flash in.

Search Keywords

Hint Category

BIOS, Hardware Maintenance Information

Date Created

10-06-96

Last Updated

18-05-98

Revision Date

15-05-99

Brand

IBM PC Server

Product Family

PC Server 704

Machine Type

8650

Model

TypeModel

Retain Tip (if applicable)

Reverse Doclinks
and Admin Purposes