STM Online Help: xstm Online Help (graphical interface)

Top
Information
Use this function to create a log of information specific to each selected device, which has an information function,
including:
The product identifier
A description of the device
The hardware path to the device
The vendor
Typically, the firmware revision code, if firmware is present in the selected devices, will also be displayed.
The information tool runs on all selected devices that are not currently busy.
When the tool exits, returning a "SUCCESSFUL" or "WARNING" status, you should consult the Information Log...,
Failure Log..., and/or Activity Log... for information retrieved by the tool about the hardware.
Top
Verify
Use this function to verify all selected devices for which a verifier function exists. The purpose of the verification
procedure is to ensure as quickly as possible that the target hardware is usable, and that you will be successful in using
the device. Verifiers don't tend to isolate down to the FRU level, nor are they generally interactive.
To verify a selected device or devices, the target device(s) must not only support verification, it must also currently be
idle.
When you first start to verify a device(s), the device(s) state on the device map will be changed to "RUNNING".
If the operation requires you to interact with the interface, the device state will change to "Query Pending". If the UI
started the tool, the query will display automatically. If the UI did not start the tool, you must click on the device, or
select
Display "Query Pending" from the "Tools --> Tools Management" menu, to display the query.
Once the verify operation has completed, this state will change to "Success", "WARNING", or "FAILURE", as
appropriate.
You should then consult the Failure Log... for information on tool failures, and the Activity Log... for all other tool
activity information.
Top
Diagnose
Use this function to diagnose all selected devices for which a diagnostic exists. The purpose of the diagnostic
procedure is to test the target hardware as completely as possible, and if any errors are found, to isolate to the FRU
level. Isolation to the component level is also provided, when possible. Diagnostic modules are not generally
interactive.