pSOSystem System Calls - Read

pRPC+ Error Codes Error Codes
B.5 pRPC+ Error Codes
When a pRPC+ system call generates an error, an error code is loaded into an internal
variable that can be read through the macro errno(). One errno variable exists
for each task. If the return value of a pRPC+ system call indicates an error, your
application should examine the errno variable to determine the cause of the error.
See the description of errno() on page 3-27 for more information.
Table B-9 lists the error codes of the pRPC+ subcomponent. Each listing includes
the error code’s hexadecimal number, its mnemonic and description, and the system
calls that can return it. The error code mnemonics are also defined in
.
TABLE B-9 pRPC+ Error Codes
Hex Mnemonic and Description System Call(s)
0x5101 FAT_PRPC_CHKSUM: Corrupted ROM. This error originates in pRPC+
initialization.
0x5102 FAT_PRPC_MEM: Insufficient memory to
hold pRPC+ data.
0x5104 FAT_PRPC_TASKCREATE: Cannot start
pmap.
B.6 Driver Error Codes
The tables below list the error codes returned by pSOSystem drivers. Each driver’s
table lists all the error codes returned by that driver. Error code information includes
hexadecimal numbers, mnemonics and descriptions.
Drivers return error codes through the pSOS+ Kernel-to-Driver Interface using the
out_retval element of the ioparms structure. The contents of out_retval are
copied to the variable pointed to by the service call input parameter retval. The
parameter retval is part of the Application-to-pSOS+ Interface. For example, any
driver errors resulting from a de_read() service call to a driver are returned at the
address pointed to by the retval argument using the following syntax:
err_code = de_read(dev, iopb, &retval);
This error originates in pRPC+
initialization.
This error originates in pRPC+
initialization.
See the chapter “I/O System” in pSOSystem System Concepts for more information
on the pSOS+ Kernel-to-Driver Interface and the Application-to-pSOS+ Interface.
B-44 pSOSystem System Calls