Technical data

CHALLENGE/Onyx Diagnostic Road Map 6-45
After setting the report level, choose a test mode (if desired). The following modes are
available:
quickmode For the memory tests, quick mode tests every nth byte instead of every
byte, where n varies from 96 to 7680 depending upon the test. The goal in
quickmode is to test 16 GB in about 10 minutes, which is accomplished by
testing every nth byte. n varies depending upon how fast or slow a test
was timed to run.
To enable quickmode, enter
setenv quickmode 1
To disable quickmode, enter
unsetenv quickmode
continue-on-error
Normally, MC3 tests stop after the first error. Enabling continue-on-error
mode causes the tests to continue even after an error is encountered.
To enable continue-on-error mode, enter
setenv cont_on_error 1
To disable continue-on-error mode, enter
unsetenv cont_on_error
By default, continue-on-error mode is disabled.
memall Runs all MC3 diagnostic commands. Can be used in quickmode and in
continue-on-error mode.
memquick Runs only the fastest MC3 diagnostic commands: mem1, mem2, mem3,
mem5, mem8, mem9, and mem10. The memquick command can be used in
quickmode and in continue-on-error mode.
There are also two special commands to help isolate memory problems in banks:
ena_bnk Enable one bank at a time.
dis_bnk Disable one bank at a time.