CONTENTS OF THIS README FILE

Transcription

1 Contents of DOWNLOAD.ZIP *UPDATE????ARJ.EXE *UPDATE????IMG.EXE *UPDATE????DD.BIN ARJ self extracting archive for DOS: Extracts update files to A:\ 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. *CRISIS????ARJ.EXE *CRISIS????IMG.EXE *CRISIS????DD.BIN ARJ self extracting archive for DOS: Extracts crisis files to C:\CIRSIS 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. README.PDF This information????... Actual BIOS release number *. Motherboard type Contents of this README file CONTENTS OF DOWNLOAD.ZIP 1 CONTENTS OF THIS README FILE 1 GENERAL REMARKS 2 WHAT S NEW? 2 KNOWN PROBLEMS 2 GENERAL RESTRICTIONS OF E1 DOS-BIOS 2 MS-DOS WITH E1 MOTHERBOARD 3 WINDOWS NT4 WITH E1 MOTHERBOARD 3 DOS BASED UPDATE PROCEDURE - RELEASE SELF EXTRACTING ARJ ARCHIVES FOR DOS 4 CRISIS DISK FOR BIOS RECOVERY 4 HOW TO USE DOS BASED FLASH TOOL "UPBIOS.EXE" 5 GENERAL: 5 OPTIONS: 5 CONFIGURATION FILE UPBIOS.CFG: 6 SECURITY: 7 BACK FLASHING: 7 PLAUSIBILITY: 7 COMMAND LINE EXAMPLES: 8 HISTORY OF E1 DOS BIOS RELEASES FOR BEETLE (I845GV) 10 RELEASE INFO WN DOS 20/00 (E1) 10 BASED ON RELEASE REQUIREMENTS/DEPENDENCES 10 REMOVED ERRORS/ERROR-NO.: 10 NEW FUNCTIONS/ENHANCED FUNCTIONS 10 FUNCTIONS UNDER DEVELOPMENT 10 ADDITIONAL REMARKS 10 DEFAULT SETUP VALUES 11 README.PDF 1 / 11

2 General remarks The E1 motherboard was not intended for use with DOS or Windows NT4. However, as some customers wanted to have a BEETLE system with Pentium 4 processor, which would be used with DOS until they have their application ready for Windows XP or Linux, we do provide this special PROJECT BIOS. There are some restrictions and also points to observe, which are described below. What s new? This is the very first release of DOS BIOS for E1 Known problems E1 DOS BEETLE should be ordered with internal floppy disk drive. Since there is no USB or CD boot available BIOS update by disk would be impossible! We could see that in some cases the onboard RS232 ports COM3: / COM4: are not available after boot up. This is caused by a non PnP operating system (DOS or WinNT4) started after BIOS internal plug and play procedure (re)organized PCI devices. The ESCD always needs to be reorganized, too. Restart BEETLE, run BIOS SETUP (F2) and set RESET CONFIGURATION DATA to YES. General restrictions of E1 DOS-BIOS Boot from (internal) IDE-CDROM not supported! Compact Flash cards (CF) are not supported as boot media USB cannot be used no boot from any USB device (CD, memory stick, etc.) possible. E1 DOS BIOS does not support sound onboard hardware PS/2 mouse is not supported. E1 DOS BIOS does not support DMI data, but also does not touch any existing DMI data E1 STD BIOS needed to load DMI data once (factory) Then BEETLE can be re flashed to E1 DOS BIOS (DMI data remains) The DOS-BIOS assigns all onboard (bridged) COM ports to fixed resources: COM1: base address 03F8, IRQ4 COM2: base address 02F8, IRQ3 COM3: base address 03E8, IRQ10 COM4: base address 0270, IRQ10 For the onboard network adapter fixed resource IRQ11 is assigned. PCI COM board does not work in lower slot Needs to be configured in upper slot Assignment of IRQ is fixed: COM5: base address 3840, IRQ12 COM6: base address 3848, IRQ12 COM7: base address 3860, IRQ12 COM8: base address 3868, IRQ12 README.PDF 2 / 11

3 MS-DOS with E1 motherboard The DOS BIOS is designed for DOS based projects only. You need to accept these restrictions: The DOS-BIOS provides more memory in the UMB area. Working with EMM386.EXE the memory area CC00-EDFF can be included. If Intel boot agent is enabled, it uses UMB space D0000-D1800. The Base DOS memory is free till the address AFFFF. In this way it is possible to expand the Base DOS memory to address B7FFF. The onboard graphics TFT adapter doesn't provide a full screen (stretching) display with DOS. If that is a requirement, a PCI graphics adapter card should be used, as e.g. the Chips & Technology / Silicon Motion Lynx EM+ (SM712) based card. If onboard bridge is used together with PCI video, BOOT VIDEO DEVICE should be setup to PCI-SLOT (BIOS setup). Windows NT4 with E1 motherboard To get a robust Windows NT4 system it is necessary to use the E1-DOS-BIOS. DOS-BIOS remappes COM3:/COM4: to legacy resources No driver for COM34 needed; do not install any! Windows NT4 does not support USB at all E1 DOS BIOS disables USB completely Even boot from USB device is not possible Windows based BIOS update (WinPhlash ) works fine In future migration to E1 STD BIOS (forced by Windows XP) is possible. README.PDF 3 / 11

4 DOS based update procedure - release 3.5 Some (new) main features of the DOS based update package: If any of these advanced features is wanted, you need to adapt the update floppy disk! See chapter "How to use flash tool UPBIOS.EXE" for further information about options. 1. DMI data will be preserved here and if BIOS will be flashed to STD BIOS. 2. BIOS setup configuration (CMOS), done with standard BIOS setup will be lost after update to DOS BIOS. 3. One main feature of releases is the 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. 4. It provides output to external line displays for BEETLE with or without VGA adapter. 5. Another new 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! The update disk needs to be adapted for this feature. Self extracting ARJ archives for DOS The self extracting ARJ archives (*ARJ.EXE), are basically made for DOS, but they do extract all data under Windows as well. The UPDATE archive extracts files directly to a floppy in drive A:\ You need to rename the archive file to "8.3 format" before running it on a DOS system. It is good practise to store and run the ARJ self extractor in root folder or C:\TEMP, because it is a DOS based tool which does not support long folder paths. Always prepare the update disk by DOS command line "format a: /s". Crisis disk for BIOS recovery If there is a power fail during programming or BIOS update failed by other reasons, use the CRISIS DISK for recovery. To be found in the same DOWNLOAD.ZIP file. The CRISIS recovery is available for DOS only. If Windows is your operating system, you need to use the crisis disk image *CRISIS*IMG.EXE to create a crisis boot disk! DOS based systems require the ARJ self extracting archive, which extracts to folder C:\CRISIS. Use C:\CRISIS\CRISDISK.BAT to build a crisis disk. You do need to boot up a DOS system - this can not be done in a Windows command box! Since a certain minimal, non standard DOS (without screen output) is needed for crisis recovery, do not use DOS commands "format" or "sys". Detailed information you also find in README.TXT in archives / image files. README.PDF 4 / 11

5 How to use DOS based flash tool "UPBIOS.EXE" This information is also placed in README_3.TXT on floppy!! General: UPBIOS.EXE release 3.x is designed for easy support of Phoenix PHLASH.EXE tool. Update procedure is running automatically, configurable via 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: Mode: force flash mode n overrides automatic mode recognition: if n=1, flashes DMI area only if n=4, flashes BIOS area only if n=5, flashes BIOS + DMI if n=6, flashes BIOS + boot block if n=7, flashes BIOS + boot block + DMI README.PDF 5 / 11

6 over: 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. 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 DMIVERSION 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! DMI data will be initialized, if found BIOS version of previous BIOS is lower to value of DMI version. 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 1, flashes DMI area only if 4, flashes BIOS area only if 5, flashes BIOS + DMI if 6, flashes BIOS + boot block if 7, flashes BIOS + boot block + DMI README.PDF 6 / 11

7 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 (D1, D2, D2basic, D2e, E1) 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(D2)-Bios to BAS(D2)-Bios (and reverse) is not possible. Back flashing: There is no problem reported for back flashing. Plausibility: Boot block IDs of old and new Bios are checked. Boot block will be flashed only if ID's 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 reflashed only, if actual DMI data area is corrupted or not available (flashing from POS to STD Bios). In addition option "dmiversion" will determine when to initialize DMI data area during Bios upgrade. 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". README.PDF 7 / 11

8 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 7" disable automatic flashmode, forcing BIOS+Bootblock+DMI to be flashed "upbios anyway" run upbios ignoring all possible errormessages README.PDF 8 / 11

9 Example configuration file "upbios.cfg" Note: The configuration area for any biosversion will alyways 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 dmiversion:aa/bb no DMI data area 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 1 flashes DMI area only 4 flashes BIOS area only 5 flashes BIOS + DMI 6 flashes BIOS + Bootblock 7 flashes BIOS + Bootblock + DMI Configuration area: biosversion:wn STD 08/18 bootblock:2sa dmiversion:03/06 cmosversion:07/16 production:1 README.PDF 9 / 11

10 History of E1 DOS BIOS releases for BEETLE (i845gv) RELEASE INFO WN DOS 20/00 (E1) Based on Release --- Requirements/Dependences Hardware Sited to run on "E1" Board Print C" and later Software none Removed Errors/Error-No.: First release New Functions/enhanced Functions First release Functions under development none Additional remarks This BIOS works for BEETLE CPU Pentium 4 (E1-CPU), acting as DOS Version to support applications with the need of high amount of UMB memory. It is designed to run on DOS and NT4 Operating System WN DOS 20/00 (E1) 07/28/2004 README.PDF 10 / 11

11 Default setup values After corrupted checksum the BIOS will set its default to the following values: MAIN Diskette A: 1.44 MB 3,5" Primary Master: AUTO Primary Slave AUTO Secondary Master: AUTO Secondary Slave: AUTO Advanced Reset Configuration Data: NO Speaker Volume HIGH Large Disk Access Mode DOS Onboard LAN Boot Prom Quick Boot Mode Video output to COM3 Chipset Configuration Local Bus IDE adapter BOTH SMART Device Monitoring Boot-Video device ONBOARD PCI 2.1 Support ENABLED I/O Device Configuration Parallel port ENABLED Mode ECP Base I/O address 378 Interrupt IRQ 7 DMA channel DMA 1 Touch Screen Routing NO REROUTING Security Set Supervisor Password NO PASSWORD SET Power Power State STAY OFF Wake On LAN Wake On Modem Ring Wake On Time Wake On Time 00:00:00 Boot Hardware Monitor Boot Order Removable devices Hard drive Network boot README.PDF 11 / 11