| Screen/Message |
Meaning |
Condition/Remarks |
 |
No memory function was detected by SIMCHECK. |
There is a major problem with the memory's control signals, or
the memory device is not supported. |
 |
The main Vdd power line has a severe short. |
The Vdd line may be shorted to Ground. |
 |
Data bit error. The fifth bit of byte 3 failed. |
Data Memory error. Many variations of this error are possible.
|
 |
Pressing
indicates that
DQ22, pin 21 is the problem. |
The last line of the display will change to provide additional
information when pressing
. See Manual
Section 4.5.6 for further information. |
 |
Pressing
indicates the
failure occurred at location 00FC00B4. |
|
 |
Pressing
shows the written
pattern and the pattern read. |
|
 |
Pressing
identifies the
function that caused the error to result. |
|
 |
Pressing
shows the states
of the RAS and CAS signals (in Hex). RAS3..0=5h=0101 meaning RAS2 and RAS0 are
on. |
|
 |
Pressing
will then show
the BUS CODE that is used for product development. It details how we internally
map the processor to the Device under Test. This is shown only so the customer
can provide us with this information in case of a compatibility issue. |
|
 |
Problem with the general wiring of the module. |
Open/shorted address, data, or control signals. Many variations
of this error are possible. |
 |
Pressing
reveals more
detailed information on the wiring error. In this case, Data Line 7 is stuck at
0. |
Data Line 7 is pin 26 of the 72p module, or pin 25 of the 30p
module. |
 |
Address signal problem. |
Open or shorted address line. See Manual Section 5.3.2 for
further information. |
 |
Pressing
reveals more
detailed information. In this case, an address row error occurred in Bank 1,
Group 1. |
The 05000000 hex code indicates the error occurred in the 27th
and 25th bit of group 1. Some upper address problems will allow you to continue
testing the module as a smaller device. |
 |
Control Lines Stuck. In this case, CAS0 is stuck at 0. |
This line is either pin 40 of the 72p module, or pin 2 of the 30p
module. |
 |
If F1 Continue was pressed, this screen appears. The test will
not continue anytime a control signal has this type of problem. |
|
 |
Device type does not match the device type in setup. |
Determined via Setup. See Manual Section 6 for further
information on the Setup Mode. |
 |
The DRAM card was setup for testing, but a regular 72pin or 30pin
was detected. |
|
 |
The speed of the module tested was slower than the setup limit of
61nS. |
Determined via Setup. |
 |
The size of the module is different than the setup size of
16Mx32. |
Determined via Setup. |
 |
Byte 1 and Byte 2 are displayed. The last three bits of Byte 1
and the first two bits of Byte 2 failed. |
Currently, the seventh bit of Byte 2 is being tested. Errors in
SINGLE BIT TEST mode will not stop the test. See Manual Section 5.3.5 for
further information. |
 |
A section of memory from the module was tested according to the
SIM CHECK II test table, however, no memory function occurred where one was
expected. |
Possible compatibility problem or major failure in a section of
the memory device. |
 |
Different banks, or groups of data bits of the device exhibit
different sizes. |
Possible size/address problem on one, or more banks of the
module. |
 |
Bank 1, Group 1 of the tested device exhibits a size of 1M. |
Additional error messages are seen by pressing
 . See Manual
Section 5.3.2 for further information. |
 |
Bank2, Group 2 of the same device exhibits a size of 8M. |
|
 |
This message is from the Test Log. The initial mode type detected
was FPM. |
The Test Log records all errors encountered. See Manual
Section 5.3.2 for further information. |
 |
In Bank 2, Group 2, the device exhibited Nibble mode. |
|
 |
Internal software error: Wrong internal test command. |
Rare error. The enduser should not normally encounter this error.
|
 |
Internal software error: Test table wrong entry. |
Rare error. The enduser should not encounter this error. |
 |
Internal software error. |
Rare error, to protect the unit from software hang. Always
followed by a reset and test returning to standby mode. |
| PAGE MODE:Tcac ERROR |
Non-Fatal error encountered during the new page mode test. Test
continues. |
SIMCHECK was unable to determine the exact Tcac (Access Time from
CAS) of the tested module. This error may occur if SIMCHECK incorrectly
identifies a 5V module as 3.3V. Try to setup the test to 5V or change
theTrcd/Trah settings (see INN-8558-APN11). |
