WN D2 motherboard BIOS update WN STD 11/31

Transcription

1 Contents of DOWNLOAD.ZIP??UPDATE????IMG.EXE??UPDATE????DD.BIN??CRISIS????IMG.EXE??CRISIS????DD.BIN??SETUP????IMG.EXE.\DOS\*.*.\WIN\*.* 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. Win-Image executable for Windows: Creates a bootable DOS based crisis disk on 1,44MB/3,5" floppy. Image file for Linux (dd): Creates a bootable DOS based crisis disk on 1,44MB/3,5" floppy. Win-Image executable for Windows: External MS-DOS setup tool for line display output 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... 1 New features and improvements... 1 Known problems or restrictions... 2 Default setup values... Fehler! Textmarke nicht definiert. BIOS UPDATE RUNNING WINPHLASH... 3 To update your BIOS please observe the following instructions:... 3 INTRODUCTION TO BEETLEVIEW REMOTE BIOS UPDATE... FEHLER! TEXTMARKE NICHT DEFINIERT. How to perform the remote update?... Fehler! Textmarke nicht definiert. Where to find README and UPDATE files?... Fehler! Textmarke nicht definiert. WINDOWS ENUMERATION OF COM PORTS... 4 How to re-arrange COM ports manually?... 4 How to re-arrange COM ports unattended?... 4 Additional hint for unattended handling of WN PCI Com card... 4 CRISIS DISK FOR BIOS RECOVERY... 5 DOS BASED UPDATE PROCEDURE BASED ON UPBIOS.EXE... 5 ZIP archive... 6 Running DOS BIOS update from external USB boot media... 6 Running DOS BIOS update from CD-ROM... 6 Back flashing:... 6 External BIOS setup for WN STD BIOS... 6 How to use DOS based flash tool "UPBIOS.EXE"... 7 HISTORY OF WN BIOS RELEASES General remarks This is a new international BEETLE motherboard BIOS release. BEETLE systems from production line will contain this release. The BIOS is suited to run on WN motherboards type "WN D2 xxx. The BIOS will show the following sign up screen: WN STD 11/31 (D2) 10/20/2009 README.PDF 1 / 11

2 For further details see general README.PDF for this motherboard type New features / improvements / highlights Correct values in HardwareMonitor TouchRouting (to COM1/COM2) correction These changes are needed because the onboard super I/O (SIO) chip reached end of life (EOL). The new chip (ITE 8712F Rev. K) requires the new BIOS. SIO includes functions like: COM (RS232) ports; Floppy Disk Controller (FDC); Parallel Port (LPT); GPIO (here used for touch routing and more functions); etc.. Known problems or restrictions If running BEETLEview with this new BIOS release, you need to install the WN tool AdjBV.Exe. Otherwise wrong values for fan speed may be displayed!!! See INTRANET RETAIL PRODUCTS SYSTEM SOFTWARE ADD Ons If SETUP is initialized by F9 key, then BIOS option IRQ-routing to COM4 COM4 is shown only after next reboot! README.PDF 2 / 11

3 BIOS update running WinPhlash If you update the BIOS on a BEETLE platform ensure to start update from appropriate very first released BIOS version or later. Otherwise if update base is test releases - you first have to run the DOS version of BIOS update procedure and prepare the system for in future Windows based updates. BIOS update can be performed with this package under Windows NT or XP. Ensure that you have administrative rights. We tested it with Windows XP and WEPOS only! 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 3 / 11

4 Windows enumeration of COM ports In case of BIOS update from pre released BIOS version with an already installed plug and play operating system like Windows XP, the full plug and play integration of super I/O chip ITE 8774F (implemented to handle WN COM3/4) may cause a detection of same ITE chip as new hardware! Since the operating systems COM port enumerator already ran and reserved COM port numbers for (now non present ) COM hardware, you may find new ports COM5: and COM6: (or COM9: and COM10: if PCI COM installed) in device manager. If PCICOM board/s is/are installed, the new COM ports do have higher numbers. How to re-arrange COM ports manually? 1. Write the following lines to a new file with.reg extension: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment] "DEVMGR_SHOW_NONPRESENT_DEVICES"="1" 2. Double click on the file (Windows explorer) and confirm import action. 3. You need to logoff and logon to activate this option 4. Run the Windows device manager and select view + show hidden devices 5. Remove all ITE COM ports (including non present ones) and rescan for new hardware. How to re-arrange COM ports unattended? 1. Copy WNdevcon.exe on your target system to folder c:\. 2. Build a batch file like this: c:\wndevcon remove ITE* c:\wndevcon rescan 3. Move the batch into auto start folder and reboot. Using the original devcon.exe from Microsoft does not remove the non present devices! You need to run this script only once after BIOS update! It is good practise to (automatically) delete the script after first Windows start up. You need to run this script before you plug in a PCI COM board (Sunix 4056WN)! The enumeration of already installed PCI COM boards will not be touched by Windows XP. And of course, you can place the executable into any other folder instead of C:\. Additional hint for unattended handling of WN PCI Com card If you want to remove SUNIX based COM ports, build a batch file like this: c:\wndevcon remove *SNX* c:\wndevcon rescan README.PDF 4 / 11

5 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 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! 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! README.PDF 5 / 11

6 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. External BIOS setup for WN STD BIOS yxstdstp.exe (to be found on update disk) is a MS-DOS based setup editor that gives you the chance to show and manipulate certain options of BIOS setup configuration even if the BEETLE configuration does not include a VGA screen. It leads you through a basic 2 x 20 character user interface, optimized for WN line display output. If output on a BA6x line display at COM3 is wanted even if a VGA screen is connected, load DOS driver BA6x_DRV.COM, included in the update disk package. This enables output to COM3; otherwise the output will be sent to screen. See README on update disk for further details README.PDF 6 / 11

7 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 7 / 11

8 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 8 / 11

9 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 9 / 11

10 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 README.PDF 10 / 11

11 History of WN BIOS releases See previous README files... README.PDF 11 / 11