SPI Programming Manual (G06.24+, H06.03+, J06.03+)

Errors
SPI Programming Manual—427506-006
A-6
–6: ZSPI-ERR-XSUMERR
–6: ZSPI-ERR-XSUMERR
Cause. The current buffer checksum does not match the checksum computed on
return from the last SPI call. This error suggests that the buffer has been modified or
damaged.
Effect. The last error is set to this error number, and the requested operation is not
completed.
Recovery. Using a debugging tool such as Inspect, check for inadvertent corruption of
the buffer contents.
–7: ZSPI-ERR-INTERR
Cause. This internal error should not occur unless the SPI software malfunctions.
Specific causes include:
•
SSGET attempted to return a token value when the program had requested a
token attribute (such as length, offset, address, or count).
•
SSGET attempted to return an undefined token attribute.
•
On returning, SSGET or SSPUT attempted to set a used length greater than the
buffer length.
•
SSPUT received an error when calling SSGET to obtain the default subsystem ID
(ZSPI-TKN-DEFAULT-SSID) from the SPI message header.
Effect. The last error is set to this error number, and the requested operation is not
completed.
Recovery. Report the problem to your HP representative, supplying a reproducible
test case.
–8: ZSPI-ERR-MISTKN
Cause. One of:
•
The token requested in a call to SSGET was not found.
•
An attempt was made to put a ZSPI-TKN-ENDLIST token into the buffer, but no
corresponding list token was found.
Effect. The last error is set to this error number, and the requested operation is not
completed.
Recovery. Corrective action depends on the application. Check for program logic
errors in scanning the buffer. Also check to see if the token is positioned outside the
current list or preceding the current position.