| |
With this new release, General Software has sought to bring the many elements of their extensive BIOS support into a structured framework, enabling engineers to easily and efficiently configure the necessary libraries and functionality that they need for a new x86 board design. Over the coming months General Software will introduce pre-configured versions of EBSF that will address the needs of specific industry applications, such as software security in gaming systems, to further reduce the time needed to get a new product design to market.
Whether it's a short boot up time, tight software security or custom self-test that is required, engineers will be able configure exactly what they need much more easily than before. BIOS developers can produce working prototypes in days, and finish deployments in weeks, thanks to the new core's configuration management that uses intuitive descriptive methods and procedures to build the BIOS image rather than assembly language directives that have been the standard approach to-date.
While assembly code is still used for fine detailed control over the configuration, objects like ACPI, MP, and PCI tables are automatically constructed, as are Setup screens and their fields, based on descriptions of the target entered by the developer. With much less assembly code to control, OEM customers can achieve results much earlier in the development process while at the same time reduce the amount of BIOS code that must be adapted manually. Being able to develop at the functional module level rather than at code level for individual components, it greatly simplifies and shortens the system validation stage of the project.
Embedded BIOS 2000 also has the right business model for embedded. Unlike desktop PC BIOSes, Embedded BIOS 2000 has been designed for embedded ODMs and OEMs, who have completely different volume, lifecycle, and support requirements than PC OEMs. Embedded BIOS 2000 is also the right choice from a business perspective .
Product Overview
Embedded BIOS 2000 is an OEM-configurable firmware layer that provides the essential functions needed by operating systems and applications for PC-compatible embedded systems, consumer electronics, telecommunications and data communications devices, Single Board Computers, point-of-sale terminals, kiosks, thin clients and pads, industrial automation devices, and other embedded devices.
Embedded BIOS 2000 offers the most comprehensive on-target features of any BIOS software in the world. Support for industry-standard initiatives like APM, ACPI, "El Torito" CDROM boot, PCI, Plug-n-Play, PXE, SMBIOS, SMM, SMP, and Legacy USB is included. In addition, you'll find embedded innovations like headless and remote console operation, burn-in diagnostics, a built-in debugger, remote access disk and Flash updating, on-target BIOS reflashing, solid-state disk emulators, and optional multimedia (graphical and/or audio) POST. Standard parts of the architecture provide for OEM-configurable POST, dynamic OEM-written policy at the board design level, chipset, Super I/O, and CPU configuration, and a comprehensive setup screen system. The ability to boot Windows NT, Windows CE, Windows 95, Windows 98, Windows 2000, Windows ME, Windows XP, Linux, and other industry-standard operating systems is provided.
From the OEM's perspective, Embedded BIOS 2000 offers an outstanding software development architecture that allows the OEM to support multiple ongoing software adaptations while leveraging existing libraries of chipset, CPU, and board-specific BIOS features. BIOS adaptation -- the process of configuring the system firmware for a specific target -- is project file-based and can be totally automated with BIOStart, the Windows-based configuration management tool.
Although it is most common to adapt the BIOS using the high-level tools provided, Embedded BIOS 2000 comes as a full source code kit. This complete solution allows the OEM the extra advantage of having no black boxes in the system. It also makes it possible for the adaptation process to only generate absolutely necessary code in the final BIOS image, minimizing the size of the BIOS.
As a licensed product, Embedded BIOS 2000 offers outstanding value. Each licensed copy includes all of the features that can be enabled in the adaptation process. Embedded BIOS 2000's rich feature set makes it possible to handle most of the system's low-level requirements without contacting several vendors for different pieces. This integrated approach makes the OEM-customized version of the BIOS the virtual nerve center of the entire embedded system, and a foundation for the 32-bit Firmbase environment.
Benefits
Embedded BIOS 2000 lowers the costs associated with developing, testing, and maintaining embedded devices by providing standard features that drive these costs down. For example, the Embedded BIOS 2000 project file architecture, and its package plug-ins, provide a way to segment project development and allow cooperative, concurrent development of firmware among team members, and across multiple projects. Embedded BIOS 2000 provides automated testing suites that can reduce the need to write diagnostic test software for Q/A. And, Embedded BIOS 2000 provides for in-field reflashing and remote target control.
Embedded BIOS 2000 also reduces the risks associated with developing new products. Firmware is often the leading cause of project slippage in designs using a desktop BIOS, because those firmware products are not designed to be adapted to support the kinds of customization that embedded developers need. Embedded BIOS's project file architecture, its modular Board, Chipset, and CPU Personality Modules, and its support for third-party package modules, makes it possible for the OEM to use and reuse larger building blocks, rather than customize core files for each new project.
Target Features
Embedded BIOS 2000 leads the industry with all the on-target features that ODMs and OEMs need for modern embedded development:
Embedded Features (all OEM-configurable):
- Quick boot with sub-second POST
- Integrated BIOS-aware debugger
- Resident Flash disk emulator
- ROM disk and RAM disk emulators
- Remote access Flash programming
- Remote access disk redirection
- System Management Mode (SMM)
- Traditional, headless, or multimedia POST
- Console redirection (ANSI)
- HTML browser front-end
- CE Ready, the Windows CE launcher
- Native RTOS loader
- Legacy USB keyboard and mouse
- Booting from USB mass storage devices (sold seperately):
- Floppy Disk Drive (optional)
- Hard Drive (optional)
- CD-ROM (optional)
- USB Hub Support
- Support for up to 8 USB Keyboards and 8 USB Mice
- Matrix keyboards
- LCD panels
- Watchdog timer
- Burn-in Diagnostics
- Installable disk servers
- OEM-configurable setup screens
- Compatibility with operating systems and networks
- Supports embedded chipsets with add-on Chipset Personality Modules
- Supports embedded CPUs with add-on CPU Personality Modules
- Supports embedded reference designs with add-on Board Personality Modules
- Up to 64 Gigabytes of RAM with quick, standard, or exhaustive testing
- Embedded PCI option ROMs
- Embedded ROM extensions
- Legacy-free configuration -- supports elimination of legacy PC/AT hardware
- Automatic (on-the-fly) IDE detection
- ATA 133 (UDMA6) compatibility for advanced PIO/UDMA
- Hard drives over 138GB
- Full multiprocessing support
- APIC and IOAPIC support
- PCI with up to 256 interrupt lines, arbitrary topologies
- Six-stage boot sequencing, including command line interpreter, and debugger
- CMOS or CMOS-less designs
- Packages support third-party, add-on modules
- Message-passing driver architecture supports dynamically-configurable POST
Industry Standards (all OEM-configurable):
- Advanced Power Management (APM) Specification 1.2
- Advanced Control and Power Interface (ACPI) Specification 2.0
- POST Memory Manager (PMM) Specification 1.01
- Plug-n-Play Specification 1.0A
- Multiprocessor Specification SMP 1.4
- SMBIOS Specification 2.3.1 (formerly DMI)
- CD-ROM Boot "El Torito" Specification 1.0
- PCI Specification 2.2
- PXE Specification
- BIOS32 Specification
- Enhanced Disk Drive Specification 1.1
- Firmbase Specification 1.3
Standard BIOS Features (all OEM-configurable):
- DRAM detection & configuration
- ROM shadowing
- Option ROM calls
- Cache control
- CPU speed control
- Microcode update
- PC/AT glue logic supported natively (8259, 8237A, 8254, 8042, etc.)
- Standard FDC, ATA drivers
- PC/XT, PC/AT keyboard drivers
- 6845 video driver
- ROM footprint from 32KB-512KB, OEM-configurable
Silicon Support
The leading x86 silicon vendors have deployed Embedded BIOS 2000 as the standard firmware on their embedded evaluation platforms for years, and Embedded BIOS 2000 is their standard bring-up BIOS of choice when developing their new embedded reference designs. Working closely with its silicon vendor partners, General Software is able to provide Embedded BIOS 2000 support modules for all major embedded processors and chipsets, including:
- Acer Labs
- AMD
- Intel
- National
- RadiSys
- ServerWorks
- STMicroelectronics
- Transmeta
- VIA
Operating System Support
General Software works with all the leading operating system vendors to ensure Embedded BIOS 2000 includes the latest industry standards that can drive the industry's embedded and general-purpose operating systems into embedded markets. Embedded BIOS 2000 is compatible with:
- DOS
- Windows 95
- Windows 98
- Windows ME
- Windows NT
- Windows NT 4.0 Server
- Windows NT Embedded
- Windows CE
- Windows 2000
- Windows XP
- Windows XP SP1
- Windows XP SP2
- Windows XP Embedded
- Windows 2003 Server
- Linux
- QNX and other Real Time Operating Systems
Note: Not all platforms can support all operating systems; restrictions may apply, depending on the chipset, CPU, and board-level hardware design. For details, contact SDC Systems.
|
|
| |
Firmbase® Technology
Firmbase Technology is General Software's patented 32-bit firmware infrastructure that contributes the surety and trust expected from firmware applications.
From a surety standpoint, Firmbase Technology provides the non-stop SMM envelope that keeps Firmware Applications running, even when the OS and user application have failed, or are missing. Firmbase is ROM-resident, ever-present, never crashes, and always works. In the 1980's we had robustness. In the 1990's we had high availability. Surety is a broader and more encompassing concept. When you use Firmbase, you can be sure that your device will keep on going, as long as there is still power.
From a trust standpoint, Firmbase Technology provides a chain of trust from power-on to OS boot. It supplies the user-level security for the BIOS and for firmware applications which don't run under control of the OS. It then provides the technology through which user applications communicate to firmware applications.
Firmware Application Suite
General Software provides firmware applications built on Firmbase® Technology, allowing them to run on any Firmbase Technology-enabled platform.
Platform Update Facility
Platform Update Facility updates a system's firmware, CMOS, and mass storage content either automatically or under control of a remote administration user community.
High Availability Monitor
High Availability Monitor monitors the health of a running system and automatically takes corrective actions when health deteriorates. HA Monitor is remote manageable and configurable for automatic and unattended operation.
Boot Security Application
Boot Security Application provides a chain of trust from the hardware to the OS and application through cryptographic challenges, ensuring that the application, hardware, and firmware are genuine.
|
|
|
Platform Update Facility The Platform Update Facility is a firmware application that allows manual replacement of upgradeable system components at any time during its operation. It can upgrade disk partitions, files within partitions, CMOS contents, and Flash memory.
This application can also operate automatically, checking selected upgradeable system components on each boot, and downloading and replacing them with new data as needed, based on ODM/OEM policies. This same automatic update can be triggered by conditions such as OS system death, or when failures are signaled by the diagnostics suite.
To accomplish this, the Platform Update Facility uses MD5 crypto-based hashes of objects, eliminating costly boot-time delays. The definitions of updateable objects are specified by the ODM/OEM in a ROM-resident policy database. Standard Firmbase Technology TCB user-level security is provided on all objects. And, this facility is remotely manageable with any web browser, over the internet.
Common applications include loading the OS and application during the manufacturing process; updating the OS, application, and BIOS images on devices in the field; repairing software on devices in the field; and backup/restore operations of partitions, files, CMOS, and Flash memory in the target.
High Availability Monitor
General Software's High Availability (HA) Monitor provides the surety your embedded system needs to autonomously detect and correct problems in the field- including OS crashes, degraded hardware performance, and failing hardware.
Built on Firmbase® Technology, HA Monitor is a firmware application that continuously monitors the foreground operating system and application, verifying that it has not crashed. When crashes such as Blue-Screens or Black Screens or Panics occur, HA Monitor generates an OS System Death HA event, which can be configured by the ODM/OEM to perform specific functions, including logging the failure to a system event log, sending an alert over the network, triggering the Platform Update Facility to reload known-working software and firmware, and rebooting the target.
To accomplish this, HA Monitor uses Firmbase Technology's HA infrastructure, becoming a key producer of HA information as it scans the health of the foreground operating system, and a consumer of the resulting actions broadcast by the Firmbase kernel's HA subsystem according to the policies set forth by the ODM/OEM.
Fine-tuned, proprietary techniques are used to detect OS System Death in Windows systems, for those systems running Windows 98, Windows NT, Windows XP, or Windows XP Embedded. Common failures, such as Blue-Screen or Black-Screen conditions, are detected, along with other more general conditions, such as when interrupts are pending but are not being serviced within the tolerances specified by the ODM/OEM.
HA Monitor can be remotely managed over the local network or Internet with any web browser or Telnet connection. Standard Firmbase Technology TCB user-level security is provided on remote administration.
Common applications include limiting down time to quantifiable levels (i.e., five 9's, six 9's, etc.) and ensuring users never witness an internal OS failure on visible monitors.
Boot Security Application
The Boot Security Application is a firmware application that establishes trust between platform hardware and the user application, preventing operation of systems compromised by unauthorized tampering with BIOS, OS, or application with cryptographic signatures on all trusted objects.
Supporting both Linux and Windows, the Boot Security Application requires the user application running under Linux or Windows to periodically (as defined by a policy established by the ODM/OEM in the system registry) request security challenges and provide challenge responses, convincing the Boot Security Application, which represents the hardware and firmware, that the application is genuine. Similarly, the Boot Security Application responds to out-of-band challenges as requested by the user application, to convince the user application that it is running on genuine hardware and firmware.
In addition to establishing mutual trust between application and hardware/firmware with cryptographic challenges, the Boot Security application can also verify that the OS and application files have not been tampered with, prior to allowing the BIOS transfer control to the OS at system startup. The ODM/OEM can specify lists of files that are cryptographically hashed, and those hashes are matched against known hash values. Any changes to the files as a result of tampering can cause the Boot Security application to raise a security violation.
The Boot Security application can also be configured to establish that the rest of the firmware in the system has not been tampered with by cryptographically hashing the boot ROM containing the BIOS. Any changes to protected areas of the BIOS ROM can cause the Boot Security application to raise a security violation.
When this protocol breaks, the Boot Security Application can be directed by a policy established by the ODM/OEM in the system registry to generate alerts over the network, run an OEM application, and log the events to mass storage. It can also trigger the Platform Update Utility to automatically reload trusted software. Standard Firmbase Technology TCB user-level security is provided on administrative remote access. And, this facility is remotely manageable with any web browser, over the internet.
Common applications include tamper-proof BIOS, OS, and user application/data on ODM/OEM hardware; and eliminating the possibility that the user application might be run successfully on non-authorized hardware.
|
|
