STM Online Help: cstm Online Help (command-line interface)
Allow User Queries (WARNING: Not Allowing Queries May Cause Data Loss)
If you want to interact with a specified tool, instead of using the tool's default information values, enter "y" at this
prompt.
WARNING: When you disable the "Allow User Queries" function, some tools will perform DESTRUCTIVE tests.
This means that ALL DATA on unmounted disks WILL BE DESTROYED. The ability to disable this function is
intended for manufacturing purposes only. It is highly recommended that you use the "Allow User Queries" function,
and DO NOT DISABLE IT.
Top
VerOptions
Syntax: veroptions | vop [execctrl] [iterations {<loop count>} | time {<minutes>} | continuously] [behavior] [errorexit |
errorcount {<errors allowed before test termination>}] [testcoverage] [maxcoverage | medcoverage | mincoverage]
[gentactlog {yes|no}] [reporterrors | reportwarnings | reportinfo] [queries] [queryallow | querynondes | querydes]
Use this command to configure the options which will be used for subsequently executing verify tools, including:
Controlling execution time/loop limits
Defining behavior on error detection
Defining test coverage
Defining the contents of the InfoActLog
Allowing/disallowing user queries
Execution Control
You can control execution of future diagnose commands via the three options associated with this heading:
Iterations to Loop -- number of times to repeat diagnose procedure
Execution Time Limit, in Minutes -- how long (in minutes) to run test
Loop Continuously -- repeat diagnose procedure until it is halted or aborted
Iterations to Loop
Enter "iterations" if you want to define the number of times the diagnose test procedure is to be repeated before it halts.
Execution Time Limit, in Minutes
Enter "time" if you want to define the length of time the diagnose test procedure is to run (in minutes), before it halts.
Loop Continuously
Enter "continuously" if you want the diagnose test procedure to repeat until you halt or abort it.
Behavior on Errors
Using the options associated with this heading, you can define the way in which you want a specified tool to behave
on encountering a "soft" error; e.g., a recoverable read error (hard errors, by contrast, cause the tool to create a failure
log and exit, no matter how this option is set).