|
| Home |
|
|
Fatal Error MessagesRTUSB-32 calls the system driver function RTUSYSErrorExit whenever an unrecoverable error occurs. can't change endpoint address The OHCI driver was unable to change the address of a newly attached device. can't change pipe notification after first transaction RTUSetPipeCallback or RTUSetPipeMsgQ was called after a pipe has been used for transactions. These functions must be called immediately after RTUOpenPipe. data stage of setup I/O can't be larger than 4k The wLength parameter to RTUSendSetup exceeds 4096, which is not supported. EHCI iso transfer: out of page slots The EHCI driver encountered non-contiguous data within a single frame (not microframe). This can happen when the number of microframes submitted for a High-Speed Isochronous transaction is not an integral multiple of 1 millisecond. EHCI.SendSetup: data stage too large The data stage of a Control transaction does not fit in a single transfer descriptor (about 24k), which is not supported. internal: can't find virtual address to translate An internal error was encountered. Please contact On Time's technical support for assistance. invalid device or ClientCallback in RTUSetClientData The ClientCallback parameter to RTUSetClientData was never passed to RTUClaimInterface, which is not supported. invalid pipe handle A Pipe handle was passed to an RTUSB-32 API function which does not reference an existing pipe, not even a closed one. Closed handles do not cause this error. Rather, they produce error code RTU_INVALID_PIPE. invalid root hub endpoint address A virtual root hub has received an I/O request for a non-existent endpoint. OHCI: out of transactions The OHCI host controller driver has a limit of 255 simultaneously pending transactions, which has been exceeded. out of buffers It was attempted to allocate a buffer for a pipe I/O notification, but no buffers were available. This condition is most likely caused by a memory leak. out of pipe handles RTUSB-32 ran out of pipe handles. This may be caused by an application failing to close pipes when devices are detached. More handles than the default of 256 can be allocated by increasing MaxHandles in RTUSBConfig. out of USB device addresses (possibly due to pipe handle leak) RTUSB-32 was unable to allocate an address for a newly attached device. 127 unique address are available, limiting the number of simultaneously connected device to a single USB to 127 (including the root hub). This error occurs if more than 127 devices are attached or an application has failed to close all pipes, causing the addresses of disconnected devices to remain in use. port in suspended state A device has been detected in the suspended state. RTUSB-32 never uses the suspended state and will try to resume the device. RTUIOWait/RTUIOWaitTimed called on non-Asynch pipe RTUIOWait or RTUIOWaitTimed has been called on a pipe which was previously placed in a different notification mode, which is not supported. RTUSB host controller driver version mismatch A host controller driver registered with RTURegisterUHCI, RTURegisterOHCI, RTURegisterEHCI, or RTURegisterXHCI has an invalid version. RTUSBConfig version mismatch RTUSBConfig.Version contains an invalid value, suggesting that the structure has been corrupted. too many pending transactions on pipe The number of pending transactions on a pipe exceeds the MaxIOs parameter to the corresponding RTUOpenPipe call. too many USB attachment callbacks RTURegisterCallback has been called more than 31 times, which is not supported without recompiling RTUSB-32 (source code required). too many USB host controllers By default, RTUSB-32 is configured to support up to 8 host controllers. This error message indicates that this limit has been exceeded. You must either recompile RTUSB-32 with RTU_MAX_HC set to a larger value (RTUSB-32 source code required) or register fewer host controllers. unable to stop device from resetting A device has been attached and has been reset to initialize it. However, it does not come out of the reset state. unable to take USB host controller ownership The BIOS has claimed ownership of a USB host controller and refuses to release it to RTUSB-32.
|
