Pre OS ACPI and PCI Tests
Last updated on September 22, 1999

Pre-OS ACPI and PCI Tests

The Pre-OS tests test the system hardware for compliance with the PCI 2.1 specification and the ACPI 1.0 specification. These tests are required for all PC 99 and SDG 2.0 submissions. These tests are run in Real Mode or Command Mode, and require you to boot off of floppy disks.

For a description of the each of the tests in the pre OS testing suites, see Pre OS Test Descriptions.

Your ACPI compliant test system must be configured as described in Setup for System Testing in order to complete the pre OS tests. Specifically, your test system must be set up as follows to run the pre OS tests:

  1. Your system must have a hard disk drive partition of at least 10 Megabytes, in FAT16 format. This drive should be designated C:.
  2. A hard disk drive partition in FAT 32 or NTFS format that is be at least as large as the system's physical RAM, with sufficient space to hold the hibernation file.

    For example: a system with 128 Megabytes (MB) of RAM would require a FAT 16 partition with 128 MB of free space.

  3. You must download the HCT 9.2 Beta 2 Web Update from the Test Kits page and install it on a PC in order to create the test floppies with MAKEDISK.BAT. This only applies to the system that will be used to make these floppies, which may not be the same as the test system.

Note: All of the Pre-OS tests (with the exception of ACPI Interrupt 15h) may fail if they have insufficient memory to hold the ACPI namespace data. If a test runs out of memory, it will exit and may end the testing run.

Note: For the pre OS tests, Test Manager is used to process the log files and to return results only.

Previews

As of the release of the HCT 9.2 Beta 2 Web Update, many of the Pre-OS tests have been moved to preview. Preview tests are not required at this time, but will be required in future releases of the HCT's. Failures in log files for preview tests should be considered warnings of future points of failure. The following Pre-OS tests are now preview:

Pre OS PCI Tests

The PCI tests require the Foxfire II PCI test adapter. For more information on the Foxfire II, please see the PCI Test Card FAQ. Always unplug the system before changing any settings on the Foxfire II card. You can damage your system by changing settings on PCI cards with power to the PCI bus. When you are instructed to cut power to the system in the instructions for the PCI test suite, that means power down the system and unplug it from the power outlet. You must fully populate your all available slots on your PCI bus(es) with Foxfire II cards in order to complete these tests. Available slots are empty slots, or slots occupied by add-in cards. All add-in PCI cards must be removed, including audio cards, NICs and modems. PCI Storage controllers should not be removed.

For the pre OS PCI tests, the following is required:

  1. The test system must be ACPI compliant and have a PCI bus with at least 3 PCI slots.
  2. At least 3 Foxfire II PCI test adapters (1 per available PCI slot in your system), which are used to test the PCI bus. Laptops cannot use the Foxfire II PCI test adapter, so the PCI tests are not required for Laptops.
  3. One set of cables, for connecting Foxfire II cards to each other (for the PCIPME2 test).
  4. A voltmeter, for measuring the voltage on the Foxfire II card manually.
  5. 2 IBM formatted floppy disks

Creating Test Floppy Disks

Before you can run the Pre-OS PCI testing suite, you will need to create the floppy disks that you will use to boot the system and to install the Pre-OS PCI testing suite. If you plan to run these tests before OS installation, you can create your floppies on another system that already has the OS installed, and is therefore able to access its CD-ROM drive.

  1. When you install the HCT 9.2 Beta 2 Web Update, the disk images are in the \posdisk\PCI folder in the update directory, set to c:\hctupd by default.
  2. In \hctupd\posdisk\PCI, run MAKEDISK.BAT. Insert a formatted floppy disk into drive A:\ and hit enter. Label this disk PCI disk 1. This disk is used to boot the test system while running the pre OS PCI tests.
  3. The disk setup utility now prompts you to insert a second floppy disk. Insert a formatted floppy disk into drive A:\ and hit enter. Label this disk PCI disk 2. This disk is used to copy the tests to the \PCITEST directory on your system.

Installing Foxfire II Cards in Your Test System

Be sure to cut power to your test system before installing Foxfire II cards into every available slot. When you install Foxfire II cards in your system, make sure that the dip switches are on each card are set as follows:
dip switch 1: ON
dip switch 2: OFF
dip switch 3: ON
dip switch 4: OFF

Before you run the PCI tests, you may wish to read the pre-os test descriptions (link).

To run the pre OS PCI Tests

  1. Follow the instructions above on creating test floppies and installing the Foxfire cards before proceeding to the next step.
  2. Start with your system powered down, but with power available.
  3. Insert PCI disk 1 into floppy drive A:\ and power on your test system. Disk 1 will boot the system into MS-DOS and then prompt you for Disk 2.
  4. Insert Disk 2 into floppy drive A:\ and press any key. Disk 2 will install the pre OS PCI tests on your system and then prompt you for Disk 1.
  5. Insert Disk 1 into floppy drive A:\ and press any key. Leave PCI disk 1 in floppy drive A:\ until you are done with the pre-os PCI tests. You will get this message: "To Abort, press Ctrl-C. To run PCI tests, press any key to continue." Press any key to begin the PCI tests.
  6. You will get a warning stating that each slot in the PCI bus must have a Foxfire II card, and instructing you to cut power to the system if this is not the case. Press any key to continue.
  7. PCIDUMP, PMDIAG, and PCICAP will all run now.
  8. For each device or controller PCICAP finds, (display, network, audio, modem) it will ask the following question:

    "Press 'y' if the following PCI device is integrated into the core chip set, press 'n' is the PCI device is on the motherboard or an add-in card: (lists (SSVID) vendor and (SSDID) device ID of device)".

    Press "Y" or "N" for each, depending on if the device is integrated into the core chipset.

  9. After PCICAP runs, you will get a message stating that you must do the following before you continue:
    1. Cut power to the test system.
    2. Set dip switch 2 on each Foxfire II card to the ON position.
    3. Return power to the system and reboot. Do not remove PCI disk 1.
  10. After you reboot, the BIOSINIT test will start. BIOSINIT will prompt you for the number of PCI slots on your bus. Enter the number of slots on your PCI bus and press Enter.
  11. BIOSINIT will run, and you will be prompted to reboot your system by pressing Ctrl + Alt + Delete.
  12. After your system reboots from floppy drive A:\, you will be prompted to press any key to continue. Press any key to continue. BIOSINIT completes, and you get a message stating that you must do the following before you continue:
    1. Cut power to the test system.
    2. Set dip switch 2 on each Foxfire II card to the OFF position.
    3. Return power to the system and reboot. Do not remove PCI disk 1.
  13. After you reboot, PCIVOLT starts and prompts you for the number of PCI slots in your test system. Enter the number of PCI slots in your test system and press the Enter key.
  14. You will get a message stating that a voltmeter is required to measure the voltage during the course of the PCI test. Press any key to continue.
  15. Attach the leads of the voltmeter to the points labeled "GND" and "3.3V" on each of the Foxfire test adapters, and make a note of the voltage on each adapter. Figure 1 shows to test the voltage across the GND and 3.3V pins shown in a blue box in the figure. If the voltage on every Foxfire II adapter is in the 3.0V - 3.6V range, press "y" to pass this test. Otherwise, press "n" to fail this test and continue with the pre OS PCI testing suite.
    Figure 1: Testing Voltage
  16. The 3.3Vaux test starts. Power off the test system by holding down the power button for 4 seconds (but do not cut power to the system), and inspect the LEDs labeled "3.3Vaux" on each Foxfire II card to verify that they are all lit, indicating that the PCI bus is receiving adequate power even when the system is powered down. After verifying that all 3.3Vaux LEDs are lit, turn the system back on.
  17. The system reboots from floppy drive A:\ . Press any key to continue.
  18. 3.3VAUX resumes. Press "y" if the 3.3Vaux LED was on for all Foxfire II cards while the system was shut down and AC power was supplied, or "n" if any of the 3.3Vaux LEDs were off. If you press "n", 3.3Vaux fails and the pre OS testing run resumes.
  19. The PCISID test starts. Press any key to enter system state 3 (S3), wait 10 seconds, and then press the power button to resume the test. Note: if the test system does not support S3, PCISID will exit without failing and resume the pre-OS testing run.
  20. After booting off floppy drive A:\, PCISID resumes and either passes or fails.
  21. The PCIPME1 test starts and prompts you for the number of PCI slots in your system. Enter the number of PCI slots in your system and press Enter.
  22. Press any key to initiate S3. Wait for 10 seconds and then press the pme momentary pushbutton switch (the white button) on the Foxfire II test adapter that is located on the slot closest to the center of the motherboard (slot 1) to awaken the system.
  23. Repeat the last step once per slot on the PCI bus. The second time you enter S3, press the momentary PME switch on the Foxfire II card in slot 2, the third time, press the PME switch on the card in slot 3. If you are unsure how the slots are numbered on your system, press the momentary PME on each card until the system returns from S3. When each PCI slot has been tested, PCIPME1 will resume and either pass or fail.
  24. The PCIWAKE test for system state 0 starts. Enter the number of PCI slots on your system and press Enter to enter system state 0 (S0). The monitor will remain powered in system state 0, until the system returns from S0 without user interaction. You are required to pass PCIWAKE for system state 0.
  25. After the system completes PCIWAKE, the following message is displayed:
    "Moving to preview tests. These tests are not required. If machine hangs, power-cycle & testing will resume at next test".
  26. PCIWAKEA starts. This test is a preview, so it will not be required until the next test kit is released. This test is the same as PCIWAKE, but tests system states S1-S3. Enter the number of PCI slots on in your system and press any key to continue.
  27. Wait at least 10 seconds, and then press the PME switch on each of the Foxfire II cards in your system until one of them generates the PME# signal which will wake up the system.
  28. Repeat steps 26 and 27 until all PCI slots have been tested with each system state. PCIWAKEA will test each of the system states that the system supports.
  29. The PCIVAUX test starts. This version of the test requires at least 3 cards. PCIVAUX tests each system state on each PCI slot as follows until each slot and system state combination have been tested:
  30. After PCIVAUX passes or fails, the Simultaneous PME# Signal Assertion Test (PME2) starts.
  31. Before you can run the PME2 test, you must power off the system, cut power to the system (unplug it), and daisy chain all the Foxfire II cards in the system together, which is most easily done when all Foxfire II cards are removed from the test system. To daisy chain the Foxfire II cards, use test clips to connect the leads labeled "ground" on each card to the "ground" leads on the other cards, and the leads labeled "PME Pushbutton" on each card to the "PME Pushbutton" leads on the other cards. See Figure 2 for details. When all cards have been daisy chained, pressing the PME pushbutton on any Foxfire card will cause all cards to create a PME# signal.
    Figure 2: Daisy-chaining FoxFire II Cards
  32. After re-inserting the Foxfire II cards, plugging the system in and turning it back on, press any key to put the system into sleep/hibernation.
  33. Wait at least 10 seconds, and then press the PME switch on any of the daisy chained Foxfire II cards to awaken the system. The system will return form sleep/hibernation, and either pass or fail.

You have completed the pre OS PCI testing suite.

Pre-OS ACPI Tests

The pre-OS ACPI tests test The Advanced Configuration and Power Interface tests validate implementations of the hardware and BIOS functionality requirements specified in the following documents:

Note: The only required hardware for these tests is 1 ACPI system and 2 IBM formatted floppy disks.

Note: The ACPIPBT and ACPIDPMT tests may cause memory allocation errors on some systems. If this happens and the system hangs, cold boot the system with floppy disk 1 in drive. This should restart the test suite with the next test.

Creating Test Floppy Disks

Before you can run the pre-OS ACPI testing suite, you will need to the create floppy disks that you will use to boot the system and to install the pre-OS ACPI testing suite. If you plan to run these tests before OS installation, you can create your floppies on another system that already has the OS installed, and is therefore able to access its CD-ROM drive.

  1. When you install the HCT 9.2 Beta 2 Web Update, the disk images are in the \posdisk\ACPI folder in the update directory, set to c:\hctupd by default.
  2. In c:\hctupd\posdisk\ACPI, run MAKEDISK.BAT. Insert a formatted floppy disk into drive A:\ and hit enter. Copy proceedes. Label this disk ACPI disk 1. This disk is used to boot the test system before running the pre-OS ACPI tests.
  3. The disk setup utility now prompts you to insert a second floppy disk. Insert a formatted floppy disk into drive A:\ and hit Enter. Label this disk ACPI disk 2. This disk is used to copy the tests to the \ACPITEST directory on your system.

To run the pre OS ACPI Tests

  1. Insert ACPI disk 1 into floppy drive A:\ and reboot your system. Disk 1 will boot into MS-DOS and and then prompt you for Disk 2.
  2. Insert ACPI Disk 2 into floppy drive A:\ and press any key. Disk 2 will install the Pre-OS ACPI tests on your system and then prompt you for disk 1.
  3. 3. Insert Disk 1 into floppy drive A:\ and press any key. Leave ACPI disk 1 in floppy drive A:\ until you are done with the pre-OS ACPI tests. The system boots off floppy drive A:\, and then runs through the following tests: ISACPI, I15HE820, E820 and ACPIDUMP.
  4. The ACPIDUMP test starts and dumps the ACPI namespace into memory. If there are problems with the ACPI namespace, ACPIDUMP will stop the pre-OS ACPI testing run. You must fix the problems reported by this test before you can continue with the pre-OS ACPI testing run. Contact your motherboard manufacturer for an updated BIOS.
  5. The ACPILAST test reboots the system from Floppy drive A:\, then resumes the testing run.
  6. The ACPIPBT test starts.
  7. Press and release the power button. You have 25 seconds to do this, otherwise, return to step 6.
  8. ACPIPBT verifies that no SCIs were generated and that PWRBTN_STS is correctly set.
  9. Press any key to continue.
  10. Press the power button. The system boots from floppy drive A:\.
  11. The ACPIPMT test starts, and the system boots from floppy drive A:\.
  12. The ACPIDMPT test runs without requiring user input.
  13. The CPUTHRTL test runs without requiring user input.
  14. After CPUTHRTL completes, press any key to continue.
  15. The ACPI4SEC test starts. Hold down the power button until the system shuts down. If the system shuts down within 4 seconds, this test passes. The ACPI4SEC test may fail to create a log file, for unknown reasons. If this happens, try running the ACPI test suite again, and the log file will probably be created the second time,
  16. Power on the system and boot off disk 1 in floppy drive A:. If you get the message "The ACPI Compliance Test Suite has completed. See AcpiMstr.log for test resultes summary.", you have completed the Pre-OS ACPI tests.

    17. Creating Log Files

    After running the ACPI and PCI pre-OS test suites, you will have to create NT log files for each test.

    1. Start HCT Test Manager.
    2. Navigate in the Test Manager tree to \System\Manual Tests\ACPI\Pre-OS\, and Add each of these tests to the Test Manager run.
    3. Navigate in the Test Manager tree to \System\Manual Tests\BUS\PCI\Pre-OS\, and Add each of these tests to the Test Manager run.
    4. Click Start to create log files for the pre OS testing suites.