User`s manual

Chapter 4 Diagnostics
General
Most diagnostics are handled by PGMX. The person that is using
PGMX need only be concerned with the meaning of any error mes-
sage that is issued by PGMX. Other information here is for persons
not using PGMX.
1) All error codes to be issued by the 9000 are preceded by an asterisk,
(*). This makes error trapping very easy.
2) When a non–fatal error occurs (such as when you are using the V
command), no error message is issued and you are returned to the
9000 command prompter when the command completes.
3) FATAL errors are output on a real time basis, that is, they are output
as soon as they are detected, and the programmer returns to the
command state.
4) Fatal Error codes include the address at which the error occurred.
Fatal Error Codes
*WP ERR @ nnnn Won’t Program error: This error is issued only
in the event that the 9000 discovered that it could not change the
data in the chip, even though the bits were not already set. When
using the QuickPulse algorithm, you will not get any *NE errors, only
*WP since the 9000 does not “pre-read” the cells prior to program-
ming.
*NE ERR @ nnnn Needs Erasing error: This error is issued only in
the event the 9000 discovered that it could not change the data in
the chips, and the bits were already set. You will never get an NE
error with the QuickPulse algorithm, because the 9000 does not pre–
read cells to be able to tell that a bit was not set previous to
programming with the QP algorithm.
*CP ERR @ nnnn ComParison error: Issued during comparisons
and verifies (U command).
Model 9000 Diagnostics Chapter 4
Page 17