WN motherboard BIOS update WN STD 00/00 (H1)

Transcription

1 Contents of DOWNLOAD.ZIP??UPDATE????IMG.EXE??UPDATE????DD.BIN??CRISIS????IMG.EXE??CRISIS????DD.BIN.\DOS\*.*.\WIN\*.* Image - executable for Windows: contains standard update disk Creates a bootable DOS based update disk on 1,44MB/3,5" floppy. Image file for Linux (dd): contains standard update disk Creates a bootable DOS based update disk on 1,44MB/3,5" floppy. Image - executable for Windows: contains crisis recovery disk Creates a bootable DOS based crisis disk on 1,44MB/3,5" floppy. Image file for Linux (dd): contains crisis recovery disk Creates a bootable DOS based crisis disk on 1,44MB/3,5" floppy. Contains files to be copied to MS-DOS 6.22 boot media Contains files for Windows based flash update README.PDF This information????... Actual BIOS release number??. Motherboard type *.* all files in folder Contents of this README file CONTENTS OF DOWNLOAD.ZIP... 1 CONTENTS OF THIS README FILE... 1 GENERAL REMARKS... 2 New features / improvements / highlights... 2 Known problems or restrictions... 2 More information... 2 Default setup values... 3 UUID... 4 BIOS UPDATE RUNNING WINPHLASH... 4 To update your BIOS please observe the following instructions:... 4 AMT... 5 RAID... 5 CRISIS DISK FOR BIOS RECOVERY... 5 DOS BASED UPDATE PROCEDURE BASED ON UPBIOS.EXE... 6 ZIP archive... 6 Running DOS BIOS update from external USB boot media... 6 Running DOS BIOS update from CD-ROM... 7 Back flashing:... 7 How to use MS-DOS based flash tool "UPBIOS.EXE"... 7 HISTORY OF PREVIOUS BIOS RELEASES README.PDF 1 / 11

2 General remarks This is a new international BEETLE standard motherboard BIOS release. Since now, BEETLE systems from production line will contain this release. The BIOS is suited to run on WN motherboards type "WN H1 and also on later releases. The BIOS will show the following sign up screen: WN STD 00/00 (H1) 03/31/2009 WN standard BIOS releases are not valid for WN basic motherboards and WN basic BIOS releases do not work with WN standard motherboards, even if they contain the same chipset! However, there is only one standard BIOS release for both standard STD and ULV motherboards. New features / improvements / highlights The Q35 chipset contains Intel AMT3.0. Onboard SATA RAID by Intel chipset The network boot (PXE) is included in upper boot group by default. If no other bootable device is present in this group, then PXE boot over network is initialized. New DMI data implementation! Newest DMI DATA MAINTENANCE disk is required! Older releases destroy the DMI data structure! See WN INTRANET / EXTRANET for update. Known problems or restrictions We tested the update disk and external BIOS setup tool with MS-DOS 6.22! For other DOS derivates, proper function is not guaranteed! WN provides mass storage / RAID controller PROMISE Fast Track TX-2650, originally made for F2 motherboards. The actual H1 BIOS 00/00 does not support it. Use onboard RAID instead. More information For further details see general README.PDF and manual for this motherboard README.PDF 2 / 11

3 Default setup values After corrupted checksum the BIOS will set its default to the following values: Main Primary Master: AUTO Primary Slave AUTO Secondary Master: AUTO Secondary Slave: AUTO Advanced Advanced Chipset Control Default Primary Video Adapter IGD IGD Memory Size MaxDVMT DVMT Graphics Memory 376MB 1 Onboard GBE LAN Enabled Onboard LAN BootRom Enabled Azalia Audio AUTO Serial ATA Enabled Native Mode Operation Serial ATA 2 SATA RAID enable Disabled Hard Disk Pre-Delay 3 Seconds I/O Device Configuration Serial port A ENABLED Base I/O address 3F8 Interrupt IRQ4 Serial port B ENABLED Base I/O address 2F8 Interrupt IRQ3 Touch Screen Routing TFT TOUCH TO COM2: DMI Event Logging Event logging ENABLED Clear all DMI event logs NO Reset Configuration Data No Speaker Volume High Video Output to COM3: Disabled Security Set Supervisor Password NO PASSWORD SET Power Power State Stay Off Standby Power Enabled Wake On Modem Ring DISABLED Wake On Time DISABLED Hardware Monitor No values to be set Boot Included in Boot Order USB FDC USB CDROM IDE CDROM USB HDD IDE 0 SATA 1 SATA 2 PCI LAN: IBA FE Slot PXE 3 Excluded from Boot Order Not available SATA3 SATA4 USB KEY USB ZIP PCI SCSI Other USB PCI Legacy Network Card UNKNOWN 1 dependant on overall available memory! 2 behaviour while BIOS boot 3 IBA = Intel Boot Agent PXE boot README.PDF 3 / 11

4 UUID This BIOS release provides a Universally Unique Identifier (UUID), which is created automatically once during very first flashing from WN BIOS update disk and never changed, even if newer BIOS release will be updated or project BIOS is used. This feature makes unique identification of every WN motherboard possible! If a BIOS project release without UUID support was flashed before, you need to start the BIOS update procedure twice the 2 nd start is only for UUID update. BIOS update running WinPhlash If you update the BIOS on a BEETLE platform ensure to start update from appropriate released BIOS version or later. The WinPhlash update procedure looks for valid BIOS identifiers and will not run if they are not found; we could see such behaviour in our labs with pre released test BIOS a security feature! BIOS update can be performed with this package under Windows. Ensure that you have administrative rights. We tested it with Windows XP and WEPOS! To update your BIOS please observe the following instructions: 1) Unzip all files of the.\win\*.* to a temporary directory on the target system to be updated. It s good practice to choose a simple folder name like C:\BIOS 2) Execute the unzipped file RUNWPH.BAT. This will start the check and update procedure without any interaction needed. Don t click any button inside the WinPhlash window. Wait until this ( ) dialog in shown. WinPhlash will report the progress of the update continuously. During that time DO NOT POWER OFF or DO NOT REBOOT the system. 3) After successful update WinPhlash will perform an automatic reboot. Note! WinPhlash must not be executed directly, as this would circumvent the plausibility checks. Always start it by the batch file! Now, running WinPhlash based package for actual BIOS release or higher all BIOS SETUP parameters will remain after update. WinPhlash writes a log file PHLASH.LOG. This can be helpful to refer to in case of a problem. If flashing the BIOS was performed successfully, delete all files from the temporary directory used for BIOS update. WinPhlash is registered to Phoenix Technologies Ltd. README.PDF 4 / 11

5 AMT The new AMT feature provides lots of new functions. The highlights are: low level remote access over LAN, reboot the BEETLE even if the operating system hangs, setup BIOS parameters over LAN connection, boot local server hard disk image over LAN, It is also possible to update the BIOS itself over AMT environment (server) without any operating system running on target BEETLE. All the features and handling can not be completely described here! For further details see BEETLE handbook and Intel documentation in WWW. RAID It is good practice to enable onboard RAID in BIOS SETUP before start of installation of Windows operating system. While installation Windows will ask you for keystroke F6 and according driver. Crisis disk for BIOS recovery If there is a power fail during BIOS flash programming or update failed by other reasons, use the CRISIS DISK for recovery. To be found in the related DOWNLOAD.ZIP file for the already existing BIOS release on motherboard! The CRISIS recovery runs only with the included minimal DOS! It s always good practise to check the availability of such a CRISIS disk for the existing previous BIOS version you want to update, before start the update procedure to a newer version! If Windows is your operating system, you need to use the crisis disk image *CRISIS*IMG.EXE to create a crisis boot disk! For Linux operating system, you can use the crisis disk image *CRISIS*DD.BIN to create a crisis boot disk by dd command! The crisis disk detection includes search for external USB floppy disks, but support of USB memory sticks is not guaranteed! Note! If the CRISIS Recovery diskette is needed, the BIOS contents is already destroyed, mostly caused by interrupted BIOS update procedure. In this case the UUID may be lost! To initialize a new UUID, use standard BIOS update disk. The CRISIS disk is a made for recovery purpose only! It should never be used for BIOS update from different releases. This may cause total malfunction, BEETLE may not start up anymore. README.PDF 5 / 11

6 DOS based update procedure based on UPBIOS.EXE There are some remarkable features of the actual DOS based update procedure. Automatic start of BIOS update after boot up of floppy! You are not prompted to confirm flash update, but you may abort the automatic procedure, when asked. It provides output to external line displays for BEETLE with or without any graphics (VGA) adapter. Support of CMOS setup data save/restore. You can set setup options as wanted, than create an image file of BIOS setup data and afterwards easily write the certain settings from image file to CMOS memory while BIOS flash update procedure! For this feature, you need to adapt the update floppy disk! See chapter How to use DOS based flash tool "UPBIOS.EXE" for further information about all options. Usage of this feature is on your own risk; you need to test before distribution! ZIP archive The folder DOS inside archive DOWNLOAD.ZIP contains all BIOS UPDATE files to be copied on a MS-DOS 6.22 bootable media (floppy, USB memory stick ). It is good practise to format the media before files are copied! Running DOS BIOS update from external USB boot media The update procedure supports DOS boot from external USB floppy, CD-ROM Unfortunately, most distributors of memory sticks do not provide any trustable information about the (DOS) boot ability of their devices. You need to buy & test This is not a BEETLE restriction most PC BIOS do show similar problems! How to create a bootable USB boot device for BEETLE? Most vendors provide a Windows based program to create bootable sticks. If not available, this may help you to do so: 1. Create a MS-DOS 6.22 (!) boot floppy and copy fdisk.exe and format.com to it 2. Install a BEETLE with WN motherboard and internal (standard) floppy drive. To avoid confusion, it s good practise to disconnect SATA/PATA hard disk drives! 3. Enable USB legacy mode in BIOS SETUP and boot DOS floppy from internal floppy drive 4. Now, you can detect if your USB mass storage is supported or not: If the USB device emulates a hard disk, FDISK should present it If the USB device emulates a floppy disk, DOS should show a new drive letter 5. Use fdisk.exe and/or format.com <drive>: /s to create a bootable media. README.PDF 6 / 11

7 Running DOS BIOS update from CD-ROM Update disk releases since 4.0 and higher support bootable CD-ROM media for BIOS update. The recommended (and easiest) way to build an update CD is this: 1) Create bootable floppy disk from WN image and leave the floppy inside drive. 2) Start your favourite tool and build a bootable CD. When ask, choose floppy disk emulation from floppy in drive! Back flashing: WN internal qualification of in future WN BIOS releases will always include a backward compatibility check. Therefore, you usually can downgrade from higher releases to the one described in this document. Exceptionally we do not recommend going back to BIOS 00/00. There are too many differences in CMOS structure and of course BIOS 00/00 contains a Windows blue screen risk with USB 2.0 devices. How to use MS-DOS based flash tool "UPBIOS.EXE" This information is also placed in README*.TXT on floppy!! General: UPBIOS.EXE release is designed for easy support of Phoenix PHLASH.EXE tool. Update procedure is running automatically, configurable by UPBIOS.CFG configuration file and via arguments from command line. All messages are minimized and optimized for use of 2x20 lines display. No need of keyboard input, but abort of procedure is possible. Beep support is provided for abort option (one double beep), successful operation (two double beeps) and error messages (three double beeps). UPBIOS.EXE is used for DOS based flash update of POS- and STD BIOS. Options are selectable from command line. It might be useful to create an AUTOEXEC.BAT providing the complete command line. Configuration is done via UPBIOS.CFG configuration file. See next page README.PDF 7 / 11

8 Options: UPBIOS [com3] [cdump] [cload] [t] [q] [p] [m n] [over] [anyway] Any options may be mixed, but if cdump is selected, no BIOS update will be done. Options from command line will override appropriate keyword properties in UPBIOS.CFG. com3: if BA6x on COM3 is available, screen output will be redirected to COM3. cdump: cload: Make a CMOS copy of actual system into the file CMOSDUMP.IMG. No BIOS update will be done. Before BIOS update, CMOS of actual system will be loaded from file CMOSDUMP.IMG t: Test mode for debugging problems only, no BIOS update will be done. q: Quick mode is waiting between 2-line-messages and beeps will be overrun p: Production mode does not use Phoenix(R) screening while flashing (always used with com3-option) M n: over: Mode: force flash mode n overrides automatic mode recognition: if n=4, flashes BIOS area only if n=6, flashes BIOS + boot block Overwrite ignores message "->no update needed" and reflash BIOS, but without clearing checksum of CMOS; so, Setup will not reset to default values. anyway: ignore error messages from UPBIOS.EXE that would abort BIOS update Any other option will break and display options available. README.PDF 8 / 11

9 Configuration file UPBIOS.CFG: Configuration is done via UPBIOS.CFG. Keywords must begin in column 0 and spell exactly until ":". Arguments have to follow immediately. Number and order of lines do not matter. Keywords work as follows: Required: BIOSVERSION BOOTBLOCK Optional: CMOSVERSION TESTVERSION TESTFLAG PRODUCTION RAMDISK MODEFLAG ID of new BIOS version to be flashed. Both IDs from old BIOS and new BIOS. If both IDs are identical, update will be aborted must-be-keys may be defined by BIOS development only! ID of new boot block to be flashed, compared by UPBIOS.EXE before any flash action. CMOS checksum will not be cleared, if found BIOS version of previous Bios is equal or higher to value of CMOS version. Superior condition is BIOS does not detect any checksum error after reboot. Keyword may be defined by Bios development only! set by Bios development only to message test versions to be flashed Set by Bios development only to debug problems. Will be OR-ed with "t" option "1" inhibits Phoenix PHLASH interface. Will be OR-ed with "p" option. Will install a RAM disk and run upbios.exe from installed RAM disk. (Drive c: to o:) overrides automatic mode recognition: if 4, flashes BIOS area only if 6, flashes BIOS + boot block Security: After calling UPBIOS.EXE all needed files are checked to be available. Using option "cload", writing to CMOS area is possible only, if header of "cmosdump.img" corresponds to system platform and BIOS version to be flashed. Otherwise upbios.exe breaks and reports error. Hardware platforms (like D2, E1, F2, G1i, H1 ) are checked via boot block check to avoid system breakdown after flashing with Bios that is not designed for that hardware. Crossover flashing from STD/POS-BIOS to BAS-BIOS (and reverse) is not possible. Back flashing: There is no problem reported for back flashing. README.PDF 9 / 11

10 Plausibility: Boot block IDs of old and new Bios are checked. Boot block will be flashed only if IDs are different. If boot block flashing is needed and boot block is write-protected, system will be unlocked. DMI data area will be checked and re flashed only, if actual DMI data area is corrupted or not available (flashing from POS to STD Bios). Error message may be overridden with command line option "anyway" or interactively by request. CMOS Checksum will not be cleared, if - the "cload" option was used OR - the "cmosversion:"-parameter in "upbios.cfg" is equal or higher to BIOS version ID found in actual system. Not clearing the CMOS checksum will prevent system from asking for F1 or F2 keys during first boot after reflashing and will preserve systems actual configuration. Upbios.exe will report success and will NOT reflash Bios, if BIOS version and boot block version found in actual system correspond to the values of must-be-keys in "upbios.cfg". Command line examples: "upbios" normal call using "upbios.cfg" for configuration, no options "upbios com3" as before, using display on COM3 if available "upbios cdump" creating CMOS-image from actual system, no BIOS update "upbios cload" load CMOS-image (if available) into CMOS, followed by BIOS update "upbios cload q p" load CMOS-image (if available) into CMOS, followed by BIOS update; no beeps, no waiting during text scrolling, no Phoenix Phlash screen; fastest way of BIOS update inclusive Setup configuration "upbios m 6" disable automatic flash mode, forcing BIOS + boot block to be (re)flashed "upbios anyway" run UPBIOS.EXE ignoring all possible error messages README.PDF 10 / 11

11 Example configuration file "upbios.cfg" Note: The configuration area for any BIOS version will always be defined by Bios development! UPBIOS [com3] [cdump cload] ============================= com3 : use display connected to COM3 if available cdump: create CMOSDUMP.IMG from actual system cload: update Bios and load CMOS with CMOSDUMP.IMG remove leading -characters to activate keywords. needed================================================ biosversion:wn XXX aa/bb new BIOS ID bootblock:x/y new BB ID optional============================================== cmosversion:aa/bb no CMOS checksum clearing, if updating from Biosversion aabb or higher testversion: any string testflag:0 if 1, messaging variables and preventing flashing production:0 if 1, does not use Phoenix Phlash Interface ramdisk:0 if 1, UPBIOS.EXE uses a RAM disk for Update modeflag:x overrides automatic mode recognition: 0 4 flashes BIOS area only 6 flashes BIOS + boot block Configuration area: biosversion:wn STD 08/18 bootblock:2sa cmosversion:07/16 production:1 History of previous BIOS releases For further info about BIOS history, see README.PDF of previous WN BIOS for this motherboard... README.PDF 11 / 11