WN F2 motherboard BIOS update WN MCD 05/V1. Contains files to be copied to MS-DOS 6.22 boot media README.PDF

Transcription

1 Contents of DOWNLOAD.ZIP??UPDATE????IMG.EXE??UPDATE????DD.BIN.\DOS\*.* Win-Image executable for Windows: Creates a bootable DOS based update disk on 1,44MB/3,5" floppy. Image file for Linux (dd): Creates a bootable DOS based update disk on 1,44MB/3,5" floppy. Contains files to be copied to MS-DOS 6.22 boot media 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 Default setup values... 3 BIOS UPDATE RUNNING WINPHLASH... 4 CRISIS DISK FOR BIOS RECOVERY... 4 DOS BASED UPDATE PROCEDURE BASED ON UPBIOS.EXE... 4 ZIP archive... 5 Running DOS BIOS update from external USB boot media... 5 Running DOS BIOS update from CD-ROM... 5 Back flashing:... 5 How to use DOS based flash tool "UPBIOS.EXE"... 6 HISTORY OF WN BIOS RELEASES... 9 README.PDF 1 / 9

2 General remarks This is a new PROJECT BIOS for BEETLE motherboard F2. Since this project release is made for very certain customer Linux environment, we only tested this operating system. This project BIOS is not made for any Windows installation! It is based on WN standard BIOS release 04/06 and is suited to run on WN motherboards type "WN F2 STD / WN F2 ULV. The BIOS will show the following sign up screen: PROJ WN MCD 05/V1 (F2) 05/07/2010 For further details see general README.PDF for this motherboard type Use of project BIOS releases without acknowledge from Wincor-Nixdorf (to be done by our special release procedure) is on your own risk!!! New features / improvements / highlights Improved power management causes lower current on 5V stdby. Changed Setup default parameter due to customers request Known problems or restrictions As a known side effect of workaround for Windows XP BSOD error, only USB 1.1 is supported if BIOS legacy USB mode is used. Accessing USB mass storage device emulated by BIOS is slower then before! Such files are for example copied while hard disk image installation running MS-DOS tools. If operating systems driver controls the USB interface, then full USB 2.0 support is provided. Another side effect may influence script controlled installation of Windows. If installation of internal hard disk (SATA) is based on a boot up from hard disk emulating USB 2.0 stick, then operating system may run enumeration different to previous BIOS releases and disk number/name may be shifted! We tested the update disk and external BIOS setup tool with MS-DOS 6.22! For other DOS derivates, proper function is not guaranteed! After flashing the Bios the system will reboot twice. This is needed to set the boot order. README.PDF 2 / 9

3 Default setup values WN F2 motherboard BIOS update WN MCD 05/V1 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 Reset Configuration Data: NO Speaker Volume HIGH Large Disk Access Mode OTHER Legacy USB Support USB Time Out Value HIGH Internal LAN Controller Onboard LAN Boot Prom Quick Boot Mode DISABLED Video output to COM3 Display messages POST & OS Fan control Automatic Chipset Configuration SMART Device Monitoring Boot-Video device ONBOARD USB 2.0 Support PCI-Reset DISABLED I/O device configuration Serial port A Base I/O address 3F8 Interrupt IRQ4 Serial port B Base I/O address 2F8 Interrupt IRQ3 Touch Screen Routing NO ROUTING DMI Event Logging View DMI event log Clear all DMI event logs NO Event Logging Mark DMI events as read Security Set Supervisor Password NO PASSWORD SET Power After power failure STAY OFF Wake On LAN Wake On Modem Ring DISABLED Wake On Time DISABLED Boot Hardware Monitor Boot Order Follow Setup Order +Removable Devices IBA FE slot (onboard PXE) +Hard Drive +CD-ROM Drive Network Boot Note! If Follow Setup Order is changed to Override setup order, the BIOS will always boot from USB media. This option can not be changed, if Legacy USB Support is disabled! README.PDF 3 / 9

4 BIOS update running WinPhlash There is no WinPlash update available for the Linux based project! 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 (e.g. 04/04) on motherboard! The CRISIS recovery is available for a minimal DOS only. It s always good practise to check the availability of such a CRISIS disk for the existing BIOS release, before you update to 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! USB sticks that emulate floppy disks may work? Note! Running the CRISIS Recovery diskette will reset parameters! The BIOS DMI data and also the UUID will 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 would cause total malfunction, BEETLE may not start up anymore. DOS based update procedure based on UPBIOS.EXE There are some remarkable features of the actual DOS based update procedure. If any of these advanced features is wanted, 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. DMI data will be preserved! 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 VGA adapter. Another feature of update procedure is the support of CMOS setup data save/restore. You can set setup options as wanted, than create an image file of BIOS setup data and after easily write the certain settings from image file to CMOS memory while BIOS flash update procedure! Usage of this feature is on your own risk; you need to test before distribution! README.PDF 4 / 9

5 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. 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 can downgrade from higher releases to the one described in this document. README.PDF 5 / 9

6 How to use 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 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: anyway: 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. ignore error messages from UPBIOS.EXE that would abort BIOS update README.PDF 6 / 9

7 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 biosversion to be flashed. Otherwise upbios.exe breaks and reports error. Hardware platforms (D2, E1, F2, ) 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 7 / 9

8 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 and rebooted. 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). Flashing from STD to POS BIOS will generate DMI error message. 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 biosversion 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 biosversion and bootblockversion 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 flashmode, forcing BIOS+Bootblock to be (re)flashed "upbios anyway" run upbios ignoring all possible errormessages README.PDF 8 / 9

9 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, uses Ramdisk for Update modeflag:x overrides automatic mode recognition: 0 4 flashes BIOS area only 6 flashes BIOS + Bootblock Configuration area: biosversion:wn STD 08/18 bootblock:2sa cmosversion:07/16 production:1 History of WN BIOS releases See previous README files... README.PDF 9 / 9