1. lxMicSMC

1.1. Overview

Copyright (c) 2011-2015 Intel Corporation. All rights reserved.

Version Number 2.22.1.0001
Released:	02/12/2015

Purpose
This test module sends IPMI Commands to the Baseboard Management Controller (BMC) on supported server systems, 
once the IMB or IPMI0 driver is installed. The IPMB command is passed on to the SMC on the Many Integrated Cores 
(MIC) PCI-e card.

Runtime Environment
The Intel(R) Modular Test Architecture Test Executive for Linux template module.

License Agreement
All code is under the Intel(R) software License which can be found at http://legal.intel.com. A copy of this agreement 
must be included if code is released outside Intel.






1.2. Version Info

 
Date	Version		Owner		Comments
11/02/2011	2.01.0.0001	SLK/RK		Initial release
11/28/2011  	2.01.1.0001 	SLK		Formal release
03/29/2012	2.02.1.0001	SLK		Added support for SMC completion code.  
					Added SMC Firmware version check.          				
		Now verifies MIC presence, using SMC completion codes.
04/14/2012	2.03.1.0001	SLK		Added SEL support: check, add, clear. 
					Added FRU verify and FRU read support.
					Added Exit Manufacturing Mode support.
06/25/2012	2.04.1.0001	AYK/SLK	Added Analog and Discrete sensor tests.
					Added support for multiple SMC cards.
					Added SEL monitor test.
					Added SEL entry interpretation. 
07/26/2012	2.05.1.0001	AYK		Support for SMC FW version 1.4 or later. 		
09/17/2012	2.07.1.0002	SLK		Added fan control test
			AYK		Added SDR reporting test (list all SDR data)	
11/05/2012	2.08.0.0004	SLK		Added manufacturing date and Serial Number checks to 
MicVerifyFRUData
11/30/2012	2.09.1.0005	SLK		If Exit Mfg Mode returns C1h, it indicates Mfg Mode is already exited - 
removed error.
					Updated "BMCNumberOfRetries" from 2 to 4. This will mainly impact 
Auto-Configuration 
					for devices which are not installed on the current system - but increases 
overall stability.
					Added a little more detail to SMC return codes C1h, 80h and 82h.	
01/04/2013	2.11.1.0006	SLK		Adjusted to retry for all non-zero BMC return codes, in addition to 82h. 
Was already
					retrying for all non-zero SMC return codes.	
01/17/2013	2.12.1.0012	SLK		Checked for non-ASCII characters in SDR device names.
					Adjusted algorithm for SMC FW < 1.4 needing different SDR offsets.
					Interpreted SMC FW version differently.
01/29/2013	2.13.1.0014	SLK		Added BMCPrintRetryInfo parameter and functionality
02/25/2013	2.14.1.0001	AYK/SLK	IPMI0 driver support	
04/11/2013	2.15.1.0001	KB/SLK	Added Report and Check Manufacturing Mode test and parameter 
MicMfgModeState. 
					Fixed fan control test to return control to SMC after calling 
MicCheckFanControl.
04/29/2013	2.16.1.0001	SLK		Fixed MicSendReqToSMCViaIpmiDrive to
					 return correct resp_len
07/23/2013	2.17.1.0001	SLK		Expanded MicCheckFanControl to regardless of manufacturing mode 
state
09/10/2014	2.18.1.0001 DJJ		Added method to programmatically determine, via the BMC, the total 
number
					of MIC cards installed along with determining each MIC card PCIe IMPI 
slot number based
					its MIC card number. Fixed BMC IPMI communcation issue. Fixed SMC 
IPMI retry looping/error
					handling. Fixed driver selection mechanism so that IPMI0 driver is 
defaulted to if driver
					parameter is invalid.
10/18/2014	2.19.1.0001 DJJ		Added MicDisplayVRPhases utility. Added MicCheckVRPhases test.
12/10/2014	2.20.1.0001 DJJ		Modified MicCheckVRPhases test to check phase standard deviation 
variation.
					Added routine to overwrite key VR phase monitoring parameters during 
autoconfig via a
					VR phase monitoring SKU info parameter array.
01/14/2015	2.21.1.0001 DJJ		Modified MicCheckVRPhases test phase standard deviation variation 
limit checker to
					accept either signed number values or absolute values as parameters. 
Added ability
					to check combinations of minimum, maximum, and delta standard 
deviation units.
					Added VR Standard Deviation Methods B, C, and D. Added VR delta 
percentage of total
					test method. 	Added parameter to enable either the current or legacy 
(version 2.17 or
					earlier) SMC IPMI error retry looping/error handling mechanism.
03/06/2015	2.22.1.0001 DJJ		Fixed IPMI retry error (IPMICTL_RECEIVE_MSG_TRUNC). Cleaned up 
VR phase
					info block message. Added optional delta recalculation for phase deltas 
that fail with high phase
					minimum values.	
							

1.3. Installation

Files needed to run this module:
	
File	Description
lxMicSMC	Executable image.
lxMicSMC.snx	Configuration file.
lxMicSMC.txt	Text only help file.
lxMicSMC.chm	Smart help file.

In addition, either the Linux IMB driver or the MonteVista IPMI0 driver must be installed, and the host board BMC must 
support the BMC to SMC communication. Please see project contact for a list of supported host boards. This release 
was tested on Intel Workstation Board W2600CR2.

IPMI0 driver configuration:
	RedHat : RedHat installation requires the following scripts to be run in this order for IPMI) driver to be configured 
correctly:
	 ipmi.sh
	 ipmi_setup.sh
   NOTE: if bash interpeter reports "bad interpreter: No such file or directory" dos2unix will have to be run on both ipmi.sh 
and ipmi.sh .
		To do this in bash type: "dos2unix ipmi.sh" and "dos2unix ipmi_setup.sh"

	SUSE : This configuration step is not required on SUSE installations, as the IPMI0 driver is installed by default.

1.4. Sub-Tests


Test 0	Auto-Configuration

Test 1	MicCheckSELErrors

Test 4	MicDisplaySELEntries

Test 5	MicReadSensorAndDisplay

Test 6	MicReadSensorQuiet

Test 7	MicSensorEventStatus

Test 8	MicCheckSensorThresholds

Test 9	MicDisplaySDR

Test 20	MicGetDeviceInformation

Test 22	MicCheckDeviceGUID

Test 34	MicAddSELEntry

Test 35	MicGetSELTime

Test 36	MicSetSELTime

Test 37	MicClearSEL

Test 50	MicVerifyFRUData

Test 51	MicReadFRUData

Test 60	MicExitManufacturingMode

Test 61	MicSMCColdReset

Test 62	MicCheckFanControl

Test 63	MicReportMfgState

Test 64 	MicCheckMfgState

Test 80 	MicDisplayVRPhases

Test 81 	MicCheckVRPhases




1.5. Test 0 - Auto-Configuration

Overview

This test is checks for the existence of the MIC SMC by communicating with it via the BMC on the host board. If not 
found, the test will remove itself. Otherwise, it saves the configuration information: Device ID, SMC Firmware version, 
various support flags, and FRU data, including manufacturer name, model number, and product name.

Parameter(s)

The following parameters are written by this test:

MicSMCDeviceID
MicSMCFirmwareVersion
MicSMCFRUsupport
MicSMCSELsupport
MicSMCSDRsupport
MicSMCSensorSupport
MicFRUManufacturerName
MicFruModelNumber
MicFRUProductName
MicFanTach40
MicFanTach100
Analog Sensors_<Sensor Name>_SensorNumber
Analog Sensors_<Sensor Name>_SDRRecID
Analog Sensors_<Sensor Name>_ThresholdSupport
Analog Sensors_<Sensor Name>_UpperCriticalThreshold
Analog Sensors_<Sensor Name>_LowerCriticalThreshold
Discrete Sensors_<Sensor Name>_SensorNumber
Discrete Sensors_<Sensor Name>_SDRRecID

The following parameters are used by this test:
MicRdSlot
MicRdAddr
MicRdBus
IPMIDriver
BMCNumberOfRetries
BMCWaitBetweenRetries
BMCPrintRetryInfo

Test Execution Time

This test takes approximately 2 seconds to execute.

Dependencies/Limitations

If the BMC is not detected on the host board, or the host board does not support BMC to SMC communication, or the 
driver designated in parameter IPMIDriver is not installed, or the MIC card cannot be found in the specified PCIe slot, or 
the SMC on the MIC card does not respond, the test will remove itself.





1.6. Test 1 - MicCheckSELErrors

Overview

This test gets the SEL Info, reads SEL records and checks the SEL records for unexpected SEL events. Expected SEL 
events can be masked with EVMMaskXX parameters. All unexpected events are reported as errors.
To view all messages as informational only, see MicDisplaySELEntries.

Parameter(s)

The following parameters are used by this test:
MicRdSlot
MicRdAddr
MicRdBus
IPMIDriver
BMCNumberOfRetries
BMCWaitBetweenRetries
BMCPrintRetryInfo

Optional Parameters:
EVMMaskXX
EVMMask_Count

Test Execution Time

Test time depends on the number of events in the SEL.

Dependencies/Limitations

If the BMC is not detected on the host board, or the host board does not support BMC to SMC communication, or the 
driver designated in parameter IPMIDriver is not installed, or the MIC card cannot be found in the specified PCIe slot, or 
the SMC on the MIC card does not respond, the test will remove itself.

Check if the expected SEL records are masked with EVMMaskXX parameters. If this test is run after the  
CheckAnalogSensors subtest or the SEL repository is not cleared for long period of time, run MicClearSEL utility to 
clear the SEL repository and retry this test





1.7. Test 4 - MicDisplaySELEntries

Overview

This test gets the SEL Info, reads SEL records and checks the SEL records for unexpected SEL events. Expected SEL 
events can be masked with EVMMaskXX parameters. All found events are reported as information messages. To report 
them as error messages, see MicCheckSELErrors.

Parameter(s)

The following parameters are used by this test:
MicRdSlot
MicRdAddr
MicRdBus
IPMIDriver
BMCNumberOfRetries
BMCWaitBetweenRetries
BMCPrintRetryInfo

Optional Parameters:
EVMMaskXX
EVMMask_Count

Test Execution Time

Test time depends on the number of events in the SEL.

Dependencies/Limitations

If the BMC is not detected on the host board, or the host board does not support BMC to SMC communication,or the 
driver designated in parameter IPMIDriver is not installed, or the MIC card cannot be found in the specified PCIe slot, or 
the SMC on the MIC card does not respond, the test will remove itself.

Check if the expected SEL records are masked with EVMMaskXX parameters. If this test is run after the  
CheckAnalogSensors subtest or the SEL repository is not cleared for long period of time, run MicClearSEL utility to 
clear the SEL repository and retry this test





1.8. Test 5 - MicReadSensorAndDisplay

Overview

This test reads the value of the selected analog or discrete sensor. It also interprets the assertion and de-assertion event 
conditions taking into consideration the type of sensor and the event flags associated with the specific sensor. The test 
displays the information to the screen. 

Parameter(s)

The following parameters are used by this test:
MicRdSlot
MicRdAddr
MicRdBus
IPMIDriver
BMCNumberOfRetries
BMCWaitBetweenRetries
BMCPrintRetryInfo
Analog Sensors_<Sensor Name>_SensorNumber
Analog Sensors_<Sensor Name>_SDRRecID
Discrete Sensors_<Sensor Name>_SensorNumber
Discrete Sensors_<Sensor Name>_SDRRecID

Test Execution Time

Test time is about 1 second

Dependencies/Limitations

If the BMC is not detected on the host board, or the host board does not support BMC to SMC communication,or the 
driver designated in parameter IPMIDriver is not installed, or the MIC card cannot be found in the specified PCIe slot, or 
the SMC on the MIC card does not respond, the test will remove itself.







1.9. Test 6 - MicReadSensorQuiet

Overview

This test reads the value of the selected analog or discrete sensor. It also interprets the assertion and de-assertion event 
conditions taking into consideration the type of sensor and the event flags associated with the specific sensor. The test is 
similar to the MicReadSensorAndDisplay test but is quiet and does not display any output. 

Parameter(s)

The following parameters are used by this test:
MicRdSlot
MicRdAddr
MicRdBus
IPMIDriver
BMCNumberOfRetries
BMCWaitBetweenRetries
BMCPrintRetryInfo
Analog Sensors_<Sensor Name>_SensorNumber
Analog Sensors_<Sensor Name>_SDRRecID
Discrete Sensors_<Sensor Name>_SensorNumber
Discrete Sensors_<Sensor Name>_SDRRecID

Test Execution Time

Test time is about 1 second

Dependencies/Limitations

If the BMC is not detected on the host board, or the host board does not support BMC to SMC communication,or the 
driver designated in parameter IPMIDriver is not installed, or the MIC card cannot be found in the specified PCIe slot, or 
the SMC on the MIC card does not respond, the test will remove itself.






1.10. Test 7 - MicSensorEventStatus

Overview

This test gets the sensor event status and interprets the assertions/ de-assertion event conditions associated with the 
specific sensor. 

Parameter(s)

The following parameters are used by this test:
MicRdSlot
MicRdAddr
MicRdBus
IPMIDriver
BMCNumberOfRetries
BMCWaitBetweenRetries
BMCPrintRetryInfo
Analog Sensors_<Sensor Name>_SensorNumber
Discrete Sensors_<Sensor Name>_SensorNumber

Test Execution Time

Test time is about 1 second

Dependencies/Limitations

If the BMC is not detected on the host board, or the host board does not support BMC to SMC communication,or the 
driver designated in parameter IPMIDriver is not installed, or the MIC card cannot be found in the specified PCIe slot, or 
the SMC on the MIC card does not respond, the test will remove itself.







1.11. Test 8 - MicCheckSensorThresholds

Overview

This test verifies that the analog sensor is operating in the normal region defined by its thresholds. This test is applicable 
only for threshold based sensors and will be enabled only in the "Analog Sensors" list. It reads the current sensor reading, 
checks whether threshold support is available for this specific sensor and checks whether the upper critical or lower 
critical threshold values are crossed. 

Parameter(s)

The following parameters are used by this test:
MicRdSlot
MicRdAddr
MicRdBus
IPMIDriver
BMCNumberOfRetries
BMCWaitBetweenRetries
BMCPrintRetryInfo
Analog Sensors_<Sensor Name>_SensorNumber
Analog Sensors_<Sensor Name>_ThresholdSupport
Analog Sensors_<Sensor Name>_UpperCriticalThreshold
Analog Sensors_<Sensor Name>_LowerCriticalThreshold

Test Execution Time

Test time is about 1 second
.
Dependencies/Limitations

Baseboard Management Controller must exist in the UUT and the driver designated in parameter IPMIDriver has to be 
installed for this test to execute successfully. This test is dependent on the correct SDR records are loaded in the system, 
and the sensors are operating within the threshold boundaries set in their SDR records.  







1.12. Test 9 - MicDisplaySDR

Overview

This test goes through the SDR repository and displays the following information about each SDR record : 
	SDR record ID
	SDR Type (Full sensor or Discrete)
	Sensor number
	Sensor Name
This is a utility for getting a list of all sensors available on the specific MIC card. This test is disabled by default. 

Parameter(s)

The following parameters are used by this test:
MicRdSlot
MicRdAddr
MicRdBus
IPMIDriver
BMCNumberOfRetries
BMCWaitBetweenRetries
BMCPrintRetryInfo

Test Execution Time

Test time is about 1 second
.
Dependencies/Limitations

Baseboard Management Controller must exist in the UUT and IMB driver must be installed in OS for this test to execute 
successfully. This test is dependent on the correct SDR records are loaded in the system, and the sensors are operating 
within the threshold boundaries set in their SDR records.  







1.13. Test 20 - MicGetDeviceInformation

Overview

This test checks the ability of the BMC on the host board to communicate with the SMC on the MIC card and retrieve 
the Device ID, SMC Firmware Version and various support capabilities of the MIC SMC. It then compares those values 
with the expected values, and fails if they do not match.

Parameter(s)

MicSMCDeviceID
MicRdBus
MicRdSlot
MicRdAddr
IPMIDriver
MicSMCFirmwareVersion
MicSMCFRUsupport
MicSMCSELsupport
MicSMCSDRsupport
MicSMCSensorSupport
BMCNumberOfRetries
BMCWaitBetweenRetries
BMCPrintRetryInfo

Test Execution Time

Test time is about 1 second

Dependencies/Limitations
If the BMC is not detected on the host board, or the host board does not support BMC to SMC communication,or the 
driver designated in parameter IPMIDriver is not installed, or the MIC card cannot be found in the specified PCIe slot, or 
the SMC on the MIC card does not respond, the test will fail.




1.14. Test 22 - MicCheckDeviceGUID

Overview

This test retrieves the programmed GUID (Guaranteed Unique ID) from the SMC, and compares it with the default 
programmed value. If it matches, the test fails, as the GUID has not been programmed.

Parameter(s)

MicRdBus
MicRdSlot
MicRdAddr
IPMIDriver
MicGUIDDefault
BMCNumberOfRetries
BMCWaitBetweenRetries
BMCPrintRetryInfo

Test Execution Time

Test time is about 1 second

Dependencies/Limitations
If the BMC is not detected on the host board, or the host board does not support BMC to SMC communication,or the 
driver designated in parameter IPMIDriver is not installed, or the MIC card cannot be found in the specified PCIe slot, or 
the SMC on the MIC card does not respond, the test will fail.





1.15. Test 34 - MicAddSelEntry

Overview

This utility adds an entry to the SEL. If the optional parameters listed below (MicAddSELdata1, 2, 3 and 4) are found in 
the package file, those values are used to submit the entry. If they are not found, default values are submitted instead.

See Table 32-1 ("SEL Event Records") of IPMI 2.0 specification for details. As a summary, these are the fields that 
matter, focusing on record type 02h (system event records):

Bytes 1-2: 	Record ID (filled in by system, so value doesn't matter)
Byte 3: 	Record Type
			02h: system event record
			C0h-DFh: OEM timestamped, bytes 8-16 OEM defined (see Table 32-2 in IPMI 2.0 specification)
			E0-FFh: OEM non-timestamped, bytes 4-16 OEM defined (see Table 32-3 in IPMI 2.0 
specification)
Bytes 4-7:	Timestamp (filled in by system, so value doesn't matter)
Bytes 8-9:	RqSA & LUN if event was generated from IPMB. Software ID if event was generated from system 
software.
		Byte 1
		[7:1] 	7-bit I2C slave address or 7-bit system software ID
		[0] 	0b = ID is IPMB slave address
			1b = system software ID
		Byte 2
		[7:4] 	Channel number
		[3:2]	Reserved - write as 00b
		[1:0]	IPMB device LUN if byte 1 holds Slave Address. 00b otherwise.
Byte 10:	EvM Rev - Event Message format version. 04h for IPMI 2.0 specification, 0h for IPMI 1.0 event 
messages.
Byte 11:	Sensor Type Code for sensor that generated the event.
Byte 12:	Number of sensor that generated the event
Byte 13: 	Event Dir | Event Type
		Event Dir
		[7]	0b = Assertion event, 01b = de-assertion event
		Event Type
		Type of trigger for the event, e.g., critical threshold going high, state asserted, etc. 
		Also indicates class of the event, e.g., discrete, threshold, or OEM. 
		The Event Type field is encoded using the Event/Reading Type Code. 
		See section 42.1 of IPMI 2.0 specification ("Event/Reading Type Codes").
		[6:0]	Event Type code
Byte 14:	Event Data 1 - per Table 29-6 of IPMI 2.0 specification, Event Request Message Event Data Field 
contents
Byte 15:	Event Data 2 - per Table 29-6 of IPMI 2.0 specification, Event Request Message Event Data Field 
contents
Byte 16:	Event Data 3 - per Table 29-6 of IPMI 2.0 specification, Event Request Message Event Data Field 
contents

The utility is disabled by default, as it is mainly for debugging use.

Parameter(s)

MicRdBus
MicRdSlot
MicRdAddr
IPMIDriver
BMCNumberOfRetries
BMCWaitBetweenRetries
BMCPrintRetryInfo

Optional parameters:
MicAddSELdata1 (covers bytes 1-4 above)
MicAddSELdata2 (covers bytes 5-8 above)
MicAddSELdata3 (covers bytes 9-12 above) 
MicAddSELdata4 (covers bytes 13-16 above)

Test Execution Time

Test time is about 1 second

Dependencies/Limitations
If the BMC is not detected on the host board, or the host board does not support BMC to SMC communication, or the 
driver designated in parameter IPMIDriver is not installed, or the MIC card cannot be found in the specified PCIe slot, or 
the SMC on the MIC card does not respond, the test will fail.

1.16. Test 35 - MicGetSELTime

Overview

This utility reports the SEL time.

Parameter(s)

MicRdBus
MicRdSlot
MicRdAddr
IPMIDriver
BMCNumberOfRetries
BMCWaitBetweenRetries
BMCPrintRetryInfo

Test Execution Time

Test time is about 1 second

Dependencies/Limitations
If the BMC is not detected on the host board, or the host board does not support BMC to SMC communication,or the 
driver designated in parameter IPMIDriver is not installed, or the MIC card cannot be found in the specified PCIe slot, or 
the SMC on the MIC card does not respond, the test will fail.

1.17. Test 36 - MicSetSELTime

Overview

This utility sets the SEL time to match the current system time.

Parameter(s)

MicRdBus
MicRdSlot
MicRdAddr
IPMIDriver
BMCNumberOfRetries
BMCWaitBetweenRetries
BMCPrintRetryInfo

Test Execution Time

Test time is about 1 second

Dependencies/Limitations
If the BMC is not detected on the host board, or the host board does not support BMC to SMC communication,or the 
driver designated in parameter IPMIDriver is not installed, or the MIC card cannot be found in the specified PCIe slot, or 
the SMC on the MIC card does not respond, the test will fail.

1.18. Test 37 - MicClearSEL

Overview

This utility clears all entries in the SEL. It is typically run at the beginning of a long test cycle to clear all entries in SEL. 
At the end of the test cycle, the SEL will be checked again to ensure no errors were logged into the SEL.

Parameter(s)

MicRdBus
MicRdSlot
MicRdAddr
IPMIDriver
BMCNumberOfRetries
BMCWaitBetweenRetries
BMCPrintRetryInfo

Test Execution Time

Test time is about 1 second

Dependencies/Limitations
If the BMC is not detected on the host board, or the host board does not support BMC to SMC communication, or the 
driver designated in parameter IPMIDriver is not installed, or the MIC card cannot be found in the specified PCIe slot, or 
the SMC on the MIC card does not respond, the test will fail.

1.19. Test 50 - MicVerifyFRUData

Overview

This test retrieves all FRU data from the SMC, including the Manufacturer Name, Product Name, Model Number, GUID 
(Guaranteed Unique ID), Manufacturing Date and Time, and card Serial Number.  It then retrieves the expected values 
from the package file, compares them, and reports an error if they do not match.

The FRU Manufacturer Name, Model Number, and Product Name are compared against a known "gold" value, since 
they can be determined ahead of time. The Manufacturing Date and Time are verified to be reasonable values. The 
GUID is confirmed to be a non-default value. 

Because the Serial Number is dynamic, not something that can be compared against a known value, it is instead 
compared against a value written to a file. For example, during a manufacturing process, the Serial Number can be 
scanned in and then compared against the FRU value. This would compare that the serial number printed on the board 
label matches the FRU serial number.

To view FRU information without verifying it, see the MicReadFRUData utility.

Parameter(s)

MicRdBus
MicRdSlot
MicRdAddr
IPMIDriver
MicFRUManufacturerName
MicFruModelNumber
MicFRUProductName
MicSMCFRU_SNFile
BMCNumberOfRetries
BMCWaitBetweenRetries
BMCPrintRetryInfo

Test Execution Time

Test time is about 1 second

Dependencies/Limitations
If the BMC is not detected on the host board, or the host board does not support BMC to SMC communication,or the 
driver designated in parameter IPMIDriver is not installed, or the MIC card cannot be found in the specified PCIe slot, or 
the SMC on the MIC card does not respond, the test will fail.

1.20. Test 51 - MicReadFRUData

Overview

This utility reports all FRU data to the user, including the Manufacturer Name, Product Name, Model Number, GUID 
(Guaranteed Unique ID), Manufacturing Date and Time, and card Serial Number. No information is verified - for that, 
see MicVerifyFRUData.

Parameter(s)

MicRdBus
MicRdSlot
MicRdAddr
IPMIDriver
BMCNumberOfRetries
BMCWaitBetweenRetries
BMCPrintRetryInfo

Test Execution Time

Test time is about 1 second

Dependencies/Limitations
If the BMC is not detected on the host board, or the host board does not support BMC to SMC communication, or the 
driver designated in parameter IPMIDriver is not installed, or the MIC card cannot be found in the specified PCIe slot, or 
the SMC on the MIC card does not respond, the test will fail.

1.21. Test 60 - MicExitManufacturingMode

Overview

This test invokes the OEM call to Exit Manufacturing Mode for the SMC. After this call is invoked, IT WILL NOT BE 
REVERSED, so use it with caution. It is set to Destructive in the SNX file. After manufacturing mode is exited, the FRU 
may no longer be written to, and a few other OEM specific commands such as adjusting the fan lower will no longer 
work.

Parameter(s)

MicRdBus
MicRdSlot
MicRdAddr
IPMIDriver
BMCNumberOfRetries
BMCWaitBetweenRetries
BMCPrintRetryInfo

Test Execution Time

Test time is about 1 second

Dependencies/Limitations
If the BMC is not detected on the host board, or the host board does not support BMC to SMC communication, or the 
driver designated in parameter IPMIDriver is not installed, or the MIC card cannot be found in the specified PCIe slot, or 
the SMC on the MIC card does not respond, the test will fail.

If FRU data is not set correctly, this test will not pass. Use the lxMicFRU utility to set FRU data before calling this.

Update with version 2.09.1.0005: If the SMC returns C1h, it indicates the Exit Manufacturing Mode was already called. 
Instead of reporting an error, an Information message is reported telling the user of this status.

1.22. Test 61 - MicSMCColdReset

Overview

This test causes a cold reset of the SMC. It is especially useful after the MicCheckFanControl test runs, to reset fan 
control to the SMC instead of controlling it manually. It is also used for other reasons including checking the FRU after 
it's programmed.

Parameter(s)

MicRdBus
MicRdSlot
MicRdAddr
IPMIDriver
BMCNumberOfRetries
BMCWaitBetweenRetries
BMCPrintRetryInfo

Test Execution Time

Test time is about 1 second

Dependencies/Limitations

This test will fail if it is run after Manufacturing Mode exits.

If the BMC is not detected on the host board, or the host board does not support BMC to SMC communication,or the 
driver designated in parameter IPMIDriver is not installed, or the MIC card cannot be found in the specified PCIe slot, or 
the SMC on the MIC card does not respond, the test will fail.

If FRU data is not set correctly, this test will not pass. Use the lxMicFRU utility to set FRU data before calling this.

1.23. Test 62 - MicCheckFanControl

Overview

IMPORTANT: Fan control test must be run without the uOS booted. Test may sporadically fail otherwise.

This subtest verifies the SMC fan control capabilities by setting the fan PWM (Pulse Width Modulation) to specified 
values and verifying that the fan tachometer speeds up or slows down correspondingly.

First, it walks through the Sensor Data Record (SDR) entries to find "fan_tach" and "fan_pwm" entries. If either is not 
found, it reports that there is no fan control and exits.

Next, it saves the fan PWM value at the beginning of the test. This will be restored at the end of the test.

It sets the fan PWM to 100%. It waits the number of seconds defined by the user in the MicFanDelaparameter (default 
10 seconds) and then reads the fan tachometer. If the tachometer value at 100% PWM differs more than 
MicFanTachTolerance percent from the tachometer value saved at 100% PWM during Auto-Configuration, the test will 
fail.

Now it sets the fan PWM to 40%. It waits the number of seconds defined by the user in the MicFanDelay parameter 
(default 10 seconds) and then reads the fan tachometer. If the tachometer value at 40% PWM differs more than 
MicFanTachTolerance percent from the tachometer value saved at 40% PWM during Auto-Configuration, the test will 
fail.

Following, it ensures that the current fan tachometer value at 40% PWM is more than MicFanTachRequiredDifference 
percentage points (default 10%) different than the current fan tachometer value at 100% PWM. In other words, the fan 
tachometer at 40% PWM must be less than the fan tachometer at 100% PWM by the user limit specified in 
MicFanTachRequiredDifference.

Finally, it sets the fan PWM back to SMC control. 

Parameter(s)

MicRdBus
MicRdSlot
MicRdAddr
IPMIDriver
MicFanDelay
MicFanTach40
MicFanTach100
MicFanTachTolerance
MicFanTachRequiredDifference
BMCNumberOfRetries
BMCWaitBetweenRetries
BMCPrintRetryInfo

Test Execution Time

Test time is about 25 seconds with default 10 second delay set in MicFanDelay. If this value is set higher or lower, the 
test time will change. However, be careful not to set MicFanDelay too low - some time must be allowed for the fan to 
speed up after the PWM value is changed.

Dependencies/Limitations

Test will remove itself if a fan sensor is not found in the SDR entries during auto-configuration.

If the BMC is not detected on the host board, or the host board does not support BMC to SMC communication, or the 
driver designated in parameter IPMIDriver is not installed, or the MIC card cannot be found in the specified PCIe slot, or 
the SMC on the MIC card does not respond, the test will fail.

IMPORTANT: Fan control test must be run without the uOS booted. Test may sporadically fail otherwise.

If MicCheckFanControl sporadically fails, make sure MicFanDelay is set to the correct value (currently 2 seconds, at this 
point). Any change in this value should be carefully validated to ensure test runs are stable.



1.24. Test 63 - MicReportMfgState

Overview

   Test sends IPMI commands to SMC then reports to user if MIC is in Manufacturing mode or has exited Manufacturing 
mode. 

Parameter(s)

MicRdBus
MicRdSlot
MicRdAddr
IPMIDriver

Test Execution Time

Test time is about 3 seconds 
 
Dependencies/Limitations

If the BMC is not detected on the host board, or the host board does not support BMC to SMC communication, or the 
driver designated in parameter IPMIDriver is not installed, or the MIC card cannot be found in the specified PCIe slot, or 
the SMC on the MIC card does not respond, the test will fail.




1.25. Test 64 - MicCheckMfgState

Overview

   This test retrieves the Manufacturing state of MIC from the SMC. Then compares this to default MicMfgModeState 
parameter if they do not match the test fails. 

Parameter(s)

MicRdBus
MicRdSlot
MicRdAddr
IPMIDriver
MicMfgModeState

Test Execution Time

Test time is about 5 seconds

Dependencies/Limitations

If the BMC is not detected on the host board, or the host board does not support BMC to SMC communication, or the 
driver designated in parameter IPMIDriver is not installed, or the MIC card cannot be found in the specified PCIe slot, or 
the SMC on the MIC card does not respond, the test will fail.




1.26. Test 80 - MicDisplayVRPhases

Overview

   This utlity reads and displays the MIC voltage regulator (VR) phase registers over an overall period of time set by the 
MicVRMonitorTime parameter. The phase register reads occur periodically; the time interval being set by the 
MicVRMonitorInterval parameter. This utility is run concurrently with MIC current drawing applications, such as SGEMM 
(VR0 loading) and PtuGDDR (VR1 loading). These applications cause loading of the VRs, which cause the phase 
registers to increase in value. If a phase is malfunctioning, its value will increase very little relative to the other 
functioning phases when load is applied to the MIC card.The malfunctioning phase's minimum value can dip below that 
of the other functioning phases as well. A sliding average, for each of the VR phases, is calculated for the last X VR 
register acquisitions; X being set by the MicVRMonitorAvgCount parameter. The phases read are set by the 
MicVRMonitorPhaseMask0 and MicVRMonitorPhaseMask1 parameters. Individual bits within these parameters enable 
reading of the VR0 and VR1 phase registers respectively.

  If the MicVRDisplayMode parameter is zero, information about all of the enabled phases (set by 
MicVRMonitorPhaseMask0 and MicVRMonitorPhaseMask1) is displayed during each occurrence of the interval set by 
the MicVRMonitorInterval parameter. If the MicVRDisplayMode parameter is one, information about all of the enabled 
phases, is displayed once at the end of utility execution.

  VR phase register information displayed includes VR phase raw value (if Display mode = 0), minimum average, 
maximum average,  maximum average - minimum average [delta], Average minimum of all enabled phase minimum 
averages, and average maximum of all enabled phase maximum averages.


Parameter(s)

MicVRMonitorTime
MicVRMonitorInterval
MicVRMonitorIntervalDelay
MicVRMonitorAvgCount
MicVRMonitorPhaseMask0
MicVRMonitorPhaseMask1
MicVRDisplayMode


Test Execution Time

Test execution time depends on the MicVRMonitorTime parameter.

Dependencies/Limitations

The correct version of MIC SMC firmware must be installed on the card.




1.27. Test 81 - MicCheckVRPhases

Overview

   This test reads and checks the MIC voltage regulator (VR) phase registers for an overall period of time set by the 
MicVRMonitorTime parameter. The phase register read/checks occur periodically; the time interval being set by the 
MicVRMonitorInterval parameter. This test is run concurrently with MIC current drawing applications, such as SGEMM 
(VR0 loading) and PtuGDDR (VR1 loading). These applications cause current  loading of the VRs, which cause the 
phase registers to increase in value. If a phase is malfunctioning, its value will increase very little relative to the other 
functioning phases when load is applied to the MIC card.The malfunctioning phase's minimum value can dip below that 
of the other functioning phases as well. A sliding average, for each of the VR phases, is calculated for the last X VR 
register acquisitions; X being set by the MicVRMonitorAvgCount parameter. The phases checked are set by the 
MicVRMonitorPhaseMask0 and MicVRMonitorPhaseMask1 parameters. Individual bits within these parameters enable 
reading of the VR0 and VR1 phase registers respectively.

  The test records the change or delta of the MIC VR0 and VR1 phase registers over time. Once the overall test time time 
period has elapsed and the specified numbers of VR phases have each its respective VR Delta Threshold (set by 
MicVRCheckDeltaThreshold0, MicVRCheckPhaseThresholdCount0 and MicVRCheckDeltaThreshold1, 
MicVRCheckPhaseThresholdCount1, respectively), all of the enabled phases (set by MicVRMonitorPhaseMask0 and 
MicVRMonitorPhaseMask1) are checked via a method specified via the MicVRCheckMode0 andMicVRCheckMode1 
parameters.

  The method used for checking the VR phase register values is determined by the  MicVRCheckMode0 and 
MicVRCheckMode1 parameters.The various VR Check Modes are listed as follows:


VR Check Mode
Method Used
Comment
0
Simple Delta Level Check
Deprecated
1
Standard Deviation Method A
Deprecated
2
Standard Deviation Method B
Deprecated
3
Standard Deviation Method C
Deprecated
4
Standard Deviation Method D
Deprecated
5
Delta Percentage of Phase Group Total 
Most reliable method for both VR0 and VR1 testing

 
  At this point in time, VR Check Mode 5 has proven to be the most effective and reliable method for consistently 
detecting MIC card phase errors that have been hardware fault injected. This method compares each VR phase register 
delta value against the total delta values across a group of VR phases. If a VR phase delta value percentage is less 
than its VR Phase Group Delta Percentage Tolerance parameter, either an error is reported or the delta value is 
recalculated and rechecked against its  VR Phase Group Delta 2 Percentage Tolerance parameter.
 
 Each VR is spilt into two phase groups as shown below:


Phase 0
Phase 1
Phase2
Phase 3
Phase 4
Phase 5
Phase 6
Phase 7
VR0
VR0
Group A
VR0
Group A
VR0
Group A
VR0
Group A
VR0
Group A
VR0
Group A
VR0
Group A
VR0
Group A
VR1
VR1
Group A
VR1
Group A
VR1
Group A
VR1
Group A
VR1
Group A
VR1
Group A
VR1
Group B
VR1
Group B

 VR0 Phase Group A is comprised of all eight VR0 phases, while VR1 is split into VR1 Phase Group A, comprised of 
VR1 phases 0 through 5, and VR1 Phase Group B, comprised of VR1 phases 6 and 7.
 
The Delta Percent Tolerance parameters for VR0 Phase Group A is MicVRCheckDeltaPctToleranceA0 and 
MicVRCheckDelta2PctToleranceA0, for VR1 Phase Group A is MicVRCheckDeltaPctToleranceA1 and 
MicVRCheckDelta2PctToleranceA1, and for VR1 Phase Group B is MicVRCheckDeltaPctToleranceB1 and 
MicVRCheckDelta2PctToleranceB1.

High Phase Minimum Delta Recalculation

 There is a special case where false errors can occur if the VR phase in question has the highest minimum value of its 
VR group. Since a phase delta value equals its maximum value minus its minimum value, a high minimum value value 
can cause a functioning the phase delta to be incorrectly flagged as failing. To address this issue, the VR Phase Group 
Delta 2 Percentage Tolerance parameter is implemented to give a phase that meets this high minimum criteria a "second 
chance".

 If neither the VR0 Delta Threshold Count nor the VR1 Delta Threshold Count is reached during execution of the test, an 
error is reported. If this condition occurs, it means that the concurrent VR phase loading applications have either not 
executed or have not caused enough VR current draw during their execution to trigger each VR Delta Threshold and 
Count.

Parameter(s)

MicVRMonitorTime
MicVRMonitorInterval
MicVRMonitorIntervalDelay
MicVRMonitorAvgCount
MicVRMonitorPhaseMask0
MicVRMonitorPhaseMask1
MicVRCheckDeltaThreshold0
MicVRCheckDeltaThreshold1
MicVRCheckPhaseThresholdMask0
MicVRCheckPhaseThresholdMask1
MicVRCheckPhaseThresholdCount0
MicVRCheckPhaseThresholdCount1
MicVRCheckDeltaPctToleranceA0
MicVRCheckDeltaPctToleranceB0
MicVRCheckDeltaPctToleranceA1
MicVRCheckDeltaPctToleranceB1
MicVRCheckDelta2PctToleranceA0
MicVRCheckDelta2PctToleranceA1
MicVRCheckDelta2PctToleranceB0
MicVRCheckDelta2PctToleranceB1


Example - VR0 Failure

  Hardware fault injected 8 CPU Phase KNC card, all VR0 phase registers implemented (MicVRMonitorPhaseMask0 
parameter = 0xFF)

  * denotes phases reaching VR0 Delta Threshold (MicVRCheckDeltaThreshold0 = 4), ! denotes failing phase

  Delta Percentage method (MicVRCheckMode = 5)

VR0 Phase Register ______________________________        0        1        2        3        4        5        
6        7 

Min _____________________________________________       57       61       60       60       57       61       
60       59 
Max _____________________________________________       64       67       66       66       64       66       
66       60 
Delta ___________________________________________        7*       6*       6*       6*       7*       5*       
6*       1 

Min Percentage __________________________________   12.000   12.842   12.632   12.632   12.000   12.842   
12.632   12.421 
Max Percentage __________________________________   12.331   12.909   12.717   12.717   12.331   12.717   
12.717   11.561 
Delta Percentage ________________________________   15.909   13.636   13.636   13.636   15.909   11.364   
13.636    2.273!

VR0 Group A Min Total _______  475
VR0 Group A Max Total _______  519
VR0 Group A Delta Total _____   44

VR0 Group B Min Total _______    0
VR0 Group B Max Total _______    0
VR0 Group B Delta Total _____    0


Example - VR1 Failure

   Hardware fault injected 5 Memory Phase KNC card,  VR1 phase registers 3,4 and 5 not implemented 
(MicVRMonitorPhaseMask1 parameter = 0xC7)

  * denotes phases reaching VR1 Delta Threshold (MicVRCheckDeltaThreshold1 = 3), ! denotes failing phase

  Delta Percentage method (MicVRCheckMode = 5)

VR1 Phase Register ______________________________        0        1        2        3        4        5        
6        7 

Min _____________________________________________       61       55       62        -        -        -       
64       64 
Max _____________________________________________       67       55       67        -        -        -       
67       67 
Delta ___________________________________________        6*       0        5*       -        -        -        
3*       3*

Min Percentage __________________________________   34.270   30.899   34.831        -        -        -   
50.000   50.000 
Max Percentage __________________________________   35.450   29.101   35.450        -        -        -   
50.000   50.000 
Delta Percentage ________________________________   54.545    0.000!  45.455        -        -        -   
50.000   50.000 

VR1 Group A Min Total _______  178
VR1 Group A Max Total _______  189
VR1 Group A Delta Total _____   11

VR1 Group B Min Total _______  128
VR1 Group B Max Total _______  134
VR1 Group B Delta Total _____    6


Example - VR1 False Failure

   Known good 5 Memory Phase KNC card,  VR1 phase registers 3,4 and 5 not implemented 
(MicVRMonitorPhaseMask1 parameter = 0xC7)

  * denotes phases reaching VR1 Delta Threshold, ! denotes failing phase, $ denotes lowest phase group minimum 
value, # denotes highest phase group minimum value

  Delta Percentage method (MicVRCheckMode = 5)

VR1 Phase Register ______________________________        0        1        2        3        4        5        
6        7 

Min _____________________________________________       62$      66#      65        -        -        -       
69#      69#
Max _____________________________________________       66       67       71        -        -        -       
73       73 
Delta ___________________________________________        4*       1        6*       -        -        -        
4*       4*

Min Percentage __________________________________   32.124   34.197   33.679        -        -        -   
50.000   50.000 
Max Percentage __________________________________   32.353   32.843   34.804        -        -        -   
50.000   50.000 
Delta Percentage ________________________________   36.364    9.091!  54.545        -        -        -   
50.000   50.000 

VR1 Group A Min Total _______  193
VR1 Group A Max Total _______  204
VR1 Group A Delta Total _____   11

VR1 Group B Min Total _______  138
VR1 Group B Max Total _______  146
VR1 Group B Delta Total _____    8

Note that of all the phases in VR1 Group A, the failing phase register, register 1, has the highest minimum value 
(indicated by #, above) of the phases within this phase group. This makes the phase eligible for delta recalculation.

Example - VR1 False Failure with High Minimum Delta Recalculation 

   Same known good 5 Memory Phase KNC card as above with same phase register data.

  * denotes phases reaching VR1 Delta Threshold, ! denotes failing phase, $ denotes lowest phase group minimum 
value, # denotes highest phase group minimum value

  Delta Percentage method (MicVRCheckMode = 5)

VR1 Phase Register ______________________________        0        1        2        3        4        5        
6        7 

Min _____________________________________________       62$      66#      65        -        -        -       
69#      69#
Max _____________________________________________       66       67       71        -        -        -       
73       73 
Delta ___________________________________________        4*       1        6*       -        -        -        
4*       4*
Delta2 __________________________________________        -        5        -        -        -        -        
-        - 

Min Percentage __________________________________   32.124   34.197   33.679        -        -        -   
50.000   50.000 
Max Percentage __________________________________   32.353   32.843   34.804        -        -        -   
50.000   50.000 
Delta Percentage ________________________________   36.364    9.091   54.545        -        -        -   
50.000   50.000 
Delta2 Percentage _______________________________   26.667   33.333   40.000        -        -        -        
-        - 
 

VR1 Group A Min Total _______  193
VR1 Group A Max Total _______  204
VR1 Group A Delta Total _____   11
VR1 Group A Delta2 Total ____   15

VR1 Group B Min Total _______  138
VR1 Group B Max Total _______  146
VR1 Group B Delta Total _____    8

When phase delta recalculation occurs, a new delta value is generated by subtracting lowest minimum value of all 
phases within the phase group (indicated by $, above) from the phases's maximum value. This new delta value is listed 
on the "Delta 2" line above. The recalculated "Delta 2 Percentage" for VR1 Phase Group A is arrived at by using the 
VR1 Phase Group A green highlighted values above, the two original deltas along with the recalculated delta.

Test Execution Time

Test execution time depends on the MicVRMonitorTime parameter.

Dependencies/Limitations

The correct version of MIC SMC firmware must be installed on the card.




1.28. Parameters

BMCNumberOfRetries
BMCWaitBetweenRetries
BMCPrintRetryInfo
IPMIDriver
EVMMaskXX
EVMMask_Count
MicAddSELdata1
MicAddSELdata2
MicAddSELdata3
MicAddSELdata4
MicFanDelay
MicFanTach40
MicFanTach100
MicFanTachRequiredDifference 
MicFanTachTolerance
MicFRUManufacturerName
MicFruModelNumber
MicFRUProductName
MicGUIDDefault
MicRdAddr
MicRdBus
MicRdSlot
MicMfgModeState
MicSMCDeviceID
MicSMCFirmwareVersion
MicSMCFRUsupport
MicSMCSDRsupport
MicSMCSELsupport
MicSMCSensorSupport
MicVRMonitorTime
MicVRMonitorInterval
MicVRMonitorIntervalDelay
MicVRMonitorAvgCount
MicVRCheckInfoMode
MicVRCheckMode0
MicVRCheckMode1
MicVRMonitorPhaseMask0
MicVRMonitorPhaseMask1
MicVRCheckDeltaThreshold0
MicVRCheckDeltaThreshold1
MicVRCheckDeltaTolerance0
MicVRCheckDeltaTolerance1
MicVRCheckBaseTolerance0
MicVRCheckBaseTolerance1
MicVRCheckMinStdDevLimit0
MicVRCheckMinStdDevLimit1
MicVRCheckMaxStdDevLimit0
MicVRCheckMaxStdDevLimit1
MicVRCheckDeltaStdDevLimit0
MicVRCheckDeltaStdDevLimit1
MicVRCheckDeltaPctToleranceA0
MicVRCheckDeltaPctToleranceB0
MicVRCheckDeltaPctToleranceA1
MicVRCheckDeltaPctToleranceB1
MicVRCheckDelta2PctToleranceA0
MicVRCheckDelta2PctToleranceA1
MicVRCheckDelta2PctToleranceB0
MicVRCheckDelta2PctToleranceB1
MicVRCheckPhaseThresholdMask0
MicVRCheckPhaseThresholdMask1
MicVRCheckPhaseThresholdCount0
MicVRCheckPhaseThresholdCount1
MicVRDisplayMode
MicVRMonitorSKUInfoArray

1.29. EVMMask_Count

Description

This optional parameter specifies the total number of SEL event messages masks as specified in the EVMMaskXX 
parameter. This parameter is used when the EVMMaskXX parameter list is not sequential.  

Default Value: 0x01
Valid Values: 0 to 100 

Default

	EVMMask00 = "0x02070a0b0c0d0e0f"

Dependencies

Optional 

Used by

Auto-Configure
MicCheckSELErrors

See Also

Parameters

1.30. EVMMaskXX

Description

This parameter specifies what Event Messages are masked from creating an error when the CheckSELErrors test is 
run. It consists of a string of hexadecimal bytes in the following format. Mask format and total bytes are record type 
specific (8 bytes for record type 02h, 10 bytes for record type C0h-DFh and 14 bytes for record type E0h-FFh).  
   
(a) System Events (RecordType = 02h)  
0x[RecordType-1B][DevAddr-1B][SensorType-1B][Sensor#-1B][EvtDir|EvtTrigger-1B][EvtData1-1B][EvtData2-1B][EvtD
ata3-1B]  
 
(b) OEM Timestamped Events (RecordType = C0h - DFh)  
0x[RecordType-1B][ManufactureID-3B][EvtData-6B]    
 
(c) OEM Non-Timestamped (RecordType = E0h - FFh)  
0x[RecordType-1B][EvtData-13B]  
 
(Note: 1B denotes 1-Byte, 13B denotes 13-Bytes & etc.)  
 
If any of the bytes in the parameter are 0xFF they are ignored in the comparison. If any of the LSB numbers on the end 
are left off or missing they are ignored in the compare. This parameter is case insensitive. Maximum length of mask is 
15 Bytes. XX = decimal number from 00 to 99, must start with 00.  
A total of 71 Event Messages as specified in the module snippet file are masked by default. User is adviced to go 
through the list of default EVMMaskXX parameters and remove all Event that should not be masked before run the 
CheckSELErrors subtest. If the EVMMaskXX list is not sequential, EVMMask_Count parameter can be used to 
specified the total number of Event Message to be masked.  
 
Default Value - EVMMask00 = 0x022010096F420FFF (Log Area Cleared event)  

Default

	EVMMask00 = "0x02070a0b0c0d0e0f"

Dependencies

Optional - if none are used, all entries found in SEL log will be reported as errors.

Used by

Auto-Configure
MicCheckSELErrors

See Also

Parameters

1.31. MicAddSELdata1

Description

Bytes 1-4 of 16 bytes of data to be added to SEL. See MicAddSelEntry for additional information.

Default

	MicAddSELdata1 = "0x00000200"

Dependencies

Required

Used by

Auto-Configure
MicAddSelEntry

See Also

Parameters

1.32. MicAddSELdata2

Description

Bytes 5-8 of 16 bytes of data to be added to SEL. See MicAddSelEntry for additional information.

Default

	MicAddSELdata2 = "0x00000007"

Dependencies

Required

Used by

Auto-Configure
MicAddSELEntry

See Also

Parameters

1.33. MicAddSELdata3

Description

Bytes 9-12 of 16 bytes of data to be added to SEL. See MicAddSelEntry for additional information.

Default

	MicAddSELdata3 = "0x08040A0B"

Dependencies

Required

Used by

Auto-Configure
MicAddSelEntry

See Also

Parameters

1.34. MicAddSELdata4

Description

Bytes 13-16 of 16 bytes of data to be added to SEL. See MicAddSelEntry for additional information.

Default

	MicAddSELdata4 = "0x0C0D0E0F"

Dependencies

Required

Used by

Auto-Configure
MicAddSelEntry

See Also

Parameters

1.35. MicFanDelay

Description

This parameter contains the user-defined number of seconds to wait after the fan PWM is set before reading the fan 
tachometer. This allows the fan time to speed up before the tachometer is read, for more accurate results in the 
MicCheckFanControl test.

If MicCheckFanControl sporadically fails, make sure MicFanDelay is set to the correct value (currently 2 seconds, at this 
point). Any change in this value should be carefully validated to ensure test runs are stable.

Default

	MicFanDelay = 2

Dependencies

Required

Used by

Auto-Configure
MicCheckFanControl

See Also

Parameters

1.36. MicFanTach40

Description

This parameter contains the value read in the fan tachometer when the fan PWM was set to 40% during 
Auto-Configuration.

Default

	MicFanTach40 = 0x54

Dependencies

Required

Used by

Auto-Configure
MicCheckFanControl

See Also

Parameters

1.37. MicFanTach100

Description

This parameter contains the value read in the fan tachometer when the fan PWM was set to 40% during 
Auto-Configuration.

Default

	MicFanTach100 = 0x108

Dependencies

Required

Used by

Auto-Configure
MicCheckFanControl

See Also

Parameters

1.38. MicFanTachRequiredDifference

Description

This parameter contains the percentage difference the fan tachometer at 40% PWM must differ from the fan tachometer 
at 100% PWM. 

Default

	MicFanTachRequiredDifference = 10

Dependencies

Required

Used by

Auto-Configure
MicCheckFanControl

See Also

Parameters

1.39. MicFanTachTolerance

Description

This parameter contains the percentage by which the current fan tachometer reading at 40% PWM and the current fan 
tachometer reading at 100% PWM may differ from the values saved during Auto-Configuration.

Default

	MicFanTachTolerance = 10

Dependencies

Required

Used by

Auto-Configure
MicCheckFanControl

See Also

Parameters

1.40. MicFRUManufacturerName

Description

Contains name of manufacturer of MIC card, as stored in SMC FRU data.

Default

	MicFRUManufacturerName = "Intel Corporation"

Dependencies

Required

Used by

Auto-Configure
MicVerifyFRUData

See Also

Parameters

1.41. MicFRUModelNumber

Description

Contains Model Number of MIC card, as stored in SMC FRU data.

Default

	MicFRUModelNumber = "G30089-100"

Dependencies

Required

Used by

Auto-Configure
MicVerifyFRUData

See Also

Parameters

1.42. MicFRUProductName

Description

Contains Product Name of MIC card, as stored in SMC FRU data.

Default

	MicFRUProductName = "Knight's Corner"

Dependencies

Required

Used by

Auto-Configure
MicVerifyFRUData

See Also

Parameters

1.43. MicGUIDDefault

Description

Parameter shows MIC default GUID (Guaranteed Unique ID) value.

Default

	MicGUIDDefault = "FFFEFDFC-FBFA-F9F8-F7F6-F5F4F3F2F1F0"

Dependencies

Required

Used by

Auto-Configure
MicGetDeviceInformation

See Also

Parameters

1.44. Analog Sensors_<Sensor Name>_SensorNumber

Description

Parameter shows the sensor number of a specific sensor <Sensor Name>.

Default

	SensorNumber = "0"

Dependencies

Required

Used by

Auto-Configure
MicReadSensorAndDisplay
MicReadSensorQuiet
MicSensorEventStatus
MicCheckSensorThresholds


See Also

Parameters

1.45. Analog Sensors_<Sensor Name>_SDRRecID

Description

Parameter shows the SDR record ID of a specific sensor <Sensor Name>.

Default

	SDRRecID = "0"

Dependencies

Required

Used by

Auto-Configure


See Also

Parameters

1.46. Analog Sensors_<Sensor Name>_UpperCriticalThreshold

Description

Parameter shows the upper critical threshold value of a specific analog sensor <Sensor Name>.

Default

	UpperCriticalThreshold = "FFFF"

Dependencies

Required

Used by

Auto-Configure
MicCheckSensorThresholds


See Also

Parameters

1.47. Analog Sensors_<Sensor Name>_LowerCriticalThreshold

Description

Parameter shows the lower critical threshold value of a specific analog sensor <Sensor Name>.

Default

	LowerCriticalThreshold = "0"

Dependencies

Required

Used by

Auto-Configure
MicCheckSensorThresholds


See Also

Parameters

1.48. Analog Sensors_<Sensor Name>_ThresholdSupport

Description

Parameter shows the relevant SDR bytes for analog sensor <Sensor Name> that indicate whether thresholds of 
different kinds are supported for this sensor.

Default

	ThresholdSupport = "1"

Dependencies

Required

Used by

Auto-Configure
MicCheckSensorThresholds


See Also

Parameters

1.49. Discrete Sensors_<Sensor Name>_SDRRecID

Description

Parameter shows the SDR record ID of a specific sensor <Sensor Name>.

Default

	SDRRecID = "0"

Dependencies

Required

Used by

Auto-Configure


See Also

Parameters

1.50. Discrete Sensors_<Sensor Name>_SensorNumber

Description

Parameter shows the sensor number of a specific sensor <Sensor Name>.

Default

	SensorNumber = "0"

Dependencies

Required

Used by

Auto-Configure
MicReadSensorAndDisplay
MicReadSensorQuiet
[****]

See Also

Parameters

1.51. IPMIDriver

Description

Parameter indicates whether the Intel-IMB driver or MonteVista-IPMI0 driver will be used for issuing the IPMI 
commands to the BMC. The selected driver must be installed on the system for the test to execute. 

Possible values for this parameter are: "IMB" or "IPMI0". 

Default

	IPMIDriver = "IPMI0"

Dependencies

Required

Used by - All tests


See Also

Parameters

1.52. BMCNumberOfRetries

Description

Parameter indicates how many times a test should re-try to issue an IPMI command if it fails with a time-out or other 
non-successful completion code values.

Default

	BMCNumberOfRetries = 2

Dependencies

Required

Used by - All tests


See Also

Parameters

1.53. BMCPrintRetryInfo

Description

Parameter indicates if retry information should be visible. If parameter is set to 0, retry information will print as a verbose 
message. If set to non-zero or is missing from the package, retry information will print as an Information message.

Default

	BMCPrintRetryInfo = 1

Dependencies

Optional

Used by - All tests


See Also

Parameters

1.54. BMCWaitBetweenRetries

Description

Parameter indicates how many milliseconds a test should wait between re-try attempts to issue an IPMI command if it 
fails with a time-out or other non-successful completion code values.

Default

	BMCWaitBetweenRetries = 500

Dependencies

Required

Used by - All tests


See Also

Parameters

1.55. MicRdCard

Description

Parameter indicates the MIC card number. Autoconfig sets the MicRdSlot parameter that corresponds to this value.

See "IPMI Intelligent Platform Management Interface Specification Second Generation v2.0" for complete information.


Default

	MicRdSlot = 0x01

Dependencies

Required

Used by

Auto-Configure
MicGetDeviceInformation
MicCheckSELErrors
 MicDisplaySELEntries 
 MicCheckDeviceGUID 
 MicAddSELEntry 
 MicGetSELTime 
 MicSetSELTime 
 MicClearSEL

See Also

Parameters

1.56. MicRdAddr

Description

Parameter indicates either the IPMI unique ID or the slave address (8 bit "write" address), dependent on the "Address 
Type" (see MicRdAddressType parameter) field. 

See "IPMI Intelligent Platform Management Interface Specification Second Generation v2.0" for complete information.

Default

	MicRdAddr = 0x30

Dependencies

Required

Used by

Auto-Configure
MicGetDeviceInformation
MicCheckSELErrors
 MicDisplaySELEntries 
 MicCheckDeviceGUID 
 MicAddSELEntry 
 MicGetSELTime 
 MicSetSELTime 
 MicClearSEL 

See Also

Parameters

1.57. MicRdBus

Description

Parameter indicates the IPMI address information. It is one byte long, broken up as follows:
[7:6] Address Type
	00b = Bus/Slot/Address
	01b = Reserved for unique identifier
[5:4] Reserved
[3:0] Bus number. Set to 0 for "Address Type" not "Bus/Slot/Address"

See "IPMI Intelligent Platform Management Interface Specification Second Generation v2.0" for complete information.

Default
	 
   MicRdBus = 0x02

Dependencies

Required

Used by

Auto-Configure
MicGetDeviceInformation
MicCheckSELErrors
 MicDisplaySELEntries 
 MicCheckDeviceGUID 
 MicAddSELEntry 
 MicGetSELTime 
 MicSetSELTime 
 MicClearSEL

See Also

Parameters

1.58. MicRdSlot

Description

Parameter indicates the PCIe IPMI slot information. Set to the slot correct slot number by autoconfig. Set to 0 if 
MicRdBus indicates it is not "Bus/Slot/Address"

See "IPMI Intelligent Platform Management Interface Specification Second Generation v2.0" for complete information.

Dependencies

Required

Used by

Auto-Configure
MicGetDeviceInformation
MicCheckSELErrors
 MicDisplaySELEntries 
 MicCheckDeviceGUID 
 MicAddSELEntry 
 MicGetSELTime 
 MicSetSELTime 
 MicClearSEL

See Also

Parameters

1.59. MicMfgModeState

Description

Parameter indicates whether MIC is in manufacturing mode or has exited manufacturing mode.
 
Values are either 0 (manufacturing mode) or 1 (exited manufacturing mode).

Default

	MicMfgModeState =  "0"

Dependencies

Required

Used by

MicCheckMfgState

See Also

Parameters

1.60. MicSMCDeviceID

Description

The Device ID of the SMC on the MIC card.

Default
	 
   MicSMCDeviceID = 0x540001

Dependencies

Required

Used by

Auto-Configure
MicGetDeviceInformation

See Also

Parameters

1.61. MicSMCFirmwareVersion

Description

Parameter indicates either the Firmware version of the SMC code.

Default

	MicSMCFirmwareVersion = "1.0.2993"

Dependencies

Required

Used by

Auto-Configure
MicGetDeviceInformation

See Also

Parameters

1.62. MicSMCFRUsupport

Description

Parameter indicates whether SMC Firmware supports FRU (Field Replaceable Unit).

Values are either 0 (unsupported) or 1 (supported).

Default

	MicSMCFRUsupport = 0x1

Dependencies

Required

Used by

Auto-Configure
MicGetDeviceInformation

See Also

Parameters

1.63. MicSMCFRU_SNFile

Description

Parameter indicates whether SMC Firmware supports FRU (Field Replaceable Unit).

Values are either 0 (unsupported) or 1 (supported).

Default

	MicSMCFRU_SNFile = "KNC_SN.txt"

Dependencies

Required

Used by

Auto-Configure
MicGetDeviceInformation

See Also

Parameters

1.64. MicSMCSDRsupport

Description

Parameter indicates whether SMC Firmware supports SDR (Sensor Data Repository) capabilities.

Values are either 0 (unsupported) or 1 (supported).

Default

	MicSMCSDRsupport = 0x1

Dependencies

Required

Used by

Auto-Configure
MicGetDeviceInformation

See Also

Parameters

1.65. MicSMCSELsupport

Description

Parameter indicates whether SMC Firmware supports SEL (System Event Log).

Values are either 0 (unsupported) or 1 (supported).

Default

	MicSMCSELsupport = 0x1

Dependencies

Required

Used by

Auto-Configure
MicGetDeviceInformation

See Also

Parameters

1.66. MicSMCSensorSupport

Description

Parameter indicates whether SMC Firmware supports sensors.
 
Values are either 0 (unsupported) or 1 (supported).

Default

	MicSMCSensorSupport = 0x1

Dependencies

Required

Used by

Auto-Configure
MicGetDeviceInformation

See Also

Parameters

1.67. MicVRMonitorTime

Description

   Sets the overall time period (in seconds) that the MicDisplayVRPhases utility or the MicCheckVRPhases test executes.

Default
	 
   None

Dependencies

Required

Used by

MicDisplayVRPhases
MicCheckVRPhases

See Also

MicVRMonitorInterval
MicVRMonitorIntervalDelay
MicVRMonitorAvgCount
Parameters

1.68. MicVRMonitorInterval

Description

   Sets the periodic VR phase register read acquisition interval time period (in seconds) that occurs within the 
MicDisplayVRPhases utility or the MicCheckVRPhases test.

Default
	 
   None

Dependencies

Required

Used by

MicDisplayVRPhases
MicCheckVRPhases

See Also

MicVRMonitorTime
MicVRMonitorIntervalDelay
MicVRMonitorAvgCount
Parameters

1.69. MicVRMonitorIntervalDelay

Description

   Sets the a time day period (in milliseconds) that occurs between individual VR phase register acquisitions during the 
MicDisplayVRPhases utility or the MicCheckVRPhases test. This inserts a delay between each  individual VR register 
read within the periodic burst of VR phase register acquisitions, allowing the SMC/IPMI logic a recovery period.

Default
	 
   None

Dependencies

Required

Used by

MicDisplayVRPhases
MicCheckVRPhases

See Also

MicVRMonitorTime
MicVRMonitorInterval
MicVRMonitorAvgCount
Parameters

1.70. MicVRMonitorAvgCount

Description

   Sets the VR phase register read acquisition sliding Averaging Count value for the MicDisplayVRPhases utility or the 
MicCheckVRPhases test.

Example

   If the Averaging Count value is 4, for each VR phase X, the current VR phase X acquisition value is averaged with the 
previous 3 VR phase X acquisition values.

Default
	 
   None

Limitations
	 
   Minimum:1 (no averaging)
   Maximum:16

Dependencies

Required

Used by

MicDisplayVRPhases
MicCheckVRPhases

See Also

MicVRMonitorTime
MicVRMonitorInterval
MicVRMonitorIntervalDelay
Parameters

1.71. MicVRCheckInfoMode

Description

   Sets the INFO display mode of the MicCheckVRPhases test for passing conditions.

	A value of zero means that the VR Phase Info Block is NOT displayed if the MicCheckVRPhases test passes. A value 
of one means that the VR Phase Info Block is displayed if the MicCheckVRPhases test passes, allowing VR phase info 
to be logged for passing test cases.

Default
	 
   none

Dependencies

Required

Used by

MicCheckVRPhases

See Also

Parameters

1.72. MicVRCheckMode0

Description

Sets the check mode of the MicCheckVRPhases test for VR0. The various VR0 Check Modes are listed as follows:

VR0 Check Mode
Method Used
Comment
0
Simple Delta Level Check
Deprecated
1
Standard Deviation Method A
Deprecated
2
Standard Deviation Method B
Deprecated
3
Standard Deviation Method C
Deprecated
4
Standard Deviation Method D
Deprecated
5
Delta Percentage of Phase Group Total 
Most reliable method for VR0 testing

 
  At this point in time, VR Check Mode 5 has proven to be the most effective and reliable method for consistently 
detecting MIC card phase errors that have been hardware fault injected. This method compares each VR phase register 
delta value against the total delta values across a group of VR phases.


Default
	 
   MicVRCheckMode0 = 0

Dependencies

Required

Used by

MicCheckVRPhases

See Also

MicVRCheckDeltaPctToleranceA0
MicVRCheckDeltaPctToleranceB0
Parameters

1.73. MicVRCheckMode1

Description

Sets the check mode of the MicCheckVRPhases test for VR1. The various VR1 Check Modes are listed as follows:

VR1 Check Mode
Method Used
Comment
0
Simple Delta Level Check
Deprecated
1
Standard Deviation Method A
Deprecated
2
Standard Deviation Method B
Deprecated
3
Standard Deviation Method C
Deprecated
4
Standard Deviation Method D
Deprecated
5
Delta Percentage of Phase Group Total 
Most reliable method for VR1 testing

 
  At this point in time, VR Check Mode 5 has proven to be the most effective and reliable method for consistently 
detecting MIC card phase errors that have been hardware fault injected. This method compares each VR phase register 
delta value against the total delta values across a group of VR phases.


Default
	 
   MicVRCheckMode1 = 0

Dependencies

Required

Used by

MicCheckVRPhases

See Also

MicVRCheckDeltaPctToleranceA1
MicVRCheckDeltaPctToleranceB1
Parameters

1.74. MicVRMonitorPhaseMask0

Description

Allows individual MIC card VR0 phase registers to be read or ignored. A bit value of 1 enables reading of a phase 
register; a value of 0 disables reading. Each bit corresponds to a VR0 phase register. Bit 0 (LSB) corresponds with VR0 
phase 0, bit 1 corresponds with VR0 phase 1, and so on.

Default
	 
   MicVRMonitorPhaseMask0 = 0xFF

Dependencies

Required

Used by

MicDisplayVRPhases
MicCheckVRPhases

See Also

MicVRCheckPhaseThresholdMask0
Parameters

1.75. MicVRMonitorPhaseMask1

Description

Allows individual MIC card VR1 phase registers to be read or ignored. A bit value of 1 enables reading of a phase 
register; a value of 0 disables reading. Each bit corresponds to a VR1 phase register. Bit 0 (LSB) corresponds with VR1 
phase 0, bit 1 corresponds with VR1 phase 1, and so on.

Default
	 
   MicVRMonitorPhaseMask1 = 0x1F

Dependencies

Required

Used by

MicDisplayVRPhases
MicCheckVRPhases

See Also

MicVRCheckPhaseThresholdMask1
Parameters

1.76. MicVRCheckDeltaThreshold0

Description

If all of the specified number of VR0 phases have reached the VR0 Delta Threshold value during the overall test time 
time period, (see MicCheckVRPhases test), all enabled VR0 phase registers are checked against VR0 tolerance/limit 
parameters. If the specified number of VR0 phases did not reach the VR0 Delta Threshold, an error occurs.

The purpose of the threshold parameters are to provide a means of ensuring that adequate VR current loading has 
occurred during the test time time period.

Default
	 
   MicVRCheckDeltaThreshold0 = 2

Dependencies

Required

Used by

MicCheckVRPhases

See Also

MicVRMonitorPhaseMask0
MicVRCheckPhaseThresholdMask0
MicVRCheckPhaseThresholdCount0
Parameters

1.77. MicVRCheckDeltaThreshold1

Description

If all of the specified number of VR1 phases have reached the VR1 Delta Threshold value during the overall test time 
time period, (see MicCheckVRPhases test), all enabled VR1 phase registers are checked against VR1 tolerance/limit 
parameters. If the specified number of VR1 phases did not reach the VR1 Delta Threshold, an error occurs.

The purpose of the threshold parameters are to provide a means of ensuring that adequate VR current loading has 
occurred during the test time time period.

Default
	 
   MicVRCheckDeltaThreshold1 = 2

Dependencies

Required

Used by

MicCheckVRPhases

See Also

MicVRMonitorPhaseMask1
MicVRCheckPhaseThresholdMask1
Parameters

1.78. MicVRCheckDeltaTolerance0

Description

Once the overall test time time period has elapsed and the specified number of VR0 phases have reached the VR0 
Delta Threshold, and MicVRCheckMode0 is zero, all enabled VR0 phase register deltas are checked against the VR0 
Delta Tolerance parameter (see MicCheckVRPhases test). The VR0 phase register is flagged if its delta is less than the 
VR0 Delta Tolerance value.

Default
	 
   MicVRCheckDeltaTolerance0 = 2

Dependencies

Required

Used by

MicCheckVRPhases

See Also

MicVRCheckMode0
MicVRMonitorPhaseMask0
Parameters

1.79. MicVRCheckDeltaTolerance1

Description

Once the overall test time time period has elapsed and the specified number of VR1 phases have reached the VR1 
Delta Threshold, and MicVRCheckMode1 is zero, all enabled VR1 phase register deltas are checked against the VR1 
Delta Tolerance parameter (see MicCheckVRPhases test). The VR1 phase register is flagged if its delta is less than the 
VR1 Delta Tolerance value.

Default
	 
   MicVRCheckDeltaTolerance1 = 2

Dependencies

Required

Used by

MicCheckVRPhases

See Also

MicVRCheckMode1
MicVRMonitorPhaseMask1
Parameters

1.80. MicVRCheckBaseTolerance0

Description

Once the overall test time time period has elapsed and the specified number of VR0 phases have reached the VR0 
Delta Threshold, all enabled VR0 phase register deltas are checked against the VR0 Delta Tolerance parameter. The 
VR0 phase register is flagged if its delta is less than the VR0 Delta Tolerance value. If the VR0 phase register is flagged 
and the VR0 Base Tolerance parameter value is zero, an error occurs. If the VR0 phase register is flagged and the VR0 
Base Tolerance parameter value is nonzero, the flagged VR0 phase minimum average value is compared to the 
average of all the other VR phase register minimum averages.  If this value is greater than the VR0 Base Tolerance 
parameter value, an error occurs (see MicCheckVRPhases test).

Default
	 
   MicVRCheckBaseTolerance0 = 0

Dependencies

Required

Used by

MicCheckVRPhases

See Also

MicVRMonitorPhaseMask0
Parameters

1.81. MicVRCheckBaseTolerance1

Description

Once the overall test time time period has elapsed and the specified number of VR1 phases have reached the VR1 
Delta Threshold, all enabled VR1 phase register deltas are checked against the VR1 Delta Tolerance parameter. The 
VR1 phase register is flagged if its delta is less than the VR1 Delta Tolerance value. If the VR1 phase register is flagged 
and the VR1 Base Tolerance parameter value is zero, an error occurs. If the VR1 phase register is flagged and the VR1 
Base Tolerance parameter value is nonzero, the flagged VR1 phase minimum average value is compared to the 
average of all the other VR phase register minimum averages.  If this value is greater than the VR1 Base Tolerance 
parameter value, an error occurs (see MicCheckVRPhases test).

Default
	 
   MicVRCheckBaseTolerance1 = 0

Dependencies

Required

Used by

MicCheckVRPhases

See Also

MicVRMonitorPhaseMask1
Parameters

1.82. MicVRCheckMinStdDevLimit0

Description

Once the overall test time time period has elapsed and the specified number of VR0 phases have reached the VR0 
Delta Threshold, and the MicVRCheckMode0 parameter is one, all enabled VR0 phase register minimum values are 
statistically analyzed to determine the number of standard deviation units of each VR0 phase minimum value (a 
non-linear distance from the mean of all enabled VR0 phase register minimum values). If a VR0 phase minimum 
standard deviation value meets or exceeds this parameter value, an error occurs (see MicCheckVRPhases test).

This minimum value standard derivation unit limit can be expressed as a signed numeric floating point value or an 
absolute numeric floating point value. A "+-" preceding the parameter numeric value signifies an absolute value, e.g 
"+-2.0" and "+-3" signify absolute values, while "2.0", "3", "+1.23", or "-0.95" are signed values .

A standard deviation unit limit value of 0.0 means that the VR0 phase minimum standard deviation value is not checked.  
("0.0", "+0", "-0" or "+-0.0" all mean 0.0)

With signed limits, a positive limit means that the value being compared must be greater than or equal to the limit to 
meet or exceed the limit, while a negative limit means that the value being compared must be less than or equal to the 
limit to meet or exceed the limit, eg. a value of 2.345 will meet or exceed at limit of 2.0, while a value of -2.345 will meet 
or exceed a limit of -2.0.

With absolute value limits, the absolute value of the value being compared must be greater than or equal to the limit to 
meet or exceed the limit, eg. a value of 2.345 or -2.345 will meet or exceed a limit of 2.0.

Default
	 
   MicVRCheckMinStdDevLimit0 = 0.0

Dependencies

Required

Used by

MicCheckVRPhases

See Also

MicVRCheckMode0
MicVRMonitorPhaseMask0
Parameters

1.83. MicVRCheckMinStdDevLimit1

Description

Once the overall test time time period has elapsed and the specified number of VR1 phases have reached the VR1 
Delta Threshold, and the MicVRCheckMode1 parameter is one, all enabled VR1 phase register minimum values are 
statistically analyzed to determine the number of standard deviation units of each VR1 phase minimum value (a 
non-linear distance from the mean of all enabled VR1 phase register minimum values). If a VR1 phase minimum 
standard deviation value meets or exceeds this parameter value, an error occurs (see MicCheckVRPhases test).

This minimum value standard derivation unit limit can be expressed as a signed numeric floating point value or an 
absolute numeric floating point value. A "+-" preceding the parameter numeric value signifies an absolute value, e.g 
"+-2.0" and "+-3" signify absolute values, while "2.0", "3", "+1.23", or "-0.95" are signed values .

A standard deviation unit limit value of 0.0 means that the VR1 phase minimum standard deviation value is not checked.  
("0.0", "+0", "-0" or "+-0.0" all mean 0.0)

With signed limits, a positive limit means that the value being compared must be greater than or equal to the limit to 
meet or exceed the limit, while a negative limit means that the value being compared must be less than or equal to the 
limit to meet or exceed the limit, eg. a value of 2.345 will meet or exceed at limit of 2.0, while a value of -2.345 will meet 
or exceed a limit of -2.0.

With absolute value limits, the absolute value of the value being compared must be greater than or equal to the limit to 
meet or exceed the limit, eg. a value of 2.345 or -2.345 will meet or exceed a limit of 2.0.

Default
	 
   MicVRCheckMinStdDevLimit1 = 0.0

Dependencies

Required

Used by

MicCheckVRPhases

See Also

MicVRCheckMode1
MicVRMonitorPhaseMask1
Parameters

1.84. MicVRCheckMaxStdDevLimit0

Description

Once the overall test time time period has elapsed and the specified number of VR0 phases have reached the VR0 
Delta Threshold, and the MicVRCheckMode0 parameter is one, all enabled VR0 phase register maximum values are 
statistically analyzed to determine the number of standard deviation units of each VR0 phase maximum value (a 
non-linear distance from the mean of all enabled VR0 phase register maximum values). If a VR0 phase maximum 
standard deviation value meets or exceeds this parameter value, an error occurs (see MicCheckVRPhases test).

This maximum value standard derivation unit limit can be expressed as a signed numeric floating point value or an 
absolute numeric floating point value. A "+-" preceding the parameter numeric value signifies an absolute value, e.g 
"+-2.0" and "+-3" signify absolute values, while "2.0", "3", "+1.23", or "-0.95" are signed values .

A standard deviation unit limit value of 0.0 means that the VR0 phase maximum standard deviation value is not 
checked.  ("0.0", "+0", "-0" or "+-0.0" all mean 0.0)

With signed limits, a positive limit means that the value being compared must be greater than or equal to the limit to 
meet or exceed the limit, while a negative limit means that the value being compared must be less than or equal to the 
limit to meet or exceed the limit, eg. a value of 2.345 will meet or exceed at limit of 2.0, while a value of -2.345 will meet 
or exceed a limit of -2.0.

With absolute value limits, the absolute value of the value being compared must be greater than or equal to the limit to 
meet or exceed the limit, eg. a value of 2.345 or -2.345 will meet or exceed a limit of 2.0.

Default
	 
   MicVRCheckMaxStdDevLimit0 = 0.0

Dependencies

Required

Used by

MicCheckVRPhases

See Also

MicVRCheckMode0
MicVRMonitorPhaseMask0
Parameters

1.85. MicVRCheckMaxStdDevLimit1

Description

Once the overall test time time period has elapsed and the specified number of VR1 phases have reached the VR1 
Delta Threshold, and the MicVRCheckMode1 parameter is one, all enabled VR1 phase register maximum values are 
statistically analyzed to determine the number of standard deviation units of each VR1 phase maximum value (a 
non-linear distance from the mean of all enabled VR1 phase register maximum values). If a VR1 phase maximum 
standard deviation value meets or exceeds this parameter value, an error occurs (see MicCheckVRPhases test).

This maximum value standard derivation unit limit can be expressed as a signed numeric floating point value or an 
absolute numeric floating point value. A "+-" preceding the parameter numeric value signifies an absolute value, e.g 
"+-2.0" and "+-3" signify absolute values, while "2.0", "3", "+1.23", or "-0.95" are signed values .

A standard deviation unit limit value of 0.0 means that the VR1 phase maximum standard deviation value is not 
checked.  ("0.0", "+0", "-0" or "+-0.0" all mean 0.0)

With signed limits, a positive limit means that the value being compared must be greater than or equal to the limit to 
meet or exceed the limit, while a negative limit means that the value being compared must be less than or equal to the 
limit to meet or exceed the limit, eg. a value of 2.345 will meet or exceed at limit of 2.0, while a value of -2.345 will meet 
or exceed a limit of -2.0.

With absolute value limits, the absolute value of the value being compared must be greater than or equal to the limit to 
meet or exceed the limit, eg. a value of 2.345 or -2.345 will meet or exceed a limit of 2.0.

Default
	 
   MicVRCheckMaxStdDevLimit1 = 0.0

Dependencies

Required

Used by

MicCheckVRPhases

See Also

MicVRCheckMode1
MicVRMonitorPhaseMask1
Parameters

1.86. MicVRCheckDeltaStdDevLimit0

Description

Once the overall test time time period has elapsed and the specified number of VR0 phases have reached the VR0 
Delta Threshold, and the MicVRCheckMode0 parameter is one, all enabled VR0 phase register delta values are 
statistically analyzed to determine the number of standard deviation units of each VR0 phase delta value (a non-linear 
distance from the mean of all enabled VR0 phase register delta values). If a VR0 phase delta standard deviation value 
meets or exceeds this parameter value, an error occurs (see MicCheckVRPhases test).

This maximum value standard derivation unit limit can be expressed as a signed numeric floating point value or an 
absolute numeric floating point value. A "+-" preceding the parameter numeric value signifies an absolute value, e.g 
"+-2.0" and "+-3" signify absolute values, while "2.0", "3", "+1.23", or "-0.95" are signed values .

A standard deviation unit limit value of 0.0 means that the VR0 phase delta standard deviation value is not checked.  
("0.0", "+0", "-0" or "+-0.0" all mean 0.0)

With signed limits, a positive limit means that the value being compared must be greater than or equal to the limit to 
meet or exceed the limit, while a negative limit means that the value being compared must be less than or equal to the 
limit to meet or exceed the limit, eg. a value of 2.345 will meet or exceed at limit of 2.0, while a value of -2.345 will meet 
or exceed a limit of -2.0.

With absolute value limits, the absolute value of the value being compared must be greater than or equal to the limit to 
meet or exceed the limit, eg. a value of 2.345 or -2.345 will meet or exceed a limit of 2.0.

Default
	 
   MicVRCheckDeltaStdDevLimit0 = 0.0

Dependencies

Required

Used by

MicCheckVRPhases

See Also

MicVRCheckMode0
MicVRMonitorPhaseMask0
Parameters

1.87. MicVRCheckDeltaStdDevLimit1

Description

Once the overall test time time period has elapsed and the specified number of VR1 phases have reached the VR1 
Delta Threshold, and the MicVRCheckMode1 parameter is one, all enabled VR1 phase register delta values are 
statistically analyzed to determine the number of standard deviation units of each VR1 phase delta value (a non-linear 
distance from the mean of all enabled VR0 phase register delta values). If a VR1 phase delta standard deviation value 
meets or exceeds this parameter value, an error occurs (see MicCheckVRPhases test).

This maximum value standard derivation unit limit can be expressed as a signed numeric floating point value or an 
absolute numeric floating point value. A "+-" preceding the parameter numeric value signifies an absolute value, e.g 
"+-2.0" and "+-3" signify absolute values, while "2.0", "3", "+1.23", or "-0.95" are signed values .

A standard deviation unit limit value of 0.0 means that the VR1 phase delta standard deviation value is not checked.  
("0.0", "+0", "-0" or "+-0.0" all mean 0.0)

With signed limits, a positive limit means that the value being compared must be greater than or equal to the limit to 
meet or exceed the limit, while a negative limit means that the value being compared must be less than or equal to the 
limit to meet or exceed the limit, eg. a value of 2.345 will meet or exceed at limit of 2.0, while a value of -2.345 will meet 
or exceed a limit of -2.0.

With absolute value limits, the absolute value of the value being compared must be greater than or equal to the limit to 
meet or exceed the limit, eg. a value of 2.345 or -2.345 will meet or exceed a limit of 2.0.

Default
	 
   MicVRCheckDeltaStdDevLimit1 = 0.0

Dependencies

Required

Used by

MicCheckVRPhases

See Also

MicVRCheckMode1
MicVRMonitorPhaseMask1
Parameters

1.88. MicVRCheckComboStdDevLimit0

Description

Once the overall test time time period has elapsed and the specified number of VR0 phases have reached the VR0 
Delta Threshold, and the MicVRCheckMode0 parameter is one, all enabled VR0 phase register delta values are 
statistically analyzed to determine the number of standard deviation units of each VR0 phase combined value (a 
non-linear distance from the mean of all enabled VR0 phase register combined values). If a VR0 combined standard 
deviation value meets or exceeds this parameter value, an error occurs (see MicCheckVRPhases test).

This maximum value standard derivation unit limit can be expressed as a signed numeric floating point value or an 
absolute numeric floating point value. A "+-" preceding the parameter numeric value signifies an absolute value, e.g 
"+-2.0" and "+-3" signify absolute values, while "2.0", "3", "+1.23", or "-0.95" are signed values .

A standard deviation unit limit value of 0.0 means that the VR0 phase combined standard deviation value is not 
checked.  ("0.0", "+0", "-0" or "+-0.0" all mean 0.0)

With signed limits, a positive limit means that the value being compared must be greater than or equal to the limit to 
meet or exceed the limit, while a negative limit means that the value being compared must be less than or equal to the 
limit to meet or exceed the limit, eg. a value of 2.345 will meet or exceed at limit of 2.0, while a value of -2.345 will meet 
or exceed a limit of -2.0.

With absolute value limits, the absolute value of the value being compared must be greater than or equal to the limit to 
meet or exceed the limit, eg. a value of 2.345 or -2.345 will meet or exceed a limit of 2.0.

Default
	 
   MicVRCheckComboStdDevLimit0 = 0.0

Dependencies

Required

Used by

MicCheckVRPhases

See Also

MicVRCheckMode0
MicVRMonitorPhaseMask0
Parameters

1.89. MicVRCheckComboStdDevLimit1

Description

Once the overall test time time period has elapsed and the specified number of VR1 phases have reached the VR1 
Delta Threshold, and the MicVRCheckMode1 parameter is one, all enabled VR1 phase register delta values are 
statistically analyzed to determine the number of standard deviation units of each VR1 phase combined value (a 
non-linear distance from the mean of all enabled VR1 phase register combined values). If a VR1 combined standard 
deviation value meets or exceeds this parameter value, an error occurs (see MicCheckVRPhases test).

This maximum value standard derivation unit limit can be expressed as a signed numeric floating point value or an 
absolute numeric floating point value. A "+-" preceding the parameter numeric value signifies an absolute value, e.g 
"+-2.0" and "+-3" signify absolute values, while "2.0", "3", "+1.23", or "-0.95" are signed values .

A standard deviation unit limit value of 0.0 means that the VR1 phase combined standard deviation value is not 
checked.  ("0.0", "+0", "-0" or "+-0.0" all mean 0.0)

With signed limits, a positive limit means that the value being compared must be greater than or equal to the limit to 
meet or exceed the limit, while a negative limit means that the value being compared must be less than or equal to the 
limit to meet or exceed the limit, eg. a value of 2.345 will meet or exceed at limit of 2.0, while a value of -2.345 will meet 
or exceed a limit of -2.0.

With absolute value limits, the absolute value of the value being compared must be greater than or equal to the limit to 
meet or exceed the limit, eg. a value of 2.345 or -2.345 will meet or exceed a limit of 2.0.

Default
	 
   MicVRCheckComboStdDevLimit1 = 0.0

Dependencies

Required

Used by

MicCheckVRPhases

See Also

MicVRCheckMode1
MicVRMonitorPhaseMask1
Parameters

1.90. MicVRCheckDeltaPctToleranceA0

Description

Once the overall test time time period has elapsed and the specified number of VR0 phases have reached the VR0 
Delta Threshold, and MicVRCheckMode0 is 5, all enabled VR0 Group A phase register deltas are checked against the 
VR0 Phase Group A Delta Percent Tolerance parameter (see MicCheckVRPhases test). If the phase delta is less than 
the VR0 Phase Group A Delta Percent Tolerance value, the following decisions occur:

1.	If VR0 Phase Group A delta recalculation is enabled by a nonzero VR0 Phase Group A Delta 2 Percent Tolerance 
parameter, MicVRCheckDelta2PctToleranceA0, the phase delta will be recalculated only if the phase's minimum 
value is the highest minimum value of all phases within VR0 Phase Group A. This recalculated delta is then checked 
against the VR0 Phase Group A Delta 2 Percent Tolerance parameter. The VR0 phase register is flagged if its 
recalculated delta is less than the VR0 Phase Group A Delta 2 Percent Tolerance value.
2.	If VR0 Phase Group A delta recalculation is disabled by a zero VR0 Phase Group A Delta 2 Percent Tolerance 
parameter or the phase's minimum value is not the highest minimum value of all phases within VR0 Phase Group A, 
the phase delta is then checked against the VR0 Phase Group A Delta Percent Tolerance parameter. The VR0 
phase register is flagged if its delta is less than the VR0 Phase Group A Delta Percent Tolerance value.

Default
	 
   MicVRCheckDeltaPctToleranceA0 = 0.0

Dependencies

Required

Used by

MicCheckVRPhases

See Also

MicVRCheckDelta2PctToleranceA0
MicVRCheckMode0
MicVRMonitorPhaseMask0
Parameters.

1.91. MicVRCheckDeltaPctToleranceB0

Description

Once the overall test time time period has elapsed and the specified number of VR0 phases have reached the VR0 
Delta Threshold, and MicVRCheckMode0 is 5, all enabled VR0 Group B phase register deltas are checked against the 
VR0 Phase Group B Delta Percent Tolerance parameter (see MicCheckVRPhases test). If the phase delta is less than 
the VR0 Phase Group B Delta Percent Tolerance value, the following decisions occur:

1.	If VR0 Phase Group B delta recalculation is enabled by a nonzero VR0 Phase Group B Delta 2 Percent Tolerance 
parameter, MicVRCheckDelta2PctToleranceB0, the phase delta will be recalculated only if the phase's minimum 
value is the highest minimum value of all phases within VR0 Phase Group B. This recalculated delta is then checked 
against the VR0 Phase Group B Delta 2 Percent Tolerance parameter. The VR0 phase register is flagged if its 
recalculated delta is less than the VR0 Phase Group B Delta 2 Percent Tolerance value.
2.	If VR0 Phase Group B delta recalculation is disabled by a zero VR0 Phase Group B Delta 2 Percent Tolerance 
parameter or the phase's minimum value is not the highest minimum value of all phases within VR0 Phase Group B, 
the phase delta is then checked against the VR0 Phase Group B Delta Percent Tolerance parameter. The VR0 
phase register is flagged if its delta is less than the VR0 Phase Group B Delta Percent Tolerance value.

Default
	 
   MicVRCheckDeltaPctToleranceB0 = 0.0

Dependencies

Required

Used by

MicCheckVRPhases

See Also

MicVRCheckDelta2PctToleranceB0
MicVRCheckMode0
MicVRMonitorPhaseMask0
Parameters.

1.92. MicVRCheckDeltaPctToleranceA1

Description

Once the overall test time time period has elapsed and the specified number of VR1 phases have reached the VR1 
Delta Threshold, and MicVRCheckMode1 is 5, all enabled VR1 Group A phase register deltas are checked against the 
VR1 Phase Group A Delta Percent Tolerance parameter (see MicCheckVRPhases test). If the phase delta is less than 
the VR1 Phase Group A Delta Percent Tolerance value, the following decisions occur:

1.	If VR1 Phase Group A delta recalculation is enabled by a nonzero VR1 Phase Group A Delta 2 Percent Tolerance 
parameter, MicVRCheckDelta2PctToleranceA1, the phase delta will be recalculated only if the phase's minimum 
value is the highest minimum value of all phases within VR1 Phase Group A. This recalculated delta is then checked 
against the VR1 Phase Group A Delta 2 Percent Tolerance parameter. The VR1 phase register is flagged if its 
recalculated delta is less than the VR1 Phase Group A Delta 2 Percent Tolerance value.
2.	If VR1 Phase Group A delta recalculation is disabled by a zero VR1 Phase Group A Delta 2 Percent Tolerance 
parameter or the phase's minimum value is not the highest minimum value of all phases within VR1 Phase Group A, 
the phase delta is then checked against the VR1 Phase Group A Delta Percent Tolerance parameter. The VR1 
phase register is flagged if its delta is less than the VR1 Phase Group A Delta Percent Tolerance value.

Default
	 
   MicVRCheckDeltaPctToleranceA1 = 0.0

Dependencies

Required

Used by

MicCheckVRPhases

See Also

MicVRCheckDelta2PctToleranceA1
MicVRCheckMode1
MicVRMonitorPhaseMask1
Parameters.

1.93. MicVRCheckDeltaPctToleranceB1

Description

Once the overall test time time period has elapsed and the specified number of VR1 phases have reached the VR1 
Delta Threshold, and MicVRCheckMode1 is 5, all enabled VR1 Group B phase register deltas are checked against the 
VR1 Phase Group B Delta Percent Tolerance parameter (see MicCheckVRPhases test). If the phase delta is less than 
the VR1 Phase Group B Delta Percent Tolerance value, the following decisions occur:

1.	If VR1 Phase Group B delta recalculation is enabled by a nonzero VR1 Phase Group B Delta 2 Percent Tolerance 
parameter, MicVRCheckDelta2PctToleranceB1, the phase delta will be recalculated only if the phase's minimum 
value is the highest minimum value of all phases within VR1 Phase Group B. This recalculated delta is then checked 
against the VR1 Phase Group B Delta 2 Percent Tolerance parameter. The VR1 phase register is flagged if its 
recalculated delta is less than the VR1 Phase Group B Delta 2 Percent Tolerance value.
2.	If VR1 Phase Group B delta recalculation is disabled by a zero VR1 Phase Group B Delta 2 Percent Tolerance 
parameter or the phase's minimum value is not the highest minimum value of all phases within VR1 Phase Group B, 
the phase delta is then checked against the VR1 Phase Group B Delta Percent Tolerance parameter. The VR1 
phase register is flagged if its delta is less than the VR1 Phase Group B Delta Percent Tolerance value.

Default
	 
   MicVRCheckDeltaPctToleranceB1 = 0.0

Dependencies

Required

Used by

MicCheckVRPhases

See Also

MicVRCheckDelta2PctToleranceB1
MicVRCheckMode1
MicVRMonitorPhaseMask1
Parameters.

1.94. MicVRCheckDelta2PctToleranceA0

Description

Once the overall test time time period has elapsed and the specified number of VR0 phases have reached the VR0 
Delta Threshold, and MicVRCheckMode0 is 5, all enabled VR0 Group A phase register deltas are checked against the 
VR0 Phase Group A Delta Percent Tolerance parameter (see MicCheckVRPhases test). If the phase delta is less than 
the VR0 Phase Group A Delta Percent Tolerance value, the following decisions occur:

1.	If VR0 Phase Group A delta recalculation is enabled by a nonzero VR0 Phase Group A Delta 2 Percent Tolerance 
parameter, the phase delta will be recalculated only if the phase's minimum value is the highest minimum value of all 
phases within VR0 Phase Group A. This recalculated delta is then checked against the VR0 Phase Group A Delta 2 
Percent Tolerance parameter. The VR0 phase register is flagged if its recalculated delta is less than the VR0 Phase 
Group A Delta 2 Percent Tolerance value.
2.	If VR0 Phase Group A delta recalculation is disabled by a zero VR0 Phase Group A Delta 2 Percent Tolerance 
parameter or the phase's minimum value is not the highest minimum value of all phases within VR0 Phase Group A, 
the phase delta is then checked against the VR0 Phase Group A Delta Percent Tolerance parameter, 
MicVRCheckDeltaPctToleranceA0. The VR0 phase register is flagged if its delta is less than the VR0 Phase Group A 
Delta Percent Tolerance value.

In summary, to disable VR0 Phase Group A delta recalculation, set the VR0 Phase Group A Delta 2 Percent Tolerance 
value to zero; to enable delta recalculation, set the VR0 Phase Group A Delta 2 Percent Tolerance value to a nonzero 
value; typically MicVRCheckDelta2PctToleranceA0 = MicVRCheckDeltaPctToleranceA0.

Default
	 
   MicVRCheckDelta2PctToleranceA0 = 0.0

Dependencies

Required

Used by

MicCheckVRPhases

See Also

MicVRCheckDeltaPctToleranceA0
MicVRCheckMode0
MicVRMonitorPhaseMask0
Parameters.

1.95. MicVRCheckDelta2PctToleranceB0

Description

Once the overall test time time period has elapsed and the specified number of VR0 phases have reached the VR0 
Delta Threshold, and MicVRCheckMode0 is 5, all enabled VR0 Group B phase register deltas are checked against the 
VR0 Phase Group B Delta Percent Tolerance parameter (see MicCheckVRPhases test). If the phase delta is less than 
the VR0 Phase Group B Delta Percent Tolerance value, the following decisions occur:

1.	If VR0 Phase Group B delta recalculation is enabled by a nonzero VR0 Phase Group B Delta 2 Percent Tolerance 
parameter, the phase delta will be recalculated only if the phase's minimum value is the highest minimum value of all 
phases within VR0 Phase Group B. This recalculated delta is then checked against the VR0 Phase Group B Delta 2 
Percent Tolerance parameter. The VR0 phase register is flagged if its recalculated delta is less than the VR0 Phase 
Group B Delta 2 Percent Tolerance value.
2.	If VR0 Phase Group B delta recalculation is disabled by a zero VR0 Phase Group B Delta 2 Percent Tolerance 
parameter or the phase's minimum value is not the highest minimum value of all phases within VR0 Phase Group B, 
the phase delta is then checked against the VR0 Phase Group B Delta Percent Tolerance parameter, 
MicVRCheckDeltaPctToleranceB0. The VR0 phase register is flagged if its delta is less than the VR0 Phase Group B 
Delta Percent Tolerance value.

In summary, to disable VR0 Phase Group B delta recalculation, set the VR0 Phase Group B Delta 2 Percent Tolerance 
value to zero; to enable delta recalculation, set the VR0 Phase Group B Delta 2 Percent Tolerance value to a nonzero 
value; typically MicVRCheckDelta2PctToleranceB0 = MicVRCheckDeltaPctToleranceB0.

Default
	 
   MicVRCheckDelta2PctToleranceB0 = 0.0

Dependencies

Required

Used by

MicCheckVRPhases

See Also

MicVRCheckDeltaPctToleranceB0
MicVRCheckMode0
MicVRMonitorPhaseMask0
Parameters.

1.96. MicVRCheckDelta2PctToleranceA1

Description

Once the overall test time time period has elapsed and the specified number of VR1 phases have reached the VR1 
Delta Threshold, and MicVRCheckMode1 is 5, all enabled VR1 Group A phase register deltas are checked against the 
VR1 Phase Group A Delta Percent Tolerance parameter (see MicCheckVRPhases test). If the phase delta is less than 
the VR1 Phase Group A Delta Percent Tolerance value, the following decisions occur:

1.	If VR1 Phase Group A delta recalculation is enabled by a nonzero VR1 Phase Group A Delta 2 Percent Tolerance 
parameter, the phase delta will be recalculated only if the phase's minimum value is the highest minimum value of all 
phases within VR1 Phase Group A. This recalculated delta is then checked against the VR1 Phase Group A Delta 2 
Percent Tolerance parameter. The VR1 phase register is flagged if its recalculated delta is less than the VR1 Phase 
Group A Delta 2 Percent Tolerance value.
2.	If VR1 Phase Group A delta recalculation is disabled by a zero VR1 Phase Group A Delta 2 Percent Tolerance 
parameter or the phase's minimum value is not the highest minimum value of all phases within VR1 Phase Group A, 
the phase delta is then checked against the VR1 Phase Group A Delta Percent Tolerance parameter, 
MicVRCheckDeltaPctToleranceA1. The VR1 phase register is flagged if its delta is less than the VR1 Phase Group A 
Delta Percent Tolerance value.

In summary, to disable VR1 Phase Group A delta recalculation, set the VR1 Phase Group A Delta 2 Percent Tolerance 
value to zero; to enable delta recalculation, set the VR1 Phase Group A Delta 2 Percent Tolerance value to a nonzero 
value; typically MicVRCheckDelta2PctToleranceA1 = MicVRCheckDeltaPctToleranceA1.

Default
	 
   MicVRCheckDelta2PctToleranceA1 = 0.0

Dependencies

Required

Used by

MicCheckVRPhases

See Also

MicVRCheckDeltaPctToleranceA1
MicVRCheckMode1
MicVRMonitorPhaseMask1
Parameters.

1.97. MicVRCheckDelta2PctToleranceB1

Description

Once the overall test time time period has elapsed and the specified number of VR1 phases have reached the VR1 
Delta Threshold, and MicVRCheckMode1 is 5, all enabled VR1 Group B phase register deltas are checked against the 
VR1 Phase Group B Delta Percent Tolerance parameter (see MicCheckVRPhases test). If the phase delta is less than 
the VR1 Phase Group B Delta Percent Tolerance value, the following decisions occur:

1.	If VR1 Phase Group B delta recalculation is enabled by a nonzero VR1 Phase Group B Delta 2 Percent Tolerance 
parameter, the phase delta will be recalculated only if the phase's minimum value is the highest minimum value of all 
phases within VR1 Phase Group B. This recalculated delta is then checked against the VR1 Phase Group B Delta 2 
Percent Tolerance parameter. The VR1 phase register is flagged if its recalculated delta is less than the VR1 Phase 
Group B Delta 2 Percent Tolerance value.
2.	If VR1 Phase Group B delta recalculation is disabled by a zero VR1 Phase Group B Delta 2 Percent Tolerance 
parameter or the phase's minimum value is not the highest minimum value of all phases within VR1 Phase Group B, 
the phase delta is then checked against the VR1 Phase Group B Delta Percent Tolerance parameter, 
MicVRCheckDeltaPctToleranceB1. The VR1 phase register is flagged if its delta is less than the VR1 Phase Group B 
Delta Percent Tolerance value.

In summary, to disable VR1 Phase Group B delta recalculation, set the VR1 Phase Group B Delta 2 Percent Tolerance 
value to zero; to enable delta recalculation, set the VR1 Phase Group B Delta 2 Percent Tolerance value to a nonzero 
value; typically MicVRCheckDelta2PctToleranceB1 = MicVRCheckDeltaPctToleranceB1.

Default
	 
   MicVRCheckDelta2PctToleranceB1 = 0.0

Dependencies

Required

Used by

MicCheckVRPhases

See Also

MicVRCheckDeltaPctToleranceB1
MicVRCheckMode1
MicVRMonitorPhaseMask1
Parameters.

1.98. MicVRCheckPhaseThresholdMask0

Description

Allows individual MIC card VR0 phase registers to trigger the VR0 Delta Threshold or be ignored. A bit value of 1 
enables a phase register to trigger the Delta Threshold; a value of 0 disables triggering. Each bit corresponds to a VR0 
phase register. Bit 0 (LSB) corresponds with VR0 phase 0, bit 1 corresponds with VR0 phase 1, and so on.

The purpose of the threshold parameters are to provide a means of ensuring that adequate VR current loading has 
occurred during the test time time period.

Default
	 
   MicVRCheckPhaseThresholdMask0 = 0xFF

Dependencies

Required

Used by

MicCheckVRPhases

See Also

MicVRMonitorPhaseMask0
Parameters

1.99. MicVRCheckPhaseThresholdMask1

Description

Allows individual MIC card VR1 phase registers to trigger the VR1 Delta Threshold or be ignored. A bit value of 1 
enables a phase register to trigger the Delta Threshold; a value of 0 disables triggering. Each bit corresponds to a VR1 
phase register. Bit 0 (LSB) corresponds with VR1 phase 0, bit 1 corresponds with VR1 phase 1, and so on.

The purpose of the threshold parameters are to provide a means of ensuring that adequate VR current loading has 
occurred during the test time time period.

Default
	 
   MicVRCheckPhaseThresholdMask1 = 0x1F

Dependencies

Required

Used by

MicCheckVRPhases

See Also

MicVRMonitorPhaseMask1
Parameters.

1.100. MicVRCheckPhaseThresholdCount0

Description

Specifies the number of VR0 phases that must reach the VR0 Delta Threshold value during the overall test time time 
period. If the specified number of VR0 phases did not reach the VR0 Delta Threshold, an error occurs.

The purpose of the threshold parameters are to provide a means of ensuring that adequate VR current loading has 
occurred during the test time time period.  

Default
	 
   MicVRCheckPhaseThresholdCount0 = 1

Dependencies

Required

Used by

MicCheckVRPhases

See Also

MicVRMonitorPhaseMask0
MicVRCheckPhaseThresholdMask0
MicVRCheckDeltaThreshold0
Parameters

1.101. MicVRCheckPhaseThresholdCount1

Description

Specifies the number of VR1 phases that must reach the VR1 Delta Threshold value during the overall test time time 
period. If the specified number of VR1 phases did not reach the VR1 Delta Threshold, an error occurs.

The purpose of the threshold parameters are to provide a means of ensuring that adequate VR current loading has 
occurred during the test time time period.  

Default
	 
   MicVRCheckPhaseThresholdCount1 = 1

Dependencies

Required

Used by

MicCheckVRPhases

See Also

MicVRMonitorPhaseMask1
MicVRCheckPhaseThresholdMask1
MicVRCheckDeltaThreshold1
Parameters

1.102. MicVRMonitorSKUInfoArray

Description

Once the overall test time time period has elapsed and the specified number of VR0 phases have reached the VR0 
Delta Threshold, and MicVRCheckMode0 is zero, all enabled VR0 phase register deltas are checked against the VR0 
Delta Tolerance parameter (see MicCheckVRPhases test). The VR0 phase register is flagged if its delta is less than the 
VR0 Delta Tolerance value.

This parameter array is a table of MicCheckVRPhases parameters that can be conditionally overwritten during 
autoconfigure. These parameters are those that will need to be changed to SKU appropriate values in the end test 
package file. An example is the MicVRMonitorPhaseMask0 parameter - where the majority of MIC SKUs implement 8 
VR0 phases, while a few low-power SKUs (5000 series and Dense Form Factor [DFF]) implement 7 VR 0 phases; the 
parameter array can be set up to overwrite the MicVRMonitorPhaseMask0 value during autoconfigure, if a low-power 
SKU is detected.

This parameter array is a table comprising a list of SKUs with the following columns:

Column
Column Name
VR Check Parameter Modified
Data Type
Comment

1
SKU
none - key column
string
Left-most part of Intel TA# to left of '-' (e.g. if TA# is "G65757-351", then SKU is "G65757")

2
Monitor Time
MicVRMonitorTime
integer
Overwrite parameter if 

3
Phase Mask 0
MicVRMonitorPhaseMask0
integer


4
Phase Mask 0
MicVRMonitorPhaseMask1
integer


5
Phase Threshold Mask 0
MicVRCheckPhaseThresholdMask0
integer


6
Phase Threshold Mask 1
MicVRCheckPhaseThresholdMask1
integer


7
Phase Threshold Count 0
MicVRCheckPhaseThresholdMask0
integer


8
Phase Threshold Count 1
MicVRCheckPhaseThresholdMask1
integer


9
Min Std Dev Limit 0
MicVRCheckMinStdDevLimit0
floating point


10
Min Std Dev Limit 1
MicVRCheckMinStdDevLimit1
floating point


11
Max Std Dev Limit 0
MicVRCheckMaxStdDevLimit0
floating point


12
Max Std Dev Limit 1
MicVRCheckMaxStdDevLimit1
floating point


13
Delta Std Dev Limit 0
MicVRCheckDeltaStdDevLimit0
floating point


14
Delta Std Dev Limit 1
MicVRCheckDeltaStdDevLimit1
floating point


15
Combo Std Dev Limit 0
MicVRCheckComboStdDevLimit0
floating point


16
Combo Std Dev Limit 1
MicVRCheckComboStdDevLimit1
floating point


17
Delta Pct Tolerance A0
MicVRCheckDeltaPctToleranceA0
floating point


18
Delta Pct Tolerance B0
MicVRCheckDeltaPctToleranceB0
floating point


19
Delta Pct Tolerance A1
MicVRCheckDeltaPctToleranceA1
floating point


20
Delta Pct Tolerance B1
MicVRCheckDeltaPctToleranceB1
floating point


21
Delta 2 Pct Tolerance A0
MicVRCheckDelta2PctToleranceA0
floating point


22
Delta 2 Pct Tolerance B0
MicVRCheckDelta2PctToleranceB0
floating point


23
Delta 2 Pct Tolerance A1
MicVRCheckDelta2PctToleranceA1
floating point


24
Delta 2 Pct Tolerance B1
MicVRCheckDelta2PctToleranceB1
floating point



If an integer column contains a zero, or if a floating point column contains a zero  ("0.0", "0", "+0", "-0", "+-0.0", etc.) the 
respective parameter is not overwritten.

Example

SKU entry H13742 contains the following columns:

Column
Column Name
Column Data
VR Check Parameter Modified
Comment
1
SKU
 H13742
none - key column

2
Monitor Time
0
none

3
Phase Mask 0
0x7F
MicVRMonitorPhaseMask0
MicVRMonitorPhaseMask0 parameter overwritten with 0x7F
4
Phase Mask 0
0
none

5
Phase Threshold Mask 0
0
none

6
Phase Threshold Mask 1
0xC3
MicVRCheckPhaseThresholdMask1
MicVRCheckPhaseThresholdMask1 parameter overwritten with 0xC3
7
Phase Threshold Count 0
0
none

8
Phase Threshold Count 1
3
MicVRCheckPhaseThresholdCount1
MicVRCheckPhaseThresholdCount1 parameter overwritten with 3
9
Min Std Dev Limit 0
0
none

10
Min Std Dev Limit 1
0
none

11
Max Std Dev Limit 0
0
none

12
Max Std Dev Limit 1
0
none

13
Delta Std Dev Limit 0
0
none

14
Delta Std Dev Limit 1
-1.95
MicVRCheckDeltaStdDevLimit1
MicVRCheckDeltaStdDevLimit1 parameter overwritten with -1.95
15
Combo Std Dev Limit 0
0
none

16
Combo Std Dev Limit 1
0
none

17
Delta Pct Tolerance A0
0
none

18
Delta Pct Tolerance B0
0
none

19
Delta Pct Tolerance A1
0
none

20
Delta Pct Tolerance B1
0
none

21
Delta 2 Pct Tolerance A0
0
none

22
Delta 2 Pct Tolerance B0
0
none

23
Delta 2 Pct Tolerance A1
0
none

24
Delta 2 Pct Tolerance B1
0
none


Default
	 
   None
 
Used by

Test 0 - Auto-Configuration

See Also

MicVRCheckMode0
MicVRMonitorPhaseMask0
Parameters

1.103. MicVRDisplayMode

Description

   Determines the MicDisplayVRPhases utility display mode. If mode is zero, information about all of the enabled phases 
is displayed during each occurrence of the periodic VR phase register acquisition interval. If mode is one, information 
about all of the enabled phases is displayed once at the end of the utility execution.

Default
	 
   MicVRDisplayMode = 0

Dependencies

Required

Used by

MicDisplayVRPhases

See Also

MicVRMonitorInterval
MicVRMonitorIntervalDelay
MicVRMonitorAvgCount
Parameters

1.104. VR Phase Info Block

Description

This is a block of INFO messages that summarizes the VR phase monitoring results. The minimum, maximum, and 
delta values, along with their standard deviation info is displayed for each VR phase. Also, a summary of the overall 
phase mean and standard deviation info is displayed for each VR. This INFO message can optionally be redirected to 
log files, which can ultimately be used to track MIC card VR phase statistics by card serial number.

	The the VR Phase Info Block is always displayed when the MicDisplayVRPhases utility exits or when the 
MicCheckVRPhases test detects a failure. The MicVRCheckInfoMode parameter determines whether the VR Phase 
Info Block is displayed when the MicCheckVRPhases test passes.

Example

01/09/2015 14:05:28  INFO  H16728-257/DFF SKU 1/MIC Monitor/Serial Test/MicWorkload+VR_Test/MicCheckVRPhases
VR0 Check Mode = 4
01/09/2015 14:05:28  INFO  H16728-257/DFF SKU 1/MIC Monitor/Serial Test/MicWorkload+VR_Test/MicCheckVRPhases
VR0 Phase Register 0 min(avg) = 61, max(avg) = 71, max(avg)-min(avg) = 10
01/09/2015 14:05:28  INFO  H16728-257/DFF SKU 1/MIC Monitor/Serial Test/MicWorkload+VR_Test/MicCheckVRPhases
VR0 Phase Register 1 min(avg) = 61, max(avg) = 71, max(avg)-min(avg) = 10
01/09/2015 14:05:28  INFO  H16728-257/DFF SKU 1/MIC Monitor/Serial Test/MicWorkload+VR_Test/MicCheckVRPhases
VR0 Phase Register 2 min(avg) = 61, max(avg) = 71, max(avg)-min(avg) = 10
01/09/2015 14:05:28  INFO  H16728-257/DFF SKU 1/MIC Monitor/Serial Test/MicWorkload+VR_Test/MicCheckVRPhases
VR0 Phase Register 3 min(avg) = 63, max(avg) = 71, max(avg)-min(avg) = 8
01/09/2015 14:05:28  INFO  H16728-257/DFF SKU 1/MIC Monitor/Serial Test/MicWorkload+VR_Test/MicCheckVRPhases
VR0 Phase Register 4 min(avg) = 63, max(avg) = 71, max(avg)-min(avg) = 8
01/09/2015 14:05:28  INFO  H16728-257/DFF SKU 1/MIC Monitor/Serial Test/MicWorkload+VR_Test/MicCheckVRPhases
VR0 Phase Register 5 min(avg) = 63, max(avg) = 71, max(avg)-min(avg) = 8
01/09/2015 14:05:28  INFO  H16728-257/DFF SKU 1/MIC Monitor/Serial Test/MicWorkload+VR_Test/MicCheckVRPhases
VR0 Phase Register 6 min(avg) = 62, max(avg) = 71, max(avg)-min(avg) = 9
01/09/2015 14:05:28  INFO  H16728-257/DFF SKU 1/MIC Monitor/Serial Test/MicWorkload+VR_Test/MicCheckVRPhases
VR0 Phase Register 0 standard deviation units:
 min = -1.299867, max = 0.000000, delta = 0.928477
01/09/2015 14:05:28  INFO  H16728-257/DFF SKU 1/MIC Monitor/Serial Test/MicWorkload+VR_Test/MicCheckVRPhases
VR0 Phase Register 0 combined standard deviation units:
 avg(min,max,delta) = 0.610861, avg(abs(min,max,delta)) = 0.928673
01/09/2015 14:05:28  INFO  H16728-257/DFF SKU 1/MIC Monitor/Serial Test/MicWorkload+VR_Test/MicCheckVRPhases
VR0 Phase Register 1 standard deviation units:
 min = -1.299867, max = 0.000000, delta = 0.928477
01/09/2015 14:05:28  INFO  H16728-257/DFF SKU 1/MIC Monitor/Serial Test/MicWorkload+VR_Test/MicCheckVRPhases
VR0 Phase Register 1 combined standard deviation units:
 avg(min,max,delta) = 0.610861, avg(abs(min,max,delta)) = 0.928673
01/09/2015 14:05:28  INFO  H16728-257/DFF SKU 1/MIC Monitor/Serial Test/MicWorkload+VR_Test/MicCheckVRPhases
VR0 Phase Register 2 standard deviation units:
 min = -1.299867, max = 0.000000, delta = 0.928477
01/09/2015 14:05:28  INFO  H16728-257/DFF SKU 1/MIC Monitor/Serial Test/MicWorkload+VR_Test/MicCheckVRPhases
VR0 Phase Register 2 combined standard deviation units:
 avg(min,max,delta) = 0.610861, avg(abs(min,max,delta)) = 0.928673
01/09/2015 14:05:28  INFO  H16728-257/DFF SKU 1/MIC Monitor/Serial Test/MicWorkload+VR_Test/MicCheckVRPhases
VR0 Phase Register 3 standard deviation units:
 min = 0.928477, max = 0.000000, delta = -1.299867
01/09/2015 14:05:28  INFO  H16728-257/DFF SKU 1/MIC Monitor/Serial Test/MicWorkload+VR_Test/MicCheckVRPhases
VR0 Phase Register 3 combined standard deviation units:
 avg(min,max,delta) = -0.964169, avg(abs(min,max,delta)) = 1.191178
01/09/2015 14:05:28  INFO  H16728-257/DFF SKU 1/MIC Monitor/Serial Test/MicWorkload+VR_Test/MicCheckVRPhases
VR0 Phase Register 4 standard deviation units:
 min = 0.928477, max = 0.000000, delta = -1.299867
01/09/2015 14:05:28  INFO  H16728-257/DFF SKU 1/MIC Monitor/Serial Test/MicWorkload+VR_Test/MicCheckVRPhases
VR0 Phase Register 4 combined standard deviation units:
 avg(min,max,delta) = -0.964169, avg(abs(min,max,delta)) = 1.191178
01/09/2015 14:05:28  INFO  H16728-257/DFF SKU 1/MIC Monitor/Serial Test/MicWorkload+VR_Test/MicCheckVRPhases
VR0 Phase Register 5 standard deviation units:
 min = 0.928477, max = 0.000000, delta = -1.299867
01/09/2015 14:05:28  INFO  H16728-257/DFF SKU 1/MIC Monitor/Serial Test/MicWorkload+VR_Test/MicCheckVRPhases
VR0 Phase Register 5 combined standard deviation units:
 avg(min,max,delta) = -0.964169, avg(abs(min,max,delta)) = 1.191178
01/09/2015 14:05:28  INFO  H16728-257/DFF SKU 1/MIC Monitor/Serial Test/MicWorkload+VR_Test/MicCheckVRPhases
VR0 Phase Register 6 standard deviation units:
 min = -0.185695, max = 0.000000, delta = -0.185695
01/09/2015 14:05:28  INFO  H16728-257/DFF SKU 1/MIC Monitor/Serial Test/MicWorkload+VR_Test/MicCheckVRPhases
VR0 Phase Register 6 combined standard deviation units:
 avg(min,max,delta) = -0.176654, avg(abs(min,max,delta)) = 0.176654
01/09/2015 14:05:28  INFO  H16728-257/DFF SKU 1/MIC Monitor/Serial Test/MicWorkload+VR_Test/MicCheckVRPhases
VR Phase Registers min(avg)(avg) = 64, max(avg)(avg) = 71
01/09/2015 14:05:28  INFO  H16728-257/DFF SKU 1/MIC Monitor/Serial Test/MicWorkload+VR_Test/MicCheckVRPhases
VR0 Phase Register min:
 mean = 62.166667, standard deviation = 0.897527
01/09/2015 14:05:28  INFO  H16728-257/DFF SKU 1/MIC Monitor/Serial Test/MicWorkload+VR_Test/MicCheckVRPhases
VR0 Phase Register max:
 mean = 71.000000, standard deviation = 0.408248
01/09/2015 14:05:28  INFO  H16728-257/DFF SKU 1/MIC Monitor/Serial Test/MicWorkload+VR_Test/MicCheckVRPhases
VR0 Phase Register delta:
 mean = 9.166667, standard deviation = 0.897527
01/09/2015 14:05:28  INFO  H16728-257/DFF SKU 1/MIC Monitor/Serial Test/MicWorkload+VR_Test/MicCheckVRPhases
VR0 Phase Mask = 0x7F
01/09/2015 14:05:28  INFO  H16728-257/DFF SKU 1/MIC Monitor/Serial Test/MicWorkload+VR_Test/MicCheckVRPhases
VR1 Check Mode = 5
01/09/2015 14:05:28  INFO  H16728-257/DFF SKU 1/MIC Monitor/Serial Test/MicWorkload+VR_Test/MicCheckVRPhases
VR1 Phase Register 0 min(avg) = 65, max(avg) = 69, max(avg)-min(avg) = 4
01/09/2015 14:05:28  INFO  H16728-257/DFF SKU 1/MIC Monitor/Serial Test/MicWorkload+VR_Test/MicCheckVRPhases
VR1 Phase Register 1 min(avg) = 65, max(avg) = 69, max(avg)-min(avg) = 4
01/09/2015 14:05:28  INFO  H16728-257/DFF SKU 1/MIC Monitor/Serial Test/MicWorkload+VR_Test/MicCheckVRPhases
VR1 Phase Register 2 min(avg) = 64, max(avg) = 69, max(avg)-min(avg) = 5
01/09/2015 14:05:28  INFO  H16728-257/DFF SKU 1/MIC Monitor/Serial Test/MicWorkload+VR_Test/MicCheckVRPhases
VR1 Phase Register 6 min(avg) = 70, max(avg) = 74, max(avg)-min(avg) = 4
01/09/2015 14:05:28  INFO  H16728-257/DFF SKU 1/MIC Monitor/Serial Test/MicWorkload+VR_Test/MicCheckVRPhases
VR1 Phase Register 7 min(avg) = 70, max(avg) = 74, max(avg)-min(avg) = 4
01/09/2015 14:05:28  INFO  H16728-257/DFF SKU 1/MIC Monitor/Serial Test/MicWorkload+VR_Test/MicCheckVRPhases
VR1 Phase Register 0 standard deviation units:
 min = -1.000000, max = -1.000000, delta = -0.577350
01/09/2015 14:05:28  INFO  H16728-257/DFF SKU 1/MIC Monitor/Serial Test/MicWorkload+VR_Test/MicCheckVRPhases
VR1 Phase Register 0 combined standard deviation units:
 avg(min,max,delta) = -0.752358, avg(abs(min,max,delta)) = 0.752358
01/09/2015 14:05:28  INFO  H16728-257/DFF SKU 1/MIC Monitor/Serial Test/MicWorkload+VR_Test/MicCheckVRPhases
VR1 Phase Register 1 standard deviation units:
 min = -1.000000, max = -1.000000, delta = -0.577350
01/09/2015 14:05:28  INFO  H16728-257/DFF SKU 1/MIC Monitor/Serial Test/MicWorkload+VR_Test/MicCheckVRPhases
VR1 Phase Register 1 combined standard deviation units:
 avg(min,max,delta) = -0.752358, avg(abs(min,max,delta)) = 0.752358
01/09/2015 14:05:28  INFO  H16728-257/DFF SKU 1/MIC Monitor/Serial Test/MicWorkload+VR_Test/MicCheckVRPhases
VR1 Phase Register 2 standard deviation units:
 min = -1.400000, max = -1.000000, delta = 1.732051
01/09/2015 14:05:28  INFO  H16728-257/DFF SKU 1/MIC Monitor/Serial Test/MicWorkload+VR_Test/MicCheckVRPhases
VR1 Phase Register 2 combined standard deviation units:
 avg(min,max,delta) = 0.515585, avg(abs(min,max,delta)) = 1.514126
01/09/2015 14:05:29  INFO  H16728-257/DFF SKU 1/MIC Monitor/Serial Test/MicWorkload+VR_Test/MicCheckVRPhases
VR1 Phase Register 6 standard deviation units:
 min = 1.000000, max = 1.000000, delta = -0.577350
01/09/2015 14:05:29  INFO  H16728-257/DFF SKU 1/MIC Monitor/Serial Test/MicWorkload+VR_Test/MicCheckVRPhases
VR1 Phase Register 6 combined standard deviation units:
 avg(min,max,delta) = 0.075788, avg(abs(min,max,delta)) = 0.752358
01/09/2015 14:05:29  INFO  H16728-257/DFF SKU 1/MIC Monitor/Serial Test/MicWorkload+VR_Test/MicCheckVRPhases
VR1 Phase Register 7 standard deviation units:
 min = 1.000000, max = 1.000000, delta = -0.577350
01/09/2015 14:05:29  INFO  H16728-257/DFF SKU 1/MIC Monitor/Serial Test/MicWorkload+VR_Test/MicCheckVRPhases
VR1 Phase Register 7 combined standard deviation units:
 avg(min,max,delta) = 0.075788, avg(abs(min,max,delta)) = 0.752358
01/09/2015 14:05:29  INFO  H16728-257/DFF SKU 1/MIC Monitor/Serial Test/MicWorkload+VR_Test/MicCheckVRPhases
VR Phase Registers min(avg)(avg) = 64, max(avg)(avg) = 71
01/09/2015 14:05:29  INFO  H16728-257/DFF SKU 1/MIC Monitor/Serial Test/MicWorkload+VR_Test/MicCheckVRPhases
VR1 Phase Register min:
 mean = 67.500000, standard deviation = 2.500000
01/09/2015 14:05:29  INFO  H16728-257/DFF SKU 1/MIC Monitor/Serial Test/MicWorkload+VR_Test/MicCheckVRPhases
VR1 Phase Register max:
 mean = 71.500000, standard deviation = 2.500000
01/09/2015 14:05:29  INFO  H16728-257/DFF SKU 1/MIC Monitor/Serial Test/MicWorkload+VR_Test/MicCheckVRPhases
VR1 Phase Register delta:
 mean = 4.250000, standard deviation = 0.433013
01/09/2015 14:05:29  INFO  H16728-257/DFF SKU 1/MIC Monitor/Serial Test/MicWorkload+VR_Test/MicCheckVRPhases
VR1 Phase Mask = 0xC7




1.105. Error Codes


ERROR codes formatted as 0xMMMTTEEE 

MMM - Module number  
TT      - Test number 
EEE   - Error code number, as below:

Error Code   	Message
522XX003 	Invalid test number (X).
522XX004	Test_name: Failed to read parameter 'param_name', with error status 'X'.
522XX005	Failed to set cleanup routine!
522XX006	Test_name: Device ID Config Miscompare! Expected Xh, Received: Yh.
522XX00E	Test_name: (BMC or SMC) command unsuccessful. CompCode=XXh
522XX00F	Test_name: Error response (X) from imbapi lib.
522XX010	CheckSELError Failed:SEL repository contained an un-masked Event Message! <Message>
522XX01A	Failed setting Test_name. Expected:Xh, Received:Xh. (FRU read error)
522XX01D	Test_name. Expected at least X bytes. Received X (IPMI read error)
522XX01E	Test_name. Error response (X) from IPMI driver.
522XX030	Test_name. GUID (ID) Matched Default! Expected: ID, Received: ID
522XX031	Test_name. Error with parameter 'name'. Expected 'string'. Received 'string'.
522XX032	Test_name. Error with parameter 'name'. Expected 'integer'. Received 'integer'.
522XX033	Test_name. Error with parameter 'name'. Expected 'unsigned integer'. Received 'unsigned integer'.
522XX034	Test_name. Error reading SEL Entry number.
522XX035	Test_name. Error: internal parameter 'name' may not be NULL.
522XX036	Test_name. Error with parameter 'name'. Expected size 'count', received size 'count'.\
52264037 	Actual manufacturing mode status (X) does not match expected manufacturing mode status(Y)
522XX03A,	No Fan Sensor Found in SDR records - cannot run fan test.
522XX03B	Parameter 'name' must be greater than zero
522XX03C	Fan PWM set to X reported tach reading Y. Expected Z. Tolerance set to X
522XX03D	Fan tach at 40 percent PWM (0xX) must be X percent less than fan tach at 100 percent PWM (0xY)
522XX03E	Incorrect FRU Manufacturing Date: <Field> (X) must be between Y and Z
522XX03F	Unable to open file X522XX040	Test_name. Failed to get FRU Inventory.
522XX041	Test_name. Read FRU Inventory size of Zero
522XX042	File (name) is empty
522XX051	Test_name: <Sensor> crossed. Sensor reads: X, threshold value: Y
522XX060	Test_name. Called with bad parameters (X).
522XX070	VR Phase Register Test Error (parameter error).
522XX071	VR Phase Register Test Error (parameter error).
522XX072	VR Phase Register Test Error (both VRs).
522XX073	VR Phase Register Test Error (either VR0 or VR1).
522XX074	VR Phase Register Error (MicVRCheckModeX = 0).
522XX075	VR Phase Register Error (MicVRCheckModeX = 0).
522XX076	VR Phase Register Error (MicVRCheckModeX = 1-4).
522XX077	VR Phase Register Error (MicVRCheckModeX = 1-4).
522XX078	VR Phase Register Error (MicVRCheckModeX = 5, no phase recalculation).
522XX079	VR Phase Register Error (MicVRCheckModeX = 5, phase recalculation).
522XX0C0	Misc messages such as memory allocation failures

Overall Debug Hints:
Ensure the MIC card is plugged into correct slot, as indicated in MicRdSlot.

Be very careful about changing parameters in this test. The most likely one to be changed is MicRdSlot (to indicate the 
slot the MIC card is plugged into).

Make sure the IMB (or IPMI0)  driver is correctly installed on the host system. Check with this command:
rpm -qa | grep imb

The host baseboard must support BMC to SMC communication. 

See "IPMI Intelligent Platform Management Interface Specification Second Generation v2.0" for complete IPMI 
command information.

IMPORTANT: Fan Control test must be run without uOS booted.

If MicCheckFanControl is sporadically failing, make sure MicFanDelay is set to the correct value (currently 2 seconds, at 
this point). Any change in this value should be carefully validated to ensure test runs are stable.

Error codes returned by 522XX00E have three main categories:
80h: This usually means the card is trying to exit Manufacturing Mode, but the FRU data is not correctly written.
82h: Communication between BMC and SMC was unsuccessful. This might indicate an issue with the BMC on the host, 
or the SMC on the card. Check to see if the SMC light is blinking - if not, there may be a hardware issue 
with the SMC. 
C1h: Some calls, such as FRU Write and SMC Cold Reset, can only be called when manufacturing mode is enabled. 

1.106. Glossary


Term	Definition

FRU	Field Replaceable Unit (typically includes information such as Serial Number, GUID, Manufacturer ID, 
Product Name, etc)

GUID	Guaranteed Unique ID

Host Board	The baseboard into which the MIC card is plugged via a PCI-e slot. 

MIC	Many Integrated Cores - an add-in card with processors and memory, to offload compute intensive 
processing

SDR	Sensor Data Repository

SEL	System Event Log

SMC	System Management Controller - similar to the BMC on the host board. It controls temperatures and other 
intelligent board management.

uOS	micro-OS - an embedded OS on the MIC card, which runs separately from the OS on the host board.

Usage mode	The mode which the MIC card is booted in. There are multiple modes, including Normal (for regular 
usage), Maintenance (to perform card maintenance), etc.

UUT	Unit Under Test - the MIC card which is being tested.




Your index page goes here...

In MS-Word, select INDEX AND CONTENTS from the INSERT menu.
Select INDEX and click OK.
header text	 


footer text	 Page 1
