PCI 2.1 BIOS

The test checks the PCI BIOS for 2.1 compliance, including checking for a valid IRQ routing table.

PCI 2.1 Cards

For each PCI device in the system, this test checks for compliance to the PCI 2.1 specification. The test reads the PCI configuration space for each PCI device in the system, verifying the following:

• The Class code, Vender ID, Device ID, and Header type are valid.
  If the core chipset silicon fails PCI Subsystem vendor ID and PCI Subsystem device ID checks, the errors can be ignored.
  
• Power Management Registers: On-board PCI devices need power management registers, unless they support power management using ACPI control methods. On-board PCI devices must support one of the two methods. If you do not have power management registers and there are failures marked 'extended capabilities' for a particular device that uses ACPI control methods, include the information in the submission package.
• That if the interrupt pin is set, then the card has a valid IRQ assigned; otherwise if the interrupt pin is not set, then the assigned IRQ is 0xFF (Unused).
  
  
• The configuration information of the Base Address Registers. For example, is the I/O length valid? Is the reserved register bit (0x01) on an I/O address set to 0x0? Is the Memory information correct?
  
  
• Read Only Bits: This verifies the card follows the PCI 2.1 specification on which bits in the configuration space need to be read-only. It will attempt to write to those bits, and expect them not to change.
  
  
• Current configuration status: This will attempt to write to the I/O decode enable bit of the command register to verify that the device is capable of disabling I/O access.
  
  
• Current configuration status: This will attempt to write to the Memory decode enable bit of the command register to verify the device is capable of disabling Memory access.
  
  
• For PCI 2.1 cards with header type 0, DWORD 0x2C is the subsystem vender and subsystem device ID. This is NOT allowed to be writeable.
  
  
• For PCI 2.1 CardBus controllers with header type 2, DWORD 0x40 is the subsystem vendor and subsystem device ID. This is NOT allowed to be writeable.
  
  
• For PCI 2.1 devices which request an IRQ, the BIOS must allocate an IRQ for that device to use.

Parameters

None.

Issues

The PCI cards now puts your system into standby mode, and then verifies that your SSVID and SSDID are not writable and are the same as before the system went into standby.

PCI Enumeration

This test evaluates automatic enumeration of PCI devices by first enumerating the current PCI devices in the system. It then prompts the user to input the number of currently open PCI slots in the machine. After the user inputs the appropriate number, the test displays further instructions and shuts down the system. After the system shuts down, the user must fill the remaining PCI slots with cards and power up the system. The test monitors the PCI enumeration on restart, verifying all inserted cards are automatically detected and that the drivers load properly.

Parameters

None.

PCI I/O Space

This test verifies the I/O ports for all PC Bridge devices start on a 4K boundary, and PCI devices are aligned on each 1K boundary within that block. There must be 256 I/O ports available. If more than one (1) bridge is installed, the 4K I/O boundaries of the bridges must be contiguous. Failures in this test are commonly caused by 10-bit decode ISA devices in the system, which are violations.

Parameters

None.

PCI Latency

The purpose of the PCI Latency test is to test device/driver combinations for compliance to the PCI Local Bus Specification revision 2.1. The checks that this test performs are based on the following sections of the PCI Local Bus Specification revision 2.1:

• 3.5.3 Arbitration Latency
• 3.6 Exclusive Access
  • 3.6.1 Starting an Exclusive Access
  • 3.6.2 Continuing an Exclusive Access
  • 3.6.3 Accessing a Locked Agent
  • 3.6.4 Completing an Exclusive Access
  • 3.6.5 Supporting LOCK# and Write-back Cache Coherency
  • 3.6.6 Complete Bus Lock
• 3.7 Other Bus Operations
  • 3.7.1 Device Specification
  • 3.7.2 Special Cycle
  • 3.7.3 Address/Data Stepping
  • 3.7.4 Configuration Cycle
  • 3.7.5 Interrupt Acknowledge
• 3.8 Error Functions
  • 3.8.1 Parity
  • 3.8.2 Error Reporting
• 3.9 Cache Support
• 3.9.1 Definition of Cache States
• 3.9.2 Supported State Transitions
• 3.9.3 Timing Diagrams
• 3.9.4 Write-through Cache Support
• 3.9.5 Arbitration Note
• 3.10 64-Bit Bus Extension
• 3.10.1 64-Bit Addressing on PCI
• 3.11 Special Design Considerations

This test also performs tests based on the PCI Local Bus Specification revision 2.1, Engineering Change Notification:

• 4.14.4 All PCI devices under test must complete the Target Initial Latency within the specified time. This time is specified in PCI clocks cycles as 16 clock cycles.
• 4.14.5 All PCI devices under tests that are host bridges are exempt from the Target Initial Latency requirements. They are instead required to complete the Target Initial latency within 32 clock cycles.
• 4.14.6 Target Initial Latency requirements are not in effect during the initialization time, which is defined as 2**25 PCI Clocks after the RST# signal is "deasserted."

Algorithm

This test tests the PCI latency of device/driver combinations, and tests the following assertions:

• Target Initial Latency: device/driver combination must start within 16 PCI clocks (PCI 2.1, section 3.5.1.1).
• Maximum Completion Time: device/driver combination must finish write transaction and stop using bus bandwidth within 10 milliseconds (approximately 334 PCI clocks) (PCI 2.1, section 3.5.3).

To Run the PCI Latency Test:

1. Before starting the systems HCTs, install the FoxFire II PCI Test Card.
   1. Power down the test system and disconnect it from the power socket.

      Caution: Installing a PCI card on the bus while a system is powered might damage the PCI card or the system. ACPI systems are powered even when they are "off".

   2. Install one (1) FoxFire II PCI Test Card in one of the slots on the test system's PCI bus 0.

      Note: If the FoxFire II card is not installed on bus 0, failures of devices on bus 0 will not be detected by the PCI Latency test.

2. After running all other required tests, run the PCI Latency test.
   1. Start the HCT test manager.
   2. Expand System -> BUS -> PCI, and double-click PCI Latency.
   3. Click the Start button to run the test.

Issues

This test requires one (1) FoxFire II PCI Test Card, which must be in one of the slots on the test system's PCI bus. This card must be installed prior to running the systems HCT Kit. This test is not designed for mobile systems.

CardBus Enumeration

This test evaluates automatic enumeration of CardBus devices by first enumerating the current CardBus devices in the system. It then prompts the user to input the number of currently open CardBus slots on the machine. After the user inputs the appropriate number, the test displays further instructions and an "OK To Continue" dialog. This dialog must NOT be cleared until after the user fills the remaining CardBus slots with devices, and waits for the devices to enumerate properly. The test monitors the dynamic CardBus enumeration, verifying all CardBus devices are automatically detected and that the drivers load properly.

Note: The PCI enumerator enumerates CardBus cards, thus the log file will show a mixture of CardBus and PCI devices from this test run.

Parameters

None.

USB Manual Tests

Note: these Test Procedures have been changed from HCT 9.0/9.1

The USB manual test suite consists of several tests. For each test you must follow the test procedure and select either "N/A", "Pass", or "Fail" before selecting the next test. After have completed the USB manual test procedures, select "Exit" from the File menu. The USB Manual Test procedures dialog will close and your test results will be recorded in the usb.tst.log logfile. You must use the equipment specified in the Test Tools and Equipment section of this procedure (or its logo'd equivalent) to perform these tests.

Test Tools and Equipment

The following equipment is needed to perform these tests:

• USB Natively equipped Pentium II, 300 MHz or higher system with a USB host controller. ACPI must be enabled on the Test system.

  Note: Systems must have a Plug and Play BIOS set to auto configure mode.

• The USB host controller must be able to wake the system using ACPI mechanisms (required for PC 99).
• 3 Peracom USB Quad Hub 4 port Self/Bus powered hubs (for more information visit http://www.peracom.com/) or Other PC99 Logo'd self/bus powered hub. Peracom USB Quad Hub 4 port Self powered hubs
• 1 Hewlett Packard HP ScanJet 4100C USB Scanner (for more info visit http://www.hp.com)
• 1 Logitech USB Wheel Mouse or Microsoft USB Wheel Mouse.
• 1 Intel USB Create and Share Camera Pack (for more info visit http://www.intel.com/createshare/crshare.htm) or Logitech QuickCam Home (for more information visit www.logitech.com).
• 1 ThrustMaster Top Gun USB joystick (for more info visit http://www.thrustmaster.com) or Microsoft USB 3D Pro Joystick.
• 1 Philips USB DSS37017 Speaker Set (for more info visit http://www.philipsmagnavox.com) or Altec Lansing USB ADA70 Digital Power Cube Speakers (for more information visit http://www.altecmm.com/).

  Note for device substitution: If you must substitute a device, make sure that you follow the Test Procedures as defined, taking into account the substituted device. Note for locating devices: If you cannot obtain the above devices in your locale, you may substitute devices from the hardware compatibility list (HCL) located at http://www.microsoft.com/hwtest/hcl. You must substitute devices with others of the same class.

  Start the USB Manual Test from Test Manager and follow the instructions.

  After selecting N/A, Pass or Fail for each test in the USB manual testing suite, select File -> Exit. your test results are recorded in usb.tst.log.

  ---

  USB Enumeration

  
  

  Type	Interactive
  Operating system	Windows 95 & 98
  Log filename	devenum.log
  Processing time	Approximately 10 minutes
  Status	Required
  Included in these HCTs:	8.x, 9.x

  This test evaluates automatic enumeration of USB devices by first enumerating the current USB devices in the system. It then prompts the user to input the number of currently open USB slots on the machine. After the user inputs the appropriate number, the test displays further instructions and an "OK To Continue" dialog. This dialog must NOT be cleared until after the user fills the remaining USB slots with devices, and waits for the devices to enumerate properly. The test monitors the dynamic USB enumeration, verifying all USB devices are automatically detected and that the drivers load properly.

  Parameters

  None.

  ---