Table A.1. Error codes used by the USB system
| Error code | Error | Description |
|---|---|---|
| 0 | USB_RESULT_OK | All OK. Operation performed successfully |
| &819B00 | USB_RESULT_ALIAS_FILE_NOT_FOUND | Alias File could not be opened |
| &819B01 | USB_RESULT_STRUCTUR_DROPPED | Operation could not be executed because it tried to use a structure which has been dropped. Don't use the structure any longer and release every references to it. |
| &819B02 | USB_RESULT_INVALID_PARAMETER | Wrong parameter passed to function |
| &819B03 | USB_RESULT_CONTROLLER_ALREADY_EXISTS | Can occur at usb_controller_register if a controller gets the same name by translation process of the alias file as a controller which has been already registered. Will be the case if you plug in two controllers into your system and did not assign names to them inside alias file. |
| &819B04 | USB_RESULT_BUS_INVALID_INTERNAL_2 | Should never occur. Internal invalid state was detected by USB-Module. Please inform developer about this. |
| &819B05 | USB_RESULT_ILLEGAL_SPEED | Either USB Host Controller is not supporting this speed or the speed is illegal in conjunction with the selected USB-Transfer type |
| &819B06 | USB_RESULT_ALL_DEVICES_USED | All device addresses are in use however. |
| &819B07 | USB_RESULT_DEVICE_ADDRESS_USED | A device address should used for new device which is already in use. |
| &819B08 | USB_RESULT_ENDPOINT_ADDRESS_USED | An endpoint address is already in use. May be used as a standalone and shall be used in both direction or may be in both directions and shall be used in a single direction. |
| &819B09 | USB_RESULT_INVALID_PIPE_STATE | Occurs if an operation shall be done on a pipe and this pipe does not have the correct state (E.G. not open but a request shall be started) |
| &819B0A | USB_RESULT_NO_TRANSACTION_PENDING | Only used by usb_transaction_get_pending function to inform the USB Host controller driver that no transactions are pending. |
| &819B0B | USB_RESULT_ERROR_GENERATED | Used by usb_transaction_result to inform the USB Host controller driver that the transaction result has been changed internally by the USB-Module into an Error. |
| &819B0C | USB_RESULT_NO_OBJECT_FOUND | Used by usb_find_object to inform the caller that the requested object could not be found. |
| &819B0D | USB_RESULT_BUS_CAPACITY_TO_SMALL | Not enough USB capacity at opening a pipe. |
| &819B0E | USB_RESULT_BUS_INVALID_PAYLOAD_SIZE | Maximal data payload size for an endpoint must be one value of 2^x and 0<=x<=10. If not this error will be generated by usb_endpoint_register. |
| &819B0F | USB_RESULT_BUS_INVALID_TRANSFER_TYPE | Shows illegal transfer type at usb_endpoint_register. That means that you either selected an invalid transfer type or that the actual host controller is not supporting this type. In all other situations it shows an heavy internal error. Please inform developer about this. |
| &819B10 | USB_RESULT_BUS_INVALID_INTERNAL_1 | This error should never occur. Please contact Simtec Electronics for further assistance. |
| &819B11 | USB_RESULT_NOT_ENOUGH_MEMORY | Unable to claim a piece of memory |